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

I1956

The Cockpit shows evidence by subject

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
Milestone status
ACTIVE
Wave
3
Waiting on
Holds back
Behind it in all
2
Evidence
0 of 1
In the waySubjectDetail
issueI1953I1953 is not DONE
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 I1956

majordomus plan verify I1956

majordomus plan done I1956

What it is

Objective
Show every subject's verdict in the Cockpit, read through the subject index from the tracked ledger at the working tree, with a separate, advisory local-run column that can only weaken it (ADR 0087 decision 3).
Why
The Cockpit renders rule, feature, capability, command, skill and provider pages, and none of them says what verifies the thing it shows.
Now
The Cockpit has no evidence area, and its pages carry no Verified by section.
Wanted
A Cockpit evidence area, and a Verified by section on rule, feature, capability, command, skill and provider pages, each the answer of evidence subject for the page's subject; beside it, a local-run column that is advisory and applied through the monotone rule.
Done when
unknown: the record declares no `completion`
Risk
It edits Cockpit files that another session's pull request (#638) also edits, so it starts after that one lands.

Acceptance

  • The Cockpit's Verified by section is the evidence subject answer for the page's subject
  • A local run can only weaken what the Cockpit shows, and the Cockpit says which run did
Validation
bash test/run.sh 513_cockpit_shows_evidencecargo test --test cockpit_evidence
Evidence required
cockpit_reads_the_subject_answer
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/cockpit/nav.rsapps/majordomus-cli/src/cockpit/mod.rsapps/majordomus-cli/src/cockpit/pages.rsapps/majordomus-cli/tests/cockpit_evidence.rstest/casesdocs/COCKPIT.md.ai/repo/features/evidence.mddocs/CLAIMS.yamldocs/claims
Not
.ai/repo/features/cockpit.md, whose claims are I1947'sA verdict the subject answer does not give
Depends on
Priority
p2
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.