Drug-Safety Agent on Databricks · Architecture · X, Y and Z for Databricks
Databricks: what it gives, what is shared, what we write
Three questions for any part of the agent: does the platform already give it to us (X), is it shared across all our agents (Y), or must this agent write it (Z)? Reading across a row shows how little of a real agent is new.
| Concern | X · Databricks out of the box | Y · shared horizontal assets | Z · this agent implements |
|---|---|---|---|
| The model | Foundation Model APIs host open models behind one URL. | A model port in the shared library; the model is a setting. | Which model, the standing instruction, the output shape. |
| Tools | Unity Catalog functions: named, permissioned, audited SQL functions. | Tool contracts (name, schema, read or write) in the library. | The three tools: counts, statistics, label check. |
| Data | Delta tables, a volume for raw files, Unity Catalog permissions and lineage. | Nothing: data is each agent's. | Ingest from openFDA; tables pair_counts, labels, event_synonyms. |
| The loop and limits | Nothing equivalent for a plain loop. | The loop, step and cost budgets, result size cap. | The numbers: 6 steps, 5 cents, 1,500 tokens, 8,000 characters. |
| Rules | None (AI Gateway can filter, but needs a custom endpoint the free plan refuses). | A policy layer and a router pattern. | The refusals and hand-off, written as rules. |
| Checks on the answer | None. | Contract and check hooks. | The output contract and the grounding check. |
| Approval | Nothing built in; Databricks Apps or a workflow could host a screen. | An approvals layer. | A local store and desk page. Not yet on Databricks. |
| Tracing | MLflow tracing. | A telemetry layer. | Not built. Wiring only. |
| Testing | Jobs for scheduled runs. | AgentTwin (a simulated world), the gates, the evaluation harness. | The world, ten scenarios, 128 tests. |
The lesson of the table. The platform supplies data, tools and models well, but it does not supply the loop, the rules or the checks. Those come from the shared library, and the thin third column is the part that is really about drug safety.
The same three-column view for Azure, AWS, Google Cloud and an open stack is on the site's architecture map.