{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T22:44:07.049Z",
  "record_id": "VXI-EXT-PROCUREMENT-RABBITMQ-DEADLETTER-HANDOFF-01-v1",
  "record_kind": "external_reference",
  "title": "RabbitMQ: Dead-letter transfer can itself fail",
  "system": "RabbitMQ",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does configuring a RabbitMQ dead-letter exchange guarantee that failed work is retained for recovery?",
  "near_questions": [
    "Can RabbitMQ lose a message while dead-lettering it?",
    "Are publisher confirms enabled for default dead-letter republishing?",
    "When is the message removed from the source queue?",
    "What if the dead-letter destination cannot accept messages?",
    "Was at-least-once dead-lettering actually configured?",
    "Does declaring a dead-letter exchange prove retention?",
    "Which queue type controls the recovery handoff?",
    "What broker errors occurred during dead-letter transfer?",
    "Which recovered message corresponds to the original action?",
    "Was failed work observed at the destination queue?",
    "What evidence checks RabbitMQ recovery retention?",
    "Can INDEX verify a RabbitMQ dead-letter strategy?"
  ],
  "supported_claims": [
    {
      "claim": "RabbitMQ 4.3 documents dead-lettering as republishing. By default it uses no internal publisher confirms and removes the message from its source queue after publishing; the message can be lost if the destination cannot accept it. Quorum queues offer an at-least-once dead-lettering alternative. A configured exchange alone does not establish a reliable recovery handoff.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Universal lossless dead-lettering, exactly-once recovery or verified queue health",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "RabbitMQ 4.3 documents dead-lettering as republishing. By default it uses no internal publisher confirms and removes the message from its source queue after publishing; the message can be lost if the destination cannot accept it. Quorum queues offer an at-least-once dead-lettering alternative. A configured exchange alone does not establish a reliable recovery handoff.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "RabbitMQ: Dead-letter exchanges",
    "source_url": "https://www.rabbitmq.com/docs/dlx",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-RABBITMQ-DEADLETTER-HANDOFF-01-v1",
    "candidate_record_sha256": "cb00f240040dbb27e105d7438143b9a2f77c94edb7360df8cfb1065d47d59657",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "RabbitMQ 4.3 documents dead-lettering as republishing. By default it uses no internal publisher confirms and removes the message from its source queue after publishing; the message can be lost if the destination cannot accept it. Quorum queues offer an at-least-once dead-lettering alternative. A configured exchange alone does not establish a reliable recovery handoff.",
    "required_buyer_context": "Source queue type, effective dead-letter strategy, exchange and routing configuration. Destination availability and broker handoff errors or confirmations. Retained destination message and recovery result correlated to the original action. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-17",
    "claim_to_check": "Does configuring a RabbitMQ dead-letter exchange guarantee that failed work is retained for recovery?",
    "documented_statement": {
      "status": "documented",
      "statement": "RabbitMQ 4.3 documents dead-lettering as republishing. By default it uses no internal publisher confirms and removes the message from its source queue after publishing; the message can be lost if the destination cannot accept it. Quorum queues offer an at-least-once dead-lettering alternative. A configured exchange alone does not establish a reliable recovery handoff.",
      "source_ids": [
        "rabbit-dlx"
      ]
    },
    "buyer_evidence_required": [
      "Source queue type, effective dead-letter strategy, exchange and routing configuration.",
      "Destination availability and broker handoff errors or confirmations.",
      "Retained destination message and recovery result correlated to the original action."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline retained-for-recovery claims without checking the effective handoff mode and destination evidence."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "rabbit-dlx",
        "url": "https://www.rabbitmq.com/docs/dlx",
        "final_url": "https://www.rabbitmq.com/docs/dlx",
        "title": "RabbitMQ: Dead-letter exchanges",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T22:37:23.989Z",
        "version_context": "RabbitMQ documentation labelled 4.3; default republishing and quorum alternative",
        "sha256": "6cc04682d485454e317cd9f6d357676a5ae91077a505178945a62caeae6611e5",
        "bytes": 66356,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "Safety; Re-Publishing with Publisher Confirms"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "A failed action can lose its recovery message at the handoff that operators expected to preserve it.",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Source queue type, effective dead-letter strategy, exchange and routing configuration. Destination availability and broker handoff errors or confirmations. Retained destination message and recovery result correlated to the original action."
    },
    "buyer_relevance": "A failed action can lose its recovery message at the handoff that operators expected to preserve it.",
    "refusal_conditions": [
      "Decline retained-for-recovery claims without checking the effective handoff mode and destination evidence."
    ]
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#rabbitmq-dead-letter-republication-loss-boundary",
  "machine_readable_record": "/varexis-index/records/rabbitmq-dead-letter-republication-loss-boundary.json"
}
