> 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/operations.md). # OPERATIONS How the Nexus programme is designed to operate: the operating spine and nine operating layers, from frameworks and charters to reports, forum and platforms. **Where this fits:** all six sectors · all six pillars · GCRI, GRF and GRA · the whole programme year · section landing · read with [The Model](/organization/model.md), [Programme](/organization/programme.md), [Governance in operation](/organization/governance-in-operation.md) and [Reference](/organization/reference.md).
Document record · Draft · Legal review required · Updated 21 October 2026 | | | | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Status** | Draft. Explanatory page; it creates no rights or obligations. | | **Legal review** | Required before final publication. | | **Version** | 2026.10.21-r3 | | **Updated** | 21 October 2026 · reviewed every 180 days | | **Owner** | Documentation desk (named reviewer pending) | | **Based on** | Nexus constitutional directives D-V3-0003 (*Twenty-system constitution*) and D-V3-0004 (*One Rail-Two Stacks and non-execution*); the owner decision of 11 October 2026 on Nexus institutional architecture and participation; the release hold policy and the claim register, in the Nexus institutional register; the Nexus Documentation Standard (draft of 16 October 2026); the sites' model, the Nexus Consortium model, the [Nexus Standards](/organization/institutions/nexus-standards.md) feeds and the owner rulings of 21 October 2026 (source pack) | | **Corrections** | Public corrections route to be announced; corrections are published as new dated versions. |
## In brief The Operations section explains how the Nexus programme is designed to work in practice: how work enters, is routed, owned, recorded, reviewed, corrected and handed to competent actors, and which operating layers carry it, from frameworks and charters to reports, media, forum and platforms. It describes a design, not running services. Its central rule is that activity, visibility and technical access never become authority: only valid authority acting on a record creates institutional meaning, and decisions stay with competent actors \[1]\[2]. {% hint style="success" %} **Aligned to the current model (21 October 2026).** This page was brought up to date with the sites' model, the Nexus Consortium model, the live public sites and the owner rulings (see [Reference](/organization/reference.md) and the [Sources library](/organization/reference/sources.md)). Where the earlier design text below differs, these points govern: * The programme has six pillars, each with a boundary and a measure it answers for: the [Labs pillar](/organization/programme/labs.md), the [Foundry pillar](/organization/programme/foundry.md), [Nexus Universe](/organization/programme/universe.md), Nexus Standards, Nexus Reports and [Risk Academy](/organization/programme/academy.md), joined by eighteen handoffs over one programme year \[7]. See [Programme](/organization/programme.md) and [the programme year](/organization/programme/the-programme-year.md). * The cycle runs Question, Evidence, Build, Organize, Test, Publish, Decide, Renew; the competent authority decides, outside the programme, consistent with the risk-management process of ISO 31000 \[7]\[8]. See [the Nexus cycle](/organization/programme/the-nexus-cycle.md). * Nexus Reports publishes quarterly country editions (Q1 State and Agenda, Q2 Evidence and Build, Q3 Stress Test and Readiness, Q4 Annual Synthesis and Renewal), an annual flagship and specialist series, after review and never to a calendar; an edition is never an official government risk register or a sovereign rating, and current approved releases are none \[9]. Edition records follow the Nexus Standards for identifiers and citation, NS-1 and NS-2 \[10]\[11]. See [Nexus Reports](/organization/programme/reports.md). * Everything described here is in formation. No national programme is recorded as constituted or active, and the current service level is R0, information and enquiries \[12]. See [Status and service levels](/organization/governance-in-operation/status-and-service-levels.md). * Technology is described as the twenty Nexus systems by their NXS codes; providers work with the Nexus Consortium at arm's length under written agreements and are described by role only. See [Systems](/organization/systems.md). {% endhint %} ## Summary The **Nexus Operations** section explains how Nexus is designed to work in practice. It covers operational frameworks, charters, networks, mechanisms, pillars, reports, media, forums and platforms across the ecosystem, and the operating spine that connects them. This section supports readers looking for **operational models**, **digital platform logic**, **implementation pathways** and **system coordination mechanisms**. Each chapter states what its layer is designed to do, what it must not be read to do, and which records would be needed before any part of it could be described as operating. ## What this section covers The ten pages below keep their existing addresses. Each explains one operating layer and links to the deeper reference pages in the [Operations part](/organization/operations.md) of this site.
PageWhat it answersLink
I. OrderWhat operation is, the operating spine from intake to archive, stage truth, decision rights and the institutional roles that bear on operating work.I. Order
II. FrameworksThe core operating methods: the Nexus Agile Framework, the Sustainable Competency Framework and the Distributed Digital Public Goods Framework.II. Frameworks
III. ChartersThe working modes of investigation, collaboration and volunteering, their common anatomy and their draft status.III. Charters
IV. NetworksGeographic working groups and embedded capability, set against the participation pillars, six regions and planned hubs.IV. Networks
V. MechanismsLearning accounts, contribution credits, work-integrated learning, micro-production, value reporting, DICE and the bounded use of risk products from [NXS-GRX](../../systems/nxs-grx.md), the global data and risk intelligence engine.V. Mechanisms
VI. PillarsAcademy, Agency, Labs, Campaigns, Marketplace and Registry as durable operating surfaces, and how they compare with the services named elsewhere.VI. Pillars
VII. ReportsReport classes, status, eligibility, preparation, review, stewardship, correction and supersession.VII. Reports
VIII. MediaPublic communication without overclaim: structural fidelity, maturity truth, review, AI disclosure and corrections.VIII. Media
IX. ForumGoverned convening and how the forum layer differs from [The Global Risks Forum](../../institutions/grf.md) and Nexus Universe.IX. Forum
X. PlatformsGoverned digital environments, status labels, identity and access, data, security, accessibility and AI controls.X. Platforms
In short: * **Frameworks and charters** organize how operational work is carried and bounded. * **Networks, mechanisms, pillars and platforms** are designed to support distributed activity, learning, contribution and coordination. * **Reports, media and forum** connect work with communication, while keeping communication separate from decision. ## How to read this section * **Authority.** Every page here is explanatory (authority level L5). It creates no obligation, adopts no instrument and records no operating service. The Investigation, Collaboration and Volunteers charters summarized in [III. Charters](/organization/introduction/operations/iii.-charters.md) are draft institutional instruments (L4) with no adoption record. Where a page and a binding record disagree, the record prevails \[5]. * **Status.** No framework, charter, network, mechanism, pillar, report series, forum or platform described here is presented as operating. The consortium programme states the current service level as R0, "Information and enquiries" \[3]. * **System capability.** Target architecture. A release hold is in force: no capability has yet been observed in live use, and no capability is described beyond the stage of integrated components, with laboratory or test evidence cited only where it is attached \[4]. * **Names.** Institutional roles use the register wording, stated on [I. Order](/organization/introduction/operations/i.-order.md). [NXS-NSF](/organization/systems/nxs-nsf.md), the trust, sovereignty and assurance plane for identity, policy gates and access decisions, is a constitutional system, not an institution, and Nexus Standards is a proposed standards programme with no publisher of record. Earlier council labels in this corpus, notably Competence Cells, predate the current NNC, NLC and NWG council vocabulary; their mapping awaits owner decision (OQ-14) \[5]. * **Depth.** The child pages keep the full structure of the original chapters (between about 8,500 and 12,500 words each). Splitting them into shorter pages is a later step that needs owner approval. * **Drafting.** This section was drafted with AI assistance and has not yet been reviewed by a named human approver. ## Why it matters Nexus needs operational structure to move from concept to disciplined practice. The operations layer is designed to turn governance, standards and strategy into workflows, tools and repeatable delivery patterns, while keeping the public-good rail separate from lawful execution by competent actors \[2]. This section gives readers the practical map of how Nexus is designed to run. It connects systems, teams, tools and reporting into one operational view, and it says plainly where records are still missing. ## Key relationships
Reading map of the Operations introduction. Frameworks, charters, networks, mechanisms and pillars, with the Organization introduction’s roles and limits and the platforms layer, feed the operating spine. The spine produces reports, media and forum outputs, which inform but never decide, and leads through NXS-RLS, the lawful handoff boundary, to competent actors, who decide.

