Enterprise C2 and tactical edge AI solve different problems
Anduril's Lattice and platforms like Palantir Maven give command a real-time operational picture across domains. They fuse intelligence from national assets, theater sensors, and network-connected platforms into a unified view. The Army's $20B Lattice contract validated the enterprise C2 model at scale.
But enterprise C2 platforms are designed for a specific operating context: reliable connectivity to cloud or regional infrastructure, dedicated compute, trained support staff, and program-of-record integration. The operator at the tactical edge often has none of these. The team in a building with one WiFi link, three iPhones, and four cameras needs AI that works right now, not AI that works when the SATCOM link recovers.
These are complementary layers in the same stack. The enterprise layer needs curated intelligence from the edge, and the edge layer needs enterprise context when available. The question is how they work together, not which one wins.
The bridge architecture: selective reachback by design
EdgeLance publishes to Lattice via a bridge that translates local mission intelligence into Lattice-compatible entity objects. The bridge is not a firehose. It implements selective reachback: the operator or team lead decides what intelligence flows upward to the enterprise layer and when.
A detection that the team is still evaluating stays local. A confirmed threat assessment with evidence gets promoted to Lattice for command visibility. A contact track that the team has cleared stays in the mission record and can be purged with the mission. The team is a curated intelligence producer, not a passive data source.
This architectural decision is what makes the integration work. Pipe everything to Lattice by default and it becomes another surveillance layer that operators reject. Never connect to Lattice and you are invisible to command and unsupportable in a program of record. Selective reachback threads the needle.
What each layer provides
**Lattice at echelon provides:** multi-domain operational picture, cross-unit deconfliction, battlespace management, fires coordination, logistics visibility, theater-level AI fusion, and program-of-record accreditation. These are enterprise requirements that a tactical edge tool should not try to replicate.
**EdgeLance at the edge provides:** local AI inference on consumer hardware, ATAK/CoT integration for the operator's existing map, mesh networking across seven link types with store-and-forward, evidence coupling from detection to source data, role-specific mission views, and ephemeral mission lifecycle with cryptographic wipe. Enterprise C2 platforms were not designed for these requirements.
**The bridge provides:** entity sync from EdgeLance to Lattice in Lattice-compatible format, controlled by the team. Lattice context flows downward when available. CoT markers flow to ATAK regardless of Lattice connectivity. The system degrades gracefully: if the bridge is offline, EdgeLance continues operating independently and queues promotions for later sync.
Why this matters for the JADC2 vision
The Joint All-Domain Command and Control vision assumes seamless information flow from sensor to shooter across all domains. In practice, that flow breaks at the tactical edge where connectivity is contested and nodes are heterogeneous. Enterprise C2 handles the echelon-to-echelon flow well. The sensor-to-team flow at the tactical edge is the gap.
NATO's Federated Mission Networking concept acknowledges that no single system will serve all participants. Interoperability between systems, rather than uniformity, is the path to joint capability. The CoT publishing, Lattice bridge, and mesh protocol make EdgeLance one node in a federated architecture, not a replacement for it.
A SOCOM team using EdgeLance at the edge and Lattice at the JOC creates a complete information flow: local sensors feed local AI, local AI produces curated intelligence, curated intelligence syncs to Lattice, and Lattice provides the joint picture that command needs. No single system handles all of that today. The combination does.
The integration model the Department should standardize
The defense acquisition community has spent years debating whether to standardize on one platform or allow competition. The better path is to standardize on interoperability protocols and let operators choose the tools that work for their mission.
EdgeLance speaks CoT for tactical interop and produces Lattice-compatible entity objects for enterprise interop. Operators keep ATAK. Command keeps Lattice. The layer between them ensures the intelligence flowing upward is curated, evidence-coupled, and operator-controlled.
Standardize the bridge, not the tool. Operators choose what works at the edge, command chooses what works at echelon, and protocols that both sides trust connect them. Lattice and EdgeLance together cover the full stack from satellite to soldier.