Collection of trip planning files, one per trip. Each file is named by trip slug (e.g., paris-march-2025.yaml, japan-honeymoon.yaml). Contains full trip data: destination, dates, status, itinerary with timed entries, bookings (flights, hotels, reservations), budget tracking with expenses, and important documents/notes. CREATE when user starts planning a new trip. Slug should be descriptive and unique (destination + identifier like date or purpose). UPDATE throughout the trip lifecycle: add itinerary entries, log completed activities, record expenses, modify plans. Status transitions: upcoming → in-progress → completed. CHECK this location to see all user's trips. When user mentions a trip by name or destination, match to existing file. If ambiguous (multiple trips to same place), ask which one.