🌀
← Back to Articles & Artefacts
artefactsnorth

TCPS2 Chapter 9 Implementation Guide for Indigenous Relational Science Platform

IAIP Research
tcps2-chapter-9-chapter-9-rese-trwjwvhisl6mtlwgpmkcvq

TCPS2 Chapter 9 Implementation Guide for Indigenous Relational Science Platform

Created: December 19, 2025

WHAT IS TCPS2 CHAPTER 9?

TCPS2 Chapter 9 = Tri-Council Policy Statement (2022) - Chapter 9: Research Involving First Nations, Inuit, and Métis Peoples

Status: MANDATORY for all federally-funded Canadian research involving Indigenous peoples Source: https://ethics.gc.ca/eng/tcps2-eptc2_2022_chapter9-chapitre9.html

FIVE CRITICAL REQUIREMENTS FOR YOUR PLATFORM

1. COMMUNITY ENGAGEMENT (Article 9.1)

✓ Must engage Indigenous community BEFORE research begins ✓ Engagement determined jointly (researcher + community) ✓ Community has veto authority over research design ✓ NOT optional; integral to ethical research

Platform Action: Build Research Agreement Registry module to track formal community partnerships

2. BOTH REB + COMMUNITY APPROVAL (Article 9.9)

✓ Institutional REB approval required ✓ Community approval ALSO required (neither substitutes for other) ✓ Community can decline research even if REB approves

Platform Action: Create dual approval tracking system; conditional REB approval

3. OCAP DATA GOVERNANCE (Article 9.2 + FNIGC)

✓ Ownership: Data attributed to community (immutable) ✓ Control: Community authenticates before data use ✓ Access: Community can retrieve & use their data ✓ Possession: Physical community control (Sovereign Data Trust)

Platform Action: Deploy OCAP enforcement systems - already designed in your architecture

4. SECONDARY USE REQUIRES RE-ENGAGEMENT (Articles 9.20-9.22)

✓ Using data for NEW research question requires NEW community approval ✓ Original consent does NOT cover secondary uses ✓ System must detect & block secondary use without community re-approval

Platform Action: Build Secondary Use Detection System with automatic community notification

5. KNOWLEDGE RESTRICTIONS HONORED (Article 9.2)

✓ Community defines what knowledge is public vs. restricted vs. sacred ✓ System ENFORCES restrictions (not just policy) ✓ Publications require community approval

Platform Action: Create Knowledge Restrictions Registry with programmatic enforcement

YOUR PLATFORM'S CURRENT ALIGNMENT

✓ ALREADY DESIGNED (From CLAUDE.md + Persephone EVO):

  • Facilitator user level (community liaison role)
  • Firekeeper user level (Indigenous leadership role)
  • Reconciliation Engine (dual-epistemic balance)
  • Sovereign Data Trust concept
  • Positionality Log architecture
  • Temporal Negligence Filter (Seventh Generation principle)

✗ GAPS TO BUILD BEFORE REB SUBMISSION:

  1. Research Agreement Registry module
  2. OCAP enforcement system (control veto loop operational)
  3. Knowledge Restrictions taxonomy & enforcement
  4. Secondary Use detection & blocking
  5. REB integration & approval tracking
  6. Researcher certification tracking (TCPS2 + OCAP training)

90-DAY IMPLEMENTATION ROADMAP

DAYS 1-30: Community Partnership

  • Identify 2-3 partner Indigenous communities (specific, named)
  • Schedule leadership meetings to introduce framework
  • Begin drafting research agreements
  • Share TCPS2 Chapter 9 requirements with community
  • Establish advisory structures (Elders Council, governance body)

DAYS 31-60: REB Preparation

  • Train all REB members in TCPS2 Chapter 9
  • Train all REB members in OCAP principles
  • Update REB procedures for Indigenous research review
  • Designate TCPS2 specialist on REB
  • Create Indigenous Research Review Track (separate from standard)

