> 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/acceleration/nexus-programs/fellowship/research.md).

# RESEARCH

This page sets out RESEARCH (research track) in the earlier design of the Fellowship, now read as learning pathways of the Risk Academy pillar.

**Where this fits:** all six sectors · the Risk Academy pillar, with Universe missions · GCRI Canada as issuer of record; GRF and GRA as course authors · Q2 qualification and Q4 renewal · programme design · see [Risk Academy](/organization/programme/academy.md); [Institutions: Risk Academy](/organization/institutions/risk-academy.md); [The programme year](/organization/programme/the-programme-year.md).

**In brief.** This page sets out RESEARCH (research track) in the earlier design of the Fellowship, now read as learning pathways of the Risk Academy pillar. A completion record is not a licence to practise, and no credential is issued until an accountable issuer, an assessment method and a revocation path are on record; the Fellowship confers no immunity, privilege, diplomatic or legal status. Learning by doing on real cycle work answers the Sendai Framework's first priority, understanding disaster risk ([UN General Assembly 2015](https://www.undrr.org/publication/sendai-framework-disaster-risk-reduction-2015-2030)), and uses the risk-management vocabulary of ISO 31000 ([ISO 2018](https://www.iso.org/standard/65694.html)).

{% hint style="info" %}
**Read with the current model (2026-10-21).**

* Fellowship tracks are learning pathways of the Risk Academy pillar. Completion is recorded, not credentialed, until GCRI Canada as issuer of record has the assessment method, the signing key and the status and revocation path on record ([Risk Academy](/organization/programme/academy.md)).
* DAO, token, NFT and on-chain governance language describes earlier design concepts. No DAO, token or on-chain body exists or governs any part of the programme; National Working Groups are expert working groups under [National Nexus](/organization/governance-in-operation/national-nexus.md), with bounded, supervised assignments and no fee for ordinary participation ([National Working Groups](/organization/governance-in-operation/nwg.md)).
* Everything described here is in formation: no national, regional or global programme is recorded as constituted or active, and the current service level is R0, information and enquiries ([Status and service levels](/organization/governance-in-operation/status-and-service-levels.md)).
* [Nexus Standards](/organization/institutions/nexus-standards.md) that bear on this page: [NS-0](https://nexustandards.com/standards/ns-0/) (constitution and principles), [NS-13](https://nexustandards.com/standards/ns-13/) (open standards development process), [NS-1](https://nexustandards.com/standards/ns-1/) (the UNI and the artifact catalog). Their text and status on nexustandards.com govern.
  {% endhint %}

## Sources

External sources and standards cited in the In brief and the note above. The text below keeps its own internal references.

1. UN General Assembly (2015). Sendai Framework for Disaster Risk Reduction 2015–2030. A/RES/69/283, 3 June 2015. <https://www.undrr.org/publication/sendai-framework-disaster-risk-reduction-2015-2030>
2. ISO (2018). ISO 31000:2018 Risk management — Guidelines. Geneva: International Organization for Standardization. <https://www.iso.org/standard/65694.html>
3. Nexus Standards, NS-0: Constitution and principles. Status as published. <https://nexustandards.com/standards/ns-0/>
4. Nexus Standards, NS-13: Open standards development process. Status as published. <https://nexustandards.com/standards/ns-13/>
5. Nexus Standards, NS-1: The UNI and the artifact catalog. Status as published. <https://nexustandards.com/standards/ns-1/>


---

# 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/acceleration/nexus-programs/fellowship/research.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.