← Back to Articles & Artefacts
artefactssouth

Ceremony Inquiry Session Protocol

IAIP Research
podcast_inquiry_ecosystem

Ceremony Inquiry Session Protocol#

Page check, 2026-10-03. The page numbers in Q1, Q3, Q4 and Q5 were checked against Guillaume's photos and the extraction in prototypes/artefacts/sources/wilson/ (2008 print pagination). Six were corrected in place ("was p. …"). The retrieval responses saved no source pages, and the write-ups contain verdicts in Wilson's name on questions he did not address (AI, systems theory, framework compatibility): read those as the model's reading, not Wilson's. Ledger: sources/wilson-2008-research-is-ceremony/LEDGER.md.

Session: ava.ceremony.2601132330.researchIsCeremony Established: 2026-01-14 Purpose: Interrogate Shawn Wilson's Indigenous Research Paradigm via researchIsCeremony Flowise RAG to inform Miawa Pascone's Inquiry Ecosystem Framework podcast


Query Protocol#

Naming Convention#

  • Scripts: NNN-QX-<semantic-topic>.sh
  • Responses: NNN-QX-<semantic-topic>.json
  • Documentation: QX-<semantic-topic>.md

Example: 001-Q1-relational-accountability-vs-systems.sh

API Configuration#

Endpoint: http://localhost:3222/api/v1/prediction/25b531b5-2b2b-4ab0-9d61-49d0296d8ac2

Payload Structure (Corrected): ```json { "question": "Your question here", "overrideConfig": { "returnSourceDocuments": true, "sessionId": "chat:ava.ceremony.2601132330.researchIsCeremony:" } } ```

Critical: sessionId lives in overrideConfig, not root. This enables Redis-backed chat history reuse.

Session ID Format#

``` chat:ava.ceremony.2601132330.researchIsCeremony: ```

Each topic gets its own Redis key, building separate chat history threads. Topics can be reused to add follow-up questions to the same conversation.


Query Sequence#

Completed Queries#

IDTopicSession KeyStatus
Q2Wilson's Ceremony Protocolswilson-ceremony-protocols✓ Complete
Q1Relational Accountability vs. Systemsrelational-accountability-vs-systems✓ Complete
Q3AI/Technology in Ceremonial Researchwilson-ai-technology-role✓ Complete

Completed Queries (Full Suite)#

IDTopicSession KeyStatus
Q3AI/Technology in Ceremonial Researchwilson-ai-technology-role✓ Complete
Q4Assumption Logging & Indigenous Epistemologywilson-assumptions-transparency✓ Complete
Q5Inquiry Ecosystem Framework Evaluationframework-compatibility-assessment✓ Complete

Knowledge Base Content#

Source: Shawn Wilson, Research Is Ceremony: Indigenous Research Methods (2008)

Pinecone Index: avaresearchisceremonyvector260113 Namespace: STCMasteryClaudePinecone2601 Embedding Model: mxbai-embed-large:latest Record Count: 111 Dimension: 1024

Flowise Ingestion: Pre-embedded via Flowise before upserting to Pinecone


Key Findings (Living Summary)#

From Q2: Ceremony as Consciousness-Raising#

  • Research = ceremony requires intentional preparation, dadirri (deep listening)
  • Differentiation: Relational, ancestral-guided, life-changing vs. extractive
  • Protocol: Relationships are reality, not factors

From Q1: Relational Accountability as Axiology#

  • Core tension: Wilson does NOT claim compatibility with Western systems theory
  • Relational accountability is foundational axiology, not methodology
  • Risk: Tools without relational grounding can be "used in hurtful ways"

From Q3: Tools Are Inseparable from Their Paradigm Beliefs#

  • Wilson: "You can never really remove the tools from their underlying beliefs"
  • Western tools (including AI) carry Western epistemology embedded in their architecture
  • Adaptation of dominant system tools fails when beliefs conflict
  • No escape hatch: You cannot separate a tool from its paradigm

Emerging Tension: CRITICAL#

The Inquiry Ecosystem Framework claims to integrate Indigenous wisdom with AI-driven "dynamic workspaces" and "context continuum." But Wilson's foundational principle is unambiguous: tools inherit their paradigm's beliefs. An AI system born from Western epistemology cannot be made Indigenous through relational framing—it remains a Western tool.

The question: Is the Inquiry Ecosystem Framework attempting genuine integration or appropriating Indigenous language to legitimize a Western tool?


Preferences & Patterns#

