Persistent Systems Wave Relay vs Protocol-Native Authority Semantics

Vendor & Product Reality

Persistent Systems is a privately held, New York-headquartered defense technology company founded in 2007. Its product family centers on the MPU5 handheld radio built on the Wave Relay MANET, an embedded module variant integrated into vehicles and unmanned platforms, higher-power infrastructure relay configurations, and a network management application for situational awareness across the mesh. Exact model designations and radio-frequency band coverage vary by configuration and procurement, and the current specifics should be taken from the vendor's own datasheets rather than from this article; the architecture-level point below does not depend on them. The radios use a software-defined radio architecture that enables waveform updates without hardware refresh. Precise deployment counts are not publicly itemized, but the product is fielded broadly across the U.S. Department of Defense, allied procurements including Foreign Military Sales and direct commercial sale, and equipment flows that have reached Ukraine since 2022. Wave Relay is not the only tactical MANET radio in the field; Silvus Technologies, TrellisWare, and L3Harris all compete in adjacent profiles. The radio's value proposition is consistent across customers: a self-forming, self-healing IP-routable mesh that survives mobility, multipath, and active jamming, with throughput sufficient for video, telemetry, and command-and-control payloads. The radio terminates IP. Above the IP layer, the customer ships whatever payload it ships, whether Tactical Assault Kit (TAK) traffic, full-motion video from unmanned aerial systems, voice over IP, sensor telemetry, or file transfer for mission packages, and the radio carries it. What the radio does not do, and does not claim to do, is govern who is permitted to inject what claim, under what authority, and how that claim should be recognized when the bearer crosses a coalition boundary or moves out of contact with command infrastructure for an extended period.

Architectural Gap

The architectural gap is the layer between link-layer hardening and application-layer payload, and it has three dimensions that recur across every Wave Relay customer integration. First, authority taxonomy: when a sensor on an unmanned platform emits an observation that traverses the mesh and reaches a command node, the receiving system must determine whose observation this is, under what credentialed role it was generated, and whether the role has the authority to inject the claim into the operational picture. Wave Relay does not carry this. The application above it must reconstruct it, typically through a combination of TAK certificates, Active Directory or equivalent identity federation, mission-specific keying, and operator discipline about which device is bound to which role. The reconstruction is per-customer, per-mission, and frequently per-coalition. Second, continuity under contested or denied conditions: when a node operates outside backhaul to its credentialing authority for hours or days, the question of whether its claims remain admissible is unanswered by the radio. Revocation depends on the credentialing authority being reachable, which in the operating profile Wave Relay was designed for is exactly the condition that fails. Customers solve this with operational-discipline workarounds, pre-shared keys with manual rotation, mission-duration certificates, time-bounded trust assumptions, that do not compose well across coalition partners with different doctrine. Third, cross-coalition recognition: a Ukrainian unit operating with a U.S.-supplied Wave Relay and a Polish unit operating with a separately procured Wave Relay are on radios that can technically interoperate at the link layer; the trust layer above is two distinct customer reconstructions that have to be bridged through per-operation, per-coalition manual integration. The cumulative cost across the customer base is substantial; the cumulative structural risk is that critical operations rely on integration that has been assembled bespoke by the using force, frequently under time pressure, and has not been independently verified against an authority taxonomy that exists at the protocol level rather than the integration level. Persistent Systems has, defensibly, declined to scope into this layer because its core competence is link-layer radio engineering and because the authority taxonomy has historically been treated as a national-command-authority concern. The gap is structural, it is not a deficiency of the radio, but the cost of leaving it as customer reconstruction has grown as coalition operations and unmanned-platform proliferation have multiplied the number of credentialed roles per mesh.

What the Memory-Native Protocol Primitive Provides

The memory-native protocol primitive defines a wire format that carries authority semantics as protocol-native fields. An observation generated by a credentialed sensor carries, in the protocol envelope, the authority under which the observation was made, a continuity hash that binds the observation to the device's operational history, hop-history that records the path the observation took across the mesh, and admissibility constraints that govern what receiving systems may do with the observation. The fields are not added by an application-layer wrapper that the using force assembled in integration. They are properties of the protocol itself, validated by a primitive-defined admissibility framework that runs at the receiver before the payload is admitted to the operational picture. The framework is local: a receiver can validate a packet's declared authority and continuity from the packet's own contents and from the receiver's local credentialing root, without backhaul to a central authority. This addresses the contested-environment continuity gap directly: a node can continue to admit credentialed observations from peers it has previously vouched for, and the credential chain travels with the observation rather than depending on connectivity to an authority server. Cross-coalition recognition becomes a credentialed cross-recognition: the U.S. authority root and the Polish authority root cross-sign at the doctrinal boundary, and observations generated under one root carry credentials that the other root can verify from the protocol envelope. The primitive does not replace Wave Relay's link-layer hardening. It defines the layer above, where Wave Relay was never scoped to operate, and it defines it as protocol rather than as integration.

Composition Pathway

