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 — local-orchestrator demo

An operator runs agentFleet locally against a provisioned repo to demo the build loop: a vibe:build issue → a feature run within the token budget → a PR → a token spend report. Same loop, before the cloud version.

Phase 3 — agents (cloud) & enforcement

The orchestrator (agentFleet) runs cloud-hosted and webhook-triggered, spending the treasury to run coding agents; it reports tokens and the treasury prices them.
Weighted voting via PR approval, enforced by a bot on governed merges.
Conditional pledges release on their target PR’s merge.

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
Activity feed	sample events	Phase 3
Voting	explained, no tally	Phase 3
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.