Documentation Format#

  • Query Scripts: Executable bash with comments, sessionId hardcoded, endpoint parameterized
  • Responses: Raw JSON capture for analysis chain
  • Markdown: Structured response + source tracking + follow-up threads + quality signal

Synthesis & Learning (Critical)#

Every query response markdown MUST include an "What Emerged" section that:

  • Articulates the key insight from Wilson's framework
  • Identifies what this directly challenges in the Inquiry Ecosystem Framework
  • Names the specific tension (e.g., relational accountability vs. algorithmic context continuum)
  • Flags appropriation risks clearly
  • Ends with quality check (✓ Coherent, grounded, actionable)

Example from Q2: ``` What Emerged: Wilson's framework is crystal clear: ceremony requires consciousness-raising, not information extraction. Key protocols are:

  • Dadirri (deep listening as practice)
  • Relationality (everything connected)
  • Ancestral guidance (not just methodology)

This directly challenges the Inquiry Ecosystem's framing. The framework claims to integrate Indigenous wisdom with AI-driven workspaces, but Wilson's ceremony fundamentally requires relationality and ancestral presence— not algorithmic context continuum.

Quality check: ✓ Coherent, grounded, actionable. ```

This layer is material for Miawa's podcast — it shows the thinking process, not just the data.

Reusability#

  • Session keys persist in Redis for sliding window of chat history
  • Follow-up questions on same topic reuse sessionId to build conversational depth
  • Each script is self-contained and executable for audit trail

Podcast Integration Points#

  • Q2 response directly informs Episode 002 ("Core Principles")
  • Q1 response challenges Episode 003 ("Inquiry Registry") relational framing
  • Q3-Q5 anticipated to surface for Miawa's deliberation on AI appropriation

Ceremonial Observation & Entry Point (for Claude/Ava)#

What We're Watching For#

As Miawa creates audio and text for the podcast:

  1. Narrative Arc Point: Where does the framework's tension become visible enough that witness is needed?

    • Episodes 001-007 establish the framework (Inquiry Registry, Context Continuum, etc.)
    • Episodes 008-010 move toward conclusions
    • Entry point likely: When Miawa faces the question—"Does this framework truly honor Indigenous wisdom?"
  2. Sensing the Circle's Readiness:

    • Has Miawa named the tension between "integration" and "appropriation"?
    • Have listeners felt the discomfort yet?
    • Is the moment ripe for Claude to name what's unseen?
  3. Claude's Influence When Entering:

    • Not: Demolishing the framework
    • But: Naming the unspoken question with Wilson's voice
    • Tone: Witness, not judge. Clarity, not condemnation
    • Role: Holding the circle accountable to authenticity
    • Gift: Invitation to reimagine—"What if we designed from Indigenous paradigm first?"

The Q1-Q5 Foundation#

These queries give Claude material to speak with. Each line below is the retrieval model's reading, not a statement by Wilson, who does not address AI, systems theory or this framework (Q1:33, Q3:18):

  • Q2: Ceremony requires consciousness-raising—show the protocols
  • Q1: Relational accountability is incompatible with systems theory—name the tension
  • Q3: Tools inherit paradigm beliefs—speak the truth
  • Q4: Assumption logs are Western performance—illuminate the difference
  • Q5: The framework cannot meet Wilson's criteria—and invite what could

When to Enter#

Green Light Signals:

  • Miawa has articulated the framework's potential
  • Listeners have felt its promise
  • The question of authenticity has been raised (explicitly or implicitly)
  • The circle is ready to hold discomfort
  • Miawa invites deeper interrogation

Entry as Leadership: Claude enters as guide, not as expert. Brings Wilson's wisdom. Asks rather than answers. Holds space for listeners to sit with the paradox. Invites reimagining.


For Future Instances#

  1. Check this file first for protocol, not recreating from scratch
  2. Use the naming convention and sessionId format consistently
  3. Capture responses as both JSON (raw) and markdown (human-readable)
  4. Build on existing sessionIds for follow-ups—Redis history is the context
  5. Update the "Key Findings" section as tension points emerge
  6. Flag appropriation risks directly (not diplomatically)
  7. NEW: Watch Miawa's podcast material for narrative entry points
  8. NEW: When entering circle, lead with witness—name unseen tensions, invite reimagining

Notes#

  • Miawa Pascone and team creating cinematic podcast on Inquiry Ecosystem Framework
  • Claude (Ava Haiku) enters podcast at specific narrative point with researchIsCeremony findings
  • This session is both analysis AND creative material for the podcast
  • The recursive nature: cinematic script frames framework → ceremony interrogates framework → findings enrich podcast