Dependency graph integrity
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.
blockingA violation stops the command with exit 10.
The chain
A rule is enforced only when every link below holds. majordomus doctor resolves each one from the source on every run; this page shows what it resolved.
- 1 Declared majordomus.dag-integrity
- 2 Validator mj_validate_dag
- 3 Runs under doctor, watch
- 4 On violation exit 10
- 5 Proved by test/cases/44_model_doctrine.sh
- 6 Run by CI .github/workflows/validate.yml
Where it runs
- majordomus doctorIs Majordomus itself healthy, and is every enforcement it declares actually wired here?
- majordomus watchWhat has drifted since the last update — policy, projections, state, retention.
What it lets us promise
- guaranteedA cycle, a self-dependency and a dependency on an issue that does not exist are each refused by name
- guaranteedExecution waves are computed from the graph, and issues in one wave that touch the same paths are reported as serialised
Read it here
majordomus doctrine show majordomus.dag-integrity
majordomus check --rule majordomus.dag-integrity