The episode boundary is drawn below the model, and its working context is local
Where a provider fires session events, the episode is opened and closed by that provider's hook rather than by the model, the start event hands the worker the bounded briefing the policy declares, and the working context each open freezes stays under the ignored half of the layer, carries the declared keys, and never carries a conversation.
blockingA 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.session-lifecycle
- 2 Validator mj_validate_session_lifecycle
- 3 Runs under doctor, watch
- 4 On violation exit 10
- 5 Proved by test/cases/54_session_lifecycle_hooks.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.
What it lets us promise
Read it here
majordomus doctrine show majordomus.session-lifecycle
majordomus check --rule majordomus.session-lifecycle