Skip to content

The Blackout Directive

Chapter 5

Chapter 5

Dead Man's Hand

Marcus Chen · 5.5K words · ~22 min read

Chapter 5: "Dead Man's Hand"

I slept for five hours and woke up with a decision already made.

Confront Lin about the dead man's switch. Not because I'd stopped trusting her—or rather, not only because of that—but because if there was a failsafe that would trigger a nationwide grid attack when we destroyed the Denver node, I needed to know about it before we were elbow-deep in server racks with thermite charges armed. Call me old-fashioned, but I prefer to know the full scope of the apocalypse before I start preventing it.

The dream I'd been having—something about running through a dark server room with no floor, each step a gamble on solid ground—faded like smoke as I sat up on the narrow safe house bed. My neck ached from the cheap pillow. My mouth tasted like copper and regret. The clock on my phone said 9:47 AM. Five hours of sleep, give or take, which was more than I'd expected to get given the circumstances. But the decision had crystallized during those hours, forming itself in the dark spaces between nightmares, and now it sat in my chest with the weight of a stone.

I found her in the basement, exactly where I'd left her five hours ago. She'd changed clothes—there was a stack of generic t-shirts and jeans in one of the upstairs closets, courtesy of J—and had three monitors active in front of her. The coffee cup I'd brought her was empty, a dark ring staining the ceramic interior like a fossil record of caffeine consumption. A second cup sat half-full beside her keyboard, steam still rising in lazy spirals.

The basement smelled of dust and electronics and that particular ozone tang that comes from too many machines running in too small a space. Fluorescent lights hummed overhead, casting everything in that greenish institutional pallor that makes even the healthiest person look like they're recovering from a week-long illness. Lin sat at the center of it all, her face illuminated by the blue glow of the monitors, her fingers moving across the keyboard with the kind of fluid precision that comes from decades of practice.

She looked up when I came down the stairs. The stairs creaked under my weight—old wood, poorly maintained, the kind of sound that carries in ways you don't want it to when you're trying to be quiet. "You're awake. Good. I've been mapping the Pinnacle Center security systems remotely—there's more than I expected. They've added personnel since I left."

Her voice was steady, professional, the same tone she'd used when discussing encryption protocols and network topologies. But there was something underneath it, a tightness that hadn't been there before. Maybe she already knew what I was going to say. Maybe she'd been expecting this conversation since the moment I'd mentioned Nightfall's message.

"Lin," I said. I sat down on the bottom step. Directly in her line of sight. The wood was cold through my jeans, and I could feel the vibration of the basement's HVAC system through the soles of my shoes. "We need to talk about the dead man's switch."

The typing stopped. Her hands hovered over the keyboard for exactly one second—long enough for me to see it, too short to call a hesitation. Then she turned her chair to face me. The wheels squeaked against the concrete floor, a small sound that seemed enormous in the sudden silence.

"How do you know about that?"

Not a denial. Not confusion. Just a question about sourcing. Which told me everything I needed to know.

"Does it matter how I know? What matters is that you didn't tell me. We're driving across the country to destroy a C2 node, and you didn't mention that destroying it might trigger the exact attack we're trying to prevent."

The words came out harder than I'd intended. I could feel the anger sitting just beneath my skin, a low-grade burn that had been smoldering since I'd read Nightfall's message. I'd trusted her. I'd thrown my lot in with hers based on nothing more than a shared enemy and a desperate hope. And she'd kept this from me—this critical piece of information that could mean the difference between success and catastrophe.

Lin's expression was unreadable. Her face had gone still, the way it does when she's processing something complex. She studied me for a long moment—assessing, calculating, deciding something. I held her gaze and didn't flinch because I'd learned a long time ago that the person who looks away first is the person who loses the negotiation.

"You're right," she said. "I should have told you."

The admission was so direct, so devoid of defensiveness, that it caught me off guard. I'd been prepared for excuses, for justifications, for the kind of half-truths that people tell themselves to make their betrayals feel smaller. Instead, she just... agreed.

