> For the complete documentation index, see [llms.txt](https://docs.altitude.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.altitude.fi/smart-contracts/what-is-the-architecture.md). # What is the architecture? Each supply/borrow currency pair is managed in a single vault, for example a wstETH-USDC vault, where a user can supply wstETH and borrow USDC. Vaults facilitate a few key functions, including: * **User actions:** Allowing the users to interact with the vault through 'deposit', 'borrow', 'repay', 'withdraw' and 'claimRewards' actions * **Lender Strategies:** deploying user assets into the lenders where the best rates can be achieved * **Farm Strategies:** deploying previously dormant capital (active capital) to earn interest on the users behalf * **Rebalancing:** ensuring the vault position is always healthy by borrowing and repaying lenders when needed * **Harvesting**: recognising earnings from the Farm Optimisations and enabling distribution to users * **Committing:** updating user balances to recognise their latest position, including earnings from the farm strategy * **Liquidations:** enabling user funds to be liquidated when the users position becomes unhealthy * **Tokenization:** tokenizing user supply and debt positions --- # 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.altitude.fi/smart-contracts/what-is-the-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.