Reference
Glossary, architecture maps, and deep dive companion docs.
Foundation Documents
Architecture Overview
The big-picture map. Come back here whenever you feel lost about where a chapter fits.
Why This Chapter Order
Explains why the curriculum is ordered this way and what breaks when the sequence is rearranged.
Code Reading Order
Shows which local `agents/*.ts` files to open first and what state or functions to inspect before the code turns into noise.
Reference Module Map
Maps the reference repo's real module clusters onto the current curriculum to validate the chapter order.
Teaching Scope
What this repo teaches, what it deliberately leaves out, and why.
Glossary
Bookmark this. Come back whenever you hit an unfamiliar term.
Data Structure Map
Every important record in one place. Use when you lose track of where state lives.
Entity Map
Use this when concepts start to blur. It tells you which layer each thing belongs to.
Deep Dive Documents
Query Control Plane
Why the simple loop needs a coordination layer as the system grows. Best read after Stage 1.
One Request Lifecycle
Traces one request from entry to write-back. Best read after Stage 2 when pieces need connecting.
Query Transition Model
Why each continuation needs an explicit reason. Best read alongside s11 (Error Recovery).
Tool Control Plane
Why tools become a coordination layer, not just a lookup table. Best read after s02.
Tool Execution Runtime
How multiple tool calls in one turn get executed safely. Best read after s02.
Message-Prompt Pipeline
The full input pipeline beyond system prompt. Best read alongside s10.
Runtime Task Model
The most common Stage 3 confusion: two meanings of 'task'. Read between s12 and s13.
Teammate-Task-Lane Model
Five concepts that look similar but live on different layers. Keep open during s15-s18.
MCP Capability Layers
MCP is more than external tools. This shows the full capability stack. Read alongside s19.