Sharp#Soft ships as a product, but it was designed as a platform. This page names the directions the architecture points toward — plainly, and deliberately without dates, specifications, or promises.
When a direction becomes a product, the whitepaper will say so first.
A roadmap without dates is a choice, not an omission.
What this page tells you
What it deliberately withholds
From nearer to further. Read top to bottom.
Sealed messaging between identities ships first; invitable shared spaces come next. A space opens only for its members — membership is cryptographic, not a database row — and removing someone genuinely closes the door: the space key rotates, and what they never opened stays closed to them. The direction: the vault and the chat grow into rooms.
One client, built to travel: Windows, macOS, and Linux as siblings rather than ports. Because private keys live on the device, each new platform carries the same guarantees — not a weaker copy. Further out, the pocket: a phone client is a captured direction, not yet a promise.
Every message inside the platform already travels sealed end to end, addressed to identities rather than to network locations. That fabric was designed to reach further than our own products — toward machines that carry identities of their own, reaching each other with no open ports, no perimeter, and no middle party in a position to observe. The direction: platform-grade encrypted transport, offered as a capability instead of kept as plumbing.
The identity-and-cryptographic fabric is deliberately separable from any single product surface. The direction: opening that fabric to third parties, so software built by others inherits the same sealing, the same identity model, and the same refusal to hold user keys — without rebuilding any cryptography.
Ownership on this platform is cryptographic: what an identity holds, only that identity can unseal. That is also the property a genuine unit of value requires. Cryptographic value primitives are a research direction — early, deliberate, unhurried. We will say more when there is more to say.
Why so vague? Because the alternative is dishonest. A public roadmap full of dates and feature lists reads well right up until reality edits it. We publish the direction of travel and keep the promises for work that exists — every concrete claim we make lives in the whitepaper, where it is traceable to its evidence.
This page points forward. For what stands today — the guarantees, the boundaries, and how to verify both — the whitepaper is the document of record.