Groningen

The facility was a converted agricultural complex — two large buildings that had been grain storage, originally, and still carried the proportions of grain storage beneath the extended roofline and the new cladding. The cooling infrastructure emerged from the eastern side of the main building in a system of steel ducting that served no agricultural purpose and that the architects had not attempted to disguise. A substation sat a hundred metres to the north, connected to the building by a cable trench that had recently been resurfaced. Two security cameras covered the approach road. The perimeter fence was higher than it needed to be for a building that contained no humans to protect.

Inside, the cold was different — managed, mechanical, the temperature held at a constant that felt, after the ambient cold outside, like a deliberate decision. Staal issued him ear protection without being asked and led him through a set of pressure doors into the primary server hall.

What Daniel had not been prepared for — and he acknowledged this to himself without pleasure, because being unprepared was a failure of research — was the scale. The public documentation described the Groningen facility as Arken's primary European compute infrastructure. He had visualised this in terms of the data centres he had visited at other companies: a floor, perhaps two, of managed servers in an office-park building. What was here was five interconnected halls, each the length of a football pitch, the servers in rows eight feet high and extending to a depth he could not see from the entrance. The sound of the cooling was below the threshold of pain but above the threshold of presence — it lived in the body rather than the ear. The light was artificial and consistent and had no relationship to the time of day outside.

He walked the first hall with Staal at his shoulder, asking the questions he had prepared, receiving answers that were precise and technically detailed and, taken individually, entirely satisfactory.

"The integration layer runs on distributed clusters," Staal said. "No single point of failure. The redundancy architecture is N+2 across all critical systems."

"How much of European client decision volume runs through here?"

"Sixty-three percent of active integrations. The remainder is handled by our Frankfurt facility and the client-side edge compute where deployments permit it."

"And the human override logs. Where are those held?"

A brief pause — the kind of pause that occurs not because the question is difficult but because the answer requires a choice between two formulations. "Override events are logged at the integration layer and flagged to the client dashboard. Long-term retention is managed per the client's data governance policy."

"And Arken's own retention?"

"We hold aggregated performance data for system improvement. Individual override logs stay with the client."

Daniel wrote this down. He wrote exactly what Staal had said, and then he looked at the words, and then he wrote: individual logs — client.

It was the correct answer to a different question than the one he had asked.

They ate in a small canteen that served coffee and sandwiches from a refrigerated unit. Staal sat across from him with his hands around a cup and answered further questions with the patience of someone who had answered them many times before and had decided that patience was, professionally, the correct response to journalists. The building settled around them. Through a narrow window near the ceiling, Daniel could see that the last light was gone.

"The public documentation references a Phase 3 capability roadmap," Daniel said. "Does the infrastructure here support Phase 3 deployment at the scale you'd need for a full rollout?"

Staal looked at him. It was a longer look than any of the previous questions had produced, and it carried the quality of someone recalculating something they had believed was settled.

"Phase 3 is a long-range development track," he said. "Current infrastructure supports our existing product commitments."

"That's not quite what I asked."

"No," Staal agreed. He drank his coffee. "Current infrastructure, with the planned extensions in the eastern block, would support a Phase 3 rollout at approximately two hundred million integrations."

The number was large enough that Daniel made sure to write it without reaction. Two hundred million. The current European integration market, across all platforms, was estimated at sixty to eighty million. A Phase 3 architecture built for two hundred million was not a long-range development track. It was a readiness position.

"When is the eastern block extension due for completion?"

"Q2 next year."

"And the accountability standards consultation closes on Thursday."

Staal looked at his hands. He said nothing for a moment. Outside the canteen window, the wind turbines were turning in the dark. Then he said: "I've told you what I can tell you."

"I know," Daniel said. "Thank you."

On the train back to Amsterdam, the carriage mostly empty, the window a black mirror, Daniel opened his notebook to the page he had used at the facility and read what was there.

Individual logs — client. He had framed the question as being about Arken's oversight of override events. Staal had answered a question about data governance. The gap between those two questions was not small.

Phase 3 infrastructure — 200M integrations. Q2 readiness. The consultation closing Thursday. The framework that would determine whether Phase 3 required human oversight documentation at all, closing in fifty-four hours.

He turned to a new page and wrote Petra's number, then held his pen above it.

She had redirected him, on the phone after the tour, toward the board presentation. She had been, now that he considered the sequence of the conversation, more interested in confirming his schedule than in discussing what he'd found. He wrote this observation and then looked at it and thought: this is what it looks like when you start finding patterns in the noise. He had spent five years covering this beat. He had learned to distrust himself when the story started feeling complete. The story that feels complete is the story someone has already finished for you.

He called her anyway. She answered on the second ring.

"How was it?"

"Large," he said. "The infrastructure is sized for a Phase 3 rollout at two hundred million integrations. Q2 next year."

A silence. "That's significant."

"Yes. It's also not in any public documentation I've seen."

"You'll use it in the piece." Not a question. "How was the board presentation?"

"Good," Daniel said. "Hartog was exactly what you'd expect. The regulatory argument is sophisticated." He looked at the dark window. "Renata Brouwer was in the room."

"You've mentioned her."

"She's named in the board minute. She was at the meeting that approved the accountability attribution architecture. And she's been leading their consultation submissions." He paused. "She was also, today, answering questions about Phase 3 infrastructure at the board presentation. She's the connective tissue."

"Daniel." Petra's voice was careful. "You have a leaked document showing a board discussion. You have a facility visit showing infrastructure scaled for future growth. You have a board presentation showing their regulatory argument. What you don't have yet is a source who can connect those three things at the level of intent. That's what you need."

"That's Yara."

"Then tomorrow morning is critical."

He said: "I know."

The train came through a lit station without stopping — a platform, a sign, a handful of people standing under fluorescent light who were visible for two seconds and then gone. Daniel watched the dark come back.

He had one more thing in his notebook. He had written it during the two minutes alone in the server hall, after Staal stepped away to take a call, while Daniel stood in the cold hum of the machines and looked at the extension works in progress on the eastern block: the concrete footings, the steel frame already rising, the site lighting left on for the overnight crew.

Someone paid for this before the consultation closed. Before they knew what the threshold would be.

He didn't call Petra back. He looked at the line for a long time, then closed the notebook, and watched the flat dark of the northern Netherlands move past the window at a hundred and forty kilometres an hour.