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

Overse had finished repairing the repair drone and sent it off to begin the rebuilds of ART’s other drones. She was sleeping on a couch in the lounge next to the galley with Ratthi, who had finished the biohazard cleanup. There was snoring.

Arada was sleeping in one of the station chairs on the control deck. (They’re very comfortable, so it’s not as bad as it sounds.)

The medical scans had finished and Thiago walked Eletra back to her bunkroom. He hadn’t gotten much more out of her than Amena had, though his questions were more subtle. With his prompting, Eletra had gone over her augment clock and was now severely confused. It showed their transport had been in this system for forty-three corporation standard days. She was certain that was wrong. It was more support for the theory that Eletra had undergone some kind of memory manipulation. The initial scan analysis showed no genetic manipulation, no hidden devices or non-human biologicals.

All my remaining drones were on sentry duty, but I made Amena go to an unused bunkroom near the galley because it was easier to defend if we were attacked by something. (It was unlikely, but so was everything unexpected that had happened so far. My risk assessment module had given up generating reports three hours ago.)

Amena tried to just lie down on the bare bunk and pillow her head on the sealed bedding pack but I made her get up and unfold it and do it right. (“You’re mean,” she groaned.)

I opened another bedding pack so my bunk would be more comfortable to sit on. I had a lot of coding and analysis to do so I wouldn’t be caught unprepared again. I needed to create workarounds for the drone-resistant camouflage on the targetDrones and countermeasures for the Target’s helmets and gear. I also needed to anticipate how targetControlSystem would countermeasure my countermeasures so I wouldn’t be screwed by an on-the-fly software update. I needed to analyze the solid-state screen device and find out if it really was a Pre–Corporation Rim relic. And I had to analyze the new data files I had just created from the shuttle’s logs.

I pulled in the data Ratthi had uploaded to the feed during his pathology examinations and the scans of the Targets’ suits and helmets. Overse had also done some helpful hardware analysis of the targetDrones. Then I got my queries and processes running so I could get started on the code. I also split off an input and started World Hoppers episode 1. I’d seen it before (lots of times before) so I didn’t need to give it my full attention.

(I really, really wanted some time to pull a new show out of longterm storage and watch a few episodes so I could really relax, but World Hoppers in background would help. It was also bait.)

After twenty-seven minutes, it worked. I was aware of ART looming in my feed. (Imagine sitting in front of a display surface and someone eight times your size shoulders in and sits in the chair with you.) It was watching World Hoppers, and also backseat driving my coding and doing its own analysis of the data. The solid-state screen device does resemble known schematics of Pre–Corporation Rim technology, ART reported, showing me a scan and the matching examples. But it is not a factory-built unit; it was assembled from components gleaned from other devices of similar age. No trace of alien remnant or known strange synthetics detected.