The Capability Stack
Eight layers. Any domain.
Hierophant for space and maritime is a transport-agnostic sovereign protocol — the same ZK command structure operates over acoustic, RF, LEO uplink, or fiber without modification to the security architecture.
01
Transport-Agnostic ZK Protocol
The Hierophant protocol layer is transport-independent. It operates identically over acoustic modems for submarine communications, LEO satellite uplinks, LoRa RF for surface vessels, and fiber for naval HQ. The security architecture does not change when the physical transport changes — post-quantum protection and zero-knowledge identity are properties of the protocol, not the transport.
Transport-Agnostic · Any Domain · Same Protocol
02
Post-Quantum Naval Encryption
NIST post-quantum cryptography for naval and space-domain communications — at the highest security parameters for strategic traffic with sensitivity windows exceeding the quantum threat timeline. Deployment orders, patrol plans, and fleet dispositions are protected against quantum decryption on a 20-year horizon.
NIST PQC · Forward Secrecy
03
EMCON-Compliant Transmission
Fixed packet sizes, phantom traffic injection, and transmission timing that cannot be correlated to specific platform activity patterns. A Hierophant transmission cannot be attributed to a specific platform type, mission profile, or operational event by passive direction-finding or traffic analysis — EMCON compliance at the protocol layer.
Fixed Packets · Phantom Traffic · EMCON
04
LEO & HAPS Sovereign Integration
Integration with sovereign low-earth-orbit constellations and high-altitude platform systems as transport layers for the non-IP C2 protocol. When undersea cables are severed, when surface RF is jammed, the LEO or HAPS segment continues the sovereign command link without any change to the protocol security properties.
LEO · HAPS · Sovereign Segment · Failover
05
Non-IP Private Networks
Naval and space C2 traffic on a non-IP protocol is invisible to the IP-layer network scanners and traffic analysis infrastructure that adversary intelligence services operate. No IP address is assigned to any platform. No route appears in BGP tables. The fleet communication architecture has no representation in the global internet address space.
No IP Addresses · No BGP · Invisible
06
Anonymous Platform Identity
Zero-knowledge protocol means no communication event reveals the identity or position of the transmitting platform. Even a passive adversary with full visibility of the channel sees encrypted data of uniform appearance with no headers, routing information, or protocol signatures that identify the platform type or unit. The fleet is operationally invisible at the communications layer.
ZK · No Platform IDs · No Position Disclosure
07
Undersea Cable-Independent Routing
The sovereign mesh does not require undersea cable infrastructure at any layer. Naval HQ to fleet communications route through RF, LoRa, LEO, or HAPS as primary transports — cable connectivity is an optional additional path, not a dependency. Cable interdiction by adversary naval forces does not disrupt command continuity.
No Cable Dependency · Multi-Transport · RF · LEO
08
Naval Hardware Messenger
Austrian-manufactured, OS-free hardware messenger for shipboard and submarine deployment. Sealed, pressure-resistant enclosure for undersea environments. Full duress and self-destruct capability for capture scenarios. The hardware carries no operating system, no civilian attack surface, and no identifiers that link it to a specific vessel or command.
OS-Free · Sealed · Anti-Tamper · EU Hardware