A prompt record carries its own identity, is bounded, and is private
Every captured prompt names the episode it belongs to or says why it cannot; the archive is readable by its owner alone, bounded by a declared retention policy, and never holds credential material verbatim.
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.prompt-continuity
- 2 Validator mj_validate_prompt_continuity
- 3 Runs under doctor, watch
- 4 On violation exit 10
- 5 Proved by test/cases/140_prompt_continuity.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.prompt-continuity
majordomus check --rule majordomus.prompt-continuity