> For the complete documentation index, see [llms.txt](https://whitepaper.frak.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.frak.id/frak-protocol/meet-the-fraktions.md).

# Meet the Fraktions

The Fraktions are content derivative based on the consumption of the content as underlying data. In other words, the Fraktions are financial products whose profitability depends on the usage of a given content. Then, with Fraktion comes the new notion of active income as opposed to most products and investments that yield passive income.

<figure><img src="/files/lmBBlDxzjNPffsaKUodv" alt=""><figcaption><p>Fraktions with different profitabilities </p></figcaption></figure>

When you buy a share of Google, you can expect the increase of the share price or to get paid with some dividend. But those potential revenue don't depend on you, your skills or your actions. They are passive.&#x20;

Otherwise, the Frak Protocol invented a dynamic APY that is directly impacted by the usage of the Fraktion's holder but also all the referees to whom he has shared the related content, and in a lesser proportion, also from the rest of the community.

The following chapter will detailed all the algorithms behind the Frak Protocol.&#x20;


---

# 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://whitepaper.frak.id/frak-protocol/meet-the-fraktions.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.