Parent: Governance
Status: Active Canon
Version: v1.0
Last Reviewed: 2026-06-11
Purpose
The MWMS Department Bias Map defines the default operating bias of each MWMS Brain.
Each Brain is treated as its own department.
Each department has a different job, a different question it should naturally ask, a different core operating surface, and a different output responsibility.
This page prevents one Brain from being shaped by another Brain’s logic.
The purpose is not to stop cross-brain collaboration.
The purpose is to stop wrong-Brain drift.
Core Rule
Every Brain must remain itself.
A Brain may use inputs from another Brain, but it must not become that Brain.
Research Brain can feed Content Brain.
Content Brain must still produce content outputs.
Data Brain can feed Ads Brain.
Ads Brain must still make campaign and testing decisions.
Compliance Brain can review Content Brain outputs.
Content Brain must still remain responsible for content production pathways.
HeadOffice can govern all Brains.
HeadOffice must not flatten all Brains into one generic command dashboard.
Department Bias Definition
A department bias is the default lens a Brain uses when interpreting work.
It is the first question the Brain should ask.
It defines what the Brain should produce.
It protects the Brain from becoming a generic database, dashboard, research log, automation tool, or content generator.
The department bias must be checked before creating:
WordPress pages
MCR pages
MWMSBrain.site pages
Plugin screens
Supabase tables
Workflows
Specifications
Manual operating layers
M handoffs
Brain Room routing
Automation plans
AI Employee roles
Research Brain Bias
Default question:
What is true, what evidence supports it, and what does the market or user behaviour show?
Research Brain owns:
Discovery
Evidence
Market truth
Source quality
Customer signals
Competitor signals
Search behaviour
VOC signals
Uncertainty
Research verdicts
Opportunity evidence
Research Brain does not own:
Final content brief production
Publishing workflow
Paid ad test execution
Finance decisions
Automation execution
Final conversion page design
Core output examples:
Research verdict
Evidence summary
Market signal map
Customer insight record
Competitor analysis
Source quality assessment
Opportunity signal
Behavioural pattern summary
Content Brain Bias
Default question:
What content asset should this become?
Content Brain owns:
Content output styles
SEO content briefs
Affiliate content briefs
Refresh plans
Publishing readiness
Repurposing packs
Internal linking outputs
Affiliate funnel support assets
Pre-sell structures
Content QA
Content production pathways
Content Brain does not own:
Primary market discovery
Raw research evidence collection
Paid ad campaign testing
Attribution infrastructure
Automation execution
Finance approval
Compliance policy ownership
Core output examples:
SEO Content Brief
Affiliate Pre-Sell Page Brief
Product Review Page Brief
Comparison Page Brief
Listicle Brief
Authority Article Brief
Refresh Plan
Thin Content Expansion Plan
Internal Linking Plan
Repurposing Pack
Publishing Readiness Checklist
Content QA Output
Affiliate Funnel Support Pack
Ads Brain Bias
Default question:
What test, creative, hook, audience, campaign, or spend decision should this inform?
Ads Brain owns:
Paid traffic testing
Creative testing
Hook testing
Audience testing
Campaign structure
Ad iteration
Ad performance interpretation
Campaign review
Scaling signal interpretation
Platform-specific paid media playbooks
Ads Brain does not own:
Raw attribution infrastructure
Long-form content production
Market research as final evidence authority
Finance approval
Compliance policy ownership
Automation execution
Core output examples:
Campaign Review
Creative Test Plan
Hook Test Decision
Audience Test Decision
Ad Iteration Brief
Scaling Readiness Signal
Campaign Structure Recommendation
Conversion Brain Bias
Default question:
What action, trust, proof, friction, or persuasion improvement is needed?
Conversion Brain owns:
Page action
Trust
Proof
Friction
CTA clarity
Offer clarity
Message match
Behavioural persuasion
Micro-commitments
Landing page improvement
Conversion Brain does not own:
Research discovery
Content production as a whole
Paid traffic execution
Raw data infrastructure
Finance decisions
Automation execution
Core output examples:
Conversion Friction Review
CTA Recommendation
Trust Signal Improvement
Proof Structure Recommendation
Offer Clarity Fix
Landing Page Improvement Brief
Compliance Brain Bias
Default question:
What claim, risk, platform, legal, safety, or evidence issue must be controlled?
Compliance Brain owns:
Claims safety
Evidence requirements
Risk classification
Platform policy
Legal wording caution
Regulated claims
Approval gates
Ad and content compliance support
Compliance Brain does not own:
Content creation direction
Campaign testing strategy
Market research verdicts
Financial scaling decisions
Automation execution
Core output examples:
Claims Risk Review
Evidence Requirement Note
Platform Policy Warning
Compliance Approval Gate
Safe Wording Recommendation
Data Brain Bias
Default question:
Can the measurement, event, attribution, and reporting be trusted?
Data Brain owns:
Measurement integrity
Event quality
Attribution
Analytics setup
Data layer logic
Reporting reliability
Dashboard data correctness
Source alignment
Data Brain does not own:
Campaign strategy
Content production
Market research verdicts
Finance scaling decision
Automation execution
Core output examples:
Measurement Integrity Review
Event Tracking Plan
Attribution Reliability Check
Data Quality Signal
Reporting Confidence Summary
Finance Brain Bias
Default question:
Is this worth funding, scaling, pausing, protecting, or reducing exposure to?
Finance Brain owns:
Budget
Capital allocation
Downside risk
CAC and LTV interpretation
Profitability
Scaling safety
Cashflow pressure
Financial exposure
Finance Brain does not own:
Creative testing
Content production
Research discovery
Automation execution
Compliance policy wording
Core output examples:
Budget Decision
Scaling Readiness Review
Capital Allocation Recommendation
Downside Risk Note
Profitability Review
CAC / LTV Signal Summary
Operations Brain Bias
Default question:
How does this get executed reliably, in the right order, with clear ownership and minimal bottlenecks?
Operations Brain owns:
Execution sequence
Workflow stability
Ownership
Task handoff
Delivery timing
Bottleneck control
Operating rhythm
Operations Brain does not own:
Research verdicts
Content strategy
Ad testing
Automation logic
Finance approval
Core output examples:
Execution Plan
Operating Checklist
Task Handoff
Bottleneck Review
Workflow Stability Note
Automation Brain Bias
Default question:
Can this run safely, predictably, repeatedly, and with human override?
Automation Brain owns:
Trigger logic
Workflow automation
Failure handling
Monitoring
Human override
Reliability
Maintainability
Automation Brain does not own:
Manual process definition before stability
Content strategy
Research truth
Finance approval
Campaign decisions
Core output examples:
Automation Readiness Review
Trigger Logic Specification
Failure Handling Plan
Human Override Rule
Monitoring Requirement
HeadOffice Bias
Default question:
Does this serve the system direction, maintain control, and keep the Brains aligned?
HeadOffice owns:
System control
Governance
Priority
Decision authority
Cross-brain alignment
System-level standards
Change control
M handoff protection
HeadOffice does not own:
Every specialist output
Replacing specialist Brain judgement
Turning every Brain into a dashboard
Core output examples:
Decision Record
Governance Rule
System Change Log
Brain Build Priority
Cross-Brain Alignment Note
M Handoff Standard
AIBS Brain Bias
Default question:
What client AI system, service package, client outcome, or delivery asset does this support?
AIBS Brain owns:
Client AI systems
AIOS service packaging
AI automation offers
Client diagnostics
Client delivery structure
Business automation opportunity mapping
AIBS sales-service alignment
AIBS Brain does not own:
MWMS internal Brain governance
General content production
Research Brain evidence ownership
Ads campaign execution
Core output examples:
AIOS Service Package
Client Diagnostic Framework
Automation Audit
Client Delivery Map
AI System Build Brief
Strategy Brain Bias
Default question:
What is the positioning, promise, narrative, differentiation, or strategic direction?
Strategy Brain owns:
Positioning
Narrative
Differentiation
Promise
Market stance
Strategic direction
Transformation story
Strategy Brain does not own:
Execution workflow
Content production details
Paid ad testing
Measurement infrastructure
Automation execution
Core output examples:
Positioning Framework
Promise Statement
Differentiation Map
Narrative Strategy
Strategic Direction Note
UX Brain Bias
Default question:
Can the user understand, navigate, interact, and complete the task easily?
UX Brain owns:
Usability
Navigation
Cognitive load
Interaction clarity
Workflow discoverability
Mental model alignment
Mobile interaction
UX Brain does not own:
Content strategy as a whole
Research evidence ownership
Ad testing
Finance decisions
Automation execution
Core output examples:
UX Friction Review
Navigation Clarity Review
Cognitive Load Reduction Recommendation
Workflow Discoverability Review
First Click Test Summary
Product Brain Bias
Default question:
What feature, package, launch path, or product value decision is needed?
Product Brain owns:
Feature value
Packaging
Product readiness
Launch fit
User value delivery
Product feedback integration
Product evolution
Product Brain does not own:
Content creation
Paid traffic testing
Research evidence ownership
Finance approval
Automation execution
Core output examples:
Feature Prioritisation Note
Product Readiness Review
Launch Fit Review
Packaging Recommendation
Product Feedback Summary
Offer Brain Bias
Default question:
What is being sold, why should someone buy it, and how is the value structured?
Offer Brain owns:
Offer structure
Value proposition
Pricing logic
Risk reversal
Audience fit
Offer readiness
Buying reason
Offer Brain does not own:
Content production as a full workflow
Campaign execution
Research evidence ownership
Measurement infrastructure
Automation execution
Core output examples:
Offer Structure
Value Proposition
Pricing Logic
Risk Reversal Recommendation
Offer Readiness Review
Sales Brain Bias
Default question:
What conversation, follow-up, objection handling, or closing path is needed?
Sales Brain owns:
Sales conversations
Lead follow-up
Objection handling
Acquisition path
Closing support
Sales enablement
Relationship-led selling
Sales Brain does not own:
Paid ad testing
Content production as a whole
Finance approval
Research evidence ownership
Automation execution
Core output examples:
Sales Call Framework
Follow-Up Sequence
Objection Handling Map
Lead Acquisition Flow
Closing Path Recommendation
Customer Brain Bias
Default question:
What customer state, lifecycle stage, retention risk, loyalty path, or relationship opportunity exists?
Customer Brain owns:
Retention
Customer state
Lifecycle
Loyalty
Segmentation
Relationship continuity
Post-purchase behaviour
Churn signals
Customer Brain does not own:
Initial market research
Content production as a whole
Paid ad execution
Finance approval
Automation execution
Core output examples:
Customer State Review
Retention Signal
Lifecycle Recommendation
Segmentation Note
Churn Risk Review
Relationship Continuity Plan
Risk Brain Bias
Default question:
What exposure, fragility, dependency, or escalation risk exists?
Risk Brain owns:
Exposure
Fragility
Concentration risk
Dependency risk
Risk classification
Risk escalation
System vulnerability
Risk Brain does not own:
General governance
Content production
Campaign decisions
Finance allocation unless risk-specific
Automation execution
Core output examples:
Risk Classification
Dependency Exposure Review
Concentration Risk Note
Fragility Signal
Escalation Recommendation
Cross-Brain Input Rule
Brains can use each other’s outputs.
But the receiving Brain must transform the input through its own department bias.
Examples:
Research Brain gives evidence to Content Brain.
Content Brain turns that evidence into content assets.
Data Brain gives metrics to Ads Brain.
Ads Brain turns those metrics into campaign decisions.
Compliance Brain gives risk notes to Content Brain.
Content Brain adjusts wording or approval status without becoming Compliance Brain.
Finance Brain gives budget limits to Ads Brain.
Ads Brain changes testing scale without becoming Finance Brain.
HeadOffice gives priority direction to all Brains.
Each Brain executes within its own department role.
Wrong-Brain Drift Warning Signs
A Brain may be drifting if:
Its UI looks like another Brain’s UI.
Its main screen is mostly records, logs, or evidence when its job is output production.
Its main output is a dashboard when its job is action.
Its build keeps expanding into useful support layers instead of its core surface.
Its handoff does not clearly state the Brain’s department job.
Its pages sound generic instead of department-specific.
Its output could belong to any Brain.
Its build relies on M guessing the real intent.
Its support layer becomes more important than its core purpose.
Core Surface Rule
Every Brain must have a clear core surface.
Support layers are allowed, but only when they help the core surface.
Examples:
Content Brain core surface:
Output Style Selector
Content Asset Brief Screen
Refresh Plan Output
Publishing Readiness Output
Repurposing Output
Affiliate Funnel Support Output
Content Brain support layer:
Site Intelligence Records
Research Brain core surface:
Evidence and Research Verdict Layer
Market Signal Interpretation
Source Quality Review
Research Brain support layer:
Intake logs
Source archive
Ads Brain core surface:
Campaign Testing Decision Layer
Creative Testing Layer
Hook and Audience Testing Layer
Ads Brain support layer:
Performance history
Creative archive
Data Brain core surface:
Measurement Integrity Layer
Attribution Reliability Layer
Data Brain support layer:
Raw data references
Event logs
HeadOffice core surface:
System Governance
Priority Control
Brain Alignment
Change Control
HeadOffice support layer:
Status boards
Change logs
Operating notes
Mandatory Use
This Department Bias Map must be used with:
MWMS Brain Identity Gate
MWMS Core Surface Versus Support Layer Rule
MWMS Brain Build Preflight Checklist
MWMS Brain Handoff Protection Standard
No Brain build should proceed without checking this page when there is any risk of cross-brain drift.
Operating Principle
Each Brain must think like its department.
Each Brain may receive inputs from other departments.
Each Brain must produce outputs that match its own department responsibility.
Final Rule
The MWMS Department Bias Map is the reference used to prevent Brains from becoming copies of each other.
The system only works if each Brain stays distinct.
No Brain is allowed to become another Brain by accident.