The Medallion Architecture Under Agents, Gold for Machines
Pull-quote: “Bronze, silver, gold assumed a person at the end of the pipeline who would notice when something looked off. An agent does not notice. The architecture has to.”
Why this matters
The medallion architecture was designed with a person at the end of the pipeline: an analyst who squints at a number that looks off, a BI developer who notices the join doubled the revenue. Agents are now first-class consumers of the same layers, tool-calling agents querying tables, retrieval pipelines feeding models, natural-language interfaces answering the business directly, and an agent does not squint. It consumes whatever the layer serves and passes the result along with fluent confidence. Bronze, silver, and gold survive the shift. What each layer must guarantee does not.
The same layers, harder promises
| Layer | With human consumers | With agent consumers |
|---|---|---|
| Bronze | Landing zone; engineers explore with judgment | A no-agent zone: unvalidated, PII un-scrubbed, and for text, an injection surface |
| Silver | Conformed; analysts sometimes query ad hoc | Pipeline territory; agents that read silver bind themselves to internals that change without notice |
| Gold | Curated marts; semantics often live in the BI tool | The product interface: semantics, documentation, and governance must live in the platform itself |
Bronze deserves the strongest statement. Raw text from the outside world is untrusted content, and an agent that retrieves it raw is an agent taking instructions from strangers. Sanitization and validation are what promotion out of bronze means, and the promotion gate is where the layer earns its name.
What agent-ready gold requires
Four properties separate a gold table an agent can safely consume from one that merely exists. First, typed and documented: table and column comments stop being documentation and become context; the agent reads them, so write them like prompt material, units, grain, join keys, caveats. Second, consistent semantics: metric views define “on-time” or “margin” once, so every consumer, human or machine, computes the same number. Ambiguity a human resolves by asking a colleague, an agent resolves by guessing. Third, governed access on behalf of the caller: the agent inherits the requesting user’s Unity Catalog permissions, row and column security included, rather than running as a superuser service account that sees everything and leaks by summarizing. Fourth, visible freshness and provenance: last-updated timestamps and lineage the agent can cite, because an answer that states the age of its data is an answer a human can calibrate trust against.
agents · NL interfaces · MCP tools
│ typed, scoped, on-behalf-of
▼
GOLD metric views · curated marts ·
comments written as context
▲ contract-gated promotion
SILVER conformed, validated ── pipelines only
▲
BRONZE raw, untrusted ── no agent reads, ever
─────────────────────────────────────────────
Unity Catalog: identity · lineage · row/column securityScope is still the discipline
Pointing an agent at a thousand-table catalog produces plausible SQL over the wrong tables; the model is rarely the weak point, the scope is. Give each agent a curated set of gold interfaces per domain, the same way you would scope any API client, and version that scope, because an agent whose data surface changes silently is an agent whose behavior changes silently. The end state is worth naming: an agent that reaches data exclusively through a small set of typed, schema-validated tools over curated marts has a data surface that is enumerable, testable, and governed rather than discovered at query time.
Closing
Keep the medallion; upgrade its promises. Bronze becomes a hard boundary no agent crosses, silver stays pipeline territory, and gold graduates into a machine-consumable product: typed, documented in prose the model will actually read, semantically consistent through metric views, governed per caller, and honest about its own freshness. Agents did not break the architecture. They removed the human safety net that was quietly holding it together, and the layers now have to hold on their own. The teams that treat gold as a product interface, with the same care an API gets, are the ones whose agents stay right when the schema underneath them moves.