The Army Jailbroke Its Weapons to Force an AI Network

Army Secretary Dan Driscoll pulled Palantir, Anduril, Lockheed Martin and seven other firms into a May sprint to force U.S. weapons onto one AI-ready network.

The public name was Right to Integrate. The lasting move showed up on Aug. 24, when a signed order told program managers to stop buying closed interfaces.

The Army Called It a Right to Integrate

On May 5, 2026, Driscoll and industry leaders announced a Right to Integrate hackathon sprint, or R2I, so offensive weapons, defensive weapons, and Army business systems could share data. The first event was set for Fort Carson, Colorado. The companies signed a statement of support and ran the work at no cost to the Army.

The Army said weapons from different makers have long sat in competing silos, so units paid extra time and field engineers to stitch them together by hand. Those patches were custom jobs, and they often failed. Driscoll’s brief was blunt: the service could not keep fighting from a swivel chair.

We cannot fight from a swivel chair across multiple disaggregated systems anymore. We must integrate at the speed of digital information, and leverage the technologies of our time, like agentic artificial intelligence, drone swarms, and cyber weapons.

Dan Driscoll, Secretary of the Army, May 5, 2026 Army release

The named launch partners were Anduril, Boeing, General Dynamics, L3Harris, Leidos, Lockheed Martin, Northrop Grumman, Palantir, Perennial Autonomy, and RTX. They pledged engineers, scientists, and dozens of pieces of kit. Vice Chief of Staff Gen. Christopher LaNeve called the stitching problem wicked, and said R2I put industry and soldiers in the same room to cut the wait.

THE FIRMS AT THE MAY 5 TABLE

• Software layer: Palantir and Anduril arrived as the data and autonomy shops the Army already had in Next Generation Command and Control.
• Legacy primes: Lockheed Martin, RTX, Boeing, Northrop Grumman, and General Dynamics make the missiles, aircraft, vehicles, and sensors that still do not share a common pipe.
• Integrators and radios: L3Harris and Leidos brought networks and systems work; Perennial Autonomy sat with the newer drone shops.

Inside a week the Fort Carson work had another name, Operation Jailbreak. Driscoll told the Senate Armed Services Committee on May 12 that by day 10 of the exercise, 30 to 50 companies had come on board, and that thousands of pieces of equipment would be jailbroken so each one could send data out and take data in.

The sprint produced more than slogans. Vendors at Fort Carson described a build they said Army Chief Technology Officer Dr. Alex Miller dubbed “The Hunter-Killer”: two unmanned ground vehicles wired in days, with AZAK chassis, HavocAI driving software, an Allen Control Systems Bullfrog gun, Leonardo DRS radar, Picogrid tying the stack, and Anduril Lattice tasking the set. Gallatin AI, working with Palantir staff on site, said it took ten days from invite to a live demo in which a spoken contact report became a drone icon on Lattice and Palantir Gaia.

That is the specimen. A voice cue on one company’s radio showed up as a track on another company’s map, without a year of custom code. A later Jailbreak round in Tampa drew more vendors chasing the same pass/fail test: expose an interface, or sit out.

Ukraine’s Delta System Forced the Comparison

Driscoll did not invent the idea in a Pentagon briefing. He has said a trip to Germany, where he met Ukrainian troops, showed him an open setup that the U.S. Army still lacked. At the May 12 hearing he praised Kyiv’s Delta command-and-control system for its ability to “integrate every single drone, every sensor and every shooting platform into just one single network.”

The Army’s own May 5 release made the same point in plainer language. Ukraine, under existential pressure, required every entrant to expose an application programming interface, then folded drones, sensors, and shooters into one picture. The U.S. Army had started down that road with Next Generation Command and Control. R2I was the attempt to drag the rest of the arsenal onto the same path.

Once the pipes are open, Driscoll told senators, generative AI can sit on top and help with decisions, a pattern he said Ukrainians had used for the entire war. Sen. Jack Reed, the committee’s ranking Democrat, boiled the shift down to a line from his own service years: the old mantra was shoot, move, and communicate; now forces communicate so they can shoot and move.

The same war is already changing how the Army buys uncrewed systems, including Ukraine-hardened drone AI on dual tracks that keep a combat-tested software stack in U.S. programs. Delta is the networking lesson. The drones are the hardware lesson. Both punish a service that still needs a human to swivel between screens.

The Walled Gardens Inside Army Procurement

