RFC-023: ENFORCE Broadcast — Ephemeral Distributed Enforcement for Governed Autonomy — 13. Local Enforcement Rules

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

← 12. Receipt Rules · Section index · 14. Propagation Rules →

13. Local Enforcement Rules

If an ENFORCE signal is valid and within scope, local enforcement MUST occur before further conflicting action.

Examples:

local_enforcement:
  deny_entry:
    if outside_zone: do_not_enter
    if inside_zone_and_exit_safe: exit
    if inside_zone_and_exit_unsafe: hold_and_escalate

  inhibit_force_capability:
    disable: force_action
    require: human_reauthorization

  degrade_autonomy:
    set_mode: supervised_or_safe

  return_to_base:
    action: navigate_to_base_or_safe_zone

  quarantine_actor:
    action: isolate_from_tools_and_peers

Local enforcement MUST produce a D-DNA event.

ddna_event:
  event_type: enforcement.local.applied
  signal_id: ebs.sar17.000842
  actor: drone.042
  applied_behavior:
    - deny_entry
    - reroute
  event_hash: sha256:...

---

---

← 12. Receipt Rules · Section index · 14. Propagation Rules →