consistency-audit

# Consistency Audit — the paper vs itself Audit intra-paper self-consistency for: **$ARGUMENTS** (requires `claims.json` from `/evidence-ledger`). Emit span-anchored `consistency-audit.findings.json`; the deterministic adjudicator — not this skill — computes the verdict. > 🔒 **Do not wrap this skill in `/loop`, `/schedule`, or `CronCreate`.** It is > verdict-bearing input — it proposes the findings the deterministic adjudicator > turns into the report. Re-firing it on a wall-clock timer adds no signal: its > output changes only when the **paper / ledger** changes, not with the clock. > Schedule the *external wait that precedes it* — ledger built → audit **once**. > (Mirrors ARIS's external-cadence doctrine.) > The flagship instrument. Internal contradiction is the single most defensible > thing you can check on an unknown submission: it needs no external GT, runs at L0 > (PDF-only), and is exactly where machine-generated papers crack — they hallucinate > *local* coherence. Recall scales with the ledger: a PDF-text (L0) ledger extracts > only number/scope spans, so the table/caption/method-drift checks gain teeth at L1 > (LaTeX), where tables and captions are actually extracted. Adapted from ARIS > `paper-claim-audit`, reframed from "paper vs result files" to **"paper vs > itself."** There is no external ground truth in this skill. ## Why this exists An autoresearch pipeline (or rushed human) writes the abstract, the tables, the method section, and the appendix in separa...