Brain Name: Content Brain
Document Type: Protocol
Status: Active
Version: v1.1
Authority: Content Brain under HeadOffice governance
Applies To: Content publishing readiness, content review, content handoff, content quality control, affiliate support content, SEO content, trust content, mwmscontentbrain.site operational use, and future publishing readiness checklist UI planning
Parent: Content Brain
Last Reviewed: 2026-05-08
Content Brain Publishing Readiness Checklist
Operational Copy Notice
This page is an operational copy used on mwmscontentbrain.site.
MCR remains the source of truth.
If this page conflicts with the MCR version, the MCR version overrides it.
This protects source-of-truth discipline.
Purpose
The Content Brain Publishing Readiness Checklist defines the required review process before any Content Brain asset is published, handed off, or used inside the MWMS ecosystem.
This checklist exists to prevent content from going live before it has:
a clear purpose
defined audience
approved source
correct structure
quality review
accuracy review
trust review
risk review
clear destination
approval owner
feedback path
Content Brain should not publish or hand off content simply because a draft exists.
A content asset is only ready when it is clear, useful, aligned, reviewed, and connected to a system purpose.
Scope
This checklist applies to:
SEO articles
authority articles
affiliate support content
pre-sell content
comparison content
review support content
FAQ content
trust support content
YouTube descriptions
email drafts
newsletter content
social repurposing content
topic cluster pages
pillar pages
content refreshes
internal linking plans
content handoff notes
repurposed content assets
sales support assets
conversion support assets
This checklist governs readiness before publication, handoff, or operational use.
It does not govern:
offer approval
campaign approval
ad launch approval
capital approval
final compliance interpretation
statistical validation
Supabase implementation
plugin implementation
Brain to Brain routing automation
HeadOffice reporting build work
M’s active development areas
Those remain governed by the relevant Brain, protocol, standard, or implementation layer.
Core Principle
No content should move from draft to publication or handoff unless it passes a readiness check.
Publishing readiness means the content has:
a clear source
a clear purpose
a defined audience
a known request
a correct content type
a completed quality review
a trust and risk review
a destination
an owner
a feedback path
If these elements are missing, the content should stay in review.
Governance Role
This protocol protects Content Brain from becoming an uncontrolled content production system.
It ensures Content Brain outputs remain:
purposeful
reviewable
traceable
useful
safe
aligned with MWMS authority boundaries
Content Brain may prepare content, but it must not publish, alter live funnel pages, or push content into active campaigns without appropriate approval.
Content Brain must not use this checklist to bypass Affiliate Brain, Compliance Brain, Conversion Brain, Ads Brain, Finance Brain, Data Brain, Experimentation Brain, or HeadOffice authority.
Relationship To MCR
MCR remains the source of truth.
The MCR version of this checklist defines the structural readiness standard.
This mwmscontentbrain.site version is an operational copy for daily use.
The Brain site version does not replace the MCR source.
If the MCR version changes, this operational copy should be reviewed and updated deliberately.
Relationship To mwmscontentbrain.site
This checklist is copied to mwmscontentbrain.site because it is operationally useful.
Future uses may include:
publishing readiness page
content approval checklist
content handoff checklist
content QA screen
content production queue checklist
refresh approval checklist
affiliate content review checklist
The page may later become a plugin or UI checklist if repeated use proves the need.
Manual workflow must prove the need before plugin or UI development begins.
MCR To Brain Classification
Destination: Copy To Content Brain
Reason: Operational use
Source Of Truth: MCR
Future Use: Publishing readiness checklist inside mwmscontentbrain.site
Future Plugin Or UI: Possible checklist module later
This operational copy follows the Content Brain Copy Map classification.
Readiness Stage 1: Source Check
Before review begins, confirm where the content request came from.
Required checks:
Source Brain identified
Requesting person or system identified
Request purpose recorded
Related offer identified where relevant
Related campaign identified where relevant
Related research signal identified where relevant
Related newsletter signal identified where relevant
Related content refresh trigger identified where relevant
Pass condition:
The content has a clear source and reason for existing.
Fail condition:
The content was created randomly, without a request source, or without a defined system purpose.
If failed, return to request classification.
Readiness Stage 2: Purpose Check
Every content asset must have a clear purpose.
Required checks:
Content purpose defined
Business role defined
Audience problem defined
Reader outcome defined
Next step defined where relevant
Funnel role defined where relevant
SEO role defined where relevant
Authority-building role defined where relevant
Pass condition:
The content has a clear job to do.
Fail condition:
The content exists only because the topic is interesting or because content volume is desired.
If failed, return to the brief stage.
Readiness Stage 3: Audience Check
The content must be written for a clear audience.
Required checks:
Audience segment defined
Awareness stage defined
Intent defined
Pain point or goal defined
Reader knowledge level understood
Reader objections considered where relevant
Reader trust level considered where relevant
Buyer persona considered where relevant
Primary perceived barrier considered where relevant
Pass condition:
The content clearly speaks to a known audience and intent.
Fail condition:
The content feels generic, unfocused, or written for everyone.
If failed, revise the brief or content angle.
Readiness Stage 4: Content Type Check
The content type must match the purpose.
Common content types:
SEO article
pillar page
topic cluster article
pre-sell article
comparison article
review support content
FAQ content
authority page
trust support page
YouTube description
email draft
social content set
refresh update
internal linking plan
repurposing asset
sales support asset
conversion support asset
Required checks:
Correct content type selected
Content structure matches the type
Audience expectation matches the type
CTA or next step matches the type
Review depth matches the risk level
Pass condition:
The content format supports the purpose.
Fail condition:
The content type does not match the reader intent or business use.
If failed, reclassify the asset.
Readiness Stage 5: Brief Alignment Check
The content should match the approved brief.
Required checks:
Working title aligned
Objective followed
Audience followed
Intent followed
Required sections included
Key questions answered
Objections addressed where required
Trust signals included where required
Internal links considered
CTA type followed
Compliance sensitivity respected
Pass condition:
The draft follows the brief.
Fail condition:
The draft drifts away from the approved purpose or invents new direction.
If failed, revise the draft or update the brief deliberately.
Readiness Stage 6: Quality Check
The content must meet the Content Brain quality bar.
Required checks:
Clear
Specific
Useful
Readable
Well structured
Non-generic
Not thin
Not repetitive
Not overlong without purpose
Not vague
Not filled with empty claims
Contains enough information gain
Answers likely reader questions
Has logical flow
Has clean headings where relevant
Pass condition:
The content is useful enough to publish or hand off.
Fail condition:
The content feels like generic AI filler, thin SEO content, or low-value publishing volume.
If failed, improve or reject the asset.
Readiness Stage 7: Accuracy Check
Content must not invent facts, claims, or details.
Required checks:
Offer details checked where relevant
Product details checked where relevant
Claims checked where relevant
Dates checked where relevant
Stats checked where relevant
Source material checked where relevant
No unsupported claims added
No fake testimonials added
No invented proof added
No exaggerated results added
Pass condition:
The content does not rely on unsupported or invented claims.
Fail condition:
The content contains claims that cannot be traced to approved source material.
If failed, revise or send for research verification.
Readiness Stage 8: SEO Check
SEO content must align with reader intent and structure.
Required checks:
Search intent clear
Main topic clear
Page structure logical
Headings useful
Internal linking opportunities identified
Topic cluster fit considered
Information gain present
Duplicate content risk checked
Thin content risk checked
Reader usefulness preserved
Pass condition:
The content is search-aware and human-useful.
Fail condition:
The content is keyword-led but weak for the reader.
If failed, revise using Content Brain SEO Content Brief Standard and Content Brain Information Gain Framework.
Readiness Stage 9: Trust Check
Content must support trust rather than hype.
Required checks:
Tone is balanced
Claims are not exaggerated
Limitations are included where needed
Reader expectations are managed
Proof is not overstated
Affiliate relationship is considered where relevant
Comparison language is fair where relevant
Transparency is present where needed
Risk-sensitive language is controlled
Pass condition:
The content improves credibility.
Fail condition:
The content relies on hype, pressure, vague promises, or weak proof.
If failed, revise or escalate for review.
Readiness Stage 10: Compliance Sensitivity Check
Compliance-sensitive content requires additional review.
High-risk areas:
health claims
pain claims
disease claims
finance claims
income claims
legal claims
safety claims
guarantee language
scarcity
urgency
testimonials
before and after claims
affiliate disclosures
comparative claims
Required checks:
Risk level classified
Sensitive claims identified
Unsupported claims removed
Disclosure need considered
Compliance Brain review requested where needed
Human approval required where needed
Pass condition:
Compliance risk is understood and managed.
Fail condition:
The content contains sensitive claims without review or proof.
If failed, hold publication and escalate.
Readiness Stage 11: Affiliate Content Check
Affiliate support content requires extra discipline.
Required checks:
Offer status clear
Offer source material checked
Funnel stage defined
Audience awareness stage defined
Claim risk checked
Disclosure need considered
Pre-sell role defined
Vendor page relationship understood
No unsupported product claims added
No fake urgency added
No price claims added unless approved
No guarantee claims added unless approved
Pass condition:
The content supports an approved or reviewable affiliate funnel safely.
Fail condition:
The content promotes an unclear or unapproved offer as if it is approved.
If failed, return to Affiliate Brain or hold as exploratory draft only.
Readiness Stage 12: Conversion Support Check
Content that supports conversion must align with the funnel.
Required checks:
Message match checked
CTA type appropriate
Objections addressed
Trust support included
Reader next step clear
No mismatch between ad, content, and offer
No overpromising before vendor page or VSL
No confusion created by content structure
Pass condition:
The content helps the reader move forward without misleading them.
Fail condition:
The content creates mismatch, confusion, or false expectation.
If failed, return to Conversion Brain or revise the content structure.
Readiness Stage 13: Internal Linking Check
Content should connect properly to the wider site where relevant.
Required checks:
Relevant internal links identified
Pillar page link considered
Topic cluster link considered
Support article link considered
Affiliate support page link considered where relevant
No excessive money-page pushing
Links help the reader
Anchor text is natural
Pass condition:
Internal linking improves navigation and topic structure.
Fail condition:
Internal links are missing, forced, or purely manipulative.
If failed, revise linking plan.
Readiness Stage 14: Repurposing Check
If content will be repurposed, confirm meaning is preserved.
Required checks:
Original meaning preserved
Claims not expanded beyond source
Format suits platform
Tone adjusted correctly
CTA adjusted correctly
Compliance risk rechecked
Source asset recorded
Repurposed asset destination defined
Pass condition:
The repurposed asset remains accurate and useful.
Fail condition:
The repurposed version adds unsupported claims or changes meaning.
If failed, revise or hold.
Readiness Stage 15: Publishing Destination Check
Before content is released, the destination must be known.
Possible destinations:
WordPress blog
landing support page
affiliate support page
email platform
YouTube description
social platform
internal knowledge page
sales support asset
content queue
refresh queue
operator handoff
Required checks:
Destination defined
Publishing owner defined
Approval owner defined
Date or timing defined where relevant
Format requirements checked
Live editing permission confirmed where relevant
Pass condition:
The content has a clear destination and owner.
Fail condition:
The content is ready in theory but has no clear place to go.
If failed, hold in ready for approval.
Readiness Stage 16: Feedback Path Check
Every meaningful content asset should produce or support learning.
Required checks:
Performance signal defined
Review timing defined where relevant
Relevant Brain feedback path identified
Possible refresh trigger identified
Possible repurposing trigger identified
Data requirement understood where relevant
Pass condition:
The content has a feedback path.
Fail condition:
The content is published with no plan to learn from it.
If failed, add a feedback note before publishing.
Standard Publishing Readiness Decision
After review, assign one decision.
Decision options:
Approved For Publishing
Approved For Handoff
Approved With Minor Edits
Hold For Revision
Hold For Compliance Review
Hold For Research Verification
Hold For Affiliate Brain Review
Hold For Conversion Brain Review
Hold For Data Brain Review
Rejected
Required Handoff Note
If content is handed off, include:
content title
content type
source request
source Brain
intended use
target destination
approval status
risk level
review notes
internal links needed
feedback signal to watch
next owner
handoff date
Minimum Publishing Readiness Checklist
For fast use, the minimum checklist is:
Source clear
Purpose clear
Audience clear
Content type correct
Brief followed
Quality checked
Accuracy checked
SEO checked where relevant
Trust checked
Compliance risk checked
Affiliate status checked where relevant
Destination clear
Approval owner clear
Feedback path clear
If any item fails, do not publish yet.
Future Plugin Or UI Candidate
This checklist may later become:
checkbox-based publishing readiness screen
content QA panel
approval workflow
content production queue step
content refresh queue step
affiliate content review screen
Content Brain should use this manually before building UI.
Manual workflow must prove the need first.
Relationship To Content Brain Copy Map
This page should be listed in the Content Brain Copy Map as:
Page Title: Content Brain Publishing Readiness Checklist
Destination: Copy To Content Brain
Reason: Operational use
Source Of Truth: MCR
Future Use: Publishing readiness checklist inside mwmscontentbrain.site
Future Plugin Or UI: Possible checklist screen later
Relationship To Content Brain Operating Model
The Content Brain Operating Model defines the responsibilities and boundaries of Content Brain.
This checklist enforces those boundaries before content moves into use.
Operating Model equals role and boundaries.
Publishing Readiness Checklist equals pre-publication control.
Relationship To Content Brain Workflow Map
The Content Brain Workflow Map defines the full content movement from request to feedback.
This checklist governs the readiness stage before publishing or handoff.
Workflow Map equals full movement.
Publishing Readiness Checklist equals approval gate.
Relationship To Content Brain Affiliate Funnel Support Map
Affiliate funnel support content must pass this checklist before use.
For affiliate-related content, extra attention must be given to:
offer status
claim risk
disclosure need
pre-sell role
message match
trust language
conversion support
Relationship To Other MWMS Documents
This page must align with:
Content Brain Copy Map
Content Brain Operating Model
Content Brain Workflow Map
Content Brain Affiliate Funnel Support Map
Content Brain SEO Content Brief Standard
Content Brain AI Content Quality Governance Framework
Content Brain Information Gain Framework
Content Brain E E A T Content Trust Framework
Content Brain Editorial Consistency Framework
Content Brain Internal Linking Strategy Framework
Content Brain Content Optimization Framework
Content Brain Content Repurposing Framework
Compliance Brain Claims Risk Framework
Affiliate Brain Offer Intelligence
Conversion Brain Message Match Framework
Data Brain Signal Integrity Framework
MWMS MCR To Brain Copy Rule
MWMS Brain Interaction Map
MWMS Document Structure Standard
MWMS Page Naming Standard
MWMS AI Output Standard Full File Delivery Rule
Relationship To Future Plugin Or UI
This checklist may later support:
Publishing Readiness Checklist UI
Content QA Screen
Approval Workflow
Content Production Queue
Content Refresh Queue
Affiliate Content Review Screen
Content Operations Dashboard
These should not be built yet.
Manual checklist use must prove operational need before plugin or UI development begins.
Drift Protection
The system must prevent:
publishing content without a clear source
publishing content without a defined purpose
publishing content without audience clarity
publishing affiliate content before offer status is clear
publishing compliance-sensitive claims without review
publishing generic AI content
publishing thin SEO content
publishing content with invented facts
publishing content with unsupported proof
publishing content with unclear destination
publishing content with no feedback path
using this checklist as a replacement for Compliance Brain approval
using this checklist as a replacement for Affiliate Brain offer approval
using this checklist as a replacement for Conversion Brain authority
building plugin or UI checklists before manual workflow use is proven
mwmscontentbrain.site replacing MCR source-of-truth authority
Architectural Intent
The Content Brain Publishing Readiness Checklist exists to protect content quality and system discipline.
It ensures that Content Brain outputs are not pushed into the ecosystem until they are fit for purpose.
The long-term intent is to make content publishing more reliable, safer, more useful, and more connected to MWMS learning loops.
This checklist supports the future operational Content Brain by creating a simple gate between draft and use.
Final Rule
Content is not ready because it exists.
Content is ready when it has passed source, purpose, audience, quality, trust, risk, destination, approval, and feedback checks.
If the content cannot pass this checklist, it should not be published or handed off.
Change Log
Version: v1.1
Date: 2026-05-08
Author: HeadOffice
Change: Created operational copy for mwmscontentbrain.site. Added Operational Copy Notice, Source Of Truth protection, Parent update for live site, manual workflow before automation discipline, relationship to future plugin or UI, and drift protection against mwmscontentbrain.site replacing MCR authority.
Version: v1.0
Date: 2026-05-06
Author: HeadOffice
Change: Initial creation of Content Brain Publishing Readiness Checklist defining the readiness gate for content publication, content handoff, affiliate support content, SEO content, trust review, compliance sensitivity, destination control, approval ownership, and feedback path.
Change Impact Declaration
Pages Created:
Content Brain Publishing Readiness Checklist
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT BRAIN PUBLISHING READINESS CHECKLIST v1.1