Lifecycle observation
A store that can be read is not a store that is being written. While episodes go on opening, the records a future worker resumes from must go on advancing, every lifecycle event received must leave evidence it arrived, and an episode that outlives the staleness threshold must be named rather than left open.
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.lifecycle-observed
- 2 Validator mj_validate_lifecycle
- 3 Runs under doctor, watch
- 4 On violation exit 10
- 5 Proved by test/cases/130_lifecycle_survives_a_stale_task.sh
- 6 Run by CI .github/workflows/validate.yml
Where it runs
- majordomus doctorIt checks governance only: is 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.lifecycle-observed
majordomus check --rule majordomus.lifecycle-observed