# qctl
Rust policy CLI for in-repo `tasks.yaml` work queues.
- Operator contract: `qctl instructions` and `skills/qctl/SKILL.md`.
- This repo's queue is [`tasks.yaml`](tasks.yaml) (`QCTL-###`).
- `horizon` maps research/evaluations that are not startable. Do not put
them on `queue` and do not set `active` to a horizon id.
- Schema is types + schemars (QCTL-001). Generated JSON lives only here.
Consumers pin a `$schema` URL and run `qctl check`. `schema_version` is 3:
a ledger declares its `style`, and `completed` is a moment in the zone that
block names. A rule that both `check` and the verbs must agree on is stated
once, as a `#[garde(...)]` attribute — schemars reads those, so a second
`#[schemars(...)]` copy is drift waiting to happen.
- Mutations rewrite only the lines they change (QCTL-002). Each scenario in
`tests/fixtures/mutations/` records what the verb wrote as one marked-up
file: `-` removed, `+` added. When a change to that output is intended,
`mise run snapshots` shows it scenario by scenario and accepts it.
- `qctl fmt` applies the declared style; `qctl fmt --check` is the hook form.
New style options are additive: a field with a default equal to today's
behaviour is a minor change, not a migration.
- Served files — `tasks/q/q` and `examples/mise.toml` — are rendered from
`.verctl/templates/`, and README's `?ref=` and install line are declared as
`[patterns]` in `verctl.toml` (QCTL-009). Edit the template or the pattern,
never the rendered file; the Version PR rewrites all five sites onto the
commit the tag names. A template git does not track renders nowhere.