# Prohibited Milestone Types

The following milestone types are NOT ALLOWED:

1. Subjective Quality Assessments

* ❌ "Launch high-quality product"
* ❌ "Achieve good user experience"
* ❌ "Build strong community"
* ❌ "Deliver professional-grade design"

2. Effort-Based (Not Outcome-Based)

* ❌ "Work on development for 3 months"
* ❌ "Hold 10 community calls"
* ❌ "Attend 5 conferences"

3. Circular/Self-Referential Metrics

* ❌ "Token price reaches $X" (price depends on milestone passing)
* ❌ "Market cap of $X million"
* ❌ "Achieve X% APY" (often manipulable)

4. Easily Manipulable Metrics

* ❌ "10,000 Twitter followers" (can buy bots)
* ❌ "100,000 website visits" (can fake traffic)
* ❌ "50 Telegram members" (can create fake accounts)

Exception: Social metrics allowed if combined with engagement metrics: ✅ "10,000 Twitter followers with ≥2% engagement rate on last 20 posts"

5. Vague Technical Terms

* ❌ "Complete smart contract development"
* ❌ "Finish backend infrastructure"
* ❌ "Implement advanced features"

6. Dependency on External Parties Without Alternatives

* ❌ "Integrate with Protocol X" (if Protocol X is single point of failure)

Correct Format: ✅ "Integrate with Protocol X OR Protocol Y OR equivalent DEX infrastructure"

7. Binary Pass/Fail for Complex Deliverables

* ❌ "Launch marketplace with all features"

Correct Format: ✅ Break into sub-milestones:

* M2a: Launch marketplace core (listing, buying, selling)
* M2b: Add advanced features (auctions, royalties, bundling)


---

# 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/prohibited-milestone-types.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.