tama commands judge

The review a write that declares a new command waits for. block-one-off-commands reads every command a written file declares — by the language's structure, whoever declared it — and decides the write from the verdicts already kept for that file path, command name and declaration. A command without a kept verdict is never let through: the hook publishes a review request and refuses the write at once, naming tama commands judge <request>. No judge runs inside the hook. This command is that review, run in the foreground: it asks the judge whether each command is a general primitive or a one-off workflow, keeps the verdicts and prints them, and the same write is afterwards decided by them alone.

#Invocation

tama commands judge <request>

• <request> is the hexadecimal id the hook's refusal names: the SHA-256 of the file path, name and declaration of every command the write declares. The request itself is requests/<request>.json under the verdicts directory ({"file_path", "commands": [[name, declaration], …]}), published atomically by the refusing hook.
• The verdicts directory is TAMA_COMMAND_VERDICTS_DIR when it is set and not empty, otherwise command-verdicts under the Tama state root. Verdicts are kept in verdicts.json there, under a lock, merged with the ones already kept.
• When every command of the request already has a kept verdict, those are printed and no judge is asked.

#Output and refusals

• One line per command: <name>: PASS, or <name>: BLOCK: <the judge's reason>. Exit 0 when every command passed, 1 when one is blocked.
• A review that cannot finish exits 1 with block-one-off-commands: tama commands judge <request>: <cause> on stderr, and the same line is appended to judge.log in the verdicts directory; a log that cannot be written is named too (block-one-off-commands: cannot retain the review failure in <path>: <cause>). The causes are each named: request <request> is already owned by a running review; read that operation's result when another tama commands judge holds the request's lock, no request <request> in <directory>: <cause>, <path> is not a request: <cause>, and the judge's own failure when the model service does not answer.
• No verb, another verb or a second argument is a usage refusal: the commands lines of tama --help on stderr, exit 2.
• On a machine that declared no model (tama model-provider set --none) the hook keeps no request and names no review; it admits the commands of a file with a recorded justification (tama justify record --kind file) and refuses each command of a file without one.

#Quickstart

A write adding a status verb to a CLI is refused, reviewed, and written again:

$ # the write is refused:
block-one-off-commands: BLOCKED: src/cli/ci/mod.rs would declare command(s) status that the judge has not read yet. Run `tama commands judge 8dc6…` …
$ tama commands judge 8dc6…
status: PASS
$ # the same write now passes on the kept verdict

#Tests

tests/one-off-commands/kept_verdicts.rs runs the built hook the way the harness does and the built tama commands judge the way the refusal names it, against the machine's real model route, with the verdicts in a directory of its own (TAMA_COMMAND_VERDICTS_DIR): a write adding a subcommand nobody judged is refused naming the request, the review answers and keeps the verdict, and the same write is then decided by that verdict alone.

Return to the complete CLI tree.