Brain Name: Content Brain
Document Type: Checklist
Status: Draft
Version: v1.0
Authority: Content Brain under HeadOffice governance
Applies To: Affiliate product content pack planning, approved or review-ready affiliate offers, content opportunity qualification, content production readiness, pre-sell content, YouTube support, VEO3 pre-video support, email support, social support, internal linking, repurposing, compliance review, research validation, and future mwmscontentbrain.site operational use
Parent: Content Brain
Last Reviewed: 2026-05-24

Content Brain Affiliate Product Content Pack Checklist

Purpose

The Content Brain Affiliate Product Content Pack Checklist provides the practical working checklist for planning, reviewing, approving, and handing off affiliate product content packs.

This checklist exists to help Content Brain operators confirm that affiliate content is not created randomly, prematurely, or without the correct review path.

It turns the Content Brain Affiliate Product Content Pack Framework into an operational checklist.

The purpose is to confirm:

offer status is known

Research Brain evidence exists or is requested

target audience is clear

funnel role is clear

content pack size is selected

required assets are selected

compliance risks are flagged

approval owner is known

internal linking plan is included

repurposing plan is included

feedback signal is defined

handoff destination is clear

Content Brain does not approve affiliate products.

Content Brain does not approve affiliate claims.

Content Brain uses this checklist to make sure content pack work is ready, safe, structured, and traceable.

Scope

This checklist applies to:

affiliate product content packs

approved affiliate offers

review-ready affiliate offers

affiliate product education content

pre-sell content

product support content

comparison content

FAQ content

objection-handling content

review support content

YouTube scripts

VEO3 pre-video scripts

YouTube descriptions

email follow-up drafts

social post sets

internal linking plans

repurposing plans

affiliate content handoff

affiliate content refresh planning

affiliate content performance review

future mwmscontentbrain.site operational use

This checklist does not govern:

Affiliate Brain offer approval

Research Brain evidence verdicts

Ads Brain campaign setup

Ads Brain campaign optimisation

Experimentation Brain test verdicts

Finance Brain budget decisions

Compliance Brain final compliance approval

Data Brain signal reliability judgement

live publishing authority

plugin or UI development

Supabase implementation

M’s active build areas

Those remain governed by the relevant Brain, protocol, standard, or implementation layer.

Core Rule

No affiliate product content pack should move into production unless the offer status, audience, purpose, review path, and approval owner are clear.

If these are not clear, the pack should remain in:

Opportunity Queue

Research Needed

Review Needed

Blocked

Parked

Content Brain should not create affiliate content just because an offer exists.

Affiliate content must support a clear business purpose and must remain inside the correct Brain authority boundaries.

Checklist Use Rule

Use this checklist before:

creating a full affiliate product content pack

creating a minimum affiliate product content pack

creating a pre-sell article

creating product support content

creating review support content

creating comparison content

creating FAQ content

creating objection-handling content

creating YouTube scripts

creating VEO3 pre-video scripts

creating email follow-up drafts

creating social post sets

handing affiliate content to another Brain or operator

publishing affiliate support content

repurposing affiliate content

refreshing affiliate content

This checklist may be used manually first.

Do not build plugin or UI from this checklist until repeated manual use proves the need.

Section 1: Offer Status Check

Confirm the affiliate offer status before any content pack work begins.

Checklist:

Offer name is known.

Affiliate network is known.

Vendor or offer source is known.

Affiliate Brain status is known.

Offer is approved, review-ready, or intentionally parked.

Offer is not rejected.

Offer is not unknown.

Offer risk level is noted.

Offer category is known.

Traffic source context is known where relevant.

Product claim sensitivity is noted.

Approval owner is identified.

If offer status is unknown, stop and route to Affiliate Brain or mark the pack as Blocked.

Section 2: Research Evidence Check

Confirm that the research base is strong enough for content planning.

Checklist:

Research Brain evidence exists or has been requested.

Product category research exists.

Audience problem research exists.

Competitor context is available or requested.

Search demand evidence is available or requested.

Vendor claims have been reviewed or flagged.

Customer questions are known or requested.

Common objections are known or requested.

Proof requirements are identified.

Missing evidence is listed.

Unsupported claims are flagged.

Research gaps are assigned to a next owner.

If evidence is missing, do not invent proof.

