Docs / Architecture Learn
Query Execution
How search, EKL, graph traversals and ask run against the ledger.
| Surface | Path |
|---|---|
ekos query find, ekos_search |
search index → ranked ids |
ekos ekl, ekos_ekl |
parser → interpreter → ledger |
ekos_state, ekos_neighborhood, ekos_dependents, ekos_impact |
Runtime graph reads |
ekos_query |
fact lookup or named traversal → typed claims, no LLM |
ekos ask |
understand → plan → retrieve → LLM synthesis → citation validation |
ekos check refs, ekos_xref_check |
the integrity index written at commit (or a fresh recompute) → findings with evidence |
ekos review, ekos workflow status, ekos_signoff_status |
review subjects and sign-off validity, recomputed from digests on each read |
Everything through the Runtime is read-only. In a distributed deployment the same queries go through a gateway that fans out to query workers, merges per-shard statistics and fuses the rankings.