The Alcove product

Review infrastructure for trips you already plan on GitHub.

Open standard + hard CI in the repo. Alcove sells adversarial PR review and cross-trip traveler memory — not a planning console.

Start planning Open dashboard Docs

Evidence loop

Thread → research → resolve → merge

Review

Unresolved thread

Opening time unverified

Evidence

/research #41

Cite shrine calendar

Decision

PR update

Keep 07:00 or revert

Accepted

Merge

Traveler accepts

Three surfaces

GitHub plans. Alcove reviews. Memory compounds.

Keep the agent plugin you already use for GitHub. Alcove installs beside it — it does not replace it.

Your assistant

Talk through the choices

Explore options and save small proposals with GitHub tools.

GitHub

Keep a record of your plan

The saved trip, proposed changes, and supporting evidence live here.

Alcove

Check and remember

Review the details and keep the traveler lessons you approve.

The review

Unresolved threads until evidence is in the repo.

A finding that matters stays open. Link a research or experiment Issue, update the PR, resolve the thread, then merge.

Hard CI green does not mean soft assumptions are true

Research answers a specific question with citations

Experiments falsify a requirement-fit hypothesis

Alcove never auto-merges

Example · your trip proposal

Proposed change · arrival day

Add a boat tour after landing

1 concern to check

ConversationCommitsChecksFiles

Alcove review · unresolved

Your flight lands at 14:00 and the tour leaves at 15:00. The transfer alone takes an hour. Where is the time for baggage and pickup?

Check this before accepting the proposal

Research the concern

Ask your assistant to check the tour’s departure time and later options, then update the proposal with what it finds.

Checks

built-in checks passed

Required fields & timesRecorded times are consistent
Alcove reviewTransfer buffer needs attention

The decision is yours

Review the answer, then accept or revise the proposal. Alcove never accepts it for you.

Awaiting your decision

Built for operational journeys

One kernel. Travel is the first profile.

Backend packages stay domain-neutral. Travel language lives in the public template, marketing, and dashboard copy.

Trip repos

Accepted trip lives on main

Agents propose on branches. Merge is the traveler’s decision — chat is never the record.

Hard CI

Impossible states fail deterministically

Schema, times, configured limits. Taste stays out of the hard path.

GitHub App

Adversarial review on the PR

Alcove challenges proxies and gaps. Material findings open unresolved threads.

Evidence

Research and experiment Issues

Answer threads with cited work. decision-review keeps the process honest.

Subjects

Traveler memory in Alcove

Profiles and approved lessons stay hosted. Trip repos store opaque ids only.

Watch

External change may propose

When enabled, material world changes open PRs. Only you merge.

Open trip starter

alcove-trip-japan

trip.yamldays/engine/Issues

Hard constraintsIn git

Itinerary nodesIn git

Bookings & linksIn git

traveler_idsIn git

Create

Make it yours.

Retune hard constraints. Fill itinerary nodes. Keep traveler secrets out of git.

Useful without Alcove

An open standard first. Hosted review second.

Deterministic checks and the planning method ship in the template. Alcove is optional infrastructure when you want adversarial review and memory across trips.

Preferences and postmortems stay out of the public template on purpose.

Dashboard

Thin by design. No itinerary UI.

Auth, GitHub connect, subject CRUD, and billing. Review stays on the PR. Reflection stays on MCP.

Connect GitHub

Install the App on the repos you want reviewed.

Manage subjects

Create travelers whose ids appear in trip YAML.

Billing

Plans and usage for hosted review — not for git itself.

Start on GitHub

Start your trip. Check your first proposal.

Connect the App, add subjects, and let review try to break the plan before the day does.

Start planning Open dashboard See pricing