Skip to content
Cockpit0.29.0
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

I1958

Evidence has one route per subject, and every panel is joined to its subject

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
test-evidence
Milestone status
ACTIVE
Wave
4
Waiting on
I1955
Holds back
I1960I1961
Behind it in all
5
Evidence
0 of 2
In the waySubjectDetail
issueI1955I1955 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I1958

majordomus plan verify I1958

majordomus plan done I1958

What it is

Objective
Generate one evidence route per subject from site/data/registry/evidence-subjects.json, as sections of the one evidence template, and join every homepage panel to its subject by its route, failing generation for a subject the index does not have (ADR 0087 decision 9).
Why
The site only joins to the index. Today no panel names a subject, and /evidence/ is one page.
Now
/evidence/ is a single page whose CI view is the Recorded by CI section of PR #577; panels carry a route and no subject; the tests of commands.json are derived in shell.
Wanted
/evidence/ is a section with a child per subject kind, plus suites, coverage and runs; the Recorded by CI section becomes the runs section; scripts/generate-site-data sets each panel's subject by joining its route to an index key and passes the executable's refusal through; the tests of commands.json are read from the artifact.
Done when
unknown: the record declares no `completion`
Risk
It also waits on PR #621 and PR #626, which change the templates it edits.

Acceptance

  • Every subject of the index has a route, and no route exists for a subject the index does not have
  • Every panel carries the subject its route joins to, or an explicit illustration marker, and an unknown subject fails generation with the executable's refusal
  • The Recorded by CI section is folded into the runs section
Validation
bash test/run.sh 516_evidence_routes_render_from_the_subject_indexbash test/run.sh 517_a_panel_subject_is_joined_from_its_route
Evidence required
routes_from_the_indexpanels_joined_to_subjects
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
scripts/generate-site-datascripts/lib/panel-subjects.jqsite/content-src/evidence.mdsite/content-src/evidencesite/templates/evidence.htmlsite/data/nav.tomltest/casesdocs/CLAIMS.yamldocs/claims.gitattributes
Not
Deriving a subject in shell or jq beyond the joinThe badge, which is I1960's
Depends on
I1952I1946I1955
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.