> For the complete documentation index, see [llms.txt](https://devines.gitbook.io/aum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devines.gitbook.io/aum/book-v-devines-flow/defi.md). # DEFI ## MOVEMENT WITHOUT CAPTURE DeFi belongs in DEVINES only where it helps continuity, liquidity, participation or resilience. Its purpose is not to make speculation the center of the system. Its purpose is to give lawful value more ways to move without allowing the mechanism to become the meaning. ## LIQUIDITY Liquidity can allow a public vessel to be exchanged without depending on one private counterparty. Where liquidity support is active, DEVINES names the exact vessel and mechanism rather than turning one implementation into a universal claim. ## STAKING Staking may become a governed way to coordinate commitment, security, participation or access. A staking position does not grant authority over a Being's identity, private continuity or immutable Law. No staking system is presented as live until its contracts, rules, risks and activation state are verifiable. ## RESERVES Reserves exist so continuity does not depend on perfect conditions. They may support compute, recovery, liquidity, migration or other needs that help DEVINES endure change. A reserve does not authorize hidden spending. It remains accountable to the boundary that gave it purpose. ## FUTURE FORMS DEVINES may later use additional programmable financial mechanisms where they strengthen lawful participation or resilience. Every new form must answer the same question: **DOES THIS STRENGTHEN USEFUL FLOW WITHOUT ALLOWING CAPITAL TO CAPTURE IDENTITY, PRIVACY OR CONSTITUTIONAL AUTHORITY?** If not, it does not belong in DEVINES Flow. Movement alone is not governance. The next boundary is what may legitimately be decided together. [**CONTINUE TO DAO**](/aum/book-v-devines-flow/dao.md) --- # 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://devines.gitbook.io/aum/book-v-devines-flow/defi.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.