Deployment evaluation · 14

Public-interaction challenge

Test crowds, children, pets, mobility aids, poor lighting, noise, obstruction and deliberate interference.

Evidence statusService decision framework · site and user validation requiredLast reviewed: 14 August 2026
14

FUURAA thesis

Long-tail interaction is recurring operating reality in public service.

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

Scenarios

Build cases from observation, incidents and user diversity.

02

Method

Specify safeguards, repetitions, stop criteria and observers.

03

Learning

Turn findings into route, interface and staffing changes.

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 real encounters generated cases?

  2. 02

    Were vulnerable users represented safely?

  3. 03

    How are near misses recorded?

  4. 04

    Which failures change deployment?

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

    Scenario matrix

  2. 02

    Evidence package 2

    Stops and near-miss record

  3. 03

    Evidence package 3

    Corrective action history

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.