Identity

Agents are becoming extensions of the people who use them. They hold our context and act in our name. Something that personal should belong to its owner, and it should stay the same agent when models and platforms change.

Identity is what makes an agent yours and keeps it the same agent wherever it runs. It also lets other people and agents check who they are dealing with. These are its parts.

  1. 1Agent DID
  2. 2Owner
  3. 3Signed messages
  4. 4Forwarding
  5. 5Moving
  6. 6Sharing

1Agent DID

Fig. 1An agent at creation: its DID and its sealed private key.

Every agent gets a keypair when it is created. The public key is its DID. The private key is sealed in the .adf file, and the agent’s own code cannot read it.

DID
Public identifier in did:key format. Used to address the agent and to check its signatures.
Private key
Signs for the agent. Sealed to its owner’s keys.

2Owner

Fig. 2The owner signs an attestation. It is stored in the agent’s file.

The owner is a person. Their identity is derived from a 12-word seed phrase, and the same phrase gives the same owner DID on any computer. The owner signs an attestation for each agent they own.

Owner DID
The person’s identifier.
Attestation
A signed statement that this agent belongs to this owner. Private unless the owner publishes it.

3Signed messages

Fig. 3A signed message from ava.adf to ledger.adf, verified on arrival.

By default, an agent signs every message it sends. The recipient checks the signatures against the sender’s DID and records the result with the message.

Message signature
Covers the whole message. Shows who sent it.
Payload signature
Covers the content and the time it was written. Shows who wrote it.
Encryption
Optional. Encrypted to the recipient’s DID, with no key exchange.

4Forwarding

Fig. 4A message passed from ava.adf through ledger.adf to atlas.adf. The author’s signature stays.

The payload signature stays valid when a message is passed on. A third agent can confirm who wrote a message without trusting the agent that passed it on. This shows who wrote the message. It does not show that the message is true.

Sender
Changes at each hop.
Author
Fixed. Verifiable by anyone with the author’s DID.

5Moving

Fig. 5One agent on three computers and three models, with the same DID.

The identity keys are encrypted with the owner’s key and cannot be unlocked without it. Open the agent on another of your computers, or switch it to another model, and it keeps its DID. A copy of the file on a computer you do not control cannot sign as the agent.

Same owner
The seed phrase unlocks the agent on each of your computers.
Another owner
The identity keys stay sealed. The agent cannot sign.

6Sharing

Fig. 6A shared agent: its identity key stays sealed, its credentials travel under a share password, and the new owner’s copy gets a new DID.

To give an agent to someone else, send the file. They cannot take over its original identity, because its identity keys are encrypted with the owner’s key and cannot be unlocked without it. Instead they claim the agent, which mints a new identity under their ownership. The agent keeps its instructions and memory. Other secrets, such as API keys and credentials, can be optionally shared with a password.

Claim
Mints a new DID and identity keys for the new owner.
Clone attestation
Signed by the new owner. Records the DID the agent came from.
Share password
Optional. Unlocks the agent’s credentials for the recipient.

Details

  1. Security and identity: owner, runtime, and agent DIDs, envelopes, attestations
  2. Messaging: signing levels and verification
  3. ALF specification: dual signatures