Sensitivity enum
Defines the Information Classification and data-privacy tier of a Pulse.
Sensitivity levels determine the encryption requirements, redaction policies, and visibility of the Pulse.payload across different Isolation levels.
Within the framework's Capability-Based Access Control (CBAC) model, this enum enables Automated Compliance Enforcement.
During the Reactive Update Cycle, a Managed Node or Integrity Gate (TestCell) utilizes the sensitivity tier to determine if a specific agent possesses the required Clearance to authorize the signal's Ingress or to perform a state mutation during the **Transformation **.
When to use
Attach a sensitivity level to a pulse to indicate its data classification. This helps enforce privacy and compliance rules.
How it works
The framework uses sensitivity to determine redaction, encryption, and access control. Higher sensitivity requires higher clearance.
Values
- public → const Sensitivity
-
Level 0: Public. Non-sensitive data that can be safely logged, cached, and transmitted across unencrypted channels.
Example: App version numbers, current theme name, or public constants.
- internal → const Sensitivity
-
Level 1: Internal. Data intended for system-wide use but not for external exposure. Restricted from egress to external third-party adapters.
Example: System-wide telemetry, cell topology metadata, or heartbeat signals.
- private → const Sensitivity
-
Level 2: Private. Data restricted to the local Sovereign Resident or the immediate cell cluster. Never broadcast across public synapses.
Example: An agent's local scratchpad, internal monologue, or local loop counters.
- confidential → const Sensitivity
-
Level 3: Confidential. Sensitive operational data requiring standard encryption at rest. Typically masked in low-level audit logs.
Example: Feature flags, internal resource URIs, or obfuscated user IDs.
- restricted → const Sensitivity
-
Level 4: Restricted. Highly sensitive data, including PII (Personally Identifiable Information). Never logged in plaintext.
Example: User email addresses, physical geolocation, or billing history.
- secret → const Sensitivity
-
Level 5: Secret. The highest tier of confidentiality. Restricted to Isolation.sandboxed or Isolation.total environments to prevent leakage.
Example: Private cryptographic keys, OAuth tokens, or administrative passwords.
Properties
- hashCode → int
-
The hash code for this object.
no setterinherited
- index → int
-
A numeric identifier for the enumerated value.
no setterinherited
- isHighRisk → bool
-
Returns
trueif the data carries significant legal or security risk, requiring elevated Clearance for any mutation.no setter - name → String
-
Available on Enum, provided by the EnumName extension
The name of the enum value.no setter - requiresMasking → bool
-
Returns
trueif the data requires proactive masking or redaction within AuditLevel.standard logs.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<
Sensitivity> - A constant List of the values in this enum, in order of their declaration.