Coverage

Which warehouses, which agents, and how validated each one is

The evaluation engine is built on SQLGlot abstract syntax trees and relational invariant semantics, so it parses most dialects. Parsing is not validation. This page says, per warehouse and per agent, what we have actually validated against the benchmark and what is still a plan.

Last updated 13 September 2026 · Protocol v9.3

Warehouses

WarehouseStatusExecution modalityWhat is specific to it
SnowflakeValidatedNative stored procedure EVALQA_RUN; evalqa CLIMicro-partition pruning, clustering keys, remote spilling, row access policies, dynamic data masking, Cortex AI functions, Cortex Agents tool calls. Snowflake page →
Databricks (Unity Catalog, Genie)Pilotevalqa CLI against SQL warehouses; notebook runnerUnity Catalog row filters and column masks, Delta time travel for counterfactual probes, Genie space instructions as the semantic layer. Phase 2 extension per operating-plan risk RSK-05.
Google BigQueryRoadmapevalqa CLIPartition and cluster pruning, row-level security policies, authorised views. Dialect parses; no benchmark partition yet.
AWS RedshiftRoadmapevalqa CLISort and distribution keys, RLS policies, dynamic data masking. Dialect parses; no benchmark partition yet.

Agents

AgentStatusHow we observe itNotes
Snowflake Cortex Agents / Cortex AnalystValidatedGenerated SQL and tool-call traces via the agent API; runtime spans via qabitSemantic model YAML treated as the definition source; tool parameter abuse family validated.
Databricks GeniePilotGenerated SQL via the conversation APISpace instructions and trusted assets treated as the semantic layer.
Custom LangChain / LlamaIndex Text-to-SQLValidatedqabit OpenTelemetry adapter; or SQL log ingestionAny agent whose generated SQL and tool calls we can capture. Framework-agnostic by design.
BI-native NL assistants (Looker, Tableau, Power BI)RoadmapSQL log ingestion onlyVerifiable where the generated SQL is observable; not where it is opaque.

Failure families by dialect

Validation status is per family and per dialect. A family validated on Snowflake is not thereby validated on Databricks; the benchmark partitions are separate.

Failure familySnowflakeDatabricksBigQueryRedshift
Join fan-outs (1:N)VALIDATEDPILOTUNVALIDATEDUNVALIDATED
SCD-2 temporal logicVALIDATEDPILOTUNVALIDATEDUNVALIDATED
Fiscal calendar shiftVALIDATEDPILOTUNVALIDATEDUNVALIDATED
Null predicate trapsVALIDATEDPILOTUNVALIDATEDUNVALIDATED
Micro-partition / pruning scansVALIDATEDn/a — different mechanicsUNVALIDATEDUNVALIDATED
Multi-tenant row leakVALIDATEDPILOTUNVALIDATEDUNVALIDATED
Tool parameter abuseVALIDATEDPILOTUNVALIDATEDUNVALIDATED
Prompt injection leakVALIDATEDPILOTUNVALIDATEDUNVALIDATED

VALIDATED = family has a partition in the 500-item Ground-Truth Calibration Benchmark for that dialect and has passed the Sev-1 gate. PILOT = invariants defined and running in sprints; corpus expanding. UNVALIDATED = defined in the taxonomy only. The remaining ten of the 18 domains are PILOT or UNVALIDATED on every dialect.

Contractual consequence

Queries in a dialect or family we have not validated are recorded as EXCLUDED_UNSUPPORTED, counted against coverage, and shown on the scorecard. They are never quietly passed. See scope & exclusions.

Snowflake Cortex assurance → Ask about Databricks pilot