Scope boundary · 18

Agility is not mission value

Keep athletic movement, route completion, payload result and downstream decision as separate evidence layers.

Evidence statusField mission framework · task, terrain and site validation requiredLast reviewed: 15 August 2026
18

FUURAA thesis

A robot can cross the obstacle and still fail the reason it was sent.

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

Motion

Report terrain, speed, falls, assistance and repeat count without editing.

02

Task

Verify every required observation, action, return and handoff.

03

Value

Confirm accepted data, changed decision, reduced exposure or saved resources.

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 layer does the evidence prove?

  2. 02

    Were task failures edited out?

  3. 03

    Did the recipient accept the result?

  4. 04

    Was the mission worth its support burden?

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

    Unedited repeated mobility trials

  2. 02

    Evidence package 2

    Task and payload acceptance

  3. 03

    Evidence package 3

    Outcome and resource comparison

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.