Content Brain Affiliate Product Content Pack Framework

Document Type: Framework
Status: Active
Version: v1.1
Authority: Content Brain Canon
Applies To: Affiliate Product Content Pack Planning, Asset Selection, Production, Editing, Review, Approval, Publishing Preparation, Measurement And Lifecycle Management
Parent: Content Brain Canon
Enforcement Mode: Operational
Last Reviewed: 2026-06-15

Content Brain Affiliate Product Content Pack Framework

Purpose

The Content Brain Affiliate Product Content Pack Framework defines how MWMS plans, produces, edits, reviews, approves, prepares and manages coordinated affiliate content packs.

An affiliate product content pack is a controlled collection of related content assets created around:

one approved affiliate offer
one defined audience or audience segment
one clear funnel or campaign objective
one approved content strategy
one shared source and evidence base
one coordinated publication or delivery pathway

The Framework exists to prevent affiliate content from being created as disconnected assets with:

conflicting messages
inconsistent offer details
unsupported claims
inconsistent disclosures
duplicated content
weak funnel relationships
unclear destinations
missing approval ownership
no publishing sequence
no lifecycle plan

Content Brain owns the production of complete affiliate content-pack assets.

Affiliate Brain retains authority over:

offer status
affiliate opportunity decisions
funnel decisions
campaign requirements
testing stage
progression decisions
kill decisions
controlled scaling

Ads Brain retains authority over:

paid traffic strategy
campaign structure
platform selection
targeting
budgets
bidding
optimisation
scaling

Content Brain must not replace those authorities.

Core Principle

A content pack is not merely a list of possible content ideas.

A content pack must define and produce a coordinated group of complete assets that work together.

A finished affiliate product content pack should have:

a defined objective
a confirmed offer status
a defined audience
a defined funnel role
approved source material
evidence boundaries
claim boundaries
disclosure requirements
selected assets
asset relationships
production order
completed production
cross-asset editing
specialist review where required
Affiliate Brain review where required
human approval
publishing preparation
destination readiness
measurement requirements
lifecycle rules

Framework Objective

The objective of this Framework is to ensure affiliate product content packs are:

strategically useful
offer-aligned
audience-aligned
funnel-aligned
evidence-aware
channel-appropriate
complete
internally consistent
correctly reviewed
ready for human-controlled publication or deployment
measurable
refreshable
reusable
retireable

Scope

This Framework applies to content packs that may include:

Website Assets

bridge pages
pre-sell pages
advertorials
affiliate review pages
comparison pages
buyer guides
product-support pages
problem-aware pages
solution-aware pages
mechanism pages
FAQ pages
trust pages
objection-handling pages
authority pages
landing pages
supporting articles
topic hubs
internal-linking structures

Article Assets

problem-aware articles
problem-education articles
solution-education articles
mechanism articles
buyer guides
affiliate reviews
comparisons
alternatives articles
FAQ articles
objection-handling articles
trust articles
evidence summaries
authority articles
refresh articles

Video And Script Assets

YouTube scripts
YouTube Shorts scripts
TikTok scripts
Instagram Reel scripts
video bridge scripts
explainer scripts
review scripts
comparison scripts
authority scripts
product-education scripts
VEO3 pre-video scripts
webinar scripts
voiceover scripts
on-screen text
scene guidance
shot guidance

Advertising Assets

hooks
headlines
primary ad copy
descriptions
search ad copy
display ad copy
native ad copy
YouTube ad scripts
Meta ad copy
TikTok ad scripts
advertorial copy
pre-sell copy
CTA variations
message-match variations
creative briefs

Email And Newsletter Assets

newsletters
promotional emails
educational emails
welcome emails
nurture sequences
affiliate promotional sequences
launch sequences
objection-handling sequences
trust sequences
comparison emails
re-engagement emails
follow-up emails
subject lines
preview text
email calls to action

Social Assets

Facebook posts
Instagram captions
Instagram carousels
LinkedIn posts
X posts
X threads
YouTube community posts
TikTok concepts
short-form scripts
social series
FAQ posts
trust posts
comparison snippets
engagement posts
comment-response content

Supporting Assets

lead magnets
checklists
guides
FAQs
disclosures
trust blocks
comparison tables
product summaries
internal-linking plans
publishing notes
repurposing plans
measurement notes
refresh notes

What This Framework Does Not Govern

This Framework does not independently govern:

offer approval
affiliate opportunity approval
campaign approval
testing approval
advertising budget
bidding
targeting
capital allocation
experiment validity
final legal interpretation
final compliance interpretation
broad research authority
campaign deployment
autonomous publication
autonomous email sending
autonomous social posting
autonomous advertising deployment
plugin development
worker activation
AI Employee activation
Brain Room routing
automatic M handoff

These remain governed by the relevant Brain, human authority, framework, protocol or authorised implementation layer.

When A Content Pack Is Required

A content pack should be used when:

several assets support one affiliate offer
several channels must remain aligned
a campaign requires coordinated assets
a website or funnel requires several related pages
a content launch requires sequenced publishing
paid traffic and supporting content must maintain message match
an offer requires education, trust, objection handling and conversion support
one source asset will be repurposed into several channel-specific assets
several assets require shared evidence or compliance controls
the offer requires a complete content system rather than one isolated asset
asset-level performance should be reviewed alongside pack-level performance

When A Content Pack Is Not Required

A content pack is not required when:

