Planned · not implemented
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.
Sarvalekha / Developer tools & services
Sarvalekha Platform
In designShared 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.
Design phase — not released. No supported release or subscription is established.
Planned capabilities
What is being designed.
Planned · not implemented
Share deliberately
Planned named sharing and groups retain explicit scope, expiry and revocation. Resource permissions remain separate from space membership and billing administration.
Planned · not implemented
Let products enforce access
Identity integration is one layer. Each product must qualify access checks throughout discovery, queries, streams, exports and supported commands.
Know the boundaries
Scope matters.
- 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.
A place in the wider picture
Connected, with clear roles.
What comes next
Direction, without a deadline.
- Shared identity, sessions and ownership foundations
- Named sharing and a complete Diagnostics integration
- Later qualified product integrations and bounded delegated work