Oko/Docs

Command reference

oko reflection signals standing

Declares the signals every installed Oko reads, as `oko install` does, so the improvement loop measures the factory on a machine where nobody declared a signal by hand.

Invocation#

Command
oko reflection signals standing [--json]

Inputs and options#

  • The product's standing signals (reflection/signals/standing.json): rediscovered-causes (rediscovered_causes, level 1), unanswered-frustration (unanswered_frustration, level 0), operator-corrections-repeat (operator_corrections, level 1) and supervisor-interventions-repeat (class_interventions, level 1). Each states where its level comes from: the workshop rule that the second defect of one shape is the finding, or the frustration register's contract that every moment is answered.

Output and state effect#

  • Declares each standing signal not declared yet, with declaredBy `oko standing signal; its level: <source>`, and prints {signals: [{name, change: declared|kept}], declarations}. A signal already declared under a standing name is kept as the machine declared it. Oko Desktop → Defects → Factory signals → Declare standing signals runs the same operation; the native API's reflection domain answers it to standing_signals. Real test: tests/reflection/signals/standing.rs.

Refusals and safe exits#

  • An unreadable or invalid declarations file refuses with its path, as list does; nothing is declared then.

CLI reference#