I2965 — The site says a test proves a guarantee only as far as recorded evidence supports it
Qualify every site sentence that says a test proves a guarantee, or that work ends proven, to what the recorded evidence supports, and declare the proof words as homepage promises so the existing homepage check refuses them in the hand-written copy unless a supported claim permits them.
DONE wave 0 · p0 · implementation profile · parallel safe
Part of development-runtime — The runtime has a development surface.
Objective
Qualify every site sentence that says a test proves a guarantee, or that work ends proven, to what the recorded evidence supports, and declare the proof words as homepage promises so the existing homepage check refuses them in the hand-written copy unless a supported claim permits them.
Why
Truth sweep 2026-10-18 (f6, S9 and S20, verified): the guarantees index (scripts/generate-site-data:1919) said 'What Majordomus actually does today, row by row, with the file that implements it and the test that proves it', docs/SITE_CLAIMS.md (generate-site-data:2370) 'the test that proves it', site/data/challenge.toml:28 'the test that proves the guarantee', and the homepage section title (site/data/marketing.toml:34) 'From first prompt to proven done', while site/data/registry/product.json records evidence declared 229, supported 0. homepage.toml [promises] holds capability words to supported claims and did not name the proof words.
Current state
Corrected in this change: the guarantees index and SITE_CLAIMS say the test that is to prove a claim and what its recorded run says; the challenge page says the test meant to prove it; the homepage title is 'From first prompt to a checked finish'; [promises] declares proven and proves; the claim evidence-navigates-both-ways names the test meant to settle it rather than the test that proves it.
Desired state
No site sentence says a test proves a claim while the evidence supports fewer claims than are declared, and case 3366 refuses one; the homepage check refuses proven or proves in the hand-written copy until a guaranteed, supported claim permits it.
Scope
- scripts/generate-site-data
- site/data/challenge.toml
- site/data/marketing.toml
- site/data/homepage.toml
- docs/CLAIMS.yaml
- docs/claims/evidence-navigates-both-ways.md
- test/cases/3366_a_proof_word_is_earned.sh
Dependencies
None. This issue is a root of the graph.
What waits on this
Acceptance criteria
- The guarantees index, SITE_CLAIMS and the site's data say a test is to prove a claim while not every claim is supported
- homepage.toml [promises] declares proven and proves, and the homepage copy uses neither
Validation
- majordomus plan validate
Evidence required
- case_a_proof_word_is_earned
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| case_a_proof_word_is_earned | test | bash test/run.sh 3366_a_proof_word_is_earned | 14 passed, 0 failed, 0 skipped on master dd4c0a87cba | dd4c0a8 |
Timeline
- started
- 2026-10-19T13:59:08Z
- verified
- —
- completed
- 2026-10-19T13:59:33Z
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/I2965.yaml. Read it back with majordomus plan show I2965.