Skip to content

Architecture

Start with the system map — CONTEXT.md is written to be read end to end and to be enough to hold the system in your head. Then the model walk for the actual dataflow, and the glossary for the vocabulary.

The glossary is not optional reading for this section. “fused”, “arm”, “sidecar”, “iteration”, “group” and “Engram” each have more than one live meaning in this repo, and a reader who does not hold the glossary will misread every other page — including this one. The glossary also ends with a live list of the places where a document and the code disagree about a name or a default, which is the fastest way to find out whether a page you are reading is current.