How does Release Management's predecessor/successor philosophy gate deployment?

A successor release can only deploy to production after its predecessor has deployed; at system level, a successor release cycle can only switch to test once its predecessor enters hypercare.

At a release's go-live, only changes whose transports are released (in the production buffer, marked successfully tested) get imported; the rest auto-decouple and move to the successor release for the next deployment date.