Development record
claim_type's closed vocabulary (criterion, causal, context) is enforced nowhere. agents/cold-reading-entailment.md instructs it and spc-63 tables it, but validateItems checks non-blank only, capture.validateReadingStrict has no enum, and issueschema declares only the field name, so an entailment payload carrying an arbitrary claim_type lands in the durable record.
issueresolvedminoriss-2608311234540729
claim_type's closed vocabulary (criterion, causal, context) is enforced nowhere. agents/cold-reading-entailment.md instructs it and spc-63 tables it, but validateItems checks non-blank only, capture.validateReadingStrict has no enum, and issueschema declares only the field name, so an entailment payload carrying an arbitrary claim_type lands in the durable record.
Grounds
- pursued: the finding is closed by a test that fails without the change; a later review or mutation run finding the same shape again would show this wrong
Frontmatter
| id | iss-2608311234540729 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2608311234540729-claim-type-s-closed-vocabulary-criterion.md
open on GitHub ↗ · commit history ↗
mentions1
- spc-63The cold-reading output contract: a strict per-position schema, a supply-regime gate, and a staged ingest that leaves evidence or nothing