{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T16:34:01.009Z",
  "record_id": "VXI-EXT-PROCUREMENT-QDRANT-ALIAS-SWITCH-RETAINED-COLLECTION-01-v1",
  "record_kind": "external_reference",
  "title": "Qdrant alias switching and retained collections",
  "system": "Qdrant",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does atomically moving a Qdrant alias to a replacement collection remove the old collection and its data?",
  "near_questions": [
    "Can a Qdrant old collection remain after an alias switch?",
    "Does an atomic Qdrant cutover delete the previous dataset?",
    "Should offboarding inventory use collection names as well as aliases?",
    "What does a successful Qdrant alias migration actually establish?"
  ],
  "supported_claims": [
    {
      "claim": "Qdrant aliases are names that refer to collections. Its documented migration pattern creates a replacement collection and atomically switches alias operations so callers can use the new collection. Alias changes and collection deletion are different operations. A successful alias switch establishes routing, not removal of the old collection or its snapshots.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Erasure or access revocation for the previous collection from an alias update",
    "Old collection contents, direct-name access and retained snapshots are unverified.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Qdrant aliases are names that refer to collections. Its documented migration pattern creates a replacement collection and atomically switches alias operations so callers can use the new collection. Alias changes and collection deletion are different operations. A successful alias switch establishes routing, not removal of the old collection or its snapshots.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Collections - Qdrant",
    "source_url": "https://qdrant.tech/documentation/concepts/collections/",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-QDRANT-ALIAS-SWITCH-RETAINED-COLLECTION-01-v1",
    "candidate_record_sha256": "9e74ca905923314472748ec1a5ae2cf101b6195c38a9ed51831e8371e794130d",
    "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 aliases are names that refer to collections. Its documented migration pattern creates a replacement collection and atomically switches alias operations so callers can use the new collection. Alias changes and collection deletion are different operations. A successful alias switch establishes routing, not removal of the old collection or its snapshots.",
    "required_buyer_context": "Alias actions and source/destination collection names; Collection inventory before and after the switch; Old collection and snapshot retention or deletion requirements. 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 atomically moving a Qdrant alias to a replacement collection remove the old collection and its data?",
    "documented_statement": {
      "status": "documented",
      "statement": "Qdrant aliases are names that refer to collections. Its documented migration pattern creates a replacement collection and atomically switches alias operations so callers can use the new collection. Alias changes and collection deletion are different operations. A successful alias switch establishes routing, not removal of the old collection or its snapshots.",
      "source_ids": [
        "qdrant-collections"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Inventory collections by their own identities rather than only through the active alias after a cutover.",
      "source_ids": [
        "qdrant-collections"
      ]
    },
    "buyer_evidence_required": [
      "Alias actions and source/destination collection names",
      "Collection inventory before and after the switch",
      "Old collection and snapshot retention or deletion requirements"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not close an exit task from an alias switch while old collection state remains unaccounted for."
    },
    "unknowns": "Old collection contents, direct-name access and retained snapshots are unverified.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Old collection contents, direct-name access and retained snapshots are unverified."
    },
    "evidence_sources": [
      {
        "source_id": "qdrant-collections",
        "url": "https://qdrant.tech/documentation/concepts/collections/",
        "final_url": "https://qdrant.tech/documentation/manage-data/collections/",
        "status": 200,
        "captured_at_utc": "2026-10-24T16:04:03.661Z",
        "sha256": "1ff607dbc7ff50c72f7149daa0fe3bf7e01184a0f9992669a47554e6c1249984",
        "bytes": 381386,
        "title": "Collections - 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": [
          "Atomic alias changes",
          "Collection identity and deletion"
        ]
      }
    ],
    "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": "Find data left behind after a successful retrieval cutover.",
      "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": "Find data left behind after a successful retrieval cutover.",
    "refusal_conditions": [
      "Do not close an exit task from an alias switch while old collection state remains unaccounted for."
    ]
  },
  "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": "Find data left behind after a successful retrieval cutover.",
    "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-alias-switch-retained-collection",
  "machine_readable_record": "/varexis-index/records/qdrant-alias-switch-retained-collection.json"
}
