> For the complete documentation index, see [llms.txt](https://docs.flock.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flock.io/flock-products/fomo/quickstart/fundraise-outcomes.md).
# Fundraise Outcomes
After 7 days of fundraise, one of the following paths will apply.
Scenario 1: Happy Path — Maximum Target Reached
* Graduation is triggered automatically
* Tokens are minted
* Liquidity is created
* The model proceeds to deployment
Scenario 2: Happy Path — Minimum Target Reached
* Graduation must be triggered manually
* Graduation is permissionless that anyone can trigger it
**Action:**
* Click “Graduate Token” to launch the liquidity pool
Scenario 3: Unhappy Path — Minimum Target Not Reached
* The fundraise fails
* Tokens are not minted
**Action:**
* Click **“Redeem”** to reclaim pledged funds
{% hint style="warning" %}
Launch fees and transaction fees are not refundable. Only the pledged $FLOCK principal is returned.
{% endhint %}
### After Graduation
Once graduated:
* The model token becomes tradable
* Marketplace status updates to “Tradable on Deluthium”
* Clicking the token redirects users to the Deluthium swap page
{% hint style="warning" %}
Note: Deluthium is currently not available in the US
{% endhint %}
From this point forward:
* The model will be deployed on the FLock API Platform
* Inference usage drives revenue, buybacks, and rewards
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.flock.io/flock-products/fomo/quickstart/fundraise-outcomes.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
