Audit contribution points against actual decisions
Treat recognition as an accounting question: every balance should be explainable from accepted work and documented reversals.
Context and provenance
Choose a contributor and list their approved submission IDs. In this edition, each approval creates one ten-point ledger entry; a withdrawal creates one negative ten-point reversal. Compare that trail with the displayed total. Look for a second award for the same record, a public item with no award or a withdrawn item that still contributes to the leaderboard.
Test the workflow with a clearly labeled temporary contribution in an isolated test database. Approve it twice and confirm that the balance changes once. Withdraw it twice and confirm one reversal. Reopen the user account after a server restart. These checks target different failure modes: repeated actions, stale interface state and missing durable storage.
Keep the audit result and any correction tied to record IDs rather than changing a score by hand without explanation. Browser reading XP and server contribution points belong to different systems and should not be added together. Neither represents money, a guaranteed reward or a claim on future tokens. Recognition remains useful when another person can reconstruct why it was earned.
Sources and evidence
Editorial review: 2026-09-23. New evidence may change this account.