Army leadership turned long-running themes into structure, policy, and funding. Here is what we heard, and what we think it means.
The AUSA Annual Meeting in Washington D.C. is usually a week of platforms and promises. This year felt different. Across the keynote, autonomy panels, Pacific and Western Hemisphere sessions, and the show floor, one message kept repeating: the Army intends to change how it buys, builds and fields technology, not just what.
We spent the week listening and reading the coverage. Below are the five shifts we think matter most, why we believe they are durable, and what we are watching next.
"The most unambiguous line of the week came from Acting Secretary Adam Telle: everything the Army buys will have open architecture, and it is "non-negotiable."
Shift 1: Open By Default
Adam Telle was blunt about the past. Systems were proprietary and not interoperable, with data locked behind "proprietary moats" and a toll to pay every time the Army crossed one. His answer is a mandate for open architecture across new buys, plus Operation Jailbreak to connect legacy systems without spending decades and millions of dollars.
The same logic runs through NGC2. The Army is building an Army-owned data layer with open architecture for industry software apps, and it just issued just under $100 million in application awards to nine companies. Core software is now being bought on top of that open foundation.
Our view: This is a real change in who holds leverage. When the government owns the data layer and demands open interfaces, value moves to suppliers who interoperate cleanly and away from those who rely on lock-in. The open question is enforcement. A mandate only matters once it shows up in requirements, evaluation criteria, and contract language.
Shift 2: Problems Over Programs
Telle argued that the Army built an incomprehensible number of platforms, gave each its own office, and over time made sustaining the program the purpose. The new Portfolio Acquisition Executives are organized around operational problems instead. He went further: if someone says the Army's biggest acquisition program is a tank, a helicopter, or a missile system, they are wrong. The biggest program is the partnership with commercial industry.
The supporting moves were concrete:
-
FUZE, described as a "Shark Tank for the Army," to find and fund ideas faster.
-
Open booking of test range time for new entrants.
-
The Infantry Squad Vehicle as the template for buying commercial excellence instead of building to mil-spec from scratch.
-
A 2027 "Manufacturing Rodeo" to stress-test manufacturability and supply chains for major systems.
Our view: speed is now a requirement alongside performance. Suppliers will be judged on how quickly capability can be integrated, updated, and re-fielded, not only on how well it works on day one.
Shift 3: Autonomy Gets a Command Structure
Autonomy moved from slideware to organization. The Army is establishing the Futures and Autonomous Systems Command (FASCOM), will integrate autonomy into at least six formation areas (including aviation, armor, fires, and sustainment), and will designate a portfolio acquisition executive for autonomy, with fielding prioritized no later than fiscal year 2028. At the department level, Secretary Hegseth discussed standing up the Autonomous Warfare Command with service-like authority, and each service is expected to stand up a component command.
Hegseth offered few specifics on how this will be funded or run. But the direction is clear, and the Army's Chief Technology Officer was equally clear that "appropriate levels of human judgment" remain part of the design.
Our view: The interesting problem is not building one autonomous system; it is running autonomy safely across many platforms, many suppliers, and many update cycles. That is an architecture challenge before it is an algorithm challenge.
Shift 4: Cheap Mass and Counter-UAS
The show floor was crowded with low-cost interceptors and loitering munitions: Anduril's Steelfin positioned as a cheaper option to PAC-3, Lockheed's PAC-3 Edge, CHAOS Industries' VESPID, Heaviside's Tyr, and GDLS's PERCH 2.0 prototypes headed to the 1st Cavalry Division. Telle called for large volumes of low-cost interceptors to defeat future swarms, and for organic drone manufacturing capacity and supply chain. Reporting on Hegseth's remarks cited a proposed budget with tens of billions earmarked for drone dominance and counter-drone technology; those are proposals, not appropriations.
The operational pull is already real. JIATF-401 is running layered counter-UAS at the Southern Border and takes orders through a dedicated site, and Gen. Ryan said small units must master both UAS and C-UAS for combat.
Our view: Mass changes the engineering constraints. Systems must be cheap, producible, and upgradable, which pushes toward commercial hardware, modular software and standard interfaces.
Shift 5: Surviving and Sustaining In Contested Space
The Pacific panels were a reminder that the hardest requirements are about endurance. Lessons from the Iran conflict reinforced constantly moving emitters ("shoot, scoot, communicate"), electronic warfare and camouflage, and maneuver for survivability. USFK is moving away from large static command posts toward distributed exercises. Leaders called for regional sustainment hubs in Korea and Japan so damaged platforms can be repaired locally, and for network interoperability across the Joint Force and allies, a "layered-mesh kill-web." Industry also pressed to drop the NOFORN label to enable more data-sharing with allies.
Our view: Distributed, allied, and contested operations mean software must run securely at the edge, tolerate disconnection, and share data across trust boundaries without exposing everything.
The Shifts at a Glance
| Shift | What Leaders Said or Did | What it Demands of Technology |
| Open by Default | Open architecture "non-negotiable"; NGC2 data layer; Operation Jailbreak | Standards-based interfaces, interoperable software, no proprietary lock-in |
| Problems Over Programs | Problem-based PAEs; FUZE; Manufacturing Rodeo; commercial buys | Fast integration and update cycles; producible, commercial-ready designs |
| Autonomy Institutionalized | FASCOM; six formation areas; autonomy PAE; FY2028 target | Safe, governable autonomy across many platforms and suppliers |
| Cheap Mass | Low-cost interceptors; organic drone production; C-UAS at the border | Low-cost, modular, upgradable systems at volume |
| Contested and Distributed | Distributed exercises; sustainment hubs; allied interoperability | Secure edge computing; resilience; controlled data sharing |
What We Are Watching Next
-
Enforcement of "Open": Does the mandate appear in solicitations, evaluation criteria and sustainment plans?
-
AUTOWARCOM and FASCOM Details: Authorities, funding lines and how the autonomy PAE interacts with platform programs.
-
Budget Reality: The large proposed figures still have to survive the appropriations process.
-
Aviation: Leaders made no direct comments on specific aviation programs such as MV-75 or Apache, but autonomy in aviation formations and the push away from program-centric structures are worth tracking closely.
Bottom Line
AUSA 2026 did not introduce a single new idea. It did something more important: it attached organizations, deadlines and a mandate to ideas the community has discussed for years. For suppliers, integrators and investors, the practical question is no longer whether open, commercial and autonomous approaches will shape Army buying. It is who is ready to deliver them safely, securely and fast.
Building for the Army’s next Phase of Modernization
Open architectures, autonomy and distributed operations all depend on software that can integrate securely, run predictably and support change over time. Lynx helps teams build mission-critical edge systems on a modular foundation, with support for mixed-criticality workloads and deterministic CPU and GPU execution.
Explore LYNX MOSA.ic and LYNX MOSA.ic.AI, or contact us to discuss your architecture.
In our next post, we look at what this means for engineers building safety-critical and mission-critical systems.
