Oko/Docs

Command reference

oko defects incidents record

Keeps one incident: what went wrong, in which session and product, what it cost and the defect it forced open. An incident belongs here, not in an AGENTS.md or a product's public pages, where it publishes the operator's internal history and outlives its cause; Tama refuses one in product code and public pages.

Invocation#

Command
oko defects incidents record --session S --happened TEXT --harm TEXT [--product P] [--defect D] [--at TIME] [--json]

Inputs and options#

  • --session is the session it happened in; --happened says what happened and --harm what it cost (time, work, the operator's attention, a release), each required.
  • --product names the product it struck; without it the incident is the fleet's. --defect names the defect it forced open, in full or by its start, resolved through the defect register. --at is when it happened as an ISO 8601 time; without it, now.
  • The register is OKO_INCIDENT_REGISTER, else incidents.json in Oko's state directory, written readable by its owner only and published nowhere.

Output and state effect#

  • Prints `recorded incident <short id> <time> <product or fleet> <session> <what happened> (defect <short id>)`; --json prints the incident. The same session, words and time recorded again answers the incident already kept and writes nothing.

Refusals and safe exits#

  • A missing --session, --happened or --harm, a --defect no defect answers to, a --at that is no ISO 8601 time and any other flag are refused by name.

CLI reference#