HeadOffice External Change Intelligence Framework

Document Type: Framework
Status: Active
Authority: HeadOffice
Applies To: HeadOffice, All Brains, Newsletter Intelligence System
Parent: HeadOffice
Version: v1.0
Last Reviewed: 2026-04-29

Purpose

The HeadOffice External Change Intelligence Framework defines how MWMS detects, classifies, and responds to external changes that may affect the ecosystem.

This framework ensures that external changes are captured before they disrupt:

• strategy
• compliance
• advertising systems
• AI workflows
• platform access
• market behaviour
• revenue opportunities
• system architecture

Without external change intelligence, MWMS risks reacting late, missing important shifts, or allowing outside changes to create internal drift.

Scope

This framework applies to:

• AI platform changes
• Google Ads and advertising platform changes
• compliance and policy changes
• market changes
• economic shifts
• affiliate platform changes
• technology infrastructure changes
• competitor and industry movement
• customer behaviour shifts

This framework governs:

• external signal detection
• change classification
• affected Brain identification
• urgency assessment
• review routing
• parking or escalation decisions

This framework does not govern:

• final Brain-level decisions
• campaign execution
• capital approval
• canon promotion
• plugin implementation

Core Principle

External change must be detected before MWMS reacts.

HeadOffice must convert outside change into structured intelligence before any Brain acts on it.

No external change should directly trigger execution without classification, routing, and review.

External Change Categories

External changes may be classified into the following categories.

1. AI Platform Change

Includes changes to:

• ChatGPT
• Claude
• Gemini
• Perplexity
• Copilot
• AI agents
• AI models
• AI tool pricing
• AI memory systems
• AI workflow features

Examples:

• new agent capability
• model pricing change
• workspace automation release
• tool access restriction
• API capability change

Primary Brain:

AIBS Brain

Supporting Brains:

Operations Brain, Data Brain, Strategy Brain

2. Advertising Platform Change

Includes changes to:

• Google Ads
• YouTube Ads
• Meta Ads
• TikTok Ads
• LinkedIn Ads
• attribution systems
• targeting options
• policy enforcement
• creative formats

Examples:

• Google Ads tracking update
• YouTube ad format change
• Meta attribution change
• policy approval shift
• new campaign type

Primary Brain:

Ads Brain

Supporting Brains:

Data Brain, Compliance Brain, Affiliate Brain, Finance Brain

3. Compliance And Policy Change

Includes changes to:

• advertising rules
• data privacy laws
• affiliate compliance rules
• platform terms
• AI usage policy
• financial marketing restrictions
• consumer protection standards

Examples:

• Google policy update
• FTC affiliate disclosure change
• privacy regulation update
• AI-generated content disclosure rule

Primary Brain:

Compliance Brain

Supporting Brains:

SIT Brain, Risk Brain, Ads Brain, Affiliate Brain, Data Brain

4. Market Behaviour Change

Includes changes to:

• customer demand
• buyer psychology
• cost-of-living pressure
• niche demand
• consumer trust
• content consumption
• social platform behaviour

Examples:

• rising demand for savings offers
• consumer distrust of AI content
• shift toward practical financial relief
• growing fatigue with low-value tools

Primary Brain:

Research Brain

Supporting Brains:

Strategy Brain, Affiliate Brain, Creative Brain, Content Brain

5. Economic Change

Includes changes to:

• inflation
• interest rates
• unemployment
• household spending
• credit pressure
• insurance costs
• energy costs
• travel costs

Examples:

• rising household bills
• increased demand for cost-saving products
• affordability pressure in key markets

Primary Brain:

Finance Brain

Supporting Brains:

Research Brain, Affiliate Brain, Strategy Brain

6. Affiliate And Offer Market Change

Includes changes to:

• affiliate networks
• offer payouts
• refund rates
• EPC trends
• compliance requirements
• offer saturation
• new verticals
• competitor promotion patterns

Examples:

• MaxBounty offer shift
• ClickBank gravity spike
• finance CPL trend
• insurance lead-gen growth

Primary Brain:

