majordomus why
The operational moments this tool answers: the catalogue, one moment, the audiences and areas, a diagnosis of your own week, and the catalogue's own validation
majordomus why
Usage
majordomus why [OPTIONS] [COMMAND]Commands
- majordomus why list Every operational moment, narrowed by any facet the catalogue reports
- majordomus why show One moment in full, with every relation derived from its metadata
- majordomus why audiences Every audience, with the moments that name it
- majordomus why areas Every operational area, with the moments that fall under it
- majordomus why diagnose What the symptoms you recognise imply: the areas they weigh towards and the mechanisms that answer them
- majordomus why validate Every finding over the catalogue; exit 10 when any is an error
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)
|
| --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)
|
| --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
-
The operational moments this repository holds
`why` with nothing after it lists, because listing is what a person wants when they ask what this section is. The count on the last line is computed from the catalogue; no number anywhere is written down.
$ majordomus whyVerified by the example tests: exits 0; prints SLUG, moment(s).
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 --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.