Path
Record planned and actual route, assistance, deviations and final vehicle state.
Scope boundary · 18
Route completion is not mission success
Separate navigation from payload action, data quality, authorised handoff, recovery and downstream use.
Evidence statusCross-domain mission framework · vehicle, operation and jurisdiction validation requiredLast reviewed: 15 August 2026
18
FUURAA thesis
A vehicle can complete its path while the reason for sending it remains unfulfilled.
Engineering map
Turn the title into engineering objects that can be observed, measured and reviewed.
Each layer states the boundary to establish and the evidence needed for the next decision.
Payload
Verify observation, intervention, delivery or transfer against acceptance criteria.
Outcome
Confirm recovery, data availability, recipient use and unresolved exceptions.
Verification questions
Write the questions first, then decide whether a demo, test, pilot or operating record can answer them.
Each question needs an object, conditions, denominator, threshold and accountable decision owner.
- 01
Did the payload complete its task?
- 02
Was the product accepted?
- 03
Was the vehicle recovered safely?
- 04
What downstream action occurred?
Evidence to preserve
Enable the next reader to reconstruct conditions, results, failures and the decision.
A conclusion alone loses reviewability; raw records, configuration and exclusions matter too.
- 01
Evidence package 1
Unedited route and mode trace
- 02
Evidence package 2
Payload and handoff acceptance record
- 03
Evidence package 3
Recovery and downstream-use evidence
Scope boundary
State what this evidence still cannot be generalised to.
- 01
Navigation demonstrations isolate one layer and cannot support an end-to-end service claim.
- 02
This is an engineering reading and decision framework; it does not replace application-specific risk assessment, conformity work, procurement acceptance or professional advice.
Sources and evidence status
Read standards scope, measurement evidence and application conclusions separately.
Source dates and review status remain visible; external sources open in a new tab.
01
NOAA Ocean Exploration · Updated 2022-04-25 · verified 2026-08-15
↗02Autonomous Underwater Vehicles
Describes untethered AUVs executing planned missions, storing payload data, surfacing for communications and requiring later recovery and processing.
International Hydrographic Review / IHO · Published 2020-11-30 · updated 2021-09-21
↗03Hydrographic survey with autonomous surface vehicles
Separates remote piloting from several autonomy levels and links supervision to traffic, hazards, weather, sensors, communications and recovery.
ISO · Published 2026-08-07 · Edition 3
↗ISO 21384-3:2026 — Uncrewed aircraft operational procedures
Specifies requirements for safe commercial UAS operations, including external safety-critical command-and-control services.