# Milestone Structure Requirements

Each milestone submission must include the following mandatory components.

### A. Milestone Title

* Format: `M[Number]: [Concise Description]`
* Example: `M1: Mainnet Launch with Core DEX Features`
* Max 80 characters

### B. Detailed Description

Comprehensive explanation including:

* What will be delivered
* Why it matters to the project
* How it advances the roadmap
* Dependencies on previous milestones (if any)

Length: 200-500 words

### C. Completion Criteria (Critical)

Minimum 3, maximum 8 objective criteria per milestone.

Format:

```
1. [Metric] [Operator] [Target Value] [Source]
2. [Metric] [Operator] [Target Value] [Source]
3. [Feature/Deliverable] is [Status] as verified by [Method]
```

Examples:

✅ GOOD:

```
1. Mainnet smart contract deployed at [address] on Ethereum, verified on Etherscan
2. Minimum 5,000 unique wallet addresses interact with protocol within 30 days of launch
3. TVL ≥ $500,000 sustained for 7 consecutive days, verified via DeFiLlama
4. Swap functionality executes ≥100 successful transactions with average slippage <0.5%
5. GitHub repository contains ≥50 commits in last 30 days with at least 3 active contributors
```

❌ BAD:

```
1. Launch mainnet (too vague)
2. Achieve good TVL (not measurable)
3. Community is satisfied (subjective)
4. Complete development (ambiguous)
```

### D. Evidence Package Requirements

Specify exactly what evidence must be submitted.

For Technical Milestones:

* Contract addresses with block numbers
* GitHub repository links with specific commit ranges
* Deployment transaction hashes
* API endpoints for verification
* Screenshots/screen recordings (timestamped, with visible URLs)

For Traction/Metrics Milestones:

* Data source links (DeFiLlama, Dune Analytics, blockchain explorers)
* Query/API parameters for reproducibility
* Time period specification (UTC timezone)
* Methodology for calculation

For Partnership/Integration Milestones:

* Official announcement links from both parties
* Integration test transaction hashes
* Joint marketing materials (dated)
* Technical documentation of integration

### E. Timeline

* **Deadline**: Exact date and time (UTC)
* **Estimated Start Date**: When work begins
* **Buffer Period**: Recommended 10-20% time buffer
* **Dependencies**: List any prerequisite milestones

### F. Funding Allocation

* **Percentage of Total Raise**: X%
* **Dollar Amount**: $XXX,XXX USDC
* **Justification**: Brief explanation of why this amount is needed for this milestone

### G. Risk Disclosures

Projects must disclose:

* External dependencies (third-party protocols, services)
* Technical risks (unaudited code, experimental features)
* Market risks (requires specific token price/TVL)
* Regulatory risks (jurisdiction-dependent features)

Format:

```
RISK LEVEL: [Low/Medium/High]
- Risk 1: [Description] | Mitigation: [Strategy]
- Risk 2: [Description] | Mitigation: [Strategy]
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.seedify.fund/milestone-guidance-criteria/milestone-structure-requirements.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.