MolinoPro

20260422_milestones-roadmap

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

Default Index
Open README.md
Root: README.mdmilestones
Milestones
H1Milestones Roadmap

Status: forward planner for the Trips, Document, Offer, Order, LineItems, and projection stack.

This file is the high-level roadmap. It is intentionally broader than the micro-goal tracker.

H2Current Baseline

Already in place or effectively established:

  • Trip CRUD in the UI.
  • Document sidebar tooling that reaches the same commercial pipeline.
  • Trip -> LineItems -> Offer -> Order -> projection flow.
  • A deterministic trip pricing engine as the current pricing authority.
  • Document-driven trip editing and assistant-assisted input.
H2Near-Term Milestones
H3M1. Standardize pricing across Trip, Product, and Experience

Goal:

  • reuse the Trip pricing engine shape for products and experiences
  • normalize outputs into the same LineItems adapter
  • keep compute deterministic and out of the UI

Success looks like:

  • one pricing family
  • multiple source types
  • one LineItems contract
H3M2. Normalize all commercial rows as LineItems

Goal:

  • make LineItems the shared economic truth for trip-based, product-based, and experience-based sales
  • support both snapshot and regeneration modes where needed

Success looks like:

  • sourceType/sourceId traceability
  • deterministic overwrite where required
  • no ad hoc pricing rows outside the LineItems model
H3M3. Formalize Offer and Order snapshots

Goal:

  • Offer should capture a stable snapshot from LineItems
  • Order should capture a stable snapshot from Offer LineItems

Success looks like:

  • no recompute in Offer creation
  • no recompute in Order creation
  • Offer edits do not rewrite historical Order truth
H3M4. Complete Apps Script export routes

Goal:

  • expose office export routes for PDF, calendar, email, and booking docs
  • keep external projections separate from business truth

Success looks like:

  • clear Next.js action -> route -> Apps Script -> metadata flow
  • stable export contracts
  • reusable office automation surface
H3M5. Finish the main booking flow

Goal:

  • support Stripe-backed booking flow where appropriate
  • keep FareHarbor as an external route and later sync target

Success looks like:

  • booking intent recorded internally
  • payment/checkout path is explicit
  • external booking route is documented as an alternative, not the only path
H3M6. Add FareHarbor calendar sync later

Goal:

  • keep bookings tracked and in sync between the app and external distribution

Success looks like:

  • calendar-aware sync rules
  • deduped external keys
  • explicit operational status
H3M7. Integrate Hotelbeds as a later service layer

Goal:

  • add a separate hotel booking capability driven by city, nights, dates, and room list arrays

Success looks like:

  • complimentary to the main trip flow
  • isolated from the core trip planner
  • used when the trip requires hotel inventory fulfillment
H2Roadmap Order
  1. Standardize pricing across Trip, Product, and Experience.
  2. Normalize all commercial rows as LineItems.
  3. Formalize Offer and Order snapshots.
  4. Complete Apps Script export routes.
  5. Finish the main booking flow.
  6. Add FareHarbor calendar sync later.
  7. Integrate Hotelbeds as a later service layer.
H2Source Links