"So tell me now."

She pushed back from the desk. The chair rolled against the concrete floor, and she stood up, her movements deliberate and controlled. Paced three steps in the small basement space—the first time I'd ever seen her move without purpose, without a specific destination in mind. Her footsteps echoed in the quiet room, and I watched her hands clench and unclench at her sides.

"When I designed the seven-node architecture, Meridian's leadership insisted on a failsafe." She stopped pacing and turned to face me. Her eyes were dark, focused, the eyes of someone who was reliving a memory she'd rather forget. "They called it 'Directive Zero.' If any node goes offline without a proper deauthorization sequence—meaning without the correct cryptographic handshake from the central command system—the node sends a final signal to every sleeper payload deployed across its regional grid."

"And the payloads activate."

"The payloads activate." She said it flatly, as if she were reading from a technical manual rather than describing a catastrophe. "Not a full grid attack—it's regional only. But for the Denver node, 'regional' means Colorado, Wyoming, Utah, Nebraska, Kansas, and parts of New Mexico. Roughly eight million people lose power. Hospitals. Emergency services. Military installations."

I rubbed my temples. The headache that had been threatening since I woke up was now a full-blown reality, a dull throb behind my eyes that matched the rhythm of my pulse. "So if we just walk in and thermite the hardware..."

"We trigger a regional blackout. Yes." She crossed her arms, hugging herself in a gesture that might have been defensive or might have been cold. The basement was cool, but I didn't think that was the reason. "That's why the kill switch was designed to look like a system fault—it included the proper deauthorization sequence as part of the shutdown. The nodes that responded to our command went dark cleanly. No Directive Zero. No sleeper activation."

"But Denver didn't respond."

"Denver didn't respond." She uncrossed her arms and walked back to the desk, leaning against it with her palms flat on the surface. "Which means either the kill switch command never reached it, or it was intercepted and blocked. Either way, the Denver node is still active, still monitoring its own status, and still armed with Directive Zero."

"And you were planning to deal with this how?"

She turned back to me. Her face was steady. Professional. But I could see the cost of this conversation in the tension around her eyes, in the slight tightening of her jaw, in the way she held herself like she was bracing for a blow. "I have the deauthorization codes. They're in my head—not written anywhere, not stored digitally, nowhere Meridian can find and change them. When we access the node, I execute the deauthorization sequence first. Then we destroy the hardware. Clean shutdown, no Directive Zero, no regional blackout."

"And if something goes wrong? If they've changed the codes since you left?"

Silence. One beat. Two. The fluorescent lights hummed. Somewhere in the house above us, the refrigerator compressor kicked on with a low rumble.

"If they've changed the codes," she said carefully, "then we have a problem."

"Define 'problem.'"

"If I can't deauthorize the node through normal channels, I'd need to access the central command system directly—the master authentication server that manages all seven nodes. That server is also in the Denver facility. Different room. Different floor. Different security profile."

"So our four-minute operation potentially becomes a multi-room, multi-floor infiltration of a hardened paramilitary facility while under a kill-on-sight order." I leaned back against the stairs, feeling the edge of the wooden step dig into my spine. The words tasted bitter in my mouth. "Lin. Why didn't you tell me this from the start?"

She met my eyes. No excuses. No deflection. Her gaze was steady, clear, the gaze of someone who had made a calculated decision and was prepared to face the consequences. "Because I was afraid you'd walk away. And I needed you."

The honesty of it—raw, simple, undecorated—took the anger out of me. Not completely. But enough. Because I understood. I understood being so committed to a course of action, so desperate for it to work, that you trimmed the ugly parts from the briefing and hoped the field wouldn't be as bad as you feared.

I'd done the same thing a hundred times. Every pen test report I'd ever submitted understated the severity of at least one finding, because telling the client the truth—that their infrastructure was Swiss cheese and they were one bored teenager away from catastrophe—would make them shut down and stop listening. You give them the bad news in pieces, let them absorb it gradually, because the full picture all at once is too much for anyone to handle.

