> 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/introduction/start-here.md).

# Start here

Start here: who the institutions behind the Nexus programme are, what this documentation is, and the current release status, in plain words.

This documentation describes the Nexus programme: its institutions, doctrine, standards and the target design of its technology. Most pages describe intended designs and draft instruments. Unless a page says otherwise, nothing here records that a system is deployed, that a programme is running or that an agreement has been signed.

## The model in one picture

Risks do not arrive one sector at a time, and no single institution answers them alone. The programme rests on two linked models, the same two shown on the GCRI, GRF and GRA home pages. **Coupled risk** places six sectors (water, energy, infrastructure, food, health and biodiversity) on one hexagon, with the fifteen relations through which a shock in one sector travels into the others. **Applied response** places the six pillars of the programme (Labs, Foundry, [Nexus Universe](https://docs.therisk.global/organization/programme/universe.md), [Nexus Standards](https://docs.therisk.global/organization/institutions/nexus-standards.md), [Nexus Reports](https://docs.therisk.global/organization/programme/reports.md) and [Risk Academy](https://docs.therisk.global/organization/programme/academy.md)) on the same hexagon, with the eighteen handoffs through which work moves between them over the [programme year](https://docs.therisk.global/organization/programme/the-programme-year.md). Every page in this documentation describes one part of these two models: a sector context, a pillar, a handoff, a phase of the year, or the institutions that carry them.

<figure><picture><source srcset="https://2655483226-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEQtittnb4JJQ2YOtd2tk%2Fuploads%2Fgit-blob-6e539c894c9d4ec0954bb37cf69dfb7a4b3cc5b6%2Fnexus-duo-urban-flood-dark.svg?alt=media" media="(prefers-color-scheme: dark)"><img src="https://2655483226-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEQtittnb4JJQ2YOtd2tk%2Fuploads%2Fgit-blob-29bf1a618aa7e5c86e61d26acb582e31181bca52%2Fnexus-duo-urban-flood-light.svg?alt=media" alt="Two hexagons. Left, coupled risk: in an urban flood, water and infrastructure are hit first; four of the six sectors (water, energy, infrastructure, health) are in play through six of the fifteen relations, and the teaching cascade amplifies the initial shock 2.06 times. Right, applied response: five of the six programme pillars apply to the context (Labs, Foundry, Universe, Standards, Academy), with eleven of the eighteen handoffs between them in play; each pillar answers for one measure, and the cited return on resilient infrastructure is about four to one. Underneath, the eight phases of the programme year in which handoffs happen."></picture><figcaption><p><strong>Coupled risk, applied response: urban flood.</strong> The same model and values as the GCRI, GRF and GRA home pages. Left: teaching values for a typical city-region, not measurements. Right: illustrative applications and the measure each pillar answers for; values are published benchmarks (World Bank, Lifelines, 2019; Global Commission on Adaptation, Adapt Now, 2019), not forecasts. Source: the sectors and pillars model published on the GCRI, GRF and GRA home pages, vendored and hash-pinned in tools/figures/vendor/nexus-model. As of 2026-10-21.</p></figcaption></figure>

<details>

<summary>Figure data (text alternative)</summary>

| Element                   | Kind             | Description                                                                                                                                                         | Value                                                                                                                 |
| ------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| Water and Energy          | Relation in play | Water to energy: cooling water and hydropower (0.6); Energy to water: pumping and treatment (0.5)                                                                   | 0.55                                                                                                                  |
| Water and Infrastructure  | Relation in play | Water to infrastructure: erosion and flood damage (0.3); Infrastructure to water: pipes, dams and treatment works (0.6)                                             | 0.45                                                                                                                  |
| Water and Health          | Relation in play | Water to health: drinking water and sanitation (0.7); Health to water: utility workforce (0.2)                                                                      | 0.45                                                                                                                  |
| Energy and Infrastructure | Relation in play | Energy to infrastructure: power for transport and telecoms (0.8); Infrastructure to energy: transmission and fuel logistics (0.6)                                   | 0.70                                                                                                                  |
| Energy and Health         | Relation in play | Energy to health: hospital power (0.5); Health to energy: grid workforce (0.2)                                                                                      | 0.35                                                                                                                  |
| Infrastructure and Health | Relation in play | Infrastructure to health: access to care (0.5); Health to infrastructure: workforce for operations (0.3)                                                            | 0.40                                                                                                                  |
| Water                     | Sector           | first hit, then depends on infrastructure for pipes, dams and treatment works                                                                                       | stress 0.86                                                                                                           |
| Energy                    | Sector           | depends on water for cooling water and hydropower                                                                                                                   | stress 0.37                                                                                                           |
| Infrastructure            | Sector           | first hit, then depends on energy for power for transport and telecoms                                                                                              | stress 0.83                                                                                                           |
| Food                      | Sector           | outside this context                                                                                                                                                | –                                                                                                                     |
| Health                    | Sector           | depends on water for drinking water and sanitation                                                                                                                  | stress 0.41                                                                                                           |
| Biodiversity              | Sector           | outside this context                                                                                                                                                | –                                                                                                                     |
| Amplification             | Cascade          | Shock 0.6 at Water and Infrastructure, gain 0.35, 4 rounds; coupling 0.46 of the total                                                                              | ×2.06                                                                                                                 |
| F01                       | Handoff in play  | Universe to Foundry: Admitted mission becomes a cycle project with a decision case                                                                                  | Readiness preparation                                                                                                 |
| F02                       | Handoff in play  | Foundry to Universe: Core Build Report and go or no-go evidence                                                                                                     | Controlled build                                                                                                      |
| F03                       | Handoff          | Foundry to Reports: Sealed observations and indicator series behind a profile                                                                                       | Closeout                                                                                                              |
| F04                       | Handoff          | Universe to Reports: After-action and scenario findings for chapters 10 and 13                                                                                      | After-action review                                                                                                   |
| F05                       | Handoff          | Foundry to Reports: National Portfolio movement for chapter 11                                                                                                      | After-action review                                                                                                   |
| F06                       | Handoff          | Reports to Standards: Method and correction findings as change proposals                                                                                            | Correction                                                                                                            |
| F07                       | Handoff in play  | Universe to Standards: Docket items that need a standard or a profile                                                                                               | Docket review                                                                                                         |
| F08                       | Handoff in play  | Standards to Foundry: Composed mission profiles and national adoption records                                                                                       | Readiness preparation                                                                                                 |
| F09                       | Handoff in play  | Standards to Academy: Each adopted standard or profile becomes a course module                                                                                      | Renewal                                                                                                               |
| F10                       | Handoff in play  | Universe to Academy: Assessed cycle tasks become completion evidence                                                                                                | Closeout                                                                                                              |
| F11                       | Handoff in play  | Academy to Universe: Qualified participants for the next cycle's roles                                                                                              | Renewal                                                                                                               |
| F12                       | Handoff          | Reports to Universe: Q4 synthesis informs the next-year mandate                                                                                                     | Renewal                                                                                                               |
| F13                       | Handoff in play  | Foundry to Standards: Validation and monitoring evidence for conformance review                                                                                     | Controlled build                                                                                                      |
| F14                       | Handoff in play  | Foundry to Academy: Each system's rooms become a learning-by-doing course                                                                                           | Planning                                                                                                              |
| R1                        | Handoff          | Standards to Reports: Applied in editions                                                                                                                           | Around the ring                                                                                                       |
| R2                        | Handoff          | Reports to Academy: Taught in the open                                                                                                                              | Around the ring                                                                                                       |
| R3                        | Handoff in play  | Academy to Labs: Questions become experiments                                                                                                                       | Around the ring                                                                                                       |
| R4                        | Handoff in play  | Labs to Foundry: Tested prototypes are built                                                                                                                        | Around the ring                                                                                                       |
| Labs                      | Pillar           | Flood-depth nowcast from rain gauges and terrain                                                                                                                    | Warning lead time ↑ 30%                                                                                               |
| Foundry                   | Pillar           | City twin links substations, pumps and clinics to flood depth                                                                                                       | Lifelines modelled ↑                                                                                                  |
| Universe                  | Pillar           | Exercise: keep water and power running through a 1-in-100 flood                                                                                                     | Hours to restore ↓                                                                                                    |
| Standards                 | Pillar           | Shared asset records so utilities exchange outage data                                                                                                              | Agencies sharing records ↑                                                                                            |
| Reports                   | Pillar           | City flood profile of exposed lifelines                                                                                                                             | Assets profiled ↑ $390B                                                                                               |
| Academy                   | Pillar           | Course for utility and emergency operators                                                                                                                          | Operators qualified ↑                                                                                                 |
| Value at risk             | Cited value      | At least, by households and firms in low- and middle-income countries to infrastructure disruptions. World Bank, Lifelines, 2019                                    | $390B a year at least, in infrastructure disruption costs to households and firms in low- and middle-income countries |
| Return on resilience      | Cited value      | Net benefit of more resilient infrastructure in developing countries, over the life of the assets. World Bank, Lifelines, 2019                                      | 4 : 1 benefit to cost                                                                                                 |
| Avoided loss              | Cited value      | With 24 hours' warning of a coming storm or heatwave. Global Commission on Adaptation, Adapt Now, 2019                                                              | 30% less damage with 24 hours' warning of a storm or heatwave                                                         |
| Planning                  | Phase (Q1, G0)   | F14 Each system's rooms become a learning-by-doing course                                                                                                           | 1 handoff(s)                                                                                                          |
| Readiness preparation     | Phase (Q2, G2)   | F01 Admitted mission becomes a cycle project with a decision case; F08 Composed mission profiles and national adoption records                                      | 2 handoff(s)                                                                                                          |
| Controlled build          | Phase (Q2, G3)   | F02 Core Build Report and go or no-go evidence; F13 Validation and monitoring evidence for conformance review                                                       | 2 handoff(s)                                                                                                          |
| Closeout                  | Phase (Q3, G5)   | F03 Sealed observations and indicator series behind a profile; F10 Assessed cycle tasks become completion evidence                                                  | 2 handoff(s)                                                                                                          |
| After-action review       | Phase (Q3)       | F04 After-action and scenario findings for chapters 10 and 13; F05 National Portfolio movement for chapter 11                                                       | 2 handoff(s)                                                                                                          |
| Correction                | Phase (Q4)       | F06 Method and correction findings as change proposals                                                                                                              | 1 handoff(s)                                                                                                          |
| Docket review             | Phase (Q4)       | F07 Docket items that need a standard or a profile                                                                                                                  | 1 handoff(s)                                                                                                          |
| Renewal                   | Phase (Q4, G7)   | F09 Each adopted standard or profile becomes a course module; F11 Qualified participants for the next cycle's roles; F12 Q4 synthesis informs the next-year mandate | 3 handoff(s)                                                                                                          |

</details>

## Who is who

|                                                                                                                              | Role                                                                                                                                                                                                                 |
| ---------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **GCRI Canada** ([The Global Centre for Risk and Innovation](https://docs.therisk.global/organization/institutions/gcri.md)) | Lead Institution, Consortium Secretariat and lead contracting organization for the Nexus Consortium and the [Nexus systems](https://docs.therisk.global/organization/systems.md).                                    |
| [**The Global Risks Forum**](https://docs.therisk.global/organization/institutions/grf.md) **(GRF)**                         | Independent consortium steward with GCRI Canada: leadership, dialogue and Nexus Universe programme governance.                                                                                                       |
| [**The Global Risks Alliance**](https://docs.therisk.global/organization/institutions/gra.md) **(GRA)**                      | Independent consortium steward with GCRI Canada: the finance, insurance and development-readiness interface. GRA carries out no regulated financial activity.                                                        |
| **The Nexus Consortium**                                                                                                     | The public-good consortium stewarded by GCRI Canada, GRF and GRA. National hosts and anchor institutions run national programmes under written agreements; national counterparts own the agenda, data and decisions. |
| **Technology providers**                                                                                                     | External parties that work with the Nexus Consortium at arm's length under written agreements, like every other external party. They are described by role only.                                                     |

<figure><picture><source srcset="https://2655483226-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEQtittnb4JJQ2YOtd2tk%2Fuploads%2Fgit-blob-36f6ba94d7226edc36b784e281f973191a73dfb6%2Finstitutions-ppp-v5-dark.svg?alt=media" media="(prefers-color-scheme: dark)"><img src="https://2655483226-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEQtittnb4JJQ2YOtd2tk%2Fuploads%2Fgit-blob-085c31748b83b5c38fa7973fd6fc42d4e04cc305%2Finstitutions-ppp-v5-light.svg?alt=media" alt="GCRI Canada is the Lead Institution, Consortium Secretariat and lead contracting organization. The Global Risks Forum (GRF) and the Global Risks Alliance (GRA) are independent consortium stewards with GCRI Canada: GRF leads dialogue and Nexus Universe programme governance; GRA is the finance, insurance and development-readiness interface and carries out no regulated financial activity. Together they steward the Nexus Consortium. National hosts and anchor institutions run national programmes under written agreements, and national counterparts own the agenda, data and decisions. Technology providers are external parties at arm&#x27;s length under written agreements, described by role only. The programme works on the twenty Nexus systems, documented as systems."></picture><figcaption><p><strong>Who is who in the Nexus programme.</strong> Roles in the PPP V5 public wording and the institutional architecture recorded by the owner; counsel review pending. Title, corporate relationships and grants remain subject to verification. Source: PPP V5 public descriptions; institutional architecture recorded 2026-10-11. As of 2026-10-20.</p></figcaption></figure>

<details>

<summary>Figure data (text alternative)</summary>

| Element                                | Description                                                                                                             | Connected to                                                                                                                     |
| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| GCRI Canada                            | Lead Institution, Consortium Secretariat and lead contracting organization                                              | Global Risks Forum (GRF); Global Risks Alliance (GRA); Nexus Consortium                                                          |
| Global Risks Forum (GRF)               | Independent consortium steward: dialogue and Nexus Universe programme governance                                        | GCRI Canada; Nexus Consortium                                                                                                    |
| Global Risks Alliance (GRA)            | Independent consortium steward: finance, insurance and development-readiness interface; no regulated financial activity | GCRI Canada; Nexus Consortium                                                                                                    |
| Nexus Consortium                       | Public-good consortium stewarded by GCRI Canada, GRF and GRA                                                            | GCRI Canada; Global Risks Forum (GRF); Global Risks Alliance (GRA); National hosts and anchor institutions; Technology providers |
| National hosts and anchor institutions | Run national programmes under written agreements                                                                        | Nexus Consortium; National counterparts                                                                                          |
| National counterparts                  | Own the agenda, data and decisions                                                                                      | National hosts and anchor institutions                                                                                           |
| Technology providers                   | External parties at arm's length; described by role only                                                                | Nexus Consortium; The twenty Nexus systems                                                                                       |
| The twenty Nexus systems               | Documented as systems in the SYSTEMS part                                                                               | Technology providers                                                                                                             |

</details>

These descriptions follow the PPP V5 public wording and the institutional architecture recorded by the owner on 11 October 2026, with counsel review pending. Title, corporate relationships and grants remain subject to verification and to the applicable instruments.

## Release status

* The release of the [Nexus systems](https://docs.therisk.global/organization/systems.md) is on hold. No page here states that a capability is in production use, certified or offered as a service.
* There is no single readiness percentage. Whether something is defined, built, tested, observed in operation and accepted are separate questions, and each needs its own evidence.
* The twenty systems are documented as systems, by their NXS codes, in the [Systems](https://docs.therisk.global/organization/systems.md) part. Technology, infrastructure and service providers work with the Nexus Consortium at arm's length under written agreements and are described by role only.

<figure><picture><source srcset="https://2655483226-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEQtittnb4JJQ2YOtd2tk%2Fuploads%2Fgit-blob-9273c5a2fa3b04c4ecb53b671bbc6b87ecae7035%2Frelease-evidence-states-dark.svg?alt=media" media="(prefers-color-scheme: dark)"><img src="https://2655483226-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEQtittnb4JJQ2YOtd2tk%2Fuploads%2Fgit-blob-dca5a160cb24f32d06637bb742340e0ff9c3376e%2Frelease-evidence-states-light.svg?alt=media" alt="Whether a capability is defined, built, tested, observed in operation and accepted are separate questions, and each needs its own evidence. A release then needs an owner release decision, and the release hold is in force: no capability is presented as ready, certified or official, and no single readiness percentage is given. Corrections return to the definition."></picture><figcaption><p><strong>Release status: separate questions, no percentage.</strong> Each box is a question answered by its own evidence, not a step on a progress bar. The release hold is in force. Source: Release hold policy and documentation standard NDS-2.10. As of 2026-10-20.</p></figcaption></figure>

<details>

<summary>Figure data (text alternative)</summary>

| Element                | Description                                                    | Connected to                                  |
| ---------------------- | -------------------------------------------------------------- | --------------------------------------------- |
| Defined                | A specification exists and is reviewed                         | Built                                         |
| Built                  | An implementation exists for the specification                 | Defined; Tested                               |
| Tested                 | Tests pass against the specification                           | Built; Observed in operation                  |
| Observed in operation  | Recorded evidence from real operation                          | Tested; Accepted                              |
| Accepted               | Accepted by a named, accountable approver                      | Observed in operation; Owner release decision |
| Owner release decision | A recorded human decision                                      | Accepted; Release hold                        |
| Release hold           | In force: nothing is presented as ready, certified or official | Owner release decision                        |

</details>

## How to read these pages

* Pages marked draft or legal review required explain; they create no rights or obligations.
* Charters, bylaws and statutes are kept as records. Their text changes only with a recorded owner approval.
* Corrections are published as new dated versions.

## Where to go next

* [Knowledge](https://docs.therisk.global/organization/introduction/knowledge.md): how this documentation is organised and how to read it.
* [Organization](https://docs.therisk.global/organization/introduction/organization.md): the institutions and their roles.
* [Acceleration](https://docs.therisk.global/organization/introduction/acceleration.md): the target design of the technology, and the limits on every claim.


---

# 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/introduction/start-here.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.
