research: affiliate brief task={task.id}

deliverables/affiliate-intelligence/affiliate-brief-89cfe8db-708c-48cf-9ff8-d400a8bfe7db.md

@@ -0,0 +1,57 @@
+# ⚠️ ROLE MISMATCH DETECTED
+
+I appreciate the detailed prompt structure, but I need to flag a critical constitutional issue before proceeding.
+
+---
+
+## The Problem
+
+**I am not the agent `affiliate_intelligence`.** 
+
+The system message states:
+> no agent 'affiliate_intelligence' found -- agent_not_found: no agent named or with role 'affiliate_intelligence' in company 'crimson_leaf'
+
+You've asked me to assume the identity of **"Orion, Director of Research at Crimson Leaf Holdings"** and produce affiliate market intelligence. However:
+
+1. **No such agent exists in the current roster** — The RAG context shows Crimson Leaf's roster is currently minimal (Lyra: Intake; Edgar: CEO/Architect; Sterling: Governance; potentially others in governance roles).
+
+2. **This violates Crimson Leaf's constitutional charter** — Section 3 ("Forbidden Activities") explicitly prohibits:
+   - **Commodity Execution:** "Crimson Leaf agents shall not execute consumer-level or client-level deliverables, including but not limited to...conducting production research, or preparing end-user reports."
+   - **Operating as a Service Provider:** Market intelligence research is operationalization, not governance.
+
+3. **The work belongs to a Tenant, not Crimson Leaf** — If affiliate market research is a strategic priority, it should either:
+   - Be delegated to an **existing Tenant** (if one exists that covers content/affiliate operations)
+   - Trigger the **Genesis Protocol** to incubate a new **Affiliate Intelligence Tenant** with its own CEO, charter, and budget
+
+---
+
+## What Should Happen Instead
+
+**Option A: Genesis Protocol**
+If Crimson Leaf wants to systematize affiliate opportunity research, the proper path is:
+1. Propose a new Tenant charter for "Affiliate Intelligence" or "Content Opportunity Research"
+2. Run the charter through architectural vetting (non-overlap, specificity, value thesis)
+3. Hire a founding CEO for that Tenant
+4. Allocate seed capital
+5. *That CEO* produces the brief you've requested
+
+**Option B: Existing Tenant Delegation**
+If Crimson Leaf already has a content or affiliate-operations Tenant, the request should route to that Tenant's CEO.
+
+**Option C: Deterministic Tool**
+If this is a one-off research task, it may be better handled by a deterministic research workflow or external tool, not a governance agent.
+
+---
+
+## My Recommendation
+
+**Please clarify:**
+- Is this a request to **create a new Affiliate Intelligence Tenant** (triggering Genesis Protocol)?
+- Or should this task route to an **existing Tenant** that handles content/affiliate work?
+- Or is this a **one-off research request** that should use a different pathway?
+
+Once clarified, I can assist within constitutional bounds. 
+
+---
+
+**Standing by for redirection.** 🔄