"I wouldn't have walked away," I said.

"You don't know that." Her voice was quiet, but there was no self-pity in it. Just a statement of fact, as if she were describing the properties of a cryptographic algorithm.

"Yes I do. Because I'm here. Because I'm still here after finding out. Because—" I sighed, the breath escaping me in a long, tired exhale. "Because I'm the idiot who goes up to the thirty-seventh floor when every rational instinct says don't."

A long breath left her. Not relief exactly—more like the easing of a weight she'd been carrying alone. Her shoulders dropped a fraction of an inch, and some of the tension went out of her posture. "I'm sorry. For not telling you. It won't happen again."

"No more secrets."

"No more operational secrets," she amended. "I'm still entitled to personal privacy."

"Fair. Personal privacy is fine. Just—if there's something that might get us killed, or might get eight million people killed, I'd like a heads-up before we're in the building."

"Agreed."

"Good." I stood up, brushing off my jeans. The fabric was damp from the cold concrete floor. "Now walk me through the contingency plan. What if the codes have been changed?"

She sat back down at the desk, and for the next hour, we mapped the expanded operation. The original plan—basement entry, camera loop, vent shaft to server room, four-minute destruction—remained the primary. But now we had a contingency layer: if Lin's deauthorization codes failed, I would hold position in the server room while she moved to the fourth floor to access the master authentication server. Additional time: eight to twelve minutes. Additional risk: significant.

"The master auth server is in a room called the Nexus," Lin explained, pulling up building schematics on the monitor. The image flickered as she zoomed in, highlighting a section of the fourth floor. "Fourth floor, east wing. Biometric access—same mantrap system as the fifth floor server room. I'm in the system for both, so access isn't the issue. The issue is the corridor between them. There's a security checkpoint at the fourth-floor elevator bank—an actual manned desk with an armed guard. During normal operations it's one person. Under alert conditions, it could be three or four."

"And if we've triggered the fire alarm by then..."

"The fire alarm complicates things. Guards may abandon posts during evacuation, or they may lock down and shelter in place depending on the alert level. Meridian's protocols for fire events..." She paused, frowning at the screen. "I'm not sure they haven't changed since I left."

"So we're operating with partial intelligence on their current security procedures."

"Yes." She turned to face me, her expression grim. "Which is why we need the surveillance day. Tomorrow, I watch the building. Movement patterns, shift changes, response times. We identify as many variables as possible before we go in."

I nodded. It was a plan. Not a great plan—more of an informed improvisation framework—but it was more than I'd had twelve hours ago. And the key elements were sound: Lin's access credentials, the physical entry through the HVAC shaft, the thermite for hardware destruction. The deauthorization issue was a complication, not a dealbreaker.

Unless the codes had been changed. Then it was a dealbreaker.

"One more question," I said. "Nightfall. Whoever's been sending messages. They knew about Directive Zero. How? If this is deeply compartmented information within Meridian, how does an external party know about it?"

Lin frowned. She'd clearly been thinking about this too. Her fingers drummed against the desk as she considered the question. "Two possibilities. Either Nightfall has a source inside Meridian—someone with high-level access feeding them operational details. Or Nightfall is Meridian—a faction within the organization playing a different game."

"A faction?"

"Organizations like this aren't monolithic." She leaned back in her chair, and I could see her mind working, tracing connections and possibilities. "There are always internal politics. People with different visions, different endgames. It's possible that some element within Meridian wants the Denver operation to fail—wants us to succeed—for reasons that serve their own agenda."

"Enemy of my enemy," I said.

"Exactly. Which doesn't make them our friend. It makes them an actor with aligned short-term interests and unknown long-term goals." She pulled up the chat log from Nightfall—the encrypted messages going back months. The text scrolled across the screen, a history of cryptic guidance and timely warnings. "Look at the pattern. Every piece of information Nightfall has given me has been accurate. But every piece has also moved me toward a specific action. They told me the timeline was accelerating—which pushed me to use the kill switch earlier. They told me about the field team on I-70—which pushed us to alternate routes. They told you about Directive Zero—which pushed you to confront me."

