Welcome to The Iron Triangle, the Cipher Brief column serving Procurement Officers tasked with buying the future, Investors funding the next generation of defense technology, and the Policy Wonks analyzing its impact on the global order.
On the night of April 24, 1980, eight Navy RH-53D Sea Stallions lifted off the deck of the USS Nimitz and headed for a patch of Iranian salt flat called Desert One. The plan needed six of them to get there in working order. One was abandoned in the desert after a rotor warning. One turned back in a dust storm. One arrived with a failed hydraulic system. The mission was aborted. Then, while the force repositioned to refuel, a helicopter drifted into an EC-130. Eight Americans died on that salt flat, and fifty-two hostages stayed in Tehran.
When the Secretary of War stood at Quantico on September 30 and announced a new four-star command for autonomous warfare, my first question was not about drones. It was about helicopters.
The Holloway review found the mission "conceptually valid and feasible" and blamed "the ad hoc nature of the organization and planning." The fix, Nunn-Cohen in 1986, gave the new Special Operations Command a budget line the services could not raid. We did eventually build better helicopter units. But we didn't build SOCOM around a helicopter. We built it around the problem that broke the helicopters.
The Secretary seems to understand this. "Ukraine's lesson is not that one type of drone wins wars," Hegseth told the room, "but rather the need for a purpose-built system that maximizes the ability to adapt." His signed memo says the output "is not a particular drone, but the ability to adapt in combat." Then the Department named it the Autonomous Warfare Command. This is like naming SOCOM the Helicopter Command. A drone is a photograph of an adaptation. The adaptation is the movie. In Ukraine, radio-controlled FPVs gave way to fiber-optic spools, which gave way to nets, shotguns and interceptor drones, each turn in weeks or months.
When the 3rd Army Corps air-dropped ground robots ten kilometers behind Russian lines during Operation Vivaldi last month, the footage went everywhere. The commanders talked about something else. A battalion commander known as "Darwin," credited a command structure "qualified enough as we are." An American volunteer with the corps described his entire job as "installing Western mission command trust and initiative." We taught them that. They are teaching it back to us with robots, and we are taking notes on the robots.
Retired Lt. Gen. Mark Hertling warns that "creating a headquarters does not create a capability." He is right, and that is the point of this column. The memo orders a 30-day implementation plan, due on the Secretary's desk around the end of October. A headquarters is a wiring diagram. The capability is a soldier in the motor pool at two in the morning with a soldering iron, a laptop and a firmware image that does not work yet. Here is how to build him, keep him and turn him loose.
Start With the Soldier We Already Have
The Army has made a great start. Its newest specialty, the 15X tactical unmanned aircraft system specialist, is graduating classes of about thirty at Fort Huachuca, with 770 expected by year's end and a planned force of two to three thousand. The colonel who runs the training brigade said it better than anyone at Quantico: "The Army has not bought a drone that the 15X is responsible for being an expert on." Train the soldier to learn the machine, not the machine's manual.
Now follow that soldier for six years. If he is good, he makes sergeant. If he is very good, he makes staff sergeant, and the day he pins it on, his job stops being the drone and starts being the eight soldiers who fly it: counseling, evaluations, ranges and the duty roster. The enlisted promotion system has one ladder, and it runs through the leadership of people. The best technician in the platoon either becomes a manager or gets passed over. Either way he leaves the bench, and the private sector is waiting with a better offer.
Bring Back the Specialist
Warrant officers exist to solve part of this problem. The Army already has an unmanned aircraft systems warrant, and the Air Force, which abolished its warrants in 1959, brought them back in December 2024 for cyber, intelligence and space. But warrants are a thin layer by design. You do not put one in every platoon, and the loop the Secretary described lives in the squad and the section.
The Army has solved this before. In 1955, after a committee recommended separating command from technical responsibility, it created specialist grades to reward experience and technical knowledge. A Specialist Six drew a staff sergeant's pay without a staff sergeant's squad. His job was to be the most technically proficient in the building, and the Army paid him to stay that way. The ladder was dismantled from the top down, and in 1985 SP5 and SP6 went away.
Bring them back, starting with unmanned systems. Promote a Specialist Five or Six on what he can build, fix, modify and teach. Same pay grades, separate ladder, one rule: technical authority, never command. Put specialists in every formation that flies, drives or swims a robot, with the warrant corps above them as the technical chain. A Specialist Six at battalion who can rewrite the flight controller tonight, and a CW3 at brigade who knows which vendor to call in the morning: that is what a fix in days looks like.
Pay for the Skill, Not the Stripe
We already pay soldiers for perishable expertise. A linguist earns a Foreign Language Proficiency Bonus of up to $500 a month per language, and must retest every year to keep it. Nobody thinks that is strange. Russian is hard, and it fades.
So does firmware. Build a tiered certification for unmanned systems (repair, modify, program) and pay it monthly, with an annual retest, because the skill expires as fast as the drones do. The money does not need an act of Congress. Under 37 U.S.C. 353, a service Secretary can designate any skill as critical and pay up to $1,750 a month in skill incentive pay, or a proficiency bonus of up to $55,000 a year for certified proficiency. The authority is sitting on the shelf.
Then add the cheapest incentive in the Army's inventory: a badge. The 1953 committee that produced the specialist grades was worried about prestige, and prestige in the Army is worn on the chest. Anyone who has watched soldiers grind through an Expert Infantryman Badge lane knows what they will do for a piece of metal. An expert badge for unmanned systems, tested on build, fix and fly against the clock, would cost almost nothing and fill every off-duty hour in the brigade.
Recruit at the Bench
In June 2025, the Army commissioned four technology executives directly as reserve lieutenant colonels. Now do it at the other end of the org chart. Let a civilian FPV builder or embedded-systems engineer enlist as a Specialist Five instead of a private, on a skills test rather than a resume.
And stop leaving the best reservoir untapped. Thousands of Americans now build drones for a living. The Guard and Reserve can put them in uniform one weekend a month as technical specialists, carrying current industry skill into units without the Army having to match a Silicon Valley salary.
Give Them Permission and a Parts Budget
A specialist who can fix the drone but is not allowed to innovate is an expensive spectator. In April 2025 the Secretary's own Army transformation memo directed the service to "seek to include right to repair provisions in all existing contracts." Finish the job, then delegate the authority to modify and fly small systems down to brigade, so a fix written tonight does not wait months for a distant office to approve it.
Then give him money. The Army's UAS Marketplace, launched in March, has already cleared more than $750 million in sales, and it is adding components and software. Ukraine went further: drone units earn points for verified strikes and spend them on the Brave1 Market, a catalog of more than a thousand products. We do not need the kill leaderboard. We need the principle. Put a parts budget and a catalog in the hands of the battalion specialist, because the fix usually costs less than the paperwork.
Train the Whole Chain
Technical acumen cannot stop at the specialist. The lieutenant has to know what to ask for, and the battalion commander has to know when a twenty-year-old is telling him something he does not want to hear. Put a hands-on unmanned systems block in the officer basic and captains career courses. Send specialists to vendor factories through Training With Industry, and bring vendor engineers forward to battalion in return. Then rate commanders on how fast their formations close the loop.
For the Procurement Officer
Before you sign, ask one question: can a twenty-two-year-old with a screwdriver and a laptop legally open this, fix it and reflash it at two in the morning? If the answer is a field service rep and a ticket number, you did not buy a capability. You rented one. Price the technical data, the open interfaces and the soldier training as line items, and count how many of your fielded systems a Specialist Six could actually work on today.
The Investment Thesis
Your next customer is a Specialist Six. Buying power is already drifting down to the units, through marketplaces here and points in Ukraine. The company with the best drone of 2026 is a commodity supplier by 2027. The company the soldier chooses to learn on, train on and fix with is a platform. Discount revenue built on dependency, and pay up for iteration speed.
The Policy Wonk's Warning
The memo says plainly that the Department will need legislation for the command itself. When the FY2028 NDAA takes it up, Congress should do for adaptation what Nunn-Cohen did for special operations: a protected budget line, and a statutory charter that defines the mission as adaptation across the force, not ownership of a category of hardware. Most of the personnel fixes above need no new law at all. Congress's job is to ask why they have not happened yet.
My Take.
The fight over this command will happen in a document most people will never read. The 30-day plan must "identify measures of adaptation and Service adoption." That clause is where AUTOWARCOM is won or lost. If adaptation is measured in drones delivered, the command becomes a very expensive purchasing agent. Measure two numbers instead: days from a unit reporting a battlefield problem to a fix in its hands, and the count of soldiers in each formation certified to make that fix. Report both to Congress every quarter. Owen West and Max Strasiser built their reputations on speed. I suspect they would welcome being graded on it.
The Risk.
The specialist ranks went away for reasons. Old soldiers still tell stories about the Spec Five who drew sergeant's pay and could not, or would not, run a detail, and about the confusion over who was in charge when the sergeant went down. The bright line between technical authority and command answers most of that. Delegating authority to modify means some soldiers will break drones. That is the tuition, and it is cheaper than the alternative. The bigger risk is the one Hertling named: a new headquarters that adds a layer between the operator and the vendor. If the 30-day plan is mostly wiring diagram and very little soldier, believe him.
Conclusion
Hegseth told the room at Quantico that the English at Agincourt moved their fletchers close to the front to keep the arrows coming. The fletchers were not archers. They were tradesmen, kept near the line because the arrows ran out faster than anyone had planned. In a few weeks, the plan on the Secretary's desk will tell us whether we understood the story. Will we count drones, or will we count days, and the soldiers who make them shorter?The Cipher Brief is committed to publishing a range of perspectives on national security issues submitted by deeply experienced national security professionals. Opinions expressed are those of the author and do not represent the views or opinions of The Cipher Brief.
Have a perspective to share based on your experience in the national security field? Send it to Editor@thecipherbrief.com for publication consideration.
Read more expert-driven national security insights, perspective and analysis in The Cipher Brief
