Open Vehicle Passport (OVP)

An open, implementation-neutral protocol for recording the lifetime history of a vehicle.

OVP is the idea that the events a vehicle accumulates over its life — oil changes, diagnostic sessions, dyno runs, ECU tunes, ownership transfers — belong to a shared, open format that any application can read and write. No single company or product owns the format; any producer can write events, any provider can host a passport, any application can read one.

Reading order

1. Vision — why this exists, what it’s not, the business philosophy behind an open protocol.
2. Manifesto — the short, quotable principles.
3. Architecture — entities, layers, how OVP and OVPF relate.
4. Identifiers — vehicle IDs, passport addresses, QR/NFC philosophy.
5. Discovery — how a client finds a vehicle’s provider, and how providers delegate.
6. Events — the event-sourcing model, facts vs. opinions, event envelope.
7. Trust — how trust is established without a central gatekeeper.
8. Roadmap — the order in which this gets built.

Two names, one project

• OVP — Open Vehicle Passport. The ecosystem: identities, discovery, trust, providers, governance.
• OVPF — Open Vehicle Passport Format. The technical specification: schemas, event formats, APIs, export/import.

View the source on GitHub