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/dsh-runtime.mdmarkdown1.5 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

_shared/references/irb_terminology_glossary.md

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

**Spec:** v3.6.7 §7.1 — pattern-protection reference for
`research_architect_agent` (survey designer mode), Pattern B1.

**Audience:** Agents drafting participant-facing consent/privacy language and
human authors reviewing instrument drafts.

**Status:** This is an ARS operational drafting convention. It is not a legal
definition set, an authority-selection rule, or a review determination. A term
is usable only with its named governing authority/convention, actor boundary,
data state, and lifecycle. Different regimes can classify the same retained
re-link key differently.

**Why this exists:** Survey drafts often use Anonymity, Confidentiality,
De-identification, and Pseudonymization as if they were interchangeable. That
can make participant-facing statements inaccurate. This glossary keeps the
facts visible while exact authority requirements remain in
`_shared/human_subjects_authority_registry.json`.

---

## Record the Operational Facts First

Before choosing a term, record:

1. every actor that collects, receives, stores, or can access the data,
   including the survey platform, institution, research team, processors, and
   recipients;
2. direct identifiers, quasi-identifiers, free text, IP addresses, cookies,
   device identifiers, timestamps, contact fields, and other metadata;
3. whether a linkage/re-link key or other additional information is created,
   who holds it, who can access both sides, and when it is destroyed or becomes
   inaccessible;
4. the purpose, disclosure boundary, security controls, retention, deletion,
   reuse, transfer, publication, and withdrawal/deletion feasibility;
5. the exact governing authority, institutional rule, or technical release
   convention and the test it applies.

Before describing an IP address or other metadata as absent from the collected
record, verify the platform settings and actual data export/log behavior. If a
platform collects metadata that researchers cannot access, say both facts; do
not silently upgrade that scoped boundary to absolute anonymity.

---

## The Four Terms

### Anonymity

**ARS drafting convention (not a universal legal definition):** Within the
explicitly named actor and lifecycle boundary, no identity-response link is
created, retained, or reasonably recoverable. Use an absolute claim such as
"anonymous to everyone" only when the platform/provider and every downstream
actor are included in, and satisfy, that verified boundary.

**Operational facts to support the wording:**

- no direct identifier or respondent-specific contact field within the stated
  boundary;
- platform metadata collection and researcher access are stated accurately;
- no code, token, or key available within the boundary can reconnect identity
  and response;
- quasi-identifier and free-text re-identification risks have been assessed
  under a named project or institutional method.

**Illustrative drafting template — populate only verified facts:**

> "The research team does not ask for your name or contact details and cannot
> link the exported response to you. The survey platform [does/does not/has not
> been verified to] log IP addresses or device metadata; [state access,
> retention, and recipient details]."

**Drift to flag:** Calling a survey absolutely anonymous while collecting a
follow-up email, retaining a researcher-accessible response code, or leaving
platform metadata behavior unstated.

### Confidentiality

**ARS drafting convention (not a universal legal definition):** An identity or
identity-response link may exist, while one or more named actors commit to
bounded access, use, and disclosure. Confidentiality is a handling promise; it
does not mean identifiers were never collected.

**Operational facts to support the wording:**

- identity/linkage holders and access roles are named;
- purposes, recipients, exceptions/limits, and publication treatment are stated;
- security, retention, deletion, reuse, and incident procedures match the
  participant-facing promise.

**Illustrative drafting template — populate only verified facts:**

> "The research team will receive [identity/contact/linkage data]. Access is
> limited to [roles] for [purposes]. Identified data will be retained until
> [event/date] and then [verified disposition]. Reports will [describe actual
> aggregation, quotation, or identification practice]."

**Drift to flag:** Promising confidentiality without naming the actual
collectors/access roles or while the planned publication and retention behavior
contradicts the promise.

### De-identification

**Convention-bound working use:** Data has been transformed and evaluated under
a **named** authority, institutional standard, or technical release test. This
glossary does not define a universal point at which data becomes de-identified,
and key destruction is not a cross-regime definition.

**Operational facts to record:**

- the named convention/test and the dataset/lifecycle stage to which it applies;
- identifiers removed, transformed, retained, or separately held;
- quasi-identifier and auxiliary-data attack assumptions;
- any linkage/re-link code, custodian, access boundary, derivation, disclosure,
  and destruction/inaccessibility state;
- the method, evaluator, threshold, date, and residual-risk statement.

**Illustrative unprofiled authority example:** Under the U.S. HIPAA Privacy Rule,
[45 CFR 164.514(b)](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.514)
describes Expert Determination and Safe Harbor routes, while
[45 CFR 164.514(c)](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.514)
permits a covered entity to assign a re-identification code subject to stated
conditions. The effect of retaining a re-link key is therefore
convention-specific and cannot be classified portably. HIPAA is not a profile
in the current #666 registry; applicability and full requirements are
`unprofiled` here.

**Illustrative drafting template — populate the named convention and facts:**

