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
I1963
Evidence is tested end to end
Where it stands
devtask.issue- Readiness
- blocked 3 of its dependencies are not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
6- Waiting on
- Holds back
- Behind it in all
1- Evidence
0of3
| In the way | Subject | Detail |
|---|---|---|
| issue | I1960 | I1960 is not DONE |
| issue | I1956 | I1956 is not DONE |
| issue | I1959 | I1959 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Prove across every surface that no surface is greener than the ledger, that the badge works in a browser, that tampered evidence is refused, and that coverage is shown with its commit.
- Why
- Each slice proves its own part. Only a case across surfaces can prove that they agree, which is what the anti-goal of a surface greener than the ledger requires.
- Now
- No case compares the verdict of one subject across the CLI, HTTP, MCP, the Cockpit and the site.
- Wanted
- Cases cover the cross-surface comparison with the monotone rule; the badge in a browser at phone width, by click, deep link and keyboard; the refusal of a tampered dataset, ledger row and artifact; and the coverage view with its commit.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- One subject reads the same verdict on every surface, and each difference names its record
- The badge reaches its evidence by click, by deep link and by keyboard at phone width
- A tampered dataset, ledger row or artifact is refused, never rendered
- Coverage is shown with its commit, and never as current for another commit
- Validation
bash test/run.sh 524_no_surface_is_greener_than_the_ledgerbash test/run.sh 525_an_evidence_badge_works_in_a_browserbash test/run.sh 526_tampered_evidence_is_refusedbash test/run.sh 527_coverage_is_shown_with_its_commit- Evidence required
no_surface_greener_than_the_ledgerbadge_works_in_a_browsertampering_refused- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
test/casestest/fixtures/evidence-end-to-enddocs/CLAIMS.yamldocs/claims.ai/repo/features/evidence.md- Not
A change to code: a defect the cases find is reported to the slice that owns itscripts/ui and interaction specs- Depends on
- 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.