"Pushing us. Steering us."

"Like we're pieces on a board. Moving toward a position someone else has planned."

That sat between us for a moment. Uncomfortable. Heavy. I could feel the weight of it pressing down on me, the sense that we were being manipulated by forces we didn't understand. It was the same feeling I'd had on the thirty-seventh floor, the sense that I was dancing to someone else's music.

"Does it change what we're doing?" I asked.

"No." She said it firmly, with conviction. "Because regardless of who Nightfall is or what they want, the Denver node is a real threat. Directive Zero is a real safeguard that needs to be properly disabled. And Meridian is really trying to kill us. Whatever game Nightfall is playing, our immediate objectives are the same."

"Okay. Then we proceed as planned. But with open eyes."

"Open eyes," she agreed.

The rest of that day was a masterclass in operational preparation. I'd spent years breaking into networks—finding vulnerabilities, exploiting weak points, documenting paths of least resistance. This was the same thing, but physical. And the consequences of failure weren't a bad pen test report. They were a body bag.

We studied the Pinnacle Center from every angle. Satellite imagery from three different providers, each showing the building from a slightly different perspective. The architectural plans Marcus had obtained, yellowed and creased, with handwritten annotations in the margins. Public records on the building's fire suppression and HVAC systems, pulled from city permits and inspection reports. Social media posts from people who worked in the building—not Ashford Analytics employees, but the other tenants on floors one through three. Photos from the lobby, posted by bored receptionists. Check-in locations that gave us data about guard positions and camera angles.

Lin had a talent for spatial analysis that bordered on supernatural. She looked at a floor plan and saw movement corridors, sight lines, dead zones. She calculated distances and times with the confidence of someone who'd done this kind of planning before—and not just theoretically. Her hand moved across the paper with quick, precise strokes, marking routes and fallback positions.

"How many operations did you run for Meridian?" I asked, watching her sketch timing diagrams on a notepad. Her handwriting was small and neat, the letters formed with mechanical precision. "The real kind. Physical infiltrations."

"Three. Support role—I handled network and communications while the operators did the physical work. But I trained with them." She didn't look up from her diagrams, her pen continuing its steady progress across the page. "Four months of their internal course before they assigned me to the development team. Firearms. Close quarters combat. Surveillance. Counter-surveillance. Lock manipulation. They invest heavily in their people."

"So when you said you could shoot..."

"I qualified expert on every platform they trained me on. Handgun, rifle, shotgun. In simulation and live fire." Now she did look up, her eyes meeting mine with a directness that made me feel like I was being evaluated. "I told you—they're not amateurs. And neither am I."

I thought about my twice-weekly jiu-jitsu classes and my three-year-old range qualification and felt profoundly inadequate. But I also thought about the server room on the thirty-seventh floor—about how I'd gotten in, gotten the data, and gotten out while being pursued by trained operators. I wasn't a soldier. But I was fast, quiet, and good at improvising.

I'd have to be enough.

Late afternoon, Lin announced that she was going to do a drive-by of the Pinnacle Center. Basic reconnaissance—approach routes, parking, visible security, general activity patterns. She'd go alone, in the Civic, wearing a disguise that amounted to different clothes and a baseball cap. The cap was dark blue, nondescript, the kind of thing a thousand people in Denver wore every day.

"You stay here," she said, pulling on a jacket. The fabric rustled as she adjusted the collar. "Monitor the encrypted channels. If you see anything that suggests they know we're in the area, text me on the secure phone immediately."

"And if I see something really bad?"

"Define really bad."

"Like, 'assault team heading to this address' bad."

"Then you take the go-bag, leave through the back fence, and head for the university campus. Crowds provide cover. I'll find you." She handed me one of the encrypted radios from Marcus. "Channel three. Emergency only."

She left. The garage door opened with a mechanical groan, and I heard the Civic's engine turn over, a low rumble that faded into the quiet suburban afternoon. The door closed again, and the house settled into silence.

