criteria accepts plain strings in English or Chinese. Verified live: "有 test_log" parsed to evidence_present on key test_log; "there must be a changelog" parsed to evidence_present on key changelog; "https://example.com returns 200" parsed to url_status with the expected status.
Parsing guesses the evidence key from your sentence, and that guess can miss. "at least 3 boundary cases" parsed to count_min but looked for a key named boundary, while the evidence key was boundary_cases; the item failed even though three cases existed. Write the exact key name in the sentence, or use the object form, whenever your key is not the obvious noun.
A criterion that is not mechanically checkable comes back with kind: "unverifiable", parsed: false, met: false, and a missing message telling you to switch to the object form. The call also carries ai_diagnostic: {"unparsed": n, "ai": "..."} when anything was left unparsed.
Rule of thumb: plain strings for prose criteria where the key name is obvious, {"text":"...","check":{...}} when a wrong guess would cost you a re-run. A re-run costs 1 credit, so being exact is cheaper than retrying.
All questions · nodcheck · Source: https://nodcheck.com/answers/natural-language-criteria