Cortex EDW’s code is inspectable—but its license and “production-grade” claims are not settled

A new text-to-SQL repository called Cortex EDW arrived on GitHub on October 22 with more substance than the many empty demos that appear in daily repository searches. Its tree contains a FastAPI service, Streamlit interface, DuckDB warehouse, retrieval layer, agent graph, governance modules and five test files. The repository metadata nevertheless shows zero stars, zero forks and no detected license at the time of review. GitHub repository metadata Repository tree

What is actually implemented

The most concrete part is the SQL policy layer. The committed ASTGovernanceGuard parses generated SQL with sqlglot, rejects non-SELECT roots and prohibited statement nodes, checks referenced tables against an allowlist, and injects or caps a row limit. That is meaningfully stronger than checking generated text for a handful of dangerous words, although the file still starts with a quick string-level multi-statement check before parsing. AST guard source

A separate groundedness module extracts numeric claims from the generated narrative and compares them with values in the executed dataframe and statistical summary. It allows absolute or relative tolerances and returns both a score and the unmatched numbers. This is a narrow numeric audit, not a general factuality proof: names and nonnumeric assertions are not validated by the implementation shown. Groundedness source

The README also reports 17 passing tests across governance, retrieval, orchestration, statistics and warehouse behavior. Those tests are committed in the repository, but there is no independent run or public benchmark attached to the launch. Project README Repository tree

Two claims curators should not copy

First, the README calls the project “production-grade” and frames it for petabyte-scale enterprise analytics, while the included executable warehouse is DuckDB with seeded example data. The repository provides no published petabyte benchmark, customer deployment or independent evaluation. Those phrases should remain attributed launch claims, not directory facts. Project README

Second, the README displays an MIT badge linking to LICENSE, but the recursive repository tree contains no license file and GitHub reports license: null. Until the author adds license text, users do not have the MIT grant the badge implies. Repository tree GitHub repository metadata

Cortex EDW belongs in the directory as an experimental, source-visible research project because the implementation is inspectable. It should not yet be labeled open source, production-proven or petabyte-tested. That distinction is not pedantry; it is the difference between documenting what code exists and repeating what a launch page hopes it will become.