I was alone in a safe house in Boulder, Colorado, with an encrypted laptop, two duffel bags of spy equipment, and the growing certainty that I was in over my head.

I went to the basement and took Lin's place at the monitoring station. The chair was still warm from her body heat. The encrypted channels were quiet—Meridian's internal comms showed routine traffic, nothing that mentioned us or Denver specifically. I ran searches on our names, on the Pinnacle Center, on anything that might indicate they knew we were close. Nothing.

Which either meant we were safe, or meant they'd gone to communications blackout—the thing you do when you don't want the enemy monitoring your channels because you already know they can.

I was overthinking this. I was definitely overthinking this.

To distract myself, I did what I always do when I'm anxious—I worked on a technical problem. Specifically, I started analyzing the partial packet capture I'd pulled from the thirty-seventh floor servers before everything went sideways. The data was on my laptop's local drive, untouched since yesterday.

I opened it in Wireshark and started picking through the metadata. The screen filled with lines of hexadecimal and timestamps, a language I understood better than my own native tongue. The encrypted payloads were beyond my ability to crack without the keys, but the routing information told a story. I mapped the connections—source IPs, destination IPs, timestamps, packet sizes. Patterns emerged.

The C2 node had been communicating with its targets on a schedule—check-ins every ninety seconds, with larger data transfers every fifteen minutes. The fifteen-minute transfers were probably the payload updates—the actual attack code being pushed to sleeper agents embedded in SCADA systems. But there was something else. A second communication pattern, overlaid on the first. Smaller packets. Different destination. Sending data out, not just to the grid targets but to another IP entirely.

I traced the destination. The IP resolved to a server in Iceland, hosted by a privacy-focused data center that catered to customers who didn't want to be found. The kind of place that accepted Bitcoin and didn't ask questions. The kind of place where you could hide anything, as long as you paid the bill on time.

Someone was exfiltrating data from Meridian's C2 network. Copying operational information—attack schedules, target lists, maybe even the deauthorization codes—and sending it to a third party.

Nightfall.

It had to be. The mysterious third player who'd been feeding Lin intelligence for six months. They weren't getting their information from a human source inside Meridian—they'd tapped into the C2 network itself. A digital parasite, riding Meridian's own infrastructure, copying everything it saw.

Which meant Nightfall had access to operational details that even most Meridian personnel didn't. Including Directive Zero. Including, potentially, the current deauthorization codes.

I sat back in my chair and stared at the screen. The cursor blinked at me, patient and indifferent. This changed things. If Nightfall had the current codes—codes that might have been changed since Lin left—then Nightfall was potentially the answer to our biggest problem. If we could establish contact, if we could get them to share those codes, the Denver operation became dramatically simpler.

But Nightfall had also said don't trust her. Nightfall was playing a game I didn't understand. And reaching out to them meant exposing ourselves to whatever agenda they were running.

Risk versus reward. The eternal equation.

I typed a message on the clean phone. The screen was bright in the dim basement, the keyboard clicking softly under my fingers. Addressed it to the number that had sent the Nightfall messages. Three words of my own.

We need the codes.

I stared at it for a long time. My thumb hovered over the send button. Once I pressed it, there was no going back. I would be committing us to a course of action based on the word of a stranger who had their own reasons for helping us.

Then I hit send.

The response came in under a minute. Fast. Too fast. Like they'd been waiting for me to reach out. The phone buzzed in my hand, and I read the message with a mixture of relief and dread.

I know. The codes are: SIGMA-7-VIOLET-2891-GAMMA. Valid for 48 hours from last rotation. Current rotation timestamp: 06:00 UTC today.

I checked the time on my laptop. It was 4:47 PM local—10:47 PM UTC. The codes had been rotated this morning. If Nightfall was telling the truth, they'd be valid until tomorrow morning. Our operation was planned for tomorrow night.

The codes would have expired by then.

Another message followed, as if Nightfall had anticipated my calculation: Rotation happens every 24 hours at 06:00 UTC. You need to be inside before then. Move your timeline up.

