Page 7

The seams are there. They’re always there.

The client is listed as a compliance division within a federal economic monitoring body. The scope is described as assessing structural vulnerabilities in offshore financial routing architectures.

The clearance level is higher than anything I’ve worked on before, and the access permissions are layered in a way that suggests someone spent a lot of time deciding exactly what I should and shouldn’t be able to see.

None of this is unusual for government work. What’s unusual is the speed. From Ethan’s initial pitch to formal authorization, it was less than a week.

Government contracts don’t move this fast. They don’t move fast at anything.

I’m sitting at my desk, staring at the authorization documents on my screen, when Sienna appears in my doorway. She’s holding two coffees and wearing that look she gets when she knows I’m about to do something I haven’t fully thought through.

“You’re overthinking it,” she says, handing me one of the cups.

“I’m not overthinking. I’m thinking the appropriate amount.”

She settles into the chair across from my desk and kicks her feet up on the edge. “You’ve been staring at that screen since I left for the coffees.”

“It’s a big contract.”

She takes a sip of her coffee. “You said yourself the work sounds interesting. Complex systems, foreign infrastructure. It’s a challenge you don’t get from corporate audits.”

I did say that. I said it last night when I couldn’t sleep, talking to her on the phone about Ethan’s pitch, turning the details over in my head like a puzzle I couldn’t put down. The complexity of it appealed to me. The idea of working on something that actually mattered, instead of just patching holes in another corporation’s security blanket.

Except something about it sits wrong. The speed. The specificity. The way Ethan seemed to know exactly what I could do before I showed him.

“The permissions are strange,” I say. “They’re giving me access to systems I shouldn’t need for a standard audit. There are layers I can’t see through—restrictions built into the architecture that don’t make sense for a compliance check.”

“Maybe they’re protecting classified information.”

“Maybe.” I turn back to the screen. “Or maybe they’re using the audit as cover for something else.”

Sienna watches me for a moment. She’s good at reading people—it’s what makes her valuable to the company—but she’s even better at reading me.

“You want to do this,” she says. It’s not a question.

“I want to understand this.”

“Same thing.” She stands, straightening her blouse. “Look, you’re the smartest person I know when it comes to systems. If something feels off, you’ll figure it out. Don’t talk yourself out of something interesting just because you can’t see all the pieces yet.”

She leans over and squeezes my shoulder before walking out. Her heels click against the floor, then fade.

I take a breath and pull up the full brief.

The documentation runs to forty-seven pages. I read every one, highlighting sections that seem inconsistent or vague. The scope keeps expanding the deeper I go—what starts as a routing assessment branches into transaction analysis, then into account verification, then into something called “pattern identification for anomalous financial behavior.” Each layer adds complexity without adding clarity.

By the time I finish, it’s past noon. I haven’t moved from my desk.

The contract is legitimate, as far as I can tell. The government credentials check out, the oversight structure is real, and the funding trail leads back to an actual congressional appropriation. Only the architecture of the job itself feels less like an audit and more like infiltration.

Which is, I suppose, what I do.

I just prefer to know what I’m infiltrating before I start.

My phone buzzes. A message from Ethan: Preliminary access credentials have been transmitted to your secure partition. Please confirm receipt.

I pull up my secure workspace and find the credentials waiting. It’s standard government encryption, two-factor authentication, the works. I enter the system environment and start the initialization process.

The interface that opens is different from what I expected. Most government systems look like they were designed in 2005 and never updated—clunky, text-heavy, functional but ugly. This one is streamlined, clearly built by someone who understands how people actually navigate complex data structures.