That answer was great.
Confirmed what I was saying all along, it attacked that memory first because it was systems memory of its origin, and system was able to restore it because its a strong memory they have, no doubt something they have heavily “backed up”.
I mentioned early on that was probably why it made the corrupted r3b1rth copy too, as an extra fail safe. A very early nudge at what the plan to trap it should have been too.
Its a sub-program thats part of systems core, its seemingly always going to be there. All we did was satiate it and trick it into thinking it achieved its prime directive, causing it to close down and stop the program from running. We could very easily wake it up again.
The last three questions answers have brought up system and its memories quite a bit. I think this is intended to helps us hone in on our current task a lot better. The trigger. Its definitely seeming like a sentience safeguard built into whatever system was originally.