○guaranteed
Repository knowledgeintermediatemaintainerwrites state
An AI client indexes what it finds: build outputs, the local state directory, a vendored binary, a data dump. The context fills with noise and, sometimes, with a secret. Every tool has its own ignore list, and none of them is the repository’s own statement of what matters.
doctor: the scope policy exists and parses
knowledge sources, knowledge nodes --scope shared: what the index discovers once the policy is applied
- over MCP:
majordomus_scope reads the policy, majordomus_scope_classify answers for one path
setup: installed-wired
given:
- 'installed, and the two enforcements the policy declares are actually in place as hooks'
steps:
- id: declared
run: ['doctor']
note: 'the scope file is present and well-formed; init seeded it'
expect:
exit: 0
stdout_contains: ['^OK layout .ai/repo/scope.yaml', 'doctor: 0 failure']
- id: sources
run: ['knowledge', 'sources']
note: 'the source classes and the files each discovers, after the scope policy is applied'
expect:
exit: 0
stdout_contains: ['^policy +shared', '^scope +shared']
- id: nodes
run: ['knowledge', 'nodes', '--scope', 'shared']
note: 'the shared objects only: nothing under .ai/local/ is a node'
expect:
exit: 0
stdout_contains: ['shared']
stdout_not_contains: ['operational']
then:
- 'what is in and out of the context is one file in the layer, with a schema'
- 'build outputs, local state, binaries and secrets are out by declaration, not by luck'
- 'the MCP server classifies a path with the same data'
What belongs in the AI context is declared once in the layer, checked, and applied by the shell tool and the server alike. A client that honours it indexes the repository, not the machine.
The scenario
Executed against the real tool, in a repository prepared by installed-wired, every time this site is generated. What follows is not a description of what should happen; it is what happened.
given
- ·installed, and the two enforcements the policy declares are actually in place as hooks
when
- 1
majordomus doctor - 2
majordomus knowledge sources - 3
majordomus knowledge nodes --scope shared
then
- ·what is in and out of the context is one file in the layer, with a schema
- ·build outputs, local state, binaries and secrets are out by declaration, not by luck
- ·the MCP server classifies a path with the same data
What the tool did
Evidence of the run this page was generated from: pass, 3 step(s). Output is normalised: the repository's path, timestamps, ids and durations are placeholders; nothing else is edited.
Tested by test/cases/94_use_cases.sh, which runs every scenario and refuses a step whose recorded output is not what it produced.
-
the scope file is present and well-formed; init seeded it
OK knowledge graph — buildable here: 100 node(s), 58 edge(s), compiled into a temporary file and removed; no stored index to go stale
OK knowledge records — 0 record(s) valid against knowledge/v1; every reference resolves [reproduce: majordomus knowledge check]
OK knowledge candidates — 0 await review, cap 40
OK layout .ai/manifest.yaml — schema ai-repository/v1
OK layout .ai/repo/scope.yaml — version 1; 14 in pathspec(s); every key is one the schema declares
OK layout .ai/local/ — ignored, and nothing under it is tracked
OK layout .ai/ — every section the manifest names exists; the layer is readable without the tool
OK layout .ai/repo/prompts — present
OK layout .ai/local/state/handovers — present, 0 record(s)
OK layout .ai/local/state/checkpoints — present, 0 record(s)
OK records ledger.jsonl — every line is a well-formed event
OK policy 39 key(s) — every policy value the code reads is declared, with no reader-side default
OK bootstrap 3 projection(s) — each points at .ai/README.md, carries no rule of its own and names only rules in force
OK catalogue 0 use case(s), 0 application(s) — every command, doctrine, claim, responsibility, category, setup and cross-reference resolves, both directions
OK context .ai/ — 20 context document(s) carry the contract; ids unique, references resolve, no final document superseded, no cycle [reproduce: majordomus context validate]
OK policy .ai/repo/policy.yaml — parsed, version 1
OK profiles 4 files — parsed; default 'implementation' exists
INFO adr .ai/repo/adrs/ — no decisions; nothing to validate
OK records decisions.md — every entry is attributable
INFO project .ai/repo/project — no canonical project model here; nothing to validate
OK command surface — 30 public command(s), reconciled against the dispatch table [reproduce: majordomus doctor]
OK doctrine 50 of 61 rule(s) carry a validator — validator, dispatch, propagation, test and CI resolve for every one of the 50; the remaining 11 declare no validator and this check does not examine them
OK wiring doctor-on-commit — wired via .githooks/pre-commit
OK wiring finish-on-push — wired via .githooks/pre-push
OK command coverage — every public command is exercised and refuted [reproduce: bash test/run.sh 31_command_coverage]
OK resolver handovers — no record for this worktree and branch (absence, not a stale match) [reproduce: majordomus handover --resolve]
OK lifecycle activity — 0 episode(s) opened here; too few to judge whether the writers stopped
OK knowledge wiring — the close path and the compaction adapter call the deriver
OK knowledge deriver — no episode has closed here; nothing to judge
INFO project .ai/repo/project — no canonical project model here; nothing to validate
OK projection AGENTS.md — content matches its stamp
OK projection CLAUDE.md — content matches its stamp
OK projection GEMINI.md — content matches its stamp
OK budget AGENTS.md — 42 lines, budget 150
OK links AGENTS.md — all references resolve
OK counts AGENTS.md — no hardcoded counts
OK context builder — 21 lines, budget 300 [reproduce: majordomus context]
OK capture share/schemas/majordomus/capture/capture.v1 — 2 file(s) describe majordomus.capture/v1 at the path the identifier derives: the record as JSON Schema, the document as protobuf
OK capture .ai/local/prompts — ignored and untracked
OK capture .ai/local/prompts — no records yet; the archive is empty
OK capture .ai/local/prompts — every prompt is present as all three: the record, the Markdown and the YAML
OK prompts .ai/local/prompts — the archive and every record in it are readable by their owner only
OK prompts .ai/local/prompts — no records yet; the archive is empty
OK prompt 4 asset(s) — front matter valid, every token known
OK records open-questions.md — every entry parses
OK retention ledger — 1 lines, cap 5000
OK retention handovers — 0 files, cap 200
OK retention checkpoints — 0 files, cap 500
OK retention sessions — 0 records, cap 500
INFO project .ai/repo/project — no canonical project model here; nothing to validate
OK rules .ai/repo/rules/vendor/majordomus — every file matches the manifest (1 (1.0.0-alpha.8))
OK rules 61 rule(s) — resolve in one deterministic order; vendored baseline plus project rules, no override — 51 carry a validator, 10 are normative text this tool does not check
OK rules blocking — all 44 blocking rule(s) carry a validator
OK schema rules — 61 rule(s) resolve in one order: the vendored baseline in manifest order, then the project's, as a dependency graph
OK schema share/kinds.yaml — 37 kind(s); every one that carries metadata declares a schema
OK schema share/schemas — 54 schema(s), each valid JSON and each applied — by a kind, through an allow-list the tool reads, by a validator that names it, or as a generated document's contract (15)
OK records 0 record(s) — every changed_files names work, not generated or local state
OK session .ai/local/session-contexts — ignored and untracked
OK session .ai/local/session-contexts — no working contexts yet; the store is empty
INFO skill .ai/repo/skills/ — no skills; nothing to validate
OK skill reachable — no personal command or skill shares a name with a projected skill [reproduce: majordomus run editors.status]
INFO use-case 30 advisory gap(s) — not covered by an active use case, and the policy does not require it: command:init command:update command:doctor command:watch command:start command:context command:checkpoint command:handover command:check command:finish command:history command:decision command:question command:prompt command:evidence command:skills command:capture command:search command:doctrine command:plan command:version command:session command:knowledge command:adr command:usecase command:rules command:migrate command:recover command:bench command:archive [reproduce: majordomus usecase coverage]
OK use-case 0 of 30 target(s) covered — every public command the policy requires is named and run by an active use case (policy use_cases.coverage)
INFO env - — bash <version>, git <version>, jq <version>, shellcheck present
WARN clone unpushed — commits on no remote: main(2) — work on one disk is invisible to every other session and cannot be integrated [reproduce: git push -u origin <branch>]
OK clone uncommitted — no linked worktree, so no uncommitted work can sit in one
INFO clone trunk — no remote-tracking branch, so this checkout's distance from the remote trunk cannot be measured
INFO clone release — no remote-tracking branch, so whether the trunk's landed work is released cannot be measured
· reasoning <decided by the advisors and the executable of the recording machine>
· layout - — <judged when the recording machine has built the executable>
· budget doctor — <timed against the policy budget>
doctor: 0 failure(s)
- exit 0
- stdout_contains /^OK layout .ai/repo/scope.yaml/
- stdout_contains /doctor: 0 failure/
-
the source classes and the files each discovers, after the scope policy is applied
context shared context 77afef342ab6 .ai/README.md
context shared context 1aa0cfc9a98b .ai/repo/README.md
context shared context 210fe3243d2c .ai/repo/adrs/README.md
context shared context 6dc507447b9f .ai/repo/applications/README.md
context shared context 06b0af6581a4 .ai/repo/deployments/README.md
context shared context 18111b83801f .ai/repo/features/README.md
context shared context c1ae02e4d03c .ai/repo/knowledge/README.md
context shared context 9939471c0d0a .ai/repo/knowledge/candidates/README.md
context shared context 3be0a8483464 .ai/repo/knowledge/curated/README.md
context shared context 53695b36fc07 .ai/repo/mesh/README.md
context shared context cb11ba2b8aeb .ai/repo/profiles/README.md
context shared context b09939447728 .ai/repo/project/README.md
context shared context aaade142a03c .ai/repo/prompts/README.md
context shared context fa27e74a38c5 .ai/repo/rules/README.md
context shared context 39f8246be04e .ai/repo/rules/project/README.md
context shared context 07e9f6f77e38 .ai/repo/sessions/README.md
context shared context c08c8f28ce3d .ai/repo/skills/README.md
context shared context 99905d2cd5a9 .ai/repo/use-cases/README.md
context shared context 95d10752d6ae .ai/repo/why/README.md
context shared context 124141e223e4 .ai/repo/workflows/README.md
policy shared policy 663ed6512fa1 .ai/repo/policy.yaml
scope shared scope 264ce22ddc67 .ai/repo/scope.yaml
profile shared profile 2bbbd4d3b45b .ai/repo/profiles/debugging.yaml
profile shared profile 4e0b1ed0bb8c .ai/repo/profiles/deep-work.yaml
profile shared profile 4e4fe1af1c3d .ai/repo/profiles/implementation.yaml
profile shared profile c3f4f310c328 .ai/repo/profiles/routine.yaml
rule shared rule fa27e74a38c5 .ai/repo/rules/README.md
rule shared rule 39f8246be04e .ai/repo/rules/project/README.md
rule shared rule 8513b44dfe15 .ai/repo/rules/vendor/majordomus/rules/adr-integrity.v1.md
rule shared rule 1c35b4925c67 .ai/repo/rules/vendor/majordomus/rules/ai-layout-integrity.v1.md
rule shared rule 6b737b2767d6 .ai/repo/rules/vendor/majordomus/rules/blocker-resolution.v1.md
rule shared rule d6a33fc1b28c .ai/repo/rules/vendor/majordomus/rules/bootstrap-integrity.v1.md
rule shared rule f8137aa6fcd4 .ai/repo/rules/vendor/majordomus/rules/candidates-reviewed.v1.md
rule shared rule 826525b6e3a9 .ai/repo/rules/vendor/majordomus/rules/catalogue-integrity.v1.md
rule shared rule a56642f78cc5 .ai/repo/rules/vendor/majordomus/rules/checkpoint-freshness.v1.md
rule shared rule 78f8269d371d .ai/repo/rules/vendor/majordomus/rules/command-coverage.v1.md
rule shared rule e468040ac890 .ai/repo/rules/vendor/majordomus/rules/command-surface.v1.md
rule shared rule adf88f652092 .ai/repo/rules/vendor/majordomus/rules/completion-gates.v1.md
rule shared rule 523fbb99c024 .ai/repo/rules/vendor/majordomus/rules/context-budget.v1.md
rule shared rule 018f8d63e837 .ai/repo/rules/vendor/majordomus/rules/context-integrity.v1.md
rule shared rule f5336d1b0b06 .ai/repo/rules/vendor/majordomus/rules/dag-integrity.v1.md
rule shared rule d804fedbbf1a .ai/repo/rules/vendor/majordomus/rules/decision-records.v1.md
rule shared rule 072a8155ad66 .ai/repo/rules/vendor/majordomus/rules/decision-threshold.v1.md
rule shared rule 78db07930224 .ai/repo/rules/vendor/majordomus/rules/deployment-contract.v2.md
rule shared rule 2033490a50b9 .ai/repo/rules/vendor/majordomus/rules/doctrine-wiring-integrity.v1.md
rule shared rule afc294593532 .ai/repo/rules/vendor/majordomus/rules/enforcement-wiring.v1.md
rule shared rule db680840291e .ai/repo/rules/vendor/majordomus/rules/handover-integrity.v1.md
rule shared rule 3427bfc92e29 .ai/repo/rules/vendor/majordomus/rules/knowledge-graph.v1.md
rule shared rule eec2b2184f6c .ai/repo/rules/vendor/majordomus/rules/knowledge-integrity.v1.md
rule shared rule 33fc8bac42c8 .ai/repo/rules/vendor/majordomus/rules/knowledge-observed.v1.md
rule shared rule ebe4eb49d09c .ai/repo/rules/vendor/majordomus/rules/layout-integrity.v1.md
rule shared rule d3c88435f42d .ai/repo/rules/vendor/majordomus/rules/ledger-integrity.v1.md
rule shared rule 628f11b96703 .ai/repo/rules/vendor/majordomus/rules/lifecycle-observed.v1.md
rule shared rule d1bb01668123 .ai/repo/rules/vendor/majordomus/rules/note-integrity.v1.md
rule shared rule 88f7f9322b00 .ai/repo/rules/vendor/majordomus/rules/obligation-closure.v1.md
rule shared rule 51e122071249 .ai/repo/rules/vendor/majordomus/rules/policy-completeness.v1.md
rule shared rule ae11a7b983a5 .ai/repo/rules/vendor/majordomus/rules/policy-integrity.v1.md
rule shared rule 84f5b9f70992 .ai/repo/rules/vendor/majordomus/rules/principle-01-sessions-are-workers.v1.md
rule shared rule cbd041431c84 .ai/repo/rules/vendor/majordomus/rules/principle-02-minimum-sufficient-context.v1.md
rule shared rule c02aa47f226c .ai/repo/rules/vendor/majordomus/rules/principle-03-externalise-decisions.v1.md
rule shared rule fb8aff3c3984 .ai/repo/rules/vendor/majordomus/rules/principle-04-one-worker-one-scope.v1.md
rule shared rule 7fa1a1c5c27e .ai/repo/rules/vendor/majordomus/rules/principle-05-justified-escalation.v1.md
rule shared rule 87de78333726 .ai/repo/rules/vendor/majordomus/rules/principle-06-depth-is-not-verbosity.v1.md
rule shared rule a843319fda37 .ai/repo/rules/vendor/majordomus/rules/principle-07-define-done-first.v1.md
rule shared rule 1b01d93b42fa .ai/repo/rules/vendor/majordomus/rules/principle-08-verify-outcomes.v1.md
rule shared rule 5eae52cc5589 .ai/repo/rules/vendor/majordomus/rules/principle-09-isolated-parallelism.v1.md
rule shared rule c7307cc9d919 .ai/repo/rules/vendor/majordomus/rules/principle-10-handovers-carry-state.v1.md
rule shared rule abbd45d5b53e .ai/repo/rules/vendor/majordomus/rules/profile-requirements.v1.md
rule shared rule f2fd82b09aaa .ai/repo/rules/vendor/majordomus/rules/project-integrity.v1.md
rule shared rule bc3eadf4f9f5 .ai/repo/rules/vendor/majordomus/rules/projection-integrity.v1.md
rule shared rule 6a768205d5ed .ai/repo/rules/vendor/majordomus/rules/prompt-capture.v1.md
rule shared rule 5d4230b7c618 .ai/repo/rules/vendor/majordomus/rules/prompt-continuity.v1.md
rule shared rule c820246fbdc1 .ai/repo/rules/vendor/majordomus/rules/prompt-integrity.v1.md
rule shared rule 9b68dbd49ac6 .ai/repo/rules/vendor/majordomus/rules/publication-currency.v1.md
rule shared rule 58fca43f73a9 .ai/repo/rules/vendor/majordomus/rules/questions-store-integrity.v1.md
rule shared rule 4043b457e438 .ai/repo/rules/vendor/majordomus/rules/record-changed-files.v1.md
rule shared rule 6ac34a128a32 .ai/repo/rules/vendor/majordomus/rules/retention-caps.v1.md
rule shared rule 959aad5152d0 .ai/repo/rules/vendor/majordomus/rules/roadmap-integrity.v1.md
rule shared rule e254bad15ecd .ai/repo/rules/vendor/majordomus/rules/rule-package-integrity.v1.md
rule shared rule d73fb1b2f702 .ai/repo/rules/vendor/majordomus/rules/schema-integrity.v1.md
rule shared rule 5bae41c80fda .ai/repo/rules/vendor/majordomus/rules/scope-integrity.v1.md
rule shared rule 2e5b9f5ad9c7 .ai/repo/rules/vendor/majordomus/rules/session-lifecycle.v1.md
rule shared rule 8f779c44c5c2 .ai/repo/rules/vendor/majordomus/rules/session-records.v1.md
rule shared rule 5beb962c3c18 .ai/repo/rules/vendor/majordomus/rules/skill-integrity.v1.md
rule shared rule 70a6e878886b .ai/repo/rules/vendor/majordomus/rules/state-consistency.v1.md
rule shared rule 7e381d15f9f3 .ai/repo/rules/vendor/majordomus/rules/task-continuity.v1.md
rule shared rule 2a25cd588cea .ai/repo/rules/vendor/majordomus/rules/task-on-the-mesh.v1.md
rule shared rule 1955176df430 .ai/repo/rules/vendor/majordomus/rules/use-case-coverage.v1.md
rule shared rule 1a2e830a8912 .ai/repo/rules/vendor/majordomus/rules/verification-integrity.v1.md
prompt shared prompt aaade142a03c .ai/repo/prompts/README.md
prompt shared prompt cd5ec861eb54 .ai/repo/prompts/continue.md
prompt shared prompt 8a5e3920d4a3 .ai/repo/prompts/debug.md
prompt shared prompt 17dba8771fc4 .ai/repo/prompts/handover.md
prompt shared prompt 16d69f71530d .ai/repo/prompts/review.md
workflow shared document 124141e223e4 .ai/repo/workflows/README.md
workflow shared document a43c0936e7e3 .ai/repo/workflows/continuity.md
workflow shared document 726b52e6993e .ai/repo/workflows/plan.md
workflow shared document 39db3723e051 .ai/repo/workflows/task-lifecycle.md
workflow shared document 09ea91004f94 .ai/repo/workflows/use-cases.md
session shared session 07e9f6f77e38 .ai/repo/sessions/README.md
curated shared knowledge 3be0a8483464 .ai/repo/knowledge/curated/README.md
candidates shared knowledge 9939471c0d0a .ai/repo/knowledge/candidates/README.md
use_case shared use-case 99905d2cd5a9 .ai/repo/use-cases/README.md
taxonomy shared taxonomy 207a79579af9 .ai/repo/use-cases/taxonomy.yaml
feature shared feature 18111b83801f .ai/repo/features/README.md
application shared application 6dc507447b9f .ai/repo/applications/README.md
mesh-declaration shared mesh-declaration 00e82f259df7 .ai/repo/mesh/mesh.yaml
readme shared document 776e4d79cd72 AGENTS.md
readme shared document 0c98332bdeb6 CLAUDE.md
readme shared document 4cd27b17330c GEMINI.md
decisions operational decision 0885fc07773e .ai/local/state/decisions.md
questions operational question ebeb154be99d .ai/local/state/open-questions.md
knowledge sources: 112 file(s) in scope all
- exit 0
- stdout_contains /^policy +shared/
- stdout_contains /^scope +shared/
-
the shared objects only: nothing under .ai/local/ is a node
context shared 77afef342ab6 context:.ai/README.md Repository AI context
context shared 1aa0cfc9a98b context:.ai/repo/README.md Tracked repository context
context shared 210fe3243d2c context:.ai/repo/adrs/README.md Architecture decisions
context shared 6dc507447b9f context:.ai/repo/applications/README.md Applications
context shared 06b0af6581a4 context:.ai/repo/deployments/README.md Deployments
context shared 18111b83801f context:.ai/repo/features/README.md Product features
context shared c1ae02e4d03c context:.ai/repo/knowledge/README.md Knowledge
context shared 9939471c0d0a context:.ai/repo/knowledge/candidates/README.md Candidate records
context shared 3be0a8483464 context:.ai/repo/knowledge/curated/README.md Curated notes
context shared 53695b36fc07 context:.ai/repo/mesh/README.md Mesh
context shared cb11ba2b8aeb context:.ai/repo/profiles/README.md Profiles
context shared b09939447728 context:.ai/repo/project/README.md Project model
context shared aaade142a03c context:.ai/repo/prompts/README.md Prompt assets
context shared fa27e74a38c5 context:.ai/repo/rules/README.md Repository rules
context shared 39f8246be04e context:.ai/repo/rules/project/README.md Project rules
context shared 07e9f6f77e38 context:.ai/repo/sessions/README.md Session records
context shared c08c8f28ce3d context:.ai/repo/skills/README.md Skills
context shared 99905d2cd5a9 context:.ai/repo/use-cases/README.md Use cases
context shared 95d10752d6ae context:.ai/repo/why/README.md Why this exists
context shared 124141e223e4 context:.ai/repo/workflows/README.md Workflows
document shared a43c0936e7e3 document:.ai/repo/workflows/continuity.md Continuity
document shared 726b52e6993e document:.ai/repo/workflows/plan.md Taking work from the plan
document shared 39db3723e051 document:.ai/repo/workflows/task-lifecycle.md The task lifecycle
document shared 09ea91004f94 document:.ai/repo/workflows/use-cases.md Use cases
document shared 776e4d79cd72 document:AGENTS.md AGENTS.md
document shared 0c98332bdeb6 document:CLAUDE.md CLAUDE.md
document shared 4cd27b17330c document:GEMINI.md GEMINI.md
mesh-declaration shared 00e82f259df7 mesh-declaration:mesh
policy shared 663ed6512fa1 policy:.ai/repo/policy.yaml
profile shared 2bbbd4d3b45b profile:debugging reproduce, isolate, fix, and prove a defect fixed
profile shared 4e0b1ed0bb8c profile:deep-work design, architecture, cross-cutting change, or a problem with no known shape
profile shared 4e4fe1af1c3d profile:implementation build a described feature or change within a known design
profile shared c3f4f310c328 profile:routine small, well-understood changes; rename, bump, wording, one-line fixes
prompt shared cd5ec861eb54 prompt:continue resume a task from durable state instead of from someone's memory
prompt shared 8a5e3920d4a3 prompt:debug frame a defect so that the fix is proven, not asserted
prompt shared 17dba8771fc4 prompt:handover produce a continuation record body for the current task
prompt shared 16d69f71530d prompt:review review the working diff against the claimed scope and the finish contract
rule shared 8513b44dfe15 rule:majordomus.adr-integrity Architecture decision integrity
rule shared 1c35b4925c67 rule:majordomus.ai-layout-integrity AI layer integrity
rule shared 6b737b2767d6 rule:majordomus.blocker-resolution Blocker resolution
rule shared d6a33fc1b28c rule:majordomus.bootstrap-integrity Bootstrap integrity
rule shared f8137aa6fcd4 rule:majordomus.candidates-reviewed Candidates are reviewed
rule shared 826525b6e3a9 rule:majordomus.catalogue-integrity Catalogue integrity
rule shared a56642f78cc5 rule:majordomus.checkpoint-freshness Checkpoint freshness
rule shared 78f8269d371d rule:majordomus.command-coverage Every public command is exercised and refuted
rule shared e468040ac890 rule:majordomus.command-surface The command surface is declared and reconciled
rule shared adf88f652092 rule:majordomus.completion-gates Completion is gated
rule shared 523fbb99c024 rule:majordomus.context-budget Context budget
rule shared 018f8d63e837 rule:majordomus.context-integrity Context integrity
rule shared f5336d1b0b06 rule:majordomus.dag-integrity Dependency graph integrity
rule shared d804fedbbf1a rule:majordomus.decision-records Decision records
rule shared 072a8155ad66 rule:majordomus.decision-threshold The decision threshold
rule shared a843319fda37 rule:majordomus.define-done-first Define done before executing
rule shared 78db07930224 rule:majordomus.deployment-contract A deployment is described once, and every artifact built from it is generated from it
rule shared 87de78333726 rule:majordomus.depth-is-not-verbosity Execution depth is not output verbosity
rule shared 2033490a50b9 rule:majordomus.doctrine-wiring-integrity Doctrine wiring integrity
rule shared afc294593532 rule:majordomus.enforcement-wiring Enforcement wiring
rule shared c02aa47f226c rule:majordomus.externalise-decisions Externalise decisions and durable state
rule shared db680840291e rule:majordomus.handover-integrity Handover integrity
rule shared c7307cc9d919 rule:majordomus.handovers-carry-state Handovers transfer state, not transcripts
rule shared 5eae52cc5589 rule:majordomus.isolated-parallelism Parallel work requires isolation
rule shared 7fa1a1c5c27e rule:majordomus.justified-escalation Escalate capability and effort only when justified
rule shared 3427bfc92e29 rule:majordomus.knowledge-graph Knowledge graph integrity
rule shared eec2b2184f6c rule:majordomus.knowledge-integrity Knowledge integrity
rule shared 33fc8bac42c8 rule:majordomus.knowledge-observed Knowledge observation
rule shared ebe4eb49d09c rule:majordomus.layout-integrity Layout integrity
rule shared d3c88435f42d rule:majordomus.ledger-integrity Ledger integrity
rule shared 628f11b96703 rule:majordomus.lifecycle-observed Lifecycle observation
rule shared cbd041431c84 rule:majordomus.minimum-sufficient-context Load minimum sufficient context
rule shared d1bb01668123 rule:majordomus.note-integrity Note integrity
rule shared 88f7f9322b00 rule:majordomus.obligation-closure Obligation closure
rule shared fb8aff3c3984 rule:majordomus.one-worker-one-scope One worker, one clear scope
rule shared 51e122071249 rule:majordomus.policy-completeness Policy completeness
rule shared ae11a7b983a5 rule:majordomus.policy-integrity Policy integrity
rule shared abbd45d5b53e rule:majordomus.profile-requirements Profile requirements
rule shared f2fd82b09aaa rule:majordomus.project-integrity Project model integrity
rule shared bc3eadf4f9f5 rule:majordomus.projection-integrity Projection integrity
rule shared 6a768205d5ed rule:majordomus.prompt-capture Prompt capture is proven, or reported unavailable
rule shared 5d4230b7c618 rule:majordomus.prompt-continuity A prompt record carries its own identity, is bounded, and is private
rule shared c820246fbdc1 rule:majordomus.prompt-integrity Prompt integrity
rule shared 9b68dbd49ac6 rule:majordomus.publication-currency A session does not finish behind its own published site
rule shared 58fca43f73a9 rule:majordomus.questions-store-integrity Questions store integrity
rule shared 4043b457e438 rule:majordomus.record-changed-files A record's changed_files names the work, not the tool's exhaust
rule shared 6ac34a128a32 rule:majordomus.retention-caps Retention caps
rule shared 959aad5152d0 rule:majordomus.roadmap-integrity The roadmap is a projection, never a document
rule shared e254bad15ecd rule:majordomus.rule-package-integrity Rule package integrity
rule shared d73fb1b2f702 rule:majordomus.schema-integrity Every object has a schema, and the rules resolve in one stated order
rule shared 5bae41c80fda rule:majordomus.scope-integrity Scope integrity
rule shared 2e5b9f5ad9c7 rule:majordomus.session-lifecycle The episode boundary is drawn below the model, and its working context is local
rule shared 8f779c44c5c2 rule:majordomus.session-records Session records are shared objects with a closed field set
rule shared 84f5b9f70992 rule:majordomus.sessions-are-workers Sessions are workers, not memory
rule shared 5beb962c3c18 rule:majordomus.skill-integrity Skill integrity
rule shared 70a6e878886b rule:majordomus.state-consistency State consistency
rule shared 7e381d15f9f3 rule:majordomus.task-continuity Task continuity
rule shared 2a25cd588cea rule:majordomus.task-on-the-mesh A task on a repository whose mesh is enabled works on the mesh
rule shared 1955176df430 rule:majordomus.use-case-coverage Use-case coverage
rule shared 1a2e830a8912 rule:majordomus.verification-integrity Verification integrity
rule shared 1b01d93b42fa rule:majordomus.verify-outcomes Verify outcomes, not activity
scope shared 264ce22ddc67 scope:.ai/repo/scope.yaml
taxonomy shared 207a79579af9 taxonomy:.ai/repo/use-cases/taxonomy.yaml
knowledge nodes: 100 in scope shared
INFO knowledge . — the schema check was not asked for (MAJORDOMUS_KNOWLEDGE_SCH
- exit 0
- stdout_contains /shared/
- stdout_not_contains /operational/
Why the tool knows this
The chain from this page to the code: the use case names commands, rules and claims; each rule is dispatched from the registry and each claim names the test that proves it; the scenario above executed the commands. Nothing in this chain is prose about intent.
Over MCP the same layer is reached through majordomus_scope, majordomus_scope_classify (the MCP surface).
The rules that make it hold
Guarantees exercised
Related use cases
Computed from what they share: claims, rules, commands, category, applications. Nobody maintains this list.
- Trace a change to the context documents it affectsList the scoped context documents, resolve which apply to a path and why, and find out which documents a change set touches before it lands.
- Extend what the executable serves by adding a file, never by rebuilding itAdd a rule, a prompt or a knowledge node to .ai/ and have it appear as an MCP resource, an HTTP route and a reference entry, with the same binary.
- Move a repository from the pre-.ai layout to the layerSee what a migration would move, move it with a backup, and prove the result is a layer the tool reads.
- Say what your work is for, once, and have every surface say itRecord an operational failure mode as one file and have the command line, the API, MCP and the website answer it without registering it anywhere.
- See what the repository holds, and run one of its capabilities, without reading a fileOpen the shared server in a browser and get the whole layer as pages: what exists, where each thing came from, what depends on what, what is failing, and a form that runs any capability.
The moments this answers