I1030 — The milestone is accepted on its evidence
Close the milestone: every acceptance criterion carries evidence, the measurements are recorded with their environment, the contributor workflow runs as written, and the remaining gaps are stated.
BLOCKED wave 7 · p0 · implementation profile · runs alone
Blocked. This issue cannot start until I1010, I1013, I1017, I1020, I1024, I1026, I1027, I1028, I1029 are done. The status is derived from that, not declared.
Objective
Close the milestone: every acceptance criterion carries evidence, the measurements are recorded with their environment, the contributor workflow runs as written, and the remaining gaps are stated.
Why
A milestone is accepted by its evidence. What a later reader has is the record, not this session.
Current state
Open.
Desired state
Accepted with evidence against every criterion, with the coverage baseline and the limitations written where they will be found.
Scope
- docs/PLAN_STATUS.md
- .ai/repo/project
Out of scope
- Reporting a derived surface as proved without the artifact that proves it
Dependencies
- I1010READY The overview is what exists, counted rather than claimed
- I1013BLOCKED Search over the graph, generated, with nothing to run
- I1017BLOCKED Live state is an overlay that degrades to nothing
- I1020BLOCKED The graph's health is answered by the doctor that already answers everything else
- I1024BLOCKED The interface has a weight, and it is measured
- I1026BLOCKED The architecture explains itself, from inside itself
- I1027BLOCKED A synthetic capability proves the architecture instead of describing it
- I1028BLOCKED The inventories this replaces are removed, not left running beside it
- I1029BLOCKED The gate refuses what would silently break the interface
Acceptance criteria
- Every acceptance criterion of the milestone has evidence recorded against it
- The coverage matrix baseline is recorded as a starting measurement rather than presented as a verdict
- The contributor workflow runs exactly as documented on a clean checkout
- Pre-existing failures, failures introduced here and failures fixed here are distinguished explicitly
- Remaining limitations are stated rather than omitted
Validation
- bash test/run.sh
- bin/majordomus doctor
- majordomus generate --check
Evidence required
- criteria_covered
- baseline_recorded
- limitations_stated
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Risk
The end of a large milestone is where intent gets recorded as outcome. Anything not demonstrated is written as a limitation.
Timeline
- started
- —
- verified
- —
- completed
- —
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/I1030.yaml. Read it back with majordomus plan show I1030.