Brain Name: Content Brain
Document Type: Operational Copy
Status: Draft
Version: v1.1
Authority: Content Brain under HeadOffice governance
Applies To: mwmscontentbrain.site future home page, Content Brain operational entry point, manual content workflow, content requests, qualification, content projects, asset planning, source and evidence control, content production, editing, review, approval, publishing preparation, lifecycle management and Site Intelligence supporting actions
Parent: Content Brain
Enforcement Mode: Operational
Last Reviewed: 2026-06-16
Content Brain Home Operational Copy
Purpose
The Content Brain Home Operational Copy defines the prepared future homepage content for mwmscontentbrain.site.
This page is not the live homepage.
It remains an MCR-controlled operational copy until migration and implementation are approved.
Its purpose is to provide a simple operational starting point for the complete Content Brain workflow.
The future homepage must help an operator:
start a content request
confirm whether the work belongs in Content Brain
check whether suitable content already exists
decide whether to create, refresh, expand, correct, merge, repurpose, relink, retire or take no action
create or identify the correct content project
plan the required content assets
identify source, evidence and approval requirements
choose between a structured brief and a direct production instruction
move content through production
move content through editing and quality review
route specialist review where required
preserve human approval
prepare approved content for publishing or delivery
record destination and completion state
manage refresh, repurposing, correction, consolidation and retirement
use Site Intelligence as a supporting input
understand what is not automated
preserve MCR as the source of truth
The homepage must represent Content Brain as a complete content production and lifecycle system.
It must not present Content Brain as only:
a content brief system
an SEO system
an affiliate-content system
a Site Intelligence system
a research-record system
a collection of checklists
a migration project
a future automation system
Scope
This operational copy applies to:
the future mwmscontentbrain.site homepage
Content Brain operator onboarding
manual content request intake
content qualification
existing-content checks
content action decisions
content project entry
asset planning
content-pack planning
source and evidence preparation
content briefing
direct production instructions
content drafting
content editing
content quality control
specialist review
human approval
publishing preparation
destination tracking
content refresh
content repurposing
content consolidation
content correction
content retirement
Site Intelligence-supported content actions
manual operational status visibility
This operational copy does not replace:
Content Brain Canon
Content Brain Architecture
Content Brain Operating Model
Content Brain Workflow Map
Content Brain Page Registry
Content Brain Copy Map
approved Content Brain frameworks
approved Content Brain standards
approved Content Brain templates
HeadOffice governance
MWMS Brain authority rules
It does not authorise:
full Content Brain plugin development
content generation automation
autonomous publishing
worker activation
queue execution
AI Employee activation
Brain Room routing
automatic M handoff
Research Brain changes
M’s active Research Brain work
live cross-Brain task wiring
Core Rule
Content Brain turns approved requests, objectives, intelligence, evidence, strategy and operational needs into complete content assets.
Content Brain is responsible for:
content planning
content project definition
asset planning
content briefing
content production
content editing
quality control
specialist-review preparation
human-approval preparation
publishing preparation
content delivery support
content refresh
content repurposing
content correction
content consolidation
content retirement
Content Brain does not replace the Brains that control:
strategy
research truth
campaign approval
financial approval
compliance interpretation
experiment validity
conversion authority
customer intelligence
data integrity
system governance
Content Brain produces and manages content within approved authority.
MCR remains the source of truth.
mwmscontentbrain.site will become the operational working environment.
Supabase will hold repeatable structured records.
Human control remains mandatory.
Future Homepage Title
Content Brain
Future Homepage Subtitle
Plan, produce, review, approve and manage MWMS content from request through lifecycle.
Future Operator Description
Content Brain is the MWMS content production and lifecycle system.
It helps turn approved requests, research, strategy, customer intelligence, campaign needs, website needs and Site Intelligence findings into complete content assets.
It supports:
website content
articles
social content
video scripts
audio scripts
webinar scripts
advertising content
newsletters
email sequences
manuals
guides
documentation
reports
lead magnets
training material
affiliate content packs
Content Brain supports the complete workflow from request and planning through production, editing, approval, publishing preparation and lifecycle management.
What Content Brain Does
Content Brain helps operators:
capture content requests
qualify requests
check existing content
prevent duplicate content
decide the correct content action
create content projects
plan individual assets
plan coordinated content packs
identify source requirements
identify evidence requirements
identify compliance requirements
identify specialist-review requirements
create proportional content briefs
issue direct production instructions for simple work
produce complete drafts
edit and revise content
check editorial consistency
check information gain
check trust and authority elements
check approved voice and terminology
prepare content for specialist review
prepare content for human approval
prepare content for publication or delivery
record destination readiness
record completion state
identify refresh needs
identify repurposing opportunities
identify consolidation opportunities
identify correction requirements
identify retirement requirements
convert Site Intelligence findings into content actions
Content Brain makes content work structured, traceable and controlled.
What Content Brain Does Not Do
Content Brain does not:
approve affiliate offers
approve campaign budgets
approve advertising campaigns
approve compliance-sensitive claims
invent evidence
invent research findings
replace Research Brain
replace Strategy Brain
replace Customer Brain
replace Conversion Brain
replace Ads Brain
replace Affiliate Brain
replace Finance Brain
replace Compliance Brain
replace Data Brain
replace Experimentation Brain
replace HeadOffice
publish automatically
send emails automatically
send newsletters automatically
post social content automatically
deploy advertisements automatically
create unrestricted content automatically
activate workers automatically
activate AI Employees automatically
route work through Brain Room automatically
hand work to M automatically
replace MCR as the source of truth
Where another Brain owns a decision, Content Brain must receive or request that decision.
It must not assume authority.
Start Here
The future Content Brain homepage should begin with one primary operator action:
Start Content Work
The operator should then identify:
what has been requested
why the content is needed
who requested it
which Brain or business area owns the objective
which audience is being served
which destination or channel is intended
whether suitable content already exists
whether research or evidence already exists
whether specialist review is required
who must approve the final content
The homepage must not force the operator to begin with a content brief.
The first step is understanding the content need.
Operational Workflow
The future homepage should display the complete operational workflow:
Content Request
Qualification
Existing Content Check
Action Decision
Content Project
Asset Planning
Source And Evidence
Brief Or Direct Instruction
Content Production
Editing And Quality Control
Specialist Review
Human Approval
Publishing Preparation
Human-Controlled Publication Or Delivery
Outcome Recording
Measurement
Lifecycle Action
Each stage must remain visible even where the current workflow is manual.
Content Request
Purpose
Capture the content need before work begins.
A content request should identify:
request title
requesting Brain or owner
business objective
content objective
target audience
content destination
required format
known deadline
approval owner
known sources
known risks
related project
related existing content
Possible request sources include:
HeadOffice
Strategy Brain
Affiliate Brain
Research Brain
Customer Brain
Creative Brain
Ads Brain
Conversion Brain
Compliance Brain
PPL Brain
AIBS Brain
Ecommerce Brain
Site Intelligence
a human operator
a website requirement
a campaign requirement
a customer-support requirement
a documentation requirement
A request is not automatic approval to produce content.
It must first be qualified.
Qualification
Purpose
Confirm that the request:
belongs in Content Brain
has a clear objective
has an identifiable audience
has a valid destination
has sufficient authority
has the required source material
does not duplicate existing work
does not conflict with another Brain
does not require an unresolved approval first
Qualification should determine:
valid request
more information required
research required
strategy required
compliance review required
another Brain owns the work
existing content may already solve the need
content work should proceed
content work should not proceed
Existing Content Check
Purpose
Prevent unnecessary duplication and identify whether existing content can be reused.
Before creating new content, check:
exact title matches
close title matches
same topic
same audience
same purpose
same funnel stage
same content format
same destination
existing MCR source pages
existing operational pages
existing project assets
existing drafts
existing published content
existing Site Intelligence findings
The existing-content decision may be:
no suitable content exists
existing content can be reused
existing content can be refreshed
existing content should be expanded
existing content should be corrected
existing content should be merged
existing content should be repurposed
existing content should be relinked
existing content should be retired
new content is required
Action Decision
Purpose
Choose the correct content action.
Available content actions include:
Create
Create a new content asset where no suitable asset exists.
Refresh
Update an existing asset because information, evidence, performance or context has changed.
Expand
Add depth, usefulness, coverage or supporting material to an existing asset.
Correct
Repair factual, structural, compliance, editorial or technical problems.
Merge
Combine overlapping content into a stronger controlled asset.
Repurpose
Adapt an approved asset into another format or channel.
Reformat
Change the presentation or delivery format without changing the approved meaning.
Relink
Improve internal relationships, navigation, authority flow or reader journey.
Retire
Remove an asset from active use while preserving the appropriate record.
Archive
Preserve an inactive asset or record without deleting it.
No Action
Record that no content work is currently required.
Specialist Review
Pause content work until the correct specialist decision is available.
Create Content Project
Create a coordinated project where one objective requires multiple assets.
Content Project
Purpose
Group related content work around one objective.
A content project may include:
one asset
multiple related assets
a website-content project
an article series
a topic hub
a social-content campaign
a video-content package
an advertising-content package
an email sequence
a newsletter series
a documentation set
a training-content set
an affiliate product content pack
a launch-support content pack
a refresh programme
a repurposing programme
A content project should identify:
project title
project objective
request source
owning Brain or business area
target audience
required outcomes
planned assets
required sources
approval owner
specialist reviewers
destinations
dependencies
blockers
current status
next action
Asset Planning
Purpose
Define the content assets needed to complete the project.
Each asset should identify:
asset title
asset type
asset purpose
target audience
destination
channel
funnel or journey role
relationship to other assets
source requirements
evidence requirements
voice requirements
format requirements
call-to-action requirements
compliance sensitivity
review requirements
approval owner
production priority
current status
next action
Possible asset types include:
website page
landing page
bridge page
article
blog post
comparison page
review page
FAQ page
social post
social content series
short-form video script
long-form video script
VEO3 script
audio script
webinar script
advertisement
advertorial
newsletter
email sequence
manual
guide
documentation page
report
lead magnet
training material
presentation content
content pack
refresh asset
repurposed asset
Source And Evidence
Purpose
Ensure content is grounded before production.
Source and evidence requirements may include:
MCR source pages
approved Research Brain findings
approved Strategy Brain direction
approved Customer Brain intelligence
approved offer information
approved product information
verified website information
approved data
approved statistics
approved testimonials
approved case studies
approved subject-matter input
approved compliance guidance
approved brand and voice standards
existing content assets
Site Intelligence findings
Source records should distinguish:
confirmed fact
approved interpretation
working assumption
unverified claim
restricted claim
content direction
creative concept
customer language
quotation
data point
Source material must remain traceable.
Content Brain must not manufacture missing evidence.
Brief Or Direct Instruction
Purpose
Use the right amount of planning for the task.
A structured content brief should be used when:
the content is complex
multiple Brains are involved
research must be interpreted
search intent matters
compliance risk exists
multiple assets are connected
a new website page is required
a major article is required
a script supports a campaign
a content pack is required
approval requirements are significant
A direct production instruction may be used when:
the task is simple
the source material is clear
the audience is clear
the destination is clear
the format is clear
approval requirements are clear
the change is minor
the content is a controlled update
Briefing must support production.
It must not become a permanent delay before production.
Content Production
Purpose
Create the complete required content asset.
Production may include:
outline creation
drafting
section development
headline development
hook development
introduction development
body content
examples
proof elements
calls to action
metadata
supporting copy
script directions
visual notes
internal-link suggestions
content-pack coordination
Content production must follow:
approved sources
approved evidence
approved voice
approved terminology
approved objectives
approved audience understanding
approved format requirements
approved compliance boundaries
A first draft is not a completed asset.
Editing And Quality Control
Purpose
Improve the draft and determine whether it is ready for specialist review or human approval.
Editing and quality control should check:
accuracy
completeness
clarity
structure
logic
usefulness
information gain
audience alignment
intent alignment
voice consistency
terminology consistency
claim support
trust elements
experience and expertise signals
internal links
external references
calls to action
formatting
duplication
unnecessary repetition
thin sections
unsupported statements
content gaps
destination requirements
Editorial review may result in:
ready for specialist review
ready for human approval
revision required
source clarification required
evidence required
compliance review required
project change required
asset no longer required
Specialist Review
Purpose
Route content to the correct specialist where the content requires authority outside Content Brain.
Possible specialist review includes:
compliance review
legal review
medical review
technical review
financial review
product review
research review
search review
data review
offer review
campaign review
brand review
Specialist review does not replace final human approval.
Human Approval
Purpose
Preserve accountable acceptance before content is released or delivered.
Human approval decisions include:
Approved
Approved With Minor Changes
Revision Required
Rejected
On Hold
Approval Pending
Approval must identify:
approver
decision
date
conditions
required changes
approved destination
approved claims
approved call to action
approved version
No draft should be treated as approved merely because it completed editing.
Publishing Preparation
Purpose
Prepare approved content for its intended destination.
Publishing preparation may include:
final title
final slug
metadata
formatting
internal links
external links
images
media notes
alt text
calls to action
tracking requirements
disclaimers
author details
approval record
destination
publication owner
delivery package
version confirmation
Publishing preparation does not mean autonomous publication.
Human-Controlled Publication Or Delivery
Content may be:
published manually
scheduled manually
handed to an approved operator
handed to another Brain
handed to a platform owner
delivered as a completed document
delivered as a script
delivered as an advertising package
delivered as a campaign-support package
delivered as documentation
No publication, sending, posting or deployment is automated in the current operating stage.
Outcome Recording
Purpose
Record what happened after the content was approved and prepared.
Possible outcomes include:
published
scheduled
delivered
implemented
rejected by destination
returned for changes
held
cancelled
replaced
merged
archived
retired
The outcome record should identify:
final asset version
destination
completion date
responsible operator
publication or delivery reference
known issues
next review date
Lifecycle Management
Purpose
Manage content after completion.
Lifecycle actions include:
monitor
refresh
expand
correct
repurpose
relink
merge
consolidate
reformat
archive
retire
no action
Lifecycle decisions may be triggered by:
new research
new strategy
new product information
new customer intelligence
performance decline
search changes
website changes
broken links
compliance changes
outdated evidence
duplicated content
new content opportunities
Site Intelligence findings
content-pack reuse
campaign requirements
Lifecycle management closes the loop between completed content and future content work.
Site Intelligence Supporting Role
Site Intelligence supports the Content Brain workflow by identifying:
missing content
thin content
weak content
duplicate content
outdated content
incorrect content
content gaps
internal-linking gaps
trust issues
compliance concerns
refresh opportunities
repurposing opportunities
consolidation opportunities
retirement candidates
Site Intelligence findings must enter the main workflow through:
Content Request
Qualification
Existing Content Check
Action Decision
Content Project where required
Site Intelligence does not replace:
content planning
content production
editing
approval
publishing preparation
lifecycle management
The Site Intelligence Records screen remains a supporting operational area.
It is not the Content Brain homepage.
Main Homepage Starting Actions
The future homepage should provide the following primary actions:
Start A Content Request
Use when new content work has been requested or identified.
Review Existing Content
Use when the operator must determine whether to reuse, refresh, expand, correct, merge, repurpose, relink or retire an existing asset.
Open A Content Project
Use when one objective requires one or more coordinated assets.
Plan Content Assets
Use when the required asset set must be defined.
Prepare Sources And Evidence
Use when research, proof, claims, customer language or source authority must be assembled.
Create A Content Brief
Use when structured planning is required before production.
Start Content Production
Use when the request, action, asset and source requirements are sufficiently clear.
Review And Edit Content
Use when a draft requires quality control.
Prepare For Approval
Use when content is ready for specialist or human review.
Prepare For Publishing
Use when an approved asset must be packaged for publication or delivery.
Manage Content Lifecycle
Use when existing content needs refresh, expansion, repurposing, correction, consolidation or retirement.
Review Site Intelligence Actions
Use when a Site Intelligence finding requires a content decision.
Supporting Operator Starting Points
Content Briefs
Go to:
Content Brain Content Brief Template
Use for:
complex or multi-step content work
Publishing Readiness
Go to:
Content Brain Publishing Readiness Checklist
Use for:
approved content being prepared for destination use
Affiliate Product Content Packs
Go to:
Content Brain Affiliate Product Content Pack Checklist
Use for:
coordinated affiliate-support assets
Affiliate Funnel Support
Go to:
Content Brain Affiliate Funnel Support Map
Use for:
mapping content to affiliate funnel stages
SEO Content
Go to:
Content Brain SEO Content Brief Standard
Use for:
search-focused content requiring SEO-specific planning
Internal Linking
Go to:
Content Brain Internal Linking Strategy Framework
Use for:
reader journeys, content relationships and authority flow
Repurposing
Go to:
Content Brain Content Repurposing Framework
Use for:
turning approved assets into new formats
Refresh
Go to:
Content Brain SEO Testing And Refresh Framework
Use for:
updating, expanding, correcting, merging or retiring existing content
Future Homepage Layout
The future homepage should use a simple operational structure.
Recommended sections:
Content Brain Status
Start Content Work
Active Content Requests
Active Content Projects
Assets In Planning
Assets In Production
Assets In Editing
Assets Awaiting Specialist Review
Assets Awaiting Human Approval
Assets Ready For Publishing Preparation
Blocked Work
Lifecycle Actions
Site Intelligence Actions
Reference And Guidance
The first operational page does not require all of these sections to be automated.
They define the future operating structure.
Recommended Future Menu
Content Brain Home
Content Requests
Content Projects
Content Assets
Sources And Evidence
Content Briefs
Production
Editing And Review
Approvals
Publishing Preparation
Lifecycle
Site Intelligence
Reference
Do not add active menus yet for:
automated generators
autonomous publishing
workers
AI Employees
Brain Room routing
cross-Brain task automation
automatic M handoff
unproven queues
unproven dashboards
Current Status Display
The future homepage should display:
Manual Workflow: Active
Human Approval: Required
MCR Source Of Truth: Active
Content Brain Operational Site: In Development
Supabase Structured Records: Supporting Site Intelligence Records Only At Current Stage
Site Intelligence Records UI: Stabilised Supporting Proof
Full Production Interface: Not Started
Content Generation Automation: Not Started
Publishing Automation: Not Started
Workers: Not Started
Queues: Not Started
AI Employees: Not Started
Brain Room Routing: Not Started
M Handoff: Not Started
Approval Boundaries
Content Brain must preserve the following authority boundaries.
HeadOffice
Controls governance, system authority and major structural decisions.
Strategy Brain
Controls strategic direction.
Research Brain
Controls research evidence, research confidence and research truth.
Customer Brain
Controls approved customer intelligence.
Creative Brain
Controls approved creative concepts and direction where applicable.
Affiliate Brain
Controls affiliate offer direction and affiliate campaign requirements.
Ads Brain
Controls advertising campaigns, placement and testing.
Conversion Brain
Controls conversion strategy.
Compliance Brain
Controls compliance interpretation and risk decisions.
Finance Brain
Controls budget and financial authority.
Experimentation Brain
Controls test validity and interpretation.
Data Brain
Controls data quality and trusted measurement.
Content Brain
Produces and manages content within approved inputs and boundaries.
MCR Source-Of-Truth Rule
MCR remains the source of truth for:
Content Brain Canon
Content Brain Architecture
Content Brain Operating Model
Content Brain Workflow Map
Content Brain Page Registry
Content Brain Copy Map
Content Brain master frameworks
Content Brain master standards
Content Brain master templates
Content Brain master specifications
mwmscontentbrain.site must contain:
operational guidance
working interfaces
approved operator pages
manual workflow support
structured operational views
It must not become a competing source of truth.
Where MCR and the operational site conflict:
MCR controls
the operational page must be corrected
implementation must pause where necessary
Supabase Position
Supabase will hold repeatable operational records.
Future structured records may include:
content requests
qualification decisions
existing-content checks
action decisions
content projects
content assets
asset relationships
source references
evidence references
briefs
production status
editing status
review status
approval status
publishing-preparation status
destination status
completion status
lifecycle status
Site Intelligence findings
blockers
archive state
Supabase records must not replace:
Canon
Architecture
Operating Model
Workflow Map
Page Registry
Copy Map
master frameworks
Human-Controlled Operating Rule
The current workflow remains human controlled.
Humans must control:
request acceptance
qualification decisions
content action decisions
project creation
asset planning
source approval
brief approval where required
production initiation
specialist-review routing
content approval
publishing preparation
publication
delivery
lifecycle decisions
Automation may only be considered after repeated manual use proves:
the need
the fields
the statuses
the decisions
the authority boundaries
the exceptions
the failure handling
the approval requirements
the recovery process
Operator Warnings
Do Not Begin With A Brief Automatically
A content brief is one tool inside the workflow.
The operator must first understand the request and decide the correct action.
Do Not Create Duplicate Content
Always check existing content before creating something new.
Do Not Treat A Draft As Approved
A draft may require:
editing
source correction
specialist review
human approval
Do Not Treat Publishing Preparation As Publication
Content Brain may prepare content for publication.
Publication remains human controlled.
Do Not Treat Site Intelligence As The Main System
Site Intelligence identifies issues and opportunities.
The main Content Brain system produces and manages content.
Do Not Treat Operational Pages As Canon
Operational pages support work.
MCR retains authority.
Do Not Treat Supabase Records As Canon
Records store operational state.
They do not define authority.
Do Not Overbuild
The current stage does not authorise:
full dashboard development
production queue development
refresh queue development
repurposing queue development
autonomous generators
autonomous publishing
worker activation
AI Employee activation
Brain Room routing
automatic M handoff
Plugin And UI Position
The future Content Brain interface may eventually include:
Content Brain Home
Content Request Intake
Qualification And Action Decision
Existing Content Check
Content Project Workspace
Asset Planning Workspace
Source And Evidence Workspace
Content Brief Workspace
Production Workspace
Editing And Quality-Control Workspace
Specialist Review Workspace
Human Approval Workspace
Publishing Preparation Workspace
Destination And Completion Status
Lifecycle Workspace
Site Intelligence Supporting Workspace
No full interface build is authorised by this page.
The manual workflow must be validated first.
Relationship To Content Brain Canon
Content Brain Canon defines Content Brain authority and boundaries.
This operational copy translates that authority into a simplified operator starting point.
This page must not override the Canon.
Relationship To Content Brain Architecture
Content Brain Architecture defines:
system layers
record relationships
operational components
source-of-truth boundaries
future interface direction
This operational copy presents the architecture as a usable homepage flow.
Relationship To Content Brain Operating Model
The Operating Model defines how humans operate Content Brain.
This page provides the operational entry point into that model.
Relationship To Content Brain Workflow Map
The Workflow Map defines movement from request through lifecycle management.
This homepage must preserve the complete sequence.
Relationship To Content Brain Page Registry
This page is recorded as:
Page Title: Content Brain Home Operational Copy
Document Type: Operational Copy
Parent Page: Content Brain
Status: Draft
Migration Classification: MCR Only First
Plugin Or UI Candidate: Possible Content Brain Home Later
Notes: Prepared future operational homepage copy aligned with the complete Content Brain request-to-lifecycle workflow.
Relationship To Content Brain Copy Map
The Content Brain Copy Map classifies this page as:
Hold And Rewrite until aligned with the complete production system.
This v1.1 replacement completes that rewrite.
The page remains:
MCR Only First
Not migrated
Not live
Not connected to the main plugin or UI
Relationship To mwmscontentbrain.site
This page is prepared future operational homepage copy for mwmscontentbrain.site.
It must not be copied until:
the revised operational structure is accepted
manual workflow requirements are confirmed
migration is approved
destination duplication is checked
source links are preserved
the operational page is validated
rollback remains possible
Current Operational Copy Status
Prepared in MCR: Yes
Aligned With Content Brain Canon v1.1: Yes
Aligned With Content Brain Architecture v1.1: Yes
Aligned With Content Brain Operating Model v1.2: Yes
Aligned With Content Brain Workflow Map v1.2: Yes
Aligned With Content Brain Page Registry v3.3: Yes
Aligned With Content Brain Copy Map v2.8: Yes
Migrated To mwmscontentbrain.site: No
Live Operational Homepage: No
Connected To Full Plugin Or UI: No
Connected To Production Automation: No
Connected To Publishing Automation: No
Connected To Workers: No
Connected To AI Employees: No
Connected To Brain Room Routing: No
Connected To M Handoff: No
Research Brain Impact: None
Drift Protection
The system must prevent:
Content Brain being reduced to briefs
Content Brain being reduced to SEO
Content Brain being reduced to affiliate content
Content Brain being reduced to Site Intelligence
Content Brain being reduced to research records
content production being omitted
editing being omitted
human approval being omitted
publishing preparation being omitted
lifecycle management being omitted
a brief being treated as approval
a draft being treated as completed content
publishing preparation being treated as publication
operational pages being treated as Canon
Supabase records being treated as Canon
temporary Site Intelligence fields becoming the permanent data model
the Site Intelligence Records screen becoming the homepage
automation being started before manual proof
workers being activated without authority
AI Employees being activated without role controls
Brain Room routing being activated prematurely
automatic M handoff
interference with M’s Research Brain work
Architectural Intent
The Content Brain Home Operational Copy exists to turn the complete Content Brain structure into a clear operator starting point.
Its role is to help an operator move from:
Content Need
to:
Qualified Content Work
to:
A Defined Content Action
to:
A Controlled Project And Asset Plan
to:
Grounded Production
to:
Edited And Reviewed Content
to:
Human Approval
to:
Publishing Preparation
to:
Lifecycle Management
The homepage should provide clarity without copying the full MCR governance structure.
The long-term operational goal is a production-focused environment that allows humans to:
see what content work exists
understand what stage it is in
understand what is blocking it
understand what approval is required
understand what should happen next
The homepage must preserve:
source authority
content traceability
approval boundaries
human control
cross-Brain separation
MCR alignment
Final Rule
Content Brain Home must represent the complete content production and lifecycle system.
It must begin with the content need.
It must not begin automatically with:
a content brief
an SEO task
an affiliate pack
a Site Intelligence test
an opportunity queue
a generator
The correct operational sequence is:
Content Request
Qualification
Existing Content Check
Action Decision
Content Project
Asset Planning
Source And Evidence
Brief Or Direct Instruction
Content Production
Editing And Quality Control
Specialist Review
Human Approval
Publishing Preparation
Human-Controlled Publication Or Delivery
Outcome Recording
Lifecycle Management
MCR remains the source of truth.
mwmscontentbrain.site remains the future operational environment.
Supabase remains the structured records layer.
Human approval remains mandatory.
No automation is authorised.
No worker is authorised.
No queue execution is authorised.
No AI Employee is authorised.
No Brain Room routing is authorised.
No automatic M handoff is authorised.
M’s Research Brain work remains untouched.
Change Log
Version: v1.1
Date: 2026-06-16
Author: HeadOffice
Change: Rewritten to align the Content Brain Home Operational Copy with the complete Content Brain production and lifecycle mandate.
Updated the homepage position from a narrow operator entry focused mainly on:
content briefs
publishing readiness
affiliate content packs
affiliate funnel support
SEO
internal linking
repurposing
refresh
to the complete operational sequence:
Content Request
Qualification
Existing Content Check
Action Decision
Content Project
Asset Planning
Source And Evidence
Brief Or Direct Instruction
Content Production
Editing And Quality Control
Specialist Review
Human Approval
Publishing Preparation
Human-Controlled Publication Or Delivery
Outcome Recording
Lifecycle Management
Added:
content-request entry
qualification controls
existing-content checks
content-action decisions
content-project structure
asset-planning structure
source and evidence requirements
proportional brief or direct-instruction decision
complete production position
editing and quality-control position
specialist-review position
human-approval position
publishing-preparation position
outcome recording
content-lifecycle management
Site Intelligence supporting role
future homepage action structure
future homepage status structure
future operational menu
Supabase record position
plugin and UI position
expanded drift protection
Clarified that:
Content Brain is a complete content production and lifecycle system
Site Intelligence is a supporting capability
content briefs are one tool rather than the required starting point for all work
a first draft is not an approved asset
publishing preparation is not publication
MCR remains the source of truth
mwmscontentbrain.site remains the future operational environment
Supabase remains the structured records layer
manual workflow remains human controlled
no content generation automation is authorised
no publishing automation is authorised
no worker, queue, AI Employee, Brain Room routing or automatic M handoff is authorised
M’s Research Brain work remains untouched
Version: v1.0
Date: 2026-05-24
Author: HeadOffice
Change: Initial creation of Content Brain Home Operational Copy. Defined the prepared simplified future homepage copy for mwmscontentbrain.site, including what Content Brain does, what Content Brain does not do, operator starting points, manual workflow, future menu sections, approval boundaries, source-of-truth note, plugin and UI hold rules, first operational copy status and relationships to Content Brain migration and governance pages.
Change Impact Declaration
Pages Created:
None
Pages Updated:
Content Brain Home Operational Copy
Pages Deprecated:
None
Pages To Move To Trash:
None
Registries Requiring Update:
Content Brain Page Registry
Content Brain Copy Map
Canon Version Update Required:
No
Architecture Version Update Required:
No
Operating Model Version Update Required:
No
Workflow Map Version Update Required:
No
Automation Status Change:
No
Plugin Or UI Status Change:
No
Worker Status Change:
No
Queue Status Change:
No
AI Employee Status Change:
No
Brain Room Routing Status Change:
No
M Handoff Required:
No
Research Brain Impact:
None
END CONTENT BRAIN HOME OPERATIONAL COPY v1.1
END OF FULL FILE OUTPUT