> 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/consortiums/frontiers/gra/academia.md).

# ACADEMIA

**Where this fits:** all six sectors ([The Model](/organization/model.md)) · [Labs](/organization/programme/labs.md), [Risk Academy](/organization/programme/academy.md) · research and universities (the ARC Helix council); Labs and Risk Academy · academic reference.

**In brief.** Read against the international frameworks it serves ([FAO 2014](https://www.fao.org/4/bl496e/bl496e.pdf); [IRENA 2015](https://www.irena.org/publications/2015/Jan/Renewable-Energy-in-the-Water-Energy--Food-Nexus); [IPBES 2024](https://www.ipbes.net/nexus-assessment)) and the [Nexus Standards](/organization/institutions/nexus-standards.md) that govern its records ([NS-0](https://nexustandards.com/standards/ns-0/), [NS-12](https://nexustandards.com/standards/ns-12/)). "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).

{% 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.
  {% endhint %}

This section collects the pages on academia from the earlier frontier layer. Its pages are:

* [Energy](/organization/cooperation/consortiums/frontiers/gra/academia/energy.md)
* [Food](/organization/cooperation/consortiums/frontiers/gra/academia/food.md)
* [Framework](/organization/cooperation/consortiums/frontiers/gra/academia/framework.md)
* [Water](/organization/cooperation/consortiums/frontiers/gra/academia/water.md)

## Sources

1. 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. <https://www.fao.org/4/bl496e/bl496e.pdf>
2. IRENA (2015). Renewable Energy in the Water, Energy and GCRI Food. Abu Dhabi: International Renewable Energy Agency. <https://www.irena.org/publications/2015/Jan/Renewable-Energy-in-the-Water-Energy--Food-Nexus>
3. IPBES (2024). Summary for Policymakers of the Thematic Assessment Report on the Interlinkages among Biodiversity, Water, Food and Health (Nexus Assessment). IPBES/11/12/Add.1. Bonn: IPBES secretariat. doi:10.5281/zenodo.13850289. <https://www.ipbes.net/nexus-assessment>
4. IPCC (2022). Climate Change 2022: Impacts, Adaptation and Vulnerability. Contribution of Working Group II to the Sixth Assessment Report (H.-O. Pörtner et al., eds.). Cambridge University Press. doi:10.1017/9781009325844. <https://www.ipcc.ch/report/ar6/wg2/>
5. Nexus Standards. NS-0: Constitution and principles. Status: PROPOSED; UNI `NXS-STD-ST-000004`. <https://nexustandards.com/standards/ns-0/>
6. Nexus Standards. NS-12: Software, models and ai/ml artifacts. Status: PROPOSED; UNI `NXS-STD-ST-000012`. <https://nexustandards.com/standards/ns-12/>
7. GCRI. The Labs pillar home. <https://therisk.global/nexus-labs/>
8. GCRI. Labs gateway. <https://therisk.global/ecosystem/labs/>
9. 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/consortiums/frontiers/gra/academia.md?ask=<question>&goal=<user_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.