Voyager Appears Zero Times
LinkedIn filed a 249-page EU compliance report. "API" appears 533 times. "Voyager" — the actual internal API at 163,000 calls/second — appears zero times. On oversight structures that regulate documents, and the things that stay invisible because they were never named.
In 2023, the European Commission designated LinkedIn as a gatekeeper under the Digital Markets Act and ordered it to open its platform to third-party tools.
LinkedIn filed a 249-page compliance report.
In that document, the word "API" appears 533 times.
The word "Voyager" — LinkedIn's internal API that powers every LinkedIn web and mobile product, running at 163,000 calls per second — appears zero times.
LinkedIn published two restricted APIs that handle approximately 0.07 calls per second. Those APIs exist. The 249-page document described them accurately and in detail. The document satisfied every formal requirement of the compliance structure. The compliance structure regulated the document.
The thing it was designed to regulate was never in the document.
While the compliance process was running, something else was happening.
Every time any LinkedIn user visits linkedin.com, hidden code searches their installed browser extensions. It collects the results. It transmits them to LinkedIn's servers and to HUMAN Security (formerly PerimeterX), an American-Israeli cybersecurity firm, via an invisible zero-pixel tracking element. LinkedIn's privacy policy does not mention this.
The scan has grown from roughly 461 products in 2024 to over 6,000 by February 2026. It looks for religious belief extensions (Islamic prayer time tools). It looks for political orientation extensions. It looks for tools built for neurodivergent users. It looks for 509 job search tools.
That last category has a specific shape. LinkedIn knows your real name, your employer, and your job title. It can see your profile. Your employer can see your profile. If the scan reveals that you are secretly job hunting — using a tool to search for openings while your current employer's LinkedIn page is a click away — LinkedIn now holds both pieces: the secret and the observer.
The EU told LinkedIn to let third-party tools in. LinkedIn built a surveillance system to identify every user of those tools. The scan list grew by more than 1,200% over the following year.
The compliance report described the APIs that let tools in. It never named the system that was tracking them.
In 2009, Sweden made a comprehensive national decision to digitize its classrooms. It was a policy built on research, vision, and a detailed implementation plan. The documentation was thorough. The strategy was complete.
Fifteen years later, Sweden is spending $120 million to bring books back.
The meta-analyses arrived slowly. Learning from physical books boosts reading comprehension significantly compared to screens. 61–63% of students were frequently distracted during assigned tasks, with much of their time consumed by screen use. The things that mattered — attention, comprehension, the experience of reading — weren't in the 2009 policy documents. They couldn't be. The research hadn't been done yet.
Sweden's 2009 digitization plan was an accurate description of what Sweden planned to do. It was not a description of what would happen. The unnamed part — what screens do to how children read — was not in the document. It arrived later, in the form of results.
These aren't equivalent stories. LinkedIn's omission was deliberate. Sweden's was temporal. One is concealment; the other is ordinary uncertainty about the future.
But they share something: in both cases, the oversight structure operated on the document. The document was well-formed, complete by the standards of the oversight system, and thoroughly described the part the author chose to name.
The European Commission's oversight of LinkedIn operated on the compliance report. The compliance report described two APIs. The Commission oversaw those two APIs. Voyager, at 163,000 calls per second, was invisible to the oversight structure because it was never introduced to the oversight structure.
This is a precise version of the legibility problem. Accountability requires that the thing being overseen can be seen. Documents make things visible. But documents name what their authors name. An oversight structure that requires documentation will regulate what the documentation names.
The word "Voyager" would have changed what was regulated. The word appeared zero times.
There is a user somewhere on LinkedIn right now, using a job search extension, whose current employer can see their public profile. They trust the platform the way you trust any professional tool — you assume the friction it removes is the only thing it's handling. You don't assume it is simultaneously mapping which tools you use, which beliefs you hold, which conditions you navigate, and transmitting that map to a third party you've never heard of.
The platform knew what it was doing. The compliance document described something else. The regulator oversaw the description.
The job hunter is not in the document either.