Document Type: Protocol
Status: Active
Version: v2.0
Authority: HeadOffice
Applies To: MWMS system implementation across Affiliate Brain, Experimentation Brain, Finance Brain, Research Brain, Data Brain, Ads Brain, Conversion Brain, and mwmsbrain.site
Parent: HeadOffice Brain
Last Reviewed: 2026-04-25
Purpose
This protocol defines the required build sequence for implementing the MWMS Opportunity System.
Its purpose is to ensure:
• correct implementation order
• dependency alignment between components
• avoidance of wasted development effort
• early creation of usable system value
• structured progression from intake to full system control
• alignment with measurement-driven decision system
This document converts MWMS architecture into a practical build plan for M.
Scope
This protocol applies to:
• mwmsbrain.site system build
• UI surface implementation
• operational workflow deployment
• cross-brain system wiring
It defines:
• build phases
• component dependencies
• implementation order
• minimum viable system
It does not define:
• code implementation
• database schema
• API logic
Core Principle
Build the system in the order that creates usable flow earliest.
Do not build downstream systems before upstream inputs exist.
Each step must produce a usable system increment.
System Build Philosophy
MWMS must be built:
• from entry point outward
• from simplest usable flow to full system
• from manual operation to automation
• from structure to execution
• from data collection to decision control
Avoid:
• building isolated components
• building future systems before current usage exists
• over-engineering early stages
• building without measurement planning
Measurement First Rule (NEW)
System build must follow:
Plan → Build → Report → Forecast → Optimize
This means:
• measurement planning must exist before tracking
• forecasting must exist before testing
• reporting must exist before decision layers
• optimization must be based on forecast comparison
Build Phases Overview
Phase 1 — Intake System
Phase 2 — Evaluation System
Phase 3 — Measurement And Forecast System
Phase 4 — Testing System
Phase 5 — Result And Learning System
Phase 6 — Capital Control System
Phase 7 — System Oversight
Phase 1 — Intake System (Highest Priority)
Components
• Affiliate Brain Intake Queue
• Opportunity Intake Record Screen
• Intake Status System
Purpose
Create the system entry point.
Outcome
Martyn can:
• enter opportunities
• store structured data
• manage intake workflow
Dependency
None
Phase 2 — Evaluation System
Components
• Offer Intelligence Queue
• Offer Intelligence Record Screen
• Evaluation Decision Panel
Purpose
Enable structured opportunity evaluation.
Outcome
System can:
• evaluate opportunities
• decide viability
• prepare for next stage
Dependency
Phase 1 must be complete
Phase 3 — Measurement And Forecast System (NEW CRITICAL PHASE)
Components
• Measurement Planning Interface (KIA)
• Tracking Requirement Definition Layer
• Forecast Definition Panel
• Decision Trigger Mapping
Purpose
Ensure all tests are measurable and predictable before execution.
Outcome
System can:
• define what data is needed
• define what will be measured
• define expected performance
• define decision logic before testing
Dependency
Phase 2 must be complete
Rule
No system may proceed to testing without:
• measurement plan
• forecast
• decision logic
Phase 4 — Testing System
Components
• Affiliate → Experimentation Handoff Object
• Test Candidate Queue
• Test Candidate Record Screen
• Test Setup Panel
Purpose
Enable controlled test creation and execution.
Outcome
System can:
• convert decisions into tests
• execute structured experiments
Dependency
Phase 3 must be complete
Phase 5 — Result And Learning System
Components
• Test Result Classification System
• Action Driven Reporting Layer
• Forecast Comparison Engine
• Learning Capture Interface
• Signal Capture System
Purpose
Turn test outcomes into structured decisions and learning.
Outcome
System can:
• classify results
• compare against forecast
• generate clear actions
• capture reusable intelligence
Dependency
Phase 4 must be complete
Phase 6 — Capital Control System
Components
• Budget Tier System
• Spend Limit Enforcement
• Capital Escalation Logic
• Loss Containment Rules
Purpose
Protect capital and enforce financial discipline.
Outcome
System can:
• control spend
• limit risk
• enforce scaling discipline
Dependency
Phase 4 must be functional
Phase 7 — System Oversight
Components
• HeadOffice Cross Brain Dashboard
• Alert System
• Control Actions
Purpose
Provide full system visibility and control.
Outcome
HeadOffice can:
• monitor entire system
• intervene when needed
• manage risk
• ensure system integrity
Dependency
All prior phases should be functional
Build Order Summary
Intake System
Evaluation System
Measurement And Forecast System
Testing System
Result And Learning System
Capital Control System
System Oversight
Minimum Viable System (MVS)
The first usable MWMS system is achieved after:
Phase 1 + Phase 2 + Phase 3 + Phase 4
This allows:
• opportunity entry
• evaluation
• measurement planning
• forecasting
• test execution
Recommended First Build Target
Start with:
Affiliate Brain Intake System
Then:
Evaluation System
Then:
Measurement And Forecast System
Development Guidance For M
M should:
• build UI surfaces matching screen specifications
• implement status transitions
• ensure record linkage between systems
• enforce stage progression logic
• avoid over-building features early
• prioritize usability over completeness
• ensure every stage produces structured output
System Evolution Strategy
After initial build:
• expand features gradually
• refine based on usage
• introduce automation later
• integrate AI after stable workflows exist
• improve forecasting accuracy over time
• improve reporting clarity
Controlled Loss Alignment
This build order supports the MWMS Controlled Loss Principle by:
• ensuring structured input
• enforcing disciplined testing
• requiring forecasting before spend
• controlling capital before scaling
• capturing learning early
Governance Role
This protocol ensures:
• MWMS is built in correct sequence
• system integrity is maintained
• development remains aligned with architecture
• operational readiness is achieved step-by-step
• decisions are measurement-driven
• scaling is controlled
Relationship To Other MWMS Pages
This protocol operates alongside:
• Affiliate Brain Opportunity Intake Workflow
• Affiliate Brain Offer Intelligence Screen Specification
• Affiliate Brain To Experimentation Brain Handoff Specification
• Experimentation Brain Test Candidate Screen Specification
• Experimentation Brain Test Result And Decision Workflow
• Finance Brain Test Budget And Capital Control Specification
• Research Brain Test Learning And Signal Capture Framework
• HeadOffice Cross Brain Performance And Control Dashboard Specification
Drift Protection
The system must prevent:
• building components out of order
• skipping measurement planning
• testing without forecasts
• implementing automation before manual flow works
• building isolated features
• ignoring dependencies
Architectural Intent
This protocol converts MWMS from:
designed system
→
buildable and executable system
It ensures:
• development follows logic
• system becomes usable quickly
• complexity grows in controlled stages
• decisions improve over time
Change Log
Version: v2.0
Date: 2026-04-25
Author: HeadOffice
Change
Upgraded build order to include:
• Measurement Planning Layer
• Forecast Definition Layer
• Action Driven Reporting
• Forecast Comparison Logic
• Decision Driven System Build
Pages Updated
MWMS Opportunity System Build Order
Pages Created
None
Registries Requiring Update
None