Data

A QC lab is robotic because the regulation makes the method get written and proven before anyone runs it. Data work never gets that boring, and only half of the reason is a good one.

GitHub’s agent adoption metrics undercounted for a stretch this year while the invoice stayed correct, and the difference between the two numbers is who would have noticed. An adoption chart with no such person on it isn’t a measurement yet.

The safe way to rename a column keeps the old name alive as an alias until the last consumer moves. For a reader that binds to names, the alias is a second column with the stale meaning, and the rename isn’t done until the step most shops never schedule.

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.