Document Type: Canon
Status: Canon
Authority: MWMS HeadOffice
Applies To: All MWMS Brains, AI systems, plugins, and execution layers
Parent: MWMS Constitution
Version: v1.3
Last Reviewed: 2026-03-15
Purpose
MWMS Canon is the constitutional root of the MWMS system.
It is the single source of structural truth governing:
• Brain definitions
• authority boundaries
• system-wide rules
• enforcement mechanisms
• AI invocation protocols
• plugin behavioural constraints
This layer defines structure, not execution.
Scope
This canon applies to:
• all MWMS Brains
• all AI systems operating within MWMS
• all plugins and automation layers
• all execution layers that rely on MWMS rules
• promotion of material into the canonical governance layer
• interpretation of constitutional knowledge classes across the ecosystem
This document governs the constitutional root of MWMS.
It does not govern:
• day-to-day execution by itself
• operational logs by themselves
• draft planning material by itself
• Brain-specific execution protocols by themselves
• plugin implementation details by themselves
• live campaign decisions by themselves
Those remain governed by operational environments, Brain canons, standards, protocols, and related execution systems.
Definition / Rules
Canon Discipline Rule (Non-Negotiable)
Only locked, versioned, approved material may exist within MWMS Canon.
The following are prohibited within this namespace:
• draft content
• brainstorming notes
• experimental structures
• temporary policies
• execution logs
• meeting summaries
• development discussion
Draft and working material must exist in operational environments such as HeadOffice, Brain Room, and Dev Console and may only be promoted here once finalized.
Promotion Rule
Material may only enter MWMS Canon if:
• it has defined scope
• it has clear authority ownership
• it includes version metadata
• it has been reviewed under a Canon session
Unversioned content is invalid by default.
Hierarchy
MWMS Canon contains two structural domains:
Governance
System-wide constitutional rules that apply to all Brains and systems.
Brains
Departmental constitutional definitions including scope, authority, boundaries, and interfaces.
Governance governs Brains.
Brains govern execution.
Execution does not alter Canon.
Knowledge Classification Standard
All intelligence stored or referenced within MWMS must be classified according to its structural type.
Three knowledge classes are recognized across the system.
Tactical Insight
Operational techniques or tactical improvements that can be directly implemented in execution environments.
Examples include:
• ad creative structures
• landing page variations
• funnel mechanics
• audience targeting tactics
These are short-cycle improvements used in testing and optimization.
Structural Model
Frameworks that describe how a system behaves over time.
Examples include:
• customer lifecycle models
• revenue forecasting models
• cohort behaviour models
• retention or churn models
Structural models guide analysis and forecasting but are not direct execution tactics.
Strategic Principle
High-level rules governing decision discipline and system design.
Examples include:
• capital survivability rules
• statistical discipline requirements
• governance structures
• scaling eligibility rules
Strategic principles define the boundaries within which all other intelligence operates.
Knowledge Usage Rule
Operational Brains must not treat Structural Models or Strategic Principles as tactical instructions.
When referencing intelligence from Research Brain or other Canon sources:
• the Insight Type must be declared
If Insight Type is undefined, the intelligence is treated as exploratory and cannot be used to justify scaling decisions.
Enforcement Principle
Canon is not enforced by memory.
Canon is enforced by structure.
All AI systems, plugins, and execution layers must reference this namespace as the authoritative rule source.
If ambiguity exists, the Canon prevails.
Final Principle
Stability precedes scale.
Structure precedes execution.
Discipline precedes intelligence.
Final Rule
If material is not locked, versioned, scoped, and approved, it does not belong in MWMS Canon.
Constitutional clarity outranks convenience.
Drift Protection
The system must prevent:
• draft material being promoted into Canon
• operational content being mistaken for constitutional authority
• unversioned pages being treated as valid canonical sources
• execution layers altering governance by implication
• exploratory intelligence being used as if it were an approved principle
• ambiguity in source authority weakening Canon discipline
Canon must remain stable, explicit, and promotion-controlled.
Architectural Intent
MWMS Canon exists to provide the ecosystem with one constitutional root layer that remains stable as the rest of MWMS evolves.
Its role is to separate locked structural truth from operational work so Brains, plugins, AI systems, and execution layers always have an authoritative source for rules, boundaries, and system-wide discipline.
Change Log
Version: v1.3
Date: 2026-03-15
Author: MWMS HeadOffice
Change: Rebuilt page to align with the locked MWMS document standard for this cleanup pass. Preserved the original constitutional purpose, canon discipline rule, promotion rule, hierarchy, knowledge classification standard, knowledge usage rule, enforcement principle, and final principle. Added Document Type, Parent, Scope, Definition / Rules structure, Final Rule, Drift Protection, and Architectural Intent sections.
Version: v1.2
Date: 2026-03-13
Author: MWMS HeadOffice
Change: Updated MWMS Canon to reflect constitutional-root positioning, promotion controls, and knowledge classification standard.
Version: v1.0
Date: 2026-02-12
Author: MWMS HeadOffice
Change: Initial creation of MWMS Canon as the constitutional root of the MWMS system.
END – MWMS CANON v1.3