Deployment evaluation · 17

Safe degraded behaviour

Challenge perception, communications, balance, tool state, compute and power loss under controlled conditions.

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

FUURAA thesis

A capable robot becomes deployable only when loss of capability leads to a bounded and recoverable state.

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

Detection

Define monitors, latency and diagnostic coverage.

02

Degradation

Choose slow, stop, hold, release or withdraw.

03

Recovery

Control isolation, assistance, verification and restart.

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 failures remain undetected?

  2. 02

    Can stopping create a new hazard?

  3. 03

    What state does a held load enter?

  4. 04

    Who confirms recovery is complete?

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

    Fault-injection plan and results

  2. 02

    Evidence package 2

    Degraded-state specification

  3. 03

    Evidence package 3

    Recovery authority and closure 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.