Skip to content

Glossary

Domain terms used in code, specs, UI copy, and conversations. Pick one spelling and stick to it everywhere.

TermDefinition
TripThe top-level container. Has a title, dates, one or more destinations, and zero or more days.
DestinationA single place a trip stops at. A trip can have many destinations (multi-stop).
DayA calendar day inside a trip. Auto-generated from trip dates; can be empty.
ActivityOne scheduled item inside a day: lodging, transport, food, sight, or free-form note.
Live modeThe “use this trip on the road” UI: today / next-up view, mark-done, inline log.
Schedule driftDifference between planned and actual time for an activity in live mode.
Forward-to-TreeperThe OS share-extension flow that hands a URL or reel to the app for AI ingest.
IngestAI process that turns an external URL (Instagram, YouTube, blog) into draft activities.
Prompt-to-itineraryAI process that builds a full draft trip from a natural-language prompt.
Open tripA trip whose host has marked it as accepting buddies. Discoverable in feeds.
Trip-mateAnother user joined to your trip via the open trip / apply-to-join flow.
CommunityA topical / destination-based feed people can join. Not the same as a trip group chat.
Trusted contactA guide or partner you’ve added to your private address book.
Verified guideA guide listing in the marketplace that has passed Treeper’s verification rules.
Day adventureA bookable single-day package from an operator: tour, hike, etc.
SourceThe origin of an activity or AI-generated suggestion. Always preserved as a back-link.
SyncThe Supabase ↔ device exchange of trip data. Local-first; last-write-wins at v0.
  • We say trip, not “itinerary” in UI copy (shorter, friendlier). The DB table is still trips.
  • We say buddy in user-facing copy, trip-mate in specs / code.
  • “Plan” is a verb; the noun is trip.