Bootstrap integrity
The path from a human reader to the AI layer is unbroken — README.md names AGENTS.md, every generated instruction file points at .ai/README.md, and none of them carries a rule of its own.
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.bootstrap-integrity
- 2 Validator mj_validate_bootstrap
- 3 Runs under doctor, watch
- 4 On violation exit 10
- 5 Proved by test/cases/03_update.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
- guaranteedProvider instruction files are generated from the one policy, deterministically
- guaranteedThe always-loaded instruction file has a line budget with a failing check
- guaranteedProvider instruction files are thin bootstraps that point at the AI layer and carry no rule of their own
Read it here
majordomus doctrine show majordomus.bootstrap-integrity
majordomus check --rule majordomus.bootstrap-integrity