Document Type: UI Structure
Status: Structural
Version: v1.0
Authority: HeadOffice
Applies To: All HeadOffice dashboards
Parent: HeadOffice UI Dashboard Layout Standard
Last Reviewed: 2026-04-06
Purpose
This document defines the standard panel types used across HeadOffice dashboards.
Panels are reusable UI interpretation surfaces that display structured signals originating from MWMS Brains.
Standardising panel definitions ensures:
consistent interpretation surfaces
consistent UI structure
reusable dashboard components
reduced wiring complexity
consistent cross-brain visibility
stable expansion of dashboard layer
Panels display signals.
Panels do not create signals.
Panels interpret structured outputs from Brain systems.
Scope
This document applies to:
HeadOffice Active Command Dashboard
HeadOffice Cross Brain Status Board
HeadOffice Escalation & Blockers Overview
HeadOffice Weekly System Movement Dashboard
Future HeadOffice dashboards must reuse these panel structures where possible.
Core Panel Types
1. System State Panel
Purpose:
Displays current structural state of a Brain system.
Examples:
opportunity flow state
testing readiness state
signal confidence state
capital exposure state
Typical signals:
stage progression signals
confidence classification signals
risk posture signals
Panel role:
provide rapid orientation of current condition.
2. Movement Panel
Purpose:
Displays structural movement occurring over time.
Examples:
opportunity progression changes
confidence level transitions
new experiment outcomes
capital readiness changes
Typical signals:
stage transitions
classification changes
new signals generated
Panel role:
make system learning visible.
3. Risk Panel
Purpose:
Displays survivability or stability related signals.
Examples:
capital exposure posture
statistical reliability concerns
structural instability indicators
dependency misalignment signals
Typical signals:
risk escalation indicators
confidence instability signals
capital constraint signals
Panel role:
increase early awareness of structural instability.
4. Dependency Panel
Purpose:
Displays relationships between Brains affecting decision flow.
Examples:
Affiliate dependency on Experimentation validation
Affiliate dependency on Finance capital approval
Research dependency influencing opportunity intake
Typical signals:
cross-brain signal alignment indicators
dependency constraint signals
Panel role:
make cross-brain coordination visible.
5. Escalation Panel
Purpose:
Displays signals requiring interpretation or clarification.
Examples:
confidence disagreement signals
capital restriction conflicts
decision routing uncertainty
Typical signals:
escalation indicators
blocked progression signals
Panel role:
highlight coordination pressure.
6. Watchlist Panel
Purpose:
Displays signals requiring observation but not immediate action.
Examples:
emerging opportunity signals
weak but interesting behavioural signals
early research pattern clusters
Typical signals:
early-stage signals
weak classification signals
emerging pattern indicators
Panel role:
preserve visibility of developing signals.
7. Summary Panel
Purpose:
Provides condensed view of structural movement across a defined time window.
Examples:
weekly movement summary
stage movement count
confidence change frequency
Typical signals:
movement aggregates
classification summaries
Panel role:
support structured periodic review.
Panel Behaviour Rules
Panels must:
display structured signals only
avoid subjective interpretation language
remain consistent with Brain authority boundaries
remain consistent with Canon definitions
avoid creating new decision logic
remain reusable across dashboards
Panels must not:
override Brain authority
create new classifications
alter signal meaning
introduce non-structured interpretation
Panels visualise structure.
Structure defines interpretation boundaries.
Relationship to Signal Routing
Panel definitions describe:
how signals appear visually.
Routing map describes:
which signals reach each panel.
Signal Surface Map describes:
where signals originate.
All three must remain aligned.
Architectural Intent
Standardised panel definitions ensure HeadOffice dashboards remain:
consistent
interpretable
expandable
governable
Stable UI structure reduces future rebuild complexity.
Consistent panels support faster wiring.
Reusable panels support system scale.
Change Log
Version: v1.0
Date: 2026-04-06
Author: HeadOffice
Initial creation of standard HeadOffice panel definitions to support consistent dashboard construction across MWMS.