The default Model Serving path would speed customer launches while route evidence remains incomplete.
The migration protects a consistent governed path, while a hold protects the customer from certifying traffic it cannot yet account for.
Who you’d be doing this for
“Compliance asked me where those requests went, and I had three different answers.”
Colette Henderson · ML Engineering Lead
Leads the customer team preparing its first regulated agent service for production.
What is at stake
Customer agent requests are appearing outside the evidence file needed for a regulated launch. You have to weigh a faster default migration against the risk of certifying routes nobody can fully explain.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- customer launch momentum vs. route accountability
- default consistency vs. reversible containment
- Beta trace coverage vs. compliance evidence
- security approval vs. migration precedent
Why Databricks
Model Serving and Unity Catalog sit at the point where regulated agent customers need both deployment velocity and evidence of how requests were handled.
Written with these in mind
Not your kind of problem? 107 more at Databricks, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.