Paper GMP records don’t allow an empty box: you cross it out, write N/A, initial it, date it. The database that replaced the form has a type for the empty box, and it spells four different absences the same way. Every count you run picks one of the four for you.
A sample ID like SITE04-PRT19-2021-00381 is four definitions promoted into a key. The audit trail can correct any column in the record and can’t touch the key, and then the key gets printed on a tube that sits in a freezer for decades. No steward ever gets to retire that one.
Warehouse operations checks its records against the shelf on a rotating schedule and knows its match rate. A data stack checks records against records, so it can agree with itself completely and still be wrong about what’s in the freezer.
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.
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.
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.
Every governance program is built to add definitions and none of them can retire one. In a regulated shop that gets worse, because the instinct to keep every record gets misread as a ban on ever deprecating a definition. They’re different objects.
The whole agent-reliability project is trying to engineer the one thing a tool can’t have: accountability. Data governance already named this. The agent is a custodian, and we keep trying to promote it to owner.