Wow, mind blown. Effectively refuting a core principle of the Agile Manifesto, as you have done, calls the entire Manifesto and Agile itself into question.
Agile manifesto is not written by and for true engineers. It is written for those who must accommodate the requirements of imperfect people developing good enough software on behalf of uncertain (evolving) requirements.
This is my subjective opinion, and I would like to know what others think. I might very well be objectively wrong for all I know. The manifesto was written 20+ years ago, when the situation might have been different, so I wouldn't be calling it out because it might have been true in that time.
The Agile Manifesto lists ideas and guidelines, not inviolable rules from a burning bush. The author didn’t have all the answers or a crystal ball. Take what you can use, adapt what you can.
One thing decades of software development teaches us: no one knows how to do it right reliably and consistently. No silver bullet. No one right way. Try ideas that seem to make sense and have worked for others, but avoid ideologies and self-proclaimed experts.
