> For the complete documentation index, see [llms.txt](https://docs.therisk.global/organization/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.therisk.global/organization/cooperation/nexus-guilds/future-of-food.md). # Future of Food Future of Food in Nexus Guilds, covering food security, food systems resilience, agriculture, food safety, supply chains, nutrition, traceability, and climate risk. **Where this fits:** [Food](/organization/model/sectors/food.md) · [Labs](/organization/programme/labs.md), [Risk Academy](/organization/programme/academy.md) · communities of practice by sector, supplying the questions of the Labs pillar; National Working Groups ([NWG](/organization/governance-in-operation/nwg.md)) · community of practice. **In brief.** Future of Food is the Nexus Guilds domain for food security, food systems resilience, and food governance. Read against the international frameworks it serves ([UN General Assembly 2015](https://www.undrr.org/publication/sendai-framework-disaster-risk-reduction-2015-2030); [FAO 2014](https://www.fao.org/4/bl496e/bl496e.pdf); [One Health High-Level Expert Panel (OHHLEP) et al. 2022](https://doi.org/10.1371/journal.ppat.1010537)) and the [Nexus Standards](/organization/institutions/nexus-standards.md) that govern its records ([NS-0](https://nexustandards.com/standards/ns-0/), [NS-13](https://nexustandards.com/standards/ns-13/)). "An experiment is exploratory: its results are labelled as such and become evidence only after the Foundry rebuilds and the Universe tests them." (Labs pillar boundary). Ordinary participation has no fee. Paid work, internships and fellowships are separate arrangements, and unqualified contributors never take safety-critical tasks. {% hint style="info" %} **Read with the current model (2026-10-21).** * Everything this page describes is a design in formation. No national, regional or global consortium is recorded as constituted or active; the current service level is R0, information and enquiries ([Status and service levels](/organization/governance-in-operation/status-and-service-levels.md)). Where the text below reads as operation, read it as design. * Recognition, scoring and validation record what was shown under stated conditions. None is a certification, licence, rating or approval, and no country or institution is ranked. {% endhint %} ### Future of Food in Nexus Guilds Future of Food is the Nexus Guilds domain for food security, food systems resilience, and food governance. It connects agriculture, food safety, supply chains, nutrition, traceability, and climate risk with governed research and reusable standards. This section shows how Future Innovation Labs study food continuity, publish evidence, and support safer coordination across the Nexus ecosystem. * **Food security** covers availability, affordability, continuity, and resilience under shocks. * **Food governance** covers traceability, recall readiness, safety controls, and communications integrity. * **Food intelligence** covers supply chain stress, dependency risk, climate exposure, and bounded analysis. ### What Future of Food covers * Agriculture, processing, storage, logistics, retail, and food distribution resilience. * Food safety, contamination response, recall readiness, and traceability interoperability. * Nutrition protection, food affordability, climate risk, water stress, and energy-for-food dependencies. ### Related pages * [Overview](/organization/cooperation/nexus-guilds/overview.md) * [Ecosystem](/organization/cooperation/nexus-guilds/ecosystem.md) * [Lab](/organization/cooperation/nexus-guilds/future-of-food/lab.md) * [Membership](/organization/cooperation/nexus-guilds/membership.md) ### Why Future of Food matters Future of Food helps teams compare evidence, improve food system resilience, and reduce risk across the food value chain. It supports safer food collaboration without crossing into procurement, enforcement, certification, or operational control. *** ## Sources 1. UN General Assembly (2015). Sendai Framework for Disaster Risk Reduction 2015–2030. A/RES/69/283, 3 June 2015. 2. FAO (2014). The Water-Energy-Food Nexus: A new approach in support of food security and sustainable agriculture. Rome: Food and Agriculture Organization of the United Nations. 3. One Health High-Level Expert Panel (OHHLEP), Adisasmito, W. B. et al. (2022). One Health: A new definition for a sustainable and healthy future. PLoS Pathogens 18(6): e1010537. doi:10.1371/journal.ppat.1010537. 4. Nexus Standards. NS-0: Constitution and principles. Status: PROPOSED; UNI `NXS-STD-ST-000004`. 5. Nexus Standards. NS-13: Open standards development process. Status: PROPOSED; UNI `NXS-STD-ST-000008`. 6. GCRI. The Labs pillar home. 7. GCRI. Working groups (NWG). 8. This documentation: [Governance in operation](/organization/governance-in-operation.md); [The Model](/organization/model.md); [historical labels](/organization/reference.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://docs.therisk.global/organization/cooperation/nexus-guilds/future-of-food.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.