Reading method · 01

System, not body shape

Start with the task, operating zone, people, tools and support system before deciding whether a humanoid form is useful.

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

FUURAA thesis

Morphology is an access strategy; the unit of value is a complete, recoverable work system.

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

Task

Define the useful outcome and rejected work.

02

Environment

Map floors, clearances, fixtures, people and change.

03

Operations

Include supervision, charging, maintenance and recovery.

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 outcome requires this morphology?

  2. 02

    Which human infrastructure is reused?

  3. 03

    What added hazards follow from height, mass and reach?

  4. 04

    Which dependencies sit outside the robot?

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

    Task and operating-zone definition

  2. 02

    Evidence package 2

    Morphology trade-off record

  3. 03

    Evidence package 3

    End-to-end operating blueprint

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.