I1123 — The milestone is accepted on its evidence
Close the milestone: every acceptance criterion carries evidence, the measured baselines are recorded with the environment they were taken on, the adoption and removal run as documented on a clean checkout, and the remaining limitations are stated.
BLOCKED wave 8 · p0 · implementation profile · runs alone
Blocked. This issue cannot start until I1104, I1107, I1115, I1117, I1118, I1119, I1120, I1122 are done. The status is derived from that, not declared.
Objective
Close the milestone: every acceptance criterion carries evidence, the measured baselines are recorded with the environment they were taken on, the adoption and removal run as documented on a clean checkout, and the remaining limitations 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 footprint, the budgets and the limitations written where they will be found.
Scope
- docs/PLAN_STATUS.md
- .ai/repo/project
Out of scope
- Reporting a mechanism as proved without the artifact that proves it
Dependencies
- I1104BLOCKED Both namespaces carry their contracts, all the way down
- I1107BLOCKED Discovery is deterministic, cached, and its cost is known
- I1115BLOCKED Completion comes from the command model, not from a second list
- I1117BLOCKED The hand-maintained lists are removed, not left running beside the derivation
- I1118BLOCKED Every invariant of this milestone is a rule with a check that runs
- I1119BLOCKED The budgets are measured, and a regression fails rather than being noticed
- I1120BLOCKED A refusal says what to do about it
- I1122BLOCKED A foreign repository, adopted, upgraded and given back
Acceptance criteria
- Every acceptance criterion of the milestone has evidence recorded against it
- The measured footprint of an adoption is recorded — every path, with its namespace and its owner
- The budgets are recorded with the machine and environment they were measured on
- The documented adoption and removal run exactly as written 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
- footprint_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 long 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/I1123.yaml. Read it back with majordomus plan show I1123.