Brain Name: Content Brain
Document Type: Operational Copy
Status: Draft
Version: v1.0
Authority: Content Brain under HeadOffice governance
Applies To: mwmscontentbrain.site future workflow page, Content Brain first operational copy batch, Content Brain operator workflow, manual content request handling, content brief routing, publishing readiness routing, affiliate content pack routing, SEO content routing, repurposing routing, refresh routing, and Content Brain source-of-truth protection
Parent: Content Brain
Last Reviewed: 2026-05-24
Content Brain Workflow Operational Copy
Purpose
The Content Brain Workflow Operational Copy defines the simplified future workflow page for mwmscontentbrain.site.
This page is not the live workflow page yet.
This page is the MCR-prepared operational copy that will later be used to create the first practical Content Brain workflow page.
Its purpose is to give an operator a simple, repeatable path for handling content work from first signal to final handoff, publishing readiness, repurposing, refresh, or learning feedback.
This page translates the larger Content Brain Workflow Map into a practical operator workflow.
The workflow should help the operator understand:
where content work starts
how to identify the source Brain
how to decide whether the work belongs in Content Brain
when to create a content brief
when to use a checklist
when to request research
when to route for approval
when to hand off
when to repurpose
when to refresh
when to retire or park content
what not to decide inside Content Brain
Scope
This operational copy applies to:
future mwmscontentbrain.site workflow page content
manual Content Brain workflow
content request handling
content opportunity handling
content brief routing
publishing readiness routing
affiliate product content pack routing
affiliate funnel support routing
SEO content routing
internal linking routing
repurposing routing
refresh routing
manual signal feedback
first migration batch preparation
operator guidance for Content Brain work
This operational copy does not apply to:
Content Brain Canon authority
Content Brain Architecture authority
Content Brain Page Registry
Content Brain Copy Map
Content Brain plugin or UI build
Supabase implementation
Brain Room routing
cross-brain automation
M’s active build work
live mwmsbrain.site plugin work
mwmscontentbrain.site migration execution
This page prepares future operational workflow content only.
It does not start migration.
Core Rule
Every Content Brain work item must follow a clear path.
No signal should become content work automatically.
No draft should become published content automatically.
No checklist should override approval authority.
No content asset should be handed off without knowing:
where the request came from
what the asset is for
what research supports it
what Brain owns the decision
what approval is required
what signal should be watched after use
Content Brain supports content execution.
It does not replace the Brains that approve offers, claims, budgets, ads, experiments, research verdicts, or strategy.
Future Workflow Page Title
Recommended future workflow page title:
Content Workflow
Recommended future page subtitle:
Turn approved signals and requests into structured content work.
Recommended operator description:
Use this workflow whenever a content signal, content request, affiliate support need, SEO opportunity, repurposing idea, refresh trigger, or campaign support request enters Content Brain.
Simple Workflow Overview
The operator workflow is:
- Receive signal or request.
- Identify the source Brain.
- Confirm whether the work belongs in Content Brain.
- Choose the correct action.
- Create or update the content brief.
- Select the right checklist or framework.
- Draft or prepare the content asset.
- Check publishing readiness.
- Route for approval where needed.
- Hand off, publish, park, repurpose, refresh, or retire.
- Record the signal to watch.
- Route learning back later.
This workflow is manual first.
Automation comes later only after repeated use proves the need.
Step 1: Receive Signal Or Request
A content workflow can start from:
HeadOffice signal
Affiliate Brain request
Research Brain insight
Search Intelligence Brain opportunity
Ads Brain support request
Experimentation Brain learning
AIBS Brain education need
Compliance Brain risk update
Finance Brain priority signal
Data Brain performance signal
manual operator observation
existing content needing review
approved product or offer needing support
A signal is not automatically a task.
The operator must first qualify it.
Step 2: Identify Source Brain
Before doing any content work, identify where the request came from.
Record:
Source Brain
request type
content purpose
urgency
approval owner
research basis
related offer or product
related campaign or test
known risk
expected output
If the source is unclear, park the item until clarified.
Step 3: Confirm Whether It Belongs In Content Brain
Content Brain should handle work involving:
content briefs
SEO content
affiliate support content
affiliate product content packs
affiliate funnel support content
YouTube script support
VEO3 pre-video support
email content
social content
publishing readiness
repurposing
refresh planning
internal linking
content improvement
manual signal feedback
Content Brain should not handle:
offer approval
claim approval
budget approval
ad campaign execution
test validation
research verdicts
search demand validation
finance decisions
conversion strategy decisions
sales strategy decisions
If the work belongs to another Brain, route it there or park it.
Step 4: Choose The Correct Action
Every signal or request should be assigned one action.
Available actions:
Ignore
Park
Research
Brief
Draft
Review
Publish
Repurpose
Refresh
Retire
Handoff
Ignore
Use when:
the signal is weak
the source is unclear
the request is irrelevant
the content opportunity has no strategic value
the work duplicates something already handled
Operator note:
Record only if useful. Do not create content work.
Park
Use when:
the idea may be useful later
research is missing
approval is missing
priority is unclear
offer status is unclear
compliance risk is unclear
finance priority is unclear
Operator note:
Parked items should not become active content work until the missing condition is resolved.
Research
Use when:
the topic needs evidence
audience language is missing
claims need source support
search intent is unclear
competitor context is needed
offer details are incomplete
market context is unclear
Operator note:
Send or wait for Research Brain or Search Intelligence Brain support before drafting.
Brief
Use when:
the content work is valid
the purpose is clear
the source Brain is known
the asset type is known
the approval path is known
Operator note:
Use Content Brain Content Brief Template.
Draft
Use when:
the brief is clear
research basis exists
asset type is selected
approval boundary is understood
Operator note:
Drafting can begin, but publishing cannot happen until readiness and approval checks are complete.
Review
Use when:
draft exists
asset needs quality check
claims need checking
links need checking
format needs checking
approval owner must review
Operator note:
Use Publishing Readiness Checklist before handoff or publication.
Publish
Use only when:
publishing authority is clear
approval is complete
claims are safe
links are checked
CTA is clear
handoff requirements are complete
Operator note:
Content Brain does not publish automatically.
Repurpose
Use when:
an approved content asset can become another format
the original message is still valid
claims will not be strengthened
approval boundaries remain clear
Operator note:
Use Content Brain Content Repurposing Framework.
Refresh
Use when:
content is outdated
performance has dropped
new research exists
search intent has shifted
claims need review
links need updating
Operator note:
Use Content Brain SEO Testing And Refresh Framework.
Retire
Use when:
content is outdated
content is low value
risk is too high
content overlaps better assets
content should be merged or redirected
Operator note:
Do not retire important pages without correct review.
Handoff
Use when:
content must go to another Brain
approval is needed
asset is ready for Ads Brain, Affiliate Brain, AIBS Brain, Sales Brain, or another owner
Operator note:
Record handoff destination and approval owner.
Step 5: Create Or Update The Content Brief
Use:
Content Brain Content Brief Template
The brief should include:
content title
source Brain
content type
audience
intent
funnel role
research basis
SEO notes
offer or product connection
approval owner
compliance risk
handoff destination
internal linking notes
repurposing potential
signal to watch
A content brief is required before drafting major assets.
Step 6: Select The Correct Checklist Or Framework
Use the right support page.
For a general content asset:
Content Brain Content Brief Template
Content Brain Publishing Readiness Checklist
For affiliate product content packs:
Content Brain Affiliate Product Content Pack Checklist
For affiliate funnel support:
Content Brain Affiliate Funnel Support Map
For SEO content:
Content Brain SEO Content Brief Standard
For internal links:
Content Brain Internal Linking Strategy Framework
For repurposing:
Content Brain Content Repurposing Framework
For refresh:
Content Brain SEO Testing And Refresh Framework
Do not use the wrong checklist just to move faster.
Step 7: Draft Or Prepare The Content Asset
Draft only after:
source Brain is clear
purpose is clear
asset type is clear
research basis is clear enough
approval boundary is known
risk level is understood
When drafting, preserve:
reader intent
source evidence
claim safety
funnel role
brand tone
SEO purpose
handoff destination
Do not add stronger claims during drafting.
Do not invent proof.
Do not rewrite risk into certainty.
Step 8: Check Publishing Readiness
Use:
Content Brain Publishing Readiness Checklist
Confirm:
audience clarity
intent match
research support
claim safety
compliance risk
SEO basics
internal links
CTA clarity
format readiness
approval owner
handoff destination
signal to watch
Checklist completion does not equal final approval.
It only confirms readiness for the next step.
Step 9: Route For Approval Where Needed
Approval may be required from:
Affiliate Brain
Research Brain
Search Intelligence Brain
Ads Brain
Experimentation Brain
Compliance Brain
Finance Brain
Conversion Brain
Sales Brain
HeadOffice
If approval owner is unclear, do not publish.
Park or hand off for clarification.
Step 10: Hand Off, Publish, Park, Repurpose, Refresh, Or Retire
After review, choose the next action:
Hand off to another Brain
Publish if approved
Park if blocked
Repurpose if approved asset can be reused
Refresh if existing asset needs update
Retire if asset no longer belongs
Record why the action was chosen.
Step 11: Record Signal To Watch
Every meaningful content asset should have a signal to watch.
Possible signals:
search impressions
search clicks
ranking movement
affiliate click behavior
VSL click behavior
YouTube engagement
email clicks
social engagement
scroll depth
time on page
conversion support
objection reduction
support request reduction
sales conversation usefulness
manual feedback from operator
Do not over-interpret weak signals.
Data Brain owns data quality.
Step 12: Route Learning Back Later
When content produces learning, route it back to the right Brain.
Examples:
Research gap goes to Research Brain.
Search trend goes to Search Intelligence Brain.
Affiliate funnel learning goes to Affiliate Brain.
Ad message learning goes to Ads Brain.
Experiment learning goes to Experimentation Brain.
Compliance concern goes to Compliance Brain.
Budget concern goes to Finance Brain.
Performance signal goes to Data Brain.
Strategic bottleneck goes to HeadOffice.
Content Brain does not hoard learning.
It routes learning.
Common Workflow Paths
New SEO Article
Path:
Signal from Search Intelligence Brain or Research Brain.
Confirm topic belongs in Content Brain.
Create content brief.
Use SEO Content Brief Standard.
Draft article.
Check Publishing Readiness.
Add internal links.
Route for approval if needed.
Publish or hand off.
Watch search and engagement signals.
Affiliate Product Content Pack
Path:
Signal from Affiliate Brain.
Confirm offer is approved or review-ready.
Check research basis.
Use Affiliate Product Content Pack Checklist.
Create content brief for each selected asset.
Map affiliate funnel support.
Check publishing readiness.
Route approval where needed.
Hand off to Affiliate Brain, Ads Brain, or publishing owner.
Watch affiliate and funnel signals.
VEO3 Pre-Video Support
Path:
Signal from Ads Brain or Affiliate Brain.
Confirm offer and campaign context.
Create content brief.
Check affiliate funnel stage.
Draft VEO3 pre-video support content.
Check claim risk.
Route for Ads Brain or Compliance Brain review.
Hand off only after approval.
Watch engagement and test signals.
Repurposing Approved Content
Path:
Approved source asset identified.
Confirm message is still valid.
Choose new format.
Use Repurposing Framework.
Preserve meaning.
Check claims.
Route approval if needed.
Hand off or publish.
Watch performance signal.
Refresh Existing Content
Path:
Refresh trigger identified.
Confirm source signal.
Review current page.
Use SEO Testing And Refresh Framework.
Update evidence.
Improve structure.
Check claims.
Update internal links.
Decide republish, merge, redirect, or retire.
Watch post-refresh signals.
Operator Decision Table
| Situation | Action |
|---|---|
| Request is unclear | Park |
| Research is missing | Research |
| Offer status unclear | Park |
| Compliance risk unclear | Review or Park |
| Content purpose clear | Brief |
| Brief complete | Draft |
| Draft ready | Review |
| Approved and ready | Publish or Handoff |
| Existing asset useful in another format | Repurpose |
| Existing content outdated | Refresh |
| Content no longer useful | Retire |
| Signal belongs to another Brain | Handoff |
Operator Warnings
Do Not Start With Drafting
Do not start with writing.
Start with:
source Brain
purpose
brief
research basis
approval boundary
Then draft.
Do Not Skip The Brief
If the content asset matters, it needs a brief.
Skipping the brief creates random content.
Do Not Treat Parked Items As Active Work
Parked means not ready.
Do not draft from parked items.
Do Not Treat Checklists As Approval Authority
Checklists help review.
They do not approve offers, claims, budgets, campaigns, tests, or strategy.
Do Not Automate Yet
The first operational version is manual.
Do not build:
queues
dashboards
generators
Supabase tables
Brain Room routing
automation
until repeated manual workflow proves the need.
Source Of Truth Note
MCR remains the source of truth for Content Brain.
mwmscontentbrain.site will become the future operational environment.
If a conflict exists between MCR and mwmscontentbrain.site, MCR wins.
Any workflow copy must remain traceable to the original MCR page.
Approval Boundaries
Content Brain must preserve these boundaries:
Affiliate Brain approves affiliate offer direction.
Research Brain provides evidence and research truth.
Search Intelligence Brain supports search demand and SERP opportunity validation.
Ads Brain owns campaign execution and ad testing.
Experimentation Brain owns test validity and learning quality.
Compliance Brain owns compliance interpretation where risk exists.
Finance Brain owns spend, budget, and capital discipline.
Conversion Brain owns conversion strategy.
Sales Brain owns sales progression strategy.
Data Brain owns data quality and signal interpretation.
HeadOffice owns governance oversight.
Content Brain supports these Brains with content assets.
It does not replace them.
First Operational Copy Status
This page is part of the first operational copy preparation batch.
Current status:
Prepared in MCR
Not migrated
Not live on mwmscontentbrain.site
Not connected to plugin/UI
Not automated
Previous operational copy prepared:
Content Brain Home Operational Copy
Next operational copy to prepare:
Content Brain Content Brief Template Operational Copy
Relationship To Content Brain Home Operational Copy
The Content Brain Home Operational Copy gives the operator the starting point.
This Workflow Operational Copy gives the operator the operating path.
Home = where to start.
Workflow = what to do next.
Relationship To Content Brain First Migration Batch Review
The Content Brain First Migration Batch Review identified the Content Brain Workflow Map as the second page in the operational copy order.
This page prepares the simplified operational copy for that workflow.
First Migration Batch Review = decision record.
Content Brain Workflow Operational Copy = prepared future operator workflow page.
Relationship To Content Brain Operational Migration Plan
The Content Brain Operational Migration Plan defines the first practical operating version of mwmscontentbrain.site.
This page implements the workflow copy from that plan.
The plan remains in MCR.
This page remains in MCR until migration is approved.
Relationship To Content Brain Copy Map
The Content Brain Copy Map classifies the Content Brain Workflow Map as:
Copy To Content Brain
This page is a prepared simplified operational copy of that future workflow page.
It should remain in MCR until migration is approved.
Relationship To Content Brain Page Registry
This page should be added to the Content Brain Page Registry as:
Page Title: Content Brain Workflow Operational Copy
Document Type: Operational Copy
Parent Page: Content Brain
Status: Draft
Migration Classification: MCR Only First
Plugin Or UI Candidate: No Direct UI
Notes: Prepared simplified future workflow copy for mwmscontentbrain.site. Defines the operator workflow from signal or request through source Brain identification, action selection, content brief creation, checklist or framework use, drafting, publishing readiness, approval routing, handoff, repurposing, refresh, retirement, signal tracking, and learning feedback.
Relationship To mwmscontentbrain.site
This page is future workflow copy for mwmscontentbrain.site.
It should not be copied yet.
It should be used only after:
Content Brain stability is confirmed
first migration batch review is accepted
operational copy batch is prepared
migration timing is approved
MCR source-of-truth links are preserved
Drift Protection
The system must prevent:
this page being treated as live migration
this page being treated as plugin/UI instruction
this page replacing Content Brain Workflow Map as MCR source
this page replacing Content Brain Canon
this page replacing Content Brain Architecture
this page overriding Content Brain Copy Map
this page bypassing the migration readiness checklist
this page weakening approval boundaries
this page starting automation work too early
this page causing work on M’s active build areas
this page turning signals into content automatically
this page treating checklists as approval authority
Architectural Intent
The Content Brain Workflow Operational Copy exists to make the future Content Brain workflow simple and usable.
Its architectural role is to translate the MCR-level Content Brain Workflow Map into a practical operator path.
The goal is repeatability.
The future workflow page should help an operator move from:
signal
to decision
to brief
to draft
to readiness check
to approval
to handoff or publishing
to learning feedback
without confusing Content Brain’s role with the authority of other Brains.
Final Rule
Do not migrate this page until migration is approved.
Do not build plugin or UI from this page yet.
Do not treat this page as source of truth over MCR control pages.
Do not use this page to override Brain authority boundaries.
Do not let any signal become content work without qualification.
Content Brain Workflow Operational Copy is a prepared future operator workflow draft only.
MCR remains source of truth.
Change Log
Version: v1.0
Date: 2026-05-24
Author: HeadOffice
Change: Initial creation of Content Brain Workflow Operational Copy. Defines the prepared simplified future workflow copy for mwmscontentbrain.site, including workflow overview, signal intake, source Brain identification, action selection, content brief creation, checklist and framework routing, drafting, publishing readiness, approval routing, handoff, repurposing, refresh, retirement, signal tracking, learning feedback, common workflow paths, operator warnings, approval boundaries, source-of-truth note, first operational copy status, and relationships to Content Brain Home Operational Copy, Content Brain First Migration Batch Review, Content Brain Operational Migration Plan, Content Brain Copy Map, Content Brain Page Registry, and mwmscontentbrain.site.
Change Impact Declaration
Pages Created:
Content Brain Workflow Operational Copy
Pages Updated:
None
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 WORKFLOW OPERATIONAL COPY v1.0