Affiliate Brain

Supporting Brains:

Research Brain, Finance Brain, Compliance Brain, Ads Brain

7. Technology Infrastructure Change

Includes changes to:

• hosting
• APIs
• Supabase
• WordPress
• automation platforms
• security tools
• cloud providers
• local inference
• model deployment

Examples:

• Supabase feature change
• WordPress security update
• AI compute cost shift
• local inference adoption

Primary Brain:

AIBS Brain

Supporting Brains:

Operations Brain, Data Brain, SIT Brain

Change Classification Fields

Each external change should be classified using:

External Change Source:

Change Summary:

Change Category:

Affected Brain:

Supporting Brains:

Confidence Level:

Urgency Level:

Priority Level:

Risk Flag:

Compliance Flag:

Action Type:

Suggested Routing:

Notes:

Action Type Options

Each change must be assigned one action type.

Park
Use when the change may matter later but does not require action now.

Review
Use when the change may affect Brain decisions or system direction.

Build Later
Use when the change suggests a future system capability.

Reject
Use when the change is noise, hype, duplicate, or irrelevant.

Escalate
Use when the change affects system architecture, compliance, capital exposure, or major strategy.

Priority Logic

Priority is derived from confidence plus urgency.

High Priority:

• confidence = high
• urgency = high

Review Priority:

• confidence = high and urgency = medium
• confidence = medium and urgency = high

Monitor Priority:

• confidence = medium and urgency = medium
• confidence = high and urgency = low

Low Priority:

• confidence = low
• urgency = low

External Change Flow

External change detected

Structured using this framework

Change category assigned

Affected Brain identified

Action type assigned

Parking or routing decision made

Brain review if required

Decision logged

Task created only if approved

Routing Rules

External changes must route through HeadOffice before Brain action.

Routing must follow:

• correct Brain ownership
• priority level
• risk level
• compliance exposure
• system impact

No Brain may act on external change without structured review.

Escalation Conditions

Escalate to HeadOffice when the change affects:

• system architecture
• compliance exposure
• capital exposure
• tracking reliability
• AI employee behaviour
• cross-Brain workflows
• platform access
• legal or policy risk

Relationship To Newsletter Intelligence System

Newsletter Intelligence is one major source of external change signals.

This framework works with:

• HeadOffice Newsletter Intelligence Intake Framework
• HeadOffice Newsletter Insight Parking System
• HeadOffice Newsletter Brain Routing Review Framework
• HeadOffice Newsletter Intelligence Operating Protocol
• HeadOffice Newsletter Intelligence Daily Signal Log

Newsletter insights may trigger this framework when they identify meaningful external change.

Governance Role

HeadOffice owns external change interpretation.

Specialist Brains may review impact within their authority, but HeadOffice controls:

• initial classification
• routing
• escalation
• system-wide interpretation
• final coordination

Drift Protection

The system must prevent:

• reacting to external change without classification
• routing change to the wrong Brain
• treating hype as strategic signal
• ignoring repeated external signals
• creating tasks before review
• allowing platform changes to bypass governance
• allowing compliance changes to remain parked too long

External change must strengthen awareness, not create chaos.

Architectural Intent

This framework ensures MWMS remains aware of the outside world without being controlled by it.

It enables:

• early detection
• structured response
• strategic patience
• compliance awareness
• market adaptation
• controlled system evolution

MWMS must adapt deliberately, not react emotionally.

Change Log

Version: v1.0
Date: 2026-04-29
Author: HeadOffice

Change:
Initial creation of HeadOffice External Change Intelligence Framework defining external change categories, classification fields, routing rules, priority logic, escalation conditions, and relationship to the Newsletter Intelligence System.

Change Impact Declaration

Pages Created:

HeadOffice External Change Intelligence Framework

Pages Updated:

None

Pages Deprecated:

None

Registries Requiring Update:

HeadOffice Page Registry

Canon Version Update Required:

No

Change Log Entry Required:

No

END HEADOFFICE EXTERNAL CHANGE INTELLIGENCE FRAMEWORK