How would you handle new requirements in the middle of a project you're managing at Google?

As a TPM with experience in Agile methodologies, I value changing and adapting to new changes that contribute to the overall goal. To deal with this situation, I would first assess the impact that this change would cause on the goal of the project. I would achieve this by checking if the changes align with the project mission, if the stakeholders satisfaction is affected by the same, if the value derived from the new requirements are worth extending deadlines or adding resources. After the assessment, I would document the new requirements, new timelines, new resource requirements and communicate the same with stakeholders. If the additional requirements would have a negative impact on the project, I would politely decline and notify the stakeholders of the same, while communicating alternatives like accommodating the requirements in another project lifecycle.