They had the key.

It had taken fourteen hours, not seventeen, which was the kind of margin that Nava filed under acceptable rather than good — acceptable meaning: it worked, no one died, and the operation left no footprint that a careful analyst would classify as human intervention rather than technical noise. Good would have meant twelve hours, clean extraction, and Taheri none the wiser. What they had gotten was fourteen hours, clean extraction, and Taheri spending ninety seconds staring at a woman who had materialized at his café table with a question about the menu in heavily accented Greek and departed before he remembered that the café did not have table service.

During those ninety seconds, Yonatan had been behind him.

He had not asked how she created the ninety seconds. He had positioned himself at the adjacent table four minutes before she approached, with a newspaper and a coffee and the particular quality of invisible competence that she had come to recognize as his operational register — present without presence, watching without watching, the stillness of a man who has made himself so unremarkable that the eye simply moves past him the way the eye moves past furniture.

The key was now on a mirrored device in her jacket pocket.

Taheri had sent his heartbeat confirmation at 07:43, from a café on the south side of Athalassa, and the seventeen dormant junctions had answered as they always answered — with eleven seconds of compressed silence that meant we are still here, we are still waiting, do not yet fire — and Taheri had folded his laptop and walked back into the Nicosia morning entirely unaware that the key he carried was now in two places instead of one.

They had taken the 10:15 flight back to Tel Aviv.

On the plane, Nava had slept for sixty minutes with the totality she always brought to short sleep, and Yonatan had spent the same sixty minutes completing the financial sub-model for the Geneva operation that he had started in the notebook during the night in the safe house, and when she woke he had placed a single page of handwritten notes on the fold-down tray in front of her without comment, and she had read it in four minutes, and they had not spoken for the remaining forty minutes of the flight because there was nothing to say that the notes had not already said.

Now they were back.

And now Nava had to build the algorithm.

The algorithm she needed was different from the one she had described to Amos. What she had described to Amos — the heartbeat replication engine, the synthetic confirmation packet that would stand in for Taheri's key and keep the seventeen junctions dormant while they neutralized the primary and secondary activation pathways — was accurate as a concept. The implementation was the problem.

The problem was this: the key was not a static credential. It was a rolling cryptographic seed, generating a new signature every time it was used, which meant that the signature she had copied from Taheri's device in Nicosia was valid for exactly one activation. One heartbeat. After that, the seed rolled, and her copy was dead, and Taheri's device was the only thing in the world that could generate the next valid signature.

Which meant she did not have a key.

She had a pattern.

And a pattern, if you understood its architecture well enough, could be extrapolated.

She had been looking at the seed architecture for six hours, since landing, and she understood it the way she understood most elegant things: fully, quickly, and with the particular irritation of someone who recognizes that the person who built this was operating at a level she respected and that respecting it made her job harder.

The seed used a variant of a Blum Blum Shub generator — a pseudorandom number algorithm based on the factorization of a large semiprime — with three modifications she had not seen before. The modifications were subtle. They were also the reason it had taken her six hours instead of two to map them. She had been circling them from four angles simultaneously, building the counter-architecture in the way she built all counter-architectures: by asking not what the system did, but what the person who designed it feared it could not do, and designing from the fear outward.

The designer's fear, as best she could read it, was replay attacks. The modifications were all anti-replay measures: mechanisms to ensure that even if an interceptor captured a valid signature, they could not reuse it or predict the next one without the physical seed device.

But anti-replay measures, by their nature, required the generator to know what it had previously generated. And a system that remembered its own history had a history that could, in principle, be reconstructed.

In principle.

In practice, reconstructing the history of a Blum Blum Shub variant from a single sample was computationally equivalent to factoring a 2048-bit semiprime, which the best available algorithms could not do in under several years.

She did not have several years. She had seven days until the calendar hard date.

She sat with this problem for another forty minutes, and then she stood up and walked to the window and looked at the street and looked at the sea she could not see from here and thought about architecture, and about the specific structural weakness of systems that were designed to be unbreakable from the outside but were never adequately stress-tested for the attack vector of someone who had briefly been inside.

She had been inside for ninety seconds.

During those ninety seconds, Yonatan had extracted not only the current signature but the device's last four activation logs — timestamps, packet sizes, routing headers — which she had dismissed at the time as supplementary data and which she now pulled back up with the feeling of someone returning to a room they left too quickly.

Four activation logs. Four timestamps. Four packet sizes.

The packet size varied. By very small amounts. Amounts that were, on their own, meaningless — noise, rounding error, the inevitable micro-variance of a real-world system that no simulation had fully predicted. But the variance was not random. It was bounded. And the bounds of the variance, correlated against the timestamps, produced a pattern in the seed's rolling sequence that was not the sequence itself — but was a shadow of it. A silhouette. A shape that contained, if you built the right inference engine around it, enough information to predict, not with certainty but with sufficient probability, the next several valid signatures.

