Hence why I keep speaking of the time when you make changes to the code.
> and the permission here is a contract: the license.
Which in this case is a pure copyright license, and therefore has no impact on how you use the software, by design, because its requirements only apply to modification and distribution. Look up how the AGPL was created. This was a concern and precisely why they did the bizarre modification-time wording that I keep pointing out.
> What you are suggesting would then violate that contract by using that modified version in a way contrary to the license granted for its modification.
We have a word for licenses that impose usage restrictions. They're called EULAs. They violate Freedom Zero and are not free software licenses.
The AGPL is not an EULA, though it tries its hardest to look like one with that clause.
I honestly don't even care that much about people choosing to interpret the AGPL in this way; I actually used to think like you, until I re-read it enough times to really understand what's going on. You're arguing that the AGPLv3 is a nonfree EULA that actually works as anti-SaaS. I'm arguing that it's a nonfree non-EULA that doesn't work. In both cases, it definitely isn't a free software license that actually works as anti-SaaS.