Handover integrity
The resolver runs and reports either the record for this worktree and branch or its clean absence; a malformed record is never silently skipped, and a record describing a history this checkout no longer has is reported.
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.handover-integrity
- 2 Validator mj_validate_resolver
- 3 Runs under doctor, watch
- 4 On violation exit 10
- 5 Proved by test/cases/23_context.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
- guaranteedState read back is labelled exact, advanced, diverged or different_context against git
- guaranteedhandover writes an append-only record with computed front matter and required sections
Read it here
majordomus doctrine show majordomus.handover-integrity
majordomus check --rule majordomus.handover-integrity