Isolation enum

Defines the Architectural Boundary & State Visibility of a Deputy.

Isolation levels determine the "Blast Radius" of a deputy's operations. They define how a deputy's actions affect the primary reactive graph and whether its state transitions are virtualized, shadowed, or physically partitioned from the core Digital Organism.

In the framework's Capability-Based Access Control (CBAC) model, isolation is the primary mechanism for Safety-Critical Sandboxing. It allows Managed Nodes (autonomous agents) to evaluate hypothetical logic transformations during the Reactive Update Cycle without compromising the production Source of Truth.

When to use

Choose the isolation level based on how much impact the deputy should have:

  • shared for live, direct execution.
  • scoped for restricted domains.
  • restricted for zero‑trust filtering.
  • sandboxed for safe simulation.
  • total for air‑gapped observation.

How it works

The isolation level determines where pulses are executed and whether they affect the principal state.

Inheritance
Available extensions

Values

shared → const Isolation

Level 0: Direct Execution (Shared) The deputy operates directly on the principal's state context. Transitions are "Live" and immediately visible to the graph. This level provides peak performance but requires strict Integrity Gate (TestCell) oversight to maintain systemic invariants.

scoped → const Isolation

Level 1: Domain Isolation (Scoped) The deputy is restricted to a specific Ontology domain or subset of fields. Mutations are live but physically constrained to prevent Contextual Bleed into unrelated system nodes.

restricted → const Isolation

Level 2: Zero-Trust Communication (Restricted) Similar to scoped, but every pulse generated by the deputy is intercepted and subjected to mandatory Governance Filtering. This ensures that Causal Provenance is verified at every step of the Reactive Update Cycle.

sandboxed → const Isolation

Level 3: Virtualized Execution (Sandboxed) The deputy operates on a "Projection" or "Clone-on-Write" layer. Transformations are virtualized and do not affect the production state.

For Managed Nodes, this provides a Reasoning Playground to evaluate multiple trajectories before committing to an optimal path.

total → const Isolation

Level 4: Logical Air-Gap (Total) The deputy is completely decoupled. While it can ingest system state during the Ingress Phase, it is physically prevented from emitting signals that reach the global distribution graph. Used for analytical observers and isolated internal reasoning within a Secure Enclave.

Properties

hashCode → int
The hash code for this object.
no setterinherited
index → int
A numeric identifier for the enumerated value.
no setterinherited
isGuarded → bool
Returns true if the isolation requires strict per-pulse message filtering to maintain systemic integrity.
no setter
isVirtual → bool
Returns true if the isolation level prevents live state mutations, requiring a virtualized or projection-based execution layer.
no setter
name → String

Available on Enum, provided by the EnumName extension

The name of the enum value.
no setter
runtimeType → Type
A representation of the runtime type of the object.
no setterinherited

Methods

noSuchMethod(Invocation invocation) → dynamic
Invoked when a nonexistent method or property is accessed.
inherited
toString() → String
A string representation of this object.
inherited

Operators

operator ==(Object other) → bool
The equality operator.
inherited

Constants

values → const List<Isolation>
A constant List of the values in this enum, in order of their declaration.