Skip to content

Retention caps

Retention caps

majordomus://rule/majordomus.retention-caps@1active retention

it references

referenced by

Rationale

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.

Required behaviour

The ledger, the handovers, the checkpoints and the session records stay under the caps the policy sets, and a cap is met by moving records aside, never by deleting one.

Failure behaviour

A violation is a FAIL finding under the category retention, and the command that found it exits 10. Under watch the same violation is reported as drift and the command exits 11.

Verification

mj_validate_retention decides it, dispatched from doctor, watch. The behavioural case test/cases/02_doctor_basic.sh proves it, and CI runs that case.

Where this comes from

canonical file
.ai/repo/rules/vendor/majordomus/rules/retention-caps.v1.md
identity
majordomus.retention-caps@1
also served as
MCP resource majordomus://rule/majordomus.retention-caps@1 · majordomus entity show rule/majordomus-retention-caps-1 · GET /api/v1/entity?uri=majordomus://rule/majordomus.retention-caps@1
in the Cockpit
/cockpit/objects/rule/majordomus-retention-caps-1

This page is generated from the file above by scripts/generate-site-data; editing the page changes nothing, editing the file changes every surface. The relations above are edges of docs/generated/graph.json, which the executable writes from the same index.

Searches the titles and descriptions of every page this site publishes.