# **Project Roadmap and PRD for a Task Protocol Score (TPS) Calculator MVP**

---

## **Universal Role Definitions**

### **1. Creator**
- **Core Function**: Gathers or generates the raw materials, data, ideas, or resources needed to initiate workflows.
- **Essential Nature**: The Creator provides the **inputs** that fuel the system. Without this role, no foundational material exists for further processes.
- **Examples Across Domains**:
- **Environmental**: Collects geotagged data, surveys biodiversity, or reports waste locations.
- **Web3**: Writes code, submits governance proposals, or designs NFTs.
- **Community**: Provides feedback, shares ideas, or moderates discussions.

---

### **2. Validator**
- **Core Function**: Ensures the quality, relevance, and accuracy of the Creator’s outputs.
- **Essential Nature**: The Validator acts as the **gatekeeper**, protecting the system from errors, inefficiencies, or misinformation.
- **Examples Across Domains**:
- **Environmental**: Verifies geotagged data, checks species accuracy, or validates planting plans.
- **Web3**: Reviews pull requests, audits smart contracts, or analyzes proposal feasibility.
- **Community**: Summarizes insights, validates survey data, or moderates proposals for alignment.

---

### **3. Executor**
- **Core Function**: Implements the validated outputs, translating them into measurable actions or results.
- **Essential Nature**: The Executor ensures the system’s **outputs** lead to real-world or operational outcomes.
- **Examples Across Domains**:
- **Environmental**: Plants trees, organizes cleanup drives, or monitors restored areas.
- **Web3**: Deploys smart contracts, sets up infrastructure, or manages treasury allocations.
- **Community**: Hosts events, manages onboarding, or executes campaigns.

---

## **How These Roles Work Together**
These roles are **interdependent** and reflect the lifecycle of any contribution-based system:
1. **Creators** provide the raw inputs that initiate the process.
2. **Validators** refine and ensure the quality of these inputs, transforming them into actionable outputs.
3. **Executors** implement these outputs, closing the loop and producing measurable outcomes.

---

## **Mathematical Representation in TPS**


### **Inputs for the Equation**
1. **Contribution Quality (\text{Task Quality}_i)**:
- A normalized score (0–100%) based on the task’s relevance, accuracy, and completeness.
- Determined by peer reviews, automated checks, or objective metrics.

2. **Role Weight (\text{Role Weight}_i)**:
- Reflects the importance of the role to the overall workflow:
- Creators: **1.0** (provide foundational inputs).
- Validators: **1.5** (ensure quality and usability).
- Executors: **2.0** (deliver tangible results).

3. **Impact Multiplier (\text{Impact Multiplier}_i)**:
- Adjusts for the significance of the workflow or campaign:
- Standard impact = **1.0**.
- High impact (e.g., critical workflows) = **1.5**.

4. **Max Possible Score**:
- Theoretical maximum score, calculated based on the number of tasks, role weights, and impact multipliers.

---

## **Generalized Application of Roles**

### **1. In Web3**
- **Creators**: Write proposals, design NFTs, or submit code.
- **Validators**: Review proposals, audit contracts, or curate NFT collections.
- **Executors**: Deploy contracts, host NFT drops, or launch governance votes.

### **2. In Environmental Restoration**
- **Creators**: Map degraded areas, collect biodiversity data, or identify waste hotspots.
- **Validators**: Verify species IDs, analyze geospatial data, or validate waste reports.
- **Executors**: Plant trees, clean rivers, or monitor wildlife recovery.

### **3. In DAOs**
- **Creators**: Submit ideas, proposals, or reports.
- **Validators**: Analyze proposals, provide feedback, or verify implementation plans.
- **Executors**: Implement governance decisions, allocate funds, or build infrastructure.

---

## **Project Roadmap**

### **Phase 1: Ideation and Design**
- **Duration**: 2 weeks
- **Goals**:
1. Define the minimum functionality of the TPS calculator.
2. Design a simple scoring formula for user testing.
3. Create UI/UX wireframes for the calculator interface.

---

### **Phase 2: Development of Core Functionality**
- **Duration**: 4 weeks
- **Goals**:
1. Build a basic input system for users to log their tasks and roles.
2. Implement the TPS calculation engine.
3. Add simple peer review and automated validation processes.

---

### **Phase 3: Beta Testing and Feedback**
- **Duration**: 3 weeks
- **Goals**:
1. Deploy the MVP to a small group of users for feedback.
2. Gather data on usability and scoring accuracy.
3. Refine the system based on user feedback.

---

### **Phase 4: Public Launch**
- **Duration**: 2 weeks
- **Goals**:
1. Deploy the TPS calculator MVP for public use.
2. Monitor performance and user engagement.
3. Identify areas for future improvement and expansion.

---

## **Product Requirements Document (PRD)**

### **1. Introduction**
#### **Purpose**
To create a simple and accessible Task Protocol Score (TPS) Calculator MVP that enables individuals or teams to calculate TPS for their contributions in a workflow, based on the quality, weight, and impact of their tasks.

#### **Scope**
This MVP will focus on:
- A core calculation system for TPS.
- User-friendly input forms for logging tasks.
- Outputs in a percentage format for simplicity and interoperability.

---

### **2. Objectives**
1. Provide a functional interface for users to input task details.
2. Automate the calculation of TPS using the defined formula.
3. Allow basic peer review for task evaluation.
4. Output clear and transparent TPS results in a percentage format.

---

### **3. Features**

#### **Core Features for the MVP**
1. **Task Logging System**:
- Users can log their tasks with details such as:
- Role: Creator, Validator, Executor.
- Task Type: Customizable based on user needs.
- Quality Inputs: Peer review scores or automated validations.
- Metadata: Timestamp, associated files, etc.

2. **TPS Calculation Engine**:
- Implements the core formula:


3. **Peer Review System**:
- Allows other users to evaluate task quality.
- Simple 0–100% rating system with optional comments.

4. **Dashboard for Results**:
- Displays TPS scores for users and workflows.
- Includes breakdowns by task type and role.

#### **Stretch Features for Later Phases**
1. Integration with blockchain for task verification and rewards.
2. Advanced analytics for comparing TPS across users or workflows.
3. Reputation-building features based on cumulative TPS.