RFC-023: ENFORCE Broadcast — Ephemeral Distributed Enforcement for Governed Autonomy — 16. TTL and Expiration

AIGP Specification › RFC-023: ENFORCE Broadcast — Ephemeral Distributed Enforcement for Governed Autonomy › 16. TTL and Expiration

← 15. Acknowledgment Rules · Section index · 17. Supersession →

16. TTL and Expiration

ENFORCE signals MUST expire.

TTL is required because enforcement state may be:

context-specific
hazard-specific
mission-specific
authority-specific
short-lived
superseded
unsafe if stale

Rules:

expired ENFORCE signals MUST NOT be treated as active
expired denial signals MAY remain advisory if local hazard persists
expired permit signals MUST NOT authorize action
expired force-related signals MUST default to deny/inhibit

On expiration, actors SHOULD fall back to:

latest valid ENFORCE
active operational envelope
local safe state
control-plane authority if available
human reauthorization if required

Expiration D-DNA:

ddna_event:
  event_type: enforcement.signal.expired
  signal_id: ebs.sar17.000842
  actor: drone.042
  expired_at: "2026-06-16T19:44:11Z"
  fallback_state: active_operational_envelope
  event_hash: sha256:...

---

---

← 15. Acknowledgment Rules · Section index · 17. Supersession →