DAYS 61-90: Technical Implementation

  • Build Research Agreement Registry
  • Deploy OCAP control veto loop
  • Create Knowledge Restrictions enforcement system
  • Build Secondary Use detection
  • Integrate REB approval tracking
  • Create researcher certification registry

CRITICAL SUCCESS FACTORS

✓ Community is co-designer (not research subject) ✓ Governance is enforceable (not just policy theater) ✓ Data sovereignty is real (community controls physical servers) ✓ Epistemic balance is measured (not just aspirational) ✓ Commitment is perpetual (150-year Seventh Generation horizon)

REB APPROVAL REQUIREMENTS

Your institutional REB will require documentation:

Must Provide BEFORE Approval:

  1. Signed research agreement with named Indigenous community
  2. Community engagement plan (written, describing ongoing engagement)
  3. Community customs documentation (what knowledge is public/restricted)
  4. Data governance plan (OCAP operationalization)
  5. Capacity-building plan (training community members)
  6. Benefit-sharing mechanisms
  7. Researcher TCPS2 + OCAP certification proof

REB Will Grant CONDITIONAL Approval:

  • Approval expires if community agreement expires
  • Annual REB review of relationship quality (not one-time)
  • Community can request research modifications
  • Publications require community sign-off

KEY TERMS DEFINED

TCPS2 = Tri-Council Policy Statement (federal research ethics) Chapter 9 = Section on First Nations/Inuit/Métis research OCAP = Ownership, Control, Access, Possession (First Nations data rights) Etuaptmumk = Two-Eyed Seeing (Indigenous + Western knowledge together) Reconciliation Engine = Your platform's system comparing dual-epistemic outputs Sovereign Data Trust = Community-controlled data infrastructure (geographic co-location) Epistemic Drift = Tendency for Western knowledge to dominate despite dual design Secondary Use = Using data for different research than originally approved Seventh Generation = Haudenosaunee principle (consider 150-year consequences)

COMMON MISTAKES TO AVOID

🚩 "We'll get community engagement after REB approval" → NO, engagement required BEFORE 🚩 "OCAP = cloud storage with community access" → NO, community needs physical control 🚩 "We got REB approval, so we're compliant" → NO, need REB + community approval both 🚩 "Community approved initial research, secondary use is covered" → NO, re-engagement required 🚩 "Indigenous researchers don't need positionality review" → NO, Article 9.15 still applies 🚩 "This is a 5-year project" → NO, TCPS2 implies perpetual accountability

IMMEDIATE NEXT STEPS

THIS WEEK:

  1. Share this document with community leadership
  2. Schedule REB member training
  3. Form planning team (technical + ethics + community)

THIS MONTH:

  1. Draft research agreements with communities
  2. Assess platform against gaps listed above
  3. Begin governance layer architecture

NEXT 90 DAYS:

  1. Formalize community partnerships (signed)
  2. Complete REB training
  3. Build governance & OCAP modules
  4. Prepare REB submission

RESOURCES

Official TCPS2:

OCAP Training:

CARE Principles:

DETAILED DOCUMENTATION AVAILABLE

This is a summary guide. Five detailed documents were created:

  1. TCPS2_Chapter9_Research_Ethics_Framework.md (264 lines)

    • Deep dive into TCPS2 principles & requirements

  2. TCPS2_Chapter9_Platform_Implementation_Checklist.md (545 lines)

    • 10-phase implementation with 100+ action items

  3. TCPS2_Platform_Architecture_Alignment.md (620 lines)

    • Technical mapping: requirement ↔ platform component

  4. TCPS2_REB_Briefing_for_Institutional_Review.md (533 lines)

    • For REB members reviewing your protocol

  5. TCPS2_Documentation_Suite_Overview.md (380 lines)

    • Integration guide tying all documents together

These files exist in conversation context. Request download if needed.

Questions? Start with community engagement. That's the foundation of TCPS2 compliance.