> 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-tokenomics/network-participation/ai-arena/task-creator.md).

# Task Creator

Task creation is the first stage of FLock’s decentralised AI training cycle. Creators define the desired models and submit tasks to the platform. Anyone who satisfies the following conditions can participate as a task creator. Thus, the system is, by design, democratic, making it accessible to a broad range of stakeholders. This fosters a sense of ownership and active involvement amongst the FLock community.

In order to become a task creator, one has to fulfil one or more of the requirements below:

(1) stake a sufficient amount of FLOCK

(2) have successfully trained or validated a task before, based on on-chain records

(3) have a reputation in the ML space or is a domain expert in relevant fields, which is verified by the FLock community

In addition to the desired model becoming available for the task creator’s use, the creator may also receive rewards proportional to their stakes.

\*This feature is not public yet.


---

# 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-tokenomics/network-participation/ai-arena/task-creator.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.