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, read-only, to MCP clients over stdio. The task lifecycle (init, start, check, finish, doctor, ...) is the shell tool bin/majordomus in the same repository; this executable does not implement those commands.

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 (read-only) 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/ (read-only) 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 3 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 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 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 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 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, creating the branch from --base (default: the trunk) when it does not exist. 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 1 example
• majordomus worktree branches Every local branch, one per line, for a shell completion that wants the live set 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 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 the two writers state, and the one command that raises both 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 two writers state, whether they agree, and the bump the commits since the last release imply 1 example
• majordomus release bump Raise the version in both places at once, to the bump the commits imply or to one you name 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 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

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.