The End of the Dashboard Queue
The "Modern Data Stack" was a massive step forward for the technology industry. It centralized information and made databases incredibly fast. But it had one fatal flaw. It only made data accessible to data analysts.
If someone in marketing or sales needed an answer, they still had to write a ticket. They had to wait for a human to translate their business question into a SQL query, build a dashboard, and explain the results. The human translation layer was a permanent bottleneck.
The AI Data Stack removes this bottleneck. It replaces the human translator with autonomous agents. But to make these agents reliable, we have to abandon one of the most painful practices in data engineering: the semantic layer.
Killing the Semantic Layer
For years, the gold standard for data automation was building a semantic layer. This is a massive, hand-written dictionary. It maps abstract business concepts directly to specific database columns.
Semantic layers are a nightmare to maintain. They are brittle. They require constant human updates. They create a new bottleneck because the data team has to anticipate every possible question a user might ask and pre-define the logic for it.
We can now replace this static dictionary with Context Management.
Instead of pre-defining everything, you give an AI agent direct access to your raw source of truth. You connect it to your data transformation code and your application logic. When a user asks a question, the agent investigates the code on demand to figure out how the data fits together.
The Scout and the Builder
If you ask an AI to write a SQL query immediately, it will fail. It will guess the table structures and invent columns that do not exist.
To fix this, you must split the work. Before writing any code, you dispatch a cheap, specialized sub-agent. Think of it as a scout.
The scout's only job is to investigate the landscape. It reads the raw code files, traces how data flows from one table to another, and checks for specific business rules. It then returns a structured brief containing the exact tables, column definitions, and filter rules needed for the job.
This brief is handed to the main agent. Because the main agent now has a perfect, verified map of the data, it can write flawless SQL without hallucinating.
Capturing Tribal Knowledge
Every company has hidden rules about its data. An analyst might know that the "orders" table duplicates rows when an item ships twice, so you always have to filter by a specific ID. Historically, this "tribal knowledge" lived exclusively in the heads of a few senior employees.