
The timing is not coincidental. Three weeks after the PLA fielded a 204-meter mothership for large uncrewed submarines and the UK granted foreign access to Ukraine's 5M-frame Avengers AI dataset, the Navy is consolidating autonomous development into a single operational command.
RASWDC's real constraint is not organizational — it is doctrine and crew certification. The Navy has built unmanned prototypes across air, surface, and undersea; it has not built the tactics or the training pipeline to deploy them as a coherent force. If Rear Adm.
Smith's phased plan delivers certified doctrine by mid-2027, the Navy can begin replacing manned escort rotations in the Hormuz with autonomous surface platforms by FY28.
RASWDC collapses the acquisition-to-fleet cycle for unmanned systems at the exact moment the Hormuz blockade and the Greenland base expansion have exposed the Navy's dependence on forward-deployed manned platforms.
The center's mandate — rapid testing, doctrine development, and field iteration — directly addresses the operational constraint that has defined the last six months: the Navy has unmanned prototypes but no integrated tactics or certified crews to deploy them at scale. Rear Adm.
Smith's phased implementation plan runs in parallel with the DRPM RAS portfolio authority, creating a feedback loop that should compress the 4-5 year development cycle to 18-24 months for air, surface, and undersea platforms. Watch whether RASWDC's first operational test cycle (likely Q4 2026 or Q1 2027) produces doctrine that the Fleet actually adopts — the gap between capability and employment has killed autonomous programs before.
Does RASWDC have dedicated funding authority, or does it depend on existing RAS line items within the FYDP? If the latter, the command becomes a coordination office, not a capability accelerator.
Strategic intelligence, synthesized daily — with a public track record. Every call graded against what actually happened.