Document Type: Specification
Status: Active
Authority: HeadOffice
Applies To: HeadOffice, All Brains via visibility layer
Parent: HeadOffice
Version: v1.1
Last Reviewed: 2026-04-29
Purpose
The HeadOffice Newsletter Intelligence Dashboard defines the UI structure and system behaviour for displaying, tracking, prioritising, and managing all newsletter-derived intelligence inside MWMS.
This dashboard ensures:
• all insights are visible
• no intelligence is lost
• extraction layers are clear
• routing decisions are traceable
• parking states are visible
• action types are easy to identify
• Brain impact is visible
• priority signals surface quickly
• system learning compounds over time
Without a dashboard:
• intelligence becomes fragmented
• decisions become invisible
• routing becomes unclear
• high-priority signals are missed
• system learning is lost
The dashboard converts newsletter intelligence into a controlled HeadOffice operational surface.
Scope
This specification applies to:
• all newsletter-derived insights
• all intake entries
• all extraction layer classifications
• all parking states
• all routing decisions
• HeadOffice visibility layer
This specification governs:
• UI layout
• data display structure
• filtering logic
• priority logic
• interaction flow
• status tracking
This specification does not govern:
• Brain-level execution
• plugin backend logic
• database schema
• newsletter extraction rules
Those are governed by separate MWMS pages.
Core Principle
All newsletter intelligence must be:
• visible
• structured
• trackable
• filterable
• prioritised
Visibility creates control.
Control enables scale.
Priority prevents overload.
Dashboard Layout Structure
The dashboard is divided into five core panels.
1. Intake Feed Panel
Purpose:
Display all incoming newsletter insights in a quick-scan stream.
Displays:
• Date
• Source
• Newsletter title
• Insight title
• Insight summary
• Extraction Layer
• Confidence
• Urgency
• Action Type
Features:
• newest first
• quick scan view
• click to expand full entry
• action type badge
• priority badge
The Intake Feed Panel must use Extraction Layer as the primary intelligence classification.
Signal Type may appear only as a secondary tag if required.
2. Classification Panel
Purpose:
Show structured classification of insights.
Displays:
• Insight
• Extraction Layer
• Primary Brain
• Supporting Brains
• Action Type
• Suggested Routing
• Confidence Level
• Urgency Level
Filters:
• Extraction Layer
• Primary Brain
• Supporting Brain
• Action Type
• Confidence
• Urgency
The Classification Panel exists to confirm that each insight has been interpreted correctly before routing or parking.
3. Parking Status Panel
Purpose:
Track where each insight currently sits.
Categories:
• Park
• Structured Capture
• Deferred
• Routing Preparation
• Review
• Rejected
Displays:
• Insight title
• Current parking state
• Action type
• Time in state
• Review timing
• Notes
This panel protects MWMS from raw ideas entering Brain systems too early.
4. Routing Panel
Purpose:
Show routing decisions and Brain assignments.
Displays:
• Primary Brain
• Supporting Brains
• Routing status
• Review status
• Brain Room thread status if available
• Brain request status if available
Status Indicators:
• Not Routed
• Routed
• Under Review
• Completed
• Escalated
Routing must only occur after structured classification.
No item should appear in this panel unless it has:
• extraction layer
• action type
• confidence level
• urgency level
• primary Brain where required
5. Strategic Signals Panel
Purpose:
Highlight high-impact and system-relevant insights.
Displays:
• Top signals
• Extraction Layer
• Cross-Brain impact
• Strategic relevance
• Urgency
• Confidence
• Escalation status
Criteria:
• high confidence
• high urgency
• multi-Brain impact
• compliance flag
• risk flag
• repeated signal pattern
• strategic relevance high
This panel is the HeadOffice signal awareness layer.
Priority Logic
The dashboard must surface priority using combined confidence and urgency.
Priority Levels:
High Priority
• confidence_level = high
• urgency_level = high
Review Priority
• confidence_level = high and urgency_level = medium
• confidence_level = medium and urgency_level = high
Monitor Priority
• confidence_level = medium and urgency_level = medium
• confidence_level = high and urgency_level = low
Low Priority
• confidence_level = low
• urgency_level = low
High Priority items must be visually surfaced in:
• Intake Feed Panel
• Strategic Signals Panel
• Dashboard summary cards
Action Type Visibility
Action Type must be treated as a primary dashboard control.
Action types:
• park
• review
• build_later
• reject
Each insight must display an Action Type badge.
Action Type controls whether an insight is:
• stored quietly
• routed for review
• held for future system build
• rejected as non-useful
Dashboard users must be able to filter and sort by Action Type.
Data Fields Structure
Each insight must include:
• ID
• Source
• Date Captured
• Newsletter Title
• Insight Title
• Extracted Insight
• Extraction Layer
• Why It Matters
• Signal Type
• Confidence Level
• Urgency Level
• Action Type
• Primary Brain
• Supporting Brains
• Parking State
• Routing Status
• Strategic Relevance
• Risk Flag
• Compliance Flag
• Review Timing
• Notes
Extraction Layer is required.
Signal Type is optional and secondary.
Interaction Flow
User workflow:
View Intake Feed
↓
Open insight
↓
Review extraction layer
↓
Review classification
↓
Confirm or adjust action type
↓
Assign parking state
↓
Prepare routing if required
↓
Send to Brain Room or Brain Request if required
↓
Record decision or next action
Filtering System
Dashboard must support filtering by:
• Source
• Date
• Newsletter title
• Extraction Layer
• Primary Brain
• Supporting Brain
• Confidence
• Urgency
• Priority Level
• Action Type
• Parking State
• Routing Status
• Risk Flag
• Compliance Flag
• Strategic Relevance
• Review Timing
Extraction Layer must be the primary system classification filter.
Signal Type may be used only as a secondary descriptive filter.
Search Functionality
Must allow:
• keyword search
• source search
• newsletter title search
• insight content search
• notes search
Sorting Options
• newest first
• highest priority
• highest urgency
• highest confidence
• by extraction layer
• by Brain
• by action type
• oldest parked first
Status Indicators
Each insight must show:
• Extraction Layer badge
• Confidence badge
• Urgency badge
• Priority badge
• Action Type badge
• Parking State badge
• Routing badge
Colour logic:
Green → high value or ready
Yellow → review or pending
Red → urgent, risk, or compliance concern
Grey → parked or inactive
Black or dark accent → rejected
Colour should support scanning only.
Status text must remain visible so meaning does not depend on colour alone.
Dashboard Summary Cards
The dashboard should include top-level summary cards.
Suggested cards:
• Total Insights Captured
• High Priority Signals
• Review Required
• Parked Insights
• Build Later Items
• Rejected Items
• Routed To Brain Room
• Compliance Flagged
• Risk Flagged
These cards help HeadOffice understand the system state quickly.
Notifications System Future Layer
Trigger alerts when:
• high priority signal appears
• high urgency signal appears
• multiple signals repeat
• compliance flag is true
• risk flag is true
• escalation required
• routing incomplete
• review item remains stuck too long
This is a future layer and should not be required for first implementation.
Integration With MWMS Systems
This dashboard connects to:
• MWMS Full Newsletter Intelligence Extraction Protocol
• HeadOffice Newsletter Intelligence Operating Protocol
• HeadOffice Newsletter Intelligence Intake Framework
• HeadOffice Newsletter Insight Parking System
• HeadOffice Newsletter Brain Routing Review Framework
• HeadOffice Newsletter Intelligence Supabase Schema Specification
• HeadOffice Newsletter Intelligence Brain Room Integration Specification
• MCR Intelligence Holding Area
• MCR Intelligence Log
• MCR Deferred Review Register
Plugin And UI Conversion Rule
This dashboard is:
Later Plugin or UI
It must not be manually recreated as static pages.
It should eventually become:
• WordPress admin dashboard
• Supabase-powered UI
• custom MWMS interface
The dashboard must remain connected to Supabase as system record.
Governance Role
HeadOffice uses this dashboard to:
• monitor intelligence flow
• maintain system visibility
• control routing discipline
• prevent chaos
• identify high-priority signals
• prevent missed opportunities
• ensure structured growth
HeadOffice owns dashboard visibility.
Specialist Brains may act on routed insights, but they do not own the original newsletter intelligence dashboard.
Drift Protection
The system must prevent:
• hidden insights
• duplicate entries
• missing extraction layer
• signal type replacing extraction layer
• missing classification
• untracked routing
• lost intelligence
• inconsistent states
• high-priority signals being buried
• dashboard records disconnected from Supabase
Dashboard visibility prevents system blindness.
Architectural Intent
This dashboard transforms MWMS into:
a live intelligence system
not static documentation.
It enables:
• continuous learning
• structured decision-making
• scalable intelligence management
• priority visibility
• real operational control
The dashboard ensures HeadOffice can see what matters, what is parked, what needs review, and what should be routed.
Change Log
Version: v1.1
Date: 2026-04-29
Author: HeadOffice
Change:
Updated dashboard specification to align with the HeadOffice Newsletter Intelligence Operating Protocol v1.1 and Supabase Schema Specification v1.1. Added Extraction Layer as the primary dashboard classification, retained Signal Type only as a secondary tag, elevated Action Type visibility, added priority logic using confidence and urgency, expanded filtering and sorting requirements, and added dashboard summary cards.
Version: v1.0
Date: 2026-04-28
Author: HeadOffice
Change:
Initial creation of HeadOffice Newsletter Intelligence Dashboard Specification defining UI structure, panel system, interaction flow, filtering logic, and integration requirements for managing newsletter-derived intelligence across MWMS.
Change Impact Declaration
Pages Created:
None
Pages Updated:
HeadOffice Newsletter Intelligence Dashboard Specification
Pages Deprecated:
None
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No
END HEAD OFFICE NEWSLETTER INTELLIGENCE DASHBOARD SPECIFICATION