Oko/Docs

Command reference

oko tasks check

Records whether one acceptance check of a task’s contract is met, with the evidence that shows it, so a reader sees which check holds instead of one verdict over the whole task.

Invocation#

Command
oko tasks check (<session> <number> | <task-id>) <check> (--met | --unmet) --evidence TEXT --by (operator | <session>)

Inputs and options#

  • The task as oko tasks state takes it; <check> is the check’s number as listings print it (“accepted when #1 …”); --met or --unmet gives the result; --evidence names what shows it — a commit and test, a report path, an observed state; --by names who records it.

Output and state effect#

  • Writes the result into the contract, replacing an earlier result for the same check, and prints the contract. Listings, show and Oko Desktop’s Tasks screen print each check as “accepted when #n [met|not met|unchecked]: <check> — <evidence>”, and the handover lists every check not yet met as “Kryterium #n niespelnione: …”. Giving new --acceptance checks clears every result, because a result answers the check it was recorded against. A result is a change to the contract: it withdraws the operator’s confirmation when a session records it, and it appears in the contract history.
  • When every acceptance check is met with nonempty evidence and the task has no oko tasks evidence row, the report gives the task `proof.checks` (the met results, recorded by whoever met the newest check, at that time), and listings print “every acceptance check met (N), the newest recorded by <who>”. That is evidence as a commit or report is: the judge still decides the task, and a verify or control pass the judge cannot answer writes its outage on it, so Tama’s block-stop-with-open-work counts it as waiting for the judge, not as open work. An unmet or unanswered check gives no proof.

Refusals and safe exits#

  • Refuses without a task, a check number, one of --met and --unmet, a nonempty --evidence and --by, and prints the usage; a number the contract does not hold refuses with “task <id> has no acceptance check #<n>; it has <count>”.

CLI reference#