{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T22:44:07.049Z",
  "record_id": "VXI-EXT-PROCUREMENT-SQS-REDRIVE-LINEAGE-01-v1",
  "record_kind": "external_reference",
  "title": "SQS: Redrive identity and recovery lineage",
  "system": "Amazon SQS",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can an SQS redrive preserve the original message identity and undo messages already moved?",
  "near_questions": [
    "Why did an SQS redriven message get a new ID?",
    "Does SQS redrive reset enqueue time?",
    "How can an action be traced across SQS redrive?",
    "Can new SQS traffic interleave with recovered messages?",
    "Does canceling a redrive recall moved messages?",
    "Which messages moved before redrive cancellation?",
    "What retention applies after SQS redrive?",
    "Is the old message ID enough for recovery correlation?",
    "Which destination consumed the redriven action?",
    "Was the application action ID retained during redrive?",
    "What evidence closes an SQS move task?",
    "Can INDEX inspect actual redriven messages?"
  ],
  "supported_claims": [
    {
      "claim": "SQS treats redriven messages as new messages with new message IDs and enqueue times, resetting retention. Redriven traffic can interleave with newly produced messages. Canceling a move leaves messages already moved at their destination. Recovery correlation therefore needs application-level action references and destination observations, not only the old message ID or a canceled move status.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Original message-ID preservation, recall of moved messages or once-only execution",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "SQS treats redriven messages as new messages with new message IDs and enqueue times, resetting retention. Redriven traffic can interleave with newly produced messages. Canceling a move leaves messages already moved at their destination. Recovery correlation therefore needs application-level action references and destination observations, not only the old message ID or a canceled move status.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Amazon SQS: Dead-letter queue redrive",
    "source_url": "https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-configure-dead-letter-queue-redrive.html",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SQS-REDRIVE-LINEAGE-01-v1",
    "candidate_record_sha256": "c44e538ea1ace62d4d4a36733d0ade91cf4c21c8cb54a1e0a61fb8fb15782d24",
    "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": "SQS treats redriven messages as new messages with new message IDs and enqueue times, resetting retention. Redriven traffic can interleave with newly produced messages. Canceling a move leaves messages already moved at their destination. Recovery correlation therefore needs application-level action references and destination observations, not only the old message ID or a canceled move status.",
    "required_buyer_context": "Original message and stable application-action references with the redrive task identifier. Destination queue, new message references and concurrent producer activity. Move cancellation result, already-moved messages and consumer outcomes. 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 an SQS redrive preserve the original message identity and undo messages already moved?",
    "documented_statement": {
      "status": "documented",
      "statement": "SQS treats redriven messages as new messages with new message IDs and enqueue times, resetting retention. Redriven traffic can interleave with newly produced messages. Canceling a move leaves messages already moved at their destination. Recovery correlation therefore needs application-level action references and destination observations, not only the old message ID or a canceled move status.",
      "source_ids": [
        "sqs-redrive"
      ]
    },
    "buyer_evidence_required": [
      "Original message and stable application-action references with the redrive task identifier.",
      "Destination queue, new message references and concurrent producer activity.",
      "Move cancellation result, already-moved messages and consumer outcomes."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline restored-lineage or fully-recalled claims without correlating moved messages and destination processing."
    },
    "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": "sqs-redrive",
        "url": "https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-configure-dead-letter-queue-redrive.html",
        "final_url": "https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-configure-dead-letter-queue-redrive.html",
        "title": "Amazon SQS: Dead-letter queue redrive",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T22:37:22.229Z",
        "version_context": "Rolling SQS developer guide; message identity and move cancellation",
        "sha256": "4f49146de66f947a2fbf27fab72889d46d6ba72170336c8718d783f49ff8030d",
        "bytes": 41404,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "Dead-letter queue redrive; Canceling an in-progress redrive"
        ]
      }
    ],
    "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": "Operators need to distinguish recovered actions from new work and identify messages still eligible for execution.",
      "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": "Original message and stable application-action references with the redrive task identifier. Destination queue, new message references and concurrent producer activity. Move cancellation result, already-moved messages and consumer outcomes."
    },
    "buyer_relevance": "Operators need to distinguish recovered actions from new work and identify messages still eligible for execution.",
    "refusal_conditions": [
      "Decline restored-lineage or fully-recalled claims without correlating moved messages and destination processing."
    ]
  },
  "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#sqs-dead-letter-redrive-identity-lineage",
  "machine_readable_record": "/varexis-index/records/sqs-dead-letter-redrive-identity-lineage.json"
}