Mark the pack as Research Needed.

Section 3: Audience And Funnel Role Check

Confirm who the content is for and where it fits in the buyer journey.

Checklist:

Target audience is defined.

Audience awareness stage is defined.

Main reader problem is defined.

Reader intent is defined.

Affiliate funnel role is defined.

Traffic source context is known.

Content destination is known.

Next step after content is clear.

CTA type is clear.

Reader objections are identified.

Reader trust concerns are identified.

Content purpose is clearly stated.

If audience or funnel role is unclear, do not move to drafting.

Section 4: Content Pack Size Check

Choose the correct pack size.

Checklist:

Pack size selected.

Pack size matches product priority.

Pack size matches available evidence.

Pack size matches offer approval status.

Pack size matches compliance risk level.

Pack size matches expected traffic source.

Pack size does not overbuild a weak opportunity.

Pack size does not under-support a high-priority opportunity.

Recommended pack sizes:

Small Pack

Medium Pack

Full Pack

If uncertain, start with a Small Pack.

Section 5: Small Pack Checklist

Use a Small Pack for early review, lower-risk support, or controlled first-stage content planning.

Small Pack should include:

Product Support Page Outline

Pre-Sell Article Outline

FAQ Or Objection Content

YouTube Description

Compliance Risk Note

Research Requirement Note

Feedback Signal To Watch

Optional additions:

Internal Linking Plan

Short Email Draft

Social Post Seeds

A Small Pack is suitable when:

the offer is still early

research is incomplete but usable

the product is not yet high priority

content support is needed but not full production

Section 6: Medium Pack Checklist

Use a Medium Pack for active but controlled product support.

Medium Pack should include:

Product Support Page

Pre-Sell Article

FAQ Content

Objection-Handling Content

YouTube Script

YouTube Description

Email Follow-Up Draft

Internal Linking Plan

Compliance Risk Notes

Research Requirement Notes

Performance Signal Plan

Optional additions:

Social Post Set

VEO3 Pre-Video Script

Comparison Content

Trust Support Notes

A Medium Pack is suitable when:

the offer is approved or strongly review-ready

there is enough research to support content

the product may support traffic or funnel testing

the content has clear business value

Section 7: Full Pack Checklist

Use a Full Pack only for high-priority products, approved campaigns, or serious affiliate support.

Full Pack may include:

Product Support Page

Problem-Aware Article

Pre-Sell Article

Comparison Article

Review Support Content

FAQ Content

Objection-Handling Content

Trust Support Notes

YouTube Script

VEO3 Pre-Video Script

YouTube Description

Email Follow-Up Draft

Social Post Set

Short-Form Script Seeds

Internal Linking Plan

Repurposing Plan

Refresh Plan

Compliance Risk Notes

Research Evidence Summary

Performance Signal Plan

A Full Pack is suitable when:

the offer is strategically important

Affiliate Brain supports the opportunity

Research Brain evidence is strong enough

Compliance risk is understood

Finance Brain does not object to resource allocation

HeadOffice or operator priority is clear

Do not create a Full Pack for weak, unapproved, or unclear offers.

Section 8: Required Asset Selection Check

Confirm which assets are actually needed.

Checklist:

Product Support Page needed.

Pre-Sell Article needed.

Problem-Aware Article needed.

Comparison Article needed.

Review Support Content needed.

FAQ Content needed.

Objection-Handling Content needed.

Trust Support Notes needed.

YouTube Script needed.

VEO3 Pre-Video Script needed.

YouTube Description needed.

Email Follow-Up Draft needed.

Social Post Set needed.

Short-Form Script Seeds needed.

Internal Linking Plan needed.

Repurposing Plan needed.

Refresh Plan needed.

Compliance Risk Notes needed.

Research Requirement Notes needed.

Performance Signal Plan needed.

Only select assets that have a clear use case.

Do not create assets just to make the pack look complete.

Section 9: Product Support Page Check

Before creating or approving a Product Support Page, confirm:

problem is clearly explained

product category is clearly explained

reader relevance is clear

next step is clear

claims are cautious

proof gaps are noted

trust concerns are addressed

affiliate disclosure needs are considered

content does not sound like vendor hype

Content Brain does not invent product results.

Section 10: Pre-Sell Article Check

Before creating or approving a Pre-Sell Article, confirm:

