Product direction
Four vectors describe how this platform is intended to develop. They are directions, not a schedule: this page carries no dates, no availability commitments and no ordering, because none of those would be evidence.
Read this first
They are two different things, and this page is the second one. The first is published in full, with its limits, on Assurance and the platform pages.
Governed messaging, files, Tunnel-native voice and video, mission rooms and compartmented identity across Android, iOS and macOS. Every claim is published on Assurance with the limit that qualifies it.
Intended platform evolution. No capability here is available for purchase, evaluation or deployment, and no date is published for any of it.
Tunnel-native voice and video are part of the current platform. The Governed Communications Gateway extends the same authority model to approved external transports.
Four vectors
Each vector extends the same question the platform already answers for a message: who holds the authority to do this, under which conditions, and for how long. None of them replaces that question with a different one.
The authority model applies to more of what an organization does than sending a message.
Two organizations can communicate without either surrendering its own authority.
Authority becomes something other systems can be built against.
Authority holds where the network does not.
Product Direction describes intended platform evolution. It does not represent currently delivered functionality unless a capability is explicitly stated as delivered.
The nearest vector
Of the four, the gateway is the one that changes what this platform is. It separates the authority decision from the channel that carries it, so an organization's existing communication estate can operate beneath one authority model rather than alongside it.
The transport may change. The authority does not.
The architecture, the transport categories and the current state are set out on the Governed Communications Gateway page. It is in development. No external communication platform is integrated or supported today.
Assurance path
A platform direction is only credible next to an honest account of what has been demonstrated. This is the sequence this program is following, and the stage it is actually at.
Automated, adversarial and cross-language evidence, plus live testing in a controlled environment. Substantially complete, and written by the implementation's own authors.
Two-endpoint acceptance of the application path on real hardware. Device and operator authority already carry physical evidence within a stated scope; the application path does not.
An external qualified party examining a frozen, reproducible baseline. Architecture, protocol, endpoint and infrastructure assurance are separate disciplines and are scoped separately.
Findings are fixed and the affected properties are retested against the same baseline, so a result can be attributed to a version.
Certification or accreditation against the scheme a deployment actually requires. No scheme is selected, and none is held.
Current stage: controlled evaluation readiness and internal verification. Independent external assessment and deployment-specific certification remain planned assurance milestones.
What this page is not
This company publishes its evidence state in full, including what is outstanding. Nothing on this page belongs in that register until it has been built and demonstrated.
No capability described here is available for purchase, evaluation or deployment on the strength of this page. What is available is published on Assurance and in the platform pages, with its limits attached. Where a direction and the evidence state appear to disagree, the evidence state is correct.
Product configurations, integrations and operational capabilities are delivered according to customer requirements, deployment environment, validation scope and applicable authorization. No approval for classified information is represented.
Evaluate it
An executive briefing covers both: what the platform does today, with its limits, and where the authority model is being taken. An engineer is present.