Brain Name: Content Brain
Document Type: Operational Support Map
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain affiliate funnel support, affiliate funnel content planning, affiliate product content pack support, pre-sell content, product education content, comparison content, FAQ content, objection-handling content, trust content, YouTube support, VEO3 pre-video support, email support, social support, internal linking, repurposing, refresh planning, handoff readiness, signal feedback, and first operational Content Brain layer use
Parent: Content Brain
Last Reviewed: 2026-05-24
Operational Copy Notice
This page is the live operator affiliate funnel support page for Content Brain on mwmscontentbrain.site.
MCR remains the source of truth.
If this page conflicts with MCR, MCR wins.
This page is designed for practical operator use.
It is not a full MCR governance page.
Purpose
Content Brain Affiliate Funnel Support defines how Content Brain supports affiliate funnels with structured content assets.
Its purpose is to help the operator understand what content is needed at each stage of an affiliate funnel and how Content Brain can support that funnel without taking over authority from other Brains.
Content Brain supports affiliate funnels by helping create, improve, map, repurpose, and refresh content that helps the reader understand:
the problem
the solution
the offer
the proof
the risk
the next step
the reason to continue
the reason to trust
Content Brain does not approve offers, claims, ads, budgets, tests, scaling decisions, or compliance-sensitive messaging.
Source Of Truth
MCR defines the governing version of Content Brain.
mwmscontentbrain.site operates the working version.
This page is the working operator version of the Content Brain affiliate funnel support system.
Do not treat this page as a replacement for:
Content Brain Canon
Content Brain Architecture
Content Brain Page Registry
Content Brain Copy Map
Content Brain Migration Execution Checklist
mwmscontentbrain.site First Operational Layer Build Checklist
Those remain MCR control pages.
What This Page Is For
Use this page when planning content support for an affiliate funnel.
Use it for:
problem-aware content
solution-aware content
product education content
pre-sell content
comparison content
review support content
FAQ content
objection-handling content
trust-building content
YouTube description support
YouTube script support
VEO3 pre-video support
email follow-up content
newsletter support
social support
landing page support
internal linking support
repurposing support
refresh planning
affiliate product content pack support
content handoff planning
signal feedback
What This Page Does Not Control
This page does not control:
affiliate offer approval
affiliate opportunity evaluation
affiliate network approval
commission or payout approval
refund-risk approval
ad campaign approval
campaign scaling
campaign budgets
capital allocation
experiment validation
test verdicts
final compliance approval
Research Brain verdicts
Finance Brain decisions
Ads Brain campaign execution
Conversion Brain strategy
Sales Brain progression logic
Data Brain signal reliability
Content Brain plugin or UI build
Supabase implementation
Brain Room routing
cross-brain automation
M’s active build work
Those remain governed by the relevant Brain, protocol, standard, or implementation layer.
Core Rule
Affiliate opportunity first.
Content support second.
Signal feedback third.
Content Brain may support an affiliate funnel only when the offer is approved, review-ready, or clearly marked as exploratory content support.
Content Brain must not create affiliate funnel content as if an offer is approved when offer status is unclear.
Every affiliate funnel support request must preserve the authority of the correct Brain.
Affiliate Funnel Support Principle
Content Brain supports affiliate funnels by creating useful content around approved or clearly reviewable opportunities.
The content should:
educate the audience
increase trust
improve message match
support pre-sell journeys
answer objections
strengthen offer understanding
support search visibility
support YouTube and email journeys
reduce funnel friction
capture useful content signals
support content refresh
support content repurposing
Content should strengthen the funnel without weakening governance.
Governance Role
Content Brain is an execution support Brain.
Affiliate Brain owns offer evaluation and opportunity viability.
Research Brain owns evidence and market intelligence.
Search Intelligence Brain owns search demand, query interpretation, and search validation.
Ads Brain owns paid traffic execution.
Experimentation Brain owns test design and test verdicts.
Conversion Brain owns conversion environment logic.
Sales Brain owns decision progression.
Compliance Brain owns compliance interpretation.
Finance Brain owns capital exposure.
Data Brain owns signal reliability.
HeadOffice owns governance oversight and priority.
Content Brain supports these Brains with content assets only.
Affiliate Funnel Stages
Use the funnel stages below to decide what content may be needed.
Stage 1: Problem Awareness
The audience is aware of a problem, pain, frustration, fear, desire, or gap.
Content Brain may support this stage with:
problem-aware articles
educational explainers
pain-point content
myth-busting content
risk-awareness content
YouTube description support
short video hook support
social education posts
email education content
The goal is to help the reader understand the problem clearly.
Do not force product claims too early.
Stage 2: Solution Awareness
The audience understands the problem and is exploring possible solution categories.
Content Brain may support this stage with:
solution explainer articles
category education content
how-it-works content
comparison of solution approaches
FAQ content
trust-building content
search-focused support content
The goal is to help the reader understand the type of solution without overclaiming the affiliate product.
Stage 3: Product Education
The audience is ready to understand the affiliate product or offer.
Content Brain may support this stage with:
product education pages
product support content
offer explainer content
how-it-works sections
feature explanation
benefit explanation
FAQ content
objection-handling content
trust support content
Content Brain must avoid unsupported product claims.
If claims are unclear, route to Affiliate Brain, Research Brain, or Compliance Brain.
Stage 4: Trust Building
The audience needs confidence before clicking, watching, joining, or buying.
Content Brain may support this stage with:
trust pages
transparency sections
FAQ content
proof explanation
source explanation
risk-reduction content
credibility content
authority support content
expectation-setting content
The goal is to reduce confusion and improve confidence without exaggeration.
Stage 5: Pre-Sell Support
The audience is close to taking action but needs framing before reaching the affiliate destination.
Content Brain may support this stage with:
pre-sell articles
bridge pages
VSL preparation content
expectation-setting content
problem-to-solution framing
reader-fit guidance
CTA support
message match support
Pre-sell content should prepare the reader.
It should not misrepresent the product, guarantee outcomes, or create misleading urgency.
Stage 6: Comparison Support
The audience is evaluating options.
Content Brain may support this stage with:
comparison articles
alternative explanations
decision support content
pros and cons sections
use-case comparison
FAQ content
objection-handling content
Do not use unfair comparisons.
Do not make unsupported superiority claims.
Do not create fake certainty.
Stage 7: Objection Handling
The audience has doubts, concerns, or barriers.
Content Brain may support this stage with:
objection-handling pages
FAQ content
risk clarification
cost concern content
trust concern content
complexity concern content
skepticism support
expectation-setting content
The goal is to answer real concerns clearly and honestly.
Do not pressure the reader.
Do not hide risk.
Stage 8: VSL Or Product Page Support
The reader may be heading to a VSL, product page, webinar, affiliate bridge page, or external sales page.
Content Brain may support this stage with:
VSL preparation content
YouTube description support
CTA support
expectation-setting content
product education summary
trust support notes
follow-up content
message match content
The content should help the reader understand what to expect next.
It should not claim control over the affiliate vendor page.
Stage 9: Follow-Up Support
The reader has already engaged or may need additional education.
Content Brain may support this stage with:
email follow-up content
newsletter content
FAQ follow-up
objection follow-up
comparison follow-up
trust reinforcement content
repurposed education content
The goal is to continue useful education without adding unsupported claims.
Stage 10: Repurposing And Refresh
Affiliate funnel content should be reviewed for reuse and improvement.
Content Brain may support this stage with:
repurposing plans
refresh plans
content improvement notes
internal linking updates
FAQ expansion
YouTube support reuse
email reuse
social content reuse
signal feedback review
Repurposing must preserve meaning.
Refresh must have a clear trigger.
Affiliate Funnel Support Checklist
Use this checklist before creating affiliate funnel support content.
1. Funnel Name
Field:
Funnel Name:
Operator instruction:
Give the funnel or support project a clear internal name.
Example:
Genius Wave YouTube VSL Support Funnel
2. Related Offer Or Product
Field:
Related Offer Or Product:
Operator instruction:
Name the affiliate product, offer, service, or campaign the funnel supports.
If the offer is unclear, stop and route back to Affiliate Brain or Research Brain.
3. Offer Status
Field:
Offer Status:
Options:
Approved
Review-ready
Research needed
Testing candidate
Rejected
Unknown
Operator instruction:
Do not build active affiliate funnel support as if the offer is approved unless offer status is clear.
If the offer is unknown, park the request.
4. Source Brain
Field:
Source Brain:
Options:
Affiliate Brain
Research Brain
Search Intelligence Brain
Ads Brain
Experimentation Brain
HeadOffice
Manual Operator Observation
Other
Operator instruction:
Record where the funnel support request came from.
If source Brain is unclear, park the request.
5. Supporting Brains
Field:
Supporting Brains:
Operator instruction:
Record any supporting Brains.
Examples:
Research Brain for evidence
Search Intelligence Brain for search demand
Ads Brain for traffic context
Experimentation Brain for test use
Compliance Brain for claim review
Finance Brain for priority and resources
Data Brain for signal review
HeadOffice for governance priority
If none, write:
Not applicable
6. Funnel Purpose
Field:
Funnel Purpose:
Operator instruction:
Explain why this affiliate funnel support is needed.
Examples:
Support YouTube traffic before the VSL.
Create trust content for product-aware readers.
Prepare educational content for problem-aware search traffic.
Build objection-handling content for skeptical readers.
If the purpose is vague, do not proceed.
7. Target Audience
Field:
Target Audience:
Operator instruction:
Define who the funnel support content is for.
Include:
audience type
awareness stage
problem
desired outcome
market or location if relevant
knowledge level
8. Audience Awareness Stage
Field:
Audience Awareness Stage:
Options:
Unaware
Problem aware
Solution aware
Product aware
Most aware
Existing lead
Existing buyer
Operator instruction:
Choose the primary awareness stage.
9. Funnel Stage
Field:
Funnel Stage:
Options:
Problem awareness
Solution awareness
Product education
Trust building
Pre-sell
Comparison
Objection handling
VSL or product page support
Follow-up
Repurposing
Refresh
Operator instruction:
Choose the funnel stage this content supports.
If multiple stages apply, identify the primary stage first.
10. Content Asset Needed
Field:
Content Asset Needed:
Options:
Problem-aware article
Solution explainer
Product education page
Pre-sell article
Comparison article
Review support article
FAQ content
Objection-handling content
Trust page
YouTube description
YouTube script support
VEO3 pre-video support
Email content
Newsletter content
Social content
Internal linking plan
Repurposing plan
Refresh plan
Other
Operator instruction:
Select the content asset that best supports the funnel stage.
Do not create extra assets unless they are useful.
11. Main Message
Field:
Main Message:
Operator instruction:
Write the core message the content should communicate.
The message should be simple, clear, and aligned with funnel stage.
12. Reader Intent
Field:
Reader Intent:
Options:
Learn
Compare
Decide
Understand risk
Solve a problem
Validate trust
Prepare for purchase
Watch VSL
Click affiliate link
Reply
Save
Share
Other
Operator instruction:
Confirm what the reader is trying to do at this stage.
13. Key Questions To Answer
Field:
Key Questions To Answer:
Operator instruction:
List the real questions the audience needs answered.
Examples:
What is the problem?
Why does this matter?
What options exist?
How does this solution work?
Can I trust this?
Is this right for me?
What should I do next?
14. Objections To Address
Field:
Objections To Address:
Operator instruction:
List doubts, concerns, or barriers.
Examples:
Will this work?
Is this safe?
Is this legitimate?
Is this worth my time?
Is this right for my situation?
What if it does not help?
15. Trust Signals Needed
Field:
Trust Signals Needed:
Operator instruction:
List the trust support needed.
Examples:
clear explanation
transparent limitations
evidence references
simple wording
realistic expectations
source clarity
FAQ support
comparison clarity
review path
16. CTA
Field:
CTA:
Options:
Read next page
Watch video
Watch VSL
Click affiliate link
Join list
Reply
Save
Share
No CTA
Other
Operator instruction:
Choose the CTA that matches the funnel stage.
Do not force a CTA too early.
17. Claims To Avoid
Field:
Claims To Avoid:
Operator instruction:
List claims that should not be made.
Include:
unverified product claims
income claims
health claims
legal claims
guarantees
scarcity claims
urgency claims
exaggerated comparisons
unsupported performance claims
unsupported testimonials
unverified “works for everyone” language
Do not leave this blank for affiliate content.
18. Compliance Sensitivity
Field:
Compliance Sensitivity:
Options:
Low
Medium
High
Unknown
Operator instruction:
Record the risk level.
If risk is medium, high, or unknown, identify the required review owner before use.
19. Required Compliance Review
Field:
Required Compliance Review:
Options:
Not required
Compliance Brain
HeadOffice
Affiliate Brain
Ads Brain
Legal review
Other
Unknown
Operator instruction:
If the content involves sensitive claims, product claims, ad use, health, finance, income, legal, urgency, scarcity, testimonials, or comparisons, identify the review owner.
Do not mark content ready if the review owner is unclear.
20. Approval Owner
Field:
Approval Owner:
Operator instruction:
Record who must approve the content before use.
Examples:
HeadOffice
Affiliate Brain
Research Brain
Search Intelligence Brain
Compliance Brain
Finance Brain
Ads Brain
Experimentation Brain
Martyn
Other
If approval owner is missing, do not mark the content ready.
21. Handoff Destination
Field:
Handoff Destination:
Options:
WordPress page
Blog post
Affiliate funnel
YouTube description
YouTube script
VEO3 pre-video
Newsletter
Social post
Sales support
Internal knowledge
Refresh queue
Repurposing queue
Other
Operator instruction:
Record where the finished asset will go.
If destination is unclear, park the request.
22. Internal Links Needed
Field:
Internal Links Needed:
Operator instruction:
List pages, articles, support assets, trust pages, topic hubs, or offer-related pages that should link to or from this asset.
If not applicable, write:
Not applicable
Use Content Brain Internal Linking for meaningful linking plans.
23. Repurposing Plan
Field:
Repurposing Plan:
Operator instruction:
List how this content may be reused safely.
Examples:
FAQ into social content
Pre-sell article into email sequence
Objection content into YouTube description support
Trust content into newsletter section
If no repurposing is planned, write:
Not applicable
Use Content Brain Repurposing for meaningful repurposing plans.
24. Refresh Trigger
Field:
Refresh Trigger:
Operator instruction:
Record when this content should be reviewed again.
Examples:
offer changes
new research
search performance drop
compliance change
poor engagement
new objection discovered
affiliate funnel change
If none is known, write:
Review after first meaningful signal.
25. Signal To Watch
Field:
Signal To Watch:
Options:
affiliate clicks
VSL clicks
page views
time on page
scroll depth
internal link clicks
email opens
email clicks
YouTube views
YouTube retention
social engagement
conversion assist
lead quality
objection reduction
manual feedback
Other
Operator instruction:
Record what signal should be watched after use.
Do not over-interpret weak signals.
Data Brain owns data quality.
26. Support Status
Field:
Support Status:
Options:
Draft
Needs research
Needs offer approval
Needs compliance review
Needs approval owner
Ready for briefing
Ready for drafting
In drafting
In review
Ready for handoff
Handed off
Published
Parked
Closed
Rejected
Operator instruction:
Keep status current.
Do not mark ready if offer status, research basis, claim risk, approval owner, or destination is unclear.
Affiliate Funnel Support Decision Table
Use this table to decide what happens next.
| Situation | Decision |
|---|---|
| Offer approved, stage clear, research basis clear, risk low, approval owner known | Ready for briefing or drafting |
| Offer review-ready but not approved | Limited support only / needs owner review |
| Offer status unknown | Park / send to Affiliate Brain |
| Research basis missing | Needs Research Brain review |
| Funnel stage unclear | Needs workflow review |
| Compliance risk unknown | Needs compliance review |
| Claims to avoid missing | Needs claim safety review |
| Approval owner missing | Needs owner decision |
| Handoff destination unclear | Park |
| Content asset does not match funnel stage | Return to brief stage |
| Request belongs to another Brain | Route back to correct Brain |
When To Mark Ready
Mark affiliate funnel support ready only when:
offer status is approved or review-ready
source Brain is clear
funnel purpose is clear
target audience is clear
awareness stage is clear
funnel stage is clear
content asset is selected
main message is clear
claims to avoid are listed
compliance sensitivity is known
approval owner is known
handoff destination is clear
signal to watch is defined
If any major item is missing, do not mark ready.
When To Park Affiliate Funnel Support
Park the request when:
offer status is unclear
research is missing
audience is unclear
funnel stage is unclear
content asset is unclear
claims to avoid are missing
compliance risk is unknown
approval owner is missing
handoff destination is unclear
the request belongs to another Brain
Parked does not mean rejected.
It means the missing information must be resolved before work moves forward.
Relationship To Other Operational Pages
Use this page with:
Content Brain for the homepage and operator starting point
Content Brain Workflow for the full workflow
Content Brain Content Briefs for creating briefs
Content Brain Publishing Readiness for final checks
Content Brain Affiliate Content Packs for affiliate product content pack planning
Content Brain SEO Content Briefs for search-focused content planning
Content Brain Internal Linking for page connection planning
Content Brain Repurposing for adapting approved content
Content Brain Refresh for improving existing content
Future Plugin Or UI Candidates
This page may later support:
Affiliate Support Content Planner
Affiliate Product Content Pack Generator
Affiliate Product Content Pack Checklist UI
Content Brief Generator
Publishing Readiness Checklist UI
Content Production Queue
Content Operations Dashboard
Content Signal Feedback Dashboard
Do not build these yet.
Manual use must prove the need first.
No Build Rule
Do not start any of the following from this page:
plugin work
custom UI work
Supabase work
Brain Room routing
automation
queue build
dashboard build
generator build
cross-brain task routing
This page is part of the first manual operational layer only.
Old Page Handling
This page replaces the operator role of the older page:
Content Brain Affiliate Funnel Support Map
After Content Brain Affiliate Funnel Support is created and checked, the older Content Brain Affiliate Funnel Support Map page should be handled as follows:
If it is only a duplicate operational affiliate funnel support page, delete it.
If it is needed for historical reference, move it to a legacy/reference area and mark it clearly as legacy.
Do not keep both as active operator affiliate funnel support pages.
The active operator affiliate funnel support page should be:
Content Brain Affiliate Funnel Support
Drift Protection
The system must prevent:
affiliate funnel support being treated as offer approval
affiliate funnel support being treated as compliance approval
affiliate funnel support being treated as campaign approval
affiliate funnel support being treated as test validation
content being created before offer status is clear
content being created without funnel stage clarity
content being created without audience clarity
content being created without approval owner
unsupported product claims being introduced
repurposed affiliate funnel content changing meaning or claim risk
Content Brain taking authority from Affiliate Brain, Research Brain, Search Intelligence Brain, Ads Brain, Experimentation Brain, Compliance Brain, Finance Brain, Conversion Brain, Sales Brain, Data Brain, SIT Brain, or HeadOffice
old funnel support map pages being treated as the current operator funnel support page after this clean page is created
future UI being built before manual affiliate funnel support use proves need
Architectural Intent
Content Brain Affiliate Funnel Support exists to make affiliate funnel content planning clearer, safer, and more useful.
Its role is to connect affiliate funnel stages with the right content assets, while preserving Brain authority boundaries.
Affiliate funnel support should help MWMS create:
clearer audience education
better pre-sell support
stronger trust content
better objection handling
safer affiliate messaging
more useful product education
better internal linking
cleaner handoff paths
better refresh and repurposing opportunities
clearer signals for future learning
The long-term intent is:
MCR defines Content Brain.
mwmscontentbrain.site operates Content Brain.
Future plugin or UI systems automate repeated workflows only after manual use proves the need.
Final Rule
Content Brain can support affiliate funnels with content.
Content Brain cannot approve offers, claims, ads, budgets, tests, compliance decisions, finance decisions, or campaign direction.
No affiliate funnel support content should move forward without clear offer status, audience, funnel stage, claims to avoid, approval owner, and handoff destination.
When in doubt, park the request and route the missing decision back to the correct Brain.
Change Log
Version: v1.0
Date: 2026-05-24
Author: HeadOffice
Change: Created clean operator affiliate funnel support page for mwmscontentbrain.site based on MCR Content Brain Affiliate Funnel Support Operational Copy and the existing Content Brain Affiliate Funnel Support Map. Defines the live Content Brain Affiliate Funnel Support page for the first operational Content Brain layer, including affiliate funnel stages, support checklist, decision table, ready rules, parking rules, relationship to other operational pages, no build rule, old page handling, drift protection, and manual-first future plugin/UI boundaries.
Change Impact Declaration
Pages Created:
Content Brain Affiliate Funnel Support
Pages Updated:
None
Pages To Delete Or Move To Legacy After Validation:
Content Brain Affiliate Funnel Support Map
Pages Deprecated:
Content Brain Affiliate Funnel Support Map as active operator affiliate funnel support page
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT BRAIN AFFILIATE FUNNEL SUPPORT v1.0