Our controls lead can own it. I was trying to make one glossary entry work; now I see the sequence needs both facts.

Show a request acknowledged while the loading area is still unavailable. That example needs no ambiguous ready.

And ask the engineers what evidence establishes availability; an explanatory label cannot establish the physical condition or replace the cell's safety assessment.

Agreed. Separate the ordinary handshake from safety functions in the document, and have the responsible teams approve both the meaning and the evidence behind each ordinary condition.

I have drafted the waiting example with both suppliers' current interpretations shown. Haven't turned either one into an approved definition yet.

Will the next shift know whom to contact if those states disagree?

The wait message should identify what is missing, not invite someone to keep pressing start.

Controls is collecting timeout and restart cases for the joint review. I'll include the escalation role in the operator notes once the engineers settle those cases.

Keep communication loss in that review too. A retained indication needs defined treatment; its presence after reconnection is not automatically evidence of a new acknowledgement.