Page 4 of Operation: Defiance

There’s a timestamp mismatch in the metadata. Three seconds. Too small to matter on its own. Or for anyone else to notice.

I correct it, add a brief explanation the program requires—even if no one will ever read it—and save my changes. The system recalculates, spinning for longer than it should, and I turn my gaze to my office window.

The mountains on the other side of Puget Sound have a fresh dusting of snow that wasn’t there this morning. I may not have wanted a desk job, but the view helps.

The Global Security Directorate runs ops all over the world. But Cyber and Systems both operate out of GSD’s main hub in Seattle. Cyber hunts live threats in real time. Systems audits the aftermath–tracking decisions, flagging inconsistencies, and making sure nothing in the official record contradicts what actually happened.

I don’t miss the field. Much.

I miss being trusted without having to explain why I’m right.

Patterns make sense to me—unlike so many other things. They’re logical. Consistent. They either hold or they don’t.

I rub my eyes, then turn back to the laptop.

The next file is clean. The one after that, too. I settle into the rhythm of review, fingers moving without conscious thought, my brain already half a step ahead.

Until another anomaly flickers on the screen.

A contractor ID I recognize scrolls by for the second time today. I stop and look back at my last few files.

The same ID appears days apart, attached to unrelated ops. That’s not unusual. A good contractor can be reused time and time again.

What’s strange is the timing. The first assignment hadn’t been closed out when the second one opened.

That should have triggered a review. It didn’t.

Systems generate noise—small inconsistencies that mean nothing on their own. Noise isn’t unusual. It only matters when it repeats. So I don’t stop or chase down why it happened. I make a mental note that it did, and move on.

My shoulder twinges as I reach for my mouse, and my thumb moves to the edge of the ring on my index finger, tracing the line of tiny diamonds set into the band until my pulse settles.

A shadow crosses the frosted glass wall of my office.Tessa, the junior analyst I’ve been mentoring for the past few months, peeks her head in, then drops into my guest chair with a dramatic sigh. “You look like you’re about to argue with a spreadsheet,” she says.

“I already won.” I offer her a small smile. “The spreadsheet just doesn’t know it yet.”

Tessa chuckles. She’s younger than me by a decade, maybe more. Still green, but also smart and observant. The kind of analyst who’ll be very good once she learns which questions belong on the record—and which don’t.

No one teaches you how much damage can come from caring about the wrong thing. You figure that out by watching who stops showing up to briefings.

“What are you working on?” she asks.

“Clean-up,” I say. “End-of-week triage.”

She makes a face. “I hate triage.”

“That’s because you still think everything deserves saving.”

Her expression shifts to mock outrage, then laughter. “Fair.”

She swivels in the chair, twirling a pen in her hands. “Can I ask you something?”

“You just did.”

She gapes at me for a beat. “You’re always so literal.”

“Occupational hazard,” I say, softening my expression into something socially…acceptable. “Go on. Ask.”

“When you see something that’s…off, but not incorrect, how long do you wait before you care?”