Document Type: Protocol
Status: Structural
Version: v1.2
Authority: HeadOffice
Applies To: All MWMS Brains, AI Employees, Plugins, and Workflow Systems
Parent: Operations Brain
Last Reviewed: 2026-04-16
Purpose
The MWMS Request Routing Map defines how all requests entering the MWMS ecosystem are classified and directed to the correct Brain or system component.
Routing discipline ensures:
correct authority handling
consistent interpretation
stable workflow coordination
reduction of duplicated effort
clear ownership of decisions
structural consistency across the ecosystem
Requests must never bypass structural routing logic.
Routing clarity protects system reliability.
Scope
This protocol governs:
routing of internal requests
routing of AI-generated requests
routing of human-generated requests
routing of external change signals
routing of improvement signals
routing between Brains
routing between system layers
routing of structured decision support requests
routing of structural update requests
This protocol applies to:
HeadOffice
all Brains
all AI Employees
all workflow automations
all decision-support interactions
This protocol does not govern:
decision authority inside each Brain
financial approvals by themselves
statistical validation by itself
governance law creation by itself
Those remain governed by specialist Brains.
Operations Brain governs routing discipline.
Core Principle
Requests must be interpreted once and routed correctly the first time.
Incorrect routing produces:
duplicate interpretation
conflicting outputs
delayed decisions
structural inconsistency
workflow instability
Correct routing improves ecosystem clarity.
Request Entry Points
Requests may originate from:
HeadOffice
AI Employees
Human operators
automation workflows
external change signals
course absorption outputs
research findings
execution feedback signals
Kaizen improvement signals
All requests must pass through structured routing logic.
Routing Classification Structure
Requests are classified into one of the following routing categories:
Governance requests
Regulation requests
Intelligence requests
Strategy requests
Execution requests
Infrastructure requests
Change intelligence requests
Improvement requests
Correct classification ensures correct authority handling.
Governance Routing
Route to HeadOffice when request affects:
system structure
brain authority boundaries
governance rules
cross-brain coordination
system architecture
strategic direction
AI governance
creation of new Brains
changes to Canon
HeadOffice maintains structural authority.
Regulation Routing
Route to Regulation Layer when request affects:
risk exposure
capital safety
compliance requirements
statistical validity
scaling safety
dependency fragility
routing integrity
measurement reliability
Destination Brains may include:
SIT Brain
Finance Brain
Risk Brain
Compliance Brain
Experimentation Brain
Regulation Brains protect system stability.
Intelligence Routing
Route to Intelligence Layer when request affects:
market interpretation
behavioural interpretation
signal meaning
insight validation
pattern recognition
customer lifecycle understanding
data reliability
Destination Brains:
Research Brain
Customer Brain
Data Brain
Intelligence Brains interpret signals.
Strategy Routing
Route to Strategy Layer when request affects:
market direction
persuasion logic
value structure
positioning logic
mechanism clarity
pricing logic
belief architecture
offer logic
Destination Brains:
Strategy Brain
Creative Brain
Offer Brain
Strategy Brains define decision logic.
Execution Routing
Execution requests affect business operation outputs.
Execution layer Brains implement operational activity.
Affiliate Routing
Route when request affects:
opportunity identification
hook testing direction
market hypothesis generation
traffic opportunity selection
Destination:
Affiliate Brain
Ads Routing
Route when request affects:
creative testing
campaign structure
traffic experimentation
ad optimisation
Destination:
Ads Brain
Content Routing
Route when request affects:
topic structure
content production
content optimisation
content repurposing
authority building content
educational content structure
content signal feedback loops
Destination:
Content Brain
PPL Routing
Route when request affects:
lead capture
lead quality interpretation
lead qualification logic
lead routing structure
lead lifecycle continuity
Destination:
PPL Brain
Sales Routing
Route when request affects:
sales qualification logic
conversation structure
offer fit interpretation
expectation alignment
sales progression logic
closing structure
conversion readiness interpretation
Destination:
Sales Brain
Conversion Routing
Route when request affects:
decision environment structure
friction reduction
trust signals
information hierarchy
call-to-action clarity
conversion clarity
Destination:
Conversion Brain
Product Routing
Route when request affects:
product structure
feature prioritisation
capability definition
delivery structure
product evolution logic
product feedback integration
product stability
Destination:
Product Brain
Partnership Routing
Route when request affects:
external collaboration
distribution leverage
strategic alliances
creator partnerships
technology partnerships
referral partnerships
joint venture relationships
value exchange relationships
partner lifecycle structure
Destination:
Partnership Brain
AIBS Routing
Route when request affects:
AI employee deployment
system automation capability
business system architecture
AI workflow integration
AI employee capability structure
Destination:
AI Business Systems Brain
Infrastructure Routing
Infrastructure requests affect system execution environment.
Operations Routing
Route when request affects:
workflow structure
process stability
handoff continuity
documentation consistency
workflow clarity
execution reliability
dependency coordination
Destination:
Operations Brain
Automation Routing
Route when request affects:
workflow automation
trigger logic
integration orchestration
system execution sequencing
task automation
routing automation
event automation
Destination:
Automation Brain
Change Intelligence Routing (NEW)
Route first to HeadOffice External Change Intelligence when request originates from:
law changes
platform policy changes
technology changes
AI capability changes
measurement environment changes
regulatory developments
vendor capability changes
infrastructure evolution
market structural change signals
HeadOffice performs triage before routing to specialist Brain.
Possible routing destinations:
Compliance Brain
Risk Brain
Research Brain
Finance Brain
Operations Brain
Automation Brain
Execution Brain
HeadOffice Strategic Review
External change must not bypass HeadOffice triage.
Kaizen Routing (NEW)
Route to Kaizen loop when request indicates:
repeated friction
repeated confusion
duplicated frameworks
unclear wording
unnecessary complexity
inefficient workflow
signal ambiguity
structural inefficiency
Kaizen improves system clarity across time.
Kaizen outputs may produce:
framework refinement
protocol clarification
routing improvement
structure simplification
naming improvement
duplication removal
Kaizen does not override authority structure.
Routing Flow Structure
Request received
↓
Request classified
↓
Routing category determined
↓
Brain authority identified
↓
Request routed to specialist Brain
↓
Interpretation returned
↓
HeadOffice visibility maintained
↓
Learning signal captured
Structured routing improves ecosystem reliability.
Routing Boundaries
Requests must not:
bypass HeadOffice governance layer
bypass Regulation Brains
bypass Experimentation validation
bypass Finance guardrails
bypass authority boundaries
bypass lifecycle structure
violate structural discipline
Violations trigger SIT escalation.
Cross Brain Routing Visibility
Routing must remain traceable across system logs.
HeadOffice must retain visibility of:
routing origin
routing destination
routing reason
routing outcome
Traceability improves system reliability.
Architectural Intent
The MWMS Request Routing Map ensures requests move through the ecosystem in a structured and predictable manner.
Structured routing improves:
decision clarity
execution stability
system learning continuity
governance consistency
scaling durability
Routing discipline protects long-term ecosystem integrity.
Final Rule
Unstructured routing produces inconsistent decisions.
Inconsistent decisions reduce optimisation reliability.
Reduced optimisation reliability weakens scaling durability.
Routing discipline protects system stability.
Change Log
Version: v1.2
Date: 2026-04-16
Author: HeadOffice
Updated routing structure to include:
Content Brain
Product Brain
Sales Brain
Partnership Brain
Automation Brain
HeadOffice External Change Intelligence routing layer
Kaizen improvement routing loop
Clarified routing boundaries between:
Offer vs Product
Sales vs Conversion
Partnership vs Sales
Execution vs Infrastructure
Improved routing clarity across all MWMS system layers.