Reading method · 03

Task sequence is the unit

Measure the complete chain from request and approach through manipulation, verification, handoff and return.

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

FUURAA thesis

Isolated walking or grasping results cannot reveal compounded failure across a real work sequence.

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

Start state

Fix object, robot, site and authority conditions.

02

Sequence

Record every transition, retry and branch.

03

Completion

Verify outcome, damage, time and final safe state.

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

    What exactly starts and ends the task?

  2. 02

    Which steps can be skipped or retried?

  3. 03

    Where is human help allowed?

  4. 04

    How are partial completions counted?

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

    Executable task protocol

  2. 02

    Evidence package 2

    Transition and exception log

  3. 03

    Evidence package 3

    Outcome verification 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.