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

# Disclaimer

This whitepaper does not constitute a prospectus or offer document of any sort and is not intended to constitute an offer of securities or a solicitation for investment in securities in any jurisdiction.

This whitepaper does not constitute an offer or solicitation to sell or any solicitation of any offer by the distributor/vendor of the PYR and LAVA tokens to purchase any PYR or LAVA tokens nor shall it or any part of it nor the fact of its presentation form the basis of, or be relied upon in connection with, any contract or investment decision.

Please note that we are unable to predict the future, conditions may change based on any number of reasons, from economy to technological developments. For example, should reward NFTs ever become obsolete for an unforeseen reason, Vulcan Forged will ensure that where feasible, users and players will be provided with some compensation.


---

# 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://vulcan-forged.gitbook.io/whitepaper/white-paper/disclaimer.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.