majordomus why audiences

Every audience, with the moments that name it

Usage

majordomus why audiences [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
--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

Who recognises what, with the counts derived

Each audience with how many public moments name it. The number is computed from the moments; an audience's own file never lists one.
```
$ majordomus why audiences
```
What it asserts: exits 0; prints SLUG, TITLE.
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 why audiences --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.