Rollout phases
VibeExchange is built so the front door ships first and the rails light up behind it, without a rewrite. The data shapes you see today already match what the real backend will produce.
Phase 0, the site (now)
A content-driven site that explains the model and shows it working with sample data.
- Browse the Exchange, read full listing detail, design flow, docs.
- Funding meters, cap tables, and activity feeds render from sample content.
- Anything that needs a backend is a labeled concept: pledge buttons say “coming soon”, cap tables are sample sponsors.
Phase 1, accounts & real listings
- Sign-in.
- Creators publish real listings; sponsors signal non-binding intent.
- Profiles and listing ownership backed by the platform database and asset storage.
Phase 2, money & repos
- Real pledges via a payment gateway, with escrow.
- The treasury ledger and derived voting shares go live.
- Ignite provisions a private repo and adds sponsors as contributors.
Phase 2.5, D1 bridge demo/live path
- A funded listing can provision a repo, seed
.roadmap/,.treasury/,.harness/, and.fleet/, start Replicas/fleet supervision, open a PR, and show status in VibeExchange. - A
vibe:buildissue projects to.roadmap/requests/<id>.tomlwhen the webhook/API bridge is configured. - agentFleet reports token-only run files; the treasury service prices spend later.
Phase 3, agents (cloud) & enforcement
- The orchestrator (agentFleet) runs through the fully configured webhook/remote runner path for every eligible listing.
- Weighted voting via PR approval is enforced by a bot on governed merges.
- Treasury pricing automation appends ledger spend entries from token reports.
- Conditional pledges release on their target PR’s merge.
Phase 4, custom versions & sync
- A sponsor or team can create a custom version of a funded app without learning Git.
- The custom version can keep up with the original, evolve separately, or offer improvements back through original-app governance.
- GitHub forks, branches, and PRs remain the behind-the-scenes substrate; the VibeExchange UI speaks in app-workspace language.
Phase 5, Launch Projects
- A funded listing or custom version can create a customer-owned Launch Project.
- Launch Studio records Stripe Projects service inventory without storing raw credentials.
- Domains flow through search, check, quote, explicit approval, registration, and Cloudflare Worker custom-domain binding.
- Managed agent runs prepare deploys, previews, release notes, and launch reviews under visible budget caps.
What’s faked today (and labeled)
| Feature | Phase 0 | Lights up |
|---|---|---|
| Pledge button | concept shell | Phase 2 |
| Funding meter | sample data | Phase 2 |
| Sponsor cap table | sample data | Phase 2 |
| Repo link | placeholder | Phase 2 |
| Build status | D1 bridge status where configured | Phase 2.5 |
| Activity feed | sample or bridge events | Phase 3 |
| Voting | explained, no tally | Phase 3 |
| Custom versions | product model documented | Phase 4 |
| Launch Projects | D1/API/UI shell | Phase 5 |
| Create listing | explained flow | Phase 1 |
Everything fake is marked, and the shapes already match the future API, so turning each phase on is a swap of data source, not a redesign.