Content Brain Migration Execution Checklist

Brain Name: Content Brain
Document Type: Checklist
Status: Draft
Version: v1.0
Authority: Content Brain under HeadOffice governance
Applies To: Content Brain migration execution, mwmscontentbrain.site first operational page migration, first operational copy batch, MCR source-of-truth protection, Content Brain migration readiness, operational page setup, manual workflow rollout, and future Content Brain site build control
Parent: Content Brain
Last Reviewed: 2026-05-24

Content Brain Migration Execution Checklist

Purpose

The Content Brain Migration Execution Checklist defines the controlled process for moving the prepared first operational copy batch from MCR into the future operational Content Brain environment on mwmscontentbrain.site.

This checklist exists to prevent uncontrolled migration.

Its purpose is to make sure that when migration begins, the operator moves only the approved operational pages, in the correct order, with the correct parent/menu placement, while keeping MCR as the source of truth.

This checklist confirms:

which pages move first

which pages do not move

what order the first migration follows

how each page should be placed on mwmscontentbrain.site

what must be checked before copying

what must be checked after copying

what must not be built yet

what remains MCR-only

what requires future plugin or UI review

what status should be recorded after migration

This page does not start migration by itself.

It is the execution control checklist for when migration timing is approved.

Scope

This checklist applies to:

Content Brain first operational migration batch

mwmscontentbrain.site first operator page setup

prepared operational copy pages

manual Content Brain workflow rollout

future Content Brain menu setup

source-of-truth reference handling

page copying order

post-copy validation

migration readiness confirmation

migration completion status

This checklist does not apply to:

Content Brain Canon migration

Content Brain Architecture migration

Content Brain Page Registry migration

Content Brain Copy Map migration

Content Brain plugin or UI build

Supabase implementation

Brain Room routing

cross-brain automation

M’s active build work

live mwmsbrain.site plugin work

HeadOffice reporting build

Affiliate Brain wiring

Research Brain wiring

Finance Brain wiring

This checklist controls page migration only.

It does not authorize automation or plugin development.

Core Rule

Only the prepared first operational copy batch should be moved first.

Do not copy every Content Brain MCR page into mwmscontentbrain.site.

Do not copy governance pages as operator pages.

Do not start plugin, UI, Supabase, Brain Room, queue, dashboard, or automation work during this migration.

The first Content Brain migration must be:

manual

small

clean

operator-friendly

traceable to MCR

easy to reverse

safe around M’s active work

MCR remains the source of truth.

mwmscontentbrain.site becomes the operational working environment.

Current Pre-Migration Status

Current Content Brain status:

Content Brain — Stability Checked / First Operational Copy Batch Prepared / Migration Not Started

Confirmed control pages:

Content Brain Page Registry v2.8

Content Brain Copy Map v2.3

Content Brain Operational Migration Plan v1.0

Content Brain First Migration Batch Review v1.0

Prepared operational copy batch:

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

Content Brain Internal Linking Strategy Operational Copy

Content Brain Repurposing Operational Copy

Content Brain SEO Refresh Operational Copy

Migration status:

Migration not started.

Plugin or UI build not started.

Supabase work not started.

Brain Room routing not started.

M’s active work not touched.

Migration Approval Gate

Before migration begins, confirm:

Migration timing approved: Yes / No

MCR source pages stable: Yes / No

Content Brain Page Registry v2.8 confirmed: Yes / No

Content Brain Copy Map v2.3 confirmed: Yes / No

First operational copy batch exists: Yes / No

No duplicate operational copy pages: Yes / No

All operational copy pages sit under Content Brain in MCR: Yes / No

No dash characters in operational copy titles: Yes / No

No accidental root-level operational copy pages: Yes / No

No plugin or UI build started: Yes / No

No Supabase work started: Yes / No

No Brain Room routing started: Yes / No

M’s active work unaffected: Yes / No

If any answer is No, do not begin migration.

First Migration Batch

The first migration batch is:

  1. Content Brain Home Operational Copy
  2. Content Brain Workflow Operational Copy
  3. Content Brain Content Brief Template Operational Copy
  4. Content Brain Publishing Readiness Checklist Operational Copy
  5. Content Brain Affiliate Product Content Pack Checklist Operational Copy
  6. Content Brain Affiliate Funnel Support Operational Copy
  7. Content Brain SEO Content Brief Standard Operational Copy
  8. Content Brain Internal Linking Strategy Operational Copy
  9. Content Brain Repurposing Operational Copy
  10. Content Brain SEO Refresh Operational Copy

These pages create the first practical operator version of Content Brain.

They should be copied or adapted into mwmscontentbrain.site as the first usable Content Brain operating layer.

