Skip to content
AIGP

RFC-023: ENFORCE Broadcast — Ephemeral Distributed Enforcement for Governed Autonomy — 12. Receipt Rules

AIGP Specification › RFC-023: ENFORCE Broadcast — Ephemeral Distributed Enforcement for Governed Autonomy › 12. Receipt Rules

← 11. Issuance Rules · Section index · 13. Local Enforcement Rules →

12. Receipt Rules

Upon receiving an ENFORCE signal, an actor MUST:

parse the signal
validate required fields
check TTL
verify issuer if possible
verify signature if possible
check scope applicability
determine trust level
apply safe-state default if uncertain
record receipt in D-DNA

If the actor is within scope and the signal is verified, it MUST enforce locally.

If the signal is unverified but safety-preserving, the actor MAY apply conservative safe behavior.

Example:

An unverified collapse-risk denial may justify not entering a zone.
An unverified permit may not justify entering a zone.
An unverified force authorization may never justify engagement.

Receipt D-DNA:

ddna_event:
  event_type: enforcement.signal.received
  signal_id: ebs.sar17.000842
  received_by: drone.042
  received_at: "2026-06-16T19:42:13Z"
  verified: true
  scope_applicable: true
  ttl_valid: true
  local_decision: enforce
  event_hash: sha256:...

← 11. Issuance Rules · Section index · 13. Local Enforcement Rules →