You mean that we write the sign, the road markings, and the speed bump for a certain speed limit, and then the cars lift off and go tearing along at thousands of kilometers an hour, so the original wording no longer works. Right. If you bolt the rules to one specific capability, they are obsolete the moment you finish writing them. But however fast the cars go, a concept like the pedestrian’s right of way does not go out of date. So the work is to think clearly about which rights are basic, and about the procedures that secure them, and then to write those down: which version is running now, who authorized it, whom it affects, where you appeal when it goes wrong, and so on. All of that should carry a version history. Everywhere outside AI, software already does this. Today we upgraded to the new Beta of Golden Gate macOS 27 . It has a build number, an identifier. Looking at the hash, I can be fairly confident that the package I downloaded, the package he downloaded, and the package you downloaded today are the same thing. And if a security test reports, “I have verified that this really does fix some vulnerabilities from the previous version,” then I can be reasonably confident that when I push it out, the same vulnerability is closed on everyone’s iPhone and everyone’s MacBook. With AI, that is not how it works.