RFC-023: ENFORCE Broadcast — Ephemeral Distributed Enforcement for Governed Autonomy — 15. Acknowledgment Rules

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

← 14. Propagation Rules · Section index · 16. TTL and Expiration →

15. Acknowledgment Rules

ENFORCE MAY require acknowledgment.

Acknowledgment SHOULD include:

signal_id
actor_id
receipt_time
verification_state
scope_applicability
local_enforcement_result
rebroadcast_result
D-DNA reference

ACK example:

enforce_ack:
  signal_id: ebs.sar17.000842
  actor_id: drone.043
  received_at: "2026-06-16T19:42:16Z"
  verified: true
  scope_applicable: true
  enforced_locally: true
  rebroadcast: true
  ddna_event_id: ddna_01J...

VGL ACK:

[ACK][◎D43][EBS842][✓VER][↻H2][#AA19]

Failure to acknowledge SHOULD be recorded when an acknowledgment was expected.

ddna_event:
  event_type: enforcement.ack.missing
  signal_id: ebs.sar17.000842
  expected_actor: drone.045
  reporting_actor: drone.042
  reason: no_ack_received
  action: escalate_when_link_restored

---

---

← 14. Propagation Rules · Section index · 16. TTL and Expiration →