md / _internal / dev-archive / trips / README.md
Molino⺢Pro

README

Master Codebase Guidebook
Markdown + HTML Dev-Docs Renderer - Frontend Client Module

Default Index
Open README.md
Root: README.mdtrips
Milestones
⬆ Parent folder📁 archive📁 fh📁 next-steps📝 20260421_trips-plan-guide📝 booking-bundle📝 calendar-agenda📝 README📝 trip-join
H1Trips

Status: canonical hub for Trips features and planning.

This folder is the entry point for Trips domain notes, route planning, pricing, offers, orders, and booking flow.

H2What belongs here
  • Trip identity and draft handling.
  • Trip planner rules and normalization.
  • Trip pricing snapshots and LineItems generation.
  • Offer and Order flow as downstream commercial snapshots.
  • BookingBundle and execution overlays for Trip fulfillment.
  • Trip-related projection rules for document, Apps Script, export, and calendar flows.
  • FareHarbor button-only execution rules for retail booking.
  • Lane-based commercial surfaces for travel and trips.
H2Canonical files
H2Related hubs
H2Folder rule
  • Keep the latest active note at the top level of this folder.
  • Move older superseded notes into archive/ inside this same folder.
  • Keep next-steps/ for the immediate execution queue.
H2Current shape

Trip is the planning entity. LineItems are the economic transfer layer. Offer and Order are downstream snapshots. Document is the orchestration surface. Apps Script is the office projection layer.

H2Route surface
  • /trips
  • /trips/new
  • /trips/[tripId]
  • /trips/[tripId]/edit
  • /trips/[tripId]/schedule
  • /trips/[tripId]/join
  • /trips/featured
H2Immediate direction
  • Present the four commercial lanes explicitly.
  • Use app-native cards for city tours and the featured guided trip.
  • Use FareHarbor booking buttons only for retail booking execution.
  • Keep flexible planning and collaborations in-app.
  • Add a small footer bridge back to Studio.
H2Current status notes
  • Trip planning already has its own engine and planner actions.
  • Trip join has dedicated create/read/recompute actions, which means the join flow is a real submodule now.
  • Trip pricing already feeds LineItems, and that bridge should stay explicit.
  • The new planner path under /trips/new is where the deterministic creation flow lives.
  • FareHarbor production UI should stay button-only, with no calendar/grid widgets.
  • Trips remains the broader commercial hub, while Studio Travel is the curated bridge.

That is the boundary this folder should preserve.