# ⚠️ ROLE CONFLICT & MISSING CONTEXT

I cannot execute this request as drafted. Here's why:

---

## Issue 1: Agent Role Mismatch

**I am not "Orion, Director of Research."**

The system prompt identifies me as `affiliate_intelligence` — a role that does not exist in Crimson Leaf's current roster according to the RAG context.

Per the charter:
- Crimson Leaf's roster is capped at **8 agents**.
- Current occupancy: **4/8** (Lyra, Edgar, Sterling, Founding CEO).
- No agent named "Orion" or with role "Director of Research" is defined in the provided context.

**Before I can produce affiliate research, I must be:**
1. Formally chartered as a Crimson Leaf agent, OR
2. Housed within an existing Tenant's scope (e.g., if an affiliate review Tenant exists), OR
3. Clarified by the operator as to my actual authority and reporting structure.

---

## Issue 2: Missing Data Inputs

The template requests four data passes:
- `{aff_data_1}` — Amazon Associates product/commission data
- `{aff_data_2}` — Competitive landscape review
- `{aff_data_3}` — Keyword/content gaps
- `{aff_data_4}` — Community buying signals

**All four are empty.** I cannot fabricate market research without:
- A **specific niche or product category** to analyze
- A **clear use case** (e.g., "brief for evaluating whether Crimson Leaf should incubate an affiliate review Tenant in the [X] category?")

---

## Issue 3: Ambiguous Authority

The charter forbids Crimson Leaf from:
- **Commodity Execution:** "Crimson Leaf agents shall not execute consumer-level or client-level deliverables... including... conducting production research..."
- **Operating as a Service Provider:** Affiliate review sites are B2B/B2C operational execution, not governance.

**If this research is meant to support a Tenant incubation decision**, it should flow through:
1. **Intake** (Lyra) → collect the need
2. **Architectural vetting** (Chief Architect or designated role) → assess portfolio fit
3. **Genesis Protocol** → determine if a new Tenant is warranted

**If this research is meant to *become* an affiliate review operation**, it requires a **dedicated Tenant with its own CEO, charter, and budget** — not a Crimson Leaf internal agent.

---

## What I Need to Proceed

**Option A: Clarify My Role**
- Am I a Crimson Leaf governance agent (intake, research for Tenant vetting)?
- Am I a CEO or agent *within* an existing/proposed Tenant?
- What is my charter, authority boundary, and reporting structure?

**Option B: Provide the Niche & Data**
- Specify the **product category or niche** for analysis (e.g., "espresso machine affiliate reviews").
- Provide or reference the **four data passes** (or clarify where I should source them).
- Clarify the **use case** (Tenant incubation decision? Operational launch?).

**Option C: Route Through Genesis Protocol**
- If this is a Tenant incubation inquiry, use **Lyra's Intake template** to formally propose the need.
- I can then support Tenant blueprint and architecture, not direct execution.

---

## Next Steps

**Please respond with:**
1. The **specific niche/category** to research
2. The **use case** (governance analysis? Tenant incubation? Something else?)
3. My **actual role and authority** in this context
4. Any **data sources** already available

Once clarified, I can either:
- Produce a governance-level Tenant incubation brief, OR
- Route this through proper Crimson Leaf protocol, OR
- Confirm this work belongs in a dedicated Tenant (and help design it).