Brennan Deveraux
14 min
As lethal autonomous weapons systems (LAWS) proliferate, current Department of War (DoW) policy remains overly focused on the technical characteristics of these systems and the terminal control of weapons after activation. This narrow focus creates an inaccurate narrative regarding human involvement. The author argues that humans are always in control of LAWS by virtue of designing them, tasking them with specific missions, and determining where and when they are used. To manage this emerging technology effectively, the DoW must move beyond development guidelines and adopt a human-centric framework that emphasizes the role of human judgment throughout the entire engagement process.
The proposed framework is built upon four pillars designed to provide clear, actionable guidance for military commanders:
The monograph applies this framework to three historical and speculative mission types: critical-target prosecution, protection, and terrain denial. By analyzing these missions, the author demonstrates that the US military has long utilized autonomous characteristics in weapons like mines and missile defense systems. The proposed framework allows the military to adapt these historical precedents to modern, more complex scenarios—such as aerial drone swarms—by ensuring that the machine acts as an extension of the commander’s intent rather than an independent actor.
Alex: [measured] It does, and the answer is to caution against defaulting to unnecessarily high release authority. The goal is to match authority level to the system's actual risk profile — the same logic already applied to artillery and scatterable mines. Keeping every decision at general-officer level isn't caution in this framing, it's a bottleneck that doesn't scale.
Sam: [probing] But what about a communications-degraded environment — the case this framework seems designed for? If the human can't intervene mid-mission, does "human-in-the-loop" mean anything at that point, or is it just a phrase left over from the old framing? [[RP_SECTION:accountability-and-mishap-reporting|Accountability and Mishap Reporting]]
Alex: [deliberate] That's where accountability does the real work. If a mishap occurs, the investigation doesn't stop at the machine — it traces the full employment chain, from the intelligence assessment that shaped the mission to the specific constraints the commander set beforehand. Deveraux is explicit that no weapon system is error-free, so the framework mandates a formal mishap database and after-action review, much like aviation safety reporting.
Sam: [thoughtful] So each engagement becomes a data point that feeds back into training and system design, rather than an isolated incident treated as a scandal.
Alex: [nodding] That's the underlying logic. It shifts the conversation away from abstract ethics — "should machines decide to kill" — toward a concrete, auditable record that can actually improve reliability across successive iterations. [[RP_SECTION:traceability-of-ethical-weight|Traceability of Ethical Weight]]
Sam: [leaning in, analytical] I want to press on one thing, though. Doesn't this just relocate the ethical weight rather than resolve it? You've moved judgment from the trigger to the mission-design phase, but someone's intent is still doing all the work — it's just earlier and less visible.
Alex: [even pace, measured] That's a fair read, and I don't think Deveraux would dispute it. The point isn't that the ethical weight disappears — it's that the current loop framework hides where that weight actually sits, which makes accountability nearly impossible to enforce. Naming the commander's intent as the locus of judgment, and building certification and reporting structures around it, at least makes the responsibility traceable.
Sam: [summarizing] So the actual bottleneck isn't the machine's decision-making at all. It's the absence of a standardized, enterprise-wide framework to authorize and audit that decision-making.
Alex: [concluding] That's the core of it. Without a formal mishap database and clear reporting procedures, the military is operating in a vacuum of accountability — and it's that vacuum, not the autonomy itself, that invites the policy failures everyone's actually afraid of.
Sam: [reflective] It's a more scalable way to think about this than the ethics-first framing usually allows. It turns a philosophical debate into something closer to actionable doctrine.
Alex: [measured] The open question the paper leaves for later work is how robust this reporting and feedback loop stays as systems operate in increasingly communications-degraded environments — record-keeping itself gets harder to guarantee exactly when you'd need it most.
Sam: [concluding] Worth keeping an eye on as the framework moves from monograph to actual policy. Thanks for walking through it.