Brain Name: Content Brain
Document Type: Copy Map
Status: Active
Version: v2.9
Authority: Content Brain Canon
Applies To: All Content Brain MCR Pages, Operational Copies, Content Brain Site Pages, Supabase Records, Migration Decisions, Future Plugin Or UI Candidates And Production-System Components
Parent: Content Brain
Enforcement Mode: Structural And Operational
Last Reviewed: 2026-06-17
Content Brain Copy Map
Purpose
The Content Brain Copy Map defines how Content Brain material moves between:
MCR
mwmscontentbrain.site
Supabase
future plugin or UI systems
future controlled workers and AI Employees
future publishing or delivery integrations
It determines:
what remains in MCR as source-of-truth authority
what may be copied to mwmscontentbrain.site
what requires simplification before operational use
what remains operational-site-only
what belongs in Supabase as structured records
what should become a future plugin or UI component
what must be held
what requires further review
what must not be copied
what must not be built yet
what must not be automated
The Copy Map prevents blind copying.
It also prevents the Content Brain operational site from becoming:
a duplicate archive of MCR
a collection of disconnected framework pages
a Site Intelligence-only system
a research-style records system
a brief generator without production
a collection of premature queues and dashboards
a plugin build that does not represent the complete Content Brain mandate
The Content Brain operational layer must eventually support the complete path from:
Request, Need Or Opportunity
→ Qualification
→ Existing Content Check
→ Action Decision
→ Content Project
→ Asset Planning
→ Source And Intelligence Assembly
→ Brief Or Direct Production Instruction
→ Content Production
→ Editing And Quality Control
→ Specialist Review
→ Human Approval
→ Publishing Preparation
→ Human-Controlled Publication Or Delivery
→ Outcome Recording
→ Measurement
→ Lifecycle Action
Content Brain must be built in MCR first.
It must then be:
classified
reviewed
tested manually
simplified where required
mapped to the correct operational destination
separated from repeatable structured records
protected by human approval
migrated only when the operational need is clear
Scope
This Copy Map applies to:
Content Brain Canon
Content Brain Architecture
Content Brain Operating Model
Content Brain Workflow Map
Content Brain Page Registry
Content Brain Copy Map
Content Brain frameworks
Content Brain standards
Content Brain templates
Content Brain specifications
Content Brain checklists
Content Brain operational copies
Content Brain migration pages
Content Brain build-control pages
Content Brain Site Intelligence pages
Content Brain production pages
Content Brain editing pages
Content Brain publishing-support pages
Content Brain refresh pages
Content Brain repurposing pages
Content Brain website-content pages
Content Brain article-content pages
Content Brain social-content pages
Content Brain script-content pages
Content Brain advertising-content pages
Content Brain newsletter and email pages
Content Brain manual and documentation pages
Content Brain content-pack pages
Content Brain WordPress plugin screens
Content Brain Supabase records
Content Brain future UI components
Content Brain future queues
Content Brain future dashboards
Content Brain future generators
Content Brain future workers
Content Brain future AI Employees
Content Brain future publishing integrations
This Copy Map does not authorise:
live plugin development beyond the current stabilised supporting Records UI proof
unrestricted content generation
autonomous publication
autonomous social posting
autonomous newsletter sending
autonomous email deployment
autonomous ad deployment
queue execution
worker activation
AI Employee activation
Brain Room routing
automatic M handoff
interference with M’s Research Brain work
Those require later approved implementation decisions.
Core Rule
MCR is the source of truth.
mwmscontentbrain.site is the operational working environment.
Supabase is the structured records layer.
Future plugin or UI systems are implementation layers.
Future workers and AI Employees are execution layers.
These layers must not be confused.
The correct movement rule is:
MCR Source Authority
→ Approved Simplification Or Operational Interpretation
→ mwmscontentbrain.site Human Working Layer
→ Supabase Structured Records Where Repetition Exists
→ Future Plugin Or UI Only After Manual Validation
→ Future Worker Or AI Employee Only After Authority, Permission, Approval And Failure Controls Exist
MCR pages must not be overwritten by operational copies.
Operational copies must not claim Canon authority.
Supabase records must not be treated as Canon.
Future interfaces must not become authority merely because they are easier to use.
Movement Classifications
MCR Only
The item remains in MCR as a source-of-truth page.
It should not be copied in full merely for convenience.
Copy To Content Brain
The item has direct operational value and may be copied only after checking:
the exact source page
the current version
the destination
existing destination pages
simplification requirements
manual need
human approval
Copy To Content Brain Later
The item may have future operational value but is not required in the current operating layer.
Simplify Before Copy
The MCR source remains authoritative.
A shorter operator-focused version may be created on mwmscontentbrain.site.
The operational copy must not:
replace the MCR source
claim Canon authority
introduce new rules
expand scope
omit critical controls
Convert To Structured Records
The item represents repeatable instances or status records.
It belongs in Supabase rather than as multiple WordPress pages.
Operational Site Only
The item is implementation-specific and should remain on mwmscontentbrain.site.
It does not become MCR authority unless deliberately promoted.
Later Plugin Or UI
The source material may support a future screen, form, dashboard, queue, checklist or workspace.
No build is authorised by this classification.
Review Later
The item may be useful but requires overlap, authority, timing or destination review.
Hold
Do not copy, build, migrate, promote or delete the item until the hold is resolved.
Do Not Copy
The item should remain only in its source location because copying would create duplication, confusion or authority drift.
Archive
The item is no longer active but should be preserved for history, evidence or recovery.
Classification Decision Questions
Before copying or moving any item, confirm:
What is the exact source page?
What authority does it have?
Is the source MCR or operational?
Does an exact or close match already exist at the destination?
Is the item a framework, record, template, checklist, specification or operational tool?
Is a WordPress page the correct destination?
Is Supabase the correct destination?
Is a plugin or UI component the correct destination?
Is the content still aligned with the current Canon?
Does it support complete content production?
Does it support only Site Intelligence?
Does it belong to another Brain?
Has its manual use been proven?
Does it need simplification?
Does it contain repeatable fields?
Does it require human approval?
Would copying create duplicate authority?
Would copying create page bloat?
Would copying interfere with M’s Research Brain work?
Is there a real current operational need?
If these questions cannot be answered, classify the item as:
Review Later
or:
Hold
MCR Source-Of-Truth Layer
MCR contains the authoritative Content Brain structure.
The following pages remain MCR source-of-truth pages.
Content Brain Canon
Classification: MCR Only
Current Version: v1.1
Operational Use: Controlled reference only
Full Copy Allowed: No
Reason: Defines Content Brain authority and complete production mandate.
Content Brain Architecture
Classification: MCR Only
Current Version: v1.1
Operational Use: Controlled architecture reference
Full Copy Allowed: No
Reason: Defines system structure and boundaries between MCR, the operational site, Supabase and future implementation layers.
Content Brain Operating Model
Classification: Copy To Content Brain Later
Current Version: v1.2
Operational Use: Future operator guidance
Full Copy Allowed: No
Reason: The operational site should use a shorter workflow-focused interpretation rather than duplicate the complete MCR page.
Content Brain Workflow Map
Classification: Simplify Before Copy
Current Version: v1.2
Operational Use: High
Full Copy Allowed: No
Reason: The operational site requires a concise working workflow while MCR retains the complete source.
Content Brain Page Registry
Classification: MCR Only
Current Version: v3.4
Operational Use: Possible read-only registry view much later
Full Copy Allowed: No
Reason: Master MCR inventory and structural record.
Content Brain Copy Map
Classification: MCR Only
Current Version: v2.9
Operational Use: Possible migration-status summary only
Full Copy Allowed: No
Reason: Governs movement between system layers.
Required Source Protection
The MCR controlling pages must not be:
overwritten by operational copies
shortened in MCR merely to suit the operational site
replaced by plugin screens
treated as Supabase records
split into duplicate authority pages
edited from the operational site
automatically synchronised without approval
deleted because a simpler operational page exists
Content Brain Operational Site Role
mwmscontentbrain.site is the operational environment.
It should eventually support:
starting content work
managing content requests
qualifying work
checking existing content
making action decisions
defining content projects
planning assets
assembling source requirements
creating content briefs
drafting content
editing content
managing specialist review
managing human approval
preparing publishing packages
recording publication or delivery state
managing refresh and repurposing
using Site Intelligence as a supporting input
showing blockers and next actions
The operational site should not become a full copy of MCR.
It should contain only material required to perform work.
Operational Content Brain Home
The future Content Brain home should provide:
current operating status
incoming requests
active content projects
assets in production
assets awaiting review
assets awaiting approval
publishing-ready assets
blocked work
next actions
refresh candidates
repurposing candidates
Site Intelligence findings requiring content action
The home must not be centred only on:
Site Intelligence records
test counts
compliance-risk counters
migration state
build signals
research-style records
Operational Workflow Position
The operational workflow should be represented as:
Request Or Opportunity
→ Qualify
→ Check Existing Content
→ Decide Action
→ Define Project
→ Plan Assets
→ Assemble Sources
→ Brief Or Direct Instruction
→ Produce
→ Edit
→ Review
→ Approve
→ Prepare For Publishing
→ Publish Or Deliver Through Human Control
→ Record Outcome
→ Measure
→ Refresh, Repurpose, Improve, Consolidate, Retire Or Take No Action
The operator should not need to read the complete MCR Workflow Map during every task.
Supabase Structured Records Layer
Supabase should store repeatable Content Brain records.
Likely future record types include:
content requests
qualification decisions
existing-content checks
action decisions
content projects
content assets
content packs
briefs
source references
evidence references
production status
editing status
specialist review status
human approval status
publishing-preparation status
destination status
publication status
delivery status
performance signals
refresh decisions
repurposing decisions
consolidation decisions
retirement decisions
Site Intelligence findings
compliance flags
blockers
archive state
Supabase records must remain connected to:
the originating request
the project
the asset
the source material
the approving human
the destination
the current status
the next action
Items That Belong In Supabase
The following should normally become structured records rather than new WordPress pages:
individual content requests
individual content projects
individual asset records
individual content briefs
individual drafts
individual approval records
individual publishing records
individual performance records
individual refresh decisions
individual repurposing decisions
individual Site Intelligence tests
individual Site Intelligence findings
repeated compliance flags
repeated migration states
repeated review outcomes
repeated operational signals
WordPress may retain:
a short summary log
a framework
a template
a protocol
a specification
a dashboard shell
a human-readable operating page
WordPress should not become a record database.
Current Site Intelligence Records Position
The current Site Intelligence Records screen is classified as:
Operational Site Only
Stabilised Structured-Record Proof
Supporting Site Intelligence Screen
Current plugin version:
v0.4.2
It has proven:
Supabase connectivity
record display
record creation
record viewing
safe record editing
record archiving from the individual Edit screen only
archived-state filtering
search and filtering
summary calculations
operational signal calculations
The confirmed current list state is:
five active records
main Actions column limited to View and Edit
Archive absent from the main records list
Archive available only inside the individual Edit screen
no delete control
The confirmed current summary totals are:
Total Records: 5
Strong Build Signals: 2
Moderate Build Signals: 3
High Compliance Risk: 2
Needs Review: 0
Migration Not Started: 5
The Records UI stability task is complete.
The current Records UI must not be treated as:
the Content Brain home
the main Content Brain workspace
the content request system
the content project system
the production system
the editing system
the approval system
the complete Content Brain data model
the permanent Content Brain architecture
Further development of that screen must remain stopped unless a later approved decision requires a specific supporting Site Intelligence change.
Site Intelligence Movement Rule
Site Intelligence MCR frameworks and protocols may remain in MCR.
Operational Site Intelligence guidance may be copied or simplified where it helps a human complete a review.
Individual Site Intelligence records belong in Supabase.
The correct movement is:
MCR Site Intelligence Framework
→ Simplified Operational Guidance
→ Human Site Review
→ Supabase Finding Or Test Record
→ Content Action Decision
→ Main Content Workflow
Site Intelligence must lead to:
create
refresh
expand
correct
merge
repurpose
relink
retire
no action
specialist review
content project required
It must not end as isolated research-style records with no production consequence.
Migration Control Pages
Content Brain Stability And Migration Readiness Checklist
Classification: MCR Only First
Operational Copy: No current need
Future UI: Possible later migration-readiness checklist
Reason: Controls readiness before moving pages into the operational site.
Content Brain Operational Migration Plan
Classification: MCR Only First
Operational Copy: No
Future UI: No direct UI
Reason: Governs migration sequencing and source protection.
Content Brain First Migration Batch Review
Classification: MCR Only First
Operational Copy: No
Future UI: No direct UI
Reason: Historical and planning review for the first proposed operational batch.
Content Brain Migration Execution Checklist
Classification: MCR Only First
Operational Copy: No direct full copy
Future UI: Possible later checklist
Reason: Controls migration execution and validation.
mwmscontentbrain.site First Operational Layer Build Checklist
Classification: MCR Only First
Operational Copy: No
Future UI: No direct UI
Reason: Guides initial operational-layer setup.
These pages do not authorise migration merely because they exist.
They must now be interpreted beneath:
Content Brain Canon v1.1
Content Brain Architecture v1.1
Content Brain Operating Model v1.2
Content Brain Workflow Map v1.2
Content Brain Page Registry v3.4
Content Brain Copy Map v2.9
Existing Operational Copy Pages
The seven named operational copies below have been created, reviewed and confirmed as current operational pages on mwmscontentbrain.site.
Their source authority remains in MCR.
They must not be treated as separate Canon or framework authority.
Content Brain Home Operational Copy
Source: MCR controlling Content Brain pages
Operational Version: v1.1
Classification: Current Operational Copy
Destination: mwmscontentbrain.site
Status: Created And Current
Source Of Truth: MCR
Reason: Provides the current operational homepage copy while Content Brain Canon, Architecture, Operating Model and Workflow Map remain authoritative.
Content Brain Workflow Operational Copy
Source: Content Brain Workflow Map
Source Version: v1.2
Operational Version: v1.1
Classification: Current Operational Copy
Destination: mwmscontentbrain.site
Status: Created And Current
Source Of Truth: MCR
Reason: Provides the current operator-facing workflow while Content Brain Workflow Map remains authoritative.
Content Brain Content Brief Template Operational Copy
Source: Content Brain Content Brief Template
Source Version: v1.2
Operational Version: v1.1
Classification: Current Operational Copy
Destination: mwmscontentbrain.site
Status: Created And Current
Source Of Truth: MCR
Reason: Provides the current operator-facing brief structure. Briefing remains proportional and does not replace production.
Content Brain Publishing Readiness Checklist Operational Copy
Source: Content Brain Publishing Readiness Checklist
Source Version: v1.1
Operational Version: v1.1
Classification: Current Operational Copy
Destination: mwmscontentbrain.site
Status: Created And Current
Source Of Truth: MCR
Reason: Provides the current operator-facing publishing-readiness checklist before human-controlled publication or delivery.
Content Brain Affiliate Product Content Pack Checklist Operational Copy
Source: Content Brain Affiliate Product Content Pack Checklist
Source Version: v1.1
Operational Version: v1.1
Classification: Current Operational Copy
Destination: mwmscontentbrain.site
Status: Created And Current
Source Of Truth: MCR
Reason: Provides the current operator-facing affiliate product content-pack checklist while the MCR checklist remains authoritative.
Content Brain Affiliate Funnel Support Operational Copy
Source: Content Brain Affiliate Funnel Support Map
Source Version: v1.2
Operational Version: v1.1
Classification: Current Operational Copy
Destination: mwmscontentbrain.site
Status: Created And Current
Source Of Truth: MCR
Reason: Provides current affiliate funnel-support guidance beneath the broader Content Brain production system.
Content Brain SEO Content Brief Standard Operational Copy
Source: Content Brain SEO Content Brief Standard
Source Version: v2.1
Operational Version: v1.1
Classification: Current Operational Copy
Destination: mwmscontentbrain.site
Status: Created And Current
Source Of Truth: MCR
Reason: Provides current SEO-specific operator guidance beneath the universal Content Brain workflow.
No Additional Operational Copy Authorised
The following existing operational-copy entries are not changed by this v2.9 alignment:
Content Brain Internal Linking Strategy Operational Copy
Classification: Review And Simplify
Destination: mwmscontentbrain.site
Reason: Useful operational guidance across website and article projects.
Current Decision: No additional migration-status change authorised by this update.
Content Brain Repurposing Operational Copy
Classification: Review And Simplify
Destination: mwmscontentbrain.site
Reason: Useful lifecycle support after the main production workflow is established.
Current Decision: No additional migration-status change authorised by this update.
Content Brain SEO Refresh Operational Copy
Classification: Review Later
Destination: mwmscontentbrain.site
Reason: Useful refresh guidance but must sit beneath the complete lifecycle workflow.
Current Decision: No additional migration-status change authorised by this update.
Existing Content Brain Site Pages
Pages already on mwmscontentbrain.site remain operational-only unless MCR deliberately adopts them.
They must be reviewed against exact and close MCR matches.
Content Brain Affiliate Content Packs
Classification: Operational Site Only Pending Review
MCR Match: Affiliate Product Content Pack Framework and Checklist
Action: Review, merge or simplify
Do Not: Promote automatically to MCR
Content Brain Affiliate Funnel Support
Classification: Operational Site Only Pending Review
MCR Match: Affiliate Funnel Support Map
Action: Review against MCR source
Content Brain Content Briefs
Classification: Operational Site Only Pending Review
MCR Match: Content Brief Template
Action: Align with MCR and future brief workflow
Content Brain Internal Linking
Classification: Operational Site Only Pending Review
MCR Match: Internal Linking Strategy Framework and Internal Linking Equity Framework
Action: Keep operational only after alignment
Content Brain Publishing Readiness
Classification: Operational Site Only Pending Review
MCR Match: Publishing Readiness Checklist
Action: Keep operational after alignment
Content Brain Refresh
Classification: Operational Site Only Pending Review
MCR Match: SEO Testing And Refresh Framework and Content Refresh Queue Specification
Action: Align beneath the complete lifecycle workflow
Content Brain Repurposing
Classification: Operational Site Only Pending Review
MCR Match: Content Repurposing Framework and Repurposing Operational Copy
Action: Align beneath the complete lifecycle workflow
Content Brain SEO Content Briefs
Classification: Operational Site Only Pending Review
MCR Match: SEO Content Brief Standard
Action: Review before continued use
Content Brain Knowledge Structure Model
Classification: Hold
MCR Match: Topic Architecture Framework and Topic Cluster And Hub Architecture Framework
Action: Review overlap before promotion or deletion
Content Brain Performance Measurement Model
Classification: Hold
MCR Match: Content Signal Feedback Framework and Data Brain authority
Action: Review cross-Brain ownership
Content Brain Signal Interpretation Framework
Classification: Hold
MCR Match: Content Signal Feedback Framework
Action: Review overlap
Content Brain Research Signal Feedback Model
Classification: Hold
MCR Match: Content Signal Feedback Framework and Research Brain authority
Action: Review boundary
Content Brain Offer Influence Model
Classification: Hold
MCR Match: Conversion Support Framework and Affiliate Brain authority
Action: Review boundary
Content Brain Pre Sell Structure Model
Classification: Hold
MCR Match: Affiliate Funnel Support Map and Conversion Brain
Action: Review boundary
Content Brain Affiliate Conversion Support Model
Classification: Hold
MCR Match: Conversion Support Framework and Affiliate Funnel Support Map
Action: Review boundary
Content Brain Cross-Brain Integration Map
Classification: Review Later
MCR Match: Content Brain Architecture and MWMS Brain Interaction Protocol
Action: Review before use as authority
Content Brain Employee Registry
Classification: Hold
Destination: Future system only
Action: Do not activate
Reason: AI Employee design and authority are not part of the current build stage.
Content Brain Build Readiness Shortlist
Classification: Operational Site Only
Action: Review against current save point
Reason: May contain outdated build assumptions.
Content Brain Manual Workflow Synthesis Report
Classification: Preserve
Destination: Operational evidence
Action: Use as evidence when defining future interface requirements.
Content Brain Manual Workflow Test Log
Classification: Convert To Structured Records Or Keep As Short Summary
Destination: Supabase plus short WordPress summary if needed
Action: Do not allow test logs to create page bloat.
Content Brain Site Content Intelligence Framework
Classification: Supporting Operational Framework
Destination: May remain operational after MCR alignment
Action: Keep Site Intelligence subordinate to production.
Content Brain Site Content Intelligence Report Generator Specification
Classification: Later Plugin Or UI
Action: Do not build yet
Reason: Supporting Site Intelligence tool only.
Content Brain Site Content Intelligence Report Template
Classification: Supporting Operational Template
Action: Preserve and review.
Content Brain Site Intelligence Manual Test Protocol
Classification: Supporting Operational Protocol
Action: Preserve.
Content Brain Site Intelligence Records Screen Specification
Classification: Stabilised Supporting UI Specification
Action: Preserve as the source specification for the current supporting Records UI.
Current State: Plugin v0.4.2 stable.
Boundary: Do not expand into the main Content Brain interface.
Content Brain Output Style Selector Specification
Classification: Hold And Review
Source: Content Brain site only
MCR Authority: None
Action: Review against the future production workspace and asset model.
Content Brain Output Layer Operating Workflow
Classification: Hold And Review
Source: Content Brain site only
MCR Authority: None
Action: Review against Workflow Map v1.2.
Content Brain Output Templates And Field Standard
Classification: Hold And Review
Source: Content Brain site only
MCR Authority: None
Action: Review against future asset types, output requirements and structured data.
Content Brain Output Layer Screen Specification
Classification: Hold And Review
Source: Content Brain site only
MCR Authority: None
Action: Review against the future production interface.
These four Output Layer pages must not be treated as MCR Canon.
They must not drive plugin development until reviewed against the corrected controlling pages.
Core Production Framework Movement
Content Brain Content Production System Framework
Source: MCR
Current Version: v1.1
Classification: Simplify Before Copy
Operational Priority: High
Destination: Future production workspace and operator guidance
Reason: Core practical production framework.
Content Brain Content Optimization Framework
Classification: Copy To Content Brain Later
Operational Priority: Medium
Destination: Future improvement and optimisation workflow
Reason: Requires approved performance signals and clear ownership.
Content Brain Content Repurposing Framework
Classification: Simplify Before Copy
Operational Priority: Medium
Destination: Future repurposing workflow
Reason: Supports lifecycle production after the central workflow is stable.
Content Brain Content Signal Feedback Framework
Classification: Copy To Content Brain Later
Operational Priority: Medium
Destination: Future measurement and lifecycle decision support
Reason: Depends on Data Brain and trustworthy signals.
Content Brain Editorial Consistency Framework
Classification: Simplify Before Copy
Operational Priority: High
Destination: Editing and quality-control guidance
Reason: Useful across all formats.
Content Brain AI Content Quality Governance Framework
Source: MCR
Current Version: v1.1
Classification: Simplify Before Copy
Operational Priority: High Later
Destination: Future quality-control checklist or review system
Reason: Must not authorise unrestricted AI generation.
Content Brain Information Gain Framework
Source: MCR
Current Version: v1.1
Classification: Simplify Before Copy
Operational Priority: Medium
Destination: Editing and content-quality checks
Reason: Supports usefulness and protection against thin content.
Content Brain Publishing Readiness Checklist
Source: MCR
Current Version: v1.1
Classification: Simplify Before Copy
Operational Priority: High
Destination: Publishing Preparation workspace or checklist
Reason: Direct operational value.
Briefing And Planning Movement
Content Brain Content Brief Template
Source: MCR
Current Version: v1.2
Classification: Simplify Before Copy
Operational Priority: High
Destination: Brief workspace or brief form
Reason: Direct operational value across multiple content formats.
Content Brain SEO Content Brief Standard
Source: MCR
Current Version: v2.1
Classification: Simplify Before Copy
Operational Priority: Medium
Destination: SEO-specific brief workflow
Reason: Specialist briefing path beneath the universal content workflow.
Content Brain Intent Alignment Framework
Classification: Simplify Before Copy
Operational Priority: High
Destination: Qualification, planning and editing guidance
Reason: Useful across formats and channels.
Content Brain Topic Architecture Framework
Classification: Copy To Content Brain Later
Operational Priority: Medium
Destination: Topic and website planning workspace
Reason: Useful for larger content programmes.
Content Brain Topic Cluster And Hub Architecture Framework
Source: MCR
Current Version: v2.1
Classification: Copy To Content Brain Later
Operational Priority: Medium
Destination: Topic cluster and internal-linking planner
Reason: Useful after project and asset planning are stable.
Source-Of-Truth Status: MCR framework only.
Operational Copy Status: Not an operational copy.
Trust Evidence And Voice Movement
Content Brain Authority Building Framework
Source: MCR
Current Version: v1.1
Classification: Copy To Content Brain Later
Operational Priority: Medium
Destination: Authority and project-planning guidance
Source-Of-Truth Status: MCR framework only.
Operational Copy Status: Not an operational copy.
Content Brain Authority Contribution Framework
Classification: Review Later
Reason: Requires cross-Brain boundary review.
Content Brain E E A T Content Trust Framework
Source: MCR
Current Version: v1.1
Classification: Simplify Before Copy
Operational Priority: Medium
Destination: Editing and quality-review checklist.
Content Brain VOC Grounded AI Copy Framework
Classification: Simplify Before Copy
Operational Priority: Medium
Destination: Source assembly and production guidance.
Content Brain Story Design Framework
Classification: Copy To Content Brain Later
Operational Priority: Medium
Destination: Script, article, advertising and narrative-content guidance.
MWMS Voice Architecture And Brand Language Standard
Classification: MCR Only With Controlled Operational Summary
Operational Priority: High
Destination: Concise voice and language guidance
Reason: Master voice authority must remain in MCR.
MWMS Content Intelligence Scanner Framework
Classification: Review Later
Reason: Must not duplicate Research Brain or Site Intelligence.
SEO And Internal Linking Movement
Content Brain SEO Testing And Refresh Framework
Classification: Simplify Before Copy
Operational Priority: Medium
Destination: Refresh workflow
Reason: Useful lifecycle function after the main production workflow is stable.
Content Brain Internal Linking Strategy Framework
Source: MCR
Current Version: v1.1
Classification: Simplify Before Copy
Operational Priority: High
Destination: Website and article project guidance
Source-Of-Truth Status: MCR framework only.
Operational Copy Status: Not an operational copy.
Content Brain Internal Linking Equity Framework
Classification: Copy To Content Brain Later
Operational Priority: Medium
Destination: Advanced internal-linking review.
Content Brain Programmatic SEO Framework
Classification: MCR Only First
Operational Priority: Much Later
Destination: Future high-risk system
Action: Do not build.
Content Brain International And Multilingual SEO Framework
Classification: Review Later
Operational Priority: Low
Action: Hold until required.
Content Brain Linkable Asset Strategy Framework
Classification: Copy To Content Brain Later
Operational Priority: Medium
Destination: Asset planning and authority-content workflow.
Affiliate Conversion And Advertising Support Movement
Content Brain Conversion Support Framework
Classification: Simplify Before Copy
Operational Priority: Medium
Destination: Planning, production and editing guidance
Boundary: Conversion Brain retains conversion authority.
Content Brain Affiliate Funnel Support Map
Source: MCR
Current Version: v1.2
Classification: Copy To Content Brain Later
Operational Priority: Medium
Destination: Affiliate project and asset planning.
Content Brain Affiliate Product Content Pack Framework
Source: MCR
Current Version: v1.1
Classification: Simplify Before Copy
Operational Priority: Medium
Destination: Affiliate content-pack workflow.
Content Brain Affiliate Product Content Pack Checklist
Source: MCR
Current Version: v1.1
Classification: Simplify Before Copy
Operational Priority: Medium
Destination: Affiliate content-pack review.
Content Brain Press Support Asset Framework
Classification: Review Later
Reason: Requires authority and cross-Brain review.
Content Brain Outreach And Contribution Framework
Classification: Review Later
Reason: Requires Partnership Brain or authority ownership review.
Content Brain Generous Gift Jolt Framework
Classification: Review Later
Reason: Requires lead-magnet, offer and value-delivery boundary review.
Ecommerce And Lifecycle Movement
Content Brain Ecommerce Welcome Flow Framework
Classification: Copy To Content Brain Later
Operational Priority: Low Until Ecommerce Need Exists
Destination: Future email and ecommerce content workflow
Boundary: Ecommerce Brain retains commercial and journey authority.
Future Queue And Dashboard Specifications
Queue and dashboard specifications remain MCR source documents.
They do not authorise implementation.
Content Brain Content Opportunity Queue Specification
Classification: Later Plugin Or UI
Current Decision: Hold
Reason: Opportunity intake must not replace request intake or the complete production workflow.
Content Brain Content Production Queue Specification
Classification: Later Plugin Or UI
Current Decision: Hold
Reason: Production statuses must first be proven through manual work.
Content Brain Content Refresh Queue Specification
Classification: Later Plugin Or UI
Current Decision: Hold
Reason: Lifecycle records and decisions must first be proven.
Content Brain Repurposing Queue Specification
Classification: Later Plugin Or UI
Current Decision: Hold
Reason: Repurposing project and asset relationships must first be proven.
Content Brain Content Operations Dashboard Specification
Classification: Later Plugin Or UI
Current Decision: Rewrite Before Build
Reason: The dashboard must reflect requests, projects, assets, reviews, approvals, destinations and lifecycle state rather than only opportunities, briefs, signals or Site Intelligence.
Future Main Plugin Or UI Components
The following future components may be considered after manual workflow validation.
Content Brain Main Operational Home
Status: Future
Priority: High after manual validation
Source: Content Brain Canon, Architecture, Operating Model and Workflow Map
Boundary: Must represent the complete production system.
Content Request Intake
Status: Future
Priority: High later
Boundary: Do not build before the manual intake and qualification process is proven.
Content Project Workspace
Status: Future
Priority: High later
Boundary: Must connect related assets to one objective and project.
Asset Planning Workspace
Status: Future
Priority: High later
Boundary: Must define formats, channels, sources, dependencies and approval needs.
Source And Evidence Workspace
Status: Future
Priority: High later
Boundary: Must preserve source traceability and evidence controls.
Content Brief Workspace
Status: Future
Priority: High later
Boundary: Must support proportional briefing and direct production instructions where a full brief is unnecessary.
Content Production Workspace
Status: Future
Priority: High later
Boundary: Must support drafting and revision without authorising unrestricted autonomous generation.
Editing And Quality Review Workspace
Status: Future
Priority: High later
Boundary: Must preserve editing, quality review and specialist review as separate states where required.
Human Approval Workspace
Status: Future
Priority: High later
Boundary: Human approval must remain explicit.
Publishing Preparation Workspace
Status: Future
Priority: High later
Boundary: Publishing preparation does not equal automatic publication.
Lifecycle Workspace
Status: Future
Priority: Later
Boundary: Must support refresh, repurposing, consolidation, correction, retirement and no-action decisions.
Site Intelligence Supporting Workspace
Status: Existing Supporting Proof
Current Plugin Version: v0.4.2
Boundary: Must remain subordinate to the main production workflow.
Future Generator Position
Generators may eventually assist with:
briefs
outlines
website pages
articles
social posts
scripts
ad copy
newsletters
emails
manuals
guides
documentation
content packs
refresh drafts
repurposed assets
No generator may be activated until:
the manual workflow is proven
asset types are defined
source requirements are defined
evidence controls are defined
approval gates exist
version handling exists
failure handling exists
human override exists
publishing remains controlled
SIT approval is obtained where required
A generator must not create unsupported facts, evidence or claims.
Future Worker Position
Future workers may eventually support:
intake processing
source collection
project preparation
brief preparation
content drafting
editing support
quality checks
review routing
publishing preparation
lifecycle monitoring
refresh recommendations
repurposing recommendations
Workers remain inactive.
No worker is authorised by this Copy Map.
Future AI Employee Position
Future Content Brain AI Employees may eventually support defined roles.
Possible roles may include:
Content Request Coordinator
Content Project Planner
Asset Planning Specialist
Content Brief Architect
Website Content Producer
Article Content Producer
Social Content Producer
Script Producer
Advertising Content Producer
Email And Newsletter Producer
Documentation Producer
Content Editor
Content Quality Reviewer
Publishing Preparation Coordinator
Content Lifecycle Analyst
Site Intelligence Reviewer
No role is approved for activation.
Each role would require:
a role card
defined authority
defined inputs
defined outputs
defined tools
defined permissions
defined escalation
defined approval gates
defined evaluation
defined failure handling
SIT review
Cross-Brain Copy Boundaries
Research Brain
Research Brain source material must not be copied into Content Brain as duplicate research authority.
Research Brain provides approved research outputs.
Content Brain uses those outputs to produce content.
Affiliate Brain
Affiliate Brain controls affiliate offer and campaign decisions.
Content Brain produces approved content assets and support materials.
Ads Brain
Ads Brain controls advertising strategy, testing and deployment.
Content Brain may create approved advertising content.
Conversion Brain
Conversion Brain controls conversion principles, conversion diagnosis and conversion authority.
Content Brain produces complete content assets using approved conversion inputs.
Conversion Brain frameworks should not be duplicated as Content Brain Canon.
Compliance Brain
Compliance decisions and rules may be referenced or surfaced operationally.
Content Brain must not duplicate Compliance Brain’s regulatory authority.
Data Brain
Data Brain supplies trusted measurement.
Content Brain stores or receives the content-specific result required for lifecycle decisions.
Content Brain must not recreate Data Brain analytics authority.
Experimentation Brain
Experimentation Brain governs valid tests and interpretation.
Content Brain creates approved content variants.
Customer Brain
Customer Brain supplies customer states, language and journey intelligence.
Content Brain uses approved inputs without duplicating Customer Brain source systems.
Creative Brain
Creative Brain supplies concepts, angles and narrative direction.
Content Brain produces complete assets from approved creative inputs.
SIT Brain
SIT Brain monitors:
authority
integrity
drift
safe activation
implementation controls
Content Brain migration and future automation must remain visible to SIT where required.
HeadOffice
HeadOffice controls:
system authority
structural conflict
major scope changes
cross-Brain disputes
future autonomy approval
major implementation approval
First Operational Production Layer
The first future main operational layer should not begin with all possible features.
The recommended sequence is:
Content Brain Home
Content Request Intake
Qualification And Action Decision
Content Project
Asset Planning
Source And Evidence
Brief Or Direct Instruction
Production Status
Editing And Review
Human Approval
Publishing Preparation
Lifecycle Status
Site Intelligence Supporting Link
This sequence represents the complete production path.
It does not mean all screens must be built at once.
The actual implementation must follow manual validation.
Pages To Keep In MCR Only At First
The following should remain MCR-only during the current stage:
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
Content Brain First Migration Batch Review
Content Brain Migration Execution Checklist
mwmscontentbrain.site First Operational Layer Build Checklist
Content Brain Programmatic SEO Framework
queue specifications
dashboard specifications
high-risk generator specifications
future AI Employee pages
future worker pages
unresolved cross-Brain frameworks
Pages Or Material Suitable For Later Simplification
The following have clear future operational value:
Content Brain Operating Model
Content Brain Workflow Map
Content Brain Content Production System Framework
Content Brain Content Brief Template
Content Brain Publishing Readiness Checklist
Content Brain Editorial Consistency Framework
Content Brain Information Gain Framework
Content Brain Intent Alignment Framework
Content Brain Internal Linking Strategy Framework
Content Brain Content Repurposing Framework
Content Brain SEO Testing And Refresh Framework
Content Brain Conversion Support Framework
Content Brain Affiliate Product Content Pack Framework
Content Brain Affiliate Product Content Pack Checklist
Content Brain SEO Content Brief Standard
Content Brain AI Content Quality Governance Framework
Content Brain E E A T Content Trust Framework
Content Brain VOC Grounded AI Copy Framework
MWMS Voice Architecture And Brand Language Standard
Each requires an operator-focused form.
None should be blindly duplicated.
Items To Convert To Structured Records
The following should become structured records where repeatable:
requests
projects
assets
briefs
sources
evidence
production states
editing states
review decisions
approval decisions
publishing-preparation states
destination states
publication outcomes
performance signals
refresh decisions
repurposing decisions
Site Intelligence tests
Site Intelligence findings
compliance flags
blockers
archive states
Items To Hold
Hold:
Output Style Selector Specification
Output Layer Operating Workflow
Output Templates And Field Standard
Output Layer Screen Specification
Content Brain Employee Registry
Programmatic SEO generator concepts
autonomous publishing concepts
autonomous social posting
autonomous email sending
autonomous ad deployment
Brain Room routing
automatic M handoff
worker activation
AI Employee activation
full queue implementation
full dashboard implementation
unrestricted content generation
unresolved operational-site pages
unresolved Research Brain overlaps
unresolved Conversion Brain overlaps
unresolved Strategy Brain overlaps
Current Priority Decision
The current priority is not immediate full migration.
The current priority is:
Preserve the corrected MCR source-of-truth pages.
Keep the revised Page Registry and Copy Map aligned.
Preserve the current Site Intelligence Records UI v0.4.2 as a stabilised supporting proof.
Do not expand the Site Intelligence Records screen.
Do not authorise another operational copy.
Do not continue framework rewriting.
Do not create another checklist, template, map or framework.
Do not create new pages beyond this replacement Copy Map page required because the current page is too large to update safely.
Validate that the seven named operational copies are recorded as created and current.
Validate that the three updated MCR frameworks remain source-of-truth pages.
Validate that no page is treated as both source authority and operational copy.
Validate that no unrelated migration status changed.
Stop the framework update sequence after alignment.
Current Operating Status
Current status:
Content Brain Canon v1.1 active
Content Brain Architecture v1.1 active
Content Brain Operating Model v1.2 active
Content Brain Workflow Map v1.2 active
Content Brain Page Registry v3.4 active
Content Brain Copy Map v2.9 active once this replacement is published
MCR remains the source of truth
mwmscontentbrain.site remains the operational environment
Supabase remains the structured records layer
the seven named operational copies are recorded as created and current at v1.1
Content Brain Internal Linking Strategy Framework v1.1 remains an MCR source-of-truth framework
Content Brain Topic Cluster And Hub Architecture Framework v2.1 remains an MCR source-of-truth framework
Content Brain Authority Building Framework v1.1 remains an MCR source-of-truth framework
no additional operational copy is authorised
no unrelated migration status is changed
Site Intelligence Tests 1 to 5 remain structured records
Site Intelligence Records UI v0.4.2 remains a stabilised supporting technical proof
the Records UI stability task is complete
the main records list provides View and Edit only
Archive remains available only inside the individual Edit screen
no delete control exists
manual workflow remains human controlled
full production interface has not started
content generation has not started
publishing automation has not started
workers have not started
queues have not started
AI Employees have not started
Brain Room routing has not started
M handoff has not started
M’s Research Brain work remains untouched
Safe Working Boundary
Until a later approved decision:
do not copy every MCR page
do not duplicate MCR in the operational site
do not delete source pages after copying
do not treat operational copies as Canon
do not treat Supabase records as Canon
do not create individual WordPress pages for repeatable records
do not expand the Site Intelligence Records screen into the main interface
do not build the full plugin
do not build production queues
do not build autonomous generators
do not build workers
do not activate AI Employees
do not activate Brain Room routing
do not automatically hand work to M
do not touch M’s Research Brain work
do not activate publishing integrations
do not publish automatically
do not send social posts automatically
do not send newsletters automatically
do not deploy ads automatically
do not promote Content Brain site-only pages without MCR review
do not let migration work replace production workflow validation
do not continue rewriting frameworks during this alignment sequence
do not authorise another operational copy
Migration Readiness Requirements
Before any future MCR material is copied or implemented, confirm:
the MCR source page exists
the exact source page is identified
the current version is known
the destination is known
the movement classification is known
an exact destination match has been checked
a close destination match has been checked
the operational need is proven
the page has been simplified where required
structured data suitability has been checked
cross-Brain ownership has been checked
source authority remains in MCR
human approval exists
rollback is possible
the destination can be validated
the movement does not affect M’s Research Brain work
Copy Validation Checklist
After an approved copy or implementation:
confirm the source page remains in MCR
confirm the destination title is correct
confirm the destination parent is correct
confirm the operational version is shorter where appropriate
confirm no duplicate destination page exists
confirm the operational version does not claim Canon authority
confirm links point to the correct source where required
confirm structured records were not converted into unnecessary pages
confirm no unsupported automation was activated
confirm Site Intelligence did not become the main interface
confirm the full production workflow remains represented
confirm the Page Registry is updated where required
confirm the Copy Map is updated where required
confirm the change is recorded where required
Relationship To Content Brain Page Registry
The Page Registry records what exists.
The Copy Map determines where it belongs and how it may move.
The Page Registry must record:
page title
document type
version
parent
status
migration classification
plugin or UI candidacy
notes
The Copy Map must record:
source location
target location
movement classification
operational value
simplification requirements
structured-record suitability
implementation restrictions
current decision
The Page Registry and Copy Map must remain aligned.
Neither replaces the other.
Relationship To MWMS MCR To Brain Copy Rule
The MWMS MCR To Brain Copy Rule provides the system-wide rule for movement from MCR into operational Brain environments.
This Copy Map applies that rule specifically to Content Brain.
Where this Copy Map conflicts with a higher MWMS copy rule:
the higher rule controls
the Content Brain Copy Map must be corrected
migration must pause
Relationship To MWMS Active Brain Status Board
The Active Brain Status Board records current system status.
The Copy Map should remain consistent with the board’s current Content Brain position.
A migration or implementation must not be described as active if it remains:
planned
drafted
held
manually tested
not started
not approved
Drift Protection
This Copy Map must prevent:
blind copying from MCR
blind promotion from the Content Brain site
duplicate source-of-truth pages
the operational site becoming an MCR clone
Content Brain being reduced to Site Intelligence
Content Brain being reduced to a research-style records system
Content Brain being reduced to briefs without production
Content Brain being reduced to affiliate or SEO content only
temporary Site Intelligence fields defining the permanent data model
the current Records UI becoming the main Content Brain interface
first drafts being treated as approved assets
publishing preparation being treated as publication
Site Intelligence records being treated as production records
MCR frameworks being copied without simplification
operational copies overwriting source pages
unresolved pages being promoted to MCR
migration pages becoming operational authority
queues being built before manual statuses are proven
dashboards being built before operator needs are proven
generators being built before evidence and approval controls exist
workers being activated before permissions and failure handling exist
AI Employees being activated without role definitions
autonomous publishing
automatic M handoff
interference with M’s Research Brain work
cross-Brain authority duplication
page bloat
uncontrolled deletion
loss of recovery copies
Architectural Intent
The Content Brain Copy Map exists to preserve the correct separation between:
source truth
operational guidance
structured records
interface implementation
execution systems
It must allow Content Brain to develop from:
MCR Authority
→ Proven Manual Workflow
→ Operational Guidance
→ Structured Records
→ Production-Focused Interface
→ Controlled Assistance
→ Governed Workers And AI Employees
→ Governed Publishing Integrations
without:
losing source authority
copying unnecessary pages
creating duplicate governance
building from temporary records
narrowing Content Brain to one supporting capability
automating before controls exist
confusing production with planning
confusing approval with publication
confusing Site Intelligence with Research Brain
interfering with another workstream
The operational Content Brain must eventually be capable of supporting:
website creation
article production
social content
video scripts
audio scripts
webinar scripts
advertising content
newsletters
email sequences
manuals
guides
documentation
reports
lead magnets
training material
content packs
editing
quality control
publishing preparation
refresh
repurposing
consolidation
correction
retirement
The Copy Map must ensure that each capability reaches the correct system layer.
Final Rule
MCR holds Content Brain authority.
mwmscontentbrain.site supports human operation.
Supabase holds repeatable structured records.
Future plugin or UI systems support validated workflows.
Future workers and AI Employees may only operate within approved authority.
No item should be copied, moved, converted, promoted, automated or deleted unless:
the source is known
the authority is known
the destination is known
the classification is known
exact and close matches have been checked
the operational need is proven
structured-record suitability has been checked
simplification needs have been checked
cross-Brain boundaries have been checked
human approval exists
recovery is possible
M’s Research Brain work remains untouched
Content Brain must remain a complete content production and lifecycle system.
Site Intelligence remains a supporting capability.
The current Site Intelligence Records screen remains a stabilised supporting technical proof.
No blind copying.
No uncontrolled migration.
No premature implementation.
No new page where an existing page should be updated or replaced, except where the current oversized WordPress page cannot be safely updated and a validated replacement is required.
No operational page promoted to Canon without deliberate approval.
No Supabase record treated as Canon.
No plugin built around temporary test fields.
No automation before manual proof.
Change Log
Version: v2.9
Date: 2026-06-17
Author: HeadOffice
Change: Aligned the Content Brain Copy Map with Content Brain Page Registry v3.4 and the pages changed after Copy Map v2.8.
Updated the following operational-copy entries to Version v1.1, Current Operational Copy status and Created And Current state on mwmscontentbrain.site:
Content Brain Home Operational Copy
Content Brain Workflow Operational Copy
Content Brain Content Brief Template Operational Copy
Content Brain Publishing Readiness Checklist Operational Copy
Content Brain Affiliate Product Content Pack Checklist Operational Copy
Content Brain Affiliate Funnel Support Operational Copy
Content Brain SEO Content Brief Standard Operational Copy
Confirmed the MCR sources for those operational copies remain the controlling source-of-truth pages.
Updated the following controlling MCR framework-version records:
Content Brain Internal Linking Strategy Framework — v1.1
Content Brain Topic Cluster And Hub Architecture Framework — v2.1
Content Brain Authority Building Framework — v1.1
Confirmed that the three updated frameworks:
remain MCR source-of-truth pages
are not operational copies
have not been reclassified as operational-site authority
Confirmed that:
Content Brain Page Registry v3.4 is the aligned Registry
Content Brain Copy Map v2.9 is the aligned Copy Map
the seven named operational copies are created and current
no additional operational copy is authorised
no unrelated migration status was changed
no duplicate Copy Map entries were introduced
no framework rewriting continued
no plugin changes were made
the Site Intelligence Records UI was not reopened
no content generation was started
no automation was started
no worker work was started
no queue work was started
no AI Employee work was started
no Brain Room routing was started
no M handoff was started
M’s Research Brain work remains untouched
Version: v2.8
Date: 2026-06-16
Author: HeadOffice
Change: Updated the Content Brain Copy Map to align confirmed MCR source versions and movement classifications for the corrected Content Brain pages.
Added confirmed MCR source and version records for:
Content Brain Affiliate Product Content Pack Checklist — v1.1
Content Brain SEO Content Brief Standard — v2.1
Content Brain AI Content Quality Governance Framework — v1.1
Content Brain Information Gain Framework — v1.1
Content Brain E E A T Content Trust Framework — v1.1
Confirmed previously corrected MCR source and version records for:
Content Brain Affiliate Product Content Pack Framework — v1.1
Content Brain Publishing Readiness Checklist — v1.1
Content Brain Content Brief Template — v1.2
Content Brain Content Production System Framework — v1.1
Content Brain Affiliate Funnel Support Map — v1.2
Confirmed classification for the five newly aligned pages as:
Simplify Before Copy
Confirmed source for the five newly aligned pages as:
MCR
Updated:
Content Brain Page Registry reference from v3.2 to v3.3
Content Brain Copy Map version from v2.7 to v2.8
Core Production Framework Movement
Briefing And Planning Movement
Trust Evidence And Voice Movement
Affiliate Conversion And Advertising Support Movement
Pages Or Material Suitable For Later Simplification
Current Operating Status
Confirmed that:
no operational copies were created
no new Content Brain pages were created
MCR remains the source of truth
the Content Brain site remains operational only
Supabase remains the structured records layer
the Site Intelligence Records UI remains a stabilised supporting technical proof
the Records UI stability task remains complete
no content generation, publishing automation, worker, queue, AI Employee, Brain Room routing or M handoff is authorised
M’s Research Brain work remains untouched
Version: v2.7
Date: 2026-06-16
Author: HeadOffice
Change: Updated the Content Brain Copy Map after completion of the Site Intelligence Records UI stability task and alignment of the Content Brain Page Registry to v3.2.
Confirmed:
the Site Intelligence Records UI is operating as plugin version v0.4.2
five active Site Intelligence records remain available
summary totals remain 5 total records, 2 strong build signals, 3 moderate build signals, 2 high compliance risks, 0 records needing review and 5 migrations not started
the main records list provides View and Edit actions only
Archive is available only inside the individual Edit screen
Archive hides records without deleting them from Supabase
no delete control exists
record creation, viewing, safe editing, search, filters, summary calculations and operational signals remain available
the Records UI stability task is complete
Updated:
Content Brain Page Registry reference from v3.1 to v3.2
Content Brain Copy Map version from v2.6 to v2.7
Current Site Intelligence Records Position
Content Brain Site Intelligence Records Screen Specification classification
Site Intelligence Supporting Workspace build status
Current Priority Decision
Current Operating Status
Safe Working Boundary
Clarified that:
the Records UI remains a stabilised supporting technical proof only
further Site Intelligence screen expansion is not authorised
the Records UI must not become the Content Brain home or main production interface
the next interface decision must begin from requests, projects, assets, production, review, approval, publishing preparation and lifecycle management
no content generation, publishing automation, worker, queue, AI Employee, Brain Room routing or M handoff is authorised
M’s Research Brain work remains untouched
Version: v2.6
Date: 2026-06-15
Author: HeadOffice
Change: Recreated the oversized Content Brain Copy Map as a new replacement page after the correction and expansion of the Content Brain controlling pages.
Aligned the Copy Map 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 Page Registry v3.1
Expanded the Copy Map to govern movement for:
content requests
content projects
content assets
content packs
sources
evidence
briefs
production states
editing states
specialist review
human approval
publishing preparation
publishing and delivery state
measurement
refresh
repurposing
consolidation
retirement
Site Intelligence support
Added:
complete system-layer movement rules
revised movement classifications
MCR source-of-truth protection
operational-site role
future operational home direction
operational workflow position
Supabase record position
Site Intelligence record and UI position
Site Intelligence movement rule
migration-control page position
operational-copy review
operational-site page review
Output Layer page hold decisions
production-framework movement decisions
future production-focused interface structure
future generator boundaries
future worker boundaries
future AI Employee boundaries
cross-Brain copy boundaries
first operational production-layer sequence
updated migration-readiness requirements
updated copy-validation checklist
expanded drift protection
Clarified that:
MCR remains the source of truth
mwmscontentbrain.site remains the operational environment
Supabase remains the structured records layer
Site Intelligence remains a supporting capability
the current Site Intelligence Records screen is not the Content Brain home
the future main interface must support requests, projects, assets, production, editing, approval, publishing preparation and lifecycle management
no automation, worker, AI Employee, Brain Room routing or M handoff is authorised
Version: v2.5
Date: 2026-05-28
Author: HeadOffice
Change: Updated Content Brain Copy Map to add the first operational-layer build checklist, migration controls and operational-copy sequencing.
Version: v2.4
Date: 2026-05-27
Author: HeadOffice
Change: Updated Content Brain Copy Map to add migration execution control and validation requirements.
Version: v2.3
Date: 2026-05-26
Author: HeadOffice
Change: Updated Content Brain Copy Map following the first operational copy batch preparation.
Version: v2.2
Date: 2026-05-26
Author: HeadOffice
Change: Updated Content Brain Copy Map following the first migration batch review.
Version: v2.1
Date: 2026-05-25
Author: HeadOffice
Change: Updated Content Brain Copy Map to add the Content Brain Operational Migration Plan.
Version: v2.0
Date: 2026-05-24
Author: HeadOffice
Change: Updated Content Brain Copy Map to add the Content Brain Stability And Migration Readiness Checklist and formal readiness gate.
Version: v1.9
Date: 2026-05-24
Author: HeadOffice
Change: Updated Content Brain Copy Map to align with Content Brain Affiliate Funnel Support Map v1.1.
Version: v1.8
Date: 2026-05-24
Author: HeadOffice
Change: Added Content Brain Affiliate Product Content Pack Checklist as a Copy To Content Brain operational checklist.
Version: v1.7
Date: 2026-05-24
Author: HeadOffice
Change: Added Content Brain Affiliate Product Content Pack Framework as a Copy To Content Brain operational framework.
Version: v1.6
Date: 2026-05-24
Author: HeadOffice
Change: Added Content Brain Content Opportunity Queue Specification as a Later Plugin Or UI candidate.
Version: v1.5
Date: 2026-05-06
Author: HeadOffice
Change: Added Content Brain Content Operations Dashboard Specification as a Later Plugin Or UI candidate.
Version: v1.4
Date: 2026-05-06
Author: HeadOffice
Change: Added Content Brain Repurposing Queue Specification as a Later Plugin Or UI candidate.
Version: v1.3
Date: 2026-05-06
Author: HeadOffice
Change: Added Content Brain Content Refresh Queue Specification as a Later Plugin Or UI candidate.
Version: v1.2
Date: 2026-05-06
Author: HeadOffice
Change: Added Content Brain Content Production Queue Specification as a Later Plugin Or UI candidate.
Version: v1.1
Date: 2026-05-06
Author: HeadOffice
Change: Added Content Brain Operating Model, Content Brain Workflow Map, Content Brain Affiliate Funnel Support Map, Content Brain Publishing Readiness Checklist and Content Brain Content Brief Template. Added stronger movement classifications and drift protection.
Version: v1.0
Date: 2026-05-06
Author: HeadOffice
Change: Initial creation of Content Brain Copy Map defining what remains in MCR, what may later move to mwmscontentbrain.site and what may later become structured operational tools.
Change Impact Declaration
Pages Created:
Content Brain Copy Map replacement page only, because the existing oversized page cannot be safely updated.
Pages Updated:
Content Brain Copy Map
Pages To Move To Trash After Validation:
The previous Content Brain Copy Map v2.8 page only after the new v2.9 replacement is published and validated.
Do not permanently delete the previous page.
Pages Deprecated:
Previous Content Brain Copy Map v2.8 after validated replacement.
Registries Requiring Update:
None.
Content Brain Page Registry v3.4 already records the aligned page versions and must remain aligned with this v2.9 replacement.
Canon Version Update Required:
No
Automation Status Change:
No
Plugin Or UI Status Change:
No.
Site Intelligence Records UI remains a stabilised supporting technical proof at plugin version v0.4.2.
No new build is authorised.
Worker Status Change:
No
AI Employee Status Change:
No
M Handoff Required:
No
Research Brain Impact:
None
END CONTENT BRAIN COPY MAP v2.9
END OF FULL FILE OUTPUT