Command reference
oko coverage
Whether every operator message Transcript Lake holds is used: read as a kind, held by a task or a defect, and how far that work has gone. The operator's standing rule is that no message of his in Transcript Lake stands without a task or a defect.
Invocation#
oko coverage [--json]Inputs and options#
- Counts the answer of the whole-Lake linkage audit (`oko rulings unlinked --all`), which reads every session with a Lake user event once. The supervisor routine runs it as its coverage step on every supervision pass (`oko sessions supervision report`).
Output and state effect#
- A message is covered when it was read as a kind and a task of its session's ledger carries it or a defect holds it; each defect holding one is counted by the furthest state it reached (withdrawn, fixed, repaired, claimed, owned, unowned). Prints `<n> operator message(s) in <n> session(s): <n> covered, <n> uncovered, <n> session(s) not read`, then `nothing holds <session> turn <n> (<kind>): <his words>`, `not read as a kind: <session> turn <n>: <his words>` and `session <id> not read: <cause>`. --json prints {source, sessions, messages, covered, uncovered, sessionsUnread, defectStates, unlinked, unread, failed}.
Refusals and safe exits#
- “oko coverage takes only --json; got <word>” and a flag it does not take (exit 2); the audit's own refusals for the rulings, reflection or defect register, and per session the refusal it was not read with, under failed.