## Badges

In the burgeoning Web3 space, reputational baggage is not something you can carry with you the way that you can in the irl world. In irl companies keep an employee file, which quite often the employee never gets a chance to see what is in their file. If the employee were to leave that company they may wish to include that company on their resume as experience. It may well be that HR at the company you are trying to get hired at, calls the compaines that are listed on the resume to inquire about the employee.

Out of fear of civil litigation, most companies will not share this information, but they can. The way they would do this is by bringing up the old employee file to see what is there. If there are unflattering items in the file, this may cost that employee the job they are looking for and you are left wondering why.

The problem here, is that a reputation "score" was given to you and you have no control over that, you didn't even know there was a negative mark in your file. Was it something you actually did? Was it a disgruntled manager that was having a bad day? Either way, it has now cost you with little chance of recovery.

The promise of Web3 has been a promise of user controlled data. In a decentralized world reputatin can be handled differently, in a way that that you can now control your reputation in the space with various onchain methods. For example, somebodey can easily look up a persons ethereum wallet and see all the transactions that someone has made. This can give a lot of information to the trained eye, however it is an incomplete story for the work that somebodey may have done.

Much of the work in Web3 is done off chain. It's done on Discord, twitter or any number of communications media. It's done in HackMD, github and Google sheets. In Web3 there isn't a central point in which to track reputation and skills of potential employees. There isn't a filing cabinet stuffed with duty files HR can pull out to see who you are. In Web3 we use our wallets.

So if a wallet is the new filing cabinet, storing past accomplishments, attendance at events or reward for learning a new skill, then NFTs are the new records of these accomplishments. DAO Masons intend to use NFT badges in order to track reputation and reward new skills.

Badges within DAO Mason are ear

[]

### Projects
// rewrite so it reflect skill reputation as opposed to overall rep //
**Who:** Project Contributors, Role Badge
**What:** Badge (SBT)
**When:** Project Completion (or at PL's discretion)
**Reputation:** Roles will have ~~predetermined~~ reputation points assigned. When NFT is minted the points will be included in the metadata and added to someones total reputation score. PL will recomend point amounts and will be approved by DAO.
**How:** Project Lead or approved admin Mints and distributes
**Architecture:** Corinthian

Example:
Project completes. Project Lead mints an SBT. SBT should hold meta data containing the project and the role the person held in the project.

Benefits:
* Role definitions give project contributors clear domains within which to operate
* Project Lead can anchor expectations based on Role definitions, removing some subjectivity
* Leads into assessment & reward mechanisms so contributors can be recognized for their contributions

### Community
// possibly just fun badges //
**Who:** Community Members
**What:** Badge (SBT)
**When**: A role achieved or other DAO-decided parameter
**Reputation:** Roles will have ~~predetermined~~ reputation points assigned. When NFT is minted the points will be included in the metadata and added to someones ~~total reputation score~~. Points will be decided by the DAO.
**How:** Decided via DAO governance
**Architecture:** Doric

Examples:
DAO votes to promote a community member to moderator of Discord and awards an SBT to the individual.
Dyno Bot is set to give an autorole at a person's 1000th post. The DAO could then send that individual an SBT.

### Knowledge

**Who:** Questers
**What:** Badge (SBT)
**When:** Quest Completion
**Reputation:** Reputation points will be determined as part of the quest proposal.
**How:** Quest Leader or other pre-decided method
**Architecture:** Ionic

Example:

Person A proposes a quest to spend 30 days learning Solidity, with weekly check-ins to show progress. (etc etc I could go on forever here I think).
At the end of thirty days, the quest leader distributes SBTs to those that completed the quest.

## Reputation and Roles

This topic was made into a seperate doc, which details how the role structure within thwe DAO could look like.

[Reputation and Roles](https://hackmd.io/@boilerrat/rJINumJjs/edit)

---


___

### Project Flow as it relates to Badges and Roles

- Project Lead Proposes Project (This also works for quests as well). With the proposal should have the following info:
- Roles Required
~~- Role Reputation Weight~~
- ~~DAO holds a discussion period where proposed amendments to the project, including role weights are decided via consensus. ~~
- Project is sent onchain for vote. (DAO may prefer more agile methods at the start)
- Yes
- Project Proceeds
- Project Initialized
- Roles filled and assigned
- No
- Project Ends

- If roles are still required the search for a contractor takes place. It will be up to the project manager in consult with PL, to decide if the project can proceed until all roles are filled.

- Project contributors sign a CLOU for the project. (This can be a pared down version of our DAO CLOU)
// possibly have sign on to project scope/doc //

- Work Proceeds

**Project Conclusion**
- Project Review, with all stakeholders
- Project Completion report prepared.(included reputation assesments)
- Report sent to DAO
- DAO votes:
- Yes
- Funds Distributed
- Metadata added to SBT
- SBT Minted
- SBT Distributed
- Reputation Score Updated
- No
- Return to Product Review

[](https://mermaid.live/edit#pako:eNp1k11v2jAUhv-K5StHoghKvpqLSYSUlpYAJe2mjfTCwx71msSR42xrCf99xk5pNm25sf0-7znHPrH3cMsJhQHcCVw-gfsoLYD6xpuV4N_pVoI5xeQRnJ19aN4UNZa8wlkDQhSNl5aJCI8eMNl_5JJWB6NNdNyCNyBCCL3FJ5KXlmV1LZ9p1YDLU81ZwSTDGXvFkvHi0TgvdYHpZs0zWoFxVbFdQUkLpxpenTJM5ssHkHQdV9pxvfnExTMI6Y4VVUuuNZm9x_K8zGin8kwbbk4HWNMfjP5sD3Cj4S16j1K85EK2_FbzsNuk-R9NmmstRgtudYUFUk1pldhswCwWumMxlZhgiQEmhBIgOUjC-wYskRoqELNCUtJGL3X0ypCIVVKwr_Xf-A6pXddSNxwkWy4oeChVgZNNlwVrNK0L8q80a82T__3nlcFmcWcWsAdzKnLMiLp_-yNKoXyiOU1hoKYEi-cUpsVB-XAtefJSbGEgRU17sNZ7ixhW1zaHwTecVUotcQGDPfwFg_NR3x06nj_0fHvgeO7Q68GXozzou44_8l01s13fcw49-Mq5SjHoexcXQ9-xXXtk-wqd63xfNDRFKWGSi9i8F_1sDr8BpWfzBA)

### Modifying Roles

Sometimes roles will surface over the course of different projects. As our processes become more efficient and streamlined, this will likely decrease over time. In this proposal it is recomended to provide role clarity and weighting to the best of the PLs ability during the project proposal phase.

Do to expediency of shipping projects, due to the trust given to the DAO to the project manager, it would be appropriate to follow their judgment in any role adjustments over the course of the project. However, reputation points should be a DAO decision because it is the DAOs reputation that is a sum of all the reputation contributors have accumulated.

The PM may make the required role adjustments and then it will be their responsibility to propose the weighting adjustments to the DAO to vote on.

#### Todo

- Create a retrospective checklist for project completion that includes looking at the defined roles & determining Badge assignments**