A phone card in Grenada
In October 1983, American forces landed on Grenada and found they could not talk to each other. Army, Marine, and Navy units carried radios that did not interoperate. Ships in sight of the Rangers could not take their calls for fire. Marines in the north could not raise the Rangers in the south.
The best-known story from the operation has an officer under fire placing a commercial long-distance call to Fort Bragg to get support routed to the fleet offshore. Naval History magazine notes the details have never been fully confirmed. The radio failures are not in dispute. They helped drive the Goldwater-Nichols Act of 1986, which fixed the command structure.
Goldwater-Nichols unified command. It did not unify equipment, and no law could. Forty years later the problem has returned in a new form, and commercial technology is both its cause and its cure.
Commercial technology solved supply and multiplied interfaces
The Army and the department buy commercial off-the-shelf hardware at a pace no program of record could match. The second Drone Dominance Gauntlet tested 23 platforms from 19 companies, and the department plans to buy more than 200,000 small drones by 2027. The Army's drone marketplace now serves 33 nations. Soldiers carry commercial phones and tablets. Satellite terminals ride on vehicles.
That is the right policy. Commercial hardware is cheap, current, and available. But each product arrives with its own ground station, its own app, and its own idea of the picture. A platoon flying aircraft from three vendors runs three control systems. A battalion adds radios with different waveforms, a commercial satellite link, and a helicopter company that sees none of it.
The field reports are consistent. At Lightning Surge 5 in September, data did not pass reliably between new command and control software and the 25th Infantry Division's radios, which used a different waveform than the unit that tested before it. "It wasn't seamless," said Brig. Gen. Shane Taylor. At Project Convergence in July, a drone maker attributed launch delays in part to communications parts made by a separate company, and a five-drone swarm turned back when Black Hawks entered its airspace.
The cost of the closed box
Every closed system levies a tax. Wire six systems to each other and you need fifteen adapters. Wire twelve and you need sixty-six. Each adapter is a contract, a test event, and a failure point, and most are built by the integrator in the field at the worst possible time.
The deeper cost is tactical. A drone that cannot take a task from the unit's plan is a drone flown by one soldier for one purpose. A sensor that reports only to its own screen adds a screen, not a capability. An aircraft the drone crew cannot see forces the whole sky to stop. Interoperability multiplies combat power. Its absence divides it.
Five domains, one mission
A unit at the edge fights across five domains of equipment. Operators carry commercial phones, tablets, and laptops on every major operating system. Drones and ground and sea vehicles come from many makers. Crewed aircraft share the airspace. Sensors range from cameras and radar to RF receivers and full-motion video. Above it all sit the enterprise C2 platform, the staff's planning tools, and TAK.
Hardware-agnostic software has to bind all five into one mission. That means one plan the whole force executes, one picture every echelon shares, one task list that assigns work to any asset that can do it, and one record of what was decided and done.
What hardware-agnostic has to mean
The term is overused. We hold it to five tests. First, translate once. Each source is mapped at the edge into a common vocabulary of observations, tracks, assets, tasks, and receipts, so the tracker, the map, and the tasking engine never care who made the sensor. Second, use open standards where they exist: MAVLink and ROS 2 for vehicles, MISB KLV and NITF for video and imagery, ADS-B and AIS for traffic, TAK for team awareness, GeoPackage for maps.
Third, task across makers. Work is offered to whichever asset can do it, judged on position, payload, and endurance, not on brand. Fourth, work disconnected. The binding happens on the unit's own hardware and survives the loss of every link to higher. Fifth, the government owns the vocabulary. If one vendor defines what a task means, every other vendor integrates on its terms.
How EdgeLance does it
EdgeLance runs on Windows, Android, macOS, iOS, and Linux, from the operator's phone to an air-gapped cluster. Capabilities ship as mission blocks that share one vocabulary and declare what they consume and produce. Vehicle telemetry, ADS-B traffic, camera detections, and RF reports become typed observations, and the multi-domain tracker fuses them into one picture that refuses what it cannot verify.
The tasking layer offers approved tasks to any asset on the roster. The best bid holds the task on a lease and returns a receipt. Integrations exist today for MAVLink autopilots, ROS 2, TAK, MISB KLV video, NITF imagery, GeoPackage, MANET radios, software-defined radio, and ADS-B. The picture and the tasks ride the EdgeLance mesh across whatever link remains.
The 2027 roadmap carries this further. One vehicle contract will connect air, ground, and sea vehicles from any maker, observe-only first, then bounded commands with receipts. Airspace control measures become hard constraints on every task, so crewed and uncrewed aircraft share the sky without grounding it. An assurance check will test any vendor's autonomy against mission constraints without trusting that vendor's own report.
Aviation is the hardest case
Nowhere is the cost of separate pictures higher than in the air. The 3rd Combat Aviation Brigade's three-color rule for drones and helicopters is sound doctrine for a force without a shared picture: when communications are limited, separate aircraft by procedure. But red grounds every drone in the sector, and the number of drones is about to grow by an order of magnitude.
A shared picture of crewed and uncrewed traffic, held at every echelon and enforced in the tasking layer, turns red from a ground stop into a hold on the tasks in the aircraft's path. We set out that case in one airspace for drones and helicopters.
What program offices should require
Require every vendor to publish what its system produces and consumes in an open, documented form, and to map it to a common vocabulary the government controls. Require vehicles to accept tasks from a common tasking layer and to report telemetry to it. Require sensors to report detections in a form another vendor's tracker can use.
Require that crewed and uncrewed aircraft appear on one picture at the echelon that flies the drones. Require all of it to work with the network down. And score interoperability in every competitive event. A drone that cannot take a task from the unit's plan should lose to one that can.
Unity of effort
Unity of command is a principle of war. Grenada showed that unity of command means little if the equipment cannot carry it. The force now buys commercial hardware by the hundred thousand, which is the right decision. The software that binds that hardware into one mission decides whether the purchase becomes combat power.
EdgeLance was built for that job: any model, any hardware, any mission, under the operator's command.