Account contract
availableA typed account boundary anchors identities used by every messaging profile.
Inspect source evidence →Messaging protocol foundation
One messaging protocol. Three explicit policy profiles.
Kynetra Talk establishes shared account, device, conversation, envelope, and edition-policy contracts for Personal, Business, and Secure messaging without presenting unfinished delivery, persistence, or encryption work as shipped.
Wave 1 foundation
Stable contracts before delivery infrastructure.
The current implementation defines protocol objects and policy boundaries. Message storage, external channels, native encryption, customer data, and deployment remain outside the shipped foundation.
Device contract
availableDevice identity is represented separately from account identity for later policy enforcement.
Inspect source evidence →Conversation contract
availableConversation scope provides the shared context for future message and participant operations.
Inspect source evidence →Envelope contract
availableA stable envelope shape separates protocol semantics from future delivery providers.
Inspect source evidence →Message persistence
roadmapNo production message store or customer-data path is part of the Wave 1 foundation.
Native encryption
roadmapThe Secure profile is a policy boundary; a native encryption implementation is not yet claimed.
Edition policy
Profiles change policy, not the protocol core.
Personal, Business, and Secure are explicit product profiles over the same foundation. Their operational delivery remains subject to later implementation and evidence.
01 · personalIndividual context
Policy shape for personal messaging experiences over the shared core.
02 · businessOrganizational context
Policy shape for tenant-aware business communication and governance.
03 · secureHigher-assurance context
Policy boundary for stronger security requirements without an unverified encryption claim.
04 · protocolOne shared contract
Accounts, devices, conversations, and envelopes remain consistent across profiles.
Checked-in evidence
A protocol foundation, not a production messenger claim.
The product state is derived from the canonical Wave 1 source and keeps every unimplemented delivery capability explicit.
Foundation version
The current canonical package version for the Talk Wave 1 source.
Verified source revision
The reviewed foundation revision establishing protocol objects and edition-policy boundaries.