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.
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) and.treasury/(the funding ledger), plus a starter scaffold. - Every released sponsor is added as a contributor.
- Branch protection is configured so governed merges require the voting bot’s check.
- Webhooks stream PRs, issues, and releases back to the listing’s activity feed.
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, opens PRs, writes .treasury/. |
Issues & PRs
Sponsors can open issues and PRs like any contributor. Their vote on a governed PR is a weighted approval — see governance.
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 is Phase 2. Today, listings show a placeholder until they ignite. See rollout phases.