pome checks reads the closed set of typed checks a digital twin declares. Those
checks are the vocabulary a [code] criterion is graded by.
This matters because a [code] criterion that binds no declared check is never
graded. It does not fall back to the judge — it scores unmatched and leaves the
score’s denominator, so a task can look green while asserting nothing. Use
pome checks add to write criteria that cannot fail to bind, and
pome checks lint to catch the ones that already do.
Do not hand-write
[code] criterion sentences. Pick a declared check and let
Pome render the English.Usage
pome checks [twin]
Lists the checks a digital twin declares: the check id, the English template it
renders, what the predicate actually compares, the substrate it needs, and every
parameter with a valid example.
Arguments
Options
pome checks add
Appends one [code] criterion to a task file. You pick the check and supply its
parameters; Pome writes the criterion text.
Arguments
Options
pome checks lint
Reports [code] criteria that bind no declared check, so are never graded. Run it
over a task library before you spend runs on it.
Arguments
Examples
See also
pome compile-seeds— compile a task’s seed prose into a sidecar.pome run— run a task once its criteria bind.