Every use case is executed against the tool, not described

Why it exists

Operational moments from the Why catalogue that name one of this feature's mechanisms. Nothing here was assigned: a moment appears because it names a rule, a command, a capability or a claim this feature also names.

• →read a promise in the README that no test stood behind
• →pasted a command from the documentation and watched it fail
• →published a page that promised more than any test could support

How it works

The objects it is made of

Kinds of the layer. Each is a schema, a source class and a file on disk; the number beside it is what this repository holds today, counted at build time.

• use-case49
• application5
• taxonomy10

Where it sits

domain

Evidence — A claim names the test that settles it, a recorded run is judged against the commit it ran at, and a claim with no recorded run says so.

areas of work

verificationdocumentation

names

DoctrineWhy

named by

Why

Evidence

What is guaranteed

Each claim this feature names, with the status its row declares, the verdict the recorded runs support, and the test that settles it.

• ○declared status: guaranteed ○recorded evidence: not run Every public command is named and run by an active use case, a guaranteed claim or an MCP tool without one is a named gap, and the policy says which gaps fail doctor, check and finish test/cases/94_use_cases.sh
• ○declared status: guaranteed ○recorded evidence: not run A use case's scenario executes against the real tool in a disposable repository, every step's exit code and output are asserted, and the normalised evidence is what the site shows test/cases/94_use_cases.sh
• ○declared status: guaranteed ○recorded evidence: not run From the files a change touched, the tool names the commands, rules, use cases, scenarios and behavioural cases affected, and scaffolds a draft for a capability no use case covers test/cases/94_use_cases.sh
• ○declared status: guaranteed ○recorded evidence: not run A use case or application cannot name a command, doctrine or claim that does not exist, and the two catalogues cannot disagree about which applies to which test/cases/28_catalogue.sh

Executable use cases

• extensionAdd a use case and let the tool prove it

The rules that hold it

• ✕blocking A use case is proved by execution, and a capability is covered by a use caseproject.use-case-evidence
• ✕blocking Use-case coveragemajordomus.use-case-coverage
• ✕blocking Catalogue integritymajordomus.catalogue-integrity

The decisions behind it

• adr-0008Use cases are executable canonical objects of the layer accepted

Using it

The commands that run it

• majordomus usecase verify

  The executable use cases: list, show, validate, run against the real tool, coverage, impact, scaffold.

Where this page comes from

the file

.ai/repo/features/use-cases.md

the same answer

majordomus product show use-cases

read further

Executable use cases

The catalogue

Related features

• same domain

  Economics

  ✓feature status: stable

  What a coding session consumes with Majordomus and without it, from matched runs judged by the same hidden tests, with every number labelled by how it was obtained and published only past a declared rule.

  Explore Economics →

• named by this feature

  Doctrine

  ✓feature status: stable

  A rule is enforced when a validator decides it, a command runs it, a test proves it and CI blocks on it; anything less is documentation, and the tool knows the difference.

  Explore Doctrine →

• same domain

  Provenance

  ✓feature status: stable

  Who did what, under which task, at which commit, in which session is a ledger the tool writes and a person can read back, not a memory of a conversation.

  Explore Provenance →

• named by this feature · names this feature

  Why

  ✓feature status: stable

  Every operational moment the tool exists for is one file with the signals that identify it and the mechanisms that answer it, and a reader's own symptoms resolve to a diagnosis by counting, not by inference.

  Explore Why →

• same domain

  Evidence

  ✓feature status: stable

  Every claim is joined to the execution recorded for its test — the outcome, the commit, the tree, the digest and the command that produces it again — and a run against this commit is never reported as the same thing as a run whose inputs merely have not changed.

  Explore Evidence →

• same domain

  Benchmarks

  ✓feature status: stable

  Every externally callable operation is timed directly, over MCP and over HTTP, the denominator is generated from the registry, and a regression against the accepted baseline fails the check.

  Explore Benchmarks →