05 · The codebase
Read the codebase like a book
There are two ways into a codebase: the story and the map. Below, both — a guided tour that walks the code in the order it makes sense to read it, and a browsable atlas of every core file grouped by architectural layer. Take the tour first; come back to the atlas whenever you need to find something. Everything here is rendered from the system's own analysis of its code, not hand-written copy.
Before you start
The whole system in three sentences
- A message becomes a self-driving task. The bridge hears you, 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. If you get lost, come back here and ask which sentence you are inside.
01 · The story
The guided tour, 13 steps
A pedagogical 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 — one clean seam per responsibility. Pick a layer, then open any file to see its functions, classes, and import relationships. Use the filter to hunt for anything the tour mentioned.