claim-verification
Claim Verification
Overview
Evidence-reliability check that walks every tagged claim in .writing/manuscript/*.tex and proves it supportable. Two core passes — completeness and citation resolution (dual source of truth via Zotero + network, with semantic match against the cited abstract) — plus an optional numeric/table consistency pass. Outputs .writing/verify-report.md per-claim PASS/FAIL and caches resolved DOIs in .writing/verify-cache.json.
The most valuable check for an AI-drafted skeleton is Pass 2: it catches hallucinated DOIs and citations whose abstract does not actually support the claim — exactly the reliability the human author leans on when refining.
Core principle: Evidence before claims, always. Violating the letter of this rule is violating the spirit.
Iron law: No STATUS: verified flip without fresh pass evidence recorded in the report.
Relation to the Claim-First Protocol: during drafting, the claim-first discipline (see ../_shared/core/claim-first-protocol.md) requires resolving a claim's evidence before writing prose against it, do not draft against a stub-status claim. Drafting flips STATUS to evidence_ready when evidence is found. This skill is what flips evidence_ready → verified after the passes succeed. Never edit STATUS to verified manually: the audit trail lives in .writing/verify-report.md.
Optional term-ordering discipline. If the project opted into .writing/glossary.md, drafting must keep every term defined before it is used: a % define: tag belongs in the right section, and no % use: tag may reference a term whose defined_in sits later in the paper. This verification skill does not re-run those checks; they are edit-time invariants, not verification-gate invariants. If you suspect a term ordering drifted after manual edits, sweep manually with grep -n '% \(define\|use\):' .writing/manuscript/*.tex and cross-reference .writing/glossary.md.