> For the complete documentation index, see [llms.txt](https://docs.basin.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.basin.global/provenance/the-basin-field-manual.md). # The BASIN Field Manual ### BASIN makes nature and the benefits it provides to all beings investable. The **BASIN Field Manual** is the central reference to all that is BASIN. It is our expression of the intertwined, entangled **relational value** of the natural systems we inhabit**.** Herein lies what we hope will be a compass, or at least a map, for the path ahead. *** ## Rules? ***If*** BASIN had rules they would be: ### Embrace Complexity Complex is not the same as complicated. Biodiversity, climate, carbon, water, nature, and beyond — economics, finance, politics, law, art, health, wealth, and **well-being** — are all interconnected. ### Stocks & Flows Ecological economics and ecosystem accounting are based on the principles of stocks and flows. This aptly mirrors nature's basins that store and circulate life-sustaining water. BASIN's model is crafted on this very essence— protecting and stewarding the stocks and flows of Nature's Intrinsic Value. ### Stacking v. Bundling Stacking splits a place into parts (food, fiber, water, carbon, biodiversity, etc); bundling values the whole. We favor bundling—one instrument, no overlap, holistic valuation. We issue on value, price on cost and let the market close the gap to fund natural asset ensurance. *** > “***When we try to pick out anything by itself, we find it hitched to everything else in the universe.***” > > -John Muir, My First Summer in the Sierra, 1911 --- # 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.basin.global/provenance/the-basin-field-manual.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.