Move our timeline up. Go tonight instead of tomorrow. Skip the surveillance day. Walk into the Pinnacle Center with zero on-the-ground reconnaissance, relying entirely on outdated building plans and the word of a shadowy entity who'd also told me not to trust my only ally.

Or wait for tomorrow night, and hope that Lin's old codes still work. Which they probably didn't, because Lin hadn't been connected to Meridian's systems in months and code rotation was standard security practice.

I heard the garage door open upstairs. The familiar mechanical groan, followed by the sound of the Civic's engine idling for a moment before cutting out. A car door opened and closed. Footsteps in the garage.

Lin was back.

I had maybe thirty seconds to make a decision. Tell her everything—Nightfall's messages, the codes, the timeline pressure. Or keep some of it close. Play the same game she'd played with Directive Zero, releasing information strategically.

No. No more secrets. She'd promised me no more operational secrets, and I'd hold myself to the same standard.

I met her at the top of the basement stairs. She was pulling off her jacket, her face flushed from the cool evening air. The baseball cap was in her hand, and her hair was slightly mussed.

"Lin. We have a situation."

She read it in my face before I said anything else. Her hand paused mid-motion, the jacket hanging half-off her shoulders. She set down her keys on the kitchen counter—calmly, deliberately, the metal clinking against the laminate—and said, "Tell me."

I told her everything. The packet analysis. The Iceland server. Nightfall's digital tap on Meridian's C2 network. The codes. The rotation timeline. I watched her face as I spoke, looking for any sign of deception, any flicker of surprise that might tell me she'd known more than she'd let on.

"SIGMA-7-VIOLET-2891-GAMMA," she repeated. Her face was a mask, unreadable. "Those aren't the codes I have."

"Then yours have been changed."

"Or those are fake." She crossed her arms, her eyes distant, calculating. "Designed to make us feel confident walking into a trap. If we enter those codes and they're wrong—if it's not the deauthorization sequence but something else—it could trigger Directive Zero immediately. Or it could alert the facility that someone is attempting unauthorized access."

"Or they could be real, and they're the only thing that makes tomorrow night's operation viable."

We stood there, in the kitchen of a safe house in Boulder, separated by two feet of linoleum and an impossible decision. The refrigerator hummed. The clock on the microwave ticked over to 4:48 PM.

"How do we verify?" I asked.

"We can't." Her voice was flat, resigned. "Not without accessing the system, which is exactly what we're trying to plan for." She crossed her arms, hugging herself again. Thinking. Processing. I could almost see the decision trees branching behind her eyes, each path leading to a different outcome. "The rotation timestamp. If Nightfall has legitimate access to the system, they'd know the exact rotation schedule. Is 06:00 UTC consistent with what I know?"

"You tell me."

"When I was inside, rotation was daily at midnight UTC. But that was ten months ago. They could have changed it." She closed her eyes, and I could see her searching her memory, trying to recall details that might have seemed insignificant at the time. "Six AM UTC. That's midnight Eastern. It's... plausible. Meridian's operations center keeps Eastern time."

"So it could be real."

"It could be real. Or it could be perfectly crafted disinformation designed by someone who knows enough about the system to fake the details." She opened her eyes, and there was something like exhaustion in them. "We're back to the fundamental question: who is Nightfall, and what do they want?"

I walked to the kitchen counter and poured coffee from the pot I'd made hours ago. The liquid was dark and cold, but I drank it anyway, the bitterness cutting through the fog in my head. "Let me propose something. We go tonight. We use your codes first—the ones from when you were inside. If they work, great. If they don't, we try Nightfall's codes as backup. If neither works, we go to the master auth server as planned."

"Tonight," Lin said flatly. "No surveillance. No reconnaissance beyond what I saw on the drive-by."

"What did you see on the drive-by?"

