Specifically, the initial run is described as being a "dry run" for Phrex's escape from Horizon, but the actual mission seems to imply that it *is* the escape; the test for figuring out the purpose of the wiring job mentions that it allows Phrex to access the Ares network, and the debugging section says that Phrex will use the hole in the floor to jump into the Talos drone.

It's not actually Phrex that escapes but another AI. Everything that happens, the other runner team, the escape, is complete random chance/opportunity to the teams original mission. Hence the Monkeywrench title. It is entirely possible that they misprinted Phrex's name of the escapee but i got the feeling that the wiring was to set up the later run but the other AI took advantage of that. THat might just be my interpretation. Fun mission but a little awkward to run.

The original plot was to have 2 seperate AIs, but his was thought to be too much for the adventure. I personally think it made more sense.. but hey, what can I say... Originaly the 2nd AI was called Thoth (and is currently called Memphis and causes no end of trouble for some Seattle runners I know)

Firestorm is going through final edits for publication ow, and I ahven't seen any of those... if it remains the same however, Phrex's contact with stored memories from the Jarhead he integrated with are the main cause for the problems. It actually woked though in giving me a thrid faction to play with that Phrex was not just cut out the way he originally was (Horizon gets into the game as well as Ares)