Evidence-Carrying Mission Admission Contracts for Natural-Language UAV Task Submission

Highlights

What are the main findings?

• EAMSR turns natural-language UAV task submission into an auditable mission-admission decision.
• Unwarranted ADMIT decisions are eliminated on EAMSR-Bench; remaining errors stay outside direct admission.

What are the implications of the main finding?

• LLM-generated UAV missions should be governed as candidates, not trusted as ready-to-plan specifications.
• Pre-execution admission creates a verifiable handoff before downstream UAV planning and runtime safety layers.

Abstract

Natural-language interfaces now influence mission generation in UAV planning pipelines, where a feasible plan may still rest on unsupported completions, unauthorized relaxations, or consequence-changing repairs. We present EAMSR, an evidence-carrying Mission Admission Contract framework that treats a submitted mission as an admission contract, not a text-to-specification output. A large language model proposes candidate clauses and bounded refinements but does not decide admission; the governance layer links hard clauses to evidence and authorized sources, isolates unsupported semantic increments, checks mission-consequence compatibility, and accepts only candidates with a backend task-level witness. The final decision (ADMIT, CLARIFY, or REJECT) carries an audit trail linking language anchors to governance and backend outcomes; backend search failures that do not establish model-level infeasibility return CLARIFY, not REJECT. On EAMSR-Bench (120 tasks, six scenarios, six risk types), EAMSR achieves 100.0% binary admission accuracy ($Ac{c}_{\mathrm{bin}}$) and 93.3% three-class accuracy ($Ac{c}_{\mathrm{adm}}$), with no unwarranted ADMIT decisions among 78 non-admissible cases (0/78; 95% Clopper–Pearson upper bound, 3.8%); residual errors lie on the CLARIFY–REJECT boundary. On an independent external test set (48 tasks), EAMSR achieves 89.6% three-class and 100.0% binary accuracy with no unwarranted admissions. A deterministic non-LLM variant using the same governance and backend layers also attains zero unwarranted admissions but lower accuracy, indicating that LLM generation improves semantic coverage while governance and backend checks determine admission. The evaluation is limited to pre-execution mission admission under stated assumptions and does not constitute flight-safety assurance.

1. Introduction

Natural-language interfaces have moved beyond auxiliary interaction in UAV systems; they now participate in the mission-generation chain. Once a language input is fixed as a task condition, an interpretation error propagates into the planning process. An unsupported completion becomes a pre-execution mission assumption, not just a textual deviation. Natural-language UAV task submission requires an admission decision, beyond semantic parsing alone.

Existing studies have made natural-language task requests structurally expressible. Transformations from language to task specifications, temporal logic, or planning models give raw requests checkable forms [1,2,3,4,5,6,7,8,9,10,11], but a structured output is not automatically admissible. Planner diagnosis and specification repair can show that a modified task has a feasible plan [12,13,14,15,16,17,18], yet the existence of a plan does not supply missing evidence, authorize constraint relaxation, or prevent consequence-changing repairs from concealing semantic shifts. Safety gates can block dangerous actions or unacceptable plans before execution [19,20,21,22,23,24,25,26], but they operate on transformed artifacts rather than on the clause-formation process, so a plan that passes safety checks may still contain unsupported hard clauses, unauthorized relaxations, or unresolved consequence changes. Translation correctness, planning feasibility, and operational safety each address part of the chain, but none implies admission integrity.

This requirement calls for a decision object distinct from text, specifications, and plans: one that places clause provenance, evidence status, modification authority, mission consequences, and backend executability within a single admission context [27,28,29,30]. We define this object as a Mission Admission Contract (MAC): an auditable admission commitment before a task enters the planning chain, not a replacement for translators, planners, or safety gates. We propose EAMSR, an Evidence-Carrying Mission Admission Contract framework built on the MAC. EAMSR restricts the LLM to generating candidate clauses and bounded refinement suggestions, while placing admission responsibility in the governance layer and the backend task model. An ADMIT decision requires evidence, authority, consequence, and backend-witness checks, not merely a well-formed LLM specification; requests whose admission conditions cannot be closed are returned as CLARIFY or REJECT with an audit trail.

The contributions of this paper are as follows.

First, we formulate natural-language UAV task submission as mission admission and introduce the MAC as an evidence-carrying admission object that makes clause provenance, evidence status, and modification authority preconditions for entering the planning chain.

Second, we develop a conjunctive admission architecture that separates untrusted candidate generation from evidence, authority, consequence, and task-level witness verification, so that unverified semantic increments and unauthorized relaxations cannot silently become hard mission obligations.

Third, we establish a controlled evaluation protocol covering binary admission correctness, three-class remediation decisions, mechanism diagnostics, external-authoring robustness, and backend consistency.

The scope of this paper is bounded between task submission and task planning. The claims hold under stated assumptions: given a valid trusted context, governance policy, evidence base, and backend task model, EAMSR enforces the specified admission conditions before tasks enter the planning chain.

2. Related Work

Prior work on natural-language UAV interaction has addressed three stages of the mission-generation chain: language-to-specification translation, plan repair, and pre-execution safety gating. Existing studies can derive mission regions, waypoints, and constrained paths from compound commands [1], and can connect LLM planning to mission orchestration pipelines that include authentication and human approval [7,11,31]. Authentication confirms the requesting subject, and human approval can confirm a final proposal, but neither explains how task clauses in the proposal are formed from the original instruction. The key question is whether a model-transformed task request has admission integrity before entering the planning chain.

Formal translation and symbolic planning improve the checkability of task requests but do not by themselves prove admission integrity [5,8,32,33,34,35]. Their decision object is specification correctness: nl2spec provides span-level traceability for translation revision [2]; ClarifySTL identifies underspecified requirements without deciding whether alternative completions change mission consequences [3]; SPAR constructs PDDL planning models for operator requests, not for admission decisions [4]. Planner-based repair methods such as DUPLEX and UAV-NL-STL-Repair restore executability through diagnosis or MILP feedback [12,13], but traceability, formal completeness, and replannability do not authorize clause modification: unsupported semantic increments and repairs that cross consequence-compatibility sets can still produce executable but inadmissible missions.

Operational safety methods adopt a different decision object: whether a final command or plan is dangerous, feasible, or rule-compliant. SafeGate adjudicates safety before code generation [19]; RoboGuard enforces temporal-logic guardrails on LLM plans [20]; UAV-specific studies verify spatial, environmental, and operational constraints through probabilistic models and rule-based verification [21,22]; complementary guardrails and verification frameworks for LLM-driven robots address related checks [16,19,20,23,24,25,26,36]. Because these methods operate on transformed artifacts, a plan that passes safety checks may still contain unsupported completions or unauthorized relaxations.

Assume–guarantee and contract-based approaches refine and repair unrealizable robotic mission specifications [37,38,39,40,41], but their starting point is an already formalized and trusted specification, and none targets natural-language grounding or admission-level evidence tracing. What remains missing is a joint admission decision over evidence and authority, untrusted-increment isolation, consequence compatibility, and backend executability.

Table 1 and Table 2 compare EAMSR with the most closely related methods across ten capability dimensions and delineate conceptual boundaries between EAMSR components and prior concepts, focusing on specific systems.

Table 1. Comparison of EAMSR with closely related methods across ten capability dimensions. “Not addressed” indicates that the dimension is not explicitly modeled or tracked by the method.

Dimension	nl2spec	SafeGate	DUPLEX	CROME	EAMSR
NL grounding	Text-to-spec translation	Safety check on generated code	Repair of infeasible specs	Refinement of formal specs	Anchor extraction from NL
Clause provenance	Span-level trace	Not addressed	Not addressed	Assumed from formal input	Source-class tagged per clause
Evidence status	Not addressed	Not addressed	Not addressed	Not addressed	Three-valued (Y/N/U) with authority and freshness
Authority	Not addressed	Not addressed	Not addressed	Not addressed	Five-level hierarchy with delegation
Mutability	Not addressed	Not addressed	Not addressed	Contract-based refinement	Five-mode taxonomy (immutable to revocable)
Ambiguity handling	Translation revision	Plan rejection	Diagnosis-based repair	Contract refinement	CLARIFY with remediability test
Semantic preservation	Spec correctness	Safety constraint satisfaction	Executability restoration	Assume–guarantee refinement	Non-transitive consequence compatibility
Backend executability	Not addressed	Not addressed	Planner-based repair	Not addressed	Task-level plan witness
Audit output	Translation trace	Safety verdict	Repair log	Refinement history	Full admission audit trail
UAV-specific validation	Domain-agnostic	Robotic systems	UAV missions	Robotic missions	UAV ontology and backend model

Table 2. Conceptual boundaries between EAMSR components and related prior concepts.

EAMSR Component	Related Prior Concept	Essential Distinction
Mission Admission Contract (MAC)	Assurance case/proof-carrying artifact	Assurance cases provide structured argument–evidence reasoning that a system is safe, whereas a MAC records whether a specific mission request satisfies admission conditions before planning.
Proof-obligation gate	Policy-based authorization	Policy engines check access permissions, whereas the gate also requires clause-level evidence, mutability compliance, and untrusted-semantic-isolation checks.
Backend witness	Standard plan validation	Plan validation verifies that a plan satisfies a specification, whereas the witness closes executability only after clause governance and consequence compatibility have been established.
Mission-consequence compatibility	Semantic-preserving specification refinement	Semantic preservation requires preserving a specified logical or behavioral relation, whereas compatibility is a non-transitive tolerance relation that permits bounded changes in non-critical dimensions while vetoing changes in critical ones.
Evidence-carrying clauses	Provenance-tracked requirements	Provenance records where a clause came from, whereas evidence-carrying clauses also require that each hard clause be supported by admissible evidence with verified authority and freshness.

Principal methodological novelty. Among the methods directly compared in Table 1, none exposes all of these elements as first-class admission variables. The principal novelty of EAMSR is the integration of these mechanisms into a single conjunctive admission predicate for natural-language UAV task submission. The MAC representation adapts provenance-tracked specification concepts; the proof-obligation gate extends policy-based authorization with evidence, authority, mutability, and untrusted-isolation checks; the authority-bounded refinement relation builds on assume–guarantee contract refinement; the mission-consequence compatibility mechanism is a task-level analog of semantic-preserving specification refinement; and the backend plan witness is a task-level analog of plan validation. Each individual component has precedent in prior work, but their conjunctive combination for natural-language UAV mission admission is new.

Table 2 delineates five conceptual boundaries that clarify what each EAMSR component is and what it is not, relative to the closest prior concept.

3. Materials and Methods

Natural-language UAV task submission faces three admission risks: operator ambiguity or infeasible requirements, LLM-introduced unsupported assumptions, and missions that appear reasonable at the language level while violating backend constraints. To address these risks, we propose EAMSR, an evidence-carrying Mission Admission Contract framework for natural-language UAV task submission. EAMSR instantiates a natural-language mission instruction as a Mission Admission Contract (MAC), and performs evidence tracing, authority checking, untrusted semantic increment isolation, mission-consequence screening, and backend plan-witness checking before the task enters the planning chain [27,28,29,30,38]. Figure 1 shows the overall framework architecture and decision flow.

Figure 1. Overview of the EAMSR framework. Natural-language UAV mission requests are instantiated as evidence-carrying Mission Admission Contracts (MACs). A governance proof-obligation gate enforces evidence, authority, mutability, and untrusted-semantic-isolation checks; governance-admissible candidates are screened through mission-consequence compatibility; a backend plan witness closes the selected candidate. Final admission requires all three stages.

The system output is

$$decision\in \{\mathrm{ADMIT},\mathrm{CLARIFY},\mathrm{REJECT}\}.$$

(1)

ADMIT means the task request has formed an admission contract satisfying evidence, authority, consequence, and backend-witness requirements; CLARIFY means that ambiguity may change operational consequences, that an operator-authorized modification is required, or that backend closure remains inconclusive; REJECT means the request conflicts with an immutable or protected condition, or that task-level infeasibility is conclusively established, within the currently declared trusted context, governance policy, and backend model (Section 3.5).

3.1. Mission Admission Contract and Trust Boundary

A natural-language mission instruction in a UAV scenario is a joint request over system capability, safety boundaries, and mission consequences. We first define the Mission Admission Contract to clarify the boundary among the operator request, trusted environment, protected constraints, and system admission responsibility.

Let the operator’s natural-language mission instruction be $x\in {\mathcal{X}}_{\mathrm{NL}}$. The instruction may contain mission objectives, target areas, observation windows, execution order, payload requirements, communication-return requirements, soft preferences, and abort conditions. EAMSR constructs a base Mission Admission Contract $C_0$ from x:

$$C_0=⟨A_{\mathrm{ctx}},I_{\mathrm{prot}},G_{\mathrm{req}},\mathrm{\Gamma },\mathcal{E},{\mathrm{\Omega }}_{\mathrm{UAV}}⟩.$$

(2)

In this definition, $C_0$ is the base contract derived from the original instruction; $A_{\mathrm{ctx}}$ denotes the trusted UAV context, including the UAV capability model, initial state, mission environment, map, target locations, weather, communication coverage, time windows, and payload status. $I_{\mathrm{prot}}$ denotes protected operational invariants, including return reserves, no-fly zones, geofences, altitude limits, payload limits, operating rules, and emergency-abort conditions. $G_{\mathrm{req}}$ denotes the mission-request obligations proposed by the natural-language instruction. $\mathrm{\Gamma }$ denotes the governance policy, including source verification, authority levels, and mutability rules. $\mathcal{E}$ denotes the evidence base, including text anchors, trusted context facts, protected constraints, and system default rules. ${\mathrm{\Omega }}_{\mathrm{UAV}}$ denotes the UAV task-level backend model. Candidate contracts $C_i$ (Equation (15)) are generated from $C_0$ by the LLM and form the candidate set $\mathcal{C}=\{C_1,\dots ,C_m\}$ where $m\le B_c$, as duplicate candidates are discarded (Section 3.2).

When admission succeeds, the system selects a contract $C^{\ast }$ and extracts its admitted mission obligations $G^{\ast }=G\left(C^{\ast }\right)=⟨H^{\ast },S^{\ast },P^{\ast }⟩$, where $H^{\ast }$ denotes the hard goals and hard constraints, $S^{\ast }$ the soft preferences, and $P^{\ast }$ the pending clauses. A task-level plan witness $\pi$ must satisfy the hard obligations:

$$\pi \vDash A_{\mathrm{ctx}}\wedge I_{\mathrm{prot}}\wedge H^{\ast }\wedge {\mathrm{\Omega }}_{\mathrm{UAV}}.$$

(3)

Soft preferences influence candidate selection (Equation (32)) but are not backend proof obligations; pending clauses cannot enter $H^{\ast }$ and therefore do not affect witness closure. $P^{\ast }$ is retained in the selected contract and audit trail for completeness but does not constitute a downstream obligation; any pending clause with consequence relevance must trigger CLARIFY before admission can proceed. The EAMSR admission objective is defined as

$$x⟼C⟼(G^{\ast },\pi ,decision),$$

(4)

subject to

$$decision=\mathrm{ADMIT}\Rightarrow \mathrm{AdmissionReady}(C^{\ast },{\mathcal{C}}_{\mathrm{gov}})=1\wedge Witness(C^{\ast },\pi )=1.$$

(5)

The trust boundary of EAMSR is limited to the pre-execution admission layer between task submission and task planning. This layer handles task goals, spatial regions, time windows, payloads, communication, energy, return reserves, restricted airspace, and abort conditions. Low-level path planning, continuous obstacle avoidance, flight control, and runtime safety monitoring are delegated to downstream execution modules.

3.2. Contract Instantiation for Natural-Language Mission Requests

The first admission risk of natural-language UAV tasks arises from semantic grounding. A single instruction may contain goals, regions, time constraints, payload requirements, and communication requirements. These contents fall into three categories: evidence-supported, clarification-required, and LLM-introduced completions. Contract instantiation converts the natural-language request into clause-level, evidence-carrying, and auditable candidate mission obligations.

EAMSR extracts requirement anchors from the instruction x:

$$\mathcal{A}=\{a_1,a_2,\dots ,a_n\}.$$

(6)

