Milestone Change Requests

The IMO framework supports two types of change requests to handle real-world complexity:

Pre-Submission Milestone Change Requests

Requests made before milestone evidence submission deadline.

Supported Cases:

1. Pivot - Strategic direction change

2. Milestone Delay (Single) - Delay one specific milestone

3. Milestone Delay (All Remaining) - Delay all future milestones

4. Early Release (Single) - Request early release for one milestone

5. Early Release (Multiple) - Request early release for multiple milestones

6. Partial Release - Request partial fund release for a milestone

Process:

For Cases 1, 2, 3, 6:

1. Project submits justification according to Milestone Guidance Criteria

2. Seedify (or Council) reviews the case (7 days)

3. Community votes on DeXe (7 days)

4. If Approved:

   • Cases 1, 2, 3: Milestone conditions are modified

   • Case 6: Next milestone becomes partial, remainder distributed proportionally to other milestones

5. If Denied: Original milestone roadmap stands

For Cases 4, 5 (Early Release):

1. Project submits justification

2. Community votes on DeXe (7 days)

3. If Approved: Funds and tokens released early

4. If Denied: Original milestone schedule stands

---

Post-Voting Milestone Change Requests

Requests made after Community voting has concluded.

Supported Cases:

1. Dispute - Challenge to Oracle, Seedify, or Community verdict

2. Partial Release - Request partial payment post-decision

Process:

1. Project or stakeholder initiates dispute/request

2. AI assists in initial dispute evaluation

3. Seedify reviews and submits report to Community (7 days)

4. Community votes on DeXe (7 days)

5. If Approved:

   • Case 1 (Dispute): Milestone funds and tokens released, original roadmap continues

   • Case 2 (Partial Release): Current milestone becomes partial, remainder distributed proportionally

6. If Denied: Original Community vote stands