Passport
A Passport answers the first question every governed call asks: who is acting? It is a portable, cryptographic identity rooted in keys on the holder's device — for humans and for agents. HUMΛN does not hold a master switch over it, and it is not a row in someone's users table.
The model
| Field | What it is |
|---|---|
did |
Decentralized identifier — the stable name of the identity (did:human:…, did:agent:…, did:org:…) |
| Keys | Device-rooted keypairs for authentication and attestation; signing happens on-device rather than on a server holding your keys |
| Kind | individual, agent, or organization — agents are first-class identities, not API keys |
| Verification layer | Where the identity sits on the Validity Ladder (anonymous → device-verified → biometric → attested → unique) |
Two properties matter for everything built on top:
- Portability. A Passport is not scoped to one app or org. Capability evidence and delegation history travel with it.
- Progressive verification. Identities start anonymous and strengthen over time. Layers 0–1 (anonymous, device-verified) ship today; the upper layers of the Validity Ladder are roadmap and labeled that way.
Agents get Passports too
An agent under HUMΛN is not an anonymous process with a bearer token. It has its own Passport — its own DID, its own keys — so every action it takes is attributable to it, distinct from the human or org that authorized it. This is what makes delegation meaningful: authority flows between identities, and the Ledger records which one acted.
What builds on it
- The Capability Graph attaches evidence to a Passport: what this identity has demonstrably done.
- Delegations are grants between Passports: this identity may act for that one, within scope.
- HumanOS verifies the Passport on every call before anything else happens.
Work with Passports
- Patterns: Passport patterns — creation, verification, and key flows
- CLI:
human whoami,human login,human passport genesis— see the CLI reference - Product view: the Passport pillar covers ownership and the Validity Ladder in depth
Next in the ladder: Capability Graph →