Trip Planner & Itinerary · Documentation
Architecture
Trip Planner & Itinerary's pipeline, its owned data, the events it emits/consumes, and what is out of scope.
← Trip Planner & ItineraryOwned data + the invariant
The app owns `demo_eco_trip` and `demo_eco_trip_item`, written through the one typed C1 adapter. Items inherit the parent trip's scope (the `trip_item` table has no credential column), so a viewer reset deletes the viewer's trips' items first, then the trips. The data invariant holds: owner trips are canonical; a viewer's trips are credential-scoped, ephemeral, and reset-clearing.
Metered AI + out of scope
Trip CRUD and candidate gathering are deterministic ($0). One metered stage — `smart-suggest` (itinerary suggestions) — runs dual-mode: Cloud `claude-haiku-4-5`, cost-capped and fail-closed; OSS recorded as `qwen3:8b (recorded · M4)` at $0; it writes a `cost_ledger` row. Simulated + labelled: the share link is a read-only token with no public publishing. No real imagery, no PII.