Planned design
One identity, distinct contexts
The design separates personal, family and organization spaces. One person may participate in several contexts while resources retain an authoritative owning space.
Public product notes
Platform, in context.
A planned shared foundation for identity, ownership spaces and resource access across Sarvalekha products.
Purpose & status.
Shared identity should make participation understandable. Platform is being designed to connect sign-in, ownership spaces and resource access without turning membership or payment into permission to read private work.
Capability scope.
Planned design
Share deliberately
Planned named sharing and groups retain explicit scope, expiry and revocation. Resource permissions remain separate from space membership and billing administration.
Planned design
Let products enforce access
Identity integration is one layer. Each product must qualify access checks throughout discovery, queries, streams, exports and supported commands.
Important limitations.
- Design phase — not released. No supported signup, SDK, installation or live endpoint is established.
- Shared identity, sessions, sharing and audit remain design goals. No production availability, capacity, cloud-provider or security guarantee is established.
- Sponsorship and billing authority do not grant private content access. Product services must enforce their own current resource permissions.