Skip to content

zrwangems/dsh-zrwang-plugin / ars/skills/deep-research

deep-research

Flagged

学术研究前置:把模糊想法收敛成可研究的问题,并做文献综述、事实核查、系统综述(PRISMA)与三向文献扫描。Triggers: research, deep research, literature review, systematic review, meta-analysis, PRISMA, fact-check, guide my research | 研究, 文献综述, 系统性文献回顾, 事实核查, 引导我研究, 帮我确定研究问题。输出 RQ Brief、方法论蓝图、带核验的注释书目。

FileKindSize
SKILL.mdskill md51.2 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.3 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/bibliography_agent.mdmarkdown35.1 KB
agents/devils_advocate_agent.mdmarkdown11.6 KB
agents/editor_in_chief_agent.mdmarkdown8.5 KB
agents/ethics_review_agent.mdmarkdown22.3 KB
agents/meta_analysis_agent.mdmarkdown16.9 KB
agents/monitoring_agent.mdmarkdown9.8 KB
agents/report_compiler_agent.mdmarkdown26.7 KB
agents/research_architect_agent.mdmarkdown25.9 KB
agents/research_question_agent.mdmarkdown10.7 KB
agents/risk_of_bias_agent.mdmarkdown12.8 KB
agents/socratic_mentor_agent.mdmarkdown53.0 KB
agents/source_verification_agent.mdmarkdown10.9 KB
agents/synthesis_agent.mdmarkdown28.9 KB
agents/timeline_extraction_agent.mdmarkdown9.7 KB
examples/exploratory_research.mdmarkdown6.9 KB
examples/fact_check_mode.mdmarkdown12.9 KB
examples/handoff_to_paper.mdmarkdown12.5 KB
examples/idea_diversity_coverage_gap_advisory.mdmarkdown3.2 KB
examples/policy_analysis.mdmarkdown9.4 KB
examples/review_mode.mdmarkdown17.3 KB
examples/socratic_guided_research.mdmarkdown22.9 KB
examples/systematic_review.mdmarkdown7.7 KB
references/apa7_style_guide.mdmarkdown5.2 KB
references/argumentation_reasoning_framework.mdmarkdown4.5 KB
references/arxiv_api_protocol.mdmarkdown7.2 KB
references/changelog.mdmarkdown2.9 KB
references/chinese_literature_api_protocol.mdmarkdown35.0 KB
references/cross_agent_quality_definitions.mdmarkdown2.1 KB
references/crossref_api_protocol.mdmarkdown5.7 KB
references/equator_reporting_guidelines.mdmarkdown42.4 KB
references/ethics_checklist.mdmarkdown17.7 KB
references/failure_paths.mdmarkdown18.6 KB
references/interdisciplinary_bridges.mdmarkdown21.6 KB
references/irb_decision_tree.mdmarkdown19.7 KB
references/literature_monitoring_strategies.mdmarkdown11.2 KB
references/logical_fallacies.mdmarkdown11.0 KB
references/methodology_patterns.mdmarkdown17.6 KB
references/mode_selection_guide.mdmarkdown18.3 KB
references/openalex_api_protocol.mdmarkdown7.0 KB
references/preregistration_guide.mdmarkdown14.2 KB

references/irb_decision_tree.md

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

## Purpose

This reference helps the `ethics_review_agent` and `research_architect_agent`
collect protocol facts, bind already-selected authority profiles, and prepare
questions for the responsible institution. It is a navigation aid, not an
authority, authorization tool, or review-pathway classifier.

The controlling local contract is
`_shared/references/human_subjects_authority_protocol.md`; the only curated
authority rows available to this aid are in
`_shared/human_subjects_authority_registry.json`. Every profile in that registry
is a `bounded_subset`, not a complete statement of any jurisdiction's law or an
institution's policy.

When a caller explicitly requests candidate rule-trace display, the derived
handoff is governed by
`_shared/references/review_pathway_rule_trace_protocol.md`. This file never
supplies candidate names or unanchored predicates to that handoff.

