{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T22:44:07.049Z",
  "record_id": "VXI-EXT-PROCUREMENT-S3-FAILED-REPLICATION-RECOVERY-01-v1",
  "record_kind": "external_reference",
  "title": "S3: Repairing objects with failed replication",
  "system": "Amazon S3",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "What evidence closes recovery for an S3 object marked FAILED for replication?",
  "near_questions": [
    "How can an S3 FAILED replication object be recovered?",
    "Does starting Batch Replication prove recovery completed?",
    "Which source version should exist at the replica destination?",
    "Does re-uploading preserve the original object version?",
    "Can a destination object exist while replication status is FAILED?",
    "What is the ownership caveat for Batch Replication repair?",
    "Which HeadObject status was observed after repair?",
    "Were the batch result and destination state reconciled?",
    "Does fixing a replication rule prove failed objects recovered?",
    "What evidence closes an S3 replication incident?",
    "Which failed replica still needs investigation?",
    "Can INDEX verify destination object versions?"
  ],
  "supported_claims": [
    {
      "claim": "AWS documents HeadObject replication status and S3 Batch Replication as a recovery path for failed objects; re-uploading instead creates new objects that initiate replication. It also warns that Batch Replication might not resolve a FAILED status in the documented destination-ownership case even when the object exists there. Destination existence and source status need reconciliation.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Identical source/destination deletion state or guaranteed recovery from any replication failure",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "AWS documents HeadObject replication status and S3 Batch Replication as a recovery path for failed objects; re-uploading instead creates new objects that initiate replication. It also warns that Batch Replication might not resolve a FAILED status in the documented destination-ownership case even when the object exists there. Destination existence and source status need reconciliation.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Amazon S3: Troubleshooting replication",
    "source_url": "https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication-troubleshoot.html",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-S3-FAILED-REPLICATION-RECOVERY-01-v1",
    "candidate_record_sha256": "0fd76abedb09d9c5f805e5ea16c387637d8f206b112e3bf360dd52e782f7ff71",
    "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 documents HeadObject replication status and S3 Batch Replication as a recovery path for failed objects; re-uploading instead creates new objects that initiate replication. It also warns that Batch Replication might not resolve a FAILED status in the documented destination-ownership case even when the object exists there. Destination existence and source status need reconciliation.",
    "required_buyer_context": "Source object version, replication rule and observed FAILED status. Repair job or new-upload results and any destination-ownership configuration. Destination version observations and unresolved status discrepancies or support findings. 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": "What evidence closes recovery for an S3 object marked FAILED for replication?",
    "documented_statement": {
      "status": "documented",
      "statement": "AWS documents HeadObject replication status and S3 Batch Replication as a recovery path for failed objects; re-uploading instead creates new objects that initiate replication. It also warns that Batch Replication might not resolve a FAILED status in the documented destination-ownership case even when the object exists there. Destination existence and source status need reconciliation.",
      "source_ids": [
        "s3-replicate"
      ]
    },
    "buyer_evidence_required": [
      "Source object version, replication rule and observed FAILED status.",
      "Repair job or new-upload results and any destination-ownership configuration.",
      "Destination version observations and unresolved status discrepancies or support findings."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline recovered-replica claims until source version, repair results and destination observations agree or discrepancies remain explicit."
    },
    "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": "s3-replicate",
        "url": "https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication-troubleshoot.html",
        "final_url": "https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication-troubleshoot.html",
        "title": "Amazon S3: Troubleshooting replication",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T22:37:24.127Z",
        "version_context": "Rolling S3 user guide; FAILED replication recovery",
        "sha256": "319c8cf97489c23edbc7be87877b72b0113106fa07cacf534489e166d8a8efbf",
        "bytes": 40936,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "Checking replication status; FAILED status and Batch Replication"
        ]
      }
    ],
    "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": "Restoring configuration or starting a batch job does not by itself establish that the intended object version is recovered at the destination.",
      "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": "Source object version, replication rule and observed FAILED status. Repair job or new-upload results and any destination-ownership configuration. Destination version observations and unresolved status discrepancies or support findings."
    },
    "buyer_relevance": "Restoring configuration or starting a batch job does not by itself establish that the intended object version is recovered at the destination.",
    "refusal_conditions": [
      "Decline recovered-replica claims until source version, repair results and destination observations agree or discrepancies remain explicit."
    ]
  },
  "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#s3-failed-replication-repair-and-version-reconciliation",
  "machine_readable_record": "/varexis-index/records/s3-failed-replication-repair-and-version-reconciliation.json"
}
