> 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/5.-early-incentives.md).

# 5. Early Incentives

Bootstrap Emissions

During the early phase of a model’s lifecycle, the protocol distributes $FLOCK emissions to accelerate adoption.

* Emissions are allocated only to models with real usage.
* Distribution is weighted by usage volume and deployment age.
* Within each model, emissions are routed primarily to $MT stakers.

As the model matures and organic revenue grows, emissions decay and become a secondary incentive. Over time, usage-funded buybacks dominate emissions, allowing the system to transition from subsidized growth to sustainable operation.


---

# 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/launch-lifecycle-deep-dive/5.-early-incentives.md?ask=<question>&goal=<user_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.
