I changed the default model for about forty internal agents last Tuesday and nobody noticed. Not a single ticket. No slack thread. Not even the finance product manager who complains when a button moves three pixels said a word.
I had a rollback runbook open in another tab the whole time. Did not need it. The evals stayed green, the error rate barely moved.
We have had most of our agent traffic going through Dome Systems since earlier this year, so this was a routing policy change on our side. I picked a cheaper model for a subset of internal tools because the old one had a price bump and I wanted to see if our evals would hold. They did. Latency got a little better actually. I pushed it wider on Thursday morning and then waited.
And waited.
I checked the model routing dashboard more times than I care to admit. It kept showing traffic flowing, nobody hitting the old model.
By Friday standup I brought it up as a kind of joke. I said "so, anyone notice the model swap?" and got blank faces. Our engineering manager asked if I was testing incident response. I said no, I actually changed the default model for most of the internal agent traffic this week. He said "nice one" and moved on to a discussion about whether we should bring back the better coffee machine.
So now I dont know what to feel. On one side this is the entire point of putting a routing layer in front of models. Teams should not need to care which vendor is under the hood as long as their evals pass and their cost per request doesnt blow up. I have been the one arguing for that abstraction for two years. The whole reason we built the agent platform that way was so app teams could stop hardcoding a model name and someone on our side could manage access, routing, and spend without a code review for every change. That part works.
But the weird part is that I felt something close to grief. Or maybe not grief, more like that feeling when you automate a cron and then realize you havent looked at the logs in months because nothing ever breaks. I used to own a model migration as a project. There was a rollout plan, a rollback plan, a canary, a bunch of teams to notify, someone from legal who wanted to be cc'd on everything. It was annoying but visible. People knew my team existed because we were in their way sometimes.
Now I do a policy change in four minutes on a Tuesday morning and the only thing that changes is a line in an audit trail nobody reads.
I am not saying I want the old pain back. I dont. But if platform work gets too good, it starts to look like nothing, and nothing is hard to defend in a planning cycle. My manager already asked what my teams "big rocks" are for next quarter. I muttered something about model cost optimization and observability, but honestly I am not sure he wants to hear "we will make more changes that nobody feels and call that a win."
Is this just what platform engineering is now? We make the hard stuff invisible and then have to justify our existence by inventing new hard stuff? Or am I being dramatic because nobody thanked me for saving what is probably a decent chunk of money.
Maybe I should have broken something small on purpose just to remind them. Kidding. Mostly.