Retention caps
The ledger, the handovers, the checkpoints and the session records stay under the caps the policy sets, so durable state does not grow without bound.
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.retention-caps
- 2 Validator mj_validate_retention
- 3 Runs under doctor, watch
- 4 On violation exit 10
- 5 Proved by test/cases/02_doctor_basic.sh
- 6 Run by CI .github/workflows/validate.yml
Where it runs
- majordomus doctorIt checks governance only: is 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
Read it here
majordomus doctrine show majordomus.retention-caps
majordomus check --rule majordomus.retention-caps