Document Type: Standard
Status: UI Design Standard
Version: v1.2
Authority: MWMS HeadOffice
Applies To: All Brain reporting pages
Parent: HeadOffice UI – Navigation & Page Architecture
Last Reviewed: 2026-04-16
Purpose
This document defines the standard structural layout used for all Brain reporting pages inside HeadOffice.
Its purpose is to ensure that all Brain pages:
feel like part of one coherent system
follow a consistent visual structure
remain easy to navigate and understand
preserve authority boundaries between Brains
present intelligence clearly without enabling execution-layer drift
Without this standard, Brain pages risk becoming inconsistent, confusing, and difficult to interpret.
This document ensures that every Brain page shares a common structure while still expressing its domain-specific intelligence.
The Brain Page Standard allows HeadOffice to interpret multiple Brains quickly without cognitive friction.
Consistency improves governance clarity.
Scope
This standard applies to:
all HeadOffice Brain reporting pages
dashboard-style Brain visibility pages
cross-Brain layout consistency
structural UI presentation rules for Brain pages
future Brain dashboard pages added to the MWMS ecosystem
signal visibility panels
summary card structures
risk and alert presentation patterns
This document governs the structural layout and presentation logic of Brain reporting pages inside HeadOffice.
It does not govern:
live operational execution
Brain authority logic by itself
campaign settings
capital approval
statistical validation
backend data integration logic
signal generation logic
routing logic
Those remain governed by the relevant Brain canons, HeadOffice governance, Signals Dashboard specification, and MWMS architecture documents.
Core Principle
All Brain pages must follow the same structural template.
However, each Brain page must still clearly reflect its own domain responsibilities.
This creates a balance between:
system consistency
domain clarity
HeadOffice must be able to move between Brains without needing to relearn interface logic.
Pages must feel unified but not interchangeable.
Brain Page Layout Structure
Every Brain page must follow this layout sequence:
Brain Header
Status and Time Window Controls
Executive Summary Cards
Domain Intelligence Panels
Cross-Brain Influence Indicators
Risk and Alert Panel
Reports and Drill-down Links
This structure is mandatory for all Brain pages.
Section 1 — Brain Header
The Brain Header identifies the Brain being viewed and its current system condition.
The header must include:
Brain Name
Current Status
optional short description of the Brain role
Example:
Affiliate Brain
Opportunity Intelligence System
Status: Healthy
Status labels should use simple system states such as:
Healthy
Watch
Risk
Degraded
Stable
Informational
These states are informational only.
They must not trigger system actions directly.
Section 2 — Status and Time Window Controls
This section allows the viewer to change the time window used by the page.
Purpose:
Provide visibility across different operational timeframes.
Recommended windows:
7 days
30 days
90 days
If a Brain does not rely on time-based reporting, this section may be omitted.
Time-window consistency improves cross-brain interpretability.
Section 3 — Executive Summary Cards
This section provides the primary signal indicators for the Brain.
These cards summarise the most important domain signals.
The number of cards should normally remain between 4 and 6.
Cards must display:
metric title
current value
optional status indicator
optional trend indicator
Example layout:
Opportunities In Intake
18
Under Evaluation
9
Approved For Test
4
Rejected
5
Metrics must be domain-specific.
Generic cards must be avoided.
Cards should reflect signals that influence decisions.
Section 4 — Domain Intelligence Panels
This is the primary working area of the page.
Panels must reflect the specific intelligence role of the Brain.
Panels may include:
tables
status summaries
pipeline visualisations
experiment summaries
classification summaries
lifecycle distributions
signal interpretation summaries
Panels must remain visibility-focused rather than control-oriented.
Panels must help HeadOffice interpret signals without performing operational actions.
Section 5 — Cross-Brain Influence Indicators (NEW)
This section highlights signals originating from other Brains that influence the current Brain’s performance environment.
Examples:
Content Brain influence on Ads Brain performance
Product Brain influence on Sales performance
Partnership Brain influence on capability expansion
Automation Brain influence on workflow reliability
Research Brain influence on interpretation clarity
Customer Brain influence on lifecycle understanding
Finance Brain influence on scaling stability
Cross-brain visibility improves system-level understanding.
This section must remain interpretive rather than operational.
Section 6 — Risk and Alert Panel
Every Brain page must contain a section dedicated to structural risk or alert visibility.
This panel surfaces warnings relevant to that Brain.
Examples include:
lifecycle violations
experiment discipline issues
capital exposure concerns
structural rule violations
system integrity alerts
automation reliability risks
dependency exposure alerts
governance warnings
This panel reinforces the governance function of HeadOffice.
Risk visibility must remain clear and consistent across all Brains.
Section 7 — Reports and Drill-down Links
The final section of a Brain page may provide links to deeper reporting views.
Examples:
detailed reports
historical logs
extended analysis pages
experiment registries
lifecycle logs
classification detail pages
These links should remain minimal.
The Brain page itself should already provide the essential signals needed for oversight.
Similar but Distinct Rule
All Brain pages must feel like part of one system.
However, they must not look identical.
Two rules apply simultaneously.
Similarity Requirement
All Brain pages must share the same visual framework.
This includes:
consistent page spacing
identical card design
consistent panel layout
common heading hierarchy
shared typography style
standardised status badges
consistent alert styling
consistent signal grouping logic
consistent summary card layout
consistent signal interpretation logic
This ensures the system feels unified.
Distinction Requirement
Each Brain page must still clearly reflect its domain.
Distinction should appear through:
page titles
panel names
summary card metrics
domain terminology
signal naming
classification language
For example:
Affiliate Brain panels reference opportunities and evaluation.
Ads Brain panels reference campaigns and experiments.
Finance Brain panels reference exposure and risk.
Content Brain panels reference signal feedback and authority growth.
Product Brain panels reference capability stability and feature priorities.
Sales Brain panels reference progression and expectation alignment.
Partnership Brain panels reference leverage and collaboration stability.
Automation Brain panels reference workflow reliability and trigger coordination.
Distinct language prevents confusion between Brains.
Brain-Specific Intent Examples
Each Brain emphasises different signals.
Affiliate Brain Page
Focus areas:
Opportunity Intake
Evaluation Queue
Viability Analysis
Classification State
Testing Readiness
Represents the front of the revenue pipeline.
Ads Brain Page
Focus areas:
Campaign Health
Active Experiments
Creative Performance
Iteration State
Scaling Candidates
Represents traffic acquisition engine.
Finance Brain Page
Focus areas:
Active Capital Exposure
Exposure Distribution
Scaling Approval Queue
Risk Levels
Runway Awareness
Protects financial survivability.
Experimentation Brain Page
Focus areas:
Experiment Registry
Validation Status
Statistical Discipline
Test Outcomes
Confidence Signals
Protects learning reliability.
SIT Brain Page
Focus areas:
System Integrity Alerts
Structural Violations
Rule Enforcement
Drift Detection
Incident Logs
Protects system architecture.
Content Brain Page (NEW)
Focus areas:
Content Signal Feedback
Topic Coverage Stability
Authority Growth Signals
Content Optimisation Signals
Education Signal Strength
Improves signal quality across system.
Product Brain Page (NEW)
Focus areas:
Feature Priority Signals
Capability Stability
Feedback Integration
Evolution Signals
Delivery Reliability
Defines capability structure.
Sales Brain Page (NEW)
Focus areas:
Qualification Stability
Expectation Alignment Signals
Progression Stability
Conversion Readiness Signals
Pipeline Stability
Stabilises revenue conversion.
Partnership Brain Page (NEW)
Focus areas:
Partner Stability Signals
Leverage Opportunities
Distribution Influence
Dependency Exposure
Collaboration Lifecycle
Expands external capability.
Automation Brain Page (NEW)
Focus areas:
Workflow Stability
Trigger Reliability
Dependency Coordination
Integration Health
Automation Continuity
Supports execution infrastructure.
Visual System Requirements
All Brain pages must follow the same visual design system.
Required qualities include:
clear information hierarchy
strong section titles
clean card layout
consistent padding and spacing
readable typography
minimal visual clutter
consistent signal formatting
consistent alert formatting
The interface must feel like a professional internal system dashboard.
Status Colour Use
Status colours must represent system state.
Recommended pattern:
Green — Healthy
Amber — Watch
Red — Risk
Blue — Informational
Colour must support structure rather than replace it.
Signal clarity must not depend solely on colour.
WordPress Constraint Rule
These pages currently exist inside WordPress admin.
Despite this constraint, Brain pages must still aim for the quality of a professional internal governance dashboard.
The interface must not resemble generic plugin configuration pages.
HeadOffice must feel like an internal operating system.
Future Brain Compatibility
This page standard is designed to support future Brains.
Potential additions may include:
Compliance Brain
Customer Brain
Research Brain
Data Brain
Community Brain
API Brain
Video Brain
When new Brains are added, they must inherit this page structure.
Consistency must be preserved across expansion.
Final Rule
Brain pages must express intelligence clearly.
They must remain:
consistent
structured
readable
professional
governance-safe
HeadOffice must feel like a coherent system console rather than a collection of unrelated admin pages.
Drift Protection
The system must prevent:
Brain pages drifting into unrelated layouts
visibility pages becoming operational control surfaces
different Brains using conflicting dashboard structure patterns
generic cards replacing domain-specific intelligence
visual inconsistency weakening system coherence
future Brain pages being added without inheriting the standard layout
signal panels being used as execution interfaces
structure weakening governance clarity
Brain reporting pages must remain visually consistent and structurally predictable.
Architectural Intent
HeadOffice UI Brain Page Standard exists to define a shared presentation framework for Brain reporting pages so HeadOffice can observe multiple systems through a coherent interface without losing domain clarity.
Its role is to ensure MWMS appears as a unified internal operating system while allowing each Brain to express the signals most relevant to its domain.
Consistency improves interpretability.
Interpretability improves decision quality.
Decision quality improves system stability.
Change Log
Version: v1.2
Date: 2026-04-16
Author: MWMS HeadOffice
Expanded standard to support newer Brains:
Content Brain
Product Brain
Sales Brain
Partnership Brain
Automation Brain
Added Cross-Brain Influence Indicators section.
Aligned terminology with Signals Dashboard v1.2.
Aligned terminology with Brain Interaction Map v1.3.
Aligned terminology with Request Routing Map v1.2.
Improved support for signal-based interpretation across system layers.
Maintained consistency with original layout structure.
END — HeadOffice UI Brain Page Standard v1.2