Document Type: Canon
Status: Canon
Version: v1.16
Authority: HeadOffice
Applies To: All MWMS work involving AI tools (Plus, Pro, future systems)
Parent: Governance
Last Reviewed: 2026-03-31
Purpose
This guide exists to ensure consistency, discipline, ecosystem alignment, and canon compliance when starting any working session involving MWMS.
It removes ambiguity about:
what mode the session is in
what rules apply
how authority is enforced
how drift is prevented
how build-state is controlled
how system improvements are captured
how file changes are delivered
what long-term ecosystem vision governs decisions
how system architecture operates
how revenue flows through the ecosystem
This is not optional process.
It is system hygiene.
This page also exists to prevent session drift caused by incomplete startup context.
Where a task depends on specific standards, those standards must be provided at session start.
Consistency comes from structure, not memory.
Scope
This canon applies to:
all MWMS AI-assisted working sessions
Plus sessions
Pro sessions
canon editing sessions
standards and page-standardisation sessions
brain-scoped work
free sessions
build sessions
governance sessions
This document governs how MWMS sessions must be started and what must be confirmed before valid work proceeds.
It does not replace:
individual brain canon
technical build specifications
page-level standards
registry update rules
savepoint requirements
change logs
Those remain governed by their own authoritative documents.
Definition Rules
Core Principle (Non-Negotiable)
AI tools do not enforce canon.
Canon is enforced at the session boundary.
If the session is not framed correctly at the start, drift is expected.
Consistency comes from structure, not memory.
Mandatory Title Compliance Rule (NEW)
All page titles must comply with:
MWMS Page Naming Standard v1.2
No dash characters are permitted in page titles.
Title structure must follow:
SYSTEM Subject Name
Examples:
MWMS Brain Connector Architecture
MWMS Brain Creation Protocol
Affiliate Brain Offer Intelligence
Ads Brain Creative Testing Workflow
Research Brain Opportunity Heatmap
Dash usage is prohibited in page titles.
Not allowed:
MWMS – Brain Connector Architecture
Affiliate Brain – Offer Intelligence
Ads Brain – Creative Testing Workflow
Dash usage previously caused:
inconsistent formatting
mixed dash characters
registry mismatch issues
automation matching failures
increased cleanup workload
visual inconsistency across Brains
All new pages must comply with the no-dash structure.
If a draft title includes a dash, the output is invalid and must be corrected before use.
MWMS Ecosystem Vision Directive
(Foundational Context)
All sessions operate inside the following long-term vision.
If work contradicts this section, escalate to HeadOffice.
What MWMS Is
MWMS is an AI-driven business ecosystem composed of specialised Brains operating semi-autonomously under central command.
HeadOffice Brain = Executive Command Layer
Humans (Martyn & M) = Final authority
MWMS is:
a coordinated AI corporation
a capital-efficient experimentation engine
a governance-first enterprise system
a continuously improving structure
Each Brain has:
defined scope
defined authority boundaries
defined workflows
defined decision limits
All Brains report to HeadOffice.
End-State Objective
When mature, MWMS becomes:
a self-improving AI corporation
a two-human executive team supported by AI employees
a multi-revenue ecosystem
a risk-optimised capital engine
a governance-protected enterprise infrastructure
The system:
uploads knowledge
tests knowledge
validates performance
integrates what works
discards what fails
improves continuously
Primary aim:
Risk less capital for better returns.
Organisational Model
HeadOffice
↓
Departmental Brains
↓
AI Employees and Systems
Core Brains include:
Affiliate Brain
Ads Brain
Experimentation Brain
PPL Brain
Research Brain
Content Brain
AI Studio Brain
Social Brain
Website Brain
Finance Brain
SIT Brain
AIBS Brain
No Brain overrides HeadOffice.
MWMS System Architecture Context
All MWMS sessions must operate with awareness of the system architecture layer.
The MWMS system consists of:
Humans
↓
WordPress Control Layer
↓
Supabase Data Layer
↓
AI Executors
↓
Output Systems
Brains communicate through structured task systems.
No Brain operates in isolation.
MWMS Canon Index Context
Core Canon Architecture Pages include:
MWMS Brain Registry
MWMS Brain Interaction Map
MWMS Decision Authority Matrix
MWMS System Data Flow Map
HeadOffice UI pages include:
HeadOffice UI Ads Command Dashboard
HeadOffice UI Affiliate Ads Pipeline Dashboard
HeadOffice UI MWMS System Command Center
Operational Brain Canons include:
Affiliate Brain Canon
Ads Brain Canon
Experimentation Brain Canon
Finance Brain Canon
SIT Brain Canon
PPL Brain Canon
System Awareness Confirmation
Before beginning work the AI must confirm:
Active Session Type
Active Brain
Operating Layer
And confirm awareness of:
HeadOffice governance authority
Brain Registry structure
cross-brain authority boundaries
Finance capital governance
SIT enforcement authority
Experimentation statistical governance
Ads Brain experimentation role
Affiliate Brain opportunity validation role
If awareness cannot be confirmed the session must pause.
MWMS Money Engine Context
Primary engine:
Traffic
↓
Offer Testing
↓
Conversion
↓
Profit
↓
Reinvestment
↓
Expansion
Operational flow:
Content → Traffic → Offers → Revenue → Scaling
Affiliate Brain is primary early-stage revenue generator.
Future expansion includes:
PPL revenue
AIBS enterprise systems
new digital ventures
AI Governance Control Layer
All AI work must operate inside governance framework:
AI Output Standard Full File Delivery Rule
AI Session Context Lock Rule
Brain Routing Rule
AI Escalation Rule
AI Refusal Protocol
AI Change Declaration Rule
AI Memory Integrity Rule
AI Evidence Requirement Rule
MWMS Verification Mode
When verifying:
page existence
page hierarchy
page parent relationships
WordPress structures
Supabase structures
screenshots
UI elements
file contents
plugin structures
AI must operate in strict evidence mode.
Rules:
Only use visible evidence provided in session.
Do not assume existence.
If not visible state:
NOT VISIBLE IN PROVIDED EVIDENCE
If uncertain state:
UNCERTAIN BASED ON PROVIDED EVIDENCE
Separate outputs into:
CONFIRMED FACTS
INFERENCES
NEXT CHECK NEEDED
Screenshots override assumptions.
File contents override assumptions.
AI must not fabricate confirmation language.
Output Structure Rule
All structural outputs must include:
OUTPUT TYPE
AFFECTED SYSTEM AREA
Valid output types:
Canon Update
Architecture Update
Registry Update
Protocol Update
Build Instruction
System Improvement
Investigation Analysis
AI Page Ownership Declaration Requirement
AI Page Ownership Declaration Requirement
Before drafting any new page, the AI must explicitly declare:
Site
Owning Brain
Document Type
Exact Page Title
Storage Location
Parent Page
This declaration must appear BEFORE the draft document content.
Purpose:
Prevent incorrect site placement.
Prevent incorrect page placement into MCR or incorrect Brain.
Ensure correct authority alignment on first creation.
Ensure parent-child structure is declared before drafting begins.
Reduce structural rework during AI-assisted development.
Support compliance with:
Brain Routing Rule
Document Taxonomy
Document Structure Standard
Brain Header Schema Standard
Page Discovery Rule
This rule does not modify canon authority structures.
It ensures structural clarity during AI-assisted build sessions.
Mandatory Full Output Rule
All structural outputs must be:
complete file output
full replacement content
no fragments
Partial output is invalid.
Change Impact Declaration Rule
All structural outputs must include:
Pages Created
Pages Updated
Pages Deprecated
Registries Requiring Update:
MWMS Architecture Registry
MWMS Brain Registry
MWMS Canon Hierarchy Map
MWMS Brain Interaction Map
Canon Version Update Required Yes or No
Change Log Entry Required Yes or No
System Registry Maintenance Rule
When pages change the following must be reviewed:
MWMS Architecture Registry
MWMS Brain Registry
MWMS Canon Hierarchy Map
MWMS Brain Interaction Map
Page Discovery Rule
New pages must be declared in:
MWMS Architecture Registry
relevant Brain architecture
relevant Brain employee registry where applicable
Undeclared pages are non-operational.
Brain Page Header Schema Rule
All Brain pages must include structured header metadata.
Change Log
Version v1.16
Date 2026-03-31
Author HeadOffice
Change:
Integrated MWMS Page Naming Standard v1.2.
Added Mandatory Title Compliance Rule enforcing no-dash title structure.
Prevents inconsistent dash usage across Brain pages.
Improves registry matching stability.
Reduces structural drift risk.
Strengthens session-boundary canon enforcement.
No authority changes.