reader problem is clear

education comes before recommendation

curiosity is created without hype

transition to next step is logical

objections are addressed

trust risks are considered

claims are not exaggerated

CTA is soft and appropriate

offer status is known

A pre-sell article should prepare the reader, not pressure the reader.

Section 11: FAQ And Objection Content Check

Before creating or approving FAQ or objection content, confirm:

questions are based on real likely concerns

answers are clear

answers do not invent facts

risk-sensitive answers are flagged

refund or guarantee statements are confirmed before use

safety or suitability questions are reviewed where relevant

affiliate recommendation language is cautious

reader confusion is reduced

FAQ content should clarify, not overpromise.

Section 12: Comparison Or Review Support Check

Before creating or approving comparison or review support content, confirm:

comparison basis is fair

claims are supported or flagged

no fake personal experience is used

no fake testimonials are used

limitations are included where needed

decision criteria are useful

reader trust is protected

vendor claims are not repeated as fact without review

Review-style content must not pretend to be firsthand experience unless firsthand evidence exists.

Section 13: YouTube Script Check

Before creating or approving a YouTube script, confirm:

hook is clear

problem framing is useful

script aligns with offer status

claims are safe

CTA is appropriate

traffic source context is known

script does not overpromise

script does not mention unapproved price claims

script supports the viewer journey

review path is clear

If the script supports paid traffic, extra claim review may be required.

Section 14: VEO3 Pre-Video Script Check

Before creating or approving a VEO3 pre-video script, confirm:

time-coded storyboard format is used

headline is included

narration is short and punchy

on-screen text is included

visual direction is included

VEO3-ready image prompts are included

no hard CTA is placed inside the pre-video

no unsupported product claims are included

visuals do not misrepresent the product

script rolls naturally into the main video

VEO3 pre-videos should act as headline and hook swap-out intros.

They should not become full sales videos.

Section 15: YouTube Description Check

Before creating or approving a YouTube description, confirm:

video topic is accurately summarised

viewer benefit is clear

affiliate disclosure requirement is considered

CTA is soft and appropriate

keywords are natural

description matches the video

description matches the landing path

description does not overclaim

link placement is clear

YouTube descriptions should support discovery and next step clarity.

Section 16: Email Follow-Up Check

Before creating or approving email follow-up content, confirm:

email purpose is clear

reader stage is clear

subject line is not misleading

problem reminder is useful

education is included

objection handling is gentle

CTA is clear

urgency is not fabricated

claims are safe

affiliate disclosure needs are considered

Email should nurture and clarify, not pressure.

Section 17: Social Post Set Check

Before creating or approving social content, confirm:

posts preserve the original message

claims are not strengthened

content is suitable for the platform

CTA is appropriate

hook is not misleading

compliance risk is considered

short-form snippets are not exaggerated

content does not imply unsupported results

Social content should not create extra claim risk during repurposing.

Section 18: Internal Linking Check

Before approving the pack, confirm:

pillar page links identified

supporting article links identified

FAQ links identified

trust page links identified

comparison links identified

YouTube support links identified where relevant

Section 19: Repurposing Check

Before approving repurposing, confirm:

source asset is approved

message is stable

claim risk is understood

new format preserves meaning

destination is clear

CTA is appropriate for the format

no stronger claim is introduced

approval owner is known

Repurposed affiliate content must not strengthen or distort claims.

Section 20: Compliance Risk Check

Before approving affiliate pack content, confirm whether content includes:

health claims

finance claims

income claims

legal claims

product performance claims

testimonials

guarantees

scarcity

urgency

comparisons

before and after claims

risk-sensitive topics

affiliate recommendations

Checklist:

risk level assigned

sensitive claims identified

claims needing review are marked

Compliance Brain review required where needed

human approval required where needed

unsafe language removed or flagged

Content Brain does not approve compliance-sensitive claims.

Section 21: Research Requirement Check

Before approving the pack, confirm:

missing vendor details are listed

missing offer details are listed

missing proof is listed

missing comparison data is listed

missing customer question data is listed

missing search demand data is listed

missing refund or guarantee confirmation is listed where relevant

research owner is assigned

research next action is clear

Do not publish unsupported claims because research is incomplete.

Section 22: Approval Owner Check

Before the pack moves forward, confirm:

