Context Engine · Architecture

An orchestrator that never reads, and readers that never write

A scheduled run reads its state note, lists every recording in the window, and dispatches one reader per recording. The readers return structured extractions; only the orchestrator writes — to the knowledge base, the digests and the state note. There is no arrow to a task database, on purpose. Hover anything for detail.