MWMS Content Brain

Content Brain

Brain Name: Content Brain
Document Type: Brain Homepage
Status: Active
Version: v1.4
Authority: HeadOffice
Applies To: Content Brain operational reference layer, mwmscontentbrain.site page navigation, first operational layer, manual workflow use, content planning, content briefing, publishing readiness, affiliate content packs, affiliate funnel support, SEO content briefs, internal linking, repurposing, refresh, and future Content Brain operational use
Parent: Top Level
Last Reviewed: 2026-05-24

Operational Copy Notice

This page is the operational homepage for Content Brain on mwmscontentbrain.site.

MCR remains the source of truth.

If this page conflicts with MCR, the MCR version overrides it.

This page is not a full governance page.

This page is the clean operator index for the first operational Content Brain layer.

Current Operating Status

Content Brain on mwmscontentbrain.site is now in:

First Operational Layer Built / Manual Workflow Only / Plugin UI Not Started

This means:

the first live operational Content Brain layer has been created

the Content Brain homepage is active

all first-layer child pages are active under Content Brain

MCR remains the source of truth

mwmscontentbrain.site is the operational working environment

manual workflow must prove need before plugin or UI build

no Content Brain plugin or UI build has started

no Supabase work has started

no Brain Room routing has started

no queue, dashboard, generator, or automation build has started

M’s active build areas remain untouched

Purpose

Content Brain is the working home for MWMS content planning, content briefing, publishing readiness, affiliate content support, SEO content support, internal linking, repurposing, and refresh work.

Its role is to help MWMS create and maintain content that is:

useful

structured

clear

trustworthy

search-aligned

intent-aligned

conversion-supportive

affiliate-supportive

refreshable

repurposable

connected to the wider MWMS system

Content Brain does not create content randomly.

Every meaningful content asset should have:

a clear source

a clear purpose

a defined audience

a defined content type

a review path

a destination

a handoff path

a feedback path

an approval owner where needed

Source Of Truth Rule

MCR defines Content Brain.

mwmscontentbrain.site operates Content Brain.

MCR remains the source of truth for:

Content Brain Canon

Content Brain Architecture

Content Brain Page Registry

Content Brain Copy Map

Content Brain migration planning

Content Brain migration execution control

Content Brain first operational layer build planning

governance boundaries

source-of-truth decisions

mwmscontentbrain.site should contain operator-useful working pages.

It should not become a duplicate archive of all MCR pages.

First Operational Layer

The first operational Content Brain layer is now built.

The active operator pages are:

Content Brain

Content Brain Affiliate Content Packs

Content Brain Affiliate Funnel Support

Content Brain Content Briefs

Content Brain Internal Linking

Content Brain Publishing Readiness

Content Brain Refresh

Content Brain Repurposing

Content Brain SEO Content Briefs

Content Brain Workflow

These pages create the first practical manual version of Content Brain on mwmscontentbrain.site.

Do not add queues, dashboards, generators, automations, or plugin screens until manual workflow use proves the need.

Start Here

Use this page as the operational index for Content Brain.

The first working page to open when starting Content Brain work is:

Content Brain Workflow

Use Content Brain Workflow to decide:

where a content request starts

which Brain owns authority

how content should be classified

when a brief is required

which checklist applies

when content should be reviewed

when content moves to refresh

when content moves to repurposing

where signals should feed back

If the work is not ready for content action, park it or send it back to the correct Brain.

Operator Starting Points

Use the task type to decide where to go next.

Content Brain Workflow

Use this page when deciding how a content request should move through Content Brain.

Use it for:

new content requests

content classification

workflow stage decisions

parking decisions

routing decisions

handoff decisions

signal feedback decisions

Start here when the content request is unclear.

Content Brain Content Briefs

Use this page when content needs a structured brief before drafting or handoff.

Use it for:

general content briefs

affiliate support briefs

affiliate product content pack briefs

affiliate funnel support briefs

YouTube support briefs

VEO3 pre-video support briefs

email briefs

social briefs

refresh briefs

repurposing briefs

Use this page before drafting meaningful content.

Content Brain Publishing Readiness

Use this page before content is published, handed off, repurposed, refreshed, or used.

Use it to check:

purpose

audience

brief alignment

message clarity

structure

usefulness

accuracy

claim risk

compliance sensitivity

approval owner

handoff destination

signal to watch

