A first, without much ceremony
On July 12, as part of a wave of strikes on Iranian targets, three uncrewed surface vessels hit the port at Bandar Abbas Naval Base, a submarine and ship maintenance facility. Central Command confirmed it the next day. It was the first American combat use of sea drones. The boats are 24 feet long, carry up to 1,000 pounds, and have a range of more than 1,000 nautical miles.
A month earlier, one of the same boats, operated by Task Force 59, picked up two Army aviators after their Apache went down off Oman and carried them to a point where a helicopter could hoist them out. The Navy described that run as autonomous.
Long range means thin links
A thousand-mile sea drone spends most of its life at the far end of a thin link. Over open water the options are satellite, line-of-sight radio, or nothing, and in the Gulf this year all of them have been jammed or spoofed. In the first four days of the war, interference events hit hundreds of commercial ships and placed tankers on dry land.
That shapes how these boats are employed. Supervision is intermittent by design. The vessel carries its orders, its constraints, and its abort conditions, and it acts on them in the stretches when nobody can reach it. Whatever it was told before the link dropped is what it will do.
The mission record is part of the weapon
When a crewed ship fires, there is a log, a watch team, and a captain who can explain the decision. When an uncrewed boat strikes after an hour of silence, the explanation has to be reconstructed from data: what target it was assigned, by whom, under what constraints, what it observed on the way, and when it last heard from a human.
That record matters for the next strike as much as the last one. The Navy is already studying how the Hormuz campaign will speed up integration of uncrewed systems into mine countermeasures and beyond. Every lesson depends on knowing what each vessel was told and what it did.
How EdgeLance handles the gap
EdgeLance assigns work to assets as tasks with an owner, a lease, and constraints, and records the result as a receipt. A boat that goes quiet keeps its lease until the lease expires, and then the task goes back on offer so another asset can pick it up. Nothing is lost when the link drops, and nothing is silently duplicated when it comes back.
Every assignment, approval, and receipt is signed and stored in the mission record on the nodes that saw it, then synced across the team's mesh when connectivity returns. The maritime awareness mission uses the same task model as the air and ground missions, so a staff running drones, boats, and ground teams sees one list of who holds what. We wrote about operating this way in our Hormuz whitepaper in June, before the first strike.
More boats, same question
The Council on Foreign Relations argues that drones and missiles have largely replaced mines as the favored tool against chokepoints, because they let an attacker pick which ships to hit. The defender's answer will include many more uncrewed boats on both sides of the fight. Each one adds another asset acting on orders it received hours ago, and the question after each strike stays the same: what was it told, and by whom.