Connectivity, Digital Twins & Vessel Passports

Thesis: Fiberglass mass production created millions of opaque boats (Fiberglass boom). Digital brokerage made them searchable without making them knowable (Modern era). The missing layer is a HIN-keyed passport that becomes a digital twin: not a gimmick dashboard, but an evented history + live systems state that improves Quality Boat Days by killing surprise.

Pace table

Layer	Near	Mid	Long
Owner-entered passport events	Now–2028	Norm among serious buyers	Expected like Carfax reflex
Yard/OEM write-back	Pilots	Regional density	Interoperable APIs
Telematics / IoT health	Premium	Mid-tier options	Battery & bilge defaults
Insurer/lender twin underwriting	Experiments	Rate differentials	Standard packets
Marketplace trust scores	Sparse	Visible badges	Liquidity shift to documented boats

Accelerators

Theft and fraud pressure; insurance hardening; electric battery SoH needs; Boat Day / competitor passport products; OEM connected-boat apps seeking retention.

Brakes

Privacy fears; dealer fear of transparent service margins; fragmented marine software; owners who never log events; cybersecurity incidents.

Owner impact on QBD

Upside: Faster closings; fewer catastrophic first-season repairs; predictive maintenance before Saturday dies; resale premiums for documented boats. Downside: Subscription creep; “check engine” anxiety; data used against owners; orphaned apps when OEM sunsets.

Action: Log surveys, winterize, major services, and upgrades to your Vessel Passport now — even before the market fully prices it. Future you is a buyer or seller.

Second-order effects

• Documented boats pull away in liquidity; undocumented become discount bins.
• Yards that write back win OEM and insurer referrals.
• AI crew agents (AI crew) become useful only if the twin is trustworthy.

Ecosystem winners / losers

Winners: Passport platforms; surveyors who certify digital packets; owners who document; lenders with lower loss ratios. Losers: “Trust me bro” sellers; yards that refuse digital trails; apps that silo without export.

Failure modes

Fake event injection; incomplete twins worse than none; telematics false alarms scrubbing good days; vendor lock-in holding HINs hostage.

Regional variance

Title/registration states differ — passport must respect US jurisdiction variance (state guides). Storm belts gain more from documented haul-out and repair histories.

Leading indicators

% of listings advertising HIN history; insurer discounts for twins; OEM API openness scores; average passport event count per active boat on Boat Day.

What Boat Day will watch

HIN graph density; write-back from ecosystem modules; SoH fields for electric; agent-readable passport schemas.

Signposts

• Near: major insurer pilot accepts passport PDF/API
• Mid: top marketplaces badge “documented history”
• Long: undocumented boats face material liquidity haircut

---

HIN graph — future shape

Nodes: vessel (HIN), owners (time-bounded), events (survey, service, claim, upgrade, sale), systems (engines, batteries, MFDs with serials), documents. Edges: installed_on, performed_by, insured_by, located_at. Boat Day’s passport is the seed; ecosystem write-back densifies it.

Privacy design that keeps trust

Owner-controlled share links; insurer-only packets; public marketplace redaction; revoke on sale. Agents must respect scopes — see AGENT_BRIEF.md.

HIN graph — agent schema sketch

Vessel(HIN) -[:HAS_EVENT]-> Event(type, date, actor, docs)
Vessel -[:HAS_SYSTEM]-> System(serial, softwareVersion, SoH?)
Vessel -[:OWNED_BY {from,to}]-> Owner
Event -[:PERFORMED_BY]-> Vendor

Boat Day passport events are the write path today; futures densify with OEM/yard write-back. Agents should POST events only with owner consent and never invent survey conclusions.

Boat Day is keeping tabs — we’ll surface advances that improve your boat days. See Radar · Scenarios.