At this level
site.exosphere · 1- site.exosphere.featureRequest.comment record A comment on a feature request. Published on the commenter's PDS.
- site.exosphere.featureRequest.commentVote record An upvote on a feature request comment. Published on the voter's PDS.
- site.exosphere.featureRequest.entry record A feature request submitted to a Sphere. Published on the author's PDS for public Spheres.
- site.exosphere.featureRequest.permissions record Permission overrides for the feature-requests module of an Exosphere Sphere. Published on the Sphere owner's PDS. Only non-default roles need to be specified — absent keys use the module's built-in defaults.
- site.exosphere.featureRequest.status record A status change on a feature request, published by an admin/owner on their PDS. Third-party indexers can replay these to derive the current status of a request.
- site.exosphere.featureRequest.vote record An upvote on a feature request. Published on the voter's PDS.
- site.exosphere.kanban.comment record A comment on a kanban task. Published on the commenter's PDS.
- site.exosphere.kanban.entry record A kanban task submitted to a Sphere. Published on the author's PDS for public Spheres.
- site.exosphere.kanban.permissions record Permission overrides for the kanban module of an Exosphere Sphere. Published on the Sphere owner's PDS. Only non-default roles need to be specified — absent keys use the module's built-in defaults.
- site.exosphere.kanban.status record A status change on a kanban task, published on the actor's PDS. Third-party indexers can replay these to derive the current column of a task.
- site.exosphere.sphere.label record Label assignment on a feature request or kanban task, published on the actor's PDS. Third-party indexers can replay the latest record per subject to derive the current label set.
- site.exosphere.sphere.member record A user's declaration that they are a member of a Sphere. Published on the member's own PDS. The Sphere owner/admin publishes a corresponding site.exosphere.sphere.memberApproval record to confirm the membership. Together, the two records form a bilateral proof of membership — similar to how AT Protocol follows work.
- site.exosphere.sphere.memberApproval record Published by a Sphere owner or admin on their own PDS to confirm a user's membership. References the member's site.exosphere.sphere.member record. The role field indicates the member's permissions within the Sphere.
- site.exosphere.sphere.permissions record Permission overrides for core Sphere actions (member management, module management, permission configuration). Published on the Sphere owner's PDS. Only non-default roles need to be specified — absent keys use the built-in defaults.
- site.exosphere.sphere.profile record Declaration of an Exosphere Sphere, published on the owner's PDS. Enables third-party discovery and indexing of Spheres across the AT Protocol network.