majordomus product domains

The domains of the product, each with the stable features that name it and what they add up to

Usage

majordomus product domains [OPTIONS]

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	Output shape (accepted by every subcommand) `text` — Lines for a person `json` — One JSON document, deterministic
--featured	flag	—	Only the features the homepage shows (accepted by every subcommand)
--all	flag	—	Include drafts and deprecated features, not only the stable ones (accepted by every subcommand)
--area	<AREA>	—	Only features serving this operational area of the why catalogue (accepted by every subcommand)
--domain	<DOMAIN>	—	Only features filed under this product domain (accepted by every subcommand)
--module	<MODULE>	—	Only features made of this capability module (accepted by every subcommand)
--names-command	<NAMES_COMMAND>	—	Only features made of this shell command (accepted by every subcommand)
--surface	<SURFACE>	—	Only features exposed through this surface: cli, api, mcp, cockpit or docs (accepted by every subcommand)
-q, --query	<QUERY>	—	Case-insensitive text over identities, titles, headlines, summaries, tags and bodies (accepted by every subcommand)

Examples

The few things the product controls, and the features under each

One block per domain in presentation order: its promise, the failure it answers, and the stable features that name it, with the interfaces, claims and use cases they add up to. A domain lists nothing itself; every member and count is derived from the features.
```
$ majordomus product domains
```
What it asserts: exits 0; prints domain(s).
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 product domains --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.