Document Type: Architecture
Status: UI Architecture
Version: v1.2
Authority: MWMS HeadOffice
Applies To: HeadOffice UI and MWMS visibility layer
Parent: HeadOffice Brain
Last Reviewed: 2026-04-16
Purpose
This document defines the locked navigation and page architecture for the HeadOffice interface inside MWMS.
Its purpose is to ensure that HeadOffice presents as:
system governance and executive visibility layer
rather than:
WordPress admin page collection
plugin utility interface
unstructured page list
HeadOffice must feel like a governance console.
It must communicate:
clarity
structure
authority
restraint
system discipline
This document prevents UI drift as MWMS expands.
Scope
This architecture applies to:
HeadOffice navigation structure
HeadOffice page families
dashboard placement
Brain visibility architecture
governance-safe UI grouping
cross-brain reporting structure
This document governs how HeadOffice pages are organised, grouped, and surfaced.
It does not govern:
live operational execution
Brain authority logic
campaign actions
capital approval
experiment validation authority
detailed component styling rules
These remain governed by Brain canons and supporting architecture documents.
Core UI Principle
HeadOffice exists to provide:
executive visibility
governance oversight
system health awareness
structural monitoring
controlled drill-down into Brain reporting
HeadOffice does not exist to act as:
execution interface
plugin utility container
general admin workspace
campaign control panel
HeadOffice is the system visibility layer.
HeadOffice UI Layer Model
HeadOffice UI is structured into three primary layers.
Layer 1 — Global Dashboard
Executive system overview.
Displays:
system health
lifecycle movement
governance alerts
capital exposure
signal summaries
This is the primary command visibility surface.
Layer 2 — Brain Reporting Pages
Each Brain has its own reporting page.
These pages expose domain-specific system intelligence.
These pages remain observational.
They do not provide execution authority.
Each Brain page follows the Brain Page Standard.
Layer 3 — Governance and Architecture Pages
These pages expose structural understanding of MWMS.
They describe:
system structure
authority logic
interaction logic
governance structure
These are not operational dashboards.
They are system reference surfaces.
Locked Navigation Structure
HeadOffice
Dashboard
Revenue Pipeline
Signals
Brains
Affiliate Brain
Ads Brain
Content Brain
Product Brain
Sales Brain
Partnership Brain
PPL Brain
Conversion Brain
Finance Brain
Experimentation Brain
SIT Brain
Customer Brain
Data Brain
Automation Brain
AIBS Brain
Reports
Weekly Changes
Brain Health
Capital Exposure
Lifecycle Distribution
System Architecture
Brain Interaction Map
Brain Interaction Protocol
Request Routing Map
Decision Authority Matrix
System Data Flow Map
Strategic Vision and Horizon
Governance
HeadOffice Canon
System Alerts
Override Logs
Change Intelligence
Kaizen Log
Navigation Intent
The navigation must reflect MWMS governance logic.
Dashboard
Top-level executive visibility surface.
Answers:
What is happening now?
Where are alerts forming?
What is moving through the system?
Which Brains require attention?
Revenue Pipeline
Primary lifecycle visibility surface.
Unifies visibility across:
Affiliate Brain
Ads Brain
Experimentation Brain
Finance Brain
Product Brain
Sales Brain
Partnership Brain
Lifecycle movement must remain visible from intake through scaling.
Signals
Central visibility surface for:
cross-brain signals
external change signals
system drift signals
improvement signals
This page supports governance awareness.
It must not become an execution interface.
Brains Section
Groups all Brain-level reporting pages.
Reinforces concept that HeadOffice oversees specialised systems.
Brain pages remain disciplined reporting surfaces.
Reports Section
Contains recurring structured summaries.
These pages provide aggregated visibility rather than structural maps.
Examples:
Weekly Changes
Brain Health
Capital Exposure
Lifecycle Distribution
Reports remain read-oriented.
System Architecture Section
Provides structural understanding of MWMS design.
Explains:
how Brains interact
how authority flows
how routing occurs
These pages support system comprehension.
Governance Section
Provides oversight controls and escalation visibility.
Contains constitutional references.
Examples:
HeadOffice Canon
System Alerts
Override Logs
Change Intelligence
Kaizen Log
Governance pages define system discipline.
Standard Page Families
All HeadOffice pages belong to one of the following families.
Dashboard Pages
Provide executive visibility.
Examples:
Dashboard
Revenue Pipeline
Signals
Brain Health
Capital Exposure
Lifecycle Distribution
Brain Pages
Provide domain-specific reporting.
Examples:
Affiliate Brain
Ads Brain
Content Brain
Product Brain
Sales Brain
Partnership Brain
Finance Brain
Experimentation Brain
SIT Brain
Customer Brain
Data Brain
Automation Brain
AIBS Brain
Architecture Pages
Provide system design visibility.
Examples:
Brain Interaction Map
Request Routing Map
Decision Authority Matrix
System Data Flow Map
Strategic Vision and Horizon
Governance Pages
Provide governance reference.
Examples:
HeadOffice Canon
System Alerts
Override Logs
Change Intelligence
Kaizen Log
Global Dashboard Standard
The Global Dashboard is the executive home page.
It should present:
Top band
Executive system summary
Examples:
Active Brains
Alerts Open
Opportunities In Pipeline
Capital Exposure State
Active Testing Count
Second band
Revenue pipeline distribution
Third band
Brain health signals
Fourth band
Capital exposure signals
Fifth band
System changes
Dashboard must remain executive in nature.
Revenue Pipeline Page Standard
Displays lifecycle movement across Brains.
Must visualise:
Intake
Evaluation
Approved for Test
Testing
Iteration
Scaling
Stabilisation
Paused
Retired
Must not allow stage manipulation.
Brain Page Standard
Each Brain page must follow shared structure.
Brain Header
Status Controls
Executive Summary Cards
Domain Panels
Cross Brain Influence Indicators
Risk Panel
Drill-down Links
Pages must feel unified but distinct.
Similar but Distinct Rule
All Brain pages share structure.
Each Brain expresses domain-specific signals.
Similarity improves readability.
Distinction prevents confusion.
Visual Direction Lock
HeadOffice must visually feel like:
professional internal system
governance console
executive decision interface
not:
generic WordPress admin
plugin configuration pages
unstructured dashboards
WordPress Constraint Rule
Implementation occurs inside WordPress.
Visual discipline must still be maintained.
Temporary technical constraints must not create structural drift.
Menu Discipline Rule
Pages appear in navigation only if they serve governance visibility roles.
No page appears simply because it exists.
Navigation must remain disciplined.
Future Expansion Rule
Future Brains must be approved before being added to navigation.
Potential additions:
Compliance Brain
Community Brain
API Brain
Video Brain
Education Brain
All new pages must inherit the same structural logic.
Final Rule
HeadOffice UI must present MWMS as a governed system.
Navigation must remain structured.
Brain pages must remain consistent.
Governance must remain visible.
System clarity must not degrade as complexity increases.
Drift Protection
The system must prevent:
navigation sprawl
WordPress admin drift
page duplication in menus
dashboards becoming execution tools
inconsistent page grouping
Brain pages losing shared structure
UI becoming cluttered as system expands
Navigation discipline protects ecosystem clarity.
Architectural Intent
HeadOffice UI Navigation and Page Architecture defines the structural blueprint of the HeadOffice visibility layer.
Its role is to ensure MWMS presents as a coherent governance console rather than a loose page collection.
Structured navigation improves:
system readability
governance clarity
scalability
long-term maintainability
Change Log
Version: v1.2
Date: 2026-04-16
Author: MWMS HeadOffice
Expanded navigation structure to include:
Content Brain
Product Brain
Sales Brain
Partnership Brain
Automation Brain
Customer Brain
Data Brain
Signals dashboard
Change Intelligence
Kaizen log
Aligned navigation with:
Brain Interaction Map v1.3
Request Routing Map v1.2
Signals Dashboard v1.2
Offer Lifecycle Dashboard v1.2
Maintained governance-safe UI discipline.