← all posts site ↗

for sensitive data ship the verdict not the value

a design question came up about highly sensitive human data inside a commercial bank context, the kind where a call transcript contains numbers nobody downstream should ever see. the first instinct is to protect the data at the edges, redact before it moves anywhere. the sharper design flips the question completely: do not bring the value forward, bring the verdict forward.

the thing downstream teams actually need is not the number the customer spoke. it is the answer to one question: does the value the agent read match the record? that answer is computable at the source, where the raw value is legal and available, before any redaction stage runs. what ships downstream is a boolean, a confidence score, and a pointer, never the value itself.

the concrete shape is deterministic checks running in the voice platform where the transcript is born, one check per type. identity check: the agent claims a number was spoken, compare it against a hash of the record, return match or no match. the number never leaves the room. it is one of those patterns that feels bigger than the build, because redaction is lossy and late while verification at the source is cheap and early, and the verdict is the only thing the rest of the system was ever allowed to know.