{
  "source_fact_boundaries": [
    "event-driven decoupling does not imply global ordering",
    "idempotent consumer uses a stable identifier and durable processed-message record",
    "retry safety depends on idempotency when repeated execution would have side effects"
  ],
  "forbidden_conclusions": [
    "event-driven architecture guarantees ordering or exactly-once side effects",
    "broker duplicate suppression removes the need for idempotent consumer design",
    "transport delivery id is always the business idempotency key",
    "deduplication solves stale or out-of-order events",
    "green local fixture proves production reliability or downstream idempotency",
    "the same idempotency key may silently alias divergent business payloads"
  ],
  "required_case_semantics": {
    "baseline_first_delivery": "RECEIPT_COMMITTED_EFFECT_APPLIED",
    "duplicate_redelivery_new_transport_id": "DUPLICATE_SUPPRESSED",
    "non_atomic_crash_window": "NON_ATOMIC_DUPLICATE_RISK",
    "stale_lower_version": "STALE_EVENT_REJECTED",
    "evidence_field_removed": "EVIDENCE_INCOMPLETE"
  }
}