{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-14T01:25:58.088Z",
  "record_id": "VXI-EXT-PROCUREMENT-SNOWFLAKE-QUERY-HISTORY-01-v1",
  "record_kind": "external_reference",
  "title": "Snowflake query history: Delay, coverage and transfer status",
  "system": "Snowflake query history",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an empty Snowflake query-history result prove no query ran?",
  "near_questions": [
    "Does empty query history prove no activity occurred?",
    "How can history latency affect an audit question?",
    "Are short hybrid-table queries always recorded individually?",
    "Does PUT success in history prove upload completion?",
    "Does GET success in history prove download completion?",
    "Which Snowflake history view did the reviewer use?",
    "How do history time windows differ between views?",
    "What evidence supports the actual transfer outcome?",
    "What should procurement ask about query-history completeness?",
    "Can an agent confuse permission to proceed with completion?",
    "Can I save the reviewed activity-history boundary?",
    "When should workload changes trigger another history review?"
  ],
  "supported_claims": [
    {
      "claim": "No. Account Usage query history can be delayed, and some short hybrid-table queries are represented elsewhere. The documentation also says a successful PUT or GET history status indicates authorisation to proceed, not completed file transfer. Review the view, workload and outcome evidence separately.",
      "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": "No. Account Usage query history can be delayed, and some short hybrid-table queries are represented elsewhere. The documentation also says a successful PUT or GET history status indicates authorisation to proceed, not completed file transfer. Review the view, workload and outcome evidence separately.",
  "related_record_ids": [
    "VXI-EXT-PROCUREMENT-PINECONE-TENANT-ROUTING-01-v1",
    "VXI-EXT-PROCUREMENT-POSTGRES-RLS-PRIVILEGES-01-v1",
    "VXI-EXT-PROCUREMENT-MONGODB-RESUME-01-v1",
    "VXI-EXT-PROCUREMENT-DATABRICKS-CONNECTION-GRANTS-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Snowflake query history retention, latency and exclusions",
    "source_url": "https://docs.snowflake.com/en/sql-reference/account-usage/query_history",
    "checked_on": "2026-10-14",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SNOWFLAKE-QUERY-HISTORY-01-v1",
    "candidate_record_sha256": "5b5ed58c9e6b5acedd0ab6d7d7d9f727578457d9087bae809a0f6c7a894098c5",
    "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": "No. Account Usage query history can be delayed, and some short hybrid-table queries are represented elsewhere. The documentation also says a successful PUT or GET history status indicates authorisation to proceed, not completed file transfer. Review the view, workload and outcome evidence separately.",
    "required_buyer_context": "History view, time window, workload/table type and operation being verified.",
    "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-14",
    "claim_to_check": "Query history is immediate and sufficient proof of every completed operation.",
    "documented_statement": {
      "status": "documented",
      "statement": "No. Account Usage query history can be delayed, and some short hybrid-table queries are represented elsewhere. The documentation also says a successful PUT or GET history status indicates authorisation to proceed, not completed file transfer. Review the view, workload and outcome evidence separately.",
      "source_ids": [
        "snowflake-history"
      ]
    },
    "buyer_evidence_required": [
      "Chosen view, time range and visibility after documented delay",
      "Workload coverage and any aggregate history needed",
      "Independent outcome evidence for file transfer or other claimed effects"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not infer inactivity or completed transfer from a single history result."
    },
    "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": "snowflake-history",
        "url": "https://docs.snowflake.com/en/sql-reference/account-usage/query_history",
        "final_url": "https://docs.snowflake.com/en/sql-reference/account-usage/query_history",
        "title": "Snowflake query history retention, latency and exclusions",
        "checked_on": "2026-10-14",
        "sha256": "a16bb76b8596773436805571077286a82a4f6b4a511400fac56c950bdd4f2091",
        "bytes": 267815
      }
    ],
    "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 activity-evidence limitations used in a data-platform review.",
      "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": "Recheck history coverage, workload types and status definitions."
    }
  },
  "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#snowflake-query-history-coverage-evidence",
  "machine_readable_record": "/varexis-index/records/snowflake-query-history-coverage-evidence.json"
}