05 · The codebase
The codebase: a tour and an atlas
This page holds two views of the same code. The guided tour walks the files in the order that makes sense to read them, and the atlas lists every core file grouped by architectural layer. Both are rendered from the system's own analysis of its code rather than from hand-written copy.
Before the tour
The whole system in three sentences
- A message becomes a self-driving task. The bridge receives the message, a durable AgentSession in Redis carries the work, and a worker drives it to done.
- The SDLC pipeline is a guarded graph. Plan through Merge, with failure edges that loop back and loop caps that stop the spin.
- It maintains itself. Subconscious memory carries lessons forward; reflections, a failure-loop detector, and a watchdog keep it healthy with no human in the loop.
Every step of the tour hangs off one of these three sentences.
01 · The story
The guided tour, 13 steps
A walk in reading order: from the README, down the runtime spine, through the pipeline and memory, out to the dashboard. Each step names the exact files to open and why they matter.
02 · The map
The atlas: every core file, by layer
The machine analysis assigned every core file to exactly one architectural layer. Selecting a layer lists its files, and opening a file shows its functions, classes, and import relationships. The filter narrows the list by path, summary, or tag.