I0831 — Performance claims at their proven status
Add claims to docs/CLAIMS.yaml for derived benchmark targets, separated cold and warm distributions, flatten-once, cache equivalence and regression refusal, each naming its case, and regenerate the site data.
BLOCKED wave 5 · 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 I0822 is done. The status is derived from that, not declared.
Objective
Add claims to docs/CLAIMS.yaml for derived benchmark targets, separated cold and warm distributions, flatten-once, cache equivalence and regression refusal, each naming its case, and regenerate the site data.
Why
The claims matrix is where a guarantee is stated once and the site reads it.
Current state
No performance claim exists.
Desired state
Guaranteed claims for what cases prove, planned for what is deferred, each with a claim page.
Scope
- docs/CLAIMS.yaml
- docs/claims
- docs/SITE_CLAIMS.md
- site/data/generated
Dependencies
- I0822BLOCKED Every canonical file is flattened at most once per command
- I0826DONE bench --check refuses a regression by policy
What waits on this
Acceptance criteria
- Every guaranteed claim names an existing case
- generate-site-data --check is in sync
Validation
- scripts/generate-site-data --check
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
A claim named guaranteed without a case is refused by the generator.
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/I0831.yaml. Read it back with majordomus plan show I0831.