Step one is identity.

By Bill Godwin, CEO, Associated ID. October 12, 2026

Associated ID is verification infrastructure for institutions. It is designed to let the institutions that already know a person, or the person or company behind an AI agent, confirm who they are, content-blind, with no central identity database. The institution decides what that confirmation is worth. This piece is about where that sits in the list below.

On October 10, 2026, Satya Nadella posted a short argument about how enterprises should handle powerful AI models. His thesis line: "we need to separate the supply of intelligence from the authority over it."

His prescription is not new, and he says so. It is, he says, the playbook every large organization already runs for powerful actors inside its walls. In his words: "The good news is we have learned a lot about how to handle powerful actors inside the enterprise. This isn't new! We've established best practices and refined them over decades (establish identity, limit privileges, log activity, create containment boundaries, etc.)"

Four items, in his order: establish identity, limit privileges, log activity, create containment boundaries.

I want to talk about the first item, establish identity, because the other three depend on it.

Why Identity Comes First:

You cannot limit the privileges of an agent you cannot name. You cannot log the activity of an agent you cannot attribute. You cannot draw a containment boundary around something you cannot identify. Every control on that list assumes you already know who you are controlling. For people, that assumption is so old we forget it is there. For AI agents, it is the open question.

An agent is software. It can be copied, renamed and redeployed in an afternoon. Its model can change under it. If identity means the model, the identity changes every release. If identity means the name on a card the agent publishes about itself, then identity is whatever the agent says it is. Neither of those is something you can limit, log or contain.

An Agent's Identity Is Who Answers For It:

Here is the plain version: an agent's identity is the person or company that answers for it. Somebody deployed it. Somebody pays for it. Somebody is accountable when it acts. We call that person or company the sponsor. Establish the sponsor, and the agent has an identity that privileges, logs and boundaries can attach to.

So the question for step one, establishing identity, is not "what is this agent?" It is "who answers for this agent, and how do I know that is true?"

Where The Answer Comes From:

For people, the answer has always come from the people and institutions who already know them. At Associated ID we put it as three questions: "Who are you, how can I trust you, and who already trusts you?" The third question, who already trusts you, is what sets Associated ID apart, and it is the one that matters for agents. We have always established trust through references, and the strongest references are the institutions that already know someone: their bank, their employer, their healthcare provider. Associated ID makes the customer's own institutions the references. The answer travels; the data never does. It stays inside the institution that owns it, protected exactly as it has always been, while Associated ID carries only sealed, encrypted confirmations it cannot read, exposing not a single relationship.

But an AI Agent? An agent has no bank, no employer, and no references. However, the person or company behind it does. Their bank already knows them. Their employer already knows them. Those institutions can confirm who is behind the agent the same way they confirm a person: by confirming that the person or company behind the agent is someone they already know and have a relationship with.

This is what Associated ID is designed for. An AI agent's sponsor is confirmed through signed attestations from institutions that already know the sponsor. Associated ID is designed to carry that confirmation, content-blind, without reading it. The confirmation travels; the data never does. The confirmation of a sponsor's identity and delegation rests on the sponsor's institutional signature, not on the agent's own model or self-report. Each significant agent action carries a sponsor co-signature, and that co-signature, not the agent's own self-report, is the basis of the agent's authority and its identity.

Mr. Nadella also wrote this: "It's why the controls that govern what a model can access and what actions it can take must sit outside the model." Identity confirmation belongs outside the model too. Associated ID's own path runs on cryptographic signatures, with no model deciding trust. Any model use sits at the edges, in device liveness, institutions' own KYC, or sponsor/institution anomaly detection, never inside Associated ID's path. He closed with the principle that "Validation must be independent of the intelligence being validated." A signature from an institution that knows the sponsor is exactly that kind of independence.

What We Claim Nothing About:

Mr. Nadella's list has four items. Establish identity: who answers for the agent? Limit privileges: decide what the agent may do. Log activity: keep a record of what it did. Create containment boundaries: be able to stop it. Associated ID exists for the first. Deciding what an agent may do, recording what it did, and stopping it when needed are the institution's controls, and they stay with the institution. Associated ID carries the confirmation of who answers for the agent; it never decides or enforces an agent's business authority. What the agent may do stays your call. It is verification infrastructure, not a data broker, not a transaction rail, not a scoring engine.

The work is patent-pending. Associated ID is designed for human and agent identity, and on Mr. Nadella's list our claim is one item: Establish Identity, step one.

If You Are Working On This:

If you run an institution that will be letting agents act on behalf of your customers, or your own staff, and you want to talk through how the institutions that already know your customers can confirm identity for the people and agents you deal with, request a conversation at associatedid.com.