LC Rains – Over Dinner: Reactor Ghosts & Code Gremlins
"You ever have that moment where you think you’ve solved the puzzle… and then wish you hadn’t?"
LC sets his fork down, pushes his tray aside, and glances toward Leilani with a small nod of mutual recognition.
"Leilani and I were working through the reactor feed from Andriana’s room — and for a moment, I thought we’d just caught a clever little monitoring tool. Someone doing system diagnostics from their quarters. Maybe weird, maybe nosy, but nothing catastrophic. Then it blinked."
He taps the datapad, which lights up briefly with a layered subroutine tree — complex, elegant, and hostile.
"What we found wasn’t just monitoring. It was buried command code. Passive. Trigger-based. Waiting."
He leans forward, resting his elbows on the table.
"This is a Trojan — probably built off internal system protocols. Elegant enough to look like internal diagnostics until you know where to look. Once the right condition's met — a jump, a system state, hell, a crew voice command — it activates. And if it had? This dinner would be happening in vacuum suits while the backup scrubbers try to keep us breathing."
He lets the silence stretch a second too long.
"So. I want your thoughts. I want your eyes. If anything has felt off, if any sensor pinged wrong, if you’ve seen a flicker on a console or a relay act drunk — speak up now."
Responses by any of the crew?
He looks around the table, letting the crew have space to process.
Then his eyes land on Decherrek.
"Decherrek — this ship was skip-traced when you found her, yes? You disabled traps, cleared data cores, checked for ghost circuits. But this? This wasn’t in the logs."
He straightens up slightly.
"I need your original debrief. Anything you pulled, anything you found and couldn’t explain — anything that might link to this. Was this part of the original trap suite, or was this laid in later?"
Responses by Decherrek?
LC exhales through his nose, pushing the datapad to center table.
"We’re going to have to scrub the whole reactor control net. Not just code — physical interlocks too. And this is important, we’ll need to spoof the system while we do it, or this thing might activate while we’re still poking at it."
He looks to Bronz, Leilani, and Tharrok in turn.
"Tamm — I know you’ve been elbows deep in power systems before. You willing to help crack open the primary housing while we guide you? I need hands I trust inside that conduit path."
Responses?
"Leilani, you’re already neck-deep with me. But I have the idea that seeing the hologram may give you better insite towards a solution without activation. Get with Said-MA as she is a wiz with computers."
Responses?
"Tharrok — you've got the sense of things others miss. If this was designed to be seen, but ignored... I want your instincts on every layer we peel back."
Responses?
He gives a nod toward Kayla and Said-Ma’s empty seats.
"Said-Ma will coordinate the scan queues and script isolation with me and Leilani. We need Kayla’s diplomatic skill set to go to Andriana and ask her for help to identify and solve this."
Then, more softly — a shift in tone.
"Now… about Andriana. This code was broadcasting in her quarters. Doesn’t mean she wrote it. Might not even mean she knew it was there. But she’s got insight we need — especially if that hologram was tied into deeper systems."
He nods again, more directly now.
"Kayla, Leilani, Bronz — I want the three of you to talk with her. Calmly. Make it clear we think it’s a threat to all of us, and we’d value her help figuring out how that projection ties into the virus structure. You’ve got the right touch for this. I don’t want her feeling cornered — but I do want her looped in."
Responses?
A pause.
Bronz, I am asking you to go directly with Kayla and Leilani as your experience with engineering and your past troubleshooting will help out in diagnosing the problem without having to set the damn Trojan off."
Responses?
Another pause.
"Speak now, sign up, or pass the Kaffe. But we deal with this before we lose power in JSpace, or we don't arrive at all."