Anduril Bolt and Lattice-Connected Drones

Vendor and Product Reality

Anduril Industries fields one of the most production-mature autonomous-systems portfolios in the United States defense industrial base. The Bolt and Bolt-M small UAS — selected under the U.S. Marine Corps Organic Precision Fires program and contracted at scale under the Department of Defense Replicator initiative — are vertical-takeoff loitering munitions controlled through a tablet-grade operator interface. ALTIUS, acquired through the Area-I acquisition, fields tube- and air-launched variants used for ISR and effects. Roadrunner is a recoverable, jet-powered, vertically-launched interceptor optimized against Group 2 and Group 3 threats. Fury is a high-performance autonomous fighter prototype now central to the U.S. Air Force Collaborative Combat Aircraft program.

Underneath those airframes sits Lattice OS — Anduril's command-and-control mesh that ingests sensor data, fuses tracks, and exposes mission tasking to operators. Lattice is the company's architectural moat: it is the surface through which heterogeneous Anduril and third-party assets present themselves to a human commander, and through which tasking flows back down to autonomy stacks. The Replicator program, in turn, has shifted Anduril's product surface from individual platforms to all-domain attritable mass at deployment scales of thousands of units, with corresponding pressure on tasking, deconfliction, and authorization infrastructure.

Architectural Gap

Lattice OS is a strong tasking and fusion plane, but its operator-intent representation is procedural: an operator selects a target, designates a corridor, or authorizes engagement, and that authorization is bound to a session, a unit, and a platform-specific autonomy stack. There is no portable, declarative, graduated-fidelity intent object that survives handoff between Bolt swarms, ALTIUS effects, Roadrunner interceptors, and Fury wingmen — let alone between Anduril systems and coalition or joint-force assets running different autonomy stacks.

This matters acutely for Lethal Autonomous Weapon System (LAWS) governance under DoD Directive 3000.09 and emerging coalition norms. The directive requires that commanders and operators retain "appropriate levels of human judgment" over the use of force. As fleet sizes grow into the Replicator regime — hundreds to thousands of attritable units per operation — per-engagement procedural authorization does not scale, and yet fully delegated autonomy is not admissible. The architectural primitive missing from Lattice is a way to express intent at graduated fidelity: from coarse rules of engagement, to mission-level corridors, to per-target authorization, with each tier carrying its own admissibility evidence and each tier composable with the others. That primitive is also what makes multi-fleet intent fusion possible: when ALTIUS and Bolt elements operate the same engagement, the intent surface must reconcile into a single admissible record rather than two procedural sessions.

What the Operator-Intent Primitive Provides

The Adaptive Query operator-intent primitive supplies the missing layer as a portable architectural element. It encodes commander and operator intent as a credentialed declaration with graduated fidelity tiers: standing authorities, mission envelopes, target-class permissions, and per-engagement authorizations are each first-class objects, each cryptographically bound to the issuing authority, and each composable into a single admissibility record at evaluation time.

Two architectural properties are decisive. First, multi-fleet intent fusion: a single declared intent can govern simultaneous tasking across heterogeneous autonomous fleets — Bolt-M, ALTIUS, Roadrunner, Fury, and non-Anduril coalition assets — because the intent object is platform-independent and the autonomy stacks consume it as a constraint surface rather than as procedural commands. Second, graduated-fidelity admissibility: the system records, for any given action, the precise intent tier under which it was admissible, producing an evidence trail that maps cleanly onto DoDD 3000.09 and analogous coalition LAWS frameworks. The primitive does not replace Lattice; it composes underneath Lattice as the substrate Lattice's tasking surface evaluates against.

Composition Pathway

Composition with Lattice OS is structural rather than disruptive. Lattice continues to perform sensor fusion, track management, and operator UX. The operator-intent substrate sits as a sibling plane: when a Lattice operator issues a tasking, that tasking is materialized as a graduated-fidelity intent object signed by the operator's credentials and propagated to relevant autonomy stacks. Bolt, ALTIUS, Roadrunner, and Fury onboard autonomy then evaluate proposed actions against the intent object and emit admissibility evidence back through Lattice.

For Replicator-scale operations, the composition path matters most at the swarm boundary: where one operator authorizes a thousand-unit Bolt-M deployment, the intent object expresses corridor, target class, time window, and engagement authorities once, and each unit's autonomy stack consumes it locally. For collaborative combat aircraft like Fury, the intent object becomes the shared admissibility surface between the manned lead and the autonomous wingmen. For coalition operations, the primitive's platform-independence allows non-Anduril systems to participate in the same admissibility regime without exposing autonomy internals.

Commercial Implication

Anduril's commercial position is increasingly defined by program-of-record awards that depend on demonstrable LAWS-admissibility at scale. Replicator, CCA, and the OPF programs all assume that fielded autonomous systems can produce auditable evidence of human judgment. A vendor that ships graduated-fidelity intent as an architectural feature is positioned to win incremental scope on those programs and to defend against entrants who frame autonomy governance as a software-update problem rather than as an architectural one. For Anduril, adopting the operator-intent primitive underneath Lattice is the lowest-friction path to that posture: it preserves Lattice's UX moat while resolving the structural gap that procurement officials and policy staff are increasingly asking about.

The competitive lens is equally direct. Shield AI, Skydio, and traditional primes are converging on autonomy stacks. The differentiator is no longer airframe or autonomy — it is admissibility infrastructure. A graduated-fidelity intent substrate is the kind of architectural feature that, once present in one vendor's stack, becomes a procurement requirement.

Licensing Implication

The operator-intent primitive is offered as a licensable architectural element rather than as a product replacement. For Anduril, the licensing pathway is composition-license: rights to embed the primitive underneath Lattice and to expose graduated-fidelity intent as a Lattice-native capability across Bolt, ALTIUS, Roadrunner, and Fury. The license carries no claim on Lattice's tasking surface, autonomy stacks, or sensor fusion; it covers the intent-object architecture, the multi-fleet fusion semantics, and the admissibility-evidence pipeline. For coalition and allied-vendor participation, sub-licensing terms allow third-party autonomy stacks to consume Anduril-issued intent objects without re-licensing, which is the structural property that makes coalition LAWS-admissibility tractable.