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 Architecture Registry is the master structural index of the MWMS ecosystem.
It exists to prevent architectural drift as the system expands.
This page defines:
• system layers
• Brain placement
• authority boundaries
• structural ownership
All new pages and Brains must align with this registry.
If a page does not clearly belong to a defined layer, it may not be promoted into Canon.
Scope
This canon applies to:
• all MWMS system layers
• all Brains and supporting systems
• placement of pages and systems inside the structural architecture
• authority separation across governance, regulation, intelligence, strategy, execution, and infrastructure
• promotion checks for new architecture-altering pages
This document governs structural placement and architectural classification across MWMS.
It does not govern:
• detailed Brain operating rules by themselves
• page naming by itself
• task execution by itself
• financial approvals by themselves
• statistical rules by themselves
• UI layout by itself
Those remain governed by the relevant canons, standards, protocols, and Brain-specific pages.
Definition / Rules
Layer 1 – Constitutional Governance
This layer defines the rules governing the entire MWMS system.
Pages:
• MWMS Constitution
• MWMS Canon
• MWMS Authority Structure
• Decision Authority Matrix
• Brain Contract
• Canon Editing Protocol
• AI Governance Rules
• MWMS System Layers Map
• MWMS Architecture Registry
Role:
Define structure and governance.
This layer never executes business operations.
Layer 2 – System Regulation (Control Brains)
These Brains regulate system stability.
They enforce discipline across the ecosystem.
Brains:
• SIT Brain
• Finance Brain
• Experimentation Brain
Responsibilities:
• structural integrity enforcement
• capital protection
• statistical discipline
• scaling validation
These Brains regulate execution but do not perform it.
Layer 3 – Intelligence Layer
This layer gathers structured intelligence.
Primary Brain:
• Research Brain
Sub-systems:
• Customer Insight Engine
• Journey Signals
• Problem Intelligence
• Retention Intelligence
• Competitive Intelligence
Responsibilities:
• evidence classification
• insight logging
• pattern detection
• market intelligence
This layer feeds validated intelligence to strategy and execution.
Layer 4 – Strategic Direction Layer
This layer defines long-term direction.
Primary Brain:
• Strategy Brain
Supporting frameworks:
• Strategic Vision & Horizon
• Cognitive Influence Framework
Responsibilities:
• market direction
• strategic planning
• mechanism development
• opportunity identification
This layer defines where MWMS should move.
Layer 5 – Execution Layer
Execution Brains operate the business.
Brains:
• Affiliate Brain
• PPL Brain
• AI Business Systems Brain (AIBS)
Responsibilities:
• market testing
• offer deployment
• traffic acquisition
• lead generation
• AI system deployment
These Brains generate revenue.
Layer 6 – Operational Infrastructure
Infrastructure systems support execution.
They do not make strategic decisions.
Systems:
• Operations Brain
• Dev Console
Responsibilities:
• workflow management
• deployment coordination
• infrastructure support
Structural Governance Rule
Every MWMS page must belong to exactly one layer.
Pages may reference other layers but may not duplicate authority.
If a page overlaps with an existing authority page, the existing page must be updated instead of creating a new one.
Page Promotion Rule
Before adding any new Canon page the following questions must be answered:
- Which system layer does this page belong to?
- Which Brain owns the page?
- Does a similar page already exist?
If a similar page exists, the existing page must be updated instead.
Structural Integrity Principle
The MWMS system must maintain clear separation between:
• Governance
• Regulation
• Intelligence
• Strategy
• Execution
• Infrastructure
This separation prevents system instability as the ecosystem expands.
Final Rule
If a page, Brain, or system element cannot be placed cleanly inside this registry, its structural role is unclear and it should not be promoted until that ambiguity is resolved.
Drift Protection
The system must prevent:
• pages being created without a clear architectural layer
• Brains expanding into adjacent layers without approval
• duplicate authority emerging through new documents
• execution systems being mistaken for governance systems
• strategic pages being treated as regulatory controls
• infrastructure tools being treated as authority surfaces
Architectural clarity must be preserved before expansion is allowed.
Architectural Intent
The MWMS Architecture Registry exists to keep the MWMS ecosystem structurally legible as it grows.
Its role is to provide one canonical map of where system elements belong so new pages, Brains, tools, and execution layers can be added without blurring authority, collapsing layers, or creating architectural 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 layer model, placement logic, governance rule, page promotion rule, and structural integrity 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 Architecture Registry as the master structural index of the MWMS ecosystem.
END – MWMS ARCHITECTURE REGISTRY v1.1