majordomus capabilities
Introspect the capability registry: what exists, where it came from, how it is exposed
majordomus capabilities
Usage
majordomus capabilities [OPTIONS] <COMMAND>This command groups the commands below and is not run on its own, so it carries no example.
Commands
- majordomus capabilities list Every capability, one line each, with its projections
- majordomus capabilities describe One capability by canonical id: schemas, provenance, every projection
- majordomus capabilities schema The canonical input or output JSON Schema of one capability
- majordomus capabilities projections Where each capability is projected, and every claim its surface does not answer
- majordomus capabilities validate Build the registry and every projection; exit 10 with every violation named
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) |
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 capabilities --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.