Oko
Oko/Docs

Command reference

oko reflection observe

Retains an observed infrastructure failure before model assessment, even when Brama cannot answer.

Invocation#

Command
oko reflection observe --input FILE|- [--json]

Inputs and options#

  • FILE contains a JSON object with nonempty string fields product, machine, service, operation, cause and state. Use --input - to read that object from standard input. Unknown fields and wrong field types refuse before writing.
  • For example, after a directory refusal, supply the reported machine and service, the failed directory operation, its actual cause and observed state; do not invent a host or a successful probe.

Output and state effect#

  • Returns the persisted queue entry with source and pendingCause. An exclusive register lock deduplicates product, machine, service and operation; changed cause or state replaces the observation and invalidates its reading while preserving a defect link. Identical evidence preserves the prior verdict or pending cause.
  • Intake makes no model request, creates no Transcript Lake message and does not admit a repair or claim a recorded defect. process assesses the infrastructure evidence separately from operator messages, then uses ordinary defect admission. list --pending exposes the same observation.
  • Oko Desktop → Defects → Infrastructure observation submits the same typed operation. Evidence reflection distinguishes observed machine, service, operation, cause and state from the later assessed cause, proposed repair and completion criterion; it also shows pending assessment and any admitted defect.
  • The reflection delivery check uses the same intake for a reported stalled delivery path. Existing defects do not suppress new observed state, and an unreadable defect register cannot prevent intake. Defect lookup and repair admission remain part of subsequent assessment.
  • The registered release journey reflection-observations runs the real CLI and an isolated native service with their own HOME and registers. It retains source revision, source patch, binary digest, invocations, exit statuses and output under the build directory; it covers file and stdin intake, concurrent deduplication, changed observed filesystem errors, shared CLI/native identity and refusal without mutation. The native case obtains its protocol version from the running service and inspects the same persisted register through both interfaces.

Refusals and safe exits#

  • A missing --input is a usage refusal. Unreadable input names the file or stdin and the I/O cause; malformed JSON names its decoding cause. Empty fields name observation FIELD. An unreadable or unwritable register reports its actual path and cause; no receipt is returned for a failed write.

CLI reference#