"At least as it iterates, improvements occur that make the UX better and provide a more pleasant experience."
Certainly more interesting features get activated. But at least with my model, the error reporting got a lot more complicated and the input acceptance rate dropped considerably around the time the product turned 15 years old.
I believe this technique is called fuzzing - Adversarial QA testing to make sure the prior sysadmins weren't total morons and left the system in an unusable state before deploying it to production.
As you say, the reporting is inscrutable, so I'd guess there are still a few bugs to be worked out.
Certainly more interesting features get activated. But at least with my model, the error reporting got a lot more complicated and the input acceptance rate dropped considerably around the time the product turned 15 years old.