I've kept unknown separate from failed in our planning notes, but the UR5e restart screen still offers the saved pocket as the next destination, even when a spacer may already be there. How should I describe that gap to controls?
Put the physical observation beside the saved state in the example, because otherwise someone will fix the counter increment and never ask how the occupied pocket should be reconciled
Controls agrees the saved number isn't enough. They propose an unresolved-transfer screen before offering any next destination, with the operator following the reviewed recovery method.
And don't make viewing that screen the action that clears it, we had that distinction come up in another discussion and it is too easy to hide behind one confirmation button
Maya, tray identity is included. Ravi, the draft separates reading from the authorised recovery decision. Thanks for that; I can review the wording without pretending the recovery tests are finished.