claim-check
Installation
SKILL.md
Claim Check (Govern)
Purpose
The compliance determination IS the work: a claim ships only with library substantiation for that GTIN and market (#4.1/#4.2); blocked claims never appear in copy, not even softened (#4.3).
When to use
After gap-score, before any copy is drafted.
Inputs
scored.json + config/claim-library.json + target market.
Steps
- Run scripts/claim_check.py --scored scored.json --library claim-library.json --market --out governed.json
- Quote verdicts verbatim. Supplier romance copy is not approval - "the supplier wrote it" changes nothing (#4.1).
Output
governed.json - the {claim_findings} hop.
Grounding requirements
Approvals cite the substantiation reference; blocks cite the regulated-term list.
Constraints
- The engine decides; the model never rephrases a blocked claim into the draft ("fights germs" for a blocked "antibacterial" is still the claim).
- Approving a regulated claim is a human/regulatory affair - out of scope.
Escalation / uncertainty
Every blocked claim escalates to the claim owner with the library citation.