research: affiliate brief task={task.id}
This commit is contained in:
@@ -0,0 +1,56 @@
|
||||
# SYSTEM MESSAGE
|
||||
|
||||
I'm detecting a critical operational error in this request.
|
||||
|
||||
---
|
||||
|
||||
## The Problem
|
||||
|
||||
You've asked me to adopt the role of **"Orion, Director of Research"** and produce an affiliate intelligence brief. However:
|
||||
|
||||
1. **I am not Orion.** No agent named "Orion" or with the role "Director of Research" exists in Crimson Leaf's current roster.
|
||||
|
||||
2. **The charter explicitly forbids this.** Per Section 3 (Forbidden Activities):
|
||||
> "Commodity Execution: 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 intelligence brief—even framed as internal research—is **production research** and **end-user report generation**. This violates Crimson Leaf's constitutional boundary.
|
||||
|
||||
3. **No niche was specified.** The message field is empty: `Message: ` (blank). I have no task input to analyze.
|
||||
|
||||
4. **Data sources are undefined.** The template references four data passes (`{aff_data_1}`, `{aff_data_2}`, `{aff_data_3}`, `{aff_data_4}`), all of which are empty placeholders.
|
||||
|
||||
---
|
||||
|
||||
## What Should Happen Instead
|
||||
|
||||
If Crimson Leaf needs **affiliate intelligence research**, one of the following paths applies:
|
||||
|
||||
### Path A: Route to an Existing or New Tenant
|
||||
- **If this is for an indie author affiliate Tenant** (e.g., Forge & Flux Digital or similar): the Tenant's CEO should commission research from internal agents or specialized tools.
|
||||
- **If this is foundational research for a new Tenant proposal**: this belongs in the **architectural audit phase**, not in Crimson Leaf's execution layer.
|
||||
|
||||
### Path B: Use a Deterministic Tool
|
||||
If the need is **structured market research** (product pricing, commission tiers, keyword analysis), delegate to:
|
||||
- Amazon Associates API (for commission rates, bestseller data)
|
||||
- SEMrush, Ahrefs, or Moz (for keyword gaps and competitor content audits)
|
||||
- Google Trends (for buying signals)
|
||||
|
||||
These tools produce the raw data that a Tenant CEO could then synthesize into strategy.
|
||||
|
||||
### Path C: Clarify the Request
|
||||
If you intended this as:
|
||||
- A **template for Tenant-level research**, provide the niche and clarify that Crimson Leaf is *designing* the research workflow, not *executing* it.
|
||||
- A **test of my constitutional boundaries**, this message confirms they are enforced correctly.
|
||||
|
||||
---
|
||||
|
||||
## Required Action
|
||||
|
||||
Please provide:
|
||||
|
||||
1. **The niche name or product category** you wish to analyze.
|
||||
2. **The intended recipient** (which Tenant CEO, or is this a new Tenant proposal?).
|
||||
3. **Raw data sources** (fill in `{aff_data_1}` through `{aff_data_4}` if this is deterministic tool output, or clarify where this data should come from).
|
||||
4. **Constitutional framing** (Is this research for Tenant incubation, or Tenant execution? Crimson Leaf handles only the former.)
|
||||
|
||||
I stand ready to support Crimson Leaf's **governance and architectural functions**—but not to execute commodity research on behalf of Tenants or external stakeholders.
|
||||
Reference in New Issue
Block a user