> For the complete documentation index, see [llms.txt](https://nft-crap.gitbook.io/the-game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nft-crap.gitbook.io/the-game/the-plot/history-of-veel-tark.md).

# HISTORY OF VEEL-TARK

<figure><img src="/files/V6J7fftpdntBCm8mgFRs" alt=""><figcaption></figcaption></figure>

The History of Veel-Tark is not only the story of the creation of a city; it is, above all, the genesis of a dream, of a magical space that takes the form of a gigantic cenacle where great knowledge and wisdom can be brought together.

Veel-Tark is thus a decentralised universe, where information is available to all. It is, in essence, a great game board that is projected on the subtle plane through the imagination of all its citizens.

Yes, Veel-Tark is a game, a game of puzzles, riddles and quests; but it is also a statement of principles and values. It is a proposal for the future, a world of portals to hidden wisdom, to a universal community, to decentralised knowledge.

Because knowledge is power. On each of us, as players, depends the use we make of it.


---

# 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://nft-crap.gitbook.io/the-game/the-plot/history-of-veel-tark.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.
