The shelfwiv-industry
What is Vin? The automotive industry’s record layer.
Where the record of a vehicle actually lives, in seventy seconds: on the wire, a fact is four fields.
What the film shows.
Every fact on screen is real.
Where does the record of a vehicle actually live? This film answers the industry-side question in seventy seconds: seventeen characters, one check digit, verified in place; and a record layer built on that spine.
Four pillars, data, services, commerce, AI, read as sets of addresses: the record, the work, the transaction, the agents. The full map is public. Type data and the record layer opens: the catalog, the as-built record, the crosswalk; each fact at its own address, with its source. On the wire, a fact is four fields: value, source, timestamp, verification. Every provider’s identifiers, mapped across one spine.
The addresses the film names.
Each one answers at its own address.
Data room.
The source copy posts on request.
- Source copyThe mp4 finals, held privately by Vin; posted on request.
- The film aboveThe public copy, on Vin’s channel: a privacy-enhanced embed (youtube-nocookie.com), no cookies until play.
For the agent you send.
The agent reads the same record you do.
Same two routes, three representations: the numbers never differ between them.
- Motionsb2aThe buyer is an agent: no human leaf; discover, bind, pay, worst-case cost posted before the call
- Machine surfaces/llms.txt/icp.json/.well-known/agents.json
- One MCP serverapis.vin/mcp serves the whole platform: every door’s tools in one server, each result carrying its door’s URL.
- AttributionX-Client-Type: html | md | json | mcp names which reader arrived; it never changes the record.
- The gateNo gate on this door's two routes: keyless reads, no account. Gated actions elsewhere return a typed OFFER or a NEEDS_HUMAN handoff, never a dead end.
