sha.chat01Now
Build and verify
Messaging, calls, Personal / Professional separation and recovery. Progress is assessed against working builds and device checks.
Most of this page is still in English. Its Kugg text is being written.
Roadmap · Updated 29 October 2026
Two worlds.
One considered release.
A working product for personal and professional communication, built module by module. The next planned invitation window is closed beta in Q1 2027.
The interactive preview needs JavaScript.
preview · sample
02Before invitations
Pass the release gates
Signed distribution, end-to-end security checks, reliable calls and messaging, and verified handling of access requests.
03Q1 2027 · target
Closed beta
The same planned window shown on the homepage. Invitations follow verified readiness; this is a target, not a guaranteed release date.
04During beta
Validate chosen modules
Test selected features, scoped agents and Professional workflows with participants. Agentic team management → Orchestrator → Agentic team remains in scope.
05After validation
Expand with evidence
Broader availability and additional integrations follow reliability, privacy and recovery checks. No public-beta date is committed here.
What the beta should make possible
A complete everyday loop.
Then more modules.
Choose a space→Message or call→Use chosen modules→Recover reliably
The first invitation should lead to an experience that can be checked on a device: the right identity, the right contacts, a conversation that works and a clear way back when something fails.
A useful private space.
Encrypted conversations and calls, personal contacts and predictable notifications, with recovery tested as part of the experience.
Professional, with its own boundaries.
Professional contacts, policy-scoped actions and a clear separation from personal keys, history and model context.
A team with a defined scope.
Agentic team management → Orchestrator → Agentic team, with chosen models, tools, delegation limits and review of consequential actions.
Optional value workflows.
Wallet and gateway capabilities follow their own implementation and verification requirements. Interest in a module does not make it available in the first build.
How a milestone earns its place
A target becomes an invitation
when the experience holds together.
Working build
Installable, signed distribution and a tested path through messaging, calls and the active Personal or Professional identity.
Boundaries and recovery
Device checks for isolation, revoked access, failed networks, session changes and recovery of the intended state.
Module availability
Capabilities enabled through feature flags when their own acceptance checks pass. The catalogue remains broad while availability is verified module by module.
Participant feedback
Selected needs guide prioritization. Usability, accessibility and reliability findings feed into the next build rather than being treated as completed work.
Feature breadth stays in scopeThe 178-capability catalogue records planned choices. Selection expresses interest; it does not confirm delivery.
Evidence determines availabilitySecurity, device testing, reliability and recovery checks determine which modules become available.