The model
VibeExchange docs
Everything behind the reverse app store — from what a listing is to how funds become votes, how repos get provisioned, and how agents build the apps the crowd asks for.
The reverse app store
List the app you wish existed, fund it as a crowd, and let agents build it — governed by sponsors.
01Listing anatomy
A listing is a pitch for an app that doesn't exist yet — spec, token budget, funding, and governance.
02Funding & pledges
Pledge plain, matched, or conditional. Funds move intent → committed → released, and released funds become voting shares.
03Governance & voting
Decisions need a funding-weighted majority within a timeline, enforced via PR approval. Settings amend through the same process.
04Repos & contributors
Every funded listing is a sponsor-private repo. Sponsors are added as contributors; platform roles map to repo permissions.
05Agents & orchestration
agentFleet — a GitHub-triggered orchestrator — spends the treasury running coding agents (Claude, Codex) in worktree isolation, opening PRs and reporting token spend.
06Build requests & the orchestrator
A `vibe:build` issue triggers agentFleet, which projects it into .roadmap/requests, builds within a token budget, opens a PR, and reports token spend.
07The .roadmap config
.roadmap/ holds scope, milestones, governance, conditions, agent config, and build requests as TOML — editable through governance.
08The .treasury ledger
.treasury/ is an append-only ledger of pledges, releases, and agent spend — the cap table and balance are derived; agentFleet reports tokens, we price them.
09Rollout phases
The site ships first with sample data; accounts, payments, repo provisioning, a local-orchestrator demo, and cloud orchestration light up in later phases.