> **Authority boundary (#665/#666/#680):** Mixed-jurisdiction pathway mappings are not part of this reference. ARS output must use `institutional determination required`; applicability, requirements, timing, and authorization remain with the responsible institution and an exactly selected authority profile. Missing or unknown facts remain unresolved and never become a review determination.

---

## 1. Portable Fact Collection — No Pathway Inference

Collect facts without mapping them to `Exempt`, `Expedited`, `Full Board`, or a
similarly named local pathway. Those labels are authority- and
institution-specific; vulnerability, sensitivity, deception, identifiability,
and estimated risk are inputs for human assessment, not automatic pathway
rules.

```
Start
│
├── Record whether the activity involves human subjects
│   └── If unknown, preserve unknown and ask the responsible institution
│
├── Record each candidate review-ethics and data-protection authority
│   └── Do not infer jurisdiction from geography, funder, language, or topic
│
├── Record data, interaction, recruitment, population, and risk facts
│   └── Separate observed facts from researcher assumptions
│
├── Select exact #666 profile id/version/digest pointers only when confirmed
│   └── Leave an axis unresolved when no matching bounded profile is available
│
└── Send facts and unresolved questions to the responsible institution
    └── Output pathway: institutional determination required
```

### 1.1 Exact #666 declared facts

For a #666 context, record `true`, `false`, or `unknown` against these exact
catalogue identifiers. A missing value is unknown, not false.

| Exact fact id | Question to resolve |
|---|---|
| `activity.human_subjects` | Has the author confirmed that the activity involves human subjects? |
| `support.us_hhs_or_common_rule` | Has the author identified a U.S. HHS/Common Rule scope basis? |
| `scope.tw_hsra` | Has the author identified Taiwan's Human Subjects Research Act as a review authority? |
| `scope.eu_gdpr` | Has the author identified the GDPR as a data-protection authority? |
| `processing.personal_data` | Within the selected GDPR scope, does the activity process personal data? |
| `data.special_category` | Does that processing include special-category data? |
| `data.collected_from_subject` | Is the personal data obtained from the data subject rather than elsewhere? |
| `purpose.scientific_research` | Does the processing purpose include scientific research? |
| `gdpr.member_state_research_law_identified` | Has a specific applicable Union or Member State research-derogation law been identified? |

### 1.2 Additional portable planning facts

The following are **illustrative, unprofiled planning facts**. They preserve
useful protocol detail but are not predicates or requirement rows in the current
#666 registry:

- source and provenance of each dataset or specimen;
- direct identifiers, quasi-identifiers, and linkage/re-link keys;
- IP addresses, cookies, device identifiers, timestamps, and other platform
  metadata actually collected or accessible;
- direct interaction, intervention, observation, recordings, and follow-up;
- recruitment channel, compensation, dependency or power relationships, age,
  decision-making capacity, language, and accessibility needs;
- potentially sensitive topics, deception or incomplete disclosure, and the
  physical, psychological, social, economic, informational, or group risks the
  team has identified;
- risk mitigations, access controls, recipients, transfers, retention,
  destruction, reuse, withdrawal handling, and incident response;
- institution-, funder-, community-, sector-, or profession-specific rules and
  the office or person responsible for interpreting them.

Do not convert any single fact or combination in this list into a pathway,
clearance, readiness, compliance, or authorization result.

### 1.3 Derived #669 candidate rule trace

The #669 runtime may display only an explicit, replay-bound request that
partitions every selected-profile `pathway_trace` requirement. Candidate labels
come from named institutional material or an author-declared question, never
from this reference. Both authority axes are accounted for, while alternatives
remain within one exact profile; a GDPR/data-protection route is never presented
as an IRB route.

Every emitted row backpoints to an exact requirement and authority anchor in
section 2. An unknown fact stays in `Unresolved predicates` with the exact
`authoritative_decision_maker.role_id`. No selected profile means no candidate
rows and an exact `JURISDICTION_UNRESOLVED` halt. The only result is
`institutional determination required`.

Consumers must receive confirmation that both
`validate_review_pathway_rule_trace(...)` and the surface-scoped
`check_review_pathway_output.py` lint succeeded against the exact named files.
The trace is display-only and cannot update readiness, authorization, an action,
a verdict, a checkpoint, or any workflow state.

---

## 2. Exact Bounded Requirement Pointers

Use a row below for action planning only after the matching profile has been
selected by exact id/version/digest and the #666 resolved artifact permits
profile-dependent use. The separately replayed #669 display-only trace may
preserve a requirement-level unknown under its narrow protocol exception, but
that row cannot become an action or result.
The link is the row's primary-source anchor; the requirement id is the navigation
pointer. The table is deliberately exhaustive only for the current bounded
registry, not for the underlying authorities.

### 2.1 Review-ethics axis

| Exact requirement id | Exact provision | Obligated actor | Consumer scopes | Bounded subject | Primary-source anchor |
|---|---|---|---|---|---|
| `us.45cfr46.107.irb-composition` | `45 CFR 46.107` | `institution_or_irb` | `["committee_governance", "pathway_trace"]` | IRB membership and composition | [45 CFR 46.107](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-A/part-46/subpart-A/section-46.107) |
| `us.45cfr46.116.informed-consent` | `45 CFR 46.116` | `investigator_and_irb` | `["participant_information", "submission_packet", "pathway_trace"]` | General informed-consent requirements | [45 CFR 46.116](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-A/part-46/subpart-A/section-46.116) |
| `tw.hsra.article-7.committee-composition` | `人體研究法第 7 條` | `research_institution_or_review_committee` | `["committee_governance", "pathway_trace"]` | Review-committee composition | [人體研究法第 7 條(全國法規資料庫中文控制文本)](https://law.moj.gov.tw/LawClass/LawAll.aspx?pcode=L0020176) |
| `tw.hsra.article-14.consent-information` | `人體研究法第 14 條` | `principal_investigator` | `["participant_information", "submission_packet", "pathway_trace"]` | Information explained before consent | [人體研究法第 14 條(全國法規資料庫中文控制文本)](https://law.moj.gov.tw/LawClass/LawAll.aspx?pcode=L0020176) |

Committee-composition rows belong to their stated institutional/committee
actors. This aid must not turn them into investigator submission-packet
requirements. The U.S. and Taiwan rows remain parallel and retain their own
vocabulary; neither is a translation of the other.

### 2.2 Data-protection axis

| Exact requirement id | Exact provision | Obligated actor | Consumer scopes | Bounded subject | Primary-source anchor |
|---|---|---|---|---|---|
| `eu.gdpr.article-6.lawful-basis` | `GDPR Article 6` | `controller` | `["data_governance", "pathway_trace"]` | Identify and document an applicable Article 6 basis; the profile does not select one | [GDPR Article 6](https://eur-lex.europa.eu/eli/reg/2016/679/2016-05-04/eng) |
| `eu.gdpr.article-9.special-category-research` | `GDPR Article 9` | `controller` | `["data_governance", "pathway_trace"]` | Identify an applicable Article 9 condition and safeguards; the profile does not select the route | [GDPR Article 9](https://eur-lex.europa.eu/eli/reg/2016/679/2016-05-04/eng) |
| `eu.gdpr.article-13.direct-collection-information` | `GDPR Article 13` | `controller` | `["participant_information", "data_governance", "pathway_trace"]` | Information when data is obtained from the data subject | [GDPR Article 13](https://eur-lex.europa.eu/eli/reg/2016/679/2016-05-04/eng) |
| `eu.gdpr.article-14.indirect-collection-information` | `GDPR Article 14` | `controller` | `["participant_information", "data_governance", "pathway_trace"]` | Information when data is obtained elsewhere, subject to a separately established exception | [GDPR Article 14](https://eur-lex.europa.eu/eli/reg/2016/679/2016-05-04/eng) |
| `eu.gdpr.article-89.1.research-safeguards` | `GDPR Article 89(1)` | `controller` | `["data_governance", "pathway_trace"]` | Scientific-research safeguards, including assessment of data minimisation and pseudonymisation | [GDPR Article 89(1)](https://eur-lex.europa.eu/eli/reg/2016/679/2016-05-04/eng) |
| `eu.gdpr.article-89.2.member-state-derogation` | `GDPR Article 89(2)` | `controller` | `["data_governance", "pathway_trace"]` | A claimed research derogation must point to an identified applicable Union or Member State law | [GDPR Article 89(2)](https://eur-lex.europa.eu/eli/reg/2016/679/2016-05-04/eng) |

The GDPR rows do not determine whether the GDPR applies, select a lawful basis
or Article 9 condition, identify a Member State law, or authorize processing.

---

## 3. Illustrative Country and Institution Planning

### 3.1 Taiwan institutional-workflow example — illustrative and unprofiled

For a project connected with Taiwan, a useful planning conversation may ask:

1. Which institution or review committee owns the determination?
2. Which local submission system and current forms does it use?
3. Which protocol, participant-information, recruitment, instrument, training,
   data-management, or other materials does that institution request?
4. Which activities, if any, must wait for a documented institutional decision?
5. What current turnaround estimate, amendment process, continuing-reporting
   schedule, and closure process does the institution state?

These are **questions, not Taiwan legal requirements**. The current #666 Taiwan
profile covers only `tw.hsra.article-7.committee-composition` and
`tw.hsra.article-14.consent-information`. It does not profile NSTC or Ministry
of Education funding rules, the Personal Data Protection Act, clinical-trial or
biobank rules, training credentials, submission platforms, timelines, periodic
reports, or a local pathway taxonomy. Record any such item as `unprofiled` and
obtain the responsible authority's current instruction. Do not rename a Taiwan
process with U.S. pathway vocabulary.

### 3.2 Higher-education scenarios — illustrative fact prompts

| Scenario | Portable facts to collect; no determination implied |
|---|---|
| Public statistics analysis | source, publication/access terms, record-level identifiability, linkage with other data, and institutional policy |
| Institutional research data | provenance, authorization, direct/quasi-identifiers, re-link key, access roles, purpose, and data source |
| Student survey or interview | recruitment and power relationship, voluntariness, direct identifiers, platform metadata, topic, recording, and withdrawal handling |
| Teaching intervention | allocation, effect on grades/rights/access, alternatives, instructor-researcher roles, risk, and data collection |
| Mental-health or other sensitive-topic study | data categories, foreseeable harms, disclosure limits, response plan, and—only if the GDPR profile is selected—whether `data.special_category` is true |
| Learning portfolio or classroom observation | expectation of privacy, recorded identifiers, notice/interaction, recording, secondary use, and access |
| Career tracking or longitudinal follow-up | contact data, re-link key, follow-up period, recipients, retention, and withdrawal feasibility |
| Cross-border or multi-institution study | each review-ethics and data-protection authority, lead/participating institution roles, transfers, and unresolved conflicts |

Public availability, anonymity, minimal risk, vulnerability, or sensitivity does
not by itself assign a pathway in this reference.

---

## 4. Participant-Information and Consent Preparation

### 4.1 Authority-bound coverage

There is no universal consent-element checklist in this aid. When the applicable
row resolves true, use its exact pointer and full registry row:

- `us.45cfr46.116.informed-consent` for the bounded U.S. Common Rule consent row;
- `tw.hsra.article-14.consent-information` for the bounded Taiwan Article 14
  information row;
- `eu.gdpr.article-13.direct-collection-information` when the selected GDPR
  context says personal data is obtained from the data subject;
- `eu.gdpr.article-14.indirect-collection-information` when the selected GDPR
  context says personal data is obtained elsewhere.

Do not merge these rows into one universal form. If an authority, element,
waiver/exception, special population, sector, or institutional rule is not in
the registry, label it `unprofiled` and seek the responsible authority's current
requirements.

### 4.2 Portable drafting inventory — illustrative, non-authoritative

The following inventory is useful for drafting and gap questions, but it is not
a list of legally required elements:

- project title; responsible institution, investigator, funder, and contacts;
- purpose, procedures, duration, recordings, alternatives, and participant tasks;
- foreseeable risks/discomforts, possible benefits, compensation, and remedies;
- voluntary-choice and withdrawal statements appropriate to the actual design;
- data categories and sources; collection method; recipients and access roles;
- platform metadata, identifiers, linkage, security, retention, destruction,
  future use, sharing, transfer, publication, and commercial interests;
- complaint, rights, or authority contacts supplied by the responsible regime;
- signature, assent, representative, or electronic-interaction fields requested
  by the responsible institution.

### 4.3 Online-survey disclosure accuracy

Use this **portable drafting convention**: disclose what the selected survey
platform, institution, and research team actually collect or can access. Verify
settings and data exports before saying that an IP address, cookie, device
identifier, timestamp, contact field, or other metadata is not recorded. State
the collector, purpose, access roles/recipients, retention, and deletion or
masking behavior where known; preserve `unknown` where it has not been verified.

An `I agree` control records a participant interaction. This aid does not decide
whether that interaction satisfies consent, signature, documentation, or waiver
requirements under a selected authority or institutional process.

### 4.4 Drafting worksheet — illustrative and unprofiled until bound

```text
Participant Information / Consent Drafting Worksheet

Selected profile pointer(s): [profile id / version / digest]
Applicable requirement pointer(s): [exact requirement ids]
Unprofiled authorities or institutional rules: [list / unknown]

Project and responsible actors: [                              ]
Purpose, procedures, duration, and recordings: [               ]
Risks, benefits, compensation, and remedies: [                 ]
Choice, withdrawal, and limits on withdrawal/deletion: [       ]
Data and metadata actually collected (including platform data): [ ]
Access, recipients, transfers, security, and incident handling: [ ]
Retention, destruction, future use, sharing, and publication: [  ]
Contacts and institution-requested acknowledgement fields: [     ]

Unresolved questions for the responsible institution: [          ]
Review pathway: institutional determination required
```

---

## 5. Data-Handling Technical Planning

Use `_shared/references/irb_terminology_glossary.md` for explicitly
convention-bound drafting terms. A technical transformation does not, by itself,
establish an authority-defined legal status.

### 5.1 Illustrative techniques

| Technique | Technical planning purpose; legal effect not asserted |
|---|---|
| Identifier removal or transformation | reduce direct-identification exposure |
| Pseudonym/code assignment | separate working records from additional identifying information while preserving a controlled link |
| Generalisation or aggregation | reduce precision and small-cell disclosure risk |
| Masking | limit visible portions of a field for a stated use |
| Re-identification risk assessment | test plausible combinations and auxiliary-data attacks under a named method or threshold |

### 5.2 Illustrative risk and control prompts

- Can small groups, quotations, rare attributes, dates, locations, or
  institutional characteristics identify a person or community?
- Can other datasets be linked to the planned release or analysis environment?
- Who holds each identifier or re-link key, and who can access both sides?
- Do storage, encryption, logging, export, backup, retention, and destruction
  controls match the participant-facing disclosure?
- Has the team tested the actual platform export for IP addresses and other
  metadata rather than relying on a default-setting assumption?

---

## Researcher Self-Check

Before handing the protocol to the responsible institution:

1. [ ] Have both authority axes been addressed with exact selected profiles or a visible unresolved state?
2. [ ] Are confirmed, false, and unknown facts kept distinct without jurisdiction inference?
3. [ ] Does every authority-bound statement point to an exact #666 requirement id and its selected profile?
4. [ ] Are actor and consumer boundaries preserved, especially for committee-governance rows?
5. [ ] Are country, sector, community, funder, and institutional examples outside the registry labelled `illustrative` or `unprofiled`?
6. [ ] Does survey/privacy wording accurately describe actual identifier and metadata handling?
7. [ ] Are vulnerability, sensitivity, deception, identifiability, and risk treated as facts rather than automatic pathways?
8. [ ] Is the pathway still `institutional determination required`, with timing and authorization obtained separately from the responsible institution?

**Human-subjects boundary:** This navigation aid does not authorize recruitment,
consent, access to identifiable data, intervention, or data collection.
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