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

I2477

A claim opens its proof: what settles it, its last run, what changed since, how to see it again

Where it stands

devtask.issue

Readiness: complete completion is recorded and every required evidence token is present
Status: DONE
Can start: not now
Milestone: development-runtime
Milestone status: ACTIVE
Wave: 2
Waiting on: none
Holds back: none
Behind it in all: 0
Evidence: 2 of 2

Moves

plan.transition

What it is

Objective: Let a reader of majordomus ui open any claim of the product (/ui/evidence?claim=<id>) into an inspector from evidence.claim: what it says and where, its state and what that means, the run behind it, what changed since it was proven, the command that reproduces it, the runs the ledger holds, and the claims its test also proves, each a link.
Why: The owner asked on 2026-10-11 to implement every view of the UI screenshots, maximally interactive (reference 09-evidence; pack v3 M10 evidence trail). The Evidence screen lists claims and findings as rows that open nothing, while evidence.claim already joins one claim to its execution, its changed files, its reproduce command and its sibling claims.
Now: A claim is a row of the Evidence screen; nothing opens it.
Wanted: ?claim=<id> asks evidence.claim for that claim and opens its inspector above the Evidence screen: its id, text, state and status, the meaning of its state, where it is said, what implements it and what settles it, its last run (outcome, seconds, commit, tree) or that it was never run, the files changed since it was proven, the reproduce command, the newest ten runs of its test, and the claims the same test proves, each a link to its own inspector. The Evidence screen's claim and finding rows lead here. A claim the matrix does not declare is shown as the capability's refusal; a value that is no claim id is never asked.
Done when: unknown: the record declares no `completion`
Risk: unknown: the record declares no `risk`

Acceptance

?claim=<id> opens the inspector with what settles it, its last run, its reproduce command and the claims its test also proves as links
the Evidence screen's claim and finding rows lead to it
an undeclared claim is said as the capability's refusal, and a value that is no id is never asked

Validation: cargo test --lib ui::claimtest/run.sh 1082_a_claim_opens_its_proof
Evidence required: ui_claim_unit_testsui_claim_case_1082
Evidence present: ui_claim_unit_testsui_claim_case_1082

Scope

Touches: apps/majordomus-cli/src/ui/claim.rsapps/majordomus-cli/src/ui/evidence.rsapps/majordomus-cli/src/ui/mod.rs.ai/repo/project/issues/I2477.yamldocs/MAJORDOMUS_UI.mdtest/cases/1082_a_claim_opens_its_proof.sh
Not: unknown: the record declares no `non_scope`
Depends on: I2462
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-10-11
Updated: 2026-10-12T11:01:25Z
Started: 2026-10-12T11:01:09Z
Verified: 2026-10-12T11:01:13Z
Completed: 2026-10-12T11:01:25Z

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.