{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-29T21:43:00.943093Z",
  "record_id": "VXI-EXT-ICE06-DATABRICKS-USAGE-RETRACTION-RESTATEMENT-01-v1",
  "record_kind": "external_reference",
  "title": "Databricks usage retraction restatement",
  "system": "Databricks",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "How should Databricks billing usage corrections affect a cost total?",
  "near_questions": [
    "Databricks usage retraction restatement",
    "negative usage correction billing table",
    "Databricks retraction without replacement",
    "record_type corrected usage total"
  ],
  "supported_claims": [
    {
      "claim": "Corrections add a negative RETRACTION to cancel the original usage and normally a RESTATEMENT containing corrected fields. If the original should not have existed, there may be only a retraction. Retain record_type and signed quantities across all related rows; ignoring negatives or requiring every correction to have a restatement can leave an incorrect total.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Usage corrections do not establish invoice settlement or independent accuracy of the underlying meter.",
    "Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.",
    "No expanded capabilities or licences for existing INDEX executables."
  ],
  "public_summary": "Corrections add a negative RETRACTION to cancel the original usage and normally a RESTATEMENT containing corrected fields. If the original should not have existed, there may be only a retraction. Retain record_type and signed quantities across all related rows; ignoring negatives or requiring every correction to have a restatement can leave an incorrect total.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Databricks: Billable usage system table",
    "source_url": "https://docs.databricks.com/gcp/en/admin/system-tables/billing",
    "checked_on": "2026-10-29",
    "candidate_record_id": "VXI-EXT-ICE06-DATABRICKS-USAGE-RETRACTION-RESTATEMENT-01-v1",
    "candidate_record_sha256": "8fa6b69b23a95acb83c9d85d2c1f6be22bb659d6d79ec09694567035bdaa370e",
    "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": "Corrections add a negative RETRACTION to cancel the original usage and normally a RESTATEMENT containing corrected fields. If the original should not have existed, there may be only a retraction. Retain record_type and signed quantities across all related rows; ignoring negatives or requiring every correction to have a restatement can leave an incorrect total.",
    "required_buyer_context": "ORIGINAL RETRACTION and RESTATEMENT rows; signed usage quantities; product and accounting dimensions; observation date. 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-29",
    "claim_to_check": "How should Databricks billing usage corrections affect a cost total?",
    "documented_statement": {
      "status": "documented",
      "statement": "Corrections add a negative RETRACTION to cancel the original usage and normally a RESTATEMENT containing corrected fields. If the original should not have existed, there may be only a retraction. Retain record_type and signed quantities across all related rows; ignoring negatives or requiring every correction to have a restatement can leave an incorrect total.",
      "source_ids": [
        "db-billing"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "A pipeline loads only original records or positive quantities. Superseded usage remains charged in the internal report. Adds Databricks record_type and retraction-only behavior rather than Google adjustment_info grouping. This is an operational review inference, not an observed deployment outcome.",
      "source_ids": [
        "db-billing"
      ]
    },
    "buyer_evidence_required": [
      "ORIGINAL RETRACTION and RESTATEMENT rows",
      "signed usage quantities",
      "product and accounting dimensions",
      "observation date"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Usage corrections do not establish invoice settlement or independent accuracy of the underlying meter."
    },
    "unknowns": "The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "No buyer deployment or transaction was observed."
    },
    "evidence_sources": [
      {
        "source_id": "db-billing",
        "url": "https://docs.databricks.com/gcp/en/admin/system-tables/billing",
        "final_url": "https://docs.databricks.com/gcp/en/admin/system-tables/billing",
        "captured_at_utc": "2026-10-29T19:10:37.122713+00:00",
        "status": 200,
        "content_type": "text/html",
        "bytes": 71057,
        "sha256": "54ae6100041a7bfc0378b908ce190705ebd9b086a4d5dd7ba6016de0b1e24a72",
        "publisher": "Databricks",
        "version_context": "Rolling official documentation; applicability is limited to the exact captured response and its stated service, API and feature constraints. Recheck present support before current reliance. Source captured 2026-10-29T19:10:37.122713+00:00.",
        "rights_review": "Public original factual paraphrase and attributed source metadata only. Captured documentation bodies, code examples, images and vendor marks remain private. No vendor software licence, certification or buyer deployment assurance is granted.",
        "capture_integrity_verified": true,
        "source_assertion_reviewed": true,
        "title": "Databricks: Billable usage system table",
        "checked_on": "2026-10-29",
        "capture_status": 200,
        "claim_review_completed": true,
        "hash_basis": "SHA-256 of captured HTTP response body bytes",
        "reviewed_sections": [
          "Record type reference",
          "Record availability",
          "Billing origin product reference"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations locally; they do not inspect provider accounts, verify live behaviour, enforce decisions or certify compliance.",
    "paid_value": {
      "decision_context": "A pipeline loads only original records or positive quantities. Superseded usage remains charged in the internal report.",
      "free": "Complete source review, questions, provenance and limitations; free to read and save locally.",
      "single_request": "Unavailable for this publication-only record; historical saved retrieval is unchanged.",
      "evidence_receipt": "Unavailable for this publication-only record; no paid retrieval entitlement is added.",
      "excluded": [
        "Fresh source research",
        "Native provider integration or schema support",
        "Live inspection or runtime enforcement",
        "Payment settlement or verified deletion",
        "Certification or expanded licences"
      ],
      "integrity": "Hashes identify content versions; they do not prove factual truth or provide a signature."
    },
    "revalidation": {
      "trigger": "Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included.",
      "specific_watch": "Record type reference"
    },
    "buyer_relevance": "A pipeline loads only original records or positive quantities. Superseded usage remains charged in the internal report.",
    "refusal_conditions": [
      "Usage corrections do not establish invoice settlement or independent accuracy of the underlying meter.",
      "Do not infer deployment conformance, authority or successful outcomes from source documentation."
    ],
    "decision_context": {
      "operator": "FinOps and invoice-reconciliation operator",
      "scenario": "A pipeline loads only original records or positive quantities.",
      "consequence": "Superseded usage remains charged in the internal report.",
      "confidence": "Primary documentation assertion supported; deployment applicability unverified"
    },
    "novelty_review": {
      "candidate_id": "ICE06-E7B595CC3135",
      "disposition": "EXTENSION",
      "nearest_record_id": "VXI-EXT-PROCUREMENT-GCP-ADJUSTMENT-GROUP-01-v1",
      "nearest_record_url": "/varexis-index/records/gcp-adjustment-group.json",
      "nearest_record_sha256": "ce0619404b170acbd9f5c1bf04ae8c5a0b54669e8e11ebfdbeb77f528bea10b0",
      "material_distinction": "Adds Databricks record_type and retraction-only behavior rather than Google adjustment_info grouping.",
      "independent_challenge": "PASS"
    },
    "optional_selection": {
      "guide_id": "ai-cost-invoice-assurance",
      "guide_url": "/index-guides/ai-cost-invoice-assurance",
      "guide_manifest": "/varexis-index/decision-guides.json",
      "checker": null,
      "boundary": "Optional adjacent workflow only. This review does not extend a checker input schema or implement native provider validation. Preserve the six canonical guides unchanged."
    },
    "exact_access": {
      "endpoint": "/mcp/catalogue",
      "tool": "get_publication_record",
      "arguments": {
        "record_id": "VXI-EXT-ICE06-DATABRICKS-USAGE-RETRACTION-RESTATEMENT-01-v1"
      },
      "record_url": "/varexis-index/records/databricks-usage-retraction-restatement.json",
      "original_mcp_search": false,
      "paid_saved_retrieval": false
    }
  },
  "niche": {
    "niche_id": "ice06-ai-cost-usage-invoice-assurance",
    "label": "AI Cost, Usage & Invoice Assurance",
    "classification_id": "ai-cost-usage-invoice-assurance",
    "classification_label": "AI Cost, Usage & Invoice Assurance",
    "topic_id": "ai-cost-usage-invoice-assurance",
    "buyer_intent": "A pipeline loads only original records or positive quantities. Superseded usage remains charged in the internal report.",
    "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-usage-retraction-restatement",
  "machine_readable_record": "/varexis-index/records/databricks-usage-retraction-restatement.json"
}