template-manuscript-claim-verification

# Manuscript claim verification ## Natural invoke - "Triple-check every claim in my manuscript before arXiv" - "Abstract numbers don't match optimization_results.csv" - "Verify citations actually support what the prose says" ## Inputs to confirm - **Project** — [`docs/_generated/active_projects.md`](../../_generated/active_projects.md). - **Manuscript style** — Pandoc-crossref vs registry tokens (see cross-ref skill). ## Workflow Build a **claim inventory** first (numbered, file:line, class: number, comparison, citation, cross-ref, method, figure reading). **Pass 1 — Source traceability:** For each claim, locate backing artifact (generated variable, `src/` + test, `output/` file, bib key, cross-ref key). Tag BACKED / WEAK / UNBACKED. The canonical deterministic check for binding manuscript numbers/citations to registered evidence is `infrastructure.validation.cli evidence <project> --fail-on-issues` — run it as the machine gate for BACKED claims. **Pass 2 — Independent recomputation:** Regenerate from clean; re-run validation CLI. Reconciliation table: stated | recomputed | tolerance | PASS/FAIL. UNREPRODUCIBLE = FAIL. **Pass 3 — Methodological adversary:** Independent review axis — overstated claims, citation mismatch, figure/caption issues, abstract not earned by results. Tag OVERSTATED / UNSUPPORTED / MISLEADING. **Pass 4 — Reference existence (anti-hallucination):** Resolve every cited reference against Crossref / OpenAlex / arXiv with the deterministic verifica...