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.

Designed, not live. These are the design's starting values (doc/ownership/05). ContributionPolicy, the contract that would hold them, is not deployed, and governance would set the real values through Timelock P.

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.

#CategoryEvidenceHow it is verifiedUnitsBudgetCap per account
1Infrastructurefinalized node-state leaf from a settled epochcryptographic and automated: signed receipts, drawn witnesses, challenge window share of each service's slice40%20%
2Software developmentmerged commit or pull request in a designated repositoryautomated checks, then 2-of-3 maintainers assign a size S 1, M 3, L 8, XL 2025%30%
3Code reviewsubstantive reviews on merged pull requestsautomated count, 10% audit sample by a maintainer 1 per review, max 205%30%
4Security findingsadvisory commitment, revealed after the fixsecurity panel, 3-of-5, by severity rubric Low 2, Medium 8, High 25, Critical 6010%50%
5Moderation and disputeswitness verdicts that match the final outcome; upheld reportsautomated from chain records 1 per correct verdict or upheld report10%20%
6Apps and integrationsmilestone: repository, live deployment, specpeer review, 2-of-3 S 2, M 6, L 155%40%
7Research and documentationmerged document, published paper or designpeer review, 2-of-3 S 1, M 3, L 85%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.

ContributionPolicy is not deployed.

No policy version has been set. The values above are the design, not a deployed policy.

Sealed periods

ReputationLedger is not deployed.

No period has been sealed. A sealed period records which policy version scored it.