Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I0831

Performance claims at their proven status

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
Milestone status
ACTIVE
Wave
5
Waiting on
Holds back
Behind it in all
1
Evidence
0 of 1
In the waySubjectDetail
issueI0822I0822 is not DONE
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I0831

majordomus plan verify I0831

majordomus plan done I0831

What it is

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.
Now
No performance claim exists.
Wanted
Guaranteed claims for what cases prove, planned for what is deferred, each with a claim page.
Done when
unknown: the record declares no `completion`
Risk
A claim named guaranteed without a case is refused by the generator.

Acceptance

  • 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 present
unknown: the record carries no `evidence` entries

Scope

Touches
docs/CLAIMS.yamldocs/claimsdocs/SITE_CLAIMS.mdsite/data/generated
Not
none
Depends on
Priority
p0
Profile
implementation
Parallel safe
false
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-05
Updated
2026-09-05
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.