--- title: "Context Layer for dbt | Dawiso" description: "A context layer turns dbt metadata - models, tests, docs, lineage, the Semantic Layer - into governed business context AI can use. Learn how it works." url: "https://www.dawiso.com/glossary/context-layer-for-dbt" language: "en" --- June 10, 2026 context layer for dbtdbt metadatadbt semantic layerdbt lineageMCPAI contextsemantic layer # Context Layer for dbt A **context layer for dbt** turns the rich metadata that [dbt](https://www.dawiso.com/glossary/dbt-models) already produces - model definitions, tests, documentation, lineage, and Semantic Layer metrics - into governed business context that AI agents can use to understand and trust your data. dbt is where much of an organization's transformation logic and business meaning is actually encoded, which makes it one of the most valuable sources of context in the entire stack. A context layer harvests that context, governs it, connects it across platforms, and serves it to AI. It matters because dbt sits at the exact point where raw data becomes business-meaningful data. Every dbt model encodes a decision about what the data means; every test encodes an expectation of quality; the `ref()` graph encodes lineage; and descriptions encode documentation. That is a goldmine of context - but it lives inside the dbt project, expressed for engineers, and an AI agent cannot consume it directly. A context layer unlocks it: it reads dbt's metadata, joins it with business definitions and the rest of the estate, and exposes governed context to any AI through an open protocol. TL;DR A **context layer for dbt** harvests dbt's rich metadata - [models](https://www.dawiso.com/glossary/dbt-models), [tests](https://www.dawiso.com/glossary/dbt-tests), descriptions, the `ref()` [lineage](https://www.dawiso.com/glossary/dbt-lineage) graph, and **dbt Semantic Layer** metrics - and turns it into governed business context AI can use. dbt is where transformation logic and business meaning are encoded, so it is a prime context source; but that context is engineer-facing and project-bound. A context layer reads dbt's metadata (e.g. the manifest), joins it with a [business glossary](https://www.dawiso.com/glossary/business-glossary) and the rest of the estate, and serves governed context to any AI agent via the open [Model Context Protocol (MCP)](https://www.dawiso.com/glossary/model-context-protocol-mcp) - so dbt's hard-won meaning grounds AI instead of staying locked in the project. ## A Context Layer for dbt For dbt specifically, a context layer means capturing the meaning that dbt encodes and making it governed, connected, and AI-consumable. dbt projects are full of context - but it is expressed in YAML and SQL for a data engineering audience, scoped to the project, and surfaced (in dbt's own tooling) primarily for humans. A context layer reads that metadata, elevates it into governed business knowledge, links it to definitions and assets beyond dbt, and serves it where AI can use it. The opportunity is unusually high with dbt because so much business logic is deliberately written down there - unlike systems where meaning is implicit, dbt projects make transformation logic and expectations explicit. A context layer's job is to not let that explicit context stay trapped. ## dbt's Rich Metadata dbt generates several kinds of metadata that are directly valuable as AI context: - **Models.** Each [dbt model](https://www.dawiso.com/glossary/dbt-models) is a governed transformation - its SQL encodes exactly how a business concept is computed. - **Tests.** [dbt tests](https://www.dawiso.com/glossary/dbt-tests) assert expectations (uniqueness, not-null, accepted values, relationships) - operational metadata about whether data can be trusted. - **Descriptions & docs.** Model and column descriptions in YAML are documentation - business meaning written down at the point of transformation. - **Lineage.** The `ref()` and `source()` graph yields a precise [lineage](https://www.dawiso.com/glossary/dbt-lineage) DAG of how models depend on one another. - **The manifest.** dbt compiles all of this into artifacts (the `manifest.json` and catalog) - a complete, machine-readable description of the project that a context layer can ingest. Taken together, dbt's metadata is one of the cleanest, most structured context sources in the modern stack - precisely because dbt forces meaning to be written down. ## The dbt Semantic Layer The **dbt Semantic Layer** deserves special attention, because it is dbt's own answer to metric consistency: it lets teams define metrics once, centrally, so that "revenue" or "active customers" is computed the same way no matter which tool asks. This is a [semantic layer](https://www.dawiso.com/glossary/semantic-layer) in the classic sense, and it is exactly the kind of governed business definition a context layer wants to capture and expose to AI. But as the distinction between a [context layer and a semantic layer](https://www.dawiso.com/glossary/context-layer-vs-semantic-layer) makes clear, metric definitions are necessary but not sufficient for AI: an agent also needs lineage (where the metric's data came from), trust signals (did the tests pass), relationships, and policy. A context layer takes the dbt Semantic Layer's metrics as its meaning core and surrounds them with the rest of that context - turning consistent definitions into trustworthy, AI-ready context. ## The Gap a Context Layer Fills dbt produces excellent context, but on its own it leaves gaps for AI: - **It's engineer-facing and project-bound.** dbt's metadata is expressed for data engineers and scoped to the dbt project; business users and AI agents can't consume it directly, and meaning beyond dbt (in source systems or BI) isn't covered. - **It needs governance and business framing.** Model and column descriptions are a great start, but turning them into governed, owned, glossary-linked business definitions is a separate discipline. - **It needs open delivery to AI.** For an AI agent to use dbt's context, it must be exposed through an open standard - the [Model Context Protocol](https://www.dawiso.com/glossary/model-context-protocol-mcp) - not just rendered in dbt's docs UI. A context layer closes these gaps: it ingests dbt's metadata, governs and business-frames it, joins it with the rest of the estate, and serves it to AI. ## How Dawiso Fits Dawiso turns dbt's rich metadata into a governed, AI-ready context layer. It ingests dbt projects - models, tests, descriptions, and the `ref()` [lineage](https://www.dawiso.com/glossary/dbt-lineage) graph - and folds them into a unified [catalog](https://www.dawiso.com/glossary/data-catalog) alongside 40+ other platforms, so dbt's transformation logic becomes part of cross-platform [lineage](https://www.dawiso.com/product/interactive-data-lineage) that traces from source systems through dbt and into [Snowflake](https://www.dawiso.com/glossary/snowflake) or [Databricks](https://www.dawiso.com/glossary/what-is-databricks-complete-guide-for-2025) and out to BI. The [business glossary](https://www.dawiso.com/product/business-glossary) elevates dbt's model and column descriptions into governed, owned definitions, and AI-assisted enrichment fills the gaps. Then the [Context Layer](https://www.dawiso.com/context-layer) serves all of it - dbt's meaning included - to any AI agent through the open [MCP Server](https://www.dawiso.com/product/mcp). The hard-won context engineers write into dbt stops being trapped in the project and starts grounding your AI. ## Conclusion dbt is one of the richest sources of context in the modern data stack, because it forces meaning to be written down: every model, test, description, and `ref()` encodes how data is computed, whether it can be trusted, and how it flows. A context layer for dbt unlocks that goldmine - ingesting dbt's metadata and Semantic Layer metrics, governing and business-framing them, connecting them across the whole estate, and serving the result to any AI agent via open MCP. The context your engineers already encode in dbt is too valuable to leave inside the project; a context layer is how you turn it into trustworthy grounding for AI. [See it in action](https://www.dawiso.com/product/mcp) MCP (Model Context Protocol) Connect agents and LLMs directly to your enterprise data and business knowledge. ### Table of contents A Context Layer for dbtdbt's Rich MetadataThe dbt Semantic LayerThe Gap a Context Layer FillsHow Dawiso Fits ## Related Terms ### [Context Layer vs Semantic Layer](https://www.dawiso.com/glossary/context-layer-vs-semantic-layer) Context layer vs semantic layer - a semantic layer defines what data means; a context layer adds lineage, governance, and relationships so AI can use it. Learn the difference. Read more → ### [What Is the dbt Semantic Layer? MetricFlow Explained](https://www.dawiso.com/glossary/dbt-semantic-layer) The dbt Semantic Layer defines metrics once in YAML next to your dbt models, and MetricFlow turns them into SQL for BI tools, spreadsheets, and AI agents. Read more → ### [What Is a Context Graph?](https://www.dawiso.com/glossary/context-graph) A context graph connects business concepts, data, processes, and people into one relationship model that grounds AI reasoning. Learn how it differs from a knowledge graph. Read more → ### [What Is Databricks Genie Ontology?](https://www.dawiso.com/glossary/databricks-genie-ontology) Databricks Genie Ontology is a context layer that grounds Genie in business meaning. Learn how Unity Catalog feeds it and where a cross-platform layer reaches. Read more → ### [What Is a Context Store for AI?](https://www.dawiso.com/glossary/context-store-for-ai) A context store for AI holds the governed business context - definitions, relationships, lineage, and policy - that AI agents query to ground their answers. Learn how it works. Read more → ### [What Is a Metadata Layer for AI?](https://www.dawiso.com/glossary/metadata-layer-for-ai) A metadata layer for AI is the governed layer of business and technical metadata that AI systems consume to understand enterprise data. Learn what it holds and why AI needs it. Read more →