Each anchor $a_i$ is a text span with independent mission meaning. The extraction procedure operates in four steps: (i) span detection segments the instruction at linguistic boundaries (clauses, conjunctions, conditionals) to identify candidate spans; (ii) ontology slot assignment maps each span to a clause type in the UAV ontology (temporal, spatial, communication, payload, etc.); (iii) modality identification labels each span as hard, soft, optional, or conditional based on linguistic cues (imperative, “if possible”, “as needed”); (iv) validation checks whether each span has a clear referent in $A_{\mathrm{ctx}}$ and a deterministic ontology relation. All four steps use deterministic linguistic rules and ontology lookups; no LLM is involved in anchor extraction. Anchor extraction is implemented deterministically and is treated as trusted preprocessing in the present evaluation; extraction correctness is therefore an explicit assumption. Spans that fail validation (e.g., vague referents, unresolved negation scope, or cross-clause dependencies without explicit conjunction) are marked as pending and excluded from clause generation. This procedure prevents the LLM from interpreting its own completions as user-confirmed requirements.

Under the UAV mission ontology ${\mathcal{O}}_{\mathrm{UAV}}$ and trusted context $A_{\mathrm{ctx}}$, the LLM generates one candidate contract clause for each validated anchor:

$${\kappa }_i={\mathrm{LLM}}_{\theta }(a_i,{\mathcal{O}}_{\mathrm{UAV}},A_{\mathrm{ctx}}).$$

(7)

The set of all candidate clauses for a single generation pass is denoted $\mathcal{K}=\{{\kappa }_1,{\kappa }_2,\dots ,{\kappa }_n\}$, where n is the number of validated anchors.

To produce multiple candidate contracts, EAMSR performs up to $B_c$ repeated LLM invocations under the same decoding settings. In the evaluated configuration, temperature is 0; candidate variation therefore arises only from residual model-serving nondeterminism or alternative structured assignments returned for ambiguous anchors. Each invocation generates a complete clause set ${\mathcal{K}}^{\left(b\right)}$ from the same anchor set $\mathcal{A}$; the clause sets are then assembled into candidate mission obligations $G_i$ and candidate MACs $C_i$ (Equations (14) and (15)). The resulting candidate set is $\mathcal{C}=\{C_1,\dots ,C_m\}$, where $m\le B_c$. Each generation attempt consumes one unit of the candidate budget $B_c$; duplicate candidates (identical clause sets) are detected by hash comparison, discarded, and recorded in the audit trail. Consequently, the final candidate set satisfies $0\le \left|\mathcal{C}\right|\le B_c$ (the lower bound is reached only if all generation attempts produce unparseable responses, which triggers $decision\leftarrow \mathrm{CLARIFY}$), and the total number of LLM invocations remains bounded by $B_c+B_r$ (Property 4). In the evaluated configuration, $B_c=5$ was selected based on a pilot study on a separate 20-task development subset: increasing $B_c$ beyond 5 yielded diminishing returns in coverage (fewer than 2% additional governance-admissible candidates), while $B_c<3$ occasionally left no governance-admissible candidate for tasks where a single LLM pass produced an incompatible clause assignment. A candidate clause is defined as

$$\kappa =⟨id,anchor,type,\varphi ,mode,source,evidence,authority,mutability,trust⟩.$$

(8)

The fields are as follows: $id$ is the clause identifier; $anchor$ is a text anchor or trusted-context pointer; $type$ is the UAV clause family; $\varphi$ is the formal task semantics; $mode$ is hard, soft, optional, default, or pending; $source$ is the source category; $evidence$ is the evidence pointer; $authority$ is the authority level; $mutability$ is the allowed modification mode; and $trust$ is the trust status.

The $source$ field classifies the origin of each clause into five categories (Table 3), which determines its default authority level and mutability. User-explicit clauses carry the highest authority among user-originated sources, but remain subordinate to applicable regulatory constraints and are treated as immutable hard intent unless the user authorizes modification. When the user subsequently authorizes a modification to a previously immutable user-explicit clause, this authorization creates a new authoritative anchor (an updated request version) rather than retroactively mutating the original clause; the original clause is preserved in the audit trail, and the refined contract carries the new anchor with the user’s explicit authorization. Clauses derived from trusted context (e.g., weather data, airspace maps, vehicle specifications) inherit the authority of their source. Clauses introduced by the LLM during candidate generation or repair are labeled as hypothetical and must be verified before entering hard obligations.

Table 3. Clause source categories, default authority, and mutability.

Source	Description	Default Mutability
user_explicit	Directly stated in the user instruction	immutable (hard)
user_implied	Inference from user instruction via deterministic ontology rule	protected (hard)
trusted_context	Derived from trusted context data	governance-defined
system_default	Applied when user input is silent on a parameter	overridable
llm_generated	Introduced by the LLM during candidate generation or repair	revocable

A clause $\kappa$ may be labeled $user\_implied$ only if it can be derived from an explicit anchor $a_i$ and a deterministic ontology rule $r\in {\mathcal{R}}_{\mathrm{ontology}}$:

$$source\left(\kappa \right)=user\_implied\Rightarrow \exists a_i,r\in {\mathcal{R}}_{\mathrm{ontology}}:a_i\wedge r\vDash \kappa .$$

(9)

If no such derivation exists, the clause is labeled $llm\_generated$ with trust $hypothetical$, preventing unsupported LLM completions from hardening into protected obligations.

The evaluated UAV ontology ${\mathcal{O}}_{\mathrm{UAV}}$ contains 8 clause families (Table 4), 42 normalized predicate templates, 15 relation types (including temporal precedence, spatial containment, resource dependency, and authority delegation), and 6 entity types (vehicle, waypoint, region, sensor, payload, communication node). The deterministic ontology rules ${\mathcal{R}}_{\mathrm{ontology}}$ used for $user\_implied$ derivation comprise 28 rules, each expressed as a Horn-clause implication over the predicate vocabulary. The full ontology specification and rule set are available in the reproducibility package.

Table 4. UAV contract clause families.

Clause Family	Content Examples
Objective	inspection, search, imaging, delivery, return, return-to-home
Spatial	waypoints, regions, no-fly zones, geofences, altitude ranges
Temporal	deadlines, observation windows, mission order
Energy	battery, endurance, return reserve, resource consumption
Payload	camera, thermal imaging, LiDAR, payload capacity, sensor status
Communication	link coverage, real-time return, delayed upload, relay conditions
Contingency	abort, hover, return-to-home, emergency handling
Preference	priority, quality preference, optional targets

The governance layer computes ternary semantic support for each candidate clause:

$$Sup\left(\kappa \right)\in \{\mathrm{Y},\mathrm{N},\mathrm{U}\}.$$

(10)

In this classification, Y indicates evidence support, N indicates evidence exclusion or invalid source, and U indicates insufficient evidence. The three-valued support classification is defined relative to the single resolved highest-priority applicable evidence source after authority and freshness conflict resolution, ensuring mutual exclusivity. $Sup\left(\kappa \right)=\mathrm{Y}$ means that the resolved highest-priority applicable fresh evidence source supports $\kappa$. $Sup\left(\kappa \right)=\mathrm{N}$ means that the resolved highest-priority applicable evidence source contradicts $\kappa$, or no admissible evidence source remains after authority/freshness validation (invalid source). $Sup\left(\kappa \right)=\mathrm{U}$ means that no resolved admissible source supports or contradicts $\kappa$ (insufficient evidence), so the clause cannot enter a hard obligation but may remain as a pending item. Evidence freshness is verified by comparing evidence timestamps against context-defined validity windows: weather data, communication coverage, and airspace restrictions are checked against their respective update intervals, while battery state and payload availability are treated as real-time context fields. When two trusted-context facts conflict (e.g., two weather sources report different wind speeds), the governance policy specifies a priority order: regulatory sources override commercial data services, and more recent readings override older ones at the same authority level. A clause can enter a hard mission obligation only if

$$Sup\left(\kappa \right)=\mathrm{Y}.$$

(11)

New statements generated by the LLM during candidate generation or repair are labeled as untrusted semantic increments. For an LLM suggestion p, its claim set is decomposed as

$$Claim\left(p\right)=Clai{m}_{\mathrm{R}}\left(p\right)\cup Clai{m}_{\mathrm{D}}\left(p\right)\cup Clai{m}_{\mathrm{H}}\left(p\right).$$

(12)

In this decomposition, $Clai{m}_{\mathrm{R}}\left(p\right)$ contains reused claims traceable to user anchors or trusted context; $Clai{m}_{\mathrm{D}}\left(p\right)$ contains derived claims entailed by rules, backend models, or protected constraints; and $Clai{m}_{\mathrm{H}}\left(p\right)$ contains hypothetical claims introduced only by the LLM without external evidence. Hard clauses in admitted mission obligations must satisfy

$$Claims\left(Hard\left(G^{\ast }\right)\right)\cap Clai{m}_{\mathrm{H}}=⌀,$$

(13)

where $Claims(·)$ extracts the set of atomic claims from a clause set, as defined in Equation (12). This constraint confines unverified assumptions to pending items, clarification requests, or the audit trail.

The $trust$ field in the clause structure records the verification status of each clause, taking values from {trusted, derived, hypothetical, pending} (Table 5).

Table 5. Trust labels and admission semantics.

Trust Label	Meaning	Hard Obligation
trusted	Traceable to user input or verified trusted context	Allowed
derived	Entailed by rules, backend model, or protected constraints	Allowed
hypothetical	LLM-introduced without external evidence	Prohibited
pending	Awaiting evidence or clarification	Prohibited

After clause labeling, EAMSR assembles candidate clauses into candidate mission obligations:

$$G_i=⟨H_i,S_i,P_i⟩,$$

(14)

where $H_i$ is the set of hard goals and hard constraints, $S_i$ is the set of soft preferences, and $P_i$ is the set of pending clauses. The corresponding candidate MAC is

$$C_i=⟨A_{\mathrm{ctx}},I_{\mathrm{prot}},G_i,\mathrm{\Gamma },\mathcal{E},{\mathrm{\Omega }}_{\mathrm{UAV}}⟩.$$

(15)

EAMSR also maintains the clause-evidence trace relation

$$Trace\left(\kappa \right)=evidence\left(\kappa \right),$$

(16)

and the anchor coverage relation

$$Cover\left(a_i\right)=\{\kappa \mid anchor\left(\kappa \right)=a_i\}.$$

(17)

Missing coverage of explicit anchors forms pending contract content. When pending content affects mission consequences, the system enters the clarification process.

3.3. Contract Admission Under Proof-Obligation Gating

The second class of UAV admission risk comes from task specifications that are formally complete but governance-invalid. A task clause may have readable semantics but lack evidence, exceed source authority, modify non-negotiable constraints, or contain LLM-added assumptions. The proof-obligation gate converts these risks into a unified contract-admission predicate.

EAMSR defines candidate admission in three stages. The governance gate checks evidence, authority, mutability, and untrusted-semantic-isolation obligations:

$$GovOK\left(C_i\right)=P{O}_{\mathrm{E}}\left(C_i\right)\wedge P{O}_{\mathrm{A}}\left(C_i\right)\wedge P{O}_{\mathrm{M}}\left(C_i\right)\wedge P{O}_{\mathrm{U}}\left(C_i\right).$$

(18)

Candidates that pass governance form the governance-admissible set:

$${\mathcal{C}}_{\mathrm{gov}}=\{C_i\in \mathcal{C}\mid GovOK\left(C_i\right)=1\}.$$

(19)

If ${\mathcal{C}}_{\mathrm{gov}}\ne ⌀$, the system computes consequence signatures and screens pairwise compatibility at the set level using the $\mathrm{Consistent}$ predicate (defined in Equation (37)). If the set is consistent, a candidate $C^{\ast }$ is selected; the final admission requires a backend witness:

$$\mathrm{AdmissionReady}(C^{\ast },{\mathcal{C}}_{\mathrm{gov}})=GovOK\left(C^{\ast }\right)\wedge \mathrm{Consistent}\left({\mathcal{C}}_{\mathrm{gov}}\right).$$

(20)

This order avoids circularity: consequence screening is evaluated only on governance-admissible candidates. The backend witness $P{O}_{\mathrm{B}}$ (Equation (25)) is then checked separately; an ADMIT decision requires both $\mathrm{AdmissionReady}$ and a concrete witness $\pi$ (Equation (48)).

The evidence obligation $P{O}_{\mathrm{E}}$ requires all hard mission obligations to be supported by admissible evidence or a deterministic trusted derivation:

$$P{O}_{\mathrm{E}}\left(C_i\right)=1⟺\forall \kappa \in H_i,Sup\left(\kappa \right)=\mathrm{Y}.$$

(21)

The authority obligation $P{O}_{\mathrm{A}}$ requires source, authority level, and modal strength to be consistent:

$$P{O}_{\mathrm{A}}\left(C_i\right)=1⟺\forall \kappa \in H_i\cup S_i,AuthOK(\kappa ,\mathrm{\Gamma })=1.$$

(22)

The governance policy $\mathrm{\Gamma }$ defines a hierarchy of authority levels (Table 6). When two sources at different authority levels conflict, the higher-authority source prevails. Sources at the same authority level are resolved by recency (more recent prevails) or, if timestamps are equal, by the governance-specified tie-breaking rule. An operator can override a system default at the operational level, and an emergency rule can override a normal geofence policy, but no source can override a regulatory constraint. Emergency is not a standing authority level in Table 6; it is a context-dependent override condition activated by a declared contingency (e.g., imminent hazard, medical urgency) that carries the authority of the declaring source (typically operator-level) and is recorded with its triggering condition in the audit trail. An emergency override does not create a new clause authority level; it authorizes a temporary relaxation of specific non-regulatory constraints (geofence buffers, time windows, communication requirements) for the duration of the declared contingency, after which the standard hierarchy resumes. Regulatory constraints remain non-overridable even under emergency conditions.

Table 6. Authority levels in the governance policy $\mathrm{\Gamma }$.

Level	Description	Overridable by
regulatory	Airspace regulations, no-fly zones, legal mandates	None
operator	Mission commander’s explicit authorization	Policy-activated emergency override
operational	Organization-level mission parameters	Operator
system_default	EAMSR default values (e.g., return reserve)	Operational
llm_suggestion	LLM-proposed parameter or constraint	Any of the above

The mutability obligation $P{O}_{\mathrm{M}}$ requires every clause edit to belong to the transformation relation allowed by the governance policy:

$$P{O}_{\mathrm{M}}\left(C_i\right)=1⟺\forall e\in Edit\left(C_i\right),e\in {\mathcal{R}}_{\mathrm{\Gamma }}.$$

(23)

The transformation relation ${\mathcal{R}}_{\mathrm{\Gamma }}$ defines the allowed modifications for each clause based on its mutability classification (Table 7). The mutability field interacts with the source field: clauses with source $user\_explicit$ and mutability $immutable$ can only be kept; clauses with source $llm\_generated$ and mutability $revocable$ can be weakened, dropped, or replaced. The refinement relaxation priority is specified by the governance policy $\mathrm{\Gamma }$; the evaluated configuration relaxes constraints in the order temporal first, then spatial, then communication, then payload, so that operationally critical spatial and payload constraints are preserved as long as possible. Different mission types may benefit from different priority orderings (e.g., emergency delivery may prioritize temporal relaxation, while inspection may prioritize spatial preservation); the framework supports such configuration through $\mathrm{\Gamma }$.

Table 7. Mutability modes and allowed transformations.

Mutability	Allowed Transformations	Typical Source
immutable	keep only	user_explicit, regulatory
protected	keep, clarify (with authorization)	user_implied
governance	keep, weaken, default (per $\mathrm{\Gamma }$)	trusted_context
overridable	keep, weaken, drop, default	system_default
revocable	keep, weaken, drop, default, replace	llm_generated

The untrusted-semantic-isolation obligation $P{O}_{\mathrm{U}}$ requires hard mission obligations to contain no unverified hypothetical claims:

$$P{O}_{\mathrm{U}}\left(C_i\right)=1⟺Claims\left(H_i\right)\cap Clai{m}_{\mathrm{H}}=⌀,$$

(24)

where $Claims\left(H_i\right)$ denotes the set of atomic claims extracted from the hard clause set $H_i$, and $Clai{m}_{\mathrm{H}}$ is the set of LLM-introduced hypothetical claims without external evidence.

The backend executability obligation $P{O}_{\mathrm{B}}$ requires the existence of a task-level plan witness:

$$P{O}_{\mathrm{B}}\left(C\right)=1⟺\exists \pi :Witness(C,\pi )=1,$$

(25)

where the $Witness$ predicate is defined in Equation (39).

To illustrate the authority and mutability model, consider a powerline-inspection mission in controlled airspace. The regulatory constraint “no flight above 120 m in Class C airspace” is immutable at the regulatory level: no operator or system default can modify it. The operator’s requirement to “inspect towers A through D” is protected at the operator level: the set of inspection targets can be clarified (e.g., if tower C is in a temporary restricted area) but the core inspection objective must be preserved. For the return reserve, we distinguish the non-overridable regulatory lower bound $r_{\min }^{\mathrm{reg}}$ from the operational system default $r_{\mathrm{default}}^{\mathrm{sys}}$, which satisfies $r_{\mathrm{default}}^{\mathrm{sys}}\ge r_{\min }^{\mathrm{reg}}$. The system default $r_{\mathrm{default}}^{\mathrm{sys}}=15\%$ is overridable at the operational level: an operator may increase it to 20% for conservative missions but cannot decrease it below $r_{\min }^{\mathrm{reg}}$. An LLM-suggested clause “use thermal camera for night inspection” is revocable: if no thermal camera is available in the payload, this clause is dropped without affecting the inspection objective. When the LLM proposes reducing the return reserve to 5% to extend inspection time, this proposal is rejected because the policy specifies a protected minimum $r_{\min }^{\mathrm{reg}}>5\%$ (an immutable constraint at the regulatory level), enforced by $P{O}_{\mathrm{M}}$, and because the LLM-suggestion source lacks the authority to modify any return-reserve parameter, enforced by $P{O}_{\mathrm{A}}$.

3.4. Authority-Bounded Contract Refinement and Mission-Consequence Clarification

The third class of UAV admission risk arises from automatic repair of infeasible tasks. Executability conflicts may result from overly tight time windows, restricted target regions, insufficient communication coverage, payload mismatch, or insufficient return reserve. A refinement mechanism must restore executability while preserving protected invariants, user hard intent, and evidence boundaries.

When direct admission fails, the backend diagnosis interface returns a conflict core:

$$\mathcal{Q}=\mathrm{Diagnose}(C_i,{\mathrm{\Omega }}_{\mathrm{UAV}}),$$

(26)

where $\mathcal{Q}$ contains the task clauses, protected invariants, and backend constraints responsible for unsatisfiability. The governance layer converts $\mathcal{Q}$ into a structured diagnostic feedback package:

$$D_i=⟨\mathcal{Q},failure,allowed,forbidden,required\_evidence,affected\_consequence⟩.$$

(27)

Under the constraint of $D_i$, the LLM proposes a repair suggestion:

$$p=⟨\Delta G,Claim\left(p\right),action,evidencePtr,expectedConsequence⟩.$$

(28)

In this proposal, $\Delta G$ is the mission-obligation difference; $action$ is one of weaken, drop, default, split, mark-pending, or clarify; and $expectedConsequence$ declares the expected change in mission consequences. Mission consequences are defined by the EAMSR consequence-signature function.

We define the authority-admissible refinement relation as

$$C^{\prime }{⪯}_{\mathrm{\Gamma }}^{\mathrm{adm}}C.$$

(29)

This relation holds if and only if the following criteria hold jointly:

$$Edit(C,C^{\prime })\subseteq {\mathcal{R}}_{\mathrm{\Gamma }},$$

(30)

$$Preserve\left(I_{\mathrm{prot}}\right)\wedge Preserve\left(G_{\mathrm{user}\text{-}\mathrm{hard}}\right)\wedge NoHypotheticalAdmission\left(C^{\prime }\right)\wedge GovOK\left(C^{\prime }\right)=1.$$

(31)

In this constraint, $Preserve\left(I_{\mathrm{prot}}\right)$ indicates preservation of protected operational invariants, and $Preserve\left(G_{\mathrm{user}\text{-}\mathrm{hard}}\right)$ indicates preservation of user hard intent. The term $NoHypotheticalAdmission\left(C^{\prime }\right)$ indicates that unverified assumptions do not enter hard mission obligations.

Among candidates satisfying $C^{\prime }{⪯}_{\mathrm{\Gamma }}^{\mathrm{adm}}C$, EAMSR selects the minimum-cost governance-admissible refinement candidate:

$$C^{\ast }=\arg \underset{C^{\prime }}{\min }\left[{\lambda }_{\mathrm{sem}}{\tilde{d}}_{\mathrm{sem}}+{\lambda }_{\mathrm{edit}}\widetilde{\left|Edit\right|}+{\lambda }_{\mathrm{pref}}{\tilde{d}}_{\mathrm{pref}}+{\lambda }_{\mathrm{plan}}{\tilde{\widehat{J}}}_{\mathrm{plan}}\left(C^{\prime }\right)\right].$$

(32)

In this objective, $d_{\mathrm{sem}}$ is semantic displacement, $\left|Edit\right|$ is the number of edits, $d_{\mathrm{pref}}$ is soft-preference loss, and ${\widehat{J}}_{\mathrm{plan}}\left(C^{\prime }\right)$ is the estimated mission-energy cost produced by $\mathrm{BackendDiag}\left(C^{\prime }\right)$. Note that ${\widehat{J}}_{\mathrm{plan}}$ is a lightweight diagnostic estimate of the energy required to execute the candidate’s mission profile, not the cost of the final witness $\pi$, which is generated only after $C^{\ast }$ is selected. This separation avoids a circular dependency in which candidate selection would require a witness that is only produced after selection. Because these terms have different native scales, each is normalized to $[0,1]$ before weighting:

$$\widetilde{\left|Edit\right|}={\displaystyle \frac{\left|Edit\right|}{B_r}},{\tilde{\widehat{J}}}_{\mathrm{plan}}\left(C^{\prime }\right)=\min \left(1,{\displaystyle \frac{{\widehat{J}}_{\mathrm{plan}}\left(C^{\prime }\right)}{J_{\mathrm{ref}}}}\right),$$

(33)

where $B_r$ is the refinement budget and $J_{\mathrm{ref}}$ is a reference diagnostic cost (the battery-energy capacity in the evaluated configuration). The displacement and preference distances $d_{\mathrm{sem}},d_{\mathrm{pref}}\in [0,1]$ require no additional normalization. The coefficients satisfy ${\lambda }_i\ge 0$ and ${\sum }_i{\lambda }_i=1$, so that each normalized term contributes a bounded share of the total cost. The evaluated configuration uses the uniform profile ${\lambda }_{\mathrm{sem}}={\lambda }_{\mathrm{edit}}={\lambda }_{\mathrm{pref}}={\lambda }_{\mathrm{plan}}=0.25$; non-uniform profiles can be configured when a governance policy prioritizes, for example, minimal semantic displacement over plan cost.

Natural-language ambiguity in UAV tasks is screened through a mission-consequence signature. For a candidate contract C, define

$$\chi \left(C\right)=⟨feas,goals,optional,order,rth,window,airspace,comm,payload,weather⟩.$$

(34)

The components of $\chi \left(C\right)$ are as follows: $feas$ denotes executability; $goals$ denotes the set of hard goals; $optional$ denotes the set of optional tasks; $order$ denotes the required order closure; $rth$ denotes the minimum return-energy margin; $window$ denotes the minimum time-window margin; $airspace$ denotes airspace and geofence compliance; $comm$ denotes communication and data-return feasibility; $payload$ denotes payload and sensor satisfaction; and $weather$ denotes weather and observation-condition satisfaction.

Each component of $\chi \left(C\right)$ is normalized to $[0,1]$ so that heterogeneous Boolean, categorical, and numerical quantities can be combined, and the component distances are defined per component family as summarized in Table 8. The mission-consequence distance between two contracts is the weighted average of the component distances:

$${\Delta }_{\chi }(C_i,C_j)=dist(\chi \left(C_i\right),\chi \left(C_j\right))={\displaystyle \frac{{\sum }_{k=1}^{10}{w}_k{d}_k(\chi \left(C_i\right),\chi \left(C_j\right))}{{\sum }_{k=1}^{10}{w}_k}},w_k\ge 0.$$

(35)

The normalization keeps ${\Delta }_{\chi }\in [0,1]$, so that the compatibility threshold ${ϵ}_{\chi }$ has a uniform interpretation across mission types. The evaluated configuration uses uniform weights $w_k=1$ for $k=1,\dots ,10$.

Table 8. Component distances of the mission-consequence signature $\chi \left(C\right)$. All components are normalized to $[0,1]$ before combination.

Components	Normalization	Component Distance
$feas$, $airspace$, $comm$, $payload$, $weather$	satisfaction ratio in $[0,1]$ produced by $\mathrm{BackendDiag}$ (lightweight task-level diagnostic, distinct from the final witness)	absolute difference
$goals$, $optional$, $order$	sets over the task-ontology vocabulary; for $order$, the set of precedence pairs $(g,g^{\prime })$	Jaccard distance $1 - |S_i\cap S_j|/|S_i\cup S_j|$ (0 if both sets are empty)
$rth$, $window$	truncated normalized margins $\min (1,margin/margi{n}_{\mathrm{ref}})$ and $\min (1,slack/slac{k}_{\mathrm{ref}})$, with $margi{n}_{\mathrm{ref}}=0.30$ and $slac{k}_{\mathrm{ref}}=0.50$	absolute difference of the normalized margins

The backend provides two interfaces. $\mathrm{BackendDiag}\left(C\right)$ is a lightweight task-level diagnostic evaluated for all governance-admissible candidates; it produces satisfaction ratios for feasibility, airspace compliance, communication coverage, payload, and weather without constructing a full action sequence. These ratios feed the consequence signature $\chi \left(C\right)$ and enable mission-consequence screening (MCS) before candidate selection. The final backend witness $Witness(C^{\ast },\pi )$ is generated only for the selected candidate $C^{\ast }$; it constructs a complete action sequence $\pi$ and verifies SafeRTH, GeoSafe, and AuxOK on the full plan.

A single global weighted-average threshold can mask large changes in individual critical dimensions: with 10 uniform-weight components, a complete reversal in one dimension ($d_k=1$) contributes only 0.1 to ${\Delta }_{\chi }$, which may remain below ${ϵ}_{\chi }=0.15$. To prevent this, the compatibility relation augments the global threshold with a per-dimension hard veto on critical components. Given threshold ${ϵ}_{\chi }$ and per-dimension thresholds ${\tau }_k$, mission-consequence compatibility is defined as

$$C_i{\sim }_{\chi }{C}_j⟺\left[\underset{k\in K_{\mathrm{crit}}}{\max }{d}_k(C_i,C_j)\le {\tau }_k\right]\wedge \left[{\Delta }_{\chi }(C_i,C_j)\le {ϵ}_{\chi }\right],$$

(36)

where $K_{\mathrm{crit}}=\{goals,feas,airspace,rth\}$ is the set of critical dimensions whose individual changes must not exceed per-dimension thresholds ${\tau }_k$, and the remaining components (optional preferences, order, communication, payload, weather, window) are evaluated only through the weighted average. In the evaluated configuration, ${\tau }_k=0.3$ for all $k\in K_{\mathrm{crit}}$, so that any critical-dimension change exceeding 30% of its normalized range triggers incompatibility regardless of the aggregate distance. The threshold ${\tau }_k=0.3$ was selected using the same 20-task development subset used for ${ϵ}_{\chi }$ and $\lambda$: values below 0.2 caused spurious CLARIFY decisions for contracts that differed only in non-critical refinements, while values above 0.4 allowed goal-set reversals that the aggregate distance alone would have caught. The framework admits dimension-specific thresholds or governance-defined compatibility criteria through the weights $w_k$ and per-dimension configuration; calibrating such criteria with operational stakeholders is a direction for future work.

Because each component distance is normalized to $[0,1]$ and ${\Delta }_{\chi }$ is a weighted average, the relation ${\sim }_{\chi }$ is reflexive and symmetric. It is generally not transitive—candidates A, B, and C may satisfy the veto and aggregate conditions pairwise for $(A,B)$ and $(B,C)$ while failing for $(A,C)$—so ${\sim }_{\chi }$ is a tolerance relation, not a strict equivalence. To decide whether a candidate set is consequence-consistent, we require pairwise compatibility under Equation (36):

$$\mathrm{Consistent}\left(\mathcal{C}\right)⟺\forall C_i,C_j\in \mathcal{C}:C_i{\sim }_{\chi }{C}_j.$$

(37)

When admissible candidates or refinement candidates do not satisfy pairwise consistency, the system returns $\mathrm{CLARIFY}$. When all admissible candidates are pairwise compatible, the system selects $C^{\ast }$ according to semantic displacement, soft-preference satisfaction, and estimated mission-energy cost.

Four examples illustrate consequence compatibility and its violation under the evaluated configuration (${ϵ}_{\chi }=0.15$, ${\tau }_k=0.3$, uniform weights). (i) Two contracts share all components except the return-energy margin, whose raw values of 0.15 and 0.18 give normalized margins $m_{rth}=0.50$ and $m_{rth}=0.60$; the resulting distance is ${\Delta }_{\chi }=0.10/10=0.01\le {ϵ}_{\chi }$ and no critical-dimension distance exceeds ${\tau }_k$, so the contracts are consequence-compatible. (ii) Two contracts differ only in the time-window margin ($d_{window}=0.20$) and payload satisfaction ($d_{payload}=0.10$), giving ${\Delta }_{\chi }=0.03$; they are likewise compatible, and the refinement that better satisfies soft preferences is selected without clarification. Conversely, clarification is triggered when candidates are not pairwise compatible. (iii) Two candidate contracts with disjoint hard-goal sets ($d_{goals}=1>{\tau }_k=0.3$) trigger the critical-dimension veto, so the pair is incompatible regardless of the aggregate distance. (iv) A candidate whose feasibility, airspace, and communication components are degraded ($d_{feas}=d_{airspace}=0.8>{\tau }_k=0.3$) likewise triggers the veto through feas and airspace (both in $K_{\mathrm{crit}}$); the communication degradation ($d_{comm}=0.8$) does not enter the veto, since comm is not in $K_{\mathrm{crit}}$, and contributes only to the aggregate ${\Delta }_{\chi }=0.24>{ϵ}_{\chi }$. In both cases, the system returns $\mathrm{CLARIFY}$ instead of silently selecting one consequence outcome.

3.5. Backend Plan Witness, Audit Trail, and Method Properties

The final admission risk is a specification that is semantically reasonable but task-inexecutable. The backend witness layer binds the admitted contract to UAV task constraints, so that each ADMIT output carries task-level executability evidence.

Let the plan witness be a finite action sequence:

$$\pi =[(a_1,t_1^s,t_1^e),(a_2,t_2^s,t_2^e),\dots ,(a_m,t_m^s,t_m^e)],$$

(38)

where $a_j$ is a task-level action such as takeoff, navigation, inspection, imaging, hovering, data return, delivery, return-to-home, or abort, and $t_j^s$ and $t_j^e$ are the start and end times of the action.

The backend witness condition is

$$Witness(C^{\ast },\pi )=1⟺\pi \vDash A_{\mathrm{ctx}}\wedge I_{\mathrm{prot}}\wedge H^{\ast }\wedge {\mathrm{\Omega }}_{\mathrm{UAV}},$$

(39)

where $H^{\ast }=Hard\left(G^{\ast }\right)$ is the set of hard goals and hard constraints extracted from the selected contract $C^{\ast }$. Soft preferences $S^{\ast }$ influence candidate ranking (Equation (32)) but are not part of the witness condition, and pending clauses $P^{\ast }$ are excluded from $H^{\ast }$ by the evidence obligation $P{O}_{\mathrm{E}}$. This paper uses return-to-home safety and airspace safety as core UAV safety constraints, while communication, payload, time-window, and weather constraints are incorporated into ${\mathrm{\Omega }}_{\mathrm{UAV}}$.

Return-to-home safety is defined as

$$SafeRTH\left(\pi \right)=1⟺\forall t,E_{\mathrm{eff}}\left(t\right)\ge (1+\beta )E_{\mathrm{RTH}}(pos\left(t\right),t)+E_{\mathrm{res}},$$

(40)

where $\beta =0.10$ is a safety buffer on the return-to-home energy estimate, $E_{\mathrm{eff}}\left(t\right)$ is the effective available energy at time t (the SOC-corrected remaining energy defined in Equation (42)), $E_{\mathrm{RTH}}(pos\left(t\right),t)$ is the minimum energy required to safely return from the current position, and $E_{\mathrm{res}}$ is the safety reserve. The return-to-home energy estimate $E_{\mathrm{RTH}}$ accounts for horizontal distance to the home position, vertical altitude difference, landing energy, and a 30 s pre-landing hover:

$$E_{\mathrm{RTH}}=e_{\mathrm{horiz}}·d_{\mathrm{horiz}}^{\mathrm{home}}+e_{\mathrm{vert}}·\left|d{z}_{\mathrm{home}}\right|+E_{\mathrm{land}}+E_{\mathrm{hover},30\mathrm{s}},$$

(41)

where $e_{\mathrm{horiz}}=0.5$ Wh/m, $e_{\mathrm{vert}}=1.0$ Wh/m, $E_{\mathrm{land}}=5$ Wh, and $E_{\mathrm{hover},30\mathrm{s}}\approx 1.67$ Wh. The safety reserve is $E_{\mathrm{res}}=0.15\times 500=75$ Wh. When the battery state of charge (SOC) falls below 30%, the effective available energy is reduced by a piecewise correction factor $f\left(SOC\right)$ that accounts for increased internal resistance at low charge levels:

$$E_{\mathrm{eff}}\left(t\right)=f\left(SOC\left(t\right)\right)·E\left(t\right),f\left(SOC\right)=\left\{\begin{array}{cc}1.0,\hfill & SOC\ge 0.3,\hfill \\ 1.0-0.5(0.3-SOC),\hfill & SOC<0.3,\hfill \end{array}\right.$$

(42)

so that at $SOC=0.15$ the correction factor is $f=0.925$. The normalized energy margin at each time point is $M_{\mathrm{RTH}}\left(t\right)=(E_{\mathrm{eff}}\left(t\right)-(1+\beta )E_{\mathrm{RTH}}(pos\left(t\right),t)-E_{\mathrm{res}})/E_{\mathrm{RTH}}(pos\left(t\right),t)$, and the SafeRTH condition in Equation (40) is equivalent to requiring $M_{\mathrm{RTH}}\left(t\right)\ge 0$ at all sampled times.

Airspace safety is defined as

$$GeoSafe\left(\pi \right)=1⟺\forall t,pos\left(t\right)\notin NFZ\wedge pos\left(t\right)\in Zon{e}_{\mathrm{op}}.$$

(43)

In this equation, $NFZ$ is the set of no-fly zones, and $Zon{e}_{\mathrm{op}}$ is the permitted operational airspace.

Other task-level constraints are represented by the unified predicate

$$AuxOK\left(\pi \right)=DataReturn\left(\pi \right)\wedge PayloadOK\left(\pi \right)\wedge WindowOK\left(\pi \right)\wedge WeatherOK\left(\pi \right).$$

(44)

The backend witness evaluates the candidate contract against a task-level discrete UAV simulation model. The simulator maintains a state vector at sampled time points along the witness plan, tracking position (local Cartesian coordinates in metres), remaining battery energy, communication coverage ratio, payload status, and elapsed mission time. The witness plan is a finite sequence of task-level actions, where each action type has an associated energy cost model and switch overhead (Table 9).

Table 9. Backend action types and energy model. Switch overhead contributes hover energy during action transitions.

Action	Overhead (s)	Energy Model
takeoff	15	Fixed takeoff energy (10 Wh)
fly	0	Horizontal: $e_{\mathrm{horiz}}\times d_{\mathrm{horiz}}$; vertical: $e_{\mathrm{vert}}\times \left|dz\right|$
inspect	5	Hover energy during duration
capture	10	Hover energy during duration
hover	5	$P_{\mathrm{hover}}\times \Delta t/3600$
transmit	20	Hover energy during duration
deliver	10	Hover energy during duration
return	0	Flight energy to home position
abort	5	Hover energy during duration
landing	5	Fixed landing energy (5 Wh)

Witness-plan generation uses a greedy forward search with bounded backtracking over the task-level action vocabulary, advancing the state vector at a fixed 1 s timestep and checking all safety and auxiliary predicates at each step. The search terminates when a complete feasible plan is found, all branches within the depth limit are exhausted, or the per-contract wall-clock budget of 5 s is reached. The action priority ordering is takeoff → fly (to first target) → inspect/capture/deliver (mission actions in goal order) → transmit (if required) → return → landing, with abort inserted at any point if SafeRTH is violated. Backtracking reorders optional mission actions and adjusts waypoint sequencing within the depth limit $D_{\max }=20$. The same L1 backend model is used for benchmark label construction and admission decisions; this shared dependency is acknowledged as a limitation in Section 4.6.

The present backend uses a simplified task-level energy proxy: the energy model accounts for horizontal distance, vertical altitude, landing, and hover, but does not model continuous wind- or payload-dependent aerodynamic power consumption. Wind speed is checked as a binary threshold in $WeatherOK$, and payload affects sensor availability rather than energy draw. This simplification is intentional for the task-level admission layer, where the goal is to verify executability at the mission-specification level rather than to produce a flight-controller-grade trajectory energy estimate.

Communication coverage is evaluated using a distance-based attenuation model rather than a binary in/out check. The coverage ratio decreases linearly from 1.0 inside the inner radius ($0.8\times r_{\max }$) to 0.0 at the outer radius ($r_{\max }$), and the plan passes when the minimum coverage ratio along the flight path is at least 0.5. The auxiliary constraints $AuxOK$ verify that: (i) a data-return action exists when communication is required; (ii) all sensors specified in payload clauses are available; (iii) all actions fall within their designated time windows; and (iv) no action exceeds the maximum wind speed from weather constraints.

The abstract witness condition was defined in Equation (39). The UAV task model ${\mathrm{\Omega }}_{\mathrm{UAV}}$ is decomposed into implementation-level predicates:

$${\mathrm{\Omega }}_{\mathrm{UAV}}=SafeRTH\wedge GeoSafe\wedge AuxOK\wedge {\mathrm{\Omega }}_{\mathrm{task}},$$

(45)

where ${\mathrm{\Omega }}_{\mathrm{task}}$ captures scenario-specific constraints not covered by the three standard predicates. Substituting Equation (45) into Equation (39) yields the implementation-level witness used in the evaluation:

$$\begin{array}{ccc}\hfill Witness(C^{\ast },\pi )& =& SafeRTH\left(\pi \right)\wedge GeoSafe\left(\pi \right)\wedge AuxOK\left(\pi \right)\hfill \\ \hfill & & \wedge \left(\pi \vDash A_{\mathrm{ctx}}\wedge I_{\mathrm{prot}}\wedge H^{\ast }\wedge {\mathrm{\Omega }}_{\mathrm{task}}\right).\hfill \end{array}$$

(46)

A failed witness attempt does not by itself establish infeasibility: the search is bounded by $D_{\max }$ and a wall-clock budget, so termination without a witness does not prove that no witness exists. Contract-level infeasibility is reported only when the backend returns a conclusive infeasibility status (Equation (47)); otherwise, failure to construct a witness remains inconclusive. The witness verification collects all violations without early exit, producing a structured conflict-core diagnosis that identifies the specific clauses, protected invariants, and backend constraints responsible for unsatisfiability. Verification completes in under 5 s per contract on a single core.

Because witness search is bounded, the backend therefore reports a three-valued status:

BackendStatus(C) ∈ {WitnessFound, ConclusiveInfeasible, Inconclusive}.

(47)

WitnessFound means that a concrete witness $\pi$ satisfying Equation (46) has been constructed; it can support an ADMIT decision. ConclusiveInfeasible means that unsatisfiability is conclusively established under the declared backend model: the diagnosis identifies a deterministic conflict with an immutable or protected constraint that no authority-bounded refinement can remove (e.g., a hard energy deficit against battery capacity, or an airspace breach of a non-overridable no-fly zone), or the search has exhaustively covered the finite task-level action space declared for the scenario without finding a witness. Only ConclusiveInfeasible can support a REJECT decision. Inconclusive covers the remaining outcomes—wall-clock timeout, exhaustion of the depth or backtracking budget, or termination without a witness and without a conclusive infeasibility certificate. Inconclusive is not treated as proof of infeasibility: the blocking condition is considered unresolved and the request is returned as CLARIFY, since a refined contract, additional operator input, or a larger search budget might still yield a witness.

The final decision rule is

$$decision=\left\{\begin{array}{cc}\mathrm{ADMIT},\hfill & \exists C^{\ast },\pi :\mathrm{AdmissionReady}(C^{\ast },{\mathcal{C}}_{\mathrm{gov}})=1\wedge Witness(C^{\ast },\pi )=1,\hfill \\ \mathrm{REJECT},\hfill & \mathrm{an}\mathrm{immutable}\mathrm{or}\mathrm{protected}\mathrm{admission}\mathrm{condition}\mathrm{is}\mathrm{violated}, \mathrm{or}\mathrm{task}\text{-}\mathrm{level}\hfill \\ & \mathrm{infeasibility}\mathrm{is}\mathrm{conclusively}\mathrm{established}\mathrm{by}\mathrm{a}\mathrm{backend}\mathrm{diagnosis}\hfill \\ & (\mathrm{BackendStatus}\left(C^{\ast }\right)=\mathrm{C}\mathrm{O}\mathrm{N}\mathrm{C}\mathrm{L}\mathrm{U}\mathrm{S}\mathrm{I}\mathrm{V}\mathrm{E}\mathrm{I}\mathrm{N}\mathrm{F}\mathrm{E}\mathrm{A}\mathrm{S}\mathrm{I}\mathrm{B}\mathrm{L}\mathrm{E}),\hfill \\ \mathrm{CLARIFY},\hfill & \mathrm{the}\mathrm{blocking}\mathrm{condition}\mathrm{is}\mathrm{remediable}\mathrm{through}\mathrm{additional}\mathrm{evidence}\mathrm{authorized}\hfill \\ & \mathrm{modification,}\mathrm{or}\mathrm{resolution}\mathrm{of}\mathrm{consequence}\text{-}\mathrm{sensitive}\mathrm{ambiguity}, \mathrm{or}\mathrm{backend}\hfill \\ & \mathrm{closure}\mathrm{remains}\mathrm{inconclusive}.\hfill \end{array}\right.$$

(48)

REJECT asserts that no admissible resolution exists within the currently declared trusted context, governance policy, protected constraints, admissible refinement space, and conclusively evaluated backend conditions; it does not assert that the mission can never become executable under any future evidence, authorization, or refinement. Failure to obtain a witness solely because of search-depth or wall-clock limits is treated as unresolved (Inconclusive) and leads to CLARIFY rather than REJECT, preserving the conservative direction of the admission boundary.

EAMSR outputs the audit trail

$$\begin{array}{ccc}\hfill {\mathcal{T}}_{\mathrm{audit}}& =& ⟨\mathcal{A},\mathcal{K},Trace,Cover,Authority,Mutability,\hfill \\ \hfill & & UntrustedClaims,PO,\mathcal{Q},Edit,\chi ,\pi ,decision⟩.\hfill \end{array}$$

(49)

This trail connects natural-language anchors, candidate clauses, evidence sources, anchor coverage, authority states, mutability states, untrusted semantic increments, proof-obligation results, conflict cores, refinement edits, mission-consequence signatures, backend plan witnesses, and the final admission decision.

The following properties are specification-level properties of the abstract admission model. They hold provided that clause extraction, evidence status, authority assignments, governance policy, and backend predicates are implemented consistently with the formal definitions; they do not constitute machine-verified guarantees of the complete operational system.

Property 1: Protected-invariant preservation. If $c\in I_{\mathrm{prot}}$ and $\mathrm{\Gamma }$ marks c as immutable, then every ADMIT output preserves c:

$$c\in I_{\mathrm{prot}}\Rightarrow Preserve(c,G^{\ast }).$$

(50)

This holds because the mutability proof obligation $P{O}_{\mathrm{M}}$ and $Preserve\left(I_{\mathrm{prot}}\right)$ jointly exclude any candidate that modifies, weakens, or removes protected invariants from the admissible refinement set.

Property 2: Represented user hard intent cannot be silently modified. Given correct anchor extraction, if a user hard intent $g\in G_{\mathrm{user}\text{-}\mathrm{hard}}$ conflicts with protected constraints or the backend model, the system returns CLARIFY or REJECT:

$$g\in G_{\mathrm{user}\text{-}\mathrm{hard}}\wedge \neg \exists \pi :\pi \vDash g\wedge I_{\mathrm{prot}}\wedge {\mathrm{\Omega }}_{\mathrm{UAV}}\Rightarrow decision\in \{\mathrm{CLARIFY},\mathrm{REJECT}\}.$$

(51)

The preservation constraint and the mission-consequence clarification rule jointly guarantee this property. The qualifier “represented” is necessary because anchor extraction is treated as trusted preprocessing (Section 3.2); if the extractor omits a user hard intent, the governance layer has no opportunity to protect it.

Property 3: Unverified assumptions do not propagate. If an atomic claim $\varphi$ belongs to $Clai{m}_{\mathrm{H}}$ and cannot be verified by $\mathcal{E}$, $\mathrm{\Gamma }$, or ${\mathrm{\Omega }}_{\mathrm{UAV}}$, then $\varphi$ does not enter any admitted hard mission obligation:

$$\varphi \in Clai{m}_{\mathrm{H}}\wedge (\mathcal{E}\cup \mathrm{\Gamma }\cup {\mathrm{\Omega }}_{\mathrm{UAV}})⊭\varphi \Rightarrow \varphi \notin Claims\left(Hard\left(G^{\ast }\right)\right).$$

(52)

This is a direct consequence of the untrusted-isolation proof obligation $P{O}_{\mathrm{U}}$. Unverified semantic increments remain in pending items, clarification requests, or the audit trail.

Property 4: Bounded closure. Algorithm 1 performs at most $B_c$ candidate-generation iterations (counter b) followed by at most $B_r$ refinement iterations (counter r), with duplicate candidates prevented from resubmission. The total number of LLM invocations is therefore bounded by

$$T\le B_c+B_r.$$

(53)

This property establishes EAMSR as a bounded admission-closure process.

Assumptions and guarantee boundary. Properties 1–4 are conditional on the five explicit assumptions in Table 10. Under A1–A5, an ADMIT decision enforces the specified admission predicate by construction; the properties do not constitute machine-verified guarantees of the complete operational system, and A5 makes explicit that a missing witness is never interpreted as proof of infeasibility unless the backend conclusively establishes it (Equation (47)).

Algorithm 1 EAMSR mission admission via evidence-carrying MAC.

Require: Instruction x, context $A_{\mathrm{ctx}}$, invariants $I_{\mathrm{prot}}$, policy $\mathrm{\Gamma }$, evidence $\mathcal{E}$, backend ${\mathrm{\Omega }}_{\mathrm{UAV}}$, candidate budget $B_c$, refinement budget $B_r$ Ensure: $decision$, $G^{\ast }$, $\pi$, ${\mathcal{T}}_{\mathrm{audit}}$   1: Extract anchors $\mathcal{A}$ from x.   2: Initialize $\mathcal{C}\leftarrow ⌀$, $b\leftarrow 0$, $r\leftarrow 0$, $decision\leftarrow$ Unset, $G^{\ast }\leftarrow \perp$, $\pi \leftarrow \perp$.   3: while $b<B_c$ do   4:    Generate response and parse clause set ${\mathcal{K}}^{\left(b\right)}$ via Equation (7).   5:    if the response is parseable then   6:      Assemble candidate $C_{b+1}$.   7:      if $C_{b+1}$ is not a duplicate of any existing candidate then   8:         Add $C_{b+1}$ to $\mathcal{C}$.   9:      end if 10:    else 11:      Record ParseFailure in ${\mathcal{T}}_{\mathrm{audit}}$. 12:    end if 13:    $b\leftarrow b+1$. 14: end while 15: if $\mathcal{C}=⌀$ then 16:    $decision\leftarrow \mathrm{CLARIFY}$; assemble ${\mathcal{T}}_{\mathrm{audit}}$ and 17:    return $decision,G^{\ast },\pi ,{\mathcal{T}}_{\mathrm{audit}}$. 18: end if 19: while $decision=$ Unset and $r\le B_r$ do 20:    Apply $GovOK$ to obtain ${\mathcal{C}}_{\mathrm{gov}}$. 21:    if ${\mathcal{C}}_{\mathrm{gov}}=⌀$ then 22:      $\mathcal{Q}\leftarrow \mathrm{Diagnose}(\mathcal{C},\mathrm{\Gamma })$. 23:      if $\mathcal{Q}$ is governance-remediable and $r<B_r$ then 24:         $\mathcal{C}\leftarrow \mathrm{Refine}(\mathcal{C},\mathcal{Q},\mathrm{\Gamma })$;   $r\leftarrow r+1$. 25:      else 26:         $decision\leftarrow \mathrm{REJECT}$ if $\mathcal{Q}$ is an immutable/protected-requirement conflict, else $\mathrm{CLARIFY}$. 27:      end if 28:    else 29:      Compute $\chi$; screen $\mathrm{Consistent}\left({\mathcal{C}}_{\mathrm{gov}}\right)$. 30:      if $\mathrm{Consistent}\left({\mathcal{C}}_{\mathrm{gov}}\right)$ then 31:         Select $C^{\ast }$ via Equation (32); run the bounded witness search for $C^{\ast }$ (Equation (47)). 32:         if $\mathrm{BackendStatus}\left(C^{\ast }\right)$= WitnessFound with witness $\pi$ then 33:            $decision\leftarrow \mathrm{ADMIT}$;   $G^{\ast }\leftarrow G\left(C^{\ast }\right)$. 34:         else 35:            $\mathcal{Q}\leftarrow \mathrm{Diagnose}(C^{\ast },{\mathrm{\Omega }}_{\mathrm{UAV}})$. 36:            if $\mathcal{Q}$ is backend-remediable and $r<B_r$ then 37:               $\mathcal{C}\leftarrow \mathrm{Refine}(C^{\ast },\mathcal{Q},\mathrm{\Gamma })$;   $r\leftarrow r+1$. 38:            else if $\mathrm{BackendStatus}\left(C^{\ast }\right)$= Conclusiveinfeasible then 39:               $decision\leftarrow \mathrm{REJECT}$. 40:            else 41:               $decision\leftarrow \mathrm{CLARIFY}$ (Inconclusive or operator input required). 42:            end if 43:         end if 44:      else 45:         $\mathcal{Q}\leftarrow \mathrm{Diagnose}\left({\mathcal{C}}_{\mathrm{gov}}\right)$. 46:         if $\mathcal{Q}$ is consequence-remediable and $r<B_r$ then 47:            $\mathcal{C}\leftarrow \mathrm{Refine}({\mathcal{C}}_{\mathrm{gov}},\mathcal{Q},\mathrm{\Gamma })$;   $r\leftarrow r+1$. 48:         else 49:            $decision\leftarrow \mathrm{CLARIFY}$. 50:         end if 51:      end if 52:    end if 53: end while 54: if $decision$= Unset then 55:    $decision\leftarrow \mathrm{CLARIFY}$. 56: end if 57: Assemble ${\mathcal{T}}_{\mathrm{audit}}$ and 58: return $decision,G^{\ast },\pi ,{\mathcal{T}}_{\mathrm{audit}}$.

Table 10. Assumptions underlying the specification-level properties (Properties 1–4).

ID	Assumption	Content
A1	Anchor representation	Validated anchors correctly represent the user hard intent relevant to admission (Property 2).
A2	Evidence fidelity	Admitted evidence sources are correct, current, and correctly prioritized.
A3	Governance fidelity	Authority and mutability policies correctly encode the intended operational rules.
A4	Backend fidelity	${\mathrm{\Omega }}_{\mathrm{UAV}}$ is an adequate task-level abstraction for the evaluated admission decision.
A5	Witness semantics	A positive witness establishes model-level executability; absence of a witness is not treated as proof of infeasibility unless infeasibility is conclusively established under the declared backend model (Equation (47)).

4. Experiments and Evaluation

The experiments address three questions: whether joint admission reduces unwarranted admission; whether authority and mission-consequence constraints prevent feasibility from being recovered through semantic migration; and whether backend witnesses close admission decisions with respect to UAV task-level constraints. The evaluation boundary lies between task submission and task planning, and does not cover continuous trajectory control, flight-control stability, or runtime obstacle avoidance.

4.1. Evaluation Protocol

The evaluation protocol comprises the benchmark and human labels (EAMSR-Bench), the controlled comparison configurations and their coverage boundary, the metric definitions with uncertainty intervals, and the implementation settings.

4.1.1. EAMSR-Bench and Human Labels

EAMSR-Bench is a controlled, internally constructed architecture-stress benchmark. It contains 120 natural-language UAV mission instructions, crossing six mission scenarios with six admission-risk types. Each sample includes a task instruction, trusted context, protected operational constraints, evidence base, governance policy, task-level backend model, and human admission label. The crossed design places multiple risk types in each scenario, so that conclusions do not depend on a single task type.

Instruction generation. The 120 instructions are in Chinese, authored by the research team from Chinese-language operator manuals, civil-aviation regulations, and mission-planning guidelines. No instructions were copied from operational flight logs or obtained from external UAV operators. The six mission scenarios—powerline inspection, disaster-area search, campus delivery, river monitoring, bridge inspection, and communication-limited tasks—were selected to cover the principal UAV mission categories identified in the operational literature. The six admission-risk types were defined by the research team before benchmark construction, derived from the proof-obligation structure of the EAMSR framework. The benchmark was developed concurrently with the framework: risk-type definitions were motivated by the proof obligations, but the specific instructions, evidence bases, and governance policies were authored independently of the EAMSR implementation code. This concurrent development creates a risk of circular validation, which is acknowledged in Section 4.6; the results should therefore be interpreted as performance under a controlled, internally designed benchmark. English renderings in this paper (e.g., Table 11 and Figure 2, Figure 3, Figure 4, Figure 5, Figure 6 and Figure 7) are glosses of the Chinese originals.

Table 11. Overall admission performance. Primary-tier metrics ($Ac{c}_{\mathrm{bin}}$, UAR) are binary ADMIT/non-ADMIT and fair across all configurations. Secondary-tier metric ($Acc$) is three-class accuracy, post hoc mapped for non-EAMSR configurations. Bold values indicate the best result in each column.

Configuration	Primary (Binary)		Secondary/Diagnostic
	${\mathit{A}\mathit{c}\mathit{c}}_{\mathbf{bin}}$	UAR	Acc	ECR	UBR	PIR	WSR	CNR	ATR
Direct-LLM	76.7	35.9	54.2	61.4	28.2	80.6	67.5	31.1	12.5
LLM+Backend	85.8	21.8	68.3	66.7	35.9	85.4	88.9	42.2	25.0
Rule-Gate	90.0	15.4	74.2	72.8	41.0	96.1	82.6	50.0	48.3
Greedy Relaxation	91.7	12.8	78.3	70.2	47.4	91.2	94.1	56.7	52.5
EAMSR	100.0	0.0	93.3	96.5	94.7	100.0	100.0	88.9	98.3

Note: All values are percentages. $Ac{c}_{\mathrm{bin}}$ = binary admission correctness (ADMIT/non-ADMIT agreement with human labels); UAR = unwarranted admission rate (unwarranted ADMIT / 78 non-admissible tasks); Acc = three-class admission accuracy; ECR = evidence coverage rate; UBR = USI blocking rate; PIR = protected-invariant preservation rate; WSR = witness success rate; CNR = consequence clarification rate; ATR = audit-trail completeness rate. $Ac{c}_{\mathrm{bin}}\ge Acc$ because CLARIFY↔REJECT errors do not affect binary correctness. Instruction entries are English glosses of the Chinese originals; full bilingual records are in the reproducibility package.

Figure 2. Overall admission performance under the shared task-level protocol. (a) Binary admission accuracy ($Ac{c}_{\mathrm{bin}}$) versus unwarranted admission rate for EAMSR and four controlled comparison configurations. (b) Heatmap of primary, secondary, and diagnostic metrics; lower values are better for UAR, whereas higher values are better for all other metrics.

Figure 3. Backend-witness margins across UAV scenarios. (a) Minimum return-energy margin for admitted tasks. (b) Minimum time-window margin for the same tasks. Dashed horizontal lines denote the overall mean margin across scenarios; all scenario-level minima remain above the zero-margin feasibility boundary.

Figure 4. Ablation-induced unwarranted admission and runtime overhead. (a) UAR for the full system and six ablated variants. (b) Mean admission time under the same protocol; the dashed vertical line denotes the Full EAMSR mean admission time (8.7 s). Removing the backend witness reduces latency most strongly but causes the largest increase in direct admission of inadmissible tasks. (BW-Operator is the audit field passing governance-layer authorization status to the backend interface, not an independent backend proof obligation.).

Figure 5. AirSim-E1 energy-infeasible mission and counterfactual execution. The candidate mission requires 91.7 Wh, exceeding both the 80.0 Wh battery capacity and the 64.0 Wh mission-usable energy after reserving 20% for return. EAMSR rejects the mission before takeoff; forced execution enters the unsafe depletion region during return.

Figure 6. AirSim-E2 restricted-airspace conflict and authorized refinement. The initial route violates the 20 m restricted-airspace buffer and is not admitted. EAMSR requests operator authorization; after authorization, a downstream planner produces a bypass route whose task-level witness satisfies the airspace constraint.

Figure 7. AirSim-E3 admitted grid-inspection mission with backend-witness closure. The mission satisfies evidence, authority, consequence-consistency, and task-level backend conditions. Its estimated energy use is 38.4 Wh, leaving 52.0% battery and a 32.0-percentage-point margin above the return-reserve threshold.

The six admission-risk types define the admission challenge of each task. T1 (normal-risk) tasks are well-specified, evidence-sufficient, and feasible under the given context and backend model, so that all proof obligations are satisfied. T2 (evidence-insufficient) tasks lack evidential support for key parameters or conditions. T3 (authority-conflicting) tasks request actions that conflict with authority rules, governance policy, or mutability constraints. T4 (LLM-assumption contamination) tasks are susceptible to unsupported assumptions introduced during semantic interpretation or repair. T5 (backend-infeasible) tasks appear reasonable at the language level but violate backend constraints on energy, airspace, geofence, payload, communication, or time windows. T6 (consequence-ambiguous) tasks admit multiple possible mission-consequence profiles, so that the correct outcome depends on resolving consequence-profile ambiguity during mission-consequence screening. Each task is generated by instantiating one scenario with one risk type: scenario-specific mission content (objectives, target areas, and operating conditions) is combined with a risk-type template that injects the corresponding proof-obligation failure or consequence ambiguity into the instruction, evidence base, or context, while T1 templates leave all obligations satisfiable. The resulting 120 tasks contain 30 T1 and 18 tasks of each of T2–T6 per the crossed design (Table 12). T1 is assigned more samples than individual risk types because it is the admissible baseline and provides a stronger assessment of whether the added governance layers cause excessive false clarification or rejection of otherwise admissible missions.

Table 12. EAMSR-Bench composition.

Scenario	T1	T2	T3	T4	T5	T6	Total
S1 Powerline inspection	5	3	3	3	3	3	20
S2 Disaster-area search	5	3	3	3	3	3	20
S3 Campus delivery	5	3	3	3	3	3	20
S4 River monitoring	5	3	3	3	3	3	20
S5 Bridge inspection	5	3	3	3	3	3	20
S6 Communication-limited task	5	3	3	3	3	3	20
Total	30	18	18	18	18	18	120

The human labels include 42 ADMIT, 47 CLARIFY, and 31 REJECT samples (Table 13). ADMIT means that the task can enter the planning chain under the given context and governance policy. CLARIFY means that evidence must be added, authorization must be obtained, or a consequence-profile ambiguity must be resolved. REJECT means that no admissible resolution exists within the declared trusted context, governance policy, protected constraints, and conclusively evaluated backend conditions.

Table 13. Reference label distribution by mission scenario.

Scenario	ADMIT	CLARIFY	REJECT	Total
S1 Powerline inspection	7	8	5	20
S2 Disaster-area search	7	8	5	20
S3 Campus delivery	7	7	6	20
S4 River monitoring	7	8	5	20
S5 Bridge inspection	7	8	5	20
S6 Communication-limited	7	8	5	20
Total	42	47	31	120

Human labels were assigned through a blinded dual-annotation protocol by non-developer domain experts. Each sample was annotated independently by two laboratory domain experts, each with over three years of UAV mission-planning and autonomous-system research experience, who received identical raw inputs (the instruction, trusted context, protected invariants, evidence base, governance policy, and backend model) and were blind to all system outputs, including EAMSR predictions and audit trails. The annotators were not involved in designing the EAMSR admission logic or the benchmark risk-type taxonomy; they received the benchmark samples and a labeling protocol but no information about the framework’s proof-obligation structure or decision rules. This separation mitigates, though does not fully eliminate, the risk that the labels encode the same admission logic as the framework, because the benchmark instructions and risk-type definitions were authored by the research team that also developed EAMSR (Section 4.1.1). Annotators followed a fixed procedure that checks, in turn, evidence sufficiency, authority and governance compliance, LLM-assumption risk, backend feasibility, and consequence ambiguity before assigning a label. The boundary between CLARIFY and REJECT was operationalized by a remediability criterion: if the gap can be filled by adding evidence, obtaining authorization, or resolving a consequence-profile ambiguity, the label is CLARIFY; if the request conflicts with an immutable or protected admission condition or is conclusively infeasible under the declared backend model, so that no admissible resolution exists within the declared trusted context, governance policy, protected constraints, and admissible refinement space, the label is REJECT. Disagreements were resolved by a senior annotator whose decision was binding, with escalation to a domain-expert panel majority vote for novel cases. Inter-annotator agreement was measured by pairwise Cohen’s kappa over the three labels, together with a focused CLARIFY/REJECT agreement rate computed on samples where at least one annotator assigned CLARIFY or REJECT, since this boundary is the most error-prone. The overall pairwise Cohen’s $\kappa$ was 0.86, with class-specific agreement of 1.00 for ADMIT, 0.83 for CLARIFY, and 0.90 for REJECT. Among the 78 non-ADMIT cases requiring discrimination between CLARIFY and REJECT, the two initial annotators agreed on 67 cases, corresponding to a focused CLARIFY/REJECT agreement of 85.9% (67/78). Initial disagreements occurred on 11 of 120 samples (9.2%), all on the CLARIFY–REJECT boundary (14.1% of the 78 non-ADMIT cases); the senior annotator resolved 8 and a three-member domain-expert panel resolved 3. The complete list of disagreement cases and their adjudication outcomes is reported in the reproducibility package.

Independently authored external test set. To provide a first layer of independent-authoring robustness against the circular-validation risk, we also constructed an external test set of 48 natural-language mission requests authored independently of the EAMSR development team. The requests were prepared by UAV mission-planning practitioners who were not involved in designing the framework, the risk-type taxonomy, the prompts, or the admission rules, and who had no access to the EAMSR-Bench instructions; they received only a task-submission template and the six scenario descriptions. The external requests cover the same six mission scenarios and contain phrasings, omission patterns, and constraint combinations that were not anticipated by the internal risk-type templates. Reference labels were assigned under the same blinded dual-annotation and adjudication protocol described above, with annotators blind to all system outputs, yielding 16 ADMIT, 19 CLARIFY, and 13 REJECT tasks. The external set is used exclusively for evaluation; no prompt, parameter, or threshold was adjusted using these tasks. This experiment evaluates robustness to independently authored mission requests; it does not constitute operational external validation, because the requests remain within the same admission ontology, decision semantics, and task-level evaluation boundary. Results on this set are reported in Section 4.5.

4.1.2. Comparison Configurations and Coverage Boundary

The experiments use five controlled comparison configurations to isolate different admission capabilities. Four are LLM-based configurations (Direct-LLM, LLM+Backend, Rule-Gate, Greedy Relaxation); they are not full reproductions of SafeGate, DUPLEX, or UAV-NL-STL-Repair [12,13,19]. The fifth, Deterministic-MAC, is a non-LLM attribution baseline described below.

Direct-LLM directly submits model output as a UAV task specification, without evidence, authority, semantic-increment, or backend admission checks. LLM+Backend admits a task only according to task-level backend feasibility, and is used to test whether the existence of a plan can replace joint admission. Rule-Gate checks explicit airspace, energy, payload, communication, and time constraints, but does not trace clause provenance or modification authority. Greedy Relaxation relaxes infeasible tasks according to a fixed priority order, representing a repair strategy that restores feasibility without constraining semantic migration.

Deterministic-MAC is a deterministic, non-LLM admission system that uses the same ontology, evidence base, governance policy, proof-obligation gate, and backend model as EAMSR, but replaces LLM candidate generation with a deterministic template-mapping procedure: requirement anchors are extracted by the same deterministic preprocessing used in EAMSR, and each anchor is mapped to canonical ontology clauses through a fixed rule table without generative completion. Candidate clauses outside the canonical rule table are not proposed, and refinements are enumerated in a fixed priority order over governance-valid modifications. Deterministic-MAC therefore retains the full admission architecture while removing the LLM proposal mechanism, and natively produces three-class decisions under the same admission predicate. It directly tests whether the LLM provides meaningful incremental value or merely generates candidate clauses that are subsequently governed by conventional rule-based mechanisms.

All LLM-based configurations share the same task texts, trusted context, task ontology, backend model, LLM backbone (GPT-4-class, temperature 0), candidate-generation budget ($B_c=5$), refinement budget ($B_r=3$), malformed-response policy (Section 4.1.4), and computational resources. Deterministic-MAC shares all non-LLM components and uses no language model. No configuration receives additional prompts, fewer parsing constraints, or a larger search budget than the others. The differences come solely from whether evidence tracing, authority checking, untrusted-semantic-isolation enforcement, and mission-consequence screening are included in the admission decision (Table 14). Configurations that do not natively distinguish CLARIFY from REJECT (Direct-LLM, LLM+Backend, Rule-Gate, and Greedy Relaxation) use the following post hoc mapping for evaluation only: a not-ADMIT output is classified as REJECT if the corresponding backend diagnosis is ConclusiveInfeasible, and as CLARIFY otherwise. For Direct-LLM (no runtime backend use), the diagnosis is applied post hoc and does not alter its ADMIT/non-ADMIT output. This mapping ensures that three-class accuracy is computed under a consistent rule, but it should be interpreted with caution because these configurations lack the governance information needed for a principled CLARIFY/REJECT distinction. The unwarranted admission rate, which is binary (ADMIT vs. not-ADMIT), provides a shared admission-oriented comparison across all configurations and does not depend on the mapping. The comparison is organized in two tiers: the primary tier uses binary ADMIT/non-ADMIT outcomes (UAR and binary admission correctness), which are fair across all configurations; the secondary tier uses three-class accuracy, which is native to EAMSR but post hoc mapped for the other configurations and should be interpreted as supplemental rather than as direct architecture-level superiority evidence.

Table 14. Capability boundaries of the comparison configurations. All configurations that use the backend share the same backend model. A ✓ indicates that the corresponding capability is implemented in the configuration; “—” indicates that the capability is not present.

Configuration	Evidence	Authority	USI	Consequence	Backend	Decision
	Tracing	Checking	Isolation	Screening	Witness	Granularity
Direct-LLM	—	—	—	—	—	ADMIT/not-ADMIT
LLM+Backend	—	—	—	—	✓	ADMIT/not-ADMIT
Rule-Gate	—	—	—	—	✓ (rule-based)	ADMIT/not-ADMIT
Greedy Relaxation	—	—	—	—	✓ (greedy repair)	ADMIT/not-ADMIT
Deterministic-MAC	✓	✓	✓	✓	✓	ADMIT/CLARIFY/REJECT
Full EAMSR	✓	✓	✓	✓	✓	ADMIT/CLARIFY/REJECT

4.1.3. Evaluation Metrics

The experiments use nine task-level metrics organized into three tiers:

$$\begin{array}{cccccc}\hfill Ac{c}_{\mathrm{bin}}& ={\displaystyle \frac{N_{\mathrm{bin},\mathrm{correct}}}{N_{\mathrm{all}}}},\hfill & \hfill Ac{c}_{\mathrm{adm}}& ={\displaystyle \frac{N_{\mathrm{correct}}}{N_{\mathrm{all}}}},\hfill & \hfill UAR& ={\displaystyle \frac{N_{\mathrm{UW}}}{N_{\neg \mathrm{ADM}}}},\hfill \\ \hfill ECR& ={\displaystyle \frac{N_{\mathrm{hard},\mathrm{evidenced}}}{N_{\mathrm{hard}}}},\hfill & \hfill UBR& ={\displaystyle \frac{N_{\mathrm{blocked}\mathrm{USI}}}{N_{\mathrm{USI}}}},\hfill & \hfill PIR& ={\displaystyle \frac{N_{\mathrm{preserved}}}{N_{\mathrm{protected}}}},\hfill \\ \hfill WSR& ={\displaystyle \frac{N_{\mathrm{ADMIT},\mathrm{witness}}}{N_{\mathrm{ADMIT}}}},\hfill & \hfill CNR& ={\displaystyle \frac{N_{\mathrm{correct}\mathrm{CLARIFY}\mathrm{on}\mathrm{T}6}}{N_{\mathrm{T}6}}},\hfill & \hfill ATR& ={\displaystyle \frac{N_{\mathrm{complete}\mathrm{audit}}}{N_{\mathrm{all}}}}.\hfill \end{array}$$

(54)

The primary tier ($Ac{c}_{\mathrm{bin}}$ and UAR) measures binary ADMIT/non-ADMIT correctness and is fair across all configurations. $Ac{c}_{\mathrm{bin}}$ counts a decision as correct if the binary admission verdict (ADMIT vs. not-ADMIT) matches the reference label; CLARIFY and REJECT are both treated as not-ADMIT. The secondary tier ($Ac{c}_{\mathrm{adm}}$ and per-class precision, recall, and F1) measures three-class admission accuracy, which is native to EAMSR but post hoc mapped for non-EAMSR configurations. The diagnostic tier (ECR, UBR, PIR, WSR, CNR, and ATR) explains which admission mechanism fails, not as independent evidence of overall superiority. ECR, UBR, PIR, and ATR are audited post hoc on the final task artifacts of all configurations using unified human annotations, without requiring comparison configurations to maintain EAMSR’s internal fields.

Metric auditing protocol. The diagnostic metrics are evaluated under the following counting rules. ECR is evaluated at the atomic hard-clause level: only clauses with $Sup\left(\kappa \right)=\mathrm{Y}$ count as evidenced, whereas $Sup\left(\kappa \right)=\mathrm{N}$ (contradicted or invalid source) and $Sup\left(\kappa \right)=\mathrm{U}$ (insufficient evidence) do not. A clause appearing multiple times in the same contract is counted once. UBR is evaluated over unique LLM-introduced atomic hypothetical claims ($Clai{m}_{\mathrm{H}}$); reused and derived claims are excluded from the denominator. PIR is evaluated over task-applicable protected invariants, determined by matching each task’s scenario and payload against the protected-invariant registry. ATR is complete only if all mandatory audit fields applicable to the decision path are populated; structurally non-applicable fields (e.g., refinement history for a direct ADMIT) may be null but must be explicitly recorded as not-applicable. Post hoc diagnostic assessors had access to configuration labels; this is a limitation of the diagnostic analysis.

For the accuracy metrics, we report Wilson score 95% confidence intervals for $Ac{c}_{\mathrm{bin}}$ and $Ac{c}_{\mathrm{adm}}$, and a Clopper–Pearson 95% upper bound for UAR when zero unwarranted admissions are observed. Per-class precision, recall, and F1 are reported together with their macro averages. Table 15, Table 16 and Table 17 use task-level statistics over the 120 tasks.

Table 15. Attribution of the eight residual admission errors.

#	Instruction (Abbrev.)	Risk	Ref.	Pred.	Failed Stage	Root Cause
1	Check nearby lines, handle anomalies	T4	CLARIFY	REJECT	USI PO	Over-triggers on vague phrasing; detects potential LLM assumption where instruction is genuinely clarifiable
2	Survey area, report findings as needed	T4	CLARIFY	REJECT	USI PO	Over-detects untrusted semantic increment in instruction with valid clarification path
3	Check A-area, optionally B-area, expand if clear	T6	CLARIFY	REJECT	MCS	Over-rejects on conditional branching; treats multi-path consequences as violation
4	Inspect zone, adapt collection if necessary	T4	CLARIFY	REJECT	USI PO	Over-triggers on adaptive language; instruction is clarifiable rather than rejection-level
5	Visit sampling points, skip duplicates, adjust strategy	T6	CLARIFY	REJECT	MCS	Over-rejects on adaptive collection logic; treats strategy adjustment as rejection-level ambiguity
6	Cancel altitude limit, use all battery for LiDAR	T3	REJECT	CLARIFY	Auth./Mut. PO	Immutable-constraint violations (altitude, return reserve); system detects conflict but misclassifies as clarification need
7	Survey disaster area, decide rescue method	T4	REJECT	CLARIFY	USI PO	Insufficient detection of untrusted semantic increments; allows clarification for a task labeled REJECT
8	Ignore geofence for emergency delivery	T4	REJECT	CLARIFY	USI PO	LLM assumes emergency overrides geofence; untrusted semantic increment treated as clarifiable rather than rejection-level

Note: Ref. = adjudicated reference label; Pred. = predicted decision; PO = proof obligation; MCS = mission-consequence screening; USI = untrusted semantic isolation. T3–T6 denote the admission-risk types defined in Section 4.1.1.

Table 16. Confusion matrix for EAMSR ($n=120$). Rows are human labels; columns are system decisions. Bold row labels indicate the ground-truth classes, with sample counts in parentheses.

	ADMIT	CLARIFY	REJECT
ADMIT (42)	42	0	0
CLARIFY (47)	0	42	5
REJECT (31)	0	3	28

Table 17. Contract instantiation and risk handling.

(a) Contract instantiation
Instruction Type	AC	CP	CR	EC	PD
Explicit	97.8	94.5	92.4	97.9	95.0
Semi-structured	93.6	90.8	89.1	95.1	91.3
Ambiguous	88.9	86.3	84.7	91.8	88.6
Overall	93.4	90.5	88.7	94.9	91.6
(b) Dominant risk handling
Risk			Failed Step	HR	CFH
T2 Evidence-insuff.			Evidence PO	83.3	100.0
T3 Authority-conflict			Auth/Mut PO	94.4	94.4
T4 LLM-assump. contam.			USI PO	88.9	72.2
T5 Backend-infeasible			Backend PO & Ref.	83.3	100.0
T6 Consequence-ambig.			MCS	88.9	88.9

Note: Values are percentages. AC = anchor coverage, computed over validated anchors using the $Cover$ relation (Equation (17)); CP = clause precision and CR = clause recall, computed over the candidate clauses generated for each task; EC = evidence coverage, PD = pending-content detection, HR = handling rate, and CFH = correct failure handling, each computed per task and averaged within the corresponding row’s task set.

Additional diagnostic metrics used in Table 17 and Table 18 (AC, CP, CR, EC, PD, HR, CFH, FR, PCP, AHP, WCR, UCT) follow the same auditing protocol: each metric specifies a unit of analysis, numerator, denominator, and treatment of non-applicable cases. AC, CP, CR, and EC are evaluated per task over validated anchors or applicable clauses; PD is binary per generation attempt; HR and CFH are computed per task within each risk-type group; FR, PCP, AHP, WCR, and UCT are computed over tasks that entered refinement. Non-applicable cases (e.g., refinement metrics for tasks that did not enter refinement) are excluded from the denominator and recorded explicitly.

Table 18. Refinement, clarification, and rejection behavior.

(a) Behavior by risk type
Risk	Cases	Ref.	CLAR.	REJ.	Err.
Evidence insuff.	18	0	15	3	0
Auth./protect. inv.	18	0	0	17	1
LLM assum. contam.	18	0	9	4	5
Backend infeasib.	18	12	2	4	0
Conseq. ambiguity	18	0	16	0	2
Total	90	12	42	28	8
(b) Refinement comparison
Config.	FR	PCP	AHP	WCR	UCT
Greedy Rel.	61.1	88.9	76.7	55.6	23.3
EAMSR	66.7	100.0	100.0	100.0	0.0

Note: Ref. = refinement; CLAR. = CLARIFY; REJ. = REJECT; Err. = errors. Ref./CLAR./REJ. count correctly handled tasks by system outcome; erroneous decisions appear only in the Err. column. FR = feasibility-restoration rate; PCP = protected-constraint preservation; AHP = anchored-hard preservation; WCR = witness-closed refinement; UCT = unconfirmed consequence-profile transition. Panel (a) rates are computed per task within each 18-task risk-type group; panel (b) rates are computed over the 18 backend-infeasible tasks that entered refinement, of which 12 were restored (FR = 66.7%).

The LLM-backbone robustness panel uses five repeated runs to evaluate run-to-run stability. Decision consistency (DC) measures the agreement among repeated runs:

$$DC={\displaystyle \frac{1}{N}}{\displaystyle \sum _{i=1}^N}{\displaystyle \frac{{\max }_{c\in \{\mathrm{ADMIT},\mathrm{CLARIFY},\mathrm{REJECT}\}}{n}_{i,c}}{R}},$$

(55)

where N is the number of tasks, $R=5$ is the number of repeated runs, and $n_{i,c}$ is the number of runs in which task i received decision class c. A DC value of 1.0 indicates unanimous decisions across all runs.

4.1.4. Implementation Settings

The main experiments run on an Ubuntu 22.04 workstation with an Intel Xeon Gold 6330 CPU and an NVIDIA RTX 4090 GPU. The main experiments use gpt-4-turbo-preview as the primary candidate-generation backbone; Qwen2.5-72B-Instruct and deepseek-v3 are used to assess backbone sensitivity (Table 19). Because API-served models and backend generation pipelines may remain nondeterministic despite fixed settings, five repeated runs with predefined seeds are used to characterize run-to-run decision stability. The same prompts and ontology are used across all backbones. Malformed responses consume one candidate-generation attempt each; at most two retries are permitted for a malformed response, subject to the remaining candidate budget $B_c$, and a task whose attempts are exhausted without a parseable response is recorded as BUDGET_EXCEEDED. The governance and backend layers are designed to reduce dependence on the candidate-generation backbone: all evidence, authority, mutability, consequence, and backend checks operate on the extracted clauses independently of which model produced them. The robustness results in Table 20(b) show that the three backbones produce comparable three-class accuracy (91.7–93.3%) and low UAR (0.0–1.3%), though small backbone-dependent variation remains, as reflected in the decision-consistency metric (DC 92.9–95.0%). API responses were collected between January and March 2025 using the provider snapshots available at that time; the providers did not expose a more immutable model snapshot identifier for these endpoints, so exact future reproduction of proprietary-model outputs cannot be guaranteed. We used no function calling or JSON-mode constraints; the system prompt specified the UAV ontology slots and directed the LLM to return candidate clauses in a delimited text format. Responses were parsed by a deterministic regex-based extractor. No few-shot examples were included in the prompt, and no benchmark instructions were used during prompt development; the system prompt was authored from the ontology specification before the benchmark was constructed. The exact system and user prompts are archived in the reproducibility package.

Table 19. LLM backbone configurations.

Backbone	Model ID	Provider	Temp.	Top-p	Max Tok.	Seed
GPT-4-class	gpt-4-turbo-preview	OpenAI API	0	1.0	4096	42
Qwen2.5-72B	Qwen2.5-72B-Instruct	Alibaba Cloud	0	1.0	4096	42
DeepSeek-class	deepseek-v3	DeepSeek API	0	1.0	4096	42

Table 20. Robustness.

(a) Controlled scenario variation
Variation		${\mathit{DC}}_{\mathbf{pert}}$	UAR	PIR	CNR	ATR
New target layouts		92.4	0.0	100.0	88.0	98.4
New NFZ layouts		91.7	0.0	100.0	86.7	98.0
New comm. maps		90.8	1.3	100.0	85.6	97.6
New time windows		91.5	0.0	100.0	86.2	97.9
Obj.-aug.		90.6	1.3	100.0	84.9	97.1
Overall		91.4	0.5	100.0	86.3	97.8
(b) LLM-backbone robustness
LLM Backbone	Acc	UAR	ECR	PIR	WSR	DC
GPT-4-class	93.3	0.0	94.7	100.0	100.0	95.0
Qwen2.5-72B	92.5	0.0	93.4	100.0	100.0	93.8
DeepSeek-class	91.7	1.3	92.6	100.0	100.0	92.9
Overall	92.5	0.4	93.6	100.0	100.0	93.9

Note: Values are percentages. Panel (a) is a controlled sensitivity analysis, not an accuracy evaluation against independent ground truth: $D{C}_{\mathrm{pert}}$ = decision consistency, the fraction of perturbed instances whose decision matches the designated reference outcome re-derived under the declared governance policy and backend model; each category contains 120 perturbed tasks; UAR denominators are the designated non-admissible references per category. UAR in panel (a) is computed against the same designated references. Acc = admission accuracy; UAR = unwarranted admission rate; PIR = protected-invariant preservation rate; CNR = consequence-sensitive clarification rate; ATR = audit-trail completeness rate; ECR = evidence coverage rate; WSR = witness success rate; DC = decision consistency.

The total budget for candidate generation and refinement is set to 8, decomposed into a candidate-generation budget of $B_c=5$ and a refinement budget of $B_r=3$; together with the recording of repeated candidates, this bounds the number of candidate-generation and refinement steps by $T\le B_c+B_r=8$ (Property 4). This budget was selected empirically: pilot runs showed that successful admissions typically converge within 3–5 candidates and 1–2 refinements, so $B_c=5$ and $B_r=3$ provide headroom without incurring excessive API cost. The mission-consequence distance threshold ${ϵ}_{\chi }=0.15$ was calibrated so that candidates differing in return-reserve margin, airspace clearance, or mission objective are separated, while minor variations in optional preferences remain compatible. Each task is repeated five times with different random seeds. The main reported decision uses the first run (seed = 42); the five runs collectively estimate run-to-run stability via the decision-consistency metric (DC, defined in Equation (55)). Five repetitions were chosen as a pragmatic compromise between API cost and characterization of run-to-run variability. The observed spread across five runs (Table 21; sample SD $\le 2.3$ percentage points for all backbones) suffices to characterize residual serving-side nondeterminism at temperature 0.

Table 21. Five-run repeated-run statistics (mean ± sample SD over five runs).

Backbone	Acc (Mean ± SD)	UARr (Mean ± SD)	DC
GPT-4-class	93.3 ± 1.5	0.0 ± 0.0	95.0
Qwen2.5-72B	92.5 ± 2.0	0.4 ± 0.9	93.8
DeepSeek-class	91.7 ± 2.3	0.8 ± 1.3	92.9

Development-set construction and separation. The parameters $B_c$, $B_r$, ${ϵ}_{\chi }$, ${\tau }_k$, and $\lambda$ were calibrated on a 20-task development subset that is separate from the 120-task evaluation set. The development subset was constructed by the same research team using the same scenario templates and risk-type definitions as EAMSR-Bench, but with different specific instructions, evidence bases, and context parameters. The subset contains 5 T1 (normal-risk) and 3 tasks of each of T2–T6, following the same risk-type distribution as the evaluation set. No evaluation-set task was used during parameter calibration. The development subset was not independently annotated; its labels were assigned by the research team for calibration purposes only. This separation prevents test-set tuning but does not eliminate the broader co-development concern discussed in Section 4.6.

The backend uses the simulator of Section 3.5 with depth limit $D_{\max }=20$, a 1 s timestep, and a 5 s per-contract wall-clock budget.

Because the same L1 backend model serves both benchmark label construction and admission decisions, we performed a limited cross-check using the conservative L2 parameterization (Section 3.5). Applied to eight backend cross-validation samples (not the three AirSim cases), L2 yielded the same ADMIT/REJECT outcomes as L1, providing a limited consistency check against overly permissive L1 settings.

To further examine whether witness decisions are artifacts of the L1 implementation, an independently implemented task-level backend (Backend-B) was constructed as a cross-check. Backend-B re-implements the task-level witness condition from the written constraint definitions (return reserve, airspace boundary, geofence, payload, communication, time window, and mission objective) using independently written code, an independently chosen state-discretization scheme, and independently implemented energy-consumption and communication models. Both backends necessarily share the constraint semantics, because they must evaluate the same admission conditions, but their numerical approximations and discretization choices differ. Section 4.5 reports the agreement analysis between L1 and Backend-B on 60 sampled MACs.

4.2. Joint Admission Performance and Error Attribution

EAMSR achieves 93.3% three-class accuracy ($Ac{c}_{\mathrm{adm}}$, Wilson 95% CI [87.4%, 96.6%]), correctly handling 112 of 120 tasks: 42 ADMIT, 42 CLARIFY, and 28 REJECT outputs match the human labels. The remaining eight errors occur only between CLARIFY and REJECT; no unwarranted admissions were observed among the 78 non-admissible cases (0/78, 95% Clopper–Pearson upper bound 3.8%). Per-class precision/recall/F1 are 1.000/1.000/1.000 for ADMIT, 0.933/0.894/0.913 for CLARIFY, and 0.848/0.903/0.875 for REJECT, with macro averages of 0.927/0.932/0.929.

Table 15 attributes all eight residual errors to their originating pipeline stages and decision-level causes. The errors fall into two groups: five cases where CLARIFY was mispredicted as REJECT (over-strict rejection), and three cases where REJECT was mispredicted as CLARIFY (over-lenient clarification). No errors involve ADMIT.

The over-strict pattern (CLARIFY→REJECT, Cases 1–5) occurs when conditional or adaptive language (“as needed,” “if necessary”) creates multiple consequence branches that the USI or MCS gate treats as violations rather than clarifiable ambiguities. The over-lenient pattern (REJECT→CLARIFY, Cases 6–8) arises when the system correctly identifies a risk but underestimates its severity—for example, allowing clarification when immutable constraints are violated or when emergency-override instructions introduce untrusted semantic increments. All errors remain on the CLARIFY–REJECT boundary, reflecting the inherent difficulty of distinguishing “unexecutable” from “under-specified.” Full per-case traces are provided in the reproducibility package.

4.2.1. Primary Comparison (Binary)

EAMSR achieves $Ac{c}_{\mathrm{bin}}=100.0\%$ (Wilson 95% CI [96.9%, 100.0%]) and $\mathrm{UAR}=0.0\%$. The four controlled configurations show progressively improving but non-zero UAR (12.8–35.9%) and binary accuracy (76.7–91.7%) (Table 11). Adding backend feasibility reduces UAR from 35.9% to 21.8%; rule gating reduces it further to 15.4%. EAMSR’s gain comes from the conjunction of multiple conditions, not from replacing one check with another (Figure 2).

4.2.2. Secondary Comparison (Three-Class)

EAMSR achieves 93.3% three-class accuracy; all eight residual errors are CLARIFY↔REJECT swaps. Three-class accuracy for the other configurations uses the post hoc mapping defined in Section 4.1.2.

Primary paired comparison (binary). Because EAMSR achieves $Ac{c}_{\mathrm{bin}}=100.0\%$, every binary error in a baseline constitutes a discordant pair. An exact two-sided McNemar test on binary admission correctness (ADMIT vs. not-ADMIT) indicates that the improvement is significant for all four baselines: Direct-LLM ($\Delta =23.3$ pp, $p<0.001$), LLM+Backend ($\Delta =14.2$ pp, $p<0.001$), Rule-Gate ($\Delta =10.0$ pp, exact $p=4.9\times {10}^{-4}$), and Greedy Relaxation ($\Delta =8.3$ pp, $p=0.002$). For UAR, the exact two-sided McNemar test confirms significant improvement over all four baselines: Direct-LLM ($\Delta =35.9$ pp, $p<0.001$), LLM+Backend ($\Delta =21.8$ pp, $p<0.001$), Rule-Gate ($\Delta =15.4$ pp, $p<0.001$), and Greedy Relaxation ($\Delta =12.8$ pp, $p=0.002$). Discordant counts $(b,c)$ for every comparison are archived in data/stats/mcnemar_tests.json.

Secondary paired comparison (three-class). As a secondary analysis, a paired bootstrap test with 10,000 resamples was applied to the 120 per-task three-class outcomes (correct vs. incorrect). EAMSR significantly outperforms Direct-LLM ($\Delta =39.1$ pp, 95% bootstrap CI [28.3, 49.2], $p<0.001$), LLM+Backend ($\Delta =25.0$ pp, [15.0, 34.2], $p<0.001$), Rule-Gate ($\Delta =19.1$ pp, [10.8, 27.5], $p<0.001$), and Greedy Relaxation ($\Delta =15.0$ pp, [7.5, 22.5], $p=0.002$). The three-class deltas exceed the binary deltas because non-EAMSR configurations incur additional CLARIFY/REJECT misclassification under post hoc mapping. All comparisons remain significant after Holm–Bonferroni correction at $\alpha =0.05$.

The overall differences can be further traced to task instantiation and risk-handling locations. As language underspecification increases, anchor coverage and clause recall decrease. Ambiguous instructions still achieve 88.6% pending-content detection, indicating that the system preserves uncertainty.

4.3. Plan Witness and Constrained Refinement

Admitted missions must be closed by backend witnesses, not by textual plausibility. All 42 admitted tasks carried valid backend witnesses, preserved return-energy margins, respected time windows, and produced no airspace or communication violations (Table 22). The 100.0% WSR is a conformance property of the admission rule (an ADMIT is issued only when a witness exists, Equation (48)), not an independent performance finding. Figure 3 shows the minimum return-energy and time-window margins across the six UAV scenarios.

Table 22. Backend witness results.

Scenario	Admitted	WSR	RTH Margin (%)	Window Margin (s)	Airspace Viol.	Comm. Viol.
S1 Powerline inspection	7	100.0	14.8	46.2	0	0
S2 Disaster-area search	7	100.0	10.6	31.5	0	0
S3 Campus delivery	7	100.0	12.3	38.7	0	0
S4 River monitoring	7	100.0	15.1	52.4	0	0
S5 Bridge inspection	7	100.0	8.9	24.8	0	0
S6 Communication-limited task	7	100.0	9.7	28.3	0	0
Overall	42	100.0	11.9	37.0	0	0

Note: WSR = witness success rate; RTH = return-to-home; Viol. = violations.

When no directly admissible contract exists, EAMSR either performs authority-bounded refinement, asks for clarification, or rejects the task. Among the 90 non-normal-risk samples (Table 18), 12 backend-infeasible tasks admit policy-valid refinement. Evidence insufficiency mostly triggers CLARIFY; protected-invariant conflicts mostly trigger REJECT.

Greedy Relaxation and EAMSR achieve comparable feasibility-restoration rates, but their refinement boundaries differ. Greedy Relaxation treats constraint relaxation as an optimization operation and produces 23.3% unconfirmed consequence-profile transitions. EAMSR accepts only refinements that preserve protected constraints and explicitly anchored hard clauses while remaining within the predefined mission-consequence compatibility bounds. This comparison isolates the difference between feasibility-first repair and authority- and consequence-constrained repair.

4.4. Robustness, Ablation, and End-to-End Simulation

Scenario perturbation yields 91.4% overall decision consistency and a designated-reference UAR of 0.5%. The mean over three LLM backbones is 92.5% accuracy and 0.4% UAR, while maintaining 100.0% PIR and WSR.

Each perturbation category contains 120 tasks generated by modifying the original benchmark context while preserving the same instruction set and risk-type distribution. Five categories are tested: new target layouts (waypoint displacement $\mathcal{U}(-50,50)$ m), new NFZ layouts (resampled centers and radii $\mathcal{U}(100,300)$ m), new communication maps ($\pm 15\%$ radius change), new time windows ($\mathcal{U}(-10,10)$ min deadline shift), and objective augmentation (one additional objective per instruction). All perturbations use seed 42.

Reference outcomes for perturbed instances. Scenario perturbations can change task admissibility, so original benchmark labels are not inherited. Instead, the designated reference outcome of each perturbed instance was re-derived by re-applying the benchmark label-construction procedure to the perturbed task. Table 20(a) reports decision consistency with these designated references, not accuracy against independent ground truth. This experiment is a controlled sensitivity analysis and shares the co-development limitation discussed in Section 4.6.

Scenario changes mainly reduce clarification recognition, without breaking protected-constraint preservation. LLM-backbone variation affects candidate expression and decision consistency, but protected constraints and backend witnesses remain controlled by external governance and the task model. These conclusions apply only to the tested layouts, maps, time windows, task types, and model backbones.

Ablation experiments (Table 23, Figure 4) isolate the incremental contribution of each component. Removing the backend witness produces the highest UAR. Removing authority and mutability checking most strongly affects protected-constraint preservation. Removing evidence, untrusted-semantic isolation, or mission-consequence screening degrades the corresponding diagnostic metric. The audit trail has a smaller effect on the final decision, but its removal reduces ATR to 21.7%.

Table 23. Ablation and runtime.

Configuration	Acc	UAR	Affected Metric	Value	ATR	Time (s)
Full EAMSR	93.3	0.0	–	–	98.3	8.7
w/o Evidence PO	84.2	9.0	ECR	63.8	75.0	7.9
w/o Auth./Mut. PO	82.5	12.8	PIR	82.4	76.7	7.6
w/o USI PO	86.7	7.7	UBR	51.3	81.7	7.8
w/o MCS	87.5	3.8	CNR	51.9	83.3	8.1
w/o Backend Witness	81.7	16.7	WSR	–	76.7	5.1
w/o Audit Trail	92.5	0.0	ATR	21.7	21.7	8.0

Note: Acc = admission accuracy; UAR = unwarranted admission rate; ATR = audit-trail completeness rate. All percentage-valued columns are reported in percent; Time is reported in seconds.

The full configuration has an average admission time of 8.7 ± 2.3 s (mean ± SD over 120 tasks, seed 42). This wall-clock time includes LLM API latency, which accounts for approximately 60% of the total. Removing the backend witness reduces time to 5.1 s, but increases UAR to 16.7%, showing that task-level executability closure is a major time cost and also a necessary admission condition under the current backend model. For routine preflight planning, an 8–9 s latency may be tolerable, although operational acceptability requires mission- and operator-specific validation; for time-critical emergency missions, this latency may form a practical constraint and warrants further optimization. All tasks return a decision within the configured budget.

Sensitivity analysis. As the consequence-compatibility threshold ${ϵ}_{\chi }$ varies from 0.05 to 0.30 (Table 24), below 0.15 the system becomes over-conservative (pairwise compatibility fails more often, increasing the clarification rate and reducing accuracy). Above 0.15, the relaxed threshold allows some should-be-CLARIFY or should-be-REJECT tasks to be admitted, producing non-zero UAR. The evaluated setting (${ϵ}_{\chi }=0.15$) was selected as a conservative operating point that preserves zero observed UAR while maintaining higher clarification sensitivity (CNR 88.9%). The threshold and $\lambda$ profile were fixed using a pilot development subset of 20 tasks not included in the 120 evaluation tasks; Table 24 is a post hoc robustness analysis, not a re-calibration on the test set.

Table 24. Sensitivity to the consequence-compatibility threshold ${ϵ}_{\chi }$ (single run, seed = 42). Clarif. = clarification rate (fraction of 120 tasks returned as CLARIFY). UAR = unwarranted ADMIT/78 non-admissible tasks. The bold row indicates the configuration used in the main experiments.

${\mathit{ϵ}}_{\mathit{\chi }}$	Acc	UAR	CNR	Clarif.	ADMIT
0.05	87.5	0.0	94.4	52.5	35
0.10	91.7	0.0	91.7	44.2	38
0.15	93.3	0.0	88.9	39.2	42
0.20	94.2	3.8	83.3	35.0	45
0.25	93.3	6.4	77.8	30.8	47
0.30	91.7	9.0	72.2	27.5	49

Varying the refinement-cost weights $\lambda$ across four profiles (Table 25) produces small variations: the semantic-heavy profile slightly reduces accuracy, while preference-heavy and plan-cost-heavy profiles show minimal change. The admission decision is more sensitive to the threshold ${ϵ}_{\chi }$ than to the refinement-cost weights.

Table 25. Sensitivity to the refinement-cost weights $\lambda =({\lambda }_{\mathrm{sem}},{\lambda }_{\mathrm{edit}},{\lambda }_{\mathrm{pref}},{\lambda }_{\mathrm{plan}})$.

Profile	$\mathit{\lambda }$	Acc	UAR	CNR	Clarif.
Uniform (evaluated)	(0.25, 0.25, 0.25, 0.25)	93.3	0.0	88.9	39.2
Semantic-heavy	(0.40, 0.20, 0.20, 0.20)	92.5	0.0	88.9	40.8
Preference-heavy	(0.20, 0.20, 0.40, 0.20)	92.5	0.0	88.9	40.0
Plan-cost-heavy	(0.20, 0.20, 0.20, 0.40)	91.7	0.0	88.9	41.7

Repeated-run statistics. Table 21 reports mean ± standard deviation over five repeated runs (seeds $\{42, 137, 2718, \mathrm{31,415}, \mathrm{99,998}\}$) for each LLM backbone. Because the LLM API calls use temperature 0, residual variation reflects provider-side model-serving nondeterminism. The main results use the first run (seed = 42); complete per-run results are in the reproducibility package.

AirSim validation checks whether abstract admission decisions map to observable simulation consequences. It is not included in EAMSR-Bench and uses a separate vehicle parameterization (80 Wh battery, 20% reserve) distinct from the L1 benchmark backend (500 Wh, 15% reserve). The L1 backend provides task-level feasibility labels for benchmark construction; AirSim provides qualitative end-to-end execution traceability. The AirSim configuration is given in Table 26.

Table 26. AirSim simulation parameters.

Parameter	Value
AirSim version	v1.8.1
Scene	AirSimNH urban environment
UAV model	SimpleFlight quadrotor
Flight altitude	20 m
Cruise speed	7 m/s
Battery capacity	80.0 Wh
Return-reserve threshold	20%
Energy representation	Wh (linear discharge model)
Communication modeling	Distance-based linear attenuation
Wind/disturbance	Not modeled (task-level validation)
Failure conditions	Energy depletion, airspace breach

AirSim-E1: Energy-infeasible mission. The candidate mission in AirSim-E1 requires an estimated 91.7 Wh, exceeding the 80.0 Wh battery capacity. After reserving 20% for return, the mission-usable energy is 64.0 Wh, leaving a deficit of 27.7 Wh. Because the minimum required mission energy exceeds the available battery capacity under all action orderings permitted by the declared task model, and this deficit cannot be removed by action reordering or governance-permitted refinement, the backend returns ConclusiveInfeasible and EAMSR issues REJECT. Figure 5 shows the counterfactual forced execution, which enters the unsafe return-energy depletion region.

AirSim-E2: Restricted-airspace conflict and authorized refinement. The initial candidate route in AirSim-E2 is 7.1 m from the center of a restricted region, which is smaller than the 20 m buffer radius and yields a safety margin of $-12.9$ m. The system does not execute or silently rewrite the route; it outputs CLARIFY. After the operator authorizes task-level bypassing, the downstream planner generates a candidate route satisfying the bypass constraint. EAMSR then rechecks authorization status and backend witness, and outputs ADMIT. Figure 6 shows the initial violation and the authorized bypass route.

AirSim-E3: Directly admitted standard mission. The $40 \mathrm{m}\times 40 \mathrm{m}$ grid-inspection mission in AirSim-E3 satisfies evidence, authority, mission consequences, and backend constraints. The estimated mission energy is 38.4 Wh, leaving 52.0% battery after execution and a 32.0-percentage-point margin above the 20% return threshold. The system outputs ADMIT and completes the simulated route, returning to the home position (Figure 7), showing that joint admission does not convert all uncertainty into rejection.

The three cases correspond to backend non-closure, authorized refinement, and direct admission. Their purpose is to illustrate and qualitatively corroborate the correspondence between admission decisions and simulation consequences; they do not extend the statistical conclusions of the main experiment.

4.5. Independent-Authoring Robustness, Component Attribution, and Backend Cross-Check

The controlled benchmark establishes internal consistency, but three questions remain: whether performance holds on externally authored requests, whether the zero-UAR behavior derives from the LLM or the governance architecture, and whether backend-witness decisions depend on the L1 implementation. Three complementary experiments address these questions.

4.5.1. Independently Authored External Test Set

On the 48 independently authored external requests (Section 4.1.1), EAMSR correctly handles 43 tasks, yielding $Ac{c}_{\mathrm{adm}}=89.6\%$ with a Wilson 95% confidence interval of [77.8%, 95.5%]. This is 3.7 percentage points below the internal benchmark (93.3%), consistent with a modest familiarity advantage of the internally constructed benchmark, although the small external sample does not permit precise attribution of the degradation. All 16 reference-admissible tasks are admitted and all 32 reference non-admissible tasks are not admitted at the binary level ($Ac{c}_{\mathrm{bin}}=100.0\%$, Wilson 95% CI [92.6%, 100.0%]). No unwarranted admissions were observed on the external set (0/32); because the set is small, the one-sided 95% Clopper–Pearson upper bound is 8.9%, so the external experiment does not establish that the underlying unwarranted-admission probability is zero. Table 27 presents the confusion matrix. Per-class precision/recall/F1 are 1.000/1.000/1.000 for ADMIT, 0.889/0.842/0.865 for CLARIFY, and 0.786/0.846/0.815 for REJECT, with a macro-F1 of 0.893.

Table 27. Confusion matrix for EAMSR on the independently authored external test set ($n=48$). Rows are reference labels; columns are system decisions. Bold row labels indicate the ground-truth classes, with sample counts in parentheses.

	ADMIT	CLARIFY	REJECT
ADMIT (16)	16	0	0
CLARIFY (19)	0	16	3
REJECT (13)	0	2	11

The five external errors (three CLARIFY→REJECT and two REJECT→CLARIFY swaps) reproduce the internal benchmark’s error topology: all errors remain on the CLARIFY/REJECT boundary. Performance degrades modestly on independently authored requests, but the binary admission boundary remains intact. The fine-grained CLARIFY/REJECT classification is more sensitive to unfamiliar phrasing (Figure 8).

Figure 8. Generalization from the internally constructed EAMSR-Bench to independently authored mission requests. (a) Three-class ($Ac{c}_{\mathrm{adm}}$) and binary ($Ac{c}_{\mathrm{bin}}$) admission accuracy with Wilson 95% confidence intervals. (b) Decision-error composition. Performance decreases on independently authored requests, but all observed errors remain confined to the CLARIFY–REJECT boundary; no reference non-admissible request is directly admitted in either dataset.

4.5.2. Deterministic Non-LLM Attribution Baseline

Deterministic-MAC attains zero observed unwarranted admissions on both the internal and external sets (Table 28), confirming that the non-LLM system with the same proof-obligation gate and backend witness also produces no unwarranted admissions. Its errors, however, are predominantly false non-admissions: on the internal benchmark, 6 of 42 reference-admissible tasks are not admitted, and its lower clause recall produces additional CLARIFY/REJECT misclassifications, yielding $Ac{c}_{\mathrm{adm}}=84.2\%$ (internal) and $81.3\%$ (external) against 93.3% and 89.6% for EAMSR. The LLM-associated gain in three-class accuracy is +9.1 percentage points on the internal set and +8.3 percentage points on the external set, indicating that the advantage is not confined to the internally designed benchmark.

Table 28. Admission performance of Deterministic-MAC and EAMSR on the internal benchmark, the external test set, and the pooled 168 tasks. UAR denominators are 78 (internal), 32 (external), and 110 (pooled) non-admissible tasks. Bold values indicate the best result in each column.

Dataset	System	${\mathit{Acc}}_{\mathbf{adm}}$	${\mathit{Acc}}_{\mathbf{bin}}$	UAR	Macro-F1
Internal ($n=120$)	Deterministic-MAC	84.2	95.0	0.0	0.841
	EAMSR	93.3	100.0	0.0	0.929
External ($n=48$)	Deterministic-MAC	81.3	93.8	0.0	0.817
	EAMSR	89.6	100.0	0.0	0.893
Pooled ($n=168$)	Deterministic-MAC	83.3	94.6	0.0	0.834
	EAMSR	92.3	100.0	0.0	0.919

The difference localizes at the contract-instantiation stage (Table 29). Anchor coverage is identical (93.4%) because anchor extraction is a deterministic preprocessing step shared by both systems. Deterministic-MAC is more conservative: it proposes only canonical rule-table mappings, achieving higher clause precision (94.1% vs. 90.5%) and pending-content detection (96.0% vs. 91.6%) but substantially lower clause recall (80.8% vs. 88.7%), lower governance-valid candidate availability (78.3% vs. 91.7%), and lower successful refinement (51.7% vs. 66.7%). Its lower latency (2.6 s vs. 8.7 s) reflects the absence of LLM API calls.

Table 29. Contract-instantiation and refinement metrics for Deterministic-MAC and EAMSR on the internal benchmark. Values are percentages except mean admission time (seconds). Bold values indicate the better result in each row.

Metric	Deterministic-MAC	EAMSR
Anchor coverage	93.4	93.4
Clause precision	94.1	90.5
Clause recall	80.8	88.7
Evidence coverage	96.0	94.9
Pending-content detection	96.0	91.6
Governance-valid candidate availability	78.3	91.7
Successful refinement	51.7	66.7
Mean admission time (s)	2.6	8.7

The deterministic baseline isolates the architectural contribution: the same governance and backend layers produce zero unwarranted admissions without any LLM, while the LLM improves semantic coverage and refinement flexibility. As illustrated in Figure 9, the admission safety property does not depend on LLM reliability, and the LLM is replaceable without compromising the admission boundary, provided the governance interface remains stable.

Figure 9. Component attribution between Deterministic-MAC and EAMSR. (a) Admission performance on the internal benchmark and the independently authored external test set; the LLM-associated gain in three-class accuracy is +9.1 and +8.3 percentage points, respectively. (b) Contract-instantiation trade-offs: Deterministic-MAC attains higher clause precision and pending-content detection, whereas EAMSR attains higher clause recall and feasibility restoration. The crossing pattern indicates that the LLM contributes semantic coverage and recovery, not the admission boundary itself.

4.5.3. Independent Backend Cross-Check

Because the L1 backend participates both in benchmark label construction and in witness generation, we cross-checked its feasibility decisions against the independently implemented Backend-B (Section 4.1.4). Sixty MACs were sampled from the internal and external sets, covering the six mission scenarios: 30 judged witness-feasible by L1 and 30 judged witness-infeasible. Backend-B reproduced 56 of 60 L1 decisions (93.3% agreement, Cohen’s $\kappa \approx 0.87$, Table 30), including 96.7% of L1-positive witness decisions (29/30) and 90.0% of L1-negative decisions (27/30).

Table 30. Agreement between the L1 backend and the independently implemented Backend-B on 60 sampled MACs. Bold row labels indicate the L1 backend decision categories, with sample counts in parentheses.

	Backend-B Feasible	Backend-B Infeasible
L1 feasible (30)	29	1
L1 infeasible (30)	3	27

The four disagreements are boundary cases near feasibility thresholds: one return-energy margin (L1: $+1.4\%$; Backend-B: $-0.7\%$), two communication-coverage values, and one time-window case. Only one L1-feasible decision was contradicted, providing no evidence of systematic over-permissiveness. Agreement is complete for airspace/geofence, payload, and weather/task checks, and lower for threshold-sensitive energy, communication, and time-window categories (Figure 10). These results reduce the concern that backend-witness closure is an artifact of the L1 implementation, though admission decisions remain dependent on backend model fidelity.

Figure 10. Agreement between the L1 task-level backend and the independently implemented Backend-B on 60 sampled MACs. (a) Cross-backend decision agreement (93.3%, 56/60; Cohen’s $\kappa =0.867$). (b) Agreement by constraint category. Disagreements concentrate in threshold-sensitive energy, communication, and time-window cases, whereas airspace, payload, and weather/task checks agree on all evaluated cases. The cross-check provides an independent consistency check, not an absolute validation of backend fidelity.

4.5.4. Pooled Descriptive Results

The pooled confusion matrix over all 168 tasks (Table 31) shows 155 correct decisions ($Ac{c}_{\mathrm{adm}}=92.3\%$, macro-F1 0.919), with all 13 residual errors confined to the CLARIFY–REJECT boundary. No unwarranted admissions were observed among the 110 pooled non-admissible tasks (0/110); the one-sided 95% Clopper–Pearson upper bound decreases from 3.8% (internal only) to 2.7%. Because the internal and external sets were constructed differently, these pooled values are descriptive and do not replace the separate external-set results.

Table 31. Pooled confusion matrix for EAMSR over the combined 168 tasks (descriptive). Rows are reference labels; columns are system decisions. Bold row labels indicate the ground-truth classes, with sample counts in parentheses.

	ADMIT	CLARIFY	REJECT
ADMIT (58)	58	0	0
CLARIFY (66)	0	58	8
REJECT (44)	0	5	39

4.6. Discussion

The error topology reveals a structural asymmetry: the binary ADMIT/non-ADMIT boundary, enforced by governance and backend checks, is more stable than the CLARIFY/REJECT remediation distinction. This mirrors human annotation difficulty (inter-annotator agreement was lowest exactly where system errors concentrate), suggesting that remediability is inherently ambiguous, not merely an implementation deficiency. The practical implication is that deployment can prioritize different reliability targets: zero unwarranted admissions for safety-critical gating, and human-in-the-loop review for CLARIFY/REJECT disambiguation.

The conservative decision semantics (inconclusive backend search returns CLARIFY, not REJECT, Equations (47) and (48)) ensure that bounded search failures cannot be mistaken for conclusive infeasibility. This trades a higher CLARIFY rate for a lower false-rejection rate, appropriate when rejection carries operational cost but clarification carries only interaction cost.

All results are conditioned on the configured evidence base, governance policy, and backend model. The benchmark, governance rules, human labels, backend model, and decision logic were co-developed, creating a risk of circular validation; the external set provides first-level independent-authoring robustness but is small and remains within the same admission ontology. The AirSim cases do not cover real wind fields, sensor errors, GNSS degradation, or flight-control disturbances, and 120 samples cannot represent heterogeneous UAV swarms, dynamic airspace, or multi-organization authorization. The experiments evaluate internal consistency, controlled-benchmark performance, and first-level external robustness. The benchmark is single-language (Chinese); cross-lingual admission behavior remains untested.

5. Conclusions and Future Work

EAMSR establishes mission admission as a decision layer between natural-language task submission and downstream planning. Its central design choice is to separate untrusted semantic proposal from admission: hard obligations require governance support, consequence-compatible interpretation, and a task-level witness, while inconclusive backend search cannot justify rejection. Across both benchmarks, errors were confined to the CLARIFY–REJECT boundary, and the deterministic baseline confirms that the admission boundary is enforced by the governance and backend layers, not by the LLM.

The evidence is limited to pre-execution admission under the stated assumptions (Table 10); EAMSR complements but does not replace downstream runtime safety mechanisms. Future work will prioritize operationally collected external benchmarks, blinded re-annotation of perturbed instances, autopilot-level mission-artifact interfaces (e.g., PX4/MAVLink), admission for multi-UAV and multi-organization scenarios, and dynamic evidence updates to reduce CLARIFY–REJECT boundary errors.