The Board Presentation
The location was not Arken's headquarters but a conference facility three streets away — a building of the kind that existed to host things its clients preferred not to host on their own premises, with catering staff who appeared and disappeared without acknowledgement and chairs that were comfortable enough to prevent distraction. Daniel arrived at eight-fifty to find that a place card had been set for him at the back of the room, slightly apart from the investor group, which numbered perhaps twenty and occupied the front two rows in the manner of people who had been doing this for years and knew where the important sightlines were. His card said Daniel Voss — Observer. The word Observer had been printed in a lighter font than his name.
Hartog was at the front with two colleagues — a CFO Daniel recognised from Arken's public filings and Renata Brouwer, who nodded at Daniel when he sat down with the brief precision of someone who had already allocated the appropriate amount of attention to his presence.
The presentation began at nine.
What followed was, Daniel noted in his book, the most technically coherent regulatory argument he had heard delivered in a corporate setting. He had attended dozens of investor presentations in five years of covering this beat — the usual structure was aspiration laundered through legal qualification — and this was not that. Hartog moved through the accountability standards framework clause by clause, the same framework Brouwer had walked Daniel through the previous morning, but where her register had been defensive, his was almost prosecutorial. He was not arguing that Arken deserved regulatory accommodation. He was arguing that the consultation's proposed framework was technically misspecified, that its documentation requirements would be unenforceable at the operational level, and that Arken's proposed amendment — which he distributed as a two-page annex and which Daniel read twice — was the only version that could actually be audited.
The amendment proposed replacing the consultation's categorical human-oversight requirements with a continuous monitoring protocol. Continuous monitoring, Hartog explained, was measurable, machine-readable, and independently verifiable. Categorical oversight — a human in the loop for decisions above a defined risk threshold — was, in practice, a documentation exercise that produced paperwork without producing accountability. It rewarded the appearance of oversight rather than the substance.
Daniel wrote down: paperwork without accountability. Then: the frame.
Because the argument was not wrong. That was the thing he found himself returning to as Hartog moved through the second section, the competitive landscape. The consultation's current drafting did reward documentation over substance — he had written this himself, fourteen months ago, in a piece about the 2030 framework review. The concern was real. The amendment was technically rigorous. The question it did not address — and Daniel noticed the absence the way you noticed a missing step in a staircase, by feeling it in your leg before your eye found it — was who designed the continuous monitoring protocol, who had access to its outputs, and whether "independently verifiable" meant the same thing in a system built by the party being verified.
He wrote this in his notebook. Not his laptop.
Brouwer took the third section: compliance architecture. Forty slides, the detail granular enough that two of the investors stopped taking notes and began simply watching her with the expression of people recalibrating an estimate. She described Arken's internal audit framework — the structure of the logging systems, the escalation protocols, the third-party verification arrangements currently in discussion with two named certification bodies. She named the two bodies. Daniel looked them up on his phone under the table. One was an independent Dutch certification firm he had encountered before. The other had been established in Brussels fourteen months ago and listed a single board member, whose name he did not recognise, in its public registration.
He wrote the name down. He would look it up later. He looked it up now.
The company had two directors. The second name was familiar: he had seen it in Arken's published governance disclosures, listed as a member of the advisory committee for their Series C capital raise. He looked at this for a moment and then put his phone face down on the table and watched Brouwer finish her section.
There was coffee afterward, the kind of coffee served in rooms where decisions were ratified rather than made. Hartog moved through the investor group with the ease of a man for whom the conversation was already complete, and found Daniel at the edge of the room by the window, looking out at the canal.
"What did you think?"
"It was a strong argument," Daniel said. He kept his voice even. "The continuous monitoring proposal is technically interesting."
Hartog smiled. "I spent three months on that amendment. The current drafting is a gift to the platforms that don't want genuine oversight — they can satisfy the documentation requirement without changing a single line of decision architecture. We're proposing something that actually works."
"Who designed the monitoring protocol?"
"We did, initially. The independent verification layer would be managed externally." He gestured toward the room behind them. "That's what the certification body arrangement is for."
Daniel nodded. He did not say: one of those certification bodies was incorporated fourteen months ago and shares a director with your Series C advisory committee. He wrote the thought, in compressed form, in his notebook while Hartog turned to greet one of the investors, and when Hartog turned back Daniel had the notebook closed and the pen in his jacket pocket.
"Your document," Hartog said, his voice lower now, the room noise covering them. "The board minute you have — I want you to understand something about it."
Daniel waited.
"It describes a discussion. A real discussion, which we had, about the direction of the product roadmap. What it doesn't describe — because it was a preliminary meeting, not a decision meeting — is the conclusion." He looked at Daniel with what appeared to be candour, the candour of a man who had decided that a partial transparency was more useful than none. "We did not approve the accountability attribution architecture as described in that document. We approved the continuous monitoring framework you heard this morning. That is Phase 3."
"The scoping document I have describes something different."
"The scoping document you have is from February. This morning is November." He let that settle for a moment. "The piece you write — if it's about what was discussed in February — is historically accurate and currently misleading. I'm telling you this because I'd rather you have the full picture." He extended his hand. "I'll have Renata send you the board resolution from May. You should have it on record."
Daniel shook his hand. He kept his face where it needed to be.
He called Petra from the pavement outside. The cold was immediate after the conference room's managed warmth — a raw, wet Amsterdam cold, the canal wind carrying it off the water.
"How was it?"
"Sophisticated," Daniel said. "Hartog is repositioning Phase 3 as the continuous monitoring framework. He's arguing it's the only version of accountability that actually works. He's going to send me a May board resolution."
A silence that lasted two seconds longer than it needed to. "Does it hold up?"
"The technical argument holds up. The amendment is well-constructed." He paused. "There are questions about the verification architecture."
"Questions you can answer before Wednesday evening?"
He looked up the canal toward the Ministry annex, where the consultation was running its penultimate day. A man in a green cycling jacket crossed the bridge at the end of the street and disappeared.
"I need to speak to Yara," he said.
"Who?"
"A source in Tanger. Former Arken, Head of Ethics. She left eight months ago." He had told Petra about Yara in September, when he had first identified her as a potential source. He had a note of this in his files. "I mentioned her in—"
"Tanger," Petra said. "Daniel, you have thirty-five hours."
"I know."
"If you go to Tanger, you're writing on the plane back."
"I know."
A pause. Then, in a different register — the register she used when she had made a decision and was presenting it as his: "This story is here. You have the document, you have the tour, you have the board presentation. You have Renata Brouwer on record explaining the compliance architecture. Hartog is giving you the rebuttal in writing. What does a source in Tanger add that you can't verify from here?"
What Yara added was the question of whether the scoping document in Daniel's bag had been sent deliberately, and by whom, and why the continuous monitoring framework that Hartog had just described as Phase 3 shared a verification body with Arken's own capital raise. He said: "Independent corroboration of the original document."
"You've already confirmed the letterhead, the board date, the named executives."
"Confirmed consistent. Not verified."
Another silence. Then: "Book the flight. Send me the return time. And Daniel—" She paused. "This is it. The Phase 3 infrastructure, the accountability architecture, the board resolution. This is the piece. Don't come back with something that contradicts it."
He said he understood. He hung up and stood for a moment on the pavement with the canal behind him and the Ministry annex ahead of him and the documents in his bag that Hartog had just partially explained.
He took out his notebook and added two words beneath the certification body director's name: Series C.
Then he opened the airline app and booked the four-fifteen to Tanger.