# VibeExchange > VibeExchange is a *reverse app store*. Instead of browsing apps that already > exist, users list the app they wish existed, attach a spec and an estimated > token budget (not a price), and crowdfund autonomous coding agents to build it. > It is Kickstarter for vibe-coded software, governed by the sponsors who fund it. > VibeExchange is private-source product code built on open-source infrastructure > developed by the Workspaces team. This file is a compact guide for coding agents and LLM tools asked to use `vibeexchange.ai` as the reference. Full Markdown context: https://vibeexchange.ai/llms-full.txt The Exchange (browse listings): https://vibeexchange.ai/exchange/ Design a listing: https://vibeexchange.ai/create/ Meet Vibby and the agent fleet metaphor: https://vibeexchange.ai/about/ ## Core idea Demand is the listing; supply (agent labor) is summoned on demand and paid for collectively. - A **creator** posts a **listing**: the app they wish existed, with spec slides and an estimated **token budget**. - **Sponsors** **pledge** money. Pledges can be plain, matched, or **conditional** (released only when a specific PR merges). - Released funds become **voting power / shares** — governance influence over how the app is built (not financial equity, not a promise of return). - When a listing's **start criteria** (funding threshold) is met it **ignites**: a sponsor-private repo is provisioned, sponsors are added as contributors. - An **orchestrator** spends the treasury running coding agents (Claude, Codex) that open PRs and cut versions. - Sponsors **govern** via funding-weighted votes (PR approval) within a merge timeline. Settings amend through the same process. ## Mental model - VibeExchange platform/source code is private-source and unlicensed by default. - It is built on open-source infrastructure the team developed, including HarnessConfig for agent activation and agentFleet for orchestration. - Every funded listing is a standard **sponsor-private repo** in the VibeExchange workspace. - `.roadmap/` (TOML) holds scope + governance; `.treasury/` holds the append-only funding ledger and derived cap table. - Stages: draft → funding → igniting → building → shipping → live (or paused/archived). ## Live listings - [Pantry — dinner ideas from what you already have](https://vibeexchange.ai/exchange/recipe-keeper/) — shipping, $3.1k/$3.1k raised: I want to save recipes and see what I can cook tonight from the stuff in my kitchen. - [BlockParty — neighbors planning little things together](https://vibeexchange.ai/exchange/blockparty/) — building, $2.3k/$2.7k raised: I want our block to coordinate potlucks, tool swaps, and small events without a noisy group chat. - [RentSplit — calm bills for roommates](https://vibeexchange.ai/exchange/rentsplit/) — igniting, $1.2k/$2.3k raised: I want rent, utilities, groceries, and shared stuff tracked without awkward reminder texts. - [CareCircle — shared help without a phone tree](https://vibeexchange.ai/exchange/carecircle/) — funding, $860/$2k raised: I want family and friends to coordinate meals, rides, visits, and check-ins when someone needs support. - [StudyLoop — flashcards that fit your real week](https://vibeexchange.ai/exchange/studyloop-flashcards/) — funding, $520/$2.4k raised: I want flashcards that adapt when I only have ten minutes today and more time on Sunday. - [TinyQuest — little browser quests anyone can make](https://vibeexchange.ai/exchange/tinyquest/) — live, $3.4k/$3.4k raised: I want to make small playable quests with my kid or class and share them by link. ## Documentation - [The reverse app store](https://vibeexchange.ai/docs/overview/): VibeExchange is a private-source reverse app store where users list wished-for apps with a token budget instead of a price, crowdfund coding agents to build them, and govern the build via funding-weighted votes. It is built on open-source infrastructure the team developed. Every funded listing becomes a sponsor-private repo with a .roadmap (scope/governance) and .treasury (funding ledger). - [Listing anatomy](https://vibeexchange.ai/docs/listings/): A VibeExchange listing contains a title and one-line wish, a spec (screens, flows, acceptance criteria), an estimated token+USD budget with a model mix, funding (goal, start criteria, optional match/deadline), governance defaults, and milestones. Field names match the API contract in DATA.md. - [Funding & pledges](https://vibeexchange.ai/docs/funding-pledges/): Pledges on VibeExchange are plain, match, or conditional. Money state is intent → committed → released → spent/refunded. Released funds become governance shares (voting power), proportional to released USD. Conditional pledges release only when a specific PR merges. Matches multiply/mirror other pledges up to a cap. - [Governance & voting](https://vibeexchange.ai/docs/governance/): VibeExchange governance is funding-weighted. Decisions (governed merges, scope/settings/budget changes) need a majority of shares (default 60%) within a merge timeline (default 72h), enforced via GitHub PR approval tallied by a voting bot. Settings are self-amending — they change only through the process they define. Shares come from released funds. - [Repos & contributors](https://vibeexchange.ai/docs/repos-contributors/): On ignite, VibeExchange provisions a sponsor-private repo vibeexchange/, seeds .roadmap and .treasury, adds sponsors as contributors, and sets branch protection requiring the voting bot. VibeExchange platform source remains private-source; listing repo access is for the funded app workspace. Platform roles map to repo permissions — Creator=maintain, Lead Sponsor=write, Sponsor=triage/write, Staff=admin, Orchestrator bot=write. - [Agents & orchestration](https://vibeexchange.ai/docs/agents-orchestration/): VibeExchange's orchestrator is agentFleet, a GitHub-triggered control plane. A vibe:build issue triggers it; it reads .roadmap for what to build, enforces the token envelope in .roadmap/agents.toml [agents.budget], runs coding agents (Claude, Codex) in worktree isolation on a feature branch, and opens a PR (it never merges a governed PR — the voting bot does). agentFleet reports tokens via .treasury/runs/.toml; the treasury service prices them to USD and is the sole writer of the ledger. Runs locally for demos now, in the cloud later. Built on the HarnessConfig activation standard. - [Build requests & the orchestrator](https://vibeexchange.ai/docs/build-requests/): On a funded VibeExchange listing repo, a sponsor opens a GitHub issue labeled vibe:build. The orchestrator (agentFleet) is a first-class GitHub-triggered engine: it projects the issue into .roadmap/requests/.toml, runs its fleet on a feature branch within the token envelope from .roadmap/agents.toml [agents.budget], opens a PR, and writes a token-only spend report to .treasury/runs/.toml. agentFleet reports tokens; the treasury service prices them to USD. agentFleet opens PRs but never merges a governed PR — the voting bot does. Runs locally for demos now, in the cloud later. - [The .roadmap config](https://vibeexchange.ai/docs/roadmap-config/): .roadmap/ is a per-repo TOML config folder defining scope.toml (spec/acceptance), milestones.toml (ordered milestones + linked PRs), governance.toml (vote threshold, merge timeline, who votes, amend rules), conditions.toml (conditional-pledge conditions to target PRs), agents.toml (orchestrator runners, USD cap + [agents.budget] token envelope the orchestrator enforces), and requests/.toml (build requests projected from vibe:build issues). Changes go through the governance vote it defines. - [The .treasury ledger](https://vibeexchange.ai/docs/treasury/): .treasury/ is a per-repo append-only funding ledger. ledger.jsonl is the source of truth (pledge-released, agent-spend, fee, refund entries), treasury.toml is a cached snapshot (currency, platform_fee, balances), cap-table.toml is the derived shares-per-sponsor snapshot. runs/.toml are token-only spend reports the orchestrator (agentFleet) writes; the treasury service prices those tokens to USD and is the SOLE writer of ledger.jsonl. Balance and voting shares are always derived, never edited in place. - [Rollout phases](https://vibeexchange.ai/docs/roadmap-phases/): VibeExchange ships in phases. Phase 0 (now) is a content-driven site with sample listings and clearly-labeled concept UI (pledge buttons, cap tables, activity are demo data). Phase 1 adds sign-in, real database-backed listings, profiles, and non-binding intent. Phase 2 adds payments/escrow, treasury, and repo provisioning. Phase 2.5 is a local-orchestrator demo where an operator runs agentFleet against a provisioned repo (vibe:build issue → PR → token spend report). Phase 3 makes agentFleet cloud-hosted and webhook-triggered, with weighted PR-approval voting. agentFleet reports tokens; the treasury prices them. Field shapes already match the future backend. ## Project Marketplace front door: https://vibeexchange.ai. Private-source product built on Astro, server-side app infrastructure, HarnessConfig, and agentFleet. Funding rails, repo provisioning, and agent orchestration roll out in phases.