{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T22:44:07.049Z",
  "record_id": "VXI-EXT-PROCUREMENT-RABBITMQ-UNROUTABLE-CONFIRM-01-v1",
  "record_kind": "external_reference",
  "title": "RabbitMQ: Confirmed publish with no destination queue",
  "system": "RabbitMQ",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a RabbitMQ publisher confirm prove that the message reached a destination queue?",
  "near_questions": [
    "Can RabbitMQ acknowledge an unroutable publish?",
    "What does basic.return add to a publisher confirm?",
    "Was mandatory enabled for this RabbitMQ publish?",
    "Which queue matched the routing key?",
    "Are publisher confirms consumer acknowledgements?",
    "Can an empty routing result still receive basic.ack?",
    "Did the return arrive before the confirm?",
    "Which exchange accepted the agent event?",
    "How should an unroutable publish be reconciled?",
    "Does a broker confirm prove the business action ran?",
    "What evidence identifies an unroutable RabbitMQ message?",
    "Can INDEX check live RabbitMQ bindings?"
  ],
  "supported_claims": [
    {
      "claim": "RabbitMQ 4.3 can confirm an unroutable publish after the exchange determines that no queue matches. With the mandatory flag, basic.return precedes the confirm for an unroutable message. Publisher confirms and consumer acknowledgements cover separate exchanges of responsibility; the publish confirm alone does not establish queue routing or application processing.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Proof of consumer completion or automatic retention of unroutable messages",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "RabbitMQ 4.3 can confirm an unroutable publish after the exchange determines that no queue matches. With the mandatory flag, basic.return precedes the confirm for an unroutable message. Publisher confirms and consumer acknowledgements cover separate exchanges of responsibility; the publish confirm alone does not establish queue routing or application processing.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "RabbitMQ: Consumer acknowledgements and publisher confirms",
    "source_url": "https://www.rabbitmq.com/docs/confirms",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-RABBITMQ-UNROUTABLE-CONFIRM-01-v1",
    "candidate_record_sha256": "db9b37790237ca8bd7462580653c8049981b628e1a094793f77f5c4a543e1e19",
    "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 can confirm an unroutable publish after the exchange determines that no queue matches. With the mandatory flag, basic.return precedes the confirm for an unroutable message. Publisher confirms and consumer acknowledgements cover separate exchanges of responsibility; the publish confirm alone does not establish queue routing or application processing.",
    "required_buyer_context": "Exchange, routing key, bindings and mandatory flag for the publish. Correlated publisher confirm and any basic.return response. Intended queue observation and consumer processing result. 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 a RabbitMQ publisher confirm prove that the message reached a destination queue?",
    "documented_statement": {
      "status": "documented",
      "statement": "RabbitMQ 4.3 can confirm an unroutable publish after the exchange determines that no queue matches. With the mandatory flag, basic.return precedes the confirm for an unroutable message. Publisher confirms and consumer acknowledgements cover separate exchanges of responsibility; the publish confirm alone does not establish queue routing or application processing.",
      "source_ids": [
        "rabbit-confirm"
      ]
    },
    "buyer_evidence_required": [
      "Exchange, routing key, bindings and mandatory flag for the publish.",
      "Correlated publisher confirm and any basic.return response.",
      "Intended queue observation and consumer processing result."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline a routed-or-processed conclusion from a publisher confirm without the routing and consumer 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-confirm",
        "url": "https://www.rabbitmq.com/docs/confirms",
        "final_url": "https://www.rabbitmq.com/docs/confirms",
        "title": "RabbitMQ: Consumer acknowledgements and publisher confirms",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T22:37:22.103Z",
        "version_context": "RabbitMQ documentation labelled 4.3; AMQP 0-9-1 publisher confirmation",
        "sha256": "092df8d1c3cd3acb78b5f607142ad95dde87eeb50d2fa677a83097e87a47d322",
        "bytes": 121173,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "Are Publisher Confirms Related to Consumer Delivery Acknowledgements?; When Will Published Messages Be Confirmed?"
        ]
      }
    ],
    "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 recovery decision based only on a positive publish acknowledgement can overlook work that reached no queue.",
      "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": "Exchange, routing key, bindings and mandatory flag for the publish. Correlated publisher confirm and any basic.return response. Intended queue observation and consumer processing result."
    },
    "buyer_relevance": "A recovery decision based only on a positive publish acknowledgement can overlook work that reached no queue.",
    "refusal_conditions": [
      "Decline a routed-or-processed conclusion from a publisher confirm without the routing and consumer 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-publisher-confirm-unroutable-message",
  "machine_readable_record": "/varexis-index/records/rabbitmq-publisher-confirm-unroutable-message.json"
}
