{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T22:44:15.019Z",
  "record_id": "VXI-EXT-PROCUREMENT-WEAVIATE-DELETED-COLLECTION-DANGLING-ALIAS-01-v1",
  "record_kind": "external_reference",
  "title": "Weaviate deleted collections and dangling aliases",
  "system": "Weaviate",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does deleting a Weaviate collection automatically remove every alias that points to it?",
  "near_questions": [
    "Can a Weaviate alias remain after its target collection is deleted?",
    "Which aliases need separate cleanup after Weaviate collection removal?",
    "Does Weaviate collection deletion also remove routing aliases?",
    "What evidence closes dangling alias cleanup during a Weaviate exit?"
  ],
  "supported_claims": [
    {
      "claim": "The pinned collection-alias guide defines an alias as a routing pointer for object operations and queries. Removing it removes the pointer, not its target collection. Conversely, deleting a collection does not automatically remove its aliases. An alias change or disappearance is therefore routing evidence, not proof of collection deletion or a complete migration.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Residual collections, backups and destination contents are not established.",
    "No independently verified physical deletion, complete recovery, legal compliance or security assurance.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "The pinned collection-alias guide defines an alias as a routing pointer for object operations and queries. Removing it removes the pointer, not its target collection. Conversely, deleting a collection does not automatically remove its aliases. An alias change or disappearance is therefore routing evidence, not proof of collection deletion or a complete migration.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Weaviate pinned documentation — collection-aliases",
    "source_url": "https://raw.githubusercontent.com/weaviate/docs/5dcf1d6dcd357a4cfaf613a63d052b932cd2f9c9/docs/weaviate/manage-collections/collection-aliases.mdx",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-WEAVIATE-DELETED-COLLECTION-DANGLING-ALIAS-01-v1",
    "candidate_record_sha256": "3bed5957fa400a7e600b0c219a89de830d2f5d8bc613f8894c4ebb6a09ad83e7",
    "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": "The pinned collection-alias guide defines an alias as a routing pointer for object operations and queries. Removing it removes the pointer, not its target collection. Conversely, deleting a collection does not automatically remove its aliases. An alias change or disappearance is therefore routing evidence, not proof of collection deletion or a complete migration.",
    "required_buyer_context": "Alias-to-collection mapping before and after the change; Underlying collection inventory; Authorised deletion or migration acceptance records. 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 deleting a Weaviate collection automatically remove every alias that points to it?",
    "documented_statement": {
      "status": "documented",
      "statement": "The pinned collection-alias guide defines an alias as a routing pointer for object operations and queries. Removing it removes the pointer, not its target collection. Conversely, deleting a collection does not automatically remove its aliases. An alias change or disappearance is therefore routing evidence, not proof of collection deletion or a complete migration.",
      "source_ids": [
        "weaviate-alias"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Reconcile dangling routing pointers separately from deleted collection data. This is a review judgment, not an observed buyer cleanup.",
      "source_ids": [
        "weaviate-alias"
      ]
    },
    "buyer_evidence_required": [
      "Alias-to-collection mapping before and after the change",
      "Underlying collection inventory",
      "Authorised deletion or migration acceptance records"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse a fully cleaned routing inventory from collection deletion alone."
    },
    "unknowns": "Residual collections, backups and destination contents are not established.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Residual collections, backups and destination contents are not established."
    },
    "evidence_sources": [
      {
        "source_id": "weaviate-alias",
        "url": "https://raw.githubusercontent.com/weaviate/docs/5dcf1d6dcd357a4cfaf613a63d052b932cd2f9c9/docs/weaviate/manage-collections/collection-aliases.mdx",
        "final_url": "https://raw.githubusercontent.com/weaviate/docs/5dcf1d6dcd357a4cfaf613a63d052b932cd2f9c9/docs/weaviate/manage-collections/collection-aliases.mdx",
        "status": 200,
        "captured_at_utc": "2026-10-24T22:28:58.286Z",
        "sha256": "0897b8ca4c3fdb9e09b75739d1e8ec450243612cddcdeddd1c201dccf527cec7",
        "bytes": 12623,
        "title": "Weaviate pinned documentation — collection-aliases",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Original bounded paraphrase; source bodies are captured privately and not redistributed. No repository-wide reuse licence asserted; only limited original factual paraphrase and source attribution are published.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Delete alias and collection lifecycle"
        ],
        "version_context": "Pinned rolling documentation; per-feature minimum versions must remain explicit; pinned weaviate/docs revision 5dcf1d6dcd357a4cfaf613a63d052b932cd2f9c9. Source documentation is not independent evidence of buyer deployment behaviour."
      }
    ],
    "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": "Reconcile dangling routing pointers separately from deleted collection data.",
      "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 pinned source, deployed version, selection policy and retained operation results before relying on a current outcome."
    },
    "buyer_relevance": "Reconcile dangling routing pointers separately from deleted collection data.",
    "refusal_conditions": [
      "Refuse a fully cleaned routing inventory from collection deletion alone."
    ]
  },
  "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": "Reconcile dangling routing pointers separately from deleted collection data.",
    "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#weaviate-deleted-collection-dangling-alias",
  "machine_readable_record": "/varexis-index/records/weaviate-deleted-collection-dangling-alias.json"
}