By Robbin Laird

No strategy to structurally constrain Iran’s military options is complete without the maritime dimension.

For decades, Tehran has treated the Strait of Hormuz, the northern Gulf, the Bab al-Mandab, and the Red Sea as chronic pressure points, instruments of coercion against adversaries and leverage over the global economy.

The IRGC Navy and affiliated forces have harassed commercial shipping, seized tankers, mined waters, and used drones and missiles to threaten or strike vessels linked to the United States, Israel, and Gulf states.

This is not incidental harassment.

It is a deliberate coercive tool, and it has worked precisely because the response has been episodic rather than structural.

Recent events underscore how central this maritime threat remains. Iran can make transit expensive and dangerous whenever it chooses.

From Reactive Escort to Persistent Domain Awareness

The U.S. response has evolved from reactive escort operations toward something more ambitious, even before the current military operation. U.S. Naval Forces Central Command, headquartered in Bahrain, has been building a maritime corollary to regional missile defense: integrated maritime domain awareness combined with collective presence.

Manned-unmanned teaming, integrating unmanned surface and aerial platforms with traditional ships and aircraft, provides persistent surveillance over critical chokepoints, making it substantially harder for Iran to conduct deniable or surprise actions at sea.

The operational concept is no longer “respond when Iran acts” but “maintain continuous awareness and presence that changes Iran’s calculus before it acts.”

The Abraham Accords have extended this maritime cooperation in ways that would have been inconceivable five years ago. The first publicly acknowledged joint naval drill among Abraham signatories, U.S. Naval Forces Central Command with Israel, the UAE, and Bahrain in the Red Sea, has been followed by exercises that have measurably enhanced interoperability in surface warfare, boarding operations, and air-maritime coordination.

These are not relationship-building exercises. They are operational rehearsals for a standing maritime regime.

Maritime Autonomous Systems as the Enforcement Backbone

The most significant operational development in this maritime architecture is the emergence of maritime autonomous systems, unmanned surface vessels (USVs) and unmanned aerial vehicles (UAVs) operating in coordinated teams, as the persistent enforcement backbone of the regime.

Where manned platforms are expensive, politically sensitive to deploy forward, and limited in their ability to maintain continuous presence across vast stretches of open water, autonomous systems offer a fundamentally different calculus.

A networked grid of USVs and maritime UAVs can maintain continuous ISR coverage of the Strait of Hormuz, the northern Gulf, and the southern Red Sea simultaneously, at a fraction of the cost of continuous manned patrols and without the political sensitivity that attends a permanent manned naval presence in every partner nation’s waters. Their sensor data feeds in real time into the common operational picture shared by Fifth Fleet, GCC navies, and Israeli maritime forces. Any IRGC vessel that departs its home port, any suspicious small-boat cluster forming near a tanker lane, any suspicious underwater signature in a chokepoint. all of it becomes immediately visible to the coalition.

The deterrent logic is straightforward.

Iran’s maritime coercive options have historically depended on elements of surprise and deniability: fast-boat swarms appearing out of nowhere, mines laid at night, tanker seizures conducted before any manned response could arrive.

A persistent autonomous ISR grid eliminates surprise and strips deniability.

If every IRGC maritime movement is tracked from departure, the coercive options that depend on the fog of the sea disappear.

What remains is only what Iran is willing to do in full view of a coalition capable of responding.

This is the meaning of a security, deterrence and interactive kill web capability to enable enforcing a maritime transit zone without an Iranian threat being acceptable to the coalition.

The Fifth Fleet Allied Component as Regime Operator

The institutional home for this maritime enforcement regime is already visible: the allied component of US Naval Forces Central Command, operating out of Bahrain. Fifth Fleet has been the operational hub for maritime security cooperation in the Gulf, the Red Sea, and the Arabian Sea for decades. What is new is the density of allied participation and the integration of autonomous systems into standing operations.

The allied component of Fifth Fleet, incorporating GCC navies, the Israeli Navy, and in the Red Sea dimension, additional European and Asian partners with equities in the free flow of commerce—provides both the political legitimacy and the operational depth for a standing maritime enforcement regime. It is not a US unilateral operation. It is a coalition standing task force with the U.S. providing command architecture, ISR integration, and high-end response capability, while regional partners provide persistent presence and routine enforcement.

The regime’s mandate would cover three core functions.

• First, continuous ISR of Iranian naval and IRGC maritime forces, with shared data feeding coalition partners in real time.
• Second, standing authority to interdict Iranian attempts to transit weapons, components, or personnel by sea in violation of agreed constraints on Iranian military rebuild—a maritime analogue to the air and land interdiction missions that characterized the post-war Iraqi containment.
• Third, immediate response authority for any Iranian attempt to threaten commercial shipping or close transit chokepoints, with pre-delegated rules of engagement that reduce the political hesitance Tehran has historically exploited.

The Integrated Architecture: Sea, Air, Land

Viewed together, the three articles in this series describe an integrated regional security architecture with interlocking components.

The GCC-Israel kill web provides air and missile defense coverage and enforces demilitarization in the land and air domains.

The maritime regime, operated through the Fifth Fleet allied component and enforced by autonomous systems, closes the maritime flank and denies Iran its historical leverage over global trade arteries.

The political framework, the militarized Abraham Accords operating under the Riyadh logic, provides the coalition legitimacy and the burden-sharing arrangement that makes the architecture sustainable without permanent large-scale U.S. operational presence.

This is not a utopian design.

It rests on components already in development, on coalitions already forming, and on political shifts already underway.

