Milestones

Milestones M0–M9 map onto Phases P0–P6 (with M3 split across P2 and P3, and M9 closing P6’s visualization polish). Each milestone’s acceptance document is republished here; the verification notes (internal harness logs) are intentionally not surfaced — they are ephemeral test artifacts.

Acceptance index

Milestone	Phase	Acceptance
M1 (T6)	P1	Index pipeline trust gates
M2 first half	P1	Scraper/parser/patches
M2 second half	P1	Validation + release gate
M3 first half	P2 + P3	Backend runtime spine + state store
M3 second half	P2 + P3	Anonymous lifecycle endpoints
M4 first half	P4	Direct evaluator + query envelope
M4 second half	P2 + P4	Typed graph view endpoints
M5 / M6	P5 + P6	Frontend shell + atlas v1
M7 beta	post-P6	Soft-beta acceptance
M8 solver expansion	P8	In-process demo adapters
M9 visualization polish	P6	Atlas polish + shareable views

The acceptance documents themselves live in the repository under docs/qa/m*-acceptance.md. They are not republished on this site by direct link because the M-numbering is internal — readers find the acceptance evidence via the Roadmap page or by following the spec / ADR cross-references.

For the course-count reconciliation between uwwoe’s index and Waterloo’s public Math course-count claims, see Math course count reconciliation.

For the measured Canva performance baseline on the 1,925-course universal projection, see Universal Canva performance baseline.

What constitutes acceptance

A milestone acceptance document records:

• Each gate the milestone was required to pass.
• The contract, behavior, or evidence proving the gate.
• The commit SHA(s) that landed the gate.
• Any caveat or follow-up tracked into a later milestone.

Verification notes (the per-milestone m*-verification-notes.md files) record the harness state during the gating run — fixture seeds, test outputs, environment specifics. Those are debugging aids; the acceptance documents are the durable record.