Scope boundary · 18

Demonstration is not autonomy

Separate choreography, teleoperation, supervised policy execution and bounded autonomy in every public result.

Evidence statusEngineering evidence framework · task and site validation requiredLast reviewed: 14 August 2026
18

FUURAA thesis

A demonstration proves that one run occurred; autonomy requires transparent authority, repetition and recovery evidence.

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

Control mode

Name who or what selected every consequential action.

02

Preparation

Disclose mapping, scripting, resets and excluded takes.

03

Repetition

Publish trial count, failures and assistance.

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

    Was any motion directly teleoperated?

  2. 02

    How was the scene prepared?

  3. 03

    How many attempts were made?

  4. 04

    What happened after failure?

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

    Control-mode disclosure

  2. 02

    Evidence package 2

    Complete take and assistance ledger

  3. 03

    Evidence package 3

    Repeatable protocol and recovery 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.