Brain Name: Content Brain
Document Type: Canon Reference
Status: Governance Reference
Version: v1.1
Authority: MWMS HeadOffice
Applies To: Content Brain, mwmscontentbrain.site, MCR, HeadOffice Brain, Research Brain, Search Intelligence Brain, Affiliate Brain, Ads Brain, Experimentation Brain, Conversion Brain, Compliance Brain, Data Brain, Finance Brain, Strategy Brain, SIT Brain, future Content Brain system wiring, and all MWMS content structures
Parent: Content Brain
Enforcement Mode: Structural
Last Reviewed: 2026-06-03
Operational Canon Notice
This page is the live-site Canon reference for Content Brain on mwmscontentbrain.site.
MCR remains the source of truth.
If this page conflicts with the MCR source-of-truth version, MCR overrides it.
This page does not replace MCR.
This page exists to define the governing identity, boundaries, purpose, and operating principles of Content Brain on the live Content Brain site.
This page should be read alongside:
Content Brain Architecture
Content Brain Page Registry
Content Brain Cross-Brain Integration Map
Content Brain Workflow
Content Brain Publishing Readiness
The Architecture page explains the live-site structure.
The Page Registry tracks the page set.
The Cross-Brain Integration Map explains how Content Brain works with other Brains.
This Canon defines the governing principles behind Content Brain.
Current Status Notice
Content Brain now has:
a clean first operational layer
a reviewed active reference framework layer
a legacy reference layer
a Cross-Brain Integration Map
an updated Page Registry
an updated Architecture page
manual-first workflow discipline
future build-readiness direction
Content Brain is not yet a plugin/UI system.
Content Brain is not yet automated.
Content Brain is currently an operational knowledge and workflow structure that should be used manually until repeated workflow patterns prove what should be systemised later.
Purpose
The Content Brain governs the structural role of content inside MWMS.
Its purpose is to ensure all content assets:
support economic outcomes
align with lifecycle stage requirements
remain structurally consistent across Brains
operate within persuasion safety limits
strengthen trust and comprehension
improve conversion readiness
reduce friction in decision environments
support search usefulness
support affiliate education
support ad-to-content message match
support internal linking
support refresh discipline
support repurposing discipline
support publishing readiness
return learning signals to the wider MWMS ecosystem
Content inside MWMS is treated as a system component rather than a creative activity.
Content must serve structural function.
Content must not operate independently of governance.
Content Brain is not merely a content-writing Brain.
Content Brain is the communication-structure Brain.
Its role is to translate intelligence into useful, structured, trustworthy, reviewable content systems.
Canon Position
Content Brain sits between intelligence and communication output.
It receives intelligence from other Brains.
It produces structured communication assets, briefs, support pages, content plans, and readiness checks.
It improves the way MWMS communicates with audiences, prospects, readers, buyers, and internal operators.
Content Brain should help the wider ecosystem communicate clearly.
It should not become a random article factory.
It should not create uncontrolled creative output.
It should not take authority from other Brains.
Core Principle
Content must improve understanding.
Understanding improves trust.
Trust improves decision comfort.
Decision comfort improves conversion stability.
Conversion stability improves system learning.
System learning improves future decisions.
Content Brain exists to create structured communication that supports this loop.
Content should not exist because it is easy to generate.
Content should exist because it serves a clear purpose inside MWMS.
Scope
This Canon applies to:
educational content
bridge pages
advertorial structures
pre-frame content
mechanism explanation content
offer explanation content
trust-building content
belief-alignment content
comparison content
authority positioning content
problem awareness content
SEO content
affiliate support content
affiliate product content packs
affiliate funnel support content
internal linking plans
repurposing plans
refresh plans
publishing readiness checks
YouTube description support
VEO3 pre-video support
email support content
landing page support content
FAQ content
objection-handling content
content supporting Affiliate Brain outputs
content supporting Ads Brain outputs
content supporting Conversion Brain outputs
content supporting Search Intelligence Brain outputs
content supporting Research Brain outputs
content supporting Experimentation Brain outputs
content supporting HeadOffice visibility
This Canon governs how content functions structurally inside MWMS.
This Canon does not govern publishing schedules by itself.
This Canon does not govern editorial calendar execution by itself.
This Canon does not authorize plugin, UI, Supabase, automation, queue, dashboard, generator, or Brain Room build work by itself.
Definition
Content is defined as structured communication designed to:
increase clarity
reduce uncertainty
support decision confidence
explain problems
explain solutions
explain mechanisms
support trust
support comparison
support reader intent
support search usefulness
support affiliate education
support conversion readiness
support message continuity
support audience progression
support internal linking
support system learning
Content is not limited to articles.
Content may include scripts, briefs, emails, landing support, video support, trust assets, FAQ assets, comparison assets, repurposing assets, and refresh instructions.
Content Brain Mission
Content Brain exists to:
turn intelligence into structured content
turn audience problems into clear explanations
turn search intent into useful content briefs
turn offer needs into affiliate support assets
turn conversion friction into decision-support content
turn trust gaps into trust-building content
turn old assets into refreshed or repurposed assets
turn page relationships into internal linking plans
turn vague ideas into structured briefs or parked requests
turn content signals into useful feedback for the correct Brain
Content Brain should make communication cleaner, safer, more useful, and more system-aligned.
Active Operational Layer
The current active operational layer on mwmscontentbrain.site is:
Content Brain
Content Brain Workflow
Content Brain Content Briefs
Content Brain SEO Content Briefs
Content Brain Affiliate Content Packs
Content Brain Affiliate Funnel Support
Content Brain Publishing Readiness
Content Brain Internal Linking
Content Brain Repurposing
Content Brain Refresh
These pages are the first pages operators should use for current Content Brain work.
The active operational layer takes priority over older legacy pages.
Active Reference Layer
Content Brain also has active reference frameworks.
These support deeper reasoning but do not replace the operator layer.
Active reference frameworks include:
Content Brain Content Optimization Framework
Content Brain Content Production System Framework
Content Brain Conversion Support Framework
Content Brain E E A T Content Trust Framework
Content Brain Information Gain Framework
Content Brain Intent Alignment Framework
Content Brain Topic Architecture Framework
Content Brain Topic Cluster And Hub Architecture Framework
These pages help operators reason more deeply about quality, trust, intent, information gain, production, topic structure, conversion support, and optimization.
They should be used when needed, not as the first workflow step.
Integration Layer
Content Brain now includes:
Content Brain Cross-Brain Integration Map
This page defines how Content Brain connects with:
HeadOffice Brain
Research Brain
Search Intelligence Brain
Affiliate Brain
Ads Brain
Experimentation Brain
Conversion Brain
Compliance Brain
Data Brain
Finance Brain
Strategy Brain
SIT Brain
The Integration Map explains:
inputs from other Brains
outputs to other Brains
authority boundaries
future wiring candidates
future AI Employee candidates
manual-first integration rules
M build handoff rules
Content Brain must work with the wider MWMS ecosystem.
It should not operate as an isolated content site.
Governance Layer
Content Brain governance is supported by:
Content Brain Canon
Content Brain Architecture
Content Brain Page Registry
Content Brain Cross-Brain Integration Map
These pages define:
identity
structure
page status
integration direction
source-of-truth discipline
future build-readiness logic
The Page Registry should be updated when Content Brain’s live structure materially changes.
The Architecture page should be updated when the structure changes.
The Canon should only be updated when the governing identity or boundaries change.
Legacy Reference Layer
Content Brain contains legacy reference pages.
Legacy pages may contain useful historical logic, but they are not active operator standards.
Legacy pages should not override:
Content Brain Workflow
Content Brain Content Briefs
Content Brain SEO Content Briefs
Content Brain Affiliate Content Packs
Content Brain Affiliate Funnel Support
Content Brain Publishing Readiness
Content Brain Internal Linking
Content Brain Repurposing
Content Brain Refresh
Legacy pages should be used only for:
historical reference
future merge planning
cleanup review
possible future field extraction
Legacy pages should not drive current workflow.
Current Legacy Rule
Default rule:
Keep legacy pages as Legacy Reference unless clearly replaced and useless.
Do not delete unless:
replacement page is confirmed
historical logic has no future value
page creates active operator confusion
page is not needed for future merge or audit
Do not rename older legacy pages until the full page is being updated.
Cross-Brain Authority Rule
Content Brain must support other Brains without taking their authority.
Content Brain does not own:
research verdicts
search validation
offer approval
affiliate opportunity approval
ad campaign approval
conversion architecture
compliance interpretation
data reliability
budget decisions
experiment verdicts
technical wiring
plugin UI
Supabase schema
Brain Room routing
automation execution
Content Brain may support these areas through structured content, but the responsible Brain retains authority.
Research Brain Relationship
Research Brain owns evidence quality, source review, market interpretation, problem validation, audience research, and customer language.
Content Brain uses Research Brain outputs to create content briefs, topic structures, support assets, and content plans.
Content Brain may return content gaps, reader confusion signals, or question patterns to Research Brain.
Content Brain must not invent evidence.
Search Intelligence Brain Relationship
Search Intelligence Brain owns search validation, SERP interpretation, query intent, keyword clusters, and search opportunity assessment.
Content Brain uses Search Intelligence outputs to create SEO content briefs, topic clusters, internal linking plans, refresh plans, and search-useful content structures.
Content Brain must not treat a topic as search-validated unless Search Intelligence Brain confirms it where search matters.
Affiliate Brain Relationship
Affiliate Brain owns offer evaluation, affiliate opportunity status, offer logic, testing readiness, and pre-sell requirements.
Content Brain supports Affiliate Brain through affiliate content packs, funnel support, FAQ content, trust assets, comparison support, YouTube support, VEO3 support, and pre-sell content.
Content Brain must not approve offers.
Content Brain must not treat unclear offer status as approved.
Ads Brain Relationship
Ads Brain owns campaign structure, ad testing, paid traffic decisions, targeting, and performance decisions.
Content Brain supports Ads Brain with YouTube descriptions, message match support, landing page support, VEO3 pre-video support, trust assets, FAQ content, and ad-to-content continuity.
Content Brain must not approve campaigns.
Experimentation Brain Relationship
Experimentation Brain owns test design, test validity, experimental control, and verdicts.
Content Brain may produce content variants, angle-support content, pre-sell variants, message sequence variants, and signal-to-watch definitions.
Content Brain must not declare winners.
Conversion Brain Relationship
Conversion Brain owns conversion architecture, friction reduction, message match, CTA logic, and decision-environment structure.
Content Brain supports Conversion Brain with trust content, FAQ content, objection-handling content, decision guides, expectation-setting content, and conversion-support assets.
Content Brain supports conversion readiness but does not own conversion logic.
Compliance Brain Relationship
Compliance Brain owns sensitive claim interpretation.
Content Brain must flag risk when content includes:
health claims
income claims
finance claims
legal claims
product performance claims
testimonials
guarantees
scarcity
urgency
comparisons
affiliate recommendations
Content Brain may prepare content, but it must not approve sensitive claims.
Data Brain Relationship
Data Brain owns measurement reliability, signal confidence, tracking quality, dashboard standards, and data interpretation.
Content Brain may define signals to watch and observe content behaviour, but Data Brain owns reliability and interpretation where decisions depend on data.
Content Brain must not over-interpret weak signals.
Finance Brain Relationship
Finance Brain owns capital, budget, tool-spend, contractor approval, and resource decisions.
Content Brain may estimate workload, production needs, and future build candidates.
Content Brain must not approve spending.
Strategy Brain Relationship
Strategy Brain owns long-term positioning, narrative direction, strategic themes, and business model alignment.
Content Brain supports Strategy Brain through structured messaging, topic clarity, content themes, and narrative consistency.
Content Brain must not override strategic direction.
SIT Brain Relationship
SIT Brain owns system integrity, source-of-truth discipline, naming discipline, structural governance, and drift protection.
Content Brain must respect SIT rules.
Content Brain should escalate drift concerns, duplicate page risks, source-of-truth conflicts, and naming conflicts.
Structural Safety Rules
Content must remain:
clear
accurate
useful
reader-aligned
trustworthy
claim-safe
approval-aware
source-of-truth aligned
cross-brain aware
structurally consistent
Content must not:
mislead
manipulate
overclaim
invent experience
invent evidence
hide risk
create false urgency
create false expectations
bypass approval owners
override other Brain authority
Persuasion Safety Rule
Content may support persuasion, but persuasion must remain safe.
Content may improve:
clarity
trust
decision confidence
problem understanding
solution understanding
expectation alignment
objection reduction
offer interpretation
Content must not use persuasion to distort perception.
Content should help the reader make a better decision.
Manual-First Rule
Content Brain must remain manual-first until workflows are proven.
Manual-first means:
operators use the pages directly
repeatable workflows are observed
useful fields become clear
handoff friction becomes visible
status paths become clear
build candidates are identified only after repeated use
Manual-first is not the final goal.
Manual-first is the proving stage before system build.
Future Build-Readiness Rule
Future Content Brain systems may include:
Content Opportunity Queue
Content Production Queue
Content Refresh Queue
Content Repurposing Queue
Content Operations Dashboard
Content Brief Generator
SEO Brief Generator
Affiliate Content Pack Generator
Affiliate Funnel Support Planner
Internal Linking Planner
Publishing Readiness Checklist UI
Content Signal Feedback Dashboard
Cross-Brain Handoff Router
Content Brain AI Employee Router
Content Brain Task Status Dashboard
Content Brain Integration Log
These should only be built after manual workflow proves the need.
Build-Ready Specification Rule
M should eventually wire proven Content Brain logic.
M should not be expected to invent Content Brain logic from scattered page ideas.
A future build-ready specification must include:
workflow name
purpose
input fields
output fields
status values
source Brain
destination Brain
approval rules
risk rules
handoff rules
parking rules
dashboard needs
data needs
user role needs
manual workflow evidence
priority level
Until this exists, the workflow should remain manual.
Operator Rule
For current Content Brain work, the operator should:
use Content Brain Workflow first when work is unclear
use Content Brain Content Briefs for general briefs
use Content Brain SEO Content Briefs for search content
use Content Brain Affiliate Content Packs for affiliate offer support
use Content Brain Affiliate Funnel Support for funnel-stage support
use Content Brain Publishing Readiness before handoff or use
use Content Brain Internal Linking for page relationships
use Content Brain Repurposing for approved reuse
use Content Brain Refresh for existing content improvement
use active reference frameworks when deeper reasoning is needed
use Content Brain Cross-Brain Integration Map when cross-brain relationships matter
use Content Brain Page Registry when page status is unclear
Naming Rule
Live-site page titles should follow these rules:
Use full Content Brain prefix for current active pages.
Do not use version numbers in page titles.
Do not use “Operational Copy” in live-site titles.
Do not use shortened names for active operator pages.
Do not keep old map, checklist, or framework titles as active operator pages if replaced.
Do not rename older legacy pages until they are being updated.
Content Brain homepage remains Top Level.
Main child pages sit under Parent: Content Brain.
Page Status Rule
Use page status labels consistently.
Accepted status labels include:
Active
Active Operational Page
Active Integration Map
Active Reference Framework
Active Operational Registry
Active Architecture Reference
Governance Reference
Legacy Reference
Legacy Role Reference
Retired
Parked
Do not use Active Framework for old pages that are no longer active operator standards.
Do not treat legacy pages as active workflow pages.
Drift Protection
This Canon must prevent:
Content Brain becoming a random article factory
Content Brain acting as a standalone content site
Content Brain taking authority from other Brains
legacy pages overriding active pages
duplicate page creation
wrong parent placement
title drift
status drift
old framework confusion
premature plugin or UI build
manual workflow evidence being skipped
M being handed vague build tasks
mwmscontentbrain.site replacing MCR source-of-truth authority
content being created without purpose
content being created without approval owner
content being created without handoff destination
content being created without reader intent
content being created without claim safety awareness
Architectural Intent
Content Brain Canon defines the governing identity and boundaries of Content Brain.
The long-term intent is for Content Brain to become:
clean
manual-first
workflow-proven
cross-brain aware
integration-ready
build-ready later
Content Brain should help the wider MWMS ecosystem communicate clearly.
It should translate intelligence into structured, useful, trustworthy, build-ready content systems.
It should not become a random content-production machine.
It should not replace other Brains.
It should prepare the logic that M can later wire into the wider MWMS system.
Final Rule
Content Brain is the communication-structure Brain.
It must support the wider MWMS ecosystem through clear, useful, trustworthy content systems.
It must respect source-of-truth discipline.
It must respect other Brain authority.
It must remain manual-first until workflows are proven.
It must become build-ready only through repeated use, clear fields, clear outputs, and clean handoff logic.
M should wire proven Content Brain logic, not vague ideas.
Change Log
Version: v1.1
Date: 2026-06-03
Author: HeadOffice
Change: Updated Content Brain Canon from older March 2026 live-site reference copy into Governance Reference status. Added current Content Brain operational layer, active reference layer, integration layer, governance layer, cross-brain authority relationships, manual-first rule, future build-readiness rule, M build-ready specification rule, operator rule, naming rule, status rule, drift protection, and integration-ready direction. Clarified that Content Brain is the communication-structure Brain and that M should later wire proven logic, not vague ideas.
Version: v1.0
Date: 2026-03-29
Author: MWMS HeadOffice
Change: Initial Content Brain Canon reference copy from March 2026 Content Brain structure.
Change Impact Declaration
Pages Created:
None
Pages Updated:
Content Brain Canon
Pages Renamed:
None
Pages Deprecated:
None
Registries Requiring Update:
Content Brain Page Registry should be updated later only if this Canon status change is tracked separately.
Canon Version Update Required:
No further Canon update required after this page is saved.
Change Log Entry Required:
No separate change log entry required unless HeadOffice decides to track Canon updates in the registry later.
END CONTENT BRAIN CANON v1.1