email.atmos.mailbox

ALPHA. Private Comail mailbox space for the official AT Protocol Spaces alpha. Canonical message content is immutable; mailbox and folder state use create-only causal revisions with deterministic reduction. These collections are the least-privilege OAuth recommendation, not a protocol write allowlist; certified adapters must reject unexpected authority collections. Legacy fixed-rkey mutable snapshots are deliberately excluded.

Repository @comail.at did:plc:yu6rmwoemqfnmsdkljyvmuhg namespace authority
Details · space
Kindspace
Authorityatmos.email
Indexed

Space

space · key any

Shown at sign-in

name

string

Comail Mailbox

Collections

collections

array · nsid

The record collections clients of this space type use. A space: scope covers these unless it names its own.

Asking for it

OAuth scope

A client asks for access to spaces of this type with this scope. On its own it covers your own spaces, with any key, and reading, creating, updating and deleting records in the collections above; authority, skey, collection, action and manage narrow or widen that. From the Atproto Spaces proposal (0016).

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • Private and shared email inboxes for the Comail Messages prototype. Stores messages, attachments, drafts, sent replies and mail state. Shared inbox membership is managed by the inbox owner.

  • ALPHA. An immutable private Comail message. Canonical RFC 5322 bytes are stored in the referenced permissioned blob; integrity and delivery metadata allow a standards-facing mailbox to be rebuilt.

  • A private copy of one folder of your sovrn email, kept up to date by sovrn. It isn't public and isn't shared with anyone unless you choose to.

  • Experimental Comail calendar Space. Calendar policies, event revisions and request claims are append-only. These collections describe the OAuth consent boundary; clients must validate the exact Space, grant and history before accepting data.

  • Private personal contacts and append-only operation history. Each account controls its own Space and separate consent.