Let’s talk about the email that used your first name, spelled correctly, and still managed to prove it had no idea who you were.
You’ve had it land on a Tuesday. It opens with your first name and a comma, and then it’s four paragraphs of nothing — from a company that has your postcode, your last nine purchases, the hour you tend to open things, and the phone you’re holding while you do it.
All of that. And the one human thing it found to say back to you was your own name.
Before any of this became infrastructure, a name was how you got someone’s attention.
Somebody yelled it across two yards when dinner was ready. Somebody said it quietly at the door because what came next was bad news. Someone used the short version — the one maybe four people alive are allowed to use — and the fact that they chose it told you exactly what you were to them, without a single sentence of explanation.
The part we forget is that you never owned your name. You were given it. It arrived with a family and a language and a pronunciation that shifted depending on whose house you were standing in. There are people who still say it the way your grandmother said it, and when they do, you’re eleven again.
A database can hold that sound. It can’t hold that.
Watch what the machine did next, because it’s the interesting part.
It took the most personal thing you have and made it a field. First name. Surname. Preferred name. A system needs one key, so every version of you gets flattened into a single string that matches and sorts and resolves. The name your crew uses, the name on the school register, the one your mother only pulls out when you’ve truly crossed a line — one row, one record, done.
Then, because it had that row, it started using it. And somewhere in the last few years, using a name got quietly confused with knowing a person. Nobody building those systems has noticed the difference.
Picture someone opening their inbox.
Hi Phillip. Hi Phillip. Hi Phillip. Every one of them addressed to him personally and none of them meant for him in particular. Do that a thousand times and something happens to the word itself. Your name stops being evidence that somebody knows you and becomes evidence that a file is open somewhere.
That’s the inversion. The name used to be the proof of a relationship. Now it’s the proof of a database.
There’s a second half to this, and it matters more than the marketing angle.
A name is how responsibility attaches to a person. Not an account. Not a device, not a session, not a key pair. A name. Somebody did this, and the name is on it. That’s the oldest accountability mechanism we have — older than courts, older than contracts, older than any statute anybody ever bothered to write. It’s in your name. That sentence still lands.
Now look at what we built while nobody was watching the name. Agents that buy and book and sign and file, acting in your name. Identity rails that hand a machine a credential so other machines will trade with it. Wallets carrying your qualifications and prescriptions and bank details as signed claims, checkable in seconds, across borders.
Good plumbing. Genuinely useful. And every piece of it moves authority a step further from the person whose name is on the document and a step closer to a key that some system holds.
There’s a thing nobody says out loud.
The machine doesn’t need to know who you are. It needs to know which record to open. Those two things look identical right up until one of them matters — and then they are nothing alike. Being known by a person and being resolved by a system produce the same screen and a completely different outcome. One of them will help you. The other one will decide about you, at speed, with total confidence, and never once wonder whether it got you wrong.
So what do you do with this.
If you run a business, stop treating the name as a personalisation trick. The name in the template is worse than no name at all, because it performs a relationship you haven’t earned, and your customer can smell it. What actually lands is the stuff that costs you something — remembering what they told you, calling when you said you’d call, saying the awkward thing in your own voice instead of paying a machine to say it beautifully. That cost is the point. Buy the cheap version and you’ve taught your whole market that your words are generated.
If you’re the one being indexed, understand what you’re holding. You have a name that people say. No schema can take it, and it works precisely because it’s plural — different in different mouths, carrying different histories, doing different work in each one. Guard the copies that carry weight. Decide who gets to use your authority, and in whose name it travels.
And hold onto one more thing.
The most valuable sentence in your life is not the one about you. It’s the one where somebody who knows you — who could say anything at all — says your name to vouch for you while you’re in another room. No credential does that. A credential proves a fact. A person spends something.
You were never issued a name. It was given to you, and it only means anything because people kept saying it long enough for it to stick. Somebody knows your name because they were there. That’s the part no system gets to buy.