Skip to content

Checkpoint freshness

Checkpoint freshness

majordomus://rule/majordomus.checkpoint-freshness@1active checkpointcontinuity

it references

referenced by

Rationale

A task whose last checkpoint is older than its profile's interval is reported, not stopped.

Required behaviour

A task whose newest checkpoint is older than its profile's interval is reported as stale, and the report does not stop the work.

Failure behaviour

A violation is a WARN finding under the category checkpoint; the command continues and exits as it otherwise would. Under watch it is reported as drift and the command exits 11.

Verification

mj_validate_checkpoint decides it, dispatched from check, watch. The behavioural case test/cases/04_start_check.sh proves it, and CI runs that case.

Where this comes from

canonical file
.ai/repo/rules/vendor/majordomus/rules/checkpoint-freshness.v1.md
identity
majordomus.checkpoint-freshness@1
also served as
MCP resource majordomus://rule/majordomus.checkpoint-freshness@1 · majordomus entity show rule/majordomus-checkpoint-freshness-1 · GET /api/v1/entity?uri=majordomus://rule/majordomus.checkpoint-freshness@1
in the Cockpit
/cockpit/objects/rule/majordomus-checkpoint-freshness-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.