Document Type: Framework
Status: Active
Authority: HeadOffice
Applies To: HeadOffice, All Brains (via structured routing)
Parent: HeadOffice
Version: v1.1
Last Reviewed: 2026-04-29
Purpose
The HeadOffice Newsletter Brain Routing Review Framework defines how newsletter-derived intelligence is evaluated and routed to the correct Brain for structured review.
This framework ensures:
• insights are routed to the correct Brain
• Brain authority boundaries are respected
• duplicate routing is avoided
• insights are not misinterpreted
• routing is prioritised correctly
• reinforced signals are escalated
• system-level patterns are recognised
• Brain overload is prevented
• system-wide consistency is maintained
• all routing decisions remain visible to HeadOffice
Without routing discipline:
• wrong Brains receive insights
• authority boundaries break
• duplicated analysis occurs
• execution quality drops
• system reliability degrades
• high-value signals are missed
• low-value signals create noise
This framework converts structured insights into correct, prioritised Brain-level inputs.
Scope
This framework applies to:
• all newsletter insights marked for Review
• all insights exiting the Parking System
• all cross-Brain routing decisions
• reinforced and repeated signals
• pattern-level intelligence
This framework governs:
• routing decision logic
• Brain selection
• routing priority
• pattern escalation
• routing visibility
• routing outcomes
This framework does not govern:
• Brain-level execution
• final decisions within Brains
• financial approvals
• campaign actions
Core Principle
Routing must occur before analysis and must respect Brain authority.
Routing must also respect:
• priority
• signal strength
• system impact
No Brain may receive an insight outside its defined role.
Routing discipline ensures structural integrity and scalability of MWMS.
Routing Process
All insights marked for Review must follow:
Insight Structured (Intake)
↓
Parking Decision Completed
↓
Routing Review Triggered
↓
Priority Evaluated
↓
Signal Strength Evaluated
↓
Primary Brain Identified
↓
Supporting Brain Identified (if required)
↓
Routing Decision Confirmed
↓
Insight Routed
↓
Outcome Recorded
Routing Priority Layer (New)
Routing must be influenced by priority.
Priority is derived from:
• confidence level
• urgency level
Routing categories:
High Priority
• confidence = high
• urgency = high
Action:
→ Immediate Review Routing
Review Priority
• high + medium
• medium + high
Action:
→ Scheduled Review Routing
Monitor Priority
• medium + medium
• high + low
Action:
→ Monitoring Routing
Low Priority
• low confidence
• low urgency
Action:
→ Park or Reject
Reinforced Signal Rule (New)
Routing must account for repeated signals.
If the same signal appears across:
• multiple sources
• multiple days
• multiple contexts
Then:
• confidence increases
• urgency may increase
• routing level escalates
Example:
First signal → Monitoring
Second signal → Scheduled Review
Third signal → Immediate Review
Repeated signals must not be treated as noise.
Pattern Routing Rule (New)
If multiple insights point to a single underlying pattern:
→ route as Strategic Review
Examples:
• AI agents becoming infrastructure
• AI tools becoming commoditised
• infrastructure consolidation trends
Pattern routing rules:
• must be identified by HeadOffice
• may override individual insight routing
• must route to Strategy Brain or AIBS Brain
Primary Brain Selection
Each insight must have one Primary Brain.
The Primary Brain is responsible for:
• interpreting the insight
• evaluating relevance
• deciding next action
Examples:
• monetisation signal → Affiliate Brain
• tool capability → Research Brain
• compliance update → Compliance Brain
• financial implication → Finance Brain
• execution impact → Ads or Content Brain
• strategic implication → Strategy Brain
• AI system impact → AIBS Brain
AIBS Brain Priority Rule (New)
If an insight impacts:
• AI systems
• agents
• infrastructure
• workflows
• automation
Then:
→ AIBS Brain must be Primary or Supporting
AIBS Brain is critical for system evolution signals.
Supporting Brain Logic
Some insights require multiple Brains.
In these cases:
• one Primary Brain must still be assigned
• additional Brains are marked as Supporting
Supporting Brains:
• may contribute insight
• must not override Primary Brain
Routing Decision Questions
HeadOffice must evaluate:
Which Brain owns this domain?
Does this insight affect decision-making?
Does this insight affect execution?
Does this insight affect financial risk?
Does this insight affect system structure?
Does this insight affect multiple Brains?
Is this a repeated or reinforced signal?
Is this part of a larger pattern?
Clear questions ensure consistent routing.
Routing Categories
Insights may be routed as:
1. Immediate Review Routing
• high priority
• reinforced signal
• system impact
• compliance or risk concern
2. Scheduled Review Routing
• medium priority
• single occurrence signal
• relevant but not urgent
3. Monitoring Routing
• low impact
• awareness only
• no immediate Brain action
4. Strategic Review Routing
• pattern-level signal
• long-term system impact
• cross-Brain relevance
→ routed to Strategy Brain or AIBS Brain
Anti-Overload Routing Rule (New)
To prevent Brain overload:
Per session limits:
• max 1–2 Immediate Review items
• max 3–5 Scheduled Review items
All other insights must be:
→ Parked or Monitored
This ensures:
• signal focus
• decision quality
• system stability
Routing Output Types
Routing may produce:
• Brain evaluation request
• framework update request
• guardrail update request
• experiment recommendation
• no action
• monitoring classification
• escalation request
All outcomes must be visible.
Routing Visibility Rule
All routing decisions must be:
• recorded
• traceable
• visible to HeadOffice
No hidden routing allowed.
Escalation Conditions
Routing must escalate when:
• insight affects multiple Brains significantly
• insight impacts system architecture
• reinforced signal becomes strategic
• Brain ownership is unclear
• high-risk or compliance issue
• pattern-level signal detected
Escalation routes to HeadOffice.
System Flow Integration
Newsletter → Extraction Protocol
↓
Intake Framework
↓
Parking System
↓
Routing Review Framework
↓
Brain Routing
↓
Brain Evaluation
↓
Outcome Logged
Governance Role
HeadOffice is responsible for:
• routing discipline
• Brain selection accuracy
• priority evaluation
• recognising reinforced signals
• identifying patterns
• preventing misrouting
• maintaining visibility
• ensuring structured flow
HeadOffice ensures:
right signal → right priority → right Brain → right outcome
Relationship To Other Systems
Works with:
• MWMS Full Newsletter Intelligence Extraction Protocol
• HeadOffice Newsletter Intelligence Intake Framework
• HeadOffice Newsletter Insight Parking System
• HeadOffice Newsletter Intelligence Operating Protocol
• HeadOffice Newsletter Intelligence Supabase Schema Specification
• HeadOffice Newsletter Intelligence Dashboard Specification
• HeadOffice Newsletter Intelligence Brain Room Integration Specification
• HeadOffice External Change Intelligence Framework
• HeadOffice Change Impact Triage Model
• HeadOffice Change Routing Protocol
• Strategic Change Review Framework
• Brain Routing Rule
This framework is the bridge between intelligence and action.
Drift Protection
The system must prevent:
• routing without classification
• routing without priority evaluation
• routing to wrong Brain
• multiple Primary Brains
• duplicate routing
• hidden routing decisions
• bypassing HeadOffice
• Brain authority violations
• treating reinforced signals as noise
• ignoring pattern-level signals
Routing errors create system instability.
Architectural Intent
This framework ensures MWMS operates as:
a coordinated multi-Brain system
not a scattered idea processor
It enables:
• structured intelligence flow
• correct interpretation
• prioritised decision-making
• controlled execution
• scalable system behaviour
Routing discipline is the core connector of MWMS.
Change Log
Version: v1.1
Date: 2026-04-29
Author: HeadOffice
Change:
Upgraded routing framework to align with system maturity. Added priority-based routing layer, reinforced signal detection, pattern routing rules, AIBS Brain priority rule, anti-overload routing limits, and extended routing decision logic to include system-level intelligence patterns.
Version: v1.0
Date: 2026-04-28
Author: HeadOffice
Change:
Initial creation of HeadOffice Newsletter Brain Routing Review Framework defining routing logic, Brain selection rules, escalation conditions, and visibility requirements for all newsletter-derived intelligence entering MWMS.
Change Impact Declaration
Pages Created:
None
Pages Updated:
HeadOffice Newsletter Brain Routing Review Framework
Pages Deprecated:
None
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No
END HEADOFFICE NEWSLETTER BRAIN ROUTING REVIEW FRAMEWORK