Accepted contributor evidence
Show what accepted work delivered.
Contributor Value turns accepted default-branch changes into evidence-backed value receipts for capability created, value protected, complexity retired, and delivery enablement.
Every result keeps attribution, coverage, shared credit, and durability boundaries visible. It is designed for a developer record and an organization view, not an employee ranking.
Contribution evidence should reward useful outcomes, including code that gets smaller.
The ledger separates code movement from accepted value. New capability can earn credit, but so can verification, documentation, migrations, useful deletion, and lower structural pressure. Generated output, duplication, reversals, and discarded work are reduced or excluded.
The result is only useful if you can see what produced it.
Default-branch change groups
Measures work after it lands on the tracked branch, grouping complete accepted changes instead of treating every raw commit as an outcome.
New value-bearing behavior
Credits net-new authored source that contributes working product, platform, integration, or system capability.
Assurance and reliability
Credits visible tests, security, reliability, and verification work that protects existing implementation value.
Complexity retired
Credits useful deletion, refactoring, and structural improvement without assuming that every deletion is automatically valuable.
Shared delivery credit
Preserves co-authorship and supported enablement evidence so conserved value is allocated without creating duplicate credit.
Value retained over time
Tracks whether accepted change value remains supported, is revised, or is reversed while showing the evidence available for that conclusion.
From repository evidence to a readable record.
Connect the contributor and repositories
Map the verified GitHub identity to repositories the person or organization is permitted to track.
Measure accepted change evidence
Reconcile token flow, change type, attribution, structural movement, and evidence coverage for each accepted group.
Build the contributor ledger
Conserve shared credit, update retained value, and expose the underlying receipts in web and mobile views.
One evidence base, read from the right perspective.
Keep a portable record of accepted work.
Open the evidence behind a value receipt, follow retained value, and choose which milestones or aggregates become public.
- Per-change value receipts
- Repository and period breakdowns
- Private-work visibility controls
Read contribution evidence with context.
Review team and contributor delivery across the same period while preserving coverage, attribution, role, and non-code context.
- Conserved shared credit
- Repository and team rollups
- Explicit anti-ranking boundary
Clear evidence boundaries are part of the product.
Contributor Value is a bounded software-delivery estimate. It is not a judgment of a person’s talent, importance, compensation, or employment performance.
Commit count, lines changed, and gross token movement provide context but do not automatically increase accepted value.
Discovery, mentorship, customer work, incident response, planning, leadership, and other valuable work require separate context.
Questions
What Contributor Value does and does not represent.
The ledger measures accepted software delivery. It does not turn a developer into a score.
What work can receive Contributor Value?
Qualifying work must reach the tracked default branch and produce accepted value evidence. Capability, tests, security work, documentation, useful deletion, refactoring, migrations, and shared delivery can all contribute when the repository evidence supports them.
Do more commits or more tokens automatically create more value?
No. Commit count and token movement provide context, but duplication, generated output, discarded work, reversals, and unsupported volume do not automatically increase accepted value.
How are useful deletions handled?
The system separates removed code from rewritten code and evaluates the surrounding structural movement. A smaller codebase can deliver positive value when accepted work retires complexity or burden without removing needed capability.
Is Contributor Value an employee ranking?
No. It does not measure a person's talent, compensation, leadership, product judgment, mentorship, customer work, or overall performance. Organization views must be read with role, coverage, and non-repository context.
Can private contribution details stay private?
Yes. Repository and contribution details remain controlled by the authorized account. A user can keep private work private or share approved aggregates without exposing source code or private repository details.
Build the accepted-work record
Let every value total open back to its evidence.
Connect your repositories to begin tracking Contributor Value, retained work, and attribution coverage.