> For the complete documentation index, see [llms.txt](https://docs.theos.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theos.io/resource-ecology.md). # Resource Ecology When producers organise to satisfy requests, they will need to combine resources and labour to produce the required products or services. Resources are linked together into "recipes" which relate all products to their constituent components, in specified physical units. Every time a recipe is requested, orders for its constituent components (i.e. resources) are requested too. These recipes are then chained together into a web called the resource ecology - a graph built up from resource recipes where each node represents a unique type of resource. The resource ecology can be likened to a transparent and shared web of supply chains in which every resource is geo-localised. By shifting from a concealed collection of abstract, linear supply chains to a transparent geo-localised resource graph, local providers can easily fill gaps in the resource web and optimize long supply pathways. Consequently, the resource ecology harmonises the efficiencies of globalisation and the resilience of localisation. --- # 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://docs.theos.io/resource-ecology.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.