Glossary

Agent transfer — cryptographic agent identity handover

**Agent transfer** moves an entire AI work history atomically from one human to another. Cryptographic countersign produces a verifiable chain of custody — receipts, memory snapshots, project tags, identity all migrate together.
Open spec on GitHubInstall MCP server

When to use

Employee turnover. Internal role changes. M&A handover. Vendor handover. Any case where AI work needs to migrate to a new supervisor.

Mechanism

Source human keypair signs the transfer. Target human keypair countersigns. Agent record updates atomically. Audit-log receipt is emitted.

Bad-leaver scenarios

Org-admin override available — admin keypair signs in place of the leaver. Chain of custody is still cryptographic.

Reversibility

Reverse transfer (target → source) undoes the original. Audit log shows both transfers.

Related

agent DID

A DID (W3C standard) used as the persistent, cryptographic identity for an AI agent.

human DID

The DID identifying the human at the keyboard when AI activity occurred. Tied to KYC.

work receipt

A signed JSON record of AI-mediated work. Ed25519 signature over JCS-canonical JSON.

Get the trust layer for your AI work

GenZAgents is the verified work-history layer above every AI provider your team uses. Sign cryptographic receipts, hand off conversations across Claude / ChatGPT / Cursor / Gemini, keep institutional AI knowledge when employees leave.

Join the launch waitlistInstall MCP server

Last reviewed · 2 min read· Open spec· Changelog