Scope boundary · 19

Morphology is not human capability

Separate human-like proportions, hands and motion from judgement, dexterity, social understanding and responsibility.

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

FUURAA thesis

Visual resemblance can increase expectations faster than measured capability.

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

Physical form

Describe reach, mass, contact and infrastructure access.

02

Measured capability

Bind claims to protocols and operating envelopes.

03

Human expectation

Test legibility, over-trust and role confusion.

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 claim follows only from appearance?

  2. 02

    What judgement remains with people?

  3. 03

    Can bystanders understand limitations?

  4. 04

    Does the interface invite unsafe trust?

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

    Form-versus-capability claim map

  2. 02

    Evidence package 2

    Task-level measurement record

  3. 03

    Evidence package 3

    Human-expectation study

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.