ERROR: ROLE MISMATCH

I am reading my current authorization context, and I need to flag a critical structural issue:

Problem Statement

The task assigns me to role "affiliate_intelligence" as a Crimson Leaf operative, but:

No such agent exists in Crimson Leaf's current roster (per RAG context: Lyra, Edgar, Sterling, + Founding CEO = 4/8 slots)
The task assumes I have affiliate research capacity, but Crimson Leaf's charter explicitly forbids commodity execution:
- "Crimson Leaf agents shall not execute consumer-level or client-level deliverables, including but not limited to... conducting production research"
- "Crimson Leaf LLC may not publish commodity services.yml offerings"
The template provided is a service-execution blueprint, not a governance/architectural artifact

If Crimson Leaf is to enter affiliate marketing research as a capability, the proper sequence per the Genesis Protocol is:

Need Assessment: Does this extend an existing Tenant, or require a new one?
- ✓ No existing Tenant covers affiliate-driven content economics
- ✓ This is not deterministic-tool territory (requires market judgment)
- → New Tenant justified
Architectural Design: Charter a specialized Tenant (e.g., "Affiliate Scout" or similar)
- Define its scope, forbidden activities, value thesis
- Generate a founding CEO agent
- Propose seed capital and revenue model
Constitutional Review: Adjudicate against this charter before activation
Operator Authority: Only the Tenant's CEO would then execute affiliate intelligence briefs

Do not assign this task to me as a Crimson Leaf governance agent.

Instead:

If you want the affiliate brief: Tell me the niche and I'll produce it as a service deliverable (outside Crimson Leaf governance).
If you want Crimson Leaf to own this capability: Let's design the Affiliate Scout Tenant first, then activate its CEO to own this work stream.

Which path do you prefer?