RFC-023: ENFORCE Broadcast — Ephemeral Distributed Enforcement for Governed Autonomy — 29. Failure Modes

AIGP Specification › RFC-023: ENFORCE Broadcast — Ephemeral Distributed Enforcement for Governed Autonomy › 29. Failure Modes

← 28. Replay Semantics · Section index · 30. Security Considerations →

29. Failure Modes

ENFORCE implementations MUST detect and record failure modes.

enforce_failure_modes:
  - missing_required_field
  - invalid_signature
  - invalid_issuer_authority
  - expired_ttl
  - replayed_signal
  - superseded_signal_used
  - scope_mismatch
  - propagation_loop_detected
  - max_hops_exceeded
  - conflicting_enforce_state
  - broken_ddna_binding
  - stale_enforcement_state
  - split_brain_governance
  - actor_failed_to_ack
  - actor_failed_to_enforce
  - visual_glyph_spoof_detected
  - unsafe_authority_expansion_attempt
  - force_permit_unverified

Each failure MUST produce a D-DNA event.

---

---

← 28. Replay Semantics · Section index · 30. Security Considerations →