majordomus why list

Every operational moment, narrowed by any facet the catalogue reports

Usage

majordomus why list [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) `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
--audience	<AUDIENCE>	—	Only moments this audience recognises (accepted by every subcommand)
--area	<AREA>	—	Only moments in this operational area (accepted by every subcommand)
--tag	<TAG>	—	Only moments carrying this tag (accepted by every subcommand)
--severity	<SEVERITY>	—	Only moments of this severity (accepted by every subcommand)
--frequency	<FREQUENCY>	—	Only moments of this frequency (accepted by every subcommand)
--lifecycle	<LIFECYCLE>	—	Only moments at this stage of work (accepted by every subcommand)
--capability	<CAPABILITY>	—	Only moments naming this capability of the executable (accepted by every subcommand)
--names-command	<NAMES_COMMAND>	—	Only moments naming this command (accepted by every subcommand)
--featured	flag	—	Only the moments the homepage features (accepted by every subcommand)
--all	flag	—	Include drafts and deprecated moments, not only the public ones (accepted by every subcommand)
-q, --query	<QUERY>	—	Case-insensitive text over identities, titles, hooks, summaries, tags, aliases, signals, examples and bodies (accepted by every subcommand)

Examples

Every public moment, in presentation order

Drafts are excluded unless `--all` is given. The facets a listing may be narrowed by are the ones the catalogue itself reports, so an audience or an area added as a file is a filter without anything being registered.
```
$ majordomus why list
```
Verified by the example tests: exits 0; prints SLUG.
Only what one audience recognises

Membership is declared by each moment and never listed in the audience's own file, so this answer is derived. An audience the catalogue does not have is an invalid input naming the ones it does, not an empty answer.
```
$ majordomus why list --audience fixture-team
```
Verified by the example tests: exits 0; prints SLUG.
The same, as the shape the API and MCP answer with

One domain model behind every projection: this document is what `GET /api/v1/why` returns and what the `majordomus_why` tool answers, including the derived facets and the catalogue's fingerprint.
```
$ majordomus why list --format json
```
Verified by the example tests: exits 0; prints one JSON document carrying /counts/moments, /facets/audiences, /fingerprint.

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