A renku is a poem many hands write in turn, under rules about what each turn may change
Every trip gets planned across a chat thread, a group text, six tabs and a spreadsheet. The thread is where the reasoning happens, and it's also where the reasoning dies. Renku is the durable, structured, multi-author plan of record — the thing humans and agents work on together over weeks.
01 / Resolution
Paris fully planned while Nice is still "four nights, probably". Resolution is a property of a region of the plan — the sequence, the verse, the character — not a zoom setting. One glance answers where the plan is thin.
02 / Legibility
Days are time-scaled columns, not lists. A 90-minute train is a 90-minute block. Unplanned time is drawn and countable. Over-packing gives itself away before anyone reads a word.
03 / Proposals
"Three nights in Nice instead of two in Lyon" arrives with its cascade computed — what moves, what breaks, what's orphaned, what it costs. A co-traveller reviews it on a phone and votes.
04 / Nothing is lost
The whole plan is snapshotted before and after every change, so undo is exact. That's what makes it safe to let the group edit freely instead of routing everything through one person.
Not discovery. Not booking. Not generation — one-shot AI itineraries are already commoditised. This is the durable object those tools produce and then throw away.