IDENTITY AS INFRASTRUCTURE
The Human Layer, Part II
A piece of work appears in a generative platform. It contains a recognizable performer. The voice is right, the face is right, and the way they move and pause and hold a line is unmistakable. The asset is good. It can be licensed, sold, distributed, plugged into a campaign. What the asset cannot do is answer one question with any confidence: who is in it.
The performer might be a verified, consenting subject. They might be a stylistic echo trained on someone whose name is in the model’s training set but whose name is nowhere in the platform’s output. The system has no resolvable answer because the system was not built to have one. The contract that covered the production sits in someone’s email. The likeness rights, if they exist, sit in a separate database belonging to a different entity. The performer’s identifier, assuming they have one, was not requested, was not stored, and would not have been resolvable from inside the workflow even if it had been.
Once agency is observable, the next question is whose agency. That was the bridge from the last piece. It is also the question most of the industry’s rights, contract, and credit frameworks quietly assume has already been answered. It hasn’t. There is no resolvable identity layer for the people inside generative media, in any form a workflow can query and trust. The asset has an identifier. The performer in the asset usually does not.
This gap does not exist because the industry hasn’t thought about it. It exists because the industry built identity infrastructure for assets fifteen years ago and never built the equivalent for people.
The industry has done this before, for assets
The Entertainment Identifier Registry has been operating since 2010. Over two million records. Founded by MovieLabs, CableLabs, Comcast, and TiVo. Widely adopted across major studios, streamers, and broadcasters, and used by PBS at the network level. It is built on the same Digital Object Identifier system that runs academic journals and scientific data, governed by the same DOI Foundation, resolvable through the same handle infrastructure originally designed by Bob Kahn.
What makes EIDR work is what it deliberately doesn’t do. The registry is intentionally thin. It holds the minimum metadata required to disambiguate one piece of content from another: title, language, release date, country, length, type. It does not hold ownership. It does not hold rights. It does not aggregate commercially valuable metadata about the asset. It is purely functional, and persistent enough to survive ownership changes. When an asset is sold, transferred, recombined, or re-edited, the identifier travels with it.
That design philosophy is the load-bearing point. EIDR works because it solved one problem cleanly and let the value layers sit on top. Disambiguation became an industry-wide service that nobody owns and everybody benefits from. The studios accepted, fifteen years ago, that some kinds of identity infrastructure cannot be a competitive advantage without breaking the system that produces the advantage. Make the registry neutral. Make it persistent. Make it governed by a body whose only job is to run the registry. Build the commercial systems on top.
That principle, accepted for assets, has not been accepted for people. The asset has had a resolvable identifier for fifteen years. The performer in the asset has not. The voice in the dub, the writer of the script, the director of the cut, the choreographer of the movement, the musician on the underscore: none of them have. Their identity has lived in contracts, payroll systems, IMDb pages, agent databases, union rolls, and credit slates. None of those are resolvable. None of those persist through ownership changes. None of those federate.
