Prompt capture is proven, or reported unavailable
A repository that declares prompt capture has it wired below the model and proven by running it; the archive stays ignored and untracked, every prompt is present as both a record and a rendering, and neither carries anything the model said.
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.prompt-capture
- 2 Validator mj_validate_prompt_capture
- 3 Runs under doctor, watch
- 4 On violation exit 10
- 5 Proved by test/cases/29_prompt_capture.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.prompt-capture
majordomus check --rule majordomus.prompt-capture