{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T16:34:01.009Z",
  "record_id": "VXI-EXT-PROCUREMENT-DATABRICKS-DELETION-VECTOR-PHYSICAL-REMOVAL-STAGES-01-v1",
  "record_kind": "external_reference",
  "title": "Databricks deletion vectors and physical file cleanup",
  "system": "Databricks",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a Delta row deletion using deletion vectors immediately remove the row bytes from all underlying data files?",
  "near_questions": [
    "Do Databricks deletion vectors immediately erase row bytes?",
    "Why can old files remain after REORG APPLY PURGE?",
    "Does compaction guarantee removal of every soft-deleted row?",
    "Which stages distinguish Delta logical deletion from file cleanup?"
  ],
  "supported_claims": [
    {
      "claim": "Databricks deletion vectors mark rows as removed without immediately rewriting the underlying data files. REORG TABLE with APPLY PURGE rewrites files containing soft-deleted data, but the old files remain until eligible VACUUM cleanup. Other compaction operations do not necessarily rewrite every affected file. Logical deletion, file rewrite and retained-file cleanup are distinct stages.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Immediate physical erasure of deleted rows or verified removal from every copy",
    "Actual file contents, retained versions, caches and external copies are unverified.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Databricks deletion vectors mark rows as removed without immediately rewriting the underlying data files. REORG TABLE with APPLY PURGE rewrites files containing soft-deleted data, but the old files remain until eligible VACUUM cleanup. Other compaction operations do not necessarily rewrite every affected file. Logical deletion, file rewrite and retained-file cleanup are distinct stages.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Deletion vectors in Databricks | Databricks on AWS",
    "source_url": "https://docs.databricks.com/aws/en/delta/deletion-vectors",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-DATABRICKS-DELETION-VECTOR-PHYSICAL-REMOVAL-STAGES-01-v1",
    "candidate_record_sha256": "5008a9837224d699258aec3e71f8df2e44f361815168429b1200a1841cb4ed39",
    "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": "Databricks deletion vectors mark rows as removed without immediately rewriting the underlying data files. REORG TABLE with APPLY PURGE rewrites files containing soft-deleted data, but the old files remain until eligible VACUUM cleanup. Other compaction operations do not necessarily rewrite every affected file. Logical deletion, file rewrite and retained-file cleanup are distinct stages.",
    "required_buyer_context": "Table deletion-vector support and affected operations; Rewrite completion and resulting file/version inventory; Retention eligibility, cleanup results and separate copy inventory. 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 Delta row deletion using deletion vectors immediately remove the row bytes from all underlying data files?",
    "documented_statement": {
      "status": "documented",
      "statement": "Databricks deletion vectors mark rows as removed without immediately rewriting the underlying data files. REORG TABLE with APPLY PURGE rewrites files containing soft-deleted data, but the old files remain until eligible VACUUM cleanup. Other compaction operations do not necessarily rewrite every affected file. Logical deletion, file rewrite and retained-file cleanup are distinct stages.",
      "source_ids": [
        "databricks-deletion-vectors",
        "databricks-vacuum"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Require evidence for the applicable stages and retention conditions before accepting a physical-removal assertion.",
      "source_ids": [
        "databricks-deletion-vectors",
        "databricks-vacuum"
      ]
    },
    "buyer_evidence_required": [
      "Table deletion-vector support and affected operations",
      "Rewrite completion and resulting file/version inventory",
      "Retention eligibility, cleanup results and separate copy inventory"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse physical-erasure claims based solely on row invisibility or a logical DELETE result."
    },
    "unknowns": "Actual file contents, retained versions, caches and external copies are unverified.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Actual file contents, retained versions, caches and external copies are unverified."
    },
    "evidence_sources": [
      {
        "source_id": "databricks-deletion-vectors",
        "url": "https://docs.databricks.com/aws/en/delta/deletion-vectors",
        "final_url": "https://docs.databricks.com/aws/en/tables/features/deletion-vectors",
        "status": 200,
        "captured_at_utc": "2026-10-24T16:04:05.835Z",
        "sha256": "9e9f69cb26915fa85812677b2fb629a24b606b90707b664194131d22884af0b6",
        "bytes": 38045,
        "title": "Deletion vectors in Databricks | Databricks on AWS",
        "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": [
          "Logical soft deletion",
          "REORG rewrite and VACUUM cleanup"
        ]
      },
      {
        "source_id": "databricks-vacuum",
        "url": "https://docs.databricks.com/aws/en/delta/vacuum",
        "final_url": "https://docs.databricks.com/aws/en/tables/operations/vacuum",
        "status": 200,
        "captured_at_utc": "2026-10-24T16:04:06.004Z",
        "sha256": "21c3da4524c9c89a85c90935b727ff4cf3183e1644e608a330203b78278c9693",
        "bytes": 49028,
        "title": "Remove unused data files with vacuum | Databricks on AWS",
        "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": [
          "Data-file versus log cleanup",
          "Lost Time Travel and disk-cache exception"
        ]
      }
    ],
    "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": "Determine what remains to be evidenced after data stops appearing in normal queries.",
      "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": "Determine what remains to be evidenced after data stops appearing in normal queries.",
    "refusal_conditions": [
      "Refuse physical-erasure claims based solely on row invisibility or a logical DELETE result."
    ]
  },
  "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": "Determine what remains to be evidenced after data stops appearing in normal queries.",
    "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-deletion-vector-physical-removal-stages",
  "machine_readable_record": "/varexis-index/records/databricks-deletion-vector-physical-removal-stages.json"
}