Figure 1. How the nine operating layers connect through the operating spine, with lawful handoff through [NXS-RLS](../../systems/nxs-rls.md), the technical rails and protocol infrastructure for protocol-governed work across institutions, to competent actors. Design; not a statement of operating services. Source: the ten chapters of this section and D-V3-0003 and D-V3-0004 [1][2], as of 2026-10-16.

Text description of Figure 1 The figure has four columns. On the left are five operating layers: II. Frameworks (NAF, SCF and DDPGF, how work moves), III. Charters (three working charters, all drafts at level L4), IV. Networks (regions, hubs and the NNC, NLC and NWG pillars), V. Mechanisms (learning, credits and value reporting) and VI. Pillars (the six pillars from Academy to Registry). In the second column the Organization introduction, which sets institutional roles and their limits, feeds the operating spine from above, and X. Platforms ([NXS-POR](/organization/systems/nxs-por.md) (public, client and partner delivery) to NXS-RLS, controls and workflows) feeds it from below; all seven inputs converge on the operating spine of I. Order, which runs from intake to archive. The spine produces three communication outputs, VII. Reports, VIII. Media and IX. Forum, which inform but never decide. The single lead path runs from the spine to NXS-RLS, which carries lawful handoffs, transaction envelopes and receipts, and from NXS-RLS to competent actors, who take every decision under their own authority.
## Related topics * [Disaster Risk Intelligence (DRI)](/organization/cooperation/consortiums/frontiers/gra/ecosystem/systems/disaster-risk-intelligence-dri.md), for simulation, dashboards and risk intelligence workflows described in the GRA ecosystem pages. * [Disaster Risk Finance (DRF)](/organization/cooperation/consortiums/frontiers/gra/ecosystem/systems/disaster-risk-finance-drf.md), for finance-readiness and fiscal resilience workflows described in the GRA ecosystem pages. These pages concern readiness, not finance: "Finance-readiness is not finance. Insurance-readiness is not underwriting" (D-V3-0004) \[2], and The Global Risks Alliance (GRA) does not lend, underwrite, rate, invest, advise on or arrange transactions \[6]. ## Canonical definitions used in this section * Institutional roles are stated once, in [I. Order of the Organization introduction](/organization/introduction/organization/i.-order.md). * How to read status words and the boundary formulas is explained in [III. Reading rules](/organization/introduction/knowledge/iii.-reading-rules.md). * The participation pillars (NNC, NLC and NWG) are explained in [I. Order of the Cooperation introduction](/organization/introduction/cooperation/i.-order.md). * The deep reference for every chapter is the [Operations part](/organization/operations.md), with its [overview](/organization/operations/overview.md). ## Next steps * Read [I. Order](/organization/introduction/operations/i.-order.md) for the operating spine, stage truth and decision rights. * Read [II. Frameworks](/organization/introduction/operations/ii.-frameworks.md) for the main operating methods. * Read [V. Mechanisms](/organization/introduction/operations/v.-mechanisms.md) for the operational building blocks. * Read [X. Platforms](/organization/introduction/operations/x.-platforms.md) for the platform layer, its controls and user workflows. ## Related pages * Up: [Introduction](/organization/introduction.md) * Across: [Knowledge](/organization/introduction/knowledge.md) · [Organization](/organization/introduction/organization.md) · [Cooperation](/organization/introduction/cooperation.md) · [Standardization](/organization/introduction/standardization.md) · [Acceleration](/organization/introduction/acceleration.md) * Counterparts: [Operations part](/organization/operations.md) · [Systems](/organization/systems.md) ## Sources 1. Nexus constitutional directive D-V3-0003, *Twenty-System Constitution* (canonical order, identifiers and remits, including NXS-RLS). Internal record, cited by identifier. 2. Nexus constitutional directive D-V3-0004, *One Rail-Two Stacks, Non-Execution and Lawful Handoff Constitution* (public-good rail, enterprise and sovereign execution stack, boundary formulas). Internal record, cited by identifier. 3. Nexus institutional register: consortium programme (participation pillars, service levels R0 to R5, current service level R0). Internal record. 4. Nexus institutional register: release hold policy (in force) and claim register. Internal record. 5. Nexus Documentation Standard, draft of 16 October 2026: authority, status, naming and council vocabulary; owner decisions of 16 October 2026; introduction operations audit of 16 October 2026. Internal editorial records; not published. 6. Public institutional site draft (not yet published; owner direction, not a binding record): GRA boundary sentence. Draft source. 7. GCRI (2026). *How Nexus works: the six pillars and the Nexus cycle*. Global Centre for Risk and Innovation. [therisk.global](https://therisk.global/nexus-cycle/). Accessed 2026-10-21. 8. ISO (2018). *ISO 31000:2018 Risk management: Guidelines*. International Organization for Standardization. [iso.org](https://www.iso.org/standard/65694.html). Accessed 2026-10-21. 9. GCRI (2026). *Nexus Reports programme*: quarterly country editions, an annual flagship and specialist series; current approved releases: none. [therisk.global](https://therisk.global/publications/nexus-reports/). Accessed 2026-10-21. 10. Nexus Standards (2026). *NS-1: The UNI and the artifact catalog* (PROPOSED), UNI NXS-STD-ST-000001. [nexustandards.com](https://nexustandards.com/standards/ns-1/). Accessed 2026-10-21. 11. Nexus Standards (2026). *NS-2: Citation and attribution* (PROPOSED), UNI NXS-STD-ST-000009. [nexustandards.com](https://nexustandards.com/standards/ns-2/). Accessed 2026-10-21. 12. GCRI (2026). *Programme status*: programme states and the current service level R0. [therisk.global](https://therisk.global/consortium/programme-status/). Accessed 2026-10-21. ## Editorial record * As of: 2026-10-21. Refresh: every 180 days, or sooner when a governing source changes. * Drafting: AI-assisted. Human review: pending; no named reviewer or approver yet. * Corrections: a public corrections route has not yet been published. Corrections will be recorded as new dated versions, not silent edits. * Change: 2026-10-16, upgraded to the documentation standard draft. Record block, In brief, cards to all ten child pages, reading note with the system status sentence, key-relationships figure, canonical definitions, related pages and sources added; original summary, coverage, related topics, rationale and next steps kept and corrected ("+" separator artefacts and the em dash removed; present-tense operating claims recast as design; DRI and DRF pages reframed with the finance-readiness boundary instead of "operational finance"). * Change: 2026-10-16 r2, owner decisions of the second round applied: readable document record, plain-language status notes and sources, Nexus Standards display codes for systems, Nexus Observatory Protocol, and no company named. * Change: 2026-10-21 r3, aligned to the current model: "Where this fits" line; alignment note on the six pillars, the programme year, [National Nexus](/organization/governance-in-operation/national-nexus.md) (NNC, NLC, NWG, [CERTs](/organization/governance-in-operation/nwg.md)), the [Helix councils](/organization/governance-in-operation/councils.md), the finance boundary, quarterly Nexus Reports, the [Risk Academy](/organization/institutions/risk-academy.md) issuance rule and the current service level R0; earlier council labels mapped under rulings R3 to R5; sources added from the public sites, the Nexus Standards and the external reference register; the earlier design text kept in full. --- # 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/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.