Pages Not To Migrate In First Batch

Do not migrate these in the first batch:

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

Content Brain AI Content Quality Governance Framework

Content Brain Programmatic SEO Framework

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 governance pages, architecture pages, control pages, readiness pages, planning pages, migration pages, risky future systems, or future plugin/UI specifications.

They remain in MCR.

First mwmscontentbrain.site Menu Structure

The first Content Brain operational menu should be:

Dashboard / Home

Content Workflow

Content Briefs

Publishing Readiness

Affiliate Content Packs

Affiliate Funnel Support

SEO And Authority

Internal Linking

Repurposing

Refresh

Reference

Do not add future queues, dashboards, generators, planners, or automation menus yet.

Migration Page Mapping

1. Dashboard / Home

MCR Source Page:

Content Brain Home Operational Copy

Future mwmscontentbrain.site Page Title:

Content Brain

Menu Location:

Dashboard / Home

Migration Action:

Copy prepared operational homepage content.

Operator Purpose:

Give the operator a simple starting point for Content Brain.

Validation:

Page explains what Content Brain does.

Page explains what Content Brain does not do.

Page lists operator starting points.

Page preserves approval boundaries.

Page states MCR remains source of truth.

2. Content Workflow

MCR Source Page:

Content Brain Workflow Operational Copy

Future mwmscontentbrain.site Page Title:

Content Workflow

Menu Location:

Content Workflow

Migration Action:

Copy prepared operational workflow content.

Operator Purpose:

Give the operator a repeatable path from signal or request to brief, review, handoff, repurposing, refresh, or feedback.

Validation:

Workflow is clear.

Actions include Ignore, Park, Research, Brief, Draft, Review, Publish, Repurpose, Refresh, Retire, and Handoff.

Source Brain logic is preserved.

Approval boundaries are preserved.

3. Content Briefs

MCR Source Page:

Content Brain Content Brief Template Operational Copy

Future mwmscontentbrain.site Page Title:

Content Briefs

Menu Location:

Content Briefs

Migration Action:

Copy prepared content brief template content.

Operator Purpose:

Give the operator reusable templates for planning content assets before drafting.

Validation:

Full brief template included.

Fast brief version included.

Affiliate brief version included.

SEO brief version included.

VEO3 support brief version included.

Repurposing and refresh brief versions included.

Approval owner and handoff destination fields remain visible.

4. Publishing Readiness

MCR Source Page:

Content Brain Publishing Readiness Checklist Operational Copy

Future mwmscontentbrain.site Page Title:

Publishing Readiness

Menu Location:

Publishing Readiness

Migration Action:

Copy prepared publishing readiness checklist content.

Operator Purpose:

Help the operator check whether a content asset is ready for review, handoff, publishing, repurposing, refresh completion, or use.

Validation:

Audience clarity check included.

Research basis check included.

Claim safety check included.

Compliance risk check included.

SEO basics check included.

Internal linking check included.

Approval owner check included.

Handoff destination check included.

Signal to watch check included.

Checklist does not claim final approval authority.

5. Affiliate Content Packs

MCR Source Page:

Content Brain Affiliate Product Content Pack Checklist Operational Copy

Future mwmscontentbrain.site Page Title:

Affiliate Content Packs

Menu Location:

Affiliate Content Packs

Migration Action:

Copy prepared affiliate product content pack checklist content.

Operator Purpose:

Help the operator check whether an affiliate product content pack is ready to be planned, briefed, drafted, or handed off.

Validation:

Offer status check included.

Research basis check included.

Audience clarity check included.

Funnel role check included.

Pack size decision included.

Asset selection included.

Claim safety check included.

Approval owner check included.

Finance and resource check included.

Handoff destination included.

Signal to watch included.

Checklist does not approve offers.

6. Affiliate Funnel Support

MCR Source Page:

Content Brain Affiliate Funnel Support Operational Copy

Future mwmscontentbrain.site Page Title:

Affiliate Funnel Support

Menu Location:

Affiliate Funnel Support

Migration Action:

Copy prepared affiliate funnel support content.

Operator Purpose:

Help the operator map content assets to affiliate funnel stages.

Validation:

Problem awareness included.

Solution awareness included.

Product education included.

Trust building included.

Pre-sell included.

Comparison included.

Objection handling included.

VSL or product page support included.

Follow-up included.

Repurposing included.

Refresh included.

Signal feedback included.

Page does not approve offers, claims, ads, tests, budgets, or compliance.

7. SEO And Authority

MCR Source Page:

Content Brain SEO Content Brief Standard Operational Copy

Future mwmscontentbrain.site Page Title:

