majordomus economics run
Run a live suite: real harness sessions with and without Majordomus, recorded as raw usage and gate verdicts. Spends provider usage
majordomus economics run
Usage
majordomus economics run [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)
|
| --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) |
| --suite | <SUITE> | pilot | The live suite to run |
| --task | <TASKS> | — | Only this task (repeatable) |
| --repetition | <REPETITIONS> | — | Only this repetition (repeatable) |
| --work-dir | <PATH> | — | Where transcripts go; never inside the repository. Workspaces are fresh directories of the system temporary directory, removed when their run ends |
| --harness | <PATH> | claude | The harness executable |
| --parallel | <PARALLEL> | 2 | Runs in flight at once |
| --session-timeout | <SESSION_TIMEOUT> | 1800 | Per-session wall-clock limit, in seconds |
| --force | flag | — | Refused: a recorded run is evidence and is never overwritten; exclude it in the methodology with a reason and record another repetition |
| --dry-run | flag | — | Prepare every workspace and print the harness command; run nothing, spend nothing |
Examples
-
Prepare a live suite without spending anything
Builds every control and treatment workspace and prints the harness command each session would run; nothing is sent to a provider. Refused with exit 12 where no methodology is declared.
$ majordomus economics run --suite pilot --dry-runWhat it asserts: exits 12.
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 economics run --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.