Priority 0 (proposed in 1/21/2024)

1. P0 - Improve label and transaction coverage
   1. discuss with partners to learn their contribution plan and any improvement this year
   2. reach out to more partners
   3. brainstorm together what sources (social media, websites, open source, etc) we can scrape more labels
   4. Metrics - COVERAGE
2. P0 - Attestation
   1. SDK work will unlock many other high-priority goals
   2. Private labels
   3. Metrics - Correctness, 100% onboarding
3. P1 - Further Label Transparency
   1. Every partner needs more info. When returning API and saying a label’s source is heuristics, make one more step to provide a link so the user can click on it to learn more about it. The link can be an academic paper about these heuristics, an analysis in Git Hub, a corporate webpage, or anything that describes the heuristics and to what extent users can learn more about it. Such link column also applies to other options such as ground truth, making it clear how the ground truth work is operated, or 3P to specify which platform and how the label is scraped.
   2. Metrics - lineage coverage reaches to XX% of new labels
4. P1 -Label Governance
   1. Create a mechanism so partners can contribute blurry labels
      1. need further discussion with the partner to agree on the mechanism
      2. Metrics - adoption
   2. Can define the scopes of labels that a user can see in at least two dimensions
      1. dimension 1: whether you can see fresh labels or 3 monthly old ones
      2. dimension 2: whether can see the CDA or other high risk sensitive label
5. Discussion:
   1. Should a microscope be the custodian for private labels?
   2. Should we have public service SLA
6. DRIs
   1. Ming to drive 1, 3 and 4 and delegate as needed
   2. Zhanwu to drive 2

Priority 1