Oko
Oko/Docs

Command reference

oko work cap

Answers which products hold as many open defects as the operator's cap (work/cap/cap.json, the number he named with his words), so their sessions resolve defects before anything else. In `oko work next|queue` every task of such a product (of the whole register, for a task outside a product) ranks after every defect and every other task, carries `capped: <open defects>` and its reason starts `held: <product> holds <n> open defect(s), at or past the operator's cap of <cap>, so its defects are resolved before this task`.

Invocation#

Command
oko work cap [--json]

Inputs and options#

  • The open defects of the register whose completion measure has not passed, counted per product.

Output and state effect#

  • Prints `<product> <n> open defect(s), cap <cap>: its tasks wait until its defects are resolved` per product at or past the cap, the most open first, then the whole register when it is; with none, `no product holds <cap> open defects; no task is held behind the cap`. --json prints `{cap, reached: [{product, open, cap}]}`, product null for the whole register.

Refusals and safe exits#

  • Any flag but --json is refused by name (exit 2); an unreadable defect register refuses naming it.

CLI reference#