Document Type: Dashboard Spec
Status: Active
Authority: HeadOffice
Parent: HeadOffice
Version: v1.0
Last Reviewed: 2026-04-21
HeadOffice Active Command Dashboard
Purpose
The HeadOffice Active Command Dashboard defines the primary command surface used to interpret live system posture and identify where immediate attention is required across MWMS.
This page exists to give HeadOffice a single operational view of:
current decision pressure
active escalations
high-priority signals
blocked progression states
capital sensitivity posture
testing integrity posture
cross-brain action readiness
The Active Command Dashboard is not a passive reporting page.
It is the executive action-orientation layer.
Its role is to help HeadOffice identify what requires review, what requires intervention, and what may proceed without disruption.
Clarity of active system posture improves decision speed.
Decision speed improves coordination quality.
Scope
This dashboard spec applies to live or near-live command visibility across:
Affiliate Brain
Ads Brain
Experimentation Brain
Finance Brain
Research Brain
SIT Brain
cross-brain escalation chains
HeadOffice review requirements
This page governs the structure of a command dashboard.
It does not define the originating logic of the signals themselves.
It interprets already-defined structural outputs from MWMS Brains and connector systems.
Command Role
The Active Command Dashboard exists to answer:
What needs attention now?
What is blocked?
What is escalating?
What is close to progression?
What is unsafe to progress?
What requires executive visibility before movement occurs?
This dashboard supports action readiness.
It does not replace Brain authority.
It improves oversight across active system conditions.
Dashboard Visibility Domains
The Active Command Dashboard may display panels relating to:
active requests requiring review
current escalations
blocked progression states
signal confidence posture
capital exposure posture
testing validity posture
risk posture requiring action
cross-brain dependency pressure
urgent unresolved issues
high-priority opportunity states
The dashboard should prioritise active decision relevance over passive historical detail.
Primary Panel Types
Active Requests Panel
Displays currently open or recently routed Brain Requests requiring visibility.
May include:
request origin
destination Brain
priority
status
review owner
time open
escalation flag
Purpose:
show what active work is currently moving through connector architecture.
Escalations Panel
Displays requests or system conditions currently escalated to:
HeadOffice
Finance Brain
SIT Brain
other governing authority
Purpose:
show where authority transfer has already been triggered.
Blockers Panel
Displays unresolved constraints preventing system progression.
Examples:
missing evidence
financial restriction
tracking weakness
test integrity issue
compliance risk
dependency not satisfied
Purpose:
show what is actively stopping system movement.
Signal Pressure Panel
Displays active decision signals requiring interpretation.
Examples:
opportunity signal rising
signal confidence strengthening
creative instability emerging
capital risk increasing
research signal density changing
Purpose:
show where system pressure is building.
Progression Readiness Panel
Displays opportunities or initiatives approaching next-stage readiness.
Examples:
test ready
scaling review ready
finance review ready
research handoff ready
connector routing ready
Purpose:
show what may soon require decision.
Risk and Integrity Panel
Displays issues affecting structural safety.
Examples:
SIT warnings
measurement integrity concerns
high attribution uncertainty
methodological weakness
signal inconsistency
request lineage failure
Purpose:
protect governance quality before progression occurs.
Command Interpretation Principles
The dashboard must emphasise:
urgency
decision relevance
visibility of unresolved issues
clear ownership
traceable signal origin
connector-lineage safety
readiness vs blockage distinction
The dashboard must not become a passive analytics wall.
It must support governed action.
Relationship to Connector Architecture
The Active Command Dashboard interprets structured outputs from:
Brain Requests
Tasks
Results
Signals
Escalations
as defined in:
MWMS Brain Connector Architecture
This means the dashboard must read:
request state
review state
escalation state
result return state
blockage state
progression state
The dashboard visualises connector activity.
It does not replace connector logic.
Relationship to Other HeadOffice Pages
HeadOffice Cross Brain Status Board
provides broad structural posture across multiple Brains.
HeadOffice Active Command Dashboard
provides immediate action-oriented oversight.
HeadOffice Escalation & Blockers Overview
provides deeper visibility into blocker and escalation conditions.
HeadOffice Weekly System Movement Dashboard
provides movement history and pacing review.
HeadOffice Cross Brain Decision Overview
provides logic for interpreting major cross-brain decisions.
Active Command Dashboard is the live executive control surface.
Signal Sources
Primary interpreted inputs may include:
Affiliate Brain Decision Structure
Affiliate Brain Velocity Decision Engine
Affiliate Brain Stage Progression Protocol
Affiliate Brain Scaling Readiness Indicators
Experimentation Brain Signal Confidence Framework
Experimentation Brain Statistical Confidence Framework
Experimentation Brain Stage Progression Protocol
Finance Brain Capital Allocation Ladder
Finance Brain Financial Risk Escalation Logic
Finance Brain Dashboard Financial Signal Indicators
Research Brain Affiliate Handoff Protocol
Research Brain Opportunity Signal Framework
Research Brain Research Verdict Framework
SIT Brain integrity and enforcement signals where available
Signals must remain traceable to originating Brain structures.
Governance Role
HeadOffice interprets active system posture through this dashboard.
The dashboard supports:
oversight
intervention timing
coordination discipline
escalation handling
readiness recognition
The dashboard does not grant new authority to HeadOffice.
It improves visibility of when existing authority should be exercised.
Drift Protection
The system must prevent:
dashboard panels displaying signals without traceable source
active command views becoming passive historical summaries
request states becoming invisible after routing
escalations appearing without owner clarity
blockers being hidden behind green-status summaries
high-priority issues being mixed with low-value noise
Command visibility must remain clear, urgent, and governable.
Architectural Intent
The HeadOffice Active Command Dashboard exists to make MWMS operationally steerable.
Its role is to convert signal visibility into action readiness so HeadOffice can intervene where needed without relying on memory, scattered navigation, or informal updates.
A command surface must show:
what is moving
what is stuck
what is dangerous
what is nearing progression
what requires decision now
This dashboard is the executive live-control layer for MWMS.
Change Log
Version: v1.0
Date: 2026-04-21
Author: HeadOffice
Change:
Initial creation of HeadOffice Active Command Dashboard defining the primary executive action-orientation surface for live system posture, escalations, blockers, and progression readiness.
END HEADOFFICE ACTIVE COMMAND DASHBOARD v1.0
CHANGE IMPACT
Pages Created:
None
Pages Updated:
HeadOffice Active Command Dashboard
Pages Deprecated:
None
Registries Requiring Update:
HeadOffice Page Registry
Canon Version Update Required:
No
Change Log Entry Required:
No