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

I1960

Every widget names its proof

Where it stands

devtask.issue

Readiness: blocked 2 of its dependencies are not DONE
Status: BLOCKED
Can start: not now
Milestone: test-evidence
Milestone status: ACTIVE
Wave: 5
Waiting on: I1958 I1959
Holds back: I1962 I1963
Behind it in all: 3
Evidence: 0 of 2

In the way	Subject	Detail
issue	`I1958`	I1958 is not DONE
issue	`I1959`	I1959 is not DONE

Moves

plan.transition

What it is

Objective: Render one evidence badge on every widget that states behaviour, linking to its subject's route with the verdict at the published commit, and compute the delivery report's required_tests_current and test_evidence_published dimensions as ADR 0087 decision 3 says.
Why: Nothing ties a site widget to a subject: where a page says verified, the word was placed by hand, and the delivery report's test dimensions are pending for want of a verdict to read.
Now: Widgets carry no subject badge; the proof partial of PR #626 is a separate component; the delivery dimensions are pending on PR #600.
Wanted: One partial, evidence-badge.html, is a plain link with a glyph, a text and a label, and renders unknown for a subject missing from the dataset, never nothing; every widget header carries it and the proof partial is absorbed into it; homepage-check budgets bytes per badge; required_tests_current passes only on a proven subject verdict at the trunk revision, and test_evidence_published reads the site's publication.
Done when: unknown: the record declares no `completion`
Risk: It also waits on PR #593, PR #600, PR #621 and PR #626; the delivery module exists only once PR #600 has landed. required_tests_current as ADR 0087 decision 3 words it passes only after a quiet trunk: a code merge between a trunk run's commit and the landing of its recording leaves the subject inputs_unchanged or stale, never proven (ADR 0087, Consequences). The owner decides before this lands whether the process makes proven reachable at the trunk or the dimension binds to a reachable state.

Acceptance

Every widget that states behaviour carries one badge linking to its subject's route, and a subject missing from the dataset renders unknown
The badge renders verified only for a proven verdict at the published commit
The badge is a plain link that works without JavaScript and fits a phone-width viewport
Each badge stays under its byte ceiling in homepage-check
The delivery report's test dimensions read the subject verdict and the site's publication, and never a CI run's own rows

Validation: bash test/run.sh 520_every_widget_names_its_proofbash test/run.sh 333_homepage_narrativescripts/ci/homepage-check
Evidence required: every_widget_names_its_subjectdelivery_test_dimensions_computed
Evidence present: unknown: the record carries no `evidence` entries

Scope

Touches: site/templates/partials/evidence-badge.htmlsite/templates/partials/terminal-figure.htmlsite/templates/partials/terminal.htmlsite/templates/partials/cli-examples.htmlsite/templates/partials/api-operation.htmlsite/templates/partials/proof.htmlsite/templates/index.htmlsite/templates/feature.htmlsite/templates/claim.htmlsite/templates/use-case.htmlsite/templates/components.htmlsite/data/homepage.tomlscripts/ci/homepage-checkapps/majordomus-cli/src/delivery/mod.rstest/casestest/cases/333_homepage_narrative.shdocs/CLAIMS.yamldocs/claims.ai/repo/features/evidence.md
Not: Alpine, details elements or an interaction spec for the badgeA count or a percentage written into a templateCustom CSS or an inline style
Depends on: I1958 I1959 I1946
Priority: p1
Profile: implementation
Parallel safe: true
Owner: unknown: the record declares no `owner`

The work so far

Branches: none
Merged: none
Commits: 0
Trunk: master
Sessions: none
Created: 2026-09-26
Updated: 2026-09-26
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.