majordomus reasoning

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

Usage

majordomus reasoning [OPTIONS] <COMMAND>

This command groups the commands below and is not run on its own, so it carries no example.

Commands

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 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 record Record 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 written
majordomus reasoning status The reasoning state of the open task — assessments, consultations, disagreements, conclusions, the timeline — and the report a handover carries
majordomus reasoning explain One record with the whole chain of its assessment: why a decision was made
majordomus reasoning check Check that reasoning stays provider-independent and that every record is consistent; exit 10 on a finding

Arguments

argument	value	default	description
--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

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 --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.