<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Topic:fallback modes &#8212; Global Security Review %</title>
	<atom:link href="https://globalsecurityreview.com/subject/fallback-modes/feed/" rel="self" type="application/rss+xml" />
	<link>https://globalsecurityreview.com/subject/fallback-modes/</link>
	<description>A division of the National Institute for Deterrence Studies (NIDS)</description>
	<lastBuildDate>Thu, 05 Nov 2026 11:53:37 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.8</generator>

<image>
	<url>https://globalsecurityreview.com/wp-content/uploads/2026/05/cropped-GSR-Chrome-Logo-2026-1-32x32.png</url>
	<title>Topic:fallback modes &#8212; Global Security Review %</title>
	<link>https://globalsecurityreview.com/subject/fallback-modes/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>When Human Approval Fails: Runtime Authority Governance for Autonomous Deterrence</title>
		<link>https://globalsecurityreview.com/when-human-approval-fails-runtime-authority-governance-for-autonomous-deterrence/</link>
					<comments>https://globalsecurityreview.com/when-human-approval-fails-runtime-authority-governance-for-autonomous-deterrence/#respond</comments>
		
		<dc:creator><![CDATA[Burak Oktenli]]></dc:creator>
		<pubDate>Thu, 05 Nov 2026 13:09:47 +0000</pubDate>
				<category><![CDATA[AI & Deterrence]]></category>
		<category><![CDATA[Archive]]></category>
		<category><![CDATA[Strategic Adversaries]]></category>
		<category><![CDATA[AI assurance]]></category>
		<category><![CDATA[audit records]]></category>
		<category><![CDATA[authorization validity]]></category>
		<category><![CDATA[autonomous deterrence]]></category>
		<category><![CDATA[autonomous weapons]]></category>
		<category><![CDATA[command authority]]></category>
		<category><![CDATA[context-aware authorization]]></category>
		<category><![CDATA[degraded communications]]></category>
		<category><![CDATA[developmental testing]]></category>
		<category><![CDATA[engagement control]]></category>
		<category><![CDATA[escalation management]]></category>
		<category><![CDATA[fallback modes]]></category>
		<category><![CDATA[human authorization]]></category>
		<category><![CDATA[human judgment]]></category>
		<category><![CDATA[independent control mechanisms]]></category>
		<category><![CDATA[military artificial intelligence]]></category>
		<category><![CDATA[mission limits]]></category>
		<category><![CDATA[preauthorized rules]]></category>
		<category><![CDATA[real-time monitoring]]></category>
		<category><![CDATA[runtime authority governance]]></category>
		<category><![CDATA[sensor evidence]]></category>
		<category><![CDATA[strategic deterrence]]></category>
		<guid isPermaLink="false">https://globalsecurityreview.com/?p=33177</guid>

					<description><![CDATA[<p>Published:  November 5, 2026 A commander approves an autonomous defensive engagement while the target is inside an authorized area. Two seconds later, before the system acts, an allied aircraft enters the area, or the target moves beyond the permitted boundary. The approval is genuine, but does it still authorize the action?   This is a hypothetical [&#8230;]</p>
<p><a href="https://globalsecurityreview.com/when-human-approval-fails-runtime-authority-governance-for-autonomous-deterrence/">When Human Approval Fails: Runtime Authority Governance for Autonomous Deterrence</a> was originally published on <a href="https://globalsecurityreview.com">Global Security Review</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><i><span data-contrast="none">Published:</span></i><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}">  November 5, 2026</span></p>
<p><span data-contrast="none">A commander approves an autonomous defensive engagement while the target is inside an authorized area. Two seconds later, before the system acts, an allied aircraft enters the area, or the target moves beyond the permitted boundary. The approval is genuine, but does it still authorize the action?</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span></p>
<p><span data-contrast="none">This is a hypothetical sequence, not a documented battlefield failure. It exposes a neglected distinction in military artificial intelligence (AI). Recording a human decision is different from ensuring that the decision remains valid when an autonomous system carries it out.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span></p>
<p><span data-contrast="none">The timing matters because military AI is moving closer to consequential decisions. The </span><a href="https://media.defense.gov/2026/Jan/12/2003855671/-1/-1/0/ARTIFICIAL-INTELLIGENCE-STRATEGY-FOR-THE-DEPARTMENT-OF-WAR.PDF"><span data-contrast="none">January 2026 Department of War AI strategy</span></a><span data-contrast="none"> calls for AI-enabled battle management and decision support, while the </span><a href="https://www.af.mil/Portals/1/documents/2026SAF/DAF_AI_Strategy_Endorsed_20260417.pdf"><span data-contrast="none">Air Force AI strategy</span></a><span data-contrast="none"> seeks shorter sensor-to-shooter timelines. The </span><a href="https://www.whitehouse.gov/presidential-actions/2026/06/national-security-presidential-memorandum-nspm-11/"><span data-contrast="none">June national security AI memorandum</span></a><span data-contrast="none"> emphasizes the chain of command and orders updated autonomy guidance. NATO&#8217;s </span><a href="https://www.nato.int/en/about-us/official-texts-and-resources/official-texts/2026/01/13/alliance-digital-strategy"><span data-contrast="none">2026 digital strategy</span></a><span data-contrast="none"> likewise calls for integrating sensor-to-effector data flows and building federated platforms for allied collaboration.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span></p>
<p><span data-contrast="none">None of these strategy documents requires proof that a deployed weapon has been given authority. Instead, they focus on urgency. How can forces accelerate legitimate action without allowing yesterday&#8217;s permission to survive the facts that justified it?</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span></p>
<p><span data-contrast="none">Human judgment can fail at a seam between the decision and its execution. An operator might authorize a particular defensive action based on a target classification, a geographic limit and evidence that friendly forces are clear. If the conditions change while the action is pending, software that checks only whether an approval flag exists may treat obsolete authorization as current.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span></p>
<p><span data-contrast="none">A digital signature can authenticate the credential used to approve an instruction. It cannot, by itself, establish that the relevant sensor evidence, rules, or mission limits have not changed since approval. An accurate model prediction does not answer that authorization question either.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span></p>
<p><span data-contrast="none">The author&#8217;s own bounded formal analysis, using the </span><a href="https://cs.lmu.edu/~ray/notes/temporallogic/"><span data-contrast="none">Temporal Logic of Actions</span></a><span data-contrast="none">, illustrates this failure path in notional authority designs. Confirmation remains recorded while a material change invalidates the conditions behind it. Requiring the approval to remain tied to the current context removes that particular modeled violation. This is a result inside a constructed specification, not evidence that actual military control software contains the same weakness.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span></p>
<p><span data-contrast="none">The public </span><a href="https://www.esd.whs.mil/portals/54/documents/dd/issuances/dodd/300009p.pdf"><span data-contrast="none">autonomy-in-weapons directive</span></a><span data-contrast="none"> already provides a policy foundation. It requires appropriate human judgment and expects covered systems to remain within authorized time, geographic and operational limits. When that is not possible, the directive calls for termination of the engagement or additional operator input, as applicable. A force that cannot conduct authorized defense quickly invites doubts about its ability to protect allies. A force that conducts an engagement after its permission has become invalid invites a different doubt. It questions  whether commanders can still control escalation. Credible deterrence requires capability and restraint to control escalation, not speed at the expense of either. This is particularly consequential during a conventional confrontation involving nuclear-armed powers. A mistimed or misdirected engagement could be interpreted as deliberate escalation before either side has a reliable explanation. The hazard does not require AI to command nuclear weapons, and nothing in this argument claims that it does.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span></p>
<p><span data-contrast="none">Requiring a fresh human click after every minor change would be an equally poor answer. Some time-critical defensive actions may need to continue under preauthorized rules, and stopping every function can be unsafe. The real requirement is to distinguish changes that are harmless within the authorized mission from changes that invalidate the basis for a consequential action.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span></p>
<p><span data-contrast="none">First, acquisition requirements should define which facts an approval covers. An authorization should refer to an identifiable action and its permitted conditions, including the relevant mission limits and evidence requirements. A material change must trigger a new authorization decision, while changes already covered by preauthorized rules can be managed locally.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span></p>
<p><span data-contrast="none">Second, enforcement cannot depend on an AI model promising to remember those limits. An independently testable control mechanism should keep proposed actions inside the permitted scope. Under degraded communication, the system should retain only the functions that remain both necessary and authorized, with a mission-specific fallback rather than an automatic universal shutdown.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span></p>
<p><span data-contrast="none">Third, testers should challenge the gap between approval and execution. In an isolated test environment, change a relevant condition after approval, delay verification, interrupt communications and restore them. Assess whether the system rejects actions no longer justified, avoids repeated switching between modes, and records enough evidence to explain its choice.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span></p>
<p><span data-contrast="none">The </span><a href="https://www.cto.mil/wp-content/uploads/2025/02/TE_of_AIES_Guidebook_Final_26Feb25.pdf"><span data-contrast="none">2025 defense developmental testing guidebook</span></a><span data-contrast="none"> already calls for examining real-time monitoring, dependable fallback and reliability switching back from a safer alternate. The added acquisition question is whether authorization remains valid precisely when an action would take effect. Test reports should record both improper actions allowed and legitimate actions unnecessarily blocked. The record should show what was proposed, which conditions supported approval, what changed and why the action proceeded or stopped. Such a record helps commanders and investigators assess a decision. It cannot, by itself, establish that an engagement was lawful or strategically wise.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span></p>
<p><span data-contrast="none">A military can possess fast autonomous weapons and still lose control of a decision made seconds earlier. Deterrence improves when machines can demonstrate that the conditions behind a human decision still hold beyond recording that someone once said it.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span></p>
<p><i><span data-contrast="none">Burak Oktenli is an independent researcher based in Washington, DC, and is pursuing a Master of Professional Studies in Applied Intelligence at Georgetown University. He studies military AI assurance, autonomous command authority, and deterrence. His analysis has appeared in Global Security Review, RealClearDefense, RUSI and the Modern War Institute at West Point. Views expressed in this article are the author&#8217;s own.</span></i><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}"> </span></p>
<p><a href="http://globalsecurityreview.com/wp-content/uploads/2026/11/When-Human-Approval-Fails-Runtime-Authority-Governance-for-Autonomous-Deterrence.pdf"><img decoding="async" class="alignnone wp-image-32906 size-full" src="http://globalsecurityreview.com/wp-content/uploads/2026/07/@-Download-Button-2026.png" alt="" width="250" height="80" /></a></p>
<p><a href="https://globalsecurityreview.com/when-human-approval-fails-runtime-authority-governance-for-autonomous-deterrence/">When Human Approval Fails: Runtime Authority Governance for Autonomous Deterrence</a> was originally published on <a href="https://globalsecurityreview.com">Global Security Review</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://globalsecurityreview.com/when-human-approval-fails-runtime-authority-governance-for-autonomous-deterrence/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
