[HOLODECK]
(( Bridge, Deck 2, USS Tiburon ))
Holodeck simulations were becoming even more realistic—impressive for an environment that already felt like real life. T’Korva felt the ship groan beneath the deck plates as the cadet tried to match the Bedfordshire’s speed. Their oddly assembled testing crew had run into unexpected variables—an obvious test parameter meant to make the exercise more accurate, she supposed.
The cadet seemed focused. T’Korva monitored the navigational and operational changes from her terminal while continuing to assess other options. The cool surface of the control panel felt as if it were warming up, a mental illusion given how well these systems were designed, without the random exploding stations of days past.
Johnson: We have the increment and the interval. If we match that, we’ll speed up with the Bedfordshire and be able to merge warp fields. Coming up on the ship now!
The clock was ticking, T’Korva was never one for anxiety, and this moment was no different. Whether it was the years of combat training with her father, before she was even 8 years old, or the Klingon academy days with weeks of no sleep meant to build their stamina and responsiveness when fatigued—none of it mattered now, this was a simulation, no matter what happened, she was walking away just fine.
Lohkina: Do it.
She was impressed by how quickly the cadet made the changes, prompting course corrections, speed adjustments, and invisible shield harmonic and warp updates that would make the next attempt more feasible.
T’Korva: Monitoring shield harmonics. ::beat:: their systems are responding to our prefix commands, I’m accessing their shield protocols now. ::beat:: and they should be coming down.
Lohkina: Repeat that last?
Johnson: All right! Their shields are down!
T’Korva: I’ll start working on the helm security, see if the program making the speed increases can be turned off.
In that moment, she was reminded she wasn’t an engineer. She’d spent time in engineering, as any command-level officer did at some point, but she preferred contributing from a tactical perspective. Still, she kept a close eye on system upgrades and changes as they came through the Starfleet ship operations memos—never knowing when a new piece of technology might offer a tactical advantage.
Lohkina: Very well. Options?
Johnson: We should be able to get into their systems, right?
T’Korva: We have tactical access and access to life support. I’m working on engines now, but my experience around prefix protocols is rusty, I will need a few more minutes. ::beat:: I have alerted transporter rooms to begin beam out when available.
Lohkina: Responses
Johnson: All shields have a certain amount they can extend past the actual size of the ship, right?
T’Korva: You are correct. ::beat:: And you may be onto something cadet. ::turning to the captain:: we could tie our shield generators into the Bedfordshire’s and double our output. It would be more strain on their engines, but if we divert any of the energy of eddy impacts towards the Tiburon’s inertial dampeners, we could reduce the strain on the Bedfordshire systems?
Lohkina: Responses
T’Korva suspended her work on the engine access and began focusing on tying the two ship’s shield generators together. She’d taken down the Bedfordshire’s shields, but left the generators at the ready, which was a smart move considering the new approach they were taking.
Johnson: Okay…here we go!
Quickly taking a moment to review the trnasporter logs, she could see that they had already transported 50 crew members from the Bedfordshire. But one of the notations in the reports started T’Korva—the crew members they beamed over were all unconscience.
T’Korva: Captain, we have 50 of their crew members aboard the ship, but none of them are awake. ::beat:: Medical has been dispatched.
Was it possible they had a virus they’d just exposed their own ship to? Was it something to do with their life support systems? oO Their life support appears to be functioning within normal parameters? Oo She had no idea where to start, they really needed a science officer—the computer would generate any real officer they didn’t already have present, but T’Korva knew that there was one thing the holodecks could never replicate, creative intuition—at least not well.
Johnson/Lohkina: Responses
An alarm indicator went off on her console drawing her focus. They were only minutes away from the first eddies and they’d only transported about 20% of the Bedfordshire’s crew. Quickly looking back towards the code she’d been working on for the shields, the compiling was almost complete—she would barely have time to test the code before implementing it.
T’Korva: Not to give us multiple things to address at once, the shield program is ready, but I do not have enough time for a proper test before we reach the eddies. I recommend we implement it and make any adjustments in real time.
Johnson/Lohkina: Responses
T’Korva went to work on the console, pulling up every monitoring program she knew about and making sure that the program did not have any fatal flaws that would have been identified during the testing phase—it appeared ready to go.
T’Korva: The program stands at the ready, awaiting your orders.
The few moments, which felt like ages, that she waited for the approval, T’Korva continued running through the command prompts and verifying the API like interface with the Bedfordshire was stable. She would have preferred to use a more stable connection, but the API interface is what she got, and it would have to do.
Johnson/Lohkina: Responses
As the captain gave the order, another green indicator lit up, she now had access to the other ship’s engines, at least diagnostically speaking…
Tags! / TBC
Lieutenant Commander T'Korva
Fleet Relief Officer
Currently Assigned to USS Octavia E, Butler NCC-82850
Writer ID.: O239910TA4