Publishing readiness is an operational checkpoint.

It is not final strategic approval.

Content Brain Affiliate Content Packs

Use this page when planning structured content support for an affiliate product or offer.

Use it for:

affiliate product content packs

pre-sell assets

FAQ assets

objection-handling assets

trust assets

YouTube support assets

VEO3 pre-video support assets

email support assets

social support assets

internal linking notes

repurposing notes

Affiliate content packs do not approve offers.

They only structure content support for approved or review-ready affiliate opportunities.

Content Brain Affiliate Funnel Support

Use this page when mapping content to affiliate funnel stages.

Use it for:

problem awareness

solution awareness

product education

trust building

pre-sell support

comparison support

objection handling

VSL or product page support

follow-up support

repurposing

refresh

signal feedback

Affiliate funnel support does not approve offers, campaigns, budgets, claims, tests, or compliance decisions.

Content Brain SEO Content Briefs

Use this page when creating search-aligned content briefs.

Use it for:

SEO articles

authority articles

topic cluster articles

pillar pages

comparison pages

review support pages

affiliate support articles

pre-sell articles

refresh briefs

search intent planning

SERP pattern notes

information gain planning

E E A T planning

internal linking planning

SEO content must serve the reader first.

Do not create thin content only to target keywords.

Content Brain Internal Linking

Use this page when planning how content assets should connect across the site.

Use it for:

reader journey support

topic cluster linking

hub and spoke linking

affiliate funnel support links

trust links

refresh links

repurposing links

internal authority flow

orphan page reduction

Internal links must help the reader.

Do not force links only for SEO.

Content Brain Repurposing

Use this page when adapting approved content into another useful format.

Use it for:

articles into emails

articles into social posts

articles into YouTube descriptions

articles into VEO3 pre-video support ideas

FAQ into social or email content

trust content into funnel support

comparison content into short-form support

approved affiliate content into support assets

Repurposing must preserve meaning.

Do not strengthen claims.

Do not add new claims without review.

Do not change compliance risk without approval.

Content Brain Refresh

Use this page when improving existing content based on a clear trigger.

Use it for:

SEO refresh

content improvement

outdated content updates

search intent review

research update review

claim review

internal link updates

affiliate content refresh

comparison content refresh

FAQ refresh

trust content refresh

merge review

redirect review

retirement review

repurposing review

Refresh work should not happen randomly.

There must be a clear reason to update, improve, merge, redirect, retire, repurpose, monitor, or park the content.

Working Rule

When using Content Brain, follow this basic order:

  1. Open Content Brain Workflow.
  2. Classify the content request.
  3. Confirm which Brain owns authority.
  4. Decide whether the request is new content, refresh, repurposing, affiliate support, SEO support, funnel support, internal linking support, or publishing readiness review.
  5. Create a brief using Content Brain Content Briefs or Content Brain SEO Content Briefs.
  6. Use Content Brain Affiliate Content Packs or Content Brain Affiliate Funnel Support where affiliate content is involved.
  7. Use Content Brain Internal Linking where page connection planning is needed.
  8. Use Content Brain Repurposing when approved content is being adapted into another format.
  9. Use Content Brain Refresh when existing content needs improvement.
  10. Use Content Brain Publishing Readiness before content is used, handed off, published, refreshed, or repurposed.
  11. Confirm claims, compliance risk, approval owner, destination, and signal to watch.
  12. Send useful signals back to the correct Brain.

Content Request Types

Content Brain may support:

SEO articles

authority content

affiliate support content

affiliate funnel content

affiliate product content packs

comparison content

review support content

YouTube descriptions

YouTube script support

VEO3 pre-video support

email content

newsletter content

social content

internal linking plans

topic cluster support

refresh plans

repurposing plans

trust-building assets

pre-sell assets

FAQ content

objection-handling content

landing page support content

message match support content

AIBS education content

sales support content

conversion support content

Approval Boundaries

Content Brain can prepare, structure, review, and support content.

Content Brain does not approve:

affiliate offers

research verdicts

search validation

campaign budgets

ad testing

campaign scaling

finance decisions

compliance-sensitive claims

experimental validity

sales progression

Data Brain signal reliability

Supabase task routes

Brain Room integration

HeadOffice reporting

live plugin execution

Those belong to the relevant Brain, system, protocol, or implementation layer.

Relationship To Other Brains

