novelty-duplication-advisory

# Novelty & Duplication Advisory — the overlap a reviewer should weigh Lay out, for **$ARGUMENTS** (a paper-dir or a `claims.json` from `/evidence-ledger`), the candidate prior-work overlap a human reviewer should weigh for two reviewer-judgment signals — **trivial combination** ("standard A+B+C") and **duplicate publication** ("repackaged prior work"). Retrieve candidates, map them side-by-side against the paper's ledger-anchored contribution, and emit `novelty-duplication-advisory.memo.md`. Run AFTER `/evidence-ledger` (so `claims.json` exists). This skill **decides nothing** — it never rules "trivial" or "duplicate", and the deterministic adjudicator caps it at `info`. > 🔒 **Do not wrap this skill in `/loop`, `/schedule`, or `CronCreate`.** It retrieves > external prior work once and synthesizes it into one advisory memo. Even though it is > **memo-only** (the adjudicator caps it at `info`, so it adds no verdict weight), the > no-new-signal cadence rule still applies: its output changes only when the **ledger / the > paper / the literature** change, never with the wall clock. It is tempting to re-fire on a > timer "to catch newly-posted prior work," but a wall-clock loop burns real DBLP + web + > cross-model budget on every tick for a paper that has not changed. Schedule the *work that > precedes it* — ledger built → run this **once**. (Mirrors ARIS's external-cadence doctrine: > `/loop`·`/schedule` are fire-control, not a judge.) > Adapted from ARIS `novelty-check`, w...