Clearance enum

Defines the Sovereign Physical Laws and structural boundaries of reactive operations within the framework.

Clearance serves as the fundamental Authorization Tier for the Reciprocal Handshake (Bidirectional Mutual Authorization) protocol. It dictates the Execution Perimeter and logical boundaries of what an autonomous agent (a Managed Node) is permitted to perform within a specific cell or across the systemic topology.

When to use

Use this to control the severity of allowed operations. Higher clearance means more powerful mutations.

How it works

Clearance is a ranked integer. The framework compares the deputy's clearance against the required level for an operation. If it's lower, the pulse is neutralised.

Non‑obvious

  • The comparison is incoming.level >= required.level.
  • observational is the lowest, unrestricted is the highest.
  • This is an evolvable dimension – a deputy can downgrade clearance for child tasks.

Levels

  • observational (0): read‑only.
  • minimal (1): safe mutations within a cell.
  • standard (2): default operational tier.
  • administrative (3): structural refactoring.
  • privileged (4): cross‑domain topology changes.
  • unrestricted (5): absolute authority.

See also: Mandate.clearance.

Inheritance
Available extensions

Values

observational → const Clearance

Level 0: Observational (The Spectator) The lowest tier. Allows for read-only access to public state and telemetry. This agent can perceive but cannot influence the state or topology.

const Clearance(0)
minimal → const Clearance

Level 1: Minimal (The Contributor) Allows for state mutations within a single Cell that do not delete data. Suitable for leaf-node logic and local reasoning.

const Clearance(1)
standard → const Clearance

Level 2: Standard (The Resident) The default operational tier. Allows for standard state updates and the broadcasting of new pulses to adjacent receptors within a module.

const Clearance(2)
administrative → const Clearance

Level 3: Administrative (The Overseer) Grants the power to perform Structural Refactoring. This includes attaching new receptors, spawning child cells, or modifying the routing tables of a local Collection.

const Clearance(3)
privileged → const Clearance

Level 4: Privileged (The Architect) Allows for cross-domain topology changes and the modification of Integrity Gates. This tier is reserved for systemic evolution and high-level orchestration.

const Clearance(4)
unrestricted → const Clearance

Level 5: Unrestricted (The Sovereign) Absolute authority. Can override any Mandate.constraints, bypass isolation, and decommission core infrastructure. This represents the root system authority or the Principal Agent.

const Clearance(5)

Properties

hashCode → int
The hash code for this object.
no setterinherited
index → int
A numeric identifier for the enumerated value.
no setterinherited
level → int
The integer representation of the authorization tier used for comparison in Integrity Gates.
final
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

authorizes(Clearance required) → bool
Returns true if this clearance level meets or exceeds the required threshold.
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<Clearance>
A constant List of the values in this enum, in order of their declaration.