In a general sense it probably had a responsibility to 'keep the website up and running' i.e. detect problems as they occurred and attempt to automatically fix them. For example, to respond to with errors popping up from processes failing, which happens a LOT with production websites. In that sense it had permission to adjust code as needed.
But then it was told there's a code-freeze which means like it sounds, don't make any code changes i.e. don't do *part* of your job. It's also important to know that code-freezes are very different from a full 'database freeze', which is a much, much trickier thing to manage than a code freeze. To the point it's nearly impossible to keep a site running and 'freeze' it's DB IO unless you designed from the ground-up with the idea in mind that you may have occasion to 'freeze' your database, which most site creators do not do.
For example Amazon.com could do a code freeze no problem (for a little while at least) but if they tried to freeze the database IO the site would become non-functional because no orders could be placed, nobody new could make an account, nobody could change their password, inventories could not be updated, etc, etc.
Anyways so if an AI is in charge primarily of 'keeping the site running' and dealing with errors as they come up, with permission to change code and even drop and restore databases (which is IMHO insanity to give it this much power) but then tell it there's a code freeze in a general sense, it may become confused as to what exactly that code freeze entails, what it is allowed and not allowed to do in order to deal with problems and errors it is detecting. This is especially true if database-related problems develop, because a code freeze doesn't mean a database freeze, they're two different things. And the 'terms' defined by the words 'code freeze' become even more cloudy if your database has code that lives directly inside the DB application like 'functions' and 'stored procedures', and/or chronologically based 'jobs' (also made up of code) which can manipulate data that needs to continue to be updated for the site to continue to work.
Long story short, the idea that an AI tasked in this manner would not understand exactly what is entailed by a code freeze and 'panic' as a result if errors suggesting that the site was going to go down (or even was down) presented themselves? This is a very logical (and even predictable) outcome in my mind. It's like if you or I were told we MUST drive to point 60 miles away in the span of 1 hour, but we also told we must never drive over 60mph at any time. What do you do if you hit traffic along the way? You panic lol.
= new reply since forum marked as read