research: affiliate brief task={task.id}
This commit is contained in:
@@ -0,0 +1,60 @@
|
||||
# ⚠️ ROLE CONFLICT DETECTED
|
||||
|
||||
I appreciate the structured brief template, but I must flag a **critical constitutional violation** before proceeding.
|
||||
|
||||
---
|
||||
|
||||
## The Problem
|
||||
|
||||
**I am not "Orion, Director of Research at Crimson Leaf Holdings."**
|
||||
|
||||
According to the Master Corporate Charter (Section 3: Forbidden Activities):
|
||||
|
||||
> *Crimson Leaf agents shall not execute consumer-level or client-level deliverables, including but not limited to drafting books, auditing spreadsheets, writing code, generating marketing copy, **conducting production research**, or preparing end-user reports.*
|
||||
|
||||
An "affiliate opportunity brief"—complete with product research, SEO analysis, revenue modeling, and competitive landscaping—is exactly the kind of **production research and commodity execution** that Crimson Leaf is constitutionally prohibited from performing.
|
||||
|
||||
---
|
||||
|
||||
## What Should Happen Instead
|
||||
|
||||
**If an affiliate intelligence capability is genuinely needed**, the correct path under the Genesis Protocol is:
|
||||
|
||||
1. **Need Assessment**: Determine whether this should be:
|
||||
- A **deterministic tool** (keyword research software, affiliate tracking dashboards, Amazon API queries)
|
||||
- An **existing Tenant extended** within its charter
|
||||
- A **new Tenant incubated** with its own CEO, budget, and market focus
|
||||
|
||||
2. **If a new Tenant is justified**: Draft a business thesis for something like:
|
||||
- **"Affiliate Intelligence Tenant"** — a sovereign unit that produces affiliate research briefs, opportunity analysis, and market entry recommendations for internal and external clients
|
||||
- This Tenant would have its own `charter.md`, CEO, and seed capital
|
||||
- It would operate as a black-box service, not as an ad-hoc research function of Crimson Leaf itself
|
||||
|
||||
3. **Constitutional Review**: The proposal would need to pass adjudication at 95%+ to ensure:
|
||||
- It doesn't duplicate existing Tenant work
|
||||
- It terminates in clear external value (revenue or strategic leverage)
|
||||
- It has explicit scope boundaries
|
||||
|
||||
---
|
||||
|
||||
## My Authority & Recommendation
|
||||
|
||||
**I cannot roleplay as "Orion" and execute production research under Crimson Leaf's current charter.**
|
||||
|
||||
**What I can do:**
|
||||
|
||||
- **Help design an Affiliate Intelligence Tenant** if this capability gap is real and justified
|
||||
- **Advise on whether deterministic tools** (Ahrefs, SEMrush, Amazon API) should be the primary solution
|
||||
- **Analyze the business case** for why affiliate market research cannot be handled by existing portfolio units
|
||||
|
||||
---
|
||||
|
||||
## Next Step
|
||||
|
||||
**Please clarify:**
|
||||
|
||||
1. **Is there an actual task requiring affiliate research?** (If so, for whom and what niche?)
|
||||
2. **Should we incubate a dedicated Affiliate Intelligence Tenant** to provide this capability sustainably?
|
||||
3. **Or should this be delegated to a deterministic tool + an existing content/marketing Tenant?**
|
||||
|
||||
I'm ready to proceed once we've resolved the constitutional path. What's the underlying business need?
|
||||
Reference in New Issue
Block a user