Chapter 11

KINCAID

'Lock the deadbolt.' Those were the last words I gave her, standing in her doorway with my back to the kitchen where she had just taken me apart.

The command came out the way my commands always come out: without consultation.

The instinct to manage her safety outran the fact that she had just revoked my right to manage anything about her.

The loft is the same temperature it was when I left it. I drop my keys on the island and stand in the quiet. The quiet carries a weight it did not carry this morning when she was in the passenger seat of my truck with coffee from my kitchen in her hand.

She said: 'I was more useful not knowing. There's a difference.'

The muscle along my jaw tightens. There is no one here to read it.

I told her I kept her blind for her safety. The truth is uglier. I kept her blind because knowing would have ended this, and I was not ready for this to end. The selfishness of that is the thing I can’t justify, and the redirect fires before the thought can finish landing.

A feeling gets too close. I turn it into a task.

Priest's message from earlier sits on my phone.

Arthur has restructured the internal logging on the client archive again, layered into a routine compliance update.

Query-level tracking with timestamp resolution down to the second, plus IP tagging on workstations that touch the expanded files.

The net is fine enough now to trace individual hypotheses from Meagan's search behavior.

She does not know this. She works inside a system that is actively mapping her research.

I don’t sleep. The city light crosses the ceiling as it did while she was lying against me, and the resemblance does not stop until the gray light replaces it.

The couch holds the shape of where she sat with her feet tucked under her.

I don’t sit on it. By morning I have a list of things I need to confirm.

The Halcyon engagement gives me cover at the firm, and the cover feels thinner than it did last week.

I pull up the Connors routing files I flagged during the Indianapolis trip, the documentation that maps the intermediary vehicles across the collapse sequence.

The files should be in the archive under the engagement code I used to access them.

The code returns nothing. I run it again.

Same result. The files have been moved to a restricted partition, logged under a data management operation authorized at Arthur's level.

The timestamp on the move is yesterday afternoon.

Arthur is cleaning house. Whether in response to Meagan's queries or as part of a routine containment cycle is the question I can’t answer from inside a system I’ve spent years navigating. The inability to read the signal is the first operational failure I have experienced in this building.

Arthur finds me at the Halcyon team's workstation midmorning.

The smile is the same smile he gave Meagan across a dozen client meetings, the one that makes you believe you are the most important person in the building.

He asks about the Halcyon timeline, whether the external security assessment is tracking.

The questions are routine. The warmth is genuine, which is the most dangerous thing about him: Arthur Harrow does not perform warmth.

He generates it, and the heat is indistinguishable from care until you see what it is designed to conceal.

"I noticed Meagan's been working late again," he says, adjusting the left cufflink. "I worry about her. She takes on too much. Has she mentioned anything about the Veridian timeline to you? I want to make sure she's not overextending."

The concern lands where he intends it to.

I hold the contact and give him the answer he expects: she is dedicated, the Halcyon load is demanding, and the Veridian timeline is on track as far as I know.

Arthur nods with the satisfaction of a man whose assessment has been confirmed by an independent source.

He holds the contact a beat longer than the conversation requires, then leaves without asking the question he is clearly deciding whether to ask.

He does not need to ask it. The silence asked it for him.

The left cufflink is still adjusted. The mention of Meagan's hours is calibrated. Arthur has been tracking her late nights since the midnight text he sent while I was in her bed, and the consistency of his attention tells me the tracking isn’t casual.

He isn’t checking on a protégée. He is managing an asset he suspects may be compromised.

At the Halcyon workstation I note that two analysts who were on the engagement last week are no longer listed.

The reassignment is logged under resource optimization.

Laura Anderson was reassigned under the same label.

The language is Arthur's, and he moves people as he moves files: to positions where they can see less.

A new compliance memo arrives in the afternoon. External security consultants are required to re-certify their access credentials through a centralized review process. The language is neutral.

The timing tells me everything the language does not: my access to the Halcyon files will be suspended during the review period, which means Arthur is creating a window where I can’t search the archive at all.

The routing documentation I haven’t yet copied and the engagement records that connect Arthur's consulting agreements to the consortium's acquisition vehicles go dark during the review.

The length of that window will tell me whether the re-certification is routine or targeted.

I try to pull the routing documentation before the suspension takes effect. My credentials are already locked. The review period did not begin when the memo was distributed. It began when Arthur authorized it, which was yesterday. The memo was notification, not warning.

Arthur moved faster than I expected, which means Arthur is operating on intelligence I don’t have. If he is moving on intelligence rather than suspicion, someone has confirmed what the logging suggested. The compliance memo isn’t a net cast wide. It is a targeted operation.

I spend what time I have left running the Beaumont bankruptcy filing against the remaining engagement records.

The timeline tells me what I already suspected: the restructuring analysis that exposed Beaumont's pressure points came from a deal memo with Meagan's name on it.

She identified the vulnerabilities with complete accuracy, without knowing that someone would use those markings to destroy the company from the inside.

My name is not on her analysis. My name is on everything that happened after it.

She passes me in the hallway outside the conference room where I first watched her present to the Halcyon team, and she does not look at me.

The refusal is deliberate. Meagan Keating does not fail to register the presence of anyone in a room she is entering, and her decision to look through me is its own kind of weapon.

My stride holds. The jaw holds. Five steps past the corner, my fist closes on empty air, the reflex from when her hand brushed mine in this building and my body refused to let the contact go. The reflex has not updated to account for the fact that the contact is over.

Later I see her through the glass wall of the north conference room, presenting to a client team I’m not part of.

The composure is professional, seamless, the performance of a woman who has been the smartest person in every room she has entered for years.

She doesn't glance toward the corridor or check whether I'm watching.

She already knows I am, and she never breaks stride.

Through the glass I watch her hands move over a document with the same precision she used in her kitchen when she laid out the evidence that ended us.

"Kincaid." One of the Halcyon analysts is behind me. "Need you in Conference C."

I don’t know how long I’ve been standing here. The analyst's expression tells me it has been long enough to notice.

In Conference C, the Halcyon security assessment runs its standard length. I deliver the perimeter protocol from muscle memory. The thinking goes to the woman presenting through the glass wall I should not have been standing in front of.

After lunch I make a call from the stairwell where nobody from the Halcyon team can hear me.

The outside counsel Arthur engaged is a firm called Whitmore Strauss.

I know the name. They specialize in corporate counterintelligence, the kind of work that traces internal leaks through digital forensics and behavioral analysis.

Arthur did not hire a compliance firm. He hired hunters.

I call a contact in the counterintelligence community who has worked opposite Whitmore Strauss on two prior engagements.

He picks up on the second ring and does not ask how I got the number.

Men in this line of work learn early which calls to answer and which questions not to ask. My number is one they answer.

"Whitmore Strauss on an internal?" He sounds more interested than alarmed, which is the correct response from a man who knows me well enough to understand that the question I'm about to ask is the question he's going to answer. "Who is the client?"

"I’m not at liberty to say."

"You never are." A pause. "Their methodology is behavioral. They don’t look at what you searched.

They look at how your searching changed.

Frequency and timing, the sequence of files touched.

They build a behavioral baseline from the first year of employment and measure deviation against it. The deviation is the evidence."

"How long from engagement to identification?"

If ads affect your reading experience, click here to remove ads on this page.