The war with Iran has been a catalyst, the shock that converted tacit convergence into visible commitment. What remains is to consolidate that commitment into durable architecture before the political moment passes and old habits of episodic crisis management reassert themselves.

The measure of success will not be whether the Islamic Republic falls.

It will be whether, a decade from now, the regional security environment has been so fundamentally restructured that Iran’s options for coercive military power projection, in the air, on the land, and at sea, have been permanently and verifiably constrained.

That is the long game Trump sketched in Riyadh.

It is now, for the first time, within reach of execution.

Note: The Combined Maritime Forces (CMF) is headquartered in Bahrain, under U.S. Naval Forces Central Command / Fifth Fleet.

The Combined Maritime Forces (CMF) is a standing partnership headquartered in Manama, Bahrain, and closely integrated with U.S. 5th Fleet/NAVCENT.

CMF operates through several subordinate Combined Task Forces (e.g., CTF 150, 151, 152, 153), which cover the Gulf, Red Sea, Arabian Sea, and adjacent waters, and are the vehicles for the “maritime enforcement regime” you describe.

CMF today is a 47‑nation coalition; membership shifts slightly over time but currently includes a broad mix of GCC, European, Asian, African, and Australasian partners.

Key groupings:

GCC and regional navies (providing routine presence in Gulf and Red Sea): Bahrain, Saudi Arabia, Kuwait, United Arab Emirates, Qatar, Oman, plus other regional states such as Jordan and Pakistan.

Israel: The Israeli Navy participates within the U.S.-led regional maritime security architecture, including CTF 153 and related Red Sea security initiatives, though some contributions are not always detailed publicly.

European partners (especially in the Red Sea/Bab el‑Mandeb dimension): United Kingdom, France, Italy, Netherlands, Norway, Spain, plus other European CMF members such as Denmark and Greece.

Non‑European extra‑regional partners: Canada, Australia, New Zealand, Japan, Republic of Korea, Singapore, Seychelles, Mauritius and other Indo‑Pacific and African contributors.

The fourth and final article in this series summarizes the argument and then discusses how such a strategic result could enable the phased expansion of non-Hormuz export routes, hardened against disruption.

For more on maritime autonomous systems and how they can effectively play the interactive roles I have laid out in this article, see my latest book:

Lessons From the Drone Wars: Maritime Autonomous Systems and Maritime Operations

For the first two articles in the series:

The Coalition Framework: Enforcing the Continued Suppression of Iranian Power Projection Capabilities

Building the Kill Web: GCC-Israel Security and Deterrence Architecture

 

By Robbin Laird

If the first strategic challenge is to define the demilitarization objective and the coalition that enforces it, the second is to build the kill web that gives that coalition real deterrent teeth.

Deterrence in the post-war Middle East cannot rest on declarations or episodic deployments.

It requires persistent, integrated, and credible architecture or security, deterrence and kill web architecture.

A kill web is distributed and resilient: sensors, shooters, and effectors are networked across platforms and domains so that degrading any single node does not collapse the whole. For a coalition enforcing Iranian demilitarization across the Gulf, the Levant, and surrounding seas, a kill web is not a preference but a necessity.

The threats are too varied, the geography too distributed, and the political sensitivities too complex for a single-nation, single-platform approach.

And as I argued my just released drone warfare book, I underscored that the security, deterrence and kill webs share many of the same ISR capabilities but differ simply in terms of the payloads to execute the desired mission outcome.

The GCC Iron Dome: Integrated Air and Missile Defense

Long before the current conflict, GCC states and Washington had been quietly laying the foundations of integrated air and missile defense, shared early warning, interoperable sensors, regular exercises, and foreign military sales packages optimized for networked employment. What had been largely notional is now urgent. The GCC secretary general has recently been explicit: Gulf states are weighing a unified missile shield that would function as a collective protective umbrella against Iranian and proxy missile and drone threats.

The strategic logic is not complicated. Iran has repeatedly used ballistic and cruise missiles, as well as UAVs, to attack Gulf energy infrastructure and threaten U.S. and partner bases. Individual national systems, Patriot, THAAD, bespoke short-range interceptors, have proven useful but insufficient when confronted with saturation attacks or the need to protect transnational infrastructure and air-sea corridors.

What a regional IAMD lattice offers is a step change: multiple look angles on the same threat, tiered engagement opportunities, and a common operational picture fusing GCC sensors, U.S. space-based and airborne warning, and Israeli battle-tested interception systems.

Israel’s layered defense is the template that now has the Gulf states’ full attention. Iron Dome, David’s Sling, Arrow, and the emerging Iron Beam laser capability have been tested repeatedly under real combat conditions, not in exercises but in actual engagements against Iranian barrages.

Gulf interest is no longer theoretical. Israel and the UAE have moved forward with defense industrial cooperation, and Israel has approved the export of systems such as the SPYDER mobile air-defense platform to the Emirates.

After experiencing Iranian barrages firsthand, the political resistance that once complicated open Israeli-Gulf defense cooperation has largely dissolved.

A post-war environment in which Iran’s missile forces are weakened but not eliminated will lower the remaining political barriers to a GCC-wide “Iron Dome-plus” enterprise anchored on Israeli and U.S. technology.

The architecture that emerges will be qualitatively different from anything the region has seen: a true multilateral air and missile defense network with shared rules of engagement and a common operational picture—not a collection of national systems operating in parallel.

From Abraham Accords to Military Compact

