Roadmap, specs and plans
Where Redline is going, why it stops where it does, and the record of how each piece was actually built.
A spec agrees the shape and the order of a body of work and decides nothing about implementation. A plan is what a spec's phase was executed from, task by task, written before the code and kept afterwards. Neither is distributed to onboarded repositories, and no CI check reads them — which also means nothing catches a stale claim in one, so treat the repository as the authority where they disagree.
Start with the roadmap: eight pieces across five phases, with Phase 0 — distribution and a baseline measurement — gating everything after it, because the rest does not compound until a standards change can reach the estate without human shepherding.
Roadmap after the Harness evaluation →
Eight pieces across five phases, and the boundary between what Redline governs and what a delivery platform does. Phase 0 gates everything after it.
Redline v3 design →
The design the roadmap builds on. Every non-goal and decision in it still holds.
Registry discovery (Phase 0.1) →
The plan for the derived register of onboarded repositories. Implemented — this is the record of how.
v3 hardening →
The hardening pass executed after v3 phase 1.
v3 phase 1 →
The plan the v3 CLI was executed from.