One command linefor the whole layer.

A capability that claims a command answers there through the same executor the HTTP API and the MCP tools ask; the clap tree is checked against the registry in both directions. The task lifecycle, start, check and finish, belongs to the shell tool, the other program that answers to majordomus.

“A capability is declared once.”

One registry, every interface

Instant overview
majordomus env: the project, version control, the toolchains, the layer and the local services.
A documented reference
234 commands and 237 examples, generated from apps/majordomus-cli/src/cli.rs.
Shell integration
majordomus completion answers a shell from the command graph.
Built for automation
Machine-readable output where a command takes --format json or --json.

$ majordomus start 'the follow-up' --scope lib

started t-<id>  profile=implementation  scope=lib
INFO handover    .ai/local/state/handovers/<time>--main--<head>--<hash>.md — prior record, same_worktree_same_branch, exact, <age> ago  [reproduce: majordomus handover --resolve]
next: majordomus context; checkpoint every 15m; majordomus check before claiming anything

majordomususage: majordomus <COMMAND>

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

mcp: Serve the repository's AI layer to an MCP client over stdio
serve: Serve the same capabilities over HTTP on the loopback interface, with the home page, /openapi.json, /swagger and the documentation under /docs/
capabilities: Introspect the capability registry: what exists, where it came from, how it is exposed
generate: Write the committed projections of the registry (docs/generated), or check that they are current
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
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
completion: Completion for any surface, answered from the command graph: the candidates a shell asks for, and the one-time integration that asks
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
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
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
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
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

12 of 43 top-level commands · from cli.json

See it in action

Examples the command reference documents, by what they do.

Overview

majordomus env
majordomus product
majordomus why
majordomus distribution
majordomus release
majordomus worktree

Inspect

majordomus mcp --inspect
majordomus product matrix
majordomus web list
majordomus models list
majordomus env explain project.version
majordomus commands graph --format json

Run

majordomus serve --port 0
majordomus serve status
majordomus executions
majordomus generate
majordomus mcp --standalone
majordomus serve stop

Check

majordomus generate --check
majordomus capabilities validate
majordomus product validate
majordomus worktree validate
majordomus web validate
majordomus bench coverage --check

Output

majordomus env status --format json
majordomus capabilities list --format json
majordomus rules report --format json
majordomus release changelog --format json
majordomus executions list --format json
majordomus entity kinds --format json

Consistent everywhere

The same capability on the command line, over HTTP and as an MCP tool.

One registryevery surface asks the same executor
Deterministicthe same input projects the same bytes
Checkeda projection that disagrees fails the build
Documented1613 arguments in the reference
Generatedthe reference is rendered from the clap tree

Common commands

Command reference Shell commands

majordomus mcpServe the repository's AI layer to an MCP client… majordomus serveServe the same capabilities over HTTP on the loo… majordomus envWhat this checkout is majordomus worktreeThe branch-to-worktree topology majordomus initCreate the .ai/ layer in this repository majordomus doctorIt checks governance only: is Majordomus itself … majordomus contextWhat the next worker needs to know now majordomus checkIs the current task still consistent with its po…