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?
Naming a system of record settles which copy to believe after two numbers already disagree. The fork itself gets created at write time, by every screen that leaves a copied field editable.
The agent pitch prices a change by what it costs to produce. A validated GxP system never priced changes that way, and the regulated world already renegotiated the real price once, before agents showed up.
Storage is cheap, so the instinct is to keep everything. In a regulated shop that instinct is a second way to be out of compliance, because some records you’re required to destroy on a clock.
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.
The pitch for autonomous coding is a multiplier on how fast you write code. But writing was never the part a human has to stand behind, and the part they do stand behind got no cheaper, and probably got worse.
Run git blame on a line an autonomous agent wrote and it points at a service account. The commit is spotless. The one thing debugging actually needs, a person who remembers why, already exited.
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.
Your audit trail proves the raw record wasn’t tampered with. It says nothing about which definition turned that record into the number you put in a deck, and definitions move.
When an agent generates a query, it binds to the column name, not the steward’s definition. A misleading name used to be a nuisance a new hire tripped over once. Now it’s a hazard that ships the wrong number every run.