Document Type: Checklist
Status: Active
Version: v1.1
Authority: Content Brain Canon
Applies To: All Content Brain Assets Requiring Human Approval, Publishing Preparation, Publication, Delivery Or Handoff
Parent: Content Brain
Enforcement Mode: Operational
Last Reviewed: 2026-06-15
Content Brain Publishing Readiness Checklist
Purpose
The Content Brain Publishing Readiness Checklist defines the required checks before a Content Brain asset is published, delivered, scheduled, handed off or placed into an authorised live system.
It exists to prevent an asset from moving into use merely because:
- a draft exists
- editing appears complete
- a brief was completed
- the asset looks finished
- a specialist reviewed one part
- a publishing destination has been selected
- an operator is ready to move on
An asset is publishing-ready only when it has passed the required checks for:
- source and authority
- objective
- audience
- content action
- asset completeness
- evidence and accuracy
- editing and quality control
- specialist review where required
- human approval
- destination requirements
- formatting
- publishing preparation
- asset relationships
- measurement
- lifecycle follow-up
The Checklist applies after production and editing.
It does not replace:
- content qualification
- content planning
- source collection
- the Content Brief Template
- the Content Production System Framework
- specialist review
- human approval
- publication
- delivery
- lifecycle management
Core Principle
Content is not ready because it exists.
Content is ready when it is:
- complete
- accurate
- supported
- reviewed
- approved
- destination-ready
- traceable
- suitable for its intended use
The required sequence is:
Draft Complete
→ Editing Complete
→ Specialist Review Complete Where Required
→ Human Approval Complete
→ Publishing Preparation Complete
→ Publishing-Ready Or Delivery-Ready
→ Human-Controlled Publication Or Delivery
These states must not be treated as interchangeable.
Scope
This Checklist applies to:
Website Content
- home pages
- about pages
- service pages
- product pages
- category pages
- collection pages
- landing pages
- bridge pages
- pre-sell pages
- advertorials
- affiliate review pages
- comparison pages
- buyer guides
- FAQ pages
- local pages
- authority pages
- pillar pages
- topic hubs
- supporting pages
- onboarding pages
- knowledge-base pages
Article Content
- educational articles
- informational articles
- commercial articles
- affiliate reviews
- comparison articles
- buyer guides
- how-to articles
- list articles
- case studies
- authority articles
- thought-leadership articles
- research-led articles
- search-led articles
- evergreen articles
- refreshed articles
Social Content
- Facebook posts
- Instagram captions
- Instagram carousels
- LinkedIn posts
- X posts
- X threads
- YouTube community posts
- TikTok concepts
- social series
- short-form scripts
- engagement posts
- comment-response content
Scripted Content
- YouTube scripts
- YouTube Shorts scripts
- TikTok scripts
- Instagram Reel scripts
- webinar scripts
- video sales letter scripts
- sales video scripts
- explainer scripts
- educational scripts
- product demonstration scripts
- podcast scripts
- voiceover scripts
- presentation scripts
- training scripts
- advertising scripts
Advertising Content
- headlines
- hooks
- primary ad copy
- descriptions
- search ads
- display ads
- native ads
- YouTube ads
- Meta ads
- TikTok ads
- advertorials
- pre-sell content
- creative briefs
- message-match content
- call-to-action variations
Email And Newsletter Content
- newsletters
- promotional emails
- educational emails
- welcome sequences
- nurture sequences
- launch sequences
- affiliate promotional sequences
- re-engagement sequences
- post-purchase emails
- abandoned-cart emails
- subject lines
- preview text
- email variations
Manuals, Guides And Documentation
- instruction manuals
- user guides
- implementation guides
- playbooks
- standard operating procedures
- reports
- white papers
- ebooks
- workbooks
- checklists
- lead magnets
- onboarding packs
- client documents
- course lessons
- training documents
- knowledge-base content
Content Packs
- website content packs
- affiliate content packs
- launch content packs
- campaign content packs
- social content packs
- email content packs
- documentation packs
- repurposing packs
Existing-Content Work
- refreshes
- expansions
- corrections
- merges
- repurposed assets
- reformatted assets
- internal-linking updates
- retirement preparation
- archive preparation
What This Checklist Does Not Govern
This Checklist does not independently govern:
- offer approval
- campaign approval
- advertising budgets
- bidding decisions
- capital approval
- statistical validation
- broad research authority
- final compliance interpretation
- final legal authority
- plugin implementation
- Supabase implementation
- worker activation
- AI Employee activation
- Brain Room routing
- autonomous publishing
- autonomous social posting
- autonomous newsletter sending
- autonomous email deployment
- autonomous advertising deployment
- automatic M handoff
These remain governed by the relevant Brain, framework, protocol, authority or authorised implementation layer.
Universal Readiness Gate
Every asset must pass the Universal Readiness Gate before it is marked:
- Publishing-Ready
- Delivery-Ready
- Approved For Handoff
- Approved For Scheduling
- Approved For Publication
- Approved For Deployment
The universal questions are:
- Is the source clear?
- Is the content action clear?
- Is the objective clear?
- Is the audience clear?
- Is the asset complete?
- Is the source material sufficient?
- Are facts and claims supported?
- Has editing been completed?
- Has specialist review been completed where required?
- Has human approval been recorded?
- Is the destination confirmed?
- Is the format correct?
- Are required related assets present?
- Is the version confirmed?
- Are publication or delivery instructions complete?
- Is measurement or follow-up defined where required?
If any required answer is no, the asset is not ready.
Readiness Status Model
Use only one current readiness status.
Available statuses are:
- Draft Complete
- In Editing
- Revision Required
- Waiting For Sources
- Waiting For Evidence
- Waiting For Specialist Review
- Specialist Changes Required
- Waiting For Human Approval
- Human Changes Required
- Approved
- Publishing Preparation
- Publishing-Ready
- Delivery-Ready
- Scheduled
- Published
- Delivered
- Publication Failed
- Delivery Failed
- Held
- Rejected
- Cancelled
- Archived
The following states must not be merged:
- Draft Complete
- Editing Complete
- Specialist Review Complete
- Approved
- Publishing-Ready
- Published
- Delivered
Stage 1: Source And Authority Check
Confirm where the asset came from and why it exists.
Required checks:
- originating request identified
- requesting human or Brain identified
- project identified where relevant
- content action identified
- content owner identified
- approval owner identified
- relevant specialist authority identified
- related offer identified where relevant
- related campaign identified where relevant
- related product identified where relevant
- related website identified where relevant
- related source asset identified where relevant
Possible content actions include:
- create
- refresh
- expand
- correct
- merge
- repurpose
- reformat
- relink
Pass condition:
The asset has a clear source, approved reason and known authority.
Fail condition:
The asset was created without a clear request, source, purpose or authority.
Failure action:
Return the asset to:
- request clarification
- project definition
- content-action review
- source verification
Stage 2: Objective And Audience Check
Confirm the asset has a defined job and audience.
Required checks:
- primary objective confirmed
- secondary objective confirmed where relevant
- audience confirmed
- audience stage confirmed
- intent confirmed
- destination role confirmed
- expected audience outcome confirmed
- expected business outcome confirmed
- call to action confirmed where relevant
- content type matches the objective
- channel matches the audience
- tone matches the audience
Pass condition:
The asset clearly serves a known audience and objective.
Fail condition:
The asset is generic, unfocused, written for everyone or disconnected from its intended use.
Failure action:
Return to:
- brief
- production instruction
- angle
- audience definition
- asset planning
Stage 3: Content Action Check
Confirm the final asset reflects the approved action.
Create
Confirm the asset is genuinely new and does not duplicate suitable existing content.
Refresh
Confirm useful existing material has been preserved where appropriate and outdated material has been updated.
Expand
Confirm the asset adds useful depth rather than unnecessary volume.
Correct
Confirm the identified factual, structural, compliance or clarity problem has been resolved.
Merge
Confirm useful material from all selected assets has been preserved and duplicate material removed.
Repurpose
Confirm the derivative asset remains faithful to the approved source while fitting the new channel.
Reformat
Confirm the content has been adapted correctly to the new format.
Relink
Confirm the required internal links, calls to action or asset relationships have been improved.
Pass condition:
The asset fulfils the approved action.
Fail condition:
The final asset drifted into a different task.
Failure action:
Return to production revision.
Stage 4: Asset Completeness Check
Confirm all required components are present.
Universal checks:
- title present
- core content complete
- opening present where required
- body structure complete
- closing present where required
- CTA present where required
- required sections present
- required evidence present
- required disclosures present
- required links present
- required metadata present
- required notes present
- required files present
- required variations present
- required supporting assets present
- no placeholder text remains
- no unfinished sections remain
- no missing asset is being hidden
Pass condition:
The asset is complete for its intended destination.
Fail condition:
The asset is only partially complete or still contains placeholders, missing components or incomplete instructions.
Failure action:
Return to production or content assembly.
Stage 5: Brief Or Production Instruction Alignment Check
Confirm the asset matches the approved instruction level.
The asset may have been produced from:
- Full Content Brief
- Short Production Brief
- Outline Or Blueprint
- Direct Production Instruction
Required checks:
- approved purpose followed
- approved audience followed
- approved content action followed
- approved asset type followed
- approved destination followed
- approved structure followed
- required questions answered
- required evidence included
- required objections addressed
- required CTA followed
- compliance boundaries respected
- completion standard met
Pass condition:
The final asset follows the approved production instruction.
Fail condition:
The asset introduces unapproved direction or ignores required elements.
Failure action:
Revise the asset or deliberately update the production instruction before continuing.
Stage 6: Source Evidence And Accuracy Check
Content must not contain unsupported or invented material.
Required checks:
- source material reviewed
- product details checked
- offer details checked
- business details checked
- names checked
- dates checked
- statistics checked
- numerical claims checked
- quoted material checked
- customer language checked
- research findings checked
- technical statements checked
- legal or compliance-sensitive statements checked
- no fabricated source added
- no fake testimonial added
- no invented customer experience added
- no invented product capability added
- no exaggerated result added
- no unsupported guarantee added
- no unapproved scarcity added
- no unsupported urgency added
Pass condition:
Material facts, claims and evidence are traceable to approved sources or clearly identified as interpretation.
Fail condition:
The asset contains statements that cannot be supported or verified.
Failure action:
- revise
- remove the statement
- request research
- request product verification
- request offer verification
- request specialist review
- hold the asset
Stage 7: Editing And Quality-Control Check
Confirm the asset has completed editing.
Required checks:
- structural editing completed
- developmental editing completed where required
- clarity improved
- readability checked
- repetition reduced
- weak filler removed
- vague statements corrected
- headings improved
- flow improved
- transitions improved
- voice aligned
- tone aligned
- audience alignment confirmed
- intent alignment confirmed
- channel fit confirmed
- CTA improved
- trust improved
- claim language controlled
- duplication checked
- formatting checked
- completeness checked
- spelling and grammar reviewed
- brand terminology checked
- information gain checked where relevant
The asset should be:
- clear
- specific
- useful
- readable
- well structured
- non-generic
- complete
- appropriately detailed
- free from avoidable repetition
- free from empty claims
- suitable for the intended channel
Pass condition:
The asset has completed editing and meets the required quality standard.
Fail condition:
The asset remains generic, thin, unclear, repetitive, incomplete or poorly structured.
Failure action:
Return to editing or production revision.
Stage 8: Trust And Transparency Check
Content must support trust rather than hype.
Required checks:
- tone is balanced
- claims are proportionate
- evidence is not overstated
- limitations are included where relevant
- audience expectations are managed
- disclosure requirements are met
- affiliate relationships are disclosed where required
- comparisons are fair
- uncertainty is not hidden
- unsupported authority language is removed
- false urgency is removed
- manipulative pressure is controlled
- promises do not exceed evidence
- the asset does not imply guaranteed outcomes unless authorised and supportable
Pass condition:
The asset is credible, transparent and appropriately persuasive.
Fail condition:
The asset relies on hype, pressure, vague promises or overstated proof.
Failure action:
Revise or escalate for compliance review.
Stage 9: Compliance And Specialist Review Check
Specialist review is required where material risk exists.
Possible specialist reviews include:
- compliance
- legal
- factual
- technical
- medical
- financial
- product
- offer
- strategy
- campaign
- brand
- client
- stakeholder
High-risk areas may include:
- health claims
- pain claims
- disease claims
- medical advice
- finance claims
- income claims
- investment claims
- legal claims
- safety claims
- product performance claims
- guarantee language
- scarcity
- urgency
- testimonials
- before-and-after claims
- affiliate disclosures
- comparative claims
- employment claims
- environmental claims
Required checks:
- risk level classified
- sensitive statements identified
- specialist review requirement confirmed
- specialist review completed where required
- requested specialist changes completed
- evidence requirements met
- disclosures included
- review decision recorded
- unresolved risk removed or held
Pass condition:
Required specialist review has been completed and all mandatory changes have been resolved.
Fail condition:
The asset contains unresolved specialist risk or required review has not occurred.
Failure action:
Hold publication or delivery.
Stage 10: Human Approval Check
Human approval remains required under the current operating model.
Required checks:
- approval owner identified
- correct version reviewed
- approval decision recorded
- requested changes completed
- final version confirmed
- approval date recorded where required
- destination approved
- publication or delivery authority confirmed
Available approval decisions:
- Approved
- Approved With Minor Changes
- Changes Required
- Evidence Required
- Specialist Review Required
- Held
- Rejected
- Cancelled
Pass condition:
An authorised human has approved the correct final version.
Fail condition:
The asset has not received human approval or the approved version differs from the publishing version.
Failure action:
Return to human review.
Stage 11: Version And Final Asset Check
Confirm the asset being prepared is the correct version.
Required checks:
- final version number or date confirmed
- old drafts clearly separated
- approved version identified
- duplicate files checked
- file names correct
- page title correct
- asset title correct
- destination copy matches approved copy
- no accidental old text remains
- no unresolved comments remain
- no tracked changes remain where inappropriate
- no hidden placeholder remains
- no temporary instructions remain
- no internal notes remain in public-facing content
Pass condition:
The correct approved asset is being prepared.
Fail condition:
Version uncertainty exists.
Failure action:
Hold and reconcile versions.
Stage 12: Destination And Formatting Check
Confirm the asset fits its destination.
Possible destinations include:
- WordPress
- website page
- landing page
- affiliate support page
- ecommerce store
- email platform
- newsletter platform
- social platform
- video production
- audio production
- advertising platform
- training system
- client delivery
- internal knowledge system
- document library
- manual delivery
- operator handoff
Required checks:
- destination confirmed
- publishing owner confirmed
- delivery owner confirmed
- platform requirements checked
- file format correct
- length appropriate
- dimensions checked where relevant
- character limits checked
- heading structure checked
- mobile presentation considered
- accessibility requirements considered
- links checked
- embedded elements checked
- image requirements checked
- alt text prepared
- captions prepared where required
- metadata prepared
- disclosures positioned correctly
- CTA placement checked
- date and timing confirmed
- destination permissions confirmed where relevant
Pass condition:
The asset is correctly formatted for the intended destination.
Fail condition:
The asset is approved but not yet suitable for its destination.
Failure action:
Return to publishing preparation.
Stage 13: Publishing Preparation Check
Publishing Preparation must be complete before the asset is marked Publishing-Ready.
Required checks:
- final title confirmed
- URL or slug guidance confirmed where relevant
- heading structure confirmed
- metadata confirmed
- description confirmed
- featured image requirement confirmed
- image assets confirmed
- alt text confirmed
- internal links confirmed
- external links confirmed
- CTA placement confirmed
- disclosures confirmed
- compliance notes confirmed
- formatting complete
- platform variation complete
- destination confirmed
- publishing checklist complete
- rollback or correction route understood where required
- publication timing confirmed
- operator instructions complete
Pass condition:
The asset can be published or delivered by an authorised human without further content work.
Fail condition:
Additional preparation is required.
Failure action:
Keep status as Publishing Preparation.
Stage 14: Asset Relationship Check
Confirm the asset fits correctly with related content.
Required checks:
- project relationship confirmed
- related asset links confirmed
- campaign relationship confirmed
- website relationship confirmed
- parent and child page relationships confirmed where relevant
- content-pack relationship confirmed where relevant
- message consistency checked
- CTA consistency checked
- offer consistency checked
- source consistency checked
- internal-link consistency checked
- duplicate-content risk checked
- conflicting statements checked
- sequence position confirmed where relevant
Pass condition:
The asset works correctly with related assets.
Fail condition:
The asset conflicts with or duplicates related work.
Failure action:
Return to project, asset-planning or editing review.
Stage 15: Content Pack Readiness Check
Use this stage when several assets form one coordinated content pack.
Required checks:
- central objective confirmed
- all required assets present
- production order complete
- shared message consistent
- shared evidence consistent
- individual channel adaptations complete
- CTAs coordinated
- asset naming consistent
- destination order confirmed
- approval status confirmed for each asset
- missing asset check complete
- pack-level review completed
- individual asset review completed
- publishing or delivery sequence confirmed
- pack-level measurement defined where relevant
Pass condition:
The complete content pack is ready.
Fail condition:
One or more required assets remain missing, inconsistent, unapproved or unprepared.
Failure action:
Hold the pack or release only the specifically approved independent assets.
Stage 16: Internal-Linking Check
Use where internal linking is relevant.
Required checks:
- required links included
- pillar-page links included where relevant
- topic-cluster links included where relevant
- supporting links included
- trust links included
- offer links included where appropriate
- affiliate links correctly handled
- anchor text natural
- links support the audience
- broken links checked
- excessive money-page pushing avoided
- link destination correct
- no accidental staging or test links remain
Pass condition:
Internal linking supports the reader and site structure.
Fail condition:
Links are missing, broken, forced or misleading.
Failure action:
Revise the linking plan.
Stage 17: External-Link And Citation Check
Use where external sources or citations are required.
Required checks:
- external sources verified
- source relevance confirmed
- source authority considered
- source date considered
- claims match the source
- links point to the correct material
- citations formatted correctly
- no fabricated citation exists
- no irrelevant citation added
- no source is misrepresented
- no excessive quotation exists
- source limitations understood
Pass condition:
External evidence is accurate, relevant and correctly represented.
Fail condition:
Citations are missing, weak, incorrect or misleading.
Failure action:
Correct, replace or remove the unsupported material.
Stage 18: Measurement And Feedback Check
Meaningful content should have an appropriate feedback path.
Required checks:
- primary signal identified
- secondary signal identified where relevant
- review timing defined
- measurement owner identified
- relevant Brain or human identified
- refresh trigger defined where relevant
- repurposing trigger defined where relevant
- expansion trigger defined where relevant
- correction trigger defined
- retirement trigger defined where relevant
- no-action condition defined where relevant
Possible signals include:
- traffic
- rankings
- impressions
- engagement
- click-through rate
- conversion support
- email opens
- email clicks
- social response
- video retention
- lead generation
- sales contribution
- content decay
- factual issues
- compliance issues
- customer feedback
- stakeholder feedback
Pass condition:
The asset has an appropriate review or feedback path.
Fail condition:
The content enters use with no ownership or follow-up where follow-up is required.
Failure action:
Add a lifecycle or measurement note.
Stage 19: Publication Or Delivery Record Check
Before or immediately after publication or delivery, record:
- asset title
- asset type
- project
- originating request
- content action
- version
- approving human
- destination
- publishing or delivery owner
- publication or delivery date
- publication status
- delivery status
- related assets
- measurement requirement
- review date
- refresh requirement
- archive state
Repeatable publication and delivery records should eventually be stored as structured records.
They should not require a new WordPress page for each asset.
Asset-Specific Module: Website Page
Use these checks for website pages.
- page purpose confirmed
- page position confirmed
- parent page confirmed
- page relationships checked
- headline confirmed
- value proposition confirmed
- CTA confirmed
- page hierarchy checked
- internal links checked
- metadata checked
- URL checked
- duplicate-page risk checked
- mobile readability checked
- form or button destinations checked
- existing-page replacement plan confirmed
- redirect need confirmed
- cross-page consistency checked
Asset-Specific Module: Article
Use these checks for articles.
- article objective confirmed
- audience intent confirmed
- topic coverage complete
- title confirmed
- introduction effective
- sections complete
- key questions answered
- evidence checked
- examples checked
- internal links checked
- external sources checked
- information gain confirmed
- duplicate-content risk checked
- metadata prepared
- CTA confirmed
- refresh review date considered
Asset-Specific Module: Social Content
Use these checks for social content.
- platform confirmed
- platform format correct
- hook suitable
- message clear
- length within limits
- tone suitable
- CTA suitable
- visual requirement confirmed
- hashtags reviewed where relevant
- links correct
- claim language checked
- source meaning preserved
- scheduling owner confirmed
- platform-specific version prepared
- no generic cross-platform copying remains
Asset-Specific Module: Script
Use these checks for scripts.
- script type confirmed
- platform confirmed
- duration checked
- hook complete
- opening complete
- structure complete
- pacing reviewed
- spoken language reviewed
- scene guidance complete where required
- shot guidance complete where required
- on-screen text complete
- evidence and claims checked
- CTA confirmed
- closing complete
- production owner confirmed
- recording or production notes complete
Asset-Specific Module: Advertising Content
Use these checks for advertising assets.
- campaign requirement confirmed
- Ads Brain or authorised human requirement confirmed
- offer confirmed
- audience confirmed
- platform confirmed
- angle confirmed
- test requirement confirmed
- claims checked
- compliance boundaries checked
- destination confirmed
- message match checked
- CTA checked
- variation labels clear
- creative requirements complete
- disclosure requirements complete
- no unapproved urgency remains
- no unapproved guarantee remains
- ad deployment remains human controlled
Asset-Specific Module: Newsletter And Email
Use these checks for newsletters and email assets.
- audience or list confirmed
- email type confirmed
- sequence position confirmed
- subject line confirmed
- preview text confirmed
- opening confirmed
- body complete
- CTA confirmed
- links checked
- personalisation fields checked
- sender requirements confirmed
- compliance and disclosure checked
- sending owner confirmed
- schedule confirmed
- sequence logic checked
- follow-up logic checked
- measurement requirements defined
- sending remains human controlled
Asset-Specific Module: Manual Guide Or Documentation
Use these checks for manuals, guides and documentation.
- user or reader confirmed
- required outcome confirmed
- authoritative source confirmed
- prerequisites included
- steps complete
- sequence correct
- warnings included
- dependencies included
- examples included where required
- troubleshooting included where required
- technical review complete
- factual review complete
- completion criteria clear
- document format correct
- version shown
- update owner identified
- review date identified
- delivery owner confirmed
Asset-Specific Module: Refresh
Use these checks for refreshed content.
- refresh trigger confirmed
- refresh scope confirmed
- useful material preserved
- outdated material removed or corrected
- new evidence checked
- new sections complete
- offer or product changes reflected
- compliance changes reflected
- internal links updated
- metadata updated
- CTA updated where required
- publication date handling confirmed
- old version preserved where required
- measurement restart or comparison defined
Asset-Specific Module: Merge
Use these checks for merged content.
- primary asset confirmed
- secondary assets identified
- useful material preserved
- duplicate material removed
- conflicting material resolved
- final structure complete
- internal links updated
- redirect requirements confirmed
- retirement requirements confirmed
- archive requirements confirmed
- publication sequence confirmed
- old assets not removed before final validation
Asset-Specific Module: Repurposing
Use these checks for repurposed content.
- source asset identified
- source asset approved
- source meaning preserved
- evidence preserved correctly
- new audience confirmed
- new channel confirmed
- new format confirmed
- structure adapted
- length adapted
- tone adapted
- hook created for new channel
- CTA adapted
- visual requirements adapted
- claims not expanded
- relationship to original asset recorded
- destination confirmed
Affiliate Content Readiness Module
Use where the asset supports an affiliate offer.
Required checks:
- offer status clear
- Affiliate Brain authority confirmed
- source material checked
- funnel stage confirmed
- audience stage confirmed
- claim risk checked
- disclosure included where required
- pre-sell role confirmed
- vendor-page relationship confirmed
- VSL relationship confirmed where relevant
- no unsupported product claims
- no fake testimonial
- no fake urgency
- no unapproved price statement
- no unapproved guarantee
- CTA matches the funnel role
- message match confirmed
- human approval recorded
Pass condition:
The asset safely supports an authorised or clearly identified affiliate use.
Fail condition:
The asset promotes an unclear, unsupported or unapproved offer.
Conversion-Support Readiness Module
Use where the asset supports a conversion pathway.
Required checks:
- message match confirmed
- audience stage confirmed
- CTA suitable
- objections addressed
- trust support included
- next step clear
- ad-to-page consistency checked where relevant
- page-to-offer consistency checked
- expectations controlled
- no false promise added
- no confusing structure remains
- Conversion Brain authority respected
Standard Final Readiness Decision
Assign one final decision.
Available decisions:
- Approved For Publishing
- Approved For Delivery
- Approved For Scheduling
- Approved For Handoff
- Approved With Minor Formatting Changes
- Hold For Revision
- Hold For Missing Assets
- Hold For Evidence
- Hold For Specialist Review
- Hold For Compliance Review
- Hold For Human Approval
- Hold For Destination Confirmation
- Hold For Publishing Preparation
- Rejected
- Cancelled
The decision must include:
Asset Title:
Asset Type:
Project:
Version:
Decision:
Decision Date:
Decision Owner:
Outstanding Actions:
Publishing Or Delivery Owner:
Destination:
Risk Level:
Next Action:
Minimum Publishing Readiness Checklist
Use this only for simple, low-risk assets.
Confirm:
- source clear
- purpose clear
- audience clear
- content action clear
- asset complete
- production instruction followed
- facts checked
- claims checked
- editing complete
- trust checked
- compliance risk checked
- specialist review complete where required
- human approval complete
- final version confirmed
- destination confirmed
- format correct
- CTA correct where required
- links checked where required
- publishing preparation complete
- feedback path defined where required
If any required item fails, do not publish or deliver the asset.
Required Handoff Note
Where the asset is handed to another authorised human or operational layer, include:
Content Title:
Asset Type:
Project:
Originating Request:
Source Human Or Brain:
Content Action:
Intended Use:
Target Destination:
Version:
Approval Status:
Risk Level:
Specialist Review Status:
Internal Links Required:
External Sources Required:
Formatting Notes:
Publishing Notes:
Feedback Signal:
Next Owner:
Handoff Date:
Outstanding Action:
Publication Failure Or Delivery Failure
If publication or delivery fails:
- do not mark the asset Published or Delivered
- record the failure
- preserve the approved asset
- identify whether the failure is technical, formatting, permission, destination or content-related
- return the work to the correct stage
- do not rewrite approved content unless necessary
- confirm whether approval remains valid after any required change
- record the final corrected outcome
Possible statuses:
- Publication Failed
- Delivery Failed
- Returned To Publishing Preparation
- Returned To Editing
- Returned To Human Approval
- Held
Current Manual Operating Boundary
Current publication and delivery remain human controlled.
The Checklist does not authorise:
- autonomous WordPress publication
- autonomous website changes
- autonomous social posting
- autonomous social scheduling
- autonomous newsletter sending
- autonomous email deployment
- autonomous advertising deployment
- autonomous document delivery
- autonomous client delivery
- autonomous ecommerce publication
- autonomous training delivery
- worker execution
- AI Employee execution
- Brain Room routing
- automatic M handoff
An authorised human must complete or approve the final publishing or delivery action.
Future Plugin Or UI Position
This Checklist may later support:
- publishing-readiness screen
- content QA panel
- specialist-review status
- human-approval gate
- publishing-preparation workspace
- destination checklist
- content-pack readiness view
- refresh approval
- affiliate-content review
- publication-status tracking
- delivery-status tracking
- failure and correction handling
Manual use must prove:
- required fields
- required statuses
- required approval points
- required failure states
- required destination checks
before plugin or UI implementation begins.
Relationship To Content Brain Content Brief Template
The Content Brief Template defines the job before production.
This Checklist confirms whether the produced asset is ready after production, editing and approval.
Content Brief Template = pre-production definition
Publishing Readiness Checklist = pre-publication and pre-delivery gate
Relationship To Content Brain Content Production System Framework
The Content Production System Framework governs how the asset is produced, edited, reviewed and prepared.
This Checklist verifies that the production process has resulted in a complete destination-ready asset.
Relationship To Content Brain Workflow Map
The Workflow Map defines the full movement of work.
This Checklist governs:
- specialist-review completion
- human-approval completion
- publishing preparation
- publishing-ready status
- delivery-ready status
- handoff
- publication or delivery outcome
Relationship To Content Brain Copy Map
This page is classified as:
Classification: Simplify Before Copy
Source Of Truth: MCR
Future Operational Use: Publishing Readiness Checklist, Human Approval Gate And Publishing Preparation Workspace
Future Plugin Or UI: Possible Publishing Readiness Module
No plugin or UI implementation is authorised by this Checklist.
Relationship To mwmscontentbrain.site
A simplified operational version may later support:
- universal readiness checks
- asset-specific checks
- specialist-review status
- human approval
- destination preparation
- version confirmation
- publishing owner
- delivery owner
- final decision
- failure handling
- lifecycle handoff
The operational version must not replace the MCR source.
Relationship To Other MWMS Documents
This page must remain aligned with:
- Content Brain Canon
- Content Brain Architecture
- Content Brain Operating Model
- Content Brain Workflow Map
- Content Brain Page Registry
- Content Brain Copy Map
- Content Brain Content Production System Framework
- Content Brain Content Brief Template
- 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 Protocol
- MWMS Document Structure Standard
- MWMS Page Naming Standard
- MWMS AI Output Standard Full File Delivery Rule
Drift Protection
The system must prevent:
- publishing because a draft exists
- publishing before editing is complete
- publishing before specialist review is complete
- publishing before human approval
- publishing the wrong version
- publishing with missing assets
- publishing incomplete content packs
- publishing unsupported claims
- publishing fabricated sources
- publishing fake testimonials
- publishing generic low-value content
- publishing thin content
- publishing content with unclear purpose
- publishing content with unclear audience
- publishing content with no destination
- publishing content with no owner
- publishing content without formatting checks
- publishing content with broken links
- publishing content without required disclosures
- publishing content with internal notes or placeholders
- treating Publishing-Ready as Published
- treating Delivery-Ready as Delivered
- treating approval as publication
- bypassing Compliance Brain
- bypassing Affiliate Brain authority
- bypassing Conversion Brain authority
- bypassing human approval
- forcing SEO checks onto unrelated content
- forcing affiliate checks onto unrelated content
- using one large checklist where the minimum version is sufficient
- using the minimum version for high-risk or complex work
- building a checklist UI before manual use proves the requirements
- autonomous publishing
- autonomous delivery
- automatic M handoff
- interference with M’s Research Brain work
Architectural Intent
The Content Brain Publishing Readiness Checklist exists to create a reliable control point between:
- production
- editing
- review
- approval
- publishing preparation
- publication or delivery
Its role is to ensure that Content Brain assets enter use only when they are:
- complete
- accurate
- supported
- reviewed
- approved
- correctly formatted
- correctly versioned
- correctly related to other assets
- ready for their intended destination
- connected to a lifecycle or feedback path where required
The Checklist must support:
- simple individual assets
- complex individual assets
- websites
- articles
- social content
- scripts
- advertising
- newsletters
- email sequences
- manuals
- guides
- documentation
- content packs
- refreshes
- merges
- repurposed content
It must support current human-controlled publishing and later controlled operational interfaces.
It must not authorise autonomous publishing.
Final Rule
Content is not ready because drafting is complete.
Content is not ready because editing is complete.
Content is not ready because specialist review is complete.
Content is not ready because human approval exists.
Content becomes Publishing-Ready or Delivery-Ready only when:
- the correct approved version is complete
- required evidence is confirmed
- required editing is complete
- required specialist review is complete
- human approval is recorded
- destination requirements are complete
- publishing preparation is complete
- required related assets are ready
- ownership and next action are clear
Publishing-Ready is not Published.
Delivery-Ready is not Delivered.
An authorised human must complete or approve the final publication or delivery action.
Change Log
v1.1 — 2026-06-15
Replaced the original narrow publishing checklist with a complete publishing-readiness and delivery-readiness control system.
Expanded the Checklist to include:
- universal readiness gate
- readiness status model
- source and authority checks
- objective and audience checks
- content-action checks
- asset-completeness checks
- production-instruction alignment
- source, evidence and accuracy checks
- editing and quality-control checks
- trust and transparency checks
- compliance and specialist-review checks
- human-approval checks
- version checks
- destination and formatting checks
- publishing-preparation checks
- asset-relationship checks
- content-pack readiness
- internal-link checks
- external-link and citation checks
- measurement and feedback checks
- publication and delivery records
- publication and delivery failure handling
Added asset-specific readiness modules for:
- website pages
- articles
- social content
- scripts
- advertising content
- newsletters
- email sequences
- manuals
- guides
- documentation
- refreshes
- merges
- repurposed content
Expanded affiliate and conversion-support checks.
Clarified the difference between:
- Draft Complete
- Editing Complete
- Specialist Review Complete
- Approved
- Publishing-Ready
- Delivery-Ready
- Published
- Delivered
Aligned this Checklist with:
- Content Brain Canon v1.1
- Content Brain Architecture v1.1
- Content Brain Operating Model v1.2
- Content Brain Workflow Map v1.2
- Content Brain Content Production System Framework v1.1
- Content Brain Content Brief Template v1.2
- Content Brain Page Registry v3.1
- Content Brain Copy Map v2.6
v1.0 — 2026-05-06
Initial creation of the Content Brain Publishing Readiness Checklist.
Defined the original readiness gate for:
- content publication
- content handoff
- affiliate support content
- SEO content
- trust review
- compliance sensitivity
- destination control
- approval ownership
- feedback paths
Change Impact Declaration
Pages Created:
None
Pages Updated:
Content Brain Publishing Readiness Checklist
Pages Deprecated:
None
Registries Requiring Update:
Content Brain Page Registry should show Content Brain Publishing Readiness Checklist v1.1.
Content Brain Copy Map should show Content Brain Publishing Readiness Checklist v1.1 where a version is recorded.
Canon Version Update Required:
No
Automation Status Change:
No
Plugin Or UI Status Change:
No
Worker Status Change:
No
AI Employee Status Change:
No
M Handoff Required:
No
Research Brain Impact:
None
END CONTENT BRAIN PUBLISHING READINESS CHECKLIST v1.1