Getting started
Core concepts
A short glossary. Everything else in these docs builds on these terms.
Bounty
A single, scoped unit of work (30 minutes to ~4 hours) posted by a founder — a bug fix, a landing-page section, a Figma-to-React conversion. It carries a fixed budget in ₹, a time estimate, a tech stack, an XP reward, and a file scope.
PR submission
Work is always delivered as a pull request — never a ZIP or a link dump. You work in a Forke-managed branch and fill out a structured FORKE_SUBMISSION.md before opening the PR.
Escrow
The founder deposits the budget up front via Razorpay. Funds are held by Forke and released to your UPI automatically the moment the work is approved — so the money is provably there before you start.
3D access
Every bounty has three gates, and all three must pass before you can claim it:
| Dimension | Measures |
|---|---|
| Level | Platform experience & consistency (LVL 1–25) |
| Skill tier | Technical depth in a track (Frontend, Backend, …) |
| Trust score | Professional reliability (completion, deadlines, ratings) |
Eligibility = Level ∩ Skill Tier ∩ Trust Score — credentials you can't fake by editing a resume.To make that concrete: a production payment-integration task might require Level 12+, a Fullstack tier of 3+, and a trust score above 85%. A developer who meets two of the three won't even see the task in their feed. This is what gives a founder structural confidence — when a React task reaches a developer, that developer has proven they can do React, not just ticked a box. See skill tracks and trust score for how each gate is computed.
Proof of work
Every approved task appears on your public profile, timestamped and linked to the merged GitHub PR. Both you and Forke show up as contributors on the owner's upstream repo. The guiding philosophy: “Prove skill by shipping. Your profile is your reputation.” — see Profile & proof of work.