Five years into the Abraham Accords, the dimension that has mattered most and been least appreciated is the burgeoning defense cooperation. Israel’s integration into the CENTCOM area of responsibility, and its participation alongside the UAE and Bahrain in multilateral exercises, has created habits of cooperation and operational wiring that extend well beyond symbolism. Joint air exercises, defense industrial deals, and intelligence exchanges focused on Iran’s missile and drone activities are now routine.

The framework has moved faster than most expected precisely because the shared threat drove it.

The next logical step what some analysts are calling an Abraham Accords 2.0 is to transform these ties into a formal integrated security architecture. The war with Iran is precisely the kind of shock that makes such an evolution politically viable in Arab capitals. When Iranian missiles, drones, and naval attacks threaten not only Israel but Gulf cities, ports, and energy installations, the case for a visible security pact with Israel acquires a powerful rationale that supersedes earlier political hesitations.

The elements of a military Abraham framework aimed explicitly at permanently constraining Iran’s military capacity would include, at minimum, a formal regional IAMD network linking GCC states, Israel, Jordan, and Egypt under a joint U.S.-regional command construct with shared rules of engagement and a common operational picture. It would include standardized procurement of key systems, interceptors, radars, command and control—to ensure interoperability and economies of scale, backed by shared financing tools. And it would include standing multilateral exercises and pre-positioned stocks that make coalition responses to Iranian rearmament or proxy rocket buildup swift and predictable rather than improvised.

The Kill Web as Deterrence Architecture

The kill web concept is central to making this deterrence architecture credible rather than declaratory. In traditional deterrence models, the threat of retaliation deters because the adversary believes the retaliating power has the will and the capability to deliver. In a coalition kill web architecture, the deterrent operates differently: the adversary faces not a single retaliating power but a distributed network of sensors and shooters that makes any aggressive action immediately visible and subject to response from multiple directions simultaneously.

For Iran, this means that any attempt to rebuild ballistic missile capability, whether in hardened facilities, dispersed locations, or through proxy channels, would be detected by a fused ISR architecture spanning U.S. space-based sensors, GCC ground-based radars, and Israeli signals intelligence, and made available simultaneously to all coalition partners.

The decision about how to respond would not require American presidential authorization in every case.

Regional partners could act at the speed of the threat.

This is the kill web logic applied to deterrence: not a single chain of command waiting for orders from Washington, but a networked coalition in which the United States provides the connective tissue and the high-end capabilities at the top of the escalation ladder while regional partners carry the sustained operational burden.

It operationalizes the Riyadh premise directly: regional actors take the lead in containing Iran while the United States provides connective tissue, high-end capabilities, and political cover.

The third article in this series examines the maritime dimension of this architecture—where the kill web meets the sea lanes, and where autonomous systems are emerging as the enforcers of a new international maritime regime around Iran’s coastline.

The Coalition Framework: Enforcing the Continued Suppression of Iranian Power Projection Capabilities

By Robbin Laird

The “Super B‑1B”: Hypersonics, Kill Webs, and the Revival of a Legacy Bomber

In earlier work, I argued that hypersonic weapons would only become strategically meaningful when embedded in a wider kill‑web construct what my colleague Ed Timperlake described as the evolution of S‑cubed, where speed, stealth, and situational awareness are fused into a 21st‑century strike enterprise.

Hypersonics, in that framing, are not silver bullets. They are one node in an evolving web of sensors, shooters, and decision‑makers. Today, the U.S. Air Force’s decision to re‑weaponize the B‑1B Lancer with new external pylons and to use it as a hypersonic testbed is a concrete expression of that transition from technology demonstration to operational architecture.

When hypersonic research reemerged in the early 2000s and 2010s, much of the debate focused on speed and range as ends in themselves. Test vehicles flew, some failed, and a familiar pattern emerged: ambitious programs, spectacular imagery, but limited impact on actual force design. In Ed’s earlier emphasis on hypersonic cruise missiles and the S‑cubed ecosystem, he emphasized that the true value of hypersonics would lie in how they were integrated with fifth‑generation fighters, ISR platforms, and distributed maritime forces to generate credible prompt strike in contested environments.

That logic is now showing up in American bomber modernization. The Air Force has chosen not to wait for a purpose‑built hypersonic aircraft. Instead, it is taking a legacy bombe, the B‑1B, and adapting it to serve as a high‑capacity carrier for hypersonic and advanced cruise missiles, nested within a broader kill web that includes the B‑21, F‑35, and a transformed maritime force. This is about using available platforms to accelerate the operationalization of hypersonics, while more advanced systems mature.

For much of the post‑9/11 era, the B‑1B was the archetypal conventional bomber, orbiting over land campaigns and delivering JDAMs and other guided munitions in permissive airspace. As attention shifted to high‑end conflict and as the B‑21 program gathered momentum, the B‑1B seemed destined to be a sunset platform, heading toward retirement due to structural fatigue and changing priorities.​

Three dynamics have combined to alter that trajectory.

• Untapped structural capacity: The B‑1B was built with six external hardpoints designed for nuclear cruise missiles, stations later deactivated under arms‑control arrangements. The structure is there; what has been missing is the political and programmatic decision to use those stations for conventional purposes.
• A near‑term standoff gap: Combatant commanders face rising demand for long‑range, survivable standoff fires, especially in the Indo‑Pacific and Europe. B‑52s are being re‑engined and re‑equipped, B‑21s are only now entering service, and inventories of long‑range conventional missiles remain stressed. The Air Force needs additional “magazine depth” from platforms already in the inventory.
• Modernization bandwidth on the B‑52: The B‑52 is undergoing a sweeping modernization, new engines, radar, avionics, and communications. There is limited capacity to also make it the primary hypersonic test and integration workhorse without introducing delays or risk. The B‑1B, by contrast, can be repurposed more cleanly as the principal hypersonic testbed and, potentially, as an operational carriage platform.

