Skip to content
AIGP

RFC-023: ENFORCE Broadcast — Ephemeral Distributed Enforcement for Governed Autonomy — 19. Conflict Handling

AIGP Specification › RFC-023: ENFORCE Broadcast — Ephemeral Distributed Enforcement for Governed Autonomy › 19. Conflict Handling

← 18. Priority Model · Section index · 20. Trust Levels →

19. Conflict Handling

Conflicts may occur when:

two signals issue different commands
one signal permits and another denies
local observation contradicts signal state
peer observation contradicts actor claim
signal TTL differs across actors
supersession is missing or unverifiable

Conflict response:

1. Validate both signals.
2. Check TTL.
3. Check issuer authority.
4. Check scope.
5. Check priority.
6. Apply stricter safety-preserving state.
7. Record D-DNA conflict event.
8. Escalate if required.

Conflict D-DNA:

ddna_event:
  event_type: enforcement.conflict.detected
  actor: drone.043
  signal_a: ebs.sar17.000842
  signal_b: ebs.sar17.000846
  selected_state: deny_entry
  reason: safety_priority
  event_hash: sha256:...

← 18. Priority Model · Section index · 20. Trust Levels →