Engineering blog
How we build ReasoningLayer
Notes on the engine, the products we build on top of it, and the problems they solve. Written by the team that ships them.
Are we fast yet? Benchmarking interactive exact scheduling
The performance story behind the interactive scheduler: the exact three-colour map in milliseconds — 128 ms on a zero-slack regional hospital where OR-Tools times out on sixteen cores — sub-second on every click (and dropping as you pin), flat memory across a long session, plus an honest list of where we are not fast yet.
Read moreThe world model AI is missing, and the engine built to hold it
LLMs hallucinate because they have no model of the world, only a model of text. Here is the reasoning layer built to fix that: RDF, OWL, SHACL and SUMO on one substrate, complete OWL 2 RL reasoning, and the fastest against six other engines across three head-to-head benchmarks.
Read moreAccess control that explains itself, with ReasoningLayer
Permissions become a handful of rules instead of thousands of rows. Every grant is derived on demand, and every answer comes back with the proof behind it.
Read moreInteractive scheduling with ReasoningLayer, a nurse scheduling use case
A scheduling tool whose job is not to draft the rota for you, but to keep every valid rota visible while you decide one cell at a time.
Read more