Chapter 2 Zoric
ZORIC
Chief Martin’s data has occupied my thoughts since her briefing concluded.
I sit at my command station, long after the bridge crew has rotated to gamma shift, analyzing the patterns she identified.
The precision is undeniable. The implications, deeply concerning.
My own initial review missed the subtlety of the pattern, focusing on individual incidents rather than the elegant, terrifying repetition she uncovered.
Her mind sees systems in ways mine does not.
The bridge doors open. It’s her.
Unacceptable.
She moves directly to my station, her gait revealing exhaustion—a shortened stride, micro-corrections to maintain balance suggesting insufficient rest. The tablet in her hands displays scrolling data streams. Her jumpsuit bears fresh oil stains on the left sleeve and right knee.
She's been working in the conduits again, despite my orders to delegate physical labor to her team.
“Captain.” Her voice carries that edge I'm learning to identify as frustration poorly contained. “I need to show you something.”
I gesture to the auxiliary display screen. “Proceed.”
She pulls up her analysis, and I'm immediately struck by the sophistication of her predictive model. The fluctuations aren't just regular—the recovery time is decreasing by point-zero-two percent each cycle.
“The pattern's tightening,” she says, pointing to the convergence curves. “Whoever's testing the system is refining their technique. In three weeks, maybe four, they'll have enough data to execute whatever they're planning.”
Her intensity elevates when discussing her systems. Her speech patterns become more rapid and clipped. It's the same response I observe in Zephyrian engineers when they encounter elegantly complex problems, but she directs it outward rather than containing it internally.
“Your analysis is thorough.” I study the projections, running my own calculations. Her timeline aligns almost perfectly with my own. “You've identified variables I hadn't considered.”
She blinks. Once. Twice. Her pupils dilate—a surprise response. “You believe me?”
“I believe your data.” I pull up my own analysis on a secondary screen. “The evidence supports your conclusions. The question remains: who possesses both the access and expertise to execute this level of system manipulation?”
Her pattern analysis is brilliant. I've been cross-referencing it with security access logs and identifying who has both the capability and opportunity to execute these manipulations.
“The access logs show a pattern, but it's complicated,” I say.
“Three authorization codes appear during each fluctuation. Two from Engineering—Walsh Burton and Diana Moss. One from Security—Tobias Hale. All three have legitimate reasons to access these systems. All three were present during every incident.”
“That's the problem.” She leans against the railing, and I notice the dark circles beneath her eyes. She's been working well past safe operational limits without rest, based on the capillary patterns in her sclera. “It has to be someone in Engineering. Someone who knows these systems intimately.”
“Or Security.”
“Hale has the access.” Her jaw muscles contract visibly. Anger or frustration, difficult to distinguish. “But I can't prove anything. And without proof, accusing anyone creates exactly the kind of chaos you're trying to avoid.”
She's correct. The accusation would divide her department, reduce efficiency by an estimated 30%, and potentially alert the saboteur. “Continue monitoring. Document everything. When the next fluctuation occurs, I want real-time observation of all relevant personnel.”
“Already planned.” She straightens, and our eyes meet briefly. A slight blush colors her cheeks. “Thank you for taking this seriously.”
“Your expertise warrants serious consideration.” The words emerge more formally than intended. “I would be... inefficient not to acknowledge superior pattern recognition when presented with it.”
Her mouth curves upward in a genuine smile that causes my markings to brighten without command. She notices, her gaze flicking to my temples before she turns to leave.
The Council's mission parameters didn't include contingencies for this particular form of distraction.
Giorgi Perrin occupies the chair across from my desk at precisely 1400 hours.
He's the civilian council head, a man of fifty-three standard years with graying hair and an expression that suggests perpetual optimism despite the mathematical improbability of maintaining such emotional consistency.
His thermal signature indicates genuine calm.
No stress markers, no deception patterns.
Unusual for someone requesting resources during a mission with tightly controlled supply chains.
“Captain, thank you for seeing me.” He settles into the chair as though we're meeting for recreational purposes rather than official business. “I wanted to discuss expanding the holiday preparations into the secondary habitation rings.”
I pull up the resource allocation spreadsheets. “You've already been granted approval for decorative installations in the primary corridors. What additional resources are required?”
“Lighting, primarily. And some synthetic garland. Maybe some of those projection units for simulating snow.” He leans forward, enthusiasm raising his vocal pitch. “The children are asking about it, and with a little time before December, we could create something really special.”
“Define 'special' in measurable terms.”
He pauses. His eyebrows elevate—surprise response to my request for quantification. “Well... special like making them feel at home. Giving them something to look forward to. Morale is quantifiable, isn't it?”
“Indirectly.” I input calculations based on crew performance metrics since the decorating project began. “Civilian psychological assessments show 12% improvement in reported contentment. Interpersonal conflicts decreased by 8%. Your project correlates with measurable mental health improvements.”
“So we can expand it?”
The logical answer conflicts with resource management protocols. But the data supports his request. “You may expand to the secondary rings. However, power consumption cannot exceed current allocations. If your lighting systems overload circuits, the project terminates immediately.”
“Understood.” He stands, offering his hand—human greeting ritual I've learned to reciprocate. His grip is warm, slightly damp. “The Chief Engineer has been very helpful with the technical aspects. She's good people, Captain.”
“Chief Martin is competent.” I release his hand, noting the terminology 'good people'. A human idiom indicating positive character assessment beyond professional capability. Interesting.
Perrin leaves, and I return to analyzing Chief Martin's fluctuation data on my primary display.
The patterns reveal sophisticated understanding of plasma dynamics and energy distribution networks.
Three separate methodologies converge in her analysis, suggesting she approached the problem from multiple theoretical frameworks before synthesizing the results.
Impressive.
The door chimes. I grant entry without looking up, assuming Perrin forgot some detail about his resource request.
“Captain.” Chief Martin's voice, not Perrin's. “Do you have a moment?”
I look up. She's carrying two cups, and the rich scent of coffee cuts through the recycled air. She places one on my desk, the ceramic making a soft sound against the metal surface.
“I thought you might want this.” She settles into the chair Perrin vacated. “You've been reviewing my data for two hours.”
I haven't noticed the time passage. “How did you know?”
“Your office lights show up on my Engineering board.
They've been on continuously.” She sips her own coffee, and I notice her hands have been cleaned—the oil stains removed, though faint discoloration remains under her fingernails.
“Also, Morris mentioned you missed the scheduled officers' meal. You need to eat, Captain. Even Zephyrians need fuel.”
The observation demonstrates concerning attention to my schedule. Or perhaps it's simply the kind of systemic monitoring any good chief engineer would perform. I choose to interpret it as the latter.
I accept the coffee. The temperature is optimal for consumption. She remembered my preference from the morning briefing. The caffeine content will improve my cognitive function for the next three hours.
“I found additional correlations in your data,” I say, pulling up the relevant screens. “The fluctuations synchronize with crew shift changes. Whoever is executing this has intimate knowledge of personnel schedules.”
She gets up and comes to my side of the desk, leaning in to view the screens directly.
Her proximity is immediate—less than an arm's length.
From this distance, I can detect her scent profile.
Machine oil, yes. But also something floral.
Her soap, perhaps, or shampoo. And beneath that, her natural biochemical signature, which registers as pleasant in a way I don't have proper categorization for.
“These correlation coefficients are incredible.” She leans closer, pointing at specific data intersections. Her arm brushes my shoulder. Incidental contact that elevates my skin temperature. “You've mapped it against every variable. This must have taken hours.”
“Several hours.” I'm acutely aware of her proximity, of the way her breathing rhythm changes when she concentrates. “Your initial analysis provided the framework. I simply expanded the dataset.”
She turns her head, and suddenly her face is very close to mine. Her eyes are dark brown with amber striations visible at this distance. Genetic variation in melanin distribution creating unexpected aesthetic complexity.
Her gaze moves to my temples, tracking the patterns there. My markings betray me, shifting toward gold now.