page.cavu.groupread

cavu.page 

{
  "$type": "com.atproto.lexicon.schema",
  "defs": {
    "main": {
      "collections": [
        "page.cavu.group",
        "page.cavu.progress",
        "at.margin.note"
      ],
      "description": "A group read: one book, one host, and the people reading it together (atproto permissioned data, proposal 0016). Anchored on the host's DID, so the host's PDS is the space host and holds one repo per participant. Each member writes their own activity into their own repo inside the space — where they are in the book (page.cavu.progress, a mirror of the record in their personal space) and the passages they've marked and written about (at.margin.note, moved here from their personal space by an explicit share, same rkey). Every member can read every repo; nothing here reaches the firehose, so a group note is visible to the group and to nobody else. The host's own repo additionally holds page.cavu.group/self, the record that says which book this is. Unlike page.cavu.personal there may be many per account, so the skey is a client-minted TID rather than a literal. Membership is host-internal and is NOT synced to the network: under managingAppPolicy the PDS asks the managing app, otherwise the host adds members directly. Either way the roster is private, which is what a reading group's roster should be.",
      "key": "tid",
      "name": "Cavu Group Read",
      "type": "space"
    }
  },
  "id": "page.cavu.groupread",
  "lexicon": 1
}

Validate Record

Validate a record against page.cavu.groupread

Validation Options
Treat any remaining unresolved references as valid

Metadata

DID
did:plc:citulkqjdzbnf7wd5xb6lled
CID
bafyreibysz5u5wzpszhdfmovlt6p6et7dd5y5ph3gbp4mqhurreq64yuuy
Indexed At
2026-08-26 21:52 UTC
AT-URI
at://did:plc:citulkqjdzbnf7wd5xb6lled/com.atproto.lexicon.schema/page.cavu.groupread

Similar Lexicons

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

  • page.cavu.group record

    What a group read is reading. Written by the host into their own repo inside a page.cavu.groupread space, under the fixed skey 'self' — one per space, so the space ref alone identifies the group and there is no second…

  • page.cavu.personal space

    A reader's private personal space (atproto permissioned data, proposal 0016): owner-only (member-list policy with no members), anchored on the reader's own DID so their PDS is also the space host, one per account under …

  • app.bulleted.space space

    An outline shared with a named set of people. Every bullet is still a record in its author's own permissioned repo for this space; the space is the authorization and sync boundary they share, not a place records are mov…

  • page.cavu.progress record

    Reading progress for one book, written to the reader's own repo. One record per (reader, publication) by convention: clients list their own repo and update the existing record for a publication rather than create a seco…

  • fyi.opensocial.pages space

    What members make for their group's site: pages, each in its author's own repo in the space. One saved under the key `profile` is that member's page about themselves; the rest wait for an admin to place them on the site.

Lexicon Garden

@