A machine type selects compute capacity. It doesn't grant data access or guarantee application performance. A resize also has lifecycle and compatibility requirements, so read the documented workflow and prepare the workload for maintenance before changing its type.
The local tasks begin with stopped instances and ask for a specific resulting size. Preserve the lifecycle state until the requester authorizes a restart. The hidden data includes distractors in another scope or region. The model saves the machine type and workload identity intent; it doesn't allocate provider capacity, check every compatibility constraint or run a benchmark. Production resizing needs those checks and a recovery plan.
Resize the stopped target without treating capacity as authorization.