
The doctrine announcement precedes any visible procurement signal, which means the Navy is telegraphing a capability gap it believes Congress will fund. Seabed defense is a NATO-wide vulnerability (Russian sabotage threats in the Baltic have been documented for years), so this likely becomes a NATO coordination requirement — expect SACEUR to demand allied submarine contributions, which will strain European navies already committed to Black Sea and Mediterranean rotations.
The real constraint is not the boats but the crew: attack submarine billets are already at 89% manning, per the 2024 force structure review. Adding a seabed rotation means either expanding the submarine industrial base (a 5-7 year effort) or cannibalizing other missions.
The Navy is formalizing undersea infrastructure defense as a warfighting priority — a shift that exposes a hard constraint on submarine force structure and signals a reallocation of attack boat tasking away from power projection.
Seabed defense requires persistent presence over fixed infrastructure (cable landing stations, nodes, repeaters), which competes directly with the current operational model of surge-deployment carrier strike groups and Pacific contingency rotations. If the Navy commits dedicated boats to CUI protection, INDOPACOM loses surge capacity in the Taiwan Strait contingency window, forcing a trade between homeland resilience and forward deterrence that the FYDP has not yet reconciled.
What is the Navy's actual force-structure requirement for seabed superiority — how many boats, what hull types, and does this come from the 355-ship plan or represent an add?
Strategic intelligence, synthesized daily — with a public track record. Every call graded against what actually happened.