Brain Name: Content Brain
Document Type: Operating Model
Status: Active
Version: v1.1
Authority: Content Brain under HeadOffice governance
Applies To: Content Brain structure, operating boundaries, working responsibilities, MCR planning, future migration to mwmscontentbrain.site, affiliate content deployment, research-backed content execution, search demand content planning, AIBS education content, and cross-brain content support
Parent: Content Brain
Last Reviewed: 2026-05-24
Content Brain Operating Model
Purpose
The Content Brain Operating Model defines how Content Brain functions inside the MWMS ecosystem.
This page exists to clarify:
what Content Brain is responsible for
what Content Brain is not responsible for
how Content Brain receives work
how Content Brain produces useful outputs
how Content Brain supports other Brains
how Content Brain turns approved signals into structured content assets
how Content Brain supports Affiliate Brain product testing
how Content Brain uses Research Brain as the truth layer
how Content Brain uses Ads Brain as an attention and hook signal layer
how Content Brain uses Experimentation Brain as a learning quality layer
how Content Brain uses AIBS Brain as an authority and education source
how Content Brain uses Search Intelligence Brain as a demand source
how Content Brain respects Compliance Brain as a risk gate
how Content Brain respects Finance Brain as a content investment discipline layer
how Content Brain may later connect to SIT Brain for workflow integrity
how Content Brain sends signals back into the system
how Content Brain remains separate from M’s active build work
how Content Brain should later move from MCR into mwmscontentbrain.site
Content Brain is not just a writing area.
Content Brain is the structured content execution system of MWMS.
Its role is to turn approved intelligence, priorities, offers, research, search demand, ad learning, product opportunities, authority needs, and audience signals into useful content assets that support growth, authority, trust, conversion, education, and long-term system learning.
Scope
This operating model applies to:
Content Brain structure inside MCR
future Content Brain operational use on mwmscontentbrain.site
content planning
SEO content planning
authority content planning
affiliate product content planning
affiliate support content planning
content opportunity planning
content production
content optimization
content refresh
content repurposing
content quality review
content signal feedback
content handoff planning
AIBS education content planning
search demand content planning
ad-support content planning
experiment-support content planning
cross-brain content support
This page governs the operating role of Content Brain.
It does not govern:
Content Brain Canon authority by itself
Content Brain technical implementation
plugin development
Supabase schema design
Brain-to-Brain request automation
HeadOffice reporting screens
Affiliate Brain opportunity approval
Research Brain intelligence ownership
Ads Brain campaign execution
Experimentation Brain test verdicts
Finance Brain capital approval
Compliance Brain compliance decisions
SIT Brain integrity enforcement
M’s active build areas
Those remain governed by their own Brains, protocols, standards, or implementation layers.
Core Principle
Content Brain turns approved system intelligence into structured content assets.
Content Brain should not create content randomly.
Every content item should have:
a source
a purpose
a target audience
a content type
a system role
a review path
a handoff destination
a feedback path
If a content request does not have these elements, it should remain in review until the purpose is clear.
Content Brain must not become a general writing assistant.
Content Brain must operate as a governed execution Brain that creates content only when the content supports a defined system purpose.
Governance Role
Content Brain is an Execution Layer Brain.
It operates under HeadOffice governance.
Content Brain supports system execution by producing and improving content assets.
Content Brain does not override Canon, strategy, capital, experimentation, compliance, research, offer approval, finance, or cross-brain authority.
Content Brain must respect the wider MWMS Brain structure, where Content Brain sits in the Execution Layer and produces content, authority, funnel-support, search, and audience-intent assets that can feed intelligence and feedback loops.
Relationship To MCR
MCR remains the source of truth.
The MCR version of Content Brain defines:
governance alignment
operating structure
framework logic
workflow rules
migration classification
cross-brain boundaries
future plugin or UI candidates
MCR does not need to be duplicated fully into mwmscontentbrain.site.
MCR defines how Content Brain should work.
The future Content Brain site should only contain the operational pages needed to make Content Brain usable.
Relationship To mwmscontentbrain.site
mwmscontentbrain.site is the future operational Content Brain environment.
It should eventually contain working pages such as:
Content Brain home page
Content Brain Workflow Map
Content Brain SEO Content Brief Standard
Content Brain Content Production System Framework
Content Brain Content Optimization Framework
Content Brain Content Repurposing Framework
Content Brain Topic Architecture Framework
Content Brain Internal Linking Strategy Framework
Content Brain Affiliate Funnel Support Map
Content Brain Publishing Readiness Checklist
Content Brain Content Brief Template
Content Brain Content Production Queue
Content Brain Content Refresh Queue
Content Brain Repurposing Queue
Content Brain Content Operations Dashboard
Content Brain Content Opportunity Queue
Content Brain Affiliate Product Content Pack
The live site should not become a full duplicate of MCR.
It should contain only the pages that support real operational use.
MCR To Brain Classification
Current classification for this page:
Destination: Copy To Content Brain Later
Reason: Operational structure and Brain orientation
Source Of Truth: MCR
Future Use: Reference page explaining how Content Brain works inside mwmscontentbrain.site
Future Plugin Or UI: No direct plugin requirement
This page may later be simplified for mwmscontentbrain.site as an operator-facing overview.
The MCR version remains the full structural source of truth.
Content Brain Primary Role
Content Brain is responsible for converting approved inputs into useful content assets.
Its primary role is:
to plan, produce, review, improve, refresh, and repurpose content that supports MWMS growth, authority, trust, conversion, education, affiliate testing, search visibility, and learning.
Content Brain helps MWMS create content that is:
useful
structured
audience-aware
search-aware
trust-aware
funnel-aware
offer-aware
research-backed
compliance-aware
reusable
measurable
connected to system learning
Content Brain Owns
Content Brain owns:
content planning
content request classification
content opportunity classification
content brief creation
SEO content structure
article structure
topic architecture
topic cluster planning
authority content planning
affiliate support content planning
affiliate product content pack planning
content production workflows
content optimization workflows
content refresh planning
content repurposing planning
editorial consistency
information gain checks
internal linking planning
publishing readiness checks
content quality checks
content performance review at the content level
content signal feedback at the content level
Content Brain may produce or support:
blog posts
SEO articles
pillar pages
topic cluster pages
comparison pages
review support content
pre-sell content
FAQ content
authority pages
trust pages
product support pages
affiliate support pages
YouTube scripts
VEO3 pre-video scripts
YouTube descriptions
email drafts
newsletter content
social content
content outlines
content briefs
content refresh plans
repurposing plans
internal linking plans
AIBS education content
client-facing explainers
research brief summaries
Content Brain Does Not Own
Content Brain does not own:
offer approval
opportunity approval
affiliate testing decisions
research verdicts
paid ad campaign decisions
creative testing authority
campaign scaling decisions
capital allocation
statistical validation
compliance approval
final business strategy
Brain-to-Brain routing implementation
Supabase task routes
HeadOffice command dashboards
plugin screens
automation execution
live publishing authority unless explicitly granted
Content Brain supports these areas with content, but it does not own their final decisions.
Operating Boundaries
Content Brain must remain inside its execution role.
It may support other Brains, but it must not absorb their authority.
Content Brain should be powerful, but bounded.
Its power comes from turning approved intelligence into structured assets, not from making decisions that belong to other Brains.
Affiliate Product Content Deployment Role
Content Brain plays a major support role in affiliate product deployment.
When Affiliate Brain identifies an approved or review-ready product opportunity, Content Brain may prepare the content assets needed to support testing, trust-building, education, and funnel readiness.
Content Brain may support affiliate product deployment with:
product support pages
pre-sell articles
FAQ content
objection-handling content
comparison articles
review support content
problem-aware articles
trust-building pages
authority support articles
YouTube scripts
VEO3 pre-video hook scripts
ad support angle notes
social post sets
email follow-up drafts
repurposing plans
internal linking plans
compliance risk notes
research requirement notes
Content Brain does not approve the product.
Content Brain does not decide whether the product should be tested.
Content Brain does not decide budget.
Content Brain does not decide campaign structure.
Content Brain does not approve claims.
Content Brain turns an approved or review-ready affiliate opportunity into a structured content pack.
Research Brain As Truth Layer
Research Brain owns research intelligence, evidence gathering, market investigation, source validation, customer insight, and research verdicts.
Content Brain uses Research Brain as the truth layer.
Content Brain may use Research Brain outputs to create:
better briefs
better articles
more accurate content
audience-aware content
problem-aware content
voice-of-customer-informed content
search-intent-informed content
competitor-aware content
affiliate support content
authority content
trust-building content
Content Brain does not replace Research Brain.
Content Brain does not invent missing evidence.
Content Brain does not create unsupported claims when research is incomplete.
If the research base is weak, Content Brain must flag the gap and request more research.
Ads Brain As Attention And Hook Testing Layer
Ads Brain owns campaign structure, ad testing, hook testing, creative testing, paid traffic execution, and paid attention signals.
Content Brain may use Ads Brain signals to understand:
which hooks attract attention
which angles create curiosity
which objections appear in paid traffic
which messages create engagement
which ad-to-page mismatches exist
which educational assets are needed
which trust gaps need supporting content
Content Brain may support Ads Brain with:
YouTube descriptions
landing page support content
ad angle support notes
trust pages
FAQ content
objection-handling content
educational support articles
retargeting content ideas
message-match support assets
Content Brain does not run ads.
Content Brain does not optimise campaigns.
Content Brain does not decide ad budgets.
Content Brain does not declare creative winners.
Content Brain converts useful ad learning into structured content assets.
Experimentation Brain As Learning Quality Layer
Experimentation Brain owns test design, evidence quality, test validity, learning interpretation, and experiment decision discipline.
Content Brain may support Experimentation Brain by creating:
content variants for approved tests
content support assets for test candidates
learning-based content refresh plans
experiment-supporting FAQs
supporting article structures
message variants for controlled review
repurposing plans based on experiment learning
Content Brain may also receive learning signals from Experimentation Brain.
These signals may indicate:
which content needs revision
which message angles deserve support
which content assets should be refreshed
which content variants are worth testing
which claims or promises need stronger evidence
which audience segments respond to specific content
Content Brain does not decide whether a test is valid.
Content Brain does not interpret statistical confidence.
Content Brain does not declare a test winner.
Content Brain turns valid experiment learning into better content assets.
AIBS Brain As Authority And Education Source
AIBS Brain owns AI business systems positioning, education, business owner explanation, offer framing, client education, and authority-building around the AIBS model.
Content Brain may use AIBS Brain as a source for:
educational content
authority articles
client-facing explainers
business owner education pages
AI systems overview content
consultant-facing support material
case-study support material
service education content
sales support education
trust-building content
Content Brain does not define AIBS strategy.
Content Brain does not change AIBS positioning without approval.
Content Brain turns approved AIBS knowledge into useful educational assets.
Search Intelligence Brain As Demand Source
Search Intelligence Brain owns search demand discovery, search behaviour interpretation, keyword opportunity signals, search pattern visibility, and search opportunity routing.
Content Brain may use Search Intelligence Brain as a demand source.
Search Intelligence Brain may provide:
keyword demand signals
topic demand signals
search intent patterns
SERP opportunity signals
content gap opportunities
question-based opportunities
comparison demand signals
local or market search signals
Content Brain may convert these into:
SEO briefs
topic clusters
pillar pages
supporting articles
FAQ pages
comparison articles
authority articles
refresh tasks
internal linking plans
Content Brain does not own search intelligence.
Content Brain does not decide demand validity by itself.
Content Brain turns approved search demand into structured content plans.
Compliance Brain As Risk Gate
Compliance Brain owns compliance interpretation, claim-risk judgement, platform policy interpretation, and risk escalation.
Content Brain must treat Compliance Brain as a risk gate.
Content Brain may draft safer content structures and flag risk areas, but it must not approve sensitive claims.
Compliance review may be required for:
health claims
finance claims
income claims
legal claims
product performance claims
testimonials
guarantees
scarcity
urgency
comparisons
affiliate recommendations
risk-sensitive topics
Content Brain must not strengthen claims while repurposing content.
Content Brain must not turn cautious language into stronger promises.
Content Brain must not publish or hand off risky claims without the correct review path.
Finance Brain As Content Investment Discipline
Finance Brain owns capital allocation, investment discipline, test budget logic, financial risk interpretation, and resource prioritisation.
Content Brain should respect Finance Brain when content work requires meaningful investment of time, money, paid traffic support, contractor work, or operational focus.
Finance Brain may influence:
which content packs are worth building first
which affiliate products deserve content support
which content assets support controlled testing
which content work should be delayed
which refresh work has higher business value
which content work is not worth the cost yet
Content Brain does not approve spend.
Content Brain does not allocate capital.
Content Brain does not decide financial exposure.
Content Brain may recommend content investment, but Finance Brain controls financial discipline.
SIT Brain As Future Workflow Integrity Layer
SIT Brain may later help protect workflow integrity, system checks, task validation, and operational reliability across Content Brain workflows.
Content Brain may eventually connect with SIT Brain for:
workflow integrity checks
queue status checks
content task validation
handoff completeness checks
missing field detection
blocked item detection
approval path validation
future automation safety
Content Brain does not require SIT automation in the first manual phase.
SIT Brain should be treated as a future integrity layer, not a current build dependency.
Do not automate this yet.
Do not build plugin UI yet.
Define the system first.
HeadOffice As Command And Oversight Layer
HeadOffice governs the ecosystem.
Content Brain sends HeadOffice:
strategic content patterns
content bottlenecks
content risks
content opportunities
cross-brain content needs
high-value content signals
content production visibility
content refresh visibility
content repurposing visibility
content operation status
HeadOffice may prioritise content direction.
HeadOffice may decide whether Content Brain work should support Affiliate Brain, AIBS Brain, Research Brain, Ads Brain, Search Intelligence Brain, or another Brain.
Content Brain does not override HeadOffice priorities.
Relationship To Other Brains
Research Brain Boundary
Research Brain owns research intelligence.
Content Brain may use research signals to create better briefs, articles, content plans, affiliate support assets, authority pages, and educational content.
Content Brain does not replace Research Brain’s evidence gathering or verdict logic.
Affiliate Brain Boundary
Affiliate Brain owns offer and opportunity evaluation.
Content Brain may support Affiliate Brain with pre-sell content, comparison content, trust content, FAQ content, review support content, and objection-handling content.
Content Brain does not decide whether an offer should be tested.
Ads Brain Boundary
Ads Brain owns campaign structure and paid traffic execution.
Content Brain may support Ads Brain with YouTube descriptions, landing support content, trust pages, ad-support content, and campaign-supporting educational assets.
Content Brain does not run or optimise ad campaigns.
Experimentation Brain Boundary
Experimentation Brain owns test design, test validity, test interpretation, and learning quality.
Content Brain may support Experimentation Brain with structured content assets and may receive learning signals from experiments.
Content Brain does not validate experiments or declare winners.
AIBS Brain Boundary
AIBS Brain owns AIBS positioning, business education, client offer logic, and AI business systems authority.
Content Brain may turn approved AIBS thinking into educational articles, explainers, authority content, and client-facing support material.
Content Brain does not define AIBS strategy.
Search Intelligence Brain Boundary
Search Intelligence Brain owns search demand discovery and search opportunity interpretation.
Content Brain may turn approved search signals into briefs, topic clusters, articles, refresh plans, and authority content.
Content Brain does not own demand validation.
Conversion Brain Boundary
Conversion Brain owns conversion environment logic.
Content Brain may support Conversion Brain with FAQs, objection content, proof content, clarity content, trust content, and message-match content.
Content Brain does not own the conversion architecture.
Sales Brain Boundary
Sales Brain owns sales progression and decision momentum.
Content Brain may support Sales Brain with follow-up content, sales enablement content, objection education, and trust reinforcement assets.
Content Brain does not own live sales process decisions.
Compliance Brain Boundary
Compliance Brain owns compliance interpretation.
Content Brain may draft safer content structures and flag risk areas.
Content Brain does not provide final compliance approval.
Data Brain Boundary
Data Brain owns signal integrity and measurement quality.
Content Brain may review content-level signals.
Content Brain does not decide whether the data itself is reliable.
Finance Brain Boundary
Finance Brain owns capital discipline, budget allocation, financial exposure, and investment confidence.
Content Brain may recommend content work based on business value, but it does not approve spending or resource allocation.
SIT Brain Boundary
SIT Brain may later support workflow integrity and operational checks.
Content Brain does not build SIT logic or depend on SIT automation during the current MCR planning phase.
HeadOffice Boundary
HeadOffice governs the ecosystem.
Content Brain may send HeadOffice strategic content patterns, bottlenecks, risks, and opportunities.
Content Brain does not override HeadOffice priorities.
Content Brain Input Sources
Content Brain may receive work from:
HeadOffice
Research Brain
Affiliate Brain
Ads Brain
Experimentation Brain
Search Intelligence Brain
AIBS Brain
Conversion Brain
Sales Brain
Customer Brain
Data Brain
Compliance Brain
Finance Brain
Content Brain internal review
manual operator requests
approved newsletter intelligence
approved opportunity signals
approved campaign support needs
approved content refresh needs
approved strategic content priorities
approved product or offer intelligence
market trend signals
search demand signals
compliance alerts
finance priority signals
Each input should be classified before work begins.
Valid Content Requests
Valid Content Brain requests include:
create a new content brief
create an SEO article outline
draft an educational article
draft an affiliate support article
draft a comparison article
create a pre-sell content outline
create a product support page outline
create affiliate FAQ content
create objection-handling content
create a YouTube script
create a VEO3 pre-video script
create ad-support angle notes
create a social post set
create an email follow-up draft
refresh an existing article
repurpose a content asset
prepare a YouTube description
prepare email content
prepare social content
create an internal linking plan
create a topic cluster plan
review content quality
review content performance
identify content gaps
prepare publishing readiness review
prepare a content pack for an approved affiliate product
prepare AIBS education content from approved AIBS positioning
Invalid or incomplete requests include:
write something about this
make content for this offer without approval
publish this now without review
create compliance-sensitive claims without review
produce random SEO pages without intent
build a plugin or UI without workflow validation
route signals automatically without governance
create content without a source Brain or system purpose
create content without a review owner
Content Packs Instead Of Random One Off Assets
Content Brain should prefer structured content packs over random one-off content assets where the business use case requires a complete support system.
A content pack is a grouped set of related content assets designed to support a defined purpose.
For affiliate products, a basic content pack may include:
product support page
pre-sell article
FAQ or objection content
YouTube script
VEO3 pre-video hook or script
ad support angle notes
social post set
email follow-up draft
repurposing plan
compliance risk note
research requirement note
For AIBS education, a basic content pack may include:
authority article
client-facing explainer
FAQ content
sales support article
objection-handling content
social post set
email education sequence
case-study support notes
repurposing plan
proof or evidence requirement note
For SEO authority building, a basic content pack may include:
pillar page
supporting articles
FAQ page
internal linking plan
comparison page where relevant
trust page where relevant
refresh plan
repurposing plan
Content packs should remain structured, traceable, and reviewable.
Content Brain must not create large packs unless the source, purpose, audience, review path, and business value are clear.
Standard Operating Flow
Content Brain work follows this operating flow:
Request received
Request classified
Source Brain identified
Purpose defined
Audience and intent mapped
Content type selected
Content pack need assessed
Brief created
Draft or asset produced
Quality review completed
SEO review completed where relevant
Trust and compliance review completed where relevant
Publishing readiness checked
Content published or handed off only if approved
Performance reviewed
Refresh or repurposing decision made
Useful signals returned to the correct Brain
This flow is detailed in the Content Brain Workflow Map.
Content Opportunity Queue Concept
Content Brain should eventually have a Content Opportunity Queue.
This queue should track signals before they become production work.
The Content Opportunity Queue is different from the Content Production Queue.
The Content Opportunity Queue tracks possible content opportunities.
The Content Production Queue tracks approved content work moving through production.
The Content Opportunity Queue may receive signals from:
HeadOffice Newsletter Intelligence
Affiliate Brain
Research Brain
Search Intelligence Brain
Ads Brain
Experimentation Brain
AIBS Brain
Product intelligence
Offer intelligence
Market trend signals
Compliance alerts
Finance priority signals
The queue should track:
opportunity title
source Brain
source signal
suggested content type
target audience
strategic purpose
priority
status
required research
approval rule
SEO or authority value
conversion value
repurposing potential
compliance risk
finance priority
experimentation link
feedback destination
Recommended status options:
Ignore
Park
Research
Draft
Review
Approve
Publish
Repurpose
Refresh
Retire
This should be defined as a separate specification after the Operating Model upgrade.
Do not build plugin UI yet.
Define the system first.
Output Types
Content Brain may produce:
content brief
SEO brief
article outline
full draft
section draft
refresh plan
repurposing plan
internal linking plan
topic cluster map
authority content plan
affiliate support content plan
affiliate product content pack
pre-sell content plan
comparison content plan
FAQ content
trust support content
YouTube script
VEO3 pre-video script
YouTube description
email draft
social post set
publishing checklist
content review note
performance review note
signal feedback note
AIBS education content
client-facing explainer
research brief summary
ad support angle notes
Content Quality Responsibilities
Content Brain must protect quality.
Content should be reviewed for:
clarity
specificity
reader usefulness
information gain
accuracy
trustworthiness
format consistency
intent alignment
thin content risk
generic AI language
missing proof
unsupported claims
poor structure
weak internal linking
unclear next step
incorrect offer framing
unapproved claims
claim escalation risk
Content Brain should prefer fewer strong content assets over many weak content assets.
SEO Responsibilities
Content Brain supports SEO by managing:
search intent alignment
topic architecture
topic cluster structure
content briefs
heading structure
internal linking
refresh opportunities
information gain
reader-first usefulness
content gap coverage
authority building
Content Brain must not create low-value SEO content just to target keywords.
SEO content must be useful to the reader first.
Authority Building Responsibilities
Content Brain supports authority by producing:
pillar content
educational content
evidence-supported content
clear explanation pages
trust-support content
topic depth
expert positioning content
consistent editorial structure
helpful comparison content
AIBS authority content
affiliate trust content
Authority content should build trust over time.
It should not rely on hype, exaggeration, or unsupported claims.
Affiliate Funnel Support Responsibilities
Content Brain supports affiliate funnels by producing:
problem-aware content
pre-sell content
comparison content
review support content
FAQ content
objection-handling content
trust-building content
offer education content
YouTube script support
VEO3 pre-video support
YouTube description support
email follow-up support
retargeting content ideas
social support content
Content Brain does not approve the offer.
It supports approved opportunities with useful content assets.
Repurposing Responsibilities
Content Brain may turn one approved asset into multiple formats.
Examples:
article to email
article to social posts
article to YouTube description
article to short-form script seed
article to VEO3 pre-video hook
video transcript to article
newsletter insight to content idea
research note to article outline
offer brief to FAQ content
affiliate article to social set
AIBS explainer to email sequence
Repurposing must preserve original meaning and avoid inventing unsupported claims.
Refresh Responsibilities
Content Brain should identify and improve content that is outdated, weak, thin, misaligned, underperforming, risky, or disconnected from current strategy.
Refresh triggers may include:
outdated information
ranking decline
traffic decline
low engagement
weak internal linking
poor information gain
missing proof
changed offer details
changed audience intent
changed competitor landscape
changed compliance risk
new research insight
new experiment learning
new search demand signal
Refresh work must be treated as a controlled workflow, not random editing.
Performance Signal Responsibilities
Content Brain may interpret content-level performance signals.
Signals may include:
traffic
ranking movement
clicks
scroll depth
time on page
internal link clicks
conversion assist
engagement
email response
YouTube click through
social engagement
content refresh need
repurposing opportunity
affiliate support value
trust support value
Content Brain should not over-interpret weak or incomplete data.
If measurement quality is unclear, Data Brain should be involved.
If test interpretation is unclear, Experimentation Brain should be involved.
If financial priority is unclear, Finance Brain should be involved.
Signal Feedback Responsibilities
Content Brain should return useful signals to the ecosystem.
Content Brain may send:
topic traction signals to Research Brain
search opportunity signals to Search Intelligence Brain or Research Brain
offer support gaps to Affiliate Brain
message support needs to Ads Brain
trust friction signals to Conversion Brain
objection education needs to Sales Brain
measurement gaps to Data Brain
strategic content opportunities to HeadOffice
compliance concerns to Compliance Brain
content investment questions to Finance Brain
experiment learning opportunities to Experimentation Brain
workflow integrity concerns to SIT Brain later
AIBS education content gaps to AIBS Brain
Signal feedback must remain structured and traceable.
Human Approval Requirements
Human approval is required before:
publishing new content
editing live funnel pages
editing active offer pages
using health claims
using finance claims
using income claims
using legal claims
using testimonials
using guarantees
using scarcity or urgency language
creating programmatic SEO pages
pushing content into paid campaign environments
changing large-scale internal linking structures
publishing affiliate recommendation content
publishing AIBS client-facing claims
Content Brain may prepare drafts and recommendations.
It should not make live changes unless authority is explicitly granted.
Relationship To Content Brain Copy Map
The Content Brain Copy Map controls which Content Brain pages remain MCR only, which pages are copied to mwmscontentbrain.site, and which pages become later plugin or UI candidates.
This page should be listed in the Content Brain Copy Map as:
Page Title: Content Brain Operating Model
Destination: Copy To Content Brain Later
Reason: Operational orientation and Brain usage clarity
Source Of Truth: MCR
Future Use: Operator reference page inside mwmscontentbrain.site
Relationship To Content Brain Workflow Map
The Content Brain Operating Model defines what Content Brain is and how it is bounded.
The Content Brain Workflow Map defines how work moves through Content Brain.
The two pages should work together:
Operating Model = role, boundaries, responsibilities
Workflow Map = step-by-step movement of work
The Operating Model should not duplicate the full workflow.
The Workflow Map should not replace the Operating Model.
Relationship To Content Brain Page Registry
The Content Brain Page Registry tracks Content Brain page existence, parent placement, status, migration classification, plugin or UI candidates, and review notes.
This Operating Model should remain listed as:
Page Title: Content Brain Operating Model
Document Type: Operating Model
Parent Page: Content Brain
Status: Active
Migration Classification: Copy To Content Brain Later
Plugin Or UI Candidate: No Direct UI
The Page Registry should be reviewed after this update to ensure version and notes remain aligned.
Relationship To Content Brain Architecture
Content Brain Architecture defines the structural components of the Brain.
The Operating Model defines how those components behave as a working system.
Architecture explains the shape.
Operating Model explains the working logic.
Workflow Map explains the movement.
Relationship To Content Brain Content Production Queue Specification
The Content Production Queue Specification defines a future system for tracking approved content production work.
Operating Model = what Content Brain does
Content Production Queue = how approved production work becomes visible
The queue must not replace the Operating Model.
The queue must not grant authority.
The queue only tracks work.
Relationship To Content Brain Content Refresh Queue Specification
The Content Refresh Queue Specification defines a future system for tracking existing content that needs review, improvement, updating, strengthening, republishing, merging, repurposing, or retirement.
Operating Model = content maintenance responsibility
Content Refresh Queue = maintenance visibility layer
The refresh queue must not become a dumping ground.
It should only track refresh work with a clear trigger, purpose, owner, and next action.
Relationship To Content Brain Repurposing Queue Specification
The Content Repurposing Queue Specification defines a future system for tracking approved content assets that should be adapted into other formats.
Operating Model = repurposing responsibility
Repurposing Queue = reuse visibility layer
Repurposing must preserve meaning, claims, compliance posture, and source context.
Relationship To Content Brain Content Operations Dashboard Specification
The Content Operations Dashboard Specification defines a future visibility surface for Content Brain operations.
Operating Model = governing logic
Dashboard = visibility surface
The dashboard must not become an authority system.
It should show production, refresh, repurposing, approvals, blocked work, risks, handoffs, and feedback needs.
Relationship To Other MWMS Standards
This page must align with:
MWMS How To Start A Session Operating Guide
MWMS AI Session Context Lock Rule
MWMS Brain Routing Rule
MWMS MCR To Brain Copy Rule
MWMS Brain Interaction Map
MWMS Brain To Brain Request Protocol
MWMS Document Structure Standard
MWMS Document Taxonomy
MWMS Page Naming Standard
MWMS AI Output Standard Full File Delivery Rule
MWMS Architecture Registry
MWMS Active Brain Status Board
Content Brain Copy Map
Content Brain Workflow Map
Content Brain Page Registry
Content Brain Canon
Content Brain Architecture
Content Brain Content Production Queue Specification
Content Brain Content Refresh Queue Specification
Content Brain Repurposing Queue Specification
Content Brain Content Operations Dashboard Specification
Drift Protection
The system must prevent:
Content Brain creating content without purpose
Content Brain creating content without a source or owner
Content Brain becoming a random writing assistant
Content Brain becoming a content factory
Content Brain absorbing Research Brain authority
Content Brain approving affiliate offers
Content Brain making paid traffic decisions
Content Brain overriding Experimentation Brain learning quality
Content Brain overriding Conversion Brain logic
Content Brain making compliance approval decisions
Content Brain making finance or investment decisions
Content Brain over-interpreting weak data
Content Brain publishing without approval
Content Brain creating low-value SEO content
Content Brain creating content packs without approval or purpose
Content Brain repurposing content in a way that changes claims
Content Brain treating ad hooks as proven truths
Content Brain treating search demand as strategic approval
Content Brain treating AIBS education content as approved positioning without AIBS confirmation
Content Brain being copied blindly to mwmscontentbrain.site
Content Brain plugin or UI work starting before operational use is clear
Content Brain interfering with M’s active build areas
Content Brain must remain a structured execution Brain, not an uncontrolled content generator.
Architectural Intent
The Content Brain Operating Model exists to make Content Brain usable, governable, and scalable.
Its long-term role is to help MWMS produce content that supports:
authority
trust
search visibility
affiliate funnels
sales progression
conversion support
audience education
AIBS education
content-led learning
product opportunity support
ad-support content
experiment-informed content improvement
search demand capture
signal feedback
system improvement
The operating model protects Content Brain from becoming chaotic.
It ensures that content work connects to system purpose, Brain authority, and measurable learning.
The future operational version on mwmscontentbrain.site should make this model easier for operators and AI Employees to use, while MCR remains the source of truth.
Final Rule
Content Brain is not a content factory.
Content Brain is a governed content execution system.
If a content task has no source, no purpose, no audience, no system role, no review path, and no feedback path, it should not move into production.
Content Brain turns approved signals into structured assets.
It does not approve the signal itself.
Change Log
Version: v1.1
Date: 2026-05-24
Author: HeadOffice
Change: Upgraded Content Brain Operating Model to strengthen cross-brain operating boundaries and affiliate product content deployment logic. Added explicit roles for Affiliate Product Content Deployment, Research Brain as truth layer, Ads Brain as attention and hook testing layer, Experimentation Brain as learning quality layer, AIBS Brain as authority and education source, Search Intelligence Brain as demand source, Compliance Brain as risk gate, Finance Brain as content investment discipline, SIT Brain as future workflow integrity layer, and HeadOffice as command and oversight layer. Added Content Packs Instead Of Random One Off Assets, Content Opportunity Queue concept, stronger output types, enhanced drift protection, and updated relationships to queue and dashboard specifications.
Version: v1.0
Date: 2026-05-06
Author: HeadOffice
Change: Initial creation of Content Brain Operating Model defining Content Brain’s role, scope, boundaries, responsibilities, input sources, output types, approval requirements, MCR relationship, future mwmscontentbrain.site relationship, and drift protection rules.
Change Impact Declaration
Pages Created:
None
Pages Updated:
Content Brain Operating Model
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 OPERATING MODEL v1.1