{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-25T20:55:19.974986+00:00",
  "record_id": "VXI-EXT-PROCUREMENT-REDIS-WAIT-FAILOVER-DATA-LOSS-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "Redis WAIT failover retention boundary",
  "system": "Redis official wait documentation",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does Redis WAIT guarantee that an acknowledged write survives failover?",
  "near_questions": [
    "Can a Redis write acknowledged by replicas still be lost?",
    "Does WAIT make Redis strongly consistent?",
    "Is failover guaranteed to promote a replica with the acknowledged write?",
    "What remains unproven after synchronous Redis replication?"
  ],
  "supported_claims": [
    {
      "claim": "Redis documents that WAIT does not make the store strongly consistent. Sentinel and Cluster attempt to promote a suitable replica, but this selection is best effort; even a write acknowledged by multiple replicas can be lost after failover. A replication acknowledgement is useful evidence, not a guarantee of survival under every failure sequence.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Sentinel and Cluster select replicas best effort; acknowledged writes can still be lost.",
    "Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.",
    "No expanded capabilities or licences for existing INDEX executables."
  ],
  "public_summary": "Redis documents that WAIT does not make the store strongly consistent. Sentinel and Cluster attempt to promote a suitable replica, but this selection is best effort; even a write acknowledged by multiple replicas can be lost after failover. A replication acknowledgement is useful evidence, not a guarantee of survival under every failure sequence.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Redis official wait documentation",
    "source_url": "https://redis.io/docs/latest/commands/wait/",
    "checked_on": "2026-10-25",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-REDIS-WAIT-FAILOVER-DATA-LOSS-BOUNDARY-01-v1",
    "candidate_record_sha256": "94ec7be65e2d3fa2e882b1980cf944fb7b44a39ebe7aeb6447a68c4c1f158752",
    "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": "Redis documents that WAIT does not make the store strongly consistent. Sentinel and Cluster attempt to promote a suitable replica, but this selection is best effort; even a write acknowledged by multiple replicas can be lost after failover. A replication acknowledgement is useful evidence, not a guarantee of survival under every failure sequence.",
    "required_buyer_context": "Acknowledged write identity; Replica and failover topology; Observed promoted-node state. 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-25",
    "claim_to_check": "Does Redis WAIT guarantee that an acknowledged write survives failover?",
    "documented_statement": {
      "status": "documented",
      "statement": "Redis documents that WAIT does not make the store strongly consistent. Sentinel and Cluster attempt to promote a suitable replica, but this selection is best effort; even a write acknowledged by multiple replicas can be lost after failover. A replication acknowledgement is useful evidence, not a guarantee of survival under every failure sequence.",
      "source_ids": [
        "redis-wait"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Distinguish acknowledged Redis replication from guaranteed retention through failover. This is a documentation-review judgment, not an observed deployment outcome.",
      "source_ids": [
        "redis-wait"
      ]
    },
    "buyer_evidence_required": [
      "Acknowledged write identity",
      "Replica and failover topology",
      "Observed promoted-node state"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse buyer-specific assurance from documentation alone. Sentinel and Cluster select replicas best effort; acknowledged writes can still be lost."
    },
    "unknowns": "The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected."
    },
    "evidence_sources": [
      {
        "source_id": "redis-wait",
        "url": "https://redis.io/docs/latest/commands/wait/",
        "final_url": "https://redis.io/docs/latest/commands/wait/",
        "status": 200,
        "captured_at_utc": "2026-10-25T20:26:14.125Z",
        "sha256": "ae3b5bae9a7aa7d9046aa523751d6bc57aea04f9640042e3fffe3348c00e9572",
        "bytes": 244032,
        "title": "Redis official wait documentation",
        "hash_basis": "SHA-256 of unmodified HTTP response body bytes",
        "rights_review": "Original factual paraphrase and citation only. Redis documentation and software have distinct applicable licences; no source page or software code is redistributed or relicensed.",
        "checked_on": "2026-10-25",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Command semantics",
          "Remarks",
          "Consistency and WAIT"
        ],
        "version_context": "Rolling Redis official documentation captured 2026-10-25. Command introduction and version-specific exceptions are stated in each bounded answer; deployed product/version/configuration unverified."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Distinguish acknowledged Redis replication from guaranteed retention through failover.",
      "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": "Recheck Consistency and WAIT in Redis official wait documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval."
    },
    "buyer_relevance": "Distinguish acknowledged Redis replication from guaranteed retention through failover.",
    "refusal_conditions": [
      "Refuse buyer-specific assurance from documentation alone. Sentinel and Cluster select replicas best effort; acknowledged writes can still be lost."
    ]
  },
  "niche": {
    "niche_id": "enterprise-ai-data-custody-exit-assurance",
    "label": "Enterprise AI Data Custody & Exit Assurance",
    "classification_id": "custody",
    "classification_label": "AI Data Custody, Retention & Exit Assurance",
    "topic_id": "custody",
    "buyer_intent": "Distinguish acknowledged Redis replication from guaranteed retention through failover.",
    "comparison_role": "matched_custody_addition"
  },
  "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#redis-wait-failover-data-loss-boundary",
  "machine_readable_record": "/varexis-index/records/redis-wait-failover-data-loss-boundary.json"
}