Affiliate Brain

Content Brain supports Affiliate Brain with:

pre-sell content

comparison content

review support content

problem-aware articles

objection-handling content

authority support pages

trust-building pages

offer education content

affiliate FAQ content

YouTube description support

VEO3 pre-video support

email support content

repurposed affiliate support assets

affiliate product content packs

affiliate funnel support maps

Affiliate Brain owns offer logic and affiliate opportunity decisions.

Research Brain

Content Brain uses research signals to create clearer content.

Research Brain owns evidence quality and research verdicts.

Content Brain may return:

content gaps

audience questions

objection patterns

topic traction signals

research gaps found during content planning

affiliate content evidence gaps

Search Intelligence Brain

Content Brain uses search insights to guide SEO content.

Search Intelligence Brain owns search demand, SERP interpretation, query patterns, and search validation.

Content Brain may return:

content opportunity decisions

topic cluster needs

SEO brief requirements

internal linking needs

refresh opportunities

comparison demand content opportunities

Ads Brain

Content Brain supports Ads Brain with:

landing page support content

trust pages

compliance-friendly educational content

YouTube descriptions

YouTube script support

VEO3 pre-video hook support

organic support assets

retargeting content ideas

message match support content

Ads Brain owns campaign logic and ad performance decisions.

Experimentation Brain

Content Brain can prepare content variants for approved tests.

Experimentation Brain owns test validity, experiment design, and experiment verdicts.

Content Brain must not declare winning variants by itself.

Conversion Brain

Content Brain supports Conversion Brain with:

message match content

objection-handling content

FAQ content

proof content

trust content

awareness-stage content

clarity support content

Conversion Brain owns conversion logic.

Sales Brain

Content Brain supports Sales Brain with:

nurture content

sales enablement articles

objection education

follow-up content

trust reinforcement assets

decision support content

Sales Brain owns sales progression.

Compliance Brain

Content Brain can flag claim risk and use safer wording.

Compliance Brain owns final compliance interpretation.

Sensitive claims must not be approved by Content Brain alone.

Finance Brain

Content Brain may identify content work that requires time, tools, contractor support, or operational resources.

Finance Brain owns budget, capital, and resource decisions.

Data Brain

Content Brain may observe content signals.

Data Brain owns data reliability, signal quality, and measurement interpretation.

Content Brain must not over-interpret weak data.

SIT Brain

SIT Brain may later support workflow integrity, queue validation, task completeness checks, and handoff completeness checks.

Content Brain should not depend on SIT automation during the current manual stage.

HeadOffice

Content Brain sends HeadOffice visibility on:

content gaps

content bottlenecks

priority content needs

content risks

cross-brain support needs

repeated workflow friction

useful content signals

HeadOffice governs direction and cross-brain priority.

Legacy Reference Pages

Older Content Brain pages may remain on the site as reference material.

Legacy or older pages should not override the current operational layer.

Treat older pages as reference-only unless reviewed and reclassified.

Do not use legacy pages as the default workflow if a current operational page exists.

Older pages without the current operational naming pattern should be reviewed later for:

renaming

merging

legacy classification

deletion

continued reference use

Do not interrupt the current operational layer build to rename old reference pages unless they create active operator confusion.

Future Plugin Or UI Candidates

The following may become useful later, but should not be built yet:

Content Opportunity Queue UI

Content Production Queue UI

Content Refresh Queue UI

Repurposing Queue UI

Content Operations Dashboard

Affiliate Product Content Pack Generator

Affiliate Product Content Pack Checklist UI

Affiliate Support Content Planner

Content Brief Generator

SEO Brief Generator

Publishing Readiness Checklist UI

Internal Linking Planner

Topic Cluster Planner

Repurposing Planner

SEO Refresh Planner

Content Signal Feedback Dashboard

Migration Readiness Checklist UI

Migration Execution Checklist UI

Manual workflow must prove need first.

No Build Rule

Do not start any of the following from this page:

plugin work

custom UI work

Supabase work

Brain Room routing

automation

queue build

dashboard build

generator build

cross-brain task routing

This page is part of the first manual operational layer only.

Drift Protection

The system must prevent:

Content Brain becoming a duplicate MCR archive

legacy pages being treated as current operational standards

old framework pages being treated as active operator pages

old checklist pages being treated as active operator pages

MCR authority being replaced by operational copies

