I disagree.You have your priorities backwards. It doesn't help us at all if we identify it, but let it crash, with irreparable damage and data loss sustained.
My priorities are straightforward, and in order of priority:
- Molly's survival
- Survival of Molly's war party
- Everything else
This thing has already jumped to conclusions and tried to kill Molly once, taking us down to 6/15 health and -1 wound penalty.
If the choices are let it crash or let it stab Molly in the neck again, Im letting it crash and fixing whats left.
As most people here who have lived through the heydyay of Worm's popularity will remember?
Dragon in Worm, while a sapient AI, had explicit, hardcoded safeguards that compelled her to attack and destroy anyone who tried to modify her programming. She had no choice in the matter.
We have no idea if anything similar exists here. We had best find out first before anything else.
If I was a Solar crafter of the High First Age producing an artificial construct with weapons that could potentially kill me, I sure as fuck would safeguard my programming and put in access codes to prevent any rival, rebel or assassin trying to subvert its programming for their own purposes.
Whether another Solar or a Lunar or someone's summoned demons.
During the Usurpation, more than one Solar who wasnt at the dinner was murdered by hitherto-loyal DBs and Sidereals subverting the programming of their constructs.
And thats not counting what, if anything, may have been introduced into its programming since.
Our proper course of action should be
- Find out if we even have authorized access, or if we'll be risking triggering lethal failsafes by trying to work on it, from a stab in the back to a self-destruct explosion taking out everything within 20 yards
- Then find out if we can fix it, and if we have the materials to do so
- Lastly, decide if we SHOULD fix it, or if the world is better off if its deactivated.