one simple independent asset is needed
the task is a minor correction
the task is one low-risk refresh
the task is one standalone email
the task is one social post
the task is one internal-link update
the task is one short-form variation
the offer has not progressed far enough to justify pack planning
suitable existing assets already satisfy the need
the proposed pack would create unnecessary content volume
Affiliate Brain has not approved the required funnel or campaign pathway

Do not create a pack merely because multiple content formats are possible.

Pack Entry Requirements

A pack may enter Content Brain from:

Affiliate Brain
HeadOffice
an authorised human
Ads Brain
Strategy Brain
an approved campaign
an approved offer
an approved content project
an existing-content review
a Site Intelligence finding
a performance signal
a refresh decision
a repurposing decision
a correction requirement

Before pack planning begins, confirm:

offer name
offer status
originating request
requesting human or Brain
pack objective
campaign or project
audience
audience stage
funnel role
traffic source
content action
destination
source material
evidence requirements
claim boundaries
disclosure requirements
approval owner
specialist-review requirements
Affiliate Brain review requirements
measurement requirements
lifecycle requirements

Offer Status Gate

No pack should move into live-use production until offer status is sufficiently clear.

Possible offer statuses include:

Exploratory

Allowed work:

pack possibilities
content-gap notes
source requirements
research questions
rough asset possibilities
non-live exploratory outlines

Do not produce publication-ready promotional assets.

Approved For Research

Allowed work:

evidence requirements
customer questions
source collection
competitor-content observations
research-support briefs
research-gap identification

Approved For Planning

Allowed work:

pack objective
asset selection
pack architecture
production sequencing
briefing
blueprinting
source and evidence planning

Approved For Funnel Support

Allowed work:

complete website assets
articles
videos
emails
newsletters
social content
bridge pages
advertorials
reviews
comparisons
trust assets
FAQs
complete content packs

Approved For Testing Support

Allowed work:

test-specific packs
controlled variations
message-match variations
test-specific bridge pages
test-specific advertorials
hooks
headlines
ad scripts
email variations
CTA variations

Live Campaign Support

Allowed work:

campaign-support packs
refreshes
controlled variations
corrections
new objections
trust improvements
repurposed assets
channel expansions

Refresh Existing Support

Allowed work:

factual updates
offer updates
evidence updates
claim corrections
disclosure updates
content consolidation
message-match improvement
new internal links
repurposing
retirement preparation

Retired Or Rejected

Do not produce new promotional packs.

Allowed work may include:

retirement planning
archive preparation
redirect planning
link updates
replacement instructions
lessons preservation

If offer status is unclear, pack production remains blocked.

Pack Objective

Every pack must have one clearly defined primary objective.

Possible pack objectives include:

problem education
solution education
mechanism education
offer introduction
pre-sell support
bridge-page support
review and evaluation
comparison support
trust development
objection handling
paid traffic support
organic traffic support
email nurture
social education
retargeting support
launch support
content refresh
offer repositioning
audience expansion
lifecycle improvement

Pack Objective:

Secondary Objective:

Expected Audience Outcome:

Expected Business Outcome:

Primary Funnel Role:

Secondary Funnel Role:

Primary Destination:

Measurement Requirement:

Audience And Funnel Definition

Each pack must define:

Primary Audience:

Secondary Audience:

Audience Segment:

Primary Buyer Persona:

Awareness Stage:

Journey Stage:

Decision Stage:

Knowledge Level:

Primary Problem:

Primary Goal:

Primary Barrier:

Primary Objection:

Trust Level:

Decision Criteria:

Desired Outcome:

Traffic Source:

Funnel Entry Point:

Funnel Exit Or Next Step:

Shared Source Control

All pack assets should draw from a controlled shared source base.

Possible shared sources include:

Affiliate Brain offer intelligence
approved vendor materials
verified product information
Research Brain findings
Customer Brain intelligence
Search Intelligence
Strategy Brain direction
Creative Brain direction
Conversion Brain guidance
Compliance Brain boundaries
approved campaign requirements
approved existing content
performance signals
human instructions

The pack must identify:

Shared Source List:

Source Owner:

Source Status:

Source Date:

Source Gaps:

Facts Requiring Confirmation:

Assumptions:

Interpretations:

Restricted Claims:

Sources must be distinguishable where possible as:

confirmed fact
verified evidence
approved strategy
validated insight
emerging signal
working assumption
human instruction
content interpretation

Shared Evidence Control

The pack must define:

Required Evidence:

Approved Evidence:

Evidence Gaps:

Research Required:

Claims Requiring Evidence:

Claims Not Permitted:

Evidence Limitations:

Citation Requirements:

Specialist Review Requirements:

Content Brain must not invent:

scientific evidence
expert endorsements
customer results
testimonials
product performance
offer outcomes
financial outcomes
medical outcomes
guaranteed results

Shared Offer Detail Control

The pack must use consistent verified offer information.

Confirm:

Offer Name:

Vendor:

Product Or Service:

Offer Status:

Price Where Verified:

Discount Where Verified:

Refund Terms Where Verified:

Rebill Terms Where Verified:

Subscription Terms Where Verified:

Guarantee Where Verified:

Delivery Terms Where Verified:

Product Features:

Mechanism:

Intended Use:

Known Limitations:

Vendor Page:

VSL:

Checkout Or Next Step:

Offer details must not vary between assets unless an approved reason exists.

Shared Claim Control

The pack must define:

Approved Claims:

Restricted Claims:

Prohibited Claims:

Claims Requiring Qualification:

Claims Requiring Evidence:

Claims Requiring Compliance Review:

Claims Requiring Human Review:

Comparative Claims:

Guarantee Language:

Urgency Language:

Scarcity Language:

Expected-Result Language:

Claim risk may be classified as:

Low
Moderate
High
Critical

High-risk and critical claims require the appropriate review before live use.

Shared Disclosure Control

The pack must define:

Affiliate Disclosure Required:

Disclosure Wording Source:

Disclosure Placement:

Platform-Specific Disclosure:

Advertorial Disclosure:

Review Disclosure:

Email Disclosure:

Social Disclosure:

Video Disclosure:

Advertising Disclosure:

Disclosure requirements may differ by destination.

Content Brain does not make final legal interpretations.

Compliance Brain or an authorised human retains final authority.

Shared Message Control

The pack must define:

Primary Message:

Supporting Message 1:

Supporting Message 2:

Supporting Message 3:

Primary Angle:

Secondary Angle:

Mechanism Position:

Authority Position:

Identity-Outcome Position:

Trust Position:

Primary CTA:

Secondary CTA:

Expected Next Step:

Messages must remain consistent while allowing channel-appropriate adaptation.

Message Match Control

The pack should preserve continuity between:

advertisement
social post
email
article
bridge page
pre-sell page
advertorial
review
comparison
video
CTA
vendor page
VSL
checkout or next step

Review message match across:

audience
problem
hook
promise
mechanism
evidence
offer
CTA
destination
expected next step

The pack must not create expectations that the next destination cannot support.

Asset Selection Principle

Every pack asset must have a defined job.

Do not include assets merely to increase pack size.

For each proposed asset, ask:

What purpose does this asset serve?
Which audience stage does it support?
Which funnel stage does it support?
Which other asset does it connect to?
What source material does it use?
What destination will use it?
What measurement applies?
What happens if this asset is not produced?
Does a suitable asset already exist?

Asset Selection Record

For each asset, define:

Asset Name:

Asset Type:

Content Action:

Purpose:

Audience:

Funnel Stage:

Channel:

Destination:

Source Material:

Evidence Requirement:

Claim Risk:

Disclosure Requirement:

Relationship To Other Assets:

Production Order:

Approval Owner:

Publishing Owner:

Measurement Requirement:

Lifecycle Requirement:

Minimum Pack Model

Use a Minimum Pack when a compact coordinated system is sufficient.

A Minimum Pack may contain:

one primary bridge page or pre-sell page
one supporting article or FAQ asset
one email or newsletter asset
one social or short-form asset
required disclosures
internal-linking or destination notes

A Minimum Pack is suitable when:

the offer is in early controlled support
the campaign is narrow
one audience is being addressed
one traffic source is active
extensive content is not yet justified
manual testing should happen before expansion

Minimum Pack does not mean outline-only.

Approved pack assets must be produced as complete assets.

Standard Pack Model

A Standard Pack may contain:

one bridge page
one pre-sell page or advertorial
one review or comparison asset
two to four supporting articles
one FAQ or trust asset
one YouTube or video script
three to ten social assets
one newsletter
three to five emails
ad hooks, headlines or scripts where authorised
internal-linking plan
publishing notes
measurement notes

A Standard Pack is suitable when:

the offer has been approved for active funnel support
more than one channel is involved
the audience requires education and trust development
sufficient sources and evidence exist
coordinated content is justified

Full Pack Model

A Full Pack may contain:

Core Funnel Assets

bridge page
pre-sell page
advertorial
affiliate review
comparison page
buyer guide
FAQ page
trust page
objection-handling page

Authority And Education Assets

problem-aware articles
solution-education articles
mechanism articles
evidence summaries
authority articles
alternatives articles
topic hub
supporting cluster articles

Video And Script Assets

YouTube scripts
YouTube Shorts scripts
VEO3 pre-video scripts
explainer scripts
review scripts
comparison scripts
social-video scripts
voiceover scripts

Advertising Assets

hooks
headlines
primary copy
descriptions
YouTube ad scripts
display copy
native copy
Meta copy
TikTok scripts
creative briefs
controlled variations

Email And Newsletter Assets

welcome sequence
educational sequence
affiliate promotional sequence
objection sequence
comparison sequence
trust sequence
re-engagement sequence
newsletters
subject-line variations
preview-text variations

Social Assets

platform-specific post sets
carousels
X threads
YouTube community posts
short-form scripts
FAQ posts
trust posts
objection posts
comparison snippets

Supporting Controls

disclosure notes
internal-linking plan
asset relationship map
production order
publication sequence
measurement plan
refresh plan
repurposing plan
retirement rules

A Full Pack should only be produced when the business need justifies it.

Custom Pack Model

A Custom Pack may be created where:

the offer has an unusual funnel
the channel mix is specialised
the audience needs a particular sequence
a client or project requires non-standard assets
existing assets reduce the need for standard pack components
risk requires a smaller or more controlled structure

The pack must still follow the shared controls defined by this Framework.

Pack Planning Flow

The standard planning flow is:

Approved Pack Requirement
→ Offer Status Confirmed
→ Pack Objective Confirmed
→ Audience Confirmed
→ Funnel Role Confirmed
→ Existing Content Checked
→ Pack Model Selected
→ Required Assets Selected
→ Asset Relationships Defined
→ Shared Sources Confirmed
→ Evidence And Claim Boundaries Confirmed
→ Disclosure Requirements Confirmed
→ Production Order Confirmed
→ Review And Approval Owners Confirmed
→ Publishing And Measurement Requirements Confirmed

Existing-Content Check

Before new pack assets are created, confirm:

which relevant assets already exist
which assets remain useful
which assets are outdated
which assets overlap
which assets contain errors
which assets should be refreshed
which assets should be merged
which assets should be repurposed
which assets should be relinked
which assets should be retired
which content gaps are genuine

Possible content actions include:

create
refresh
expand
correct
merge
repurpose
reformat
relink
retire
archive
no action

A pack must not create unnecessary duplicate content.

Pack Architecture

The pack architecture should define how assets connect.

Possible relationships include:

Advertisement
→ Bridge Page
→ Vendor VSL

Advertisement
→ Advertorial
→ Bridge Page
→ Vendor Page

Search Article
→ Review Page
→ Vendor Page

Problem-Aware Article
→ Solution Article
→ Comparison Page
→ Offer

Social Post
→ Supporting Article
→ Bridge Page

YouTube Video
→ Description Link
→ Bridge Page

Newsletter
→ Article
→ Review Page

Email Sequence
→ Pre-Sell Page
→ Vendor Page

The pack architecture should identify:

entry assets
education assets
trust assets
evaluation assets
conversion-support assets
follow-up assets
repurposed assets
destinations
measurement points

Production Instruction Levels

Each pack or asset may begin from one of four instruction levels.

Full Content Brief

Use for:

complex packs
high-risk packs
several stakeholders
several channels
complete affiliate websites
major campaigns
sensitive offers
specialist-review-heavy work

Short Production Brief

Use for:

clear individual pack assets
moderate-risk work
known formats
known destinations
refreshes
controlled additions

Outline Or Blueprint

Use where:

pack structure requires approval
page structure requires approval
email sequence order requires approval
script structure requires approval
asset relationships require approval

Direct Production Instruction

Use where:

the asset is simple
the objective is clear
the audience is clear
the offer status is clear
sources are complete
risk is low
destination is known

A full formal brief is not mandatory for every asset.

The job must still be sufficiently defined.

Production Order

Production order should reflect asset dependency.

A recommended general order is:

Confirm pack controls.
Confirm shared source material.
Confirm offer details.
Confirm shared claims and disclosures.
Produce the central funnel asset.
Produce required supporting website assets.
Produce authority and educational assets.
Produce email and newsletter assets.
Produce video and script assets.
Produce social assets.
Produce advertising assets in line with Ads Brain requirements.
Complete cross-asset editing.
Complete message-match review.
Complete specialist review.
Complete Affiliate Brain review where required.
Complete human approval.
Complete publishing preparation.
Complete pack readiness review.
Complete human-controlled publication or deployment.
Record outcomes and lifecycle requirements.

Production order may change where dependencies require it.

Central Asset Principle

Every pack should identify its central asset or central destination.

Possible central assets include:

bridge page
pre-sell page
advertorial
review page
comparison page
buyer guide
topic hub
YouTube video
webinar
email sequence
lead magnet

Supporting assets should reinforce or extend the central asset.

They should not contradict it.

Asset Production Requirements

Each approved asset must be produced as a complete usable asset.

Content Brain must not submit:

an outline instead of a required bridge page
headings instead of a required article
bullet points instead of a required review
ideas instead of a required social set
subject lines instead of a required email sequence
recommendations instead of a required advertorial
a pack list instead of the completed pack

unless the approved output specifically requested planning only.

Individual Asset Ownership

Each asset should define:

Production Owner:

Editing Owner:

Specialist Review Owner:

Affiliate Brain Reviewer Where Required:

Human Approval Owner:

Publishing Or Delivery Owner:

Measurement Owner:

Lifecycle Owner:

One person may hold several roles during manual operation.

The responsibilities must still remain clear.

Cross-Asset Editing

After individual asset editing, the pack must complete cross-asset editing.

Cross-asset editing should check:

offer details remain consistent
price and terms remain consistent
mechanism remains consistent
audience remains consistent
claims remain consistent
evidence is represented consistently
disclosures are present where required
CTAs are coherent
destination links are correct
tone remains suitable
repeated content is intentional
contradictions are removed
unnecessary duplication is reduced
asset sequencing makes sense
content-pack navigation works
message match is preserved

Pack-Level Quality Control

A pack-level review should ask:

Does the pack fulfil its objective?
Does every asset have a necessary role?
Does the pack serve the intended audience?
Does the sequence reflect the audience journey?
Does the pack use approved source material?
Are claims controlled across every asset?
Are disclosures correct across destinations?
Are assets complete?
Are assets individually useful?
Do the assets work together?
Is the CTA path coherent?
Is message match maintained?
Is the pack appropriately persuasive?
Does the pack contain unnecessary volume?
Are required assets missing?
Is the pack ready for specialist review?
Is the pack ready for human approval?

Specialist Review

Pack-level specialist review may include:

compliance
legal
medical
financial
technical
product
offer
brand
strategy
campaign
client
stakeholder

Specialist review may occur:

once at pack-control level
individually for high-risk assets
again after revisions
before final approval

Specialist review must confirm whether changes apply to:

one asset
several assets
the shared claim set
the entire pack

Affiliate Brain Review

Affiliate Brain review may be required to confirm:

offer status remains correct
funnel role is correct
campaign requirement is correct
asset selection supports the approved pathway
traffic-source context is correct
CTA pathway is correct
testing requirements are respected
controlled variations are labelled correctly
no unapproved affiliate decision has been introduced

Affiliate Brain review does not replace:

editing
specialist review
human publication approval

Ads Brain Review

Ads Brain review may be required where the pack includes paid advertising assets.

Ads Brain may confirm:

platform
format
campaign role
variation requirements
message-match requirement
destination
test structure
creative requirement

Ads Brain retains control over:

budgets
bidding
targeting
deployment
optimisation
scaling

Human Approval

Human approval is required before publication, delivery, scheduling or deployment.

Human approval may occur:

for the complete pack
by asset
by asset group
by publishing sequence

The approval decision must identify:

approved version
approved assets
held assets
rejected assets
required changes
destination
publishing or delivery owner

Pack Approval Decisions

Available decisions include:

Pack Approved
Pack Approved With Minor Changes
Selected Assets Approved
Pack Revision Required
Evidence Required
Specialist Review Required
Affiliate Brain Review Required
Ads Brain Review Required
Pack Held
Pack Rejected
Pack Cancelled

Approval does not mean publication has occurred.

Publishing Preparation

Publishing preparation may include:

final titles
URLs
slugs
page hierarchy
metadata
internal links
external links
affiliate links
CTA placement
image requirements
creative requirements
alt text
captions
disclosures
formatting
platform variations
asset naming
version confirmation
destination confirmation
publication sequence
delivery notes
measurement notes

Pack-Level Publishing Readiness

A pack is Publishing-Ready or Delivery-Ready only when:

all required assets are complete
all required editing is complete
shared details are consistent
claims are supportable
disclosures are complete
specialist review is complete
Affiliate Brain review is complete where required
Ads Brain review is complete where required
human approval is recorded
final versions are confirmed
destinations are confirmed
publishing preparation is complete
missing assets are resolved
publication sequence is confirmed
measurement ownership is clear

Partial Pack Release

A partial pack may be released only when:

approved assets are independently usable
missing assets do not create misleading gaps
the release does not break the funnel
the release does not break compliance requirements
the approved publication sequence allows it
human approval explicitly authorises partial release

The pack status must show that remaining assets are incomplete or held.

Human-Controlled Publication And Deployment

Current publication, delivery and deployment remain human controlled.

This includes:

WordPress publication
website updates
email sending
newsletter sending
social posting
social scheduling
video deployment
advertisement deployment
content delivery
client delivery

Content Brain produces and prepares the assets.

An authorised human completes or approves the final action.

Pack Publication Sequence

The pack should define:

Asset 1:

Destination:

Publication Date:

Publishing Owner:

Dependency:

Asset 2:

Destination:

Publication Date:

Publishing Owner:

Dependency:

Asset 3:

Destination:

Publication Date:

Publishing Owner:

Dependency:

Additional Assets:

The sequence should account for:

required landing destinations
link availability
email timing
social timing
campaign timing
search content timing
review and correction time
dependencies between assets

Asset-Level Measurement

Possible asset-level signals include:

impressions
clicks
click-through rate
bridge-page progression
VSL progression
conversion support
search visibility
rankings
email opens
email clicks
video retention
social engagement
time on page
exit patterns
internal-link use
CTA interaction
customer feedback
compliance concerns

Pack-Level Measurement

Possible pack-level signals include:

progression across assets
cross-channel message consistency
content-assisted conversions
repeated objections
asset contribution
channel contribution
audience-stage movement
content gaps
weak sequence points
message-match problems
claim-risk patterns
content-decay patterns
refresh requirements
assets with no useful role

Pack-level measurement does not automatically prove causation.

Signals should be interpreted by the relevant authority.

Measurement Ownership

Data Brain retains measurement-integrity authority.

Experimentation Brain retains test-validity authority.

Affiliate Brain retains affiliate pathway and progression authority.

Ads Brain retains campaign-performance authority.

Content Brain uses approved signals to improve content.

Signal-To-Pack Actions

Approved signals may lead to:

headline revision
hook revision
bridge-page revision
advertorial revision
review improvement
comparison improvement
FAQ expansion
objection content
trust content
new email
new newsletter
new social asset
new script
new controlled variation
content refresh
pack expansion
pack reduction
repurposing
asset merge
asset retirement
pack retirement
no action

Pack Refresh

A pack refresh may be triggered by:

offer change
price change
refund change
rebill change
guarantee change
vendor-page change
VSL change
product change
evidence change
claim concern
compliance change
audience change
campaign change
traffic-source change
performance decline
search decline
content decay
broken links
outdated screenshots or examples
new research
new objections
new customer language
competitor change

Pack Refresh Flow

Refresh Trigger
→ Pack Audit
→ Affected Assets Identified
→ Shared Controls Reviewed
→ Refresh Scope Approved
→ Individual Asset Updates
→ Cross-Asset Consistency Review
→ Specialist Review Where Required
→ Affiliate Brain Review Where Required
→ Human Approval
→ Publishing Preparation
→ Human-Controlled Update
→ Outcome Recording

A shared offer-detail change may require several assets to be refreshed together.

Pack Correction

A pack correction is required where an error affects one or more assets.

Possible errors include:

wrong offer detail
wrong price
wrong refund term
wrong rebill term
unsupported claim
missing disclosure
broken link
incorrect CTA
message mismatch
outdated evidence
technical inaccuracy
compliance risk

Correction Flow:

Error Identified
→ Risk Assessed
→ Affected Assets Identified
→ Live-Use Decision
→ Corrections Produced
→ Cross-Asset Review
→ Specialist Review Where Required
→ Human Approval
→ Human-Controlled Update
→ Outcome Recorded

High-risk errors may require immediate holding or removal.

Pack Merge

Pack merging may be appropriate where:

two packs overlap
two offer pathways have been consolidated
duplicate content systems exist
one pack has stronger approved content
audience or campaign structure has changed

Merge Flow:

Overlapping Packs Identified
→ Primary Pack Selected
→ Useful Assets Preserved
→ Duplicate Assets Removed
→ Shared Controls Reconciled
→ Conflicts Resolved
→ Final Pack Architecture Defined
→ Content Updated
→ Cross-Asset Review
→ Human Approval
→ Publishing Preparation
→ Human-Controlled Publication
→ Old Assets Retired Or Archived

Pack Repurposing

Pack assets may be repurposed across:

website
social
email
newsletter
video
audio
advertising
lead magnets
training
support materials

Repurposing must preserve:

source integrity
evidence boundaries
offer accuracy
disclosure requirements
claim limitations
message meaning

Repurposing Flow:

Approved Source Asset
→ New Channel Or Format
→ Audience Confirmed
→ Repurposing Objective
→ Derivative Asset Plan
→ Production
→ Channel-Fit Editing
→ Cross-Asset Review
→ Human Approval
→ Publishing Preparation
→ Human-Controlled Publication Or Delivery

Pack Retirement

A pack may require retirement when:

the offer is rejected
the offer is retired
the vendor relationship ends
the product is unavailable
the content is no longer accurate
the funnel has been abandoned
the campaign has ended permanently
compliance risk cannot be resolved
the content has been replaced
continued maintenance is not justified

Retirement Flow:

Retirement Trigger
→ Affiliate Brain Status Confirmed
→ Active Use Checked
→ Traffic And Link Impact Checked
→ Replacement Or Redirect Plan
→ Email And Social Use Checked
→ Campaign Use Checked
→ Human Approval
→ Human-Controlled Retirement
→ Archive Or Deletion Outcome Recorded

Do not remove pack assets without checking:

search visibility
inbound links
internal links
live campaigns
emails
newsletters
social content
redirects
related assets
compliance needs
historical records

Pack Status Model

Possible statuses include:

Requested
Qualified
Waiting For Offer Status
Waiting For Research
Waiting For Sources
Waiting For Evidence
Planned
Pack Architecture Defined
Ready For Briefing
Ready For Production
In Production
Partial Draft Complete
Draft Complete
In Editing
Cross-Asset Editing
Revision Required
Waiting For Specialist Review
Waiting For Affiliate Brain Review
Waiting For Ads Brain Review
Waiting For Human Approval
Partially Approved
Approved
Publishing Preparation
Partially Publishing-Ready
Publishing-Ready
Delivery-Ready
Partially Published
Published
Delivered
Publication Failed
Blocked
Held
Rejected
Cancelled
Refresh Required
Correction Required
Repurposing Required
Retirement Required
Retired
Archived

These statuses should not become permanent structured fields until manual use confirms the required model.

Pack Records

Future structured pack records may include:

pack name
offer
offer status
project
campaign
objective
audience
funnel stage
traffic source
pack model
shared sources
evidence requirements
claim controls
disclosure controls
asset list
asset relationships
production order
asset status
editing status
specialist-review status
Affiliate Brain review status
Ads Brain review status
approval status
publishing status
measurement requirement
lifecycle status
blocker
next action

Supabase is the likely destination for repeatable pack and asset records.

MCR remains the source of truth for this Framework.

Minimum Pack Planning Record

For simple manual use, record:

Pack Name:

Offer:

Offer Status:

Pack Objective:

Audience:

Funnel Role:

Traffic Source:

Primary Destination:

Pack Model:

Required Assets:

Shared Sources:

Evidence Requirements:

Claim Risk:

Disclosure Requirements:

Production Order:

Approval Owner:

Publishing Owner:

Measurement Requirement:

Lifecycle Review Date:

Minimum Pack Readiness Check

Before marking a simple pack ready, confirm:

offer status clear
pack objective clear
audience clear
funnel role clear
required assets complete
offer details consistent
sources checked
evidence checked
claims checked
disclosures checked
editing complete
cross-asset editing complete
specialist review complete where required
Affiliate Brain review complete where required
human approval recorded
final versions confirmed
destinations confirmed
publishing preparation complete
publication sequence confirmed
measurement path defined where required

Relationship To Content Brain Affiliate Funnel Support Map

The Affiliate Funnel Support Map defines how Content Brain supports affiliate pathways across funnel stages and channels.

This Framework defines how coordinated affiliate product content packs are constructed and managed within that system.

Affiliate Funnel Support Map = affiliate pathway and authority map

Affiliate Product Content Pack Framework = pack planning, production and lifecycle method

Relationship To Content Brain Content Production System Framework

The Content Production System Framework defines the general production process.

This Framework applies that process to coordinated affiliate content packs.

Relationship To Content Brain Content Brief Template

The Content Brief Template provides:

Full Content Brief
Short Production Brief
Outline Or Blueprint
Direct Production Instruction

This Framework defines how those instruction levels apply across pack and asset production.

Relationship To Content Brain Publishing Readiness Checklist

Individual assets and complete packs must pass the relevant Publishing Readiness checks before publication, delivery, scheduling or deployment.

Relationship To Content Brain Affiliate Product Content Pack Checklist

The Affiliate Product Content Pack Checklist provides the practical verification process for:

pack completeness
shared controls
asset completion
cross-asset consistency
review completion
approval
publishing readiness
lifecycle readiness

Relationship To Affiliate Brain

Affiliate Brain provides:

offer status
funnel requirements
campaign context
testing stage
opportunity status
required content outcomes
approval boundaries

Content Brain provides:

pack planning
asset planning
complete asset production
editing
cross-asset consistency
publishing preparation
lifecycle content support

Relationship To Ads Brain

Ads Brain provides:

platform requirements
paid-traffic strategy
campaign structure
test requirements
variation requirements
performance signals

Content Brain produces approved advertising and supporting content assets.

Ads Brain retains deployment and optimisation authority.

Relationship To Research Brain

Research Brain provides:

evidence
market intelligence
mechanism intelligence
competitor intelligence
customer evidence
research confidence

Content Brain uses approved research to create pack assets.

Relationship To Customer Brain

Customer Brain provides:

audience segments
motivations
barriers
decision criteria
desired outcomes
journey context
customer language

Relationship To Strategy Brain

Strategy Brain provides:

positioning
launch direction
strategic narrative
market priorities
growth priorities

Relationship To Creative Brain

Creative Brain may provide:

concepts
stories
hooks
emotional direction
creative angles
narrative ideas

Relationship To Conversion Brain

Conversion Brain provides:

trust requirements
friction analysis
page-structure guidance
CTA guidance
message-match guidance
persuasion principles

Relationship To Compliance Brain

Compliance Brain provides:

claim boundaries
disclosure interpretation
prohibited-content guidance
escalation decisions
risk interpretation

Relationship To Experimentation Brain

Experimentation Brain provides:

test structure
variant requirements
measurement rules
interpretation standards

Relationship To Data Brain

Data Brain provides:

measurement integrity
trusted performance signals
attribution context
reporting inputs

Relationship To Finance Brain

Finance Brain retains authority over:

test budgets
capital allocation
profitability decisions
scaling capital

Relationship To SIT Brain

SIT Brain may monitor:

authority boundaries
workflow integrity
unsafe implementation
premature automation
system drift

Relationship To HeadOffice

HeadOffice retains:

system governance
cross-Brain conflict resolution
material structural authority
future autonomy approval

Relationship To MCR

MCR remains the source of truth.

This Framework defines the full affiliate product content-pack method.

Operational simplifications must not replace MCR authority.

Relationship To mwmscontentbrain.site

A simplified operational version may later support:

pack request
offer status
pack objective
audience
funnel stage
asset selection
asset relationships
sources
evidence
claims
disclosures
production order
asset status
review status
approval status
publishing preparation
measurement
lifecycle actions

No operational interface build is authorised by this Framework.

Relationship To Content Brain Copy Map

This page is classified as:

Classification: Simplify Before Copy

Source Of Truth: MCR

Future Operational Use: Affiliate Product Content Pack Planning And Production Workspace

Future Plugin Or UI: Possible Affiliate Content Pack Workspace

No plugin or UI implementation is authorised by this Framework.

Relationship To Content Brain Page Registry

This page should be listed as:

Page Title: Content Brain Affiliate Product Content Pack Framework

Document Type: Framework

Parent Page: Content Brain Canon

Status: Active

Version: v1.1

Classification: Simplify Before Copy

Source Of Truth: MCR

Current Manual Operating Boundary

The affiliate content-pack process remains human controlled.

Current restrictions:

no unrestricted content-pack generator
no autonomous pack planner
no autonomous content worker
no autonomous editing worker
no autonomous specialist approval
no autonomous Affiliate Brain approval
no autonomous Ads Brain approval
no autonomous publication
no autonomous social posting
no autonomous email sending
no autonomous advertising deployment
no autonomous campaign changes
no autonomous queues
no Brain Room routing
no automatic M handoff
no AI Employee activation
no interference with M’s Research Brain work

The presence of a complete pack framework does not authorise automation.

Future Interface Direction

A future affiliate content-pack interface may eventually support:

pack request
offer status
project
campaign
objective
audience
funnel role
traffic source
pack model
asset selection
asset relationships
production order
shared sources
evidence controls
claim controls
disclosure controls
asset production
editing status
cross-asset review
specialist review
Affiliate Brain review
Ads Brain review
human approval
publishing preparation
publication status
measurement
lifecycle actions
blockers
next actions

The interface must support complete production.

It must not be limited to:

pack ideas
outlines
brief generation
Site Intelligence records
migration states
checklist counters
content opportunities

Drift Protection

The system must prevent:

packs being created without clear offer status
packs being created without a defined objective
packs being created without a defined audience
packs being created without a funnel role
unnecessary packs
unnecessary asset volume
duplicate assets
outlines being treated as completed assets
briefs being treated as completed assets
pack lists being treated as completed packs
Content Brain taking over Affiliate Brain decisions
Content Brain taking over Ads Brain decisions
packs using inconsistent offer details
packs using inconsistent prices or terms
packs using conflicting mechanisms
unsupported claims
invented evidence
fake testimonials
invented customer experience
false guarantees
false scarcity
false urgency
missing disclosures
deceptive advertorial presentation
repurposed assets expanding claims
inconsistent CTAs
broken message match
missing pack assets being hidden
partial packs being released without approval
specialist-review changes being applied to only one asset when several are affected
the wrong version being published
Publishing-Ready being treated as Published
Approval being treated as Publishing-Ready
assets being retired without traffic, link and campaign review
content records becoming separate WordPress pages
operational pages becoming Canon
queue assumptions being treated as active systems
premature plugin development
premature automation
worker activation
AI Employee activation
Brain Room routing
automatic M handoff
interference with M’s Research Brain work

Architectural Intent

The Content Brain Affiliate Product Content Pack Framework exists to turn approved affiliate opportunities into complete coordinated content systems.

It connects:

offer intelligence
audience intelligence
research
strategy
creative direction
funnel requirements
traffic requirements
content planning
asset production
editing
cross-asset consistency
specialist review
Affiliate Brain review
human approval
publishing preparation
measurement
lifecycle action

The Framework must support:

compact early-stage packs
standard active packs
full multi-channel packs
organic affiliate pathways
paid affiliate pathways
website systems
content systems
email systems
social systems
video systems
advertising support
refreshes
corrections
merges
repurposing
retirement

It must support current manual operation and later controlled implementation.

Future interfaces, workers and AI Employees must operate beneath this Framework.

They must not narrow or bypass it.

Final Rule

An affiliate product content pack is complete only when the required approved assets have been produced, reviewed, approved and prepared as one coordinated system.

A pack plan is not a completed pack.

A brief is not a completed pack.

An asset list is not a completed pack.

An outline is not a completed pack.

Individual drafts do not become a completed pack until cross-asset review is complete.

Affiliate Brain controls affiliate decisions.

Ads Brain controls paid campaign decisions.

Content Brain controls affiliate content-pack production.

Research Brain controls research authority.

Compliance Brain controls specialist claim and disclosure interpretation.

Experimentation Brain controls test validity.

Data Brain controls measurement integrity.

Humans retain final approval, publication, delivery and deployment control.

No pack may move into live use unless:

offer status is clear
pack objective is clear
audience is clear
funnel role is clear
required assets are complete
shared sources are confirmed
evidence is sufficient
claims are controlled
disclosures are complete
editing is complete
cross-asset consistency is confirmed
specialist review is complete where required
Affiliate Brain review is complete where required
Ads Brain review is complete where required
human approval is recorded
publishing preparation is complete
final versions are confirmed
destinations are confirmed
publication sequence is confirmed

Approved is not Publishing-Ready.

Publishing-Ready is not Published.

Delivery-Ready is not Delivered.

No premature automation.

No autonomous publishing.

No autonomous campaign changes.

No worker activation.

No AI Employee activation.

No Brain Room routing.

No automatic M handoff.

No interference with M’s Research Brain work.

Change Log

v1.1 — 2026-06-15

Created a full replacement for the previous Content Brain Affiliate Product Content Pack Framework.

Expanded the Framework from an affiliate support-pack model into the complete affiliate content-pack planning, production, review, approval, publishing-preparation, measurement and lifecycle system.

Clarified:

Content Brain owns complete content-pack production
Affiliate Brain owns offer, funnel, testing and affiliate pathway decisions
Ads Brain owns paid campaign structure, budgets, bidding, optimisation and scaling
Research Brain remains the research authority
Compliance Brain retains specialist claim and disclosure authority
humans retain final approval, publication, delivery and deployment control

Added:

rules for when a pack is required
rules for when a pack is not required
offer-status gates
pack-objective control
audience and funnel definition
shared source controls
shared evidence controls
shared offer-detail controls
shared claim controls
shared disclosure controls
shared message controls
message-match controls
asset-selection rules
asset-selection records
Minimum Pack model
Standard Pack model
Full Pack model
Custom Pack model
pack planning flow
existing-content checks
pack architecture
four production-instruction levels
production order
central-asset principle
complete asset-production requirements
individual asset ownership
cross-asset editing
pack-level quality control
specialist review
Affiliate Brain review
Ads Brain review
human approval
pack approval decisions
publishing preparation
pack-level publishing readiness
partial-pack release rules
publication sequence
asset-level measurement
pack-level measurement
signal-to-pack actions
pack refresh
pack correction
pack merge
pack repurposing
pack retirement
pack status model
future structured pack records
minimum manual planning record
minimum readiness check
revised manual operating boundaries
future interface direction
expanded drift protection

Removed dependence on inactive opportunity and production queues.

Clarified that:

a full brief is not mandatory for every asset
outlines do not count as completed assets
individual drafts do not count as a completed pack
Publishing-Ready remains separate from Published
Delivery-Ready remains separate from Delivered

Aligned this Framework with:

Content Brain Canon v1.1
Content Brain Architecture v1.1
Content Brain Operating Model v1.2
Content Brain Workflow Map v1.2
Content Brain Affiliate Funnel Support Map v1.2
Content Brain Content Production System Framework v1.1
Content Brain Content Brief Template v1.2
Content Brain Publishing Readiness Checklist v1.1
Content Brain Page Registry v3.1
Content Brain Copy Map v2.6

v1.0

Initial creation of the Content Brain Affiliate Product Content Pack Framework.

Defined the original affiliate content-pack model covering:

offer context
audience
funnel role
product-support content
pre-sell content
articles
reviews
comparisons
FAQs
trust content
YouTube support
VEO3 support
email
social
internal linking
repurposing
compliance notes
research requirements
performance signals
future operational use

Change Impact Declaration

Pages Created:

Content Brain Affiliate Product Content Pack Framework replacement page

Pages Updated:

None during replacement creation

Pages To Move To Trash After Validation:

Previous Content Brain Affiliate Product Content Pack Framework v1.0 page

Pages Deprecated:

Previous Content Brain Affiliate Product Content Pack Framework v1.0 after the v1.1 replacement is published and validated

Registries Requiring Update:

Content Brain Page Registry should show Content Brain Affiliate Product Content Pack Framework v1.1.

Content Brain Copy Map should show Content Brain Affiliate Product Content Pack Framework v1.1 where a version is recorded.

Canon Version Update Required:

Automation Status Change:

Plugin Or UI Status Change:

Worker Status Change:

AI Employee Status Change:

M Handoff Required:

Research Brain Impact:

None

END CONTENT BRAIN AFFILIATE PRODUCT CONTENT PACK FRAMEWORK v1.1