Most AI trip planners produce text. You get a lovely three-paragraph suggestion for a coastal weekend, and then you do all the actual work: find the stay, find the boat trip, check whether the times collide, add up the cost.
GGNomad is shaped so that does not have to happen. A trip plan is a real domain object — a named plan with dates, traveler count, and ordered items that each carry a type, a day number, a scheduled time, a price, and a currency, rolling up into an item count and a total. Adding a stay, a tour, and a festival ticket to a plan are real, governed mutations, and the plan renders as a day-by-day detail page in the app today.
That matters because it means AI drafting is a writer against an existing structure rather than a new feature that must invent one. The assistant reads the same federated graph the app reads — stays, tours, activities, events, and transport offers in one schema instead of four siloed inventories — and writes into the same trip-plan mutations a human uses. So a drafted plan is not a suggestion pane; it is a plan you can open, reorder, share with a group, and cost-split.
What is genuinely built today: the trip-plan domain, the day-by-day detail page, cross-domain inventory in one graph, and an assistant that can read your screen and act through the graph. What is not yet built is the planner engine itself — a dedicated operation that takes "five days, two people, coastal, under budget" and returns a ranked, time-feasible itinerary, then extends it when you add a day or repairs it when a listing goes unavailable. That engine, along with the ranking signals behind it, is designed and ticketed, not shipped.
So today the honest version is: ask the assistant to help and it works through the same catalogue you do, item by item. The roadmap version is one prompt in, a complete costed plan out, with every item traceable to the listing it came from.
Illustrative scenario. The trip-plan domain and the assistant are live; generated, extendable, self-repairing itineraries are on the roadmap. This story is narrative-only for now — there is no interactive "Do it yourself" walkthrough because the planner engine is still being built.
Ready to make this your story?