The result is a reframing of the B‑1B’s future. Rather than a bomber drifting toward retirement, it becomes a bridge asset: a conventional, non‑nuclear platform repurposed for 21st‑century long‑range strike with a focus on massed standoff fires.

The technical heart of this revival is Boeing’s Load Adaptable Modular (LAM) pylon. This is not a minor hardware tweak. It is a deliberate attempt to turn the B‑1B’s dormant external stations into versatile hardpoints capable of carrying large and heavy weapons, including hypersonic systems.

Key characteristics of LAM, as described in open reporting and Air Force communications, include:

Modular architecture: LAM is designed to accept a variety of weapons, from 2,000‑lb‑class standoff missiles to 5,000‑lb‑plus stores in the hypersonic weight class.

Six‑station installation: Up to six pylons can be mounted on the B‑1B’s legacy external hardpoints, which were originally tied to nuclear roles.

Hypersonic compatibility: The geometry, loads capacity, and release envelopes are being validated for both boost‑glide and air‑breathing hypersonic weapons, as well as established cruise missiles like JASSM and LRASM.

Flight testing at Edwards Air Force Base has already demonstrated key milestones. A B‑1B from the 419th Flight Test Squadron has flown with LAM installed, conducting captive‑carry missions with a 5,000‑lb‑class inert store and releasing representative weapon shapes to validate separation and loads. These tests underpin the Air Force’s public claim that it has “significantly reduced risk” for an operational external‑carry capability on the B‑1B.

The Air Force has gathered these efforts under what budget documents and reporting describe as a Hypersonic Integration Program for the B‑1B. This program began with relatively modest investments in FY‑22 and FY‑23 to turn a single aircraft into an external‑carry‑enabled testbed, then expanded into a broader External Heavy‑Stores Pylon effort in the FY‑26 submission.

The elements of this pathway include:

• Initial testbed funding: Early funds established the hardware and integration work for a B‑1B configured for external carriage of large stores. This allowed the Air Force to conduct real‑world flight tests rather than relying solely on modeling.​
• Risk‑reduction demonstrations: Captive carry of a 5,000‑lb‑class store and the safe release of a surrogate weapon shape from LAM provided empirical data on loads, flutter, separation, and handling qualities. This data, in turn, supports the argument that the B‑1B is a suitable platform for future operational integration of hypersonic systems.
• Expansion into a fleet‑level modification: In 2025, the Air Force awarded Boeing a contract to produce and fit the new pylons more broadly, framing the effort as both a loadout gain and an enabler of hypersonic testing that does not slow B‑52 modernization. Planned work through the FY‑26 budget cycle includes computational fluid‑dynamics analysis, wind‑tunnel tests, structural and wiring changes, and updates to the B‑1B’s stores‑management system.

Seen through the lens of my earlier hypersonic work, this is a classic case of using an existing platform to accelerate the operationalization of a new weapon class. Instead of waiting for a perfect, bespoke solution, the Air Force is building a pathway from test to combat via the B‑1B.

How much additional firepower?

Public figures for B‑1B loadouts remain partly notional, but the trends are clear. At present, a B‑1B configured for conventional standoff weapons can carry up to 24 JASSM or LRASM internally. With LAM pylons on all six external stations, each capable of hosting two 2,000‑lb‑class missiles, you have a theoretical maximum of 12 additional external standoff weapons.

This yields several useful reference points:

• Conventional standoff expansion: Internal JASSM/LRASM (≈24) plus external JASSM/LRASM (≈12) suggests a potential total around 36 missiles per aircraft in some configurations. Even if operational constraints reduce that number somewhat, the increase in “shots per sortie” is substantial.
• Hypersonic carriage potential: When configured for larger, heavier hypersonic weapons, each pylon may carry a single 5,000‑lb‑plus weapon instead of two smaller missiles. Open‑source analyses, extrapolating from LAM demonstrations and AGM‑183‑class dimensions, suggest the B‑1B could eventually carry on the order of 10–12 large hypersonic weapons in mixed internal‑external configurations, with some assessments going higher depending on assumptions. These are not program‑of‑record numbers, but they illustrate the scale of the potential.​
• Internal bay depth: The Air Force has also re‑rigged the forward internal bomb bay to increase magazine depth and fit longer weapons. This modification, originally tailored to cruise missiles, is equally relevant to future hypersonic designs, giving planners additional flexibility in how they mix inside‑bay and external carriage.

From an operational perspective, even a conservative increase from 24 to low‑30s standoff weapons per B‑1B changes the math of salvo generation, particularly in maritime strike scenarios in the Pacific, where large volumes of long‑range missiles are needed to saturate defenses and ensure kills against high‑value naval targets.

Several analysts have dubbed the upgraded aircraft the “super B‑1B”, emphasizing a streamlined mission set: high‑capacity conventional strike with long‑range, non‑nuclear standoff weapons, including hypersonic systems. The Air Force has been clear that the B‑1B remains a conventional platform; the reopened external stations are for conventional weapons, even if they draw on the structural legacy of a nuclear configuration.

Strategically, this emerging role has at least four implications:

