{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T22:44:07.049Z",
  "record_id": "VXI-EXT-PROCUREMENT-OUTBOX-DUAL-WRITE-01-v1",
  "record_kind": "external_reference",
  "title": "Transactional outbox: Commit and event publication",
  "system": "AWS Prescriptive Guidance",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can a database change commit while its agent completion event is never published?",
  "near_questions": [
    "Did the database commit without publishing the event?",
    "What is the transactional outbox evidence boundary?",
    "Can an outbox relay publish the same event twice?",
    "Which committed change owns this outbox entry?",
    "Is an absent completion event proof of no effect?",
    "Was the pending event saved with the database change?",
    "What happened between commit and notification?",
    "How should an operator reconcile an outbox backlog?",
    "Which consumer handled the relayed event?",
    "Does an outbox remove the need for consumer deduplication?",
    "Can INDEX confirm an outbox implementation?",
    "Is transactional outbox guidance a deployment guarantee?"
  ],
  "supported_claims": [
    {
      "claim": "AWS describes the dual-write gap between a database update and a message notification: one can succeed while the other fails. A transactional outbox records the change and pending event within one database transaction, then publishes separately. The relay can publish duplicates, so consumers still need duplicate handling. This is architecture guidance, not evidence that a buyer implemented the pattern.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Atomicity across arbitrary services or proof that the buyer uses an outbox",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "AWS describes the dual-write gap between a database update and a message notification: one can succeed while the other fails. A transactional outbox records the change and pending event within one database transaction, then publishes separately. The relay can publish duplicates, so consumers still need duplicate handling. This is architecture guidance, not evidence that a buyer implemented the pattern.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "AWS Prescriptive Guidance: Transactional outbox pattern",
    "source_url": "https://docs.aws.amazon.com/prescriptive-guidance/latest/cloud-design-patterns/transactional-outbox.html",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-OUTBOX-DUAL-WRITE-01-v1",
    "candidate_record_sha256": "4341039e0f8a7537652cb206cf1e2d2443970abe0d5fedf4763731c7fd5bd24e",
    "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": "AWS describes the dual-write gap between a database update and a message notification: one can succeed while the other fails. A transactional outbox records the change and pending event within one database transaction, then publishes separately. The relay can publish duplicates, so consumers still need duplicate handling. This is architecture guidance, not evidence that a buyer implemented the pattern.",
    "required_buyer_context": "Database transaction outcome and corresponding outbox entry or equivalent commit evidence. Relay attempts, publication acknowledgements and stable event-to-action identifiers. Consumer results and treatment of repeated or missing events. 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": "Can a database change commit while its agent completion event is never published?",
    "documented_statement": {
      "status": "documented",
      "statement": "AWS describes the dual-write gap between a database update and a message notification: one can succeed while the other fails. A transactional outbox records the change and pending event within one database transaction, then publishes separately. The relay can publish duplicates, so consumers still need duplicate handling. This is architecture guidance, not evidence that a buyer implemented the pattern.",
      "source_ids": [
        "outbox"
      ]
    },
    "buyer_evidence_required": [
      "Database transaction outcome and corresponding outbox entry or equivalent commit evidence.",
      "Relay attempts, publication acknowledgements and stable event-to-action identifiers.",
      "Consumer results and treatment of repeated or missing events."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline an event-complete or safe-retry conclusion while committed changes and publication outcomes remain unreconciled."
    },
    "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": "outbox",
        "url": "https://docs.aws.amazon.com/prescriptive-guidance/latest/cloud-design-patterns/transactional-outbox.html",
        "final_url": "https://docs.aws.amazon.com/prescriptive-guidance/latest/cloud-design-patterns/transactional-outbox.html",
        "title": "AWS Prescriptive Guidance: Transactional outbox pattern",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T22:37:22.229Z",
        "version_context": "Architecture guidance; not a deployed service guarantee",
        "sha256": "8444f45302b4af60a33ae465c2fac9a48190a915a5c2b1f893692799b6546d7f",
        "bytes": 30822,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "Intent; Issues and considerations"
        ]
      }
    ],
    "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": "Missing completion events can conceal committed actions and make a blind retry duplicate their effects.",
      "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": "Database transaction outcome and corresponding outbox entry or equivalent commit evidence. Relay attempts, publication acknowledgements and stable event-to-action identifiers. Consumer results and treatment of repeated or missing events."
    },
    "buyer_relevance": "Missing completion events can conceal committed actions and make a blind retry duplicate their effects.",
    "refusal_conditions": [
      "Decline an event-complete or safe-retry conclusion while committed changes and publication outcomes remain unreconciled."
    ]
  },
  "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#transactional-outbox-commit-event-publication-gap",
  "machine_readable_record": "/varexis-index/records/transactional-outbox-commit-event-publication-gap.json"
}
