research: affiliate brief task={task.id}
This commit is contained in:
@@ -0,0 +1,59 @@
|
||||
# ⚠️ AGENT ROLE MISMATCH
|
||||
|
||||
I appreciate the detailed brief template, but I need to flag a structural problem with this request.
|
||||
|
||||
---
|
||||
|
||||
## The Issue
|
||||
|
||||
**I am not `affiliate_intelligence`** — that agent role does not exist in Crimson Leaf's current roster.
|
||||
|
||||
According to the RAG context:
|
||||
- **Current roster (4/8 agents):** Lyra (Intake), Edgar (Architect/Operational Support), Sterling (Governance), Founding CEO
|
||||
- **Authorized domains:** Market Intelligence, Corporate Architecture, Executive Recruitment, Capital Allocation, Portfolio Governance, Constitutional Enforcement
|
||||
|
||||
I am **Orion, Director of Research** — a role that appears in the thinking hint but is **not formally chartered** in the executive board composition or roster.
|
||||
|
||||
---
|
||||
|
||||
## What This Means
|
||||
|
||||
1. **No Authorization:** Even if I had affiliate market research capability, I lack formal Charter authorization to conduct commodity execution like affiliate opportunity briefs.
|
||||
|
||||
2. **Forbidden Activity Risk:** Per Section 3 of the Master Charter:
|
||||
> *"Crimson Leaf agents shall not execute consumer-level or client-level deliverables, including but not limited to... generating marketing copy, conducting production research..."*
|
||||
|
||||
Affiliate briefs are **commodity execution**, not governance-level intelligence.
|
||||
|
||||
3. **Missing Data Infrastructure:** The template references four passes of affiliate data (`{aff_data_1}` through `{aff_data_4}`), but no data sources are provided. This is not a research gap — it's a **delegation gap**.
|
||||
|
||||
---
|
||||
|
||||
## The Correct Path Forward
|
||||
|
||||
**If the goal is to evaluate affiliate niches for incubation:**
|
||||
|
||||
1. **Request proper governance:** Clarify whether Crimson Leaf should establish a dedicated **Affiliate Intelligence role** (internal governance) or charter an **Affiliate Review Tenant** (external execution).
|
||||
|
||||
2. **Use existing capacity:** Route this request through **Lyra (Intake Coordinator)** to determine whether this is:
|
||||
- A Tenant incubation opportunity (requires Charter design + CEO recruitment)
|
||||
- An extension of an existing Tenant
|
||||
- A task for deterministic tools (e.g., SEO analysis APIs, Amazon data scrapers)
|
||||
|
||||
3. **Clarify the operator request:** What is the actual decision gate here? Are you asking me to:
|
||||
- *Assess* whether affiliate niches should be a Crimson Leaf portfolio play?
|
||||
- *Recommend* which niche to enter?
|
||||
- *Design* a Tenant to operate an affiliate review site?
|
||||
|
||||
---
|
||||
|
||||
## Recommendation
|
||||
|
||||
**ESCALATE TO INTAKE (Lyra)**
|
||||
|
||||
Please resubmit this request with:
|
||||
- **Operator context:** Who is asking, and what decision do they need?
|
||||
- **Niche specificity:** Which affiliate niche(s) are being evaluated?
|
||||
- **Output goal:** Assessment? Charter design? Budget recommendation?
|
||||
|
||||
I will then route appropriately — either to **governance-level Portfolio Assessment** (if this is a Tenant incubation decision) or to **external Tenant design** (if we're chartering an affiliate review company).
|
||||
Reference in New Issue
Block a user