A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I0015

Open the first real milestone and execute one issue through it

Where it stands

Readiness: complete completion is recorded and every required evidence token is present
Status: DONE
Can start: not now
Milestone: M000
Milestone status: DONE
Wave: 8
Waiting on: none
Holds back: none
Behind it in all: 0
Evidence: 1 of 1

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.
Now: M000 was executed partly outside the system, because the system did not exist when it began.
Wanted: 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.
Done when: unknown: the record declares no `completion`
Risk: Choosing a milestone to make the demonstration easy would defeat the purpose.

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

Adapter: scripts/github-sync
Repository: unknown: the derived plan's header carries no repository
External issue: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Nothing is wrong with these records.