Brain Name: Content Brain
Document Type: System Map
Status: Active
Version: v1.1
Authority: Content Brain under HeadOffice governance
Applies To: Content Brain planning, production, optimization, repurposing, refresh, operational use on mwmscontentbrain.site, and future Content Brain workflow development
Parent: Content Brain
Last Reviewed: 2026-05-08
Operational Copy Notice
This page is an operational copy used on mwmscontentbrain.site.
MCR remains the source of truth.
If this page conflicts with the MCR version, the MCR version overrides it.
This protects source-of-truth discipline.
Content Brain Workflow Map
Operational Copy Notice
This page is an operational copy used on mwmscontentbrain.site.
MCR remains the source of truth.
If this page conflicts with the MCR version, the MCR version overrides it.
This protects source-of-truth discipline.
Purpose
The Content Brain Workflow Map defines how content work moves through the MWMS ecosystem.
It exists to create a clear operating flow for:
content ideas
content requests
research signals
SEO briefs
article planning
draft production
quality review
publishing readiness
content optimization
content refresh
content repurposing
content performance review
signal feedback into other Brains
This page ensures Content Brain becomes a structured execution Brain rather than an unstructured writing area.
Content Brain must not produce content randomly.
Every content action should have a defined source, purpose, workflow stage, output, and feedback path.
Scope
This workflow map applies to:
Content Brain work created in MCR
operational Content Brain work on mwmscontentbrain.site
SEO content planning
authority content planning
affiliate support content planning
content refresh work
content repurposing work
content quality review
content signal feedback
content performance review
content handoff planning
manual content workflow use before automation
future Content Brain queue planning
This page governs the movement of content work through Content Brain.
It does not govern:
offer approval
paid advertising decisions
campaign scaling decisions
capital allocation
compliance approval
plugin implementation
Supabase schema implementation
Brain to Brain request automation
HeadOffice reporting build work
M’s active development areas
Those remain governed by the relevant Brain, protocol, standard, or implementation layer.
Core Principle
Content Brain turns approved insight into structured content assets.
Content Brain does not create strategy in isolation.
Content Brain receives signals, requests, or priorities from the wider MWMS ecosystem, turns them into useful content outputs, and feeds performance or learning signals back to the appropriate Brain.
The core workflow is:
Input
Classification
Brief
Production
Review
Publishing Readiness
Publication Or Handoff
Performance Review
Refresh Or Repurpose
Signal Feedback
Governance Role
Content Brain is an Execution Layer Brain.
It produces content assets that support growth, trust, authority, search visibility, affiliate funnels, sales progression, conversion support, and audience education.
Content Brain operates under HeadOffice governance.
Content Brain must respect authority boundaries with:
Research Brain
Affiliate Brain
Ads Brain
Conversion Brain
Sales Brain
Compliance Brain
Data Brain
Finance Brain
HeadOffice
Content Brain may support these Brains with content, but it must not override their authority.
Relationship To MCR
MCR remains the source of truth.
This workflow map was created in MCR first.
MCR stores the structural logic, governance alignment, and workflow definition.
This mwmscontentbrain.site page is the operational copy.
If the MCR version changes, this operational copy should be reviewed and updated only after the change is confirmed.
Relationship To mwmscontentbrain.site
mwmscontentbrain.site is the working operational Content Brain environment.
This page acts as the practical workflow guide for content work on the live Content Brain site.
It may later support:
a content request guide
a content production checklist
a content queue workflow
a content brief generator flow
a content refresh queue flow
a content repurposing workflow
a content signal feedback workflow
a future Content Brain dashboard
The live Brain site must not replace MCR authority.
It should operationalise this workflow only within the boundaries defined by MCR and the Content Brain Copy Map.
Workflow Stage 1: Input
Content work begins when a valid input enters Content Brain.
Valid inputs may come from:
HeadOffice
Research Brain
Affiliate Brain
Ads Brain
Conversion Brain
Sales Brain
Customer Brain
Data Brain
Content Brain internal review
manual operator request
approved newsletter intelligence signal
approved opportunity or campaign need
Content Brain should not accept vague content requests without classification.
Every content input should define:
source
purpose
target audience
content type
intended use
priority
related Brain
required output
approval requirement
Workflow Stage 2: Input Classification
Every content input must be classified before work begins.
Classification prevents random content creation and keeps Content Brain aligned with MWMS goals.
Content request types include:
New Content
Refresh Existing Content
Repurpose Existing Content
Affiliate Support Content
Authority Building Content
SEO Content
Sales Support Content
Conversion Support Content
Trust Support Content
Newsletter Derived Content
YouTube Support Content
Social Repurposing Content
Internal Linking Work
Topic Cluster Work
Performance Review Work
Classification fields should include:
request title
request source
requesting Brain
supporting Brain
content type
business purpose
audience stage
search intent where relevant
funnel role where relevant
priority
risk level
required output
approval owner
status
Workflow Stage 3: Purpose Definition
Before a brief is created, the content purpose must be defined.
Content Brain should ask:
Who is this content for?
What problem does it solve?
What stage of awareness does it serve?
What Brain does it support?
What business function does it support?
What action should the content help enable?
What signal will tell us whether it worked?
If the purpose is unclear, the request should remain in review rather than moving to production.
Workflow Stage 4: Audience And Intent Mapping
Content Brain must define the reader or viewer intent before writing.
Intent may include:
problem awareness
solution exploration
product comparison
objection resolution
trust building
how to education
pre purchase evaluation
post purchase education
retention support
sales enablement
search discovery
affiliate pre sell
Content Brain should not create content only because a topic sounds interesting.
The topic must be connected to audience intent and system purpose.
Workflow Stage 5: Content Type Selection
After intent is clear, Content Brain selects the correct content type.
Common content types include:
SEO article
pillar page
topic cluster article
comparison article
review support article
pre sell article
FAQ page
authority page
trust support page
YouTube description
email draft
newsletter draft
social post set
short form script seed
content refresh plan
internal linking plan
topic cluster map
publishing checklist
performance review note
Content type determines structure, quality checks, and approval requirements.
Workflow Stage 6: Content Brief Creation
The content brief is the control document for production.
Content Brain should not move directly from idea to draft unless the task is small and low risk.
A strong content brief should include:
working title
content objective
audience
awareness stage
intent
primary topic
secondary topics
search angle where relevant
funnel role
related offer where relevant
key reader questions
objections to address
trust signals needed
proof needed
internal links needed
external references needed
call to action type
compliance sensitivity
required format
quality bar
approval owner
The Content Brain SEO Content Brief Standard should guide SEO briefs.
Workflow Stage 7: Draft Production
Draft production begins only after the brief is clear.
Content Brain may create:
outline
first draft
section draft
rewrite
summary
email version
YouTube description
social adaptation
FAQ block
comparison section
trust section
Content production should follow the approved brief.
Drafts should not introduce new claims, new offers, new pricing, new guarantees, or new compliance-sensitive statements without review.
Workflow Stage 8: Quality Review
Every meaningful content output should pass through quality review.
Quality review checks:
clarity
accuracy
usefulness
specificity
reader value
information gain
tone consistency
format consistency
trustworthiness
claim safety
internal logic
missing proof
thin content risk
overly generic AI language
Content Brain AI Content Quality Governance Framework and Content Brain Information Gain Framework should guide this review.
Workflow Stage 9: SEO And Structure Review
Where content is SEO related, Content Brain should review:
search intent alignment
title structure
heading structure
topical coverage
internal linking opportunities
content gap coverage
entity coverage
information gain
reader journey
topic cluster fit
refresh potential
duplicate content risk
thin content risk
SEO work should remain useful to humans first.
Content Brain must not create low value content only to target keywords.
Workflow Stage 10: Trust And Compliance Review
Trust and compliance review is required when content includes:
health claims
finance claims
income claims
legal claims
product performance claims
testimonials
guarantees
scarcity
urgency
comparisons
affiliate recommendations
risk sensitive topics
Content Brain may prepare the content, but Compliance Brain owns final compliance interpretation where risk exists.
When risk is unclear, Content Brain should flag the page for review rather than proceed.
Workflow Stage 11: Publishing Readiness
Before content is published or handed off, Content Brain should confirm:
purpose is clear
audience is clear
content type is correct
brief has been followed
quality review completed
SEO review completed where relevant
trust review completed where relevant
internal links identified
CTA is appropriate
source Brain is identified
approval owner is identified
publishing destination is clear
performance signal is defined
If any item is missing, the content should remain in review.
Workflow Stage 12: Publication Or Handoff
Content Brain may hand off content for:
WordPress publishing
email usage
YouTube description usage
social repurposing
affiliate funnel support
sales enablement
internal knowledge use
Content Brain does not automatically publish unless publishing authority is clearly granted.
Publication or handoff should preserve:
content title
content type
source request
related Brain
approval owner
date created
status
destination
notes
Workflow Stage 13: Performance Review
After content is live or used, Content Brain should review performance when data is available.
Possible review signals include:
traffic
ranking movement
clicks
time on page
scroll depth
internal link clicks
conversion assist
lead quality
affiliate support value
engagement
email response
YouTube click through
social response
content refresh need
Content Brain should not over interpret weak data.
Performance review should distinguish between:
early signal
directional signal
strong signal
unclear signal
no signal
Workflow Stage 14: Refresh Decision
Content may require refresh when:
traffic declines
ranking drops
content becomes outdated
intent changes
new competitor content appears
offer changes
internal links are weak
content is thin
proof is missing
trust signals are weak
conversion support is poor
reader questions are unanswered
Content Brain SEO Testing And Refresh Framework should guide refresh decisions.
Refresh work should be treated as a workflow, not a casual edit.
Workflow Stage 15: Repurposing Decision
Content may be repurposed when it has:
strong audience relevance
clear educational value
strong proof or insight
high search value
strong funnel support value
strong social potential
strong email potential
strong YouTube support value
Repurposing may create:
social post
video outline
YouTube description
short form script seed
newsletter section
FAQ block
comparison snippet
sales support note
Content Brain Content Repurposing Framework should guide repurposing decisions.
Workflow Stage 16: Signal Feedback
Content Brain should send useful signals back into the ecosystem.
Signal types include:
topic traction signal
audience intent signal
content gap signal
search opportunity signal
objection signal
trust gap signal
conversion support signal
affiliate support gap
refresh need
repurposing opportunity
internal linking gap
content quality issue
Signal Destinations
Research Brain receives:
search demand signals
topic traction signals
voice of customer patterns
audience problem signals
Affiliate Brain receives:
offer support gaps
pre sell content needs
comparison content opportunities
affiliate trust gaps
Ads Brain receives:
message support needs
YouTube description needs
ad to page mismatch signals
campaign support content needs
Conversion Brain receives:
objection patterns
CTA support gaps
trust friction signals
message match issues
Sales Brain receives:
follow up content needs
objection education needs
trust reinforcement content
sales enablement content
Data Brain receives:
content measurement issues
signal reliability concerns
tracking gaps
performance interpretation needs
HeadOffice receives:
strategic content patterns
major content bottlenecks
cross Brain content opportunities
system level content risk
high priority content opportunities
Standard Content Workflow Summary
The standard Content Brain workflow is:
Input received
Input classified
Purpose defined
Audience and intent mapped
Content type selected
Brief created
Draft produced
Quality review completed
SEO and structure review completed where relevant
Trust and compliance review completed where relevant
Publishing readiness confirmed
Content published or handed off
Performance reviewed
Refresh or repurposing decision made
Signal feedback routed to relevant Brain
This workflow keeps content connected to purpose, system value, and measurable learning.
Workflow Status Model
Content work should use a clear status model.
Recommended statuses:
new
classified
briefing
drafting
in_review
ready_for_approval
approved
published
handed_off
monitoring
refresh_needed
repurpose_needed
closed
blocked
This status model may later become part of a Content Brain queue or plugin UI.
Minimum Viable Content Workflow
The minimum viable workflow for Content Brain is:
request
classification
brief
draft
review
handoff
signal feedback
This should be proven manually before complex automation, dashboards, or plugin tools.
The first goal is usable structure.
Automation can come later.
Future Plugin Or UI Candidates
This workflow may later support:
Content Request Form
Content Production Queue
Content Brief Generator
Publishing Readiness Checklist
Content Refresh Queue
Repurposing Planner
Internal Linking Planner
Topic Cluster Planner
Content Performance Review Screen
Content Signal Feedback Dashboard
These should not be built yet.
They should remain future implementation candidates until MCR structure and workflow use are stable.
Relationship To Content Brain Copy Map
The Content Brain Copy Map controls whether this page stays in MCR, is copied to mwmscontentbrain.site, or becomes a future plugin or UI function.
Current classification:
Destination: Copy To Content Brain
Reason: Operational use
Source Of Truth: MCR
Future Use: Working workflow page inside mwmscontentbrain.site
Future Plugin Or UI: Possible Content Production Queue and workflow dashboard
Relationship To Other MWMS Standards
This workflow must align with:
MWMS MCR To Brain Copy Rule
MWMS Brain Interaction Map
MWMS Brain Routing Rule
MWMS AI Session Context Lock Rule
MWMS AI Output Standard Full File Delivery Rule
MWMS Document Structure Standard
MWMS Document Taxonomy
MWMS Page Naming Standard
MWMS System Data Flow Map
MWMS Brain To Brain Request Protocol
Content Brain Copy Map
Content Brain Canon
Content Brain Architecture
Drift Protection
The system must prevent:
content being created without a defined purpose
content being created without source Brain context
content being published without review
SEO content being created only for keywords without reader value
affiliate support content being created before offer approval
content signals being ignored after publication
content feedback bypassing the correct Brain
Content Brain absorbing authority from Research Brain, Affiliate Brain, Ads Brain, Conversion Brain, Sales Brain, Compliance Brain, Data Brain, Finance Brain, or HeadOffice
workflow pages being copied to mwmscontentbrain.site without classification
future UI being built before workflow use is understood
mwmscontentbrain.site replacing MCR source-of-truth authority
Content Brain must remain structured, purposeful, and connected to the wider MWMS system.
Architectural Intent
The Content Brain Workflow Map exists to make content execution visible, repeatable, and governable.
Its role is to move Content Brain from scattered content creation into a disciplined production and learning system.
Content Brain should help MWMS produce content that:
supports business priorities
builds authority
improves trust
supports affiliate funnels
strengthens search visibility
supports sales and conversion
creates reusable assets
feeds learning back into the ecosystem
The long-term intent is for Content Brain to become a working operational environment on mwmscontentbrain.site, while MCR remains the source of truth.
Final Rule
Content Brain must not create content just because content can be created.
Content work must move through a defined workflow, serve a clear system purpose, and produce either a useful asset or a useful signal.
If the content has no purpose, no audience, no owner, and no feedback path, it should not enter production.
Change Log
Version: v1.1
Date: 2026-05-08
Author: HeadOffice
Change: Created operational copy for mwmscontentbrain.site. Added Operational Copy Notice, clarified MCR source-of-truth relationship, strengthened live-site operating role, added manual workflow before automation discipline, added restrictions around M’s active build areas, and clarified that this page is an operational workflow page rather than source-of-truth authority.
Version: v1.0
Date: 2026-05-06
Author: HeadOffice
Change: Initial creation of Content Brain Workflow Map defining the structured movement of content work from input through classification, brief, production, review, publishing readiness, performance review, refresh, repurposing, and signal feedback.
Change Impact Declaration
Pages Created:
Content Brain Workflow Map
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT BRAIN WORKFLOW MAP v1.1