The closed designs were not an accident of old software. Driscoll told the committee that for decades the budget process “incentivized companies to protect their intellectual property at all costs,” and that the result was “walled gardens” in command and control. The Army paid for exquisite systems, then paid again for the engineers who made those systems nod at each other.

Miller, the Army’s CTO, has been the one saying the quiet part in public. Commercial software drove the cost of integration toward zero once interfaces were open, he said, while the department spent decades issuing standards and still living with “close and proprietary interfaces.” Openness, in his telling, stops being a slogan and becomes a ticket in.

We are setting conditions to where being open is industry’s ticket to participate. If you do not expose your interfaces and your documentation, you will not be able to join the ecosystem. This will be especially true for autonomous systems.

Dr. Alex Miller, U.S. Army chief technology officer, May 5, 2026 Army release

That is a different threat from “please add AI.” A prime can keep its secret sauce inside a module. It cannot keep the Army from plugging a third-party app into the socket, and it cannot charge a second time to unlock a format it chose to hide. Miller’s line about MOSA shifting “from a verb” to “a noun” is the tell: companies will treat open design as a product choice, not a briefing slide, because the alternative is exclusion from autonomy buys.

On June 16 in Paris, speaking at Eurosatory, Driscoll said the Army had reviewed about 100 systems in 30 days and still needed those systems to send and receive data through common digital interfaces. Air defense, he said, does not work if the gear cannot talk. The hackathon was already being used as proof that the review could move at that pace.

Anduril Leads the Common Data Layer

R2I sits on top of Next Generation Command and Control, the Army’s attempt to replace single-function command posts with one data picture for fires, logistics, airspace, and the rest. On June 22 the Army said it had locked a common data layer after ten months of live work with two divisions.

Anduril leads that baseline. Lattice is the edge piece. Palantir’s Foundry is the cloud piece. Raft handles registries, transforms, and federation. Anduril still runs the “full stack” at the 4th Infantry Division, which hammered the design at Ivy Mass in May across Fort Carson and Pinon Canyon, including cyber and electromagnetic attack. Lockheed Martin still runs the full stack at the 25th Infantry Division, which used Lightning Surge during Balikatan 2026 to pass sensors, fires, and airspace through one picture from Hawaii, the continental United States, and the Philippines.

WHO OWNS WHICH LAYER

Joseph Welch, the portfolio acquisition executive for command and control, said vendor teams had already shown they could converge on that baseline and set up a fast scale. Brig. Gen. Shane Taylor, who runs Command and Control Information Network, kept pushing industry to self-team rather than wait for a single prime to own the pipe.

On July 29, after Project Convergence Capstone 6 at Fort Irwin, the Army said NGC2 was ready to scale. The 10-month prototype phase was over. Delivery would start with I Corps headquarters later in 2026. Driscoll, still in the job, said the side that can sense a target, process the data, and put a round on it first is the side that wins, and that the bigger national-security risk was moving too slowly.

A shared layer has a cost. An Army assessment of an early NGC2 prototype in 2025 called the design very high risk; Palantir said no holes were found in its own platform. Opening every socket also concentrates the blast radius if that socket is wrong. The June baseline did not retire that fight. It picked a vendor stack and kept walking.

What the August Directive Bans

The standing order, not the weekend demo, is what changes a contract. Army Directive 2026-21 on modular interfaces, signed by Driscoll and effective Aug. 24, tells program managers to put open-system design, open interfaces, and full documentation into every new start and every legacy upgrade, no matter the dollar value or the buying path. It covers the regular Army, the National Guard, and the Reserve.

The memo points to combat reporting and to a validation sprint during Operation Jailbreak as evidence that open architectures and APIs let Army systems share a picture. Then it lists duties that read like a procurement lawyer’s version of Miller’s ticket-to-play line.

WHAT PROGRAM MANAGERS NOW OWE

• Open design: Software and systems must use modular design and standard interfaces so other Army gear and approved third-party apps can plug in.
• Exposed APIs: Managers must keep secure, two-way APIs or cousins such as gRPC, MQTT, WebSockets, GraphQL, and Model Context Protocol, with Army rights to features, functions, and data.
• No fake walls: Contractors may not use proprietary data formats or technical limits that block integration, and they may not kill an API without a better replacement at no extra cost.
• Paper and rights: Contracts must deliver documented telemetry, data streams, and control functions, plus the data rights needed to sustain the gear.
• Cyber rules: Every modular interface has to meet Army and Department of War security policy.

