Restricted analysis, made public daily.
Declassified under standing order Edition No. 033 Wednesday, August 5, 2026

The Case Is About Secrets.
The Stakes Are the Interface.

On July 10, Apple sued OpenAI, io Products, and two former Apple hardware employees in federal court, alleging a coordinated theft of trade secrets for OpenAI’s consumer hardware push. This week, Apple asked the judge to block them from using anything they allegedly took, before the case is even decided. The allegations are unproven. The fight underneath them is not: over which device gets to stand between a person and their next decision.

On the record, this is a trade-secret case: a Delaware nonprofit and its for-profit arm, two former Apple hardware employees, and forty-one pages of allegations about laptops, authentication bugs, and confidential design files. Filed July 10 in the Northern District of California, Apple v. Liu et al. accuses OpenAI, io Products, and those two former employees of what the complaint calls “a coordinated pattern of misconduct at an institutional level,” allegations OpenAI has not conceded and no court has tested. But read past the docket number, and the case is describing something Apple didn’t have to sue anyone to prove: a fight over which company builds the device that decides what you see next.

The specific claims are vivid, and unproven. Apple alleges that one defendant, an eight-year Apple electrical engineer, kept an Apple-issued laptop after leaving for OpenAI in January, later exploited what the complaint calls a “previously unknown authentication bug” to reach Apple’s internal file shares, and coached a departing colleague on how to “avoid trouble with the security team” while copying confidential files before her own exit. Apple alleges that a second defendant, twenty-four years at Apple and most recently Vice President of Product Design for iPhone and Apple Watch, now the company’s Chief Hardware Officer, used an Apple internal project codename to ask job candidates “what’s the plan” for unannounced products, and directed job candidates to bring “actual parts” from Apple to a “show and tell” interview, a directive that, per the complaint, surprised at least one candidate, who said he “didn’t even know we could take those from the office.” Apple says it wrote OpenAI directly to raise these concerns in February and received no response. That silence, per the complaint, is what turned an internal investigation into a federal filing.

This week, Apple went further. It asked the court for a preliminary injunction barring the corporate and individual defendants from accessing, using, or disclosing the disputed information before the underlying case is even resolved, along with expedited discovery, including depositions of the two individual defendants, additional OpenAI employees, and corporate representatives from OpenAI and io Products. OpenAI’s response was not a simple denial. In a public post the same week, OpenAI called the suit “careless, aggressive and oddly personal,” published an email chain it says shows Apple’s outside counsel contacted the wrong person in February, after confusing two Asian last names, and said it heard nothing further about the specific allegations for five months before Apple sued. Apple’s request for the injunction, the post states, is “based on false information and completely unnecessary because we do not have, nor want, any of their trade secrets.” No hearing date has been set. Nothing here is decided.

A channel doesn’t fail quietly. When it changes, every signal built for the old one breaks at once.

What the docket can’t capture

Strip away the laptops and the codename, and what Apple is actually litigating is proximity. OpenAI didn’t acquire io Products (the hardware startup one of the defendants co-founded with former Apple design chief Jony Ive) because it wanted to build another phone. It bought a track record in the kind of ambient, agent-first device that could sit between a person and their next decision without an app ever getting opened to do it. If a device like that works, it doesn’t compete with the iPhone on features. It competes with every interface that currently stands between a person’s intent and the systems that act on it: search bar, browser tab, storefront, phone screen.

Clinical note — the vulnerability underneath the other five

Every clinical pattern in this record assumes a channel. Authority Misclassification, Signal Fragmentation, Contextual Ambiguity, Trust Transfer Failure, and Decision Exclusion all describe how a system fails to recognize genuine expertise through today’s interfaces: search, browsers, chat. None of them assume the interface itself is about to change.

A device transition doesn’t cause one clinical pattern. It risks causing all five, at once. A record built for search behaves differently the moment the entry point isn’t a search bar at all: signals fragment across a new surface, context resets, trust has to re-transfer, and an entity built for yesterday’s interface can be excluded from a decision it never got the chance to enter.

Named for the record. The underlying dispute is Apple Inc. v. Liu et al., No. 5:26-cv-07078-VKD, filed July 10, 2026, in the Northern District of California. It is a Defend Trade Secrets Act claim, unresolved, with all allegations still unproven, named here as evidence that the contest for the next interface is already underway, not as a verdict on who wins it.

What this means if you’re not Apple or OpenAI

You don’t need to build a device to have a stake in this fight. Every layer of authority infrastructure (a client’s identity architecture, their entity record, their evidence, their disclosures) currently assumes a shape of contact: a website, a search result, a voice assistant, a chat window. The device contest underway right now is a bet that the shape of contact is about to change again, the way it has changed before. The irreversible mistake is building an authority record that only works on today’s interface. Answer Engine Authority is built the other way: portable across whatever wins, because the record was never wired to any one interface in the first place.

Sources

Apple Inc. v. Chang Liu, Tang Yew Tan, OpenAI Foundation, OpenAI Group PBC, and io Products, LLC, No. 5:26-cv-07078-VKD (N.D. Cal., San Jose Division), complaint filed July 10, 2026, read directly from the filed document (CourtListener docket 73602437). Every quoted phrase above describing the original complaint’s allegations is drawn from that filing itself.

This week’s preliminary-injunction and expedited-discovery motion is drawn from contemporaneous reporting, including MacDailyNews and Bloomberg (August 4, 2026). OpenAI’s response is drawn directly from its own public statement, “Apple is getting this wrong” (OpenAI, August 3, 2026). The original July 10 filing is also independently corroborated by CNBC. As of publication, no hearing date has been set and the court has ruled on nothing.

If the interface changes tomorrow, does your authority change with it — or does it start over?

Your authority record shouldn’t have to bet on which device wins this fight. The Encoded Authority Diagnostic starts by testing whether yours already can. Or bring the harder question to SIA — the Intelligence Officer, briefed on every edition

of this record the morning it releases.

Every edition, in order, from No. 001 · A new edition releases daily, 05:30 CT.

Open the Record
‹ Edition No. 032 Next Dispatch — releases 05:30 CT ›