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

I1953

Evidence answers by subject, on every surface

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
2
Waiting on
I1951
Holds back
I1955I1956I1962
Behind it in all
10
Evidence
0 of 2
In the waySubjectDetail
issueI1951I1951 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 I1953

majordomus plan verify I1953

majordomus plan done I1953

What it is

Objective
Add the evidence.subject, evidence.coverage, evidence.runs and evidence.run capabilities, so that the CLI, HTTP and MCP answer by subject from the one authority and read supplementary records only through the monotone rule (ADR 0087 decision 3).
Why
Only claims and rules can be asked about today. A feature, a command, a capability, an MCP tool and a use case have no answer, although each is what a reader of the site or the Cockpit is looking at.
Now
evidence show, evidence claim and evidence proves answer by claim; rules answers by rule; nothing answers for any other subject, and nothing lists run or coverage records.
Wanted
majordomus evidence subject <key>, evidence coverage, evidence runs and evidence run <id> exist as declared capabilities served over the CLI, HTTP and MCP tool calls; an unknown subject exits 13; supplementary records are listed beside the verdict and applied only through the monotone rule.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • Every subject kind of the index answers through evidence subject with the same verdict over the CLI, HTTP and MCP
  • An unknown subject is refused with exit 13
  • A supplementary record only ever weakens a verdict, and each weakening names its record
  • Coverage is shown as current only for its own commit with a clean tree
Validation
bash test/run.sh 508_evidence_answers_by_subjectbash test/run.sh 509_supplementary_records_only_weakenmajordomus generate --check
Evidence required
answers_by_subjectsupplementary_only_weakens
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/capability/builtin/evidence.rsapps/majordomus-cli/src/commands/evidence.rsapps/majordomus-cli/src/cli.rsapps/majordomus-cli/src/evidence/supplementary.rsapps/majordomus-cli/src/evidence/mod.rsapps/majordomus-cli/src/evidence/subject.rstest/casesdocs/EVIDENCE.mddocs/HOW_IT_WORKS.mddocs/README.mddocs/CLAIMS.yamldocs/claims.ai/repo/features/evidence.md
Not
MCP resource templates per subjectA version bump
Depends on
I1952I1951
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.