Chapter 12 #2
Every radio on Tidewater goes silent. Every encrypted channel drops. Every operator in the field loses contact with command, and the blackout window opens for whatever Garrick's handler has planned on the physical side.
That's the mission reason. The counterstrike isn't close to finished. I can't build it from behind a security cordon.
It's clean and logical and defensible, and it isn't the real reason.
The real reason is that telling Griff means saying I'm scared, and saying I'm scared means admitting that the woman who flew across an ocean at eighteen to prove she didn't need anyone has spent the last several weeks rearranging her entire operating system around a man with steady hands and a Texas drawl, and that rearrangement has created a vulnerability she doesn't know how to patch.
I save the message. I log it in the monitoring framework.
I begin tracing the routing path, working backward through the C2 infrastructure to determine whether the message originated from inside the base network or was relayed in from the handler's external position.
The packet headers suggest an internal origin, routed through the C2 chain to obscure the source, but the anonymizing layers make a definitive answer impossible without more time.
If Garrick sent this from a terminal on base, the internal routing hops will narrow his physical location. If the handler sent it from outside, the external relay pattern will confirm a different threat posture.
I don't pick up the phone.
The hours between the message and the briefing disappear into the code, and by the time the comm building watch changes and the daylight through the windows shifts from gray to full morning, the progress has climbed past the halfway mark.
The briefing is at eleven, in Hartwell's conference room, with the full task force assembled.
I present the counterstrike architecture, walking the room through the interception protocol and the deployment sequence with the precision I've used in every briefing since I arrived at Tidewater. I need another night, minimum.
Rivera is the one who gives me away.
She doesn't mean to. She's presenting her update on the physical search for Garrick, the gate camera footage, the patrol sweeps, the NCIS team combing the base.
Then she pulls up the overnight monitoring log, the one my framework generates automatically and feeds to her secure terminal, and she says, "The monitoring framework flagged a threat communication at oh-eight-hundred.
Ms. Bradshaw, have you updated Lieutenant Holland on the specifics?
We need to coordinate the physical security response. "
The room is quiet for a beat. Then Griff's head turns.
He's standing against the wall near the door, the same position he takes in every briefing, arms crossed, one boot flat against the concrete.
His face doesn't change. His posture doesn't shift.
But his eyes move from Rivera to me, and the look that lands is not anger.
It's the flat, controlled assessment of someone who just discovered an uncharted threat in a space he thought he'd cleared, and the betrayal underneath it is worse than fury because fury is loud and this is silent.
"What communication?" His voice is dangerously even. He doesn't raise it.
Rivera's gaze moves between us. She registers the temperature shift, and whatever she reads in Griff's posture tells her to keep moving.
She redirects to the next agenda item without answering his question, and the briefing continues for another twenty minutes while I sit with the knowledge that the conversation waiting on the other side of this room is going to be worse than anything Garrick could send through a network.
Hartwell adjourns. The room empties in clusters, Rivera's analysts collecting their tablets, Thatcher and Holden heading for the corridor, Sullivan already on his radio coordinating the next patrol rotation.
Griff doesn't move from the wall. He waits until the last person clears the door, and then he reaches behind him and pulls it shut.
The conference room is empty except for the two of us and the hum of the overhead projector cooling down.
"When." Griff gives me one word. He doesn't need more.
"This morning. Addressed to my workstation directly. Not intercepted traffic this time, but a message sent to me using my custom system identifier. They know who I am, they know the loft, and they know about us."
"And you didn't tell me."
"The counterstrike isn't finished. If I'd told you this morning, you'd have told Hartwell, and Hartwell would have pulled me off the comm building floor and locked me behind a security detail. Everything I've built would have died where it stood."
"So the code matters more than the threat.
" He pushes off the wall and takes a step toward the table where I'm standing.
The movement is controlled, measured, and carries the weight of a man who uses physical space like vocabulary.
"You received a direct threat that named my home and my name, and you sat on it for hours so you could keep typing. "
"I logged it in the monitoring framework. Rivera had it within minutes. The automated feed gave her everything."
"Rivera." The name lands flat and hard. "Rivera, who is running a case file. Not the person who sleeps next to you."
He stops on the other side of the table.
The distance between us feels more calculated than any distance he's put between us before, and the restraint in it is worse than if he'd closed the gap, because I can see the tension in his arms, the way his weight shifts forward before he catches it, and that catch sits in the air between us with a weight I can feel against my sternum.
"You let the system tell me. Like I'm a line item on your threat matrix."
"The system worked exactly as designed."
"The system wasn't designed to replace me." The words land harder than he means them to, and I can see the moment he registers the weight of what he just said. He doesn't walk it back.
His hands are flat on the table now, the tendons across his knuckles drawn tight, and I know those hands.
I know what they feel like at the back of my neck and curled against my hip at three in the morning, and watching them grip a conference table with that kind of force pulls something tight behind my sternum that I can't reason with and can't dismiss.
"You're conflating two different roles."
"No. You are." His voice drops half a register, and the sound of it finds the low place behind my ribs where everything I've been trying not to feel about this man lives.
"You're treating the man who's trying to keep you alive and the man who woke up with you this morning like they're separate people who need separate information.
They're not. I'm one person, Nox, and you hid a threat from both of me. "
The precision of that cuts deeper than I'm prepared for.
He's right, and I'm not ready to say so, because saying so means admitting the thing underneath the decision, the thing I've been running from since the balcony, since the couch, since the first Tuesday he knocked on my doorframe and asked permission to enter a room he didn't need permission for.
"I didn't tell you because telling you changes the equation," I say, and my voice is steady because I've been keeping my voice steady through worse conversations than this.
"You hear a threat against me and you close ranks.
You pull tighter. You put yourself between me and the work, and the work is the only thing that stops this.
I can't build it from behind your shoulders. "
"You think I'd pull you off the work."
"I think you'd try to pull me out of the building."
"Maybe you should be out of the building.
" He straightens to his full height, and the overhead light cuts shadows along his jaw that make the anger look architectural.
"Maybe the woman who just received a direct death threat should be somewhere other than the building connected to the network the threat came through. "
"And maybe the EOD officer who renders live devices for a living should understand that the person closest to the bomb is the one best positioned to disarm it."
The silence that follows is thick and charged. His hands are still flat on the table, and his jaw is set at the angle I've watched him hold during bomb assessments, the controlled stillness that won't let the room see what the situation is costing him.
The vein at his temple is visible. I've kissed that spot. The memory is unhelpful and persistent and absolutely refuses to leave.
"I can't protect someone who won't let me in," he says, and the words are quiet and stripped of everything tactical.
"I didn't ask for protection." The response comes out harder than I mean it to. "I asked for time. You're the one who made it personal."
"I made it personal." He lets that sit. "You called me in the dead hours because a probe scared you. You said the word home about my loft. You fell asleep on my chest. But I made it personal."
The accuracy of every word lands like a hammer strike, and I have no defense against it because every fact he's citing is true and every fact he's citing is something I chose to do, and the distance between what I chose and what I'm willing to admit choosing is where this argument lives.
"This conversation is unproductive," I say, and I hear how clinical it sounds, and I hate it, and I say it anyway because clinical is the only register I have left when the alternative is honest.
Griff looks at me for a long count. Then he nods, once, and the nod is worse than any argument because it says he heard what I meant, not what I said, and what I meant is I'm not ready, and what he heard is you might not be enough, and both of those things are wrong but I don't have the words to explain why because the words would cost me something I'm not sure I can pay back.
He turns and walks out. The door closes behind him with a soft click that sounds louder than any slam.
The conference room is empty. The projector hums. My hands are steady on the table, and my chest is tight, and the counterstrike isn't close to finished, and the man who just walked out of this room is the reason I care whether Tidewater survives tomorrow, and I just let him leave thinking I don't need him.
I go back to the comm building. The code is waiting. The monitors are where I left them, cold and blue and patient, and Griff's texts have stopped coming.
He's on patrol. Rivera's security updates route through my monitoring framework, and his call sign appears in the movement logs as he works through a sweep pattern covering the eastern perimeter, the power hub, the waterfront infrastructure.
He's doing the job, walking the base with his sidearm and his radio, checking sightlines and junction boxes, hunting a threat while I sit in this chair and build the only defense Tidewater has.
We're on opposite sides of the same base, working opposite ends of the same problem, and the silence between us is the silence I chose.
The counterstrike climbs. Past seventy. Past eighty. The interception protocols pass simulation testing, the deployment sequences fire in the correct order, and the clean-restore modules bring each compromised system back online within the acceptable window.
It's working. It's elegant, and it's the best code I've ever written, and the person I want to tell is walking a perimeter on the other side of the water, not texting me.
At ninety-two percent, it hits a wall.
The three anomalous nodes I flagged this morning.
The ones with the latency I couldn't explain, the fractional delay in their handshake cycles that I tagged and deprioritized because the bulk of the architecture needed building first. Now I'm here, and the anomaly isn't a quirk. It's a design feature.
The final nodes in Garrick's malware use a handshake protocol that requires input from a hardware device, something physical plugged into the network at a specific junction point.
The latency I noticed was the gap between the digital trigger and the hardware response, the fraction of a second where the code reaches out for a signal that doesn't originate from a server. It originates from a device.
My code can intercept every digital component, but these last nodes won't fire without a physical signal I can't replicate or intercept because the source isn't software.
It's something wired into the infrastructure, sitting in a junction box or a maintenance corridor, waiting for the activation cascade to reach it.
The relay device we found during the initial sweep was one piece.
These are others, planted in locations the initial sweep didn't reach, and they're the linchpin of the entire architecture.
Without them, the malware's final cascade stalls.
With them, no amount of code I write will complete the interception.
I need someone who understands physical devices. Someone who can identify the hardware components, locate them in the network infrastructure, and either remove them or modify them so the counterstrike can bypass the handshake.
I stare at the screen. The cursor blinks. The bay is dark through the windows, and my phone sits on the desk with no new messages, and the last eight percent requires the one person I told I didn't need.