Every use case is executed against the tool, not described

What a person does with the tool is one file with a scenario the tool runs against itself; the page shows that execution, and a public command no use case runs is a gap the tool reports.

status

stable

exposed through

• ✓cli
• ·api
• ✓mcp
• ·cockpit
• ✓docs

area

verification

documentation

What it does

majordomus usecase run executes every scenario; usecase coverage tallies every public command, guaranteed claim and MCP tool against the use cases that name and run it; usecase impact says what a change reaches; usecase scaffold --missing writes a draft for each gap from what the tool already knows. An application says when the tool fits and, because a catalogue that only lists fits is marketing, when it does not.

What it does not do

A draft never counts until it is made active, and a status written by hand is refused: the maturity of a use case is what its evidence supports.

The commands that run it

• majordomus usecase verify

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

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-case42
• application5
• taxonomy10

What it answers

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

The rules that hold it

• blockingA use case is proved by execution, and a capability is covered by a use caseproject.use-case-evidence
• blockingUse-case coveragemajordomus.use-case-coverage
• blockingCatalogue integritymajordomus.catalogue-integrity

What is guaranteed

• guaranteed 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
• guaranteed 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
• guaranteed 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
• guaranteed 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

Executable use cases

• extensionAdd a use case and let the tool prove it