> 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/operations/pillars.md). # PILLARS **Where this fits:** all six sectors · [the six pillars](/organization/programme.md) · the Nexus Consortium · the programme year · section landing. **In brief.** This page is the landing of PILLARS. Each pillar keeps its own boundary; no pillar decides for a public authority, and nothing here is a certification, an approval or a deployment. {% hint style="info" %} **Read with the current model (21 October 2026).** This section holds the earlier operating pillar set. The programme now has six pillars, each with its measures generated from the sites' model ([Programme](/organization/programme.md)). The table maps each earlier pillar to its successors. Everything here is in formation; the current service level is R0, information and enquiries ([Programme status](https://therisk.global/consortium/programme-status/)). {% endhint %} ## From the earlier pillar set to the six pillars | Earlier pillar | Page | Successor pillars | | -------------- | ----------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | | Academy | [Academy](/organization/operations/pillars/i.-academy.md) | [Risk Academy](/organization/programme/academy.md) | | Agency | [Agency](/organization/operations/pillars/ii.-agency.md) | [Nexus Universe](/organization/programme/universe.md), [Foundry](/organization/programme/foundry.md) | | Labs | [Labs](/organization/operations/pillars/iii.labs.md) | [Labs](/organization/programme/labs.md) | | Campaigns | [Campaigns](/organization/operations/pillars/iv.-campaigns.md) | [Nexus Universe](/organization/programme/universe.md), [Nexus Reports](/organization/programme/reports.md) | | Marketplace | [Marketplace](/organization/operations/pillars/v.-marketplace.md) | [Foundry](/organization/programme/foundry.md), [Nexus Universe](/organization/programme/universe.md) | | Registry | [Registry](/organization/operations/pillars/vi.-registry.md) | [Nexus Standards](/organization/programme/standards.md) | | Reports | [Reports](/organization/operations/pillars/vii.-reports.md) | [Nexus Reports](/organization/programme/reports.md) | | 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/) | ## Sources 1. ISO (2018). ISO 31000:2018 Risk management — Guidelines. Geneva: International Organization for Standardization. 2. How Nexus works. 3. Programme status. --- # 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/operations/pillars.md?ask=&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.