Document Type: Framework
Status: Active
Authority: Data Brain
Parent: Data Brain Architecture
Applies To: All MWMS environments where behavioural, interaction, or conversion signals are captured, interpreted, or used for decision-making
Version: v1.0
Last Reviewed: 2026-04-23

Purpose

The Data Brain Signal Context Framework defines how MWMS enriches raw behavioural signals with meaningful context so they can be correctly interpreted and used for decision-making.

Raw events without context are incomplete.

A signal only becomes meaningful when its surrounding conditions are understood.

This framework ensures that:

• signals are not interpreted in isolation
• interaction meaning is preserved
• behavioural intent can be inferred
• optimisation decisions are based on real context, not surface-level data

Core Principle

A signal without context is not a reliable signal.

Events describe what happened.

Context explains:

• where it happened
• why it happened
• under what conditions it happened
• what it means

Without context:

→ interpretation becomes guesswork

Position in MWMS System

This framework operates within:

• Data Brain → signal enrichment and interpretation
• Research Brain → behavioural insight generation
• Ads Brain → interaction quality evaluation
• Conversion Brain → funnel optimisation
• Experimentation Brain → test interpretation

This framework feeds:

• Signal Classification Framework
• Measurement Integrity Framework
• Attribution Reliability Framework

Signal vs Context

Signal (Raw Event)

Examples:

• click
• page view
• form submission
• video play

Signals represent:

→ an action occurred

Context (Enrichment Layer)

Examples:

• page region
• component type
• user state
• funnel stage
• interaction intent

Context represents:

→ meaning behind the action

Context Requirement Rule

All important signals must include sufficient context to be interpretable.

High Context Signal

Includes:

• location
• component
• interaction type
• funnel stage
• relevant user state

→ Fully interpretable
→ High decision value

Moderate Context Signal

Includes:

• some context layers
• partial understanding

→ Useful but limited

Low Context Signal

Includes:

• minimal context
• action only

→ Weak interpretation value

No Context Signal

Includes:

• raw event only

→ Not suitable for meaningful analysis

Context Enrichment Methods

1. Data Attributes

Add contextual data directly to elements.

Examples:

• region identifiers
• component identifiers
• interaction labels

2. DOM Structure Interpretation

Use element hierarchy to infer context.

Examples:

• parent containers
• layout structure
• component grouping

3. Data Layer Enrichment

Push structured context into the data layer.

Examples:

• page metadata
• user state
• funnel stage

4. Naming Conventions

Use consistent naming to encode context.

Examples:

• event naming structures
• parameter naming rules

Context Integrity Rule

Context must be:

• accurate
• consistent
• stable across environments

Incorrect context is worse than missing context.

Incorrect context leads to false interpretation.

Context Dependency Rule

Some context depends on:

• configuration state
• user state availability
• page load timing
• external systems

If context is not available at event time:

→ context reliability is reduced

Context Failure Types

Missing Context

Signal fires but lacks context.

Result:

→ incomplete interpretation

Incorrect Context

Signal includes wrong context.

Result:

→ misleading interpretation

Inconsistent Context

Same interaction produces different context values.

Result:

→ unreliable comparisons

Delayed Context

Context arrives after event fires.

Result:

→ event recorded without meaning

Context Validation Requirements

Context must be validated through:

• test interactions
• debug inspection
• data layer review
• consistency checks across pages

Validation ensures:

• context is present
• context is correct
• context is stable

Relationship to Event Reliability

Event reliability determines:

→ whether a signal exists

Context determines:

→ what the signal means

Both are required for decision-quality data.

Relationship to Other Frameworks

Supports:

• Data Brain Event Reliability Framework
• Data Brain Measurement Integrity Framework
• Data Brain Signal Classification Framework
• Data Brain Attribution Reliability Framework
• Research Brain Behavioural Signal Framework

Failure Modes Prevented

misinterpreting clicks
optimising based on incomplete signals
misidentifying high-performing elements
confusing navigation behaviour with intent
incorrect funnel analysis
loss of behavioural meaning

Drift Protection

The system must prevent:

• context definitions changing unnoticed
• component identifiers becoming inconsistent
• layout changes breaking context mapping
• naming conventions degrading over time

Context must remain stable to remain meaningful.

Architectural Intent

The Data Brain Signal Context Framework ensures MWMS evolves from:

→ tracking actions

to:

→ understanding behaviour

It transforms:

data → information → insight

Context is what enables that transformation.

Final Rule

If a signal lacks context:

→ it must not be treated as fully interpretable

Change Log

Version: v1.0
Date: 2026-04-23
Author: Data Brain

Change:
Initial creation of Data Brain Signal Context Framework defining how MWMS enriches behavioural signals with meaningful context.

Change Impact Declaration

Pages Created:
Data Brain Signal Context Framework

Pages Updated:
None

Pages Deprecated:
None

Registries Requiring Update:
MWMS Architecture Registry

Canon Version Update Required:
No

Change Log Entry Required:
Yes