Each loop (lane) is a full autonomous cycle running a fixed spine — intent → scout → triage → tdd → build-planner → build → audit → ship (the literal spine_order of docs/architecture/phase-registry.json; its trailing end entry is a graph sentinel, and retrospective/memo are optional post-ship phases, not spine) — plus goal-type-conditional insertions around tdd/build such as test-amplification, secret-leak-scan, flake-rerun-scan, error-handling-scan, coverage-gate, and adversarial-review (from the registry’s goal recipes; not universal phases). Each lane works in its own git worktree against a weighted task queue. A supervisor dispatches N lanes per wave; a trust kernel binds audit verdicts to exact trees and reserves git commit for evolve ship. Lanes racing to land rebase and re-audit.
| 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), absolute pins, 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).