{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T12:55:40.483Z",
  "record_id": "VXI-EXT-PROCUREMENT-LAMBDA-ASYNC-01-v1",
  "record_kind": "external_reference",
  "title": "Lambda async: Accepted events, duplicates and expiry",
  "system": "AWS Lambda",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does successful asynchronous Lambda invocation prove the function completed?",
  "near_questions": [
    "Can Lambda deliver an asynchronous event twice?",
    "Does a successful invocation request prove completion?",
    "Are function errors and throttles retried alike?",
    "Can an event expire before execution?",
    "What happens after all processing attempts fail?",
    "Is a dead-letter queue configured?",
    "Does a failure destination contain invocation context?",
    "Can a saturated function lose aged events?",
    "How does the handler detect repeated work?",
    "Which identifier ties acceptance to completion?",
    "What should procurement request for failure recovery?",
    "Can I save this asynchronous-delivery review?"
  ],
  "supported_claims": [
    {
      "claim": "Asynchronous invocation uses a service queue. Function errors and throttling follow different retry behaviour; duplicate delivery is possible even without a function error. Events can expire or exhaust attempts. Dead-letter queues and failure destinations capture different failure information and require configuration.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "Asynchronous invocation uses a service queue. Function errors and throttling follow different retry behaviour; duplicate delivery is possible even without a function error. Events can expire or exhaust attempts. Dead-letter queues and failure destinations capture different failure information and require configuration.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Lambda asynchronous error handling",
    "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/invocation-async-error-handling.html",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-LAMBDA-ASYNC-01-v1",
    "candidate_record_sha256": "80cc660b21644cf03fc6544a93db6eb2c301b1a93bf2e40734b1ad084f5a5b3a",
    "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": "Asynchronous invocation uses a service queue. Function errors and throttling follow different retry behaviour; duplicate delivery is possible even without a function error. Events can expire or exhaust attempts. Dead-letter queues and failure destinations capture different failure information and require configuration.",
    "required_buyer_context": "Invocation mode, event age, retry policy, concurrency and failure destinations. Effective configuration and dated operational evidence have not been 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-16",
    "claim_to_check": "An accepted asynchronous request guarantees one completed function execution.",
    "documented_statement": {
      "status": "documented",
      "statement": "Asynchronous invocation uses a service queue. Function errors and throttling follow different retry behaviour; duplicate delivery is possible even without a function error. Events can expire or exhaust attempts. Dead-letter queues and failure destinations capture different failure information and require configuration.",
      "source_ids": [
        "lambda-async"
      ]
    },
    "buyer_evidence_required": [
      "Asynchronous retry and maximum event-age settings.",
      "Failure destination or dead-letter configuration.",
      "Function idempotency and completion evidence."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Keep request acceptance separate from verified completion and failure recovery."
    },
    "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": "lambda-async",
        "url": "https://docs.aws.amazon.com/lambda/latest/dg/invocation-async-error-handling.html",
        "final_url": "https://docs.aws.amazon.com/lambda/latest/dg/invocation-async-error-handling.html",
        "title": "Lambda asynchronous error handling",
        "checked_on": "2026-10-16",
        "sha256": "4c2644508e48c2f54bf2bd5e3c7d70b3ebafdfefdbcb07344b85adde88be8382",
        "bytes": 14445
      }
    ],
    "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": "Preserve the acceptance-versus-completion boundary for automated integration review.",
      "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": "Invocation mode, event age, retry policy, concurrency and failure destinations."
    }
  },
  "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#lambda-async-duplicate-expiry-boundary",
  "machine_readable_record": "/varexis-index/records/lambda-async-duplicate-expiry-boundary.json"
}