I think a lot of platform engineering discourse still has a very annoying habit. We keep treating automation as if the main risk is not having enough of it. Not enough controllers. Not enough reconcilers. Not enough policy engines. Not enough workflows. Not enough AI copilots orchestrating the orchestrators. And sure, sometimes that is true. But once a system gets a bit serious, the failure mode changes. The problem is usually not that you lack automation. The problem is that you now have automation making decisions from a stale mental model of reality. That is why the Kubernetes v1.36 work on staleness mitigation and observability for controllers is more important than it sounds. It is not just a controller-author quality-of-life improvement. It is a small but very clear signal about the next platform pain point. My take is simple: controller staleness is the hidden tax of platform automation, and the more teams automate, the more expensive that tax gets.…