{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T16:34:01.009Z",
  "record_id": "VXI-EXT-PROCUREMENT-QDRANT-WRITE-WAIT-REPLICA-ACKNOWLEDGEMENT-01-v1",
  "record_kind": "external_reference",
  "title": "Qdrant completed writes and replica acknowledgement",
  "system": "Qdrant",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a Qdrant write completed with wait=true establish that every configured replica has applied the change?",
  "near_questions": [
    "Does Qdrant wait=true mean every replica finished?",
    "Can a Qdrant consistency error leave a write partially applied?",
    "How does write_consistency_factor affect deletion confirmation?",
    "Can an offline Qdrant replica catch up after a completed write?"
  ],
  "supported_claims": [
    {
      "claim": "Qdrant distinguishes a queued acknowledgement from a completed operation through wait. Replica acknowledgement is separately governed by write_consistency_factor, whose default is one. Offline replicas may receive updates after recovery. An error caused by insufficient acknowledgements can still leave a change partially applied. Completion must be interpreted with the configured replication and consistency requirements.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Universal replica convergence or rollback from a single response",
    "The actual state of each replica and subsequent read results are not inspected.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Qdrant distinguishes a queued acknowledgement from a completed operation through wait. Replica acknowledgement is separately governed by write_consistency_factor, whose default is one. Offline replicas may receive updates after recovery. An error caused by insufficient acknowledgements can still leave a change partially applied. Completion must be interpreted with the configured replication and consistency requirements.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Points - Qdrant",
    "source_url": "https://qdrant.tech/documentation/manage-data/points/",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-QDRANT-WRITE-WAIT-REPLICA-ACKNOWLEDGEMENT-01-v1",
    "candidate_record_sha256": "93cd6848762dae95f37c465dbc5afdabf713a575dca85afedbd0a1e4db4cd500",
    "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": "Qdrant distinguishes a queued acknowledgement from a completed operation through wait. Replica acknowledgement is separately governed by write_consistency_factor, whose default is one. Offline replicas may receive updates after recovery. An error caused by insufficient acknowledgements can still leave a change partially applied. Completion must be interpreted with the configured replication and consistency requirements.",
    "required_buyer_context": "Operation ID, wait setting and response status; Replication factor, write_consistency_factor and replica health; Read consistency requirements and subsequent observations. 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-24",
    "claim_to_check": "Does a Qdrant write completed with wait=true establish that every configured replica has applied the change?",
    "documented_statement": {
      "status": "documented",
      "statement": "Qdrant distinguishes a queued acknowledgement from a completed operation through wait. Replica acknowledgement is separately governed by write_consistency_factor, whose default is one. Offline replicas may receive updates after recovery. An error caused by insufficient acknowledgements can still leave a change partially applied. Completion must be interpreted with the configured replication and consistency requirements.",
      "source_ids": [
        "qdrant-points",
        "qdrant-consistency"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Reconcile operation status, required acknowledgements and replica state before treating a deletion as cluster-wide.",
      "source_ids": [
        "qdrant-points",
        "qdrant-consistency"
      ]
    },
    "buyer_evidence_required": [
      "Operation ID, wait setting and response status",
      "Replication factor, write_consistency_factor and replica health",
      "Read consistency requirements and subsequent observations"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse all-replica completion claims based only on wait=true or a write error."
    },
    "unknowns": "The actual state of each replica and subsequent read results are not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The actual state of each replica and subsequent read results are not inspected."
    },
    "evidence_sources": [
      {
        "source_id": "qdrant-points",
        "url": "https://qdrant.tech/documentation/manage-data/points/",
        "final_url": "https://qdrant.tech/documentation/manage-data/points/",
        "status": 200,
        "captured_at_utc": "2026-10-24T16:09:54.900Z",
        "sha256": "c4f3006196e510025b254aecf7d7408bf7f2a7e223b5a8e05e851e059cfed02e",
        "bytes": 545679,
        "title": "Points - Qdrant",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "version_context": "Rolling official vendor documentation captured on 2026-10-24; account tier, service version, enabled features and buyer configuration require separate verification.",
        "reviewed_sections": [
          "Acknowledged versus completed operations and wait"
        ]
      },
      {
        "source_id": "qdrant-consistency",
        "url": "https://qdrant.tech/documentation/scaling/consistency-guarantees/",
        "final_url": "https://qdrant.tech/documentation/scaling/consistency-guarantees/",
        "status": 200,
        "captured_at_utc": "2026-10-24T16:04:03.664Z",
        "sha256": "8f596dd0db2c2f5ccf676aa068e84fe0479d898c5fadb72e5d5cb8ef62b3a11c",
        "bytes": 162008,
        "title": "Consistency Guarantees - Qdrant",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "version_context": "Rolling official vendor documentation captured on 2026-10-24; account tier, service version, enabled features and buyer configuration require separate verification.",
        "reviewed_sections": [
          "write_consistency_factor",
          "Offline replicas and partially applied errors"
        ]
      }
    ],
    "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": "Avoid mistaking an accepted cleanup or partial write for confirmed cluster-wide state.",
      "free": "Complete review, sources, practical questions 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 the documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Avoid mistaking an accepted cleanup or partial write for confirmed cluster-wide state.",
    "refusal_conditions": [
      "Refuse all-replica completion claims based only on wait=true or a write error."
    ]
  },
  "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": "Avoid mistaking an accepted cleanup or partial write for confirmed cluster-wide state.",
    "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#qdrant-write-wait-replica-acknowledgement",
  "machine_readable_record": "/varexis-index/records/qdrant-write-wait-replica-acknowledgement.json"
}
