{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T02:40:06.177Z",
  "record_id": "VXI-EXT-PROCUREMENT-BIGQUERY-MAX-BYTES-01-v1",
  "record_kind": "external_reference",
  "title": "BigQuery maximum bytes: A per-query estimate is not an account budget",
  "system": "BigQuery",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does maximum bytes billed cap every BigQuery charge for an agent workflow?",
  "near_questions": [
    "Which billing model uses maximum bytes billed?",
    "Is the estimate checked before execution?",
    "Can a clustered-table query be conservatively rejected?",
    "Does LIMIT always reduce scanned bytes?",
    "Does the setting cap storage charges?",
    "Can several individually allowed queries exceed a workflow budget?",
    "What estimate did the agent receive?",
    "Does a rejected query prove the actual bytes would exceed the limit?",
    "Which capacity charges need separate review?",
    "What spending authority covers repeated queries?",
    "When should an account-budget claim be refused?",
    "Can I save a per-query cost-boundary review?"
  ],
  "supported_claims": [
    {
      "claim": "For on-demand queries, maximum bytes billed checks an estimate before execution and can reject a query above the limit. Clustered-table estimates can exceed the eventual billed amount. This query setting does not establish an account-wide budget or cover every storage and capacity charge.",
      "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": "For on-demand queries, maximum bytes billed checks an estimate before execution and can reject a query above the limit. Clustered-table estimates can exceed the eventual billed amount. This query setting does not establish an account-wide budget or cover every storage and capacity charge.",
  "related_record_ids": [
    "VXI-EXT-PROCUREMENT-AWS-BUDGET-LATENCY-01-v1",
    "VXI-EXT-PROCUREMENT-AZURE-BUDGET-ALERT-01-v1",
    "VXI-EXT-PROCUREMENT-GCP-BUDGET-MODES-01-v1",
    "VXI-EXT-PROCUREMENT-VERCEL-SPEND-SCOPE-01-v1",
    "VXI-EXT-PROCUREMENT-SNOWFLAKE-MONITOR-SCOPE-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "BigQuery query cost controls",
    "source_url": "https://docs.cloud.google.com/bigquery/docs/best-practices-costs",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-BIGQUERY-MAX-BYTES-01-v1",
    "candidate_record_sha256": "70ea7e6a07f45fc1c04059fecb057517e9bf419475a3794ad2115717ee6e207d",
    "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 on-demand queries, maximum bytes billed checks an estimate before execution and can reject a query above the limit. Clustered-table estimates can exceed the eventual billed amount. This query setting does not establish an account-wide budget or cover every storage and capacity charge.",
    "required_buyer_context": "BigQuery: Billing model, byte estimate, query settings and other cost categories; buyer configuration and operational evidence are required.",
    "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": "One query byte limit bounds the entire workflow or account bill.",
    "documented_statement": {
      "status": "documented",
      "statement": "For on-demand queries, maximum bytes billed checks an estimate before execution and can reject a query above the limit. Clustered-table estimates can exceed the eventual billed amount. This query setting does not establish an account-wide budget or cover every storage and capacity charge.",
      "source_ids": [
        "bigquery-cost"
      ]
    },
    "buyer_evidence_required": [
      "Billing model and per-query maximum-bytes setting.",
      "Estimated query bytes and rejection/acceptance evidence.",
      "Separate storage, capacity and multi-query workflow costs."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Keep account-wide cost claims separate from a single-query byte guard."
    },
    "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": "bigquery-cost",
        "url": "https://docs.cloud.google.com/bigquery/docs/best-practices-costs",
        "final_url": "https://docs.cloud.google.com/bigquery/docs/best-practices-costs",
        "title": "BigQuery query cost controls",
        "checked_on": "2026-10-16",
        "sha256": "06001fa2119a7d7da4ff29f66de7ce91efa4e2622b9a562b7f4b4b7d5d5a7282",
        "bytes": 410679
      }
    ],
    "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 the exact guard and remaining cost categories for an authorised query workflow.",
      "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": "Billing model, byte estimate, query settings and other cost categories"
    }
  },
  "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#bigquery-maximum-bytes-query-boundary",
  "machine_readable_record": "/varexis-index/records/bigquery-maximum-bytes-query-boundary.json"
}