The moral question is not whether a machine can aim.
AI in warfare includes logistics, intelligence analysis and systems involved in applying force. These uses differ sharply. A tool that predicts maintenance needs does not raise the same immediate questions as a weapon that selects and engages targets without further human intervention.
This original dialogue features fictional speakers: Rowan, a military planner, and Leila, a humanitarian-law researcher. It is an ethical analysis, not operational targeting guidance or a verbatim exchange with ChatGPT. The argument concerns human control, legal responsibility and the evidence needed before claims of improved protection can be trusted.
Speed is a benefit only inside justified limits.
Automation can reduce some human errors. A system does not tire in the same way as a person, and fast defensive responses can matter when threats develop quickly. It would be wrong to reject a protective technology merely because the mechanism is computational.
It would also be wrong to infer protection from speed alone. Distinguishing lawful targets and assessing civilian harm depend on context. A system can be consistent about the wrong classification. The central question is whether humans can understand and constrain the use of force in the circumstances where it will occur.
Then evaluate the specific system and environment. A tightly bounded defensive task differs from open-ended operation among civilians. We should compare realistic alternatives, including the errors people make, rather than compare an imperfect machine with an imaginary flawless human.
Agreed about realistic comparisons. But “better on average” is insufficient when failures are unpredictable or responsibility is blurred. The ICRC recommends ruling out unpredictable autonomous weapon systems and systems designed or used to target people, while constraining others.[1] Those are its policy recommendations, not a statement that a single new global treaty has already settled every issue.
Human control is a chain of decisions
- 01
Before use
Authorization specifies the task, limits, evidence requirements and approval authority. - 02
During operation
Effective intervention requires sufficient understanding, time and practical authority. - 03
When conditions change
Changed conditions test whether the system stops or remains within authorized limits. - 04
After an incident
Records support investigation of decisions and identification of responsible actors.
Responsibility cannot be delegated to an output.
A commander should not be allowed to say “the model decided” as if that ends the inquiry. Procurement, testing, authorization and operational choices remain human decisions. Records must show what people were told about limitations and whether deployment respected them.
And the interface must not turn human approval into a ritual. If the operator has too little time or information to assess a recommendation, a button press may offer the appearance of judgment without its substance. The ICRC and SIPRI study of human control examines these relationships among the system, task and environment.[2]
Then some uses may be unacceptable even when the technology is impressive. We need restrictions that survive pressure for tempo and scale. A narrower authorization can be more credible than a broad promise that a human is always “in the loop.”
That is the point of the distinction. A responsible debate can recognize potential defensive benefits while requiring evidence, legal assessment and meaningful constraints. The humanitarian burden is not satisfied by a demonstration or a claim that rivals are moving faster.
The race can delegate the decision before anyone votes to.
A state can reasonably worry that slower decisions leave it vulnerable to a rival. A supplier can reasonably worry that stricter limits cost it a contract. Those incentives can push each participant toward greater delegation even when all would prefer a less dangerous contest. That is a collective-action problem, not proof that every new capability must be deployed.
And the steering starts upstream. UNIDIR’s 22 October 2026 commentary emphasizes how developers and integrators shape data, testing and autonomy long before use, while states retain their responsibilities.[3] An officer's final approval cannot repair every choice embedded in a supplier's system. Ask who can inspect an update, reject a change or maintain a workable alternative.
The strongest case for AI is therefore bounded: a specific use might improve protection compared with realistic alternatives. The skeptical case is strongest when decision speed outruns comprehension, several institutions depend on the same opaque judgment, or a supplier becomes too essential to challenge. These are warning signals to investigate, not measured rates of escalation.
UNIDIR’s 19 October 2026 strategy guidelines address the institutional work of developing, implementing and reviewing a national approach.[4] Guidelines and voluntary frameworks are not a newly binding global treaty. Their value depends on whether authorities can demand evidence and enforce meaningful limits when competition makes doing so costly.
Sources & further reading
Follow the evidence.
- 01ICRC position on autonomous weapon systems
12 May 2021 position; policy recommendations distinguished here from existing treaty law.
- 02ICRC & SIPRI: Limits on Autonomy in Weapon Systems
2020 analysis of human control, the task and the operating environment.
- 03UNIDIR: Industry responsibility in developing military AI
22 October 2026 commentary on upstream technical choices, private-sector responsibility and state obligations.
- 04UNIDIR: Guidelines for a National Strategy on AI in Security and Defence
19 October 2026 institutional guidelines; guidance rather than a new binding global treaty.
