Quote:
LC: projects a schematic of the Miss Fortune’s reactor control system outlining the Power plant with a colored overlay (marked as Adriana's helographic projection)
(SNIPPED)
"We pulled this out of the power plant's log. Leilani caught it piggybacking on a pre-jump load test cycle. We’re talking signature obfuscation, timing algorithms keyed to false positives — like someone wanted it to look like a hardware glitch."
*[He glances up at Said-Ma.]*
"Leilani, Tamm, Bronz and I believe it is a Virus is embedded in the power plant firmware, not flight control, and it doesn’t trip until second-stage field stability, which could mean either it was meant to kick in-jump... or it was planted by someone who didn’t know how we sequence. Either way, the damn thing’s dormant now — for the moment....we think and that is where you come in."
[LC taps to isolate a block of code — unreadable garbage to most, but for the trained eye, there’s structure in the entropy.]
"Leilani and I are at the end of what we know and we need a second set of eyes on the assembly layer here. Someone ran a recursive loop with a payload that might be adjusting safety thresholds, or might be faking telemetry. Either one means trouble." [/b][/color]
Quote:
Leilani nodded along with Rains; she'd been studying the code along with others.
"The code isn't adaptabable, so we should be able to quarantine it for now. Then once we know what the code's signature is, we might be able to teach the ship's own system to get rid of it. That's the good news!"
"Bad news is that every system talks to the Power systems, for obvious reasons, so we don't know how infected they are. Normally, I'd suggest we purge the system and restore from the factory backup, but I'm guessing that isn't an option?"
Quote:
"Not while we are still in J-space," Tamm adds
Quote:
LC: "Engineering Team: Tamm, you keep the plant stable and honest. Leilani, you pair with him, using your naval engineering and computer training to spot where the virus might be hiding in the ship’s arteries. You two are our safety net — no component gets isolated without your say-so and a redundant path lined up.
- Computer Team: Said-Ma, you and I will parse the code directly, subroutine by subroutine. We’ll trace the recursive loops and identify which ones are just smoke and which ones might be wired to a failsafe. I’ll handle the documentation and command-tree legality — no change gets logged without a fallback.
- Psi Projection Anchor: For this, we’ll need Adriana’s help — if she’s willing. Her talent can give us a map of the code’s shape, not just its numbers. Bronz, you’ll anchor her, keep the projection steady, and translate it into terms we can use. Your instincts, her clarity. Together, you give us a view none of us can reach alone.
- Ship Monitoring systems or Bridge watch: (looking at Tarrok). "Tharrok, my brother from another mother, this unfortunately falls to you to as watch officer."
Prime Directive: Maintain the jump bubble, and never cut life support. Anything else we can quarantine or bypass until we make landfall."
NOTES: The above is intended as a summary. Slightly edited. Now for crew actions!
Said Ma agrees to take the lead on analyzing the computer code. "Eventually we'll have to find out how it got in here, too. And where it came from."
Bronz is tasked with "anchoring" Adriana's Psi/+computer projection and manipulation(?) or the Power Plant controls.
Tharrok has the 'watch'.
Leilani and Tamm team to both keep the current power operations stable and also trace the 'reach' of the malicious code. (Did I understand that correctly?)
OOC:
Will be starting a new thread. Each crewmember should declare their actions/plans as best they can. Dice rolls might be a good idea though may not be used; stated actions are more important at this point.
MOVING TO A NEW THREAD....