"Easily. But more sensitive means more false positives. We'll be chasing ghosts."
"Better to chase ghosts than miss the real threat. Implement it."
I dove into the algorithm modifications, adjusting detection thresholds, expanding the correlation analysis to catch even subtle variations of the command signal pattern. Around me, Engineering continued its work, as the tension built. Someone aboard Mothership, someone with technical expertise and intimate system knowledge, was actively sabotaging operations. And now they knew we were hunting them.
"Modified algorithm is ready," I announced twenty minutes later. "Sensitivity increased by thirty percent. Any power modulation that remotely resembles their command structure will trigger analysis."
"Deploy it. And Dana?" Er'dox's amber eyes were steady on mine. "Good work. Both on the detection and the analysis. You're thinking like a senior engineer."
"I'm thinking like someone who spent three weeks keeping broken systems functional through creative problem-solving. Same principles."
"Exactly. Which is why you're valuable here, you approach problems from directions our standardized training doesn't consider."
The compliment warmed something in my chest that I didn't have time to analyze. I focused on the displays instead, watching the enhanced algorithm activate across Mothership's power network.
"Trap implementation begins in four hours," Er'dox said. "We'll announce the countermeasures through official channels, make it look like we're confident we've solved the intrusion problem. Meanwhile, we monitor for any response."
"They'd be stupid to take the bait."
"Most saboteurs are arrogant enough to believe they're smarter than their opposition. We're counting on that arrogance."
The next four hours were standard monitoring work with variance checks, system adjustments, the routine maintenance that kept Mothership functional. But underneath the routine, tension hummed like a live wire. Every crew member in Engineering knew we were hunting a saboteur. Every variance alert made hearts jump before analysis confirmed it was normal fluctuation.
I caught Er'dox watching me during the monitoring, his expression unreadable. When our eyes met, he didn't look away.
"Problem?" I asked.
"No problem. Just making sure you're maintaining focus despite exhaustion."
"I'm fine."
"You're functional. There's a difference." He moved closer to my station. "After this trap deployment, you're taking actual rest. Twelve hours off-duty. Non-negotiable."
"Twelve hours is?—"
"Necessary for sustained performance. Dana, you've done field operations, algorithm development, and now active monitoring in less than twenty-four hours. Your work is exceptional, but your body has limits." His voice softened slightly. "I need you sharp, not running on determination and caffeine."
"You sound concerned."
"I'm always concerned when valuable engineers push themselves to break down." But something in his expression suggested it wasn't just professional concern. "Promise me. Twelve hours rest after this mission phase."
"Okay. I promise." The words came easier than expected.
At 1400 hours exactly, Captain Tor'van made the announcement through official channels. I listened to it broadcast across Engineering's comm system, noting the carefully crafted language designed to sound confident while revealing just enough detail to bait our saboteur.
"All crew, Command. We've identified the power network intrusion methodology and implemented countermeasures. The saboteur's access has been blocked through enhanced encryption protocols. Additional details are available through department security briefings. Tor'van out."
The announcement was deliberately vague about specifics. No mention of my algorithm. No details about detection capabilities. Just a confident assertion that the problem was solved, with implied vulnerabilities in how we'd solved it.
Now we waited for the saboteur to react.
Three hours of monitoring. Three hours of watching power distribution patterns with my enhanced algorithm scanning for any hint of command signal activity. My team rotated through shifts, but I stayed at my station, unable to walk away when we were this close.
Er'dox stayed too, monitoring from his central command station with the same focused intensity.
At 1647 hours, my algorithm triggered.
"Got something," I said, pulling up the correlation analysis. "Subsection nine, timing pattern consistent with command signal characteristics. But it's different from before, more distributed, trying to mask the sequential propagation."
