Document Type: Canon
Status: Canon
Version: v1.2
Authority: HeadOffice
Applies To: Entire MWMS Ecosystem
Parent: MWMS Canon
Last Reviewed: 2026-03-15
Purpose
This document defines the structural authority order of all canon documents within the MWMS ecosystem.
As the number of canon documents increases, it becomes essential to clearly define which documents override others in the event of conflict.
This hierarchy prevents governance ambiguity and ensures that all rules operate within a consistent chain of authority.
The Canon Hierarchy Map acts as the structural authority diagram for the MWMS constitution.
Scope
This canon applies to:
• all MWMS canon documents
• conflict resolution between governance documents
• authority ordering across the MWMS ecosystem
• interpretation of precedence when multiple rules appear to conflict
• structural governance of future canon expansion
This document governs canon precedence and override logic.
It does not govern:
• operational workflow design
• page-level implementation details
• plugin code behaviour
• specific campaign decisions
• architecture document content beyond canon compliance
Architecture, protocol, framework, specification, standard, and reference documents must all comply with canon authority ordering, but they are not elevated above canon by this map.
Definition / Rules
Core Principle
Canon operates in layers of authority.
Higher layers define foundational rules.
Lower layers must operate within the boundaries defined by the layers above them.
If a conflict occurs between two canon documents, the document higher in the hierarchy prevails.
Canon Authority Levels
The MWMS canon operates across five authority levels.
Level 1 – Constitutional Layer
This layer defines the foundational identity, philosophy, and operating model of MWMS.
Documents in this layer define the long-term structure and purpose of the ecosystem.
Examples include:
• MWMS Constitution
• MWMS Canon Index
• How to Start a Session – MWMS Operating Guide
These documents establish the philosophical and structural foundation of MWMS.
No lower-level document may contradict this layer.
Level 2 – Governance Layer
This layer defines how authority is distributed and how decisions are controlled within the system.
These documents define organisational authority and governance enforcement.
Examples include:
• MWMS Authority Structure
• Canon Editing Protocol
• AI Governance Framework
These rules govern how the ecosystem maintains discipline and decision control.
Level 3 – Organisational Layer
This layer defines the structure of the MWMS organisation.
It establishes how Brains exist, interact, and evolve.
Examples include:
• MWMS Brain Registry
• MWMS Brain Lifecycle
• MWMS Brain Creation Protocol
• MWMS Brain Operating Contract
These documents define how the organisation itself is structured.
Level 4 – Operational Governance Layer
This layer defines the operational coordination rules used by Brains and AI systems.
Examples include:
• MWMS Brain Request System
• MWMS Brain Interaction Protocol
• MWMS Decision Record System
These documents ensure that operational actions follow structured processes.
Level 5 – Technical Governance Layer
This layer defines the technical infrastructure standards required for MWMS systems.
Examples include:
• MWMS Supabase Task Schema Standard
These documents ensure the technical systems supporting MWMS remain consistent and interoperable.
Architecture Documents vs Canon
MWMS contains many documents that describe system architecture or operational workflows.
Examples include:
• MWMS Affiliate Revenue Engine
• Offer Intelligence Page Template
• Affiliate Opportunity Pipeline
• Velocity Decision Engine
• Offer Graveyard / Rejected Offers Intelligence
These documents describe operational systems.
They are governed by canon but are not themselves canon authority documents.
Architecture documents must comply with canon.
Canon always overrides architecture.
Conflict Resolution Rule
If two documents conflict, the hierarchy resolves the conflict automatically.
Examples:
• if an operational protocol contradicts a governance rule, the governance rule prevails
• if a technical standard contradicts a constitutional principle, the constitutional principle prevails
This ensures consistent governance across the entire MWMS ecosystem.
Governance Enforcement
HeadOffice is responsible for enforcing the canon hierarchy.
SIT Brain may assist by detecting:
• structural conflicts
• rule violations
• document inconsistencies
However, final authority remains with HeadOffice and Human Executive Authority.
Mental Model
The MWMS canon operates like a constitutional government.
Constitutional Layer = Foundational law
Governance Layer = Government authority structure
Organisational Layer = Government departments
Operational Layer = Government procedures
Technical Layer = Infrastructure standards
This hierarchy ensures MWMS can grow without losing structural discipline.
Outcome
The Canon Hierarchy Map ensures that all MWMS governance documents operate within a clearly defined authority structure.
It prevents rule conflicts, maintains organisational clarity, and protects the long-term stability of the ecosystem.
As MWMS grows, this hierarchy allows new canon documents to be added without creating governance ambiguity.
Drift Protection
The system must prevent:
• lower-layer documents overriding higher-layer canon
• architecture pages being treated as constitutional authority
• governance ambiguity caused by missing precedence rules
• conflicting canon pages being interpreted without hierarchy reference
• uncontrolled canon expansion without authority placement
All canon interpretation must respect hierarchy order.
Final Rule
If a canon document cannot be placed clearly within the hierarchy, its authority is not yet safe to rely on.
Placement must be explicit before conflict resolution can be trusted.
Architectural Intent
The MWMS Canon Hierarchy Map exists to preserve a clear constitutional order across the growing MWMS governance system.
Its role is to ensure that as new canon pages are added, they enter a known authority structure so conflicts can be resolved consistently and the ecosystem can expand without losing governance coherence.
Change Log
Version: v1.2
Date: 2026-03-15
Author: MWMS HeadOffice
Change: Standardised the page fully to the locked cleanup format for this pass. Preserved the original five-level hierarchy, conflict-resolution rule, architecture-versus-canon distinction, governance enforcement logic, mental model, intended outcome, and drift-protection logic. Added a dedicated Final Rule section and updated the review date.
Version: v1.1
Date: 2026-03-14
Author: MWMS HeadOffice
Change: Rebuilt page to align with MWMS document standards. Added standardised document header, introduced Purpose / Scope / Definition / Rules structure, added Parent field, normalised formatting, and preserved the original five-level canon hierarchy and conflict-resolution logic.
Version: v1.0
Date: 2026-03-06
Author: MWMS HeadOffice
Change: Initial creation of the MWMS Canon Hierarchy Map. Introduced a five-level authority hierarchy for all canon documents to clarify precedence and prevent governance conflicts as the MWMS canon expands.
END – MWMS CANON HIERARCHY MAP v1.2