Handbook
Deliver milestones
Platform delivery is organized in milestones (M0–M6) plus a self-host alpha track. Each milestone has a charter, charge, and evidence folder. This hub lists charters — not every evidence artifact.
Hub · Updated
Milestone themes
M0 — Platform charter
Scope, outcomes, and governance baseline
M1 — ForgeRun spine
Evidence and run lifecycle contracts
M2 — Lenses control plane
Workspace visibility before automation
M3 — Governed reasoning
LCDL tasks inside Platform boundaries
M4 — Controlled execution
Fleet jobs with explicit argv boundaries
M5 — Agent workcells
Catalog, runners, and campaign phases
Milestone charters
| Milestone | Focus | Charter |
|---|---|---|
| M0 | Platform charter | Charter |
| M1 | ForgeRun spine | Charter |
| M2 | Lenses control plane | Charter |
| M3 | Governed reasoning | Charter |
| M4 | Controlled execution | Charter |
| M5 | Agent workcells | Charter |
| M6 | Channel ingress | Charter |
| Self-host alpha | Vertical demo | Charter |
How sprints relate to the handbook
- Sprint structure — naming, folders, and evidence expectations
- Milestone plan — planning view across milestones
- Roadmap — product-facing timeline
Maintainer note
Evidence logs, fixtures, and samples under each sprints/*/evidence/ and fixtures/ remain in the repo for audit — browse from the milestone folder when reviewing a specific charge.