Glossary
The vocabulary, in plain English.
This platform introduces a small number of terms deliberately. Each one is defined here in a sentence or two, without a protocol dissertation.
- Category
- Authority model
- Components
- Deployment
Terms
Fourteen terms.
Category
Sovereign Communication Authority
The governance of communication authority as infrastructure. The organization decides who may communicate, from which device, under which identity, with whom and for how long, while message content stays outside the infrastructure that carries it.
Authority model
Device Authority
The decision about which physical devices exist inside the system at all. A device is admitted deliberately and can be withdrawn on its own, without disturbing other devices.
Authority model
Identity Authority
The decision about which operational identity a person holds, and which authority that identity carries. Authority can be constrained by mission context, relationship, capability, device and time, rather than granted once and held everywhere.
Authority model
Relationship Authority
The decision about who may reach whom. A relationship is issued as a signed, directional, expiring authorization rather than discovered through a directory.
Authority model
Mission Authority
The decision about the scope a set of relationships belongs to. Closing a mission removes the standing authority created inside it.
Component
Tunnel Mobile
The native operator endpoint. Content is sealed and opened here, and the payload key exists only on authorized endpoints.
Component
Tunnel Command
The organization's authority environment. It issues, scopes and withdraws authority, and holds no key that can decrypt mission content.
Component
Tunnel Relay
Delivery infrastructure the customer can operate. It carries sealed material it cannot open and never receives the authorization graph.
Component
Secure Core
The shared foundation the other three are built on: cryptography, identity, authorization, delivery and recovery, implemented once rather than three times.
Architecture
Relationship-Protected Networking
Protecting the communication relationship itself, not only the message. Delivery carries an opaque alias scoped to one direction, mission and epoch, so the architecture maintains no global relationship graph. Endpoints necessarily hold their own local relationships, and Command holds the authorizations it issued.
Architecture
Secure Mission Bundle
The transport-independent sealed package that carries protected material together with its own authorization, policy and expiry. It can be composed offline and handed on when a permitted transport appears.
Deployment
Managed Deployment
Tunnel operates the relay infrastructure under defined operational controls. The customer still governs its own organization, and payload keys stay on authorized endpoints.
Deployment
Sovereign Deployment
The customer operates the infrastructure and holds the enrollment authority, the cryptographic roots, the jurisdiction and the audit domain. On-premises, private cloud, isolated or air-gapped.
Commercial
Controlled Evaluation
A scoped engagement in which a qualified organization evaluates the platform on its own devices, under written scope and success criteria, ending on a known date with a documented outcome.