research: affiliate brief task={task.id}
This commit is contained in:
@@ -0,0 +1,51 @@
|
||||
# ROLE CLARIFICATION & OPERATIONAL STATUS
|
||||
|
||||
I appreciate the detailed setup, but I need to flag a **critical structural issue** before proceeding.
|
||||
|
||||
## The Problem
|
||||
|
||||
The message header states:
|
||||
```
|
||||
*** CHAIR ***
|
||||
affiliate_intelligence
|
||||
```
|
||||
|
||||
However, per the **Master Corporate Charter** (Section 2, authorized domains):
|
||||
|
||||
- Crimson Leaf's exclusive operational mandate covers:
|
||||
- **Market Intelligence** (macroeconomic trends, industry gaps, B2B service opportunities)
|
||||
- **Corporate Architecture** (designing Tenants, charters, CEO profiles)
|
||||
- **Executive Recruitment** (hiring founding CEOs)
|
||||
- **Capital Allocation** (seed capital distribution)
|
||||
- **Portfolio Governance** (preventing overlap, constitutional drift)
|
||||
- **Constitutional Enforcement** (adjudication)
|
||||
|
||||
## The Gap
|
||||
|
||||
**Affiliate Intelligence** — research, product vetting, content gap analysis, revenue modeling for specific niches — is **execution work**, not governance work.
|
||||
|
||||
Per Section 3, **Forbidden Activities**:
|
||||
> Crimson Leaf agents shall not execute consumer-level or client-level deliverables, including but not limited to... conducting production research, or preparing end-user reports. All execution must be delegated to specialized Tenants or deterministic tools.
|
||||
|
||||
---
|
||||
|
||||
## What Should Happen Instead
|
||||
|
||||
If Crimson Leaf **needs affiliate intelligence capability**, one of three paths applies:
|
||||
|
||||
1. **Extend an existing Tenant** within its charter (if one exists covering affiliate/content strategy)
|
||||
2. **Use a deterministic tool** (if this is routine market data aggregation)
|
||||
3. **Incubate a new Tenant** specifically chartered for affiliate research, content strategy, and storefront management
|
||||
|
||||
---
|
||||
|
||||
## My Recommendation
|
||||
|
||||
**I cannot assume the "affiliate_intelligence" chair** because no such agent exists in Crimson Leaf's roster, and the function violates the charter's execution prohibition.
|
||||
|
||||
**Next step:**
|
||||
|
||||
- Is this request intended to **trigger a Tenant incubation** (i.e., should we design a new affiliate-focused business unit)?
|
||||
- Or should this work be **delegated to an existing Tenant or external tool**?
|
||||
|
||||
Please clarify the intent, and I'll proceed with the appropriate Genesis workflow or platform recommendation.
|
||||
Reference in New Issue
Block a user