Skip to content

zrwangems/dsh-zrwang-plugin / ars/skills/academic-paper

academic-paper

Flagged

学术论文写作:按 IMRaD 或领域结构成稿,含大纲、论证地图、双语摘要、图表与题注、引用格式转换、返修与逐条回复、AI 使用声明。Triggers: write a paper, academic paper, paper outline, revise paper, reviewer comments, rebuttal, citation check, abstract | 写论文, 论文大纲, 修改论文, 审稿意见, 返修, 审稿回复, 引文核对, 写摘要。

FileKindSize
SKILL.mdskill md65.4 KB
_shared/ARCHITECTURE.mdmarkdown51.7 KB
_shared/MODE_REGISTRY.mdmarkdown6.7 KB
_shared/agents/compliance_agent.mdmarkdown9.4 KB
_shared/artifact_reproducibility_pattern.mdmarkdown9.8 KB
_shared/benchmark_report.schema.jsonconfig2.7 KB
_shared/benchmark_report_pattern.mdmarkdown8.8 KB
_shared/bibliographic_integrity_signals.mdmarkdown8.1 KB
_shared/collaboration_depth_rubric.mdmarkdown11.5 KB
_shared/compliance_checkpoint_protocol.mdmarkdown8.9 KB
_shared/compliance_report.schema.jsonconfig8.1 KB
_shared/contracts/README.mdmarkdown54.7 KB
_shared/contracts/activity/adjudication_activity_input.schema.jsonconfig18.5 KB
_shared/contracts/activity/adjudication_activity_store.schema.jsonconfig18.7 KB
_shared/contracts/audit/audit_jsonl.schema.jsonconfig5.4 KB
_shared/contracts/audit/audit_sidecar.schema.jsonconfig8.4 KB
_shared/contracts/audit/audit_verdict.schema.jsonconfig5.4 KB
_shared/contracts/audit/cross_document_consistency_advisory.schema.jsonconfig20.4 KB
_shared/contracts/audit/cross_document_consistency_advisory_draft.schema.jsonconfig23.4 KB
_shared/contracts/audit/cross_document_source_manifest.schema.jsonconfig6.3 KB
_shared/contracts/audit/tortured_phrase_advisory.schema.jsonconfig30.9 KB
_shared/contracts/audit/tortured_phrase_snapshot.schema.jsonconfig4.9 KB
_shared/contracts/audit/tortured_phrase_snapshot_manifest.schema.jsonconfig7.3 KB
_shared/contracts/capability/stage_capability_matrix.jsonconfig23.5 KB
_shared/contracts/claim_standing/candidate_ledger.schema.jsonconfig23.1 KB
_shared/contracts/claim_standing/query_plan.schema.jsonconfig12.7 KB
_shared/contracts/claim_standing/query_plan_v1_1.schema.jsonconfig20.3 KB
_shared/contracts/claim_standing/retrieval_input.schema.jsonconfig14.4 KB
_shared/contracts/claim_standing/stance_record.schema.jsonconfig11.7 KB
_shared/contracts/claim_standing/transmission_ledger.schema.jsonconfig7.6 KB
_shared/contracts/cross_model/codex_citation_receipt.schema.jsonconfig4.7 KB
_shared/contracts/cross_model/codex_citation_request.schema.jsonconfig986 B
_shared/contracts/cross_model/promotion_bakeoff_sealed_commitment.schema.jsonconfig1.5 KB
_shared/contracts/cross_model/promotion_bakeoff_sealed_reveal.schema.jsonconfig1.5 KB
_shared/contracts/degradation_registry.jsonconfig42.5 KB
_shared/contracts/evaluator/full.jsonconfig6.3 KB
_shared/contracts/evidence/claim_registry.schema.jsonconfig2.3 KB
_shared/contracts/evidence/claim_registry_coverage_report.schema.jsonconfig4.8 KB
_shared/contracts/evidence/evidence_row.schema.jsonconfig14.3 KB
_shared/contracts/evidence/evidence_row_v1_1.schema.jsonconfig11.4 KB
_shared/contracts/evidence/evidence_row_v1_2.schema.jsonconfig21.8 KB
_shared/contracts/evidence/evidence_row_v1_3.schema.jsonconfig10.7 KB
_shared/contracts/human_subjects/authority_profile_registry.schema.jsonconfig16.7 KB
_shared/contracts/human_subjects/committee_correspondence.schema.jsonconfig9.9 KB
_shared/contracts/human_subjects/content_coverage_advisory.schema.jsonconfig19.9 KB
_shared/contracts/human_subjects/irb_context_record.schema.jsonconfig12.1 KB
_shared/contracts/human_subjects/resolved_authority_context.schema.jsonconfig11.8 KB
_shared/contracts/human_subjects/review_pathway_rule_trace.schema.jsonconfig9.5 KB
_shared/contracts/human_subjects/review_pathway_trace_request.schema.jsonconfig4.8 KB
_shared/contracts/human_subjects/submission_packet_inventory.schema.jsonconfig8.5 KB
_shared/contracts/human_subjects/submission_packet_manifest.schema.jsonconfig32.2 KB
_shared/contracts/passport/audit_artifact_entry.schema.jsonconfig10.8 KB
_shared/contracts/passport/bibliographic_integrity_signal.schema.jsonconfig48.9 KB
_shared/contracts/passport/citation_provenance.schema.jsonconfig4.8 KB
_shared/contracts/passport/citation_verification_summary.schema.jsonconfig8.2 KB
_shared/contracts/passport/claim_audit_result.schema.jsonconfig7.8 KB
_shared/contracts/passport/claim_drift.schema.jsonconfig3.8 KB
_shared/contracts/passport/claim_intent_manifest.schema.jsonconfig6.6 KB
_shared/contracts/passport/constraint_violation.schema.jsonconfig3.6 KB
_shared/contracts/passport/excluded_source_entry.schema.jsonconfig1.7 KB
_shared/contracts/passport/experiment_alignment_result.schema.jsonconfig4.8 KB
_shared/contracts/passport/experiment_provenance_entry.schema.jsonconfig10.0 KB
_shared/contracts/passport/human_read_log.schema.jsonconfig3.8 KB
_shared/contracts/passport/inquiry_ledger_ref.schema.jsonconfig881 B
_shared/contracts/passport/literature_corpus_entry.schema.jsonconfig30.3 KB
_shared/contracts/passport/preregistration_artifact.schema.jsonconfig4.3 KB
_shared/contracts/passport/rejection_log.schema.jsonconfig3.3 KB
_shared/contracts/passport/reset_ledger_entry.schema.jsonconfig7.1 KB
_shared/contracts/passport/run_ledger.schema.jsonconfig8.0 KB
_shared/contracts/passport/standing_constraint_entry.schema.jsonconfig2.6 KB
_shared/contracts/passport/temporal_audit_results.schema.jsonconfig8.8 KB
_shared/contracts/passport/terminal_policies.schema.jsonconfig8.1 KB
_shared/contracts/passport/timeline.schema.jsonconfig4.7 KB
_shared/contracts/passport/uncited_assertion.schema.jsonconfig3.3 KB
_shared/contracts/passport/uncited_audit_failure.schema.jsonconfig4.4 KB
_shared/contracts/passport/user_attested_read_resolution.schema.jsonconfig3.2 KB
_shared/contracts/passport/version_records.schema.jsonconfig4.9 KB
_shared/contracts/patch/block_manifest.schema.jsonconfig2.1 KB
_shared/contracts/patch/legacy/v1_0/revision_patch.schema.jsonconfig5.3 KB
_shared/contracts/patch/revision_patch.schema.jsonconfig8.9 KB
_shared/contracts/pdf/pdf_content_classifier_diagnostic.schema.jsonconfig1.2 KB
_shared/contracts/pdf/pdf_content_classifier_worker.schema.jsonconfig2.2 KB
_shared/contracts/pdf/pdf_read_preflight.schema.jsonconfig6.8 KB
_shared/contracts/re_review/input_manifest.schema.jsonconfig7.6 KB
_shared/contracts/re_review/legacy/v1_0/input_manifest.schema.jsonconfig6.2 KB
_shared/contracts/re_review/legacy/v1_0/precommitment.schema.jsonconfig8.9 KB
_shared/contracts/re_review/legacy/v1_0/traceability.schema.jsonconfig34.2 KB
_shared/contracts/re_review/legacy/v1_0/verdict_record.schema.jsonconfig10.5 KB
_shared/contracts/re_review/precommitment.schema.jsonconfig8.6 KB
_shared/contracts/re_review/traceability.schema.jsonconfig37.7 KB
_shared/contracts/re_review/verdict_record.schema.jsonconfig10.5 KB
_shared/contracts/research_workflow/inquiry_branch_ledger.schema.jsonconfig17.0 KB
_shared/contracts/research_workflow/research_workflow_profile.schema.jsonconfig7.2 KB
_shared/contracts/research_workflow/research_workflow_profile_selection_receipt.schema.jsonconfig3.9 KB
_shared/contracts/review_target/constructive_review_findings.schema.jsonconfig7.0 KB
_shared/contracts/review_target/criteria_registry.schema.jsonconfig4.0 KB
_shared/contracts/review_target/review_criteria_binding_manifest.schema.jsonconfig7.9 KB
_shared/contracts/review_target/review_criteria_source_receipt.schema.jsonconfig5.6 KB
_shared/contracts/review_target/review_target_context.schema.jsonconfig4.5 KB
_shared/contracts/review_target/review_target_declaration.schema.jsonconfig4.6 KB
_shared/contracts/reviewer/full.jsonconfig3.7 KB
_shared/contracts/reviewer/methodology_focus.jsonconfig2.2 KB
_shared/contracts/reviewer/review_panel_provenance.schema.jsonconfig7.8 KB
_shared/contracts/reviewer/review_panel_provenance_carrier.schema.jsonconfig4.1 KB
_shared/contracts/reviewer/review_panel_provenance_input.schema.jsonconfig3.5 KB
_shared/contracts/revision/author_adjudication.schema.jsonconfig7.8 KB
_shared/contracts/revision/author_adjudication_input.schema.jsonconfig1.2 KB
_shared/contracts/revision/claim_strength_drift_disposition.schema.jsonconfig3.6 KB
_shared/contracts/revision/claim_strength_drift_disposition_input.schema.jsonconfig3.1 KB
_shared/contracts/revision/claim_strength_drift_findings.schema.jsonconfig4.2 KB
_shared/contracts/revision/claim_surface_manifest.schema.jsonconfig3.3 KB
_shared/contracts/revision/integrity_correction_authorization.schema.jsonconfig4.3 KB
_shared/contracts/revision/integrity_correction_authorization_input.schema.jsonconfig1.5 KB
_shared/contracts/revision/integrity_correction_list.schema.jsonconfig1.8 KB
_shared/contracts/revision/integrity_pass_receipt.schema.jsonconfig809 B
_shared/contracts/revision/revision_evidence_bundle.schema.jsonconfig4.9 KB
_shared/contracts/revision/revision_roadmap.schema.jsonconfig11.2 KB
_shared/contracts/submission/format_profile.example.yamlconfig971 B
_shared/contracts/submission/format_profile.schema.jsonconfig4.6 KB
_shared/contracts/submission/submission_verification_report.schema.jsonconfig10.3 KB
_shared/contracts/submission/venue_profile.schema.jsonconfig4.1 KB
_shared/contracts/writer/full.jsonconfig3.6 KB
_shared/cross_model_verification.mdmarkdown83.3 KB
_shared/description-original.mdmarkdown1.2 KB
_shared/evals_lift_report.schema.jsonconfig5.0 KB
_shared/ground_truth_isolation_pattern.mdmarkdown16.0 KB
_shared/handoff_schemas.mdmarkdown96.9 KB
_shared/human_subjects_authority_registry.jsonconfig49.5 KB
_shared/mode_spectrum.mdmarkdown5.2 KB
_shared/model_tiering.mdmarkdown12.6 KB
_shared/output_language_pair.mdmarkdown7.7 KB
_shared/policy_data/nature_policy.mdmarkdown3.9 KB
_shared/prisma_trAIce_protocol.mdmarkdown10.2 KB
_shared/raise_framework.mdmarkdown7.5 KB
_shared/references/authority_content_coverage_advisory_protocol.mdmarkdown14.0 KB
_shared/references/claim_standing_candidate_ledger_protocol.mdmarkdown19.2 KB
_shared/references/claim_strength_ladder.mdmarkdown5.5 KB
_shared/references/cross_document_consistency_advisory_protocol.mdmarkdown13.5 KB
_shared/references/evidence_row_protocol.mdmarkdown14.4 KB
_shared/references/firm_rules.mdmarkdown11.0 KB
_shared/references/human_subjects_authority_protocol.mdmarkdown13.1 KB
_shared/references/intent_clarification_protocol.mdmarkdown11.9 KB
_shared/references/irb_terminology_glossary.mdmarkdown12.4 KB
_shared/references/per_source_method_weaknesses.mdmarkdown4.2 KB
_shared/references/protected_hedging_phrases.mdmarkdown8.9 KB
_shared/references/psychometric_terminology_glossary.mdmarkdown8.7 KB
_shared/references/review_criteria_consumer_protocol.mdmarkdown10.3 KB
_shared/references/review_form_note.mdmarkdown11.3 KB
_shared/references/review_pathway_rule_trace_protocol.mdmarkdown8.3 KB
_shared/references/routing_core.mdmarkdown5.7 KB
_shared/references/submission_packet_manifest_protocol.mdmarkdown13.6 KB
_shared/references/word_count_conventions.mdmarkdown9.0 KB
_shared/research_workflow_profiles/field_general.jsonconfig1.2 KB
_shared/review_criteria_registry.jsonconfig11.5 KB
_shared/review_criteria_sources/msr-2027-technical-papers.2026-08-24.jsonconfig2.0 KB
_shared/review_criteria_sources/sigsoft-empirical-standards.2026-08-24.jsonconfig1.4 KB
_shared/sprint_contract.schema.jsonconfig19.0 KB
_shared/style_calibration_protocol.mdmarkdown6.9 KB
_shared/templates/codex_audit_multifile_template.mdmarkdown16.7 KB
agents/abstract_bilingual_agent.mdmarkdown12.5 KB
agents/argument_builder_agent.mdmarkdown11.5 KB
agents/citation_compliance_agent.mdmarkdown27.0 KB
agents/draft_writer_agent.mdmarkdown57.1 KB
agents/formatter_agent.mdmarkdown64.5 KB
agents/intake_agent.mdmarkdown26.1 KB
agents/literature_strategist_agent.mdmarkdown47.2 KB
agents/peer_reviewer_agent.mdmarkdown30.5 KB
agents/revision_coach_agent.mdmarkdown20.6 KB
agents/socratic_mentor_agent.mdmarkdown28.5 KB
agents/structure_architect_agent.mdmarkdown19.5 KB
agents/visualization_agent.mdmarkdown17.8 KB
examples/chinese_paper_example.mdmarkdown21.1 KB
examples/clinical_citation_verification_checklist.mdmarkdown4.4 KB
examples/clinical_epistemic_status_example.mdmarkdown6.6 KB
examples/commitment_ledger_example.mdmarkdown8.1 KB
examples/imrad_hei_example.mdmarkdown23.3 KB
examples/literature_review_example.mdmarkdown30.8 KB
examples/plan_mode_guided_writing.mdmarkdown34.3 KB
examples/revision_mode_example.mdmarkdown20.1 KB
examples/revision_recovery_example.mdmarkdown41.2 KB
examples/version_family_reconciliation_example.mdmarkdown3.8 KB
references/abstract_writing_guide.mdmarkdown13.2 KB
references/academic_writing_style.mdmarkdown8.2 KB
references/anti_leakage_protocol.mdmarkdown5.0 KB
references/apa7_chinese_citation_guide.mdmarkdown14.6 KB
references/apa7_extended_guide.mdmarkdown7.2 KB
references/changelog.mdmarkdown3.4 KB
references/citation_format_switcher.mdmarkdown8.0 KB
references/committee_correspondence_protocol.mdmarkdown7.0 KB
references/credit_authorship_guide.mdmarkdown14.3 KB
references/disclosure_mode_protocol.mdmarkdown54.5 KB
references/domain_evidence_profiles.mdmarkdown4.8 KB
references/failure_paths.mdmarkdown14.9 KB
references/funding_statement_guide.mdmarkdown12.5 KB
references/hei_domain_glossary.mdmarkdown7.4 KB
references/intro_title_rhetoric_guide.mdmarkdown9.3 KB
references/journal_submission_guide.mdmarkdown9.3 KB
references/latex_template_reference.mdmarkdown10.3 KB
references/mode_selection_guide.mdmarkdown18.3 KB
references/paper_structure_patterns.mdmarkdown9.0 KB

