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

Commands

Every command of every program here, and every surface that carries it.

What this repository offers

d448d54d6305d4b9

263commandsthe command graph

221shownthis filter

Composed from the three declarations that already exist: the clap tree of the Rust executable, the shipped command registry of the shell tool, and the recipes the workflow runner describes. Where a command appears is derived from what running it changes, never declared.

Every command

command	effect	program	workflow	mcp tool	summary
majordomus bench coverage	read only	executable	`just bench-coverage`	—	Every required target and whether it is covered; the denominator is generated from the registry
majordomus brief	read only	executable	`just brief`	`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
majordomus capabilities	read only	executable	—	—	Introspect the capability registry: what exists, where it came from, how it is exposed
majordomus capabilities describe	read only	executable	`just capabilities-describe`	`majordomus_capability`	One capability by canonical id: schemas, provenance, every projection
majordomus capabilities list	read only	executable	`just capabilities-list`	`majordomus_capabilities`	Every capability, one line each, with its projections
majordomus capabilities projections	read only	executable	`just capabilities-projections`	`majordomus_projections`	Where each capability is projected, and every claim its surface does not answer
majordomus capabilities schema	read only	executable	`just capabilities-schema`	—	The canonical input or output JSON Schema of one capability
majordomus capabilities validate	read only	executable	`just capabilities-validate`	—	Build the registry and every projection; exit 10 with every violation named
majordomus commands	read only	executable	`just 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
majordomus commands bridge	read only	executable	`just commands-bridge`	—	Materialise the workflow bridge from the graph, and refresh the cache the completion reads; writes nothing when the graph has not changed
majordomus commands explain	read only	executable	`just 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
majordomus commands graph	read only	executable	`just commands-graph`	—	The whole graph as one document, with its fingerprint and every diagnostic
majordomus commands list	read only	executable	`just commands-list`	—	Every command, one line each: what it is, what running it changes, and where it is projected
majordomus commands show	read only	executable	`just commands-show`	—	One command in full: its arguments, its effect, what it needs, and every surface that carries it
majordomus commit	read only	executable	`just 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
majordomus commit history	read only	executable	`just commit-history`	`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
majordomus commit plan	read only	executable	`just commit-plan`	`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
majordomus commit scopes	read only	executable	`just commit-scopes`	`majordomus_commit_scopes`	Every scope this repository's commit history uses, how often, and the directories each one is written about
majordomus commit validate	read only	executable	`just commit-validate`	`majordomus_commit_validate`	Judge one commit message against the repository's commit policy; exit 10 when a finding is an error
majordomus completion	read only	executable	`just completion`	—	Completion for any surface, answered from the command graph: the candidates a shell asks for, and the one-time integration that asks
majordomus completion init	read only	executable	`just completion-init`	—	The shell integration to load once, which carries no command of its own and asks this executable for every candidate
majordomus completion query	read only	executable	`just completion-query`	—	The candidates for one command line, from the command graph. What a shell adapter calls on every TAB
majordomus continuity	read only	executable	—	—	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
majordomus continuity plan	read only	executable	`just continuity-plan`	`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
majordomus continuity records	read only	executable	`just continuity-records`	`majordomus_continuity_records`	Every published handover the local store admits, by line, and every file it refused
majordomus continuity status	read only	executable	`just continuity-status`	`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
majordomus convergence	read only	executable	`just convergence`	`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
majordomus dashboard	read only	executable	—	—	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
majordomus dashboard overview	read only	executable	`just dashboard-overview`	`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
majordomus delivery	read only	executable	—	—	Whether each product feature exists: on master, deployed, publicly verified, tested, its evidence published and linked — every dimension computed, unknown never a pass
majordomus delivery report	read only	executable	`just delivery-report`	`majordomus_delivery`	Every feature against every dimension, with the development stage of what does not exist
majordomus delivery show	read only	executable	`just delivery-show`	`majordomus_delivery_feature`	One feature: every dimension with its reason and remediation
majordomus devcontext	read only	executable	—	—	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
majordomus devcontext compile	read only	executable	`just devcontext-compile`	`majordomus_devcontext`	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
majordomus devcontext explain	read only	executable	`just devcontext-explain`	`majordomus_devcontext_explain`	Why one canonical identifier is or is not in the context a request compiles to
majordomus devcontext policy	read only	executable	`just devcontext-policy`	`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
majordomus devtask	read only	executable	—	—	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
majordomus devtask issue	read only	executable	`just devtask-issue`	`majordomus_devtask`	One issue as an executable development task, every field carrying where it came from
majordomus devtask milestone	read only	executable	`just devtask-milestone`	`majordomus_devtask_milestone`	One milestone as an executable dependency graph: ready, blocked, parallelizable, critical blockers, cycles
majordomus distribution	read only	executable	`just distribution`	—	How this project is packaged, published and installed: the platforms, the artifact names, the installer, the releases
majordomus distribution artifact	read only	executable	`just distribution-artifact`	`majordomus_artifact`	The archive name and root directory a target and a tag derive
majordomus distribution build	read only	executable	`just distribution-build`	`majordomus_build`	What this executable is: version, target triple, profile, commit
majordomus distribution matrix	read only	executable	`just distribution-matrix`	—	The release build matrix, as the release workflow reads it
majordomus distribution metadata	read only	executable	`just distribution-metadata`	—	The public metadata one release record publishes, rendered from the record alone
majordomus distribution releases	read only	executable	`just distribution-releases`	`majordomus_releases`	Every recorded release, newest first, and the one an unpinned installation resolves to
majordomus distribution show	read only	executable	`just distribution-show`	`majordomus_distribution`	The model: the install command, where an installation goes, and every declared target
majordomus distribution status	read only	executable	`just distribution-status`	`majordomus_install_status`	Whether the advertised one-line installation works right now, and what is missing when it does not
majordomus distribution targets	read only	executable	`just distribution-targets`	—	Every declared target, one line each, with the artifact name it derives
majordomus distribution validate	read only	executable	`just distribution-validate`	—	Every invariant of the model and of the release records; exit 10 with each violation named
majordomus economics	read only	executable	—	—	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
majordomus economics check	read only	executable	`just economics-check`	`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
majordomus economics explain	read only	executable	`just economics-explain`	`majordomus_economics_explain`	One metric and everything it rests on: formula, class, pairs, runs, exclusions, and how to reproduce it
majordomus economics measure	read only	executable	`just economics-measure`	—	Run a deterministic suite (no model is called) and record its measurement
majordomus economics references	read only	executable	`just economics-references`	—	Prove every task's hidden tests fail on its starting state and pass on its reference solution. No model is called
majordomus economics run	read only	executable	`just economics-run`	—	Run a live suite: real harness sessions with and without Majordomus, recorded as raw usage and gate verdicts. Spends provider usage
majordomus economics runs	read only	executable	`just economics-runs`	`majordomus_economics_runs`	The recorded runs every metric is computed from
majordomus economics summary	read only	executable	`just economics-summary`	`majordomus_economics`	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
majordomus entity	read only	executable	—	—	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
majordomus entity kinds	read only	executable	`just entity-kinds`	`majordomus_kinds`	Every kind of the layer, the route of its index, and every route collision there is
majordomus entity show	read only	executable	`just entity-show`	`majordomus_entity`	One entity: its route, what it references, what references it, where it is served
majordomus env	read only	executable	`just 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
majordomus env banner	read only	executable	`just 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
majordomus env enter	read only	executable	`just 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
majordomus env explain	read only	executable	`just 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
majordomus env export	read only	executable	`just env-export`	—	The variable assignments a shell in this repository benefits from, for `eval`. Assignments only: no command, no side effect
majordomus env preflight	read only	executable	`just 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
majordomus env status	read only	executable	`just env-status`	—	The whole snapshot, resolved in full: what the layer holds is counted, and the cache the banner reads is written
majordomus evidence	read only	executable	—	—	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
majordomus evidence claim	read only	executable	`just evidence-claim`	`majordomus_evidence_claim`	One claim: its proof state, the execution behind it, and how to reproduce it
majordomus evidence proves	read only	executable	`just evidence-proves`	`majordomus_evidence_test`	One test: its latest execution and every claim it proves
majordomus evidence show	read only	executable	`just evidence-show`	`majordomus_evidence`	Every claim against the evidence recorded for it
majordomus evidence stamp	read only	executable	`just evidence-stamp`	—	Measure the checkout as a run left it, for `record --provenance`
majordomus executions	read only	executable	`just executions`	—	The executions of the server serving this repository: what has run, what is running, and what each one said
majordomus executions events	read only	executable	`just executions-events`	`majordomus_execution_events`	One execution's retained events, oldest first
majordomus executions list	read only	executable	`just executions-list`	`majordomus_executions`	Every execution the server remembers, newest first
majordomus executions protocol	read only	executable	`just executions-protocol`	`majordomus_execution_protocol`	The live channel's contract: where it is, what it writes, and the schema of each message
majordomus executions show	read only	executable	`just executions-show`	`majordomus_execution`	One execution in full: its state, its steps, its diagnostics and what it produced
majordomus guard	read only	executable	—	—	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
majordomus guard hook	read only	executable	`just 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
majordomus intent	read only	executable	—	—	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
majordomus intent binding	read only	executable	`just intent-binding`	`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
majordomus intent coverage	read only	executable	`just intent-coverage`	`majordomus_intent_coverage`	Which work carries which criterion, and the reason every issue exists
majordomus intent explain	read only	executable	`just intent-explain`	`majordomus_intent_explain`	Why an intent stands where it stands: its stage, each criterion, the work realising it
majordomus intent list	read only	executable	`just intent-list`	`majordomus_intents`	Every intent, with the stage derived from its milestones and its evidence
majordomus intent preflight	read only	executable	`just intent-preflight`	`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
majordomus intent realization	read only	executable	`just intent-realization`	`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
majordomus intent show	read only	executable	`just intent-show`	`majordomus_intent_record`	One intent in full: each milestone's derived status and each criterion's evidence state
majordomus intent validate	read only	executable	`just intent-validate`	`majordomus_intent_validate`	Every finding over the intents; exit 10 when any is a failure
majordomus knowledge	read only	executable	—	—	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
majordomus knowledge candidates	read only	executable	`just knowledge-candidates`	`majordomus_knowledge_candidates`	The candidate records awaiting review, with the branch of the episode each came from and how long each has waited
majordomus knowledge record	read only	executable	`just knowledge-record`	`majordomus_knowledge_record`	One knowledge record by id: its front matter, and every reference it names resolved against the index, the ledger and git
majordomus knowledge status	read only	executable	`just knowledge-status`	`majordomus_knowledge_status`	Whether the deriver is still writing: the last derivation, the newest closed episode, and the stopped-writer judgement against session.freshness
majordomus mcp	read only	executable	`just mcp`	—	Serve the repository's AI layer to an MCP client over stdio
majordomus mesh	read only	executable	—	—	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
majordomus mesh claim	read only	executable	`just 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
majordomus mesh doctor	read only	executable	`just mesh-doctor`	`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
majordomus mesh events	read only	executable	`just mesh-events`	—	The cooperation journal's events after a Lamport stamp, in Lamport order
majordomus mesh firewall	read only	executable	`just mesh-firewall`	`majordomus_mesh_firewall`	What the host firewall must admit for the declared mesh and whether it does; `apply` admits it, as root
majordomus mesh handover	read only	executable	—	—	Publish a handover of this checkout to the mesh, or consume one another runtime published
majordomus mesh handover consume	read only	executable	`just mesh-handover-consume`	—	Consume a handover another runtime published, writing it as a local record `handover --resolve` finds
majordomus mesh handover publish	read only	executable	`just mesh-handover-publish`	—	Publish this checkout's newest handover record (or the one named) to every linked runtime
majordomus mesh identity	read only	executable	`just mesh-identity`	`majordomus_mesh_identity`	This machine's node identity, public half only; absent is an answer, not an error
majordomus mesh nodes	read only	executable	`just mesh-nodes`	—	Every node the running server has observed, deduplicated by node identity, with trust, presence, endpoints and provenance
majordomus mesh peer	read only	executable	`just mesh-peer`	—	One runtime: its machine, liveness, link, sessions and claims; exits 10 when it is not known here
majordomus mesh peers	read only	executable	`just 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
majordomus mesh release	read only	executable	`just mesh-release`	—	Release a claim this server's current run holds
majordomus mesh review	read only	executable	—	—	Ask the mesh for a review, or answer a request
majordomus mesh review answer	read only	executable	`just mesh-review-answer`	—	Answer a review request
majordomus mesh review request	read only	executable	`just mesh-review-request`	—	Ask for a review of a branch, commit or pull request
majordomus mesh review withdraw	read only	executable	`just mesh-review-withdraw`	—	Withdraw a review request this runtime asked for, with its result
majordomus mesh session	read only	executable	—	—	Open, update or close a session on the mesh
majordomus mesh session close	read only	executable	`just mesh-session-close`	—	Close a session; its claims end with it on every linked runtime
majordomus mesh session open	read only	executable	`just mesh-session-open`	—	Open or update a session: what it is, what it does, where
majordomus mesh state	read only	executable	`just mesh-state`	—	The state every linked runtime converges on, summarised with its digest; --full for every session, claim, handover and review
majordomus mesh status	read only	executable	`just 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
majordomus mesh verify	read only	executable	`just mesh-verify`	—	Prove cooperation now: local health, a live round with every peer this server dials, and convergence; exits 10 when a check fails
majordomus models	read only	executable	—	—	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
majordomus models list	read only	executable	`just models-list`	`majordomus_models`	Every declared vendor and model, optionally narrowed; the order is the declaration's, which is routing's preference order
majordomus models route	read only	executable	`just models-route`	`majordomus_models_route`	Which model a stated need selects, the fallback chain behind it, and why every excluded model fell out
majordomus monitor	read only	executable	`just 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
majordomus offload	read only	executable	—	—	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
majordomus offload derive	read only	executable	`just 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
majordomus offload hosts	read only	executable	`just 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
majordomus offload probe	read only	executable	`just 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
majordomus pack	read only	executable	—	—	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
majordomus pack build	read only	executable	`just 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
majordomus pack plan	read only	executable	`just pack-plan`	`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
majordomus pack verify	read only	executable	`just pack-verify`	`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
majordomus product	read only	executable	`just 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
majordomus product domains	read only	executable	`just product-domains`	`majordomus_product_domains`	The domains of the product, each with the stable features that name it and what they add up to
majordomus product list	read only	executable	`just product-list`	`majordomus_features`	Every feature, narrowed by any filter, with the surfaces derived for each
majordomus product matrix	read only	executable	`just product-matrix`	`majordomus_product_matrix`	Every feature against every interface, and every module, command and kind against the features that name it
majordomus product providers	read only	executable	`just product-providers`	`majordomus_providers`	Every provider the tool has an adapter for, with what this repository does with it
majordomus product show	read only	executable	`just product-show`	`majordomus_feature`	One feature in full: what it is made of, resolved, and everything derived from that
majordomus product validate	read only	executable	`just product-validate`	`majordomus_product_validate`	Every finding over the model; exit 10 when any is an error
majordomus prs	read only	executable	`just 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)
majordomus prs brief	read only	executable	`just 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
majordomus prs cleanup	read only	executable	`just prs-cleanup`	—	Close the pull requests whose work is provably on master already; without `--apply` it only lists them
majordomus prs drain	read only	executable	`just prs-drain`	—	Merge the next ready pull request, verify it landed, observe again, and repeat — at most `--max` merges; `--dry-run` decides without acting
majordomus prs events	read only	executable	`just prs-events`	`majordomus_integration_events`	The audit trail: every selection, merge, refusal, stale decision and closure this checkout's executor recorded
majordomus prs explain	read only	executable	`just prs-explain`	`majordomus_pull_request_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
majordomus prs plan	read only	executable	`just 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
majordomus prs prove-dry-run	read only	executable	`just prs-prove-dry-run`	`majordomus_pull_requests_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
majordomus prs refresh	read only	executable	`just prs-refresh`	—	Observe the forge now (the GitHub CLI and one `git fetch`) and record the observation; the only read that reaches the network
majordomus prs repair	read only	executable	`just 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
majordomus prs status	read only	executable	`just prs-status`	`majordomus_pull_requests`	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
majordomus prs trains	read only	executable	`just prs-trains`	`majordomus_pull_request_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
majordomus quality	read only	executable	—	—	What this executable's own public surface is held to: documentation, executable examples, module coverage, and every command accounted for against the capability registry
majordomus quality report	read only	executable	`just quality-report`	`majordomus_quality`	Measure the crate and report every finding, with the rule it breaks and what to do about it
majordomus quality rustdoc	read only	executable	`just quality-rustdoc`	`majordomus_quality_rustdoc`	Judge the crate's rustdoc tree against the crate: every page present, HEAD's, nothing broken or leaked
majordomus reasoning	read only	executable	—	—	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
majordomus reasoning advisors	read only	executable	`just reasoning-advisors`	`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
majordomus reasoning check	read only	executable	`just reasoning-check`	`majordomus_reasoning_check`	Check that reasoning stays provider-independent and that every record is consistent; exit 10 on a finding
majordomus reasoning explain	read only	executable	`just reasoning-explain`	`majordomus_reasoning_explain`	One record with the whole chain of its assessment: why a decision was made
majordomus reasoning plan	read only	executable	`just reasoning-plan`	`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
majordomus reasoning status	read only	executable	`just reasoning-status`	`majordomus_reasoning`	The reasoning state of the open task — assessments, consultations, disagreements, conclusions, the timeline — and the report a handover carries
majordomus release	read only	executable	`just 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
majordomus release analyze	read only	executable	`just release-analyze`	—	What the public contract did since the last release, and the smallest version this tree may therefore declare
majordomus release changelog	read only	executable	`just 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
majordomus release next	read only	executable	`just 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)
majordomus release version	read only	executable	`just 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
majordomus rules	read only	executable	—	—	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
majordomus rules proves	read only	executable	`just rules-proves`	`majordomus_rule_proves`	One test: every rule it proves, and the rules that would be left with none
majordomus rules report	read only	executable	`just rules-report`	`majordomus_rules`	Every rule against the proof there is for it
majordomus rules show	read only	executable	`just rules-show`	`majordomus_rule`	One rule: what proves it, what it depends on, and what is missing
majordomus scope	read only	executable	`just scope`	`majordomus_scope`	The repository scope: what a worker reads and what it never reads; with paths, whether each is in or out and why
majordomus serve	read only	executable	`just serve`	—	Serve the same capabilities over HTTP on the loopback interface, with the home page, /openapi.json, /swagger and the documentation under /docs/
majordomus serve ensure	read only	executable	`just 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
majordomus serve status	read only	executable	`just serve-status`	—	Where this checkout's server stands — absent, starting, ready, outdated or stale — and every server of the repository
majordomus serve stop	read only	executable	`just 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
majordomus served	read only	executable	—	—	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
majordomus served show	read only	executable	`just served-show`	`majordomus_served`	Each deployment's newest record, re-judged against a commit
majordomus shell	read only	executable	—	—	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
majordomus shell check	read only	executable	`just shell-check`	`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
majordomus skills	read only	executable	—	—	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
majordomus skills explain	read only	executable	`just skills-explain`	`majordomus_skill_explain`	One skill in full: each naming test and its evidence, its page, its gates, every invocation
majordomus skills status	read only	executable	`just skills-status`	`majordomus_skills`	Every skill with its derived standing: tested, documented, enforced, used
majordomus skills verify	read only	executable	`just skills-verify`	`majordomus_skills_verify`	Every finding over the skills; exit 10 when any is a failure
majordomus web	read only	executable	`just web`	—	The repository's web surfaces: what is exposed, where it is mounted, what produced it, and whether the topology is valid
majordomus web compose	read only	executable	`just web-compose`	—	Compose every published surface into one publishable tree
majordomus web explain	read only	executable	`just web-explain`	—	Why each surface exists and where each of its values came from
majordomus web list	read only	executable	`just web-list`	—	Every discovered surface: id, kind, mount, producer
majordomus web manifest	read only	executable	`just web-manifest`	—	Write the resolved topology to the generated manifest
majordomus web report	read only	executable	—	—	Render a generated report into its own surface under the generated web root
majordomus web report benchmarks	read only	executable	`just web-report-benchmarks`	—	The benchmark run: a results document, or the accepted baseline
majordomus web report cockpit-snapshot	read only	executable	`just web-report-cockpit-snapshot`	—	The Cockpit itself, read once at this commit and written as static pages a publication carries at /cockpit (ADR 0147)
majordomus web report tests	read only	executable	`just web-report-tests`	—	The test run: the behavioural cases' report, and the crate's own totals
majordomus web report ui	read only	executable	`just web-report-ui`	—	The UI conformance audit, rendered as a section of the test surface (/tests/ui)
majordomus web report ui-snapshot	read only	executable	`just web-report-ui-snapshot`	—	The UI itself, read once at this commit and written as static pages a publication carries at /ui (ADR 0141)
majordomus web validate	read only	executable	`just web-validate`	—	Check the topology's invariants; exit 10 on any error finding
majordomus why	read only	executable	`just 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
majordomus why areas	read only	executable	`just why-areas`	`majordomus_why_areas`	Every operational area, with the moments that fall under it
majordomus why audiences	read only	executable	`just why-audiences`	`majordomus_why_audiences`	Every audience, with the moments that name it
majordomus why diagnose	read only	executable	`just why-diagnose`	`majordomus_why_diagnose`	What the symptoms you recognise imply: the areas they weigh towards and the mechanisms that answer them
majordomus why list	read only	executable	`just why-list`	`majordomus_why`	Every operational moment, narrowed by any facet the catalogue reports
majordomus why show	read only	executable	`just why-show`	`majordomus_why_moment`	One moment in full, with every relation derived from its metadata
majordomus why validate	read only	executable	`just why-validate`	`majordomus_why_validate`	Every finding over the catalogue; exit 10 when any is an error
majordomus worktree	read only	executable	`just 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
majordomus worktree branches	read only	executable	`just worktree-branches`	—	Every local branch, one per line, for a shell completion that wants the live set
majordomus worktree cleanup	read only	executable	`just worktree-cleanup`	—	The branches merged into the trunk whose worktree is clean or absent: what could be removed. Removes nothing without --remove
majordomus worktree doctor	read only	executable	`just worktree-doctor`	—	Every diagnostic of the topology, errors, warnings and facts, each with its code and remedy; exit 10 when there is an error
majordomus worktree guard	read only	executable	`just 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
majordomus worktree inspect	read only	executable	`just worktree-inspect`	`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
majordomus worktree list	read only	executable	`just worktree-list`	—	Every registered worktree with its standing, one line each; exit 10 when the topology has an error
majordomus worktree migrate	read only	executable	`just worktree-migrate`	`majordomus_worktree_migration_plan`	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
majordomus worktree path	read only	executable	`just 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
majordomus worktree root	read only	executable	`just worktree-root`	—	Print the container every linked worktree belongs under, and nothing else: `cd "$(majordomus worktree root)"`
majordomus worktree status	read only	executable	`just worktree-status`	`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
majordomus worktree topology	read only	executable	`just worktree-topology`	`majordomus_worktrees`	The whole topology: repository, container, trunk, every worktree, every branch without a worktree, every diagnostic; exit 10 when it has an error
majordomus worktree uncommitted	read only	executable	`just worktree-uncommitted`	`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
majordomus worktree validate	read only	executable	`just worktree-validate`	—	Every error of the topology, and nothing else; exit 10 when there is one
majordomus check	read only	tool	`just check`	—	Is the current task still consistent with its policy, its scope and this checkout?
majordomus context	read only	tool	`just context`	—	What the next worker needs to know now, in authority order and within a budget.
majordomus doctor	read only	tool	`just doctor`	—	It checks governance only: is Majordomus itself healthy, and is every enforcement it declares actually wired here?
majordomus doctrine	read only	tool	`just doctrine`	—	What rules are enforced, by what, and whether each one is actually wired.
majordomus history	read only	tool	`just history`	—	Read the append-only ledger back, filtered by task, event or time.
majordomus prompt	read only	tool	`just prompt`	—	List, show and render the repository's own prompt assets, substituting known tokens only.
majordomus search	read only	tool	`just search`	—	Find a durable record without reading all of them, in authority order.
majordomus skills	read only	tool	`just skills`	—	The repository's skills — provider-neutral procedures under the skills section — listed, shown and checked from the one catalogue every surface reads.
majordomus version	read only	tool	`just version`	—	Print the version, without needing a repository or an installation.
majordomus watch	read only	tool	`just watch`	—	What has drifted since the last update — policy, projections, state, retention.