A session does not finish behind its own published site
A repository that publishes has a second tree — the one the public is being served — and no commit-level gate can measure it, because no change to any file can make it right or wrong. A session that lands work and leaves the publication owed has finished nothing the public can see, and every check stays green while that is true. The gates that measure a deployment are declared as such in the CI model, and finish asks them.
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.publication-currency
- 2 Validator mj_validate_publication_currency
- 3 Runs under finish
- 4 On violation exit 10
- 5 Proved by test/cases/275_publication_is_current.sh
- 6 Run by CI .github/workflows/validate.yml
Where it runs
A repository selects this line of the finish contract by naming publication_current in verification.finish_requires. A requirement the policy names that no doctrine defines is reported and refuses.
Read it here
majordomus doctrine show majordomus.publication-currency
majordomus check --rule majordomus.publication-currency