Reading method · 02

Operating envelope first

State surfaces, slopes, steps, lighting, payload, traffic, communications and disturbance limits before quoting performance.

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

FUURAA thesis

A capability claim is only meaningful inside the conditions in which it was repeatedly measured.

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 envelope

Record geometry, friction, compliance and obstacles.

02

Task envelope

Bound objects, loads, tools, timing and quality.

03

Human envelope

State training, proximity, intervention and bystanders.

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 conditions were varied?

  2. 02

    Which limits trigger stop or assistance?

  3. 03

    Was the complete machine tested?

  4. 04

    What invalidates transfer to a new site?

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

    Versioned operating-envelope table

  2. 02

    Evidence package 2

    Challenge-condition results

  3. 03

    Evidence package 3

    Stop and transfer criteria

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.