Completion is gated
A task reaches the outcome completed only when no validation gate its own change set selects is known to be failing, and a gate's verdict discharges nothing once the files that select it have changed since the run.
blocking A 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.completion-gates
- 2 Validator mj_validate_completion_gates
- 3 Runs under check, finish
- 4 On violation exit 10
- 5 Proved by test/cases/131_completion_gates.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 finishEvaluate the finish contract and refuse the outcome if any line of it is unmet.
A repository selects this line of the finish contract by naming gates_passed in verification.finish_requires. A requirement the policy names that no doctrine defines is reported and refuses.
Read it here
majordomus doctrine show majordomus.completion-gates
majordomus check --rule majordomus.completion-gates