What this project would ship
- A
claimstable keyed by(project_id, claimant_user_id)with status enum (active,expired,submitted,accepted,rejected). - Submission flow: claimant points at an artifact (PR URL, uploaded file, linked external work) and marks the claim submitted.
- Acceptance flow: founders (or eventually a reviewer pool) accept, partial-credit, or reject. Acceptance triggers credit accrual to the claimant's balance.
- Status transitions reflected on the public project page so the audit trail of who did what is legible.
Why this is currently proposed not open
Entry 016 commits to the gateway in principle, but G-038 leaves the mechanics open: identity requirements at claim time, acceptance gates, calibration-challenge flow, anti-gaming posture. None of these can ship without first being decided. This project waits on those.
What unblocks moving to open
A G-038 update specifying:
- Claim semantics (FCFS / time-boxed / multi-claimant).
- Identity floor (registration only vs verified email/GitHub).
- Acceptance flow (who, what gates, partial-credit handling).
- Calibration-challenge mechanism.
- Anti-gaming layer (account age, prior history, founder veto).
Why this matters
Without this, the contributor sovereignty principle (Entry 005) remains rhetorical. The roadmap publishing the work is necessary but not sufficient. The credit-earning gateway is the load-bearing piece.