Sounds cool.
>catastrophic infrastructure failuresWould a cyberattacker really do that? /dev/nulling that /dev/sda would be pretty bad already, and considerably simpler.
>What worries me is that I'd introduce this opportunity waiting for a solution and then instantly present a solutionYou can do something more interesting than intro -> problem -> solution, stuff doesn't go that way IRL, you can leave stuff broken if you want. Maybe have the guy publish the AI-backup for it to be hopelessly exploited just because he doesn't give a fuarrk or something like that.
It would be cool if the guy frequented some textboard or chatroom of some sort, but that shouldn't be overdone with overly 1337 nicknames and lingo.
Try not to be too dull with the writing (the building looked like X. the guy did Y. he remembered Z), make it fun to read. Btw, if anyone knows of a /cyb/ author that also happens to be good at writing (I mean, having cool ideas but also being good at making them interesting to read), please tell.
Also, why was the AI there? I don't get the backup part.
>>2002Like in that movie,
The Machine