BethBennett0759 · 26 Apr 2025, 22:55 UTC
What does the operator see that confirms held, placed, or unknown?
6 pointsOnly the pocket number at present. Tool feedback is logged but not shown beside the job state. Worse, the code advances on the release command, not confirmed release. That's the bit under review.
23 pointsThen don't give them a restart recipe based on that number. It can lie.
8 pointsAgreed. We're mapping requested action, confirmed action and unknown state separately, with controls reviewing how physical confirmation and saved state stay consistent. Ambiguous cases go to the authorised recovery process.
22 pointsInclude a stop after placement but before the saved state updates. The opposite mismatch matters too.
15 pointsAdded that case. Offline checks now keep both interruptions visibly unresolved instead of suggesting the next pocket. Practical recovery validation and operator training still need doing before release.
17 pointsWho owns that validation? Get it named before this becomes the apparently finished job on the shelf.
19 pointsThis discussion is closed to new replies after six months without activity. Last activity: .