The build-loop, end to end
The four core phases left to right, input to output, plus iterate, closeout, and learn. Click a phase to expand its sub-steps; click any phase, step, gate, agent chip, or role for detail.
Per session, real SessionStart hooks (retrieval, memory, architecture) also fire — they live in the data's hooks, not as a role.
- user goal / prompt
- repo + git state
- build-loop memory
Reads the live repo, past build-loop memory, and docs, then writes intent, goal, pass/fail acceptance probes, and the trigger flags (such as risk-surface and UI) that later phases read.
MECE partition plus dependency order.
N implementers edit their own files in parallel under a single-writer commit protocol.
Seven sub-steps A-G.
Phase 5 is a LOOP, not a forward stage: on a Review failure it escalates a stuck cascade by failure count, applies a fix, and loops BACK to Review (up to 5 classic / 25 autonomous).
Runs by default.
Always emits a ## Learn line.
- committed, validated change
- ## Learn outcome + drafts