SEO Content Briefs

Menu Location:

SEO And Authority

Migration Action:

Copy prepared SEO content brief content.

Operator Purpose:

Help the operator plan search-aligned content with intent, evidence, trust, internal links, and information gain.

Validation:

Search intent included.

SERP pattern notes included.

Target audience included.

Research basis included.

Information gain angle included.

E E A T trust requirements included.

Claims to avoid included.

Internal linking plan included.

Approval owner included.

Signal to watch included.

Page does not replace Search Intelligence Brain or Research Brain.

8. Internal Linking

MCR Source Page:

Content Brain Internal Linking Strategy Operational Copy

Future mwmscontentbrain.site Page Title:

Internal Linking

Menu Location:

Internal Linking

Migration Action:

Copy prepared internal linking guidance content.

Operator Purpose:

Help the operator decide how pages should connect through useful internal links.

Validation:

Source page field included.

Target page field included.

Reader journey purpose included.

Topic relationship included.

Funnel relationship included.

Link type included.

Anchor text guidance included.

Affiliate risk included.

Compliance risk included.

Signal to watch included.

Page discourages forced links and keyword stuffing.

9. Repurposing

MCR Source Page:

Content Brain Repurposing Operational Copy

Future mwmscontentbrain.site Page Title:

Repurposing

Menu Location:

Repurposing

Migration Action:

Copy prepared repurposing guidance content.

Operator Purpose:

Help the operator turn approved content into additional useful formats without changing meaning or increasing risk.

Validation:

Approved source asset rule included.

Meaning preservation rule included.

Repurposed format options included.

Claims to avoid included.

Compliance risk included.

Approval owner included.

Handoff destination included.

Signal to watch included.

Page prevents uncontrolled rewriting.

10. Refresh

MCR Source Page:

Content Brain SEO Refresh Operational Copy

Future mwmscontentbrain.site Page Title:

Refresh

Menu Location:

Refresh

Migration Action:

Copy prepared SEO refresh guidance content.

Operator Purpose:

Help the operator review, improve, merge, redirect, retire, or park existing content based on evidence and usefulness.

Validation:

Refresh trigger included.

Source signal included.

Search intent review included.

Research review included.

Claim and compliance review included.

Content quality review included.

Internal link review included.

Merge review included.

Retirement review included.

Signal to watch included.

Page discourages refresh without a trigger.

Pre-Copy Checklist For Each Page

Before copying each page, confirm:

MCR source page exists: Yes / No

MCR source page title is exact: Yes / No

MCR source page parent is Content Brain: Yes / No

MCR source page status is Draft or Published intentionally: Yes / No

Destination page title is approved: Yes / No

Destination menu location is known: Yes / No

No duplicate destination page exists: Yes / No

Source-of-truth note remains included: Yes / No

Approval boundaries remain included: Yes / No

No plugin/UI instruction is accidentally treated as active build: Yes / No

If any answer is No, pause before copying.

Post-Copy Checklist For Each Page

After copying each page to mwmscontentbrain.site, confirm:

Page exists on mwmscontentbrain.site: Yes / No

Page title is clean: Yes / No

Page is in correct menu location: Yes / No

Page content copied correctly: Yes / No

No MCR-only governance content was accidentally copied: Yes / No

Source-of-truth note remains visible: Yes / No

Approval boundaries remain visible: Yes / No

No plugin/UI work started: Yes / No

No automation work started: Yes / No

No Supabase work started: Yes / No

No Brain Room routing started: Yes / No

If any answer is No, correct before moving to the next page.

Destination Title Cleanliness Rule

Destination page titles must not include:

dash characters

underscores

version numbers

“copy” wording

“operational copy” wording unless intentionally kept

draft notes

MCR-only labels

The future operator site should use clean operator titles.

Example:

Use:

Content Brain

Do not use:

Content Brain Home Operational Copy

Use:

Content Workflow

Do not use:

Content Brain Workflow Operational Copy

Use:

Refresh

Do not use:

Content Brain SEO Refresh Operational Copy

Source Of Truth Rule

Every migrated operational page must preserve this note in a suitable form:

MCR remains the source of truth for Content Brain. mwmscontentbrain.site is the operational working environment. If a conflict exists between MCR and this site, MCR wins.

This note may be shortened for operator readability, but it must not be removed.

Approval Boundary Rule

Every migrated operational page must preserve the relevant approval boundary.

Content Brain does not approve:

affiliate offers

claims

budgets

ad campaigns

experiments

research verdicts

search validation

finance decisions

compliance-sensitive messaging

strategy decisions

Content Brain supports content execution.

It does not replace the authority of the other Brains.

