> For the complete documentation index, see [llms.txt](https://docs.arafi.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arafi.app/introduction/understanding-the-basic-architecture.md). # Understanding the Basic Architecture The architectural design of AraFi involves at its core the implementation of liquid wrappers to accrue desired governance tokens. These assets will be put to work by the ARA Treasury to optimize returns and leverage their efficient economic models to drive liquidity to desired pairs. Our long term intention is to accrue revenue for ARA Holders. Gaining access to these resources will allow ARA to implement: \- Farming Boosts that provide greater LP farming rewards \- Adding an extra incentive layer to improve efficiency and increase holder profit potential. \- Providing strategic influence on the underlying governance structure for our holders. --- # 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://docs.arafi.app/introduction/understanding-the-basic-architecture.md?ask=&goal= ``` `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.