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
I1962
The evidence gates read subject findings and widgets
Where it stands
devtask.issue- Readiness
- blocked 2 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
0of2
| In the way | Subject | Detail |
|---|---|---|
| issue | I1960 | I1960 is not DONE |
| issue | I1953 | I1953 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Make subject findings refusing, rewriting the evidence baseline in the same change, and make the evidence validator read every rendered widget, so that a widget without a subject or a count hard-coded into a template fails CI (ADR 0087 decision 10).
- Why
- Subject findings stay advisory until a gate reads them, and ADR 0087 names this validator as the mechanism against a widget without a subject and a hard-coded count.
- Now
- scripts/evidence-check ratchets claims only; subject findings are advisory; no gate reads the site's widgets for a subject; lib/commands.sh and scripts/ci/command-furnished derive command coverage in shell.
- Wanted
- evidence-check refuses a subject finding beyond the rewritten baseline; a stable feature without evidence and a widget without a subject each fail a gate by name; the shell command-coverage readers read the index artifact or are held equal to it by a case.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- Subject findings refuse, and the baseline is rewritten in the same change, with its reason
- A rendered widget without a subject fails the validator, naming the widget
- A count or a percentage hard-coded into a template fails the validator
- The shell command-coverage readers agree with the subject index
- Validation
bash test/run.sh 522_evidence_check_reads_widgetsbash test/run.sh 523_evidence_rules_are_gatedscripts/evidence-check- Evidence required
subject_findings_refusewidgets_name_subjects- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
scripts/evidence-check.ai/repo/evidence-baseline.txtscripts/rust-coveragelib/commands.shscripts/ci/command-furnishedscripts/lib/evidence-widgets.mjsscripts/lib/interactions.mjsscripts/site-check.ai/repo/automation/inventory.jsonl.ai/repo/ci/gates.yaml.ai/repo/rules/project/no-stable-feature-without-a-test.v1.md.ai/repo/rules/project/a-widget-names-its-evidence-subject.v1.md.ai/repo/features/evidence.md.ai/repo/features/coverage.mddocs/CLAIMS.yamldocs/claimstest/cases- Not
Weakening the baseline's ratchet- Depends on
- Priority
- p1
- 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-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.