Document Type: Canon
Status: Canon
Authority: MWMS HeadOffice
Applies To: All MWMS Brains and AI Employees
Version: v1.2
Last Reviewed: 2026-04-16
Parent: MWMS Canon
Purpose
This document defines how Brains communicate, coordinate work, and enforce authority boundaries inside the MWMS ecosystem.
Without a defined interaction protocol, Brains could operate in isolation, duplicate work, or violate governance boundaries.
The protocol ensures all Brains interact through structured, auditable mechanisms rather than informal or uncontrolled exchanges.
This preserves:
system integrity
governance enforcement
operational clarity
data traceability
decision consistency
cross-brain coordination reliability
learning continuity
The interaction protocol ensures MWMS operates as a coordinated AI organisation rather than disconnected tools.
Scope
This canon applies to:
all cross-brain coordination inside MWMS
all AI employees participating in cross-brain work
task-based work movement between Brains
authority-boundary enforcement during collaboration
logging and audit visibility for cross-brain interaction
external change routing into Brains
continuous improvement feedback routing
This document governs how work moves between Brains and how cross-brain communication must be structured.
It does not govern:
brain-internal workflow design by itself
campaign execution by itself
capital approval by itself
compliance rulings by themselves
system architecture wiring by itself
session-start protocol by itself
Those remain governed by the relevant Brain canons, MWMS System Architecture, MWMS Authority Structure, and How to Start a Session — MWMS Operating Guide.
Core Principle
Brains do not communicate through conversation.
Brains communicate through structured tasks and shared system data.
All cross-brain coordination must occur through the MWMS task system.
This ensures every action is:
recorded
auditable
traceable
reviewable by HeadOffice
repeatable
visible across the ecosystem
MWMS remains governance-safe only when interaction is structured.
MWMS Interaction Model
Brains interact using the following structure:
Requesting Brain
↓
Structured Task Creation
↓
Task Database (Supabase)
↓
Receiving Brain / AI Employee
↓
Execution or Analysis
↓
Result Logged
↓
HeadOffice Visibility
No direct Brain-to-Brain overrides exist.
All coordination flows through the task system.
Interaction Types
The MWMS ecosystem recognises several types of cross-brain interaction.
Intelligence Requests
Used when one Brain requires analysis or interpretation from another Brain.
Example:
Affiliate Brain requests market interpretation.
Research Brain analyses behavioural or market signals.
Structured intelligence returned.
Example flow:
Affiliate Brain
↓
Task created: intelligence_request
↓
Research Brain processes task
↓
Results logged to system
Intelligence requests improve decision clarity.
Compliance Verification
Used when work must pass integrity or regulatory review.
Example:
Execution Brain prepares campaign structure.
Compliance Brain verifies claim safety and platform compliance.
Example flow:
Execution Brain
↓
Task created: compliance_check
↓
Compliance Brain reviews
↓
Decision logged
Compliance verification protects system safety.
Financial Oversight
Used when decisions affect capital allocation or risk exposure.
Example:
Ads Brain requests budget increase.
Finance Brain evaluates exposure risk.
Example flow:
Execution Brain
↓
Task created: capital_request
↓
Finance Brain evaluates
↓
HeadOffice visibility maintained
Financial oversight protects survivability.
Experimentation Interaction
Used when signal confidence must be validated statistically.
Example:
Ads Brain produces performance variation.
Experimentation Brain evaluates statistical reliability.
Example flow:
Ads Brain
↓
Task created: experiment_validation
↓
Experimentation Brain evaluates
↓
confidence signal returned
Experimentation interaction protects learning reliability.
Strategy Interaction
Used when value structure or persuasion logic must be defined.
Example:
Affiliate Brain identifies opportunity.
Offer Brain structures value proposition.
Creative Brain structures persuasion logic.
Example flow:
Affiliate Brain
↓
Task created: strategy_request
↓
Offer Brain / Creative Brain evaluate
↓
structured decision logic returned
Strategy interaction protects decision quality.
Execution Coordination
Execution Brains coordinate delivery of commercial activity.
Examples include:
Content Brain supports Ads Brain through education environments.
Product Brain supports Sales Brain through delivery capability clarity.
Partnership Brain supports Product Brain through capability expansion.
Sales Brain supports Conversion Brain through expectation alignment clarity.
Example flow:
Execution Brain
↓
Task created: execution_support_request
↓
Receiving Execution Brain processes request
↓
Result logged
Execution coordination improves commercial reliability.
Content Intelligence Feedback Interaction (NEW)
Content Brain produces behavioural signals influencing multiple Brains.
Example:
Content performance reveals audience intent patterns.
Signals routed to:
Research Brain
Customer Brain
Data Brain
Creative Brain
Offer Brain
Example flow:
Content Brain
↓
Task created: signal_feedback
↓
Receiving Brain interprets signal
↓
insight logged
Content improves signal clarity across ecosystem.
Product Capability Interaction (NEW)
Product Brain interacts with Offer Brain, Sales Brain, and Partnership Brain to ensure capability aligns with value structure and delivery expectations.
Example flow:
Offer Brain defines value structure
↓
Task created: capability_alignment_request
↓
Product Brain evaluates capability structure
↓
response logged
Product interaction protects delivery reliability.
Sales Interaction (NEW)
Sales Brain coordinates with:
PPL Brain
Conversion Brain
Product Brain
Customer Brain
to ensure demand converts into stable revenue.
Example flow:
PPL Brain produces qualified lead signals
↓
Task created: sales_progression_request
↓
Sales Brain interprets readiness
↓
result logged
Sales interaction improves conversion stability.
Partnership Interaction (NEW)
Partnership Brain interacts with Product Brain, Sales Brain, Content Brain, and Offer Brain to expand ecosystem capability through structured collaboration.
Example flow:
Product Brain identifies capability gap
↓
Task created: partnership_capability_request
↓
Partnership Brain evaluates collaboration options
↓
result logged
Partnership interaction expands leverage capability.
Automation Coordination (NEW)
Automation Brain coordinates workflow orchestration across Brains.
Example:
task triggers
workflow sequencing
integration execution
routing automation
Example flow:
Operations Brain defines workflow structure
↓
Task created: automation_sequence_request
↓
Automation Brain executes orchestration logic
↓
workflow result logged
Automation interaction improves scalability.
Change Intelligence Interaction (NEW)
External changes enter the system through HeadOffice.
Example sources:
law changes
platform policy updates
technology shifts
measurement changes
AI capability changes
Example flow:
External signal received
↓
Task created: change_intelligence_review
↓
HeadOffice triage
↓
routing to specialist Brain
Change intelligence interaction protects ecosystem relevance.
Kaizen Interaction (NEW)
Continuous improvement signals may originate from any Brain.
Example triggers:
repeated friction
repeated confusion
duplicated structures
inefficient workflows
unclear signals
Example flow:
Brain identifies improvement opportunity
↓
Task created: kaizen_improvement_signal
↓
HeadOffice reviews pattern
↓
improvement applied
Kaizen interaction improves system clarity across time.
Authority Enforcement
Brain interaction must always respect MWMS authority structure.
Authority hierarchy:
Humans (Martyn & M)
↓
HeadOffice
↓
Brains
↓
AI Employees
Rules:
Brains cannot override HeadOffice.
AI employees cannot override Brains.
Humans retain final authority.
Authority breaches must be escalated.
Authority clarity protects governance discipline.
Brain Autonomy Limits
Brains operate autonomously only within their defined scope.
Autonomy applies to:
routine operational decisions
analysis and research tasks
campaign execution within limits
workflow optimisation
signal interpretation
Autonomy does not apply to:
capital allocation beyond thresholds
governance modification
system architecture changes
creation of new Brains
structural law modification
These require escalation.
Task Logging Requirements
Every cross-brain interaction must create a system record containing:
Task ID
Originating Brain
Receiving Brain
Task Type
Status
Timestamp
Result
Traceability protects operational memory.
Failure Handling
If a Brain fails to complete a task:
task remains visible
HeadOffice visibility triggered
human review if necessary
Failure cannot be hidden.
Transparent failure improves reliability.
Audit Visibility
HeadOffice maintains visibility over:
task creation
cross-brain requests
execution results
routing patterns
failure patterns
improvement signals
Visibility protects governance stability.
Interaction Philosophy
MWMS is not a collection of isolated tools.
It is a coordinated AI organisation.
Brains function like departments in a company.
Departments communicate through structured work requests.
Not informal conversation.
Structured communication ensures:
accountability
clarity
operational discipline
scaling reliability
Relationship to Other Canon Documents
This protocol operates alongside:
MWMS Authority Structure
MWMS System Architecture
MWMS Request Routing Map
MWMS Brain Interaction Map
How to Start a Session — MWMS Operating Guide
Authority Structure defines who controls decisions.
Architecture defines how the system is wired.
Routing Map defines where requests go.
Interaction Protocol defines how work moves between Brains.
Mental Model
Authority Structure = organisational hierarchy
System Architecture = technical wiring
Interaction Protocol = department workflow
Routing Map = task traffic control
Brain Interaction Map = ecosystem map
Together they form the operational coordination system of MWMS.
Final Principle
A Brain that acts alone becomes chaos.
A Brain that interacts through structure becomes part of a system.
MWMS requires structured interaction.
Final Rule
No cross-brain interaction is valid unless it is:
task-based
logged
authority-safe
visible to governance
Informal coordination is non-compliant.
Drift Protection
The system must prevent:
informal brain-to-brain requests outside the task system
cross-brain work occurring without traceable records
AI employees acting across brain boundaries without authorised routing
hidden task failure or silent non-completion
authority breaches being handled casually
cross-brain coordination drifting into conversation instead of structured workflow
structured interaction must remain enforceable.
Architectural Intent
MWMS Brain Interaction Protocol exists to ensure cross-brain collaboration remains reliable, auditable, and governance-safe as the ecosystem expands.
Its role is to ensure Brains function as coordinated departments within a structured organisation.
Interaction discipline protects system stability.
Change Log
Version: v1.2
Date: 2026-04-16
Author: MWMS HeadOffice
Updated to include:
Content Brain interaction signals
Product Brain interaction pathways
Sales Brain interaction pathways
Partnership Brain interaction pathways
Automation Brain orchestration role
Change Intelligence routing interaction
Kaizen improvement loop interaction
Clarified separation between Strategy vs Execution interactions
Clarified Product vs Offer vs Sales vs Partnership interaction boundaries
Strengthened cross-brain workflow discipline alignment with MWMS Request Routing Map v1.2
END — MWMS Brain Interaction Protocol v1.2