citation-forensics

# Citation Forensics — are the references real and honestly used? Audit citation integrity for: **$ARGUMENTS** (requires `claims.json` from `/evidence-ledger`; reasons over its `type:"citation"` claims). Emit span-anchored `citation-forensics.findings.json`. This skill computes **no verdict**. > 🔒 **Do not wrap this skill in `/loop`, `/schedule`, or `CronCreate`.** It is > verdict-bearing input — it proposes the citation 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 / bibliography** > changes, not with the clock, and each run spends real cross-model + lookup budget > per cited key. Schedule the *external wait that precedes it* — bibliography > finalized → ledger rebuilt → audit **once**. (Mirrors ARIS's external-cadence > doctrine.) > Adapted from ARIS `citation-audit`, re-wired onto this repo's evidence ledger and > the reviewer≠adjudicator contract, and reframed from "audit + **rewrite** the bib" > to **"emit ledger-anchored findings, never touch the paper."** Three layers, ported > verbatim: **existence → metadata → context.** Following the repo's > `baseline-comparison-audit` pattern, the **executor** gathers the canonical facts > (DBLP / arXiv / DOI) as neutral evidence; a **fresh cross-model reviewer** judges > existence + metadata + context over those facts. The reviewer never grades — the > deterministic adjudicator does. ## Why this exists An...