Use-case coverage
Every public command, and every guaranteed claim and MCP tool the policy asks for, is named and run by at least one active use case whose scenario executes against the real tool; a gap is a failure or a report according to the policy, never silence.
blockingA violation stops the command with exit 10.
The chain
A rule is enforced only when every link below holds. majordomus doctor resolves each one from the source on every run; this page shows what it resolved.
- 1 Declared majordomus.use-case-coverage
- 2 Validator mj_validate_use_case_coverage
- 3 Runs under doctor, check, finish
- 4 On violation exit 10
- 5 Proved by test/cases/94_use_cases.sh
- 6 Run by CI .github/workflows/validate.yml
Where it runs
- majordomus doctorIs Majordomus itself healthy, and is every enforcement it declares actually wired here?
- majordomus checkIs the current task still consistent with its policy, its scope and this checkout?
- majordomus finishEvaluate the finish contract and refuse the outcome if any line of it is unmet.
A repository selects this line of the finish contract by naming use_cases_covered in verification.finish_requires. A requirement the policy names that no doctrine defines is reported and refuses.
What it lets us promise
Read it here
majordomus doctrine show majordomus.use-case-coverage
majordomus check --rule majordomus.use-case-coverage