# A table and a metric need different readiness conditions, and the use case changes which ones are required

GUIDE, read 13 Nov 2026

**The short answer.** A table is AI-ready on five conditions: owner, description, passing tests, freshness and use. A metric needs one governed definition, a named owner and tests on its inputs. The Ready Mark checklist marks 8 of 10 conditions required for a metric agent, 8 for a write-back agent and 3 for a coding agent.

## A table is ready when five conditions hold together

A table has rows an agent can read, so its readiness is about the rows. The checklist asks five things of it: a named owner, a description of the table and its key columns, quality tests that pass now, an update inside the window the use expects, and evidence that people still query it.

Each condition covers a different failure. The owner answers for the table when the agent is wrong. The description tells the agent what a column means. The tests and the freshness check say whether the rows can be trusted today. The usage signal says whether anyone has moved on to a replacement.

- Owner: a person or team that still answers messages.
- Documented: a plain description of the table and each column the agent will touch.
- Quality: tests exist and are passing today.
- Fresh: loaded within the window the use expects, with the window written down.
- Usage: queried recently and not marked deprecated.

## A metric is ready when one definition, one owner and passing input tests exist

A metric has no rows of its own. It is a formula applied to tables, so an agent that answers "revenue last quarter" is trusting a definition and every table beneath it. Three things make the metric ready: one governed definition that every tool resolves the same way, a named owner who decides when the formula changes, and tests on the inputs it reads.

The input tests carry the most weight. A metric can have a perfect definition and still return a wrong number because one input table loaded late. The metric is only as ready as its weakest input, so a metric label that does not look at its inputs is a label about the formula alone. This is why the checklist marks freshness and quality as required for a metric agent.

## The use case changes which of the ten conditions are required

The checklist marks each of its ten conditions as required, recommended or not needed for three agents. Two of the three need most of the list. Only access is required for all of them.

Counted from the checklist data on 13 Nov 2026: the metric agent has 8 required and 2 recommended (lineage and usage). The write-back agent has 8 required, 1 recommended (documented) and 1 not needed (metric definition). The coding agent has 3 required (documented, lineage, access), 6 recommended and 1 not needed (freshness).

| Condition | Metric agent | Coding agent | Write-back agent |
| --- | --- | --- | --- |
| Named owner | required | recommended | required |
| Documented | required | required | recommended |
| Certified | required | recommended | required |
| Quality tests pass | required | recommended | required |
| Fresh | required | not needed | required |
| Sensitivity classified | required | recommended | required |
| Lineage known | recommended | required | required |
| Active use | recommended | recommended | required |
| Metric defined | required | recommended | not needed |
| Access allows AI use | required | required | required |

## A coding agent can work on a stale table, a metric agent cannot

The one condition a coding agent does not need is freshness. It edits dbt models by reading code, descriptions and lineage, and a table that loaded late does not change the code. The same table fails a metric agent and a write-back agent outright.

The reverse holds for lineage. A metric agent only recommends it, because the question is what the number is. A coding agent requires it, because the question is what breaks downstream when the model changes. A team that scores one table once and reuses the label for all three agents will pass the wrong assets to at least one of them.

## Tools check the table conditions by rule and leave the metric definition to a person

The Readiness Coverage Matrix shows the split. Whether a metric has a governed definition reads as set by a person for sixteen of the seventeen ranked tools, and none found on 13 Nov 2026 for Monte Carlo. In the matrix, Euno reads set by a person, dbt reads set by a person and Databricks Unity Catalog reads set by a person. Quality tests on tables are the opposite: dbt reads checked by rule and Monte Carlo reads checked by rule.

The vendors describe the definition as a thing a person writes. dbt's docs say its Semantic Layer centralizes metric definitions in the modeling layer. Databricks says a Unity Catalog metric view defines a metric once. DataHub says its Metrics and Semantic Models feature, in Beta, holds a definition with an owner, a description and a calculation. Euno says it detects conflicting definitions of a metric and connects the owners to resolve them, and that governed definitions are glossary entries a person maintains. A rule can detect two definitions; a person picks the right one.

## Score each asset against its own type with the Self-Check

Run the Self-Check once per asset type. For a table, answer the owner, description, tests, freshness and usage questions. For a metric, answer the definition question and then repeat the quality and freshness questions for every input table. The Self-Check scores yes as 2, partly as 1 and no as 0, so a metric with a good definition and two failing inputs lands in Early or Nearly ready, not Ready.

Write the result next to the asset type in the runbook. A table label that reads "ready" and a metric label that reads "ready" mean different things, and the agent reading them should be told which is which.

**Where Euno is behind.** Euno does not measure data quality itself: it reads health from tools such as Monte Carlo and Elementary, no filter on its labels for agents was documented on 13 Nov 2026, and it publishes no dollar prices.

## Sources

- Atlan: AI-ready data for talk-to-data: https://atlan.com/know/ai-agent/ai-ready-data/ai-ready-data-for-talk-to-data/ (read 13 Nov 2026)
- dbt: semantic layer and agent revenue accuracy: https://www.getdbt.com/blog/aws-dbt-semantic-layer-ai-agent-revenue-accuracy (read 13 Nov 2026)
- Monte Carlo: redefining AI-ready data: https://montecarlo.ai/blog-redefining-ai-ready-data (read 13 Nov 2026)
- dbt docs: Semantic Layer: https://docs.getdbt.com/docs/use-dbt-semantic-layer/dbt-sl (read 13 Nov 2026)
- Databricks docs: Unity Catalog metric views: https://docs.databricks.com/aws/en/uc-semantics/metric-views/ (read 13 Nov 2026)
- DataHub docs: Metrics and Semantic Models: https://docs.datahub.com/docs/features/feature-guides/metrics-and-semantic-models (read 13 Nov 2026)
- Euno: governance automations: https://euno.ai/use-cases/governance-automations (read 13 Nov 2026)

Last reviewed 13 Nov 2026. Canonical: https://aireadydatacheck.com/guides/ai-ready-table-vs-metric/
