majordomus evidence show

Every claim against the evidence recorded for it

Usage

majordomus evidence show [OPTIONS]

Arguments

argument	value	default	description
--state	<STATE>	—	Only claims in this proof state (proven, inputs_unchanged, stale, failing, not_run, unrunnable, no_test)
--status	<STATUS>	—	Only claims declaring this status (guaranteed, advisory, planned, rejected)
--findings	flag	—	Only the claims whose declared status the evidence does not support
--check	flag	—	Exit 10 when a claim declares a guarantee the evidence does not support
--presented	<REV>	—	Judge at the checked-out commit as committed (HEAD, or any name of it), from the ledger that commit holds, instead of at the working tree
--presented-tree	clean \| dirty \| unknown	—	What you know about the presented commit's tree (clean, dirty, unknown); it can only weaken the measured state `clean` — Nothing you know of: the measured state stands `dirty` — The build did not come from the commit as committed; nothing reads as proven `unknown` — You cannot say whether it did; nothing reads as proven
--repo	<PATH>	—	Start the search for the repository root here (default: the current directory) (accepted by every subcommand)
--discovery	vcs \| filesystem	vcs	How declarative files are enumerated (accepted by every subcommand) `vcs` — Tracked files, through the version-control index (the layer's contract); a layer none of which is tracked is read from the work tree `filesystem` — A walk of the work tree with the same glob semantics; untracked files included
--strict	flag	—	Refuse to proceed when any file of the layer carries an error diagnostic (accepted by every subcommand)
--share	<DIR>	—	The tool distribution's share directory (kinds.yaml, schemas/); default: $MAJORDOMUS_SHARE, then the repository's own share/, then the one beside the executable (accepted by every subcommand)
--format	text \| json	text	Output shape (accepted by every subcommand) `text` — Lines for a person `json` — One JSON document, deterministic

Examples

The whole join, as one document

The same answer `GET /api/v1/evidence` and the MCP tool `majordomus_evidence` return: every claim with its proof state, the sentence that explains how that state was derived, the execution behind it, the files that have changed since, and the command that produces the proof again. The tallies count the whole matrix even when the claims are filtered, so a narrowed answer never misreports how much of it was examined.
```
$ majordomus evidence show --format json
```
What it asserts: exits 0; prints one JSON document carrying /claims, /totals, /ledger/path, /findings.
Tested by apps/majordomus-cli/tests/cli_examples.rs, which runs the command against the built executable and asserts what the page states.
The checked-out commit, judged as committed

The reading a site built from this commit needs: every claim judged from the ledger the commit holds rather than the working tree's, against the commit's own tree, measured without the ledger's working copy. The first line names what was judged. A run the working ledger holds that the commit's does not can only withhold `proven`, and is named when there is one; a revision other than the checked-out commit is refused.
```
$ majordomus evidence show --presented HEAD
```
What it asserts: exits 0; prints judged at, as committed.
Tested by apps/majordomus-cli/tests/cli_examples.rs, which runs the command against the built executable and asserts what the page states.

Where this comes from

Declared once in apps/majordomus-cli/src/cli.rs: clap for the structure, typed Rust metadata beside it for the examples. This page, majordomus evidence show --help, docs/generated/cli.md and docs/generated/cli.json are projections of that one declaration.

The whole command line on one page: the registry's command-line page. The task lifecycle (init, start, finish, doctor, ...) belongs to the shell tool, a different program: Commands and its specification.