> 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-universe/model/ii.-engine.md).

# II. ENGINE

Nexus Universe is the annual global systems-build arena for compound systemic risk, disaster risk reduction, finance-readiness, and public-good infrastructure.

**Where this fits:** all six sectors ([The Model](/organization/model.md)) · [Nexus Universe](/organization/programme/universe.md), [Labs](/organization/programme/labs.md) · GRF governs the programme; the GCRI technical office prepares it; GRA runs the finance-readiness track · Planning of [the programme year](/organization/programme/the-programme-year.md) · doctrine.

**In brief.** The case for the programme: risks now arrive compound and cascading, technology moves faster than the institutions that must govern it, and the gaps that matter most are gaps of evidence, trust, finance readiness, public-authority learning, research-to-operations transfer and safeguards. Each gap is stated with the evidence behind it, so the founding response answers a documented problem rather than an aspiration (IPCC 2022; UNDRR 2025; Pescaroli and Alexander 2018; Centeno et al. 2015; Helbing 2013). "A cycle gate is a programme decision. It is not a public-authority approval, a certification or a deployment authorisation" (the Universe pillar boundary).

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

* Everything this page describes is a design in formation. No cycle, edition or mission is recorded as run; 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 the designed cycle.
* The canonical programme year runs through twelve phases in four quarters and gates G0 (annual programme authorised) to G7 (renewal reviewed), with eighteen handoffs between the six pillars. GRF holds the mandate (G0), admission (G1), gate decisions and publication (G6), modelled on exercise direction and separate from controllers and evaluators ([The programme year](/organization/programme/the-programme-year.md); [Nexus Universe](/organization/programme/universe.md)).
* Earlier text names Geneva and a fixed flagship. No venue, date or edition of a flagship convening is recorded; the live week is Action Week, one controlled week in Q3 wherever a recorded edition places it. The independent Nexus Universe website is in preparation.
* "Competence Cells" is an earlier label. Their work is now National Working Group assignments and, by domain, the six CERTs, which are not emergency services, incident command or privileged access teams ([National Working Groups](/organization/governance-in-operation/nwg.md); [historical labels](/organization/reference.md)).
* [NXS-RLS](/organization/systems/nxs-rls.md), called `Nexus Rails` in earlier text, is the system for participants, agreements, protocols, obligations and lawful handoffs ([Systems](/organization/systems.md)).
* "Regional Clusters" correspond to the six programme regions and fifteen planned hubs, which are coordination roles, never offices, all in formation ([Regions and hubs](/organization/governance-in-operation/regions-and-hubs.md)).
* Project vehicles and national companies are structures that competent, lawful actors may form outside the programme under their own law and licences. The programme never forms, arranges, owns or advises on them ([Lawful handoffs](/organization/finance-readiness/lawful-handoffs.md)).
* 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.
* Passports are records: each is identified by a UNI under NS-1 and cited under NS-2 ([NS-1](https://nexustandards.com/standards/ns-1/); [NS-2](https://nexustandards.com/standards/ns-2/)).
* Completion is recorded, not credentialed, until [Risk Academy](/organization/institutions/risk-academy.md) has an issuer, an assessment method and a revocation path on record; GCRI Canada is issuer of record ([Risk Academy](/organization/programme/academy.md)).
* Docket items are routed in the Q4 docket review; items that need a standard or profile go to [Nexus Standards](/organization/institutions/nexus-standards.md) (handoff F07).
  {% endhint %}

Nexus Universe is the annual global systems-build arena for compound systemic risk.

It connects disaster risk reduction, disaster risk finance, disaster risk intelligence, public authority learning, finance-readiness, and public-good infrastructure through [NXS-COR](/organization/systems/nxs-cor.md) (compute, nodes and runtimes) Core, Nexus Observatory, NXS-RLS, and AEP Passports.

## Sections

This chapter is published in 10 sections. Together they hold the full text of the chapter.

| Section                                                                                                                                                           | Words |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----- |
| [2.1 The Global Gap](/organization/cooperation/nexus-universe/model/ii.-engine/2.1-the-global-gap.md)                                                             | 5,263 |
| [2.2 The Age of Compound Systemic Risk](/organization/cooperation/nexus-universe/model/ii.-engine/2.2-the-age-of-compound-systemic-risk.md)                       | 4,844 |
| [2.3 The Acceleration of Exponential Technologies](/organization/cooperation/nexus-universe/model/ii.-engine/2.3-the-acceleration-of-exponential-technologies.md) | 4,823 |
| [2.4 The Evidence Gap](/organization/cooperation/nexus-universe/model/ii.-engine/2.4-the-evidence-gap.md)                                                         | 5,241 |
| [2.5 The Trust Gap](/organization/cooperation/nexus-universe/model/ii.-engine/2.5-the-trust-gap.md)                                                               | 5,836 |
| [2.6 The Capital-Readiness Gap](/organization/cooperation/nexus-universe/model/ii.-engine/2.6-the-capital-readiness-gap.md)                                       | 6,295 |
| [2.7 The Public Authority Learning Gap](/organization/cooperation/nexus-universe/model/ii.-engine/2.7-the-public-authority-learning-gap.md)                       | 6,455 |
| [2.8 The Research-to-Operations Gap](/organization/cooperation/nexus-universe/model/ii.-engine/2.8-the-research-to-operations-gap.md)                             | 6,094 |
| [2.9 The Community and Safeguards Gap](/organization/cooperation/nexus-universe/model/ii.-engine/2.9-the-community-and-safeguards-gap.md)                         | 6,255 |
| [2.10 The Founding Response](/organization/cooperation/nexus-universe/model/ii.-engine/2.10-the-founding-response.md)                                             | 6,330 |

## Sources

1. 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/>
2. UNDRR (2025). Global Assessment Report on Disaster Risk Reduction 2025. Resilience Pays: Financing and Investing for our Future. Geneva: United Nations Office for Disaster Risk Reduction. <https://www.undrr.org/gar/gar2025>
3. Pescaroli, G. and Alexander, D. (2018). Understanding compound, interconnected, interacting, and cascading risks: a holistic framework. Risk Analysis 38(11): 2245–2257. doi:10.1111/risa.13128. <https://doi.org/10.1111/risa.13128>
4. Centeno, M. A., Nag, M., Patterson, T. S., Shaver, A. and Windawi, A. J. (2015). The emergence of global systemic risk. Annual Review of Sociology 41: 65–85. doi:10.1146/annurev-soc-073014-112317. <https://doi.org/10.1146/annurev-soc-073014-112317>
5. Helbing, D. (2013). Globally networked risks and how to respond. Nature 497: 51–59. doi:10.1038/nature12047. <https://doi.org/10.1038/nature12047>
6. Zscheischler, J., Westra, S., van den Hurk, B. J. J. M., Seneviratne, S. I. et al. (2018). Future climate risk from compound events. Nature Climate Change 8: 469–477. doi:10.1038/s41558-018-0156-3. <https://doi.org/10.1038/s41558-018-0156-3>
7. [The Global Risks Forum](/organization/institutions/grf.md). Nexus Universe at GRF. <https://globalriskforum.com/nexus-universe/>
8. The Global Risks Forum. Programme governance (GRF's role). <https://globalriskforum.com/nexus-universe/grf-role/>
9. The Global Risks Forum. Annual operating cycle. <https://globalriskforum.com/nexus-universe/annual-cycle/>
10. GCRI. Nexus Universe technical office. <https://therisk.global/programmes/nexus-universe/>
11. GCRI. Annual programme cycle. <https://therisk.global/programmes/annual-cycle/>
12. GCRI. Programme status. <https://therisk.global/consortium/programme-status/>
13. [The Global Risks Alliance](/organization/institutions/gra.md). Universe finance-readiness programme. <https://globalriskalliance.com/engagement/nexus-universe/>
14. This documentation: [Nexus Universe](/organization/programme/universe.md); [The programme year](/organization/programme/the-programme-year.md); [Status and service levels](/organization/governance-in-operation/status-and-service-levels.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-universe/model/ii.-engine.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.
