Chapter 5 #2
"Narrow enough that I wouldn't be running any more searches from her workstation for a while.
The flag is automated, not manual. Which means it might sit in a queue until someone gets to it, or it might route straight to whoever built the trigger.
If it's the second option, the clock is already running. "
"Can you tell who built the trigger?"
"Working on it. I can tell you it wasn't installed as part of the standard security package. It was added separately, which means somebody decided those specific engagement files needed an extra set of eyes. That's not IT protocol. That's personal."
I end the call. The loft holds its silence, indifferent and wide, and the silence is the wrong kind of empty today.
Arthur's system caught her clean. Not almost. Not a near miss. The flag exists and the queries are logged. Somewhere in the firm's database, a record sits with Meagan's workstation ID attached to searches she thought were invisible.
I told her at the bar that her work was being repurposed. I didn't tell her the building she works in is wired to catch anyone who notices.
This is Arthur's second win, and Meagan doesn't know it yet.
I text her.
Wicker Park. Tonight. The place on Division with the green awning. 8 PM.
The reply comes fast.
You're making a habit of this.
Of what?
Summoning me to bars I've never heard of.
You keep showing up.
I keep having reasons to do so.
I read her last message twice.
The bar on Division is smaller than the Logan Square place. Darker. A room where the bartender knows not to remember faces and the lighting exists to make conversation possible without making recognition easy. I'm here first. Corner booth, back to the wall, sight line to the door.
She walks in on time, and the room does what every room does when Meagan Keating enters it: it rearranges itself around her without her permission.
She's in a coat I haven't seen before, dark and fitted. When she pulls it off and drapes it over the booth, the blouse underneath is silk, the color of smoke. I lose about three seconds of situational awareness to the line of her collarbone before I pull myself back to operational.
She slides into the booth across from me. The table is smaller than the one in Logan Square. Our knees touch under it, and neither of us moves.
"You look like a man with bad news," she says.
"Your searches got flagged."
The sentence lands. Her face gives nothing away to anyone who isn't watching her as closely as I am. Her jaw stays level. Her eyes stay steady. She goes still in a way that's more telling than any reaction would be.
The floor just shifted underneath her career, and she's already calculating how to keep standing. Her breath catches once, a half-second hitch she buries before it reaches her face.
"Which ones."
"All of them. Every query that touched the secondary operation. The flag is automated, built into the engagement files as a separate trigger. It wasn't part of the standard security package. Someone added it."
Her eyes move. Not to me. Somewhere internal, running the implication to its end point.
"Arthur."
"Maybe. Or someone Arthur trusts enough to hand the keys to.
The trigger was designed to catch exactly the search pattern you were running.
Structured queries, cross-referenced against multiple engagements, routed through standard workflow to avoid detection.
" I hold her stare. "You were good. The system was better. "
She processes. I can see it happening behind her eyes, the rapid reorganization of everything she thought she knew about her own operational security. The calculations are moving faster than the conversation.
"How much time do I have?"
"Depends on whether the flag routes to a queue or a person. If it's a queue, days. If it's a person, the clock is already running."
"Then I need to know who the person is."
I lean back. She's thinking about the system. I'm thinking about the predator.
"You're asking the wrong question, Keating."
Her chin lifts. The defiance is automatic, instinctive, the response of someone who doesn't accept being told she's wrong about anything. "Enlighten me."
"You're trying to outrun a security system. You can't. It already has your queries. The data is logged. No amount of rerouting changes what's already been recorded." I lean forward. "Stop thinking about the system. Start thinking about the person who built the trigger."
"That's what I just said. I need to know who the person is."
"You need to know why they built it. Not what the trigger does.
Why someone decided those specific engagement files needed monitoring.
The trigger tells you what Arthur is protecting.
The person who installed it tells you where Arthur's trust ends and his paranoia begins.
That's the seam you're looking for. Not in the data. In the org chart."
She's quiet for a beat. The bar hums around us, low conversation and glass against wood, and the sound covers the silence.
Her eyes are on mine, and the quality of her attention has shifted from defensive to a look I recognize from Pilsen: the one she gets when a piece of information rearranges the board.
"You don't think in systems," she says.