Travel Itinerary Debate — by an AI council
Design a trip that fits your budget, energy and what you actually want. Four rival AIs debate it and hand back: A debated itinerary with the trade-offs and a recommended plan.
A debated itinerary with the trade-offs and a recommended plan.
Signed off by an independent Final QA audit — with a “verify before you rely on this” list, never a black box.
Why this team
Itineraries are written by the most energetic version of you, then lived by the tired one — so the Pragmatist plans for the human who actually lands after a red-eye, and the Minimalist defends the empty hours that make trips feel like travel instead of logistics. The Optimist protects the ambition worth keeping — the once-in-a-lifetime thing you would regret rationalising away — and the End-User Advocate speaks for the co-travellers whose energy and interest never match the planner’s, which is the real source of most holiday friction.
Each seat runs on a different frontier model — GPT, Claude, Gemini, Grok — so it’s a genuine cross-model review, not one AI in costumes. How a run works →
What the debate sounds like
An illustrative excerpt — A couple with a seven-year-old is planning ten days in Japan across Tokyo, Kyoto and Osaka, with a spreadsheet currently listing twenty-three attractions and four hotel changes.
The arithmetic fails before the aesthetics do: four hotel changes in ten days is four half-days lost to packing, checkout and transit — a full day of the trip spent relocating. And twenty-three attractions across ten days with a child is 2.3 per day with zero slack, which means one meltdown or one rainy morning cascades through the whole sheet. Two bases — Tokyo and Kyoto, day-trip to Osaka — returns a day of holiday for free.
Reading this as the seven-year-old: the itinerary contains eleven temples and shrines, which from one metre tall is eleven gravel courtyards. The trip this child remembers is the robot restaurant, the train with the nose, and the arcade — and a child having a good trip is the single biggest determinant of the adults having one. One child-anchor per day, scheduled first, is not indulgence; it is infrastructure.
Delete the ranking illusion: the twenty-three items are not 1-to-23, they are three unmissables and twenty things a guidebook felt obliged to list. Protect the three absolutely, hold five as weather options, and let the rest go without ceremony. The afternoon with no plan in a Kyoto neighbourhood will outrank eighteen of them in memory — unplanned time is not unused time.
Questions
Can the council build the itinerary from scratch, or only critique mine?
Both work — give it the destination, dates, party and priorities and it proposes the structure; give it your draft and it debates the trade-offs you have already made. The draft version is usually more valuable: the disagreements surface what you actually care about, which is the real planning input.
How does it handle travellers with different energy levels and interests?
That conflict gets a seat at the table rather than a compromise nobody chose: the debate designs for the actual party — split mornings, one anchor per person per day, and the permission structure for separating occasionally. Most holiday friction is an itinerary written for one temperament and lived by three.
Does it know current prices, opening hours and bookings?
Treat those as your homework, not its knowledge — details like hours and availability change too fast to trust from memory, and the deliverable flags exactly which items need booking-ahead verification (and which to book first). The council’s job is the shape of the trip: pace, sequencing, trade-offs, and what to leave flexible.
Your material is used only to run your review — never to train public models. Encrypted in transit and at rest. Security & privacy →
Want full control — pick your own minds, set the depth? Open the full council →