Vendor and Product Reality
Anduril's Lattice is the company's software platform for autonomy and command-and-control, and Lattice Mesh is its data-fabric layer: a way for heterogeneous defense platforms, drones, sensors, ground vehicles, and command nodes from multiple vendors, to share data with one another in a decentralized way, without routing everything through a central server. It is built precisely for the environments where conventional networking fails: contested electromagnetic conditions, intermittent connectivity, and multi-vendor coalitions where no single cloud is reachable or trusted by everyone. Lattice Mesh is the most visible commercial expression of an idea this body of work also holds: that autonomy at the edge needs a decentralized data fabric, not a hub. Its prominence proves the market. Mesh data sharing for autonomy is now a category, and a serious one.
The agreement is genuine and worth stating before the divergence. Both Lattice Mesh and the memory-native protocol reject the central server as the place where coordination happens, and both target the contested, multi-vendor, partition-prone conditions of real operations. The difference is what a packet is permitted to be.
The Architectural Choice: Packets as Payload
In a mesh built on conventional principles, however decentralized, the data unit is payload and the governance lives in the nodes. Routing decisions, access-control rules, and trust state are held in node-resident configuration, and a packet is the thing moved between nodes that hold that configuration. This works well when the nodes are consistently configured and reachable, and it is the architecture that mature mesh fabrics optimize. But it locates authority in the node rather than in the data, which means a packet arriving at a node is governed by whatever that node currently believes, and the consistency of those beliefs across a contested, multi-vendor mesh is exactly what partition and adversary conditions disrupt. The packet carries data; it does not carry the rules for its own handling.
What the Memory-Native Primitive Provides
The memory-native protocol makes the data unit a self-governing operand. Every message carries a governed envelope: an authority-taxonomy field naming the credentialing authority and the scope of the asserted permission; a dynamic-device-hash continuity field anchoring the originating device's credential history without a real-time revocation fetch; a hop-history relay field recording the chain of nodes that handled the message under their own credentials; and a store-and-forward propagation field that preserves freshness, scope, and authority across partition events. A governance class field at a fixed wire offset lets any node locate and act on the message's handling regime before it parses the payload, and an opaque relay is required only to preserve that field bit-for-bit. Routing scope, mutation policy, trust window, and lineage travel inside the unit, so a receiving node evaluates a message against the authority the originator declared rather than against the node's own possibly-stale configuration, and it does so locally, without a round-trip. The nodes become generic executors of governance the packet carries.
Complementary at the Problem, Divergent at the Wire
Lattice Mesh and the memory-native protocol are fighting the same battle under different doctrine. At the level of the problem, decentralized data sharing for autonomy in contested, multi-vendor environments, they are aligned, and a platform like Lattice is exactly the kind of system that could carry a governed envelope as opaque payload over its existing fabric. At the level of wire-architecture they diverge: node-resident governance over packets-as-payload, versus carried governance in packets-as-operands. The envelope rides above any transport, so the divergence is composable rather than exclusive: a mesh optimized for decentralized delivery can transport self-governing data units and gain per-message carried authority without changing its routing. No relationship, endorsement, or infringement is asserted; the comparison is architectural.
Disclosure Scope
The memory-native protocol, in which the data unit carries a governed envelope encoding authority, scope, device-hash continuity, hop history, and store-and-forward propagation, and in which nodes evaluate carried governance locally without a central authority, is disclosed in the protocol filing (U.S. Application No. 19/366,760, published as US 2026/0052096 A1). This article compares that disclosed mechanism with Anduril's publicly described Lattice Mesh data fabric and positions carried, packet-resident governance as complementary to a decentralized delivery fabric. References to Anduril and Lattice are to public materials and are used for comparison only.
