I0015 — Open the first real milestone and execute one issue through it
Prove the system on real repository work: open a milestone that exists because the repository needs it, and take one of its issues from READY to DONE entirely through the model.
DONE wave 8 · p0 · deep-work profile · runs alone
Part of M000 — Milestone and DAG driven development.
Objective
Prove the system on real repository work: open a milestone that exists because the repository needs it, and take one of its issues from READY to DONE entirely through the model.
Why
Infrastructure that has never carried real work is a demo. The cutover is the only evidence that the discipline is usable.
Current state
M000 was executed partly outside the system, because the system did not exist when it began.
Desired state
A real post-bootstrap milestone exists, one of its issues is DONE with evidence recorded through plan evidence, and the graph has recomputed the next ready issue.
Scope
- .majordomus/project
Out of scope
- A synthetic demonstration milestone
Dependencies
- I0012DONE Make CI refuse an invalid model or a stale projection
- I0014DONE Make the worker instructions require the model
Acceptance criteria
- The milestone addresses a defect or gap the repository already recorded, not one invented for this issue
- One issue moved READY to ACTIVE to VERIFY to DONE through the command surface
- The evidence attached to it is a command and its result, not a narrative
- The next ready issue after it is derived, not chosen
Validation
- bin/majordomus plan status
- bin/majordomus plan next
Evidence required
- lifecycle
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| lifecycle | manual | bin/majordomus plan start I0101 && plan verify I0101 && plan evidence I0101 --covers gap_reproduced ... && plan done I0101 && plan next | M001 opened from docs/CLAIMS.yaml's blocker-survives-handover, a planned claim with no implementation and no test. I0101 went READY to ACTIVE to VERIFY to DONE through the command surface; its evidence is bash test/run.sh 50_blocker_across_handover with its result; the graph then derived I0102 as the next ready issue without anybody choosing it | 05423af |
Risk
Choosing a milestone to make the demonstration easy would defeat the purpose.
Timeline
- started
- 2026-09-04T05:15:05Z
- verified
- 2026-09-04T05:15:06Z
- completed
- 2026-09-04T05:15:08Z
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I0015.yaml. Read it back with majordomus plan show I0015.