> For the complete documentation index, see [llms.txt](https://niftsy-protocol-niftsy-1.gitbook.io/niftsy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://niftsy-protocol-niftsy-1.gitbook.io/niftsy/key-documents/white-paper/tokenomics.md).

# The architecture of the Project and the role of the Token

So, the Project’s architecture looks like this.

![](/files/-MeVQw3PI_KeWpQT99Lc)

It is important to note the following principles of model formation. They are listed below.

1. **The links between** “Protocol - Oracle – Index” are formed initially from the bottom up, but after that the Project works from all three elements.
2. **Oracle and Index** can be created outside the Project, but Protocol cannot.
3. **All three entities** are based on primitive transactional reputation models, that means, they consider a) quantitative; b) temporal; c) subjective criteria.
4. **All elements** operate on the basis of openness, decentralization, and consider all entities (scripts, AIs, users, etc.) as possible actors in the Project.
5. **All three entities** interact with each other through the Token functionality which is a necessary element of the Project ecosystem.

The features of the Token are discussed in more detail below.


---

# 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://niftsy-protocol-niftsy-1.gitbook.io/niftsy/key-documents/white-paper/tokenomics.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.