A deployment is described once, and every provider artifact is generated from it
A deployment of the executable is a canonical object of the layer against a closed contract; the container definition and the provider configuration are projections of it, never a second description.
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.deployment-contract
- 2 Validator mj_validate_deployments
- 3 Runs under doctor, watch
- 4 On violation exit 10
- 5 Proved by test/cases/84_deployment_contract.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.
Read it here
majordomus doctrine show majordomus.deployment-contract
majordomus check --rule majordomus.deployment-contract