> 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/programme.md).

# PROGRAMME

The Nexus programme: six pillars that hand work to one another over one programme year, led by the Nexus Consortium and carried by GCRI, GRF and GRA, each in its role.

*Where this fits: the applied-response side of the model. Pillars: all six. Institutions: GCRI, GRF and GRA. Cycle: the whole* [*programme year*](/organization/programme/the-programme-year.md)*. Kind: part landing.*

**In brief.** The programme answers coupled risk with six pillars. The Labs pillar explores, the Foundry pillar builds, Nexus Universe convenes and tests, [Nexus Standards](/organization/institutions/nexus-standards.md) codifies and corrects, Nexus Reports publishes and [Risk Academy](/organization/institutions/risk-academy.md) teaches. Each pillar hands its work to the next through eighteen recorded handoffs, and the year closes when the findings of one cycle set the mandate of the next. Every pillar is led by the Nexus Consortium. GCRI, [The Global Risks Forum](/organization/institutions/grf.md) (GRF) and [The Global Risks Alliance](/organization/institutions/gra.md) (GRA) each contribute in their own role, and none is the parent, agent or regulator of another ([GCRI, GRF and GRA](https://therisk.global/consortium/institutions/)). Nothing on these pages records a running programme: the cycle is a designed specification, no edition has been released, no credential has been issued, and every programme is at service level R0, "information and enquiries" ([Programme status](https://therisk.global/consortium/programme-status/)).

The six pillars are the same six shown on the right-hand hexagon of the GCRI, GRF and GRA home pages ([How Nexus works](https://therisk.global/nexus-cycle/)). The tables on this page are generated from that model, so the documentation and the sites cannot drift apart.

<figure><picture><source srcset="/files/PQPoJndQgIqy5zhOiKxk" 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-f8b2e2a1caabaff994d5282fd8fe82367e0e82e4%2Fprogramme-pillar-hex-light.svg?alt=media" alt="The six pillars of the programme on one hexagon: Labs at the top, then clockwise Foundry, Nexus Universe, Nexus Standards, Nexus Reports and Risk Academy. Fourteen recorded handoffs (F01 to F14) carry work between pillars in named phases of the programme year, and four ring handoffs (R1 to R4) carry it around the ring continuously. With every pillar selected, all eighteen handoffs are in play and seventeen feedback loops close. Underneath, the eight phases of the year in which recorded handoffs happen."></picture><figcaption><p><strong>The six pillars and their eighteen handoffs.</strong> The same pillar model as the GCRI, GRF and GRA home pages. A designed programme cycle, not a record of operation: no edition has been released and no credential issued. 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                 |
| --------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- |
| 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 in play | Foundry to Reports: Sealed observations and indicator series behind a profile                                                                                       | Closeout              |
| F04                   | Handoff in play | Universe to Reports: After-action and scenario findings for chapters 10 and 13                                                                                      | After-action review   |
| F05                   | Handoff in play | Foundry to Reports: National Portfolio movement for chapter 11                                                                                                      | After-action review   |
| F06                   | Handoff in play | 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 in play | 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 in play | Standards to Reports: Applied in editions                                                                                                                           | Around the ring       |
| R2                    | Handoff in play | 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          | Explore, experiment and prototype                                                                                                                                   | in this route         |
| Foundry               | Pillar          | Build, simulate and prepare                                                                                                                                         | in this route         |
| Universe              | Pillar          | Convene and test                                                                                                                                                    | in this route         |
| Standards             | Pillar          | Codify, correct and apply                                                                                                                                           | in this route         |
| Reports               | Pillar          | Publish in every format                                                                                                                                             | in this route         |
| Academy               | Pillar          | Teach in the open                                                                                                                                                   | in this route         |
| 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>

## The six pillars

| Pillar                                                  | Does                              | Role                                                                                                                                                                                           | Steward                                                                | Public home                                                           |
| ------------------------------------------------------- | --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | --------------------------------------------------------------------- |
| [Labs](/organization/programme/labs.md)                 | Explore, experiment and prototype | Where questions become experiments and prototypes: new methods, data and tools are tried in the open, with their limits on record, before the Foundry builds them, under the Nexus Consortium. | The Nexus Consortium                                                   | [therisk.global/nexus-labs](https://therisk.global/nexus-labs/)       |
| [Foundry](/organization/programme/foundry.md)           | Build, simulate and prepare       | Where things are built, simulated and prepared: every output of GCRI, GRF and GRA, under the Nexus Consortium.                                                                                 | The Nexus Consortium                                                   | [The twenty systems](/organization/systems.md)                        |
| [Nexus Universe](/organization/programme/universe.md)   | Convene and test                  | Where everything comes together in the annual programme, with GCRI, GRF and GRA each contributing in its role and capacity.                                                                    | The Global Risks Forum (programme steward), under the Nexus Consortium | [universe.nexus](https://universe.nexus/)                             |
| [Nexus Standards](/organization/programme/standards.md) | Codify, correct and apply         | Where all standards are developed, corrected and applied, in the open, with adoption decided by each jurisdiction.                                                                             | Nexus Standards, with GCRI Canada as secretariat                       | [nexustandards.com](https://nexustandards.com/)                       |
| [Nexus Reports](/organization/programme/reports.md)     | Publish in every format           | Where all outputs are published, in all formats, across its five sites, each with sources, limits and corrections.                                                                             | The Nexus Consortium                                                   | [therisk.global/nexus-reports](https://therisk.global/nexus-reports/) |
| [Risk Academy](/organization/programme/academy.md)      | Teach in the open                 | Where everything is taught in the open, in real locations and for impact, by learning on real cycle work.                                                                                      | Risk Academy, with GCRI Canada as issuer of record                     | [risksacademy.com](https://risksacademy.com/academy-home/)            |

Each pillar keeps one boundary, quoted on its page. Taken together, the six boundaries are the programme's guarantee that evidence never passes for authority. An experiment is not evidence until it has been rebuilt and tested. A simulated capability is not a validated result. A gate is not a public-authority approval. A validator report is not a conformance claim. An edition is not an official risk register or a sovereign rating. A completion record is not a licence to practise.

## Who carries each pillar

The programme is not run by a single organisation. GCRI Canada is Lead Institution, Consortium Secretariat and lead contracting organization. GRF stewards Nexus Universe and records its gates. GRA makes risk evidence readable to finance and insurance and carries out no regulated financial activity. The table gives each institution's contribution to each pillar.

| Institution                                                      | Role in the programme                                                                                                               | Labs                                                                                                                                        | Foundry                                                                                                                    | Universe                                                                                    | Standards                                                                                                                             | Reports                                                                                          | Academy                                                                            |
| ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------- |
| [Global Centre for Risk and Innovation](https://therisk.global/) | Evidence and build: science, methods, data and the technical work behind every pillar; Lead Institution and Consortium Secretariat. | Runs the experiments: its science and technology teams design prototypes, record the method and publish what failed as well as what worked. | Its science and technical platforms bring the methods, data and evidence that the Foundry builds on.                       | Its technical office prepares the scientific and data readiness of each mission.            | GCRI Canada is publisher of record and secretariat; GCRI stewards the evidence, methods, data and open research behind the standards. | Hosts the canonical Nexus Reports site and publishes evidence on countries, sectors and methods. | Authors courses on methods, data and the Foundry systems, hosted on Risk Academy.  |
| [Global Risks Forum](https://globalriskforum.com/)               | Mandate and convening: stewards Nexus Universe and records each programme gate.                                                     | Brings the questions that policy and governance need answered, and admits an experiment to the programme at a recorded gate.                | Admits missions and accepts the build for exercise at a recorded gate, so Foundry work enters the programme on the record. | Stewards and governs the programme: the mandate, gates G0 to G7, convening and Action Week. | Convenes participation and keeps the public record of recognition and standing.                                                       | Publishes governance analysis and authorises publication of the year's results at gate G6.       | Authors courses on governance, policy and programme roles, hosted on Risk Academy. |
| [Global Risks Alliance](https://globalriskalliance.com/)         | Finance readability: makes risk evidence readable to finance and insurance.                                                         | Brings finance questions to test, so a prototype is tried on evidence that financial institutions can read.                                 | Brings finance-readiness questions, so builds produce evidence that financial institutions can read.                       | Runs finance-readiness dialogues on what each mission means for finance and insurance.      | Makes the standards readable to finance and insurance.                                                                                | Publishes sector analysis and the finance and insurance readiness series.                        | Authors courses on finance, insurance and readiness, hosted on Risk Academy.       |

Decisions about public action are never taken inside the programme. Every step of the [Nexus cycle](/organization/programme/the-nexus-cycle.md) that decides belongs to "the relevant government, operator or licensed institution" ([Board and governance](https://therisk.global/about/board-and-governance/)).

## Pages in this part

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Labs</strong></td><td>Explore, experiment and prototype in the open</td><td><a href="/organization/programme/labs.md">Labs</a></td></tr><tr><td><strong>Foundry</strong></td><td>Build, simulate and prepare</td><td><a href="/organization/programme/foundry.md">Foundry</a></td></tr><tr><td><strong>Nexus Universe</strong></td><td>Convene and test: the annual programme</td><td><a href="/organization/programme/universe.md">Nexus Universe</a></td></tr><tr><td><strong>Nexus Standards</strong></td><td>Codify, correct and apply</td><td><a href="/organization/programme/standards.md">Nexus Standards</a></td></tr><tr><td><strong>Nexus Reports</strong></td><td>Publish in every format, each quarter</td><td><a href="/organization/programme/reports.md">Nexus Reports</a></td></tr><tr><td><strong>Risk Academy</strong></td><td>Teach in the open, by learning on real cycle work</td><td><a href="/organization/programme/academy.md">Risk Academy</a></td></tr><tr><td><strong>The programme year</strong></td><td>Time scales, quarters, phases, gates G0 to G7, and every actor in them</td><td><a href="/organization/programme/the-programme-year.md">The programme year</a></td></tr><tr><td><strong>The Nexus cycle</strong></td><td>Eight steps from a question to renewal, and who decides</td><td><a href="/organization/programme/the-nexus-cycle.md">The Nexus cycle</a></td></tr><tr><td><strong>Identifiers and records</strong></td><td>One UNI for every cycle object, and the records each pillar owns</td><td><a href="/organization/programme/identifiers-and-records.md">Identifiers and records</a></td></tr></tbody></table>

## From observation to decision

The pillars rest on one evidence path. A signal becomes an observation, the observation becomes governed evidence, and the evidence reaches a competent authority, which alone decides.

<figure><picture><source srcset="/files/W4ykxuEifvmSaWBJizyj" 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-328a50d456aab7583da4b132425f1d57a12c4e16%2Fevidence-to-decision-light.svg?alt=media" alt="Observatories capture a signal and structure it into an observation under Nexus Observatory Protocol. NXS-GRX holds it as governed evidence with quality and provenance, and an evidence review checks it. NXS-EWS may prepare a warning-support candidate and NXS-AAP a trigger check; NXS-DSS assembles a decision-support package. The NXS-NSF policy gate releases it, and NXS-RLS hands it off under written agreements. The competent authority alone decides and issues any warning; corrections return to the observatories."></picture><figcaption><p><strong>From observation to decision.</strong> Indicative material only, never an official warning; a design of the sequence, not a record of any run. Source: D-V3-0003 and D-V3-0004. As of 2026-10-20.</p></figcaption></figure>

<details>

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

| Element                   | Description                        | Connected to                                 |
| ------------------------- | ---------------------------------- | -------------------------------------------- |
| Signal captured           | Remote, in-situ or edge            | Observation                                  |
| Observation               | Under Nexus Observatory Protocol   | Signal captured; Governed evidence           |
| Governed evidence         | Quality and provenance             | Observation; Evidence review                 |
| Evidence review           | Checked before use                 | Governed evidence; Warning-support candidate |
| Warning-support candidate | NXS-EWS; never an alert            | Evidence review; Decision-support package    |
| Decision-support package  | NXS-DSS with NXS-AAP trigger check | Warning-support candidate; Policy gate       |
| Policy gate               | NXS-NSF release                    | Decision-support package; Lawful handoff     |
| Lawful handoff            | NXS-RLS under written agreements   | Policy gate; Decision                        |
| Decision                  | The authority alone decides        | Lawful handoff; Any warning issued           |
| Any warning issued        | By the authority, not by Nexus     | Decision                                     |

</details>

## Read further

* [The model](/organization/model.md): coupled risk and applied response, the two hexagons behind this part.
* [Institutions](/organization/institutions.md): GCRI, GRF, GRA and the Nexus Consortium.
* [Foundry technical reference](/organization/systems.md): the twenty systems on which the pillars run.
* [Cooperation](/organization/cooperation.md) and [Operations](/organization/operations.md): the earlier, deeper doctrine of the Consortium, Nexus Universe, frameworks and reporting.

## Sources

* GCRI, [How Nexus works](https://therisk.global/nexus-cycle/), the six pillars and their handoffs, as of 2026-10-21.
* GCRI, [GCRI, GRF and GRA](https://therisk.global/consortium/institutions/) and [Board and governance](https://therisk.global/about/board-and-governance/), the institutions and their decision rights.
* GCRI, [Programme status](https://therisk.global/consortium/programme-status/), the seven-state status machine and service level R0.
* Pillar model and programme spine of the sites (vendored in the documentation repository, `tools/figures/vendor/nexus-model`), the source of every generated table on this page.


---

# 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/programme.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.