REPOSELL Listing — Gamification System
The main listing should feel like a living open-source directory where publishers, contributors and buyers build reputation through verifiable activity.
The constraint that rules all of it: gamification must never override verification, security or ranking integrity. A project cannot buy reputation.
Serverless by construction
The entire system runs without servers — through manifests + CI. XP events are generated exclusively by GitHub Actions (PR verification, scheduled health sweeps, release validation) and recorded as signed, append-only event files inside the listing repository. Git history makes the ledger immutable; profiles and leaderboards are static artifacts regenerated by scheduled workflows. Users cannot submit { "xp": 1000000 } — events only exist if CI wrote them.
1. Core principle
text
Real activity
↓
Verified events ← generated by CI, never self-reported
↓
Reputation / XP ← signed event ledger in git
↓
Levels + badges
↓
Profile reputation
↓
Limited discovery benefits
1
2
3
4
5
6
7
8
9
10
11
2
3
4
5
6
7
8
9
10
11
Never award points for arbitrary clicks, page views, fake forks, or self-reported activity.
2. Three gamified actors
| Actor | Who | Earns reputation by |
|---|---|---|
| 🧑💻 Publishers | Publish software through /sell | Maintaining high-quality products |
| 🔎 Curators / Contributors | Submit projects via PRs | Discovering and maintaining the catalog |
| 🛒 Buyers | Purchase products | Legitimate purchases and verified interactions |
3. Publisher XP
Measures quality and maintenance, not popularity:
| Action | XP |
|---|---|
| First verified product | +100 |
| New verified release | +25 |
| Successful health check | +5 |
| Maintain product 30 days | +25 |
| Maintain product 90 days | +75 |
Fix broken /sell | +25 |
| Add complete manifest | +20 |
| Add release documentation | +15 |
| Verified payment configuration | +20 |
| Successful buyer transaction | +10 |
| Verified review received | +5 |
| Product reaches 10 verified buyers | +50 |
| Product reaches 100 verified buyers | +250 |
Caps and anti-abuse apply: repeatedly redeploying the same release generates no infinite XP.
4. Curator / contributor XP
text
PR submitted → CI verification → PR merged → contributor receives XP
1
| Action | XP |
|---|---|
| Submit valid listing | +25 |
| Listing passes CI first try | +10 |
| Find broken listing | +20 |
| Submit valid correction | +15 |
| Update stale metadata | +10 |
| Remove dead listing | +20 |
| Maintain listing 30 days | +10 |
A community curation game — without giving contributors control over someone else's software.
5. Buyer XP
| Action | XP |
|---|---|
| First purchase | +50 |
| Purchase from new publisher | +20 |
| Purchases from 5 different publishers | +50 |
| Verified review | +10 |
| Helpful review | +20 |
| Report broken product | +15 |
| Report confirmed security issue | +100 |
Positive reviews are never rewarded — a 1-star and a 5-star review earn the same participation XP. Buyer XP derives only from verified settlement/transaction records.
6. Levels
text
Level 1 Explorer 0 XP
Level 2 Scout 100 XP
Level 3 Contributor 300 XP
Level 4 Curator 750 XP
Level 5 Builder 1,500 XP
Level 6 Maintainer 3,000 XP
Level 7 Architect 6,000 XP
Level 8 Pathfinder 12,000 XP
Level 9 Vanguard 25,000 XP
Level 10 Legend 50,000 XP
1
2
3
4
5
6
7
8
9
10
2
3
4
5
6
7
8
9
10
Names can be made more distinctive to Reposell later.
7. Product reputation — separate from person reputation
A product earns its own score from measurable signals:
text
Verification status · release health · maintenance
successful purchases · legitimate reviews · update frequency
documentation completeness · publisher reputation
1
2
3
2
3
Not: who paid the most, who has the most followers, who generated the most page views.
8. Product badges
Badges represent real achievements: 🟢 Verified · 🔄 Maintained · ⚡ Active · 🛡 Security Verified · 📦 Release Ready · 🌱 New · 🏆 Popular (verified purchases, not views) · 💎 Established · 🧭 Community Pick.
9. Verification badges ≠ reputation badges
Extremely important distinction:
text
VERIFIED ← objective, never purchasable, never XP-earned
✓ GitHub ownership verified
✓ Release verified
✓ /sell verified
✓ Manifest verified
✓ Payment link verified
✓ Signature verified
✓ Health check passed
1
2
3
4
5
6
7
8
2
3
4
5
6
7
8
versus:
text
LEVEL 7 · PATHFINDER · 12,430 XP ← pure gamification
1
10. Streaks run on /health
text
Daily/periodic CI → /health → PASS → streak continues
1
🔥 7 / 30 / 90 / 365-day maintenance streaks — based on actual automated health checks, never manual check-ins.
Failure path: FAIL → grace period → publisher notified → fixed within window → streak preserved. Temporary infrastructure failure must not unfairly destroy reputation.
11. Discovery rewards — controlled limits
Ranking may weigh:
text
normal ranking + quality signals + maintenance + community reputation
1
A high-level curator might carry a small "Trusted curator" signal — but XP is never equivalent to ranking, otherwise people optimize the game instead of building good software.
12. Community quests
Verifiable completion conditions only:
- 🔎 Find Broken Listings — find 10 listings with broken
/health - 🧹 Catalog Cleanup — help verify 25 stale listings
- 🆕 Discover — submit 5 new verified open-source products
- 🛠 Maintenance Week — help restore 20 unhealthy listings
- 🌎 Ecosystem Explorer — purchase from 10 different publishers
13. Seasonal events
Optional seasons ("REPOSELL SEASON 01 — THE FIRST WAVE") with seasonal ranks. Seasonal rewards never permanently distort reputation; historical achievements stay visible (🏆 Season 1 Top 10 Contributor).
14. Independent leaderboards
Separate boards per actor prevent cross-role gaming:
- Publishers: most maintained · most verified products · most successful releases
- Curators: top discoverers · top maintainers · top bug hunters
- Buyers: top explorers · top reviewers
Someone who buys 500 products does not become the best curator.
15. Anti-gaming architecture
XP comes from an immutable event system — every event is CI-generated and signed:
json
{
"event": "release_verified",
"subject": "repo/project@v1.5.0",
"actor": "github:user",
"timestamp": "...",
"verification": "passed",
"xp": 25,
"signature": "ed25519:..."
}
1
2
3
4
5
6
7
8
9
2
3
4
5
6
7
8
9
Explicit implementations:
- Diminishing rewards — repeated actions yield less/no XP
- Daily/weekly caps — blocks automated farming
- Unique-action requirements — a hundred re-releases don't farm XP
- Verified identities — actions map to real GitHub/payment/listing events
- Anti-self-dealing — publishers can't earn buyer XP on their own product
- Fraud reversal — refund/invalidation reverses the XP event
16. Reputation decay — done right
Lifetime XP never decays. Two numbers:
text
Lifetime XP: 18,420 ← historical contribution, forever
Current reputation: 92 ← reflects current behavior
1
2
2
A neglected product can lose its 🔄 Maintained badge without erasing its owner's history.
17. Trust tiers
text
Unverified → Verified → Established → Trusted → Highly Trusted
1
Trust ≠ XP. It combines identity verification, ownership verification, successful history, transaction history, security history, maintenance and community signals.
18. Gamification UI
Publisher profile:
text
┌─────────────────────────────────────┐
│ ENZO │
│ 🏆 ARCHITECT · 7,420 XP │
│ ████████████████░░░ 82% │
│ 🔥 94 day maintenance streak │
│ ✓ 12 verified products │
│ ✓ 48 verified releases │
│ ✓ 1,240 buyers │
└─────────────────────────────────────┘
1
2
3
4
5
6
7
8
9
2
3
4
5
6
7
8
9
Product page:
text
┌─────────────────────────────────────┐
│ My Awesome Package │
│ ✓ VERIFIED · 🔄 MAINTAINED · ⚡ ACTIVE │
│ ★ 4.8 · 1,240 verified buyers │
│ v2.4.1 · updated 3 days ago │
│ [ BUY — $50 ] │
└─────────────────────────────────────┘
1
2
3
4
5
6
7
2
3
4
5
6
7
19. The most important rule
Gamification never determines whether something is allowed to be listed.
text
SECURITY / TRUST
│
▼
Can it be listed? ── NO → blocked (see Release Model)
│ YES
▼
QUALITY SIGNALS
▼
DISCOVERY
▼
GAMIFICATION
1
2
3
4
5
6
7
8
9
10
11
2
3
4
5
6
7
8
9
10
11
Not XP → permission. Instead:
text
Verification → permission
Reputation → trust
Gamification → engagement
1
2
3
2
3
That separation keeps the listing from becoming a spammy points-system while making the ecosystem feel alive, competitive and fun.
Related: The Listing Network (gamification of community listing operators) · Listing Registry (the PR pipeline generating curator events) · Release Model (the verification gates behind every badge).