Document Type: Reference
Status: Reference
Authority: MWMS HeadOffice
Applies To: Entire MWMS ecosystem
Parent: HeadOffice Brain
Version: v1.1
Last Reviewed: 2026-03-15
Purpose
The Executive Operations Board defines the HeadOffice page used to monitor the most important operational priorities across the MWMS ecosystem in a single view.
Its purpose is to provide immediate visibility into:
• priority opportunities
• active experiments
• campaigns requiring review
• capital risk signals
• governance breaches
• systems needing escalation
• next actions requiring human attention
The Executive Operations Board is not a reporting archive.
It is the live executive operating page for HeadOffice.
Scope
This reference applies to:
• HeadOffice executive visibility across active MWMS operations
• priority and escalation monitoring
• cross-brain coordination visibility
• live operational attention management
• bottleneck, risk, and next-action display at the executive level
This document defines the intended structure and role of the Executive Operations Board as a visibility and coordination surface.
It does not govern:
• direct operational execution
• capital approval by itself
• lifecycle-stage changes by itself
• canon overrides
• direct data mutation
• automation approval by itself
Those remain governed by HeadOffice, Finance Brain, SIT Brain, and the relevant operational systems.
Definition / Rules
Core Role
The Executive Operations Board exists to answer one question:
What requires attention right now?
This page is the highest-level operational coordination layer inside MWMS.
It must allow Martyn, M, and future authorised operators to immediately identify:
• what is moving
• what is stuck
• what is risky
• what is promising
• what needs a decision
• what needs escalation
Board Structure
The board is divided into seven operational zones.
Priority Queue
This section displays the highest-priority items currently active in the MWMS ecosystem.
Examples include:
• offers awaiting review
• campaigns awaiting decision
• scaling candidates
• governance issues
• budget approvals
• stalled experiments
Recommended fields:
• Item Name
• Brain Owner
• Priority Level
• Current Status
• Required Action
• Due Timing
Priority levels:
• Critical
• High
• Normal
• Deferred
Purpose:
Ensure the most important work is always visible first.
Active Revenue Engine
This section shows all revenue-producing or revenue-seeking systems currently active.
Examples include:
• affiliate offers in testing
• ads campaigns in testing
• PPL campaigns
• scaled opportunities
• paused revenue systems
Recommended fields:
• Offer / System Name
• Channel
• Lifecycle Stage
• CPA / CPL Stability
• Current Decision Status
• Revenue Status
Purpose:
Provide live visibility into the money engine.
Decision Required Panel
This section lists items requiring a HeadOffice, Finance, or human decision.
Examples include:
• budget approval requests
• scaling approval requests
• override declarations
• paused campaign re-entry review
• new automation approval requests
Recommended fields:
• Decision Item
• Origin Brain
• Decision Type
• Risk Level
• Recommendation
• Required Approver
Purpose:
Separate observation from decision-making.
Governance & Integrity Alerts
This section displays structural or compliance issues across MWMS.
Examples include:
• SIT violations
• experiment integrity issues
• capital guardrail warnings
• lifecycle stage mismatches
• missing structural declarations
• cross-brain routing conflicts
Recommended fields:
• Alert Type
• Severity
• Affected Brain
• Reference ID
• Current Status
• Escalation Owner
Purpose:
Make governance failures impossible to ignore.
Bottleneck Tracker
This section shows where work is becoming stuck inside the MWMS system.
Examples include:
• offers stuck in evaluation
• campaigns waiting too long for design
• tests awaiting validation
• capital approvals delayed
• systems waiting on structural updates
Recommended fields:
• Item
• Current Stage
• Days Stalled
• Owning Brain
• Blocking Cause
• Next Action
Purpose:
Prevent hidden stagnation.
System Health Snapshot
This section provides a compressed overview of ecosystem health.
Recommended fields:
• Number of Active Offers
• Number of Active Experiments
• Number of Scaled Systems
• Number of Paused Systems
• Capital Exposure State
• Governance Alert Count
• Automation Health State
• System Stability Rating
Purpose:
Provide fast situational awareness.
Next Actions Ledger
This section lists the immediate next actions across the ecosystem.
Examples:
• review Offer X
• approve Budget Y
• validate Experiment Z
• rewrite Creative A
• investigate SIT alert B
• update Canon C
Recommended fields:
• Action
• Responsible Brain
• Responsible Human / AI
• Priority
• Deadline
• Status
Purpose:
Convert visibility into movement.
Board Input Sources
The Executive Operations Board draws data from:
• MWMS – Brain Registry
• MWMS – Brain Interaction Map
• MWMS – Decision Authority Matrix
• MWMS – System Data Flow Map
• MWMS – Offer Lifecycle Dashboard
• HeadOffice UI – Ads Command Dashboard (Spec)
• HeadOffice UI – Affiliate + Ads Pipeline Dashboard (Spec)
• HeadOffice UI – MWMS System Command Center (Spec)
And from operational Brain outputs including:
• Affiliate Brain
• Ads Brain
• Experimentation Brain
• Finance Brain
• SIT Brain
• PPL Brain
• AIBS Brain
Authority Rules
The Executive Operations Board may:
• display system priorities
• display revenue pipeline status
• display governance alerts
• display pending decisions
• display bottlenecks
• display next actions
The Executive Operations Board may not:
• launch campaigns
• approve capital directly
• change lifecycle stage
• override a Brain canon
• modify system data directly
This page is a command visibility and coordination layer only.
Recommended Layout
Top Row
• Priority Queue
• Decision Required Panel
Second Row
• Active Revenue Engine
• Governance & Integrity Alerts
Third Row
• Bottleneck Tracker
• System Health Snapshot
Bottom Row
• Next Actions Ledger
Operating Logic
HeadOffice should use the board in this sequence:
- Check Governance & Integrity Alerts
- Check Priority Queue
- Review Decision Required Panel
- Review Active Revenue Engine
- Review Bottleneck Tracker
- Confirm Next Actions Ledger
This sequence ensures:
• governance first
• capital second
• operations third
• movement always visible
Future Expansion
Future versions may include:
• AI-generated executive summaries
• automatic bottleneck detection
• cross-brain action routing
• real-time task sync with Supabase
• daily executive brief generation
• decision aging alerts
These features require separate approval.
Final Rule
The Executive Operations Board exists to make the MWMS ecosystem operable at the executive level.
HeadOffice must be able to see:
• what matters
• what is blocked
• what is risky
• what is ready
• what comes next
If the system cannot show this clearly, executive control weakens.
Drift Protection
The system must prevent:
• the board drifting into a reporting archive instead of a live executive surface
• operational clutter hiding urgent items
• governance alerts being buried beneath lower-priority information
• decision items being mixed vaguely with observation-only items
• bottlenecks remaining invisible because no single executive surface tracks them
• the board becoming an execution console rather than a coordination layer
The Executive Operations Board must remain immediate, visible, and action-oriented.
Architectural Intent
MWMS – Executive Operations Board exists to give HeadOffice a single executive coordination surface for live ecosystem attention management.
Its role is to bring together priorities, risks, decisions, bottlenecks, and next actions so the MWMS ecosystem can be steered with clarity rather than managed through scattered pages and fragmented operational awareness.
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 role, seven-board-zone structure, input sources, authority rules, recommended layout, operating logic, future expansion ideas, and final governance intent. Added Document Type, Scope, Definition / Rules structure, Drift Protection, and Architectural Intent sections.
Version: v1.0
Date: 2026-03-13
Author: MWMS HeadOffice
Change: Initial creation of MWMS – Executive Operations Board defining the live executive operating page for HeadOffice.
END – MWMS – EXECUTIVE OPERATIONS BOARD v1.1