title: Tempest AT Protocol PDS Specification Index updated: 2026-06-03 #

Tempest is a Phoenix application that will become a self-hostable AT Protocol Personal Data Server.

Near-term focus: Target Profile - Solo Login + Archive. Hosted-provider scale can come later.

Subsystem specifications live in this directory.

Reading Order #

0. Target Profile - Solo Login + Archive
1. Architecture
2. XRPC HTTP Surface
3. SQLite Storage
4. Accounts and Auth
5. Identity and Handles
6. Repository Core
7. Record APIs
8. Lexicon Schema Loading and Generation
9. Blobs
10. Sync and Firehose
11. Security, OAuth, and Delegated Access
12. Migration and Account Lifecycle
13. Admin Operations
14. Deployment and Observability
15. Interop and Integration Testing
16. PDS Compatibility Against Reference Surface
17. Public Stats Dashboard
18. Documentation Viewer
19. Account Management Control Panel
20. Password Resets and Resend Email Delivery
21. Admin XRPC Methods

Source Baseline #

Research was checked on 2026-05-07 against:

• AT Protocol Repository spec: https://atproto.com/specs/repository
• AT Protocol Sync spec: https://atproto.com/specs/sync
• AT Protocol XRPC spec: https://atproto.com/specs/xrpc
• AT Protocol Account spec: https://atproto.com/specs/account
• AT Protocol DID spec: https://atproto.com/specs/did
• AT Protocol Handle spec: https://atproto.com/specs/handle
• AT Protocol Blob spec: https://atproto.com/specs/blob
• Blob lifecycle guide: https://atproto.com/guides/blob-lifecycle
• Official Bluesky PDS distribution: https://github.com/bluesky-social/pds
• AT Protocol Lexicons: https://github.com/bluesky-social/atproto/tree/main/lexicons
• AT Protocol OAuth spec: https://atproto.com/specs/oauth
• AT Protocol OAuth scopes guide: https://atproto.com/guides/scopes
• AT Protocol account migration guide: https://atproto.com/guides/account-migration
• Reference PDS implementation: https://github.com/bluesky-social/atproto/tree/main/packages/pds
• Cocoon PDS: https://github.com/haileyok/cocoon

Documentation Rules #

• Prefer plain technical prose.
• Keep protocol facts separate from project choices.
• Every subsystem spec must include HTTP verification.
• Every completed subsystem must have integration tests before it is considered done.
• Smoke tests must be Hurl files under test/smoke/*.hurl and must run with hurl --test.
• Use Req for outbound HTTP in application code.
• Run mix precommit before marking implementation work complete.