Document Type: Protocol
Status: Active
Authority: HeadOffice
Applies To: HeadOffice, Brain Room, Supabase Intelligence System
Parent: HeadOffice
Version: v1.1
Last Reviewed: 2026-04-29
Purpose
The HeadOffice Newsletter Intelligence Operating Protocol defines the daily, repeatable workflow for processing newsletters into structured MWMS intelligence.
This protocol ensures:
• consistent daily execution
• no missed intelligence
• controlled system flow
• correct use of all components
• discipline between intake, parking, and routing
• alignment with MWMS governance
Without an operating protocol:
• system becomes inconsistent
• steps are skipped
• insights are lost
• routing becomes unreliable
• dashboard becomes unused
This protocol turns the system into a daily operating habit.
Scope
This protocol applies to:
• daily newsletter processing
• HeadOffice intelligence intake
• Supabase record creation
• Brain Room interaction
• routing and review cycles
This protocol governs:
• daily workflow
• step order
• discipline rules
• completion criteria
This protocol does not govern:
• Brain-level decisions
• financial approvals
• campaign execution
Core Principle
Every newsletter must follow the same structured path.
No shortcuts.
Consistency creates system power.
Daily Operating Flow
Step 1 — Collect Newsletters
Gather all newsletters for the session.
Sources may include:
• AI newsletters
• marketing newsletters
• platform updates
• compliance alerts
Step 2 — Extract Intelligence (Structured Output Required)
Use:
👉 MWMS Full Newsletter Intelligence Extraction Protocol
Rules:
• ignore fluff
• extract only MWMS-relevant signals
• focus on business impact
• every insight must follow a structured output format
🔧 Mandatory Extraction Structure (Working Intelligence Map)
For EACH valid insight, the following fields MUST be defined:
• Insight — clear, single-signal statement
• Extraction Layer — from Newsletter Intelligence Protocol (e.g. Tool Intelligence, Strategic Trend, Monetisation Signal)
• Affected Brain — primary and supporting Brains
• Action Type — park / review / build_later / reject
• Confidence — low / medium / high
• Urgency — low / medium / high
• Notes — context, implications, or reasoning
Extraction Discipline Rules
• one insight per entry
• no combined or multi-signal entries
• no raw notes or unstructured text
• no routing without classification
• no skipping fields
Purpose of Structured Extraction
This structure ensures:
• consistent Supabase records
• reliable Brain routing
• clean intelligence storage
• scalable system processing
• reduced interpretation drift
Unstructured extraction is not permitted.
Step 3 — Create Supabase Records
For each valid insight:
• create newsletter_intelligence_items record
• assign source
• store structured insight fields
• assign signal type
• assign confidence
• assign urgency
All records must match structured extraction format.
Step 4 — Classify Action
Assign:
• park
• review
• build_later
• reject
Classification must match structured extraction output.
Step 5 — Assign Parking State
Route to:
• holding_area
• intelligence_log
• deferred_review
• routing_preparation
• rejected
Step 6 — Prepare Routing
If action = review:
• assign primary Brain
• assign supporting Brains
• define routing priority
Step 7 — Create Brain Room Thread
If routing required:
• create thread
• attach intelligence_item_id
• include structured summary
Step 8 — Send Brain Request
• assign Primary Brain
• define request type
• set priority
Step 9 — Record Responses
• capture Brain response
• store in Supabase
• log event
Step 10 — Record Decision
Update intelligence record:
• routing_status
• action_type
• notes
• decision outcome
Step 11 — Trigger Task (If Required)
If decision requires action:
• create task
• link to intelligence item
Weekly Review Loop
Once per week:
Review:
• deferred insights
• parked insights
• repeated signals
• missed routing opportunities
Promote insights if:
• confidence increases
• pattern emerges
• Brain relevance becomes clear
Monthly Strategic Review
Review:
• high-impact signals
• multi-Brain signals
• system-level changes
Route to:
👉 Strategic Change Review Framework
Completion Criteria (Per Session)
A session is complete when:
• all newsletters processed
• all valid insights recorded
• all insights structured correctly
• all insights classified
• all routing decisions prepared
• all review items sent to Brain Room
• no unprocessed content remains
Governance Rules
HeadOffice must:
• follow full workflow
• not skip steps
• not route without classification
• not create tasks without decisions
• not allow raw ideas into system
• not allow unstructured extraction
Common Failure Points (Prevent These)
• skipping extraction structure
• storing ideas in notes instead of Supabase
• routing without structure
• overloading Brain Room
• ignoring parking discipline
• not updating routing status
System Loop
Newsletter
↓
Extraction (Structured)
↓
Supabase Record
↓
Parking
↓
Routing
↓
Brain Room
↓
Decision
↓
Task
↓
System Improvement
Relationship To Other Systems
Works with:
• MWMS Full Newsletter Intelligence Extraction Protocol
• HeadOffice Newsletter Intelligence Intake Framework
• HeadOffice Newsletter Insight Parking System
• HeadOffice Newsletter Brain Routing Review Framework
• HeadOffice Newsletter Intelligence Dashboard Specification
• HeadOffice Newsletter Intelligence Supabase Schema Specification
• HeadOffice Newsletter Intelligence Brain Room Integration Specification
Drift Protection
The system must prevent:
• inconsistent execution
• skipped steps
• unstructured extraction
• untracked insights
• broken routing
• unlogged decisions
• system fragmentation
Discipline ensures system reliability.
Architectural Intent
This protocol ensures:
MWMS runs newsletter intelligence like a system, not a habit.
It enables:
• consistent execution
• scalable intelligence capture
• reliable decision flow
• system growth through discipline
Change Log
Version: v1.1
Date: 2026-04-29
Author: HeadOffice
Change:
Added mandatory structured extraction format (Working Intelligence Map fields) to Step 2. Introduced extraction discipline rules and enforced structured intelligence output to improve Supabase consistency, routing reliability, and system scalability.
Version: v1.0
Date: 2026-04-28
Author: HeadOffice
Change:
Initial creation of HeadOffice Newsletter Intelligence Operating Protocol defining daily workflow, step-by-step execution process, weekly and monthly review loops, and system discipline for newsletter intelligence processing.
END — HEADOFFICE NEWSLETTER INTELLIGENCE OPERATING PROTOCOL v1.1