System state must become immediately clear after handoff
Aliases: post-transition state · takeover confirmation · mode awareness
What it is
Post-handoff mode awareness means that after transfer a person immediately knows who controls each function, which protections remain, whether prior commands persist, and what is executing. “Control acquired” is insufficient when partial automation and queued action remain.
Why it happens
Base, arm, speed constraint, and avoidance can transfer separately. One mode label hides partial allocation, prompting all-manual or all-automatic assumptions. Uncleared trajectory queues can combine with new input and produce automation surprise.
Studying it
Full, partial, and failed handoffs with varied feedback delay can test function-level controller reports, mode errors, dual commands, recovery, and confidence. False-positive display and lagging display should be injected.
Where it stops holding
Integrated systems need not show every channel continuously, but action-relevant exceptions require prominence. Familiar defaults do not replace current confirmation. Emergency brevity must still reveal active constraints and residual action.
Applying it
- Show function-level allocation, remaining constraints, queued commands, and state timestamp after transfer.
- Define clear, pause, or continue rules for old queues and update display and controller from one commit event.
- Test partial handoff and display–backend desynchronisation, counting mode errors and command conflicts.