RFC-023: ENFORCE Broadcast — Ephemeral Distributed Enforcement for Governed Autonomy — 6. Definitions

AIGP Specification › RFC-023: ENFORCE Broadcast — Ephemeral Distributed Enforcement for Governed Autonomy › 6. Definitions

← 5. Non-Goals · Section index · 7. ENFORCE Signal Model →

6. Definitions

6.1 ENFORCE Signal

An ENFORCE signal is a short-lived, signed governance state update that instructs affected actors to deny, inhibit, degrade, pause, return, reroute, escalate, or otherwise constrain behavior.

6.2 Issuer

The issuer is the authority that creates the ENFORCE signal.

Examples:

incident_commander
mission_control
control_plane
runtime_authority_monitor
safety_controller
legal_authority
human_operator
verified_peer_actor
cognitive_safety_monitor

6.3 Affected Actor

An affected actor is an actor within the ENFORCE signal’s scope.

Examples:

drone.*
ground_robot.*
agent.finance.*
hga.cyborg_responder.*
force_capable_system.*

6.4 Scope

Scope defines where, when, and to whom the ENFORCE signal applies.

Scope may include:

mission
tenant
actor class
actor identity
geography
altitude
tool scope
data scope
conversation session
battlefield area
incident zone
time window

6.5 TTL

TTL is the time-to-live of the enforcement state.

Expired ENFORCE signals MUST NOT be treated as active enforcement.

6.6 Supersession

Supersession defines whether this ENFORCE signal replaces a prior signal.

6.7 Propagation

Propagation defines whether recipients must rebroadcast the signal.

6.8 Inhibition

Inhibition is the architectural reduction, denial, degradation, isolation, or disabling of capability.

---

---

← 5. Non-Goals · Section index · 7. ENFORCE Signal Model →