Sufficient probability.

She defined sufficient as ninety-two percent. Below ninety-two percent, the risk of a failed heartbeat triggering the contingency layer was too high. Above ninety-two, the window of acceptable operational risk opened.

She thought she could get to ninety-four.

She sat back down and began to build.

She worked for four hours without speaking. This was not unusual. What was unusual was the quality of the silence in the room, which had changed from the shared-work silence of the past three days into something with a different texture — she was aware of him in the room in a way she had not been before, not distracted by the awareness, not affected by it in any way she was prepared to examine, simply aware, the way you become aware of a sound that has been present for several days and which you register for the first time as something other than background.

He was rebuilding the Majd financial model with the new information from Dmitri — the Geneva symposium, the Western oil company consulting relationships, the IRGC payment channel that now had a name and a face attached to it — and he was doing this with the same quality of unhurried thoroughness that she had stopped finding frustrating around the end of the second day and had started finding, without entirely intending to, something else.

She did not examine what the something else was.

At 11:40 p.m., she ran the first test iteration of the algorithm.

Eighty-one percent. Eleven points short.

She looked at the output for a long moment. The gap between eighty-one and ninety-two was not a small gap. It was the gap between the algorithm she had built and the algorithm she needed, and closing it required either more data — which meant going back to Taheri for another sample, which was operationally unacceptable — or a better inference model, which meant understanding the seed's modification structure more deeply than she currently did.

She pulled up the modification architecture and looked at it again.

And then — at the precise moment that the irritation of eighty-one percent was settling into the particular stubbornness that preceded her best work — she became aware that Yonatan had stopped typing.

She did not look up.

"You're stuck," he said.

"I'm thinking."

"You've been looking at the same section of code for eleven minutes."

She looked up. He was watching her with the focused attention he usually directed at datasets — not invasive, not presumptuous, simply present and observant in the way that she had learned was simply how he occupied space.

"The confidence is at eighty-one," she said. "I need ninety-two. The gap is in the third modification to the seed generator. I understand what it does. I don't yet understand why it was designed the way it was, and I can't exploit a design choice I don't understand the reason for."

He was quiet for a moment.

"What does the modification do?" he asked.

"It introduces a time-dependent variable into the seed rotation. Every activation, the seed shifts not just based on the previous value but based on the elapsed time since the last activation, weighted by a factor that I can't isolate because it changes with each cycle."

"A decay function," he said.

She looked at him.

"The weighting factor decays over time," he said. "The longer between activations, the smaller the time-dependent contribution. The designer wanted the system to behave differently depending on whether activations were happening on schedule or running late." He paused. "Because a late activation is a stress signal. It means something in the operational environment has changed. The system adapts its behavior under stress."

She stared at him.

"How do you know that?"

"I don't know it. I'm describing the economic behavior of a system that needs to maintain predictability under variable conditions while discouraging predictability from the outside. The time-decay modification is the equivalent of a central bank adjusting its policy rate in response to market stress — the mechanism changes when the environment changes, so that anyone modeling the mechanism from outside can't assume stable parameters." He looked at her screen. "If I'm right, the decay rate is probably tied to the seventy-two-hour cycle. The weighting factor halves every cycle it runs late."

She turned back to the code.

She found it in four minutes.

It was not exactly a halving — it was a reduction by the natural log of the delay in hours, which was mathematically adjacent to what he had described and which, once she had isolated it, collapsed the unknown variable in the third modification from a free parameter to a calculable function of the timing data she already had.

She ran the algorithm again.

Ninety-four point seven.

She sat back in her chair. The relief was real and brief and she let it be both, because the algorithm was operational and that was what mattered and there was no reason to perform either more or less than what she actually felt, which was the specific satisfaction of a problem that had resisted and then yielded, mixed with something else she was also not examining.

"You found it," he said from across the room. Not a question. He had been watching the screen.

"We found it," she said. The correction was automatic, and she was aware, as she made it, that she meant it.

He looked at her with an expression she had not seen on his face before — not the settled certainty of his analytical register, not the focused watchfulness of his operational one. Something quieter than both. Something that acknowledged, without comment, that the correction had been made and received.

"Do you find me attractive?" she asked.

The silence that followed was approximately two seconds long and contained, she estimated, more information per unit time than most conversations managed in an hour.

"That's not relevant to the mission," he said.

She looked at him. He looked back at her. His face had not changed — the same quality of stillness, the same even attention — but there was something in the eyes that was different from the analytical register and she could not, with her considerable skill at reading faces, determine whether that something was an answer or a different kind of question.

She laughed.

It surprised her. Not the laugh itself — she had a laugh that surprised people who expected something more controlled — but the moment of it, the specific location of it inside a conversation that had begun with a cryptographic seed generator and arrived here by a route she had not planned and could not entirely explain.

