8. Competence
Competence
JULIAN
A dual-access breach requires an unhesitating forfeiture of operational control.
But sitting in the Coloane Village safe house, staring at the dark, scrolling logic of the Consortium’s maritime server farm, I’m not dictating the tempo.
I’m following hers.
“Garbage data compiled.” Her voice is a low, mechanical monotone matching the rhythmic strike of her keyboard. “Payload sits at four terabytes. Ready on the deployment queue.”
She’s positioned at the exploit layer, armed with an improvised denial-of-service packet so massive it’s mathematically guaranteed to crash the satellite uplink routing traffic to the offshore holding shell.
I’m positioned at the architectural level, waiting for the exact millisecond her attack chokes the server. The reboot will drop its firewall for a fraction of a second. That’s my window—step inside, rewrite the handshake, lock the Consortium’s credentials out for good.
To execute the exploit successfully, we need a zero-latency, perfectly synchronized deployment sequence. We haven’t run a diagnostic. We haven’t practiced the timing string.
“Deployment algorithm is hot.”
“Routing intercept is prepped.” My hands hover over my keys. I don’t look at her. I watch the monitoring port I attached to her outgoing signal. “Call the sequence.”
We established a shorthand. It took exactly three hours and forty minutes for two inherently suspicious, deeply isolated operators to develop a fully integrated communication loop.
I don’t know when it happened. I just know that she doesn’t need to speak full sentences for me to understand her logic.
“T-minus ten.”
Her screen reflects in the dark glass of the blackout window. The green code cascades at a blinding speed. It isn’t structured. It’s violent. It’s a digital battering ram currently aimed at a five-billion-dollar maritime defense grid, and she built it by hand while drinking black coffee.
“Five.”
I shift my weight forward, bracing for the execution.
“Execute.”
She drops the payload.
The denial-of-service packet floods the satellite uplink. The resulting data traffic spike registers on my monitor as a massive, blinding red wall. The offshore server staggers under the immense weight of four terabytes of localized garbage data.
For three seconds, nothing happens. The latency hangs in the room, heavy and dense.
Then, the red wall abruptly flatlines to zero.
“Server’s down.” Her fingers fly over the keys as she establishes her monitoring loop. “Automated reboot sequence initiated. You have thirty seconds before the firewall cycles back online.”
I hit enter.
I don’t waste time looking for the main door. I don’t need a door. The walls are down.
I deploy the administrative overwrite I held in my queue. The script bypasses the system’s organic security protocols entirely, diving straight into the core handshake infrastructure. The original code requires an alphanumeric sequence verified by a localized Swiss IP.
I highlight the logic block and obliterate it.
I replace it with a closed-loop authentication protocol. It’s impenetrable, unyielding, and legally backed by the United States Department of Justice. The moment the server establishes a connection to the internet again, it locks every single account attempting to route through it.
“Protocol overwritten. Executing permanent lockdown.”
“They’re coming back online.” Ivy watches the screen. “The firewall is cycling. Eight seconds until lock.”
“I hold the administrative tier.” I finalize the script, embedding the changes.
“I’m salting the logs.” She shifts her attack vector without missing a beat.
She doesn’t simply detach. Before the server’s security grid solidifies, Ivy dumps a sophisticated, highly disruptive algorithm straight into their forensic data cache.
She isn’t just deleting our footprints.
She’s scattering three million false data trails leading to dormant servers in Reykjavik, Mumbai, and Johannesburg. It will take the Consortium’s forensic team a solid month to untangle the mess, assuming they can afford to hire a team once they realize their money is trapped.
“Firewall holds.” The status indicators snap from yellow to a solid, undeniable green. The administrative access is locked. The accounts are frozen. The server is completely, systemically, deaf to the Consortium’s demands.
I sit back in my chair.
“The node is dark.”
The rapid-fire clatter of her keyboard finally ceases.
The silence that follows isn’t empty. It’s charged with the heavy, electric residue of a synchronized assault. We just crippled the secondary routing hub of the most dangerous financial network on the planet, and we did it from a safe house in Coloane Village while the rest of Macau sleeps.
I look at Ivy.
She releases her grip on the mouse. She leans back in the mechanical chair, letting her head rest against the tall backrest. She closes her eyes and releases a long, slow exhale.
I analyze her physical posture. The tension in her shoulders melts into a quiet, profound exhaustion. She doesn’t look like a victorious hacker who just beat the house. She doesn’t look triumphant or arrogant.
She looks satisfied.
She looks exactly like a system architect who solved a geometrically impossible equation.
I recognize the expression perfectly. I recognize the feeling behind it. It’s the deep, cellular satisfaction of executing a flawless logic sequence.
I didn’t know it looked like that from the outside. I didn’t know the quiet serenity of operational competence could pull like gravity.
Her competence is violently attractive, a fact that lands with cold, analytical clarity.
It’s a massive operational liability.
I stand and walk to the small kitchenette. I find the grinder, load a fresh allocation of beans, and set it running. The harsh, mechanical grinding noise obliterates the lingering tension in the room.
I need the noise. I need the manual task to re-align my focus.
The coffee brews in silence. I pour two mugs. Black.
I carry them back to the operational space, setting one on the desk beside her right hand.
She doesn’t jump. She simply opens her eyes, picks up the ceramic mug, and takes a long drink. The steam curls around her face, highlighting the sharp angle of her cheekbone.
“You code like a fed.”
She doesn’t look at me. Her eyes lock on the dark monitor, tracking the final, dying echoes of the server we just killed.
I take a drink of my coffee. I don’t engage the provocation immediately.
“I mean that as a compliment.” Her voice is low in the quiet room. “It’s load-bearing. There’s nothing wasted. Everything you build is designed to withstand a siege.”
She understands the architecture. Fourteen analysts at the Department of Justice review my scripts every month, and none of them understand the philosophy behind the code.
They just verify the legality. She spent three hours inside my routing node and instantly diagnosed the entire psychological foundation of my work.
“You code like you’re daring the system to catch you.” I lean against the edge of my desk.
She takes another sip of coffee. A ghost of a smile touches the corner of her mouth.
“That’s the point.”
I watch her. In her profile, they categorized her as a reckless improviser. They assumed she was chaotic.
They were categorically incorrect.
The chaos is a deliberate defense mechanism. She builds beautiful, wildly dangerous exploits because she trusts her ability to navigate the fallout better than she trusts a locked door.
“You survived eleven weeks against a cell of internationally funded assassins.” I keep my tone perfectly level. “The technique is effective.”
“I survived eleven weeks because the strike teams didn’t know what they were looking for.
” She sets her mug down, dragging her fingers through the tangled mess of her dark hair.
“But whoever is building their cyber-defenses does. The person writing their counter-code isn’t just reacting to me.
They’re predicting me. An architect building a cage. ”
I file the metaphor away. The Architect. It’s a fitting title for the ghost operating the Consortium’s digital defense.
“I wasn’t the primary target.” Her voice drops, losing its defensive edge. “I was the collateral damage standing next to the real target.”
She shifts her gaze to me.
“Your file.” The sharp, analytical curiosity abruptly shifts the vector of the conversation. “The Kincaid breach. The woman Task Force 9 protected. Iris.”
I nod once. I don’t confirm or deny the classification status of the file. I simply acknowledge the fact.
“The file says the Consortium contracted a hit squad to liquidate her before she could testify.” Her eyes narrow slightly. “It also says Boyd Vance was the primary deterrent deployed by your team to ensure she survived.”
She’s systematically probing the operational boundaries of Task Force 9, trying to assess exactly how lethal the people supposedly protecting her actually are.
“Boyd Vance ensured her survival, yes.”
“What happened to her?” The question is entirely sincere. I can see the underlying calculation.
Ivy is a woman who lives her life according to a strict risk-assessment protocol. She asks if trusting Task Force 9 works. She wants to know whether the protection holds or whether the witness eventually dies when the cameras turn away.
“She testified.” I hold her gaze. “She survived the trial. She is currently living under a modified identity, provided directly by Hutch. She is completely safe.”
Ivy studies my face. “And Boyd?”
“Boyd accepted a grounding order.” I keep my expression deliberately neutral. “To stay with her.”
Ivy blinks, genuine surprise registering on her face. “He stayed with the witness.”
“He stayed with the woman he protected.” I correct her because the distinction matters.
It isn’t a fairy tale; it was a ruthless, calculated decision made by a man who refused to leave a vulnerability exposed.
“They’re together. He still operates for Task Force 9, but they reside at the mountain stronghold now. Neither of them is missing.”
Ivy absorbs the data point. She files it alongside the analog map and the maritime DoS exploit. It is a new variable in her internal logic sequence.
“This Boyd Vance.” Her tone dips into something lighter, something almost teasing. “Is he really the best operator you have?”
She remembers my answer from earlier. More.
I don’t smile. I keep my expression locked into the cold, deadpan neutrality of a federal briefing.
“He’s the best I’ve ever seen. In the field.”
I take a slow drink of my coffee, holding her gaze over the rim of the mug.
“I’m better at everything else.”
I say it with total, unshakeable sincerity. The arrogance is deliberate. The arrogance is a weapon.
Ivy stares at me for a split second, processing the unapologetic weight of the statement.
And then she laughs.
It isn’t a scoff. It isn’t the defensive, mocking sound she deployed in the rental car during the standoff.
It is a real laugh. It is startled out of her, bright and genuine, transforming her face entirely.
The hard edges of the cornered operator vanish, replaced for three terrifying seconds by a woman genuinely amused by the man standing in front of her.
That’s the laugh.
The realization hits me with the sudden, catastrophic impact of a severed power line.
I know, with the precise, undeniable certainty of an architect who understands system compromise, that I am, without a doubt, in genuine trouble.
I don’t look away. I can’t look away.
The desire I’ve methodically suppressed for the last three hours suddenly bypasses every security protocol I possess. It isn’t theoretical anymore. It isn’t an operational hazard I can mitigate with distance.
I want to touch her.
I want to cross the three feet between our desks, take the coffee mug out of her hand, and put my hands on her. I want to see if the heat radiating off her skin feels identical to the adrenaline coursing through her code.
The silence stretches, heavy and dangerous. The amusement slowly fades from her eyes, replaced by a sudden, answering awareness. She feels the shift in the room. She feels the gravity.
I break eye contact and turn back to my desk. I put the coffee mug down, hit a key to wake the partition, and forcefully drag the unread file for the final, tertiary routing node to the center of my screen.
“We have eighteen hours.” My voice is a flat, mechanical drone. “The core node won’t surface until we execute the final DoS sequence on the third relay.”
I bring my hands up to the keyboard.
I need to work.
I must work.
If I force myself to analyze the architecture of the Consortium’s final routing layer, I don’t have to address the fact that the most dangerous vulnerability in this apartment is no longer the Southeast Asia cell closing in on our signal.
The most dangerous vulnerability in the apartment is me.