Repos & contributors
Every funded listing is a standard sponsor-private git repo. The marketplace is just the front door; the repo is where scope, money, code, and governance for that app actually live.
Longer term, most users should not need to know that. VibeExchange can present the repo as an app workspace: a place to fund features, request changes, compare versions, and decide whether to keep a custom version synced with the original or offer changes back.
What happens on ignite
When a listing’s start criteria are met:
- A sponsor-private repo
vibeexchange/<listing-slug>is created in the org. - It’s seeded with
.roadmap/(scope + governance),.treasury/(the funding ledger),.harness/,.fleet/, and a starter scaffold. - Every released sponsor is added as a contributor.
- The current bridge can start Replicas/fleet supervision, open a PR, and report status back to VibeExchange.
- Branch protection, voting-bot checks, and webhook activity streaming are configured as the listing’s automation is enabled.
Roles → repo permissions
| Platform role | Repo permission | Why |
|---|---|---|
| Listing Creator | maintain | Drives day-to-day; governed merges still need the vote. |
| Lead Sponsor | write | Open PRs, review, vote-by-approval. |
| Sponsor (released) | triage or write | Issues + PR review/approval by default. |
| Conditional / Intent | none | Added only once released. |
| Staff | admin | Break-glass + moderation; logged. |
| Orchestrator bot | write | Commits and opens PRs; writes token-only run reports under .treasury/runs/. |
Issues & PRs
Sponsors can open issues and PRs like any contributor once they have repo access. Their vote on a governed PR is intended to be a weighted approval, see governance. Bot enforcement may still be staged for a listing.
Custom versions
A funded app can eventually support custom versions. Behind the scenes this maps to GitHub forks and pull requests. In the VibeExchange UI, the user-facing language should be simpler:
- customize this app;
- keep up with the original;
- evolve separately;
- offer this change back.
See custom versions & sync for the product model.
Privacy
Repos are private, but sponsors are real repo contributors, so the contributor list is visible to fellow sponsors by design. This is disclosed up front when you pledge.
These repos are for the funded apps, not the VibeExchange platform itself. The platform remains a private-source product built on open-source infrastructure we developed.
Status
Repo provisioning and the D1-backed build-status bridge are the current demo/live path for funded listings. Governance enforcement and activity webhooks may still be staged per listing. See rollout phases.