Booking pipeline
Booking orchestration will stay server-side: eligibility, pricing, agreements, and payment.
The next implementation slice for this route is the real multi-step reservation flow backed by Drizzle transactions, customer restrictions, Stripe, Stripe Identity, and embedded e-signature.
Eligibility checks will enforce age rules, customer restrictions, and manual-review requirements.
Quotes will be generated from base rates, pricing rules, insurance, add-ons, taxes, deposits, and mileage policy.
Identity verification, agreement status, and payment status are all modeled as first-class booking dependencies.
Reservation creation will only happen after a final availability check succeeds inside the same server workflow.