The pitch is always the same
Lattice connects every sensor on the battlefield into one real-time picture. Maven fuses satellite imagery, drone feeds, and intelligence databases into a single analysis platform. The slide decks are compelling. The demos are polished. The contracts are enormous.
The pitch to command: total awareness. Camera feeds, operator positions, drone tracks, detections, decisions, all flowing up to a screen in a JOC thousands of miles away. The pitch to Congress: accountability, with every action recorded and every AI recommendation auditable.
Nobody talks about the pitch to the operator. There is not one. The operator is the data source, not the customer.
What top-down platforms actually build
Lattice and Maven are enterprise platforms. They are designed to aggregate data from the edge and present it to command. The data flows up. The decisions flow down. The architecture assumes persistent connectivity to cloud infrastructure, theater-level servers, or at minimum a reliable SATCOM link.
This architecture works for command. A general in Tampa watching a Reaper feed over Yemen has exactly the setup these platforms were built for: high bandwidth, stable connectivity, a room full of analysts, and time to deliberate. Maven's $1.3B contract serves 20,000+ users. The vast majority of those users are analysts, not operators.
For the team in the field, these platforms create a different dynamic. Every sensor feed, camera frame, biometric data point, and GPS track becomes a record that someone in a different timezone can review and second-guess after the fact. Operators know this. They have always known this.
This is the documented, intentional design of enterprise C2 platforms: total data capture, full audit trail, persistent cloud storage. It is a feature, not a bug. And it is why operators distrust the software they are told to carry.
The trust problem is real and it is costing capability
A study by the Netherlands Armed Forces on personal health monitoring found that operators accepted wearable data collection when it was framed as a tool for their own safety and managed by their medic. Acceptance dropped sharply when the same data was accessible to command or external review. Same capability, different trust architecture, different outcome.
This pattern repeats across every domain. Operators use ATAK because they control it. They resist platforms that pipe their data to a JOC because they do not control where it goes or who reviews it. The result is that units carry devices they do not use, run software they do not trust, and make decisions with less information than the technology could provide, because the information architecture was built for command oversight, not operator empowerment.
The DoD AI Strategy memo calls for AI that operates 'on-board, in real time, and often without any sort of connectivity.' The operational argument for edge AI is bandwidth and latency. The trust argument is stronger: if the AI runs on the operator's device and the data stays with the team, the operator will actually use it.
Ecosystem lock-in is the business model
Lattice requires Anduril hardware. You cannot buy Lattice software and run it on a laptop. You buy the sensor, the relay, the edge compute box, and the command node. The entire stack is proprietary. Switching cost is total. Once you are in the Lattice ecosystem, every new sensor, every new drone, every new capability comes from Anduril or does not integrate at all.
Palantir's pricing at $141K per core per year is not a software license. It is a commitment to Palantir's data architecture. Your data lives in Palantir's ontology. Your analysts learn Palantir's tools. Your workflows depend on Palantir's platform. Moving off Palantir means rebuilding every workflow from scratch. This is intentional.
Both platforms are also fragile. Lattice 'fallen far short of service members' expectations' in Navy exercises according to November 2025 reporting. The Pentagon banned Anthropic from Maven with a 180-day removal deadline, forcing Palantir to rip out its core AI engine. When your mission capability depends on one vendor's cloud infrastructure and that vendor's AI partner gets banned by the Pentagon, your mission capability disappears with it.
The operators at the edge do not feel these decisions as policy debates. They feel them as tools that stop working. The video feed goes dark. The analysis tab returns an error. The AI that was identifying threats yesterday is offline today because someone in Washington had a contract dispute. The operator's trust in the technology drops to zero. It does not come back.
What operators actually want
Operators want mission technology that works when everything else is broken. No comms, no cloud, no SATCOM, no cell signal. If the tool dies when the link drops, it is dead weight they carried for nothing. It also has to help them do their job without creating a liability: every frame of video and GPS breadcrumb is a potential exhibit in a review they did not ask for. And they want to control what gets shared, when, and with whom.
That is not paranoia. It is learned behavior from twenty years of operations where helmet camera footage, radio transcripts, and engagement data were reviewed by people who were not in the fight and did not understand the context. Decisions made in seconds got second-guessed by people who have never been in those conditions.
The technology that earns operator trust belongs to the team. ATAK works because the operator controls it. Radios work because comms are ephemeral. A paper map does not record who looked at it. The software layer on top of all this needs to follow the same principle: useful to the team, controlled by the team, disposable by the team.
A different architecture
The premise is simple: the mission belongs to the team running it. AI, data, models, detections, and decisions stay on the team's hardware by default. Nothing phones home or streams to a cloud, and nothing persists after the mission unless the team decides it should.
Each mission is its own loadout. Models, reference data, and AI prompts are packaged for the specific operation. The team runs the mission on their devices. When the op is over, the loadout wipes clean. What the team chooses to keep, a high-level summary, selected evidence, an AAR, gets packaged and exported on the team's terms. What they choose to destroy is destroyed.
Sync with Lattice, Palantir, or command is an option, not a requirement. EdgeLance can publish summaries, entity tracks, or selected intelligence upward when the team and their chain of command agree it should happen. The gate is in the team's hands, not in a cloud platform's always-on pipeline. Command gets the picture they need. Operators do not become a surveillance feed.
This is not anti-command. Command needs the mission picture. But the mission picture should be what the team produces and chooses to share, not a raw firehose of every sensor frame and GPS breadcrumb captured by a platform designed for total data collection. The medic's wearable data should inform the medic and the team lead, not populate a dashboard in a JOC. The drone feed should help the team make decisions, not become a courtroom exhibit.
The market gap is trust
Lattice and Maven are not going away. They serve the enterprise layer and they do it well enough for the customers they were designed for. The gap is not at the theater level. The gap is at the team level, where operators need AI, sensors, mesh, and mission tools that they actually trust enough to use.
The $70 billion DoD budget for drones and AI in 2027 is not going to buy trust. Trust comes from architecture. If the architecture puts the team in control of their own data, their own AI, and their own mission record, operators will use it. If the architecture pipes everything to a cloud by default and calls it 'accountability,' operators will find workarounds or ignore it entirely.
That is what EdgeLance was designed around. Local AI on the team's hardware, mesh that works when nothing else does, ATAK integration on the map they already trust, and a mission lifecycle that starts and ends with the team's decision about what to keep, share, or destroy.