zrwangems/dsh-zrwang-plugin / ars/skills/academic-pipeline
academic-pipeline
Flagged学术研究总编排:研究→写作→诚信检查→评审→返修→复审→终检→定稿的十阶段流水线,每阶段停在用户确认点,含材料护照与 7 类 AI 研究失败模式检查。Triggers: academic pipeline, research to paper, full paper workflow, end-to-end paper | 完整论文流程, 从研究到论文, 端到端写论文, 论文流水线。
_shared/references/claim_strength_ladder.md
View on GitHub> 输出语言(本 DSH 集成强制):所有面向用户的文字、稿件、摘要、评审与报告一律使用**简体中文**;英文术语与引文保持英文。文中的 `zh-TW` / `zh-tw-en` 只是上游语言代码与脚本参数,不代表要用繁体输出。用户明确要求其他语言时以用户为准。
>
> 多角色执行(评审团、十阶段流水线、角色扮演)必须使用 DSH 的 Agent Team 工具(`spawn_teammate`、`team_task_*`、`wait_agent`、`send_message`);当前会话看不到这些工具,说明用户没开 Agent Team,必须先提示用户开启,不得退化成单会话顺序扮演。
# Claim-Strength Ladder
**Issue:** #569. **External motivation:** DELEGATE-52 (arXiv:2604.15597) — round-trip
document editing corrupts scientific content by *subtle modification, not deletion*.
#390's block-anchored patch confines that exposure to touched blocks; this reference
governs the epistemic dimension *inside* a touched block, which the patch mechanism
does not check. Mechanism shape borrowed from
[Yila-AI/sci-ssci-skills](https://github.com/Yila-AI/sci-ssci-skills) by
@MissOrangePeel (`sci-ssci-polishing`, `references/invariants.md`).
**Epistemic status:** the field-relative ladder remains advisory / interpretive
guidance. Since #670, exact claim surfaces that were explicitly registered and
hash-bound are mechanically preserved or replaced only by exact author-approved
bytes in current patch 1.1; the runtime does not infer a rung from prose and does
not detect unregistered semantic movement. E6 therefore remains mandatory for
unregistered prose. The deterministic sibling `#570` separately conserves
numbers and citation tokens; see `scripts/check_revision_token_conservation.py`.
## The ladder
Epistemic claims sit on an ordered strength scale. Revision must never move a claim
along it **silently** — in either direction — without an authorizing roadmap item.
```
is consistent with / may suggest
< is associated with / relates to / correlates with
< predicts
< contributes to
< affects / influences / leads to / shapes
< causes / determines / demonstrates that / proves
```
The exact ordering varies by field (a clinical "predicts" and an econometric
"predicts" are not identical), so the operative rule is **"no silent move,"** not
one universal ordering. When unsure whether two phrasings occupy the same rung,
treat them as different rungs and preserve the source.
## What counts as a move (and what does not)
A **move** — requires authorization:
- `associated with` → `leads to` / `reduces` / `drives` / `causes` (up)
- `may support` / `might improve` → `supports` / `improves` (drop of a modal hedge = up)
- `predicts` → `is associated with` (down — silently *weakening* misrepresents the
author just as much as strengthening; bidirectional by design)
- deleting a design-based causal caveat ("the observational design cannot establish
causation"), a scope hedge ("in this sample", "for this cohort"), a status hedge
("preliminary", "exploratory"), or a null/negative result
- re-attaching a background citation's claim to the current study's finding
NOT a move — no authorization needed:
- reordering a sentence while keeping the same verb and hedges
- foregrounding / positioning prose that adds emphasis WITHOUT changing the verb's
rung (e.g. stating the contribution is important, while the finding stays
"associated with")
- a description swap at the same rung ("narrows the range" ↔ "reduces the range")
- condensing prose that preserves every hedge and every claim's rung
## Load-bearing overlap with existing protections
- **Hedges.** `_shared/references/protected_hedging_phrases.md` protects hedges
against *compression* in abstract-only mode. The ladder extends the same concern
to *revision rounds* and adds the ordered scale that the phrase roster lacks. A
phrase already on a paper's `protected_hedges` list is a ladder invariant too.
- **Novelty.** #548 bounds *priority* language ("first study to…"); the ladder
governs *causal/evidential* strength. Disjoint concerns, same anti-overclaim family.
- **Numbers/citations.** #570 conserves numeric and citation *tokens*
deterministically; the ladder covers what token-matching cannot see (negation,
direction, modality, causal strength). The two are necessary-but-not-sufficient
complements, mirroring the v3.11 deterministic-gate / LLM-semantic split.
## Where this is consumed
- `draft_writer_agent` § Claim-Strength Ladder (#569) — revision mode: a patch op
touching a registered claim surface carries its exact #670 authorization when
movement is author-approved; unregistered surfaces remain explicit E6 scope.
- Stage 4.5 integrity audit — the audit vocabulary names the drift class so a
reviewer/gate can flag it; advisory rows only, never terminal.
- #672 cross-document consistency advisory — semantic callers may use the ladder
for field-relative abstract/results or discussion/results rung observations.
The deterministic finalizer implements no keyword matcher or numeric ranker;
the `LLM-ADVISORY` / `UNMEASURED` result grants no revision authority and
cannot change Stage 4.5 or Stage-5 routing.
## Measurement
The acceptance test for any change to this guidance is
`evals/heldout/revision_claim_drift/`. The 2026-07-22 baseline measured 2/8 = 25%
claim-strength/hedge drift on the current frontier model under hedge-drop and
null-reframe pressure — the evidence that this mechanism earns its place rather
than closing as documented-negative-scope. Model- and time-specific; re-run, don't
reuse.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |