Content Brain Affiliate Product Content Pack Checklist

Document Type: Checklist
Status: Active
Version: v1.1
Authority: Content Brain under HeadOffice governance
Applies To: Affiliate Product Content Pack Qualification, Planning, Production, Review, Approval, Publishing Preparation, Measurement And Lifecycle Management
Parent: Content Brain
Enforcement Mode: Operational
Last Reviewed: 2026-06-15

Content Brain Affiliate Product Content Pack Checklist

Purpose

The Content Brain Affiliate Product Content Pack Checklist defines the practical verification process used to confirm whether an affiliate product content pack is:

necessary
correctly planned
sufficiently sourced
accurately produced
internally consistent
properly reviewed
human approved
publishing-ready
measurable
lifecycle-ready

This Checklist operates beneath the Content Brain Affiliate Product Content Pack Framework.

The Framework defines how affiliate content packs should work.

This Checklist confirms whether an individual pack has followed that Framework.

The Checklist exists to prevent:

unnecessary content packs
packs with unclear offer status
packs with no defined audience
packs with no funnel role
disconnected assets
incomplete assets
outline-only assets being treated as finished content
inconsistent offer details
inconsistent claims
missing disclosures
weak message match
incomplete review
premature publishing
incomplete packs being presented as complete
packs with no measurement or lifecycle plan

Core Principle

A content pack is not complete because an asset list exists.

A content pack is not complete because briefs exist.

A content pack is not complete because outlines exist.

A content pack is not complete because individual drafts exist.

A pack is complete only when the required approved assets:

have been fully produced
have completed editing
work together
use consistent source material
use consistent offer details
remain within approved evidence and claim boundaries
contain required disclosures
have completed required specialist review
have completed required Affiliate Brain review
have completed required Ads Brain review
have received human approval
have completed publishing preparation
are ready for their approved destinations

Scope

This Checklist applies to:

Minimum Affiliate Product Content Packs
Standard Affiliate Product Content Packs
Full Affiliate Product Content Packs
Custom Affiliate Product Content Packs
affiliate website packs
affiliate funnel packs
paid-traffic support packs
organic-content packs
article packs
video and script packs
advertising packs
newsletter and email packs
social content packs
refresh packs
repurposing packs
correction packs
merged packs
retirement packs

What This Checklist Does Not Authorise

This Checklist does not independently authorise:

offer approval
offer rejection
campaign approval
testing approval
stage progression
budget approval
bidding
targeting
campaign deployment
campaign optimisation
controlled scaling
statistical interpretation
final legal interpretation
final compliance interpretation
broad research
autonomous publication
autonomous social posting
autonomous email sending
autonomous advertising deployment
plugin development
worker activation
AI Employee activation
Brain Room routing
automatic M handoff

These remain controlled by the appropriate Brain, human authority, framework, protocol or authorised system.

Checklist Decision Model

Each section should receive one of the following decisions:

Pass
Pass With Minor Action
Hold
Fail
Not Applicable

A pack must not receive final approval while a mandatory section remains:

Hold
Fail
Not Reviewed

Pack Review Record

Pack Name:

Offer:

Offer Status:

Project:

Campaign:

Pack Type:

Content Action:

Primary Audience:

Primary Funnel Role:

Traffic Source:

Primary Destination:

Pack Owner:

Production Owner:

Editing Owner:

Affiliate Brain Reviewer:

Ads Brain Reviewer:

Specialist Reviewer:

Human Approval Owner:

Publishing Owner:

Measurement Owner:

Lifecycle Owner:

Review Date:

Current Pack Status:

Stage 1: Pack Requirement Check

Confirm whether a coordinated content pack is genuinely required.

Required checks:

more than one related asset is needed
the assets support one shared affiliate objective
the assets require coordinated messaging
the assets require shared source material
the assets require shared evidence or claim control
the assets support one connected funnel, campaign or audience journey
the work cannot be handled more efficiently as one standalone asset
existing content does not already satisfy the requirement
pack production is justified by current offer status
pack size is proportionate to the business need

Pass condition:

A coordinated pack is the correct production model.

Fail condition:

The proposed pack creates unnecessary content volume, duplication or complexity.

Failure action:

Reduce the request to:

one standalone asset
one refresh
one correction
one repurposed asset
no action

Pack Required:

Yes

Reason:

Decision:

Stage 2: Originating Authority Check

Confirm the request has a valid source.

Possible originating authorities include:

Martyn
HeadOffice
Affiliate Brain
Ads Brain
Strategy Brain
authorised human operator
approved campaign requirement
approved offer requirement
approved lifecycle decision
approved refresh decision
approved repurposing decision
approved correction requirement

Required checks:

requesting authority identified
request purpose recorded
offer identified
project identified
campaign identified where relevant
pack owner identified
approval owner identified
publishing owner identified
unresolved authority conflict absent

Pass condition:

The pack has a clear authorised source and ownership.

Fail condition:

The pack was created without clear authority or ownership.

Failure action:

Return for request qualification.

Decision:

Stage 3: Offer Status Check

Confirm the offer status before pack work progresses.

Possible statuses:

Exploratory
Approved For Research
Approved For Planning
Approved For Funnel Support
Approved For Testing Support
Live Campaign Support
Refresh Existing Support
Retired
Rejected
Held
Unknown

Required checks:

offer status confirmed by Affiliate Brain or authorised human
offer has sufficient authority for current pack stage
live-use production is authorised where required
testing assets are authorised where required
retired or rejected offers are not receiving new promotional assets
unclear status is not being treated as approval

Pass condition:

Offer status supports the current pack activity.

Fail condition:

The offer status is unclear, insufficient, retired or rejected.

Failure action:

Hold pack production.

Offer Status:

Current Authorised Activity:

Decision:

Stage 4: Pack Objective Check

Confirm the pack has one clear primary objective.

Possible objectives include:

problem education
solution education
mechanism education
offer introduction
pre-sell support
bridge-page support
review support
comparison support
trust development
objection handling
paid-traffic support
organic-traffic support
email nurture
social education
launch support
retargeting support
content refresh
content repurposing
correction
retirement

Required checks:

primary objective defined
secondary objective defined where relevant
expected audience outcome defined
expected business outcome defined
primary destination defined
pack assets support the objective
no unrelated assets have been added
pack scope is not broader than required

Pass condition:

Every asset contributes to the approved pack objective.

Fail condition:

The pack is a collection of possible assets without a clear shared purpose.

Decision:

Stage 5: Audience Check

Confirm the pack is designed for a defined audience.

Required checks:

primary audience defined
secondary audience defined where relevant
audience segment defined
buyer persona identified where relevant
awareness stage defined
journey stage defined
decision stage defined
knowledge level understood
primary problem defined
desired outcome defined
primary barrier defined
primary objection defined
trust level considered
decision criteria considered
customer language available where required

Pass condition:

The pack speaks to a known audience and journey stage.

Fail condition:

The pack is generic or attempts to speak to everyone.

Decision:

Stage 6: Funnel Role Check

Confirm the pack has a defined role in the affiliate pathway.

Possible funnel roles include:

awareness
problem education
solution education
mechanism education
offer introduction
pre-sell
bridge
evaluation
review
comparison
trust
objection handling
conversion support
retargeting
follow-up
post-click education
lifecycle support

Required checks:

primary funnel role confirmed
secondary funnel role confirmed where relevant
entry point confirmed
next step confirmed
traffic source confirmed
central destination confirmed
asset sequence supports the funnel role
CTA path is coherent
the pack does not take over Affiliate Brain authority

Pass condition:

The pack has a clear place in the approved affiliate pathway.

Fail condition:

Assets exist without a defined journey or next step.

Decision:

Stage 7: Pack Model Check

Confirm the correct pack model has been selected.

Possible pack models:

Minimum Pack
Standard Pack
Full Pack
Custom Pack

Minimum Pack Check

Confirm:

the objective is narrow
the audience is focused
the traffic source is limited
only essential assets are included
early controlled use is appropriate
complete assets will be produced
outlines are not being counted as finished assets

Standard Pack Check

Confirm:

active funnel support is justified
multiple channels or assets are required
sufficient evidence exists
education, trust and conversion support are required
production scope remains manageable

Full Pack Check

Confirm:

full multi-channel production is justified
the offer has sufficient status and evidence
sufficient production capacity exists
the content system requires extensive asset coverage
full-pack production is not being used merely to create volume

Custom Pack Check

Confirm:

non-standard assets are justified
existing content has been considered
specialised channel requirements are documented
custom scope still follows shared controls

Selected Pack Model:

Reason:

Pack Model Appropriate:

Decision:

Stage 8: Existing-Content Check

Confirm existing content has been reviewed before new assets are created.

Required checks:

relevant website pages checked
relevant articles checked
relevant bridge pages checked
relevant reviews checked
relevant comparisons checked
relevant advertorials checked
relevant emails checked
relevant newsletters checked
relevant social content checked
relevant scripts checked
relevant advertising assets checked
relevant lead magnets checked
duplicate-content risk assessed
outdated content identified
reusable content identified
refresh opportunities identified
merge opportunities identified
repurposing opportunities identified
retirement needs identified

Possible actions:

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

Pass condition:

New production is limited to genuine content needs.

Fail condition:

The pack duplicates suitable existing content.

Decision:

Stage 9: Shared Source Check

Confirm the pack has a controlled source base.

Possible sources include:

Affiliate Brain offer intelligence
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
Ads Brain campaign requirements
approved existing content
approved performance signals
authorised human instructions

Required checks:

shared source list complete
source owners identified
source dates checked
source reliability considered
source gaps recorded
assumptions recorded
interpretations distinguished from facts
restricted source use identified
outdated sources removed
source conflicts resolved
no source fabricated

Source classifications may include:

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

Pass condition:

The pack uses a visible and controlled source base.

Fail condition:

Pack content relies on unclear, unsupported or fabricated source material.

Decision:

Stage 10: Shared Evidence Check

Confirm the evidence base supports pack claims.

Required checks:

evidence requirements defined
approved evidence identified
evidence gaps recorded
research requirements completed
claims linked to evidence where required
evidence limitations understood
evidence is not overstated
citations are accurate where required
no study or report is misrepresented
no expert endorsement is invented
no customer result is invented
no testimonial is invented
no outcome is presented as guaranteed without valid authority

Pass condition:

The pack’s factual and persuasive claims remain within approved evidence boundaries.

Fail condition:

Claims exceed the available evidence.

Failure action:

remove claim
qualify claim
request research
request specialist review
hold affected assets

Decision:

Stage 11: Shared Offer Detail Check

Confirm all assets use consistent verified offer information.

Required checks:

offer name consistent
vendor name consistent
product or service description consistent
price consistent where used
discount consistent where used
refund terms consistent
rebill terms consistent
subscription terms consistent
guarantee language consistent
delivery terms consistent
feature descriptions consistent
mechanism description consistent
intended-use language consistent
limitation statements consistent
vendor page correct
VSL correct
CTA destination correct
old offer details removed

Pass condition:

All pack assets represent the offer consistently.

Fail condition:

Offer details differ between assets without approved reason.

Decision:

Stage 12: Shared Claim Control Check

Confirm the pack uses controlled claim language.

Required checks:

approved claims listed
restricted claims listed
prohibited claims listed
claims requiring qualification identified
claims requiring evidence identified
claims requiring specialist review identified
guarantee language checked
urgency language checked
scarcity language checked
result language checked
comparison claims checked
health or medical claims checked
income or finance claims checked
safety claims checked
performance claims checked
no asset expands claims beyond the approved source

Claim Risk:

Low
Moderate
High
Critical

Pass condition:

Claims remain consistent, supportable and appropriately controlled across the pack.

Fail condition:

One or more assets introduce unsupported or unapproved claims.

Decision:

Stage 13: Shared Disclosure Check

Confirm disclosure requirements are defined and applied.

Required checks:

affiliate disclosure requirement confirmed
disclosure wording approved
website disclosure placement confirmed
review disclosure confirmed
comparison disclosure confirmed
advertorial disclosure confirmed
email disclosure confirmed
newsletter disclosure confirmed
social disclosure confirmed
video disclosure confirmed
advertising disclosure confirmed
platform-specific requirements considered
disclosure is visible
disclosure is understandable
disclosure is not hidden after the recommendation
Compliance Brain or authorised human review completed where required

Pass condition:

Required disclosures are present and suitable for each destination.

Fail condition:

Required affiliate, advertorial or material relationship disclosures are missing or unclear.

Decision:

Stage 14: Shared Message Check

Confirm the pack communicates one coherent approved message system.

Required checks:

primary message defined
supporting messages defined
primary angle defined
secondary angle defined
mechanism position consistent
authority position consistent
identity-outcome position consistent
trust position consistent
CTA direction coherent
audience problem consistently represented
expected outcome consistently represented
channel adaptation does not change core meaning
no asset introduces conflicting positioning

Pass condition:

The pack’s message remains coherent across assets and channels.

Fail condition:

Assets present conflicting promises, mechanisms, audiences or CTAs.

Decision:

Stage 15: Message-Match Check

Confirm continuity across the full content path.

Review where relevant:

ad to bridge page
ad to advertorial
social post to article
email to bridge page
article to review
YouTube video to description link
newsletter to offer page
bridge page to vendor page
pre-sell page to VSL
review page to vendor page
comparison page to selected offer
CTA to destination

Required checks:

audience remains consistent
problem remains consistent
hook remains connected
promise remains supportable
mechanism remains consistent
offer remains consistent
evidence remains consistent
CTA matches the next step
destination supports the expectation
no misleading jump exists

Pass condition:

The pack creates a coherent path from entry asset to approved next step.

Fail condition:

The destination cannot support the expectation created by the preceding asset.

Decision:

Stage 16: Asset Selection Check

Confirm every selected asset has a necessary role.

For each asset, verify:

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

Required checks:

every asset has a defined purpose
no unnecessary asset has been included
no required asset is missing
each asset fits the selected pack model
each asset has a destination
each asset has ownership
each asset connects to the pack architecture

Pass condition:

The selected asset set is complete but proportionate.

Fail condition:

The pack contains unnecessary assets or omits critical assets.

Decision:

Stage 17: Central Asset Check

Confirm the pack has a central asset or central destination where required.

Possible central assets include:

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

Required checks:

central asset identified
central asset purpose defined
supporting assets connect correctly
CTA pathway supports the central asset
central asset is complete
central asset has passed editing
central asset has passed required review
destination is confirmed

Pass condition:

The pack has a clear centre or primary journey.

Fail condition:

Supporting assets lead to unclear or conflicting destinations.

Decision:

Stage 18: Pack Architecture Check

Confirm the relationship between assets is clear.

Pack Entry Asset:

Education Asset:

Trust Asset:

Evaluation Asset:

Conversion-Support Asset:

Follow-Up Asset:

Repurposed Assets:

Primary Destination:

Secondary Destination:

Measurement Points:

Required checks:

entry assets identified
supporting sequence defined
internal links defined
CTAs defined
dependencies recorded
destination order confirmed
publication order considered
no circular or broken pathway exists
assets do not compete unnecessarily
pack remains understandable to the audience

Pass condition:

The pack operates as a coordinated content system.

Fail condition:

Assets exist as disconnected pieces.

Decision:

Stage 19: Production Instruction Check

Confirm each asset has the correct level of production instruction.

Possible instruction levels:

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

Required checks:

instruction level selected
level is proportionate
purpose is clear
audience is clear
asset type is clear
destination is clear
source material is clear
evidence requirements are clear
claim boundaries are clear
required structure is clear
CTA is clear
review requirements are clear
completion standard is clear

Pass condition:

Each asset is sufficiently defined for production without unnecessary briefing overhead.

Fail condition:

The asset is under-defined or over-briefed.

Decision:

Stage 20: Production Order Check

Confirm asset production occurs in a logical sequence.

Recommended general sequence:

Pack controls
Shared sources
Offer details
Evidence and claims
Central funnel asset
Supporting website assets
Authority and educational assets
Newsletter and email assets
Video and script assets
Social assets
Advertising assets
Cross-asset editing
Message-match review
Specialist review
Affiliate Brain review
Ads Brain review where required
Human approval
Publishing preparation
Pack readiness
Human-controlled publication or deployment

Required checks:

dependencies identified
central asset produced early enough
supporting assets use approved central messaging
ad assets are not finalised before destination message is stable
publication sequence is considered
production order does not create avoidable rework

Pass condition:

Production order reflects asset dependencies.

Fail condition:

Assets are produced in a way that creates inconsistency or avoidable rework.

Decision:

Stage 21: Complete Asset Production Check

Confirm each required asset has been fully produced.

The following do not count as completed assets unless specifically requested:

idea lists
outlines
content seeds
headline lists
section notes
brief summaries
recommendations
rough fragments
incomplete drafts
placeholder copy

For each asset, record:

Asset Name:

Required Output:

Current Status:

Complete:

Editing Complete:

Specialist Review Complete:

Affiliate Brain Review Complete:

Ads Brain Review Complete:

Human Approval Complete:

Publishing Preparation Complete:

Destination:

Outstanding Action:

Pass condition:

Every required pack asset exists as a complete usable asset.

Fail condition:

One or more required assets remain incomplete or are represented only by outlines or ideas.

Decision:

Stage 22: Individual Asset Quality Check

Confirm each asset meets the Content Brain quality standard.

Required checks:

clear
useful
specific
audience-aligned
intent-aligned
channel-appropriate
complete
correctly structured
accurate
evidence-aware
appropriately persuasive
non-generic
free from unnecessary repetition
free from filler
free from unsupported claims
correctly formatted
CTA appropriate
disclosures included where required

Pass condition:

Each asset is independently fit for its intended role.

Fail condition:

One or more assets are thin, generic, unclear, incomplete or unsuitable.

Decision:

Stage 23: Cross-Asset Editing Check

Confirm pack-level editing has occurred after individual asset editing.

Required checks:

offer details consistent
price and terms consistent
mechanism consistent
audience consistent
claim language consistent
evidence represented consistently
disclosures present where required
CTA pathway coherent
destination links correct
tone suitable across channels
intentional repetition distinguished from duplication
conflicting statements removed
unnecessary repetition reduced
asset order makes sense
internal links work
pack navigation works
message match preserved
outdated versions removed from the pack

Pass condition:

The pack operates as one coordinated system.

Fail condition:

Assets contradict, duplicate or weaken one another.

Decision:

Stage 24: Internal-Linking Check

Confirm website and content relationships are correctly linked.

Required checks:

central page links present
supporting article links present
review links present
comparison links present
FAQ links present
trust links present
bridge-page links correct
vendor links correct
affiliate tracking links correct where authorised
anchor text natural
links support the reader
no excessive money-page pushing
no broken links
no test or staging links
redirect needs documented
retirement-related link changes documented

Pass condition:

Internal linking supports navigation, funnel movement and site structure.

Fail condition:

Links are missing, broken, forced or misleading.

Decision:

Stage 25: Advertising Asset Check

Use where the pack contains paid advertising assets.

Required checks:

Ads Brain request confirmed
platform confirmed
campaign role confirmed
audience confirmed
format confirmed
angle confirmed
hook confirmed
CTA confirmed
destination confirmed
message match confirmed
variations labelled
test requirements followed
claims within approved limits
disclosures included where required
creative requirements complete
no unapproved urgency
no unapproved scarcity
no unapproved guarantee
Ads Brain review complete
deployment remains human controlled

Pass condition:

Advertising assets are complete and suitable for authorised campaign handling.

Fail condition:

Assets introduce unapproved campaign, claim or deployment decisions.

Decision:

Stage 26: Email And Newsletter Check

Use where the pack contains newsletters or email sequences.

Required checks:

audience or list confirmed
email purpose confirmed
sequence order confirmed
subject lines complete
preview text complete
emails complete
CTA pathway coherent
links checked
personalisation fields checked
offer details consistent
disclosures included
sending owner confirmed
schedule confirmed
follow-up logic confirmed
measurement requirement defined
email-platform formatting prepared
sending remains human controlled

Pass condition:

Email and newsletter assets are complete and deployment-ready.

Fail condition:

Emails are incomplete, inconsistent or have no approved sending path.

Decision:

Stage 27: Video And Script Check

Use where the pack contains video or audio scripts.

Required checks:

script type confirmed
platform confirmed
duration confirmed
hook complete
opening complete
structure complete
pacing reviewed
spoken language reviewed
scene guidance complete where required
shot guidance complete where required
on-screen text complete
claims checked
evidence checked
CTA confirmed
disclosure requirements confirmed
production notes complete
human approval recorded

Pass condition:

Scripts are complete and production-ready.

Fail condition:

Scripts are incomplete, hard to deliver or contain unsupported material.

Decision:

Stage 28: Social Content Check

Use where the pack contains social assets.

Required checks:

platform identified
platform-specific format used
hook suitable
core message clear
length suitable
tone suitable
CTA suitable
visual requirements defined
links correct
claims checked
disclosure requirements checked
source meaning preserved
generic cross-platform copying removed
scheduling owner confirmed
posting remains human controlled

Pass condition:

Social assets are adapted correctly for their platforms.

Fail condition:

Social assets are generic copies or introduce unsupported claims.

Decision:

Stage 29: Affiliate Review And Comparison Check

Use where the pack contains review or comparison content.

Required checks:

review purpose clear
comparison criteria clear
offer details verified
intended audience fit explained
benefits supportable
limitations included
alternatives treated fairly
competitor claims checked
no fabricated firsthand experience
no fake testing
no fake expert authority
refund and rebill details verified where included
disclosure present
CTA appropriate
Affiliate Brain review complete where required

Pass condition:

Review and comparison assets are fair, transparent and useful.

Fail condition:

The asset uses deceptive independence, fabricated experience or unsupported superiority.

Decision:

Stage 30: Advertorial And Pre-Sell Check

Use where the pack contains advertorial, pre-sell or bridge content.

Required checks:

traffic source confirmed
audience stage confirmed
hook aligned
educational value present
mechanism represented accurately
offer transition clear
CTA appropriate
disclosure present where required
advertorial presentation not deceptive
no fabricated reporting
no invented customer story
no fake testimonial
no unsupported urgency
destination accurately represented
message match confirmed
human approval recorded

Pass condition:

The asset prepares the audience without deception or overstatement.

Fail condition:

The asset creates false editorial independence or unsupported expectations.

Decision:

Stage 31: Specialist Review Check

Confirm required specialist review has been completed.

Possible reviewers include:

Compliance Brain
legal reviewer
medical reviewer
financial reviewer
technical reviewer
product reviewer
offer reviewer
brand reviewer
strategy reviewer
client
stakeholder

Required checks:

risk level classified
reviewer identified
correct version reviewed
reviewer decision recorded
mandatory changes completed
shared changes applied across all affected assets
unresolved risks held
re-review completed where required

Pass condition:

All required specialist review is complete.

Fail condition:

Material risk remains unresolved.

Decision:

Stage 32: Affiliate Brain Review Check

Confirm Affiliate Brain review where required.

Required checks:

offer status remains correct
funnel role remains correct
campaign context remains correct
asset selection supports approved pathway
traffic-source context remains correct
CTA path remains correct
testing requirements respected
controlled variations labelled
no unapproved affiliate decision introduced
rejected or held assets identified

Pass condition:

The pack remains aligned with Affiliate Brain authority.

Fail condition:

The pack introduces unapproved offer, funnel or testing decisions.

Decision:

Stage 33: Ads Brain Review Check

Use where the pack contains paid campaign assets.

Required checks:

platform requirements confirmed
campaign role confirmed
asset formats confirmed
test requirements confirmed
variation labels confirmed
destination confirmed
message match confirmed
creative requirements confirmed
Ads Brain review decision recorded
no budget, bidding or targeting decision introduced by Content Brain

Pass condition:

Advertising assets meet Ads Brain requirements without crossing authority boundaries.

Decision:

Stage 34: Human Approval Check

Confirm an authorised human has approved the correct pack and asset versions.

Required checks:

approval owner identified
correct pack version reviewed
correct asset versions reviewed
approval decision recorded
requested changes completed
selected assets approved
held assets identified
rejected assets identified
destination approved
publication sequence approved
partial release approved where relevant
approval date recorded

Possible decisions:

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

Pass condition:

The approved assets and versions are clearly identified.

Fail condition:

Approval is missing, unclear or applies to a different version.

Decision:

Stage 35: Final-Version Check

Confirm the correct versions are being prepared for use.

Required checks:

pack version confirmed
asset versions confirmed
old drafts separated
file names correct
page titles correct
asset titles correct
approved copy matches destination copy
no unresolved comments
no tracked changes where inappropriate
no placeholders
no internal instructions in public content
no obsolete offer details
no duplicate final files
approved links included

Pass condition:

The correct approved versions are ready.

Fail condition:

Version uncertainty remains.

Decision:

Stage 36: Publishing Preparation Check

Confirm all assets are correctly prepared for their destinations.

Required checks where relevant:

final titles confirmed
URLs confirmed
slugs confirmed
page hierarchy confirmed
metadata confirmed
headings confirmed
internal links confirmed
external links confirmed
affiliate links confirmed
CTA placement confirmed
image requirements confirmed
alt text confirmed
captions confirmed
disclosures confirmed
formatting complete
platform variations complete
asset naming complete
destination confirmed
publishing instructions complete
delivery instructions complete
publication sequence complete
measurement notes complete

Pass condition:

An authorised human can publish or deploy the assets without further content work.

Fail condition:

The pack remains in Publishing Preparation.

Decision:

Stage 37: Pack-Level Publishing Readiness Check

Confirm the complete pack is genuinely ready.

Required checks:

required assets complete
missing assets resolved
individual editing complete
cross-asset editing complete
offer details consistent
evidence sufficient
claims controlled
disclosures complete
message match confirmed
specialist review complete
Affiliate Brain review complete where required
Ads Brain review complete where required
human approval recorded
final versions confirmed
destinations confirmed
publishing preparation complete
publication sequence confirmed
measurement ownership clear
lifecycle ownership clear

Possible decisions:

Publishing-Ready
Delivery-Ready
Partially Publishing-Ready
Hold For Missing Assets
Hold For Revision
Hold For Evidence
Hold For Specialist Review
Hold For Affiliate Brain Review
Hold For Ads Brain Review
Hold For Human Approval
Hold For Publishing Preparation
Rejected
Cancelled

Decision:

Stage 38: Partial-Pack Release Check

Use when only part of the pack will be released.

Required checks:

approved assets are independently usable
missing assets do not create a misleading gap
release does not break the funnel
release does not break message match
release does not break disclosures
release does not create unsupported claims
release does not create broken links
human approval explicitly permits partial release
remaining assets remain clearly marked incomplete
pack status remains Partially Approved or Partially Published
later publication sequence remains recorded

Pass condition:

Partial release is safe, useful and explicitly approved.

Fail condition:

The pack must remain held.

Decision:

Stage 39: Human-Controlled Publication Or Deployment Check

Confirm final action remains human controlled.

Required checks:

publishing owner identified
deployment owner identified
schedule confirmed
destination permissions confirmed
approved version used
links tested
publication result confirmed
failed publication not marked Published
failed delivery not marked Delivered
failed deployment not treated as Live
publication date recorded
delivery date recorded
campaign deployment remains under Ads Brain and human control

The Checklist does not authorise autonomous:

WordPress publication
website editing
social posting
social scheduling
newsletter sending
email deployment
advertising deployment
campaign changes
document delivery
client delivery

Decision:

Stage 40: Publication Sequence Check

Confirm pack assets will be published or deployed in the correct order.

For each asset, record:

Asset:

Destination:

Publishing Date:

Publishing Owner:

Dependency:

Status:

Required checks:

landing destinations exist before traffic is sent
internal links will work at release
email timing is correct
social timing is correct
campaign timing is correct
supporting articles exist where required
review time is included
correction time is included
launch dependencies are visible
held assets do not block approved independent assets unless required

Pass condition:

The publication sequence is practical and coherent.

Decision:

Stage 41: Asset-Level Measurement Check

Confirm meaningful assets have appropriate measurement requirements.

Possible signals:

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
CTA interaction
internal-link use
customer feedback
compliance concerns
content-decay signals

Required checks:

signal defined
measurement owner defined
review date defined
relevant authority identified
signal limitations understood
no single signal treated as proof without context

Decision:

Stage 42: Pack-Level Measurement Check

Confirm the pack can be reviewed as a connected system.

Possible pack-level signals:

progression across assets
cross-channel consistency
assisted conversions
repeated objections
asset contribution
channel contribution
journey-stage movement
weak sequence points
message-match problems
content gaps
claim-risk patterns
content-decay patterns
unused assets
duplicated assets

Required checks:

primary pack signal defined
secondary pack signals defined
review owner identified
review timing defined
Affiliate Brain feedback path identified
Ads Brain feedback path identified where relevant
Data Brain input identified where relevant
Experimentation Brain input identified where relevant
Content Brain lifecycle action path identified

Decision:

Stage 43: Refresh Readiness Check

Use where the pack or one or more assets require refresh.

Required checks:

refresh trigger identified
affected assets identified
shared controls reviewed
outdated offer details identified
outdated evidence identified
changed claims identified
disclosure changes identified
message-match changes identified
broken links identified
content-decay issues identified
refresh scope approved
useful existing content preserved
review and approval requirements confirmed

Possible refresh triggers:

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
broken links
new research
new objections
new customer language

Decision:

Stage 44: Correction Check

Use where an error affects one or more assets.

Required checks:

error identified
risk assessed
affected assets identified
live-use decision made
correction produced
shared changes applied
cross-asset review completed
specialist review completed where required
human approval completed
update prepared
correction outcome recorded

Possible errors:

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 concern

High-risk errors may require immediate holding or removal.

Decision:

Stage 45: Merge Check

Use where overlapping assets or packs should be consolidated.

Required checks:

primary asset or pack selected
secondary assets identified
useful material preserved
duplicate material removed
conflicting details resolved
shared controls reconciled
final architecture defined
internal links updated
redirect requirements confirmed
retirement requirements confirmed
human approval recorded
old assets not removed before validation

Decision:

Stage 46: Repurposing Check

Use where approved pack assets are adapted to new channels or formats.

Required checks:

source asset identified
source asset approved
repurposing objective defined
new audience confirmed
new channel confirmed
new format confirmed
core meaning preserved
evidence preserved correctly
claims not expanded
disclosure requirements adapted
structure adapted
tone adapted
length adapted
CTA adapted
visual requirements adapted
human approval recorded
relationship to original asset recorded

Decision:

Stage 47: Retirement Check

Use where pack assets should be removed, archived or replaced.

Required checks:

retirement trigger identified
Affiliate Brain offer status confirmed
campaign use checked
traffic checked
search visibility checked
inbound links checked
internal links checked
email use checked
newsletter use checked
social use checked
advertising use checked
replacement identified where required
redirects planned
archive requirements identified
human approval recorded
historical record preserved where required

Possible retirement triggers:

offer rejected
offer retired
vendor relationship ended
product unavailable
content inaccurate
funnel abandoned
campaign permanently ended
compliance risk unresolved
replacement asset approved
maintenance no longer justified

Decision:

Stage 48: Queue And Automation Boundary Check

Confirm inactive or future systems have not been treated as operational.

The following are not active operational systems:

Content Opportunity Queue
Content Production Queue
Content Refresh Queue
Content Repurposing Queue

These may exist as:

concepts
specifications
future interface ideas
future structured-workflow candidates

They must not be treated as:

active routing systems
automatic production systems
autonomous task systems
current operational dependencies

Required checks:

no inactive queue dependency exists
no autonomous routing assumed
no worker assumed
no AI Employee assumed
no Brain Room routing assumed
no automatic M handoff assumed
manual ownership remains clear

Decision:

Stop Conditions

Stop pack progression when:

offer status is unclear
offer status does not permit current work
pack objective is unclear
audience is unclear
funnel role is unclear
pack is unnecessary
existing content already satisfies the need
source material is insufficient
evidence is insufficient
offer details conflict
claims are unsupported
disclosures are missing
required assets are incomplete
central asset is incomplete
cross-asset contradictions remain
specialist review is incomplete
Affiliate Brain review is incomplete where required
Ads Brain review is incomplete where required
human approval is missing
final version is unclear
destination is unclear
publishing preparation is incomplete
publication sequence is unclear
partial release is not explicitly approved
high-risk error remains unresolved

Final Pack Decision

Pack Name:

Offer:

Pack Model:

Pack Version:

Review Date:

Decision Owner:

Final Decision:

Available decisions:

Pack Approved
Pack Approved With Minor Actions
Selected Assets Approved
Partially Publishing-Ready
Publishing-Ready
Delivery-Ready
Hold For Offer Status
Hold For Research
Hold For Sources
Hold For Evidence
Hold For Missing Assets
Hold For Revision
Hold For Specialist Review
Hold For Affiliate Brain Review
Hold For Ads Brain Review
Hold For Human Approval
Hold For Publishing Preparation
Retirement Approved
Rejected
Cancelled

Approved Assets:

Held Assets:

Rejected Assets:

Outstanding Actions:

Publishing Owner:

Measurement Owner:

Lifecycle Owner:

Next Review Date:

Minimum Pack Checklist

Use this only for simple Minimum Packs.

Confirm:

pack is genuinely required
request authority is clear
offer status is clear
objective is clear
audience is clear
funnel role is clear
pack model is appropriate
existing content has been checked
required assets are defined
required assets are complete
shared sources are confirmed
evidence is sufficient
offer details are consistent
claims are controlled
disclosures are complete
message match is confirmed
editing is complete
cross-asset editing is complete
specialist review is complete where required
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
publication sequence is confirmed
measurement path is defined
lifecycle owner is defined

The Minimum Pack Checklist must not be used for:

complex packs
high-risk packs
full multi-channel packs
sensitive claims
unclear offer status
incomplete sources
incomplete evidence
packs requiring extensive specialist review

Relationship To Content Brain Affiliate Product Content Pack Framework

The Affiliate Product Content Pack Framework defines:

pack principles
pack models
planning
production
review
approval
publishing preparation
measurement
lifecycle management

This Checklist verifies whether a pack has followed that Framework.

Framework = operating method

Checklist = practical verification

Relationship To Content Brain Affiliate Funnel Support Map

The Affiliate Funnel Support Map defines how Content Brain supports affiliate pathways.

This Checklist confirms whether a specific content pack is complete and ready within that pathway.

Relationship To Content Brain Content Production System Framework

The Content Production System Framework defines the general production process.

This Checklist verifies whether pack and asset production has completed the required stages.

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 Checklist confirms whether the selected instruction level sufficiently defined the work.

Relationship To Content Brain Publishing Readiness Checklist

The Publishing Readiness Checklist controls universal asset readiness.

This Checklist adds affiliate pack-level checks for:

offer status
funnel role
shared offer details
shared claims
shared disclosures
cross-asset editing
pack completeness
Affiliate Brain review
Ads Brain review
pack measurement
pack lifecycle

Relationship To Affiliate Brain

Affiliate Brain controls:

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

Content Brain controls:

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

Relationship To Ads Brain

Ads Brain controls:

platform selection
campaign structure
targeting
budgets
bidding
testing deployment
optimisation
scaling

Content Brain produces authorised advertising content.

Relationship To Research Brain

Research Brain controls broad research authority.

Content Brain uses approved research to produce pack assets.

Relationship To Compliance Brain

Compliance Brain controls specialist claim and disclosure interpretation.

This Checklist does not replace Compliance Brain review.

Relationship To Experimentation Brain

Experimentation Brain controls test validity and interpretation.

The Checklist verifies that required variants and labels exist.

It does not determine whether a test is valid.

Relationship To Data Brain

Data Brain controls measurement integrity.

Content Brain uses approved signals for content lifecycle decisions.

Relationship To MCR

MCR remains the source of truth.

This page defines the master affiliate product content-pack verification standard.

Operational versions must not replace MCR authority.

Relationship To mwmscontentbrain.site

A simplified operational checklist may later support:

pack qualification
offer status
pack objective
audience
funnel role
asset selection
sources
evidence
claims
disclosures
production status
cross-asset editing
specialist review
Affiliate Brain review
Ads Brain review
human approval
publishing preparation
final readiness
measurement
lifecycle actions

No operational interface build is authorised by this Checklist.

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 Verification Workspace

Future Plugin Or UI: Possible Affiliate Content Pack Checklist Module

No plugin or UI implementation is authorised by this Checklist.

Relationship To Content Brain Page Registry

This page should be listed as:

Page Title: Content Brain Affiliate Product Content Pack Checklist

Document Type: Checklist

Parent Page: Content Brain

Status: Active

Version: v1.1

Classification: Simplify Before Copy

Source Of Truth: MCR

Current Manual Operating Boundary

The affiliate content-pack checklist remains manually controlled.

Current restrictions:

no automatic pack qualification
no unrestricted pack generator
no autonomous asset production
no autonomous editing
no autonomous specialist approval
no autonomous Affiliate Brain approval
no autonomous Ads Brain approval
no autonomous human approval
no autonomous publishing
no autonomous social posting
no autonomous social scheduling
no autonomous newsletter sending
no autonomous email deployment
no autonomous advertising deployment
no autonomous campaign changes
no active content queues
no Brain Room routing
no automatic M handoff
no worker activation
no AI Employee activation
no interference with M’s Research Brain work

The presence of this Checklist does not authorise automation.

Future Interface Direction

A future checklist interface may support:

pack details
offer status
request authority
pack objective
audience
funnel role
pack model
existing-content check
asset selection
shared sources
shared evidence
offer details
claims
disclosures
message match
production order
asset completion
editing
cross-asset editing
specialist review
Affiliate Brain review
Ads Brain review
human approval
final versions
publishing preparation
pack readiness
partial release
publication status
measurement
refresh
correction
merge
repurposing
retirement
blockers
next action

Manual use must prove the required fields, decisions and statuses before implementation.

Drift Protection

The system must prevent:

unnecessary packs
packs without clear authority
packs without clear offer status
packs without a defined objective
packs without a defined audience
packs without a funnel role
pack-size inflation
duplicate asset creation
outlines being treated as complete assets
content seeds being treated as complete assets
asset lists being treated as complete packs
incomplete assets being hidden
inconsistent offer details
inconsistent prices
inconsistent refund or rebill terms
inconsistent mechanisms
inconsistent claims
unsupported claims
invented evidence
fake testimonials
fabricated firsthand experience
false urgency
false scarcity
unsupported guarantees
missing disclosures
deceptive advertorial presentation
broken message match
broken asset relationships
missing central destinations
advertising assets bypassing Ads Brain
affiliate decisions bypassing Affiliate Brain
broad research bypassing Research Brain
specialist review bypassing Compliance Brain
individual editing being mistaken for cross-asset editing
approval being mistaken for Publishing-Ready
Publishing-Ready being mistaken for Published
Delivery-Ready being mistaken for Delivered
partial release without explicit approval
the wrong version being published
assets being retired without traffic, link and campaign review
queues being treated as active systems
content records becoming separate WordPress pages
operational pages becoming Canon
premature plugin or UI development
autonomous publishing
autonomous campaign changes
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 Checklist exists to verify that approved affiliate content packs become complete coordinated content systems.

It connects practical verification across:

offer status
pack purpose
audience
funnel role
asset selection
source control
evidence control
offer-detail consistency
claims
disclosures
message match
production
editing
cross-asset consistency
specialist review
Affiliate Brain review
Ads Brain review
human approval
publishing preparation
publication sequence
measurement
lifecycle management

The Checklist must support:

Minimum Packs
Standard Packs
Full Packs
Custom Packs
website packs
article packs
video packs
advertising packs
email packs
newsletter packs
social packs
refresh packs
correction packs
repurposing packs
retirement packs

It must support current manual operation and later controlled implementation.

Future interfaces, workers or AI Employees must operate beneath this Checklist.

They must not narrow or bypass it.

Final Rule

An affiliate product content pack must not move into live use unless:

the pack is genuinely required
request authority is clear
offer status is clear
pack objective is clear
audience is clear
funnel role is clear
the correct pack model is selected
existing content has been checked
required assets are selected
required assets are fully produced
shared sources are confirmed
evidence is sufficient
offer details are consistent
claims are controlled
disclosures are complete
message match is confirmed
individual editing is complete
cross-asset editing is complete
specialist review is complete where required
Affiliate Brain review is complete where required
Ads Brain review is complete where required
human approval is recorded
final versions are confirmed
publishing preparation is complete
destinations are confirmed
publication sequence is confirmed
measurement ownership is clear
lifecycle ownership is clear

A pack plan is not a completed pack.

A brief is not a completed pack.

An outline is not a completed asset.

A draft is not an approved asset.

Approval is not Publishing-Ready.

Publishing-Ready is not Published.

Delivery-Ready is not Delivered.

Affiliate Brain controls affiliate decisions.

Ads Brain controls paid campaign decisions.

Content Brain controls 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 premature automation.

No active queue dependency.

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 Checklist.

Expanded the Checklist into the complete pack qualification, planning, production, review, approval, publishing-readiness, measurement and lifecycle verification system.

Added checks for:

whether a pack is genuinely required
originating authority
offer status
pack objective
audience
funnel role
Minimum, Standard, Full and Custom Pack selection
existing content
shared sources
shared evidence
shared offer details
shared claims
shared disclosures
shared messaging
message match
asset selection
central asset
pack architecture
production-instruction level
production order
complete asset production
individual asset quality
cross-asset editing
internal linking
advertising assets
newsletters and email sequences
video and scripts
social content
reviews and comparisons
advertorial and pre-sell content
specialist review
Affiliate Brain review
Ads Brain review
human approval
final-version control
publishing preparation
pack-level readiness
partial-pack release
human-controlled publication
publication sequence
asset-level measurement
pack-level measurement
refresh
correction
merge
repurposing
retirement
inactive queue boundaries
stop conditions
final pack decision

Removed operational dependence on:

Content Opportunity Queue
Content Production Queue
Content Refresh Queue
Content Repurposing Queue

Clarified that these remain future specifications only and are not active systems.

Clarified that:

content seeds do not count as completed assets
outlines do not count as completed assets
asset lists do not count as completed packs
individual editing does not replace cross-asset editing
approval does not equal Publishing-Ready
Publishing-Ready does not equal Published
partial release requires explicit human approval
final publication and deployment remain human controlled

Aligned this Checklist 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 Affiliate Product Content Pack Framework v1.1
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 Checklist.

Defined the original checks for:

offer status
research evidence
audience
funnel role
pack size
required assets
YouTube support
VEO3 support
compliance risk
approval ownership
internal linking
repurposing
handoff
performance signals
stop conditions
future queue and plugin use

Change Impact Declaration

Pages Created:

Content Brain Affiliate Product Content Pack Checklist replacement page

Pages Updated:

None during replacement creation

Pages To Move To Trash After Validation:

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

Pages Deprecated:

Previous Content Brain Affiliate Product Content Pack Checklist 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 Checklist v1.1.

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

Canon Version Update Required:

Automation Status Change:

Plugin Or UI Status Change:

Queue Status Change:

No active queues authorised

Worker Status Change:

AI Employee Status Change:

M Handoff Required:

Research Brain Impact:

None

END CONTENT BRAIN AFFILIATE PRODUCT CONTENT PACK CHECKLIST v1.1