majordomus product
The product: what this repository's tool does for a person, as the features under the layer declare it, with every surface, count and moment derived; the matrix of features against interfaces; the providers; and the model's own validation
majordomus product
Usage
majordomus product [OPTIONS] [COMMAND]Commands
- majordomus product list Every feature, narrowed by any filter, with the surfaces derived for each
- majordomus product show One feature in full: what it is made of, resolved, and everything derived from that
- majordomus product matrix Every feature against every interface, and every module, command and kind against the features that name it
- majordomus product providers Every provider the tool has an adapter for, with what this repository does with it
- majordomus product validate Every finding over the model; 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)
|
| --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) |
| --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
-
What the product does, as the layer declares it
`product` with nothing after it lists the features, because listing is what a person wants when they ask what the tool is for. Every column is derived: the surfaces a feature is exposed through come from the modules, commands and kinds it names, never from the file.
$ majordomus productVerified by the example tests: exits 0; prints SLUG, SURFACES, feature(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 product --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.