content being produced without purpose

content being published without review

content being refreshed without a clear trigger

content being repurposed without preserving meaning

internal links being added without reader benefit

affiliate content packs being treated as offer approval

affiliate funnel support being treated as compliance approval

SEO content being created without search intent

publishing readiness being treated as final approval

plugin or UI tools being built before manual workflow proves need

Content Brain taking authority from Affiliate Brain, Research Brain, Search Intelligence Brain, Ads Brain, Experimentation Brain, Conversion Brain, Sales Brain, Compliance Brain, Data Brain, Finance Brain, SIT Brain, or HeadOffice

mwmscontentbrain.site becoming cluttered with unclassified pages

Architectural Intent

Content Brain exists to make content useful, structured, governed, and operationally aligned.

The long-term intent is:

MCR defines Content Brain.

mwmscontentbrain.site operates Content Brain.

Future plugin or UI systems automate repeated Content Brain workflows only after manual use proves the need.

Content Brain should help MWMS produce better content, not more random content.

The current phase is about completing and validating a clean manual operating layer before adding automation.

Current First Layer Validation

The first operational Content Brain layer now includes:

Content Brain

Content Brain Affiliate Content Packs

Content Brain Affiliate Funnel Support

Content Brain Content Briefs

Content Brain Internal Linking

Content Brain Publishing Readiness

Content Brain Refresh

Content Brain Repurposing

Content Brain SEO Content Briefs

Content Brain Workflow

These pages should remain:

published or intentionally draft

under the correct parent

free from version numbers in the WordPress title

free from dash characters in the WordPress title

free from “Operational Copy” in the WordPress title

free from old map, checklist, standard, or framework titles as active operator pages

Final Rule

Content Brain is the working environment.

MCR is the source of truth.

Use the active operational pages first.

Treat legacy pages as reference only.

No blind copying.

No uncontrolled migration.

No plugin or UI build before workflow need is proven.

No Supabase work from this page.

No Brain Room routing from this page.

When unsure, route the decision back to the correct Brain.

Change Log

Version: v1.4
Date: 2026-05-24
Author: HeadOffice
Change: Updated existing mwmscontentbrain.site Content Brain homepage from v1.3 to v1.4 after completion of the first 10-page operational layer. Replaced shortened page-name references with the final live-site page titles, added completed first operational layer status, cleaned homepage purpose as operator index, added active operator page summaries, reinforced legacy page handling, expanded current first layer validation, and preserved manual workflow-only boundaries. Removed homepage drift toward detailed checklist/workflow content and restored the page as a clean navigation and operating index.

Version: v1.3
Date: 2026-05-24
Author: HeadOffice
Change: Updated existing mwmscontentbrain.site Content Brain homepage from v1.2 to v1.3. Preserved the operational homepage role and version history while aligning the page with the current Content Brain MCR closeout state, Content Brain Page Registry v3.0, Content Brain Copy Map v2.5, Content Brain Migration Execution Checklist, mwmscontentbrain.site First Operational Layer Build Checklist, first operational layer build phase, manual workflow-only rule, updated operator starting points, first operational layer page set, approval boundaries, no plugin/UI rule, no Supabase rule, no Brain Room routing rule, and source-of-truth discipline.

Version: v1.2
Date: 2026-05-08
Author: HeadOffice
Change: Rebuilt Content Brain homepage on mwmscontentbrain.site as an operational navigation index after first migration group completion. Added active operational page groups, legacy reference section, MCR source-of-truth section, future plugin or UI candidates, working rule, and clearer live-site navigation purpose.

Version: v1.1
Date: 2026-05-08
Author: HeadOffice
Change: Updated operational Content Brain page for mwmscontentbrain.site. Added Operational Copy Notice, Source Of Truth Rule, operational role, migration discipline, relationship to Content Brain Copy Map and Page Registry, future plugin or UI candidate logic, expanded cross-brain relationships, drift protection, and clarified that mwmscontentbrain.site is an operational copy while MCR remains source of truth.

Version: v1.0
Date: 2026-03-29
Author: HeadOffice
Change: Initial structural definition of Content Brain.

Change Impact Declaration

Pages Created:
None

Pages Updated:
Content Brain

Pages Deprecated:
None

Registries Requiring Update:
None

Canon Version Update Required:
No

Change Log Entry Required:
No

END CONTENT BRAIN v1.4