> For the complete documentation index, see [llms.txt](https://mortgagefi-docs.gitbook.io/mortgagefi-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mortgagefi-docs.gitbook.io/mortgagefi-documentation/risk-management/ongoing-risk-management.md). # Ongoing Risk Management * Additional post-launch security audits planned, to be funded by protocol income * Community-driven governance for risk parameter adjustments * Continuous monitoring and improvement of risk models MortgageFi's risk management approach creates a robust and sustainable ecosystem that actively involves its users. The absence of traditional liquidation risk and the user-triggered default resolution process are key features that not only protect the system but also empower and reward vigilant participants. While all financial systems carry inherent risks, these measures significantly enhance the protocol's resilience to potential threats in the DeFi space, fostering a more engaged and responsible user community. --- # 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://mortgagefi-docs.gitbook.io/mortgagefi-documentation/risk-management/ongoing-risk-management.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.