Projection integrity

majordomus://rule/majordomus.projection-integrity@1active projection

it references

depends_on majordomus.sessions-are-workers@1

referenced by

governed_by repository-opened-in-ai-clients
governed_by repository-with-authored-governance
depends_on majordomus.context-budget@1
depends_on majordomus.deployment-contract@1
exercises adopt-an-existing-repository
exercises extend-what-the-executable-serves
exercises find-out-what-drifted
exercises keep-the-bootstrap-thin-and-within-budget
exercises say-what-the-tool-is-for
exercises see-what-the-repository-holds-without-reading-it
exercises serve-the-layer-to-ai-clients

Rationale

Every generated instruction file exists, matches the stamp it carries, and is never silently overwritten after a hand edit.

Required behaviour

Every generated instruction file exists, matches the content it declares, and is never silently overwritten after a hand edit.

Failure behaviour

A violation is a FAIL finding under the category projection, 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_projection decides it, dispatched from doctor, watch. The behavioural case test/cases/03_update.sh proves it, and CI runs that case.

Where this comes from

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