Oko
Oko/Docs

Command reference

oko routines create

Stores a typed Oko operation in Stado's durable schedule registry.

Invocation#

Command
oko routines create --id UUID --name NAME --action ACTION --cron EXPR --tz IANA --host HOST [--query TEXT --limit N] [--days N] [--enabled]

Inputs and options#

  • Retain the caller-generated UUID before submitting. Cron has five fields; timezone is an IANA identifier.
  • ACTION is one of context, autonomy, control, telemetry, index, reflection, supervision, suggestions, rules, sweep, released, recurrences, linked, requirements, obligations and failures.
  • Choose an existing local host; Oko checks its registry kind before submitting. Context optionally takes a query and requires --limit; control hands each owing session its work, telemetry publishes work snapshots and requires --days, reflection reads Transcript Lake and queues unavailable model judgments, and supervision settles waits and executor turns before acting on measured capacity. Sweep reads changed transcripts, released reconciles published repairs, recurrences runs every repaired class's completion probe at the head of its checkout (`oko defects recurrences check`), linked keeps every pushed commit naming an unrepaired open defect on it as a candidate (`oko defects linked`), requirements reads every transcript that grew for what the operator requires (`oko requirements read`), obligations runs one reminder pass over the obligations register (`oko obligations remind`), and failures runs one pass of the call-failure intake (`oko failures scan`).

Output and state effect#

  • Creates a paused schedule unless --enabled is explicit. Stado owns time, placement and overlap prevention; Oko creates no second timer.
  • An uncertain creation is inspected with show sch-<UUID without hyphens>; do not invent a replacement UUID.
  • A rules occurrence remembers correction identities and visible content for lessons, and counts for other proposals. Its receipt lists delivered and pending proposal IDs, successful channels, channel failures and unreadable digest sources. Partial notification delivery records only the proposals that reached a channel.

Refusals and safe exits#

  • An unknown host carries Stado's registry refusal; a registered nonlocal host is refused with its observed kind. Duplicate identity or invalid cron/timezone or definition fail without creating replacement work.
  • Only context, autonomy, control, telemetry, index, reflection, supervision, suggestions, rules, sweep, released, recurrences, linked, requirements, obligations and failures are supported. Payment instructions, arbitrary commands and a query or limit on any action but context are refused; a context routine without its positive limit is refused, as is a stored context routine written before limits were stated.
  • A rules occurrence in which no channel took a new proposal fails with each channel's reason. Invalid delivery history or a Tama digest without proposal and unreadable arrays refuses the read rather than claiming there is no work.

CLI reference#