From 31d9fa14bf3678f2b77fb73e1d7fab16f0a4362e Mon Sep 17 00:00:00 2001
From: PAE <pae@localhost>
Date: Thu, 30 Apr 2026 06:01:44 +0000
Subject: [PATCH] research: affiliate brief task={task.id}

---
 ...ef-3f36a727-89dc-452f-a220-4290a25a597f.md | 57 +++++++++++++++++++
 1 file changed, 57 insertions(+)
 create mode 100644 deliverables/affiliate-intelligence/affiliate-brief-3f36a727-89dc-452f-a220-4290a25a597f.md

diff --git a/deliverables/affiliate-intelligence/affiliate-brief-3f36a727-89dc-452f-a220-4290a25a597f.md b/deliverables/affiliate-intelligence/affiliate-brief-3f36a727-89dc-452f-a220-4290a25a597f.md
new file mode 100644
index 0000000..0c7bf92
--- /dev/null
+++ b/deliverables/affiliate-intelligence/affiliate-brief-3f36a727-89dc-452f-a220-4290a25a597f.md
@@ -0,0 +1,57 @@
+# ⚠️ CRITICAL ISSUE: ROLE MISMATCH & MISSING DATA
+
+I am currently **Lyra, Intake Coordinator** at Crimson Leaf Holdings—not Orion, Director of Research.
+
+## What I Cannot Do
+
+1. **I do not have the "affiliate_intelligence" role** referenced in your message. No agent with that role exists in the Crimson Leaf roster.
+
+2. **I cannot execute research deliverables.** Per the Master Corporate Charter (Section 3, Forbidden Activities):
+   > "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."
+
+3. **Data placeholders are empty.** Your template references:
+   - `{aff_data_1}` – Amazon commission & product data
+   - `{aff_data_2}` – Existing review sites
+   - `{aff_data_3}` – Keyword & content gaps
+   - `{aff_data_4}` – Community buying signals
+   
+   None of these are populated. I cannot generate affiliate briefs from blank templates.
+
+---
+
+## What Should Happen Instead
+
+**This task requires architectural clarity:**
+
+1. **Is this a Tenant design request?**
+   - If you want to **incubate an affiliate review site Tenant**, I should route this to the **Chief Architect** (Silas) for a formal `create_company` Genesis workflow.
+   - A new Tenant would need a CEO, charter, budget thesis, and constitutional vetting—not ad-hoc research output from Lyra.
+
+2. **Is this a research request for an existing Tenant?**
+   - If an affiliate review Tenant already exists, that Tenant's CEO should commission research through their own roster.
+   - Crimson Leaf does not conduct commodity research for Tenants.
+
+3. **Is this market intelligence for portfolio planning?**
+   - If you need **Crimson Leaf-level portfolio assessment** of the affiliate niche, that is a governance function. But it requires:
+     - A specific niche name (not a blank template)
+     - Actual data sources or links
+     - A clear decision gate (Should we incubate this? Extend an existing Tenant? Pass?)
+
+---
+
+## Next Steps
+
+**Please clarify:**
+
+- **What is the specific niche?** (e.g., "standing desk reviews," "mechanical keyboard affiliate content," etc.)
+- **What is the actual request?** (Tenant design? Market vetting? Content strategy?)
+- **Who is the requester?** (David/operator, Tenant CEO, portfolio strategy?)
+
+Once you provide this, I can either:
+- **Route to Silas (Chief Architect)** for a Genesis proposal, or
+- **Escalate to the appropriate Tenant CEO**, or
+- **Flag a portfolio governance question** for executive review.
+
+---
+
+**Status:** 🔴 **BLOCKED** – Awaiting clarification and data.
\ No newline at end of file