Document Type: Canon
Status: Canon
Authority: MWMS HeadOffice
Applies To: Entire MWMS ecosystem
Document ID: MWMS_CANON_INDEX
Parent: MWMS Canon
Version: v1.2
Last Reviewed: 2026-03-15
Purpose
The MWMS Canon Index is the master directory of all canonical governance documents within the MWMS ecosystem.
Its purpose is to provide:
• a single navigation point for all Canon documents
• clarity over which documents are authoritative
• visibility into the structural layers of the ecosystem
• a stable reference for developers, AI systems, and operators
Only documents listed in this index are recognised as active MWMS Canon.
Scope
This canon applies to:
• all recognised MWMS canon documents
• the structural organisation of Canon by governance layer
• distinction between Canon authority and subordinate architecture material
• ecosystem-wide reference for developers, operators, and AI systems
• preservation of a single authoritative Canon directory
This document governs the directory structure of MWMS Canon and how canonical material is grouped and referenced.
It does not govern:
• direct operational execution
• plugin implementation by itself
• Brain-specific task logic by itself
• non-canon draft material
• page naming rules by themselves
• authority precedence beyond the MWMS Canon Hierarchy Map
Those remain governed by the relevant canons, standards, protocols, and architecture documents.
Definition / Rules
Canon Philosophy
The MWMS Canon functions as the constitutional framework of the ecosystem.
It defines:
• authority
• governance
• operational rules
• system architecture
• development discipline
Build systems, automation, plugins, and workflows must operate within the boundaries defined by Canon.
Canon is upstream.
Implementation is downstream.
Canon Structure
The MWMS Canon is organised into several governance layers:
• Ecosystem Vision
• Governance & Authority
• System Architecture
• Operational Protocols
• Technical Standards
• Registry & Reference
Each layer defines a different aspect of the MWMS system.
Ecosystem Vision
These documents define the strategic purpose and long-term objectives of MWMS.
Documents:
How to Start a Session – MWMS Operating Guide
This document ensures every working session begins within the correct ecosystem context and operating discipline.
Governance & Authority
These documents define how authority operates within MWMS.
Documents:
MWMS Authority Structure
Defines the organisational hierarchy:
Humans → HeadOffice → Brains → AI Employees
This document clarifies decision authority and responsibility boundaries across the ecosystem.
System Architecture
These documents define the structural wiring of the MWMS ecosystem.
Documents:
MWMS – System Architecture
Defines how the technical layers interact:
Humans → WordPress → Supabase → Executors → Outputs
MWMS – Money Engine Diagram
Defines how MWMS generates and reinvests capital.
Traffic → Offers → Conversion → Profit → Reinvestment
These documents describe how value flows through the system.
Operational Protocols
These documents define the operational governance rules used across the MWMS ecosystem.
Documents:
MWMS – Brain Creation Protocol
Defines how new Brains are proposed, approved, and registered.
MWMS – Brain Lifecycle
Defines the lifecycle stages through which Brains evolve:
Creation → Operation → Evolution → Retirement
MWMS – Brain Operating Contract
Defines the operational boundaries and responsibilities of each Brain.
MWMS – Brain Request System
Defines how tasks are formally requested and routed between Brains.
MWMS – Brain Interaction Protocol
Defines how Brains communicate and collaborate across the system.
MWMS – Decision Record System
Defines how major decisions are documented and preserved within the ecosystem.
Technical Standards
These documents define the infrastructure standards required for MWMS.
Documents:
MWMS – Supabase Task Schema Standard
Defines the canonical database schema used by the MWMS task system.
This schema governs:
• brain requests
• tasks
• task events
• artifacts
• decision records
• lessons learned
These standards ensure that all system automation and integrations follow a unified technical architecture.
Registry & Reference
These documents maintain system inventory, documentation, and governance history.
Documents:
MWMS – Brain Registry
The official master record of all Brains operating within MWMS.
Canon Change Log
Records all approved changes made to Canon documents.
MWMS – Canon Index
The master directory of all canonical governance documents.
These documents ensure the system maintains traceable governance history and structural clarity.
Architecture & Intelligence Systems (Reference Layer)
These documents define architecture and intelligence systems used by MWMS.
These documents operate under Canon governance but are not themselves Canon rules.
Examples include:
• MWMS Affiliate Revenue Engine
• Offer Intelligence Page Template
• Affiliate Opportunity Pipeline
• Velocity Decision Engine
• Offer Graveyard / Rejected Offers Intelligence
These documents define operational architecture and intelligence frameworks used by the system.
They remain subordinate to Canon governance.
Affiliate Revenue System Architecture
The following documents define the operational architecture of the MWMS Affiliate Revenue Engine.
These pages form the structural workflow used to evaluate affiliate opportunities, generate marketing creatives, execute advertising campaigns, and analyse performance outcomes.
Documents:
MWMS Affiliate Revenue Engine
Defines the full affiliate campaign lifecycle and revenue generation workflow.
Offer Intelligence Page Template
Defines the required structure used to analyse affiliate opportunities prior to Velocity evaluation.
Offer Graveyard / Rejected Offers Intelligence
Defines the intelligence system used to record rejected, paused, or retired affiliate opportunities and preserve negative intelligence.
Velocity Decision Engine
Defines the capital-allocation gatekeeping system used by Affiliate Brain to approve or reject testing decisions.
These documents collectively form the operational architecture of the MWMS affiliate experimentation system.
Canon Change Control
Changes to Canon must follow the Canon Editing Protocol.
All updates must:
• declare version changes
• be recorded in the Canon Change Log
• maintain governance integrity
Canon updates require HeadOffice authority.
Canon vs Implementation
Canon defines rules and structure.
Implementation includes:
• WordPress plugins
• Supabase schema deployments
• executors and agents
• automation workflows
• campaigns and operations
Implementation must never contradict Canon.
If a conflict occurs, Canon prevails.
Mental Model
Canon = Constitution
HeadOffice = Government
Brains = Departments
Tasks = Work Orders
Executors = Workers
System Architecture = Infrastructure
The Canon Index is the table of contents of the MWMS constitution.
Final Principle
A complex system requires clear rules.
Canon ensures MWMS grows with:
• discipline
• consistency
• governance integrity
The Canon Index ensures those rules remain visible and accessible.
Drift Protection
The system must prevent:
• canon material existing without directory visibility
• subordinate architecture pages being mistaken for canon authority
• reference architecture expanding without constitutional context
• operators treating non-indexed material as active Canon
• canon growth creating navigation ambiguity
• implementation layers being confused with constitutional layers
All canonical interpretation must begin from an authoritative, visible index.
Architectural Intent
MWMS – Canon Index exists to provide one stable constitutional directory for the MWMS ecosystem.
Its role is to keep canonical governance visible and navigable while clearly separating true Canon authority from subordinate architecture and intelligence pages that operate beneath it.
Change Log
Version: v1.2
Date: 2026-03-15
Author: MWMS HeadOffice
Change: Added Affiliate Revenue System Architecture subsection under the Architecture & Intelligence Systems reference layer. Preserved existing Canon Index structure while making the affiliate experimentation architecture grouping explicit inside the index.
Version: v1.1
Date: 2026-03-13
Author: MWMS HeadOffice
Change: Initial structured version of MWMS Canon Index defining governance layers, system architecture references, operational protocols, technical standards, registry pages, and the distinction between Canon and subordinate architecture documents.
Version: v1.0
Date: 2026-03-13
Author: MWMS HeadOffice
Change: Initial creation of MWMS Canon Index as the master directory of all canonical governance documents within the MWMS ecosystem.
END – MWMS – CANON INDEX v1.2