GigaOm recently classified it as a mature market, and tools like AtScale, dbt, and LookML have made semantic modeling a default component of the modern data stack.. A context layer consumes semantic definitions from dbt MetricFlow, Cube, AtScale, or platform-native semantic models and adds governance, lineage, and policy on top. It reads semantic definitions where they already live, from dbt semantic models to platform-native ones such as Databricks metric views and Power BI semantic models.
The two layers share surface-level similarities that fuel the “isn’t this just the same thing? It’s a pattern that requires multiple capabilities Limitations of Semantic Layers for Enterprise AI Context working together. It provides AI systems and human users not just what data means, but when, how, and under what rules that meaning applies.
When a dashboard asks for “active customers in Q3,” the semantic layer translates that into the exact SQL, against the exact tables, with the exact filters everyone agreed on. That gap is where the next round of AI incidents will come from, and it’s also what regulators are starting to ask about specifically. It lives in the heads of senior people, and an agent in production needs it encoded somewhere it can execute against. Gartner came closest at its Data and Analytics Summit in March 2026, separating a Context layer (ontology, schema, metrics, policy as code) from an Intelligence layer above it (reasoning, models, agentic workflow). DataHub’s State of Context Management 2026 found 88% of organizations claim their context is operational while 61% delay AI initiatives because it isn’t usable in practice.
Quick facts: semantic layer category map
- This architecture gives each agent a focused, semantically rich context — the revenue agent doesn’t have to reason about live customer health, and the customer agent doesn’t have to navigate the full semantic model.
- Other MCP clients (Claude Desktop, Cursor, custom frameworks) work if you configure authentication manually, but they’re not the officially supported path as of the writing of this article.
- Understanding the consumption model is essential for production deployment planning.
- It’s the foundation that lets an external agent understand what’s available in a Fabric workspace before deciding which more specific tool to invoke.
A context layer for AI agents is the architectural tier between enterprise data and AI agents that translates raw data into governed business meaning the agent can act on reliably. Two-thirds of August respondents said their organizations run, pilot or build one. Snowflake is approaching the same gap from the routing side. OpenAI’s Data agent, launched inside ChatGPT Work in September, connects directly to warehouses including Snowflake, Databricks and BigQuery and pulls context from Slack, BI dashboards and file storage in the same pass. Direct queries to live systems, where an agent runs SQL or calls an API or an MCP server and reads whatever comes back, were named by 21%, up from 11% in July, a change large enough to call. Pick one workflow that gets answered slowly today because the data spans two or three systems.
Pick Path B when you have API access and want Voicebox’s reasoning chain and provenance for no additional cost. Voicebox runs its own ontology-aware natural-language-to-SPARQL pipeline and returns the reasoning chain and provenance with each answer. The rules are defined once in the semantic model and evaluated over live data when the query runs. Stardog supports OWL reasoning and user-defined rules written in Stardog Rule Syntax (SRS) or SWRL.
The semantic layer turns lakehouses into AI decision backbones – SiliconANGLE
The semantic layer turns lakehouses into AI decision backbones.
Posted: Wed, 04 Nov 2026 08:00:00 GMT source
An event-driven architecture keeps context current as upstream systems change, so neither your semantic layer nor your context layer is reasoning from yesterday’s state. A context platform serves as the infrastructure that produces, governs, and delivers the context that semantic layers https://aicurated.com/ and context layers both depend on. Organizations have invested in abstraction layers while underinvesting in the metadata foundation those layers depend on. And despite 88% of organizations claiming to have fully operational context platforms, 61% frequently delay AI initiatives due to a lack of trusted data.
- An event-driven architecture keeps context current as upstream systems change, so neither your semantic layer nor your context layer is reasoning from yesterday’s state.
- A context platform serves as the infrastructure that produces, governs, and delivers the context that semantic layers and context layers both depend on.
- And despite 88% of organizations claiming to have fully operational context platforms, 61% frequently delay AI initiatives due to a lack of trusted data.
- The two layers share surface-level similarities that fuel the “isn’t this just the same thing?
- Context layers built on DataHub-managed metadata stay reliable because the operational signals, lineage, and policies they surface are unified and fresh.
- Organizations have invested in abstraction layers while underinvesting in the metadata foundation those layers depend on.
Translate Business Terms Into Accurate Data Queries
- It’s endemic in enterprise data environments because data is created by engineers optimizing for storage and query performance, while business questions are asked by humans operating in business language.
- It joins the usage logs to the account and product tables, picks its own trailing-twelve-month cutoff, and runs a COUNT(DISTINCT) across a year of usage.
- It provides the foundation both require to be trustworthy.
- Use the SKILL + semantic layer strategy, and you approach 100% accuracy, control costs, and scale AI intelligence across the organization.
- With proper prompt engineering, results approached 100%.
- See how teams at companies like Miro, Optum, and Block use DataHub to unify metadata, business knowledge, and documentation into a single governed source of truth that serves humans and AI agents from day one.
Enterprise data is scattered across systems that define the same things differently. The execution infrastructure is imperative — it actually runs queries. Understanding all five levels helps architects know what to build and evaluators know what to assess — and why semantic layers alone won’t deliver production-grade accuracy. Without AI agents this flexibility, organizations deploy multiple isolated agents that can’t share context, can’t access distributed data, and can’t meet users in their natural workflows. Understanding this “AI Disconnect” is essential for building semantic layers that actually solve production problems.
Level 3: Catalog & Business Definitions (Governance Layer)
The architectural property to understand is the IRI template. It computer vision research writes the queries, runs them across the company’s data, and replies with a short narrative answer plus the supporting numbers. The compute that hosts the agent, terminates inbound requests, manages tool credentials, and provides the operational surface for security and governance.
It provides AI ethics the foundation both require to be trustworthy. See how teams at companies like Miro, Optum, and Block use DataHub to unify metadata, business knowledge, and documentation into a single governed source of truth that serves humans and AI agents from day one. Context layers built on DataHub-managed metadata stay reliable because the operational signals, lineage, and policies they surface are unified and fresh.