Enterprise AI rarely fails loudly. More often it fails silently, returning answers that sound plausible but are simply wrong. The root cause is usually not the model itself but the gap in meaning: machine learning models have no built-in understanding of what your organisation means by “customer,” “revenue,” or “active account.” In this episode, we explore how to close that semantic gap before it undermines trust in your AI systems.

We walk through the layers of meaning organisations need to make explicit, from taxonomies to ontologies to semantic models, and why defining business concepts in a structured way is essential groundwork for any serious AI initiative. We then look at how a Data Vault architecture provides a trustworthy integration foundation, where conflicting definitions from different source systems can be reconciled long before they reach an end user or an AI agent.

From there, we discuss the role of a centralised semantic layer in making sure dashboards and AI agents pull the same governed metrics at query time, so everyone, human or machine, works from a single version of the truth. Finally, we explore how automated tools can speed up the work by proposing definitions and mappings, and why strict human oversight remains essential to keep those systems accurate and reliable at scale.

Resources mentioned in this episode:

• From Taxonomy to Trusted AI by Ignition, explaining the layers of meaning and how they map onto Data Vault
• Semantic Layer guide by Scalefree, showing how to deliver those definitions to every tool that needs them

Stay connected:

• Join the conversation in the Data Innovators Exchange community
• Subscribe to the DataPro newsletter for more insights on data and AI

• Join the Data Innovators Exchange for free at https://www.skool.com/data-management-innovators-4116/about
• Sign up for the free Data Pro Newsletter at https://www.datapro.news/subscribe

Who’s Judging the Judges? Why AI Evaluation Still Needs Humans

Evaluation-driven development promises a structured way to measure AI quality, but there’s a catch most teams overlook: the automated scorers at the heart of their pipelines are rarely checked against real human judgment. In this episode, we look at why reliable AI evaluation starts with people, not dashboards.

We discuss why teams should resist adopting rigid benchmarks upfront and instead begin with hands-on error analysis of real production data, the only reliable way to surface the failure modes that actually matter to users. We also look at LLM-as-a-judge systems: they scale well, but they come with built-in blind spots such as position bias, verbosity bias, and a tendency to favour their own outputs. Without careful human calibration, those biases quietly distort your quality signal.

We also cover why public leaderboards and generic metrics fall short, since they can be gamed and rarely reflect what your users need. And with the evaluation tooling market consolidating through major acquisitions, we explain why keeping your evaluation data portable and secure should be part of your strategy now.

The takeaway is simple: a trustworthy quality assurance pipeline depends on continuous human oversight, not blind faith in unverified automated scores.

Resources mentioned in this episode:

• Master the traceability and context AI requires: Read Ignition Data’s guide on Understanding the Semantic Foundations That Make AI Work.
• Safely embed models into your enterprise pipelines without falling into the "garbage in, garbage out" trap: Discover Scalefree's practical breakdown in Unlock the Intelligence Layer: LLMs in Data Warehousing

Stay connected:

• Join the conversation in the Data Innovators Exchange community
• Subscribe to the DataPro newsletter for more insights on data and AI

• Join the Data Innovators Exchange for free at https://www.skool.com/data-management-innovators-4116/about
• Sign up for the free Data Pro Newsletter at https://www.datapro.news/subscribe

The Open Data Contract Standard (ODCS) v3.1.0 has emerged as the industry's definitive format for defining data agreements after competing specifications were deprecated. Managed by the Bitol project under the Linux Foundation, this version introduces stricter validation, enhanced relationship mapping, and machine-actionable service-level agreements. While the standard reached Graduated status in 2026, the ecosystem faces complexity as enforcement tools like Soda and Great Expectations undergo significant licensing and ownership changes. Experts highlight that while ODCS provides a robust declarative framework, it remains a specification rather than an execution engine. Consequently, successful implementation requires pairing the standard with functional enforcement points, such as dbt or the Data Contract CLI, to ensure data quality is actually monitored. Without such active integration, these contracts risk becoming mere documentation rather than binding, executable guarantees.

• Join the Data Innovators Exchange for free at https://www.skool.com/data-management-innovators-4116/about
• Sign up for the free Data Pro Newsletter at https://www.datapro.news/subscribe