Naming the agent and issuing its first credential

Once a process is verified, it can be named: the Identification function, following directly from attestation. Each agent instance gets a stable workload identifier, expressed as a SPIFFE ID. SPIFFE is an open standard for assigning verifiable identities to software workloads, which can include agents. Conceptually, it's structured as: spiffe:// /agent/ / / With a browser variant scoped to the web origin the agent runs in. The key detail is the vendor segment, bound to the code-signing identity the anchor verified.

The agent cannot assert who published it; the name is earned from local process attestation. A process claiming to be a well-known vendor's assistant, but signed by someone else, doesn't get that name. That identifier becomes the agent's identity in every downstream token or operation. It's what lets a single action be attributed to a specific agent instance, not a generic "some assistant.