Skip to content

Read at

A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:01:48Z by majordomus 0.29.0. Nothing on this page is read again. See it live

Command

Everything that can be run, and what is running.

Every command of the executable and the shell tool, with what it changes, and the executions this process is running or remembers.

  • Commands263commands.list /total
  • Executions0executions.list /count
  • Active0executions.list /active
  • Queued0executions.list /queued
  • Live channels0executions.list /live_channels

Commands

Each with the line a person types and what it changes when it runs.

CommandWhat it doesEffect
majordomus benchTime every externally callable operation (each capability directly, over MCP and over HTTP, and the transports' own operations), report coverage, compare with the accepted baselinerepository_mutation
majordomus bench baselineThe accepted baseline of this platform under .ai/repo/benchmarks/rust/repository_mutation
majordomus bench baseline updateRun the benchmarks and record them as this platform's baseline (a reviewable, tracked file)repository_mutation
majordomus bench coverageEvery required target and whether it is covered; the denominator is generated from the registryread_only
majordomus briefWhat 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 leaseread_only
majordomus capabilitiesIntrospect the capability registry: what exists, where it came from, how it is exposedread_only
majordomus capabilities describeOne capability by canonical id: schemas, provenance, every projectionread_only
majordomus capabilities listEvery capability, one line each, with its projectionsread_only
majordomus capabilities projectionsWhere each capability is projected, and every claim its surface does not answerread_only
majordomus capabilities schemaThe canonical input or output JSON Schema of one capabilityread_only
majordomus capabilities validateBuild the registry and every projection; exit 10 with every violation namedread_only
majordomus commandsEvery command this repository offers, from whichever program offers it: the graph, one command, where each one is projected, and the workflow bridge derived from itread_only
majordomus commands bridgeMaterialise the workflow bridge from the graph, and refresh the cache the completion reads; writes nothing when the graph has not changedread_only
majordomus commands explainWhy one command appears where it does: the declaration it came from, the policy that placed it, and the reason for every surface that withholds itread_only
majordomus commands graphThe whole graph as one document, with its fingerprint and every diagnosticread_only
majordomus commands listEvery command, one line each: what it is, what running it changes, and where it is projectedread_only
majordomus commands showOne command in full: its arguments, its effect, what it needs, and every surface that carries itread_only
majordomus commitThe 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 policyread_only
majordomus commit historyJudge every commit in a range of history against the commit policy, in one pass; exit 10 when any carries an errorread_only
majordomus commit planWhat 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 movesread_only
majordomus commit scopesEvery scope this repository's commit history uses, how often, and the directories each one is written aboutread_only
majordomus commit validateJudge one commit message against the repository's commit policy; exit 10 when a finding is an errorread_only
majordomus completionCompletion for any surface, answered from the command graph: the candidates a shell asks for, and the one-time integration that asksread_only
majordomus completion initThe shell integration to load once, which carries no command of its own and asks this executable for every candidateread_only
majordomus completion installPut that integration into the shell's startup file, between managed markers, so that no one maintains it by handlocal_mutation
majordomus completion queryThe candidates for one command line, from the command graph. What a shell adapter calls on every TABread_only
majordomus continuityContinue 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 writtenread_only
majordomus continuity deviceThis device's identity — the mesh node key, created when absent — and its label; with --label, rename itlocal_mutation
majordomus continuity planDecide, writing nothing, whether and how a published handover can be resumed here: trust, lineage, source compatibility, uncommitted work at the originread_only
majordomus continuity publishPublish this checkout's newest handover as a signed record for another machine; refused when it carries a secret or a machine pathrepository_mutation
majordomus continuity recordsEvery published handover the local store admits, by line, and every file it refusedread_only
majordomus continuity resumeResume a published handover when its plan is ready: write it into this checkout's handovers, carry its decisions, and continue its linerepository_mutation
majordomus continuity statusThis 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 hereread_only
majordomus continuity syncExchange published handovers with a git remote: fetch, merge as a union, push; an unreachable remote leaves what is pending pendingrepository_mutation
majordomus convergenceIs 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 themread_only
majordomus dashboardThe 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 itread_only
majordomus dashboard overviewIs 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 unknownread_only
majordomus deliveryWhether each product feature exists: on master, deployed, publicly verified, tested, its evidence published and linked — every dimension computed, unknown never a passread_only
majordomus delivery reportEvery feature against every dimension, with the development stage of what does not existread_only
majordomus delivery showOne feature: every dimension with its reason and remediationread_only
majordomus devcontextThe 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 budgetread_only
majordomus devcontext compileCompile 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 budgetread_only
majordomus devcontext explainWhy one canonical identifier is or is not in the context a request compiles toread_only
majordomus devcontext policyThe compiler's own rules: the tiers, every edge of the composed graph and what is done with it, the selectors, the defaultsread_only
majordomus devtaskOne 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 valueread_only
majordomus devtask issueOne issue as an executable development task, every field carrying where it came fromread_only
majordomus devtask milestoneOne milestone as an executable dependency graph: ready, blocked, parallelizable, critical blockers, cyclesread_only
majordomus distributionHow this project is packaged, published and installed: the platforms, the artifact names, the installer, the releasesread_only
majordomus distribution artifactThe archive name and root directory a target and a tag deriveread_only
majordomus distribution buildWhat this executable is: version, target triple, profile, commitread_only
majordomus distribution matrixThe release build matrix, as the release workflow reads itread_only
majordomus distribution metadataThe public metadata one release record publishes, rendered from the record aloneread_only
majordomus distribution releasesEvery recorded release, newest first, and the one an unpinned installation resolves toread_only
majordomus distribution showThe model: the install command, where an installation goes, and every declared targetread_only
majordomus distribution statusWhether the advertised one-line installation works right now, and what is missing when it does notread_only
majordomus distribution targetsEvery declared target, one line each, with the artifact name it derivesread_only
majordomus distribution validateEvery invariant of the model and of the release records; exit 10 with each violation namedread_only
majordomus economicsToken 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 claimread_only
majordomus economics checkRefuse an unsupported savings claim: quantities next to the economics vocabulary in hand-written prose, and bound claims whose evidence does not standread_only
majordomus economics explainOne metric and everything it rests on: formula, class, pairs, runs, exclusions, and how to reproduce itread_only
majordomus economics measureRun a deterministic suite (no model is called) and record its measurementread_only
majordomus economics referencesProve every task's hidden tests fail on its starting state and pass on its reference solution. No model is calledread_only
majordomus economics runRun a live suite: real harness sessions with and without Majordomus, recorded as raw usage and gate verdicts. Spends provider usageread_only
majordomus economics runsThe recorded runs every metric is computed fromread_only
majordomus economics summaryEvery metric with its class, sample size and interval, the pairs, the segments, the state of the evidence, and the one statement the publication rule allowsread_only
majordomus entityEvery 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 namesread_only
majordomus entity kindsEvery kind of the layer, the route of its index, and every route collision there isread_only
majordomus entity showOne entity: its route, what it references, what references it, where it is servedread_only
majordomus envWhat this checkout is: the project, version control, the toolchains it declares, what the layer holds, the workflows, the provider projections and the local servicesread_only
majordomus env bannerRender the snapshot for a terminal. Goes to standard error, never standard output, because direnv reads standard output as the environment it is settingread_only
majordomus env enterEnter 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 answerread_only
majordomus env explainWhere each value came from: the file, command or constant that decided it, the resolver that read it, and how far it can be trustedread_only
majordomus env exportThe variable assignments a shell in this repository benefits from, for `eval`. Assignments only: no command, no side effectread_only
majordomus env preflightWhether 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 valueread_only
majordomus env statusThe whole snapshot, resolved in full: what the layer holds is counted, and the cache the banner reads is writtenread_only
majordomus evidenceWhat 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 happenedread_only
majordomus evidence claimOne claim: its proof state, the execution behind it, and how to reproduce itread_only
majordomus evidence provesOne test: its latest execution and every claim it provesread_only
majordomus evidence recordRecord a run that happened into the ledgerlocal_mutation
majordomus evidence showEvery claim against the evidence recorded for itread_only
majordomus evidence stampMeasure the checkout as a run left it, for `record --provenance`read_only
majordomus executionsThe executions of the server serving this repository: what has run, what is running, and what each one saidread_only
majordomus executions cancelAsk an execution to stoplocal_mutation
majordomus executions eventsOne execution's retained events, oldest firstread_only
majordomus executions listEvery execution the server remembers, newest firstread_only
majordomus executions protocolThe live channel's contract: where it is, what it writes, and the schema of each messageread_only
majordomus executions showOne execution in full: its state, its steps, its diagnostics and what it producedread_only
majordomus generateWrite the committed projections of the registry (docs/generated), or check that they are currentrepository_mutation
majordomus guardThe 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 claimsread_only
majordomus guard hookJudge 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 otherwiseread_only
majordomus intentWhat 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 servesread_only
majordomus intent bindingWhat 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 refusedread_only
majordomus intent coverageWhich work carries which criterion, and the reason every issue existsread_only
majordomus intent explainWhy an intent stands where it stands: its stage, each criterion, the work realising itread_only
majordomus intent listEvery intent, with the stage derived from its milestones and its evidenceread_only
majordomus intent preflightWhich intent the work on an issue, or on some paths, serves, whether it is maintenance, or why it may not proceed; exit 10 when refusedread_only
majordomus intent proposeWrite a new, unplanned intent: what must become true (ADR 0144)repository_mutation
majordomus intent realizationWhich 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 evidenceread_only
majordomus intent showOne intent in full: each milestone's derived status and each criterion's evidence stateread_only
majordomus intent validateEvery finding over the intents; exit 10 when any is a failureread_only
majordomus knowledgeWhat 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 thresholdsread_only
majordomus knowledge candidatesThe candidate records awaiting review, with the branch of the episode each came from and how long each has waitedread_only
majordomus knowledge recordOne knowledge record by id: its front matter, and every reference it names resolved against the index, the ledger and gitread_only
majordomus knowledge statusWhether the deriver is still writing: the last derivation, the newest closed episode, and the stopped-writer judgement against session.freshnessread_only
majordomus mcpServe the repository's AI layer to an MCP client over stdioread_only
majordomus meshThe 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 aloneread_only
majordomus mesh claimClaim repository paths for a session; exits 10 naming the claims it meets when an exclusive claim on any linked runtime holds themread_only
majordomus mesh doctorProve the mesh prerequisites on this machine alone: declaration, identity, sockets, multicast, broadcast, the protocol end to end, and the host firewallread_only
majordomus mesh eventsThe cooperation journal's events after a Lamport stamp, in Lamport orderread_only
majordomus mesh firewallWhat the host firewall must admit for the declared mesh and whether it does; `apply` admits it, as rootread_only
majordomus mesh firewall applyRun 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 meshlocal_mutation
majordomus mesh handoverPublish a handover of this checkout to the mesh, or consume one another runtime publishedread_only
majordomus mesh handover consumeConsume a handover another runtime published, writing it as a local record `handover --resolve` findsread_only
majordomus mesh handover publishPublish this checkout's newest handover record (or the one named) to every linked runtimeread_only
majordomus mesh identityThis machine's node identity, public half only; absent is an answer, not an errorread_only
majordomus mesh nodesEvery node the running server has observed, deduplicated by node identity, with trust, presence, endpoints and provenanceread_only
majordomus mesh peerOne runtime: its machine, liveness, link, sessions and claims; exits 10 when it is not known hereread_only
majordomus mesh peersEvery machine and runtime this checkout's server cooperates with, each link's state, and the active sessions; --full for every session and claimread_only
majordomus mesh releaseRelease a claim this server's current run holdsread_only
majordomus mesh reviewAsk the mesh for a review, or answer a requestread_only
majordomus mesh review answerAnswer a review requestread_only
majordomus mesh review requestAsk for a review of a branch, commit or pull requestread_only
majordomus mesh review withdrawWithdraw a review request this runtime asked for, with its resultread_only
majordomus mesh sessionOpen, update or close a session on the meshread_only
majordomus mesh session closeClose a session; its claims end with it on every linked runtimeread_only
majordomus mesh session openOpen or update a session: what it is, what it does, whereread_only
majordomus mesh stateThe state every linked runtime converges on, summarised with its digest; --full for every session, claim, handover and reviewread_only
majordomus mesh statusWhether the mesh runs in this checkout's server and why not when it does not, with every provider's state and the registry's talliesread_only
majordomus mesh verifyProve cooperation now: local health, a live round with every peer this server dials, and convergence; exits 10 when a check failsread_only
majordomus modelsThe 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 candidateread_only
majordomus models listEvery declared vendor and model, optionally narrowed; the order is the declaration's, which is routing's preference orderread_only
majordomus models routeWhich model a stated need selects, the fallback chain behind it, and why every excluded model fell outread_only
majordomus monitorEverything 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 markedread_only
majordomus offloadA 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 committedread_only
majordomus offload deriveDerive 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 outread_only
majordomus offload hostsThe 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 0read_only
majordomus offload probeMeasure every declared host — free space, derives running or waiting — and name the one a derive would take; exit 12 when none can take oneread_only
majordomus packThe 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 outputread_only
majordomus pack buildWrite 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 oneread_only
majordomus pack planWhat 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 readread_only
majordomus pack verifyVerify a written pack against its manifest and the profile it names; exit 10 on a finding, 12 when the manifest cannot be readread_only
majordomus productThe 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 validationread_only
majordomus product domainsThe domains of the product, each with the stable features that name it and what they add up toread_only
majordomus product listEvery feature, narrowed by any filter, with the surfaces derived for eachread_only
majordomus product matrixEvery feature against every interface, and every module, command and kind against the features that name itread_only
majordomus product providersEvery provider the tool has an adapter for, with what this repository does with itread_only
majordomus product showOne feature in full: what it is made of, resolved, and everything derived from thatread_only
majordomus product validateEvery finding over the model; exit 10 when any is an errorread_only
majordomus prsPull-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)read_only
majordomus prs briefOne 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 observedread_only
majordomus prs cleanupClose the pull requests whose work is provably on master already; without `--apply` it only lists themread_only
majordomus prs drainMerge the next ready pull request, verify it landed, observe again, and repeat — at most `--max` merges; `--dry-run` decides without actingread_only
majordomus prs eventsThe audit trail: every selection, merge, refusal, stale decision and closure this checkout's executor recordedread_only
majordomus prs explainWhy one pull request is where it is: the revisions it was decided against, every piece of evidence, its rank and the factors behind itread_only
majordomus prs planWhat the executor would do next: the next merge, the pull requests that need master brought in, and the lanes; nothing is changedread_only
majordomus prs prove-dry-runProve 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 onread_only
majordomus prs refreshObserve the forge now (the GitHub CLI and one `git fetch`) and record the observation; the only read that reaches the networkread_only
majordomus prs repairBring 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 actread_only
majordomus prs statusEvery 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 absentread_only
majordomus prs trainsThe 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 absentread_only
majordomus qualityWhat this executable's own public surface is held to: documentation, executable examples, module coverage, and every command accounted for against the capability registryread_only
majordomus quality reportMeasure the crate and report every finding, with the rule it breaks and what to do about itread_only
majordomus quality rustdocJudge the crate's rustdoc tree against the crate: every page present, HEAD's, nothing broken or leakedread_only
majordomus reasoningProvider-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 advisorread_only
majordomus reasoning advisorsEvery 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 answerread_only
majordomus reasoning checkCheck that reasoning stays provider-independent and that every record is consistent; exit 10 on a findingread_only
majordomus reasoning explainOne record with the whole chain of its assessment: why a decision was maderead_only
majordomus reasoning planWhether a stated uncertainty warrants independent review, how much, and from which available advisors — with every advisor left out and why; records nothingread_only
majordomus reasoning recordRecord 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 writtenrepository_mutation
majordomus reasoning statusThe reasoning state of the open task — assessments, consultations, disagreements, conclusions, the timeline — and the report a handover carriesread_only
majordomus releaseWhat 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 itread_only
majordomus release analyzeWhat the public contract did since the last release, and the smallest version this tree may therefore declareread_only
majordomus release bumpRaise the version in the one place it is authored, to at least what the public contract requires; scripts/derive derives the restrepository_mutation
majordomus release changelogThe changelog, composed from the layer's release records, the decisions dated inside each release's window, and the conventional commits in its rangeread_only
majordomus release nextThe 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)read_only
majordomus release versionThe 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 implyread_only
majordomus rulesEvery 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 aboutread_only
majordomus rules provesOne test: every rule it proves, and the rules that would be left with noneread_only
majordomus rules reportEvery rule against the proof there is for itread_only
majordomus rules showOne rule: what proves it, what it depends on, and what is missingread_only
majordomus runRun a capability as an execution and follow it: its steps, its progress and its output as they happenrepository_mutation
majordomus scopeThe repository scope: what a worker reads and what it never reads; with paths, whether each is in or out and whyread_only
majordomus serveServe the same capabilities over HTTP on the loopback interface, with the home page, /openapi.json, /swagger and the documentation under /docs/read_only
majordomus serve ensureMake 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 standsread_only
majordomus serve statusWhere this checkout's server stands — absent, starting, ready, outdated or stale — and every server of the repositoryread_only
majordomus serve stopStop 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 undoread_only
majordomus servedWhether 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 commitread_only
majordomus served forgeAsk the forge which deployments and releases it recorded, and keep the answer for the readerslocal_mutation
majordomus served observeProbe the build identity a deployment serves, judge it against a commit and record itlocal_mutation
majordomus served showEach deployment's newest record, re-judged against a commitread_only
majordomus shellThe 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 hasread_only
majordomus shell checkRefuse 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 measuredread_only
majordomus skillsEvery 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 orphansread_only
majordomus skills explainOne skill in full: each naming test and its evidence, its page, its gates, every invocationread_only
majordomus skills statusEvery skill with its derived standing: tested, documented, enforced, usedread_only
majordomus skills verifyEvery finding over the skills; exit 10 when any is a failureread_only
majordomus webThe repository's web surfaces: what is exposed, where it is mounted, what produced it, and whether the topology is validread_only
majordomus web composeCompose every published surface into one publishable treeread_only
majordomus web explainWhy each surface exists and where each of its values came fromread_only
majordomus web listEvery discovered surface: id, kind, mount, producerread_only
majordomus web manifestWrite the resolved topology to the generated manifestread_only
majordomus web reportRender a generated report into its own surface under the generated web rootread_only
majordomus web report benchmarksThe benchmark run: a results document, or the accepted baselineread_only
majordomus web report cockpit-snapshotThe Cockpit itself, read once at this commit and written as static pages a publication carries at /cockpit (ADR 0147)read_only
majordomus web report testsThe test run: the behavioural cases' report, and the crate's own totalsread_only
majordomus web report uiThe UI conformance audit, rendered as a section of the test surface (/tests/ui)read_only
majordomus web report ui-snapshotThe UI itself, read once at this commit and written as static pages a publication carries at /ui (ADR 0141)read_only
majordomus web validateCheck the topology's invariants; exit 10 on any error findingread_only
majordomus whyThe operational moments this tool answers: the catalogue, one moment, the audiences and areas, a diagnosis of your own week, and the catalogue's own validationread_only
majordomus why areasEvery operational area, with the moments that fall under itread_only
majordomus why audiencesEvery audience, with the moments that name itread_only
majordomus why diagnoseWhat the symptoms you recognise imply: the areas they weigh towards and the mechanisms that answer themread_only
majordomus why listEvery operational moment, narrowed by any facet the catalogue reportsread_only
majordomus why showOne moment in full, with every relation derived from its metadataread_only
majordomus why validateEvery finding over the catalogue; exit 10 when any is an errorread_only
majordomus worktreeThe branch-to-worktree topology: where every linked worktree belongs (`<repo>-wt/<branch>`), where each one is, and the lifecycle — create, migrate, repair, guardread_only
majordomus worktree branchesEvery local branch, one per line, for a shell completion that wants the live setread_only
majordomus worktree cleanupThe branches merged into the trunk whose worktree is clean or absent: what could be removed. Removes nothing without --removeread_only
majordomus worktree createCreate 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 givenrepository_mutation
majordomus worktree doctorEvery diagnostic of the topology, errors, warnings and facts, each with its code and remedy; exit 10 when there is an errorread_only
majordomus worktree ensureThe canonical worktree of a branch: created when absent, answered when present, refused when the branch is checked out somewhere elserepository_mutation
majordomus worktree guardMay 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 asksread_only
majordomus worktree inspectOne branch: its canonical path, whether it exists, what occupies the path, the worktree holding it, and what stands in the wayread_only
majordomus worktree listEvery registered worktree with its standing, one line each; exit 10 when the topology has an errorread_only
majordomus worktree migrateBring 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 nothingread_only
majordomus worktree pathPrint the canonical path of a branch, and nothing else: `cd "$(majordomus worktree path feature/x)"`. Derived from the name; the branch need not existread_only
majordomus worktree removeRemove one linked worktree by branch or path. Never the primary checkout, never a branch, never uncommitted work without --forcedestructive
majordomus worktree repairDrop git's registrations of worktrees whose directories are gone, and repair the administrative links of the ones that exist. Deletes no directoryrepository_mutation
majordomus worktree rootPrint the container every linked worktree belongs under, and nothing else: `cd "$(majordomus worktree root)"`read_only
majordomus worktree statusWhere 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 placeread_only
majordomus worktree topologyThe whole topology: repository, container, trunk, every worktree, every branch without a worktree, every diagnostic; exit 10 when it has an errorread_only
majordomus worktree uncommittedEvery 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 noneread_only
majordomus worktree validateEvery error of the topology, and nothing else; exit 10 when there is oneread_only

commands.list122 msAPI/api/v1/commandsMCPmajordomus_commandstechnical view

capabilities.list0 msread 6 s agoAPI/api/v1/capabilitiesCLImajordomus capabilities listMCPmajordomus_capabilitiestechnical view

Executions

What this process is running, or ran and remembers, through its execution engine.

This process is running no execution and remembers none.

executions.list0 msread 10 s agoAPI/api/v1/executionsCLImajordomus executions listMCPmajordomus_executionstechnical view