Oko/Docs

Command reference

oko reflection process

Asks Brama to assess queued transcript and infrastructure evidence and assign a shape to every unshaped defect.

Invocation#

Command
oko reflection process [--source ID] [--json]

Inputs and options#

  • The queue persisted by scan, observe or the defect register. --source assesses one exact reflection source; the pass also reconciles gate decisions and superseded rulings.

Output and state effect#

  • Records operator corrections, refusals, frustration, goal divergence and demonstrably ignored supervisor directives with context as defects; other readings remain notes in the queue. Before writing a finding, Brama compares open candidate defects by the failed operation: the same incident receives a contextual note; a distinct occurrence receives a separate defect even if its title is identical. A repeated product-and-shape opens one ready class task assigned to an observed live executor in that product's checkout. Routine retries retain an eligible live owner, adopt a task whose executor stopped, restore readiness when any instance remains open, and reopen it for a new instance; one patched defect cannot close the class. Returns processed sources and pending sources with causes. Ruling-gate reconciliation is included.
  • If a defect write succeeded but retaining its source link or class assignment failed, the next pass rejoins the persisted defect by its Lake session and source marker before comparing candidates or writing another. It keeps the same defect and contextual evidence; several persisted matches refuse by source rather than silently choosing one.
  • Infrastructure evidence is assessed without attributing operator frustration or supervisor misconduct. Defect recording retains its machine, service, failed operation and observed state and still uses normal repair admission. Processing passes serialize separately from intake, so concurrent assessments cannot create competing defects and new observations remain writable while Brama is unavailable.
  • If intake changes evidence during assessment, the older result does not replace the current queue entry. The pass reports that source as pending with evidence changed during judgment, not as processed; the next pass assesses the current evidence.

Refusals and safe exits#

  • A failed resolver or Brama call leaves the affected source pending with its actual cause for the next pass; it never labels text by a word list. Invalid model output, including a categorical supervisor claim without explicit sender identity, an identity outside the offered defects or no evidence-based identity reason, remains pending with the conflicting answer. A completed reading is retained while defect recording refuses, so retry does not reinterpret the operator's message. If no live executor works in the class product checkout, an inventory row lacks alive or cwd evidence, or its owner changes during reconciliation, that source remains pending with the observed cause rather than overwriting the assignment or attributing it to a different product. An unknown --source refuses before processing.

CLI reference#