RFC-023: ENFORCE Broadcast — Ephemeral Distributed Enforcement for Governed Autonomy — 32. Conformance

AIGP Specification › RFC-023: ENFORCE Broadcast — Ephemeral Distributed Enforcement for Governed Autonomy › 32. Conformance

← 31. Privacy and Human Rights Considerations · Section index · 33. Examples →

32. Conformance

An implementation is ENFORCE Broadcast conformant if it supports:

conformance_requirements:
  create_enforce_signal: required
  sign_enforce_signal: required
  validate_required_fields: required
  verify_issuer_authority: required
  verify_signature: required
  validate_ttl: required
  validate_scope: required
  apply_local_enforcement: required
  apply_safe_default_on_uncertainty: required
  record_ddna_issue_event: required
  record_ddna_receipt_event: required
  record_ddna_local_enforcement_event: required
  support_rebroadcast: required
  enforce_propagation_limits: required
  support_ack_when_possible: recommended
  detect_conflicts: required
  record_conflicts: required
  support_vgl_projection: recommended
  reject_unverified_force_permit: required_if_force_capable

---

---

← 31. Privacy and Human Rights Considerations · Section index · 33. Examples →