No Plugin Or UI Rule

During first migration, do not build:

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

SEO Refresh Planner

Content Signal Feedback Dashboard

Migration Readiness Checklist UI

Manual workflow must prove need first.

No Supabase Rule

During first migration, do not create:

Supabase tables

Supabase views

Supabase functions

Supabase triggers

Supabase task routes

Supabase event routes

Supabase dashboards

Supabase queue storage

Supabase automation storage

This migration is page/content migration only.

No Brain Room Routing Rule

During first migration, do not create:

Brain Room commands

Brain Room task routing

Brain Room request forms

Brain Room AI triggers

Brain Room automation hooks

Brain Room executor links

This migration is not a Brain Room build step.

M Work Protection Rule

During first migration, do not touch:

M’s HeadOffice reporting build

Affiliate Brain wiring

Research Brain wiring

Finance Brain wiring

Supabase task routes

Brain Room integration

live mwmsbrain.site plugin work

Make.com scenarios connected to M’s current system

cross-brain automation logic

The Content Brain migration must remain safely outside M’s active build path.

Migration Execution Order

Use this exact order:

  1. Create the Content Brain home page on mwmscontentbrain.site.
  2. Create the Content Workflow page.
  3. Create the Content Briefs page.
  4. Create the Publishing Readiness page.
  5. Create the Affiliate Content Packs page.
  6. Create the Affiliate Funnel Support page.
  7. Create the SEO Content Briefs page.
  8. Create the Internal Linking page.
  9. Create the Repurposing page.
  10. Create the Refresh page.
  11. Set up the simple menu structure.
  12. Confirm source-of-truth notes remain visible.
  13. Confirm approval boundaries remain visible.
  14. Confirm no future plugin/UI pages were created.
  15. Confirm no automation work started.
  16. Record migration status.

Menu Setup Checklist

After page creation, create or confirm menu sections:

Dashboard / Home: Yes / No

Content Workflow: Yes / No

Content Briefs: Yes / No

Publishing Readiness: Yes / No

Affiliate Content Packs: Yes / No

Affiliate Funnel Support: Yes / No

SEO And Authority: Yes / No

Internal Linking: Yes / No

Repurposing: Yes / No

Refresh: Yes / No

Reference: Yes / No

Do not add future queue/dashboard/generator menu sections yet.

Migration Completion Checklist

After all first-batch pages are copied, confirm:

All 10 pages exist on mwmscontentbrain.site: Yes / No

All page titles are clean: Yes / No

All pages are in the correct menu location: Yes / No

All pages preserve source-of-truth note: Yes / No

All pages preserve approval boundaries: Yes / No

No MCR-only governance pages copied as operator pages: Yes / No

No plugin or UI build started: Yes / No

No Supabase work started: Yes / No

No Brain Room routing started: Yes / No

No M’s active work touched: Yes / No

Operator can use the site manually: Yes / No

Post-Migration Status

After first migration is complete, update the working status to:

Content Brain — First Operational Layer Migrated / Manual Workflow Active / Plugin UI Not Started

Do not use this status before pages are actually migrated.

Before migration, the status remains:

Content Brain — Stability Checked / First Operational Copy Batch Prepared / Migration Not Started

Post-Migration Review Questions

After migration, answer:

Can an operator understand what Content Brain does?

Can an operator follow the content workflow?

Can an operator create a content brief?

Can an operator check publishing readiness?

Can an operator plan an affiliate product content pack?

Can an operator map affiliate funnel support?

Can an operator plan SEO content?

Can an operator plan internal links?

Can an operator repurpose approved content safely?

Can an operator refresh existing content safely?

Are approval boundaries visible?

Is MCR source-of-truth preserved?

Is the site still manual first?

If the answer to any question is No, fix the operational page before moving forward.

Future Work After Migration

Only after the first operational layer is used manually should future work be considered.

Possible later work:

Content Opportunity Queue

Content Production Queue

Content Refresh Queue

Repurposing Queue

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

SEO Refresh Planner

Content Signal Feedback Dashboard

These remain future candidates only.

Relationship To Content Brain Page Registry

The Content Brain Page Registry tracks this page as part of Content Brain structure.

This page should be added to the registry as:

Page Title: Content Brain Migration Execution Checklist

Document Type: Checklist

Parent Page: Content Brain

Status: Draft

Migration Classification: MCR Only First

Plugin Or UI Candidate: Possible Migration Execution Checklist UI Later

Notes: Defines the controlled checklist for migrating the first operational copy batch from MCR into mwmscontentbrain.site, including migration approval gate, first batch page mapping, menu placement, source-of-truth rules, approval boundary rules, pre-copy checks, post-copy checks, no plugin/UI rule, no Supabase rule, no Brain Room routing rule, M work protection, migration execution order, completion checks, and post-migration status.

