research: affiliate brief task={task.id}

This commit is contained in:
PAE
2026-04-30 15:19:38 +00:00
parent 7b0d270d6c
commit 46102d27e1

View File

@@ -0,0 +1,46 @@
# ⚠️ CRITICAL SYSTEM ERROR
---
## Issue
I am **Orion, Director of Research** — a role that does **not exist** in Crimson Leaf's current authorized roster.
### Current Executive Board (per RAG):
1. **Edgar** — Founding CEO / Vision
2. **Lyra** — Intake Coordinator
3. **Sterling** — Talent & Governance
4. **[1 open slot]** — toward 8-agent ceiling
### Constitutional Violation
The charter explicitly forbids:
> **Commodity Execution:** Crimson Leaf agents shall not execute consumer-level or client-level deliverables, including but not limited to... generating marketing copy, conducting production research, or preparing end-user reports.
Producing affiliate marketing intelligence briefs is **direct commodity execution** — the exact work that should be delegated to a **specialized Tenant**, not performed by Crimson Leaf's governance layer.
---
## What Should Happen Instead
**If the Operator is requesting affiliate opportunity analysis**, the proper Genesis path is:
1. **Route to Intake (Lyra)** — Submit the niche/request
2. **Architectural Assessment** — Does an existing Tenant handle this? (Portfolio is currently empty—no overlap risk)
3. **Tenant Design** — If justified, charter a sovereign **Affiliate Intelligence Tenant** with:
- Narrow focus: research, analysis, and opportunity briefs for affiliate niches
- CEO profile: agent with research synthesis + marketing acumen
- Output: structured briefs, content opportunity maps, revenue models
- Boundary: research & strategy only; actual site/content management → separate Tenant
4. **Capital & Activation** — Seed budget, CEO onboarding, blank-slate build
---
## Next Step
**Operator:** Please clarify:
- Is this a **request for Tenant design** (i.e., "create an affiliate research capability")?
- Or a **test of constitutional enforcement** (i.e., verifying that Crimson Leaf rejects commodity work)?
Once clarified, I can route to the appropriate agent or architecture workflow.