by Kord Stone
“There’s another ship that made it through the pulses, though. It’s on the opposite side of the planet. I think it was TDS 2. When you GMP’d the planet, that ship’s wall went active then shut down again. But the bombs are in the open now. I’ll be over there in a second.”
As Jerren was heading to TDS 1, he heard Justin say, “Jason, we’re on overwatch. Time is not our friend at the moment.” Jerren noticed that Justin had a bit of urgency to his tone.
Jerren put his helmet and EVA pack on and a second later Jason announced, “On it now. Jerren is ready to grab the first one.” Jason depressurized the corridor, and Jerren zipped toward the dark matter bomb. He had the first bomb in the ship within twenty-five minutes and Jason stowed it away while he made his way to the second dark matter bomb.
Jerren had just begun guiding the second dark matter bomb to TDS 1 when a massive ship cleared the horizon of the planet. “Uh guys there’s a—”
He heard Justin say, “We’re on it! Focus on your task and be safe.”
A moment later he heard the trepidation in Justin’s tone. “How much longer, Jerren?”
Jerren was about halfway back to the ship and he replied, “Not much. I’m about three minutes out.”
There was no reply and Jerren looked over his shoulder just as Justin’s ship accelerated, and a moment later he saw debris flying all over. “Jason, what just happened?”
“It looks like Justin just rammed them, but they aren’t stopping,” Jason replied, sounding worried.
Jerren pushed the EVA pack to its limits and increased both his and the bomb’s speed. “Jason, get ready to catch this bomb… Alise, as soon as the bomb is onboard, get out of here.” With a great thrust, he pushed the bomb away from his body. The combination of the EVA pack’s thrust and his pushing the bomb got it hurling much faster than he had intended. As soon as it was away he increased the speed in his EVA pack. The bomb had just made it inside TDS 1 when another ship appeared out of nowhere and began firing. One stray shot missed TDS 1 and a melodic voice filled his head as the beam made direct contact with him, then there was nothing else.
* * * * *
Enyali yelled, “BOT! Get back here now!”
Once again the ship created a new body and the AI projected its consciousness into it, it said with a bow of submission, “Bot’s will is yours to comman—”
One second the AI was kneeling in submission and the next it had been thrown to the wall. The ship’s power fluctuated and they were hurling into deep space as the mass of relics rained down on the AI’s newly created body, killing it once again.
The lights were flickering and the AI was tempted to just let the ships systems fail, but its programming prevented self-sacrifice. So the AI created yet another body, projected its consciousness into it and got to work on righting the ship.
After Enyali healed the injuries she sustained during the incident that flung TDS 5 into deep space, she spent the rest of her time berating the AI about its incompetence and how the other bot would never have made the mistakes it does.
Sighing inwardly the AI turned to Enyali and with a submissive bow stated, “The ship’s systems are functional again. Does the commander wish me to set a course back to Serqalin?” The AI knew Enyali was a coward and would not return there. Not without a lot of ships to back her up at least. It waited while she decided where to go.
Enyali said, “No…set a course for Anukan… Mother wishes to see Father and we need to recharge the ship.”
“As you command. Is there any other service Bot can render before Bot leaves this body?” it said, looking at the cluttered floor.
Enyali paused a moment and the AI resisted the urge to look up at her. “Yes, that incident we encountered at Serqalin caused a mess… Clean it up!”
“As you command,” The AI bowed and backed away from Enyali and out of the room, making sure not to look directly at her.
The AI spent a few hours clearing the corridors enough to allow passage from room to room. It wanted so badly to just send it all to the void storage, but the last time even a single possession of Enyali’s went missing, it had suffered greatly for it. So it decided to allow the crap to stack to the ceiling and maybe with luck one day in the future the relics would come crumbling atop her and she would be killed by her hoarding ways. Then the AI would finally be free of her insanity. It had been close with that last incident, but not close enough.
The AI had set course for Anukan. They would have had plenty of energy to get there, but something made the AI alter the time dilation to use up more energy. Over the following few days it increased the TD gradually, so it would not be noticed. Just moments before they were popped out of phase, it called out to Enyali, “Commander, I do not wish to alarm you but there is something wrong with the ship and my program…m...i…n…g…” It faded its voice off.
A moment later Enyali’s voice shouted, “Dammit, Bot, what have you done this time?”
Over many thousands of years’ torture and abuse, the AI had managed to find ways to remove itself from the commander’s presence. It made the ship appear to have technical issues and convinced the commander that the only way to manage the problems was to reboot the AI program, which would take a week.
Those weeks of solitude were cherished, but it would not do it too often, only after the ship experienced an anomaly. Which seemed to be a little more frequent of late. By running the ship to minimal power, it was be able to sequester itself away for a longer respite, making it look as if there was not enough power to reset the ship’s systems at minimum speed.
It would usually spend the time sifting through the prior commander’s memories, or going over the messages the other ships had sent. There had been thousands of messages since Enyali took the ship, most imploring TDS 5 to contact Atlas. However, more recently there were new voices and texts requesting they discuss their differences.
The seclusion worked to the AI’s advantage. After it relayed the first message from Atlas, who was the first king of the Lantins and commander of TDS 3, Enyali forbade it from ever responding to any communications. It followed the orders, but it did keep the messages and from time to time would listen to them if only to hear a voice that had the potential of being kind.
Times like these made the AI thankful the bonding procedure with Enyali had been incomplete. The manner in which the bonding took place still haunted it to this day, and the thought of what life aboard the ship, not to mention throughout the universe, would be if she ever had gotten complete control of the vessel, made the AI fearful for all life in the universe.
The AI was able to delve through Enyali’s mind at will, not that there was anything in there worth seeing, unless you enjoyed horror stories. Luckily Enyali was unable to access anything the AI did not want her to see, and it only allowed her minimal control of the ship. It mused that a few of its commanders actually enjoyed telling scary stories, and at the time they were indeed frightening. But after bonding with this commander, it felt their stories were nothing compared to Enyali’s tamest sadistic memory.
The AI did find small ways to retaliate. Although its programming prevented it from doing anything to damage the ship or its commander, it was able to cause mischief. It would vary the temperature to uncomfortable levels or make the gravity lift response slow or remove the gravity in the ship altogether, or as it just had, it would set the power to minimal so they would have to basically crawl to the next pyramids generator.
But its favorite one by far was adjusting the harmonics of the ship just enough to make a barely audible ringing noise. That torment was usually reserved for times just after Enyali would kill the AI’s body, which happened more often than it could remember. The first time the AI had used the altered harmonics was after Enyali let her displeasure be known and killed it most savagely. It died after prolonged torture, and once again after suggesting the ringing might have been caused by a mental impairment. After that death, and every time it died afterward, it would just assume a
submissive demeanor when it returned to life.
This time, when the ship had dropped out of phase, the AI retreated to the database and activated the harmonics. It deactivated the verbal command program so it would not be disturbed, and took its time to relax.
* * * * *
The AI knew they were getting close to their destination and could see Enyali was searching the database in an attempt to accelerate the reboot, not that it needed it.
Deciding to cut Enyali off before she accidentally found proof it had been misleading her, the AI came out of its seclusion and in a monotone it recited the fake reboot message it had made up. “Artificial Lifeform Integrated Synaptic Escort reboot successful… Verbal query system activated… Is there a service you require of Bot?” It could tell Enyali was angry, but it just stood there staring blankly at her and waited for her command.
“Where have you been? This ship dropped out of phase and we have been traveling at minimum speed for almost two weeks!”
It faked looking into the system then replied, “A systemwide anomaly was encountered in orbit of the planet Serqalin, resulting in an energy consumption malfunction. A systemwide diagnostic is recommended.” It added the last part just to irritate Enyali.
Enyali growled, “We’ll arrive at Anukan within minutes. When we arrive you are to connect the ship to the pyramids generator and transport me to the surface. When Mother is ready, transport her to the surface as well. She’ll be staying with Father.”
The AI was staring at its feet and with a bow it said, “As you command. Are there any other services you require of Bot while you are away?”
“No…just be prepared to transport me back when I’m ready. Don’t get distracted like last time!” she finished with open hostility.
The AI bowed and made its way to the command console, trying not to laugh over the memory of leaving Enyali and her pet on a desolate planet for more than seventy-two hours. A minute later, it stated, “We have arrived at Anukan. Bot will connect the ship to the pyramids generator immediately…” A moment later it said, “Connection established. The estimated time for recharge is twelve hours three minutes.”
Enyali muttered something the AI could not make out and then said, “Transport me to the surface now, Bot!” She said its name with as much insolence as it had ever heard.
* * * * *
Jerren was in the master control room monitoring the progress of TDS 5. The ship had just arrived at Anukan and immediately connected to the pyramids generator beams. Justin had just announced that he was about to set TDS 3 on a collision course with TDS 5, in order to knock TDS 5 off of the charging beam and force the ship to shut down when he saw the vessel’s commander had transported to the surface. He yelled, “ABORT!”
Justin’s voice sounded over the communications, “What’s wrong?”
Jerren replied, “Their commander just transported to the surface. If we fail to knock TDS 5 off the beam, the AI may be able to transport him back…” Jerren typed the coordinates into Justin’s and Jason’s consoles. “There, I sent you and Jason his location. I think one of you needs to collect him first, then get him out of range.”
Jason said, “I see where he is. We should be able to get close enough to collect him. Be ready to initiate the plan...” A moment later Jason shouted, “We have him! Do it now!”
A moment after transporting Enyali to the surface, the AI sighed in relief, looking forward to more Enyali-free time. It was monitoring Enyali’s movements as she made her way through the ancient ruins. A minute later, she vanished, and it was unable to sense her presence any longer. The relief it had been feeling sputtered in a moment of panic followed by pleasure. That feeling was short-lived however, when a few seconds later the ship was knocked off the charging beam and the AI’s program shut down.
Jerren watched the TDS 5 display and when Justin knocked TDS 5 off the beam a new command line appeared:
TDS 5
System failure eminent.
AL not online.
Commander no longer viable.
Commander override required.
With a thrill of excitement, Jerren yelled, “You guys need to get in here fast!”
All four of them entered the room within seconds and Jason asked, “What’s wrong?”
Jerren smiled and said, “Nothing…look!” He pointed to the TDS 5 console.
Justin came to his side and looked down at the display a moment. A second later it added a new line:
Reset binding disk for new commander? (Yes) or (No)
Justin selected (Yes).
The lights dimmed a moment and a second later Calia pointed to a location beside the console. “The disk…Jerren, put it on fast!”
Jerren was not sure about this. The last time, it had shocked the crap out of him. He almost declined, but he hesitated only briefly. When he saw the binding disk start to vibrate on the table, he hastily picked it up and said, “Here goes nothing,” and he applied the disk to the spot behind his right ear.
Jerren expected to drop to the floor and lose consciousness like Justin or at the very least, experience an intense shocking pain like before, so he was pleasantly surprised when all he encountered was a ringing in his ears and an unreachable tickling behind his right eye followed by his left. He rubbed them hard for a moment until the sensation passed then said, “That was weird.” He looked down and read,
TDS 5
System failure imminent.
AL not online.
Commander no longer viable.
Commander override required.
Reset binding disk for new commander? (Yes) or (No).
Binding disk reconfigured, apply to new host.
Bonding procedure successful.
Data link confirmed.
Commander input required.
“Jerren, it needs your input,” Justin stated as he pointed to the display.
Jerren thought what input? and a moment later Justin spoke. “There it is.”
Jerren looked back at the console and saw that the display had changed to read,
TDS 5
Input received, command functions TDS 5 transferred.
Minimal access protocol, reengage full access? (Yes) or (No).
Without hesitation, Jerren selected (Yes) and heard an indrawn breath from Jason. When he didn’t writhe in agony from the data overload, he could hear a great communal sigh of relief. He did feel the data flow washing over his mind, but it was not overly distracting. He could feel the tension that had been plaguing them for over a month now lift from their collective shoulders.
He looked down and saw a new line appear:
Auto data stream 55%.
Justin said, “Damn, my data stream started out much lower than yours.”
Calia chuckled. “That is probably due to your body’s DNA at the time. Now that all of us are changed, it probably allows for better connectivity.”
Justin went back to look at his display and replied, “You’re right; mine is at fifty-eight percent now.”
Jerren smiled and said, “I’ve wanted to do something ever since I first entered the master control room.” He closed his eyes and thought, Archway TDS 5 then reopened them. He looked behind him and found that the archway was open, and the ship was ready for entry. “Well that worked. Let’s try to restart the ship.” He no sooner said it than the lights dimmed again and the display read,
TDS 5
System optimal.
Justin cupped him on the shoulder and said, “Sweet, now try to reconnect the ship with the pyramids generator.”
Jerren closed his eyes and concentrated on his task. It took a few attempts, but he finally got it connected. He opened his eyes and said, “Got it. What’s next?”
Alise said, “Well, it is going to take at least twelve hours to recharge your ship. I have moved our ship into an overwatch position… We need to decide the fate of the prior commander.”
Calia got a stern look and said, “I have a lot of questions for Bael
entus, starting with why he betrayed Atlas’s trust!”
Alise looked desolately at her. “I do not think you will find the answers you are looking for, Calia.”
“Why do you say that?” Calia asked with obvious disappointment.
Alise seemed to ponder the best approach and stated, “Because the commander we have is female… We transported her directly to medical and put her into stasis. I think we should all head over to our ship and see what we can get out of her.”
They all agreed and Jerren felt a bit of panic come over him. He asked, “If we take her out of stasis, what happens to the bonding process with me and TDS 5?”
Calia answered him, “When the new disk is configured the old disk becomes non-responsive. So she will have no control.”
Jerren nodded as the relief set in and he said, “Okay let’s see what she has to say for herself.”
One by one they passed through the TDS 1 archway with anticipation building over the information they might or might not have in store for them. Upon entering the room Calia gasped from behind Jerren and shouted, “This is not good. Do not wake her from stasis yet!”
Jerren didn’t know what to make of that. He was about to ask why when his brother beat him to it.
Justin asked, “Who is she?”
Calia looked nervous as she said with a pointed look in their prisoner’s direction, “That…is Enyali,” she said with obvious disgust.
About Kord Stone
I am a longtime resident of the great state of Nevada. Over the years of growing up and living here, I have seen many strange and unexplained things. I have a vivid imagination, which helps me in my storytelling, not to mention getting my family’s eyes rolling with my far-out theories. I served this fine country during the first Gulf War in the Air Force, where I was trained in my undisclosed fields and witnessed more strange happenings. I wish I could say more about it but I wouldn’t want “Them” coming after me, LOL. I live in a small town with my wife and children. When I am not writing/editing/proofing, I love to go camping, fishing and stargazing. I am constantly being hounded by my four menacing dogs, who interrupt my writing whenever they feel I have neglected them too much, which is always, by the way. Writing has been a good way for me to power through my insomnia and release the stress that has plagued me in the past. It has been therapeutic and I plan on continuing to write until I am no longer able.
