Command reference
oko routines standing
Declares and enables Oko's continuous work on every installed machine: transcript catalogue and ledger, task control, released-defect reconciliation, reflection, and executor-supervision. The latter runs `oko sessions supervision run` under Stado. The model policy pass also remains in Oko's service, so waits can be settled even when the scheduler itself cannot answer.
Invocation#
oko routines standing [--host HOST] [--json|--plain]Inputs and options#
- --host names the registry host; left out, it is the machine this runs on as `stado registry self --name-only` names it. Installing Oko's service surface runs this with the host the installation placed it on.
- The routines, their cadence and zone are declared in the product (routines/standing/standing.json): each fires every minute and Stado skips an occurrence while the previous one runs, so one run follows the other.
Output and state effect#
- Each routine's identity is derived from its name and host; missing schedules are created, paused ones resumed, changed cadence or zone corrected, and unchanged ones left alone. Superseded model-policy schedules are removed. The executor-supervision receipt includes the policy pass, source-backed capacity decision, starts, retirements and refusals; `oko sessions supervision` and Oko Desktop → Agent sessions show it.
- Oko Desktop runs the same operation from Automation → Recurring work → Ensure standing routines.
Refusals and safe exits#
- `oko routines standing: --host is empty; name a registry host or leave it out`.
- `oko routines standing: which registry host this machine is could not be read: <Stado's answer>; name it with --host`, and `stado registry self named no host for this machine; name it with --host`.
- `oko routines standing: Stado holds sch-<id> for <name> on <host> and it cannot be used: <issue>` for a schedule under that identity whose definition is corrupt or foreign.
- Every refusal of `oko routines create`, `edit` and `resume` for the same host, verbatim: a host that is not a local registry host, or Stado refusing the schedule.