{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-22T21:15:08.873Z",
  "record_id": "VXI-EXT-PROCUREMENT-DATABRICKS-DROP-OBJECT-STORAGE-PURGE-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "Databricks Unity Catalog: Dropped objects and delayed file purge",
  "system": "Databricks",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does dropping a Unity Catalog table or volume immediately delete its underlying files?",
  "near_questions": [
    "Does dropping an external Databricks table delete cloud storage files?",
    "Are managed Unity Catalog files erased as soon as a table is dropped?",
    "Can cloud storage policies retain data after Unity Catalog purge?",
    "What evidence distinguishes dropped metadata from deleted Databricks data?"
  ],
  "supported_claims": [
    {
      "claim": "For external tables and volumes, Unity Catalog removes metadata while underlying files remain. Managed files pass through a recovery window and asynchronous purge; the captured guide allows roughly 7–30 days after deletion. Customer storage versioning or soft-delete policies can retain files beyond purge. Object type and storage policy determine the residual-data boundary.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Immediate erasure, guaranteed recovery or removal of cloud-retained copies",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "For external tables and volumes, Unity Catalog removes metadata while underlying files remain. Managed files pass through a recovery window and asynchronous purge; the captured guide allows roughly 7–30 days after deletion. Customer storage versioning or soft-delete policies can retain files beyond purge. Object type and storage policy determine the residual-data boundary.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Object storage lifecycle in Unity Catalog",
    "source_url": "https://docs.databricks.com/aws/en/data-governance/unity-catalog/object-storage-lifecycle",
    "checked_on": "2026-10-22",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-DATABRICKS-DROP-OBJECT-STORAGE-PURGE-BOUNDARY-01-v1",
    "candidate_record_sha256": "947371479707acdd80e63b9589194df49cb13e20b24913780195bd7a14cef879",
    "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": "For external tables and volumes, Unity Catalog removes metadata while underlying files remain. Managed files pass through a recovery window and asynchronous purge; the captured guide allows roughly 7–30 days after deletion. Customer storage versioning or soft-delete policies can retain files beyond purge. Object type and storage policy determine the residual-data boundary.",
    "required_buyer_context": "Object type and managed or external storage mapping; Deletion time, recovery eligibility and purge observations; Cloud versioning, soft-delete and lifecycle settings. 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-22",
    "claim_to_check": "Does dropping a Unity Catalog table or volume immediately delete its underlying files?",
    "documented_statement": {
      "status": "documented",
      "statement": "For external tables and volumes, Unity Catalog removes metadata while underlying files remain. Managed files pass through a recovery window and asynchronous purge; the captured guide allows roughly 7–30 days after deletion. Customer storage versioning or soft-delete policies can retain files beyond purge. Object type and storage policy determine the residual-data boundary.",
      "source_ids": [
        "databricks-lifecycle"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "A dropped catalogue entry is not a complete data-removal receipt.",
      "source_ids": [
        "databricks-lifecycle"
      ]
    },
    "buyer_evidence_required": [
      "Object type and managed or external storage mapping",
      "Deletion time, recovery eligibility and purge observations",
      "Cloud versioning, soft-delete and lifecycle settings"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse verified-erasure or universal-recovery claims without object-specific storage evidence."
    },
    "unknowns": "Purge completion, retained versions and recovery eligibility are unobserved.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Purge completion, retained versions and recovery eligibility are unobserved."
    },
    "evidence_sources": [
      {
        "source_id": "databricks-lifecycle",
        "url": "https://docs.databricks.com/aws/en/data-governance/unity-catalog/object-storage-lifecycle",
        "final_url": "https://docs.databricks.com/aws/en/data-governance/unity-catalog/object-storage-lifecycle",
        "title": "Object storage lifecycle in Unity Catalog",
        "checked_on": "2026-10-22",
        "captured_at_utc": "2026-10-22T21:06:18.229Z",
        "version_context": "Databricks on AWS guide last updated 2026-10-02; captured 2026-10-22. Storage-type distinctions apply.",
        "sha256": "c7e36de748e470132d127ea50b98d196b2b32ed3adac1f5ab37d070583b7f397",
        "bytes": 39649,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Storage type",
          "Recovery window",
          "Purge"
        ],
        "capture_status": 200,
        "rights_review": "Factual paraphrase and source metadata only; response body retained privately and not redistributed."
      }
    ],
    "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 signing off data exit while underlying cloud files remain.",
      "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 signing off data exit while underlying cloud files remain.",
    "refusal_conditions": [
      "Refuse verified-erasure or universal-recovery claims without object-specific storage evidence."
    ]
  },
  "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 signing off data exit while underlying cloud files remain.",
    "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#databricks-drop-object-storage-purge-boundary",
  "machine_readable_record": "/varexis-index/records/databricks-drop-object-storage-purge-boundary.json"
}
