Chapter 17: Pierce Decides

The Vienna station was three flights up in a building that shared its entrance with a business consulting firm and an immigration law office. Pierce had been using the fourth-floor workroom as a forward base for two weeks—a terminal, a desk, a window onto Mariahilfer Strasse and the particular light of late afternoon in a city where the summer came in long and flat and reluctant to commit.

She had a Geneva location on Cole.

Approximate, not precise. A financial monitoring flag she'd requested through Swiss banking channels six weeks ago, triggered that morning on a transaction pattern consistent with Cole's documented operational finance behavior. She'd run the behavioral match herself: gap intervals between transactions, denomination patterns, geographic distribution of account activity. The match was good. It was not a positive identification, but she'd been doing this for sixteen years and she knew when good was close enough.

She opened the case file.

Option A: submit a location brief to Langley, request a direct apprehension authorization on the Geneva lead, coordinate with the Swiss desk to have a team in position within thirty-six hours. She had run this scenario eight times in her career. Six of those eight had resulted in apprehensions inside forty-eight hours. Her close rate was among the highest in CI.

She had enough for Option A.

Against Option A: the London parallel operation.

Three private contractors, operating in her theater without coordination with any station she could document. Better resourced than a CI surveillance team. Less careful than a CI surveillance team—they'd left a forensic trace that Pierce had found without trying, which meant the people who'd run it hadn't cared about trace, or had been confident that trace wouldn't matter. The operation had missed Cole and burned Nadia Volkov's Vienna network in the process.

If she submitted the Geneva brief today, it went to her supervisor and through authorization channels she couldn't fully trace from where she sat. The London operation had run through channels she couldn't trace from where she sat.

These might not be the same channels. They might be.

She opened a secondary window and typed a query into the restricted personnel database. She'd been running cross-checks on MERIDIAN-adjacent personnel in the week since London—the same checks she ran on every case: death record, military documentation, supporting administrative records. The list had twenty-two names. She'd cleared eighteen of them in the last five days. She started on the nineteenth.

The first two she ran that afternoon came back clean. Consistent documentation, records that agreed with each other across the three systems she could access.

The third name was listed in the Iron Division peripheral documentation as a contracted support specialist. Cause of death: training accident, classified location, thirteen months ago. She pulled the primary death record. She pulled the military administrative package.

She looked through both for the accident investigation record.

There was none.

She ran the search again, checking alternate filing locations—separate case number, delayed submission, associated program documentation. Nothing. For a training accident in a classified program, the absence of any investigation record was not procedurally possible. An accident generated investigation documents at minimum for the insurance classification, the program liability record, and the next-of-kin notification. These were not optional. They were generated automatically by the administrative processing system at the time of death reporting.

The absence meant the documentation had been removed, not that it had never existed.

She noted it and moved to the next name.

The fourth was listed as a cause of death: drowning, off-duty, two years ago. The death record matched the military documentation. She pulled the autopsy summary.

The toxicology section was blank.

She looked at this. Standard protocol for unattended drowning deaths in the military contractor population required a full toxicological screen. The field in the autopsy summary was not listed as pending. It was listed as not applicable.

Not applicable was not a valid entry for an unattended drowning.

She sat with this for a moment.

Then she looked at what she had: a BOLO timestamp filed before the Moldova strike was logged. A CI liaison notation for Wren that shouldn't have been in the access records by any administrative path she'd been able to reconstruct. Now a training accident with no investigation record. An autopsy with a missing toxicology screen.

None of these were proof of anything. They were anomalies. Anomalies that didn't resolve.

She ran the problem again from the top, the way she ran every problem: not from what she believed but from what the logic permitted.

If the anomalies were administrative errors—misfiled records, clerical gaps, outdated database entries—then they were unrelated. She had found four unrelated anomalies while working a single case over fourteen weeks. Possible. The probability decreased with each anomaly, but possible.

If the anomalies were not errors, the intentional version required someone with Deputy Director access who had generated a BOLO on a Langley-recognized alias before a sanctioned strike had occurred, with a CI officer inserted as liaison in an access record he had no authorization to appear in, and two deaths with structurally compromised documentation that should have been generated automatically.

Closing Cole in that context was not a neutral act.

Pierce would accept professional risk. She'd accepted it throughout her career—the risk that a judgment call would not be understood, that a decision made in good faith would be assessed differently in hindsight. That was the price of working at this level.

She would not accept complicit involvement in something she could not see clearly. She would eventually have to explain her decisions in a proceeding she couldn't currently anticipate, and she did not have a clean explanation for handing Cole to a chain that might have wanted him dead before it wanted him caught.

She picked up the secure phone and called her supervisor.

"Calling on the Cole file," she said when he answered.

"What do you have?"

"The Geneva lead didn't hold." She kept her voice at the pace she used for routine updates. "I ran the behavioral signature against the updated transaction profile—the intervals are off when you account for the Swiss clearing cycle. It's a false positive." She paused one beat. "Last confirmed position is Bratislava, six days old. I'm recommending we maintain the watch notice and stand down active pursuit. No point burning resources on a stale signature."

Her supervisor was quiet for two seconds.

"Okay," he said. "Keep the watch active. Let me know if anything surfaces."

"Will do."

She set the phone down.

She looked at the terminal. Her hands were on the desk. She looked at them—steady, nothing readable in them. She noted this in the precise way she noted things that would matter later: accurately, without editing.

She had just given her supervisor a false operational assessment. She'd done it fluently, without hesitation, and the lie was technically supportable in the way that well-constructed lies were: rooted in real variables, stated in her normal cadence, ending with the recommendation that any thorough analyst would make if she actually believed what she'd said.

She had been a procedure person for sixteen years. She had operated within defined process because defined process was what kept individual judgment from compounding into institutional dysfunction. She knew the argument because she'd made the argument, to other people, in other contexts.

She set it aside and went to work.

She opened her personal laptop—not the station terminal—and began pulling the records she'd found. She was building a file on personal equipment, outside the official case record. She didn't have a name for what she was doing. She had done it anyway, for the last three weeks, adding to it in pieces. She was the kind of person who built files.

She added the two new anomalies: the missing toxicology screen, the absent accident investigation. She added them alongside the BOLO timestamp and the Wren notation. She pulled the supporting documentation for both deaths and saved it to the same encrypted folder.

Then she ran a search she should have run six weeks ago: the administrative closure records for both deaths. The formal sign-off that designated how each case had been classified and who had authorized the classification. She was looking for the authorizing documentation.

The first closure record appeared quickly. The authorization field showed an alphanumeric code—an office designation, not an individual name. Standard for classified closures.

The second took longer. She found it in the associated administrative package rather than the primary record. The authorization code was there.

She put both codes on the screen.

She looked at them.

Different case identifiers. Different date stamps. The prefixes were different.

The administrative suffix on both codes was identical. Eight characters. The same eight characters on both closure authorizations, two deaths with no other documented connection.

Pierce had worked in this building long enough to have memorized more of the administrative architecture than was strictly necessary. The suffix was not general. It corresponded to two offices in the organization. One was in the Office of General Counsel. One was in the Deputy Director's suite.

She stared at both codes.

Three seconds.

Then she sent the page to the station printer, walked to the printer, took the page, folded it once, and put it in the inside pocket of her coat, which was hanging on the chair beside her desk.

She sat back down and went back to work.