> For the complete documentation index, see [llms.txt](https://docs.fragment.technology/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fragment.technology/concept/circles.md).

# Circles

<figure><img src="/files/jWJbifCplYse6pw5gF6J" alt=""><figcaption><p>Circles release</p></figcaption></figure>

Due to the fact that the *Frag·Verse AI* is not yet ready to manage all learning tasks, our technology integrates the notion of ***Fragment Circles*** allowing the modeling of the universe of the literary work via social circles.

The community is the most important concept of Web3. This is a new paradigm and we develop Fragment with community by design.

Thanks to Circles, fans will participates from the start of the projects and be co-creator of NFT collections. They will earn tokenized fragments and gouvernance token in exchange for their contribution.

The universe modeling will be fast and user friendly thanks to a beautiful graphic conception tool but above all, it will be social. Thanks to participating of all the community, the modelization will be reliable and accurate with a system of upvote and downvote via our DAO.


---

# 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.fragment.technology/concept/circles.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.