v1 roadmap: feature in/out cut
closedGoal
Set the v1 feature boundary (in/out) now that ADR-0006 locked the data-placement and space topology.
In scope (proposed)
- Signup (OAuth + XRPC + DNS ownership gate), custom + hosted-PDS + service domains
- Provisioning (postmaster records → Stalwart via Registry)
- Login (brokered atproto OAuth) + OIDC tokens + app passwords
- Webmail (fork) + app view (admin)
- Public
at.sovrn.mail.servicerecord at login
Out of scope / deferred (per ADR-0006 + docs/09)
checkUserAccessmanaging-app hook + admin app-sharing UX (v2)- GAL / roster-visibility flag (design later)
- Request→ratify member writes; per-user personal space; third-party client attestation
- Calendar/mail publication lexicons, open-calendar projection
- Multi-node Stalwart HA, paid tiers, E2EE
Deliverable
A single document (docs/roadmap-v1.md) or tracker comment listing the cut line, tied to Q2 (MVP cut line) and the Phase 0 exit gate (0d541aa).
Basis: docs/adr/0006-data-placement-and-space-topology.md, docs/09-open-questions.md.
1 Comment
Superseded/complete: the v1 feature cut is embodied in ADR-0009 and the live trackers (75966cc cell architecture; epic 516fcde for the signup saga); no separate roadmap doc is maintained. In-scope items are tracked by their feature bugs (login/webmail: 0ffe23b, 764b8e2, ac83db8, 31b625f; provisioning: epic 516fcde). Closing.