I0932 — The milestone is accepted on its evidence
Close the milestone: every acceptance criterion carries evidence, the measured baselines are documented with the environment they were taken on, the workflow in the documentation runs as written, and the outcome is a plan record rather than a conversation.
BLOCKED wave 9 · p0 · implementation profile · runs alone
Blocked. This issue cannot start until I0920, I0923, I0925, I0926, I0927, I0928, I0929, I0931 are done. The status is derived from that, not declared.
Objective
Close the milestone: every acceptance criterion carries evidence, the measured baselines are documented with the environment they were taken on, the workflow in the documentation runs as written, and the outcome is a plan record rather than a conversation.
Why
A milestone is accepted by its evidence. The numbers, the commands and the deployed URL are what a later reader has; this session's messages are not.
Current state
Open.
Desired state
The milestone is accepted with evidence against every criterion, and the baselines and limitations are written where they will be found.
Scope
- docs/PLAN_STATUS.md
- .ai/repo/project
Out of scope
- Reporting a plan as an implementation
- Recording a measurement without the environment it was taken on
Dependencies
- I0920BLOCKED The image's dependencies are known and its advisories are policy
- I0923BLOCKED Cold start and endpoint cost are benchmark targets like everything else
- I0925BLOCKED Every deployment rule is a check that runs
- I0926BLOCKED The deployment documentation is generated and reachable
- I0927BLOCKED The cockpit shows the deployment from the same data
- I0928BLOCKED A pull request cannot merge a deployment that would not work
- I0929BLOCKED Production deploys from CI with a token scoped to one application
- I0931BLOCKED The application exists, one machine runs it, and the URL answers
Acceptance criteria
- Every acceptance criterion of the milestone has evidence recorded against it
- The measured baselines — binary, image, context, build durations, readiness, resident memory, endpoint latency — are documented with the machine and environment they were measured on
- The developer workflow in the documentation runs 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 deploy doctor
Evidence required
- baselines_documented
- criteria_covered
- report_recorded
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 temptation at the end is to record intent as outcome. Anything not demonstrated is a limitation, and it is written as one.
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/I0932.yaml. Read it back with majordomus plan show I0932.