A profile sets how often a worker should checkpoint, and a stale task is reported

declared status!declared status: advisory Projected into the worker's instructions. Whether a worker honours it is not observable from outside. Documentation, not enforcement.

recorded evidence○recorded evidence: not run Not judged: only a guaranteed claim is held to a recorded run. how evidence is recorded

The staleness report is guaranteed. Whether the worker checkpoints is not.

majordomus check --checkpoint
majordomus watch     # DRIFT staleness … when the interval has passed

Detail rendered from docs/claims/checkpoint-interval.md.

From the statement to the proof

1. 1 · the public statement

   A profile sets how often a worker should checkpoint, and a stale task is reported

   Made on Profiles.

2. 2 · the canonical claim

   checkpoint-interval!declared status: advisory in docs/CLAIMS.yaml

   Defined in read it on this site · share/skeleton/policy.yaml

3. 3 · the implementation

   lib/check.sh · majordomus check

4. 4 · the test and the scenarios

   Test: test/cases/04_start_check.sh

5. 5 · the recorded runs

   ○recorded evidence: not run how evidence is recorded

Verify it yourself

The test runs in a disposable temporary repository and asserts the behaviour, not a string in the source.

bash test/run.sh 04_start_check

Where this claim is used

Related claims same implementation

• ○declared status: guaranteed Every line of the append-only ledger is a well-formed event, and a malformed line is a failure rather than a skipped record
• !declared status: advisory A decision record without a task, a head and a reason is reported, and does not block
• ○declared status: guaranteed An entry in the questions store that does not parse blocks acceptance exactly as an unresolved question does
• ○declared status: guaranteed check reports whether state, scope, blockers and checkpoint age are consistent right now
• ○declared status: guaranteed A touched file outside the claimed scope is a failure, not a warning
• ○declared status: guaranteed Overlap between parallel workers is computed on claimed paths in both containment directions
• !declared status: advisory A profile declares which context a worker should load and no more
• ○declared status: guaranteed A task record names the checkout it belongs to, and another checkout is never held to its scope
• ○declared status: guaranteed A blocking question keeps blocking after the work is handed to a new task

The moments this answers

• → found a task "in progress" that nobody had touched for three weeks A status that was authored rather than computed is true at the moment of writing and decays silently from then on.
• → lost a failure a worker had already reproduced, because the session ended A failure observed inside a session is described in that session and nowhere else, so the next one starts from the report rather than the evidence.