I0843 — The performance workflow is discoverable and complete
Close the milestone: every acceptance criterion of M004 has evidence, the README workflow runs as written, the site is regenerated, and the final report is a plan record rather than a conversation.
BLOCKED wave 6 · p0 · implementation profile · runs alone
Part of M004 — Performance is executable evidence, and the hot path does no canonical work twice.
Blocked. This issue cannot start until I0831, I0835, I0841, I0842 are done. The status is derived from that, not declared.
Objective
Close the milestone: every acceptance criterion of M004 has evidence, the README workflow runs as written, the site is regenerated, and the final report is a plan record rather than a conversation.
Why
A milestone is accepted by its evidence, not by finishing its issues.
Current state
Open.
Desired state
M004 accepted with evidence on every criterion.
Scope
- docs/PLAN_STATUS.md
- .ai/repo/project
Dependencies
- I0830DONE docs/PERFORMANCE.md, README, CONTRIBUTING and CLI reference
- I0831BLOCKED Performance claims at their proven status
- I0835BLOCKED CI runs the structural performance checks
- I0841BLOCKED Cache equivalence proved by property-shaped cases
- I0842BLOCKED Before and after evidence for every optimisation
Acceptance criteria
- plan validate passes and M004 reports every evidence_required token satisfied
Validation
- bin/majordomus plan validate
- bin/majordomus plan status
Evidence required
- docs_integrated
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 last issue is the one that checks the others honestly.
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/I0843.yaml. Read it back with majordomus plan show I0843.