> For the complete documentation index, see [llms.txt](https://docs.zirodelta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zirodelta.com/modules/treasury-engine.md). # Treasury Engine The Treasury Engine manages the system's own money: its reserves, its liquidity and the capital it puts in front of clients' money. ## What it is designed to manage * **The first-loss buffer** in the Yield Engine's pool, funded by the project. * **Capital for credit,** such as loans against wzdUSD and advances against upcoming payouts. * **Working float** used to make conversions and payouts quick. * **Liquidity** in the markets the system relies on. * **An app's own cash,** for apps that want their company money held and managed through the modules. ## Rules * Client money and Zirodelta's own capital are tracked separately. * Riskier roles are filled with Zirodelta's capital, not client money. * Treasury positions that matter to users are published on the [transparency page](https://zirodelta.com/transparency) as they go live. ## Status In development. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.zirodelta.com/modules/treasury-engine.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.