Beyond Tunnel

Governed communications across multiple transports.

Tunnel Sovereign governs its own communication plane today. It is being designed to extend that authority beyond it, so approved external channels can act as transport while Command decides who may communicate, with whom, for what purpose, through which capability, and for how long.

  • In development
  • Transport categories, not vendors
  • Authority decided at Command
  • Not available today
Governed Communications GatewayOrganizational authority descends through Tunnel Command to a Governed Communications Gateway. One transport lane is delivered: Tunnel Native, which already carries text, files and Tunnel-native voice and video. Six further transport categories are in development and are drawn as dashed outlines inside a band labelled IN DEVELOPMENT: collaboration platforms, messaging networks, email, external voice and video, mission and tactical bearers, and machine communication. Authority is decided above the gateway in every case, so a transport carries a result it did not decide and cannot widen.Organizational authorityWho decides, and on whose behalfTunnel CommandGrants, limits and withdraws authorityGoverned Communications GatewayApplies the authority decision to a transportTunnel NativeDelivered Text, files, voice, videoIN DEVELOPMENTCollaborationPlatform channelsMessagingNetworks not ownedEmailStore and forwardExternal voice and videoThird-party mediaMission / TacticalRadio, satellite, fieldMachineNo person presentThe transport may change. The authority does not.
Authority is decided once, above the gateway. A transport carries a result it did not decide and cannot widen. Tunnel Native is the delivered transport, and it carries Tunnel-native voice and video today. The categories inside the dashed band are in development and are not available. They are categories, never named products.

The separation

A transport carries a decision it did not make.

Every communication system already decides two different things: whether a message can be delivered, and whether it should have been allowed at all. Most systems answer both in the same place. Separating them is what makes an external channel governable without trusting it.

The transport may change. The authority does not.

  • Command establishes authority. Transport carries the result.
  • Reachability is a property of a network. Authority is a decision of an organization.
  • Possession of a channel is one thing. Authority to use it is another.
  • A capability withheld at Command stays withheld on every transport.
  • Withdrawal is decided once and applies wherever the grant reached.
  • The authority to communicate stays with the organization that issued it.

Transports

One authority model. Several communication transports.

These are transport categories rather than named products. This site names a platform once it is integrated, and today that list holds one entry: the native Tunnel plane.

Delivered

Tunnel Native

The Tunnel communication plane, messaging, files and native voice and video alike, governed end to end by Command today.

In development

Collaboration platforms

Channels inside an organization's existing collaboration estate, carrying an authority decision made outside it.

In development

Messaging networks

Consumer and carrier messaging an organization does not control, bounded by a grant it does.

In development

Email

Store-and-forward correspondence, bounded by the same grant that bounds a message.

In development

External voice and video

Approved third-party real-time media, carrying a decision Command made outside it.

In development

Mission and tactical bearers

Radio, satellite and field-carried bearers, where reachability is intermittent and authority still has to hold.

In development

Machine communication

Systems and services that communicate without a person present, acting under an authority someone is accountable for.

Tunnel-native voice and video are part of the current platform. The Governed Communications Gateway extends the same authority model to approved external transports.

What it governs

One authorization, and what the transport is not permitted to change.

An organizational policy becomes a single grant with a stated scope. The example below is illustrative: it shows the administrative shape of a decision, not the internal format that carries it.

Authorization · illustrativeActive
PrincipalAn operator, on an enrolled device
CounterpartyOne named external party
MissionA single named mission
CapabilitiesText and document. Voice is not granted
DirectionOutbound and inbound with that party only
ExpiryA stated time, after which it lapses without being revoked
TransportAn approved transport
GovernanceGranted at Command, recorded in a verifying audit chain
The transport carries this decision. It does not make it, cannot widen it, and cannot keep it alive past its expiry. Withdraw the grant at Command and the capability stops, on whichever transport was carrying it.

Current state

In development, stated plainly.

The native Tunnel transport is governed end to end today, and that is the only transport this platform governs. The gateway and every external lane beneath it are architecture and intent.

One transport is governed today, and it is the native Tunnel plane. Treat everything else on this page as architecture and intent: the external lanes describe where the authority model is going, and an organization evaluating governed communication now is evaluating the native plane under controlled evaluation.

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

Bring the transports you already operate.

An executive briefing covers the authority model, where the gateway architecture is going, and what is and is not delivered today. An engineer is present.