Manish Karney

Field notes / 2019 · Family Link · Identity & dignity

We called it a supervised member. He called it his account.

The infrastructure needed one clean word for the relationship. The teen on the other end of that word already had a name, a history, and a sense of whose account it was.

Live question

When supervision is added to an account a person already owns, whose account is it now?

4 min read
IdentityDignityTrust

The clean move was to stop saying “child account.” For the under-13 world it had been a fixed account type, born supervised, only ever created through us. To support teens and accounts that already existed, we generalized it to a “supervised member”: any account in a family can carry a supervision edge that starts late, is time-bounded, and can be removed. That abstraction is the thing I am proudest of architecturally. It is also the thing I keep arguing with myself about.

Because the teen does not experience an edge in a graph. He experiences a Gmail account he has had since he was eleven, with his drafts and his photos and his login, and one day a banner appears telling him a parent now supervises it. We made an early, non-negotiable rule that we would never recreate or wipe an account to supervise it. Migrations operate on the data that is already there. I framed that as a reliability decision, no destructive migrations, but the truer reason is dignity. Wiping the account to re-mint it as a “managed” one would have said: the person we are protecting is a fresh object we get to define. He is not. He was here first.

We were not assigning an identity to him. We were attaching a relationship to an identity he already had, and the order of those two things is the whole ethics of it.

Then the harder question: how visible should the supervision be to him. We required a persistent indicator that the account is supervised and which parent is responsible. I believe in that, and I still flinch at it. A persistent label is honest, it refuses the silent-takeover that turns supervision into surveillance. But a label is also a status. A teen who hands his phone to a friend now wears it. We could have made it quieter and called that respect. We made it visible and called that consent. I am not certain those are different from where he stands, only that I would rather he be told something true and a little exposing than something comfortable and untrue.

What the abstraction bought us was real: one policy plane, no drifting “teen stack,” the same model serving a six-year-old and a sixteen-year-old. What it cost was a word. “Supervised member” is accurate and it is bloodless, and the people reading their own banner did not pick it. I kept pushing for the product surfaces to name the parent, name the controls, name the way out, so that the human specificity the data model flattened was put back at the layer where he actually reads. The abstraction is honest about the system. It is quiet about the person. The person is the one who has to live inside it.

The open question I never closed: an account is supposed to be the digital extension of a self. We added a second party to one without changing who it belongs to, and told ourselves that ownership and supervision are separable. Most of the time, with a parent acting in good faith, they are. I still do not know what we owe the teen for whom that is the day his account stopped feeling entirely like his.