majordomus evidence
What actually ran and what it proves: every claim of the matrix against the runs recorded for it, one claim's proof, one test's claims, and the recording of a run that happened
majordomus evidence
Usage
majordomus evidence [OPTIONS] <COMMAND>This command groups the commands below and is not run on its own, so it carries no example.
Commands
- majordomus evidence show Every claim against the evidence recorded for it
- majordomus evidence claim One claim: its proof state, the execution behind it, and how to reproduce it
- majordomus evidence proves One test: its latest execution and every claim it proves
- majordomus evidence record Record a run that happened into the ledger
- majordomus evidence stamp Measure the checkout as a run left it, for `record --provenance`
Arguments
| argument | value | default | description |
|---|---|---|---|
| --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)
|
| --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)
|
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 --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.