Page 32 of Power Play

I drop her at the corner of her block because proximity to her building in my truck is a variable neither of us wants Arthur to have. She leans across the console, kisses me once, and gets out without looking back.

The taste of her coffee is on my mouth for three blocks.

By evening, the decision is made. Priest called in the late afternoon with information that closed the window. Arthur has restructured the internal monitoring on the client archive. The changes are subtle, layered into a routine security update that nobody at the firm would question, but the effect is a tighter net. The queries Meagan has been running are now being logged with a resolution that will trace her research back to specific hypotheses. She isn't being watched anymore. She's being mapped.

"One more thing," Priest had said. "Your Halcyon access logs were pulled into the same review. Separate request, same authorization level. Arthur isn't just mapping her research. He's mapping proximity."

Proximity. Arthur is measuring the distance between Meagan's queries and my access patterns. If the overlap is visible from his vantage point, the next calculation he runs is the one that puts her name next to mine.

I sit in my truck and run the timeline. If Arthur maps her research before she finds the full picture, he'll have enough to act against her directly. The protection I've been building around her, the locks and the measured information, won't hold against Arthur operating with specific intelligence about what she knows.

I have to tell her tonight, all of it, the timeline, the scope, the years I spent inside it. The expression she'll wear when she understands what I did and what I failed to do.

I drive toward Printer's Row.

The plan is as close to a plan as a man like me gets: arrive, sit down, say the words. I've been storing them behind my teeth since the night I wrote her name in my ledger and had to cross it out because the first name came before the last. I don't know what happens after the words leave my mouth. I've run threat assessments on warlords with private armies, and none of them scared me the way the next hour scares me.

Traffic stacks heading south, brake lights lining up on State Street. Meagan works late. She's been working late for days, running the data through the corrected lens, circling toward the answer with every query she enters into a system Arthur is tightening around her. She has the expanded archive and the routing patterns I pointed her toward when I should have pointed her toward the truth.

If I tell her first, it's a confession. If she finds it first, it's a betrayal.

The dread sits low in my stomach, formless and certain. I’m not going to get there in time.

10

MEAGAN

The Renaud correction has been rearranging the data in my head for days, and tonight, sitting in my office with the expanded archive open across three monitors, the new shape is finally visible.

I've been running the data through the angle Kincaid gave me in his loft while I was lying against his chest and pretending I was only thinking about the case. The Renaud hypothesis was elegant and logical. It was the version of this story where Arthur is a victim and the world still makes the kind of sense I need it to make.

Kincaid's jaw told me the hypothesis was wrong before his mouth did. The tactical correction he offered instead, the one about the routing predating Renaud's involvement, was precise enough to send me back to the data with sharper eyes. I ran the harder version of the theory the next morning, the version I should have run first, would have run first, if I hadn't wanted the other one to be true badly enough to build a case for it instead of against it.

Arthur is the designer.

The routing skeleton I traced through the Veridian engagement and the Marcelline files, through the logistics company I pulled from the expanded archive, all of it leads back to the same hand. The intermediary vehicles change names. The sectors rotate. The skeleton underneath is identical: targeted companies destabilized through manufactured instability, then acquired at a fraction of fair value by consortium-linked entities.

I've been staring at this skeleton for days. Tonight I’m looking at it from the corrected angle, and the angle reveals a layer I missed.

The engineered collapses required handlers. Someone had to manage the operational logistics of each takedown, from planted board dissent and leaked financials to the coordinated pressure campaigns that fractured family-held companies from the inside.

That work would not appear in the client-facing deal memos. It would appear in the project records, in the line items that track who was assigned to each job and when.

The expanded access Arthur gave me reaches into the full assignment history. He granted it to monitor my research. The irony of his invisible hand is that the same reach lets me see team rosters on deals I was never assigned to.

I start pulling rosters for the companies I've mapped to the collapse pattern, cross-referencing files to see who was working on each deal. Internal teams rotate on any book of business: different analysts, different partners depending on the sector. The internal names change with every assignment.

The external consultant does not.

His name appears on the first file I pull, listed under external security and operational consulting. It appears on the next, and the next after that, on every record that maps to a company that was targeted and destroyed.

The name is Evan Kincaid. His assignments stretch back years before the gala, before he handed me a white card, before the meeting in a Pilsen coffee shop where he told me he'd been watching Arthur longer than I'd been working for him.

My thumb presses into the inside of my ring finger under the desk. The crescent from Laura's visit has faded. I begin making a new one.

I run the confirmation twice, from different angles, pulling different files and checking whether the pattern holds when I vary the search parameters.

The verification reflex is the one part of me that will always function. The pattern holds from every angle and with every variation. His name is on the work, and the work maps to the destruction. The timeline places him inside the operation during the exact years he told me he was only beginning to suspect the operation existed.