---
# System prepended metadata

title: 'Verification Frameworks v0 Scoping [Old]'

---

# Verification Frameworks v0 Scoping [Old]

:::success
just like minimum reviews/contributing guidelines on a PR but make it a contribution.
:::

## not goal

- Verification frameworks are NOT value or assigning value
- Verified contributions are NOT going to display on the dashboard
- VF's v0 are not touching staged contributions
- VF v0 does not touch curating the feed into seperate views
- PLEASE ADD EXCESS THINGS FROM R&D / PRODUCT SYNC
    - From [R & D sync](https://hackmd.io/eEKnixBIS-usdSRs4SB2ig):
    - Verification does NOT mean:
        - that the contribution was valuable, meaningful, or desired by the DAO
        - the ability or permission needed to associate a contribution with a DAO (currently any recruit or member can submit contributions to a DAO)

### Goal & User stories

As a whole, the v0 experience is meant to be very simple: a **verified** contribution gives a checkmark to a DAO's contributions on the tables (sometimes referred to as feeds). This both looks nice and enables for fine grained admin "control" over a DAO. the VF-v0 is meant to be a simple feature bundle that tees up research and gives us a base to launch more functionality. 

**Problem statement**

- Problem: Admins want to gate contributions and users want to know when their work joins the DAO 
- Solution: Build the admin framework; enhance delight on the user feeds (tables of contribution & attestations).

**As a DAO Admin**

- I need to see why verification frameworks can help my DAO
    - So that I can surface verified work and reduce spam
- I need to be able to set and adjust verification parameters on the fly
    - So that i can easily adjust to my contributors demands (keep settings current & adapt to current circumstances– e.g. spam or low effort contribution.)
- I need to be able explain and digest what a VF even is, simply and clearly.

**As a DAO member**

- I need to understand why acceptance to a DAO is powerful.
    - (what utility does this unlock for me and how do I experience it)
- I want to be able to curate (filter, sort, etc) my attestation feed 
    - So that I can easily see only verified contributions for my DAO.
- I want to attest to contributions and know how that pushes a DAO forward.
    - So that I can feel excited about pushing attestations over a threshold 
- I want to see that my DAO doesn't have verification, 
    - so that I can ask my admins why? or ask to become an admin to enable that function.
    - E.g., "we don't have a checkmark, why is that?"

**As a DAO recruit**

- I want the checkmarks on other contributions so that I can feel like I'm part of that DAO.
    - I want to feel verified so that my work is seen
    - I want to attest since there is a tab there that I can't engage with.
- I can't attest so I see the value of both attesting and feel delight when I engage as a member.

**UX As a DAO admin:**

![](https://hackmd.io/_uploads/Sk32waFhj.png)
- I set up verifications for my DAO on the DAO settings page.
- I can edit the verification numbers whenever i would like.

![](https://hackmd.io/_uploads/ByoXdaKho.png)
- I can choose one of the two frameworks  "top down" (only a number of admin attestations matter)
    
![](https://hackmd.io/_uploads/BkuCPTt3o.png)
- I also  can gate verifications by emergent (pure # of attestations from any DAO member)

**UX as admin, member, and recruit**
![](https://hackmd.io/_uploads/HyJIKTtno.png)

- I can see the verification of those contributions 
    - The Checkmark here would indicate your contribution acceptance into the DAO.

![](https://hackmd.io/_uploads/BJ9wY6K2s.png)

- If i hover on those tags and checkmarks, hover text indicates what is happening with the contribution.

![](https://hackmd.io/_uploads/ryeadkc2o.png)

- same hover experience on the attestation table.
- including a delightful exprience of accepting a contribution would be nice.
- I can explain verification to my DAO members
    - through`on.hover` helper text 
    - through Govrn's gitbook covering the feature
- I can delete my attestation if i accidentally attest. 

### Depedencies & Tech questions

**DAO Membership** :heavy_check_mark: 
**Multi-tagging in the tables for multiple DAOS and for multi contributions/attestations.**
**Taxonomy fixes**
**Seperating out what happened vs what is accurate on an attestation**
**Technical constraints**

- Can I delete my attestation if i accidentally attest?
- 


---
## Scope

### v0.0 light features to be technically specc-ed elsewhere

- Table updates & resolvers for multi-DAO and contribution by DAO
- A toggle or button on attestation itself that indicates "approve as admin"
- Tooltips and hover states everywhere
- Framework states for contributions
    - unverified
    - verified 
    - congrats it's accepted!
- Framework states for attestations
    - no of attestations remaining (plus counter schema)
    - final attestation
    - no framework
    - Attestation success!

### Later

- show "admin voted on" this sticker on the contributions/attestations feed [DAO dashboard].


## Technical design

- What new tables or columns do we need?
- Api endpoints
- hooks, resolvers 
    - anything we'll need to update for frontend?
- Schema
- New Infrastructure

Signoff

- [ ] Frontend 
- [ ] Architecture 
- [ ] Backend, API, hooks


### Frontend Spec

- hooks, resolvers anything we'll need to update for frontend?
- New components
- Libraries to install
- 

### Definition of Done

- ***Outline what is required to consider this project complete. It’s necessary to have alignment on the definition of done.***

## Metrics

- ***What metrics do you want enabled as part of this feature? Each metric should be related to answering at least one future question on how to adapt the feature***

##### Related Links

- [Initial project plan, concerns, UX and meeting notes.](https://hackmd.io/3n1RPq-kSSu6c34nWUwyaQ)
- [Project in Linear](https://linear.app/govrn/project/verification-framework-v0-31b8efb800e0)
- [Loom of admin experience](https://www.loom.com/share/7051212cc9564410be6350aff8329533)
- Loom of contributor experience

> we can make FOMO more apprent if we make public and private views of dashbaords; complete with copy that drives recruits towards membership.


## Tech Spec Sync Meeting 1: 2/7/23

- Initial purpose of adding a verification checkmark is straight forward but what is the impact on daily users?
- Verified contribution -> checkmark to a DAO's contributions
- What does gating solve / what is meant by gating?
  - Why would a DAO want to do this?
  - Surfacing of contributions that would eventually flow into value frameworks to prevent a flood of contributions that won't ever see value
- Admins/users surfacing contributions that are ready for value
  - Is it similar to a PR being accepted? 
  - Admin sets up threshold criteria for what is accepted
- Similar mental model for how an organization would set review thresholds on pull requests being accepted -> once accepted, these contributions are eligible for value assignment (in the future)
- Important to the user because they have increased clarity around what DAOs consider accepted contributions
  - **Clarifies expectations** around contributing to a DAO
- For DAO admins/core, this would prevent spam and reduce noise for value assignment inputs
- **benefit to user:**
  - clarity around expectations for what are accepted contributions (esp. with regard to value assignment)
- **benefit to dao core/admin:**
  - reduce noise of contribution inputs for value assignment
- What is the *why* for DAO admins?
  - *Why* add this to their DAO?
- What happens to previously verified contributions if a DAO shifts their framework?
  - Are they locked in at the time of acceptance OR are they fluid and if a DAO changes, the contribution loses the verification status?
- I want to be able to curate my attestation feed 
    - in the future options could include: curating the dashboard, financing levels of verified contributions, sharing thresholded 
- Curate: Filtering attestation feed by verified status
  - Recruits to be surfaced in the feed for DAOs
- Users will want to ping admins to set up a VF so that they have clearer expectations around what it means to be a contributor / inspires more confidence as a contributor *in* that DAO
- What user actions need to happen and what is the impact?
- What are the boundaries? What is in/out of scope?



Future iterations involve adjusting  at different levels (restructuring feeds to verified contributions only, accepting things into a different feed etc.). 0