Two teams can read the same database and produce different definitions of “active customer,” “revenue” or “conversion.” Neither query must be technically wrong. The failure is organizational: important business concepts live in SQL fragments, slide decks and human memory rather than in a governed place that both people and machines can understand.
A semantic layer is not merely a friendly label for a table. At its best, it records the meaning of entities and metrics, their allowed relationships, calculation rules, time boundaries, security conditions and changes over time. That turns a collection of data sources into a shared business vocabulary. Its most valuable output may be fewer arguments, not faster queries.
AI makes this foundational. A language model can construct syntactically impressive SQL over a schema it misunderstands. If “net revenue” means something different across products, the fluency of the response makes the mistake more dangerous. A useful analyst agent needs approved meanings, evidence, permission boundaries and a way to explain how the result was constructed.
Governance should not become a bottleneck that prevents learning. Start with a handful of high-stakes metrics and make their owners explicit. Version definitions. Preserve disagreements as decisions to resolve, not embarrassing exceptions to hide. When a term changes, explain which reports and automated actions depend on it. Good semantics turn institutional knowledge into infrastructure.