Back Mindstar Rising
Chapters (47)
  1. Cover
  2. Mindstar Rising
  3. Annotation
  4. CHAPTER ONE
  5. CHAPTER TWO
  6. CHAPTER THREE
  7. CHAPTER FOUR
  8. CHAPTER FIVE
  9. CHAPTER SIX
  10. CHAPTER SEVEN
  11. CHAPTER EIGHT
  12. CHAPTER NINE
  13. CHAPTER TEN
  14. CHAPTER ELEVEN
  15. CHAPTER TWELVE
  16. CHAPTER THIRTEEN
  17. CHAPTER FOURTEEN
  18. CHAPTER FIFTEEN
  19. CHAPTER SIXTEEN
  20. CHAPTER SEVENTEEN
  21. CHAPTER EIGHTEEN
  22. CHAPTER NINETEEN
  23. CHAPTER TWENTY
  24. CHAPTER TWENTY-ONE
  25. CHAPTER TWENTY-TWO
  26. CHAPTER TWENTY-THREE
  27. CHAPTER TWENTY-FOUR
  28. CHAPTER TWENTY-FIVE
  29. CHAPTER TWENTY-SIX
  30. CHAPTER TWENTY-SEVEN
  31. CHAPTER TWENTY-EIGHT
  32. CHAPTER TWENTY-NINE
  33. CHAPTER THIRTY
  34. CHAPTER THIRTY-ONE
  35. CHAPTER THIRTY-TWO
  36. CHAPTER THIRTY-THREE
  37. CHAPTER THIRTY-FOUR
  38. CHAPTER THIRTY-FIVE
  39. CHAPTER THIRTY-SIX
  40. CHAPTER THIRTY-SEVEN
  41. CHAPTER THIRTY-EIGHT
  42. CHAPTER THIRTY-NINE
  43. CHAPTER FORTY
  44. CHAPTER FORTY-ONE
  45. CHAPTER FORTY-TWO
  46. CHAPTER FORTY-THREE
  47. CHAPTER FORTY-FOUR

"Just nine of them?" Greg asked incredulously.

"There's nothing complicated about the process," said Philip. "We've had neuro-coupling for eight years now, and the RNA splice is a standard procedure. It's only the cost of this much bioware which prevents it from becoming widespread."

"OK, next question. Would the hotrod team which launched the blitz have to be told you were here, or could they find out by analysing the data flow through Event Horizon's network?"

"They'd know the NN core was an important part of the network from observing the data flow, but that's all. Unless they were specifically told what the NN core was, the best they could guess is that it was an ordinary bioware number-cruncher loaded with a Turing personality-responses program."

"In other words, they know about you."

"Looks that way, boy."

"With only twelve people knowing about the core, I can pin down that mole for you, no messing," Greg said. "So where is the other leak liable to have come from?"

"Ministry of Defence, I hope," said Walshaw.

"Most likely," Philip Evans admitted. "Morgan here kept a tight security cordon around the giga-conductor project, but we had to co-operate with the MOD. It was on a confidential basis, of course, but leaks are inevitable on a project this big. You just have to balance the risk against the payoff."

"Two separate leaks," Morgan said. "It's an appalling lapse. One I could accept, but compromising the NN core and the giga-conductor as well, that hurts."

Greg paused, worried about what Walshaw had said, his intuition producing that annoying tingle again. Two separate, simultaneous, high-level leaks was stretching coincidence a long way. "Did you ever find out how Kendric's tekmerc team acquired their data on Zanthus's security monitor parameters in the first place? They must have had copies to work out that destreaming manoeuvre."

Walshaw frowned, glancing at the black column. "We are still tracking down the actual tekmercs. They've taken a lot of trouble to cover their tracks."

"So nobody I found passed the data over?"

"No."

"Could it have been a hotrod burn which pulled the data?"

Julia cleared her throat, giving Walshaw an enquiring look. The security chief nodded reluctantly.

"To get at the monitor programs you would have to either burn straight into the security division's data core or copy the programs direct from Zanthus's 'ware," she said. "Zanthus would probably be the easiest option, but you would need to be up there to do it."

"If it was a hotrod burn," Greg mused.

"Bloody hell, boy; you're not telling me we've still got a Judas in the company?"

"There is no such thing as coincidence," Greg said soberly. "Two leaks on the two greatest ultra-hush projects Event Horizon is running, plus a loose end over the security monitor programs. Make up your own mind."

"I said that it had to be someone familiar with our security data procedures," Julia said.

"So you did, Juliet, so you did."