Chapter 01 Context

What is Project Flytrap?

Project Flytrap is a recurring, HQDA-directed Army counter-UAS experimentation series in Europe focused on enabling offensive counter-drone operations so brigades can gain and maintain mobility. Rather than designating a single commercial product, Flytrap establishes a structured learning environment where Army units and allied partners put equipment into soldiers' hands and resolve network integration challenges across echelons.

Tracing its start to March 2025, the initiative progressed deliberately from individual operator familiarization through collective squad, platoon, and troop exercises. That progression allows technical teams to isolate integration bottlenecks, training gaps, and data-collection failures in smaller trials before scaling up to multinational force-on-force events.

Chapter 02 The discussion

Breaching the multi-domain reconnaissance-strike complex

The AUSA 2026 briefing partitions the modern battlefield problem into two linked arenas: enabling brigade maneuver in the close fight (led by Col. Tim Price) and orchestrating convergence in the deep layer (led by Col. Charles King). In the brigade fight, traditional security and counter-reconnaissance areas have evolved into a networked reconnaissance-strike complex combining kinetic UAS threats, counter-UAS systems, electronic warfare (EW), command networks, and precision fires.

Functionally, this reconnaissance-strike complex operates like a connected alarm system linked to a weapon: sensors detect a formation, networks transmit the data, commanders or algorithms select targets, and fires or drones strike—halting friendly maneuver before a unit ever reaches a physical obstacle. Because units initially lacked a doctrinal framework for applying new unmanned tools to this multi-domain obstacle, the formation adapted the traditional breaching framework SORA—Suppress, Obscure, Reduce, Assault:

• Stimulate and Suppress: To locate hidden threats, the brigade flies small, attritable UAS into the enemy’s security area to provoke the adversary into cycling EW systems from passive to active or turning on radars—generating electromagnetic signatures that higher headquarters can exploit for targeting.
• Obscure via Spectral Camouflage: Obscuration extends beyond visual smoke to encompass spectral camouflage—managing and reducing electromagnetic signatures that would otherwise betray a formation's position to enemy sensors.
• Reduce C2 Nodes and Assault: While breaking any link in the enemy's kill chain helps preserve mobility, attacking enemy command-and-control (C2) nodes, headquarters, and drone ground-control stations with one-way attack munitions disrupts multiple threats simultaneously—opening a corridor for the assault force to pass through, strike the enemy's rear, and restore offensive momentum.

Minimum viable products and multi-echelon convergence

A central lesson from Operation Flytrap is prioritizing Minimum Viable Products (MVPs) over waiting for perfection. Getting workable systems into soldiers' hands today allows formations to build core operational competency now rather than losing years awaiting an ideal solution. At the same time, lessons from Ukrainian operations—where units must overcome "drone transparency" to reoccupy territory—underscore that a brigade cannot execute a multi-domain breach alone; success requires multi-echelon convergence and external resources from higher headquarters.

Chapter 03 Data

Network integration and the Common Operating Picture

Throughout Project Flytrap, network integration emerged as the primary technical challenge. When multiple sensors operate across separate, incompatible vendor systems, commanders lack a unified view of the battlespace. Solving data collection across resilient networks requires feeding disparate sensor tracks into a single shared data stream and Common Operating Picture (COP) so formations can interpret threats and act rapidly.

In Flytrap 4.5, Army teams evaluated the Integrated Sensor Architecture (ISA) to establish open-architecture data formats and verify vendor integration claims. During the AUSA Q&A, panelists also highlighted the acquisition balance between direct unit-level vendor engagement and standardized vetting processes—ensuring that emerging AI and sensor tools meet open integration baselines before fielding.

For supporting IT environments, connectivity and usability must be engineered together. A resilient architecture ensures that sensor data, configuration states, and system handoffs remain intelligible to operators, maintainers, and higher headquarters alike.

Chapter 04 Infrastructure

Compute, power constraints, and integrated maneuver enablers

Deploying autonomous systems and multi-domain sensors to tactical formations immediately exposes physical infrastructure limits—particularly around onboard compute, resilient communications, and power generation. These operational realities align directly with the three foundational pillars examined in our companion Autonomous Warfare Command analysis: compute, communications, and data.

Power management and forward EW integration

