app.cosmosis.superclusterSpace
Space type for a single Cosmosis Supercluster. Each Supercluster gets its own Space of this type, holding exactly one app.cosmosis.supercluster record. The Space skey and the record's rkey share the same tid. Resolving the Supercluster also requires access to the Spaces of every Cluster and Supercluster it references.
Details · space
| Kind | space |
|---|---|
| Authority | cosmosis.app |
| Indexed |
Space
space · key tidShown at sign-in
name
stringCosmosis Supercluster
Collections
collections
array · nsidThe record collections clients of this space type use. A space: scope covers these unless it names its own.
Asking for it
OAuth scopeA 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 matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
Space type for a single Cosmosis Cluster. Each Cluster gets its own Space of this type, holding exactly one app.cosmosis.cluster record plus that Cluster's app.cosmosis.clusterMember records. The Space skey and the Cluster record's rkey share the same tid. Granting an app access to one Space of this type exposes only that one Cluster.
-
app.cosmosis.galaxySpace
spaceSpace type for a user's Cosmosis Galaxy: the outer boundary of who they would feel comfortable interacting with online. Each user has one Space of this type, holding the app.cosmosis.galaxy record (rkey self) and the Galaxy's app.cosmosis.galaxyMember records. The skey is a tid, because HappyView requires skeys to be unique per Space type across the whole instance.
-
app.cosmosis.supercluster
recordA derived grouping of accounts defined as a set expression (union / intersection / difference) over Clusters and/or other Superclusters. No members are stored directly; membership is evaluated at query time by resolving the expression tree. Superclusters are always permissioned: each lives inside its own dedicated Space of type `app.cosmosis.superclusterSpace`, with the Space `skey` and record `rkey` sharing the same tid. (Every leaf of an expression is ultimately a Cluster, and Clusters are alw
-
app.cosmosis.cluster
recordA personally curated group of accounts. Clusters have no fixed size cap: membership is stored as separate `app.cosmosis.clusterMember` records rather than inline, so a Cluster can hold thousands of members. Clusters are always permissioned: each Cluster lives inside its own dedicated Space of type `app.cosmosis.clusterSpace`. Note that the Space's own member list governs *access* to the Cluster and is distinct from the clusterMember records, which are the Cluster's *contents*.