Regarding the current four-phase amendment process.
I can imagine a situation where we are a couple of blocks from the end of the promotion phase and, hypothetically, we may be 0.001% away from reaching a quorum.
In this situation, we don’t know if the chain will migrate to the new protocol until the proverbial 11th hour. Teams who build tools/products or operate services on top of Tezos would need to coordinate around a significant event that may not happen.
If we create a fifth and final stage in the amendment cycle called, for example, “freeze”.
If the promotion reaches quorum, then we would have a “freeze” period of perhaps two weeks. This time would allow developers and infrastructure operators to plan and prepare for the protocol transition knowing for sure that the new protocol will come into effect at a specific block height.
If the proposal fails to reach quorum in the promotion phase or gets voted down in the promotion phase, the cycle resets back to the proposal phase immediately.