The Golden Record: One File Everyone Can Trust
why a central registry never lets ten different offices each hold their own version of the truth about the same citizen, and what a single, trusted, reconciled record actually is.
Part 1
Part 2
Every Local Office Keeps Its Own Ledger
why a city with a dozen unconnected branch offices ends up with a dozen slightly different versions of the same citizen, and how the same thing happens inside every growing company's systems.
Part 3
Is This the Same Citizen, Twice?
how a records clerk decides whether two ledger entries describe one person or two, and the basics of entity resolution and matching that make a golden record possible in the first place.
Part 4
Which Address Wins? The Survivorship Rule
once a registry clerk confirms two file cards describe the same citizen, she still has to decide which conflicting entry actually survives into the merged file — the discipline of survivorship rules.
Part 5
Exact Match vs. Educated Guess
the registry's two matching methods — checking a stamped file number that has to match exactly, and weighing a cluster of partial similarities that never will — and when a clerk should trust each one.
Part 6
The Family Tree in the Filing Cabinet
a registry doesn't just file citizens one by one — it tracks who's related to whom, which household they belong to, and which subsidiary office reports to which parent, and master data does the same.
Part 7
The Registry of People
the citizen registry — names, addresses, households, consent preferences — as the model for the most common starting domain in any MDM program: customer master data.
Part 8
The Registry of Things, Places, and Suppliers
beyond the citizen register, a registry also maintains the property ledger, the licensed-supplier list, and the gazetteer of official place names — the product, vendor, and location domains of MDM.
Part 9
The Master File and the Working Copy
the registry holds the legally binding master file, but a branch office is still allowed to keep its own working copy for day-to-day use — the distinction between a system of record and a system of reference.
Part 10
The Clerk's Desk: Stewardship and the Review Queue
not every filing decision at a registry gets made automatically — some land, deliberately, in a clerk's in-tray for human judgment, which is exactly what a data stewardship review queue is for.
Part 11
Notifying Every Branch Office of a Correction
when the registry corrects a citizen's file, the fix is worthless until every branch office relying on the old version actually hears about it — the discipline of propagating golden record updates downstream.
Part 12
Splitting Two Citizens Back Apart
sometimes the registry merges two files that turn out to be two different people after all, and undoing that merge safely — without losing anything either file legitimately owned — is its own discipline.
Part 13
A Registry With Ten Million Names
the reconciliation habits that work fine for a small-town registry break down completely at the scale of a nation's worth of citizen files, and master data matching faces the exact same wall.
Part 14
Teaching the Clerk to Recognize a Likely Match
a seasoned clerk develops an instinct for which file cards probably describe the same citizen, built from thousands of past cases — the same instinct AI-assisted entity matching learns from labeled data.
Part 15
An Assistant Who Drafts the Survivorship Rule
instead of a clerk starting from a blank page every time a new kind of conflict shows up, a registry assistant now drafts a proposed rule from precedent — AI-assisted survivorship rule suggestions.
Part 16
Grading the Registry's Own Paperwork
a well-run registry doesn't just trust its own files — it periodically grades them for completeness, consistency, and accuracy, and gives every file a score anyone can check before relying on it.
Part 17
Handing the AI a Record It Can Actually Trust
a policy analyst building a citywide forecast is only as good as the registry files feeding it — and the same is true, more urgently than ever, for AI and ML features built on master data.
Part 18
Updating the Record the Moment It Changes
some registry corrections can wait for the weekly ledger review, and some genuinely can't — the real tradeoff between real-time master data management and periodic batch reconciliation.
Part 19
When a Small Town Doesn't Need a Central Registry
a village where the one clerk already knows everyone by name doesn't need a national reconciliation bureau — and plenty of small, simple systems don't need full MDM either.
Part 20
One Registry, Every Office Relying On It
the certified copy and the branch offices, the clerk's careful judgment and the fast-lane exceptions, every article's lesson reassembled into one registry every office can actually trust.