Catalogue integrity

Every use case and application describes the tool in terms the tool has — each command, doctrine and claim it names exists, and the two catalogues reference each other in both directions.

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.catalogue-integrity
2 Validator mj_validate_catalogue
3 Runs under doctor, watch
4 On violation exit 10
5 Proved by test/cases/28_catalogue.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

guaranteedA 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

Read it here

read one rule

majordomus doctrine show majordomus.catalogue-integrity
majordomus check --rule majordomus.catalogue-integrity