Drop the Littoral, Keep the Argument: What Deptula’s Sharpest Objection Gets Right

David Deptula’s response to my piece on the “air littoral” made one argument I did not adequately answer, and it is the one worth sitting with rather than relitigating.

It is not the dispute over who was responsible for Hormuz. It is not the dispute over what he has or has not proposed as a solution. It is a narrower, more interesting claim: that the maritime kill web analogy, the mass-produced USV wolfpacks, the payload-utility manager, the node-host orchestrating a distributed mesh, demonstrates a recurring dynamic in force economics, but does not demonstrate that low-altitude airspace is a “littoral.” Similarity in cost structure, he argues, is not identity of battlespace. A metaphor is being asked to do the work of a doctrine, and it cannot.

I think he is right about that.

And I think conceding it actually strengthens the underlying argument rather than weakening it.

The Metaphor Was Never Load-Bearing

Here is what “littoral” was doing in my original piece: it was a bridge word, a way of saying “the thing Bremer and Grieco found in low-altitude airspace over Iran is structurally the same thing I have been documenting at sea” without having to build the structural case from scratch. That is a legitimate rhetorical move, analogies earn their keep by transferring a body of prior work into a new argument quickly, but Deptula’s objection exposes what the analogy was quietly asking readers to accept along with it: that because the economics of the threat resemble each other across domains, the battlespace must resemble each other too.

Those are separate claims, and only the first one is true.

The maritime littoral is a real, geographically specific thing: the zone where land, sea, and air forces interact near a coastline, with its own bathymetry, its own sensor physics, its own history of doctrine going back to riverine warfare and amphibious operations. Low-altitude airspace over the Strait of Hormuz shares none of that. It is not a coastal seam. It is airspace at a particular altitude band, full stop.

Calling it a littoral because the weapons in it are cheap and numerous, the way the weapons in an actual littoral often are, is exactly the sleight of hand Deptula is naming: borrowing the authority of an established doctrinal term for a claim the term was never built to carry.

So the honest position is not “he’s being pedantic about vocabulary.” It’s that the vocabulary was doing more work than the underlying argument could support on its own, and a serious critic was right to take it away.

What Survives Without It

Here is what does not depend on the word “littoral” at all, and what the maritime work actually established, independent of any geographic metaphor:

When a force built around a small number of expensive, hard-to-replace platforms, a capital ship, a fifth-generation fighter, meets an adversary fielding thousands of cheap, distributed, attritable ones, the expensive force’s doctrinal advantages stop transferring. Its sensors, its survivability, its precision, all of it was built to win a contest of destruction against an integrated system with identifiable high-value nodes. A swarm has no such nodes. Winning against mass requires answering with mass, or with enough persistent, distributed sensing and engagement capacity that losing individual nodes doesn’t matter. Timperlake’s separation of target acquisition from target engagement, running continuously, rather than concentrated in a small number of exquisite platforms that arrive, act, and leave.

That argument does not need Hormuz to be a “littoral.” It needs Hormuz to be a place where cheap mass met an exquisite force built for a different fight which is exactly what happened, and which Deptula does not dispute.

Read this way, the Black Sea, the prospective Taiwan Strait fight, and the skies over Iran are not analogous because they are all “littorals” in some extended sense. They are analogous because they are all instances of the same underlying force-design problem: intelligent mass versus exquisite scarcity. That framing is domain-agnostic by construction. It does not care whether the contested space is air, sea, or land, because the thing doing the explanatory work is the economics of the threat and the architecture of the response, not the altitude or the depth at which the contest occurs.

Why This Matters More Than It Looks

Deptula’s deeper objection, the one underneath the vocabulary fight, is that “air littoral” as a doctrinal category would organize responsibility around altitude rather than around mission, and that this is backwards. His artillery example makes the point cleanly: nobody assigns responsibility for enemy artillery to the Air Force merely because the round travels through the air. Responsibility follows the mission, the objective, and the command relationship, not the physical medium a threat happens to pass through.

He is arguing, in effect, that “air littoral” smuggles in a jurisdictional claim disguised as a description. And an intelligent-mass-versus-exquisite-scarcity framework does not have that problem, because it never claimed a domain or a service in the first place. It is a statement about what kind of force architecture wins a given contest, applicable to whichever service, or combination of services, is actually assigned the mission. It tells you what capabilities a joint task force needs against a mass threat. It does not tell you, and was never trying to tell you, which service patch belongs on the officer commanding it.

That is a better foundation to build on than the one I offered originally, not because it is more diplomatic, but because it is more precise about what the maritime work actually proves. The payload-utility manager and node-host architecture Ed Timperlake and I developed is a claim about how to fight mass with mass economically. It travels to the air domain, to space, arguably to cyber, on its own terms. It never needed “littoral” to make the trip, and asking the word to do that work invited exactly the objection Deptula raised.

An open force-design question

Once the vocabulary is set aside, what remains is a genuine and still-open force-design question, and it is worth being precise about what it is.

Jointness at the moment of employment does not resolve who builds intelligent mass in the years beforehand, when service budgets, not combatant commands, decide what gets bought.

That is a harder and more consequential argument than whether a stretch of airspace deserves a maritime label, and it is the one the Hormuz experience should actually be pushing the services toward having.

That is where this debate should go next.

The Air Littoral Is a Maritime Problem Too: What the Kill Web Fleet Can Teach the Airpower Debate

The Air Littoral Is a Maritime Problem Too: What the Kill Web Fleet Can Teach the Airpower Debate