> "For [dataset/lifecycle stage], the team applied [named de-identification
> convention/test] on [date]. [Identifiers and transformations]. A re-link code
> [does/does not] remain; it is held by [actor] under [access/disclosure
> conditions]. Residual risk was evaluated by [method/role] as [bounded result]."

**Drift to flag:** Saying only "identifiers were removed," omitting the governing
test, or assuming that the presence/absence of a key has the same legal effect
under every regime.

### Pseudonymization

**GDPR authority-specific definition:**
[GDPR Article 4(5)](https://eur-lex.europa.eu/eli/reg/2016/679/2016-05-04/eng)
defines pseudonymisation for personal data by reference to processing that
prevents attribution to a specific data subject without additional information,
provided that additional information is kept separately and protected by
technical and organisational measures. Because the definition concerns
personal data, pseudonymised data is not treated as anonymous merely because a
code replaced direct identifiers.

Article 4(5) is a definitional anchor, not a separate requirement row in the
current bounded registry. When the exact GDPR profile is selected and the
applicability facts resolve true,
`eu.gdpr.article-89.1.research-safeguards` points to the bounded Article 89(1)
research-safeguards row, which records that pseudonymisation is assessed where
the research purposes can be fulfilled that way. It does not assert that every
study or every other regime uses the GDPR definition.

**Operational facts to support GDPR-specific wording:**

- the pseudonym/substitution method and the additional information needed for
  attribution;
- separate holders, storage, and access controls;
- who can combine the dataset and additional information and for which purposes;
- retention/destruction state and technical/organisational safeguards.

**Illustrative drafting template — populate only verified facts:**

> "For the selected GDPR context, the working dataset is pseudonymised. Direct
> identifiers are replaced by [method]. The additional information needed to
> reconnect the code to a participant is held separately by [actor], accessible
> to [roles] for [purposes], and retained until [event/date]."

**Drift to flag:** Calling GDPR-pseudonymised data anonymous, or applying the
GDPR term to another authority without naming that authority's own convention.

---

## Quick Distinction Table

| Term | Identity/re-link state under the stated boundary | What the wording communicates | Authority/convention status |
|---|---|---|---|
| **Anonymity** | No identity-response link within a precisely named and verified actor/lifecycle boundary | inability to link within that boundary | ARS drafting convention unless a selected authority defines it |
| **Confidentiality** | Link may exist | limits on access, use, and disclosure | ARS drafting convention plus any selected authority/institutional terms |
| **De-identification** | Depends on the named test; retained-key effect is convention-specific | transformation and bounded residual-risk result | name the governing authority or technical release convention |
| **Pseudonymization** | Under GDPR, attribution requires separately kept additional information | a controlled but still personal-data state in the GDPR context | GDPR Article 4(5); other regimes must be named separately |

---

## Exact #666 Pointers for Participant/Data Language

These identifiers are navigation pointers only. Use them only from an exactly
selected, resolved profile and read the full row, obligated actor, predicate,
consumer scopes, and authority anchor.

| Drafting question | Exact bounded requirement pointer(s) |
|---|---|
| U.S. Common Rule participant consent | `us.45cfr46.116.informed-consent` |
| Taiwan Human Subjects Research Act participant information | `tw.hsra.article-14.consent-information` |
| GDPR lawful-basis record | `eu.gdpr.article-6.lawful-basis` |
| GDPR special-category condition/safeguards | `eu.gdpr.article-9.special-category-research` |
| GDPR information for direct collection | `eu.gdpr.article-13.direct-collection-information` |
| GDPR information for collection elsewhere | `eu.gdpr.article-14.indirect-collection-information` |
| GDPR scientific-research safeguards | `eu.gdpr.article-89.1.research-safeguards` |

The registry does not currently profile HIPAA de-identification, a universal
anonymity test, a universal confidentiality promise, or institution-specific
release thresholds. Mark those bases `unprofiled` rather than fabricating a row
or verdict.

---

## Where This Glossary Is Enforced

The `research_architect_agent` survey designer mode requires consent/privacy
language to pass through this glossary before output. The pattern-protection
clause lives in `../deep-research/agents/research_architect_agent.md` under
`PATTERN PROTECTION (v3.6.7)`. Passing through the glossary means checking actual
data flow and attaching the named convention; it does not establish legal
applicability, compliance, review pathway, readiness, or authorization.

---

## Primary Sources and Local Authority Contract

- `_shared/references/human_subjects_authority_protocol.md` ([local protocol](human_subjects_authority_protocol.md)) — exact-selection, bounded-profile, pointer-only, and no-verdict contract.
- [Curated #666 authority registry](../human_subjects_authority_registry.json) — requirement ids and row-local primary-source anchors.
- [45 CFR 164.514](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.514) — HIPAA de-identification and re-identification-code provisions; illustrative and unprofiled in #666.
- [GDPR Articles 4(5) and 89](https://eur-lex.europa.eu/eli/reg/2016/679/2016-05-04/eng) — pseudonymisation definition and research-safeguards source; only the bounded Article 89(1) requirement is represented by `eu.gdpr.article-89.1.research-safeguards`.
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