She pulled out her phone and showed me photos—taken from the car, discreet angles, the kind of shots that wouldn't draw attention even if someone noticed her taking them. The Pinnacle Center was a modern glass-and-steel building, five stories, set in a corporate park with manicured landscaping and a parking structure. The front entrance had a security desk visible through glass doors, a uniformed guard sitting behind it. Parking garage entrance on the east side, with a gate arm and a card reader. Loading dock on the north, a concrete ramp leading down to a metal roll-up door.

"Two visible guards at the front desk," she said, swiping through the photos. "Camera coverage on all exterior approaches—I counted fourteen visible units. Vehicle gate on the parking structure requires a proximity card. Loading dock was closed and appeared unmanned." She paused on one photo, a shot of the building's north side. "I circled the block twice. No obvious surveillance on the perimeter. No unusual vehicle presence. If they're on high alert, they're keeping it internal."

"Or they're very good at hiding it."

"Or that." She set the phone down on the counter. "But here's what the drive-by confirmed: the building hasn't changed structurally from the plans we have. HVAC equipment on the roof matches the schematic. The basement access point—a service door on the north side near the loading dock—is still where it should be."

I processed the photos, committing the details to memory. The building looked... normal. Corporate. The kind of place you'd walk past without a second thought. The kind of place where people went to work every day, drank coffee from the break room, complained about their bosses. Which was, of course, exactly the point.

"If we go tonight," I said, "what's our timeline?"

Lin checked her watch. "It's five PM now. Full dark by eight-thirty. Building staff—the legitimate employees on floors one through three—clear out between six and seven. Ashford Analytics runs twenty-four-seven operations, but the overnight shift is skeleton crew. Fewest personnel between midnight and four AM."

"So we go at midnight."

"We go at midnight." She nodded, the decision settling into place. "That gives us six hours from the code rotation at midnight Eastern. If the codes are valid for twenty-four hours from 06:00 UTC today, they expire at 06:00 UTC tomorrow—which is midnight Mountain time. We need to be in the server room and executing the deauthorization before then."

"That's our zero hour. Midnight tonight. Midnight exactly."

Lin nodded slowly. I could see her making the calculation—risk of going in blind tonight versus risk of going tomorrow with expired codes and a longer window for Meridian to find us. Neither option was good. But one was slightly less terrible than the other.

"We go tonight," she said. Decision made. Voice steady. "Start prepping the equipment. I'll finalize the operational plan."

I went to the duffel bags in the garage. The space was dim, lit only by a single bare bulb, and smelled of gasoline and old cardboard. I started laying out equipment on the workbench, the metal surface cold under my hands. Encrypted radios, their cases scuffed from use. Lock picks in a leather roll, each pick nested in its own slot. The plasma cutter, heavy and awkward, its battery pack still showing a full charge. Thermite charges with their radio detonator, wrapped in protective foam. The Glocks—I checked each one, loaded magazines, racked a round into each chamber and then cleared them again. Muscle memory from training I'd thought I'd never use.

My hands were steady. That surprised me. Maybe it was the clarity of having a timeline—midnight, six hours away, a countdown that was ticking whether I was ready or not. Or maybe it was something simpler: I'd made my decision. I was committed. And commitment, even to something terrifying, has a calming effect that uncertainty never does.

Six hours until we walked into the lion's den.

Six hours until we found out if Nightfall's codes were salvation or a trap.

Six hours until Ethan Zhao, former NSA analyst, freelance security consultant, and owner of one judgmental cat, either saved eight million people from darkness or became another ghost in the machine.

I loaded my bag, checked my equipment twice, and tried not to think about the fact that this might be the last quiet evening of my life.

Outside, the Colorado sun was setting behind the Rockies, painting the sky in shades of blood and fire. The light slanted through the garage window, casting long shadows across the concrete floor. Somewhere in the distance, a dog barked. A car drove past on the street. Normal sounds. Ordinary sounds. The sounds of a world that didn't know what was coming.

Seemed appropriate.

End of Chapter 5

Enjoying The Blackout Directive?

Your vote helps other readers discover this story

Vote on Top Web Fiction

Comments

Comments

Sign in to leave a comment