system constant

_ContextSystem const system

The canonical root context and Terminal Ancestor of the reactive fabric's governance model.

system serves as the ultimate fallback for all ontological lookups, defining the global "Safe Mode" and default operational parameters for any Cell that has not been explicitly specialized.

When to use

  • Default Initialization: Used automatically by the framework when no explicit context is provided to a Cell factory.
  • Baseline Security: When you need a node to operate with minimal, framework-standard authority and global visibility.
  • Generic Logic: For infrastructure or utility cells that do not belong to a specific business domain.

How it works

  1. Prototype-based Inheritance: Acts as the root node of the contextual graph. Any lookup that fails in a specialized context cascades up to system.
  2. Global Baseline: Enforces minimal Ontology.constraints and Mandate defaults to prevent "Authority Vacuum" errors during pulse transmission.
  3. Hybrid Convergence: As a static const, it provides a pre-compiled, zero-cost path for metadata resolution and security checks across the entire reactive wave.

Non‑obvious

  • Immutable Anchor: Unlike specialized contexts, system cannot be fully evolved into a different identity; it defines the shared reality of the system.
  • Visibility: Nodes under the system context are visible to all diagnostic and auditing layers by default.
  • Zero-Cost Access: Because it is shared across all nodes, it incurs no heap pressure regardless of the graph size.

Example: Implicit vs. Explicit System Context

// Implicitly uses Context.system
final defaultCell = Cell.ingress(0);

// Explicitly referencing for configuration
final loggerCell = Cell.ingress(
  'Log entry',
  context: Context.system,
);

Returns:

The singleton Context instance representing the framework's Root Authority.

See Also:

Implementation

static const system = _ContextSystem();