Every object has a schema, and the rules resolve in one stated order
The order the rules apply in is written down rather than left in the code; every kind the tool reads declares a schema, every schema is named by a kind, and every path under the repository's AI layer is claimed by a source so that nothing is carried through unvalidated.
blocking A 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.schema-integrity
- 2 Validator mj_validate_schema_integrity
- 3 Runs under doctor, watch
- 4 On violation exit 10
- 5 Proved by test/cases/32_schema_integrity.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.
Read it here
majordomus doctrine show majordomus.schema-integrity
majordomus check --rule majordomus.schema-integrity