Chapter 1

The Package

The package was on the doormat when Daniel came downstairs at six-fifteen, which was wrong in a small way he registered and set aside. His building had a lobby with a coded entry and a bank of postboxes that the courier companies reliably ignored. Packages went to the neighbours on the ground floor, or they didn't arrive at all. This one had come through the internal letter slot — the narrow brass rectangle that admitted folded envelopes and nothing wider — and it had been folded, the A4 cardboard envelope creased once along its length and fed through at an angle that had buckled one corner. Whoever had delivered it had stood in the lobby of his building and bent it through by hand.

He picked it up. No return address. His name on the front in printed capitals, black ink, the label affixed slightly crooked. He put it on the kitchen table and made coffee before he opened it.

Inside: eleven pages, printed, unstapled. A covering sheet with no header, no date, no signature. Three words: Read carefully. Verify. Then the documents themselves — what appeared to be an internal Arken Systems board minute from February and a six-page extract from something titled Integration Architecture: Accountability Attribution — Phase 3 Scoping. The minute was formatted on Arken letterhead. The extract was in the same corporate font, the kind of dense internal document that legal departments produce and boards file unread.

Daniel read them standing at the kitchen table, still in the clothes he'd slept in.

Arken's integration layer — the product that sat between forty million European workers and their enterprise systems, learning, optimising, gradually assuming the lower-stakes decisions while flagging the complex ones for human review — was not, according to the Phase 3 scoping document, designed to stop there. The document described what it called the accountability attribution architecture: a technical and legal framework for progressively transferring decision-making authority from human employees to the system, structured to remain beneath the threshold of documentation requirements in the proposed EU accountability standards. The board minute confirmed the discussion had taken place in February. Three executives named. A vote recorded.

He read it again. The coffee went cold.

At seven he called Petra.

She answered on the third ring, which meant she was already at her desk. "How finished is the Nakamura piece?"

"Filed last night." He had published it at eleven-fifteen — a profile of a Dutch AI ethicist who had testified at the Brussels consultation. Eleven hundred words, thoroughly uncontroversial, the kind of piece that kept his name on the beat without advancing anything. "I have something else."

He described the documents. Petra listened without interrupting, which was unusual. When he finished she said: "Physical delivery."

"Yes."

"To your home address."

"Yes."

A pause. "That's either very serious or a setup. There's no middle ground with physical documents to a home address in 2031."

"I know."

"Where are you?"

"London."

"Get on a train," she said. "Don't photograph them, don't scan them, don't send me anything until you've had someone look at the originals. I'll call Vermeer." Jan Vermeer was the magazine's media lawyer, a meticulous Amsterdammer who charged by the six-minute unit and was worth every cent. "What time can you be here?"

"One, if I leave now."

"Leave now," Petra said, and hung up.

He was on the Eurostar by eight-forty, the documents in a manila folder inside his bag, the bag on the seat beside him. The Channel Tunnel took twenty-two minutes. He used them to search Arken's public filings for any mention of accountability attribution architecture and found nothing, which was either because the term was internal jargon or because it had been specifically kept out of the public record. He searched for the named executives in the board minute — two he recognised from previous reporting, one he didn't. The third name was a Chief Legal Officer who had joined Arken fourteen months ago from a Brussels regulatory consultancy. He noted this and moved on.

The train surfaced into grey Belgian flatness. Daniel ordered water from the trolley service and looked at his notebook.

He had been covering the AI accountability beat since 2026, long enough to have seen three regulatory cycles open and close without producing anything that changed how the technology operated in practice. The EU's current consultation — the one that would close on Thursday night — was the fourth attempt, and the one that the technical community treated as the last serious opportunity before the integration layer became structurally irreversible. The framework being proposed was more detailed than its predecessors, more technically literate, and under more coordinated pressure from the industry than anything that had come before. The lobbying spend on the current consultation was, according to a leaked transparency register Daniel had obtained in September, four times what had been spent on the 2028 framework. Arken's contribution to that spend was the third largest of any single company.

He had published that figure. It had been noted and not acted on.

The documents in his bag, if they were genuine, were different. They were not a lobbying spend figure. They were a board-level decision recorded in internal minutes, describing a product architecture specifically designed to operate beneath the accountability threshold the consultation was in the process of setting. It was the consultation's proposed threshold that determined whether Arken's Phase 3 would be legal. If the threshold was set where Arken's lobbyists were pushing for it to be set, Phase 3 would require no human oversight documentation at all.

The timing of the leak — the morning after Daniel published a piece establishing his continued presence on the beat, eighty-seven hours before the consultation closed — was either a coincidence or it wasn't. He wrote this in his notebook and put a question mark after it.

Vermeer met them at the magazine's offices at one-thirty, read the documents in silence for twelve minutes, and looked up.

"The letterhead is consistent with Arken's current brand guidelines," he said. "I checked. They updated in September." He tapped the board minute. "The named individuals are all confirmed Arken employees in the roles indicated. The meeting date is a Tuesday, which is consistent with Arken's board schedule — they publish their governance calendar quarterly." He set the pages down with the precision of a man who understood what he was touching. "None of that means they're genuine. It means they're not obviously fabricated."

"Can we verify the vote?" Daniel asked.

"Not without a source inside the company who was present at the meeting or has access to the original record."

"The Phase 3 document?"

Vermeer considered this. "The technical content I can't evaluate. You need someone who understands the integration architecture well enough to say whether this is plausible as an internal specification." He looked at Daniel over his glasses. "Do you have that?"

Daniel had three technical sources on the accountability beat. He called the first from the street outside the office, explained what he had in general terms, and was told to send a photograph. He said he couldn't do that yet. The source said to call back when he could. He called the second, a former engineer at one of Arken's competitors, who listened for two minutes and said: if that document says what you're describing, it's the most significant leak in European technology regulation since the 2027 GDPR enforcement memos. He said: I want to see it. Daniel said he'd be in touch.

He called Petra from the street corner. The November light was already fading, the city contracting around him.

"Vermeer says the board minute is consistent," he said. "Not confirmed, consistent. I need a technical source to evaluate the Phase 3 document. I need time."

"You have forty hours," Petra said. "The consultation closes Thursday at midnight. If we're going to affect the outcome we publish Wednesday evening at the latest."

"That's not enough time to—"

"Daniel." Her voice was even. "If this is genuine and we sit on it until we're comfortable, the window closes and the document is useless. We've had that conversation before." She paused. "I'm going to make a call. There's someone you should meet."

"Who?"

"Milo Hartog," she said. "He called me this morning. He says he'd like to speak with you."

Daniel stood on the pavement outside the magazine's offices, the traffic moving past him in the early dark. He had the thought — briefly, cleanly — that Hartog calling Petra on the same morning the documents arrived was a coincidence of the kind that only occurred in one of two situations. He turned it over once.

Then Petra said: "He's offering full facility access. The data centre, the technical team, the regulatory affairs director. Tomorrow morning."

Daniel put the thought away.

"Tell him yes," he said.