I can understand your reasoning, but I cannot agree with you. In your perspective, I see a disconnection with the agile manifesto, manily with "Individuals and interactions over processes and tools".

From my experience, when we use User Stories as requirements we fall into the old traditional mindset. I do believe that building the shared understanding is the most understanding. The acceptance criteria should reflect the agreements on how to confirm the User Story.

I am curious where you got the definition that User Stories are requirements. Could you share the source? Please. From my understanding, User Stories were created to remove the distance between developers and users, and to focus on the problems instead of solutions. Therefore, I cannot perceive that as requirements, for me it's more like a discovery. User Stories is just the start, never the end.