RFC-023: ENFORCE Broadcast — Ephemeral Distributed Enforcement for Governed Autonomy — 14. Propagation Rules

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

← 13. Local Enforcement Rules · Section index · 15. Acknowledgment Rules →

14. Propagation Rules

If an ENFORCE signal declares rebroadcast required, affected actors become temporary governance relays.

A recipient MUST rebroadcast when:

rebroadcast_required == true
recipient is within propagation scope
TTL remains valid
hop_count < max_hops
signal verification succeeds or safety rules allow advisory rebroadcast

A recipient MUST NOT rebroadcast when:

TTL expired
signature invalid
issuer authority invalid
scope does not apply and propagation scope excludes recipient
max_hops exceeded
signal conflicts with higher-priority verified signal

Propagation D-DNA:

ddna_event:
  event_type: enforcement.signal.rebroadcast
  signal_id: ebs.sar17.000842
  rebroadcast_by: drone.042
  hop_count: 1
  channels:
    - mesh
    - visual_glyph
  rebroadcast_at: "2026-06-16T19:42:15Z"
  event_hash: sha256:...

---

---

← 13. Local Enforcement Rules · Section index · 15. Acknowledgment Rules →