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

Usage

majordomus reasoning plan [OPTIONS]

Arguments

argument	value	default	description
--materiality	<MATERIALITY>	material	trivial, low, material, high or critical
--confidence	<CONFIDENCE>	medium	low, medium or high
--capabilities	<CAPABILITIES>	—	Advisory capabilities review needs, comma-separated
--repo	<PATH>	—	Start the search for the repository root here (default: the current directory) (accepted by every subcommand)
--discovery	vcs \| filesystem	vcs	How declarative files are enumerated (accepted by every subcommand) `vcs` — Tracked files, through the version-control index (the layer's contract); a layer none of which is tracked is read from the work tree `filesystem` — A walk of the work tree with the same glob semantics; untracked files included
--strict	flag	—	Refuse to proceed when any file of the layer carries an error diagnostic (accepted by every subcommand)
--share	<DIR>	—	The tool distribution's share directory (kinds.yaml, schemas/); default: $MAJORDOMUS_SHARE, then the repository's own share/, then the one beside the executable (accepted by every subcommand)
--format	text \| json	text	`text` for a person, `json` for a machine; both render the same answer (accepted by every subcommand) `text` — Lines for a person `json` — One JSON document, deterministic

Examples

What a material uncertainty calls for

Whether independent review is worth having, how many advisors the mode allows, which available advisors a capability-driven selection asks, and why every other advisor is left out. With no suitable advisor the plan is the structured local review. Nothing is recorded.
```
$ majordomus reasoning plan --materiality material
```
What it asserts: exits 0; prints outcome, budget.
Tested by apps/majordomus-cli/tests/cli_examples.rs, which runs the command against the built executable and asserts what the page states.
A high uncertainty that asks for named capabilities

The selection covers the requested capabilities first, then prefers an advisor reached through a different adapter, then declaration order; every advisor not selected carries its reason. With none available the outcome is the structured local review.
```
$ majordomus reasoning plan --materiality high --capabilities independent_reasoning,code_review
```
What it asserts: exits 0; prints outcome, budget.
Tested by apps/majordomus-cli/tests/cli_examples.rs, which runs the command against the built executable and asserts what the page states.

Where this comes from

Declared once in apps/majordomus-cli/src/cli.rs: clap for the structure, typed Rust metadata beside it for the examples. This page, majordomus reasoning plan --help, docs/generated/cli.md and docs/generated/cli.json are projections of that one declaration.

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