







Why Capability Trees are the right governance primitive for permissioned spaces.
Capability Trees: Sovereignty Is the Point
This piece argues that DASL introduces security risk when applied to delegations, and that by not using DASL, capability trees avoid that risk.
The Substrate Requirements for Capability Trees
The bar other data sovereignty substrates must meet, to be compatible with Capability Trees.
Habitat & permission spaces for organizations - building [at] habitat
Our plans for organizational permissions on spaces
Capability Trees: A Protocol-Level Extension of Object Capabilities, Draft 4
This draft incorporates feedback from Brooklyn Zelenka (@expede.wtf) and Daniel Holmgren (@dholms.at), and developments in the ATProto Private Data Working Group. Previous drafts remain available for transparency.
greensky: what does permissioned data feel like? - building [at] habitat
Capability Trees: A Protocol-Level Extension of Object Capabilities, Draft 3
This draft incorporates feedback from Brooklyn Zelenka (@expede.wtf), Daniel Holmgren (@dholms.at), and Zicklag (@zicklag.dev), and addresses questions raised in the ATProto Private Data Working Group. Draft 2 remains available for transparency.
Capability Trees: A Protocol-Level Extension of Object Capabilities, Draft 2
This draft addresses questions and feedback from the ATProto community, in particular from Zicklag (@zicklag.dev) and Brooklyn Zelenka (@expede.wtf). Draft 1 remains available for transparency.
Evaluating permissioned spaces for community contexts - meri's missives
A look at Bluesky's proposed approach to private data on ATProto
Early Permission Sets · bluesky-social atproto · Discussion #4437
Progress is coming along on "Permission Sets", as part of the atproto OAuth and permission system. As with other parts of the protocol, seeing how this functionality gets implemented for ...
Permissioned Spaces - WG.1
@Permissioned Spaces Expressive Authorization at the PDS @verdverm.com | @blebbit.app
Permissioned Spaces - WG.1
@Permissioned Spaces Expressive Authorization at the PDS @verdverm.com | @blebbit.app
Habitat's road to release: 01 simplespace - building [at] habitat
First up: a pre-implementation of permissioned spaces
while we're here, here's how i wish permission sets were explained to me
atproto made simple: granular permissions
underreacted.leaflet.pubwhy they’re bad? just ask claude. it ran into the same exact things i’ve ran into. until all of these are fixed imo its perfectly acceptable for developers to ignore permission sets. they’re just not baked until they’re understandable read this transcript: claude.ai/share/dbd3e30d-958d-4ac8-a3fc…
Claude
claude.ai