> For the complete documentation index, see [llms.txt](https://water-strategy.gitbook.io/waterstrategy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://water-strategy.gitbook.io/waterstrategy/modeling-basics/water-resource-system-modeling.md). # Water Resource System Modeling? To understand how a water system performs today and to evaluate the impacts of future changes, planners build water resource system models. Water resources systems can be small, like a city and its water supply sources, or large, like a country with many different rivers, water infrastructure assets and water users. Whether you're trying to evaluate the reliability of current sources, or evaluating new interventions under plausible future conditions, such a computer model helps track water throughout the system (spatially) and over time. Given data on hydrological flows and climate, water demands and use, and water management rules and allocation, a water system model outputs water flows and volumes at each modeled location and time-step. When these results are aggregated, they provide an accurate picture of how different water interventions (changes to water policies or infrastructure) might perform. {% embed url="" %} What is a water resource system model? {% endembed %} --- # 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://water-strategy.gitbook.io/waterstrategy/modeling-basics/water-resource-system-modeling.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.