Recognition
Optional endorsements of paid work, season scores, and badge drafts — off until an admin turns it on.
Recognition is an optional module for celebrating higher-quality work. It is off until an admin turns it on under Recognition in the community settings. It never changes payouts, budgets, who may sign a treasury transaction, or membership roles.
Turning it on
Admins open Recognition in the sidebar (settings). Enable the module, pick a season cadence (quarter or month), and set how many endorsements each lead or admin may grant per season. Presets (Quiet, Standard, Loud) fill sensible knobs; you can still edit them afterward.
Turning recognition off hides the season board and refuses new endorsements. Past events stay in the community's history.
Endorsing paid work
On a paid or reconciled task, admins and leads of that workgroup can Endorse each assignee's wallet from the task dialog. Call attendance tasks cannot be endorsed. You cannot endorse yourself. Each assignee may have one active endorsement per task; a mistaken endorsement can be Revoked (by the grantor or an admin).
A short optional note explains why the work stood out. Each actor has a season budget of endorsements — remaining count is shown in the dialog.
Peer kudos
When Allow peer kudos is on, any member who meets the membership-age rule may give Kudos on a paid task assignee (separate from lead endorsements, with a lower score weight). Reciprocal kudos in a short window do not count toward the season score.
Season board and score
The season board (linked from Recognition settings when the module is on) lists wallets and their season score. Score is built only from recognition events: 3 points per active endorsement, 0.25 per counting peer kudos. ADA paid never enters the formula.
Tiers: Noted (1–2), Craft (3–5), Exemplar (6+). The leaderboard ranking is optional (Show season leaderboard); when off, the page still lists people with scores without numbered places.
Recognized contributors as voters
With Offer “Recognized contributors” as a proposal electorate on, admins may choose that electorate under Governance settings for a proposal kind. At voting open, members who meet the minimum recognition score in the look-back window (and the usual membership-age rule) are snapshotted — still one member, one vote. If recognition is off or that option is unchecked, the electorate is empty, so only turn it on when the module is in use.
Season badge drafts
Admins on the season board can Download badge drafts for Exemplar wallets: JSON metadata suggestions for NFTs. Mint them under the treasury policy on Mint like any other NFT (several per transaction). Recognition never auto-mints or spends treasury funds for badges.
What recognition is not
- Not a substitute for marking a task payable or paying it
- Not token-gated membership or admin rights
- Not a claim on the treasury