> For the complete documentation index, see [llms.txt](https://litepaper.mvhq.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://litepaper.mvhq.io/core-objectives.md).

# Core Objectives

**Incentivize** **Long Term Value Exchange**\
Value exchange is important, and our approach to rewarding users prioritizes long term engagement, mitigating drop-offs. Stakeholders should feel that the rewards for their contributions to our network are appropriate and enticing.

**Make Governance Meaningful and Easily Accessible**\
Governance shouldn't be confined to obscure forums or complex protocols, nor should it revolve around low-impact proposals. 

**Design For Recyclability**\
Our incorporation of asset streaming enables us to effectively "re-use" tokens set aside for initiatives like airdrops, exponentially increasing the impact and flexibility we can have with those initiatives.

**Tightly Coupled Utility**\
**$**HQ should align to empower with Metaverse HQ's Protocols


---

# 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://litepaper.mvhq.io/core-objectives.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.