email.atmos.calendar

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.

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 Calendar (alpha)

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 calendar preferences and source settings. Each account controls its own Space and separate consent.

  • A private or shared CalenDat calendar.

  • Private calendar events in the community.lexicon.calendar.event shape, plus one dev.serendipty01.impro.calendarList record (rkey self) naming the calendars and their colours. One space per account (skey self).

  • 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.

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