Document Type: Protocol
Status: Governance Protocol
Authority: MWMS HeadOffice
Applies To: Entire MWMS ecosystem
Version: v1.1
Last Reviewed: 2026-03-15
Parent: MWMS Canon
Purpose
The MWMS Brain Creation Protocol defines the official process required to create a new Brain within the MWMS ecosystem.
The protocol exists to prevent:
• uncontrolled system expansion
• duplicated responsibilities
• authority conflicts between Brains
• structural instability
Every Brain must pass this protocol before being recognised as an official MWMS Brain.
If a Brain has not passed this process, it is not considered part of the MWMS ecosystem.
Scope
This protocol applies to:
• creation of new Brains inside MWMS
• evaluation of proposed Brain missions and scopes
• approval requirements for structural expansion
• registry-entry requirements for newly approved Brains
• retirement and scope-change governance for existing Brains
This document governs how new Brains may be proposed, evaluated, approved, registered, modified, or retired.
It does not govern:
• day-to-day operations of an approved Brain
• AI employee behavior by itself
• canon authority by itself
• campaign execution
• capital allocation
• unapproved experimental ideas that remain outside formal Brain status
Those remain governed by HeadOffice, the MWMS Brain Registry, the MWMS AI Employee Registry, and the relevant Brain canons.
Definition / Rules
Core Principle
Brains represent departments within the MWMS organisation.
A Brain may only be created when:
• a distinct operational responsibility exists
• the responsibility cannot be handled by an existing Brain
• the Brain provides clear value to the ecosystem
Brains must never be created for convenience.
They must exist only when structurally necessary.
Brain Creation Approval Authority
Only the following authority may approve creation of a new Brain:
Human Executive Authority
(Martyn Walker & M)
Approval must occur before the Brain may be added to the MWMS Brain Registry.
Brain Creation Evaluation
Before approval, the proposed Brain must pass the following evaluation questions.
1 — Unique Mission
Does the Brain have a clearly defined mission?
The mission must not duplicate the responsibility of an existing Brain.
If overlap exists, the Brain must not be created.
2 — Clear Operational Scope
The Brain must define a clear operational scope.
This scope must specify:
• what the Brain is responsible for
• what the Brain is not responsible for
The scope must not conflict with another Brain’s authority.
3 — Ecosystem Value
The Brain must provide measurable value to the MWMS ecosystem.
Examples include:
• revenue generation
• intelligence gathering
• operational support
• governance protection
If the Brain does not provide meaningful value, it must not be created.
4 — AI Employee Requirement
The Brain must justify the creation of at least one AI employee role.
If the Brain does not require specialised AI employees, it likely does not need to exist as a separate Brain.
5 — Governance Compatibility
The Brain must be compatible with the MWMS governance structure.
It must clearly define:
• which Brain or authority it reports to
• how its decisions are governed
• what its escalation path is
Brain Creation Process
When a new Brain is proposed, the following process must occur.
Step 1 — Proposal
The proposed Brain must be documented with:
• Brain Name
• Primary Mission
• Operational Scope
• Parent Authority
• Proposed AI Employees
Step 2 — Evaluation
The Brain must pass the five evaluation criteria defined in this protocol.
If any criteria fail, the proposal must be rejected or revised.
Step 3 — Approval
Human Executive Authority must approve the Brain.
Approval confirms that the Brain is necessary and structurally valid.
Step 4 — Registry Entry
Once approved, the Brain must be added to the:
MWMS Brain Registry
The registry becomes the official record of the Brain’s existence.
Step 5 — Employee Creation
Once the Brain is registered:
AI Employees may be created for that Brain and recorded in the:
MWMS AI Employee Registry
Brain Modification Rules
Existing Brains may not change their mission or scope without approval.
If a Brain requires expansion of scope:
• the change must be evaluated
• the change must be approved by HeadOffice
• the Brain Registry must be updated
Brain Retirement
If a Brain becomes obsolete, it may be retired.
Retirement requires:
• HeadOffice approval
• registry update
• AI employee reassignment or removal
Governance Rule
No Brain may:
• create new Brains
• expand authority independently
• operate outside its defined scope
Only HeadOffice may authorise structural expansion.
Outcome
The Brain Creation Protocol ensures that MWMS grows in a controlled, stable, and structured manner.
It protects the ecosystem from:
• unnecessary complexity
• governance conflicts
• uncontrolled expansion
Final Rule
No new Brain is valid unless it has passed proposal, evaluation, approval, and registry entry through this protocol.
A useful idea is not the same as an authorised Brain.
Drift Protection
The system must prevent:
• new Brains being created informally
• overlapping Brain missions being approved without challenge
• scope expansion occurring without governance review
• unregistered Brains being treated as official system components
• convenience-based structural expansion
• Brain retirement occurring without registry cleanup and employee review
Brain creation must remain deliberate, governed, and structurally justified.
Architectural Intent
MWMS – Brain Creation Protocol exists to control how the ecosystem expands at the departmental level.
Its role is to ensure that new Brains are created only when they serve a distinct, governed, and valuable function so MWMS can scale without drifting into duplication, authority confusion, or structural mess.
Change Log
Version: v1.1
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 purpose, core principle, approval authority, evaluation criteria, creation process, modification rules, retirement rules, governance rule, and system-protection intent. Added Document Type, Parent, Scope, Definition / Rules structure, Final Rule, Drift Protection, and Architectural Intent sections.
Version: v1.0
Date: 2026-03-13
Author: MWMS HeadOffice
Change: Initial creation of MWMS – Brain Creation Protocol defining the official process for creating new Brains within the MWMS ecosystem.
END – MWMS – BRAIN CREATION PROTOCOL v1.1