• Extended relevance of the B‑1B fleet: The combination of internal bay modifications and external pylons allows the B‑1B to remain a relevant contributor to high‑end strike into the 2030s and potentially the 2040s, bridging the period when B‑21s are still ramping up in numbers.
• Increased flexibility for Bomber Task Force rotations: A B‑1B equipped with LAM pylons and advanced standoff weapons becomes a more valuable asset for global Bomber Task Force deployments, able to surge large missile salvos from forward operating locations without requiring local stockpiles on the same scale.
• A practical hypersonic integration pathway: Using the B‑1B as a primary hypersonic integration platform allows the Air Force to test, refine, and field hypersonic weapons in meaningful numbers without overburdening the B‑52 fleet. Lessons learned on the B‑1B—release envelopes, integration with mission planning, C2 connectivity—can later be ported to the B‑52 and B‑21.
• Signaling to allies and adversaries: The visible modification of a legacy bomber to carry hypersonics signals that the United States intends to field these systems as part of an operational force package, not as boutique technology. In my earlier terms, it is a move from “hypersonic science project” to “hypersonic node in the kill web.”

The B‑1B story is not an isolated modernization project. It is a case study in how the S‑cubed framework and the kill‑web concept are shaping real decisions.

In “The Coming of the Hypersonic Cruise Missile: A Key Element of S‑Cubed Evolution”, Ed Timperlake and I argued that speed would matter most when combined with stealth and a dense information architecture, allowing forces to sense, decide, and strike faster and from more angles than an adversary could manage. Hypersonic cruise missiles in that construct were a way to compress an adversary’s decision‑time and hold critical targets at risk, especially in maritime and air‑defense networks.​

The upgraded B‑1B fits naturally into that picture:

• Fifth‑generation aircraft and ISR platforms (F‑35, B‑21, unmanned systems) provide forward sensing, targeting, and battle‑space understanding.
• Distributed maritime forces and land‑based fires hold adversary naval and land targets at risk from multiple directions.
• B‑1Bs with hypersonic and advanced standoff weapons provide the volume of long‑range firepower needed to exploit that sensor network, generating salvos large enough to break through layered defenses and deliver meaningful effects.

In this sense, the “super B‑1B” is not just a revived bomber. It is an instantiation of the hypersonic‑enabled kill web that Ed Timperlake and I have been describing for more than a decade. The aircraft gives physical form to an abstract concept: a legacy platform rewired to function as a high‑capacity node in a distributed, networked strike enterprise.

The B‑1B will not be the last word in hypersonic carriage. Over time, the B‑21, new unmanned platforms, and potentially naval systems will take on more of the load. But as of the mid‑2020s, the Lancer’s transformation is one of the clearest examples of how the U.S. Air Force is turning hypersonic theory into operational reality.

By re‑activating dormant hardpoints, leveraging modular pylons, and integrating new weapons through a deliberate risk‑reduction program, the service is demonstrating a pattern likely to recur: adapt what you have, learn by doing, and keep the force moving toward a kill‑web enabled future rather than waiting for perfect solutions.

For readers interested in the underlying details of the B‑1B hypersonic integration effort, the following open sources provide useful background:

Air & Space Forces Magazine, “Air Force Funds New B‑1 Pylons, Eyeing Loadout Gains” (July 2025) – budget figures, LAM description, and Hypersonic Integration Program language.​ (John A. Tirpak, “Air Force Funds New B‑1 Pylons, Eyeing Loadout Gains,” Air & Space Forces Magazine, July 15, 2025, https://www.airandspaceforces.com/air-force-new-external-pylons-b-1-loadout-hypersonic-testing/).

The War Zone, “B‑1B To Finally Get New External Pylons…” – discussion of LAM capacity and test history.​ (Joseph Trevithick, “B‑1B To Finally Get New External Pylons Drastically Expanding Missile Carriage Potential,” The War Zone, July 8, 2025, https://www.twz.com/air/b-1b-to-finally-get-new-external-pylons-drastically-expanding-missile-carriage-potential.).

The Aviation Geek Club, “New External Pylons will drastically expand USAF B‑1B weapon capabilities” – quotes from Boeing on the B‑1 as hypersonic testbed.​ (Dario Leone, “New External Pylons Will Drastically Expand USAF B‑1B Weapon Capabilities,” The Aviation Geek Club, July 10, 2025, https://theaviationgeekclub.com/new-external-pylons-will-drastically-expand-usaf-b-1b-weapon-capabilities/.)

Interesting Engineering, “B‑1B Bone gets hypersonic bite” – notional figures for hypersonic carriage (up to 31 weapons) and general program framing. (“B‑1B Bone Gets Hypersonic Bite: US Bombers to Launch Mach 5+ Missiles,” Interesting Engineering, July 10, 2025, https://interestingengineering.com/military/b-1b-hypersonic-us-bomber-missiles.).

Official Air Force test‑wing releases and video, “Can one size fit all? Edwards demonstrates new modular pylon” – details on LAM tests at Edwards AFB. (Chase Kohler and Giancarlo Casem, “Can One Size Fit All? Edwards Demonstrates New Modular Pylon,” Edwards Air Force Base News, August 5, 2024, https://www.edwards.af.mil/News/Article/3861218/can-one-size-fit-all-edwards-demonstrates-new-modular-pylon/; and Giancarlo Casem, “Can One Size Fit All? Edwards Demonstrates New Modular Pylon,” video, 2:32, 412th Test Wing, August 2, 2024,  https://www.dvidshub.net/video/932709/can-one-size-fit-all-edwards-demonstrates-new-modular-pylon.).

For my most recent report on the evolution of hypersonic weapons, see the following:

Hypersonic Weapons and Strategic Competition: From Science Project to Operational Reality

 

 

By Robbin Laird

Hitchcock’s classic movie, The Birds, offers four core lessons that map almost too neatly onto modern drone swarms.​

• No front lines. In Bodega Bay, danger comes from the sky, not from a defined direction of advance. Likewise, drone swarms turn the battlespace into an enveloping condition rather than a manageable front. There is no “main axis” to track and no stable rear area to protect. For the defender, the environment itself has become hostile.
• Windows of vulnerability. Hitchcock’s birds strike in bursts, exploiting moments when characters are exposed: at gas pumps, in cars, in a schoolyard. Drone swarms behave similarly, massing for short periods to overwhelm local defenses and then dispersing before a counterstrike can materialize. The operational art shifts from steady positional defense to managing successive windows of acute vulnerability.​
• Emergent communication. The birds appear to coordinate without a visible signal. In swarming systems, this is exactly the point. Coordination emerges from “local neighbor data”—each node adjusts its behavior based on the movements and signals of those immediately around it, without reliance on a single detectable command link. For electronic warfare, this means “finding the frequency” or “killing the C2 node” is no longer enough.​
• Shifting modes of attack. Hitchcock moves seamlessly between individual harassment and mass assault. In contemporary terms, this is the spectrum from precision “personality strikes” against specific individuals to saturation attacks designed to crush an entire perimeter. The same architecture supports both, which complicates traditional notions of escalation ladders and proportional response.​

The cinematic lesson is that once the environment becomes the threat, the defender’s psychology changes. The characters in The Birds stop asking “Where is the enemy?” and start asking “When will it hit again?” That shift from spatial to temporal anxiety is exactly what persistent drone presence now imposes on frontline units.

Hydra vs. Brain: Emergent Behavior and the Collapse of Centrality

Traditional military organizations have treated command as a scarce, central function. The logic of the “brain”, a single C2 node orchestrating subordinate units, has shaped everything from staff design to targeting doctrine. Swarm intelligence flips that logic.​

In biological swarms, birds or fish follow simple rules: maintain distance, align with neighbors, avoid obstacles. Complex formations and maneuvers emerge from these simple interactions, not from a central signal. Autonomous drone swarms replicate this with software. Each drone shares sensor data locally, adjusts course and speed, and converges on targets through bottom-up coordination.​

The contrast is stark:

• In a centralized architecture, data flows back to headquarters for analysis and retasking. This introduces latency, creates single points of failure, and invites strategic decapitation.
• In a distributed swarm, the “decision” to adjust geometry or reassign targets occurs at the edge. Sensor-to-shooter timelines compress to minutes or less because the processing and behavior-change happen where the sensors and weapons reside.​

The operational consequences are profound:

• Saturation at scale. Aegis, Iron Dome, or their successors can be numerically overwhelmed when confronted with dozens or hundreds of small, low-cost attackers arriving nearly simultaneously.​​
• Resilience through redundancy. If up to 90 percent of the swarm can be shot down and the mission still succeed, then attrition becomes an accepted design feature. A defender can “win” every engagement tactically, shoot down most of what it sees, and still lose operationally.​
• Precision without centrality. With onboard computing and shared local data, swarms can conduct facial recognition, gait analysis, and pattern tracking even in GPS-denied environments, enabling highly discriminating strikes without a permanent, exposed “brain” in the loop.​
• Instead of a single command node, what the defender faces is a Hydra: a distributed network in which cutting off “heads” (individual units) barely degrades performance. Targeteers must therefore move from decapitation models to network-disruption models: jamming local links, poisoning shared data, or inducing systemic misalignment.​

Intelligent Mass: The Warfare Laboratory in Ukraine

Ukraine has become the world’s most intense real-time experiment in intelligent mass. Where late–Cold War modernization emphasized “exquisite scarcity”, a few highly capable, extremely expensive platforms, Ukraine has embraced cheap, numerous, quickly iterated systems tied together through software and improvisational doctrine.​​

Operation Spider Web is the emblematic case. On June 1, 2025, Ukrainian security services executed a coordinated strike using 117 Osa quadcopters launched from concealed compartments inside commercial trucks spread across five Russian airbases over 4,300 kilometers. The operation destroyed or damaged dozens of aircraft, with estimates running into the tens of billions of dollars in losses, at a marginal cost per drone in the low thousands of dollars.​

Several features of Spider Web illustrate the new grammar of intelligent mass:

• Trojan-horse launch architecture. Drones were hidden in wooden cabins on standard cargo trucks, with remotely operated roofs that opened to launch platforms on command. This exploited civil cover and bypassed traditional perimeter defenses designed for missiles, not embedded launchers.​​
• Deep tailoring of software. Ukrainian engineers trained targeting algorithms on legacy aircraft airframes stored in places like the Poltava Museum of Long-Range Aviation. This demonstrates how an agile software layer can adapt more quickly than hardware modernization cycles; the museum becomes a data lab.​
• ISR preconditions. The strike against a Russian Kilo-class submarine with an autonomous naval drone “Sub Sea Baby” came only after Ukrainian forces destroyed Russia’s lone Il-38N “Sea Dragon” maritime patrol aircraft, suppressing its ISR “eyes.” In swarm-era operations, engaging ISR nodes becomes a precondition for swarm effectiveness rather than a mere enabling activity.​
• Human–machine teaming. While the architecture is autonomous at the edge, Spider Web still relied on human operators for mission planning, legal oversight, and dynamic adaptation to changing tactical conditions. The swarm is not “fully automatic war”; it is a new form of man–machine collaboration.

The lesson is not that expensive platforms are obsolete, but that their survivability and strategic value now depend on how well they are integrated into a kill web where every node can be a sensor, shooter, or decoy. Intelligent mass is not a single system; it is an ecosystem.​​

Psychological Warfare: Personalization, Persistence, and the Hum of Rotors

Swarm intelligence does not only change lethality. It changes how war feels. Just as Hitchcock’s characters are slowly broken by the constant threat of attack from above, modern forces and civilian populations experience a new kind of persistent psychological pressure.​

Three elements stand out.

• Unpredictability. In a battlefield saturated with small, hard-to-detect drones, no one can fully know when or where the next strike will occur. This is particularly acute when personality strikes are part of the repertoire: any vehicle, meeting, or brief walk across an open area might be the moment of targeting.​
• Surveillance as trauma. Persistent ISR from drones means the “eyes in the sky” are always present. The line between observation and attack blurs; a drone loitering overhead could simply be collecting data—or it could be seconds away from engaging. That ambiguity creates what you describe as a permanent “gray zone,” where every movement feels like a potential death sentence.​
• Collapse of strategic distance. Precision swarms can kill one person and spare another standing inches away. The result is an intensely personal experience of being hunted, even when the strategic intent is abstract. Victims do not feel like collateral damage; they feel selected.​
• The soundscape matters. The low, constant hum of rotors becomes the equivalent of Hitchcock’s ominous silence: an auditory reminder that the environment itself has turned hostile. Militaries will have to develop not just counter-drone tactics, but psychological resilience measures for troops working under continuous swarm threat, much as they once did for artillery bombardment and chemical weapons.​

Chaos Management and the New Cost Exchange

If relatively inexpenseive drone can compel a defender to expend a 50,000-dollar interceptor or worse, destroy a platform worth tens or hundreds of millions of dollars, the cost-exchange ratio collapses in favor of the attacker. The traditional model of defending high-value assets with high-value interceptors becomes unsustainable.​

This drives several emerging realities:

• Dispersed lethality and survivability. Large concentrations of high-value platforms, airbases packed with aircraft, carrier strike groups relying on a few key nodes, become inviting swarm targets. Dispersed operations, modular basing, and mobile launch units become not just options but necessities.​
• New defense architectures. Systems like Israel’s Iron Beam, a high-energy laser designed to intercept rockets, mortars, and drones at a per-shot cost measured in a few dollars, represent an attempt to restore cost parity. Even so, the capital cost of fielding enough laser units to cover large areas remains high, and physics imposes range limits.​
• Strategic neutralization vs. stability. Rather than aiming to “restore stability,” states must pursue strategic neutralization: making aggression so costly, slow, and frustrating under constant swarm threat that it becomes strategically irrational.​

Ukraine’s Brave1 initiative, the “Amazon for war” model, embodies this logic at the industrial and doctrinal level. Brave1 connects defense forces, startups, investors, and regulators to accelerate the fielding of new unmanned systems, electronic warfare tools, and counter-swarm solutions, awarding hundreds of grants and creating a pipeline where battlefield feedback rapidly shapes new iterations. It treats innovation speed as a weapon system in its own right.​

Teaching the Swarm Era: Curriculum for the Warfare Laboratory

For curriculum designers and professional military education, the swarm era demands a new intellectual toolkit.

The goal is to move students from thinking of drones as “platforms” to seeing them as manifestations of a hostile, adaptive condition in which they must operate.​

Several pedagogical priorities emerge:

• From platforms to patterns. Emphasize emergent behavior, kill webs, and network effects rather than individual system specifications. Case studies like Spider Web, Sub Sea Baby, and localized swarm attacks against armor and logistics convoys should anchor discussion.​
• Red-teaming with intelligent mass. Put students in the role of the swarm architect. Force them to design operations that exploit windows of vulnerability, ISR suppression, and cost-exchange asymmetries. This helps them understand what they are truly defending against.
• Psychology under persistent threat. Integrate modules on cognitive load, decision fatigue, and moral injury under drone surveillance and attack. Training must prepare commanders to make decisions when every move could trigger a swarm response.
• Ethics and escalation. Personality strikes, dual-use infrastructure targeting, and cross-border swarm operations raise legal and moral questions that cannot be left to technicians alone. Students must grapple with how law and ethics operate in an environment where everything is a potential sensor and every sensor a potential shooter.
• Innovation literacy. Officers need to understand agile development, open architectures, and the dynamics of defense-tech ecosystems like Brave1 as much as they understand traditional acquisition programs. The ability to work with software teams, test units, and volunteer networks becomes a core competency.

In many ways, the classroom itself must become a mini–warfare laboratory: a place where ideas, prototypes, and scenarios are iterated quickly, with failure treated as data rather than stigma.

Final Synthesis: Living With the Weaponized Sky

We are living through a transition from war as a contest of platform strength to war as a contest of networked resilience and adaptation speed.

Swarm intelligence sits at the heart of this shift.

Cheap, numerous, software-defined systems operating on local information have turned the sky and increasingly the sea and ground into a persistent, intelligent presence that cannot be wished away.​

Like the survivors driving out of Bodega Bay at the end of The Birds, today’s forces will not have the luxury of “solving” the swarm problem.

They will have to learn to operate under a permanently weaponized sky, where every hum of rotors may be nothing—or may be the first note of a synchronized, emergent attack.​

The task for strategists, commanders, and curriculum designers is not to restore a lost stability, but to master chaos management in this new environment; to build forces, doctrines, and societies that can endure, adapt, and prevail under the logic of the swarm.

Lessons From the Drone Wars: Maritime Autonomous Systems and Maritime Operations

 

By Robbin Laird

Trump’s Riyadh speech is seldom recalled for its strategic architecture. Most commentary at the time focused on the rhetorical framing of Islam.

But strip away the atmospherics and the speech laid out a division of labor that has proven remarkably durable: Muslim-majority partners would take the lead in confronting extremism; the United States would provide the weapons, political backing, and intelligence.

Washington was positioning itself as arsenal and arbiter, not permanent regional policeman.

Iran was named explicitly. Trump called it out as the state that funds, arms, and trains terrorists, militias, and other extremist groups, and he called on all nations of conscience to isolate Tehran.

Viewed from 2026, that call looks like the opening move of a long game, one whose architecture is now becoming visible.

That long game rests on three pillars:

• Empower the GCC as a regional anchor.
• Normalize and integrate Israel into the regional security architecture.
• And structurally constrain Iran’s military capacity rather than manage an endless balancing act between Tehran and its neighbors.

The Abraham Accords were not an ornamental diplomatic achievement. They were the mechanism for converting a tacit anti-Iranian convergence between Israel and the Gulf into a visible, US-brokered framework spanning diplomatic, economic, and increasingly military domains.

Breaking the Sword, Not the Rulers

The key insight often lost in the debate about whether the current war with Iran will topple the regime is that toppling the regime is not the point. The point is to reshape the environment so that Iran’s capacity to translate ideology into military and coercive power is permanently constrained.

That is a different objective, and it implies a different kind of success.

The current military campaign reflects this logic with considerable precision. The United States and Israel, backed by select regional partners, are systematically targeting Iran’s conventional military infrastructure: airfields, missile depots, IRGC bases, naval assets, and the command-and-control architecture that ties Iran’s long-range strike complex together.

This campaign may not produce immediate regime collapse and Iran’s leadership has survived external military pressure before.

But the military correlation of forces is shifting significantly. Iran’s high-end conventional tools, ballistic and cruise missiles, drones at scale, advanced air defenses, blue-water naval capabilities, are being degraded faster than they can be regenerated under wartime and sanctions conditions.

This creates what might be called a paradoxical opening. A regime still in place but stripped of much of its conventional punch will find itself operating in a regional order no longer organized around US-Iran crisis management.

The question is not “does the regime fall?” but “what structure constrains it going forward?”

The Architecture of Demilitarization: A Coalition Framework

Three interconnected elements are emerging as answers to that question: a GCC-wide integrated air and missile defense architecture, an expanded and militarized Abraham Accords framework, and a maritime security compact that denies Iran coercive leverage over the world’s energy and trade arteries.

Taken together, they represent not a crisis management patch but a durable reordering of the regional security environment.

This article — the first in a four-part series — sets out the general logic of the coalition framework and the demilitarization objective it serves.

The second article examines the GCC-Israel security and deterrence architecture that gives the framework teeth.

The third turns to the maritime regime and the role of autonomous systems in enforcing it.

The fourth concludes the series and adds how enhanced stability in the region allows the phased expansion of non-Hormuz export routes, hardened against disruption.

The concept of enforced demilitarization differs from disarmament in an important respect. Disarmament implies a negotiated outcome: Iran agrees to give up capabilities in exchange for something.

Enforced demilitarization implies a structural outcome: Iran’s attempts to rebuild are detected, challenged, and interdicted by a surrounding coalition whose capabilities and will make sustained Iranian rearmament prohibitively costly.

The goal is not agreement: it is an enforced environment.

The coalition capable of enforcing such an environment already exists in embryonic form. The GCC states, Saudi Arabia, the UAE, Bahrain, Kuwait, Qatar, and Oman, share a compelling interest in a permanently weakened Iran. Israel, now integrated into CENTCOM and maintaining active defense cooperation with Gulf partners, adds the most combat-tested air, missile defense, and intelligence capabilities in the region. The United States provides the connective tissue: ISR architecture, strategic logistics, high-end strike, and political cover. Jordan and Egypt round out the geometry.

What is new is the political viability of making this coalition explicit.

The war with Iran with its direct missile and drone attacks on Gulf cities, ports, and energy infrastructure has dissolved the political resistance that once complicated open Israeli-Gulf defense cooperation. Gulf leaders no longer need to explain purchasing Israeli technology or conducting joint exercises to their publics.

The explanation, as one senior Gulf official noted, writes itself.

The Logic of Structural Constraint

A structurally constrained Iran is one in which the surrounding security architecture itself limits what Tehran can do militarily, regardless of what happens inside Iran politically.

In that order, Iran’s attempts to rebuild ballistic missiles, long-range drones, or blue-water naval capabilities would be detected early by shared ISR and targeted quickly by US-enabled regional forces. Its proxies would face better-defended cities and infrastructure. At sea, Iranian harassment would confront multinational patrols backed by persistent unmanned surveillance and clearer rules of engagement.

This architecture will not eliminate risk.

Tehran will intensify its asymmetric tools, cyber operations, covert attacks, political subversion, and may pursue nuclear hedging to compensate for conventional vulnerability.

Those are real challenges requiring their own responses.

But the architecture dramatically reduces the regime’s margin for conventional military coercion and clamps down on the most destructive forms of power projection.

From the perspective of Trump’s Riyadh “long game,” the war with Iran, tragic and dangerous as it is, can be understood as the catalyst phase: the shock that enables the emergence of a GCC–Israel–US security system designed to make “never again” a military reality, even if the Islamic Republic survives politically.

The goal is to at a minimum change the environment in which the regime operates.

The second article in this series examines how that environment is being built, through integrated air and missile defense, the militarization of the Abraham Accords framework, and the kill web architecture that makes coalition deterrence credible rather than declaratory.