Dependency graph integrity

majordomus://rule/majordomus.dag-integrity@1active plandag

it references

depends_on majordomus.one-worker-one-scope@1

referenced by

exercises deliver-issues-in-waves
exercises plan-the-work-as-data

Rationale

The issue dependency graph is acyclic, every edge names an issue that exists, and no issue is executing ahead of a dependency that is not done.

Required behaviour

The issue dependency graph is acyclic, every edge names an issue that exists, and no issue executes ahead of a dependency that is not done.

Failure behaviour

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

Where this comes from

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