Command line reference

Majordomus control plane: a data-driven MCP server over the repository's .ai/ layer

The Rust executable of Majordomus. It reads the repository's provider-neutral AI layer under .ai/ and serves it to MCP clients over stdio. Almost every capability is a query; the few that change anything declare themselves as commands and are listed by `capabilities list --kind command`. Most of the task lifecycle (init, start, check, finish, doctor, ...) is the shell tool bin/majordomus in the same repository. Development semantics are converging onto capabilities of this registry one at a time (ADR 0040); until one has, this executable does not implement that command.

Every command

Each has its own page with its usage, its arguments, their defaults and accepted values, and at least one example that the crate's tests run against the built executable.

• majordomus mcp Serve the repository's AI layer to an MCP client over stdio 3 examples
• majordomus serve Serve the same capabilities over HTTP on the loopback interface, with the home page, /openapi.json, /swagger and the documentation under /docs/ 1 example
• majordomus serve status Where this checkout's server stands — absent, starting, ready, outdated or stale — and every server of the repository 1 example
• majordomus serve ensure Make sure a ready server serves this checkout: start one when there is none or the lease is stale, wait for one that is starting, and report where it stands 1 example
• majordomus serve stop Stop this checkout's server — the one its lease names, when it answers for this checkout — and wait for that server's lease to go, which another process taking the checkout over does not undo 1 example
• majordomus capabilities Introspect the capability registry: what exists, where it came from, how it is exposed group
• majordomus capabilities list Every capability, one line each, with its projections 2 examples
• majordomus capabilities describe One capability by canonical id: schemas, provenance, every projection 1 example
• majordomus capabilities schema The canonical input or output JSON Schema of one capability 1 example
• majordomus capabilities projections Where each capability is projected, and every claim its surface does not answer 2 examples
• majordomus capabilities validate Build the registry and every projection; exit 10 with every violation named 1 example
• majordomus generate Write the committed projections of the registry (docs/generated), or check that they are current 4 examples
• majordomus bench Time every externally callable operation (each capability directly, over MCP and over HTTP, and the transports' own operations), report coverage, compare with the accepted baseline 1 example
• majordomus bench coverage Every required target and whether it is covered; the denominator is generated from the registry 2 examples
• majordomus bench baseline The accepted baseline of this platform under .ai/repo/benchmarks/rust/ group
• majordomus bench baseline update Run the benchmarks and record them as this platform's baseline (a reviewable, tracked file) 1 example
• majordomus scope The repository scope: what a worker reads and what it never reads; with paths, whether each is in or out and why 2 examples
• majordomus web The repository's web surfaces: what is exposed, where it is mounted, what produced it, and whether the topology is valid 1 example
• majordomus web list Every discovered surface: id, kind, mount, producer 1 example
• majordomus web explain Why each surface exists and where each of its values came from 1 example
• majordomus web validate Check the topology's invariants; exit 10 on any error finding 1 example
• majordomus web manifest Write the resolved topology to the generated manifest 1 example
• majordomus web report Render a generated report into its own surface under the generated web root group
• majordomus web report tests The test run: the behavioural cases' report, and the crate's own totals 1 example
• majordomus web report benchmarks The benchmark run: a results document, or the accepted baseline 1 example
• majordomus web report ui The UI conformance audit, rendered as a section of the test surface (/tests/ui) 1 example
• majordomus web report ui-snapshot The UI itself, read once at this commit and written as static pages a publication carries at /ui (ADR 0141) 1 example
• majordomus web report cockpit-snapshot The Cockpit itself, read once at this commit and written as static pages a publication carries at /cockpit (ADR 0147) 1 example
• majordomus web compose Compose every published surface into one publishable tree 1 example
• majordomus why The operational moments this tool answers: the catalogue, one moment, the audiences and areas, a diagnosis of your own week, and the catalogue's own validation 1 example
• majordomus why list Every operational moment, narrowed by any facet the catalogue reports 3 examples
• majordomus why show One moment in full, with every relation derived from its metadata 1 example
• majordomus why audiences Every audience, with the moments that name it 1 example
• majordomus why areas Every operational area, with the moments that fall under it 1 example
• majordomus why diagnose What the symptoms you recognise imply: the areas they weigh towards and the mechanisms that answer them 2 examples
• majordomus why validate Every finding over the catalogue; exit 10 when any is an error 1 example
• majordomus devtask One issue or one milestone as an executable development scope: what was authored, where the plan graph puts it, what happened to it, whether a worker may start it — with the origin of every value on the value group
• majordomus devtask issue One issue as an executable development task, every field carrying where it came from 3 examples
• majordomus devtask milestone One milestone as an executable dependency graph: ready, blocked, parallelizable, critical blockers, cycles 2 examples
• majordomus distribution How this project is packaged, published and installed: the platforms, the artifact names, the installer, the releases 1 example
• majordomus distribution show The model: the install command, where an installation goes, and every declared target 1 example
• majordomus distribution status Whether the advertised one-line installation works right now, and what is missing when it does not 1 example
• majordomus distribution validate Every invariant of the model and of the release records; exit 10 with each violation named 1 example
• majordomus distribution targets Every declared target, one line each, with the artifact name it derives 1 example
• majordomus distribution matrix The release build matrix, as the release workflow reads it 1 example
• majordomus distribution artifact The archive name and root directory a target and a tag derive 1 example
• majordomus distribution releases Every recorded release, newest first, and the one an unpinned installation resolves to 1 example
• majordomus distribution metadata The public metadata one release record publishes, rendered from the record alone 1 example
• majordomus distribution build What this executable is: version, target triple, profile, commit 1 example
• majordomus env What this checkout is: the project, version control, the toolchains it declares, what the layer holds, the workflows, the provider projections and the local services 1 example
• majordomus env status The whole snapshot, resolved in full: what the layer holds is counted, and the cache the banner reads is written 1 example
• majordomus env banner Render the snapshot for a terminal. Goes to standard error, never standard output, because direnv reads standard output as the environment it is setting 1 example
• majordomus env export The variable assignments a shell in this repository benefits from, for `eval`. Assignments only: no command, no side effect 1 example
• majordomus env enter Enter the repository: the assignments a shell here benefits from on standard output, the banner on standard error, the workflow bridge refreshed when a declaration behind it moved, and the runtime ensured — the whole of what entering this repository is, as one call, so that no person and no agent has to remember a sequence. Never builds, never reaches a remote network, and never waits for a server it started to answer 1 example
• majordomus env explain Where each value came from: the file, command or constant that decided it, the resolver that read it, and how far it can be trusted 1 example
• majordomus env preflight Whether Majordomus is in force in this checkout, claim by claim, with the evidence behind each verdict: git, the episode and its briefing, the task and handover, the policy, rules and ADRs, the shared server and the surfaces it serves, the peer board, recorded test runs, rule enforcement, provider projections and the deployment. A verdict that asserts something is in force always names its evidence. Resolves fast, from the rule tally a `--full` run cached; the HTTP route `/api/v1/environment/preflight` and the MCP tool `majordomus_preflight` answer the same value 1 example
• majordomus commands Every command this repository offers, from whichever program offers it: the graph, one command, where each one is projected, and the workflow bridge derived from it 1 example
• majordomus commands list Every command, one line each: what it is, what running it changes, and where it is projected 1 example
• majordomus commands show One command in full: its arguments, its effect, what it needs, and every surface that carries it 1 example
• majordomus commands explain Why one command appears where it does: the declaration it came from, the policy that placed it, and the reason for every surface that withholds it 1 example
• majordomus commands graph The whole graph as one document, with its fingerprint and every diagnostic 1 example
• majordomus commands bridge Materialise the workflow bridge from the graph, and refresh the cache the completion reads; writes nothing when the graph has not changed 1 example
• majordomus completion Completion for any surface, answered from the command graph: the candidates a shell asks for, and the one-time integration that asks 1 example
• majordomus completion query The candidates for one command line, from the command graph. What a shell adapter calls on every TAB 1 example
• majordomus completion init The shell integration to load once, which carries no command of its own and asks this executable for every candidate 1 example
• majordomus completion install Put that integration into the shell's startup file, between managed markers, so that no one maintains it by hand 1 example
• majordomus worktree The branch-to-worktree topology: where every linked worktree belongs (`<repo>-wt/<branch>`), where each one is, and the lifecycle — create, migrate, repair, guard 1 example
• majordomus worktree status Where this call is — branch, worktree, canonical or not, uncommitted work — and how many errors the whole topology carries; exit 10 when this worktree is out of place 1 example
• majordomus worktree list Every registered worktree with its standing, one line each; exit 10 when the topology has an error 1 example
• majordomus worktree topology The whole topology: repository, container, trunk, every worktree, every branch without a worktree, every diagnostic; exit 10 when it has an error 1 example
• majordomus worktree root Print the container every linked worktree belongs under, and nothing else: `cd "$(majordomus worktree root)"` 1 example
• majordomus worktree path Print the canonical path of a branch, and nothing else: `cd "$(majordomus worktree path feature/x)"`. Derived from the name; the branch need not exist 1 example
• majordomus worktree inspect One branch: its canonical path, whether it exists, what occupies the path, the worktree holding it, and what stands in the way 1 example
• majordomus worktree create Create the canonical worktree of a branch. A branch that does not exist here is fetched from the trunk's remote and taken up when the remote has it; otherwise it is created from --base, else from the remote's trunk fetched now (the local trunk only when the remote cannot be read, and then said, with how far behind). The path is derived; none may be given 1 example
• majordomus worktree ensure The canonical worktree of a branch: created when absent, answered when present, refused when the branch is checked out somewhere else 1 example
• majordomus worktree migrate Bring every misplaced worktree to its canonical path, dirty state included, with a fingerprint taken before and after each move; --plan shows the steps and changes nothing 1 example
• majordomus worktree validate Every error of the topology, and nothing else; exit 10 when there is one 1 example
• majordomus worktree doctor Every diagnostic of the topology, errors, warnings and facts, each with its code and remedy; exit 10 when there is an error 1 example
• majordomus worktree guard May a mutation proceed from here? Exit 0 in a canonical worktree, in the primary checkout on the trunk, or detached; exit 10 with the reason otherwise. What the pre-commit hook asks 1 example
• majordomus worktree repair Drop git's registrations of worktrees whose directories are gone, and repair the administrative links of the ones that exist. Deletes no directory 1 example
• majordomus worktree remove Remove one linked worktree by branch or path. Never the primary checkout, never a branch, never uncommitted work without --force 1 example
• majordomus worktree cleanup The branches merged into the trunk whose worktree is clean or absent: what could be removed. Removes nothing without --remove 1 example
• majordomus worktree uncommitted Every linked worktree holding uncommitted work: how many paths, how old the oldest change, what holds it (an active task, an open episode, a process inside) and whether it is abandoned, with the command that would put it on a remote ref. Reads every worktree and writes none 1 example
• majordomus worktree trunk How far this checkout and the local trunk are from the remote trunk, as of the last fetch, judged against the policy's checkout.trunk_distance: current, lagging, stale, unjudged or unmeasured, with the commands that bring it current. Fetches nothing; exit 10 when stale 1 example
• majordomus worktree branches Every local branch, one per line, for a shell completion that wants the live set 1 example
• majordomus prs Pull-request integration: every open pull request classified against the current master with its evidence, the ranked plan, and the executor that merges the next provably safe one — one at a time, re-planning after each (ADR 0101) 1 example
• majordomus prs status Every open pull request with its disposition, risk and reason, in rank order, from the last recorded observation; exit 10 when the observation is stale or absent 1 example
• majordomus prs plan What the executor would do next: the next merge, the pull requests that need master brought in, and the lanes; nothing is changed 1 example
• majordomus prs explain Why one pull request is where it is: the revisions it was decided against, every piece of evidence, its rank and the factors behind it 1 example
• majordomus prs refresh Observe the forge now (the GitHub CLI and one `git fetch`) and record the observation; the only read that reaches the network 1 example
• majordomus prs drain Merge the next ready pull request, verify it landed, observe again, and repeat — at most `--max` merges; `--dry-run` decides without acting 1 example
• majordomus prs cleanup Close the pull requests whose work is provably on master already; without `--apply` it only lists them 1 example
• majordomus prs repair Bring master into one named pull request whose only conflict with it is over derived (`merge=derived`) files. Eligible only when the classification says it is behind master and its merge conflicts on no authored path; an authored conflict is refused, naming the files. A dry run by default, decided offline on the last recorded observation, like `status`. With `--apply` it takes the integration lease, observes the forge again, records the act on the trail first, and merges master in a scratch worktree, derives, commits and pushes a fast-forward leased on the observed head; it never merges into master. Exit 10 on a refusal or an absent observation, 12 when it could not act 1 example
• majordomus prs events The audit trail: every selection, merge, refusal, stale decision and closure this checkout's executor recorded 1 example
• majordomus prs trains The trains of stacked pull requests, in landing order: each link's disposition, relation to master, prepared head under `refs/prep/<n>` (pushed or pending) and turn. Offline and read-only, from the last recorded observation; exit 10 when it is stale or absent 1 example
• majordomus prs brief One line for a session briefing: the last queue built in this checkout (open, by lane, the next merge, the starving), who holds the integration lease and whether it reaches across machines, the last merge, and the last refresh, failure or stale decision. Offline, decides no relation, and prints nothing where the forge was never observed 1 example
• majordomus prs prove-dry-run Prove the non-mutating cycle moves nothing: snapshot origin's refs, the open pull requests, the audit trail, the lease and the local refs, run refresh, plan, drain --dry-run and cleanup (listing), snapshot again and compare; the refresh's fetched mirrors must equal what origin serves. Exit 10 naming what moved. Takes no flag: there is nothing to turn on 1 example
• majordomus offload A branch's derive run on another machine the repository declares (.ai/repo/offload/), in that machine's turn: the hosts and their limits, a probe that names the host a derive would take, and the derive itself — bundle in, a FIFO queue on the host, a build directory of its own, bundle back, staged and never committed group
• majordomus offload hosts The declared hosts and their limits, the queue and the remote layout, as the declaration states them; reads no host. A repository that declares none says so and exits 0 1 example
• majordomus offload probe Measure every declared host — free space, derives running or waiting — and name the one a derive would take; exit 12 when none can take one 1 example
• majordomus offload derive Derive a worktree on a declared host and stage what it changed; nothing is committed or pushed. Exit 2 on an untracked file or an unresolved merge, 10 when the derive fails, 11 when it deletes a tracked file, 12 when no host can take it, 75 when the queue's wait runs out 1 example
• majordomus convergence Is any of this repository's work held where it can be lost? Every holding — a work tree with uncommitted files, a branch with commits, a stash — with the disposition read from git, and one verdict over them 1 example
• majordomus commit The commit as a value: what the working tree would commit and how it divides, the scope vocabulary this repository's history yields, and the verdict on one message against the commit policy 1 example
• majordomus commit plan What the working tree would commit: branch, upstream, divergence, every staged, unstaged and untracked path, any merge or rebase in progress, and the commits the history's own scoping supports — under a fingerprint that makes the plan refusable once the tree moves 2 examples
• majordomus commit scopes Every scope this repository's commit history uses, how often, and the directories each one is written about 1 example
• majordomus commit history Judge every commit in a range of history against the commit policy, in one pass; exit 10 when any carries an error 1 example
• majordomus commit validate Judge one commit message against the repository's commit policy; exit 10 when a finding is an error 1 example
• majordomus product The product: what this repository's tool does for a person, as the features under the layer declare it, with every surface, count and moment derived; the matrix of features against interfaces; the providers; and the model's own validation 1 example
• majordomus product list Every feature, narrowed by any filter, with the surfaces derived for each 2 examples
• majordomus product show One feature in full: what it is made of, resolved, and everything derived from that 1 example
• majordomus product domains The domains of the product, each with the stable features that name it and what they add up to 1 example
• majordomus product matrix Every feature against every interface, and every module, command and kind against the features that name it 1 example
• majordomus product providers Every provider the tool has an adapter for, with what this repository does with it 1 example
• majordomus product validate Every finding over the model; exit 10 when any is an error 1 example
• majordomus release What this project has shipped and what it would ship next: the changelog derived from the layer's own records, the version authored in one place and projected for the shell tool, and the one command that raises it 1 example
• majordomus release changelog The changelog, composed from the layer's release records, the decisions dated inside each release's window, and the conventional commits in its range 1 example
• majordomus release version The version the crate manifest declares, whether the projection the shell tool reads states it, any version written by hand where the tool's files live, and the bump the commits since the last release imply 1 example
• majordomus release analyze What the public contract did since the last release, and the smallest version this tree may therefore declare 1 example
• majordomus release next The version a landing of HEAD onto the trunk allocates, and why: the trunk's version, the measured movement, the policy floor and any exemption (ADR 0134) 1 example
• majordomus release bump Raise the version in the one place it is authored, to at least what the public contract requires; scripts/derive derives the rest 1 example
• majordomus quality What this executable's own public surface is held to: documentation, executable examples, module coverage, and every command accounted for against the capability registry group
• majordomus quality report Measure the crate and report every finding, with the rule it breaks and what to do about it 2 examples
• majordomus quality rustdoc Judge the crate's rustdoc tree against the crate: every page present, HEAD's, nothing broken or leaked 2 examples
• majordomus run Run a capability as an execution and follow it: its steps, its progress and its output as they happen 1 example
• majordomus executions The executions of the server serving this repository: what has run, what is running, and what each one said 1 example
• majordomus executions list Every execution the server remembers, newest first 1 example
• majordomus executions show One execution in full: its state, its steps, its diagnostics and what it produced 1 example
• majordomus executions events One execution's retained events, oldest first 1 example
• majordomus executions cancel Ask an execution to stop 1 example
• majordomus executions protocol The live channel's contract: where it is, what it writes, and the schema of each message 1 example
• majordomus devcontext The context a development session should be given, compiled from the repository: for an issue, a milestone, an intent or a set of paths, what is selected and why, what was left out and why, what collapsed into what, and the budget group
• majordomus devcontext compile Compile the context for a piece of work: every selected object with its provenance, the reason and the confidence, everything left out with the reason, what was deduplicated, and the per-tier budget; exit 10 when what may not be dropped already exceeds the budget 2 examples
• majordomus devcontext explain Why one canonical identifier is or is not in the context a request compiles to 1 example
• majordomus devcontext policy The compiler's own rules: the tiers, every edge of the composed graph and what is done with it, the selectors, the defaults 1 example
• majordomus guard The edit guard: whether a provider's tool may write a file of this checkout now, judged from the active task's scope and the writing session's live mesh claims group
• majordomus guard hook Judge the edit a provider's pre-tool payload (on stdin) is about to make; exit 2 with the reason and the remedy when no claim covers it, 0 otherwise 1 example
• majordomus mesh The mesh: the nodes this repository's running server has discovered on the network, this machine's node identity, and the self-check that proves the prerequisites on this machine alone group
• majordomus mesh status Whether the mesh runs in this checkout's server and why not when it does not, with every provider's state and the registry's tallies 1 example
• majordomus mesh nodes Every node the running server has observed, deduplicated by node identity, with trust, presence, endpoints and provenance 1 example
• majordomus mesh identity This machine's node identity, public half only; absent is an answer, not an error 1 example
• majordomus mesh enrol Add this machine's public key to the mesh declaration's trust list, once; commit it to join 1 example
• majordomus mesh doctor Prove the mesh prerequisites on this machine alone: declaration, identity, sockets, multicast, broadcast, the protocol end to end, and the host firewall 1 example
• majordomus mesh firewall What the host firewall must admit for the declared mesh and whether it does; `apply` admits it, as root 1 example
• majordomus mesh firewall apply Run the commands that admit the plan on this host's firewall; needs root, and exits 10 when it refuses or the firewall still does not admit the mesh 1 example
• majordomus mesh peers Every machine and runtime this checkout's server cooperates with, each link's state, and the active sessions; --full for every session and claim 1 example
• majordomus mesh peer One runtime: its machine, liveness, link, sessions and claims; exits 10 when it is not known here 1 example
• majordomus mesh state The state every linked runtime converges on, summarised with its digest; --full for every session, claim, handover and review 2 examples
• majordomus mesh events The cooperation journal's events after a Lamport stamp, in Lamport order 1 example
• majordomus mesh verify Prove cooperation now: local health, a live round with every peer this server dials, and convergence; exits 10 when a check fails 1 example
• majordomus mesh claim Claim repository paths for a session; exits 10 naming the claims it meets when an exclusive claim on any linked runtime holds them 1 example
• majordomus mesh release Release a claim this server's current run holds 1 example
• majordomus mesh session Open, update or close a session on the mesh group
• majordomus mesh session open Open or update a session: what it is, what it does, where 1 example
• majordomus mesh session close Close a session; its claims end with it on every linked runtime 1 example
• majordomus mesh handover Publish a handover of this checkout to the mesh, or consume one another runtime published group
• majordomus mesh handover publish Publish this checkout's newest handover record (or the one named) to every linked runtime 1 example
• majordomus mesh handover consume Consume a handover another runtime published, writing it as a local record `handover --resolve` finds 1 example
• majordomus mesh review Ask the mesh for a review, or answer a request group
• majordomus mesh review request Ask for a review of a branch, commit or pull request 1 example
• majordomus mesh review answer Answer a review request 1 example
• majordomus mesh review withdraw Withdraw a review request this runtime asked for, with its result 1 example
• majordomus mesh build-cache The mesh build cache: what each dependency install and build directory is cached under group
• majordomus mesh build-cache key Every lockfile the repository tracks, with the key its install or build directory is cached under: schema version, platform, toolchain and input digest 1 example
• majordomus mesh build-cache ensure Restore a dependency install or a cold cargo build directory from the local level or this node's store, verified by its digest; on a miss run the command and save what it left. MAJORDOMUS_BUILD_CACHE=off bypasses every level 1 example
• majordomus mesh build-cache env The sccache client configuration for the store this node selected, as a script `eval` reads: local disk first, the store second only when it is healthy now, the credential by file path only 1 example
• majordomus mesh build-cache provision Plan what this host still owes as a cache provider, or with --apply bring it there as root; idempotent, no secret reported 1 example
• majordomus monitor Everything that happens around this repository, followed in one stream: mesh sessions, claims, handovers and reviews on every linked machine, the executor's merges and failures, and GitHub's pull requests and runs, with what is addressed to you marked 2 examples
• majordomus models The model catalogue the distribution declares, and the explainable routing over it: vendors, canonical model references, typed capabilities, and which model a stated need selects — with why, for every candidate group
• majordomus models list Every declared vendor and model, optionally narrowed; the order is the declaration's, which is routing's preference order 1 example
• majordomus models route Which model a stated need selects, the fallback chain behind it, and why every excluded model fell out 1 example
• majordomus reasoning Provider-independent reasoning: the optional advisors and what they can do now, what an uncertainty calls for, the session's reasoning records, their state and provenance, and the checks that keep reasoning independent of any advisor group
• majordomus reasoning advisors Every advisor with its status and why, the mode in force, and who can provide each advisory capability now; no advisor at all is an ordinary answer 2 examples
• majordomus reasoning plan Whether a stated uncertainty warrants independent review, how much, and from which available advisors — with every advisor left out and why; records nothing 2 examples
• majordomus reasoning record Record one reasoning step of the open task from JSON (`{"kind":"assessment",...}`) read from --file or standard input; a record that breaks a rule is refused and nothing is written 1 example
• majordomus reasoning status The reasoning state of the open task — assessments, consultations, disagreements, conclusions, the timeline — and the report a handover carries 1 example
• majordomus reasoning explain One record with the whole chain of its assessment: why a decision was made 1 example
• majordomus reasoning check Check that reasoning stays provider-independent and that every record is consistent; exit 10 on a finding 1 example
• majordomus evidence What actually ran and what it proves: every claim of the matrix against the runs recorded for it, one claim's proof, one test's claims, and the recording of a run that happened group
• majordomus evidence show Every claim against the evidence recorded for it 2 examples
• majordomus evidence claim One claim: its proof state, the execution behind it, and how to reproduce it 1 example
• majordomus evidence proves One test: its latest execution and every claim it proves 1 example
• majordomus evidence record Record a run that happened into the ledger 1 example
• majordomus evidence stamp Measure the checkout as a run left it, for `record --provenance` 1 example
• majordomus served Whether a deployment serves the commit it was meant to: observe the build identity it serves, judged by commit containment, and read each deployment's recorded standing against a commit group
• majordomus served observe Probe the build identity a deployment serves, judge it against a commit and record it 1 example
• majordomus served forge Ask the forge which deployments and releases it recorded, and keep the answer for the readers 1 example
• majordomus served show Each deployment's newest record, re-judged against a commit 1 example
• majordomus deploy The tree a deployment's provider receives, assembled outside the checkout from the deployment object at one commit: its build inputs, the provider's generated files, the buildpack line and the executable built at that commit group
• majordomus deploy slug Assemble the tree a provider receives into a directory outside the checkout 1 example
• majordomus rules Every rule against the proof there is for it: what each one names, whether it is in the tree, whether a runner drives it, whether anything ran, and whether what ran is older than what it is about group
• majordomus rules report Every rule against the proof there is for it 1 example
• majordomus rules show One rule: what proves it, what it depends on, and what is missing 1 example
• majordomus rules proves One test: every rule it proves, and the rules that would be left with none 1 example
• majordomus intent What must become true above the milestones: every intent with its stage derived from the plan and its satisfaction from the recorded evidence, one intent, the model's own validation, and which intent a piece of work serves group
• majordomus intent list Every intent, with the stage derived from its milestones and its evidence 2 examples
• majordomus intent show One intent in full: each milestone's derived status and each criterion's evidence state 1 example
• majordomus intent validate Every finding over the intents; exit 10 when any is a failure 1 example
• majordomus intent coverage Which work carries which criterion, and the reason every issue exists 2 examples
• majordomus intent preflight Which intent the work on an issue, or on some paths, serves, whether it is maintenance, or why it may not proceed; exit 10 when refused 1 example
• majordomus intent binding What a piece of work is bound to before it starts: the issue, the intent or the paths it names resolved to the criteria it serves, or an exemption the policy declares, with the two pins a resumed worker compares; exit 10 when refused 1 example
• majordomus intent realization Which work realises which intent — tasks, episodes, providers, handovers, peer claims — each link with its provenance, and each intent's unmet criteria and drift; exit 10 when an intent whose milestones are all DONE is contradicted by its evidence 2 examples
• majordomus intent explain Why an intent stands where it stands: its stage, each criterion, the work realising it 1 example
• majordomus intent propose Write a new, unplanned intent: what must become true (ADR 0144) 1 example
• majordomus delivery Whether each product feature exists: on master, deployed, publicly verified, tested, its evidence published and linked — every dimension computed, unknown never a pass group
• majordomus delivery report Every feature against every dimension, with the development stage of what does not exist 1 example
• majordomus delivery show One feature: every dimension with its reason and remediation 1 example
• majordomus plan How far each issue's work has travelled: none, branch, pr_open, merged, released or deployed, each with the object that proved it; the plan's records are read and moved by the shell tool's `plan` group
• majordomus plan delivery Every issue's furthest delivery stage, with the object that proved it and its declared status beside it 2 examples
• majordomus plan drift Every contradiction between an issue's declared status and its delivery — merged_not_recorded, active_without_work, done_without_trace — each with its proof; with --gate, judged against the window .ai/repo/ci/plan.yaml declares 2 examples
• majordomus economics Token economics, measured: matched runs with and without Majordomus, every metric with its measurement class and sample size, the statement the evidence allows, and the check that refuses an unsupported savings claim group
• majordomus economics summary Every metric with its class, sample size and interval, the pairs, the segments, the state of the evidence, and the one statement the publication rule allows 2 examples
• majordomus economics explain One metric and everything it rests on: formula, class, pairs, runs, exclusions, and how to reproduce it 1 example
• majordomus economics runs The recorded runs every metric is computed from 1 example
• majordomus economics check Refuse an unsupported savings claim: quantities next to the economics vocabulary in hand-written prose, and bound claims whose evidence does not stand 1 example
• majordomus economics tasks Each task's wall time, refusals and episodes, from every checkout's ledger; the fields nothing observes yet are named as not observed 1 example
• majordomus economics measure Run a deterministic suite (no model is called) and record its measurement 1 example
• majordomus economics run Run a live suite: real harness sessions with and without Majordomus, recorded as raw usage and gate verdicts. Spends provider usage 1 example
• majordomus economics references Prove every task's hidden tests fail on its starting state and pass on its reference solution. No model is called 1 example
• majordomus entity Every object of the layer as an addressable node: the kinds and their routes, and one entity with its references, its backlinks, the surfaces that answer for it and the state of what it names group
• majordomus entity kinds Every kind of the layer, the route of its index, and every route collision there is 1 example
• majordomus entity show One entity: its route, what it references, what references it, where it is served 2 examples
• majordomus shell The repository's shell automation against the tracked migration inventory: every shell unit declared with an exemption, and every exemption naming a unit the tree still has group
• majordomus shell check Refuse every shell unit the inventory does not declare, and every declaration whose unit is gone; exit 10 on a finding, 12 when the tree cannot be measured 1 example
• majordomus layout The boundary between the layer's tracked and local halves, checked against the layouts their contracts declare: every path a contract excludes, named with the contract group
• majordomus layout check Refuse every path a declared layout excludes, naming the contract; exit 10 on a finding, 12 when the halves cannot be read 1 example
• majordomus pack The tracked tree as token-bounded text shards for a language model's file search: plan what a profile carries and leaves out, build it under tmp/packs/, and verify a written pack against its manifest; never a binary, a worktree, a link or build output group
• majordomus pack plan What a profile would pack: files carried, files left out by reason, the shards and every finding that refuses the build; exit 10 on a finding, 12 when the tree cannot be read 1 example
• majordomus pack build Write the pack (index, shards, pack.json) and verify what was written; exit 10 when the plan or the written pack has a finding, and nothing is built from a plan with one 1 example
• majordomus pack verify Verify a written pack against its manifest and the profile it names; exit 10 on a finding, 12 when the manifest cannot be read 1 example
• majordomus dashboard The Dashboard Suite: each page a projection of the capabilities that hold its facts, every card carrying its source capability, the JSON pointer its value was read from, the Cockpit page with the evidence and the command that acts on it group
• majordomus dashboard overview Is it healthy, what changed, what is broken, what needs action: every card with its value, the source's verdict, and the capability and pointer it was read from; exit 10 when the overview is fail or unknown 1 example
• majordomus brief What surrounds this session, in one line and in a few: its episode and task, the peers of every board, the mesh, the integration queue and the derive queue, asked of the server holding this checkout's lease 1 example
• majordomus blackboard Who works on what in this repository, on every board and every linked machine: each worker with its client, intent, checkout, branch and claims, the claims that meet, the reviews and handovers that wait, typed relations verified only by an explicit identifier, and whether every source could be read — asked of the server holding this checkout's lease 1 example
• majordomus skills Every skill as a proven capability: the tests that name it and the evidence behind them, its page, the doctrine and gates that hold it, what invokes it, and the orphans group
• majordomus skills status Every skill with its derived standing: tested, documented, enforced, used 2 examples
• majordomus skills explain One skill in full: each naming test and its evidence, its page, its gates, every invocation 1 example
• majordomus skills verify Every finding over the skills; exit 10 when any is a failure 1 example
• majordomus knowledge What the knowledge deriver left for review and whether it is still writing: the candidate records awaiting promotion, one record by id with every reference it names resolved, and the derivation status of this checkout judged against the policy's freshness thresholds group
• majordomus knowledge candidates The candidate records awaiting review, with the branch of the episode each came from and how long each has waited 1 example
• majordomus knowledge record One knowledge record by id: its front matter, and every reference it names resolved against the index, the ledger and git 1 example
• majordomus knowledge status Whether the deriver is still writing: the last derivation, the newest closed episode, and the stopped-writer judgement against session.freshness 1 example
• majordomus continuity Continue work on another machine: publish this checkout's newest handover as a signed record in refs/majordomus/continuity, exchange records with a git remote, and plan and resume a handover another device published — with its source compatibility, lineage and trust decided before anything is written group
• majordomus continuity status This device, the record this checkout continues, the store against its remote (no network), every line of work, and what other devices published that could be resumed here 1 example
• majordomus continuity records Every published handover the local store admits, by line, and every file it refused 1 example
• majordomus continuity device This device's identity — the mesh node key, created when absent — and its label; with --label, rename it 1 example
• majordomus continuity plan Decide, writing nothing, whether and how a published handover can be resumed here: trust, lineage, source compatibility, uncommitted work at the origin 1 example
• majordomus continuity publish Publish this checkout's newest handover as a signed record for another machine; refused when it carries a secret or a machine path 1 example
• majordomus continuity sync Exchange published handovers with a git remote: fetch, merge as a union, push; an unreachable remote leaves what is pending pending 1 example
• majordomus continuity resume Resume a published handover when its plan is ready: write it into this checkout's handovers, carry its decisions, and continue its line 1 example

What makes this true

Every command above is declared once, in apps/majordomus-cli/src/cli.rs, together with its examples. The executable walks that declaration into docs/generated/cli.json, and these pages, --help and docs/generated/cli.md render it. A command a person can run cannot exist without an example: the executable's own validator refuses it, and the examples shown here are the argument vectors the crate's example tests execute against the built binary.

The whole command line on one page: the registry's command-line page. The task lifecycle (init, start, check, finish, doctor, ...) belongs to the shell tool bin/majordomus, a different program: see Commands and its specification.