{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-29T21:43:00.943093Z",
  "record_id": "VXI-EXT-ICE06-DATABRICKS-SHARED-SKU-ORIGIN-ATTRIBUTION-01-v1",
  "record_kind": "external_reference",
  "title": "Databricks shared SKU origin attribution",
  "system": "Databricks",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can a Databricks SKU uniquely identify which product generated usage?",
  "near_questions": [
    "Databricks shared SKU billing origin",
    "serverless jobs SKU product attribution",
    "billing_origin_product cost allocation",
    "product_features usage reconciliation"
  ],
  "supported_claims": [
    {
      "claim": "Several Databricks products can share a SKU. The guide identifies billing_origin_product and product_features as the fields for distinguishing the originating product and features, including shared serverless-jobs billing. SKU-only allocation can merge different workloads; preserve the applicable product fields and their documented population conditions.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Billing attribution fields do not independently establish the human requester or purchasing authority.",
    "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": "Several Databricks products can share a SKU. The guide identifies billing_origin_product and product_features as the fields for distinguishing the originating product and features, including shared serverless-jobs billing. SKU-only allocation can merge different workloads; preserve the applicable product fields and their documented population conditions.",
  "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-SHARED-SKU-ORIGIN-ATTRIBUTION-01-v1",
    "candidate_record_sha256": "24c7d5080334183ce1e1a0f329b58b8fcbced6e185d33bbd54b53745056e6d31",
    "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": "Several Databricks products can share a SKU. The guide identifies billing_origin_product and product_features as the fields for distinguishing the originating product and features, including shared serverless-jobs billing. SKU-only allocation can merge different workloads; preserve the applicable product fields and their documented population conditions.",
    "required_buyer_context": "sku_name; billing_origin_product; product_features; workload metadata; attribution policy. 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": "Can a Databricks SKU uniquely identify which product generated usage?",
    "documented_statement": {
      "status": "documented",
      "statement": "Several Databricks products can share a SKU. The guide identifies billing_origin_product and product_features as the fields for distinguishing the originating product and features, including shared serverless-jobs billing. SKU-only allocation can merge different workloads; preserve the applicable product fields and their documented population conditions.",
      "source_ids": [
        "db-billing"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "An operator allocates all serverless-jobs SKU cost to a single workflow. Different platform features can be charged to the wrong internal owner. Adds a native shared-SKU product attribution mechanism rather than FOCUS invoice line grain. This is an operational review inference, not an observed deployment outcome.",
      "source_ids": [
        "db-billing"
      ]
    },
    "buyer_evidence_required": [
      "sku_name",
      "billing_origin_product",
      "product_features",
      "workload metadata",
      "attribution policy"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Billing attribution fields do not independently establish the human requester or purchasing authority."
    },
    "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": "An operator allocates all serverless-jobs SKU cost to a single workflow. Different platform features can be charged to the wrong internal owner.",
      "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": "Billing origin product reference"
    },
    "buyer_relevance": "An operator allocates all serverless-jobs SKU cost to a single workflow. Different platform features can be charged to the wrong internal owner.",
    "refusal_conditions": [
      "Billing attribution fields do not independently establish the human requester or purchasing authority.",
      "Do not infer deployment conformance, authority or successful outcomes from source documentation."
    ],
    "decision_context": {
      "operator": "FinOps and invoice-reconciliation operator",
      "scenario": "An operator allocates all serverless-jobs SKU cost to a single workflow.",
      "consequence": "Different platform features can be charged to the wrong internal owner.",
      "confidence": "Primary documentation assertion supported; deployment applicability unverified"
    },
    "novelty_review": {
      "candidate_id": "ICE06-C0EE9B7616F1",
      "disposition": "NEW",
      "nearest_record_id": "VXI-EXT-PROCUREMENT-FOCUS-INVOICE-DETAIL-GRAIN-IDENTITY-01-v1",
      "nearest_record_url": "/varexis-index/records/focus-invoice-detail-grain-identity.json",
      "nearest_record_sha256": "83a06c153a53f848692df753275140ac298b2d30fbef30fe30f98b0aa3aee46b",
      "material_distinction": "Adds a native shared-SKU product attribution mechanism rather than FOCUS invoice line grain.",
      "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-SHARED-SKU-ORIGIN-ATTRIBUTION-01-v1"
      },
      "record_url": "/varexis-index/records/databricks-shared-sku-origin-attribution.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": "An operator allocates all serverless-jobs SKU cost to a single workflow. Different platform features can be charged to the wrong internal owner.",
    "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-shared-sku-origin-attribution",
  "machine_readable_record": "/varexis-index/records/databricks-shared-sku-origin-attribution.json"
}