International bestselling editor and writer with over 35 million books in print, Kristine Kathryn Rusch writes in many genres, from science fiction to mystery, from western to romance. She has written under a pile of pen names, but most of her work appears as Kristine Kathryn Rusch. Her novels have made bestseller lists around the world and her short fiction has appeared in eighteen best of the year collections. She has won more than twenty-five awards for her fiction, including the Hugo, Le Prix Imaginales, the Asimov's Readers Choice award, and the Ellery Queen Mystery Magazine Readers Choice Award.

Publications from The Chicago Tribune to Booklist have included her Kris Nelscott mystery novels in their top-ten-best mystery novels of the year. The Nelscott books have received nominations for almost every award in the mystery field, including the best novel Edgar Award, and the Shamus Award.

She also edits. Beginning with work at the innovative publishing company, Pulphouse, followed by her award-winning tenure at The Magazine of Fantasy & Science Fiction, she took fifteen years off before returning to editing with the original anthology series Fiction River, published by WMG Publishing. She acts as series editor with her husband, writer Dean Wesley Smith, and edits at least two anthologies in the series per year on her own.

To keep up with everything she does, go to and sign up for her newsletter. To track her many pen names and series, see their individual websites (,,,,

The Renegat by Kristine Kathryn Rusch

As a young recruit, brilliant engineer Nadim Crowe accidentally destroys an entire Scrapheap full of ships. Now, decades later, he ends up on the crew of the Renegat, the only ship in the Fleet ever sent on a mission backwards to investigate an ancient Scrapheap.

Something invaded that Scrapheap and the Fleet wants to know what. Or who.

The Renegat: The only ship the Fleet dares risk. The Renegat: A ship of misfits and screw-ups sent on an impossible mission. All alone in deep space.

A thrilling new addition to the Diving Universe.


The Renegat is a standalone novel in my Diving universe series. The Fleet uses an anacapa drive to enable travel across vast distances. Only sometimes the anacapa drive causes time slips. Some of those slips are minor—a few hours or even a day or two. And sometimes those slips are years, decades, even centuries. The crew of the Renegat finds themselves far from home, both in time and space, only to experience something even worse—a mutiny. – Kristine Kathryn Rusch



  • "Rusch's handling of the mystery and adventure is stellar, and the whole tale proves quite entertaining."

    – Booklist Online on Diving into the Wreck
  • "This is classic sci-fi, a well-told tale of dangerous exploration. The first-person narration makes the reader an eyewitness to the vast, silent realms of deep space, where even the smallest error will bring disaster. Compellingly human and technically absorbing, the suspense builds to fevered intensity, culminating in an explosive yet plausible conclusion."

    – RT Book Reviews Top Pick on Diving into the Wreck
  • "Rusch delivers a page-turning space adventure while contemplating the ethics of scientists and governments working together on future tech."

    – Publishers Weekly on Diving into the Wreck



The Scrapheap

Internal Clock Malfunction

Perpetual Now

The force field breach caught the Scrapheap's attention. It tried to enter the breach properly into its log, but could not cite a date. The Scrapheap did not have the capacity to manufacture a date, so its systems awoke.

It needed assistance. Human assistance.

The Scrapheap did not know how long it had functioned without human assistance. Its internal clock had doubled over on itself three times and had malfunctioned on the fourth reset. That malfunction did not trigger an alarm, because it was no threat to the Scrapheap itself.

The Scrapheap monitored and evaluated threats. Its protocols demanded that it record major breaches and threats from outside. Internal threats were dealt with routinely.

Energy spikes were minimized. Certain ships were contained within their own private force fields.

The Scrapheap had done such things since its beginning.

It did not think of its beginning as anything but the start of its internal clock. It was not self-aware, although certain systems had more awareness than other systems.

The Scrapheap knew its own history. It had started as five decommissioned ships, stored side by side in a region of space its creators believed to be little used and off the main travel routes for the sector. Those decommissioned ships were to be transferred to the nearest sector base, but the base had no need for the ships.

So the first force field was created. It protected all five ships. Those ships remained in the force field, and then other ships were added. Some were brought in under their own power. Others were towed in by a larger ship. Still others arrived using their anacapa drives.

On one occasion, those arrivals had caused a chain reaction. The energy wave from the arriving anacapa drive had triggered a malfunction in a dying anacapa drive, causing one ship to explode and resulting in damage to two more.

Humans had arrived three months later with a new core for the Scrapheap, and a control center to protect that new core. The Scrapheap's mission grew that day, to preserve and protect the ships and the ship parts inside its force field.

The Scrapheap followed its mission diligently, recording its activity, logging it, using the dates from its internal clock.

Over centuries, the Scrapheap grew from five ships to one million, three hundred and sixty-three thousand, seven hundred and one. Not all of the ships were intact. Many of the items the Scrapheap called ships were not ships at all, but parts of ships.

In the early centuries, the humans returned regularly, flashing their identifications and removing ships that still had value. The humans moved intact ships inside a secondary force field near the core, and did not touch those ships, although those ships routinely maintained themselves. If one of those ships malfunctioned, it would flag itself for removal from the secondary force field. If possible, the ship would then remove itself from the secondary force field.

If the ship could not move itself, the Scrapheap would do so, using a powerful tractor beam that only existed inside the secondary force field.

The Scrapheap maintained all of the external shields that belonged to the ships gathered in the main force field. In that way, those ships would not spark another disaster. The Scrapheap added and removed miniature force fields, rotated some ships away from others, kept those with dying anacapa drives isolated from ships that could possibly negatively interact with the dying drives.

The humans went in and out of the Scrapheap, removing ships and parts of ships as needed. Some ships' anacapa drives were activated remotely, and those ships left the Scrapheap on their own power. Sometimes humans entered the Scrapheap through various portals built into the large exterior force field, and removed ships.

One thousand years into the Scrapheap's existence, the humans ceased removing ships. The only changes inside the Scrapheap were the ones the Scrapheap initiated itself.

Until the breach.

A ship tried to enter the Scrapheap. That ship did not know the code to activate the portal in the force field, so the Scrapheap activated its defenses.

The ship left.

This was not unusual. It happened routinely throughout the Scrapheap's existence, so the Scrapheap did not create a log for the incident, although the incident remained in the short-term buffers.

Then the ship returned. It used a code that had not been used since the first four hundred years of the Scrapheap's existence.

The force field opened.

The ship entered the Scrapheap, flew around many of the ships inside the Scrapheap, and left.

The ship repeated this behavior for two hours on each of the next five days.

On the sixth day, the ship returned. It followed a path it had used before, and stopped near a DV-Class ship. Humans then emerged from the returning ship, and traveled to the DV-Class ship. The humans entered the DV-Class ship, and one-point-two hours later, the anacapa drive inside that ship activated.

The DV-Class ship left the Scrapheap.

The new ship remained inside the Scrapheap. The Scrapheap tried to contact that new ship. It did not respond. The new ship eventually left via engine power through the opening in the force field.

The Scrapheap then tried to identify the type of ship that the new ship had been. That type of ship did not exist in the Scrapheap's records. Nor did the ship seem to be a ship that could have been updated from any other ship in the Scrapheap's records.

The Scrapheap had scenarios programmed into its systems for such an occurrence. The scenarios postulated that the ship had stolen the entry codes and was now stealing vessels.

The Scrapheap would attack the ship when it returned.

But it did not return.

Instead, the DV-Class vessel returned. Humans, identified as the same or similar to the ones who had arrived earlier, traveled from the returning DV-Class vessel to another DV-Class vessel. Then the second DV-Class vessel's anacapa drive activated, and removed the second DV-Class vessel from the Scrapheap. Then the first DV-Class vessel left again.

At that moment, the Scrapheap attempted to log the interaction as a serious breach. It could not do so. It no longer had the ability to time-stamp a log.

The Scrapheap had a failsafe to send information to its creators should the log function break down. But that failsafe had limitations.

The Scrapheap had to send the information from its short-term buffers to the humans before the information was recycled out of the buffers.

Upon discovering that it needed to send the information from the short-term buffers, the Scrapheap acted immediately. It sent the information along the channels it had been using for its decennial updates.

The Scrapheap also requested a repair of its systems as well as an augmentation that would prevent the unwarranted theft of vessels.

It could not attack vessels that had been stored inside the Scrapheap.

But it could flag the breaches as suspicious, maintain the records of those breaches, until the human creators arrived and determined what to do with the information.

Because the buffered information needed to be protected differently than the decennial update and because the buffered information could not be permanently stored, the Scrapheap requested a receipt be sent when the information reached its final destination.

The Scrapheap had not made such a request in all of its existence. The request set different protocols into place, protocols the Scrapheap had never used before.

The information system was old. The buffered information first traveled to sector bases closed, abandoned, and forgotten. The information then routed back to the Scrapheap, which repackaged the information and sent the information again.

The Scrapheap repackaged six times before the information managed to get through that hurdle in the system.

The Scrapheap then deleted the previous sector bases from its communications channel. It sent information directly to the working sector base.

More ships disappeared weekly, so the Scrapheap sent buffered information weekly.

The Scrapheap did not get a response.

Its systems were programmed to continue to send information until it received instructions.

It received none.

So it continued to send, even as the buffer cleaned itself out, and the log mechanism jammed. The Scrapheap did close the force field and reactivate the defensive measures, but sanctioned DV-Class vessels continued to enter the Scrapheap, disgorge humans to another DV-Class vessel, and then remove that DV-Class vessel.

The emptiness inside the Scrapheap grew.

The Scrapheap was not alarmed by this change. The Scrapheap was not sentient.

But it responded like any powerless being under attack.

It asked for help.

It defended itself as best it could, while it waited for a response.