A travel itinerary platform built advisor-first. An advisor builds a client's trip and publishes it; the client reads it on their phone, chooses between the options offered, and adds their own notes as they travel.
- Domain model and permissions — membership rather than ownership decides who can do what, and a person on a trip needs no account.
- Backend architecture: a Hono API over PostgreSQL with Drizzle, Redis and BullMQ for background work.
- Separate traveller, advisor and admin applications over shared data-access, permissions and UI packages — plus the iOS app, a Capacitor shell with a one-command App Store release pipeline.
- The booking import pipeline: forward a confirmation email or upload a PDF, Claude extracts the items, and nothing lands on a trip until someone approves it.
- Trip messaging — planning, travel-party and per-item threads whose rosters derive from trip roles, live over server-sent events.