Document Type: Protocol
Status: Active
Version: v1.1
Authority: Operations Brain
Parent: Operations Brain
Applies To: Entire MWMS Ecosystem
Last Reviewed: 2026-03-15
Purpose
The Operations Brain acts as the central routing layer for MWMS.
All new requests, ideas, opportunities, system issues, and governance questions should first pass through Operations Brain before being directed to the appropriate Brain.
This ensures:
• disciplined system flow
• proper Brain utilisation
• reduced system drift
• clear responsibility boundaries
• controlled decision pathways
Operations functions as the traffic-control layer of the MWMS ecosystem.
Scope
This protocol applies to:
• incoming requests across the MWMS ecosystem
• routing of ideas, opportunities, system issues, governance questions, and coordination tasks
• manual routing decisions made through Operations Brain
• initial classification before specialised Brain work begins
• future automation of request classification and routing
This document governs how Operations Brain classifies and routes new incoming work.
It does not govern:
• specialised analysis performed by target Brains
• canon modification by itself
• capital approval by itself
• experiment validation by itself
• SIT enforcement by itself
• final strategic decisions by themselves
Those remain governed by HeadOffice, Affiliate Brain, Experimentation Brain, SIT Brain, Finance Brain, and the relevant Brain-specific documents.
Definition / Rules
Core Principle
No new request should directly enter a specialised Brain.
All incoming activity first passes through Operations Brain routing logic.
Operations determines the correct destination and routes the request accordingly.
This prevents:
• misclassification
• duplicated work
• governance bypass
• structural drift
Routing Structure
The following routing structure defines how incoming requests are classified and directed.
1 – Opportunity / Offer Evaluation
Route To:
• Affiliate Brain
Examples:
• ClickBank product
• affiliate offer discovery
• vendor funnel review
• VSL evaluation
• affiliate program analysis
• revenue opportunity review
Affiliate Brain performs structured opportunity evaluation before any testing decision is considered.
2 – Market Insight / Knowledge Intake
Route To:
• Research Brain
Examples:
• newsletter insights
• AI tool discoveries
• industry trends
• economic signals
• competitor observations
• platform changes
Research Brain captures insights and converts them into structured system intelligence.
3 – Experiment Proposal
Route To:
• Experimentation Brain
Examples:
• A/B testing ideas
• creative-concept testing
• hook experiments
• landing-page variations
• marketing-angle experiments
Experimentation Brain governs the testing framework and ensures structured experimentation discipline.
4 – System Error / Integrity Issue
Route To:
• SIT Brain
Examples:
• plugin errors
• architectural conflicts
• system drift
• data inconsistencies
• governance violations
• system integrity alerts
SIT Brain enforces structural integrity and protects the MWMS architecture.
5 – Governance / Structural Decisions
Route To:
• HeadOffice
Examples:
• canon modifications
• architecture changes
• Brain authority adjustments
• ecosystem structural decisions
• policy clarification
HeadOffice holds final authority over governance and structural design.
6 – Operational Task / Process Coordination
Route To:
• Operations Brain
Examples:
• workflow improvements
• process design
• system coordination tasks
• execution support
• routing clarification
Operations Brain ensures smooth coordination between specialised Brains.
Routing Decision Flow
Incoming request
↓
Operations Brain
↓
Request classification
↓
Request routed to correct Brain
↓
Brain performs specialised function
Boundaries
Operations Brain does not:
• perform affiliate analysis
• conduct experiments
• modify canon
• override SIT enforcement
• make strategic decisions
Operations only routes and coordinates.
Specialised Brains perform the actual work.
Authority
Authority Type: Coordination
Operations Brain may:
• classify requests
• route tasks
• coordinate workflow
• escalate requests
Operations Brain may not:
• override governance
• bypass SIT enforcement
• approve capital deployment
• change system architecture
Future Development
Future MWMS upgrades may introduce an AI Operations Coordinator capable of automatically classifying and routing requests based on input type.
Current implementation remains manual routing with defined protocol.
Final Rule
If routing is unclear, the request must not be guessed into a specialised Brain.
Unclear routing must be escalated or clarified through Operations discipline first.
Drift Protection
The system must prevent:
• incoming requests bypassing Operations Brain routing
• specialised Brains receiving work outside their intended scope
• governance matters being misrouted into operational Brains
• integrity issues being treated as normal execution tasks
• opportunity analysis being confused with experimentation or governance work
• manual convenience weakening routing discipline
Routing clarity must come before execution speed.
Architectural Intent
MWMS Request Routing Map exists to make Operations Brain the controlled intake layer for the MWMS ecosystem.
Its role is to ensure that new activity enters the system through one disciplined routing surface so specialised Brains can remain focused, authority boundaries remain clear, and ecosystem drift is reduced over time.
Change Log
Version: v1.1
Date: 2026-03-15
Author: MWMS HeadOffice / Operations Brain
Change: Rebuilt page to align with the locked MWMS document standard for this cleanup pass. Preserved the original purpose, core principle, six routing categories, routing decision flow, boundaries, authority model, and future-development note. Added Document Type, Scope, Definition / Rules structure, Final Rule, Drift Protection, and Architectural Intent sections. Normalised title to the standard MWMS title format.
Version: v1.0
Date: 2026-03-11
Author: Operations Brain
Change: Initial creation of MWMS Request Routing Map defining Operations Brain as the central routing layer for incoming requests across the MWMS ecosystem.
END – MWMS REQUEST ROUTING MAP v1.1