Document Type: Framework
Status: Structural
Version: v1.0
Authority: HeadOffice
Applies To: HeadOffice, All MWMS Brains, AI Employees, System Dashboards
Parent: HeadOffice Brain
Last Reviewed: 2026-04-20
Purpose
The HeadOffice Constraint Identification Framework defines how limitations within the MWMS ecosystem are detected, interpreted, and prioritised for resolution.
All systems experience constraints.
Constraints limit performance.
Constraints limit growth speed.
Constraints may exist in:
traffic generation
conversion performance
workflow continuity
signal interpretation
resource allocation
automation reliability
Identifying constraints improves system optimisation efficiency.
Removing constraints improves system throughput.
Constraint visibility improves strategic clarity.
Understanding limitations improves prioritisation accuracy.
Constraint identification enables focused improvement rather than scattered effort.
Scope
This framework applies to:
performance limitations
workflow bottlenecks
measurement limitations
conversion friction points
resource allocation limitations
automation instability
signal reliability limitations
This framework governs:
how constraints are detected
how constraints are interpreted
how constraint severity is evaluated
how constraint visibility improves decision clarity
This framework does not govern:
constraint resolution methods by themselves
capital allocation decisions by themselves
experiment design by itself
These remain governed by:
Experimentation Brain
Finance Brain
Operations Brain
Definition
A constraint is a factor that limits system performance or progression.
Constraints may reduce:
traffic effectiveness
conversion effectiveness
workflow efficiency
learning speed
scalability
Constraints may exist at multiple layers simultaneously.
Constraint visibility improves system understanding.
Understanding constraints improves decision focus.
Core Constraint Categories
Traffic Constraints
Limitations affecting traffic acquisition effectiveness.
Examples:
low traffic quality
high acquisition cost
limited scalable traffic sources
Traffic constraints reduce lead generation capability.
Conversion Constraints
Limitations affecting decision progression effectiveness.
Examples:
high friction environments
low clarity environments
weak trust signals
Conversion constraints reduce revenue efficiency.
Signal Constraints
Limitations affecting intelligence reliability.
Examples:
measurement inconsistencies
unclear attribution
low signal confidence
Signal constraints reduce decision accuracy.
Workflow Constraints
Limitations affecting operational continuity.
Examples:
handoff delays
dependency conflicts
sequencing inefficiencies
Workflow constraints reduce execution speed.
Resource Constraints
Limitations affecting capability expansion.
Examples:
limited time
limited capital
limited development capacity
Resource constraints limit scaling potential.
Automation Constraints
Limitations affecting system scalability.
Examples:
unstable automation triggers
unreliable workflow automation
unclear trigger conditions
Automation constraints reduce efficiency gains.
Constraint Identification Signals
Constraints may be indicated by:
performance stagnation
increasing variability
repeated workflow delays
declining conversion performance
inconsistent signal interpretation
Constraint signals require investigation rather than immediate reaction.
Understanding root cause improves resolution effectiveness.
Constraint Severity Levels
Constraints may be interpreted as:
minor constraint
moderate constraint
critical constraint
Severity influences prioritisation urgency.
Critical constraints require faster attention.
Minor constraints may be monitored.
Severity interpretation improves resource allocation clarity.
Constraint Interaction Effects
Multiple constraints may interact.
Example:
traffic constraint + conversion constraint may reduce lead volume significantly.
Constraint interaction may amplify impact.
Understanding interactions improves prioritisation accuracy.
Relationship to Other MWMS Frameworks
HeadOffice Priority Visibility Framework
determines importance of constraint resolution.
Constraint Identification Framework identifies what limits system performance.
Operations Brain Operational Bottleneck Detection Framework
detects workflow bottlenecks.
Constraint Identification Framework integrates bottleneck signals into system-level visibility.
Data Brain Signal Confidence Framework
identifies signal reliability strength.
Constraint Identification Framework identifies intelligence limitations.
Experimentation Brain Growth Process Framework
supports structured improvement processes.
Constraint Identification Framework identifies improvement targets.
Governance Role
HeadOffice governs system direction and prioritisation.
Constraint Identification Framework ensures system limitations remain visible.
Constraints must remain:
observable
interpretable
cross-Brain consistent
evidence-informed
Constraint visibility must improve decision clarity.
Constraint visibility must not create unnecessary complexity.
Drift Protection
The system must prevent:
ignoring system limitations
optimising non-constraints
misinterpreting symptoms as root causes
focusing on visible issues instead of structural limitations
Constraint clarity improves optimisation effectiveness.
Optimisation effectiveness improves system scalability.
Architectural Intent
HeadOffice Constraint Identification Framework ensures MWMS improvement efforts target the true limiting factors within the ecosystem.
Constraint visibility improves:
resource efficiency
decision focus
system throughput
growth stability
Clear constraint identification enables MWMS to improve systematically rather than reactively.
Change Log
Version: v1.0
Date: 2026-04-20
Author: HeadOffice
Change:
Initial creation of structured constraint identification framework.
Defines how system limitations are detected and interpreted across multiple Brains.
Improves prioritisation clarity and optimisation focus across MWMS ecosystem.