majordomus economics tasks

Each task's wall time, refusals and episodes, from every checkout's ledger; the fields nothing observes yet are named as not observed

Usage

majordomus economics tasks [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 `text` — Lines for a person `json` — One JSON document, deterministic
--since	<SINCE>	—	Only tasks started at or after this time (YYYY-MM-DDTHH:MM:SSZ)
--until	<UNTIL>	—	Only tasks started before this time (YYYY-MM-DDTHH:MM:SSZ)

Examples

Each task's wall time and episodes

One record per task from every checkout's ledger, with the fields nothing observes yet named as not observed. A repository with no ledger answers no task and lists its checkout as not read.
```
$ majordomus economics tasks --format json
```
What it asserts: exits 0; prints one JSON document carrying /count, /tasks, /ledgers, /unread.
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 tasks --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.