You know, it’s not enough to restate your own points, you have to read and absorb the things other people are saying.
Once again, “Working software over documentation” does not mean “Working software instead of documentation.”
It means that working software is more important than documentation, but both can be important. And it can be that documentation exists to make the software work.
If I said “Working software over software patterns,” that wouldn’t mean “Never, ever, ever use the Command Pattern, or Adaptors, or a Facade.” It just means that you use those things to make the software work. And if they are essential to making the software work, they are essential.
So you tell me that software is nothing without documentation, and I happen to agree. But software is also nothing without binaries. But that doesn’t mean “binaries over working software.” It just means, “build binaries as part of working software."
For example, when you have to interface with others. They can work on the software that depends on yours before you have even written a single line of code, and it will work.
Software without documentation also can lead to serious issues – as in the "does the train continue running when the signal is broken" question I mentioned a dozen times now.
In actual critical projects, Documentation over software. The best software is nothing without documentation.
That’s the first point where I have to disagree with it.
In many other points, agile leads to teams just carrying the technical debt with them.