request owner is known

production owner is known

review owner is known

approval owner is known

handoff owner is known

next owner is known

If no approval owner exists, the pack cannot be approved.

Section 23: Handoff Check

Before handoff, confirm the handoff note includes:

product name

pack size

included assets

source offer

offer status

approval status

risk level

review notes

publishing destination

traffic source context

internal links needed

feedback signals to watch

next owner

handoff date

A pack without a handoff note creates rework and risk.

Section 24: Performance Signal Check

Before closing or publishing the pack, define signals to watch.

Possible signals:

VSL clicks

affiliate link clicks

YouTube description clicks

email clicks

organic traffic

ranking movement

scroll depth

time on page

internal link clicks

conversion assist

FAQ engagement

social engagement

content refresh need

repurposing opportunity

Checklist:

signal selected

measurement source known

review date set

feedback destination Brain selected

Data Brain needed if measurement is unclear

Experimentation Brain needed if learning interpretation matters

Content Brain should not over-interpret weak data.

Section 25: Final Readiness Checklist

Before the pack is marked ready for approval or handoff, confirm:

offer status is known

research basis exists or gaps are flagged

audience is clear

funnel role is clear

pack size is selected

required assets are selected

content purpose is clear

content does not invent proof

content does not fake experience

claims are safe or flagged

compliance risk is reviewed or escalated

approval owner is known

internal linking plan exists

repurposing plan exists where needed

handoff destination is clear

feedback signal is defined

next owner is clear

If any of these are missing, do not mark the pack ready.

Section 26: Stop Conditions

Stop the content pack process if:

offer status is unknown

offer is rejected

research is missing

audience is unclear

funnel role is unclear

approval owner is missing

compliance risk is high and unreviewed

claims are unsupported

content requires fake experience

content would mislead the reader

finance priority is unclear for a resource-heavy pack

handoff destination is unknown

the pack has no business purpose

Stop conditions should move the pack to:

Blocked

Research Needed

Review Needed

Parked

Rejected

Section 27: Minimum Manual Tracking Fields

For manual use, track:

Product Name

Affiliate Network

Offer Status

Pack Size

Target Audience

Funnel Role

Traffic Source Context

Research Status

Compliance Risk

Approval Owner

Selected Assets

Internal Linking Needed

Repurposing Needed

Handoff Destination

Performance Signal

Status

Next Owner

Next Action

This is enough to use the checklist without building a plugin.

Section 28: Future Plugin Or UI Candidate

This checklist may later support:

Affiliate Product Content Pack Checklist UI

Affiliate Product Content Pack Generator

Pack Brief Form

Pack Asset Selector

Pack Approval Tracker

Pack Risk Review Panel

Pack Handoff Panel

Pack Performance Review Panel

These should not be built yet.

Manual workflow must prove the need first.

Relationship To Content Brain Affiliate Product Content Pack Framework

The Content Brain Affiliate Product Content Pack Framework defines the full system.

This checklist provides the operator-ready version.

Framework = structure and rules

Checklist = practical execution aid

Both should remain aligned.

Relationship To Content Brain Workflow Map

The Workflow Map defines how signals move through opportunity intake, production, refresh, repurposing, and feedback.

This checklist is used when an affiliate product content pack opportunity is approved or ready for review.

Workflow Map = movement

Checklist = readiness and quality control

Relationship To Content Brain Content Opportunity Queue Specification

Affiliate product content pack ideas should usually enter through the Content Opportunity Queue first.

This checklist should be used after the opportunity is ready for review, production, or handoff.

Opportunity Queue = should this become content?

Checklist = is this pack ready and safe?

Relationship To Content Brain Content Production Queue Specification

Approved pack assets may move into the Content Production Queue.

The Production Queue tracks production movement.

This checklist confirms readiness before production, approval, or handoff.

Relationship To Content Brain Copy Map

This page should be added to the Content Brain Copy Map as:

Page Title: Content Brain Affiliate Product Content Pack Checklist

Classification: Copy To Content Brain

Reason: Operational checklist for building, reviewing, approving, and handing off affiliate product content packs.

Source Of Truth: MCR

Future Destination: mwmscontentbrain.site

Future Use: Affiliate product content pack readiness checklist

Plugin Or UI Later: Possible Affiliate Product Content Pack Checklist UI

