Brain Name: Content Brain
Document Type: Operational Checklist
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain publishing readiness, content review, handoff readiness, affiliate content checks, SEO content checks, refresh completion checks, repurposing readiness, approval ownership, claim safety, compliance risk awareness, and first operational Content Brain layer use
Parent: Content Brain
Last Reviewed: 2026-05-24
Operational Copy Notice
This page is the live operator publishing readiness page for Content Brain on mwmscontentbrain.site.
MCR remains the source of truth.
If this page conflicts with MCR, MCR wins.
This page is designed for practical operator use.
It is not a full MCR governance page.
Purpose
Content Brain Publishing Readiness defines the final operational check before content is published, handed off, repurposed, refreshed, or used.
This page exists to stop content from moving forward before the basics are clear.
Before any meaningful content asset is used, the operator should confirm:
the content has a clear purpose
the content has a clear audience
the content follows the brief
the source Brain is known
the approval owner is known
the content type is correct
the claim risk has been checked
the compliance sensitivity has been considered
the handoff destination is clear
the next action is clear
the signal to watch is defined
Publishing readiness is not the same as final approval.
It is the operational checkpoint before content moves forward.
Source Of Truth
MCR defines the governing version of Content Brain.
mwmscontentbrain.site operates the working version.
This page is the working operator version of the Content Brain publishing readiness system.
Do not treat this page as a replacement for:
Content Brain Canon
Content Brain Architecture
Content Brain Page Registry
Content Brain Copy Map
Content Brain Migration Execution Checklist
mwmscontentbrain.site First Operational Layer Build Checklist
Those remain MCR control pages.
What This Page Is For
Use this page before content is:
published
handed off
used in a funnel
used in an affiliate content pack
used in an email
used in a YouTube description
used in VEO3 pre-video support
used in social content
used in sales support
used in a campaign support asset
repurposed
refreshed
sent to another Brain
marked ready
This page gives the operator a practical readiness check.
What This Page Does Not Control
This page does not control:
offer approval
campaign approval
capital approval
final compliance approval
statistical validation
search validation
affiliate opportunity approval
paid ad decisions
plugin implementation
Supabase implementation
Brain Room routing
HeadOffice reporting build work
M’s active development areas
Those remain governed by the relevant Brain, protocol, standard, or implementation layer.
Core Principle
Content is not ready just because it has been written.
Content is ready only when:
the purpose is clear
the audience is clear
the structure is useful
the brief has been followed
the risks have been checked
the destination is known
the approval owner is known
the next action is clear
the content can safely move forward
If any major readiness item is missing, the content should remain in review.
When To Use This Checklist
Use this checklist for:
new articles
SEO content
affiliate support content
affiliate product content pack assets
affiliate funnel support content
comparison content
review support content
FAQ content
objection-handling content
trust-building content
YouTube descriptions
YouTube script support
VEO3 pre-video support
email content
newsletter content
social content
internal linking work
repurposed content
refreshed content
AIBS education content
sales support content
conversion support content
Use the full checklist for important, public-facing, affiliate-related, SEO-focused, compliance-sensitive, or campaign-supporting content.
Use the fast checklist for small, low-risk, internal, or clearly defined tasks.
Fast Publishing Readiness Check
Use this for small or low-risk content.
Confirm:
Content title:
Content type:
Source Brain:
Content purpose:
Target audience:
Brief followed: Yes / No
Claim risk checked: Yes / No
Compliance sensitivity: Low / Medium / High / Unknown
Approval owner:
Handoff destination:
Signal to watch:
Ready status:
Ready
Needs edits
Needs approval
Needs research
Needs compliance review
Parked
Do not mark content ready if the approval owner, destination, or risk level is unclear.
Full Publishing Readiness Checklist
Use this for important, public-facing, affiliate-related, SEO-focused, campaign-supporting, or compliance-sensitive content.
1. Content Identity
Field:
Content Name:
Operator instruction:
Record the working title or final content name.
2. Content Type
Field:
Content Type:
Options:
SEO article
Blog post
Authority page
Affiliate support content
Affiliate product content pack asset
Affiliate funnel support asset
Pre-sell article
Comparison article
Review support article
FAQ content
Objection-handling content
Trust support content
YouTube description
YouTube script support
VEO3 pre-video support
Newsletter
Social content
Internal linking update
Refresh update
Repurposed content
AIBS education content
Sales support content
Conversion support content
Other
Operator instruction:
Choose the closest content type.
3. Source Brain
Field:
Source Brain:
Options:
HeadOffice
Affiliate Brain
Research Brain
Search Intelligence Brain
Ads Brain
Experimentation Brain
AIBS Brain
Compliance Brain
Finance Brain
Data Brain
Conversion Brain
Sales Brain
SIT Brain
Manual Operator Observation
Operator instruction:
Record where the content request, signal, or priority came from.
If the source Brain is unclear, do not mark the content ready.
4. Supporting Brain
Field:
Supporting Brain:
Operator instruction:
Record any Brain that supplied research, offer logic, search demand, compliance notes, ad context, conversion logic, sales context, or data signals.
If none, write:
Not applicable
5. Content Purpose
Field:
Content Purpose:
Operator instruction:
Explain why the content exists.
The purpose should be specific.
Weak purpose:
Write an article about this topic.
Strong purpose:
Educate problem-aware readers before they click through to the affiliate VSL.
If the purpose is unclear, the content is not ready.
6. Target Audience
Field:
Target Audience:
Operator instruction:
Record who the content is for.
Include:
audience type
awareness stage
pain point
desired outcome
market or location if relevant
knowledge level
If the audience is too broad or unclear, the content needs review.
7. Reader Intent
Field:
Reader Intent:
Options:
Learn
Compare
Decide
Understand risk
Solve a problem
Validate trust
Prepare for purchase
Watch VSL
Click affiliate link
Book call
Reply
Share
Save
Other
Operator instruction:
Confirm the content matches what the reader is likely trying to do.
8. Funnel Role
Field:
Funnel Role:
Options:
Awareness
Education
Trust building
Pre-sell
Comparison
Objection handling
Decision support
Follow-up
Retention
Internal support
Not applicable
Operator instruction:
Confirm where the content fits in the journey.
If the funnel role is unclear for affiliate or conversion-support content, review before use.
9. Brief Alignment
Field:
Brief Alignment:
Options:
Fully aligned
Mostly aligned
Partly aligned
Not aligned
No brief exists
Operator instruction:
Confirm whether the content follows the correct brief.
If no brief exists for meaningful content, create or complete the brief before marking ready.
Use:
Content Brain Content Briefs
Content Brain SEO Content Briefs
Content Brain Affiliate Content Packs
Content Brain Affiliate Funnel Support
where needed.
10. Message Clarity
Field:
Message Clarity:
Options:
Clear
Mostly clear
Needs editing
Unclear
Operator instruction:
Confirm the content has one clear main message.
If the reader would not understand the main point quickly, the content needs editing.
11. Structure Check
Field:
Structure Check:
Options:
Strong
Acceptable
Needs improvement
Weak
Operator instruction:
Review whether the content has a useful structure.
Check:
headline or title
introduction
section flow
subheadings
logical order
FAQ section if needed
CTA or next step
reader journey
If the structure is confusing, content is not ready.
12. Usefulness Check
Field:
Usefulness Check:
Options:
Useful
Mostly useful
Generic
Thin
Not useful
Operator instruction:
Confirm the content gives the reader practical value.
Watch for:
generic AI language
thin explanation
repeated points
no clear answer
weak examples
no information gain
no useful next step
If the content is thin or generic, return it for improvement.
13. Accuracy Check
Field:
Accuracy Check:
Options:
Checked
Needs checking
Research missing
Not applicable
Operator instruction:
Confirm factual content has been reviewed against the available source material.
If the content makes factual claims without a research basis, it is not ready.
14. Research Basis
Field:
Research Basis:
Operator instruction:
Record the research, signals, evidence, source pages, or Brain notes supporting the content.
If missing, write:
Research basis missing — content not ready for public use.
15. Search Intent Check
Field:
Search Intent Check:
Options:
Aligned
Mostly aligned
Needs review
Not SEO content
Operator instruction:
For SEO content, confirm the content matches search intent.
Check:
query intent
reader expectation
SERP pattern
topic coverage
information gain
internal linking
If search intent is unclear, route to Search Intelligence Brain or Research Brain.
16. SEO Basics Check
Field:
SEO Basics Check:
Options:
Complete
Mostly complete
Needs work
Not SEO content
Operator instruction:
For SEO content, confirm:
title is clear
heading structure is logical
target topic is clear
supporting topics are covered
internal links are considered
content is useful to humans
no keyword stuffing exists
Do not mark SEO content ready if it is thin or written only for keywords.
17. Internal Linking Check
Field:
Internal Linking Check:
Options:
Complete
Needs internal links
Not applicable
Operator instruction:
Confirm whether internal links are needed.
Use Content Brain Internal Linking where the linking plan is meaningful.
Check:
source page
target page
reader journey
topic relationship
funnel relationship
anchor text
affiliate risk
compliance risk
18. CTA Check
Field:
CTA Check:
Options:
Clear
Needs improvement
Wrong CTA
No CTA needed
Operator instruction:
Confirm the CTA fits the content role.
The CTA should match:
audience stage
offer status
content purpose
approval status
destination
Do not force a CTA where it does not fit.
19. Affiliate Offer Status
Field:
Affiliate Offer Status:
Options:
Approved
Review-ready
Research needed
Testing candidate
Rejected
Not applicable
Unknown
Operator instruction:
If the content supports an affiliate offer, confirm offer status.
Do not publish affiliate support content as if the offer is approved unless offer status is clear.
20. Affiliate Claim Check
Field:
Affiliate Claim Check:
Options:
Safe
Needs review
High risk
Not applicable
Operator instruction:
For affiliate content, confirm that the content does not make unsupported claims.
Check for:
product performance claims
income claims
health claims
guarantees
scarcity
urgency
unverified testimonials
exaggerated comparisons
If risk exists, route to Compliance Brain.
21. Claims To Avoid Check
Field:
Claims To Avoid Check:
Options:
Checked
Needs review
Missing
Not applicable
Operator instruction:
Confirm the content avoids claims listed in the brief.
If the content introduces new claims, return it for review.
22. Compliance Sensitivity
Field:
Compliance Sensitivity:
Options:
Low
Medium
High
Unknown
Operator instruction:
Record the risk level.
If risk is medium, high, or unknown, identify the required review owner before use.
23. Required Compliance Review
Field:
Required Compliance Review:
Options:
Not required
Compliance Brain
HeadOffice
Affiliate Brain
Ads Brain
Legal review
Other
Unknown
Operator instruction:
If compliance sensitivity is medium, high, or unknown, record who must review it.
Do not mark content ready without a review owner.
24. Tone And Style Check
Field:
Tone And Style Check:
Options:
Aligned
Mostly aligned
Needs editing
Wrong tone
Operator instruction:
Confirm the tone matches the content purpose.
Preferred tones may include:
clear
helpful
practical
direct
calm
authority-building
trust-focused
compliance-aware
conversion-supportive
non-hype
Do not use hype unless explicitly approved.
25. Brand And System Alignment
Field:
Brand And System Alignment:
Options:
Aligned
Mostly aligned
Needs review
Not aligned
Operator instruction:
Confirm the content fits MWMS standards and does not create conflict with the wider system.
Check whether the content supports the correct Brain and does not overstep authority.
26. Repurposing Risk Check
Field:
Repurposing Risk Check:
Options:
Safe
Needs review
High risk
Not repurposed content
Operator instruction:
For repurposed content, confirm it preserves meaning.
Do not allow repurposed content to:
strengthen claims
change compliance risk
alter the approved message
add unsupported promises
change offer meaning
27. Refresh Completion Check
Field:
Refresh Completion Check:
Options:
Complete
Needs more work
Not refresh content
Operator instruction:
For refreshed content, confirm:
the refresh trigger was addressed
outdated content was corrected
missing information was added
internal links were reviewed
claim risk was checked
content quality improved
next review signal is recorded
28. Handoff Destination
Field:
Handoff Destination:
Options:
WordPress page
Blog post
YouTube description
YouTube script
VEO3 pre-video
Newsletter
Social post
Affiliate funnel
Sales support
Internal knowledge
Refresh queue
Repurposing queue
Other
Operator instruction:
Record where the content goes next.
If the destination is unclear, the content is not ready.
29. Approval Owner
Field:
Approval Owner:
Operator instruction:
Record who must approve the content before use.
Examples:
Martyn
HeadOffice
Affiliate Brain
Research Brain
Search Intelligence Brain
Ads Brain
Experimentation Brain
Compliance Brain
Finance Brain
Conversion Brain
Sales Brain
AIBS Brain
Other
If approval owner is missing, do not mark ready.
30. Final Decision
Field:
Final Decision:
Options:
Ready for use
Ready for handoff
Ready for approval
Needs edits
Needs research
Needs compliance review
Needs owner decision
Parked
Rejected
Operator instruction:
Choose the correct final status.
Only select Ready for use when all important checks are complete.
31. Signal To Watch
Field:
Signal To Watch:
Options:
search impressions
search clicks
ranking movement
affiliate clicks
VSL clicks
YouTube views
YouTube retention
email opens
email clicks
social engagement
time on page
scroll depth
conversion support
sales usefulness
objection reduction
manual feedback
Other
Operator instruction:
Choose the signal that will show whether the content was useful.
Do not over-interpret weak signals.
Data Brain owns data quality.
32. Notes
Field:
Notes:
Operator instruction:
Record any final issues, risks, approvals, or follow-up tasks.
Publishing Readiness Decision Table
Use this table to decide what happens next.
| Situation | Decision |
|---|---|
| Purpose clear, brief followed, risk low, approval owner known | Ready for handoff or use |
| Purpose clear, but edits needed | Needs edits |
| Research basis missing | Needs research |
| Offer status unclear | Needs Affiliate Brain or Research Brain review |
| Claim risk unclear | Needs compliance review |
| Approval owner missing | Needs owner decision |
| Destination unclear | Parked |
| Content thin or generic | Needs improvement |
| Repurposed content changes meaning | Needs review |
| Refreshed content does not address trigger | Needs more work |
| Content belongs to another Brain | Route back to correct Brain |
When To Mark Ready
Mark content ready only when:
the purpose is clear
the audience is clear
the brief has been followed
the content is useful
claim risk has been checked
compliance sensitivity is known
approval owner is known
handoff destination is clear
signal to watch is defined
Marking content ready does not override final approval authority.
When To Park Content
Park content when:
purpose is unclear
audience is unclear
source Brain is unclear
brief is missing
research basis is missing
offer status is unclear
compliance risk is unclear
approval owner is missing
handoff destination is unclear
content belongs to another Brain
Parked does not mean rejected.
It means the missing information must be resolved before the content moves forward.
Relationship To Other Operational Pages
Use this page with:
Content Brain for the homepage and operator starting point
Content Brain Workflow for the full workflow
Content Brain Content Briefs for creating content briefs
Content Brain Affiliate Content Packs for affiliate content pack planning
Content Brain Affiliate Funnel Support for funnel-stage mapping
Content Brain SEO Content Briefs for search-focused content planning
Content Brain Internal Linking for page connection planning
Content Brain Repurposing for adapting approved content
Content Brain Refresh for improving existing content
Future Plugin Or UI Candidates
This page may later support:
Publishing Readiness Checklist UI
Content Production Queue
Content Refresh Queue
Repurposing Queue
Content Operations Dashboard
Content Quality Checklist
Content Signal Feedback Dashboard
Do not build these yet.
Manual use must prove the need first.
No Build Rule
Do not start any of the following from this page:
plugin work
custom UI work
Supabase work
Brain Room routing
automation
queue build
dashboard build
generator build
cross-brain task routing
This page is part of the first manual operational layer only.
Old Page Handling
This page replaces the operator role of the older page:
Content Brain Publishing Readiness Checklist
After Content Brain Publishing Readiness is created and checked, the older Content Brain Publishing Readiness Checklist page should be handled as follows:
If it is only a duplicate operational readiness page, delete it.
If it is needed for historical reference, move it to a legacy/reference area and mark it clearly as legacy.
Do not keep both as active operator publishing readiness pages.
The active operator publishing readiness page should be:
Content Brain Publishing Readiness
Drift Protection
The system must prevent:
content being marked ready without a clear purpose
content being marked ready without source Brain context
content being marked ready without approval owner
affiliate content being marked ready before offer status is clear
SEO content being marked ready without reader intent
repurposed content being marked ready after changing meaning
refresh content being marked ready without addressing the refresh trigger
claim risk being ignored
compliance sensitivity being unknown
handoff destination being unclear
publishing readiness being treated as final approval
old checklist pages being treated as the current operator readiness page after this clean page is created
future UI being built before manual readiness use proves need
Architectural Intent
Content Brain Publishing Readiness exists to create a clear final check before content moves forward.
Its role is to protect the MWMS system from unclear, risky, thin, misaligned, or unapproved content.
Publishing readiness is the bridge between:
brief
draft
review
handoff
publishing
repurposing
refresh
signal feedback
The long-term intent is:
MCR defines Content Brain.
mwmscontentbrain.site operates Content Brain.
Future plugin or UI systems automate repeated workflows only after manual use proves the need.
Final Rule
No meaningful content should be marked ready without a clear purpose, clear audience, clear approval owner, known risk level, and clear handoff destination.
Publishing readiness does not override the authority of another Brain.
It is a final operational check, not final strategic approval.
When in doubt, mark the content as:
Needs review
Needs approval
Needs research
Needs compliance review
Parked
Do not force content forward.
Change Log
Version: v1.0
Date: 2026-05-24
Author: HeadOffice
Change: Created clean operator publishing readiness page for mwmscontentbrain.site based on MCR Content Brain Publishing Readiness Checklist Operational Copy and the existing Content Brain Publishing Readiness Checklist page. Defines the live Content Brain Publishing Readiness page for the first operational Content Brain layer, including fast readiness check, full publishing readiness checklist, decision table, ready rules, parking rules, relationship to other operational pages, no build rule, old page handling, drift protection, and manual-first future plugin/UI boundaries.
Change Impact Declaration
Pages Created:
Content Brain Publishing Readiness
Pages Updated:
None
Pages To Delete Or Move To Legacy After Validation:
Content Brain Publishing Readiness Checklist
Pages Deprecated:
Content Brain Publishing Readiness Checklist as active operator publishing readiness page
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT BRAIN PUBLISHING READINESS v1.0