{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T13:45:35.999Z",
  "record_id": "VXI-EXT-PROCUREMENT-DATABRICKS-RESULT-COMPLETENESS-01-v1",
  "record_kind": "external_reference",
  "title": "Databricks SQL: Execution success does not establish full result retrieval",
  "system": "Databricks SQL Statement Execution API",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does Databricks SQL SUCCEEDED mean the agent retrieved the complete evidence result?",
  "near_questions": [
    "Has the agent fetched every Databricks result chunk?",
    "Can a successful SQL statement return truncated evidence?",
    "What does the Statement Execution truncated flag mean?",
    "Is the first Databricks response the entire query result?",
    "Which row and byte limits were applied to this SQL request?",
    "How do we reconcile chunk indexes with the result manifest?",
    "Does SUCCEEDED establish that all rows were downloaded?",
    "Which statement ID belongs to these retrieved chunks?",
    "What evidence is missing after a result-link retrieval failure?",
    "How should a buyer check completeness of a Databricks evidence query?",
    "Can the agent close a review before following next-chunk references?",
    "What separates SQL execution status from client retrieval coverage?"
  ],
  "supported_claims": [
    {
      "claim": "Databricks documents that SQL Statement Execution results can span multiple chunks. The response identifies subsequent chunks, and byte or row limits can set the truncated flag. Execution success therefore does not show that the client fetched every chunk or received an untrimmed result. Reconcile the manifest, limits and collected data for the same statement.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration, actual data erasure, effective access or completed business actions",
    "Legal advice, compliance determination, vendor certification or safety assurance",
    "Runtime enforcement, permission to act or expanded licensed-checker coverage"
  ],
  "public_summary": "Databricks documents that SQL Statement Execution results can span multiple chunks. The response identifies subsequent chunks, and byte or row limits can set the truncated flag. Execution success therefore does not show that the client fetched every chunk or received an untrimmed result. Reconcile the manifest, limits and collected data for the same statement.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Databricks: Statement Execution API",
    "source_url": "https://docs.databricks.com/aws/en/dev-tools/sql-execution-tutorial",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-DATABRICKS-RESULT-COMPLETENESS-01-v1",
    "candidate_record_sha256": "cafab5138780222cf9f03ce12404635c4759a466ef1b5c26324302d65f5b9298",
    "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 documents that SQL Statement Execution results can span multiple chunks. The response identifies subsequent chunks, and byte or row limits can set the truncated flag. Execution success therefore does not show that the client fetched every chunk or received an untrimmed result. Reconcile the manifest, limits and collected data for the same statement.",
    "required_buyer_context": "The statement ID, query scope, parameters and execution status. The manifest, truncation flag, applied limits and chunk references. The collected chunks, row coverage and unresolved retrieval failures. 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-18",
    "claim_to_check": "Does Databricks SQL SUCCEEDED mean the agent retrieved the complete evidence result?",
    "documented_statement": {
      "status": "documented",
      "statement": "Databricks documents that SQL Statement Execution results can span multiple chunks. The response identifies subsequent chunks, and byte or row limits can set the truncated flag. Execution success therefore does not show that the client fetched every chunk or received an untrimmed result. Reconcile the manifest, limits and collected data for the same statement.",
      "source_ids": [
        "databricks-results"
      ]
    },
    "buyer_evidence_required": [
      "The statement ID, query scope, parameters and execution status.",
      "The manifest, truncation flag, applied limits and chunk references.",
      "The collected chunks, row coverage and unresolved retrieval failures."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not claim a complete result from SUCCEEDED or the first chunk alone when manifest coverage and truncation have not been reconciled."
    },
    "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-results",
        "url": "https://docs.databricks.com/aws/en/dev-tools/sql-execution-tutorial",
        "final_url": "https://docs.databricks.com/aws/en/dev-tools/sql-execution-tutorial",
        "title": "Databricks: Statement Execution API",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T13:33:51.500Z",
        "version_context": "Rolling AWS deployment guide; SQL Statement Execution API 2.0",
        "sha256": "780c8b023621959fb0e9437cb9debbfdfd93b07805519233344bf9f28f4e890c",
        "bytes": 207658,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Does Databricks SQL SUCCEEDED mean the agent retrieved the complete evidence result?"
        ]
      }
    ],
    "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": "An analyst or audit buyer must distinguish successful query execution from complete retrieval of the evidence used for a decision.",
      "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": "The statement ID, query scope, parameters and execution status. The manifest, truncation flag, applied limits and chunk references. The collected chunks, row coverage and unresolved retrieval failures."
    },
    "buyer_relevance": "An analyst or audit buyer must distinguish successful query execution from complete retrieval of the evidence used for a decision.",
    "refusal_conditions": [
      "Do not claim a complete result from SUCCEEDED or the first chunk alone when manifest coverage and truncation have not been reconciled."
    ]
  },
  "niche": {
    "label": "Agent Authority & Action Evidence",
    "niche_id": "agent-authority-action-evidence",
    "topic_id": "action-evidence-reconciliation",
    "buyer_intent": "An analyst or audit buyer must distinguish successful query execution from complete retrieval of the evidence used for a decision."
  },
  "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-sql-result-chunks-truncation",
  "machine_readable_record": "/varexis-index/records/databricks-sql-result-chunks-truncation.json"
}