The AUSA panel underscored that power generation and battery management remain major operational constraints. Integrating full-stack AI autonomy onto small, soldier-carried drones places heavy demands on limited battery capacity required to run sensors, communications, and onboard processing simultaneously. Sustaining these systems in the field requires deliberate planning for power generation, battery loads, and ruggedized support.

Organizational integration is equally critical. Rather than treating specialists as separate attachments, the 2nd Cavalry Regiment embeds its electronic warfare platoon up front as part of its multifunctional reconnaissance company. Operating ahead of the formation with dedicated spectrum-monitoring tools, EW soldiers identify what capabilities the adversary is bringing to bear in the breach so commanders can counter them or maneuver around them.

Chapter 05 People

Training the "New Basics" and bounding AI authority

Technology only translates into combat effectiveness when soldiers across every specialty can operate it under pressure. In the AUSA discussion, CSM Jesse Clark emphasized integrating the "New Basics"—unmanned ground vehicles (UGVs), UAS, counter-UAS, and electromagnetic spectrum awareness—directly alongside the Army’s enduring fundamentals of shoot, move, communicate, medicate, camouflage, and map reading.

Standardization through Unit Training Management and Expert Badges

Turning ad-hoc field workarounds into durable proficiency requires standardization and a disciplined Unit Training Management (UTM) system backed by dedicated time, personnel, and equipment. To establish a common baseline across all military occupational specialties, the panel proposed incorporating drone, counter-drone, and spectrum-awareness tasks into the Army’s established Expert Badge series. Even when soldiers are not designated specialists, shared baseline fluency allows teams to operate together seamlessly.

Cultivating leaders capable of driving formations amid high cognitive load requires three complementary strengths: officers with strong intellectual curiosity and tactical judgment, heavy reliance on technical expertise from the Army’s warrant officer cohort, and empowering younger soldiers who are rapidly adopting UAS tools today and will carry that native confidence into future NCO and leadership roles.

Chapter 06 The connection

From the Cross-Domain Contact Layer to Autonomous Warfare Command

Col. Charles King’s briefing on Multi-Domain Command Pacific (MDCPAC) illustrates how brigade-level integration lessons scale to theater-wide operations. Serving as the theater army’s forward edge inside an adversary’s Weapons Engagement Zone (WEZ), MDCPAC executes a multi-domain cover mission: operating small, independent teams across domains that perform reconnaissance, counter-recon, strike, and penetration to disaggregate elements of the adversary’s system and create temporary windows of relative overmatch that a separately operating main body and joint force can exploit.

To orchestrate these distributed teams without concentrating every sensor and weapon in a single vulnerable headquarters, MDCPAC employs the Cross-Domain Contact Layer (CDCL) framework built on four integrated components:

• All-Domain Sensor Arrays: Integrated sensing spanning from space to terrestrial layers.
• Agile Effectors: Layered kinetic and non-kinetic capabilities positioned for rapid convergence.
• Agentic AI-Enabled C2 at the Edge: Automated control systems that orchestrate sensors and manage parts of the fires chain.
• Durable Ground Formations: Sustainable maneuver forces able to survive inside the WEZ, conduct reconnaissance, and seize terrain.

In an era of contested logistics and sophisticated defense networks, traditional 72-hour joint targeting cycles are too slow. By using edge agentic AI to compress kill chains from minutes to seconds and reduce cognitive load, the CDCL allows commanders to focus on tactical judgment, command intent, and seizing the initiative. While Project Flytrap and our companion Autonomous Warfare Command article address distinct operational contexts, both underscore the same infrastructure reality: rapid convergence depends on ruggedized edge compute, resilient communications, and governed data pipelines.

Chapter 07 Program perspective

Make readiness reviewable

For the supporting IT environment, Flytrap’s broader relevance is a reminder to value verifiable integration evidence over isolated demonstrations. Program managers, system integrators, and infrastructure suppliers need a shared record of what configuration was delivered, how it integrates into the Common Operating Picture, and what power and sustainment dependencies remain.

Chapter 08 Next steps

From insight to infrastructure readiness

Project Flytrap demonstrates that readiness is forged when usable technology, shared data, realistic power budgets, and disciplined training meet in the field.

Paragon Micro, through its Public Sector division, supports the infrastructure foundation behind those requirements. Inside Paragon Micro’s System Readiness Center, engineering teams bring multi-vendor configuration, staging, testing, and delivery preparation into a controlled integration environment—backed by architecture, modernization, and lifecycle services across compute, storage, networking, security, and cloud.