> 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.md). # OPERATIONS Nexus operations for operational frameworks, digital platforms, governance mechanisms, networks, reporting systems, and deployment workflows. **Where this fits:** all six sectors · [the six pillars](/organization/programme.md) · the Nexus Consortium · the programme year · part landing. **In brief.** The **Nexus Operations** section defines how Nexus runs in practice. Operations describe designs in formation; nothing here is a deployment, a certification or a decision for a public authority.
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.

The six pillars and their eighteen handoffs. 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.

Figure data (text alternative) | 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) |
{% hint style="info" %} **Read with the current model (21 October 2026).** Operations holds the earlier operating layer: pillars, mechanisms, [Nexus Reports](/organization/programme/reports.md) guides, media, the forum and the networks. Read it with the current model: the six pillars ([Programme](/organization/programme.md)), the programme year ([The programme year](/organization/programme/the-programme-year.md)), [National Nexus](/organization/governance-in-operation/national-nexus.md) and its participation pillars ([Governance in operation](/organization/governance-in-operation.md)) and the systems by NXS code ([Systems](/organization/systems.md)). Risk practice follows ISO 31000 ([ISO, 2018](https://www.iso.org/standard/65694.html)). Everything here is in formation; the current service level is R0, information and enquiries ([Programme status](https://therisk.global/consortium/programme-status/)). {% endhint %} The **Nexus Operations** section defines how Nexus runs in practice. It connects **operational frameworks**, **digital platforms**, **governance mechanisms**, **network operations**, **reporting systems**, and **deployment workflows** into one operational architecture. This section explains how Nexus moves from institutional design into day-to-day execution. It supports program delivery, operational planning, platform governance, reporting, media workflows, and implementation across national, regional, and global environments. ### What this section covers * **Operational frameworks** for governance, delivery, and implementation. * **Digital platforms** for accounts, publishing, discovery, groups, and journals. * **Governance mechanisms** for learning, reporting, rewards, and value systems. * **Network operations** for working groups, competence cells, and coordination. * **Operational reporting and media workflows** for submissions, manuscripts, and topic management. ### Core operations themes * **Operational architecture** for structured execution across Nexus systems. * **Platform operations** for digital infrastructure, publishing, and community workflows. * **Governance operations** for mechanisms, reporting, and institutional coordination. * **Network management** across regions, groups, and operational cells. * **Implementation readiness** for scalable, auditable, and repeatable operations. ### Explore this section * [OVERVIEW](/organization/operations/overview.md) - the top-level overview of Nexus operations. * [FRAMEWORKS](/organization/operations/frameworks.md) - operational frameworks such as the Nexus Agile Framework, Sustainable Competency Framework, and Distributed Digital Public Goods Framework. * [CHARTERS](/organization/operations/charters.md) - charter-based operating models for investigation, collaboration, and volunteers. * [NETWORKS](/organization/operations/networks.md) - working groups, regions, and competence-cell operations. * [MECHANISMS](/organization/operations/mechanisms.md) - integrated learning, rewards, reporting, and production mechanisms. * [PILLARS](/organization/operations/pillars.md) - academy, agency, labs, campaigns, marketplace, and registry pillars. * [REPORTS](/organization/operations/reports.md) - eligibility, preparation, submission, stewardship, and manuscript workflows. * [MEDIA](/organization/operations/media.md) - media operations, policy, and topic management. * [FORUM](/organization/operations/forum.md) - program structure, technical implementation, strategic management, and appendices. * [PLATFORMS](/organization/operations/platforms.md) - platform operations for identity, content, search, groups, rooms, and publishing. The **Nexus Operations** page is the entry point for execution across Nexus. It connects frameworks, platforms, mechanisms, reports, networks, and media into one searchable structure for operational governance and delivery. ## Sources 1. ISO (2018). ISO 31000:2018 Risk management — Guidelines. Geneva: International Organization for Standardization. 2. How Nexus works. 3. Programme status. 4. How Nexus Consortium works. --- # 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.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.