Document Type: Canon
Status: Canon
Version: v1.1
Authority: HeadOffice
Parent: Governance
Applies To: All MWMS Brains, AI Systems, Plugins, and Execution Layers
Last Reviewed: 2026-03-15
Purpose
The MWMS System Layers Map defines the architectural layers of the MWMS ecosystem.
It clarifies how different system components interact and prevents architectural drift as the platform expands.
This page provides the structural blueprint for:
• Brain hierarchy
• decision flow
• execution boundaries
• governance oversight
This document describes structure.
It does not control execution.
Scope
This canon applies to:
• all MWMS Brains
• all AI systems
• all plugins
• all execution layers
• structural placement of system components within the ecosystem
• decision-flow interpretation across the layered model
This document governs the layer model used to classify and separate MWMS system components.
It does not govern:
• detailed Brain operating procedures by themselves
• direct task-routing rules by themselves
• plugin implementation details by themselves
• campaign execution by itself
• capital approval thresholds by themselves
• page-level UI design by itself
Those remain governed by the relevant canons, protocols, standards, and architecture pages.
Definition / Rules
Layer 1 – Constitutional Governance
This is the highest authority layer of MWMS.
It defines the rules that govern the entire system.
Components include:
• MWMS Constitution
• MWMS Canon
• MWMS Authority Structure
• MWMS Brain Contract
• MWMS Agentic SDLC Doctrine
This layer defines:
• authority boundaries
• system governance rules
• AI operational constraints
• canonical structure requirements
No Brain or execution system may override this layer.
Layer 2 – Governance Brains
Governance Brains enforce discipline across the system.
They do not run operations.
They protect structural integrity.
Brains in this layer include:
• SIT Brain
• Finance Brain
• Experimentation Brain
Responsibilities:
• system integrity monitoring
• statistical discipline
• capital protection
• scaling eligibility enforcement
These Brains act as system regulators.
Layer 3 – Intelligence Layer
This layer gathers, organizes, and validates information.
The primary component is:
• Research Brain
Research Brain responsibilities include:
• insight collection
• evidence classification
• customer intelligence
• competitive intelligence
• pattern detection
This layer feeds validated intelligence to decision-making Brains.
Layer 4 – Strategic Direction Layer
This layer defines long-term system direction.
Primary component:
• Strategy Brain
Responsibilities include:
• market positioning
• strategic planning
• mechanism development
• opportunity direction
Strategy Brain determines where the system should move.
Layer 5 – Execution Brains
Execution Brains operate the business.
They generate revenue and deploy products.
Brains in this layer include:
• Affiliate Brain
• PPL Brain
• AI Business Systems Brain (AIBS)
Responsibilities include:
• market testing
• offer deployment
• lead generation
• AI solution deployment
These Brains convert intelligence into action.
Layer 6 – Operational Infrastructure
This layer supports execution but does not make strategic decisions.
Components include:
• Operations Brain
• Dev Console
Responsibilities include:
• workflow management
• deployment coordination
• technical infrastructure support
These systems enable operational efficiency.
System Decision Flow
MWMS decisions follow a structured path.
Research Brain produces intelligence.
Strategy Brain interprets long-term direction.
Execution Brains test opportunities.
Experimentation Brain validates statistical outcomes.
Finance Brain validates capital discipline.
HeadOffice makes final scaling decisions.
SIT Brain monitors the entire process for integrity.
Decision pipeline:
Research
↓
Strategy
↓
Execution
↓
Experimentation
↓
Finance
↓
HeadOffice
SIT monitors all layers.
Structural Discipline Rule
Each Brain must operate only within its designated system layer.
Execution Brains may not override governance rules.
Governance Brains may not execute operations.
Infrastructure systems may not make strategic decisions.
This separation prevents systemic instability.
Canonical Principle
MWMS architecture follows one guiding principle:
Structure precedes scale.
The layered model ensures:
• governance remains stable
• execution remains flexible
• intelligence accumulates over time
Final Rule
If a Brain, tool, or system element cannot be placed clearly within one layer, its role is structurally unclear and must be resolved before further expansion.
Layer ambiguity is governance risk.
Drift Protection
The system must prevent:
• Brains operating across multiple layers without explicit authority
• governance systems being treated as execution systems
• infrastructure tools being treated as strategic authorities
• execution layers bypassing constitutional or governance layers
• architectural growth occurring without clear layer placement
• decision-flow confusion caused by blurred structural boundaries
All system elements must remain layer-legible.
Architectural Intent
MWMS System Layers Map exists to preserve a clear structural model for the entire MWMS ecosystem.
Its role is to make governance, regulation, intelligence, strategy, execution, and infrastructure visibly distinct so the platform can expand without collapsing into architectural confusion or authority drift.
Change Log
Version: v1.1
Date: 2026-03-15
Author: HeadOffice
Change: Rebuilt page to align with the locked MWMS document standard for this cleanup pass. Preserved the original six-layer model, system decision flow, structural discipline rule, and canonical principle. Added Document Type, Scope, Definition / Rules structure, Final Rule, Drift Protection, and Architectural Intent sections.
Version: v1.0
Date: 2026-03-09
Author: HeadOffice
Change: Initial creation of MWMS System Layers Map defining the architectural layers of the MWMS ecosystem.
END – MWMS SYSTEM LAYERS MAP v1.1