Oko
Oko/Docs

Command reference

oko rulings decided

Answers what the operator already decided about a subject, in his own words, so a session or supervisor asked 'what did he decide about X' reads it instead of asking him again. The statements are the ones `oko rulings check` compares with: every standing ruling of the rulings register and every rule the task ledger holds from his messages. Brama's model reads them against the subject and names the ones that decide about it; nothing is matched by words.

Invocation#

Command
oko rulings decided --about TEXT [--json]

Inputs and options#

  • --about is the subject, in any words. Example: `oko rulings decided --about 'whether a service may wait on Brama'`.

Output and state effect#

  • Prints each ruling that decides about it as `ruling <id> (<session> #<n>, <time>): <his words>`, each ledger rule as `rule: <the rule as the ledger holds it>`, then `why: <the model's cause>`; `the operator decided nothing about "<subject>" that his rulings or rules hold` when none does. --json prints `{about, rulings: [{ruling, said, session, ordinal, saidAt}], rules, cause}`. Nothing is written when a model read it.
  • Oko Desktop's Rulings screen asks the same reading under What he decided (OkoKit `decided(about:)`, native action `rulings.decided`) and shows the same rulings, rules, cause or refusal.

Refusals and safe exits#

  • `oko rulings decided: no model read what the operator decided about "<subject>" (<cause>); his <n> standing rulings and <m> rules are in <path> for your own model to read` (exit 1) when Brama is held, gives no reading, or what he said could not all be read; the file, `ask-comparisons/decided-<sha256 of the subject>.json` in Oko's folder (`OKO_ASK_COMPARISONS` names another directory), holds `{about, cause, said}`. It is kept and the precondition read by the same code `oko rulings check` uses when Brama gives no comparison.
  • `oko rulings decided: Brama returned an unreadable reading (<error>): <answer>`, `oko rulings decided: Brama cited ruling <id>, which no standing ruling is: <answer>` and `oko rulings decided: Brama cited rule <n>, beyond the ledger's rules: <answer>` (exit 1): a citation that does not match the registers is never printed as his words.
  • `oko rulings decided requires --about <text>` and `oko rulings decided does not take <flags>; it takes --about, --json` (exit 2). Real test: `tests/rulings/decided/journey.rs` in the rulings-barred target.

CLI reference#