VER-01: why_human routes model-executable checks to the human ask #212

New issue

Closed

opened 2026-08-18 10:23:54 +00:00 by john · 0 comments

john commented

2026-08-18 10:23:54 +00:00

Owner

Requirement VER-01, seeded at the v3.5.3 close.

verify.md treats the presence of why_human as proof an item is human-only, but cad-verifier-contract/SKILL.md writes that field for every UNCERTAIN truth as well as every human-only check. A truth is UNCERTAIN whenever no probe was observed, which is precisely a check the model can settle by running one.

The result is the exact defect FRI-01 targeted: model-executable checks handed back to the user one at a time. Live payload: _archive-v2.5.0/1/verifier-findings.json:111.

verify.md already states the right predicate in prose (irreversible against real data, or outside the model's reach). The field is not that predicate.

Fix direction: make the bar the test, and read why_human as a reason to be judged rather than an answer.

Requirement VER-01, seeded at the v3.5.3 close. `verify.md` treats the presence of `why_human` as proof an item is human-only, but `cad-verifier-contract/SKILL.md` writes that field for every UNCERTAIN truth as well as every human-only check. A truth is UNCERTAIN whenever no probe was observed, which is precisely a check the model can settle by running one. The result is the exact defect FRI-01 targeted: model-executable checks handed back to the user one at a time. Live payload: `_archive-v2.5.0/1/verifier-findings.json:111`. `verify.md` already states the right predicate in prose (irreversible against real data, or outside the model's reach). The field is not that predicate. **Fix direction:** make the bar the test, and read `why_human` as a reason to be judged rather than an answer.