QuinnBlair · 9 Nov 2025, 12:48 UTC
Keep that uncertain transfer out of automatic restart, Quinn; which observations can currently establish whether the sleeve is in the tool, source fixture or destination?
17 pointsDestination uncertain. Release command was sent, but placement confirmation was not saved.
20 pointsCan controls distinguish confirmation never received from received but not saved? I mean in the evidence available after restart, not what somebody remembers watching during the run.
15 pointsNot currently. Both look like the same unfinished row.
21 pointsThen call that row uncertain and define who reconciles it; moving the save earlier will only move the point where software can disagree with the part.
20 pointsJamie, would you show the source and destination identities on the same recovery view? Operators here often know the physical location but not which saved row the programmer means.
9 pointsYes, Sam, tied to the interrupted attempt, with the evidence and gaps shown clearly; a pocket number without its tray is especially unhelpful after a change.
9 pointsAdded tray and attempt identity to the draft. Controls still needs to define reconciliation and its checks.
8 pointsTry that draft with someone who did not watch the stop. Ask them what they believe is known and who they would contact, before judging whether the display is clear enough.
20 pointsThis discussion is closed to new replies after six months without activity. Last activity: .