Back Network Effect Save as PDF
Contents (23)
  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8
  9. 9
  10. 10
  11. 11
  12. 12
  13. 13
  14. 14
  15. 15
  16. 16
  17. 17
  18. 18
  19. 19
  20. 20
  21. ACKNOWLEDGMENTS
  22. ABOUT THE AUTHOR
  23. CONTENTS

I liked that. I had watched media with ghosts, though I didn’t have access to the files or titles anymore. I said, A ghost that kills you.

To prove to me that I was helpless, TargetContact started to show me security video. There was no metadata to tell me where it had been recorded. Not a ship. The space dock, maybe? But what was an agricultural bot doing on a space dock? An agricultural bot that’s fighting with … Holy shit, that’s me.

TargetContact told targetControlSystem, This is software, not a SecUnit. The SecUnit was on the surface, we have it now.

TargetControlSystem told TargetContact: You are giving it data, stop.

Me Version 1.0 is on the planet and has been captured and we are seriously screwed now. I’m sorry, ART. I’m sorry, humans and Me 1.0.

That was when I caught a tentative secure contact from SecUnit 3.

It had just disabled its governor module.

I checked the corridor camera view and watched it surreptitiously move its feet, the armor flexing as it shifted its shoulders. It was strange seeing this from the outside. I knew what it was thinking. My first realization had been: the governor module’s gone and I can do whatever I want! My second realization: what do I want? (I’d been stuck on that question for a long time.) (Actually Me Version 1.0 was still stuck on it, as far as I knew.)

I asked 3, What do you want?

SecUnit 3 said, To help you retrieve our clients. Then it added, After that I have no information.

Now it’s on.

I sent SecUnit 3 a brief instruction/message bundle and it answered, Acknowledge. On your mark.

TargetContact was telling targetControlSystem, Neutralize this software, then—And then they started screaming because I’d triggered all my code bundles and targetControlSystem had triggered its code bundle to purge SecSystem and I had attempted a purge of targetControlSystem. Weirdly, TargetContact was somehow directly connected to targetControlSystem and seemed to be experiencing physical responses based on what I was doing to it. Wow, that was a bad position to be in just about now.

TargetContact tried to disengage and but I locked it in. TargetControlSystem tried to delete me but I was making single-function duplicates of myself and turning them loose so it was having to divide its attention a lot. Other things were happening at the same time, three of which were:

1) CodeBundle.LockItDown had closed all the hatches on board except those directly between SecUnit 3’s position and the shuttle access.

2) CodeBundle.FuckThem had fried all targetDrones.

3) CodeBundle.FuckThisToo had cut the connections between the solid-state screen device and the humans’ implants. Oh, and I shut down life support on the bridge so the Targets in there would be thinking about other things besides restarting their screen.

I told SecUnit 3, Mark.

It pivoted to the locked hatch of the lounge, punched through the panel for the controls, and hit the manual release before I could open it remotely. (That’s one of the reasons Me Version 1.0 misses its armor.) Some humans had jolted awake when the implant connections were cut and others had started to twitch and moan. ART’s human Turi, who was young like Amena, shoved halfway to their feet and stared at SecUnit 3 as it stepped inside. SecUnit 3 said to all the dazed, half-conscious humans, “I’m here to retrieve you. Please cooperate to the best of your ability and I will take you to safety.” It had read my message bundle because it then turned its helmet to Turi and added, “Perihelion sent me.”