Each loop (lane) is a full autonomous cycle. It runs a fixed spine: intent → scout → triage → tdd → build-planner → build → audit → ship. This order is the literal spine_order of docs/architecture/phase-registry.json. Its last entry, end, is a graph sentinel. retrospective and memo are optional phases after the ship, not part of the spine.
For some goal types, the goal recipes of the registry insert more phases around tdd and build. Examples are test-amplification, secret-leak-scan, flake-rerun-scan, error-handling-scan, coverage-gate and adversarial-review. These phases are not universal. A code cycle that touches files also runs code-review between build and audit (conditional_mandatory, ADR-0124; in shadow since v22.27.0).
Each lane works in its own git worktree. It takes tasks from a queue in the order of a computed rank (ADR-0121). A supervisor dispatches N lanes per wave. A trust kernel binds audit verdicts to exact trees, and it reserves git commit for evolve ship. If lanes race to land, they rebase and audit again.
| Feature | In one line |
|---|---|
| Fleet width | How exactly N concurrent loops are delivered — through benches, walls, and live width changes |
| Phase pipeline | A config-defined machine with a non-negotiable ship floor |
| Trust kernel | Enforcement that survives a lying model — guards, allowlists, audit↔tree binding |
| Bridge & drivers | LLM CLIs run like industrial equipment: liveness probes, exhaustion detection, exit contracts |
| Model routing | Tiers (fast/balanced/deep/top), one routing table, fallback chains and an advisor on a leash |
| Quality gates | EGPS predicates, coverage graduation, adversarial audit — what makes PASS mean something |
| Ship & release | The only doors out of the repo — and the binary-deletion defect on the success path |
| Token telemetry | Measuring what every phase burns — and the silent outage that almost hid it |
| Queue integrity | Every "done" claim verified at the system that owns the truth |
| Chronicle | Turning yesterday’s lessons into today’s planning context |
| Resilience | Crashes, cascades, and quota walls as survivable, self-healing states |
docs-code-alignment-2026-07 campaign, plus two behavior defects (inert phase-guard hook; manual-ship binary deletion).