Koovira Dev Docs
20-modules/trip-planner/overview.md

Module: Trip Planner (trip_planner / โ€”)

Status: ๐ŸŸก Partially implemented (built; zero throughput) ยท Last validated: 2026-09-06 ยท Priority: P2

A wizard that plans trips and matches stays/experiences (integrates with StayGo tripPlannerMatch). Validated against triplanner.php, trip_wizard.php + schema.

A. Purpose

Users plan multi-stop trips (itinerary + preferences) and get matched supply. No commission model defined; not on the dashboard command center.

C. Entry points

/trip_wizard.php, /tripmanager.php, /triplanner.php.

E. Feature registry (prefix TRIP-)

IDFeatureTablesStatus
TRIP-001Trip wizardtrip_wizard_submissions๐ŸŸข
TRIP-002Trip plan + itemstrip_plans (0), trip_plan_items๐ŸŸก
TRIP-003Preferencestrip_plan_preferences๐ŸŸก
TRIP-004Collaborators / sharetrip_plan_collaborators, trip_shares๐ŸŸก
TRIP-005Stay matchStayGo HotelModule::tripPlannerMatch :2712๐ŸŸข

G. Data model (2026-09-06)

TableRowsNote
trip_plans0zero plans exist right now
trip_plan_items0
trip_plan_preferences6orphaned โ€” see note below
trip_plan_collaborators0
trip_shares0
trip_wizard_submissions0
Correction (2026-09-06): trip_plan_preferences is not empty โ€” it holds 6 rows (trip_plan_id 69, 70, 76, 77, 78, 79; datecreated 2026-08-26) referencing trip_plan_id values that no longer exist in trip_plans (which is 0 rows). This means the feature was exercised on 2026-08-26 (at least ~79 trip plans were created up to that point) and trip_plans / trip_plan_items were since wiped (QA reset or similar) without clearing the dependent trip_plan_preferences rows. "Zero throughput" below describes the current DB snapshot, not the feature's history โ€” flag this orphan-row / missing-cascade pattern for engineering if a clean reset is expected (trip_plan_preferences has no FK enforcing cleanup here).

Status note

trip_plans = 0 right now โ€” no live plans โ€” but the orphaned trip_plan_preferences rows above show the wizard has been used at least once (2026-08-26) before a reset cleared trip_plans. Absent from the dashboard command center: confirmed via incfiles/dashboard/_cc_config.php (KV_CC_TILES/KV_CC_TILE_MODULE, 2026-09-06) โ€” no tile with key trip/triplanner exists in that registry (36 tiles checked), unlike startup_passport which does have one ('startup' tile, programs band).

Dependencies / change-impact

Depends on StayGo (tripPlannerMatch), location/search. Change-impact: low (unused); wiring a booking handoff to StayGo would activate it.