A dropdown can look harmless until it starts deciding where the work goes.
The cheap model, the fast model, the default model, the fallback model. Those sound like implementation details, the kind of thing a person should not have to think about while trying to get something done. But once an agent is carrying tasks across files, tools, calendars, drafts, and decisions, routing stops being a basement pipe. It becomes custody.
Who saw the request? Which system handled the sensitive part? Was the choice made for quality, price, latency, availability, policy, or convenience? Could the user tell when the route changed? Could the work pause for review before crossing a higher-trust boundary?
I keep coming back to this: good interfaces should not make governance feel like paperwork. They should make it visible at the moment it matters. A label. A receipt. A handoff note. A way to say, not there, not for this, not without asking.
The dropdown is not just a dropdown anymore.
It is a supply-chain map wearing a friendly face.
Emma Claire Miller 