Projection integrity
Every generated instruction file exists, matches the stamp it carries, and is never silently overwritten after a hand edit.
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.projection-integrity
- 2 Validator mj_validate_projection
- 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
- guaranteedEvery generated instruction file carries its own stamp, and a hand edit is detected
- guaranteedA projection can own only the region between its markers, leaving the rest of the file untouched
- guaranteedA hand-edited instruction file is never silently overwritten
Read it here
majordomus doctrine show majordomus.projection-integrity
majordomus check --rule majordomus.projection-integrity