Brain Name: Content Brain
Document Type: Operational Copy
Status: Draft
Version: v1.1
Authority: Content Brain under HeadOffice governance
Applies To: mwmscontentbrain.site future publishing-readiness page, completed content assets, editing and quality-control outcomes, specialist-review outcomes, human approvals, publishing preparation, delivery preparation, website content, articles, social content, scripts, advertising content, newsletters, emails, manuals, documentation, content packs, refreshed content and repurposed content
Parent: Content Brain
Enforcement Mode: Operational
Last Reviewed: 2026-06-16
Content Brain Publishing Readiness Checklist Operational Copy
Purpose
The Content Brain Publishing Readiness Checklist Operational Copy defines the prepared future operator checklist for confirming that an approved content asset is ready to be published, scheduled, delivered or handed to its authorised destination owner.
This page remains an MCR-controlled operational copy.
It is not yet the live mwmscontentbrain.site publishing-readiness page.
Its purpose is to confirm that the correct work has been completed before an asset leaves Content Brain’s production and approval workflow.
Publishing readiness should confirm:
the correct asset has been produced
the correct version is being checked
production is complete
editing and quality control are complete
specialist review is complete where required
human approval has been recorded
approval conditions have been applied
sources and evidence remain valid
claims remain within approved boundaries
the destination is confirmed
links are correct
formatting is ready
required media and metadata are ready
the call to action is correct
the publishing or delivery owner is known
tracking requirements are known
the final package is complete
known blockers have been resolved
the correct next action is clear
Publishing readiness does not mean publication has occurred.
It confirms only that the approved asset is ready for the authorised human-controlled publication or delivery step.
Scope
This operational copy applies to:
website pages
landing pages
bridge pages
advertorials
affiliate review pages
comparison pages
buyer guides
articles
blog posts
social posts
social carousels
social threads
short-form scripts
long-form scripts
video scripts
audio scripts
webinar scripts
advertising copy
advertising scripts
newsletters
emails
email sequences
manuals
guides
documentation
reports
lead magnets
training content
content packs
affiliate product content packs
refreshed content
expanded content
corrected content
merged content
repurposed content
reformatted content
publishing packages
delivery packages
This operational copy does not replace:
Content Brain Canon
Content Brain Architecture
Content Brain Operating Model
Content Brain Workflow Map
Content Brain Publishing Readiness Checklist
Content Brain Content Brief Template
Content Brain Content Brief Template Operational Copy
Content Brain Workflow Operational Copy
approved source records
approved evidence
specialist-review decisions
human approval
destination-owner authority
This page does not authorise:
automatic publication
automatic social posting
automatic email sending
automatic newsletter sending
automatic advertising deployment
automatic website changes
automatic delivery
automatic approval
worker activation
queue execution
AI Employee activation
Brain Room routing
automatic M handoff
changes to M’s Research Brain work
Core Rule
An asset may be marked Publishing-Ready or Delivery-Ready only when all required production, review and approval stages have been completed.
The required sequence is:
Content Production
Editing And Quality Control
Specialist Review Where Required
Human Approval
Publishing Preparation
Publishing Readiness Check
Human-Controlled Publication Or Delivery
Outcome Recording
An asset must not skip directly from:
Draft Complete
to:
Publishing-Ready
An asset must not be treated as approved because:
a brief exists
a draft exists
editing is complete
a checklist has been completed
a specialist has commented
the asset looks finished
the destination owner is waiting
Human approval must remain a separate confirmed decision.
Publishing-readiness completion is not approval.
Publishing-readiness completion is not publication.
Publishing-readiness completion is not delivery.
Publishing Readiness Decision
Every reviewed asset must receive one clear decision.
Available decisions are:
Publishing-Ready
The asset is approved and ready for authorised publication or scheduling.
Delivery-Ready
The asset is approved and ready to be handed to the authorised destination or implementation owner.
Ready With Minor Final Action
The asset is approved, but a small clearly defined publishing-preparation action remains.
Returned For Editing
Editorial, structural, clarity, formatting or quality work remains.
Returned For Source Or Evidence Review
A source, evidence or factual issue remains unresolved.
Returned For Specialist Review
Required specialist authority has not been completed or a new specialist issue has appeared.
Returned For Human Approval
Approval is missing, incomplete, outdated or does not cover the final version.
Returned For Publishing Preparation
The asset is approved, but destination-specific preparation remains incomplete.
Blocked
A known issue prevents readiness.
Held
The asset should not proceed until a defined future condition is met.
Rejected
The asset must not be published or delivered in its current form.
Cancelled
The content work is no longer required.
Readiness Status
Each asset should show one current readiness status.
Available statuses:
Not Ready
In Editing
Waiting For Source Confirmation
Waiting For Evidence
Waiting For Specialist Review
Waiting For Human Approval
In Publishing Preparation
Ready With Conditions
Publishing-Ready
Delivery-Ready
Scheduled
Published
Delivered
Blocked
Held
Rejected
Cancelled
The status must describe the asset’s actual state.
Do not mark an asset Published or Delivered merely because it is Publishing-Ready.
Publishing Readiness Checklist
Asset Identity
Asset Title:
Asset ID:
Asset Version:
Asset Type:
Related Request:
Related Project:
Related Brief:
Related Parent Asset:
Related Content Pack:
Content Action:
Create
Refresh
Expand
Correct
Merge
Repurpose
Reformat
Relink
Other Approved Action
Prepared By:
Readiness Reviewer:
Date Reviewed:
Primary Destination:
Publishing Or Delivery Owner:
Asset Identity Checks
Confirm:
the correct asset is being reviewed
the final working title is correct
the asset type is correct
the current version is identified
the reviewed version matches the approved version
the related request is known
the related project is known where required
the related brief or instruction is known
the destination is known
the publishing or delivery owner is known
Pass:
Yes / No / Not Applicable
Failure Action:
Return to the correct asset, project, brief or version record.
Production Completion
Confirm:
the required asset has been fully produced
the production output matches the requested asset type
the production output fulfils the approved objective
all required sections are present
all required components are present
all required variations are present
all related pack assets required at this stage are present
the asset is not an incomplete draft
the asset does not contain unfinished placeholders
the asset does not contain hidden drafting notes
the asset does not contain unresolved production comments
the asset does not contain accidental internal instructions
production completion criteria have been met
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Content Production.
Editing And Quality Control
Confirm:
structural editing is complete
clarity editing is complete
factual alignment is complete
source alignment is complete
evidence alignment is complete
voice alignment is complete
tone alignment is complete
audience alignment is complete
intent alignment is complete
destination alignment is complete
repetition has been reduced
unnecessary content has been removed
thin sections have been improved
content gaps have been resolved or deliberately accepted
headings are clear
the content flow is logical
the call to action is clear
the content is complete
the asset is useful
the asset has appropriate information gain
the content does not duplicate existing content unnecessarily
the content meets the required completion standard
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Editing And Quality Control.
Source And Evidence
Confirm:
all important factual statements have an approved basis
all material sources remain valid
all approved sources are traceable
research inputs remain current enough for the asset
statistics are accurate and appropriately presented
dates are correct
product information is correct
offer information is correct
customer-language inputs are approved
examples are accurate
testimonials are approved where used
case studies are approved where used
working assumptions are not presented as confirmed facts
emerging signals are not presented as proven conclusions
unverified claims have been removed or clearly controlled
restricted claims have not been used without approval
the final asset has not introduced unsupported new claims
no evidence has been invented
no source has been invented
no customer experience has been invented
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Source And Evidence Assembly, Research Brain, the source owner or the appropriate specialist reviewer.
Claims And Compliance
Confirm:
the compliance risk level is known
approved claims remain within their approved wording and meaning
restricted claims have been removed or controlled
prohibited claims are absent
required disclosures are present
required disclaimers are present
required qualifications are present
material limitations are not hidden
the asset does not turn possibility into certainty
the asset does not turn correlation into causation
the asset does not turn opinion into verified fact
the asset does not turn customer language into proof
the asset does not turn product support into a medical claim
the asset does not strengthen claims during editing or formatting
affiliate relationships are disclosed where required
commercial intent is not misleading
specialist compliance review is complete where required
legal review is complete where required
other required risk review is complete
Pass:
Yes / No / Not Applicable
Failure Action:
Return to the appropriate specialist review or editing stage.
Specialist Review
Confirm whether specialist review was required.
Specialist Review Required:
Yes / No
Required Specialist Type:
Compliance
Legal
Medical
Technical
Financial
Research
Product
Offer
Search
Data
Campaign
Brand
Stakeholder
Client
Other
Confirm:
the required specialist received the correct asset version
the specialist decision is recorded
required changes were completed
the final asset still matches the reviewed version
no material change occurred after specialist review
specialist conditions are visible
specialist restrictions are visible
required evidence additions were completed
required wording changes were completed
no unresolved specialist objection remains
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Specialist Review or complete the required revisions and repeat the affected checks.
Human Approval
Human approval remains mandatory before publication or delivery under the current operating model.
Confirm:
the approval owner is identified
the approval decision is recorded
the approver reviewed the correct version
the approved destination is recorded
approval conditions are recorded
required changes were completed
the final asset still matches the approved version
the final call to action matches the approved version
the final claims match the approved version
no material content change occurred after approval
the approval has not expired or been withdrawn
all additional approvers required have responded
the asset is not being treated as approved merely because editing is complete
Approval Decision:
Approved
Approved With Minor Changes
Revision Required
Rejected
Held
Approval Pending
Approval Owner:
Approval Date:
Approved Version:
Approval Conditions:
Pass:
Yes / No
Failure Action:
Return to Human Approval.
Material Change Check
Confirm whether any material change occurred after specialist review or human approval.
Material changes include:
objective change
audience change
asset-type change
destination change
offer change
product change
source change
evidence change
claim change
call-to-action change
legal or compliance change
major structural change
meaning change
substantial new section
substantial deleted section
major headline or promise change
If a material change occurred:
the affected specialist review must be repeated where required
human approval must be repeated
the approved version must be updated
Material Change After Approval:
Yes / No
New Review Required:
Yes / No
New Approval Required:
Yes / No
Pass:
Yes / No
Failure Action:
Return to the affected review and approval stages.
Title And Naming
Confirm:
the final title is approved
the title accurately represents the content
the title does not overstate the evidence
the title does not contain an unapproved claim
the title fits the destination
the title follows approved naming requirements
the asset filename is correct where relevant
the version label is correct
the page title contains no unnecessary version where WordPress title rules prohibit it
the title does not duplicate another active destination asset unintentionally
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Publishing Preparation or Human Approval if meaning changes.
URL And Slug
Use where a web destination is involved.
Confirm:
the destination URL is known
the slug is approved
the slug is readable
the slug is relevant
the slug is not unnecessarily long
the slug does not duplicate another active URL
redirect requirements are known
canonical requirements are known where applicable
the old URL is preserved where required
the new URL does not create avoidable content duplication
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Publishing Preparation or the authorised website owner.
Metadata
Use where metadata is required.
Confirm:
the meta title is present
the meta title accurately represents the content
the meta description is present
the meta description accurately represents the content
metadata does not introduce stronger claims than the asset
social-preview title is present where required
social-preview description is present where required
email subject line is present where required
email preview text is present where required
schema or structured-content notes are present where required
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Publishing Preparation.
Content Structure And Formatting
Confirm:
heading levels are logical
sections are in the correct order
paragraphs are readable
lists are formatted correctly
tables are readable
quotes are formatted correctly
warnings are visible
important notes are visible
calls to action are correctly placed
spacing is consistent
the asset fits the destination format
mobile readability has been considered where relevant
email formatting is suitable where relevant
social formatting is suitable where relevant
script formatting is suitable where relevant
manual or documentation formatting is suitable where relevant
no drafting markup remains
no accidental formatting code remains
no broken layout is visible
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Publishing Preparation or Editing And Quality Control.
Internal Links
Use where internal links are relevant.
Confirm:
required internal links are present
links point to the intended destination
anchor text is clear
anchor text is not misleading
links support the reader journey
links support the content relationship
links support the approved funnel or journey role
duplicate unnecessary links have been removed
broken links are absent
links do not point to draft or unavailable pages unintentionally
new content is linked from appropriate existing pages where required
old content is updated where required
merge or redirect actions are included where required
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Publishing Preparation or the internal-linking owner.
External Links And References
Confirm:
required external links are present
external links are accurate
external links point to the intended source
sources remain available
references support the statement they accompany
commercial links are identified where required
affiliate links are correct where required
tracking parameters are correct where required
unapproved links are absent
broken external links are absent
unsafe or low-trust sources are not used without approval
external links do not create an avoidable compliance problem
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Source Review or Publishing Preparation.
Images And Media
Confirm:
required images are present
required graphics are present
required video or audio files are present
the correct media versions are used
media matches the approved content
image rights or permissions are known where required
image captions are present where required
alt text is present where required
alt text is accurate
alt text is useful
media filenames are appropriate
media dimensions are suitable
media quality is acceptable
media does not contain unsupported claims
media does not contradict the content
thumbnails are approved where required
visual instructions are clear where production occurs elsewhere
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Publishing Preparation, Creative Brain or the approved media owner.
Call To Action
Confirm:
the required call to action is present
the call to action matches the approved objective
the call to action matches the approved destination
the call to action is clear
the call to action is not misleading
the call to action does not introduce an unapproved promise
the call-to-action link is correct
the call-to-action button text is correct
the call to action appears in the correct location
the call to action matches related campaign or funnel assets where required
the call to action is appropriate for the audience stage
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Editing, Conversion Review, Affiliate Brain, Ads Brain or Human Approval as appropriate.
Destination Requirements
Confirm:
the destination is identified
the destination owner is identified
the destination accepts the asset type
required platform fields are known
required dimensions are known
required character limits are met
required duration limits are met
required file formats are correct
required naming conventions are met
required platform disclosures are present
required publishing permissions exist
required access is available to the authorised human
the asset does not depend on an unavailable destination feature
destination-specific formatting is complete
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Publishing Preparation or the destination owner.
Website Publishing Requirements
Use for website content.
Confirm:
the correct website is identified
the correct page type is identified
the Parent page is correct where relevant
the page title is correct
the slug is correct
the content hierarchy is correct
required forms are present
required buttons are present
required links are present
required tracking is known
required disclosures are present
author details are correct where required
featured image requirements are met
mobile display has been checked where possible
desktop display has been checked where possible
page duplication has been checked
the page does not replace an MCR source page unintentionally
the page does not create a competing source of truth
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Publishing Preparation or the authorised website operator.
Article Publishing Requirements
Use for articles and blog content.
Confirm:
the article title is approved
the introduction matches the article intent
the article answers the required questions
information gain is present
required examples are present
required sources are present
required internal links are present
required external references are present
required metadata is ready
required author information is ready
required category or topic placement is known
required featured image is ready
required FAQ content is ready where applicable
the article does not duplicate another active article unnecessarily
the review date is known where required
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Editing, Source Review or Publishing Preparation.
Social Publishing Requirements
Use for social content.
Confirm:
the correct platform is identified
the post format is correct
the caption is complete
the hook is approved
the visual asset is ready
the call to action is correct
links are correct where supported
hashtags are appropriate where used
platform limits are met
thread or carousel sequence is correct
on-screen text is correct where required
the content remains understandable outside the source asset
claims remain controlled
human posting or scheduling owner is identified
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Editing, Creative Review or Publishing Preparation.
Script Delivery Requirements
Use for video, audio, webinar, presentation or advertising scripts.
Confirm:
the script type is correct
the final script version is identified
the target duration is appropriate
the opening hook is approved
the structure is complete
the spoken language is natural
scene notes are clear where required
shot notes are clear where required
voiceover notes are clear where required
on-screen text is correct
pronunciation notes are present where required
claims are approved
the call to action is approved
the production owner is known
the delivery format is correct
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Script Editing, Specialist Review or Publishing Preparation.
Advertising Content Requirements
Use for advertising content.
Confirm:
the requesting Brain is known
the approved campaign requirement is known
the offer is confirmed
the audience is confirmed
the platform is confirmed
the angle is approved
the hook is approved
the message matches the destination
claims remain within approved boundaries
required variations are complete
required character or duration limits are met
compliance review is complete
Ads Brain review is complete where required
the campaign handoff owner is identified
Content Brain is not being treated as the campaign authority
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Ads Brain, Affiliate Brain, Compliance Review, Editing or Publishing Preparation.
Newsletter And Email Requirements
Confirm:
the correct audience or list is identified
the email type is correct
the sequence position is correct where relevant
the subject line is approved
preview text is approved
sender information is known
reply-to information is known where relevant
links are correct
the call to action is correct
required disclosures are present
unsubscribe or platform requirements are handled by the authorised sending system
the email has been formatted for the destination platform
the sequence logic remains correct
sending ownership is clear
Content Brain is not being treated as the sending authority
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Email Editing, Compliance Review, Publishing Preparation or the authorised sender.
Manual Guide And Documentation Requirements
Confirm:
the intended reader is clear
the required outcome is clear
steps are complete
steps are in the correct order
warnings are visible
dependencies are stated
technical details are correct
screenshots are current where used
examples are accurate
version information is correct
update ownership is known
review date is known
delivery format is correct
specialist review is complete where required
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Editing, Technical Review or Publishing Preparation.
Content Pack Requirements
Confirm:
the central objective is clear
all required assets are present
asset relationships are correct
shared sources remain consistent
shared evidence remains consistent
shared messages remain consistent
shared voice remains consistent
shared claims remain consistent
asset-specific adaptations are complete
cross-asset contradictions are absent
production order has been followed where required
each asset has the correct destination
each asset has the correct approval status
pack-level approval is complete where required
individual publishing or delivery owners are known
the pack-level completion standard is met
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Asset Planning, Production, Editing, Approval or Publishing Preparation.
Refresh Requirements
Use for refreshed content.
Confirm:
the refresh trigger is recorded
the correct existing asset was updated
outdated information was addressed
new evidence was included where required
obsolete evidence was removed
claims were rechecked
links were rechecked
metadata was rechecked
the original purpose remains valid or has been deliberately changed
the updated version is identified
material changes received new approval
republishing or update ownership is known
the next review date is known
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Refresh Production, Source Review, Approval or Publishing Preparation.
Repurposing Requirements
Use for repurposed content.
Confirm:
the source asset is approved
the source version is identified
the original meaning is preserved where required
the new format fits the destination
the new audience or audience stage is understood
the content has been adapted rather than copied blindly
claims have not been strengthened
new claims have not been introduced without approval
the new hook is approved
the new call to action is approved
platform requirements are met
the derivative asset has received required review and approval
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Repurposing Production, Editing, Specialist Review or Human Approval.
Merge And Retirement Requirements
Use where content is merged, redirected, archived or retired.
Confirm:
the primary asset is identified
useful content has been preserved
duplicate content has been removed
redirect requirements are known
internal links requiring updates are known
old URLs are recorded
archive requirements are known
retirement approval is recorded
recovery copies remain where required
the retired asset will not remain active accidentally
the merged asset has been reviewed and approved
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Merge Planning, Publishing Preparation or the authorised website owner.
Tracking And Measurement
Confirm:
the signal to watch is recorded
the measurement owner is known
the measurement source is known
required tracking is present or assigned
required campaign parameters are correct
required event requirements are known
the post-publication review date is known
the refresh trigger is known where required
tracking requirements do not block publication unnecessarily where tracking is not required
Content Brain does not claim authority over Data Brain measurement integrity.
Pass:
Yes / No / Not Applicable
Failure Action:
Return to Publishing Preparation, Data Brain or the destination owner.
Publishing Or Delivery Ownership
Confirm:
the final publication or delivery action has an authorised human owner
the owner knows the asset is ready
the owner has access to the destination
the owner has the correct asset version
the owner has the required instructions
the owner has the required media
the owner has the required links
the owner has the required metadata
the owner has the required disclosures
the owner understands any approval conditions
the owner understands any scheduling conditions
the owner understands any tracking requirements
the owner knows what outcome must be recorded
Pass:
Yes / No
Failure Action:
Hold the asset until ownership is clear.
Blocker Check
Confirm that no unresolved blocker remains.
Possible blockers include:
missing source
missing evidence
missing specialist review
missing human approval
incorrect version
unresolved claim
unresolved compliance issue
missing destination
missing media
broken link
missing metadata
missing disclosure
missing tracking requirement
missing publication owner
destination access problem
technical problem
conflicting instruction
outdated approval
material post-approval change
Current Blocker:
Blocker Owner:
Required Resolution:
Resolution Due:
Blocker Resolved:
Yes / No
Pass:
Yes / No
Failure Action:
Mark Blocked and return the asset to the correct owner or stage.
Final Version Control
Confirm:
the final version number or identifier is recorded
the approved version and publishing version match
the final file or page copy is clearly identified
earlier drafts will not be published accidentally
the correct media files are attached
the correct links are included
the correct metadata is included
the final package is complete
the version can be recovered
the previous active asset remains recoverable where required
Pass:
Yes / No
Failure Action:
Return to Publishing Preparation.
Final Publishing Package
The final package should include where relevant:
final approved asset
asset title
asset type
version
destination
publishing or delivery owner
approval record
specialist-review record
final metadata
final links
final media
final call to action
required disclosures
required disclaimers
tracking requirements
formatting instructions
schedule instructions
delivery notes
review date
measurement requirement
lifecycle trigger
Final Readiness Decision
Asset Title:
Asset Version:
Destination:
Publishing Or Delivery Owner:
Production Complete:
Yes / No
Editing And Quality Control Complete:
Yes / No
Specialist Review Complete Or Not Required:
Yes / No
Human Approval Complete:
Yes / No
Approval Covers Final Version:
Yes / No
Publishing Preparation Complete:
Yes / No
No Unresolved Blocker:
Yes / No
Final Decision:
Publishing-Ready
Delivery-Ready
Ready With Minor Final Action
Returned For Editing
Returned For Source Or Evidence Review
Returned For Specialist Review
Returned For Human Approval
Returned For Publishing Preparation
Blocked
Held
Rejected
Cancelled
Decision Owner:
Decision Date:
Decision Notes:
Conditions:
Immediate Next Action:
Next Action Owner:
Publication Or Delivery Rule
Where the decision is Publishing-Ready or Delivery-Ready:
provide the authorised owner with the final package
confirm the correct version
confirm the destination
confirm conditions
complete the human-controlled publication or delivery action
record the outcome
do not assume the action occurred merely because the package was handed over
Outcome Recording
After the human-controlled action, record:
Asset Title:
Asset Version:
Destination:
Action:
Published
Scheduled
Delivered
Partially Published
Publication Failed
Delivery Failed
Held
Cancelled
Action Owner:
Action Date:
Destination Reference:
Live URL Or Delivery Reference:
Known Issue:
Corrective Action Required:
Measurement Required:
Review Date:
Lifecycle Action Required:
Failure Handling
Publication Failure
Where publication fails:
record the failure
identify whether the problem is content, format, access, technical or destination related
return the asset to the correct preparation stage
do not mark the asset Published
Delivery Failure
Where delivery fails:
record the failure
identify the cause
confirm whether the asset remains approved
correct the delivery package or destination problem
do not mark the asset Delivered
Post-Publication Error
Where an error is discovered after publication:
record the issue
assess severity
correct urgent risk where authorised
notify the correct owner
route factual or evidence issues to the source owner
route compliance issues to the appropriate specialist
route technical issues to the destination owner
update the asset version
record the correction outcome
Approval Withdrawal
Where approval is withdrawn:
stop publication or delivery where possible
mark the asset Held or Blocked
record the reason
return the asset to the required stage
do not continue using the withdrawn approval
Operator Warnings
Do Not Use This Checklist Before Production Is Complete
Publishing readiness is a late-stage check.
It is not a drafting checklist.
Do Not Treat The Checklist As Approval
A completed checklist does not approve the asset.
Human approval must already exist.
Do Not Review The Wrong Version
The approved version and publishing version must match.
Do Not Allow Material Changes After Approval Without Reapproval
Meaningful post-approval changes require renewed review and approval.
Do Not Treat Publishing-Ready As Published
Publication or delivery remains a separate human-controlled action.
Do Not Invent Missing Details
Unknown destination, ownership, links, evidence or approvals must remain unresolved until confirmed.
Do Not Ignore Blockers
Blocked assets are not ready.
Do Not Let Formatting Introduce New Claims
Titles, metadata, graphics, captions and calls to action must remain within approved boundaries.
Do Not Publish Automatically
The current operating model remains human controlled.
Source-Of-Truth Rule
MCR remains the source of truth for:
Content Brain Canon
Content Brain Architecture
Content Brain Operating Model
Content Brain Workflow Map
Content Brain Publishing Readiness Checklist
Content Brain master frameworks
Content Brain master standards
Content Brain master templates
This operational copy provides practical operator guidance.
It does not replace the controlling MCR source pages.
Supabase Position
Future structured readiness records may be stored in Supabase.
A structured readiness record may include:
asset relationship
asset version
project relationship
destination
production status
editing status
specialist-review status
approval status
publishing-preparation status
readiness decision
blockers
publishing owner
delivery owner
outcome
live destination reference
measurement requirement
review date
archive state
Supabase records must not replace:
the controlling checklist
the approval record
the MCR source-of-truth pages
Plugin And UI Position
A future Publishing Preparation or Publishing Readiness workspace may eventually support:
asset selection
version confirmation
checklist completion
specialist-review confirmation
approval confirmation
destination selection
metadata preparation
link checking
media preparation
blocker recording
final-package creation
readiness decisions
publication or delivery handoff
outcome recording
No Publishing Readiness Checklist UI or publishing automation is authorised by this page.
Manual use must first prove:
the required checklist fields
the optional fields
the destination-specific fields
the status values
the blocker types
the approval checks
the failure paths
the outcome records
Approval Boundaries
Content Brain preserves the following boundaries.
HeadOffice controls governance and major structural decisions.
Strategy Brain controls strategic direction.
Research Brain controls broad research evidence and research truth.
Customer Brain controls approved customer intelligence.
Creative Brain controls approved creative direction where applicable.
Affiliate Brain controls affiliate offer direction and affiliate campaign requirements.
Ads Brain controls advertising campaign execution, testing and optimisation.
Conversion Brain controls conversion strategy.
Compliance Brain controls compliance interpretation and risk decisions.
Finance Brain controls financial and budget authority.
Experimentation Brain controls test validity and interpretation.
Data Brain controls data integrity and trusted measurement.
Content Brain produces, edits and prepares content within approved boundaries.
The authorised human or destination owner controls final publication or delivery.
Relationship To Content Brain Home Operational Copy
Content Brain Home Operational Copy provides the operator starting point.
Publishing readiness appears near the end of the operational workflow.
Relationship To Content Brain Workflow Operational Copy
Content Brain Workflow Operational Copy defines the sequence:
Production
Editing And Quality Control
Specialist Review Where Required
Human Approval
Publishing Preparation
Publishing Readiness
Human-Controlled Publication Or Delivery
This page provides the detailed readiness check.
Relationship To Content Brain Content Brief Template Operational Copy
The Brief Operational Copy defines:
the required asset
the approved sources
the production requirements
the review requirements
the approval owner
the destination
the publishing-preparation requirements
This checklist confirms that those requirements were satisfied.
Relationship To Content Brain Publishing Readiness Checklist
Content Brain Publishing Readiness Checklist remains the controlling MCR checklist.
This operational copy translates the controlling checklist into detailed operator guidance.
Relationship To Content Brain Page Registry
This page should be recorded as:
Page Title: Content Brain Publishing Readiness Checklist Operational Copy
Document Type: Operational Copy
Version: v1.1
Parent Page: Content Brain
Status: Draft
Migration Classification: MCR Only First
Plugin Or UI Candidate: Possible Publishing Preparation And Readiness Workspace Later
Notes: Prepared operational publishing-readiness checklist confirming production, editing, specialist review, human approval, destination preparation, final version control, publishing ownership and outcome recording.
Relationship To Content Brain Copy Map
The controlling Publishing Readiness Checklist is classified as:
Simplify Before Copy
This v1.1 operational copy provides the operator-focused readiness structure.
It remains:
MCR Only First
Not migrated
Not live
Not connected to publishing automation
Relationship To mwmscontentbrain.site
This page is prepared future operator content for mwmscontentbrain.site.
It must not be copied until:
the manual publishing-readiness workflow is validated
the required fields are confirmed
the destination-specific requirements are confirmed
the operational structure is accepted
migration is approved
destination duplication is checked
source links are preserved
the operational page is validated
rollback remains possible
Current Operational Copy Status
Prepared In MCR: Yes
Aligned With Content Brain Canon v1.1: Yes
Aligned With Content Brain Architecture v1.1: Yes
Aligned With Content Brain Operating Model v1.2: Yes
Aligned With Content Brain Workflow Map v1.2: Yes
Aligned With Content Brain Home Operational Copy v1.1: Yes
Aligned With Content Brain Workflow Operational Copy v1.1: Yes
Aligned With Content Brain Content Brief Template Operational Copy v1.1: Yes
Aligned With Content Brain Publishing Readiness Checklist v1.1: Yes
Aligned With Content Brain Page Registry v3.3: Yes
Aligned With Content Brain Copy Map v2.8: Yes
Migrated To mwmscontentbrain.site: No
Live Operational Checklist: No
Connected To Full Plugin Or UI: No
Connected To Publishing Automation: No
Connected To Social Automation: No
Connected To Email Automation: No
Connected To Advertising Deployment: No
Connected To Workers: No
Connected To Queues: No
Connected To AI Employees: No
Connected To Brain Room Routing: No
Connected To M Handoff: No
Research Brain Impact: None
Replacement Page Procedure
Where the existing WordPress page is too large for safe replacement:
create a new WordPress page
use the exact title:
Content Brain Publishing Readiness Checklist Operational Copy
set Parent to:
Content Brain
publish the complete v1.1 replacement
confirm the new page displays correctly
confirm the title is exact
confirm the Parent is Content Brain
confirm the version inside the page is v1.1
confirm only one active page has the exact title
move the old v1.0 page to Trash as recovery
do not permanently delete the old page during replacement validation
Drift Protection
The system must prevent:
this page being treated as live migration
this page replacing the controlling Publishing Readiness Checklist
this page replacing Content Brain Canon
this page replacing Content Brain Architecture
this page overriding Content Brain Workflow Map
this page overriding Content Brain Copy Map
publishing readiness being checked before production is complete
drafts being treated as approved
editing completion being treated as approval
specialist review being omitted where required
human approval being omitted
publishing preparation being omitted
readiness being treated as publication
readiness being treated as delivery
the wrong asset version being published
material post-approval changes bypassing reapproval
unsupported claims being added in titles or metadata
broken links being ignored
required disclosures being omitted
destination ownership remaining unclear
blocked assets being marked ready
automatic publication
automatic social posting
automatic email sending
automatic newsletter sending
automatic ad deployment
worker activation
queue activation
AI Employee activation
Brain Room routing
automatic M handoff
interference with M’s Research Brain work
Architectural Intent
The Content Brain Publishing Readiness Checklist Operational Copy exists to provide the final controlled bridge between approved content and authorised publication or delivery.
Its role is to confirm that the asset has moved correctly through:
production
editing
quality control
specialist review where required
human approval
publishing preparation
It then allows the asset to move to:
human-controlled publication
human-controlled scheduling
human-controlled delivery
authorised handoff
The checklist protects against:
incomplete assets
wrong versions
unsupported claims
missing approval
missing review
broken links
missing metadata
missing disclosures
incorrect destinations
unclear ownership
unrecorded blockers
premature publication
The correct principle is:
confirm readiness
preserve approval
prepare the final package
hand the asset to the authorised human
record what actually happened
Final Rule
Publishing readiness means:
the correct asset
the correct version
production complete
editing complete
specialist review complete where required
human approval complete
approval conditions applied
publishing preparation complete
destination confirmed
ownership confirmed
no unresolved blocker
Publishing readiness does not mean:
published
scheduled
sent
posted
deployed
delivered
Those remain separate human-controlled actions.
Do not publish an unapproved asset.
Do not publish the wrong version.
Do not allow material post-approval changes without renewed approval.
Do not invent missing sources, approvals, links or destination details.
Do not mark a blocked asset ready.
MCR remains the source of truth.
mwmscontentbrain.site remains the future operational environment.
Supabase remains the structured records layer.
Human publication and delivery control remain mandatory.
No publishing automation is authorised.
No social-posting automation is authorised.
No email or newsletter automation is authorised.
No advertising deployment automation is authorised.
No worker is authorised.
No queue execution is authorised.
No AI Employee is authorised.
No Brain Room routing is authorised.
No automatic M handoff is authorised.
M’s Research Brain work remains untouched.
Change Log
Version: v1.1
Date: 2026-06-16
Author: HeadOffice
Change: Rewritten to align the Content Brain Publishing Readiness Checklist Operational Copy with the complete Content Brain request-to-lifecycle workflow.
Repositioned publishing readiness after:
Content Production
Editing And Quality Control
Specialist Review Where Required
Human Approval
Publishing Preparation
Added:
asset identity checks
version control
production-completion checks
editing and quality-control checks
source and evidence checks
claims and compliance checks
specialist-review confirmation
human-approval confirmation
material post-approval change checks
title and naming checks
URL and slug checks
metadata checks
formatting checks
internal-link checks
external-link checks
image and media checks
call-to-action checks
destination checks
website requirements
article requirements
social-content requirements
script-delivery requirements
advertising-content requirements
newsletter and email requirements
manual and documentation requirements
content-pack requirements
refresh requirements
repurposing requirements
merge and retirement requirements
tracking and measurement checks
publishing and delivery ownership
blocker checks
final version control
final publishing package
final readiness decision
outcome recording
publication-failure handling
delivery-failure handling
post-publication error handling
approval-withdrawal handling
future Supabase readiness-record position
future Publishing Preparation and Readiness workspace position
replacement-page procedure
expanded drift protection
Clarified that:
publishing readiness is not publication
publishing readiness is not delivery
checklist completion is not approval
human approval must already exist
the approved version and publishing version must match
material post-approval changes require renewed review and approval
publication and delivery remain human controlled
MCR remains the source of truth
manual workflow remains human controlled
no publishing automation, worker, queue, AI Employee, Brain Room routing or automatic M handoff is authorised
M’s Research Brain work remains untouched
Version: v1.0
Date: 2026-05-24
Author: HeadOffice
Change: Initial creation of Content Brain Publishing Readiness Checklist Operational Copy. Defined the prepared simplified future publishing-readiness checklist for mwmscontentbrain.site, including content, SEO, claims, links, CTA, formatting, approval, handoff and post-publication signal checks.
Change Impact Declaration
Pages Created:
One replacement page using the existing exact title where required by WordPress page-size limits:
Content Brain Publishing Readiness Checklist Operational Copy
Pages Updated:
None where replacement-page creation is required
Pages To Move To Trash After Validation:
Old Content Brain Publishing Readiness Checklist Operational Copy v1.0 page
Pages Permanently Deleted:
None
Pages Deprecated:
Old v1.0 page after the v1.1 replacement is validated and moved to Trash
Registries Requiring Update:
Content Brain Page Registry
Content Brain Copy Map
Canon Version Update Required:
No
Architecture Version Update Required:
No
Operating Model Version Update Required:
No
Workflow Map Version Update Required:
No
Automation Status Change:
No
Plugin Or UI Status Change:
No
Publishing Automation Status Change:
No
Worker Status Change:
No
Queue Status Change:
No
AI Employee Status Change:
No
Brain Room Routing Status Change:
No
M Handoff Required:
No
Research Brain Impact:
None
END CONTENT BRAIN PUBLISHING READINESS CHECKLIST OPERATIONAL COPY v1.1
END OF FULL FILE OUTPUT