Records · Contributions · Policy
How contribution is scored
The categories of work, how each is verified, and how points are shared out. Changes apply from a future period onward. Past periods are never re-scored.
Rules
- Each period has a fixed budget of points per category. Categories never compete with each other.
- One account can take at most its category's cap. What a cap cuts off stays unallocated.
- Changes apply from a future period onward. Past periods are never re-scored.
- Governance cannot award or remove points for a named account. No such function exists.
- No input to the score is an AXON balance, an AXON reward or a stake weight.
Categories
design Each category has its own share of a period's points, and a cap on what one account can take.
| # | Category | Evidence | How it is verified | Units | Budget | Cap per account |
|---|---|---|---|---|---|---|
| 1 | Infrastructure | finalized node-state leaf from a settled epoch | cryptographic and automated: signed receipts, drawn witnesses, challenge window | share of each service's slice | 40% | 20% |
| 2 | Software development | merged commit or pull request in a designated repository | automated checks, then 2-of-3 maintainers assign a size | S 1, M 3, L 8, XL 20 | 25% | 30% |
| 3 | Code review | substantive reviews on merged pull requests | automated count, 10% audit sample by a maintainer | 1 per review, max 20 | 5% | 30% |
| 4 | Security findings | advisory commitment, revealed after the fix | security panel, 3-of-5, by severity rubric | Low 2, Medium 8, High 25, Critical 60 | 10% | 50% |
| 5 | Moderation and disputes | witness verdicts that match the final outcome; upheld reports | automated from chain records | 1 per correct verdict or upheld report | 10% | 20% |
| 6 | Apps and integrations | milestone: repository, live deployment, spec | peer review, 2-of-3 | S 2, M 6, L 15 | 5% | 40% |
| 7 | Research and documentation | merged document, published paper or design | peer review, 2-of-3 | S 1, M 3, L 8 | 5% | 40% |
Governance participation is counted only toward its own share of voting weight. It is not a contribution category.
The formula
For each period and category: the category's budget is shared in proportion to finalized units, scaled down when a category is quiet, and capped per account. What a cap cuts off stays unallocated.
budget_c = periodPoints × budgetShare_c effective = budget_c × min(units_c, minUnits_c) / minUnits_c points_c(a) = min(effective × units_c(a) / units_c, cap_c × budget_c)
Policy versions
A version never changes once set. It applies from the period it is scheduled for, never to a period already under way.
No policy version has been set. The values above are the design, not a deployed policy.
Sealed periods
No period has been sealed. A sealed period records which policy version scored it.