> 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/launch-lifecycle-deep-dive/1.-launch-initiation.md).

# 1. Launch Initiation

A model launch begins with a Real Model Asset Offering (RMO) initiated by the Real Model Asset (RMA) Issuer.

During this phase:

* The RMA Issuer defines a concrete model deployment configuration, including model architecture and hosting tier.
* A 7-day fundraising process is opened where participants commit $FLOCK to support the deployment.
* Fundraising follows predefined minimum and maximum targets that reflect the economic requirements of hosting and operating the model.

Crucially, no Model Tokens ($MT) are minted during this stage. If the minimum fundraising target is not met within the launch window, the deployment does not proceed and pledged funds are redeemable (excluding platform fees). This ensures that model assets only come into existence when sufficient economic backing is secured.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.flock.io/flock-products/fomo/launch-lifecycle-deep-dive/1.-launch-initiation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
