Brain Name: Content Brain
Document Type: Framework
Status: Draft
Version: v1.0
Authority: Content Brain under HeadOffice governance
Applies To: Affiliate product content support, approved or review-ready affiliate offers, content opportunity qualification, content production planning, pre-sell support, YouTube support, VEO3 pre-video support, email support, social support, internal linking, repurposing, compliance review, and future mwmscontentbrain.site operational planning
Parent: Content Brain Canon
Last Reviewed: 2026-05-24
Content Brain Affiliate Product Content Pack Framework
Purpose
The Content Brain Affiliate Product Content Pack Framework defines the standard content package Content Brain may create to support an approved or review-ready affiliate product.
This framework exists to prevent Content Brain from creating random affiliate content assets one at a time without structure, review, or system purpose.
Its purpose is to define:
what an affiliate product content pack is
when a content pack should be created
what assets may belong inside the pack
which Brains must be involved
what Content Brain owns
what Content Brain does not own
how research, compliance, finance, ads, experimentation, and affiliate approval connect to the pack
how each content asset should be reviewed
how content packs move into production, refresh, or repurposing
how signals from the content pack return to the wider MWMS ecosystem
Content Brain does not approve affiliate products.
Content Brain does not decide whether an offer should be tested.
Content Brain creates structured content assets that support approved affiliate product opportunities.
Scope
This framework applies to:
affiliate product content packs
approved affiliate offers
review-ready affiliate offers
affiliate product education content
pre-sell article planning
comparison article planning
review support content
FAQ content
objection-handling content
trust-building content
YouTube script support
VEO3 pre-video support
YouTube description support
email follow-up content
social post sets
internal linking plans
repurposing plans
affiliate content refresh
affiliate content signal feedback
future mwmscontentbrain.site operational planning
This framework does not govern:
Affiliate Brain offer approval
Research Brain evidence verdicts
Ads Brain campaign setup
Ads Brain campaign optimisation
Experimentation Brain test verdicts
Finance Brain budget decisions
Compliance Brain final compliance approval
Data Brain signal reliability judgement
live publishing authority
plugin or UI development
Supabase implementation
M’s active build areas
Those remain governed by the relevant Brain, protocol, standard, or implementation layer.
Core Principle
Affiliate product content should be packaged, not scattered.
Content Brain should not create one random article, one random script, one random email, or one random social post without understanding the product, audience, funnel role, review path, and approval status.
A strong affiliate product content pack should have:
a source offer
a clear approval status
a target audience
a funnel role
a content purpose
a research base
a claim-risk review path
a production path
a handoff destination
a feedback path
If those elements are missing, the pack should not move into production.
Governance Role
Content Brain is an execution Brain.
Affiliate Brain owns affiliate opportunity evaluation.
Research Brain owns research evidence and source validation.
Compliance Brain owns compliance interpretation.
Finance Brain owns capital and investment discipline.
Ads Brain owns paid traffic execution.
Experimentation Brain owns test design and learning quality.
Content Brain owns the content package structure and the production of approved content assets.
This framework defines how Content Brain should package affiliate product content without absorbing authority from other Brains.
Definition
An affiliate product content pack is a structured group of content assets designed to support an affiliate product opportunity.
The pack may support:
product education
problem awareness
pre-sell framing
trust building
objection handling
comparison support
YouTube traffic
email follow-up
social repurposing
internal linking
affiliate funnel support
campaign support
content testing
refresh and repurposing
A content pack is not automatically required for every offer.
The pack should be created only when the offer is strong enough, approved enough, or strategically useful enough to justify structured content work.
When To Create A Content Pack
A Content Brain Affiliate Product Content Pack may be created when:
Affiliate Brain has approved the offer for support
Affiliate Brain has marked the offer as review-ready
Research Brain has supplied enough evidence to begin content planning
HeadOffice has prioritised the product or opportunity
Ads Brain needs content support for an approved campaign direction
Experimentation Brain needs controlled content assets for a test
Search Intelligence Brain identifies search demand connected to the product
AIBS Brain requires an educational angle around the product category
a manual operator requests structured content support for an approved offer
a product has enough content value to justify a pack
A content pack should not be created when:
offer status is unknown
research is missing
compliance risk is unclear
approval owner is missing
the product is low-quality or unproven
the product is not aligned with MWMS strategy
the product is not worth the content investment
the content would rely on unsupported claims
the request is only “make some content for this offer”
Pack Entry Requirements
Before a content pack enters production, Content Brain should confirm:
product name
affiliate network
vendor or offer source
Affiliate Brain status
Research Brain evidence status
target audience
primary problem
main product promise
main objections
key trust risks
claim-risk level
traffic source context
content destination
approval owner
review owner
handoff destination
performance signal to watch
If these are not available, the pack should remain in Opportunity Queue, Research Needed, or Blocked status.
Standard Content Pack Components
A full affiliate product content pack may include:
Product Support Page
Pre-Sell Article
Problem-Aware Article
Comparison Article
Review Support Content
FAQ Content
Objection-Handling Content
Trust Support Notes
YouTube Script
VEO3 Pre-Video Script
YouTube Description
Email Follow-Up Draft
Social Post Set
Internal Linking Plan
Repurposing Plan
Compliance Risk Notes
Research Requirement Notes
Performance Signal Plan
Not every pack requires every asset.
The pack should be sized according to product priority, approval status, risk, and business value.
Minimum Viable Affiliate Product Content Pack
The minimum useful affiliate product content pack should include:
Product Support Page Outline
Pre-Sell Article Outline
FAQ Or Objection Content
YouTube Script Or YouTube Description
Compliance Risk Note
Research Requirement Note
Internal Linking Plan
Feedback Signal To Watch
This minimum pack is enough to support early content planning without overbuilding.
Full Affiliate Product Content Pack
A full pack may include:
Product Support Page
Pre-Sell Article
Problem-Aware Article
Comparison Article
FAQ Page
Objection-Handling Article
Review Support Article
Trust Support Page
YouTube Script
VEO3 Pre-Video Script
YouTube Description
Email Follow-Up Draft
Social Post Set
Short-Form Script Seeds
Internal Linking Plan
Repurposing Plan
Refresh Plan
Compliance Risk Review Notes
Research Evidence Summary
Performance Signal Plan
This full pack should only be used for higher-priority affiliate products.
Product Support Page
The Product Support Page explains the product category, problem, solution context, and reader pathway.
It should not be a hype page.
It should help the reader understand:
what problem the product category addresses
who the product may be relevant for
what questions the reader should ask
what objections or concerns matter
what proof or evidence should be reviewed
where the next step is
This page may support a VSL click, affiliate bridge page, or educational funnel.
Content Brain must avoid unsupported claims.
Pre-Sell Article
The Pre-Sell Article prepares the reader before they reach the product page, VSL, or affiliate offer.
It should:
educate the reader
frame the problem
increase relevance
reduce confusion
address early objections
create curiosity without hype
prepare the next click
The pre-sell article should not pretend to be the vendor.
It should support the reader’s decision journey.
Problem-Aware Article
The Problem-Aware Article focuses on the reader’s pain point, frustration, risk, or need before introducing the product.
It may explain:
why the problem matters
common causes
common mistakes
what people usually try
why some solutions fail
what to look for next
This content helps warm the audience before product-specific content.
Comparison Article
The Comparison Article helps the reader understand options.
It may compare:
product categories
solution types
decision criteria
features
risks
use cases
pros and cons
It should not make unfair or unsupported claims.
It should be useful, balanced, and review-safe.
Review Support Content
Review Support Content helps support product evaluation without pretending to provide unsupported firsthand proof.
It may include:
what the product claims to do
who it appears to be for
what the buyer should check
common questions
risk notes
trust indicators
decision considerations
Content Brain must not fake personal experience, fake testimonials, or unsupported results.
FAQ Content
FAQ Content answers common reader questions.
FAQ topics may include:
what the product is
who it may suit
who it may not suit
what problem it addresses
how it is positioned
what to check before buying
refund or guarantee questions if confirmed
safety or suitability questions
traffic-source-specific concerns
FAQ content must be claim-safe.
If an answer requires vendor confirmation, research, or compliance review, it should be flagged.
Objection-Handling Content
Objection-Handling Content addresses the reader’s doubts.
Common objections may include:
will this work for me
is this trustworthy
is this worth the money
is this safe
is this too complicated
is this just hype
what happens if it does not work
how is this different
what should I know before deciding
Objection-handling content should not pressure the reader.
It should clarify, educate, and reduce confusion.
Trust Support Notes
Trust Support Notes identify what proof, credibility, or reassurance the content needs.
Trust support may include:
vendor credibility
transparent explanation
clear disclaimers
specific evidence
limitations
expectation setting
comparison clarity
refund policy confirmation if available
safe claim language
Trust content should build confidence without exaggeration.
YouTube Script
The YouTube Script supports video traffic.
It may be used for:
organic YouTube
Google Video Ads support
educational video
problem-aware video
comparison video
trust support video
affiliate pre-sell video
The script should align with MWMS video standards and avoid unsafe claims.
It should include:
hook
problem framing
education
curiosity
transition
soft CTA
risk-aware wording
The script should not make price claims unless approved.
The script should not show or describe restricted product details if an offer-specific rule says not to.
VEO3 Pre-Video Script
The VEO3 Pre-Video Script is a short headline and hook-style intro that rolls into the main video.
It should follow the MWMS VEO3 pre-video standard.
It should include:
time-coded scene blocks
headline
narration
on-screen text
visual direction
VEO3-ready image descriptions
science-curious or problem-aware hook where appropriate
no hard CTA inside the pre-video
no unsupported product claims
The VEO3 pre-video should be designed for hook testing without rewriting the main video.
YouTube Description
The YouTube Description supports video discovery and viewer next steps.
It may include:
short summary
viewer benefit
soft next step
affiliate disclosure where required
relevant keywords
safe language
link placement guidance
The description must not overclaim.
The description must match the video and landing path.
Email Follow-Up Draft
The Email Follow-Up Draft supports nurture and reminder content.
It may include:
problem reminder
education
FAQ answer
objection clarification
trust reinforcement
soft CTA
Email content must avoid pressure, unsupported urgency, and exaggerated claims.
If the product is compliance-sensitive, the email must be reviewed before use.
Social Post Set
The Social Post Set turns approved content into short posts.
It may include:
problem-aware posts
educational posts
myth-busting posts
FAQ posts
comparison snippets
curiosity posts
short video captions
Social content must preserve the original meaning.
Repurposed social content must not strengthen claims, add urgency, or create misleading promises.
Internal Linking Plan
The Internal Linking Plan defines how the affiliate content connects to other MWMS content assets.
It may include:
pillar page links
supporting article links
FAQ links
trust page links
comparison links
offer support links
YouTube support links
Content Brain should use internal linking to improve reader journey, not just SEO.
Internal linking should avoid overloading money pages with aggressive linking.
Repurposing Plan
The Repurposing Plan defines how approved content assets can be reused.
Examples:
pre-sell article to email
FAQ content to social posts
YouTube script to short-form script seeds
problem-aware article to VEO3 pre-video ideas
comparison article to social carousel text
trust notes to email follow-up
Repurposing must preserve meaning and claim safety.
Compliance Risk Notes
Compliance Risk Notes identify claim-sensitive areas.
These may include:
health claims
finance claims
income claims
legal claims
product performance claims
testimonials
guarantees
scarcity
urgency
before and after claims
risk-sensitive comparisons
Compliance Risk Notes should say what needs review.
They do not approve the content.
Compliance Brain owns final compliance interpretation.
Research Requirement Notes
Research Requirement Notes identify missing evidence or facts.
These may include:
vendor proof needed
offer details needed
customer review verification needed
competitor comparison needed
refund policy confirmation needed
claim support needed
audience pain point evidence needed
search demand confirmation needed
Research Brain owns deeper research and validation.
Content Brain should not invent missing evidence.
Performance Signal Plan
Each content pack should define signals to watch after use.
Signals may include:
VSL clicks
affiliate link clicks
YouTube description clicks
email clicks
organic traffic
ranking movement
scroll depth
time on page
internal link clicks
conversion assist
FAQ engagement
social engagement
content refresh need
repurposing opportunity
Data Brain should be involved if signal reliability is unclear.
Experimentation Brain should be involved if learning interpretation matters.
Pack Size Model
Affiliate product content packs should be sized based on priority.
Small Pack
Use for early review or low-risk support.
Includes:
Product Support Page Outline
Pre-Sell Article Outline
FAQ Or Objection Content
YouTube Description
Compliance Risk Note
Research Requirement Note
Medium Pack
Use for active but controlled product support.
Includes:
Product Support Page
Pre-Sell Article
FAQ Content
Objection-Handling Content
YouTube Script
YouTube Description
Email Draft
Internal Linking Plan
Compliance Risk Notes
Research Requirement Notes
Full Pack
Use for high-priority products, approved campaigns, or serious affiliate support.
Includes:
Product Support Page
Problem-Aware Article
Pre-Sell Article
Comparison Article
Review Support Content
FAQ Content
Objection-Handling Content
Trust Support Notes
YouTube Script
VEO3 Pre-Video Script
YouTube Description
Email Follow-Up Draft
Social Post Set
Short-Form Script Seeds
Internal Linking Plan
Repurposing Plan
Refresh Plan
Compliance Risk Notes
Research Evidence Summary
Performance Signal Plan
Pack Status Model
Recommended status values:
new
opportunity_queued
research_needed
classified
briefing
drafting
in_review
needs_revision
ready_for_approval
approved
ready_for_handoff
handed_off
published
monitoring
refresh_needed
repurpose_needed
blocked
closed
rejected
Pack Priority Model
Priority values:
Low
Medium
High
Critical
Low Priority:
Useful but not urgent.
Medium Priority:
Relevant and worth producing when capacity allows.
High Priority:
Important to active affiliate support, funnel support, search demand, or content strategy.
Critical Priority:
Required for active campaign support, major opportunity, urgent risk control, or HeadOffice priority.
Critical priority should be used sparingly.
Pack Risk Model
Risk values:
Low
Medium
High
Critical
Low Risk:
General education or low-sensitivity content.
Medium Risk:
Affiliate content with moderate product discussion or comparison.
High Risk:
Content involving health, finance, income, legal, strong claims, testimonials, guarantees, urgency, or paid campaign support.
Critical Risk:
Content that may create platform, legal, financial, reputation, or compliance exposure if mishandled.
High and critical risk packs require review before production or publication.
Brain Relationship Model
Affiliate Brain
Affiliate Brain provides:
offer status
affiliate opportunity decision
product fit context
offer risk context
affiliate funnel role
approval status
Content Brain returns:
content pack plan
content support gaps
offer education needs
pre-sell content needs
comparison content needs
trust content needs
FAQ and objection patterns
Content Brain does not approve offers.
Research Brain
Research Brain provides:
evidence
audience insight
competitor context
market context
problem validation
source validation
Research Brain may also identify missing evidence.
Content Brain returns:
research gaps
content questions
evidence needs
topic traction signals
audience questions
Content Brain does not invent missing research.
Search Intelligence Brain
Search Intelligence Brain provides:
search demand signals
keyword opportunities
SERP patterns
topic demand
question-based opportunities
comparison demand
Content Brain returns:
SEO content opportunities
brief requirements
topic cluster needs
internal linking needs
refresh opportunities
Content Brain does not validate search demand by itself.
Ads Brain
Ads Brain provides:
hook signals
angle signals
ad-to-page mismatch signals
message performance signals
campaign support needs
Content Brain returns:
YouTube scripts
VEO3 pre-video scripts
YouTube descriptions
supporting educational content
trust content
message-match support
Content Brain does not optimise paid campaigns.
Experimentation Brain
Experimentation Brain provides:
test learning
variant insight
message learning
content experiment needs
learning quality guidance
Content Brain returns:
content variants
refresh ideas
repurposing opportunities
controlled content assets
Content Brain does not declare test winners.
AIBS Brain
AIBS Brain may provide:
authority framing
education positioning
business owner explanation needs
client-facing context
Content Brain may create:
educational explainers
authority support content
sales support articles
FAQ content
Content Brain does not define AIBS strategy.
Compliance Brain
Compliance Brain provides:
risk interpretation
claim guidance
platform policy review
sensitive content direction
Content Brain returns:
claim-risk notes
review requests
safer draft structures
flagged language
Content Brain does not approve compliance-sensitive claims.
Finance Brain
Finance Brain provides:
investment discipline
priority guidance
budget awareness
resource allocation context
Content Brain returns:
pack size recommendation
content investment estimate
resource-heavy content warnings
priority questions
Content Brain does not approve spend.
Data Brain
Data Brain provides:
measurement discipline
signal reliability guidance
tracking interpretation
Content Brain returns:
performance signal needs
content-level observations
tracking gaps
Data Brain owns data reliability.
HeadOffice
HeadOffice provides:
strategic priority
cross-brain direction
approval escalation
system oversight
Content Brain returns:
content pack status
content opportunities
content bottlenecks
risk notes
strategic content patterns
HeadOffice governs the ecosystem.
Standard Pack Workflow
The standard workflow for an affiliate product content pack is:
Offer or signal received
Opportunity queued
Offer status checked
Research status checked
Audience and funnel role defined
Pack size selected
Required assets selected
Compliance risk assessed
Content brief created
Assets produced
Quality review completed
SEO review completed where relevant
Trust and compliance review completed where relevant
Approval completed
Handoff or publishing destination confirmed
Performance signal defined
Pack handed off, published, monitored, refreshed, or repurposed
Signal feedback routed to the relevant Brain
Pack Brief Requirements
Every affiliate content pack should include a pack brief.
The pack brief should include:
product name
affiliate network
vendor or offer source
offer status
approval owner
target audience
awareness stage
primary problem
main promise
main objections
content goal
funnel role
traffic source context
required assets
pack size
claim-risk level
research status
compliance review requirement
internal linking needs
handoff destination
performance signals
feedback destination
Production Rules
Content Brain may produce pack assets only when:
the offer status is known
the pack purpose is clear
the audience is defined
the content type is selected
the review path is known
the approval owner is identified
claim risk has been considered
research gaps have been flagged
Content Brain should not produce affiliate pack assets from vague requests.
Review Rules
Review requirements depend on risk level, product category, traffic source, and content type.
Possible reviews:
Affiliate Review
Research Review
SEO Review
Trust Review
Compliance Sensitivity Review
Ads Support Review
Experimentation Review
Finance Priority Review
Human Approval Review
Not every asset needs every review.
High-risk assets must not be published without review.
Approval Rules
Approval is required before:
publishing affiliate recommendation content
using health claims
using finance claims
using income claims
using legal claims
using testimonials
using guarantees
using scarcity or urgency language
pushing content into paid campaign support
publishing comparison claims
publishing review-style content
using AIBS or MWMS positioning in client-facing claims
Content Brain may prepare draft assets.
It does not grant final approval.
Handoff Rules
When a content pack is handed off, the handoff note should include:
product name
pack size
included assets
source offer
offer status
approval status
risk level
review notes
publishing destination
traffic source context
internal links needed
feedback signals to watch
next owner
handoff date
A pack without a handoff note creates confusion and rework.
Refresh Rules
Affiliate product content may need refresh when:
offer details change
vendor page changes
compliance risk changes
search intent changes
performance declines
ad learning changes
reader questions appear
internal links change
new research becomes available
comparison landscape changes
Refresh work should enter the Content Refresh Queue.
Repurposing Rules
Affiliate product content may be repurposed when:
the asset is approved
the message is stable
claim risk is understood
the new format preserves meaning
the destination is clear
Repurposing may create:
social post
short-form script seed
YouTube description
FAQ snippet
VEO3 pre-video hook
newsletter section
sales support note
Repurposing should not strengthen claims.
Internal Linking Rules
Affiliate product packs should include internal linking guidance.
The plan should identify:
supporting articles
pillar pages
comparison pages
FAQ pages
trust pages
related YouTube content
related offer pages
related educational content
Internal links should improve reader journey.
They should not create aggressive or unnatural money-page linking.
Content Pack Quality Checklist
Before approval, confirm:
product status is known
audience is clear
problem is clear
funnel role is clear
traffic source context is known
research gaps are flagged
claims are safe or marked for review
content is useful
content is specific
content does not sound generic
content does not invent proof
content does not fake experience
internal links are planned
handoff destination is clear
feedback signal is defined
approval owner is known
Future Plugin Or UI Candidate
This framework may later support:
Affiliate Product Content Pack Generator
Affiliate Content Pack Checklist
Pack Brief Form
Pack Asset Tracker
Pack Approval Tracker
Pack Risk Review Panel
Pack Repurposing Planner
Pack Performance Review Panel
These should not be built yet.
Manual workflow must prove the need first.
Relationship To Content Brain Operating Model
The Content Brain Operating Model defines Content Brain’s role in affiliate product content deployment.
This framework defines the standard pack Content Brain may create for approved or review-ready affiliate product opportunities.
Operating Model = role and boundary
Affiliate Product Content Pack Framework = repeatable content package
Relationship To Content Brain Workflow Map
The Content Brain Workflow Map defines how signals become opportunities, production tasks, refresh tasks, repurposing tasks, and feedback signals.
This framework defines what Content Brain may produce after an affiliate product content opportunity has been approved.
Workflow Map = movement
Content Pack Framework = asset structure
Relationship To Content Brain Content Opportunity Queue Specification
Affiliate product content pack ideas should usually enter through the Content Opportunity Queue before production.
The Opportunity Queue should decide whether the pack should be:
ignored
parked
researched
reviewed
approved
promoted to production
promoted to refresh
promoted to repurposing
This framework defines what happens after the opportunity is approved.
Relationship To Content Brain Content Production Queue Specification
Approved pack assets may move into the Content Production Queue.
The Production Queue tracks:
briefing
drafting
review
approval
handoff
publication
monitoring
This framework defines the pack structure.
The Production Queue tracks production movement.
Relationship To Content Brain Content Refresh Queue Specification
Existing affiliate content pack assets may enter the Content Refresh Queue when they become outdated, weak, risky, or misaligned.
Refresh Queue = existing asset improvement
Content Pack Framework = original asset package
Relationship To Content Brain Repurposing Queue Specification
Approved affiliate pack assets may enter the Repurposing Queue when they can be reused in another format.
Repurposing Queue = asset adaptation tracking
Content Pack Framework = source pack structure
Relationship To Content Brain Affiliate Funnel Support Map
The Affiliate Funnel Support Map defines how Content Brain supports affiliate funnel stages.
This framework defines the content pack that may serve those stages.
Affiliate Funnel Support Map = funnel role and support logic
Affiliate Product Content Pack Framework = pack assets and production rules
Relationship To Content Brain Copy Map
This page should be added to the Content Brain Copy Map as:
Page Title: Content Brain Affiliate Product Content Pack Framework
Classification: Copy To Content Brain
Reason: Operational framework for producing structured affiliate content packs once offers are approved or review-ready.
Source Of Truth: MCR
Future Destination: mwmscontentbrain.site
Future Use: Affiliate product content pack planning and production guidance
Plugin Or UI Later: Possible Affiliate Product Content Pack Generator
Relationship To Content Brain Page Registry
This page should be added to the Content Brain Page Registry as:
Page Title: Content Brain Affiliate Product Content Pack Framework
Document Type: Framework
Parent Page: Content Brain Canon
Status: Draft
Migration Classification: Copy To Content Brain
Plugin Or UI Candidate: Possible Affiliate Product Content Pack Generator Later
Notes: Defines the standard content pack for approved or review-ready affiliate products, including product support pages, pre-sell content, FAQ content, YouTube support, VEO3 pre-video support, email, social, internal linking, repurposing, compliance notes, and research requirement notes.
Relationship To Other MWMS Standards
This page must align with:
Content Brain Operating Model
Content Brain Workflow Map
Content Brain Content Opportunity Queue Specification
Content Brain Content Production Queue Specification
Content Brain Content Refresh Queue Specification
Content Brain Repurposing Queue Specification
Content Brain Content Operations Dashboard Specification
Content Brain Affiliate Funnel Support Map
Content Brain Content Brief Template
Content Brain SEO Content Brief Standard
Content Brain Publishing Readiness Checklist
Content Brain Copy Map
Content Brain Page Registry
Content Brain AI Content Quality Governance Framework
Content Brain Information Gain Framework
Content Brain E E A T Content Trust Framework
MWMS MCR To Brain Copy Rule
MWMS Brain Interaction Map
MWMS Brain To Brain Request Protocol
MWMS Page Naming Standard
MWMS Document Structure Standard
MWMS AI Output Standard Full File Delivery Rule
MWMS Active Brain Status Board
Drift Protection
The system must prevent:
affiliate content being created without offer status
affiliate content being created without research basis
affiliate content being created without audience clarity
affiliate content being created without approval owner
affiliate content packs becoming random bundles of assets
Content Brain approving offers
Content Brain approving compliance-sensitive claims
Content Brain deciding ad strategy
Content Brain deciding test validity
Content Brain deciding capital allocation
Content Brain inventing proof
Content Brain faking product experience
Content Brain strengthening claims during repurposing
Content Brain publishing without approval
content packs being built before workflow need is clear
plugin or UI work starting before manual use proves the need
Content Brain interfering with M’s active build areas
Architectural Intent
The Content Brain Affiliate Product Content Pack Framework exists to make affiliate product content support repeatable, governed, and useful.
Its long-term role is to help MWMS support affiliate opportunities with structured content assets rather than scattered production.
The framework ensures that affiliate product content is:
source-aware
research-aware
approval-aware
risk-aware
funnel-aware
search-aware
trust-aware
repurposable
measurable
connected to signal feedback
The long-term intent is for this framework to support a future Affiliate Product Content Pack Generator or checklist inside mwmscontentbrain.site after manual workflow proves the need.
Final Rule
Content Brain does not approve affiliate products.
Content Brain does not approve affiliate claims.
Content Brain does not decide campaign strategy.
Content Brain creates structured affiliate product content packs only when the offer status, audience, purpose, review path, and approval owner are clear.
If those are missing, the pack should remain in Opportunity Queue, Research Needed, or Blocked status.
Change Log
Version: v1.0
Date: 2026-05-24
Author: HeadOffice
Change: Initial creation of Content Brain Affiliate Product Content Pack Framework defining the standard content package for approved or review-ready affiliate products, including pack components, minimum and full pack models, pack workflow, review rules, approval rules, handoff rules, refresh rules, repurposing rules, internal linking rules, quality checklist, future plugin or UI potential, relationships to Content Brain Operating Model, Workflow Map, Opportunity Queue, Production Queue, Refresh Queue, Repurposing Queue, Affiliate Funnel Support Map, Page Registry, and Copy Map.
Change Impact Declaration
Pages Created:
Content Brain Affiliate Product Content Pack Framework
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
Content Brain Page Registry
Content Brain Copy Map
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT BRAIN AFFILIATE PRODUCT CONTENT PACK FRAMEWORK v1.0