Synopsis
Description
pome checks reads the closed set of typed checks a digital twin declares. Those
checks are the vocabulary a [code] criterion is graded by.
Read this page before you write a criterion by hand. 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. pome checks add writes criteria that cannot fail to
bind, and pome checks lint catches the ones that already do.
pome checks [twin]
List the checks a twin declares: the check id, the English template it renders,
what the predicate compares, the substrate it needs, and every parameter with a
valid example.
Arguments
Options
Examples
pome checks add
Append one [code] criterion to a task file. You pick the check and supply its
parameters; Pome writes the criterion text. In an interactive terminal, leaving
--check off opens a numbered picker that prompts for each parameter; in a
script or CI, both flags are required.
Arguments
Options
Plus the global flags —
--api-url, --artifacts-dir, and -V, --version.
An unknown --check is refused with the checks available for the twins the
task file itself declares, so the suggestion is about the task in front of you.
Examples
pome checks lint
Report [code] criteria that bind no declared check, and so are never graded.
Run it over a task library before you spend runs on it.
Arguments
Examples
Exit status
Exit
1 from pome checks lint is what makes it usable as a CI gate over a task
library.
See also
pome compile-seeds— compile a task’s seed prose into a sidecar.pome run— run a task once its criteria bind.- Write a task — where criteria sit in the task format.