[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FD12SBNF76TTSWDKW6S30W":3,"skill-same:01M7FD12SBNF76TTSWDKW6S30W":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7FD12SBNF76TTSWDKW6S30W","integrity-forensics",null,"Run the Anti-Autoresearch integrity-forensics sweep (span-anchored evidence ledger → GPT auditors propose findings → a rules-only reporter that lists every proposal with what the auditor said about it) against a paper via a SHA-pinned thin launcher — then convert the verdict into a typed policy gate (BLOCK\u002FWARN\u002FNO_NEW_BLOCKER) and an append-only obligations ledger. Use when user says \"integrity forensics\", \"forensic audit this paper\", \"投稿前自查诚信\", \"审这篇论文的诚信\", or says \"anti-autoresearch\" when the upstream repo's own skills are not installed. Also invoked by \u002Fpaper-writing (submission self-forensics, default ON), \u002Fpeer-review (forensic appendix), \u002Fresubmit-pipeline.","CZX-LBJ\u002Fdeepseek-science","CZX-LBJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F204594689?v=4","01M7FC59WQ9PFXT04MKGJDCFFT","czx","01M7FC59XB2GW0BKWN9JTDBQS7",1,"MIT","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fintegrity-forensics\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: integrity-forensics\ndescription: \"Run the Anti-Autoresearch integrity-forensics sweep (span-anchored evidence ledger → GPT auditors propose findings → a rules-only reporter that lists every proposal with what the auditor said about it) against a paper via a SHA-pinned thin launcher — then convert the verdict into a typed policy gate (BLOCK\u002FWARN\u002FNO_NEW_BLOCKER) and an append-only obligations ledger. Use when user says \\\"integrity forensics\\\", \\\"forensic audit this paper\\\", \\\"投稿前自查诚信\\\", \\\"审这篇论文的诚信\\\", or says \\\"anti-autoresearch\\\" when the upstream repo's own skills are not installed. Also invoked by \u002Fpaper-writing (submission self-forensics, default ON), \u002Fpeer-review (forensic appendix), \u002Fresubmit-pipeline.\"\nargument-hint: \"[paper-dir | pdf | arxiv-id]\"\nallowed-tools: Bash(*), Read, Write, Grep, Glob, mcp__codex__codex\n---\n\n# Integrity Forensics — thin launcher for Anti-Autoresearch\n\nAudit target: **$ARGUMENTS**\n\n> **What this is.** ARIS generates papers; [Anti-Autoresearch](https:\u002F\u002Fgithub.com\u002Fwanshuiyin\u002FAnti-Autoresearch)\n> is its outward-pointed dual — reviewer-side integrity forensics (46 patterns\n> across 8 families, deterministic GRIM\u002FGRIMMER\u002Fstatcheck core, span-anchored\n> claims, a rules-only reporter that summarizes rather than adjudicates). This skill is a\n> **thin launcher**: it pins an upstream commit, validates the pin with the\n> upstream eval gate, delegates execution unchanged, and post-processes the\n> verdict into ARIS's policy vocabulary. It vendors nothing and forks nothing.\n\n> 🔁 **Cadence fence** (`shared-references\u002Fexternal-cadence.md`): this skill is\n> verdict-bearing decision support. Do not wrap it in `\u002Floop` \u002F `\u002Fschedule` —\n> and NEVER as \"iterate edits until it stops flagging\" (see The One Forbidden\n> Loop below).\n\n## Constants\n\n- **ANTI_AR_REPO = `https:\u002F\u002Fgithub.com\u002Fwanshuiyin\u002FAnti-Autoresearch.git`**\n- **ANTI_AR_COMMIT = `b47af6f983b38347b6d2110379e266400597cf66`** — the SHA-pin.\n  The launcher NEVER tracks upstream HEAD; bumping this constant is a reviewed\n  change (see Pin-bump checklist).\n- **CLONE_DIR = `~\u002F.aris\u002Fanti-autoresearch`** — the pinned working copy. Host-neutral\n  on purpose: ARIS also runs on DeepSeek Harness, Codex CLI, Cursor, Trae,\n  Antigravity and Copilot CLI, where `~\u002F.claude\u002F` would name an installation the\n  user does not have. An older clone at `~\u002F.claude\u002Fanti-autoresearch` is unused;\n  move it and its `.aris_eval_ok_*` receipt only to keep an offline\n  deterministic-only run working, otherwise delete it whenever convenient.\n- **NO REVIEWER KNOBS.** This launcher exposes no reviewer model\u002Feffort\n  parameters and never maps ARIS `— effort:` onto upstream settings. The\n  pinned upstream runs exactly what it pins (`gpt-6-astra` + `xhigh`, its own\n  design decision). Overriding upstream review policy from a launcher would\n  create a second, unauditable configuration surface.\n- **GATE_HELPER = `forensics_gate.py`** — resolved via the canonical chain\n  (`shared-references\u002Fintegration-contract.md` §2): `.aris\u002Ftools\u002F` →\n  `tools\u002F` → `$ARIS_REPO\u002Ftools\u002F` → `$ARIS_REPO\u002Ftools\u002F` via `~\u002F.aris\u002Frepo`.\n  Failure policy A (required): if it cannot be resolved at\n  `assurance: submission`, STOP — never improvise the gate.\n\n## Step 0 — Bootstrap the pin (idempotent)\n\n```bash\nCLONE_DIR=\"$HOME\u002F.aris\u002Fanti-autoresearch\"\nANTI_AR_COMMIT=\"b47af6f983b38347b6d2110379e266400597cf66\"\n\nmkdir -p \"$HOME\u002F.aris\"\nif [ ! -d \"$CLONE_DIR\u002F.git\" ]; then\n    git clone --no-checkout https:\u002F\u002Fgithub.com\u002Fwanshuiyin\u002FAnti-Autoresearch.git \"$CLONE_DIR\"\nfi\n# fetch ONLY if the pin isn't already present — a cached, validated pin works offline\ngit -C \"$CLONE_DIR\" cat-file -e \"$ANTI_AR_COMMIT^{commit}\" 2>\u002Fdev\u002Fnull \\\n    || git -C \"$CLONE_DIR\" fetch -q origin\ngit -C \"$CLONE_DIR\" checkout -qf \"$ANTI_AR_COMMIT\" || {\n    echo \"FATAL: cannot checkout pinned commit $ANTI_AR_COMMIT\"; exit 1; }\n# Force a PRISTINE tree at the pin — local tampering with the clone (edited\n# adjudicator, injected module, even one hidden inside a NESTED git repo,\n# which single-f clean skips) must not survive bootstrap and run under the\n# official pin's name. Every step is checked; then the tree is verified.\ngit -C \"$CLONE_DIR\" reset --hard -q \"$ANTI_AR_COMMIT\" || {\n    echo \"FATAL: reset to pin failed\"; exit 1; }\ngit -C \"$CLONE_DIR\" clean -ffdxq || {\n    echo \"FATAL: clean failed\"; exit 1; }\n[ -z \"$(git -C \"$CLONE_DIR\" status --porcelain)\" ] || {\n    echo \"FATAL: clone is not pristine after reset+clean — refusing to run\"; exit 1; }\n\n# One-time-per-pin validation: the upstream eval gate (8 injected-defect\n# classes, 100% recall + zero clean false positives) must PASS before this\n# pin is allowed to produce a verdict. NEVER skip; NEVER proceed on failure.\n# The marker lives OUTSIDE the clone: a marker inside a tamperable tree proves\n# nothing (and `git clean` above would erase it, forcing re-eval every run).\nMARKER=\"${CLONE_DIR}.aris_eval_ok_${ANTI_AR_COMMIT}\"\nif [ ! -f \"$MARKER\" ]; then\n    ( cd \"$CLONE_DIR\" && python3 eval\u002Frun_eval.py ) || {\n        echo \"FATAL: upstream eval gate FAILED at pin $ANTI_AR_COMMIT — refusing to\"\n        echo \"       use an unvalidated forensics pin for verdicts.\"; exit 1; }\n    touch \"$MARKER\"\nfi\necho \"anti-autoresearch pinned at $ANTI_AR_COMMIT (eval gate: validated)\"\n```\n\n## Step 1 — Delegate: run the upstream sweep, unchanged\n\nOpen and follow **`$CLONE_DIR\u002Fworkflows\u002Fanti-autoresearch\u002FSKILL.md`** end to\nend on the target. Two wrapper rules — the ONLY things this launcher adds:\n\n1. **cwd.** Upstream skills self-locate via `git rev-parse --show-toplevel`.\n   Run every upstream bash block with `cd \"$CLONE_DIR\"` first — ALWAYS the cd,\n   never just an exported `ROOT` (upstream blocks re-derive ROOT themselves\n   and would overwrite it) — and refer to the paper by **absolute path**,\n   otherwise upstream resolves ROOT to the ARIS repo and finds the wrong\n   Python spine.\n2. **Codex calls carry `approval-policy: never` + `sandbox: read-only`**\n   (session hygiene; upstream already specifies fresh-thread-per-dimension,\n   serial execution, and its own model pins — do not alter them).\n\nEverything else — the evidence ledger, coverage.json state machine, the nine\nauditor dimensions, the refutation pass, the deterministic summary — is\nupstream's contract. **Never rewrite, soften, or re-map its outputs**\n(`report.json` + `REPORT.md`, verdict ∈ CLEAN_GIVEN_EVIDENCE \u002F SOFT_FLAGS \u002F\nHARD_FLAGS \u002F REVIEW_UNAVAILABLE). The observability level (L0\u002FL1\u002FL2) is\nwhatever upstream derives from the artifacts present — do not promise L2.\n\n## Step 2 — Typed gate + obligations (ARIS-side post-processing)\n\n```bash\n# Resolve $GATE_HELPER via the canonical chain (integration-contract §2), then\n# ONE atomic call (update + gate in a single locked transaction — the gate only\n# ever speaks for the report the ledger has folded, sha-bound):\npython3 \"$GATE_HELPER\" evaluate --report \"$PAPER_DIR\u002Freport.json\" --paper-dir \"$PAPER_DIR\" \\\n    --anti-ar-commit \"$ANTI_AR_COMMIT\" --executor-model \"\u003Cthis pipeline's executor>\"\n# exit 0 = WARN \u002F NO_NEW_BLOCKER · exit 1 = BLOCK\n```\n\nThe gate translates the verdict into policy WITHOUT re-labeling it:\n\n| upstream verdict | policy |\n|---|---|\n| `HARD_FLAGS` | **BLOCK** — an auditor proposed something critical and it is on the table for you to read; never \"the machine found fraud\" |\n| `REVIEW_UNAVAILABLE` | **BLOCK** — an incomplete sweep cannot wave a paper through |\n| `SOFT_FLAGS` | **WARN** — human disposition. Read the never-ran list too: the upstream verdict folds incompleteness in only when it would otherwise be clean, so a WARN can sit on top of a sweep where verdict-bearing dimensions never ran. `evaluate` and `fresh` both print those dimensions |\n| `CLEAN_GIVEN_EVIDENCE` | **NO_NEW_BLOCKER** — *never* called PASS or accepted: it means \"no flag found in the evidence at hand\", not an acquittal |\n| anything else | **BLOCK** (fail closed) |\n\nplus: any OPEN critical obligation → BLOCK; any OPEN obligation → at least\nWARN; a closed-without-receipt or unknown-status ledger entry → BLOCK (a\nhand-edited `\"status\": \"RESOLVED\"` does not open the gate).\n\n`gate.json` also records a `paper_fingerprint` (sha over the paper's compile\ninputs AND deliverables — `.tex`\u002F`.bib`\u002F`.sty`\u002F`.cls`\u002Ffigures\u002FPDF). The\ndownstream preflight is ONE command:\n`python3 \"$GATE_HELPER\" fresh --paper-dir \"$PAPER_DIR\" --anti-ar-commit \"$ANTI_AR_COMMIT\"`\n— exit 0 ⟺ the gate was produced at the CURRENT pin ∧ a gate\nexists ∧ nothing in the paper changed after it ∧ the gate matches the current\nobligations ledger ∧ the decision — **re-computed from the sha-verified\narchived report (`last_report.json`) + the live ledger, never read from the\ngate's stored token** — is pass-capable (`WARN` \u002F `NO_NEW_BLOCKER`). Anything\nelse — missing gate, post-gate edit or recompile, unbound ledger or archive,\nrecompute mismatch, `BLOCK`, unknown token — exits 1: re-run the sweep +\n`evaluate`. Every ledger mutation (`update`\u002F`resolve`\u002F`waive`) deletes the\nstanding `gate.json`, so an interrupted run can never leave a stale pass; and\n`evaluate` refuses a report OLDER than any paper file (a stale report cannot\nbe folded onto text it never audited). Run `evaluate` immediately after the\nsweep, before touching any paper file.\n\nThe gate artifact also records honest provenance: upstream's auditors are\nGPT-family, so for a **Claude executor** the findings carry `cross-family`\nproposal provenance; for a **Codex executor** they are `same-family`. Either\nway this gate only raises flags — it has no acceptance to grant, so the\ndistinction is informational, not a loophole.\n\n## Step 3 — Fix what it found (obligations, not a polish loop)\n\nEvery OPEN obligation gets DISPOSITIONED — fixed, or explicitly waived. Upstream now\nreports every proposal an auditor made rather than deciding which ones do not count, so\nexpect more obligations than a pre-2026-08 sweep opened, and expect some of them to be\nproposals you disagree with. **`waive` is a first-class, expected outcome** — \"a model\nproposed this and I, the human, judge it wrong\" is a normal disposition here, not a last\nresort. Weigh each one against the report's columns: `Anchored`, `Observability`,\n`FP-risk`, `Surface`, `Ext-check`.\n\nFor the ones that are real, use the right door:\n\n| Finding family | Repair route |\n|---|---|\n| A — numeric self-consistency | recompute from the RESULT FILES (`\u002Fpaper-claim-audit` evidence chain); fix the number, not the sentence |\n| D — experiment integrity | back to `\u002Fexperiment-audit` \u002F rerun |\n| E — citations | `\u002Fcitation-audit` KEEP\u002FFIX\u002FREPLACE machinery |\n| G — proof & derivation | `\u002Fproof-checker`'s fix loop |\n| B \u002F C \u002F H — scope, baselines, eval design | science-level: feed the finding to `\u002Fauto-review-loop` as reviewer INPUT, or to the human |\n| AIS \u002F advisory (zero-weight) | optional context for `\u002Fauto-paper-improvement-loop`; never gates |\n\nClose each obligation explicitly — the receipt is typed and hashed:\n\n```bash\npython3 \"$GATE_HELPER\" resolve --paper-dir \"$PAPER_DIR\" --obligation-id \u003Cid> \\\n    --fix-type corrected-from-results|claim-narrowed|claim-withdrawn|citation-replaced \\\n    --evidence \u003Cpath-to-the-ground-truth-that-backs-the-fix> \\\n    --verified-by \"human:\u003Cname>\" | \"checker:\u003Ctool>\" | \"cross-family-review:\u003Cthread-id>\"\n# or, with HUMAN sign-off only:\npython3 \"$GATE_HELPER\" waive --paper-dir \"$PAPER_DIR\" --obligation-id \u003Cid> \\\n    --approver \"human:\u003Cname>\" --reason \"\u003Cwhy this stands as-is>\"\n```\n\nRules the ledger enforces mechanically (`tests\u002Ftest_forensics_gate.py`):\n- **append-only** — re-running the sweep can open obligations, never close them;\n- a finding that *disappears* from a later report stays OPEN and gains\n  `UNRESOLVED_DISAPPEARANCE` — rewording the span is not a fix;\n- `claim-withdrawn` is an honest fix (deleting an unsupported claim is a\n  legitimate resolution — with the deletion diff as evidence);\n- a **waiver is not a resolution**: human-approved, permanently recorded,\n  original finding snapshot immutable;\n- the executor's `fix_type` label is a receipt, not a verdict — closure of a\n  critical needs a family checker, a fresh cross-family review, or a human\n  (`--verified-by` requires TYPED provenance and is recorded; naming a human\n  who did not approve is a false record with a permanent paper trail);\n- receipts are **re-verified, not remembered**: on every later gate the\n  evidence file must still exist and still hash to what was recorded at\n  closure time — editing the evidence after closing re-opens the BLOCK;\n- `resolve`\u002F`waive` (like `update`) **invalidate the standing `gate.json`** —\n  finish Step 3 by re-running the sweep + `evaluate`, so the gate that\n  downstream preflights read reflects the post-fix state.\n\n### The One Forbidden Loop\n\n**Never run \"edit → re-sweep → repeat until CLEAN\".** That objective function\nteaches the editor to defeat the detector — deleting an anchored span kills a\nflag faster than fixing the number, and the result is a paper laundered\nagainst its own audit. The re-run after fixes exists to confirm the\nDISCREPANCY is gone (and to catch new ones); the obligations ledger — not the\nverdict — decides whether the gate opens.\n\n## Trust boundary (what is computed vs what is protocol)\n\n- **Computed** (the gate enforces these mechanically): verdict→policy mapping,\n  append-only ledger lifecycle, sha bindings (report ↔ ledger ↔ archive),\n  receipt re-hashing, the paper fingerprint, pin\u002Fversion match, and the\n  recomputed decision (`fresh` never trusts a stored token).\n- **Protocol** (instruction-graded, deliberately): that the sweep actually ran\n  at the pinned clone against this paper. The gate raises the bar —\n  structural floor (a report must name its adjudicator and carry a coverage\n  map), stale-report mtime guard — and that is where it stops. There is no\n  cryptographic binding between the report and the paper, deliberately: this is\n  a research-workflow gate, not a provenance system, and the honest statement is\n  that a determined executor can hand it a stale report. Likewise `human:` \u002F `checker:` \u002F `cross-family-review:` labels are\n  accountability, not authentication: a false label is an explicit,\n  permanent false record.\n- **Out of scope**: a party rewriting the `.aris\u002F` artifacts consistently with\n  shell access has owner power (they could delete the directory outright).\n  The gate defends against the sloppy or corner-cutting executor and against\n  honest crashes\u002Fraces\u002Fresumes — not against the machine's owner.\n\n## Pin-bump checklist (maintainers)\n\n1. Set the new `ANTI_AR_COMMIT`; delete no markers (the eval gate re-runs\n   automatically for the new SHA).\n2. Diff upstream's `schemas\u002Freport.schema.json` + verdict vocabulary against\n   the gate's policy table; extend `tools\u002Fforensics_gate.py` BEFORE bumping if\n   they moved.\n3. Old findings\u002Fobligations stay valid (fingerprints are span\u002Fhash-based, not\n   id-based) — but findings produced by an older adjudicator must be\n   **re-audited, not re-adjudicated** (upstream's own migration rule).\n4. Tell users when a bump changes how much they must disposition. `fresh`\n   rejects every stored `gate.json` at the old pin with `PIN_MISMATCH`, so a\n   bump already forces a re-sweep for everyone — bundle upstream changes behind\n   ONE bump rather than two, or the re-sweep cost is paid twice.\n\n> **2026-08 bump (`98a75fc`) — expect more open obligations.** Upstream moved\n> from adjudicating proposals to reporting them: findings its FP-risk,\n> observability, surface and needs-external-check gates used to demote to `info`\n> now arrive above info, so they open obligations. Nothing got worse in the\n> paper; more of what the auditors said is now visible. Waiving a proposal you\n> judge wrong is the expected disposition, and the report's per-finding columns\n> (`Anchored`, `Observability`, `FP-risk`, `Surface`, `Ext-check`) are what you\n> weigh. Upstream also deleted its report self-binding hashes in the same window\n> — nothing here ever consumed them.\n\n## Codex-native note (mirror)\n\nUpstream ships no Codex-native pack; its auditor skills are Claude-Code\ncontracts. A Codex-native session may run upstream's **deterministic-only\nmode** (numeric core + adjudicator with an all-`review_unavailable` coverage\nmap — honestly scoped: it can flag, it can never say CLEAN). The full\nnine-dimension sweep requires a host that can execute upstream's Claude-Code\ncontracts unchanged — Claude Code and the `dsh-aris` bundle on DeepSeek Harness\nare the known ones. Translating upstream's\nreviewer calls into `spawn_agent` on the fly is REWRITING an upstream\ncontract — forbidden.\n\n## Review tracing\n\nUpstream saves its own per-dimension traces under the paper's\n`.aris\u002Ftraces\u002F`. The launcher adds only the `.aris\u002Fforensics\u002F` artifacts:\n`gate.json` (pins `anti_ar_commit` + report\u002Fledger hashes + the paper-text\nfingerprint), `obligations.json` (the append-only ledger), and\n`last_report.json` (the sha-verified archive of the folded report that\n`fresh` recomputes from).\n","# Integrity Forensics — thin launcher for Anti-Autoresearch\n\nAudit target: **$ARGUMENTS**\n\n> **What this is.** ARIS generates papers; [Anti-Autoresearch](https:\u002F\u002Fgithub.com\u002Fwanshuiyin\u002FAnti-Autoresearch)\n> is its outward-pointed dual — reviewer-side integrity forensics (46 patterns\n> across 8 families, deterministic GRIM\u002FGRIMMER\u002Fstatcheck core, span-anchored\n> claims, a rules-only reporter that summarizes rather than adjudicates). This skill is a\n> **thin launcher**: it pins an upstream commit, validates the pin with the\n> upstream eval gate, delegates execution unchanged, and post-processes the\n> verdict into ARIS's policy vocabulary. It vendors nothing and forks nothing.\n\n> 🔁 **Cadence fence** (`shared-references\u002Fexternal-cadence.md`): this skill is\n> verdict-bearing decision support. Do not wrap it in `\u002Floop` \u002F `\u002Fschedule` —\n> and NEVER as \"iterate edits until it stops flagging\" (see The One Forbidden\n> Loop below).\n\n## Constants\n\n- **ANTI_AR_REPO = `https:\u002F\u002Fgithub.com\u002Fwanshuiyin\u002FAnti-Autoresearch.git`**\n- **ANTI_AR_COMMIT = `b47af6f983b38347b6d2110379e266400597cf66`** — the SHA-pin.\n  The launcher NEVER tracks upstream HEAD; bumping this constant is a reviewed\n  change (see Pin-bump checklist).\n- **CLONE_DIR = `~\u002F.aris\u002Fanti-autoresearch`** — the pinned working copy. Host-neutral\n  on purpose: ARIS also runs on DeepSeek Harness, Codex CLI, Cursor, Trae,\n  Antigravity and Copilot CLI, where `~\u002F.claude\u002F` would name an installation the\n  user does not have. An older clone at `~\u002F.claude\u002Fanti-autoresearch` is unused;\n  move it and its `.aris_eval_ok_*` receipt only to keep an offline\n  deterministic-only run working, otherwise delete it whenever convenient.\n- **NO REVIEWER KNOBS.** This launcher exposes no reviewer model\u002Feffort\n  parameters and never maps ARIS `— effort:` onto upstream settings. The\n  pinned upstream runs exactly what it pins (`gpt-6-astra` + `xhigh`, its own\n  design decision). Overriding upstream review policy from a launcher would\n  create a second, unauditable configuration surface.\n- **GATE_HELPER = `forensics_gate.py`** — resolved via the canonical chain\n  (`shared-references\u002Fintegration-contract.md` §2): `.aris\u002Ftools\u002F` →\n  `tools\u002F` → `$ARIS_REPO\u002Ftools\u002F` → `$ARIS_REPO\u002Ftools\u002F` via `~\u002F.aris\u002Frepo`.\n  Failure policy A (required): if it cannot be resolved at\n  `assurance: submission`, STOP — never improvise the gate.\n\n## Step 0 — Bootstrap the pin (idempotent)\n\n```bash\nCLONE_DIR=\"$HOME\u002F.aris\u002Fanti-autoresearch\"\nANTI_AR_COMMIT=\"b47af6f983b38347b6d2110379e266400597cf66\"\n\nmkdir -p \"$HOME\u002F.aris\"\nif [ ! -d \"$CLONE_DIR\u002F.git\" ]; then\n    git clone --no-checkout https:\u002F\u002Fgithub.com\u002Fwanshuiyin\u002FAnti-Autoresearch.git \"$CLONE_DIR\"\nfi\n# fetch ONLY if the pin isn't already present — a cached, validated pin works offline\ngit -C \"$CLONE_DIR\" cat-file -e \"$ANTI_AR_COMMIT^{commit}\" 2>\u002Fdev\u002Fnull \\\n    || git -C \"$CLONE_DIR\" fetch -q origin\ngit -C \"$CLONE_DIR\" checkout -qf \"$ANTI_AR_COMMIT\" || {\n    echo \"FATAL: cannot checkout pinned commit $ANTI_AR_COMMIT\"; exit 1; }\n# Force a PRISTINE tree at the pin — local tampering with the clone (edited\n# adjudicator, injected module, even one hidden inside a NESTED git repo,\n# which single-f clean skips) must not survive bootstrap and run under the\n# official pin's name. Every step is checked; then the tree is verified.\ngit -C \"$CLONE_DIR\" reset --hard -q \"$ANTI_AR_COMMIT\" || {\n    echo \"FATAL: reset to pin failed\"; exit 1; }\ngit -C \"$CLONE_DIR\" clean -ffdxq || {\n    echo \"FATAL: clean failed\"; exit 1; }\n[ -z \"$(git -C \"$CLONE_DIR\" status --porcelain)\" ] || {\n    echo \"FATAL: clone is not pristine after reset+clean — refusing to run\"; exit 1; }\n\n# One-time-per-pin validation: the upstream eval gate (8 injected-defect\n# classes, 100% recall + zero clean false positives) must PASS before this\n# pin is allowed to produce a verdict. NEVER skip; NEVER proceed on failure.\n# The marker lives OUTSIDE the clone: a marker inside a tamperable tree proves\n# nothing (and `git clean` above would erase it, forcing re-eval every run).\nMARKER=\"${CLONE_DIR}.aris_eval_ok_${ANTI_AR_COMMIT}\"\nif [ ! -f \"$MARKER\" ]; then\n    ( cd \"$CLONE_DIR\" && python3 eval\u002Frun_eval.py ) || {\n        echo \"FATAL: upstream eval gate FAILED at pin $ANTI_AR_COMMIT — refusing to\"\n        echo \"       use an unvalidated forensics pin for verdicts.\"; exit 1; }\n    touch \"$MARKER\"\nfi\necho \"anti-autoresearch pinned at $ANTI_AR_COMMIT (eval gate: validated)\"\n```\n\n## Step 1 — Delegate: run the upstream sweep, unchanged\n\nOpen and follow **`$CLONE_DIR\u002Fworkflows\u002Fanti-autoresearch\u002FSKILL.md`** end to\nend on the target. Two wrapper rules — the ONLY things this launcher adds:\n\n1. **cwd.** Upstream skills self-locate via `git rev-parse --show-toplevel`.\n   Run every upstream bash block with `cd \"$CLONE_DIR\"` first — ALWAYS the cd,\n   never just an exported `ROOT` (upstream blocks re-derive ROOT themselves\n   and would overwrite it) — and refer to the paper by **absolute path**,\n   otherwise upstream resolves ROOT to the ARIS repo and finds the wrong\n   Python spine.\n2. **Codex calls carry `approval-policy: never` + `sandbox: read-only`**\n   (session hygiene; upstream already specifies fresh-thread-per-dimension,\n   serial execution, and its own model pins — do not alter them).\n\nEverything else — the evidence ledger, coverage.json state machine, the nine\nauditor dimensions, the refutation pass, the deterministic summary — is\nupstream's contract. **Never rewrite, soften, or re-map its outputs**\n(`report.json` + `REPORT.md`, verdict ∈ CLEAN_GIVEN_EVIDENCE \u002F SOFT_FLAGS \u002F\nHARD_FLAGS \u002F REVIEW_UNAVAILABLE). The observability level (L0\u002FL1\u002FL2) is\nwhatever upstream derives from the artifacts present — do not promise L2.\n\n## Step 2 — Typed gate + obligations (ARIS-side post-processing)\n\n```bash\n# Resolve $GATE_HELPER via the canonical chain (integration-contract §2), then\n# ONE atomic call (update + gate in a single locked transaction — the gate only\n# ever speaks for the report the ledger has folded, sha-bound):\npython3 \"$GATE_HELPER\" evaluate --report \"$PAPER_DIR\u002Freport.json\" --paper-dir \"$PAPER_DIR\" \\\n    --anti-ar-commit \"$ANTI_AR_COMMIT\" --executor-model \"\u003Cthis pipeline's executor>\"\n# exit 0 = WARN \u002F NO_NEW_BLOCKER · exit 1 = BLOCK\n```\n\nThe gate translates the verdict into policy WITHOUT re-labeling it:\n\n| upstream verdict | policy |\n|---|---|\n| `HARD_FLAGS` | **BLOCK** — an auditor proposed something critical and it is on the table for you to read; never \"the machine found fraud\" |\n| `REVIEW_UNAVAILABLE` | **BLOCK** — an incomplete sweep cannot wave a paper through |\n| `SOFT_FLAGS` | **WARN** — human disposition. Read the never-ran list too: the upstream verdict folds incompleteness in only when it would otherwise be clean, so a WARN can sit on top of a sweep where verdict-bearing dimensions never ran. `evaluate` and `fresh` both print those dimensions |\n| `CLEAN_GIVEN_EVIDENCE` | **NO_NEW_BLOCKER** — *never* called PASS or accepted: it means \"no flag found in the evidence at hand\", not an acquittal |\n| anything else | **BLOCK** (fail closed) |\n\nplus: any OPEN critical obligation → BLOCK; any OPEN obligation → at least\nWARN; a closed-without-receipt or unknown-status ledger entry → BLOCK (a\nhand-edited `\"status\": \"RESOLVED\"` does not open the gate).\n\n`gate.json` also records a `paper_fingerprint` (sha over the paper's compile\ninputs AND deliverables — `.tex`\u002F`.bib`\u002F`.sty`\u002F`.cls`\u002Ffigures\u002FPDF). The\ndownstream preflight is ONE command:\n`python3 \"$GATE_HELPER\" fresh --paper-dir \"$PAPER_DIR\" --anti-ar-commit \"$ANTI_AR_COMMIT\"`\n— exit 0 ⟺ the gate was produced at the CURRENT pin ∧ a gate\nexists ∧ nothing in the paper changed after it ∧ the gate matches the current\nobligations ledger ∧ the decision — **re-computed from the sha-verified\narchived report (`last_report.json`) + the live ledger, never read from the\ngate's stored token** — is pass-capable (`WARN` \u002F `NO_NEW_BLOCKER`). Anything\nelse — missing gate, post-gate edit or recompile, unbound ledger or archive,\nrecompute mismatch, `BLOCK`, unknown token — exits 1: re-run the sweep +\n`evaluate`. Every ledger mutation (`update`\u002F`resolve`\u002F`waive`) deletes the\nstanding `gate.json`, so an interrupted run can never leave a stale pass; and\n`evaluate` refuses a report OLDER than any paper file (a stale report cannot\nbe folded onto text it never audited). Run `evaluate` immediately after the\nsweep, before touching any paper file.\n\nThe gate artifact also records honest provenance: upstream's auditors are\nGPT-family, so for a **Claude executor** the findings carry `cross-family`\nproposal provenance; for a **Codex executor** they are `same-family`. Either\nway this gate only raises flags — it has no acceptance to grant, so the\ndistinction is informational, not a loophole.\n\n## Step 3 — Fix what it found (obligations, not a polish loop)\n\nEvery OPEN obligation gets DISPOSITIONED — fixed, or explicitly waived. Upstream now\nreports every proposal an auditor made rather than deciding which ones do not count, so\nexpect more obligations than a pre-2026-08 sweep opened, and expect some of them to be\nproposals you disagree with. **`waive` is a first-class, expected outcome** — \"a model\nproposed this and I, the human, judge it wrong\" is a normal disposition here, not a last\nresort. Weigh each one against the report's columns: `Anchored`, `Observability`,\n`FP-risk`, `Surface`, `Ext-check`.\n\nFor the ones that are real, use the right door:\n\n| Finding family | Repair route |\n|---|---|\n| A — numeric self-consistency | recompute from the RESULT FILES (`\u002Fpaper-claim-audit` evidence chain); fix the number, not the sentence |\n| D — experiment integrity | back to `\u002Fexperiment-audit` \u002F rerun |\n| E — citations | `\u002Fcitation-audit` KEEP\u002FFIX\u002FREPLACE machinery |\n| G — proof & derivation | `\u002Fproof-checker`'s fix loop |\n| B \u002F C \u002F H — scope, baselines, eval design | science-level: feed the finding to `\u002Fauto-review-loop` as reviewer INPUT, or to the human |\n| AIS \u002F advisory (zero-weight) | optional context for `\u002Fauto-paper-improvement-loop`; never gates |\n\nClose each obligation explicitly — the receipt is typed and hashed:\n\n```bash\npython3 \"$GATE_HELPER\" resolve --paper-dir \"$PAPER_DIR\" --obligation-id \u003Cid> \\\n    --fix-type corrected-from-results|claim-narrowed|claim-withdrawn|citation-replaced \\\n    --evidence \u003Cpath-to-the-ground-truth-that-backs-the-fix> \\\n    --verified-by \"human:\u003Cname>\" | \"checker:\u003Ctool>\" | \"cross-family-review:\u003Cthread-id>\"\n# or, with HUMAN sign-off only:\npython3 \"$GATE_HELPER\" waive --paper-dir \"$PAPER_DIR\" --obligation-id \u003Cid> \\\n    --approver \"human:\u003Cname>\" --reason \"\u003Cwhy this stands as-is>\"\n```\n\nRules the ledger enforces mechanically (`tests\u002Ftest_forensics_gate.py`):\n- **append-only** — re-running the sweep can open obligations, never close them;\n- a finding that *disappears* from a later report stays OPEN and gains\n  `UNRESOLVED_DISAPPEARANCE` — rewording the span is not a fix;\n- `claim-withdrawn` is an honest fix (deleting an unsupported claim is a\n  legitimate resolution — with the deletion diff as evidence);\n- a **waiver is not a resolution**: human-approved, permanently recorded,\n  original finding snapshot immutable;\n- the executor's `fix_type` label is a receipt, not a verdict — closure of a\n  critical needs a family checker, a fresh cross-family review, or a human\n  (`--verified-by` requires TYPED provenance and is recorded; naming a human\n  who did not approve is a false record with a permanent paper trail);\n- receipts are **re-verified, not remembered**: on every later gate the\n  evidence file must still exist and still hash to what was recorded at\n  closure time — editing the evidence after closing re-opens the BLOCK;\n- `resolve`\u002F`waive` (like `update`) **invalidate the standing `gate.json`** —\n  finish Step 3 by re-running the sweep + `evaluate`, so the gate that\n  downstream preflights read reflects the post-fix state.\n\n### The One Forbidden Loop\n\n**Never run \"edit → re-sweep → repeat until CLEAN\".** That objective function\nteaches the editor to defeat the detector — deleting an anchored span kills a\nflag faster than fixing the number, and the result is a paper laundered\nagainst its own audit. The re-run after fixes exists to confirm the\nDISCREPANCY is gone (and to catch new ones); the obligations ledger — not the\nverdict — decides whether the gate opens.\n\n## Trust boundary (what is computed vs what is protocol)\n\n- **Computed** (the gate enforces these mechanically): verdict→policy mapping,\n  append-only ledger lifecycle, sha bindings (report ↔ ledger ↔ archive),\n  receipt re-hashing, the paper fingerprint, pin\u002Fversion match, and the\n  recomputed decision (`fresh` never trusts a stored token).\n- **Protocol** (instruction-graded, deliberately): that the sweep actually ran\n  at the pinned clone against this paper. The gate raises the bar —\n  structural floor (a report must name its adjudicator and carry a coverage\n  map), stale-report mtime guard — and that is where it stops. There is no\n  cryptographic binding between the report and the paper, deliberately: this is\n  a research-workflow gate, not a provenance system, and the honest statement is\n  that a determined executor can hand it a stale report. Likewise `human:` \u002F `checker:` \u002F `cross-family-review:` labels are\n  accountability, not authentication: a false label is an explicit,\n  permanent false record.\n- **Out of scope**: a party rewriting the `.aris\u002F` artifacts consistently with\n  shell access has owner power (they could delete the directory outright).\n  The gate defends against the sloppy or corner-cutting executor and against\n  honest crashes\u002Fraces\u002Fresumes — not against the machine's owner.\n\n## Pin-bump checklist (maintainers)\n\n1. Set the new `ANTI_AR_COMMIT`; delete no markers (the eval gate re-runs\n   automatically for the new SHA).\n2. Diff upstream's `schemas\u002Freport.schema.json` + verdict vocabulary against\n   the gate's policy table; extend `tools\u002Fforensics_gate.py` BEFORE bumping if\n   they moved.\n3. Old findings\u002Fobligations stay valid (fingerprints are span\u002Fhash-based, not\n   id-based) — but findings produced by an older adjudicator must be\n   **re-audited, not re-adjudicated** (upstream's own migration rule).\n4. Tell users when a bump changes how much they must disposition. `fresh`\n   rejects every stored `gate.json` at the old pin with `PIN_MISMATCH`, so a\n   bump already forces a re-sweep for everyone — bundle upstream changes behind\n   ONE bump rather than two, or the re-sweep cost is paid twice.\n\n> **2026-08 bump (`98a75fc`) — expect more open obligations.** Upstream moved\n> from adjudicating proposals to reporting them: findings its FP-risk,\n> observability, surface and needs-external-check gates used to demote to `info`\n> now arrive above info, so they open obligations. Nothing got worse in the\n> paper; more of what the auditors said is now visible. Waiving a proposal you\n> judge wrong is the expected disposition, and the report's per-finding columns\n> (`Anchored`, `Observability`, `FP-risk`, `Surface`, `Ext-check`) are what you\n> weigh. Upstream also deleted its report self-binding hashes in the same window\n> — nothing here ever consumed them.\n\n## Codex-native note (mirror)\n\nUpstream ships no Codex-native pack; its auditor skills are Claude-Code\ncontracts. A Codex-native session may run upstream's **deterministic-only\nmode** (numeric core + adjudicator with an all-`review_unavailable` coverage\nmap — honestly scoped: it can flag, it can never say CLEAN). The full\nnine-dimension sweep requires a host that can execute upstream's Claude-Code\ncontracts unchanged — Claude Code and the `dsh-aris` bundle on DeepSeek Harness\nare the known ones. Translating upstream's\nreviewer calls into `spawn_agent` on the fly is REWRITING an upstream\ncontract — forbidden.\n\n## Review tracing\n\nUpstream saves its own per-dimension traces under the paper's\n`.aris\u002Ftraces\u002F`. The launcher adds only the `.aris\u002Fforensics\u002F` artifacts:\n`gate.json` (pins `anti_ar_commit` + report\u002Fledger hashes + the paper-text\nfingerprint), `obligations.json` (the append-only ledger), and\n`last_report.json` (the sha-verified archive of the folded report that\n`fresh` recomputes from).\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25},"Bash(*), Read, Write, Grep, Glob, mcp__codex__codex","[paper-dir | pdf | arxiv-id]","main","18193d71ea3441d7c033dbf195b8a7c75ac96f75","packages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fintegrity-forensics",0,"https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science","https:\u002F\u002Fgithub.com\u002FCZX-LBJ","一个没事喜欢随便写点代码的小菜鸡\r\n","2026-10-22 09:48:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add CZX-LBJ\u002Fdeepseek-science --skill integrity-forensics",{"tool":40,"command":41},"bunx","bunx skills add CZX-LBJ\u002Fdeepseek-science --skill integrity-forensics",{"tool":43,"command":44},"pnpm","pnpm dlx skills add CZX-LBJ\u002Fdeepseek-science --skill integrity-forensics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fintegrity-forensics\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7FEEKSNMRMKW6JEK93PFDFY","bio-free-energy-calculations","Performs alchemical free-energy calculations including relative binding free energy (RBFE \u002F FEP+) and absolute binding free energy (ABFE) via OpenFE, FEP+, GROMACS, AMBER pmemd, and OpenMM with explicit lambda scheduling, soft-core potentials, MBAR\u002FBAR analysis, cycle-closure validation, and protocol-appropriate enhanced sampling. Compares ML alternatives (Boltz-2 affinity, DeepDock). Use when ranking analogs by binding affinity beyond docking accuracy, performing prospective lead optimization, or validating SAR predictions.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Fbioskills\u002Fchemoinformatics\u002Ffree-energy-calculations\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7FEE5CTE5QK55CEMXNNVWY9","bio-conformer-generation","Generates 3D conformer ensembles using RDKit ETKDGv3 with knowledge-enhanced distance geometry, MMFF94\u002FUFF force-field optimization, CREST + GFN2-xTB semi-empirical refinement, and macrocycle-aware torsion preferences. Provides explicit decision rules for single vs ensemble conformer use, RMSD pruning, energy windows, conformer count, and force-field choice. Use when preparing 3D ligands for docking, generating descriptor input for 3D QSAR, or sampling macrocycle\u002Fpeptide conformational ensembles.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Fbioskills\u002Fchemoinformatics\u002Fconformer-generation\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7FEDNGFEMFWD1MSEDR5H7CY","bio-admet-prediction","Predicts ADMET properties using ADMETlab 3.0 (119 platform features, including 77 prediction models with modeled-endpoint uncertainty), ADMET-AI, DeepChem MolNet, and chemprop D-MPNN with explicit handling of OECD QSAR principles, applicability domain assessment, calibration, hERG\u002FCYP\u002FAMES endpoints, and PAINS \u002F Lipinski \u002F Ro5 \u002F Veber \u002F BBB druglikeness filters. Use when filtering compounds for drug-likeness, prioritizing leads by predicted safety, or building an in-house ADMET QSAR model.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Fbioskills\u002Fchemoinformatics\u002Fadmet-prediction\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7FED69GFB54FRF7AV5066DN","writing-systems-papers","Paragraph-level structural blueprint for 10-12 page systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys. Provides page allocation, paragraph templates, and writing patterns. Use when user says \"写系统论文\", \"systems paper structure\", \"OSDI paper\", \"SOSP paper\", or wants fine-grained structural guidance for a systems conference submission.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fwriting-systems-papers\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7FECVVDWZ0X0VEDTCE4B4DZ","wiki-enrich","Fill in the per-paper TODO sections of research-wiki\u002Fpapers\u002F\u003Cslug>.md pages that literature-ingest skills leave as bare scaffolds. Use when user says 'enrich wiki', 'fill paper TODOs', 'wiki body 補完', '把 paper 摘要寫進 wiki', 'research-wiki 自動填', or after a batch ingest that left papers\u002F as TODO scaffolds.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fwiki-enrich\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7FECD4BCJ2MTSBDDSE3ZAJ5","web-debug-search","Search GitHub, Stack Exchange, Chinese technical communities, official documentation, and general developer web sources for software errors, compatibility problems, API usage questions, and real-world workarounds. Use for debugging and discovery only; results are not paper-citation evidence.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fweb-debug-search\u002FSKILL.md",[],[]]