"That's the first time I've laughed in—" she started.

"Months," he said quietly. Not unkindly. As though he had been watching this for long enough to know it.

She looked at him for one more second. Then she turned back to the screen.

"Ninety-four point seven," she said. "We have a working heartbeat replicator. Seven days until the hard date. We need to be in Geneva before the end of the week."

"I know," he said.

"Go to sleep, Yonatan."

"You first."

She thought about arguing. She looked at the algorithm on the screen — clean, operational, holding at ninety-four point seven — and decided that the algorithm would still be there in six hours and that what it needed from her now was not more looking but a rested brain.

She went to sleep.

He opened the notebook and wrote one line, closed it, and looked at the algorithm on the screen for a long time before he turned off the desk lamp and the room went dark except for the glow of the monitors and the stars outside that neither of them, from inside, could see.

Bradley Cole arrived the way Americans always arrived in other people's intelligence operations: with confidence, with good shoes, and with the implicit assumption that his presence represented an upgrade rather than a complication.

He was forty-seven years old, CIA Chief of Station for the Tel Aviv residency, and he had the specific build of a man who had been athletic in his thirties and had since made peace with the metabolism of his forties without entirely surrendering his self-image. He wore a linen jacket the color of sand and he had the easy, unhurried manner of someone who had spent twenty years in this region and had arrived at the considered conclusion that the way to survive it was to be the calmest person in every room he entered.

He was calm now.

He was also, Nava thought from the moment he walked through the door of the safe house, operating on information he should not have had, and the question of where he had obtained it was something she began working on immediately, in the background, while the foreground managed his arrival.

Amos had sent a one-line message thirty minutes earlier: Cole requests a meeting. I told him where you are. Unavoidable. He knows about Majd.

The message had arrived while Yonatan was at Shacharit and Nava was on her third coffee and her second pass through the Geneva operational plan. She had read it twice, put the phone face down, and spent the twenty minutes before Cole's arrival considering what unavoidable meant in Amos's vocabulary, which was a precise and deliberately limited vocabulary. Amos did not use the word unavoidable to mean I had no choice. He used it to mean I made a choice, and the choice was this, and I am telling you so that you understand the constraint rather than waste time resenting it.

The constraint was Bradley Cole.

The question was why.

Cole looked around the safe house with the practiced neutrality of a man who had seen many safe houses and found this one neither better nor worse than average. He looked at Nava's operational map on the wall — she had re-taped the brown paper, extended it by another meter, and added the Geneva topography and the symposium venue footprint — and he looked at Yonatan, who had returned from prayers eight minutes earlier and was at his desk with the siddur closed and the laptop open, and he looked at the two coffee cups and the four empty water glasses and the general organized density of a workspace that had been inhabited continuously for five days by people who worked the way serious people work, which is to say without regard for the appearance of working.

"Good morning," Cole said. His Hebrew was workable. He chose English.

"Bradley," Nava said. She did not offer her hand. Not a statement — simply her standard operational register, which did not include handshakes.

Cole looked at Yonatan. "You're Eliyahu. The financial analyst."

"Yes," Yonatan said, without looking up from the laptop.

Cole processed this for a moment. He had, Nava had been told by people who knew him well, a genuine talent for reading rooms and a genuine blind spot for rooms that did not conform to his expectations of how rooms should operate. This room did not conform. Two people who had been working continuously in the same space for five days developed a shared atmosphere that was difficult to enter gracefully from the outside, and Cole was, she could see, feeling the difficulty without entirely understanding it.

"I'll sit," he said, and sat.

He placed a folder on the table. Thin — six pages, maybe eight. He did not open it.

"You found the architect," he said. "Cyrus Majd. MIT, Geneva, the Rothbury Energy Group consulting arrangement." He paused. "We've had Majd in our picture for fourteen months."

The room was quiet.

"You had him," Nava said, "and you didn't share."

"We had a profile. Not operational intelligence. Not the activation architecture. Not the pipeline compromise." He looked at her steadily. "We knew he was in the IRGC orbit. We didn't know what he was building."

"What do you want, Bradley?"

"I want you both in Langley by the end of the week. Joint operational command, full resource sharing, coordinated neutralization of the Mahdi architecture before the hard date." He said this the way he had probably rehearsed it — direct, reasonable, framed as a proposal rather than a demand, with the implicit understanding that the resources he was offering were real and that real resources in a seven-day window were not nothing.

Nava looked at him.

She looked at the folder on the table.

She thought about joint operational command, about what it meant in practice when the CIA coordinated with Israeli intelligence on a time-sensitive operation with a hard deadline, about the specific history of those coordinations and the specific pattern of how they resolved when the interests were ninety percent aligned and ten percent not, and how the ten percent not had a tendency to become forty percent not at precisely the moment when it mattered most.

"No," she said.

