{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T12:55:40.483Z",
  "record_id": "VXI-EXT-PROCUREMENT-DATABRICKS-VACUUM-01-v1",
  "record_kind": "external_reference",
  "title": "Delta VACUUM: File retention, history and cached data",
  "system": "Databricks Delta",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does keeping Delta history guarantee old table versions remain queryable after VACUUM?",
  "near_questions": [
    "Can VACUUM remove files needed for time travel?",
    "Is transaction-log retention governed by VACUUM?",
    "Does a retained history row prove data remains recoverable?",
    "What retention window applies to data files?",
    "Are metadata-only deletes physically rewritten?",
    "Can cached Parquet data remain queryable?",
    "Are shallow clones subject to different rules?",
    "Can predictive optimization run cleanup?",
    "Which recovery version does the buyer require?",
    "Is cleanup completion a universal erasure certificate?",
    "What evidence should be retained before maintenance?",
    "Can I save the reviewed history-versus-files boundary?"
  ],
  "supported_claims": [
    {
      "claim": "VACUUM removes eligible unreferenced data files, which can remove the files needed by older table versions. Log retention is a separate process. Metadata-only deletes and cached copies have additional considerations. Retained history entries alone are not proof of recoverable data or complete removal from every execution environment.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "VACUUM removes eligible unreferenced data files, which can remove the files needed by older table versions. Log retention is a separate process. Metadata-only deletes and cached copies have additional considerations. Retained history entries alone are not proof of recoverable data or complete removal from every execution environment.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Databricks VACUUM retention and history",
    "source_url": "https://docs.databricks.com/aws/en/delta/vacuum",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-DATABRICKS-VACUUM-01-v1",
    "candidate_record_sha256": "0736bc9e769adec3d685999ec31c4a3acbe06175a3b2716576a6c9f3bbd7c815",
    "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": "VACUUM removes eligible unreferenced data files, which can remove the files needed by older table versions. Log retention is a separate process. Metadata-only deletes and cached copies have additional considerations. Retained history entries alone are not proof of recoverable data or complete removal from every execution environment.",
    "required_buyer_context": "Table type, runtime, data-file retention, log retention, cleanup history and caches. Effective configuration and dated operational evidence have not been 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-16",
    "claim_to_check": "Retained transaction history guarantees recovery after data-file cleanup.",
    "documented_statement": {
      "status": "documented",
      "statement": "VACUUM removes eligible unreferenced data files, which can remove the files needed by older table versions. Log retention is a separate process. Metadata-only deletes and cached copies have additional considerations. Retained history entries alone are not proof of recoverable data or complete removal from every execution environment.",
      "source_ids": [
        "databricks-vacuum"
      ]
    },
    "buyer_evidence_required": [
      "Data-file and log retention settings.",
      "VACUUM history and required recovery versions.",
      "Deletion-vector, clone and cache scope where applicable."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Require necessary data files and applicable cache evidence before claiming recovery or erasure."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "databricks-vacuum",
        "url": "https://docs.databricks.com/aws/en/delta/vacuum",
        "final_url": "https://docs.databricks.com/aws/en/tables/operations/vacuum",
        "title": "Databricks VACUUM retention and history",
        "checked_on": "2026-10-16",
        "sha256": "cc2be28a7d8b134e8cfb4955120824af32f8f043c8c8d742f99c7635188d288b",
        "bytes": 49083
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Save a bounded recovery and retention review before depending on historical data.",
      "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": "Table type, runtime, data-file retention, log retention, cleanup history and caches."
    }
  },
  "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-vacuum-history-and-cache-boundary",
  "machine_readable_record": "/varexis-index/records/databricks-vacuum-history-and-cache-boundary.json"
}