The assistant secretary for acquisition, logistics and technology has 90 days from Aug. 24 to issue implementing guidance, which lands on Nov. 22, 2026, and 120 days to report status, which lands on Dec. 22. The same office has two years to fold the rules into Army Regulation 70-1. Until that rewrite publishes, the directive stays in force.

Title 10 already told major programs to use a modular open systems approach. This order pushes the same demand down to small upgrades and names the tricks, proprietary formats, dead APIs, missing docs, that primes have used to keep a follow-on paycheck. Jailbreak showed a path. The directive makes refusal a contract problem.

Eight TITAN Stations Move Into Production

The money followed the policy by a week. On Aug. 31 the Army’s intelligence and spectrum office moved the Tactical Intelligence Targeting Access Node into production with two delivery orders totaling $192 million. Palantir, the production lead, received $127 million. Anduril received a 65 million delivery order for TITAN hardware and shelter integration, issued through the Army’s enterprise agreement with the company.

The orders buy eight initial production systems, four TITAN Advanced and four TITAN Basic, for delivery over 18 months from Aug. 31. Those eight join nine prototype units the Army already holds for operational use. Palantir’s production team includes L3Harris, Sierra Nevada, Strategic Technology Consulting, and World Wide Technology. Anduril builds the rugged vehicle-mounted gear in Costa Mesa, California, and integrates power, thermal, control, and operator subsystems.

TITAN PRODUCTION SNAPSHOT

• Palantir order: $127 million to lead production and integration of the eight stations.
• Anduril order: $65 million for hardware, mission shelters, and vehicle integration.
• Mix: Four advanced units with more processing, four basic units built for a lighter truck.
• Next buy: The Army said another production order is expected in fiscal 2027.

TITAN is the Army’s AI-enabled, movable intelligence ground station. It is meant to pull satellite, air, and ground feeds, then turn that pile into targeting data for long-range fires without parking a fixed processing barn in range of enemy guns. In other words, it is one of the boxes that only works if the sensors and shooters around it actually publish data. A jailbroken radio with no TITAN is a stream into nowhere. A TITAN truck with walled sensors is a shed full of silent racks.

The split on the order is the industrial tell. Palantir owns the software and the prime role. Anduril owns the metal that has to survive dust, heat, and a bad road. Lockheed and RTX are not on this production sheet. They are still inside NGC2 at the 25th Infantry Division, and they were at the May 5 table. The new work, the data layer and the targeting node, is going to the firms that already treat the interface as the product.

Driscoll Resigned After Signing the Order

Driscoll submitted his resignation on Aug. 31, the same date as the TITAN orders, after about 18 months as the 26th secretary. He had been confirmed in February 2025. The White House announced the departure; President Trump then named Adam Telle, the assistant secretary overseeing civil works, as acting secretary in early September. Driscoll’s public line of work did not stop. In Kyiv on Sept. 12, in his first remarks after leaving, he again said Ukraine’s Delta system still beats what the U.S. military fields, and that large armies have not matched that speed.

FROM SPRINT TO STANDING ORDER

1. May 5, 2026: Driscoll and ten firms announce the Right to Integrate sprint; Fort Carson is named as the first site, at no cost to the Army.
2. May 12, 2026: He tells the Senate that Operation Jailbreak is underway, that 30 to 50 companies are in by day 10, and that thousands of pieces of gear will be opened.
3. June 22, 2026: The Army names Anduril to lead the NGC2 common data layer, with Palantir and Raft as partners, after ten months with the 4th and 25th Infantry Divisions.
4. July 29, 2026: After Project Convergence Capstone 6, the Army says NGC2 is ready to scale, starting with I Corps headquarters later in 2026.
5. Aug. 24, 2026: Army Directive 2026-21 takes effect and bans proprietary formats and closed APIs on new work and upgrades.
6. Aug. 31, 2026: TITAN production orders hit $192 million, and Driscoll tenders his resignation the same day.

The sequence is the argument. A hackathon can be walked back when the tents come down. A directive that lasts until the acquisition regulation is rewritten, a clock of up to two years, is harder to shrug off, even with an acting secretary and a vacant uniformed chief. The primes still build the missiles and the airframes. They now have to publish the sockets, or they lose the next autonomy buy to a shop that will.

I Corps is supposed to take the first operational NGC2 kit later in 2026. The implementing guidance on those sockets is due Nov. 22. Until then the Army is fielding a network whose rulebook is a May sprint, a June vendor pick, and an August memo signed by a secretary who is already gone.