Ravi Rali Enterprise AI & Data

Perspectives

AI readiness depends on the data foundation

Around 15% of organizations report data foundations adequate for agentic AI. Metadata, lineage, quality, MDM, and semantics are the work that closes the gap.

Enterprise AI Architect · Enterprise Data Architect · Director, AI & Data Management Point of view

The requirement this answers

“Ensure enterprise data is AI-ready and fit for GenAI and agentic consumption”

Treat metadata, lineage, quality, MDM, and semantics as deliverables rather than prerequisites to defer.

The constraint is the context, not the model

Frontier models are widely available infrastructure. What is specific to your organization is whether you can tell an agent, in machine-readable form, what "active study", "customer", or "revenue" means, who may see which attribute, and how fresh the answer is.

An agent pointed at an undocumented physical schema does not fail visibly. It returns confident, well-formatted, incorrect answers, which is harder to detect than an error.

What AI readiness means in practice

Machine-consumable metadata that can be queried at execution time. Column-level lineage that runs end to end. Quality expectations learned from observed distributions rather than assumptions encoded years earlier. Mastered entities so the agent resolves to one customer. A semantic layer where each metric is defined once. And access control inherited from the source, so retrieval cannot surface what the user could not otherwise open.

Permission leakage through vector stores is the most common security gap I see in enterprise RAG. Documents get embedded and their access controls do not travel with them.

Sequencing

Build the trust plane before the agent plane. Organizations adopt AI-assisted authoring roughly three times faster than AI-assisted verification, which means defects arrive faster too. A roadmap that places the semantic layer in a later phase will need revisiting.

How I apply it

  • Treat the semantic layer and data contracts as first-phase deliverables
  • Govern vector indexes as data assets, with lineage, classification, retention, and access
  • Inherit retrieval permissions from source documents in every case
  • Instrument evals on every AI-executed pipeline step

What good looks like

  • Critical metrics are defined once and consumed by BI and agents from the same place
  • The catalog can be queried by a machine at execution time
  • Retrieval quality is measured and trended
  • The derivation of an AI answer can be shown to an auditor
Related: Data Engineering, Rebuilt by AI