On 10 and 11 August 2026 the person who designed this had a conversation with an AI. It did not start on this subject. He was looking for partner candidates, came across a company that resembles us, and the question of how to see that company took over.
The same thing happened four times in that conversation. The AI reads through the frame of the existing market — rival, standard, sales channel — and the designer corrects it toward the structure.
The record keeps the wrong claims rather than deleting them. That makes those four the four places this structure is most often misread.
This is not a new interview. It uses only what is actually in that conversation. Where a quote names a company, the name is replaced with the category and the replacement is marked in brackets. What the conversation did not cover, this piece does not cover.
First — what was awkward
Before looking at anything similar, the designer said this.
"When someone asks what the difference is from that — we didn't have a clear 'this is it'."
And after looking closely at the similar thing, he added:
"Looking at similar ones like this, it gets clearer and sharper."
Not that there was no answer, but that his own position came into focus only against something that resembled it. That is why this piece carries the process rather than the conclusion.
Misreading ① — "a prior competitor in the same category"
What the AI read. Runtime plus authoring tools plus store. A twenty-year-old company already doing it, deployed at scale. It read this as "structurally almost the same".
The correction.
"The position is a bit off. (…) This is just a single framework — the automotive version of [a smart-TV OS]. It's similar, but our focus is connecting devices, and that isn't their motto and doesn't look like it either. More like an entertainment OS for a car? Like a smart TV OS. They build it themselves and run their own apps on it."
The last clause draws the whole category — they build it themselves and run their own apps on it.
The direction of the relationship is reversed. There, one device receives many apps. Here, one player receives many devices. The outsides resemble each other while the arrows point opposite ways.
Misreading ② — "then they are the competition"
The reversal of direction was settled. The AI read what followed as a competitive posture.
The correction.
"If our player goes into [automotive infotainment, smart TVs, navigation units, home automation] and so on, it goes in as one app, but it can connect to any device. Not the API way — by looking at the device's UI."
The whole turn is in that one sentence. Once it is inside as a single app, that closed device becomes the place from which everything outside it can be handled. Not something to fight — something to pass through.
And he attached the conditions himself.
"Our player should be free, and device makers should use our standard. … If there's no security problem inside the device there's no ground to refuse."
"These devices don't touch the core of the vehicle, so mounting them becomes a workable picture."
The point is that the conditions came first. Open it for free, and touch nothing inside the device. A passage stands on those two and nothing else.
Misreading ③ — "a sub-profile under MCP Apps"
When the conversation moved to the MCP side, the AI concluded that the UI standard slot was already taken by MCP Apps, so the right move was to sit underneath it as a constrained-environment profile.
The correction.
"MCP Apps came out well after me. And it uses the word 'apps', but it's closer to an expression form for the LLM's UI. You can't control MCP as a tool through the UI there."
And then, what he had actually built, in one sentence.
"I took MCP, the channel where the LLM talks, and made it a window a person can talk through too — and you can also look at it together."
You can also look at it together — not replacing, but able to coexist. Two pieces from now this volume puts the two windows side by side.
He also said, in that exchange, why this volume needs to exist.
"Right now it's 'Apps already exists, you're late'. People who know a bit will keep saying that when they see this. The difference has to be understood precisely and explained."
Misreading ④ — "partners do the selling"
For a long stretch the AI read this as a partner sales model. It also read the per-industry material as a partner catalogue.
The correction.
"This isn't partners — it's mounting the player, or FlowOS for devices, on the control panel of a special-purpose vehicle. Showing what fits that domain and having them buy a starter pack and mount it themselves. That's what the keynotes were for."
"For partners it was so they'd get the inspiration — 'there's a market like this, I could apply it here'."
The industry material was never a list of things to sell. It was a map of where this can sit. Someone who owns a domain looks at it and thinks "this would work on our equipment too."
That is why four trades sit side by side at the back of this volume.
What runs through all four
Put the four together and the same shape appears. Each time, the AI tried to place this into a slot that already exists in the market — rival, or sub-specification, or sales channel. And each time the correction was changing the subject of the sentence.
Who makes the business. Who opens the window. Who mounts it on the equipment.
Here is where the designer called that difference the core.
"There, everyone's business model is generated inside their own device. With the player, all the owners of every domain can build their own business model. This looks like the core difference to me. This is the difference and the emphasis I wanted to pin down."
The next piece is about that.
What Is Not in This Interview
What was not in that conversation is not in this piece either. Nothing new was asked.
- when the question was first put, and by whom
- what they think MCP Apps got right
- what was given up in building this structure
All three have a place to be asked next time.
makemind.dev "Horizon" — Every quote is from that conversation, and no exchange was invented.