Design requirements for a Badges feature

Behaviors to recognize:

- Volunteers for community roles. (ex: "Club Secretary 2022-2024")
- Attending community events. (ex: "2016 Spring Meetup Attendee")
- Recognitions by community (ex: "Person of the Year")
- Achievements defined by the community (ex: "Completed a certification program")
- Other time investments in the community
- Considerations for a new badge:

Is this badge self-assigned, requested, or awarded? (Automation is out of scope for now)

- Who approves requests / awards it?
- Does the badge "group" with others? (ex: annual event)
- Does the badge "stack" with others, and do we only care about the latest/highest?
- Can you repeat the badge and what limits are there?
- Does the badge have functionality attached? (ex: unlocking a privilege)
- What meta is relevant? (ex: day/year awarded)

What needs to be done?

- [ ] Finalize scope of badges we're trying to enable (above)
- [ ] Product requirements for first iteration of the feature
- [ ] Mockups of workflows to create, request, view, and award a badge.