crimson_leaf/deliverables/affiliate-intelligence/affiliate-brief-662f8c00-a68b-4c68-bfdd-69959cfa4375.md

I appreciate the detailed context, but I need to flag a critical structural issue before proceeding.

---

The Problem

I am listed as "affiliate_intelligence" in the chair designation, but according to the Crimson Leaf charter and RAG context:

1. No such agent exists in the current roster. The documented Crimson Leaf internal roster is: Lyra (Intake), Edgar (Architect/CEO), Sterling (Governance), plus a Founding CEO seat — totaling 4/8 agents.

2. This violates the charter's prohibition on undefined roles. Section 3 ("Forbidden Activities") explicitly forbids Crimson Leaf from operating as a service provider. The charter is clear: Crimson Leaf does not execute deliverables (including market research or affiliate brief generation). Execution is delegated to sovereign Tenants with their own CEOs, charters, and budgets.

3. The task request itself is a commodity execution task — drafting a business brief for affiliate marketing — which the charter explicitly prohibits Crimson Leaf from performing (Section 3: "drafting books, auditing spreadsheets, writing code, generating marketing copy, conducting production research, or preparing end-user reports").

4. The data placeholders are empty — {aff_data_1}, {aff_data_2}, {aff_data_3}, {aff_data_4} — so there is no actual research to synthesize.

---

What Should Happen Instead

Option A: Tenant Creation If Crimson Leaf's portfolio needs affiliate marketing intelligence as a distinct capability, the proper path is:

1. Draft a Tenant charter for an "Affiliate Intelligence & Content Unit" with its own CEO, market focus, and budget.
2. Route this through the Genesis Protocol (architectural audit → charter refinement → capital thesis → 95% adjudication threshold).
3. Hire the founding CEO, provision the Tenant, and empower them to build the affiliate research practice.

Option B: Deterministic Tool Delegation If this is a one-off research request, Crimson Leaf should:

1. Confirm the actual affiliate niche in question.
2. Delegate to existing web scraping, SEO, and keyword research tools (SEMrush, Ahrefs, Google Keyword Planner, etc.).
3. Synthesize results in a brief, but not as a governance artifact—as a routing document to a future Tenant or external service.

Option C: Clarify the Operator's Intent Is this a test of constitutional enforcement? A genuine request to scope a new Tenant? Or misrouting of a task intended for a different system?

---

My Recommendation

Do not proceed with affiliate brief generation under the "affiliate_intelligence" chair.

Instead, clarify:

1. Does Crimson Leaf need a dedicated Affiliate Intelligence Tenant?
2. Or is this research input for a different decision (e.g., scoping a future Indie Author Affiliate Tenant)?
3. What is the actual niche being researched?

I'm ready to support either path—but only within constitutional boundaries.