majordomus knowledge
Discovery reads the version-control index with the declared pathspecs and never walks the tree. Nodes keep their identity across a rebuild, kinds are never guessed, and an edge exists only where a file states it. sources, nodes, edges, candidates and check write nothing. search, show and related look up the same nodes and edges and write nothing either: there is no stored index to go stale, so a lookup compiles what the checkout holds; search places each node on the first rung of a fixed ladder it reaches (id, title, title-prefix, path, body) and names the rung (I0811). validate judges the graph itself — duplicate ids, edges with a missing end or no provenance, declared paths and tracked sources that no longer exist — failing on a broken relationship Majordomus defines and only reporting a broken link an author wrote; doctor and watch ask the same validator through majordomus.knowledge-graph (I0812). derive turns the ledger lines one episode stamped into candidate records under the tracked knowledge section, deterministically and without a model; a second run over the same evidence writes nothing and says so. promote and reject are a person's acts on a candidate and each leaves a ledger line; nothing here stages a file (ADR 0091). observe records what a session met as one observation.recorded ledger line, refusing a kind, subject or evidence reference of the wrong shape and a statement that spans lines or opens like a conversation (ADR 0118).
What it is
local mutationThe compiled index over what this repository states, and the candidate records it derives from what an episode did.
- Identity
tool.knowledge- Program
- tool
- Runs
- interactive
- Requires
- repositorylayer
Where it appears
- Command line
majordomus knowledge- Workflow
just knowledge- MCP tool
- —
- HTTP
- —
- Declared in
share/commands.yaml- Capability
- —