> For the complete documentation index, see [llms.txt](https://city-protocol.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://city-protocol.gitbook.io/docs/vault-as-a-service/what-is-vaas/design-goals.md). # Design Goals VaaS is built around five design goals. ### Secure capital deployment User funds should first enter a secure vault contract. Capital should not move directly from the user to an exchange, market maker, borrower, or strategy venue. The vault becomes the controlled entry point where permissions, deposit limits, allocation rules, and risk controls are enforced. ### Configurable vault policy Different strategies require different parameters. VaaS supports modular vault configuration so curators can define accepted assets, minimum deposits, capacity, fees, allocation rules, redemption periods, strategy limits, oracle settings, and emergency controls. ### Verifiable accounting Vault accounting should be visible and repeatable. NAV reports, share price updates, deposits, withdrawals, fees, settlement records, strategy debt, and permission changes should be available for monitoring through onchain events, subgraph indexing, and dashboards. ### Creator-bound execution Vault creators or curators should define the mandate of the vault before execution begins. Strategy managers can make tactical allocation decisions only inside approved boundaries. This separation lets the vault pursue yield while preventing capital from leaving the policy envelope originally defined for the product. ### Redemption integrity Withdrawals should be predictable and verifiable. Once a withdrawal request enters a redemption process, the vault should track the request, lock pricing at the correct time, calculate required liquidity, verify settlement assets, and allow the user to claim only when liquidity is available. --- # 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://city-protocol.gitbook.io/docs/vault-as-a-service/what-is-vaas/design-goals.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.