---
# System prepended metadata

title: GR12 Scope of Work

---

# GR12 Scope of Work

## References

-  https://lucid.app/lucidchart/9dc7a462-563a-44c8-9b67-6c764f19a0d9/edit?page=LdX0TIjVlAQJ&invitationId=inv_f3a5ad14-c50b-466f-b558-1a59a43e813e#

## Nomenclature

- SDOP: Sybil Detection Operationalized Process

## Scope of Work (to be discussed)

- Iterate on the SDOP functions, mainly
    - Defining the Sybil Survey I/O
        - Consists of written rationale, playbook and diagram
    - Defining the SDOP Feature Engineering backlog
        - Define clearly what is the "Observations Backlog" and how to use it
        - Define clearly what is the "Feature Backlog" and how to use it
    - Iterating on the SDOP app architecture
        - Involves making sure that the SDOP codebase is scalable and easily re-usable. Can require code refactoring and/or changing the hosting platform
- Defining a Onboarding Process on the SDOP ML Model Development
    - Can include technical work for making sure that the interfaces of work are clear
    - May require defining roles, responsabilities and interfaces
    - In terms of deliverables, this is equivalent to have a written guide for each role + a overview
- Sketch the "Community Inteligence" workstream in terms of goals, functions and roles.
    - Equivalent to have a written statement about what CI is
    - Fraud tax should belong here
- Define core deliverables for the Data-Ops workstream in terms of artifacts and I/O with other workstreams
    - This is a doc that tells how a data archictecture should look like, and who are going to be their typical consumers / mantainers
- Define and sketch products for the FDD / Data Science, including
    - Live Fraud Detection Public Dashboard
    - Round Statistics Dashboard
    - Fraud Metrics Over Round History Dashboard
    - One doc and one sketch for each product