Relationship To Content Brain Page Registry

This page should be added to the Content Brain Page Registry as:

Page Title: Content Brain Affiliate Product Content Pack Checklist

Document Type: Checklist

Parent Page: Content Brain

Status: Draft

Migration Classification: Copy To Content Brain

Plugin Or UI Candidate: Possible Affiliate Product Content Pack Checklist UI Later

Notes: Practical checklist for planning, reviewing, approving, and handing off affiliate product content packs, including offer status, research evidence, audience, funnel role, pack size, required assets, compliance risk, approval owner, internal linking, repurposing, feedback signals, and handoff readiness.

Relationship To Other MWMS Standards

This checklist must align with:

Content Brain Affiliate Product Content Pack Framework

Content Brain Operating Model

Content Brain Workflow Map

Content Brain Content Opportunity Queue Specification

Content Brain Content Production Queue Specification

Content Brain Content Refresh Queue Specification

Content Brain Repurposing Queue Specification

Content Brain Content Operations Dashboard Specification

Content Brain Affiliate Funnel Support Map

Content Brain Content Brief Template

Content Brain SEO Content Brief Standard

Content Brain Publishing Readiness Checklist

Content Brain Copy Map

Content Brain Page Registry

Content Brain AI Content Quality Governance Framework

Content Brain Information Gain Framework

Content Brain E E A T Content Trust Framework

MWMS MCR To Brain Copy Rule

MWMS Brain Interaction Map

MWMS Brain To Brain Request Protocol

MWMS Page Naming Standard

MWMS Document Structure Standard

MWMS AI Output Standard Full File Delivery Rule

MWMS Active Brain Status Board

Drift Protection

The system must prevent:

affiliate content being created without offer status

affiliate content being created without research basis

affiliate content being created without audience clarity

affiliate content being created without funnel role

affiliate content being created without approval owner

affiliate content packs becoming random bundles of assets

Content Brain approving offers

Content Brain approving compliance-sensitive claims

Content Brain deciding ad strategy

Content Brain deciding test validity

Content Brain deciding capital allocation

Content Brain inventing proof

Content Brain faking product experience

Content Brain strengthening claims during repurposing

Content Brain publishing without approval

content packs being built before workflow need is clear

plugin or UI work starting before manual use proves the need

Content Brain interfering with M’s active build areas

Architectural Intent

The Content Brain Affiliate Product Content Pack Checklist exists to make affiliate content pack execution practical, repeatable, and safe.

Its long-term role is to help MWMS produce affiliate support content with structure, review discipline, and handoff clarity.

The checklist ensures that affiliate product content packs are:

source-aware

research-aware

audience-aware

funnel-aware

approval-aware

risk-aware

handoff-ready

repurposing-ready

measurable

connected to signal feedback

This checklist should become one of the first practical operational pages copied to mwmscontentbrain.site when Content Brain migration begins.

Final Rule

Do not create an affiliate product content pack unless:

offer status is known

research basis exists or gaps are flagged

audience is clear

funnel role is clear

approval owner is known

risk level is understood

handoff destination is clear

feedback signal is defined

If those are missing, the pack should remain in Opportunity Queue, Research Needed, Review Needed, Parked, or Blocked status.

Change Log

Version: v1.0
Date: 2026-05-24
Author: HeadOffice
Change: Initial creation of Content Brain Affiliate Product Content Pack Checklist, providing an operator-ready checklist for planning, reviewing, approving, and handing off affiliate product content packs. Defines offer status checks, research checks, audience and funnel checks, pack size checks, asset checks, YouTube and VEO3 checks, compliance checks, approval checks, handoff checks, performance signal checks, stop conditions, manual tracking fields, future plugin or UI candidates, and relationships to the Affiliate Product Content Pack Framework, Workflow Map, Opportunity Queue, Production Queue, Page Registry, and Copy Map.

Change Impact Declaration

Pages Created:
Content Brain Affiliate Product Content Pack Checklist

Pages Updated:
None

Pages Deprecated:
None

Registries Requiring Update:
Content Brain Page Registry
Content Brain Copy Map

Canon Version Update Required:
No

Change Log Entry Required:
No

END CONTENT BRAIN AFFILIATE PRODUCT CONTENT PACK CHECKLIST v1.0