Document Type: Runbook
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: HeadOffice dashboard wiring sequence
Parent: HeadOffice Brain
Last Reviewed: 2026-04-06
Purpose
This document defines the recommended build order for HeadOffice dashboards.
The purpose is to ensure early visibility of meaningful system signals while reducing unnecessary UI build complexity.
Dashboards should be wired in an order that delivers the highest coordination value first.
Early visibility improves decision clarity.
Early clarity improves build efficiency.
Build Order
Phase 1 — Core System Visibility
These panels provide immediate awareness of whether the system is functioning coherently.
HeadOffice Active Command Dashboard
Wire first panels:
System State Panel — Opportunity Flow State
source: Affiliate Brain Opportunity Queue
System State Panel — Testing Velocity State
source: Affiliate Brain Velocity Decision Engine
System State Panel — Signal Confidence State
source: Experimentation Brain Signal Confidence Framework
Risk Panel — Capital Risk Posture
source: Finance Brain Financial Risk Escalation Logic
Purpose:
confirm system is operating normally.
Phase 2 — Cross Brain Alignment
HeadOffice Cross Brain Status Board
Wire panels:
Dependency Panel — Affiliate ↔ Experimentation alignment
Dependency Panel — Affiliate ↔ Finance alignment
System State Panel — Research signal flow state
Watchlist Panel — emerging signals
Purpose:
confirm Brains remain aligned.
Phase 3 — Friction Visibility
HeadOffice Escalation & Blockers Overview
Wire panels:
Escalation Panel — cross-brain signal disagreement
Risk Panel — capital exposure constraint signals
Dependency Panel — stalled progression signals
Purpose:
identify structural pressure early.
Phase 4 — System Learning Visibility
HeadOffice Weekly System Movement Dashboard
Wire panels:
Movement Panel — stage progression movement
Movement Panel — new opportunities added
Summary Panel — weekly signal change overview
Purpose:
interpret system development over time.
Build Principle
Dashboards must:
prioritise interpretability
prioritise signal clarity
avoid visual complexity before signals exist
avoid premature UI optimisation
Signal visibility is more important than visual polish.
Clarity before aesthetics.
Structure before styling.
Relationship to Other Documents
Signal Surface Map defines signal origin.
Live Signal Routing Map defines signal destination.
Panel Definitions define UI structure.
Build Priority defines implementation order.
Architectural Intent
Build order ensures HeadOffice receives meaningful visibility as early as possible.
Early signal visibility improves:
debugging speed
coordination clarity
system confidence
future UI expansion decisions
Structured sequencing prevents wasted build effort.
Change Log
Version: v1.0
Date: 2026-04-06
Author: HeadOffice
Initial creation of dashboard wiring priority sequence for HeadOffice operational visibility layer.