Reading method · 03

Operational domain before autonomy

Specify airspace or waters, traffic, weather, visibility, depth, communications and recovery access before approving a mission.

Evidence statusCross-domain mission framework · vehicle, operation and jurisdiction validation requiredLast reviewed: 15 August 2026
03

FUURAA thesis

A vehicle is autonomous only within a declared and controlled operational domain.

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.

01

Environment

Bound wind, sea state, current, depth, temperature, visibility and precipitation.

02

Traffic

Map people, aircraft, vessels, fishing gear, obstacles and protected areas.

03

Services

Bound navigation, communications, weather, launch and recovery dependencies.

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.

  1. 01

    Which conditions are explicitly inside scope?

  2. 02

    What forces delay, degradation or abort?

  3. 03

    How is domain drift detected?

  4. 04

    Which control depends on local infrastructure?

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.

  1. 01

    Evidence package 1

    Versioned operational-domain specification

  2. 02

    Evidence package 2

    Traffic, hazard and dependency map

  3. 03

    Evidence package 3

    Go/no-go and change-control record

Scope boundary

State what this evidence still cannot be generalised to.

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.