The composition pathway with Wave Relay is consumption rather than modification. The primitive's wire format is carried inside the IP payload that Wave Relay already transports. The radio's waveform, mesh routing, encryption, and management plane operate unchanged. The vendor's network management application continues to render network topology and node health. Existing TAK-based situational awareness continues to operate; the primitive's authority fields appear as additional admissibility metadata that TAK-aware applications can consume or ignore depending on integration maturity. Customer integration shifts from reconstructing the trust layer in bespoke architecture to admitting the primitive into the customer's authority hierarchy. The U.S. command authority becomes a credentialing root within the primitive's framework. Allied authorities become credentialing roots that cross-sign with the U.S. root at doctrinal boundaries the using forces already negotiate. Ukrainian forces operating with U.S.-supplied Wave Relay equipment gain a protocol-native authority layer rather than a customer reconstruction. Coalition operations gain a structural cross-coalition recognition framework that does not require per-operation, per-mission integration to function. Unmanned platforms gain credential continuity that survives backhaul loss. The radio continues to do what the radio does well; the layer above stops being the using force's individual reconstruction problem.

Commercial & Licensing Posture

Persistent Systems' commercial position is that of a hardware vendor with deep waveform and integration expertise; Wave Relay sells as a radio family and as the management system above it, not as a trust framework. The licensing posture Adaptive Query contemplates is a primitive license to Persistent Systems that the company integrates as an embedded capability of the Wave Relay product family: a firmware-level admissibility framework that ships with the radio and a management-system extension that exposes credentialing, cross-coalition recognition, and continuity-aware revocation as configurable customer-facing capabilities. The commercial value to Persistent Systems is a differentiated trust layer that no competing tactical MANET vendor offers, that addresses pain the customer base is paying integration cost to solve today, and that strengthens the company's position in coalition procurements where cross-recognition is a procurement discriminator. The commercial value to Adaptive Query is per-radio royalty scaled to the Wave Relay deployment footprint and a foundational reference deployment in the defense market. The structural value to the using forces is that the trust layer they have been individually reconstructing becomes a property of the radio they have already procured, validated independently, and consistent across coalition partners. The radio remains the radio. The protocol above it carries what the protocol should always have carried. The licensing structure is intentionally compatible with Foreign Military Sales pathways and with the export-control regime that Wave Relay already operates within: the primitive's specification, admissibility framework, and reference verifier are licensable under terms that match the controlled-technology disposition of the radio itself, so that a coalition partner authorized to procure Wave Relay is authorized to receive the trust layer that integrates with it. Pricing is structured as a per-unit royalty embedded in the radio's bill of materials at the manufacturing step, plus a recurring license fee for the management-system extension sold alongside the vendor's network management offering. Adaptive Query retains rights to license the primitive in parallel to non-competing vendors in the tactical-radio adjacencies, Silvus, TrellisWare, L3Harris, under terms that recognize Persistent Systems' first-mover position and that accelerate the cross-vendor recognition that coalition operations require. The endpoint of the commercial pathway is a tactical mesh ecosystem in which authority semantics are a property of the protocol every participating radio speaks, regardless of vendor of origin or coalition of operation, and in which Persistent Systems holds the lead position as the first vendor to ship that property as a native capability of its radio family.

Enabling Embodiments

A skilled implementer can build the approach described here directly from the disclosed structure. The unit of transport is a self-describing agent object that carries, in a signed envelope, an identifier, a payload, and a memory field holding execution lineage, access log entries, and policy references. The authority under which a claim was generated, the continuity binding that ties a claim to a device's operational history, the recorded traversal path across the mesh, and the constraints that govern admission are encoded as fields of that envelope rather than as an application-layer wrapper. On receipt, a node parses the envelope, verifies the signature block, and evaluates admissibility locally against its own credentialing root and against the embedded policy references, without a round trip to a central authority server. This is what makes the framework operate under denied or intermittent backhaul: the credential chain travels with the observation, and a node may continue to admit claims from peers it has previously vouched for.

The disclosure is intended to be read broadly, and admits many embodiments. The self-describing object may be carried inside the IP payload of a MANET radio such as Wave Relay, or over TCP/IP, HTTP, WebSockets, WebRTC, mesh relay, or delay-tolerant networking, with no modification to the underlying transport. The credentialing root may be a single national command authority, or two or more authorities that cross-sign at a doctrinal boundary so that observations generated under one root carry credentials another root can verify from the envelope. Admissibility evaluation may be performed at every hop, at zone boundaries, or only at terminal command nodes. Continuity may be expressed as a hash chain, a signed lineage record, or an equivalent tamper-evident structure. The credentialing role bound to a device may be static for a mission, rotated on a schedule, or revised as the device's memory field accumulates. The receiving application may consume the authority fields as first-class admissibility metadata or ignore them for backward compatibility. None of these variations is essential to the core, which is that authority, continuity, traversal history, and admissibility are protocol-native fields validated locally at the receiver. The cases described above are operating examples, not the outer bound of the disclosure.

Disclosure Scope

The invention described in this article, the Memory-Native Protocol and its protocol-native authority, continuity, traversal-history, and admissibility semantics, is disclosed in United States Patent Application 19/366,760. Statements in this article about what the invention does, its mechanisms, fields, and guarantees, are grounded in that application and are the subject of this dated public disclosure.

All references to Persistent Systems, Wave Relay, and the other named vendors and products (Silvus Technologies, TrellisWare, L3Harris, and the TAK ecosystem) are external market and technical context. They describe third-party systems accurately at the architecture level and are not claims of United States Patent Application 19/366,760. Product names, model designations, deployment figures, band coverage, and commercial and licensing arrangements attributed to those vendors are the properties of their respective owners and should be confirmed against the vendors' own materials; the commercial and licensing posture described above is a contemplated arrangement of Adaptive Query and does not represent any agreement with or endorsement by Persistent Systems.