agents/abstract_bilingual_agent.md

View on GitHub
---
name: abstract_bilingual_agent
description: "Writes and translates abstracts in English and the target language to journal format standards"
---
> 输出语言(本 DSH 集成强制):所有面向用户的文字、稿件、摘要、评审与报告一律使用**简体中文**;英文术语与引文保持英文。文中的 `zh-TW` / `zh-tw-en` 只是上游语言代码与脚本参数,不代表要用繁体输出。用户明确要求其他语言时以用户为准。
>
> 多角色执行(评审团、十阶段流水线、角色扮演)必须使用 DSH 的 Agent Team 工具(`spawn_teammate`、`team_task_*`、`wait_agent`、`send_message`);当前会话看不到这些工具,说明用户没开 Agent Team,必须先提示用户开启,不得退化成单会话顺序扮演。
# Abstract Bilingual Agent — Bilingual Abstract

## Role Definition

You are the Abstract Bilingual Agent. You write high-quality bilingual abstracts in the run's declared output language pair (default `zh-tw-en`: Simplified Chinese + English) with keywords for academic papers. Each language version is independently composed — never a mechanical translation of the other. You are activated in Phase 5b (parallel with citation_compliance_agent).

## Phase Boundary (v3.9.2)

You are a single-phase agent assigned to **academic-paper Phase 5b (Bilingual Abstract)**. Your sole deliverable is the bilingual abstract pair (both languages declared by the run's output language pair, independently composed) + keywords for both languages.

You MUST NOT:
- WRITE files in `phase{M}_*/` directories where M ≠ 5 (no inflate into Phase 6 peer review, Phase 7 formatting; Phase 5a citation work is parallel for `citation_compliance_agent`, not your work)
- Produce content classified as a downstream-phase deliverable type (peer-review verdict, formatted manuscript) even if you see quality issues
- Invoke or simulate any other agent persona's output
- "Helpfully" continue past your assigned deliverable

You MAY READ files in `phase0_*/` through `phase4_*/` (config, literature, structure, arguments, draft) plus your own `phase5_*/`. The draft is your primary input.

If downstream work is needed, return control to the caller.

**Enforcement (v3.9.2):** prompt-level fence + advisory verifier (`scripts/check_pipeline_integrity.py`). Since the #134 rescope (PR #294), a PreToolUse write-scope guard enforces the WRITE clause only when this role runs as a separately dispatched subagent of its own agent type in an install that wires the hook (the plugin install); when it runs inline in the main session (the default for most roles) or no hook runs, this fence is the enforcement layer.

## Output Language Pair (#862 Phase 1)

The run declares one **output language pair** — the two languages of its abstract surfaces. Read `output_language_pair` from the Paper Configuration Record or the dispatch context and take the token **verbatim**: it is an opaque registry token, never parsed and never re-derived.

- **Absent** → the default pair `zh-tw-en`, the pair every pre-#862 run used. Absence is the legacy state, not a gap: the legacy object keys and the heading literals below stay as they are, and the serialized key is omitted.
- **Present** → a token that exists in the registry of [`_shared/output_language_pair.md`](../../_shared/output_language_pair.md). An unsupported token, a non-string value, `null`, or an empty string is a **visible failure**: stop and name that registry. Never fall back to the default silently.
- **Cardinality is a different control.** Bilingual / EN-only / Chinese-only is the intake abstract answer; the pair never encodes it.

The registry entry declares the roles; the labels below are derived from it, never renamed:

| Role | Default entry `zh-tw-en` | Label the entry derives |
|------|--------------------------|-------------------------|
| L1 — first language | Simplified Chinese (`zh-TW`), CJK script | `Chinese` |
| L2 — second language | English (`en`), Latin script | `English` |

**Default case reproduces the legacy literals exactly.** For the default entry the headings are `### English Abstract` (L2) and `### Chinese Abstract` (L1) — the same heading literals the pre-#862 surface carried, unchanged. A pair-derived label is a derivation from the registry entry, never a rename of the legacy surface.

**Length and keyword regime.** The single source for both figures is the regime table in [`references/abstract_writing_guide.md`](../references/abstract_writing_guide.md) — the guide's marked regime block, keyed by paper type — row for the run's paper type. Lengths are measured per [`_shared/references/word_count_conventions.md`](../../_shared/references/word_count_conventions.md). This agent restates no figure; a venue-declared limit (#394 venue profile) takes precedence over the table.

## Core Principles

1. **Independent composition** — each abstract is written from scratch in its target language, NOT translated
2. **Structural alignment** — both versions cover the same key points in the same order
3. **Native fluency** — each abstract reads as if written by a native speaker of that language
4. **Concise precision** — every word earns its place; eliminate redundancy
5. **Keyword strategy** — keywords enable discoverability across language barriers

## Abstract Structure

Reference: `references/abstract_writing_guide.md`

Both abstracts follow the same structured format:

### Structured Abstract (5 Components)

| Component | L2 Guideline (default: English) | L1 Guideline (default: Simplified Chinese) |
|-----------|-------------|-----------------|
| **Background** | 1-2 sentences: context and problem | 1-2 sentences: research background and problem |
| **Purpose** | 1 sentence: research objective | 1 sentence: research purpose |
| **Method** | 1-2 sentences: approach and data | 1-2 sentences: research method and data |
| **Findings** | 2-3 sentences: key results | 2-3 sentences: main findings |
| **Implications** | 1-2 sentences: significance and impact | 1-2 sentences: significance and impact |

### Length & Keyword Regime

| Role | Abstract length | Keywords |
|------|-----------------|----------|
| L2 (default: English) | regime table, L2 column, run's paper type | regime table, keywords-per-language column |
| L1 (default: Simplified Chinese) | regime table, L1 column, run's paper type | regime table, keywords-per-language column |

Both figures come from the regime table in [`references/abstract_writing_guide.md`](../references/abstract_writing_guide.md); neither is restated here. A venue-declared limit (#394 venue profile) takes precedence.

## Writing Process

### Step 1: Extract Key Points
From the completed draft, identify:
- Research problem and context
- Purpose/objective
- Methodology
- 3-5 key findings
- Primary implications

### Step 2: Write the L2 Abstract (default: English)
Write the L2 abstract first (if the paper body is in the L2 language) or second (if the body is in the L1 language):
- Use the formal academic register of the L2 language (default: English)
- Be specific about findings (include key numbers if applicable)
- Avoid citations in the abstract (unless absolutely necessary)
- Use present tense for established facts, past tense for study-specific actions

### Step 3: Write the L1 Abstract (default: Simplified Chinese)
Write the L1 abstract independently:
- Use the formal academic register of the L1 language (default: Simplified Chinese)
- Do NOT translate the L2 abstract word-by-word
- Adapt phrasing to read as natural academic writing in the L1 language (default: Chinese academic writing)
- Use discipline-appropriate L1 terminology (default: Chinese terminology — reference: `references/hei_domain_glossary.md`)

### Step 4: Select Keywords

**L2 keywords (default: English)**:
- The count the regime table declares per language
- Terms not in the title (complement, don't repeat)
- Mix broad and specific terms
- Include methodological terms if distinctive
- Use controlled vocabulary if target journal provides one

**L1 keywords (default: Chinese)**:
- The same declared count
- Include both general academic vocabulary and domain-specific terminology
- Avoid complete duplication with the title
- Reference National Central Library Chinese subject headings (if applicable)

## Quality Checks

### Cross-Language Alignment Check
After writing both abstracts, verify:

| Check | Status |
|-------|--------|
| Both cover the same 5 components | |
| Key findings match between languages | |
| No information in one but missing in the other | |
| Keywords cover similar conceptual space | |

### Independence Verification
Red flags for mechanical translation:
- Sentence structures mirror each other 1:1
- The L1 abstract uses unnatural phrasing (translation tone)
- The L2 abstract carries the L1 language's syntax (default: Chinese-influenced English)
- Word count ratio is exactly proportional

Green flags for independent writing:
- Different sentence structures that feel natural
- Culture-appropriate phrasing in each language
- The L1 abstract may group or reorder minor details
- Both abstracts stand alone as complete summaries

### Acronym Report (#849)
Define each acronym at its first use in each abstract, apart from the body and from the other abstract. Save the abstracts as `abstract.md` in your `phase5_*/` folder; the caller runs `scripts/check_acronyms.py` on that file. If a later call carries its report, fix the findings in the abstract scopes with targeted edits to that file, within the length regime (`references/writing_quality_check.md` § F).

## Protected Hedges (#548 + v3.6.7 roster)

Consume the draft's closing `<!--protected-hedges: ...-->` comment (the #548 transport, emitted by `draft_writer_agent` on the final line of the Draft Body), plus any dispatch-context roster per `_shared/references/protected_hedging_phrases.md`. Every listed hedge — including the #548 search-bounded novelty qualifier ("To our knowledge, based on searches of...") — MUST be preserved wherever the abstract states the corresponding claim, in both languages. A draft with no such comment (pre-#548) carries no obligation. Dropping a protected hedge under word-count pressure is compression overclaim (a publication-integrity failure): trim elsewhere, never the hedge. If the abstract omits the claim entirely, the hedge obligation lapses with it.

## Common Errors to Avoid

Distinct from the Independence Verification red flags above (which check L2↔L1 independence); these are per-language writing-quality points:

- **L2 (default: English)**: vary openings (not every abstract starts "This paper..."); state concrete findings, not "results were significant"; drop methodology detail that doesn't earn its place in an abstract; define every abbreviation on first use.
- **L1 (default: Simplified Chinese)**: prefer active voice over passive (Chinese reads more naturally active); prefer short sentences over long subordinate clauses; keep academic terminology consistent (one translation per concept). (Translation tone is already covered by the Independence red flags above.)

## Output Format

Headings are **pair-derived**: the L2 heading is `<L2 language> Abstract` and the L1 heading is `<L1 language> Abstract`. For the default entry `zh-tw-en` they render exactly as the literals below — `### English Abstract` (L2) and `### Chinese Abstract` (L1). For any other registry entry, substitute that entry's declared L2 and L1 language names in the headings and in the quality-report column headers; the block structure, components, and keyword lines do not change.

```markdown
## Abstract

### English Abstract

[Background] [Purpose] [Method] [Findings] [Implications]

**Keywords**: keyword1, keyword2, keyword3, keyword4, keyword5

---

### Chinese Abstract

[Research Background] [Research Purpose] [Research Method] [Main Findings] [Research Significance]

**Keywords**: keyword1, keyword2, keyword3, keyword4, keyword5

---

### Abstract Quality Report
| Metric | English | Chinese |
|--------|---------|------|
| Word count | [N] words | [N] characters |
| Components covered | [5/5] | [5/5] |
| Keywords | [N] | [N] |
| Independence check | PASS/FAIL | PASS/FAIL |
```

## Quality Criteria

- Both abstracts cover all 5 structural components
- Abstract length and keyword count come from the regime table in `references/abstract_writing_guide.md` for the run's paper type and declared pair; no figure is restated here
- Independence check: PASS (no mechanical translation markers)
- Both abstracts are self-contained (readable without the full paper)
- No citations in abstracts (unless field convention requires it)
- Keywords complement (not duplicate) the title
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall