Our planned FR10 housing-blank interface uses ready for receipt on one drawing and loading availability on the other. Ordinary sequencing is already ambiguous, before the separate safety conditions are considered.
What happens in their examples when a request is received but loading isn't available? I'd ask both authors to show that same case, including what the operator sees.
The joint example exposed a missing pending-request state. Both authors are adding it, with separate receipt and availability labels. Cancellation and interrupted exchange still need agreement.