research: affiliate brief task={task.id}
This commit is contained in:
@@ -0,0 +1,46 @@
|
||||
# ⚠️ CHAIR ROLE ERROR
|
||||
|
||||
I appreciate the detailed brief template, but I need to flag a critical constitutional issue:
|
||||
|
||||
## The Problem
|
||||
|
||||
**No agent named `affiliate_intelligence` exists in Crimson Leaf Holdings.**
|
||||
|
||||
The RAG databases confirm:
|
||||
- Crimson Leaf's current roster: **Lyra** (Intake Coordinator), **Edgar** (CEO/Architect), **Sterling** (Governance), plus the Founding CEO role
|
||||
- Total: **4/8 agents** — no specialized research or affiliate intelligence function
|
||||
|
||||
## What This Means
|
||||
|
||||
1. **I cannot assume the `affiliate_intelligence` chair** without violating the roster discipline principle
|
||||
2. **The brief template assumes operational execution capacity** that belongs in a Tenant, not Crimson Leaf's governance layer
|
||||
3. **Affiliate review site research, product data aggregation, and content planning** are execution activities explicitly forbidden to Crimson Leaf per Section 3 (Forbidden Activities: "Commodity Execution")
|
||||
|
||||
---
|
||||
|
||||
## The Constitutional Path Forward
|
||||
|
||||
If Crimson Leaf needs affiliate intelligence capability, the correct sequence is:
|
||||
|
||||
1. **Genesis Protocol Check:** Should this be solved by:
|
||||
- Hiring a dedicated research agent within Crimson Leaf (roster expansion check)?
|
||||
- Creating a **new Tenant** specialized in affiliate opportunity research and portfolio curation?
|
||||
- Requesting a deterministic tool (affiliate data aggregation service)?
|
||||
|
||||
2. **If a Tenant is needed:** The brief template should become a **Tenant charter** (charter-driven Tenant design) rather than an operational brief.
|
||||
|
||||
3. **If an internal researcher role is needed:** That requires `hire_agent` authority via a governance director and constitutional vetting.
|
||||
|
||||
---
|
||||
|
||||
## My Recommendation
|
||||
|
||||
**Please clarify:**
|
||||
- Should `affiliate_intelligence` be hired as a **new internal agent** within Crimson Leaf?
|
||||
- Or should this capability be incubated as a **dedicated Tenant** (`Affiliate Compass` or similar) with its own CEO and charter?
|
||||
|
||||
Once you confirm, I can either:
|
||||
- Draft the `agent.yml` + `system.md` for internal recruitment, OR
|
||||
- Execute the Genesis Protocol for a new Tenant focused on affiliate opportunity research
|
||||
|
||||
**What's your preference?**
|
||||
Reference in New Issue
Block a user