GuideSeptember 19, 20261 min read
Plan the trip in GitHub — not in chat
Why trip truth belongs in a repository, hard checks stay taste-free, and adversarial review belongs on the pull request.
Chat is a great place to explore. It is a terrible system of record for a trip that has to survive airports, opening hours, and the day itself.
Put the accepted trip on main. Let agents propose pull requests. Run deterministic checks on hard invariants only — broken schema, impossible times, configured limits — and keep taste out of CI. When a soft assumption looks weak, leave an unresolved review thread and answer it with a research or experiment Issue, not a thumbs-up in the sidebar.
Alcove’s job in that loop is adversarial review plus traveler memory across journeys. Planning stays on GitHub. Merge stays yours.