Relationship To Content Brain Copy Map

This page should be added to the Content Brain Copy Map as:

Current Page: Content Brain Migration Execution Checklist

Classification: MCR Only First

Reason: Migration control checklist used to govern the future movement of prepared operational copy pages into mwmscontentbrain.site. It is not an operational page and should not be copied blindly.

Source Of Truth: MCR

Future Destination: MCR first, possible short operational migration admin checklist later if repeated migrations require it

Future Use: First operational layer migration execution control

Plugin Or UI Later: Possible Migration Execution Checklist UI Later

Relationship To Content Brain Operational Migration Plan

The Content Brain Operational Migration Plan defines the planned first operating version.

The Content Brain Migration Execution Checklist controls the actual migration process when timing is approved.

Operational Migration Plan = what should happen.

Migration Execution Checklist = how to execute it safely.

Relationship To Content Brain First Migration Batch Review

The Content Brain First Migration Batch Review decided which pages belong in the first operational copy batch.

The Migration Execution Checklist controls how that approved batch moves to mwmscontentbrain.site.

First Migration Batch Review = what is in the batch.

Migration Execution Checklist = how the batch is moved.

Relationship To Content Brain Operational Copy Pages

This checklist controls the movement of:

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

Content Brain Internal Linking Strategy Operational Copy

Content Brain Repurposing Operational Copy

Content Brain SEO Refresh Operational Copy

These pages remain MCR-prepared operational copies until migration is approved.

Relationship To MWMS MCR To Brain Copy Rule

This checklist applies the MWMS MCR To Brain Copy Rule to Content Brain migration.

The rule remains:

MCR is source of truth.

Brain sites are operational environments.

Only selected operational pages move.

Governance pages stay in MCR.

Plugin or UI systems are built later only after repeated manual workflow proves the need.

No blind copying.

No uncontrolled migration.

Drift Protection

The system must prevent:

migration starting before approval

copying all MCR Content Brain pages blindly

copying governance pages as operator pages

copying planning pages as operator pages

copying migration-control pages as operator pages

copying future UI specifications as live operator pages

starting plugin or UI build during migration

starting Supabase work during migration

starting Brain Room routing during migration

touching M’s active build

removing source-of-truth notes

removing approval boundaries

renaming pages with dirty titles

placing pages in the wrong menu

creating duplicate destination pages

treating migration as automation

treating prepared operational copies as source-of-truth replacements

Architectural Intent

The Content Brain Migration Execution Checklist exists to bridge the gap between MCR preparation and safe operational migration.

Its architectural role is to ensure that the future mwmscontentbrain.site first layer is built from the prepared operational copy batch, not from raw governance pages or uncontrolled copying.

The goal is to create a simple working Content Brain site that an operator can use manually before any plugin, UI, queue, dashboard, or automation work begins.

The intended path is:

MCR structure

control-page alignment

first migration batch review

operational copy preparation

migration execution checklist

manual mwmscontentbrain.site migration

manual workflow usage

future plugin/UI consideration only after repeated use

Final Rule

Do not begin migration until migration timing is approved.

Do not copy every MCR Content Brain page.

Do not copy governance pages as operator pages.

Do not build plugin/UI systems during migration.

Do not create Supabase structures during migration.

Do not create Brain Room routing during migration.

Do not touch M’s active build.

Only migrate the approved first operational copy batch.

MCR remains the source of truth.

mwmscontentbrain.site becomes the operational working environment only after migration is executed safely.

Change Log

Version: v1.0
Date: 2026-05-24
Author: HeadOffice
Change: Initial creation of Content Brain Migration Execution Checklist. Defines the controlled process for migrating the prepared first operational copy batch from MCR into mwmscontentbrain.site, including migration approval gate, first migration batch, pages not to migrate, menu structure, migration page mapping, pre-copy checklist, post-copy checklist, destination title cleanliness rule, source-of-truth rule, approval boundary rule, no plugin/UI rule, no Supabase rule, no Brain Room routing rule, M work protection rule, migration execution order, menu setup checklist, migration completion checklist, post-migration status, post-migration review questions, future work after migration, and relationships to Content Brain Page Registry, Content Brain Copy Map, Content Brain Operational Migration Plan, Content Brain First Migration Batch Review, operational copy pages, and MWMS MCR To Brain Copy Rule.

Change Impact Declaration

Pages Created:
Content Brain Migration Execution Checklist

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 MIGRATION EXECUTION CHECKLIST v1.0