Oko
Oko/Docs

Command reference

oko tasks verdict

The judge's verdict, bound to the task as it stands. A not-done or blocked after either counts one more round; done starts the count over; blocked must carry a blocker file that names this task; withdrawn says the task is no work owed and only the operator, the session the message was given in, or a session quoting the operator's own words from its transcript may record it. A verdict ends the task's outage; one --by operator is confirmed on the terminal it runs from.

Invocation#

Command
oko tasks verdict (<session> <number> | <task-id>) --outcome done|not-done|blocked|withdrawn --reason TEXT [--missing TEXT ...] [--blocker PATH] [--operator-said TEXT] --by JUDGE

Inputs and options#

  • The task; --outcome, --reason and --by are required; --missing repeats; --blocker names a blocker JSON file.

Output and state effect#

  • Records the verdict and the round count.
  • Real contract-revision qualification: run `node tests/judge/binding/contract_revision.mjs` from the Oko checkout with OKO_BIN, OKO_TEST_SOURCE_REVISION, OKO_TEST_VERDICT_SOURCE_TASK, OKO_TEST_VERDICT_SOURCE_SESSION, OKO_TEST_BY, OKO_TEST_ACCEPTANCE_CHECK and OKO_TEST_SUCCESS_EXIT selecting a committed candidate and a real isolated fixture. The fixture must already have an independent done verdict, an explicit commit/report proof and a met acceptance check with actual evidence. Do not use operator work.
  • The journey marks the selected check unmet through `tasks check`, reads the stored new contract revision and requires the old verdict to stop applying while the explicit proof stays unchanged. Cleanup restores the original check result and evidence through the CLI, but requires the new revision to remain unjudged rather than revive the historical verdict. Concurrent or unobserved amendments refuse cleanup instead of overwriting them. The retained `.build/judge/contract-revision` report contains source revision, candidate and journey digests, commands, exit statuses, output and cleanup failures. Authoring this journey is not a passing qualification or proof of atomic verdict persistence.

Refusals and safe exits#

  • `oko tasks verdict requires --by <session>`, `oko tasks verdict requires --outcome <text>`, `… requires --reason <text>` (exit 2); `--outcome takes done, not-done, blocked or withdrawn, got <text>`; `<path> cannot be read: <error>`, `<path> is not a blocker: <error>`; `refusing a verdict whose request or checked blocker does not match task #<n>`; `task <id> was given in session <s>; only the operator, that session, or a session quoting the operator's own words from its transcript with --operator-said may withdraw it, not <by>`; `--operator-said is read from session <by>'s transcript, and none is on this machine`; `the operator never wrote "<said>" in session <by> (<n> turns read from <path>); quote his words exactly`; `session <id> gave no task #<n>`; for --by operator, the terminal confirmation refusals of `oko tasks close`.

CLI reference#