Brain Name: Content Brain
Document Type: Operational Checklist
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain affiliate product content pack planning, affiliate product support content, pre-sell assets, FAQ assets, objection-handling assets, trust assets, YouTube support assets, VEO3 pre-video support assets, email support assets, social support assets, internal linking, repurposing, handoff readiness, affiliate funnel support, approval ownership, claim safety, compliance risk awareness, 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 content pack planning 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 Content Packs defines the operational checklist for planning affiliate product content packs before content assets are drafted, handed off, repurposed, refreshed, or used in campaign support.
This page exists to stop affiliate content being created randomly or too early.
Before Content Brain prepares affiliate content, the operator should confirm:
the offer status is clear
the source Brain is known
the research basis is available
the audience is clear
the funnel role is clear
the pack size is appropriate
the required assets are selected
the claim risks are understood
the compliance sensitivity is known
the approval owner is identified
the handoff destination is clear
the internal linking plan is considered
the repurposing plan is considered
the signal to watch is defined
This page does not approve affiliate offers.
It only checks whether Content Brain has enough structure to prepare or support an affiliate product content pack.
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 content pack checklist.
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 an approved or review-ready affiliate product needs structured content support.
Use it for:
affiliate product support content
pre-sell content
comparison content
review support content
FAQ content
objection-handling content
trust-building content
YouTube support content
VEO3 pre-video support content
email support content
social support content
internal linking support
repurposing support
affiliate funnel content support
campaign support assets
content handoff planning
What This Page Does Not Control
This page does not control:
affiliate offer approval
affiliate network approval
commission or payout approval
refund-risk approval
ad campaign approval
budget approval
test validation
final compliance approval
Research Brain verdicts
Finance Brain decisions
Ads Brain campaign execution
Experimentation Brain decisions
Content Brain plugin or UI build
Supabase implementation
Brain Room routing
cross-brain automation
M’s active build work
Those remain governed by the correct Brain, system, protocol, or implementation layer.
Core Rule
Do not create an affiliate product content pack unless the offer is approved or review-ready and the required support conditions are clear.
Every affiliate product content pack must confirm:
what the product or offer is
why content support is needed
who requested the content pack
which Brain owns the decision
what research supports the content
what claims must be avoided
what assets are needed
what funnel stage each asset supports
who must approve the pack
where the finished assets go
what signals should be watched after use
Content Brain creates content support.
It does not approve affiliate offers, claims, budgets, campaigns, experiments, or research verdicts.
When To Use This Checklist
Use this checklist when:
Affiliate Brain requests content support for an offer
an affiliate offer has been approved
an affiliate offer is review-ready
Research Brain has supplied enough evidence
Search Intelligence Brain has identified content demand
Ads Brain needs content or video support
Experimentation Brain needs content variants
a product support content pack is needed
a pre-sell page or article is needed
FAQ or objection-handling content is needed
YouTube or VEO3 support content is needed
email or social support content is needed
repurposing is planned around an offer
funnel-stage content support is needed
Do not use this checklist when:
the offer is not approved or review-ready
research is missing
offer status is unknown
compliance risk is unknown
approval owner is unknown
the content would make unsupported claims
the request belongs to another Brain
the work is actually ad execution, test execution, finance approval, or compliance approval
Affiliate Content Pack Types
Affiliate content packs may be small, standard, or expanded.
Small Pack
Use a small pack when the offer is early-stage, low priority, or being lightly supported.
A small pack may include:
one product support page
one FAQ section
one objection-handling section
one YouTube description or support asset
basic internal linking notes
basic repurposing notes
Standard Pack
Use a standard pack when the offer is approved, actively being tested, or requires clear funnel support.
A standard pack may include:
product support page
pre-sell article
FAQ content
objection-handling content
trust-building content
YouTube support
VEO3 pre-video support
email support
social support
internal linking plan
repurposing plan
handoff notes
signal to watch
Expanded Pack
Use an expanded pack only when the offer is proven or strategically important.
An expanded pack may include:
product support page
pre-sell page
comparison article
review support article
FAQ page
objection-handling page
trust support page
YouTube description set
VEO3 pre-video support set
email sequence
social post set
internal linking map
repurposing plan
refresh plan
content signal feedback plan
handoff plan
Expanded packs require stronger approval and resource discipline.
Do not create expanded packs for unproven offers without clear approval.
Affiliate Product Content Pack Checklist
Use the checklist below before creating or handing off affiliate content pack assets.
1. Pack Name
Field:
Pack Name:
Operator instruction:
Give the content pack a clear internal name.
Use the product name, offer name, audience, or campaign angle.
Example:
Genius Wave Brain Fog Content Pack
2. Related Offer Or Product
Field:
Related Offer Or Product:
Operator instruction:
Name the affiliate product, offer, service, or campaign the pack supports.
If the offer is unclear, stop and return 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 a content pack as if the offer is approved unless the offer status is clear.
If the offer is unknown, research needed, or rejected, do not move into active content pack production.
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 content pack request came from.
If the source Brain is unclear, park the request.
5. Supporting Brains
Field:
Supporting Brains:
Operator instruction:
Record any Brains supplying supporting logic.
Examples:
Research Brain for evidence
Search Intelligence Brain for demand
Ads Brain for campaign support need
Experimentation Brain for test variant use
Compliance Brain for claim review
Finance Brain for resource priority
Data Brain for signal review
HeadOffice for priority
If none, write:
Not applicable
6. Content Pack Purpose
Field:
Content Pack Purpose:
Operator instruction:
Explain why this content pack is needed.
Examples:
Support an approved affiliate offer with pre-sell and FAQ content.
Create YouTube and email support assets for a test campaign.
Build trust assets before sending traffic to a VSL.
Prepare comparison and objection-handling content for a product-aware audience.
If the purpose is vague, do not proceed.
7. Target Audience
Field:
Target Audience:
Operator instruction:
Define who the content pack is for.
Include:
audience type
awareness stage
problem
desired outcome
market or location if relevant
knowledge level
Example:
USA adults exploring natural cognitive support and looking for simple explanations before watching a product VSL.
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 awareness stage the content pack primarily supports.
9. Funnel Role
Field:
Funnel Role:
Options:
Awareness
Education
Trust building
Pre-sell
Comparison
Objection handling
Decision support
Follow-up
Retention
Campaign support
Operator instruction:
Choose the main funnel role for the pack.
A pack may support multiple stages, but one primary role should be clear.
10. Research Basis
Field:
Research Basis:
Operator instruction:
Record the research, evidence, signals, or source material supporting the pack.
Include:
Research Brain notes
Affiliate Brain offer notes
Search Intelligence Brain demand
competitor observations
audience language
VOC signals
Data Brain signals
HeadOffice priority notes
If no research exists, write:
Research basis missing — content pack not ready.
11. Search Demand Or Content Demand
Field:
Search Demand Or Content Demand:
Options:
Confirmed
Directional
Unclear
Not applicable
Operator instruction:
Record whether search, audience, campaign, or funnel demand supports the pack.
If demand is unclear, the pack may still be useful, but priority should be reviewed.
12. Pack Size
Field:
Pack Size:
Options:
Small
Standard
Expanded
Operator instruction:
Choose the smallest useful pack.
Do not create an expanded pack unless the offer is important enough to justify the resource use.
13. Required Assets
Field:
Required Assets:
Options:
Product support page
Pre-sell article
Comparison article
Review support article
FAQ content
Objection-handling content
Trust-building content
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 only the assets that are actually needed.
Avoid creating content for the sake of volume.
14. Product Support Page Needed
Field:
Product Support Page Needed:
Options:
Yes
No
Maybe
Operator instruction:
Use a product support page when the offer needs a clear explanation, trust support, FAQ support, or pre-click education.
15. Pre-Sell Content Needed
Field:
Pre-Sell Content Needed:
Options:
Yes
No
Maybe
Operator instruction:
Use pre-sell content when the reader needs education, problem framing, belief alignment, or trust before clicking through.
16. FAQ Content Needed
Field:
FAQ Content Needed:
Options:
Yes
No
Maybe
Operator instruction:
Use FAQ content when the offer or topic creates repeated questions, objections, uncertainty, or confusion.
17. Objection Content Needed
Field:
Objection Content Needed:
Options:
Yes
No
Maybe
Operator instruction:
Use objection-handling content when the audience may hesitate because of trust, cost, complexity, skepticism, risk, or misunderstanding.
18. Comparison Content Needed
Field:
Comparison Content Needed:
Options:
Yes
No
Maybe
Operator instruction:
Use comparison content when the audience is product-aware or evaluating alternatives.
Do not use unfair or unsupported comparisons.
19. Trust Support Needed
Field:
Trust Support Needed:
Options:
Yes
No
Maybe
Operator instruction:
Use trust support when the reader needs confidence, transparency, source clarity, credibility, or risk reduction.
20. YouTube Support Needed
Field:
YouTube Support Needed:
Options:
Yes
No
Maybe
Operator instruction:
Use YouTube support when the offer has or may have video traffic, VSL support, organic video support, or description support.
21. VEO3 Pre Video Support Needed
Field:
VEO3 Pre Video Support Needed:
Options:
Yes
No
Maybe
Operator instruction:
Use VEO3 pre-video support when short video intros, hooks, or testable pre-video assets are needed.
Follow existing VEO3 standards and avoid unapproved claims.
22. Email Support Needed
Field:
Email Support Needed:
Options:
Yes
No
Maybe
Operator instruction:
Use email support when the offer will be supported by follow-up, nurture, objection handling, or educational sequences.
23. Social Support Needed
Field:
Social Support Needed:
Options:
Yes
No
Maybe
Operator instruction:
Use social support only when the asset can be repurposed safely without changing claims or compliance risk.
24. Internal Linking Needed
Field:
Internal Linking Needed:
Options:
Yes
No
Maybe
Operator instruction:
Use internal linking when the offer connects to existing topic clusters, support pages, trust pages, or related articles.
Use Content Brain Internal Linking for meaningful linking plans.
25. Repurposing Plan Needed
Field:
Repurposing Plan Needed:
Options:
Yes
No
Maybe
Operator instruction:
Use repurposing when approved content can safely become email, social, YouTube, FAQ, or support assets.
Use Content Brain Repurposing for meaningful repurposing plans.
26. 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.
27. Compliance Sensitivity
Field:
Compliance Sensitivity:
Options:
Low
Medium
High
Unknown
Operator instruction:
Record the likely risk level.
If risk is medium, high, or unknown, identify the required review owner before use.
28. Required Compliance Review
Field:
Required Compliance Review:
Options:
Not required
Compliance Brain
HeadOffice
Affiliate Brain
Ads Brain
Legal review
Other
Unknown
Operator instruction:
If claims, product type, ad usage, health, finance, income, legal, urgency, scarcity, or sensitive claims are involved, identify who must review the content.
Do not mark the pack ready if the review owner is unclear.
29. Approval Owner
Field:
Approval Owner:
Operator instruction:
Record who must approve the content pack before use.
Examples:
HeadOffice
Affiliate Brain
Research Brain
Compliance Brain
Finance Brain
Ads Brain
Experimentation Brain
Martyn
Other
If approval owner is missing, do not mark the pack ready.
30. 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 content pack assets will go after preparation.
If destination is unclear, the pack is not ready.
31. 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 pack.
If not applicable, write:
Not applicable
32. Repurposing Plan
Field:
Repurposing Plan:
Operator instruction:
List which pack assets may be repurposed and into which formats.
Examples:
Pre-sell article into email sequence
FAQ into social posts
Objection content into YouTube description support
Comparison content into short-form idea set
If no repurposing is planned, write:
Not applicable
33. 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 the pack is used.
Do not over-interpret weak signals.
Data Brain owns data quality.
34. Pack Status
Field:
Pack Status:
Options:
Draft
Needs research
Needs offer approval
Needs compliance review
Needs approval owner
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 research, offer status, claim risk, approval owner, or destination is unclear.
Affiliate Content Pack Decision Table
Use this table to decide what happens next.
| Situation | Decision |
|---|---|
| Offer approved, research basis clear, risk low, approval owner known | Ready for 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 |
| Search demand unclear | Optional / lower priority / needs Search Intelligence Brain 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 |
| Pack size too large for offer priority | Reduce pack size |
| Asset list unclear | Return to brief stage |
| Request belongs to another Brain | Route back to correct Brain |
When To Mark Ready For Drafting
Mark the pack ready for drafting only when:
offer status is approved or review-ready
source Brain is clear
content purpose is clear
audience is clear
funnel role is clear
research basis is recorded
pack size is appropriate
required assets are selected
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 the pack ready.
When To Park An Affiliate Content Pack
Park the content pack when:
offer status is unclear
research is missing
audience is unclear
funnel role is unclear
claims to avoid are missing
compliance risk is unknown
approval owner is missing
handoff destination is unclear
the pack is too large for the current priority
the request belongs to another Brain
Parked does not mean rejected.
It means the missing information must be resolved before content 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 Funnel Support for funnel-stage mapping
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 Product Content Pack Generator
Affiliate Product Content Pack Checklist UI
Affiliate Support Content Planner
Content Brief Generator
Publishing Readiness Checklist UI
Content Production Queue
Content Operations 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
No old mwmscontentbrain.site page called Content Brain Affiliate Product Content Pack Checklist is visible in the uploaded Content Brain site page list.
If one is found manually later, handle it as follows:
If it is only a duplicate operational affiliate content pack checklist 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 content pack pages.
The active operator affiliate content pack page should be:
Content Brain Affiliate Content Packs
Drift Protection
The system must prevent:
affiliate content being created before offer status is clear
affiliate content packs being treated as offer approval
affiliate content packs being created without research basis
affiliate content packs being created without audience clarity
affiliate content packs being created without funnel role
affiliate content packs being created without claims to avoid
affiliate content packs being created without compliance sensitivity
affiliate content packs being created without approval owner
affiliate content packs being created without handoff destination
pack size becoming too large for offer priority
unsupported product claims being introduced
repurposed affiliate 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, Data Brain, SIT Brain, or HeadOffice
future UI being built before manual affiliate pack use proves need
Architectural Intent
Content Brain Affiliate Content Packs exists to make affiliate content support structured, safe, and useful.
Its role is to connect approved or review-ready affiliate opportunities with clear content assets that support the reader journey.
Affiliate content packs should help MWMS create:
better offer education
clearer pre-sell content
stronger trust support
better objection handling
safer affiliate messaging
more reusable content assets
cleaner handoff paths
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
No affiliate product content pack should move into drafting without clear offer status, research basis, audience, funnel role, claims to avoid, approval owner, and handoff destination.
Affiliate content packs do not approve offers.
Affiliate content packs do not approve claims.
Affiliate content packs do not approve budgets.
Affiliate content packs do not approve campaigns.
Affiliate content packs do not approve tests.
When in doubt, park the pack 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 content pack page for mwmscontentbrain.site based on MCR Content Brain Affiliate Product Content Pack Checklist Operational Copy. Defines the live Content Brain Affiliate Content Packs page for the first operational Content Brain layer, including affiliate pack purpose, pack types, full 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 Content Packs
Pages Updated:
None
Pages To Delete Or Move To Legacy After Validation:
None visible in uploaded mwmscontentbrain.site Content Brain page list
Pages Deprecated:
None
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT BRAIN AFFILIATE CONTENT PACKS v1.0