{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T22:44:07.049Z",
  "record_id": "VXI-EXT-PROCUREMENT-KAFKA-EXTERNAL-EXACTLY-ONCE-01-v1",
  "record_kind": "external_reference",
  "title": "Kafka: Transaction guarantees at external destinations",
  "system": "Apache Kafka",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Do Kafka transactions make an agent's writes to an external service exactly once?",
  "near_questions": [
    "Does Kafka exactly-once processing cover an external API?",
    "Where is the consumer offset stored relative to output?",
    "Does read_committed make a database write transactional?",
    "Which sink cooperates with Kafka recovery?",
    "Can a transaction commit leave external-effect uncertainty?",
    "What evidence links consumer progress to stored output?",
    "Does Kafka Streams guarantee arbitrary outside actions once?",
    "How is an external sink reconciled after a crash?",
    "Which writes fall outside the Kafka transaction?",
    "Was sink output coordinated with the consumed offsets?",
    "Can INDEX certify end-to-end exactly-once processing?",
    "What bounds Kafka transaction claims for agent tools?"
  ],
  "supported_claims": [
    {
      "claim": "Kafka 4.3 describes exactly-once processing between Kafka topics using transactions and read-committed consumers. For an external destination, the consumer position must be coordinated with the stored output; cooperation from that destination is needed. Kafka transaction success alone does not extend its guarantee to an arbitrary external API or database write.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Automatic atomicity with external APIs or verification of a buyer connector",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "Kafka 4.3 describes exactly-once processing between Kafka topics using transactions and read-committed consumers. For an external destination, the consumer position must be coordinated with the stored output; cooperation from that destination is needed. Kafka transaction success alone does not extend its guarantee to an arbitrary external API or database write.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Apache Kafka: Message delivery semantics",
    "source_url": "https://kafka.apache.org/43/design/design/",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-KAFKA-EXTERNAL-EXACTLY-ONCE-01-v1",
    "candidate_record_sha256": "902238d77a87abbf0ac5f1d14d7c7b1cfaed27e2a8b50d542c90d4437733a262",
    "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": "Kafka 4.3 describes exactly-once processing between Kafka topics using transactions and read-committed consumers. For an external destination, the consumer position must be coordinated with the stored output; cooperation from that destination is needed. Kafka transaction success alone does not extend its guarantee to an arbitrary external API or database write.",
    "required_buyer_context": "Input topic offsets, transaction identifiers and consumer isolation configuration. External destination write results and the mechanism coordinating them with progress. Crash or retry recovery evidence linking stored output to the committed consumer position. 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": "Do Kafka transactions make an agent's writes to an external service exactly once?",
    "documented_statement": {
      "status": "documented",
      "statement": "Kafka 4.3 describes exactly-once processing between Kafka topics using transactions and read-committed consumers. For an external destination, the consumer position must be coordinated with the stored output; cooperation from that destination is needed. Kafka transaction success alone does not extend its guarantee to an arbitrary external API or database write.",
      "source_ids": [
        "kafka-external"
      ]
    },
    "buyer_evidence_required": [
      "Input topic offsets, transaction identifiers and consumer isolation configuration.",
      "External destination write results and the mechanism coordinating them with progress.",
      "Crash or retry recovery evidence linking stored output to the committed consumer position."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline end-to-end exactly-once claims without evidence that the external destination coordinates effects and progress."
    },
    "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": "kafka-external",
        "url": "https://kafka.apache.org/43/design/design/",
        "final_url": "https://kafka.apache.org/43/design/design/",
        "title": "Apache Kafka: Message delivery semantics",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T22:37:24.024Z",
        "version_context": "Apache Kafka 4.3 versioned design documentation",
        "sha256": "bcca1c2a60856d1be95d7774beb60e7ff5531ede367529becb787e5772531ef4",
        "bytes": 146232,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "Message Delivery Semantics; Using Transactions"
        ]
      }
    ],
    "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 connector can replay or lose external effects despite transactional handling within the message system.",
      "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": "Input topic offsets, transaction identifiers and consumer isolation configuration. External destination write results and the mechanism coordinating them with progress. Crash or retry recovery evidence linking stored output to the committed consumer position."
    },
    "buyer_relevance": "A connector can replay or lose external effects despite transactional handling within the message system.",
    "refusal_conditions": [
      "Decline end-to-end exactly-once claims without evidence that the external destination coordinates effects and progress."
    ]
  },
  "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#kafka-transaction-external-sink-effect-boundary",
  "machine_readable_record": "/varexis-index/records/kafka-transaction-external-sink-effect-boundary.json"
}
