Document Type: Framework
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: All Brains, All Outputs, All Decision Systems
Parent: HeadOffice Growth Model Architecture Standard
Last Reviewed: 2026-04-25
Purpose
The MWMS Action Definition Framework defines what qualifies as a valid action within the MWMS system.
Its purpose is to ensure that:
• outputs do not end in observation
• insights do not end in interpretation
• decisions do not end in abstraction
All outputs must result in:
👉 a clear, executable action
This framework enforces action quality across all MWMS systems.
Core Principle
An output without action has no operational value.
Clarity of action determines system effectiveness.
Weak actions reduce system performance.
Strong actions drive system progress.
Definition
An action is a clearly defined, executable step that:
• moves the system forward
• tests a hypothesis
• protects capital
• improves performance
• reduces risk
Core Question
This framework answers:
👉 What exactly will be done next?
Action Categories
1. Test Action
Action that initiates structured experimentation.
Examples:
• create A/B test
• test new creative angle
• test funnel variation
• isolate segment behaviour
Purpose
• generate learning
• validate hypotheses
• reduce uncertainty
2. Scale Action
Action that increases exposure or investment.
Examples:
• increase budget
• expand traffic source
• duplicate winning campaign
• extend offer reach
Purpose
• grow revenue
• leverage validated performance
3. Optimisation Action
Action that improves an existing system component.
Examples:
• refine messaging
• adjust targeting
• improve landing page
• reduce friction
Purpose
• improve efficiency
• increase conversion
• enhance system performance
4. Protection Action
Action that reduces risk or prevents loss.
Examples:
• reduce budget
• pause campaign
• stop scaling
• isolate failing segment
Purpose
• protect capital
• prevent system degradation
5. Investigation Action
Action that gathers more information.
Examples:
• run diagnostic analysis
• decompose performance
• validate data integrity
• review segment behaviour
Purpose
• improve understanding
• reduce uncertainty
• prepare for testing
6. Exit Action
Action that removes a failing component.
Examples:
• kill offer
• stop campaign
• remove segment
• discontinue strategy
Purpose
• eliminate waste
• prevent continued loss
Action Quality Levels
Strong Action
A strong action is:
• specific
• measurable
• executable
• time-bound
• assigned
Example
Launch test for new landing page variant targeting segment A within next testing cycle.
Weak Action
A weak action is:
• vague
• non-specific
• non-executable
• lacks ownership
Example
Improve landing page performance.
Invalid Action
An invalid action is:
• purely observational
• descriptive
• lacks intent
Example
Conversion rate is low.
Action Structure
Every valid action must include:
1. Action Type
Identify category:
• Test
• Scale
• Optimise
• Protect
• Investigate
• Exit
2. Action Definition
Clearly define:
• what will be done
3. Target Area
Specify:
• which system component is affected
4. Owner
Assign:
• responsible Brain or system
5. Timing
Define:
• when action will occur
6. Expected Outcome
Define:
• what success looks like
Action Clarity Rule
Every action must answer:
👉 What will be done
👉 Where it will be done
👉 Who will do it
👉 When it will be done
If any element is missing:
→ action is incomplete
Action Mapping Rule
Every Decision Narrative must map to:
👉 exactly one primary action
Optional:
• secondary actions
But no conflicting actions allowed.
Action Priority Logic
High Priority
• protects capital
• addresses major performance drop
• resolves system instability
Medium Priority
• improves performance
• tests meaningful opportunity
Low Priority
• minor optimisation
• low-impact improvement
Cross Brain Use
Data Brain
Supports investigation actions through validated data.
Experimentation Brain
Executes test actions.
Affiliate Brain
Defines scale, optimise, or exit actions for offers.
Ads Brain
Executes campaign-level actions.
Finance Brain
Controls protection and scaling actions.
Research Brain
Supports investigation and pattern discovery.
HeadOffice
Approves high-impact and strategic actions.
Relationship To Other Frameworks
This framework connects to:
• MWMS Decision Narrative Framework
• Data Brain Performance Decomposition Framework
• Experimentation Brain Diagnostic Trigger Framework
• Experimentation Brain Test Result And Decision Workflow
• Affiliate Brain Offer Health Monitoring Framework
Failure Modes Prevented
This framework prevents:
• vague outputs
• non-executable decisions
• analysis without action
• unclear responsibility
• delayed execution
Drift Protection
The system must prevent:
• actions becoming generic
• actions lacking ownership
• actions lacking timing
• actions lacking clarity
• outputs without action
Architectural Intent
This framework ensures MWMS operates as:
👉 an action-driven system
not:
👉 an analysis system
It enforces execution discipline across all Brains.
Final Rule
If an action cannot be executed immediately:
→ it must be redefined
Change Log
Version: v1.0
Date: 2026-04-25
Author: HeadOffice
Change
Initial creation of Action Definition Framework to enforce execution clarity across MWMS based on data storytelling action principles.
Change Impact Declaration
Pages Created:
MWMS Action Definition Framework
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
HeadOffice Framework Registry
MWMS Architecture Registry
Canon Version Update Required:
No
Change Log Entry Required:
Yes