backpackr.ai

The problem

AI can draft an itinerary in seconds, but nobody knows whether it holds up on the ground. Travellers who do know have no good way to correct it, and every traveller ends up planning from scratch.

How it fits together

1. 01AI draftA first itinerary in seconds.
2. 02ForkCopy any trip and make it yours.
3. 03ProposalSuggest a change, like a pull request.
4. 04MergeThe owner accepts what works.
5. 05Verified placesReports improve every trip that visits.

What I'm building

• Each itinerary is its current state plus an append-only log of small changesets, so reads stay fast and full history is kept.
• Days and stops have stable keys shared across forks, so a change to the original trip can be replayed on every fork.
• A comment with an attached fork is a proposal the owner can merge, the same way a pull request works.
• Verification belongs to places rather than itineraries, so one traveller's report improves every trip that visits that place.
• The fork and merge rules live in a shared TypeScript package, separate from the app.