Cole looked at her without surprise, which meant he had expected this, which meant the proposal had not been the actual proposal. The actual proposal was coming.

"We have assets in Geneva you don't," he said. "We have a surveillance package on Majd that has been running for six weeks. We have an established operational footprint inside the symposium venue — three of our people are registered as delegates. We can give you access to all of it." He paused. "What we can't give you is a seven-day unilateral operation in Swiss territory that destabilizes three years of bilateral intelligence relationships if it goes wrong."

"And if it goes right?" Yonatan said, from his desk.

Cole turned. It was the first time Yonatan had contributed to the conversation, and Cole, Nava noticed, recalibrated slightly — the way you recalibrate when someone you had been reading as background turns out to be foreground.

"If it goes right," Cole said, "everybody wins."

"That's a remarkably symmetrical assessment of an operation in which your interests and ours align on the outcome but differ substantially on the attribution." Yonatan turned from the laptop. "You want Majd neutralized without a public trail that leads to either service. We want Majd neutralized and the pipeline architecture dismantled before the hard date. Those are compatible objectives with incompatible operational requirements. Joint command introduces a coordination layer that we don't have time for."

"We have time if we start now."

"We're already operating," Nava said. "Starting over from a joint command structure costs us two days minimum. We have seven."

"Then let us integrate into what you're already running. Not command — support. Assets, surveillance data, the symposium access. You run the operation. We provide infrastructure."

Silence.

Nava looked at Cole and thought about the six weeks of surveillance data and the three delegates inside the symposium and the Geneva footprint she did not have, and she thought about the mole inside the directorate and what joint operational integration meant for the security of an operation that was already compromised at the institutional level, and she thought about seven days and the specific weight of the hard date sitting at the end of them.

She also looked at Yonatan, because she found that she was doing this now — not asking for input, not seeking approval, simply including him in the sight line of a decision the way you include someone whose judgment you have come to trust even when you have not yet finished deciding whether you trust it.

He was looking at Cole. His expression had not changed. But there was something in the angle of his attention that she had learned to read as disagreement — not active disagreement, not resistance, but the specific posture of a man who has identified a variable the other person has not addressed.

"No," she said.

Cole looked at her.

"The mole," she said. "You know about the mole."

A pause that was a fraction too controlled to be casual.

"We have intelligence suggesting a compromise inside your directorate," Cole said. "We were planning to—"

"You were planning to use it," she said. "As leverage. Not now — later, after the operation, when the question of attribution and credit became a negotiation." She looked at him without heat. "That's not a criticism, Bradley. That's just operational logic. But it tells me that whatever you integrate into this mission is going to carry a second purpose, and I don't have the bandwidth to manage second purposes in a seven-day window."

Cole looked at her for a long moment. He was, she knew, genuinely intelligent — not as fast as she was, not as architecturally patient as Yonatan, but intelligent in the particular way that twenty years of surviving the Middle East station produced: adaptable, unsurprisable, and very good at knowing when he had lost a negotiation without losing face in the process.

"The surveillance package," he said. "Six weeks of Majd. I'll send it to you this afternoon, no conditions, no integration requirement. Consider it a professional courtesy."

"We'll consider it," she said.

He stood. He picked up the folder — he had never opened it, she noted, which meant it had been a prop, a visual anchor of seriousness, not actual evidence of anything he was prepared to share unilaterally. He buttoned his jacket.

"Nava," he said at the door. "The hard date is real. Whatever you think about joint operations, don't let the perfect be the enemy of the operational."

"I never do," she said.

He left.

The door closed. The room settled back into its own atmosphere the way a room does when a foreign element is removed — not with relief exactly, but with a kind of readjustment, a return to its natural frequency.

Nava looked at Yonatan.

"You said no," he said. He was not objecting. He was confirming.

"Yes."

"Without consulting me."

"I looked at you."

He was quiet for a moment. "That's not consultation."

"No," she agreed. "It's faster."

Something shifted in his expression — not quite amusement, not quite its absence, something between the two that she had begun to find distinctive. "You were right to say no," he said. "The surveillance data is worth having. The integration is not."

"I know."

"I would have said the same thing."

"I know," she said again. She turned back to the map on the wall. Geneva. The symposium venue on the Rue de Lausanne, the Majd surveillance footprint she did not yet have but would have by this afternoon, the seven days that had become six while they were talking to Bradley Cole. "Pack a bag. We leave for Geneva tomorrow morning."

"I know," he said.

She looked at him over her shoulder. He was already back at the laptop, already in the data, and she had the specific sensation of a person who has been in a room with someone for five days and has, somewhere in those five days without marking the moment, stopped noticing the strangeness of the room and started noticing only the work and the person doing it alongside her, and the way those two things had, at some point she could not identify, become difficult to separate from each other.

She turned back to the map.

Six days.

They both knew.