Document Type: Framework
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: All Brains, All Outputs, All Interfaces (Dashboards, Logs, Reports, Screens)
Parent: HeadOffice Growth Model Architecture Standard
Last Reviewed: 2026-04-25
Purpose
The MWMS Output Structuring Framework defines how outputs are structured to ensure clarity, focus, and decision effectiveness.
Its purpose is to prevent:
• overloaded outputs
• unclear communication
• multi-point confusion
• signal dilution
All outputs must be structured to deliver:
👉 one clear idea
👉 one clear conclusion
👉 one clear action
Core Principle
Clarity requires constraint.
An output must communicate:
👉 one primary point
Multiple points reduce clarity and weaken decision quality.
Definition
An output is any unit of information produced by MWMS, including:
• dashboards
• logs
• reports
• analysis summaries
• decision narratives
• system messages
Output structure defines how information is presented within that unit.
Core Question
This framework answers:
👉 Is this output clear enough to act on?
Primary Output Rule
Each output must contain:
👉 one primary message
This message must be:
• clear
• specific
• non-ambiguous
Example (Valid)
Customer quality is declining in new traffic segment.
Example (Invalid)
Customer quality is declining, conversion is unstable, traffic is increasing, and performance is mixed.
Supporting Information Rule
Outputs may include supporting information, but only if it:
• reinforces the primary message
• does not introduce competing ideas
• remains directly relevant
Rule
Supporting information must not:
• introduce new conclusions
• dilute the primary message
• create ambiguity
Signal Hierarchy Structure
Outputs must follow:
1. Primary Signal
The main point.
2. Supporting Signals
Data that reinforces the main point.
3. Context Signals
Optional information providing background.
Rule
Hierarchy must be clear and structured.
Output Compression Rule
Outputs must:
• remove unnecessary detail
• eliminate redundant information
• compress language where possible
Objective
Maximize:
👉 clarity per unit of information
Multi-Point Separation Rule
If multiple valid points exist:
👉 they must be split into separate outputs
Rule
One output = one decision path
Output Types
1. Diagnostic Output
Describes:
• what is happening
• why it is happening
2. Decision Output
Defines:
• what must be done
3. Action Output
Specifies:
• exact next step
Rule
Outputs may combine types, but must maintain:
👉 single primary message
Output Readability Rule
Outputs must be:
• easy to scan
• easy to understand
• quick to interpret
Constraint
The user must not need to:
• interpret multiple meanings
• resolve contradictions
• infer missing logic
Cognitive Load Rule
Outputs must minimize:
• mental effort
• processing time
• interpretation burden
Principle
If the user must think too hard:
→ output is poorly structured
Cross Brain Use
Data Brain
Produces structured signals.
Experimentation Brain
Uses structured outputs to guide tests.
Affiliate Brain
Uses outputs to evaluate offers.
Ads Brain
Uses outputs for campaign decisions.
Finance Brain
Uses outputs for capital control.
Research Brain
Stores structured outputs for reuse.
HeadOffice
Consumes outputs for strategic decisions.
Relationship To Other Frameworks
This framework connects to:
• MWMS Decision Narrative Framework
• MWMS Action Definition Framework
• Data Brain Performance Decomposition Framework
• Data Brain Customer Quality Tracking Framework
• Experimentation Brain Diagnostic Trigger Framework
Failure Modes Prevented
This framework prevents:
• overloaded outputs
• unclear messaging
• conflicting conclusions
• slow decision making
• misinterpretation of data
Drift Protection
The system must prevent:
• multi-point outputs
• excessive detail
• unclear hierarchy
• redundant information
• output complexity
Architectural Intent
This framework ensures MWMS outputs are:
👉 clear
👉 focused
👉 decision-ready
It enforces communication discipline across all systems.
Final Rule
If an output contains more than one core message:
→ it must be split
Change Log
Version: v1.0
Date: 2026-04-25
Author: HeadOffice
Change
Initial creation of Output Structuring Framework to enforce clarity and single-point communication across MWMS outputs.
Change Impact Declaration
Pages Created:
MWMS Output Structuring 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