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 and allied units, with additional adoption across conventional-force programs. The TW-950 TSM Shadow handheld and the TW-875 TSM Ghost relay radio are among the most visible product lines, and TrellisWare also licenses TSM for integration onto third-party hardware. The waveform itself, currently in its TSM-X generation, is engineered around scalable on-the-move mesh operation: many 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 scalable relay behavior, coupled with congestion management and link-quality adaptation, sustains working mesh operation at node densities and motion profiles that stress older narrowband tactical waveforms. TSM is frequently selected for operational concepts that assume loss of fixed infrastructure, denial of GPS or LTE backhaul, and continuous adversary electronic-warfare pressure. TrellisWare's licensing model, which places TSM on multiple radio platforms rather than a single closed appliance, has contributed to its wide adoption across U.S. SOF and allied partners. TrellisWare competes in this space alongside other tactical-mesh vendors such as Persistent Systems and Silvus Technologies, each with distinct waveforms; the comparison in this article is scoped to TSM specifically and to the architectural layer above it, not to the relative merits of those waveforms.

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

The memory-native protocol places governance and authority resolution inside the wire format of the payload itself, rather than at the transport. As disclosed in 19/366,760, the unit of transmission is not a stateless packet but an agent: a cryptographically signed data object comprising a unique identifier, a payload, a transport header, a memory field, and a digital signature. The memory field is an append-only record carrying verifiable lineage, access logs, and policy references, and it is these embedded elements, not an external session or gateway, that govern what a receiving node may do with the agent.

A governed observation is therefore an agent whose memory field carries a portable, verifiable assertion of its originating authority, the governance scope under which it was emitted, and the policy references a receiver must evaluate before ingestion. On receipt, a node re-serializes the agent's canonical fields and validates the signature against the sender's public key; if validation fails, the agent is discarded and the rejection is logged locally. On success, the node parses the transport header and memory field and evaluates the referenced policy agent, which encodes access constraints, mutation eligibility, and role rules, to determine routing and mutation eligibility. The outcome is deterministic and produces a structured trace: admitted, or refused with a recorded reason, or held under a quarantine flag for manual review. Because the evaluation is intrinsic to the agent, it is independent of which transport carried it to the receiver.

A skilled implementer can build this. The agent is a canonical serialization signed by the originating node; signature verification is standard public-key validation over the UID, payload, memory field, and transport header; policy references resolve either as embedded canonical identifiers or by alias against a zone-local table; and admissibility is the deterministic evaluation of those policy references and access-log entries by the receiving node's protocol stack. Embodiments range from stateless edge nodes that run only a routing layer and a minimal memory interpreter, through memory-aware nodes that maintain a persistent trust graph, to full-stack nodes that additionally run indexing and adaptive-consensus layers; the substrate is disclosed as operable over TCP/IP, HTTP, WebRTC, mesh relay, and delay-tolerant networking without modification to the agent.

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 memory-native agent also carries forward a property that link-layer authority cannot: lineage. The memory field records mutation lineage as a sequential, hash-chained, per-node-signed record of the structural changes an agent has undergone, including prior governing zones and the policy references under which each change was accepted. When an admitted observation is re-emitted, derived, or summarized, that 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 is derivable from a trusted origin and remained inside the governance scope the originator set.

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 receiving node's protocol stack verifies the agent's signature and evaluates its policy references against the inbound governed observation. Admitted observations enter the node's operational state; refused observations are logged with their structured reason and held outside admissible state, or quarantined for review. Downstream processing such as display, fusion, or retransmission operates only on admitted state, and each node appends a trace entry recording the decision. 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 was designed to solve. Composition, not competition, is the operative relationship.

Disclosure Scope

The architecture described here for OUR side, the memory-bearing agent, the signed append-only memory field carrying verifiable lineage, access logs, and policy references, the deterministic routing, indexing, and consensus layers, and the transport-independent evaluation of admissibility, is disclosed in United States Patent Application 19/366,760, "Cognition-Compatible Network Substrate and Memory-Native Protocol Stack." That filing is the authoritative source for the mechanisms attributed to the memory-native protocol in this article, and this article is intended as a dated public description of that disclosure.

All statements about TrellisWare Technologies, the TSM (Tactical Scalable MANET) waveform, TSM-X, the TW-950 TSM Shadow, the TW-875 TSM Ghost, and any other named product, vendor, or program are external context describing third-party technology at the architecture level. They are not claims of the filing, do not describe features of the memory-native protocol, and are provided only to situate the disclosed architecture relative to a widely fielded tactical mesh transport. TSM is a capable, real-world waveform; the comparison is scoped to the specific architectural axis of payload-level authority resolution, which is orthogonal to the routing and link-management problems TSM addresses, and is not a claim about TSM's fitness for its intended purpose.