Elara’s gaze remains fixed on the encrypted lattice.
“This isn’t finished,” she says.
“No,” I answer.
The enemy survived the truth.
CHAPTER 35
ELARA
The data suite feels smaller tonight, not because the room has changed but because the implications inside it have expanded beyond anything these walls were meant to contain. The processors run hot enough that the air carries a faint metallic sharpness, and the projection field spreads from floor to ceiling in layered geometries of code that shimmer and fold back into themselves like something alive and patient. I stand with both hands braced against the edge of the central console, watching the encrypted lattice rotate slowly in three dimensions, and I let my breathing match its rhythm because forcing this too quickly will only make it close again.
Kael remains behind me, not crowding but close enough that the warmth of him presses into the space between my shoulder blades, a steady presence that anchors without distracting. Rethan stands to my right, arms folded across his chest, the tension in his posture restrained but visible in the set of his jaw as he studies the rotating encryption architecture.
“This is not Alliance construction,” I say at last, my voice low and deliberate, as I magnify the inner branch of the lattice and let the decryption engine begin peeling it back layer by careful layer instead of striking it head-on.
Rethan tilts his head slightly, studying the recursive pattern unfolding in luminous lines. “Alliance military code fights harder than that,” he says, and there is irritation beneath the observation because this quiet compliance feels more unsettling than resistance would.
“It doesn’t just fight,” I reply, tracing the cascade of keys as they fall in repeating triplets and then echo backward through the branch in a subtle recursive signature. “Alliance code doesn’t care about aesthetic cohesion. It’s blunt. This is engineered to be elegant.”
Kael steps closer, the projection light reflecting faintly off the pale ridges along his skin. “Elegant in what way?” he asks, and the question is not casual; it is strategic, as though he is mapping the shape of the enemy even before I confirm its name.
I expand the validation cycle and let it complete fully so they can see what I see. The triplet cascade finishes, and then there is that faint backward ripple—a delayed resonance that closes the loop instead of terminating it.
“That echo,” I say quietly. “Baragon uses it in their diplomatic cipher architecture. I intercepted it once years ago in a sanctions packet routed through a neutral trade mediator. It’s subtle, but it’s consistent.”
Rethan’s expression tightens. “Baragon does not involve itself in regional conflicts openly.”
“No,” I agree, as I unlock the next layer and allow the supply route matrix to unfold across the wall in a network of thin, glowing threads. “They involve themselves in destabilization quietly.”
The room grows still as the routes resolve into recognizable patterns. Alliance depots. Civilian energy distributors. Independent freight lines. The connections are indirect but deliberate, layered beneath shell companies and intermediary contractors that are legally separate but structurally aligned.
Kael’s voice lowers in timbre. “These shipments,” he says, pointing to a cluster of highlighted transfers, “they predate the summit by months.”
“Yes,” I answer, overlaying the summit bombing file on top of the logistics timeline so the correlation becomes undeniable. “Material acquisition. Financial disbursement. Deployment coordination. It was seeded long before Valen ever stood at that podium.”
Rethan exhales slowly, the sound measured but edged. “You are saying he was supplied.”
“I am saying he was cultivated,” I reply, as I expand the financial lattice beneath the routes and allow the ownership chains to unwind through multiple holding entities until the Baragon-aligned intermediaries appear at the terminus like a shadow that had been standing there all along.
Kael’s gaze remains fixed on the projection. “He believed he was acting independently,” he says.
“Yes,” I answer, and I feel the weight of it settle in my chest. “He believed escalation was stabilization. He believed he was preserving Alliance order through controlled aggression. But he was guided—resourced, informed, and nudged toward specific thresholds.”
I shift the display again, drawing up archived conflict data from peripheral systems and overlaying it against the decrypted pattern. A mining dispute in an independent cluster flares into view, its timeline aligning with a Baragon-aligned funding injection that predates the outbreak by weeks. A border clash between minor powers lights up next, showing the same recursive encryption signature embedded in an otherwise innocuous trade sanction file.
The pattern repeats in deliberate cycles: ignition, escalation, partial containment, structural weakening.
“They don’t want annihilation,” I say, letting the full model expand across the far wall so both Kael and Rethan can see the predictive arcs. “They want contraction. They want corridor reductions, resource strain, political fracture. Enough damage to destabilize but not enough to unify against them.”
Kael steps forward, close enough now that his shoulder nearly brushes mine as he studies the Baragon projection model that sits buried at the heart of the cache. “This model,” he says, his voice steady but carrying something darker beneath it, “it anticipated our treaty.”
“Yes,” I reply, because there is no point in softening that truth. “It accounted for a reduction of Reaper territory and a retraction of Alliance mobilization. It predicted corridor constriction as a likely outcome if both sides avoided total war.”
Rethan’s eyes narrow as he scans the percentage curves. “They ran simulations on our survival.”
“They ran simulations on our restraint,” I correct, and I feel a flicker of cold clarity as the realization sharpens. “Full-scale annihilation would have been unpredictable. Managed contraction is profitable.”
