Trellisware TSM Optimizes Routing, Not Authority Resolution
by Nick Clark | Published April 25, 2026
TrellisWare Technologies' TSM-X waveform — running on the TW-950 Banshee handheld and TW-875 Ocelot family of tactical radios — has become the de facto mobile ad hoc networking (MANET) standard for U.S. Special Operations Command, allied special-mission units, and a growing roster of conventional-force programs. The waveform's scalability under jamming, mobility, and terrain occlusion is widely regarded as best-in-class. But TSM is a link-and-network-layer technology. It moves bits across a contested mesh; it does not decide whether the payload those bits encode should be admitted into a receiver's operational state. Authority resolution, governance, and payload-level admissibility live in an architectural layer above TSM — a layer that today is reconstructed per-program by integrators and customers, at material cost and uneven assurance. This article examines the structural relationship between TSM as a deployed mesh waveform and the memory-native protocol primitive that composes above it.
Vendor and Product Reality
TrellisWare Technologies is a San Diego-based defense electronics firm whose TSM (Tactical Scalable MANET) waveform family powers tactical radios fielded across U.S. Special Operations Forces, the U.S. Marine Corps, allied tier-one units, and an increasing share of Army programs of record. The TW-950 Banshee handheld and the TW-875 Ocelot two-channel manpack are the most visible product lines, but TSM is also licensed onto third-party hardware, including airborne relays and ground-vehicle systems. The waveform itself — currently in its TSM-X generation — is engineered around scalable on-the-move mesh operation: hundreds of nodes can join, leave, and route across a self-healing topology while moving through urban canyons, mountainous terrain, or contested electromagnetic environments.
The engineering achievement is real and load-bearing. TSM's wave-relay-style flooding, coupled with its proprietary congestion management and link-quality adaptation, produces working mesh behavior at densities and motion profiles where legacy SRW, ANW2, and HF/VHF mesh protocols collapse. Field reports from Joint Special Operations Command exercises and coalition deployments consistently cite TSM as the waveform of choice when the operational concept assumes loss of fixed infrastructure, denial of GPS or LTE, and continuous adversary electronic-warfare pressure. The waveform's commercial position reflects this: TrellisWare licenses TSM into a hardware ecosystem (Silvus, L3Harris partner products, Persistent Systems comparators notwithstanding) that has effectively standardized the tactical-mesh layer for U.S. SOF and a widening ring of NATO and Five Eyes partners.
What TSM provides, with engineering rigor, is a routing and link-management substrate. What TSM does not provide — and was never designed to provide — is a payload-level authority model. The waveform forwards what its operators tell it to forward; it does not adjudicate whether the contents are governed, whether the originator is in scope, or whether the receiver's policy permits ingestion.
The Architectural Gap
Tactical mesh routing answers a transport question: given a topology, link conditions, and congestion state, what is the best next-hop or set of next-hops for this packet? The question is bounded, well-formed, and TSM answers it well. Authority resolution answers a different question: given a payload that has arrived, what governance constraints attach to it, who is the originating authority, what trust hierarchy validates that authority, and is the receiver's current operational state permitted to act on the payload? This second question is not a routing question. Its inputs — credentialing chains, jurisdictional scope, mission-package governance, cross-domain release rules — are orthogonal to link quality and topology.
The opacity of TSM's link-layer mesh authority compounds the gap. Because TSM is a proprietary waveform, the cryptographic identity and key-management story at the radio layer is a vendor-controlled construct. That construct is engineered for radio-to-radio admission to the mesh; it is not a payload-bearing identity model and it does not extend to applications, sensors, or downstream consumers riding on top of the mesh. A C2 message, an ISR observation, a logistics update, and a casualty report all traverse the same TSM mesh with the same link-layer treatment. None of them carry, by virtue of being on TSM, any portable, verifiable assertion of payload-level governance authority.
The consequence is that every program that fields TSM-equipped radios re-implements payload-level authority above the waveform — typically inside an application gateway, a tactical server, or a middleware layer specific to the mission system. The reconstructed authority model rarely composes cleanly across coalition partners, across mission packages, or across the lifetime of the deployed force. Each integration is bespoke, each is partial, and each represents engineering cost that recurs at every program start.
What the Memory-Native Protocol Primitive Provides
Adaptive Query's memory-native protocol primitive places governance and authority resolution inside the wire format of the payload itself, rather than at the transport. Each governed observation carries a portable, verifiable assertion of its originating authority, the governance scope under which it was emitted, and the admissibility constraints a receiver must evaluate before ingestion. The receiver runs a deterministic admissibility evaluator that produces a binary decision — admit or refuse — with a structured reason record. Because the evaluation is intrinsic to the payload, it is independent of which transport carried the payload to the receiver.
This independence is the architectural property that matters for TSM. A governed observation that arrives over a TSM mesh is evaluated by the same logic as one that arrives over LTE backhaul, a satellite uplink, or a sneakernet thumb drive. The evaluator does not need to trust the mesh; it trusts the cryptographic chain anchored in the payload. The mesh's job is to deliver bits as quickly and reliably as it can. The primitive's job is to ensure that what gets ingested into the receiver's operational memory is what the originating authority sanctioned, under the governance that authority was scoped to enforce.
The primitive also carries forward a property that link-layer authority cannot: lineage. When an admitted observation is re-emitted, derived, or summarized, the derivation chain remains attached. A downstream consumer — a coalition partner, an analytic cell, an after-action reviewer — can verify not only that an observation was admissible at first ingest, but that every transformation since has remained inside the governance envelope the originator scoped.
Composition Pathway With TSM
The composition pathway is clean precisely because the concerns are orthogonal. TSM continues to do what it does well: optimize routing, manage congestion, adapt to link quality, scale across hundreds of moving nodes in contested spectrum. The memory-native protocol rides as opaque payload across the TSM mesh. From TSM's perspective, governed observations are just bytes — TSM neither understands nor needs to understand the governance assertions inside them. From the primitive's perspective, TSM is a high-quality transport whose path-optimization properties affect latency and delivery reliability but not admissibility.
At the receiver — a TW-950 paired with a tactical end-user device, a vehicle-mounted situational-awareness server, or an airborne relay terminating into a fusion node — the admissibility evaluator runs against the inbound governed observation. Admitted observations enter the receiver's operational memory; refused observations are logged with their structured reason and held outside admissible state. The receiver's downstream processing (display, fusion, retransmission) operates only on admitted state. Re-emission across TSM, when authorized, carries the lineage chain forward.
Coalition and multi-vendor deployments, which today require painful per-partner gateway engineering, become structurally tractable. A coalition node that receives a U.S.-originated governed observation across TSM evaluates it under the published governance scope. If the partner is in scope, ingestion proceeds; if not, the refusal record is portable and auditable. The waveform did its job; the primitive did its job; the integration cost shrinks to configuration of governance scopes rather than reimplementation of trust plumbing.
Commercial and Licensing Implications
For TrellisWare and its hardware partners, the primitive is additive rather than competitive. TSM remains the licensed waveform; the primitive sits in the application and middleware layer above it. Programs that today commission custom authority middleware to wrap TSM-equipped fleets gain a standardized layer with portable governance semantics, reducing integration risk and shortening fielding timelines. Defense customers — particularly USSOCOM, the Marine Corps, and allied SOF — gain a path to coalition interoperability that does not require renegotiating link-layer trust at every operational seam.
For program offices and integrators, the licensing question is whether the primitive is acquired as a reference implementation, a licensed library, or as a patent-cleared specification that multiple vendors implement. Adaptive Query's positioning of the patent at the architectural layer — above any specific waveform — means TSM-equipped programs are not locked into a vendor stack to gain the governance properties the primitive provides. The same primitive composes equally well above Persistent Systems' Wave Relay, Silvus' StreamCaster mesh, or commercial LTE and Wi-Fi transports. Programs retain waveform optionality while gaining a stable governance contract.
The strategic posture is straightforward: TrellisWare optimized the routing problem. The remaining problem — payload-level authority resolution for governed observation admissibility across heterogeneous tactical fleets — is structurally separate, and it is the problem the memory-native protocol primitive was designed to solve. Composition, not competition, is the operative relationship.
