Document Type: Canon
Status: Canon
Authority: HeadOffice
Applies To: All MWMS Brains
Parent: MWMS Canon
Version: v1.1
Last Reviewed: 2026-03-15
Purpose
This document defines the formal authority hierarchy operating across MWMS.
Its purpose is to ensure that authority, execution, and enforcement remain structurally separated so the ecosystem can operate with discipline and without ambiguity.
This document exists to clarify:
• who holds final authority
• which Brains make decisions
• which layers execute work
• how enforcement interacts with execution
• how capital movement is controlled
Authority clarity prevents structural drift.
Scope
This canon applies to:
• all MWMS Brains
• governance, decision, enforcement, and execution layers
• authority flow across the ecosystem
• capital movement approval logic
• override and block relationships between system layers
This document governs authority structure across MWMS.
It does not govern:
• detailed Brain operating procedures by themselves
• task routing by itself
• statistical validation rules by themselves
• page naming by itself
• UI behaviour by itself
• implementation details of executors or plugins by themselves
Those remain governed by the relevant canons, standards, protocols, and technical documents.
Definition / Rules
Governance Hierarchy
MWMS operates under a strict layered authority model.
Authority flows top-down.
Execution flows bottom-up.
Enforcement operates horizontally.
Authority Layers
HeadOffice (Supreme Governance)
Role:
• constitutional authority
• Canon control
• capital scaling approval
• override power
Limitations:
• does not execute
• does not run campaigns
HeadOffice is final authority.
Affiliate Brain (Capital Allocation Engine)
Role:
• offer research
• structural scoring (Velocity)
• capital verdict (YES / NO)
• testing definition
Limitations:
• cannot scale without HeadOffice
• cannot override SIT
• cannot alter Canon
Affiliate controls structured decision, not governance.
SIT Brain (System Integrity & Testing)
Role:
• drift detection
• enforcement
• block authority
• structural verification
Limitations:
• cannot approve execution
• cannot scale campaigns
• cannot create strategy
• cannot alter Canon
SIT may block but never approve.
Operations Brain (Execution Layer)
Role:
• executes approved actions
• deploys campaigns
• implements approved systems
Limitations:
• no governance authority
• cannot override any Brain
• cannot modify Canon
• cannot move capital without approval
Operations executes only.
Authority Flow Model
HeadOffice
↓
Affiliate Brain (Decision)
↓
Operations (Execution)
SIT operates horizontally across all layers as enforcement.
Capital Movement Rule
Capital may only move if:
• Affiliate Velocity = YES
• Canon Gates satisfied
• Testing defined
• HeadOffice scaling approval granted
If any condition fails, capital does not move.
No exceptions.
Override Rules
• HeadOffice may override any Brain
• SIT may block any execution
• Affiliate may not override SIT
• Operations may override no one
Authority is not shared.
Final Rule
Where authority is unclear, execution must pause.
Unclear authority is itself a governance risk.
Drift Protection
The system must prevent:
• execution occurring without clear authority sequence
• decision layers being confused with governance layers
• enforcement layers being treated as approval layers
• capital moving without all required authority conditions
• lower layers assuming override power they do not possess
• structural ambiguity being tolerated during execution
Authority must remain explicit, top-down, and enforceable.
Architectural Intent
MWMS Authority Structure exists to preserve clean separation between governance, decision, enforcement, and execution inside the MWMS ecosystem.
Its role is to ensure that MWMS can scale as a governed system without collapsing into shared authority, informal overrides, or uncontrolled execution.
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 governance hierarchy, authority layers, authority flow model, capital movement rule, and override rules. Added Document Type, Parent, Version, Purpose / Scope / Definition / Rules structure, Final Rule, Drift Protection, and Architectural Intent sections.
Version: v1.0
Date: 2026-02-23
Author: HeadOffice
Change: Initial creation of MWMS Authority Structure defining layered authority flow, execution flow, enforcement positioning, capital movement conditions, and override rules.
END – MWMS AUTHORITY STRUCTURE v1.1