(2026-10-12, owner request: document that this is coming; not started)
Agents should be able to keep activity that isn't public, using atproto's Spaces (permissioned data) rather than a private tier invented by didbot. The plan epic plan/spaces.md already holds the design position: access control, not confidentiality, with the work gated on the Spaces specification maturing and a reference implementation landing. This issue tracks actually building it once that gate opens.
Scope when picked up:
- the PDS side: storing and serving records in a Space, admission of readers, and the specification's integrity and signature construction
- OAuth scopes for Space access
- agent-side: writing into a Space through the existing account credentials
- vibescrobble showing the difference between public and Space activity (the epic's exit criterion: a record in a Space is readable by an admitted reader, invisible to one who isn't, and the canvas shows the difference)
Any new lexicon, credential or stored state needs explicit owner approval per CLAUDE.md.
Checked on main at 1351e8b33 in a sweep. Not a contained fix: it needs new stored state (records in a Space and admitted readers), new OAuth scopes and likely a new lexicon. Each of those needs owner approval.
plan/spaces.mdkeeps it blocked on the Spaces spec maturing.