AI layer integrity
The repository's AI layer is real: the manifest declares a format this executable reads and every section it names exists, the checkout-local half is ignored by git and nothing under it is tracked, and no project data remains under the pre-.ai .majordomus/ path.
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.ai-layout-integrity
- 2 Validator mj_validate_ai_layout
- 3 Runs under doctor, watch
- 4 On violation exit 10
- 5 Proved by test/cases/01_init.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
- guaranteedInstalling into a repository that already has an installation is refused
- guaranteedThe repository's AI layer is one directory whose manifest names every section, readable without the tool
- guaranteedCheckout-local state lives under .ai/local/, is ignored by git, and is absent on a fresh clone or worktree
- guaranteedA repository on the pre-.ai layout is migrated once, explicitly, with a previewed plan and a verified backup of its local state, and the command is idempotent afterwards
- guaranteedThe tool runs read-only from any location, and two locations of one version agree about one repository
Read it here
majordomus doctrine show majordomus.ai-layout-integrity
majordomus check --rule majordomus.ai-layout-integrity