Rule package integrity
The repository's effective rule set is real: the vendored baseline matches its manifest file for file, every rule resolves with its dependencies and no two claim one identity, and no project rule reuses the vendored namespace.
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.rule-package-integrity
- 2 Validator mj_validate_rule_package
- 3 Runs under doctor, watch
- 4 On violation exit 10
- 5 Proved by test/cases/67_rule_dag.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 watchWhat has drifted since the last update — policy, projections, state, retention.
What it lets us promise
- guaranteedEvery rule the tool enforces is declared once, as a rule object in the repository's effective set, and doctor proves each one is reached by the command that claims to run it
- guaranteedThe rule baseline is vendored into the repository with a manifest naming every file and its hash, and a hand edit is detected and refused
- guaranteedThe effective rule set is resolved as a dependency graph in a deterministic order, and a set that does not resolve is applied by nothing
Read it here
majordomus doctrine show majordomus.rule-package-integrity
majordomus check --rule majordomus.rule-package-integrity