Autonym specification

v0.1 draft · Apache-2.0 · last changed 2026-09-18

Reading this document

Normative language follows RFC 2119: MUST, SHOULD and MAY carry their defined meanings. Levels are written L0 to L3. Machine values, keys, scopes and paths are set in monospace. Examples are informative unless stated otherwise.

• L0CategoriesCategories only, no values
• L1PreferencesPreferences and needs, no direct identifiers
• L2NamedFirst names and household relationships
• L3IdentifiedIdentifying details

Contents

1. 1Scope and terminology
2. 2Handles and discovery: the autonym: scheme and /.well-known/autonym
3. 3The record: entries, provenance, temporal attributes, conflict rules
4. 4Domains and vocabulary v1
5. 5Disclosure levels and the compiler
6. 6Authorisation: OAuth 2.1, grants, scopes, delegation, revocation
7. 7MCP surface
8. 8REST API
9. 9Errors
10. 10Purge instructions
11. 11Export, import and migration between hosts
12. 12Recipient registry (Phase 2, placeholder)
13. 13Emergency card (Phase 2, placeholder)
14. 14Connectors and the observed lane (Phase 2, placeholder)
15. 15Conformance profiles: Core, Write, Portable, Delegated
16. 16Change process

Standards this builds on

Autonym does not define its own cryptography, authorisation or vocabularies where mature ones exist. A level is a human-facing name for a set of selectively disclosed claims: the person and the recipient see levels, the cryptography sees claims.

How to cite

Autonym specification v0.1 draft. New Media Solutions Ltd, 2026. https://autonym.dev/spec