Document Type: Standard
Status: UI Design Standard
Version: v1.1
Authority: MWMS HeadOffice
Applies To: All Brain reporting pages
Parent: HeadOffice UI – Navigation & Page Architecture
Last Reviewed: 2026-03-15
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
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.
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
This document governs the structural layout and presentation logic of Brain reporting pages inside HeadOffice.
It does not govern:
• live operational execution
• Brain authority by itself
• campaign settings
• capital approval
• statistical validation
• backend data integration logic
Those remain governed by the relevant Brain canons, HeadOffice governance, and supporting architecture documents.
Definition / Rules
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
The system must feel unified, but pages must never feel interchangeable.
Brain Page Layout Structure
Every Brain page must follow this layout sequence:
• Brain Header
• Status & Time Window Controls
• Executive Summary Cards
• Domain Intelligence Panels
• Risk & Alert Panel
• Reports / 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
These states are informational only.
They must not trigger system actions directly.
Section 2 – Status & 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
These windows should remain consistent across Brain pages where time-based reporting exists.
If a Brain does not require time windows, the control may be omitted.
Section 3 – Executive Summary Cards
This section provides the top indicators for the Brain.
These cards summarise the most important signals from that Brain.
The number of cards should normally remain between 4 and 6.
Cards must display:
• metric title
• current value
• optional status indicator
Example layout:
Opportunities In Intake
18
Under Evaluation
9
Approved For Test
4
Rejected
5
The exact metrics must be tailored to the Brain’s domain.
Generic cards must be avoided.
Section 4 – Domain Intelligence Panels
This is the primary working area of the page.
Panels in this section must reflect the specific role of the Brain.
Panels may include:
• tables
• status summaries
• pipeline visualisations
• experiment summaries
• classification summaries
Each Brain must define panels relevant to its responsibilities.
Panels must remain focused on visibility rather than operational control.
Section 5 – Risk & 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
This panel reinforces the governance function of HeadOffice.
It must remain visible and clear.
Section 6 – Reports & 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
• data exports where appropriate
These links should remain minimal.
The Brain page itself should already provide the essential information 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
This ensures that the system feels professional and unified.
Distinction Requirement
Each Brain page must still clearly reflect its domain.
Distinction should appear through:
• page titles
• panel names
• summary card metrics
• terminology used on the page
• domain-specific alerts
For example:
Affiliate Brain panels should reference opportunities and evaluation.
Ads Brain panels should reference campaigns and experiments.
Finance Brain panels should reference exposure and risk.
This prevents page confusion.
Brain-Specific Intent
Each Brain page should emphasise different signals.
Affiliate Brain Page
Focus areas:
• Opportunity Intake
• Evaluation Queue
• Viability Analysis
• Classification State
• Testing Readiness
This page represents the front end of the revenue pipeline.
Ads Brain Page
Focus areas:
• Campaign Health
• Active Experiments
• Creative Performance
• Iteration State
• Scaling Candidates
This page represents the traffic acquisition engine.
Finance Brain Page
Focus areas:
• Active Capital Exposure
• Exposure Distribution
• Scaling Approval Queue
• Risk Levels
• Runway Awareness
This page protects financial survivability.
Experimentation Brain Page
Focus areas:
• Experiment Registry
• Validation Status
• Statistical Discipline
• Test Outcomes
• Meta-study Signals
This page enforces experiment integrity.
SIT Brain Page
Focus areas:
• System Integrity Alerts
• Structural Violations
• Rule Enforcement
• Drift Detection
• Incident Logs
This page protects system architecture and rules.
AIBS Brain Page
Focus areas:
• Automation Status
• Workflow Health
• System Uptime
• AI Workforce Visibility
• Operational Stability Alerts
This page monitors automation 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
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 never replace structure.
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 operations dashboard.
The interface must not resemble generic plugin configuration pages.
Future Brain Compatibility
This page standard is designed to support future Brains.
Potential additions may include:
• Research Brain
• Product Brain
• PPL Brain
• Opportunity Brain
• Compliance Brain
When new Brains are added, they must inherit this page structure.
Final Rule
Brain pages must express the intelligence of each system clearly.
They must remain:
• consistent
• structured
• readable
• professional
HeadOffice must feel like a coherent governance console rather than a collection of unrelated admin pages.
The Brain Page Standard ensures that MWMS presents as a disciplined system.
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
Brain reporting pages must remain visually consistent, structurally predictable, and governance-safe.
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 make the MWMS governance console feel unified, disciplined, and readable while still allowing each Brain page to express the signals that matter most to its own role.
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 principle, layout sequence, section definitions, similarity-versus-distinction logic, Brain-specific intent, visual system requirements, WordPress constraint rule, future compatibility note, and final rule. Added standard document header, Scope, Definition / Rules structure, Drift Protection, and Architectural Intent sections.
Version: v1.0
Date: 2026-03-13
Author: MWMS HeadOffice
Change: Initial creation of HeadOffice UI – Brain Page Standard defining the standard structural layout for all Brain reporting pages inside HeadOffice.
END – HEADOFFICE UI – BRAIN PAGE STANDARD v1.1