verify-before-claim

# Verify Before Claim <skill_contract> <input>One falsifiable claim, its artifact or system, risk, expected result, permissions, and available checks.</input> <output>A scoped claim decision with fresh evidence, residual risk, approval, and rollback status.</output> <done>The cheapest direct check after the final material change supports the exact allowed wording.</done> <non_goals>Producing the artifact, inferring success from effort, or widening a claim beyond checked evidence.</non_goals> No evidence, no claim. Match the check to the exact claim, use fresh evidence, and keep execution authority separate from approval authority for consequential actions. ## Usage Template Provide: proposed claim, artifact or system, risk level, available checks, expected result, permissions, and rollback path. ## Workflow <intake> 1. Rewrite the proposed statement as one falsifiable claim. 2. Classify risk: low, material, or consequential. 3. Select the cheapest check that directly tests the claim. 4. Record expected signal, time boundary, and acceptable evidence. </intake> <unknowns_gate> If the artifact, expected behavior, or verification method is missing, return `NEEDS_INPUT`. If only indirect evidence exists, return `INSUFFICIENT_EVIDENCE` or narrow the claim; never fill the gap with confidence language. </unknowns_gate> <execute> Run the selected check after the final material change. Examples: targeted test, lint, build, link check, read-after-write, diff inspect...