Brain Name: Content Brain
Document Type: Migration Plan
Status: Draft
Version: v1.0
Authority: Content Brain under HeadOffice governance
Applies To: Content Brain MCR structure, Content Brain operational migration planning, mwmscontentbrain.site first-version planning, Content Brain manual workflow design, operational page simplification, migration sequencing, and future Content Brain plugin or UI readiness
Parent: Content Brain
Last Reviewed: 2026-05-24
Content Brain Operational Migration Plan
Purpose
The Content Brain Operational Migration Plan defines the first practical operating version of Content Brain on mwmscontentbrain.site.
This plan exists to decide what should be copied, simplified, transformed, delayed, or held in MCR before Content Brain becomes an operational Brain site.
The purpose is not to build plugin systems, dashboards, automation, Supabase tables, or UI screens.
The purpose is to define the first usable manual version of Content Brain so an operator can work with:
content opportunities
content briefs
SEO content
affiliate product content packs
affiliate funnel support
publishing readiness
repurposing
refresh planning
internal linking
content quality checks
manual signal feedback
This page protects Content Brain from becoming a messy duplicate of MCR.
MCR remains the source of truth.
mwmscontentbrain.site should become the practical operator environment.
Scope
This migration plan applies to:
Content Brain MCR pages
Content Brain operational pages
Content Brain checklists
Content Brain templates
Content Brain workflow maps
Content Brain affiliate support pages
Content Brain SEO and authority pages
Content Brain repurposing pages
Content Brain refresh pages
Content Brain migration planning
future mwmscontentbrain.site structure
manual Content Brain workflow
future plugin or UI planning
This migration plan does not apply to:
live plugin development
Supabase schema creation
Brain Room routing
cross-brain automation
HeadOffice reporting build
Affiliate Brain wiring
Research Brain wiring
Finance Brain wiring
Ads Brain campaign setup
Experimentation Brain test routing
mwmsbrain.site plugin work
M’s active build work
Those remain out of scope.
Core Rule
Content Brain must move in this order:
MCR structure first.
Stability check second.
Migration plan third.
Operational simplification fourth.
Manual mwmscontentbrain.site version fifth.
Plugin or UI only later after repeated manual use proves the need.
No Content Brain page should be copied to mwmscontentbrain.site just because it exists in MCR.
Only pages with clear operator value should move first.
Current Starting Status
Content Brain current status:
Stability Checked / Migration Not Started
Confirmed control pages:
Content Brain Page Registry v2.5
Content Brain Copy Map v2.0
Content Brain Stability And Migration Readiness Checklist v1.0
Confirmed migration rule:
Do not migrate until the first migration group is reviewed and each page has a clear operational purpose.
Confirmed build boundary:
No plugin/UI build yet.
No Supabase build yet.
No Brain Room routing yet.
No cross-brain automation yet.
No interference with M’s active build.
Migration Objective
The first version of mwmscontentbrain.site should help an operator answer:
What content work should be done?
Why should it be done?
Which Brain requested it?
What is the content type?
What research or approval is required?
What template should be used?
What checklist must be completed?
Where does the finished content go?
What signal should be watched after use?
The first version should support manual work before automation.
First Version Operating Principle
The first operational version of Content Brain should be simple, useful, and operator-friendly.
It should not be a full MCR archive.
It should not expose every governance page.
It should not overwhelm the operator with long architecture pages.
It should provide the working pages needed to:
plan
brief
draft
review
publish
repurpose
refresh
handoff
track learning manually
First Operational Site Structure
The recommended first mwmscontentbrain.site structure is:
Dashboard / Home
Content Workflow
Content Briefs
Affiliate Content Packs
Affiliate Funnel Support
SEO And Authority
Publishing Readiness
Repurposing
Refresh
Internal Linking
Signal Feedback
Reference
This is a planning structure only.
Do not build the site menu yet until the migration sequence is approved.
First Migration Group
The first migration group should be drawn from the Content Brain Copy Map.
Recommended first migration group:
Content Brain
Content Brain Workflow Map
Content Brain Content Production System Framework
Content Brain SEO Content Brief Standard
Content Brain Content Brief Template
Content Brain Publishing Readiness Checklist
Content Brain Affiliate Product Content Pack Checklist
Content Brain Topic Architecture Framework
Content Brain Topic Cluster And Hub Architecture Framework
Content Brain Intent Alignment Framework
Content Brain Information Gain Framework
Content Brain E E A T Content Trust Framework
Content Brain Content Optimization Framework
Content Brain SEO Testing And Refresh Framework
Content Brain Internal Linking Strategy Framework
Content Brain Content Repurposing Framework
Content Brain Conversion Support Framework
Content Brain Affiliate Funnel Support Map
Content Brain Affiliate Product Content Pack Framework
These should not all be copied blindly.
Each page must be simplified or transformed according to its operational role.
Pages To Copy First As Operator Pages
The strongest first operator pages are:
Content Brain
Content Brain Workflow Map
Content Brain Content Brief Template
Content Brain Publishing Readiness Checklist
Content Brain Affiliate Product Content Pack Checklist
Content Brain Affiliate Funnel Support Map
Content Brain SEO Content Brief Standard
Content Brain Internal Linking Strategy Framework
Content Brain Content Repurposing Framework
Content Brain SEO Testing And Refresh Framework
These pages provide the basic manual operating system for Content Brain’s first operational version.
Pages To Simplify Before Copying
The following pages should be simplified before being copied to mwmscontentbrain.site:
Content Brain Workflow Map
Content Brain Affiliate Funnel Support Map
Content Brain Affiliate Product Content Pack Framework
Content Brain Content Production System Framework
Content Brain SEO Content Brief Standard
Content Brain Topic Architecture Framework
Content Brain Topic Cluster And Hub Architecture Framework
Content Brain Intent Alignment Framework
Content Brain Information Gain Framework
Content Brain E E A T Content Trust Framework
Content Brain Content Optimization Framework
Content Brain SEO Testing And Refresh Framework
Content Brain Internal Linking Strategy Framework
Content Brain Content Repurposing Framework
Content Brain Conversion Support Framework
Reason:
These pages may contain governance, architecture, long relationship sections, change logs, or MCR-specific explanations that are useful in MCR but too heavy for an operator site.
The operational copies should focus on:
what to do
when to use it
what inputs are required
what output is expected
what checklist applies
where to hand off
what not to decide
Pages To Keep MCR Only
The following pages should remain MCR only:
Content Brain Canon
Content Brain Architecture
Content Brain Page Registry
Content Brain Copy Map
Content Brain Stability And Migration Readiness Checklist
Content Brain Operational Migration Plan
Reason:
These are authority, structure, registry, migration control, readiness-control, or migration-planning pages.
They should not become normal operating pages on mwmscontentbrain.site.
A short reference summary may be created later if needed.
Pages To Copy Later
The following should wait until the first manual workflow is stable:
Content Brain Operating Model
Content Brain Content Signal Feedback Framework
Content Brain Page Registry summary version
Reason:
These are useful, but not essential for the first operator version.
They can be copied later as simplified reference pages after the first operational version is usable.
Later Plugin Or UI Only
The following should not be copied as normal pages.
They should remain future plugin or UI planning items:
Content Brain Content Opportunity Queue Specification
Content Brain Content Production Queue Specification
Content Brain Content Refresh Queue Specification
Content Brain Repurposing Queue Specification
Content Brain Content Operations Dashboard Specification
Reason:
These are specifications for future structured systems.
They should not be mistaken for live dashboards or queues.
They should become UI only after manual workflow proves the need.
Recommended First Menu Structure
Dashboard / Home
Purpose:
Give the operator a simple overview of what Content Brain does.
Should include:
what Content Brain owns
what Content Brain does not own
how to start content work
where to find templates
where to find checklists
what requires approval
what is not automated yet
Source page:
Content Brain
Migration action:
Simplify and copy.
Content Workflow
Purpose:
Show the manual path from signal to content output.
Should include:
signal intake
opportunity qualification
brief creation
drafting
review
publishing readiness
handoff
repurposing
refresh
feedback
Source page:
Content Brain Workflow Map
Migration action:
Simplify heavily and copy.
Content Briefs
Purpose:
Give the operator the main working template for content creation.
Should include:
content title
source Brain
content type
audience
intent
research basis
SEO notes
funnel role
approval owner
handoff destination
signal to watch
Source page:
Content Brain Content Brief Template
Migration action:
Copy as operational template.
Affiliate Content Packs
Purpose:
Help create structured content support for approved or review-ready affiliate products.
Should include:
pack size
selected assets
offer status
research status
approval owner
compliance risk
handoff destination
performance signal
Source pages:
Content Brain Affiliate Product Content Pack Checklist
Content Brain Affiliate Product Content Pack Framework
Migration action:
Copy checklist first.
Simplify framework into operator guidance.
Affiliate Funnel Support
Purpose:
Help operators understand how content supports affiliate funnels without taking authority from Affiliate Brain, Ads Brain, Research Brain, Compliance Brain, Finance Brain, or Experimentation Brain.
Should include:
problem-aware content
solution-aware content
pre-sell content
FAQ and objection content
trust content
YouTube support
VEO3 support
email follow-up support
repurposing
signal feedback
Source page:
Content Brain Affiliate Funnel Support Map
Migration action:
Simplify and copy.
SEO And Authority
Purpose:
Guide SEO article planning, topic structure, trust, E E A T, and information gain.
Should include:
SEO brief use
search intent
topic architecture
topic clusters
information gain
trust review
authority support
Source pages:
Content Brain SEO Content Brief Standard
Content Brain Topic Architecture Framework
Content Brain Topic Cluster And Hub Architecture Framework
Content Brain Intent Alignment Framework
Content Brain Information Gain Framework
Content Brain E E A T Content Trust Framework
Migration action:
Copy SEO brief first.
Simplify the rest into operator reference pages.
Publishing Readiness
Purpose:
Confirm content is ready before publishing or handoff.
Should include:
audience check
research check
source check
claim check
SEO check
internal linking check
CTA check
compliance risk check
approval owner check
handoff check
Source page:
Content Brain Publishing Readiness Checklist
Migration action:
Copy as operator checklist.
Repurposing
Purpose:
Help operators turn approved content into new formats without changing meaning or increasing claim risk.
Should include:
source asset
approved message
new format
platform
CTA
risk check
approval owner
handoff destination
Source page:
Content Brain Content Repurposing Framework
Migration action:
Simplify and copy.
Refresh
Purpose:
Help operators improve existing content based on age, performance, research gaps, compliance concerns, or new signals.
Should include:
refresh trigger
page being refreshed
reason
research update
SEO update
claim review
internal linking update
republishing decision
Source page:
Content Brain SEO Testing And Refresh Framework
Migration action:
Simplify and copy.
Internal Linking
Purpose:
Help operators link Content Brain assets into the correct topic and funnel structure.
Should include:
pillar page
supporting page
affiliate page
trust page
FAQ page
comparison page
YouTube support page
reader journey
Source page:
Content Brain Internal Linking Strategy Framework
Migration action:
Simplify and copy.
Signal Feedback
Purpose:
Capture what Content Brain learns after content is used.
Should include:
content asset
source Brain
signal type
performance source
learning
next action
Brain to notify
Source page:
Content Brain Content Signal Feedback Framework
Migration action:
Do not copy in the first batch unless needed.
Use a simple manual note first.
Reference
Purpose:
Give operators limited access to supporting guidance without overwhelming them.
Should include:
MCR source-of-truth note
Content Brain boundaries
approval boundaries
links back to MCR pages
Source pages:
Content Brain Operating Model
Content Brain Canon summary
Content Brain Copy Map summary
Migration action:
Create short reference summaries later.
Do not copy full governance pages.
Manual Workflow For First Operational Version
Content Brain should run manually like this:
Signal or request is identified.
Operator checks whether it belongs in Content Brain.
Operator checks source Brain and authority boundary.
Operator decides whether to ignore, park, research, draft, review, publish, repurpose, refresh, or retire.
Operator creates a content brief.
Operator selects the correct checklist or framework.
Operator drafts or prepares the content asset.
Operator checks publishing readiness.
Operator routes for approval where needed.
Operator hands off or publishes only after approval.
Operator records the signal to watch.
Operator routes learning back to the correct Brain later.
This workflow is manual first.
What Content Brain First Operational Version Should Do
Content Brain should support:
SEO article planning
content brief creation
affiliate product content pack planning
affiliate funnel support
YouTube script support
VEO3 pre-video support
email content support
social content support
repurposing
refresh planning
publishing readiness review
manual signal feedback
internal linking planning
operator decision support
What Content Brain First Operational Version Should Not Do
Content Brain should not:
approve affiliate offers
approve compliance-sensitive claims
run ads
approve budgets
validate experiments
control Research Brain verdicts
control Finance Brain decisions
control Ads Brain testing
control Conversion Brain strategy
publish automatically
create Supabase tasks automatically
route Brain Room tasks automatically
build dashboards
build plugin UI
replace MCR source-of-truth pages
Operational Copy Simplification Rules
When copying a page from MCR to mwmscontentbrain.site:
remove long MCR-only governance sections where not needed
keep authority boundaries visible
keep source-of-truth note visible
keep operator steps clear
keep checklists practical
keep templates usable
shorten relationship sections
shorten change logs
remove internal build history unless useful
turn frameworks into practical guidance
avoid overwhelming the operator
Do not weaken compliance, finance, research, or approval boundaries.
First Migration Batch Recommendation
Recommended first batch for operational copy:
Content Brain
Content Brain Workflow Map
Content Brain Content Brief Template
Content Brain Publishing Readiness Checklist
Content Brain Affiliate Product Content Pack Checklist
Content Brain Affiliate Funnel Support Map
Content Brain SEO Content Brief Standard
Content Brain Internal Linking Strategy Framework
Content Brain Content Repurposing Framework
Content Brain SEO Testing And Refresh Framework
This smaller first batch is better than copying the entire first migration group at once.
Reason:
It gives the operator enough to work without overwhelming the site.
Second Migration Batch Recommendation
Recommended second batch:
Content Brain Affiliate Product Content Pack Framework
Content Brain Content Production System Framework
Content Brain Topic Architecture Framework
Content Brain Topic Cluster And Hub Architecture Framework
Content Brain Intent Alignment Framework
Content Brain Information Gain Framework
Content Brain E E A T Content Trust Framework
Content Brain Content Optimization Framework
Content Brain Conversion Support Framework
Reason:
These pages support deeper SEO, authority, optimization, and affiliate funnel work after the first operating layer is usable.
Hold For Later
Hold the following:
Content Brain Operating Model
Content Brain Content Signal Feedback Framework
Content Brain Page Registry summary version
Content Brain Canon summary
Content Brain Architecture summary
Content Brain Stability And Migration Readiness Checklist summary
Reason:
These are useful references, but not required for the first operating build.
Future Plugin Or UI Candidates
Do not build these yet:
Content Opportunity Queue UI
Content Production Queue UI
Content Refresh Queue UI
Repurposing Queue UI
Content Operations Dashboard
Affiliate Product Content Pack Generator
Affiliate Product Content Pack Checklist UI
Affiliate Support Content Planner
Content Brief Generator
SEO Brief Generator
Publishing Readiness Checklist UI
Internal Linking Planner
Topic Cluster Planner
Repurposing Planner
Content Signal Feedback Dashboard
Migration Readiness Checklist UI
These are future candidates only.
Manual workflow must prove need first.
Migration Readiness Gate
Before any migration begins, confirm:
Content Brain Page Registry is current.
Content Brain Copy Map is current.
Content Brain Stability And Migration Readiness Checklist exists.
First migration batch is approved.
Operational simplification rules are clear.
No duplicates exist.
Parents are correct.
MCR remains source of truth.
M’s active work is not touched.
No plugin or UI build has started.
No automation is being added.
Relationship To Content Brain Page Registry
The Content Brain Page Registry tracks what exists.
This migration plan should be added to the registry as:
Page Title: Content Brain Operational Migration Plan
Document Type: Migration Plan
Parent Page: Content Brain
Status: Draft
Migration Classification: MCR Only First
Plugin Or UI Candidate: No Direct UI
Notes: Defines the first practical operating version of mwmscontentbrain.site, including first migration batch, second migration batch, simplified operational copy rules, first menu structure, manual workflow, pages to hold, future plugin/UI candidates, and migration readiness gate.
Relationship To Content Brain Copy Map
The Content Brain Copy Map controls movement from MCR to mwmscontentbrain.site.
This migration plan should be added to the Copy Map as:
Current Page: Content Brain Operational Migration Plan
Classification: MCR Only First
Reason: Planning and governance page used to define the first operational migration structure before copying any Content Brain pages to mwmscontentbrain.site.
Source Of Truth: MCR
Future Destination: MCR first, possible short operational summary later
Future Use: Migration planning reference
Plugin Or UI Later: No direct UI
Relationship To Content Brain Stability And Migration Readiness Checklist
The Content Brain Stability And Migration Readiness Checklist is the gate.
This migration plan is the roadmap.
The checklist confirms whether migration is safe.
The migration plan defines what migration should look like.
Both must agree before migration begins.
Relationship To MWMS MCR To Brain Copy Rule
This migration plan applies the MWMS MCR To Brain Copy Rule to Content Brain.
The rule remains:
MCR is the source of truth.
Brain sites are operational environments.
Only selected, useful, operational pages should be copied.
Governance stays in MCR.
Plugin and UI systems come later.
No blind copying.
No uncontrolled migration.
Relationship To Other Brains
Affiliate Brain
Content Brain will support Affiliate Brain by preparing affiliate content packs, pre-sell content, support pages, YouTube support, VEO3 support, FAQ content, objection content, and repurposing assets.
Content Brain does not approve affiliate offers.
Research Brain
Content Brain will depend on Research Brain for evidence, market context, audience language, competitor information, and source truth.
Content Brain does not invent research verdicts.
Search Intelligence Brain
Content Brain will use search demand signals, keyword opportunities, topic gaps, and SERP insights for SEO and authority planning.
Content Brain does not own search demand validation.
Ads Brain
Content Brain will support Ads Brain with content assets, YouTube descriptions, VEO3 pre-video hooks, pre-sell content, and message match support.
Content Brain does not run ads.
Experimentation Brain
Content Brain will support tests with content variants and learning-based refresh or repurposing.
Content Brain does not decide test validity.
AIBS Brain
Content Brain will support AIBS with educational content, explainers, authority content, FAQ content, trust assets, and client-facing content.
Content Brain does not define AIBS strategy.
Compliance Brain
Content Brain will flag claim risks and approval requirements.
Content Brain does not approve compliance-sensitive claims.
Finance Brain
Content Brain will respect content investment discipline and avoid overbuilding weak opportunities.
Content Brain does not approve spend.
Data Brain
Content Brain will collect and return content-level signals.
Data Brain owns signal quality and interpretation.
SIT Brain
Content Brain may later use SIT for workflow integrity and completeness checks.
No SIT automation is required for the first operational version.
HeadOffice
Content Brain will report migration readiness, content bottlenecks, support gaps, affiliate content pack status, and content opportunity signals to HeadOffice.
HeadOffice remains governance oversight.
Drift Protection
The system must prevent:
copying all MCR pages blindly
moving governance pages as operator pages
copying Canon as source-of-truth replacement
copying Architecture as an interface
building UI before manual workflow exists
starting Supabase work too early
starting Brain Room routing too early
creating a bloated mwmscontentbrain.site
confusing migration planning with migration execution
weakening Brain authority boundaries
Content Brain approving offers
Content Brain approving compliance
Content Brain approving budgets
Content Brain validating experiments
Content Brain replacing Research Brain
Content Brain replacing Ads Brain
Content Brain replacing Finance Brain
Content Brain interfering with M’s active build
Architectural Intent
The Content Brain Operational Migration Plan exists to move Content Brain from a strong MCR foundation into a usable manual operating environment without rushing into automation.
The long-term architecture is:
MCR defines the Brain.
mwmscontentbrain.site operates the Brain.
Plugin and UI systems automate repeated workflows later.
Content Brain should prove the manual workflow first.
Only after manual use shows repeated patterns should MWMS build queues, dashboards, generators, or automation.
Final Rule
Do not migrate Content Brain until the first migration batch is approved.
Do not build plugin/UI before manual workflow proves the need.
Do not copy governance pages as operational pages.
Do not turn mwmscontentbrain.site into a duplicate MCR archive.
The first operational version of Content Brain should be simple, practical, and operator-friendly.
MCR remains the source of truth.
Change Log
Version: v1.0
Date: 2026-05-24
Author: HeadOffice
Change: Initial creation of Content Brain Operational Migration Plan. Defines the first practical operating version of mwmscontentbrain.site, recommended menu structure, first migration batch, second migration batch, pages to hold, simplification rules, manual workflow, future plugin/UI candidates, migration readiness gate, and relationships to Content Brain Page Registry, Content Brain Copy Map, Content Brain Stability And Migration Readiness Checklist, MWMS MCR To Brain Copy Rule, and related MWMS Brains.
Change Impact Declaration
Pages Created:
Content Brain Operational Migration Plan
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
Content Brain Page Registry
Content Brain Copy Map
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT BRAIN OPERATIONAL MIGRATION PLAN v1.0