State consistency

majordomus://rule/majordomus.state-consistency@1active stategit

it references

depends_on majordomus.sessions-are-workers@1

referenced by

governed_by several-agents-one-repository
exercises catch-an-agent-that-says-it-is-done
exercises checkpoint-long-work
exercises know-whether-this-work-is-finished
exercises resume-in-the-right-worktree
exercises run-several-workers-at-once

Rationale

The task record still describes this checkout — same branch, and HEAD at or ahead of the recorded commit.

Required behaviour

A task record is trusted only while it still describes this checkout: same branch, HEAD at or ahead of the recorded commit.

Failure behaviour

A violation is a FAIL finding under the category state, 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_state decides it, dispatched from check, finish, 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/state-consistency.v1.md
identity: majordomus.state-consistency@1
also served as: MCP resource majordomus://rule/majordomus.state-consistency@1 · majordomus entity show rule/majordomus-state-consistency-1 · GET /api/v1/entity?uri=majordomus://rule/majordomus.state-consistency@1
in the Cockpit: /cockpit/objects/rule/majordomus-state-consistency-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.