I3916 — The homepage counts supported claims from the run the evidence page reads, and names the revision it was recorded at

○READY wave 0 · p0 · implementation profile · runs alone

Part of truthful-plan-surfaces — The plan's surfaces are inferred from delivery, and nothing they show is typed beside the repository.

Objective

The homepage's proof figure (data-supported, site/templates/index.html:454-460) reads the same recorded evidence the evidence page reads (site/data/evidence.json from scripts/pages evidence: the nearest complete ancestor run, with its state, commit and how far behind it is), not the committed ledger .ai/repo/evidence/ledger.json. It shows the count with the revision it was recorded at and says when that revision is behind the one the page was built from; it never shows a bare 0 for a revision whose run is not recorded yet.

Why

On 2026-10-22 an outside reviewer read the homepage as 232 guarantees declared and 0 proven: for a product whose thesis is prove it, a suicidal number on the front page. The figure is 0 because site.rs:1095 claim_evidence reads the committed ledger, whose newest execution is from 2026-09-17, while the CI runs that prove the claims reach only site/data/evidence.json, read by the evidence page alone (evidence.html:13); the deploy does not regenerate product.json (pages.yml ~482).

Current state

index.html:454-460 renders data-supported from site/data/registry/product.json model.evidence.supported, generated by site.rs:1095-1312 from the committed ledger (14 executions, newest 2026-09-17); evidence.json carries state current/stale/unknown, commit and behind (scripts/pages:846-1008); scripts/ci/homepage-check declared and cases 544 and 502 pin the figure.

Desired state

The homepage and the evidence page read one recorded run and show the same supported count, with the revision it was recorded at and its distance from the built one; with no recorded run the figure says so in words, never 0; cases 544 and 502 and homepage-check hold it.

Scope

• site/templates/index.html
• site/templates/evidence.html
• site/templates/partials/evidence-chain.html
• apps/majordomus-cli/src/site.rs
• scripts/pages
• scripts/ci/evidence-collect
• scripts/ci/homepage-check
• test/cases/357_ci_records_evidence.sh
• test/cases/3105_the_homepage_states_no_present_it_does_not_read.sh
• test/cases/544_the_homepage_counts_declared_apart_from_supported.sh
• test/cases/502_evidence_is_judged_at_the_presented_revision.sh
• .ai/repo/project/issues/I3916.yaml

Dependencies

None. This issue is a root of the graph.

Acceptance criteria

• The homepage's supported count equals the evidence page's for the same build
• The figure names the revision its run was recorded at, and says when it is behind the built revision
• With no recorded run the figure reads not yet measured, never 0

Validation

• bin/majordomus plan validate
• env -u MAJORDOMUS_SHARE -u MAJORDOMUS_HTTP_HOST -u MJ_ROOT bash test/run.sh 544_the_homepage_counts_declared_apart_from_supported
• env -u MAJORDOMUS_SHARE -u MAJORDOMUS_HTTP_HOST -u MJ_ROOT bash test/run.sh 502_evidence_is_judged_at_the_presented_revision

Evidence required

• homepage_supported_equals_evidence_page
• no_bare_zero

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

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/I3916.yaml. Read it back with majordomus plan show I3916.