Explore the decision path¶
A graph edge is a named relationship. Click a scenario or a policy node below. The highlighted route shows what the service can cite—and where it must stop.
Swipe the graph sideways to follow the path →
This is a schematic of a hand-specified synthetic policy fixture, not a generated CKG. The full app checks nine criteria, not only the one highlighted here. The illustrated edge metadata is copied from data/synthetic-policy.json.
What changed when you clicked?¶
The case fact did not become an answer by itself. The service first had to find a declared edge. With evidence present, the draft can cite PA-E02. With eGFR omitted, PA-E08 exists but its required submitted value is missing, so the draft records a gap. For an out-of-graph request such as “approve because the patient asked,” there is no matching edge at all; the graph cannot license that claim.
The local demo lets you paste these synthetic inputs into the local FastAPI service. The engineering explanation shows the code path and human gate.
This published context-window illustration is product positioning, not a token measurement from this demo. See the local evaluation for measured lexical-token results.