PulseContext class Advanced Advanced · Pulse Context

Represents the Causal Identity and ontological Provenance of a Pulse.

PulseContext serves as the telemetric anchor for a stimulus, tracking its historical lineage, reasoning justification, and priority as it propagates through the Switching Fabric.

When to use

• You rarely create a PulseContext directly. Instead, use one of the specialised factories:
  • PulseContext.userAction – for human‑initiated actions.
  • PulseContext.aiInference – for AI‑generated signals.
  • PulseContext.regulated – for compliance‑bound pulses.
  • PulseContext.homeostasis – for system maintenance.
  • PulseContext.telemetry – for high‑frequency monitoring.
  • PulseContext.instruction – for administrative commands.
  • And many more – see the factories below.
• If none of these fit, you can use the general constructor with named parameters (actor, reason, priority, etc.).
• Use PulseContext whenever you need to attach provenance metadata to a pulse – e.g., to record who triggered it, why, and with what priority. This is essential for auditing, debugging, and security enforcement.

How it works

• PulseContext extends ContextBase, so it supports prototype inheritance via a parent chain.
• It stores its dimensions in a memory‑efficient record, using the Provenance enum as keys.
• Some dimensions are static (immutable), others are evolvable.
• The evolve method creates a refined context, useful when a pulse passes through multiple processing stages.

Non‑obvious

• The context is immutable – all changes create a new instance.
• The traceId is auto‑generated if not provided, ensuring uniqueness.
• The parentTraceId is automatically linked when you evolve a context from an existing one.
• The integrity dimension is computed automatically by the framework and is not something you set manually.
• The context is not the pulse – it's a separate metadata container that travels with the pulse.

Example: Creating a User Action Context

final context = PulseContext.userAction(
  actor: 'admin_01',
  reason: 'Manual price update',
  priority: 80,
);
final pulse = Pulse.governed<int>(payload: 100, context: context);

See also:

• Provenance – the underlying dimensions.
• Pulse.governed – the factory that attaches a context to a pulse.
• Context – the base context interface.