Decision records
Every entry in decisions.md carries the task, the head and the reason, so a decision can be found by the worker who needs it.
advisoryA violation is reported and the command still succeeds.
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.decision-records
- 2 Validator mj_validate_decisions
- 3 Runs under check, doctor, watch
- 4 On violation reported; the command still exits 0
- 5 Proved by test/cases/21_decision_question.sh
- 6 Run by CI .github/workflows/validate.yml
Where it runs
- majordomus checkIs the current task still consistent with its policy, its scope and this checkout?
- 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
Read it here
majordomus doctrine show majordomus.decision-records
majordomus check --rule majordomus.decision-records