Insurance
On at the second
the job starts.
The rideshare 3-period state machine, but every transition is a signed event a carrier can verify. Drivers don't manage coverage — we do, automatically, from the second they go online.
On at the second
Four periods, one state machine
Coverage that knows where you are in the trip.
P0 — Driver offline
Personal auto policy is in force. The driver is not earning, no L1fe Link coverage applies.
P1 — Online, no job
Contingent liability fills the gap: $50k bodily injury per person, $100k per accident, $25k property. Underwritten by Coverwhale.
P2 — Heading to pickup
Full commercial. $1M combined single limit. Triggers the second you accept; ends when the cargo or passenger is in the vehicle.
P3 — Cargo on board
Full commercial + cargo-class rider. Adds product-loss coverage: $5k parcel, $10k food, $50k Rx, $100k specialty. Ends when delivered.
The road, all of it
Coverage that doesn't
end at the city line.
Highway, side street, gravel road, gated dock. The state machine doesn't care about geography — only about whether you're earning.
Why deterministic matters
Sixteen legal transitions. No more, no less.
The state machine is order-sensitive: only the documented 16 legal transitions are reachable from the 4 states. Any other transition is rejected at the contract boundary.
For a claim adjuster, that's the whole point. They can replay the chain of events for any shift and prove which period applied at the exact second of an incident. Not "well, the driver said…" — just the chain.
Carrier integration.
Carriers consume a signed event stream — one period-change envelope per state change, with the trigger event ID, driver ID, from/to period, and timestamp. Resumable via Last-Event-ID. We onboarded Coverwhale as the first carrier; a second is in flight.
Questions
Drivers, carriers, claim adjusters.
Drivers: drivers@l1fe.ai. Carriers + claim adjusters: insurance@l1fe.ai. The source-of-truth state machine is open and pinned by unit test — read the contract before you integrate.