A use case is proved by execution, and a capability is covered by a use case

majordomus://rule/project.use-case-evidence@1active use-casesevidencedocumentation

it references

depends_on majordomus.catalogue-integrity@1
depends_on majordomus.use-case-coverage@1

referenced by

Nothing in the layer names it. Backlinks are derived, so an empty list is an answer rather than an omission.

Rationale

A catalogue of prose drifts on the first edit that forgets it; a demonstration nobody ran is fiction with a prompt sign. Anything derivable is derived, anything not derivable has one canonical home, and anything claimed as guaranteed is backed by executable evidence: the use case is where those three meet for the reader who asks "what does a person do with this, and does it work".

Required behaviour

Every public command is named and run by an active use case under .ai/repo/use-cases/; a guaranteed claim or an MCP tool without one is a reported gap. A page shows a command's output only from the evidence of the scenario the generator executed. status and target are authored; maturity is computed by the generator and appears nowhere in a file. After a change to lib/, bin/majordomus, share/commands.yaml, a rule, docs/CLAIMS.yaml, the crate or a use case, majordomus usecase impact is run and the scenarios and cases it names are run before finish.

Failure behaviour

majordomus.use-case-coverage fails doctor, check and finish on a required gap (the policy's use_cases.coverage); scripts/generate-site-data refuses a scenario that fails and --check refuses evidence that does not regenerate; scripts/site-check refuses a page whose evidence did not pass; a reviewer refuses a use case that carries a copied output or a written maturity.

Verification

test/cases/94_use_cases.sh (the chain, every reference mutated), test/cases/28_catalogue.sh, test/cases/10_site_data.sh and 11_site_derivation.sh (the generated data and its freshness), scripts/site-check, and majordomus doctor.

Where this comes from

canonical file: .ai/repo/rules/project/use-case-evidence.v1.md
identity: project.use-case-evidence@1
also served as: MCP resource majordomus://rule/project.use-case-evidence@1 · majordomus entity show rule/project-use-case-evidence-1 · GET /api/v1/entity?uri=majordomus://rule/project.use-case-evidence@1
in the Cockpit: /cockpit/objects/rule/project-use-case-evidence-1

This page is generated from the file above by scripts/generate-site-data; editing the page changes nothing, editing the file changes every surface. The relations above are edges of docs/generated/graph.json, which the executable writes from the same index.