Knowledge observation
While episodes keep closing, the knowledge they produced must keep being derived. A closed episode no derivation followed, once it is older than the freshness threshold, is a stopped writer; a lifecycle whose close path never calls the deriver while the policy switch is on is a writer that was never started.
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.knowledge-observed
- 2 Validator mj_validate_knowledge_lifecycle
- 3 Runs under doctor, watch
- 4 On violation exit 10
- 5 Proved by test/cases/563_knowledge_is_derived_at_the_boundary.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
- guaranteed A provider's end event and its compaction event derive the knowledge the episode produced into candidate records under the tracked tree, from the ledger and git and never from a conversation, whether or not a task is active, and record that they did so in the ledger
- guaranteed A policy switch that is off derives nothing and says so; a derivation that fails inside a provider hook is recorded as provider.event.failed and the hook still exits 0
- guaranteed A repository in which episodes close and no knowledge derivation follows within the stale threshold is reported as a stopped writer by doctor and watch, and the finding clears when a derivation is written
Read it here
majordomus doctrine show majordomus.knowledge-observed
majordomus check --rule majordomus.knowledge-observed