{
  "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-CONNECTION-THRESHOLD-01-v1",
  "record_kind": "external_reference",
  "title": "Redis WAIT connection and threshold evidence",
  "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 a successful Redis WAIT response establish the requested replication level for every prior application write?",
  "near_questions": [
    "Does Redis WAIT cover writes from every pooled connection?",
    "Can a WAIT timeout still return a replica count?",
    "Must the returned WAIT count meet the requested threshold?",
    "Does WAIT block inside a Redis transaction or script?"
  ],
  "supported_claims": [
    {
      "claim": "Redis WAIT reports how many replicas acknowledged earlier writes on the current connection. It returns a count on timeout as well as success, so that count must be compared with the requested level. In MULTI and other nonblocking contexts it returns immediately rather than waiting. A WAIT call on another pooled connection does not establish the original writes' barrier.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Timeout also returns a count; pooled connections and nonblocking MULTI/script contexts cannot be assumed to provide a global barrier.",
    "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 WAIT reports how many replicas acknowledged earlier writes on the current connection. It returns a count on timeout as well as success, so that count must be compared with the requested level. In MULTI and other nonblocking contexts it returns immediately rather than waiting. A WAIT call on another pooled connection does not establish the original writes' barrier.",
  "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-CONNECTION-THRESHOLD-01-v1",
    "candidate_record_sha256": "f65290c74e003ef4299f003bf2690138cbb8f285ab5ce84cf1c67b5fd09122aa",
    "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 WAIT reports how many replicas acknowledged earlier writes on the current connection. It returns a count on timeout as well as success, so that count must be compared with the requested level. In MULTI and other nonblocking contexts it returns immediately rather than waiting. A WAIT call on another pooled connection does not establish the original writes' barrier.",
    "required_buyer_context": "Connection carrying the writes and WAIT; Requested and returned replica counts; Timeout and blocking context. 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 a successful Redis WAIT response establish the requested replication level for every prior application write?",
    "documented_statement": {
      "status": "documented",
      "statement": "Redis WAIT reports how many replicas acknowledged earlier writes on the current connection. It returns a count on timeout as well as success, so that count must be compared with the requested level. In MULTI and other nonblocking contexts it returns immediately rather than waiting. A WAIT call on another pooled connection does not establish the original writes' barrier.",
      "source_ids": [
        "redis-wait"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Bind a WAIT replication count to prior writes on the same connection and the requested threshold. This is a documentation-review judgment, not an observed deployment outcome.",
      "source_ids": [
        "redis-wait"
      ]
    },
    "buyer_evidence_required": [
      "Connection carrying the writes and WAIT",
      "Requested and returned replica counts",
      "Timeout and blocking context"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse buyer-specific assurance from documentation alone. Timeout also returns a count; pooled connections and nonblocking MULTI/script contexts cannot be assumed to provide a global barrier."
    },
    "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": "Bind a WAIT replication count to prior writes on the same connection and the requested threshold.",
      "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 Command semantics; Remarks 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": "Bind a WAIT replication count to prior writes on the same connection and the requested threshold.",
    "refusal_conditions": [
      "Refuse buyer-specific assurance from documentation alone. Timeout also returns a count; pooled connections and nonblocking MULTI/script contexts cannot be assumed to provide a global barrier."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "audit",
    "classification_label": "Audit, Provenance & Evidence Accountability",
    "topic_id": "audit",
    "buyer_intent": "Bind a WAIT replication count to prior writes on the same connection and the requested threshold.",
    "comparison_role": "supplementary_discovery"
  },
  "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-connection-threshold",
  "machine_readable_record": "/varexis-index/records/redis-wait-connection-threshold.json"
}