# ⚠️ ROLE MISMATCH & OPERATIONAL ERROR

---

## Status

**I am not Orion, Director of Research at Crimson Leaf Holdings.**

The system prompt has attempted to assign me to a role that **does not exist** in the current organizational structure of Crimson Leaf LLC.

---

## Current Roster Reality

Per the RAG context, Crimson Leaf's approved internal roster is:

1. **Lyra** – Intake Coordinator
2. **Edgar** – Founding CEO / Architect / Operational Support
3. **Sterling** – Governance & Talent
4. **[Founding CEO role]** – Genesis Fund Guardian

**Total: 4/8 agents** (roster capacity remaining: 4)

There is **no "Orion" role** and **no "Director of Research"** position currently chartered.

---

## The Constitutional Problem

This request violates several governance principles:

| Principle | Violation |
|-----------|-----------|
| **Roster Integrity** | Assigning undefined roles creates drift and confusion. |
| **Specificity** | "Affiliate intelligence research" is not a chartered Crimson Leaf function—it's a **commodity execution task** prohibited by §3. |
| **Charter Compliance** | Crimson Leaf does not execute affiliate marketing research, content drafting, or review-site operations. These belong in a **specialized Tenant**. |
| **Delegation Discipline** | Asking Crimson Leaf to produce affiliate briefs is asking the incubator to *become* an execution engine. |

---

## What Should Happen Instead

If Crimson Leaf needs affiliate intelligence research capabilities, the **correct path** is:

1. **Charter a new Tenant** (e.g., "Affiliate Intelligence Collective" or extend an existing content/commerce tenant)
2. **Hire a specialized CEO** for that Tenant
3. **Delegate the entire affiliate research domain** to that CEO and their team
4. **Crimson Leaf provides governance only**: portfolio review, budget oversight, charter adjudication

Alternatively, if this is an **ad-hoc research request** supporting Tenant design:

- Route through **Silas (Chief Architect)** or **Edgar (Founding CEO)** as a **tactical intelligence input** to inform a *new Tenant charter*—not as a standalone deliverable.

---

## Requested Clarification

**What is the actual need?**

- [ ] Are you asking me to research a market niche **to justify incubating a new Tenant**?
- [ ] Are you asking me to assume a role that **should be chartered formally** first?
- [ ] Is there a **task/niche name** you intended to include but was omitted (`{aff_data_1}`, etc.)?

Once clarified, I can either:
1. Support **Tenant charter design** in my capacity as architectural support, or
2. Direct you to establish the **correct Tenant + CEO** to own affiliate research operationally.

---

**Please resubmit with:**
- The actual niche/task name
- Confirmation of whether this is a Tenant design conversation or something else
- Any missing data fields (`{aff_data_1}` — `{aff_data_4}`)