At this level
app.cosmosis ยท 8- app.cosmosis.cluster record A 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*.
- app.cosmosis.clusterMember record A single account's membership in a Cluster. Lives inside the same Space as its parent `app.cosmosis.cluster` record. Delete this record to remove the account from the Cluster. The record key SHOULD be the subject's DID when that DID is a valid record key (true for all did:plc and most did:web identifiers), which makes writes idempotent and lets clients remove a member without a lookup; otherwise use a tid.
- app.cosmosis.clusterSpace space 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.galaxy record A user's Galaxy: the outer boundary of who they know they would feel comfortable interacting with online. Each account has at most one Galaxy (record key `self`). Membership is stored as separate `app.cosmosis.galaxyMember` records so a Galaxy can hold thousands of accounts. Galaxies are always permissioned: the Galaxy lives in a dedicated Space of type `app.cosmosis.galaxySpace`. The Space `skey` is a tid minted at creation (HappyView skeys are unique per Space type across an entire instance, s
- app.cosmosis.galaxyMember record A single account inside the owner's Galaxy. Lives inside the Galaxy's Space; the parent Galaxy is implied, since each account has exactly one Galaxy and each Galaxy Space holds exactly one Galaxy record. Delete this record to remove the account from the Galaxy. The record key SHOULD be the subject's DID when that DID is a valid record key (true for all did:plc and most did:web identifiers); otherwise use a tid. There must be at most one galaxyMember per subject, and readers must still de-duplica
- app.cosmosis.galaxySpace space Space 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 record A 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.superclusterSpace space 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.