Brain Name: Content Brain
Document Type: Operational Workflow
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain operational workflow, content request handling, content classification, content briefing, content production guidance, publishing readiness, affiliate content support, SEO content support, internal linking, repurposing, refresh, and signal feedback
Parent: content brain
Last Reviewed: 2026-05-24
Operational Copy Notice
This page is the live operator workflow page for Content Brain on mwmscontentbrain.site.
MCR remains the source of truth.
If this page conflicts with MCR, MCR wins.
This page is designed for practical use by the operator, not as a full MCR governance page.
Purpose
Content Workflow defines how content work moves through Content Brain.
It exists to stop content work becoming random, scattered, unclear, duplicated, or disconnected from MWMS priorities.
This workflow helps the operator move content from:
request
signal
idea
brief
draft
review
publishing readiness
handoff
repurposing
refresh
signal feedback
Content Brain should not create content just because content can be created.
Every content action should have:
a clear source
a clear purpose
a clear audience
a clear content type
a clear workflow stage
a clear approval path
a clear destination
a clear feedback signal
Source Of Truth
MCR defines the governing version of Content Brain.
mwmscontentbrain.site operates the working version.
This page is the working operator version of the Content Brain workflow.
Do not treat this page as a replacement for:
Content Brain Canon
Content Brain Architecture
Content Brain Page Registry
Content Brain Copy Map
Content Brain Migration Execution Checklist
mwmscontentbrain.site First Operational Layer Build Checklist
Those remain MCR control pages.
What This Workflow Is For
Use this workflow for:
new content requests
SEO content planning
authority content planning
affiliate support content
affiliate product content packs
affiliate funnel support
content briefs
draft planning
publishing readiness review
content refresh
content repurposing
internal linking planning
content performance review
signal feedback
content handoff
What This Workflow Does Not Control
This workflow does not control:
affiliate offer approval
paid advertising decisions
campaign scaling decisions
capital allocation
compliance approval
research verdicts
search validation
test validity
plugin implementation
Supabase implementation
Brain Room routing
HeadOffice reporting build work
M’s active development areas
Those remain governed by the correct 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 sends performance or learning signals back to the correct Brain.
The standard Content Workflow is:
- Input received
- Input classified
- Purpose defined
- Audience and intent mapped
- Content type selected
- Brief created
- Draft or asset prepared
- Quality review completed
- SEO and structure review completed where relevant
- Trust and compliance risk checked where relevant
- Publishing readiness confirmed
- Content published, handed off, refreshed, repurposed, or parked
- Signal feedback routed to the relevant Brain
Minimum Viable Workflow
The minimum workflow is:
request
classification
brief
draft or asset preparation
review
handoff
signal feedback
Use the minimum workflow for small or low-risk content tasks.
Use the full workflow for important, affiliate, SEO, compliance-sensitive, campaign-supporting, or high-impact content.
Workflow Stage 1: Input Received
Content work begins when a valid input enters Content Brain.
Inputs may come from:
HeadOffice
Research Brain
Affiliate Brain
Search Intelligence Brain
Ads Brain
Experimentation Brain
Conversion Brain
Sales Brain
Customer Brain
Data Brain
AIBS Brain
Content Brain internal review
manual operator request
newsletter intelligence signal
approved opportunity or campaign need
Do not accept vague content requests without clarification.
A valid input should define:
source
requesting Brain
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.
Classify the request as one of the following:
New Content
Refresh Existing Content
Repurpose Existing Content
Affiliate Support Content
Affiliate Product Content Pack
Affiliate Funnel Support
Authority Building Content
SEO Content
Sales Support Content
Conversion Support Content
Trust Support Content
Newsletter Derived Content
YouTube Support Content
VEO3 Pre Video Support
Social Repurposing Content
Internal Linking Work
Topic Cluster Work
Performance Review Work
If the request does not fit any useful category, park it or send it back to the source Brain.
Classification Fields
Each content request should capture:
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
handoff destination
signal to watch
Workflow Stage 3: Purpose Definition
Before a brief is created, define the content purpose.
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 stay in review.
Do not move unclear content into production.
Workflow Stage 4: Audience And Intent Mapping
Content Brain must define the reader or viewer intent before content is created.
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
campaign support
Content should not be created only because a topic sounds interesting.
The topic must connect to audience intent and system purpose.
Workflow Stage 5: Content Type Selection
After intent is clear, select 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
YouTube script support
VEO3 pre-video support
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
affiliate content pack
affiliate funnel support asset
The content type determines the structure, quality checks, risk level, and approval requirements.
Workflow Stage 6: 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 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
handoff destination
signal to watch
Use:
Content Briefs for general content
SEO Content Briefs for search-focused content
Affiliate Content Packs for affiliate product support
Affiliate Funnel Support for funnel-stage content
Workflow Stage 7: Draft Or Asset Preparation
Draft or asset preparation begins only after the brief is clear.
Content Brain may prepare:
outline
first draft
section draft
rewrite
summary
email version
YouTube description
social adaptation
FAQ block
comparison section
trust section
pre-sell section
affiliate support asset
refresh plan
repurposing plan
internal linking plan
Content production must follow the approved brief.
Drafts must 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
The operator should ask:
Is this useful?
Is this clear?
Is this specific?
Is this aligned with the brief?
Does this serve the reader?
Does this support the correct Brain?
Does this create risk?
If the answer is unclear, keep the content in review.
Workflow Stage 9: SEO And Structure Review
Where content is SEO-related, 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.
Do not create low-value content only to target keywords.
Search demand, SERP interpretation, and query validation remain owned by Search Intelligence Brain and Research Brain.
Workflow Stage 10: Trust And Compliance Risk Check
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 safer wording and flag risk.
Compliance Brain owns final compliance interpretation where risk exists.
When risk is unclear, flag the content for review instead of moving forward.
Workflow Stage 11: Publishing Readiness
Before content is published, handed off, repurposed, refreshed, or used, 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
claim risk checked
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 stays in review.
Use the Publishing Readiness page before final use.
Workflow Stage 12: Publish, Handoff, Park, Refresh, Or Repurpose
After readiness review, choose the next action.
Possible outcomes:
Publish
Hand off
Park
Send back for research
Send back for approval
Refresh
Repurpose
Retire
Merge
Monitor
Content Brain may hand off content for:
WordPress publishing
email usage
YouTube description usage
social repurposing
affiliate funnel support
sales enablement
internal knowledge use
campaign support
Content Brain does not automatically publish unless publishing authority is clearly granted.
Workflow Stage 13: Performance Review
After content is live or used, 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 classify signals as:
early signal
directional signal
strong signal
unclear signal
no signal
Data Brain owns signal reliability and measurement interpretation.
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
compliance risk changes
Refresh work should be treated as a workflow, not a casual edit.
Use the Refresh page when updating existing content.
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
strong affiliate support value
Repurposing may create:
social post
video outline
YouTube description
short-form script seed
newsletter section
FAQ block
comparison snippet
sales support note
affiliate follow-up content
Repurposing must preserve meaning.
Do not strengthen claims.
Do not add new claims without review.
Do not change compliance risk without approval.
Use the Repurposing page for this work.
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
compliance risk signal
Signal Destinations
Research Brain receives:
search demand signals
topic traction signals
voice-of-customer patterns
audience problem signals
content gaps
Research gaps found during content planning
Affiliate Brain receives:
offer support gaps
pre-sell content needs
comparison content opportunities
affiliate trust gaps
affiliate content pack 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
Search Intelligence Brain receives:
search content gaps
internal linking opportunities
SERP mismatch notes
refresh opportunities
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
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.
Do not build that UI yet.
When To Park A Request
Park a request when:
purpose is unclear
audience is unclear
source Brain is unclear
approval owner is missing
research basis is weak
offer status is unclear
compliance risk is unclear
budget or resource issue exists
destination is unknown
the request belongs to another Brain
Parked content is not rejected.
It is held until the missing information is resolved.
When To Send Back To Another Brain
Send the request back when:
Research Brain must confirm evidence
Affiliate Brain must confirm offer status
Search Intelligence Brain must confirm search demand
Ads Brain must confirm campaign need
Experimentation Brain must confirm test use
Compliance Brain must review claim risk
Finance Brain must confirm resource priority
Data Brain must confirm signal reliability
HeadOffice must confirm priority
Content Brain supports the content work.
It does not take authority from the owning Brain.
Future Plugin Or UI Candidates
This workflow may later support:
Content Request Form
Content Opportunity Queue
Content Production Queue
Content Brief Generator
Publishing Readiness Checklist UI
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 manual workflow use proves need.
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.
Relationship To Other Operational Pages
Use this workflow with:
Content Brain for the homepage and operator starting point
Content Briefs for creating content briefs
Publishing Readiness for final readiness checks
Affiliate Content Packs for affiliate product content planning
Affiliate Funnel Support for funnel-stage content mapping
SEO Content Briefs for search-focused content planning
Internal Linking for page connection planning
Repurposing for adapting approved content
Refresh for improving existing content
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 or review-ready status
content signals being ignored after publication
content feedback bypassing the correct Brain
Content Brain taking authority from Research Brain, Affiliate Brain, Search Intelligence Brain, Ads Brain, Experimentation Brain, Conversion Brain, Sales Brain, Compliance Brain, Finance Brain, Data Brain, SIT Brain, or HeadOffice
old workflow map pages being treated as the current operator workflow after this clean page is created
future UI being built before workflow use is understood
Architectural Intent
Content Workflow 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:
MCR defines Content Brain.
mwmscontentbrain.site operates Content Brain.
Future plugin or UI systems automate repeated workflows only after manual use proves the need.
Old Page Handling
This page replaces the operator role of the older page:
Content Brain Workflow Map
After Content Workflow is created and checked, the older Content Brain Workflow Map page should be handled as follows:
If it is only a duplicate operational workflow page, delete it.
If it is needed for historical reference, move it to a legacy/reference area and mark it clearly as legacy.
Do not keep both as active operator workflow pages.
The active operator workflow page should be:
Content Workflow
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.0
Date: 2026-05-24
Author: HeadOffice
Change: Created clean operator workflow page for mwmscontentbrain.site based on MCR Content Brain Workflow Operational Copy and the existing Content Brain Workflow Map. Defines the live Content Workflow page for the first operational Content Brain layer, including input handling, classification, purpose definition, audience and intent mapping, content type selection, brief creation, draft preparation, quality review, SEO and structure review, trust and compliance risk check, publishing readiness, handoff, performance review, refresh, repurposing, signal feedback, status model, parking rules, cross-Brain routing boundaries, no build rule, old page handling, and drift protection.
Change Impact Declaration
Pages Created:
Content Workflow
Pages Updated:
None
Pages To Delete Or Move To Legacy After Validation:
Content Brain Workflow Map
Pages Deprecated:
Content Brain Workflow Map as active operator workflow page
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT WORKFLOW v1.0