A storage platform can enforce any retention clock you hand it. What it can’t do is know which clock a record is on, and the only moment that answer can enter the system is the write. So the real policy decision is a schema token: required, or defaulted?
An internal platform has no price, so it can’t rank the work fairly and it can’t refuse anything cleanly. Every ’no’ turns political, and the roadmap ends up set by whoever escalates best.
A public API can force you off an old version by making the endpoint go dark on a date. An internal platform has the same compatibility burden and no way to ever pull that lever, so nothing it ships ever gets retired.
An internal platform’s adoption chart looks like a vote and isn’t one. When the teams on it had nowhere else to go, the number everyone reports up means almost nothing, and the most captive consumer of all is the app you built it for.
The moment you harvest a platform out of an app, the app stops being something you can change quietly. That standing cost lands hardest on the team that built it, and most extraction plans never budget for it.
I argued the way to find a platform’s real boundary was to watch the second team that wanted in. The catch I keep running into: two consumers tell you what they have in common, and that’s not the same thing as what the platform is.
You built an app. It worked. Then a second team showed up and couldn’t use it without inheriting every opinion you baked in. Congratulations, there’s a platform hiding inside your application.