> 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/cooperation/nexus-universe/model/x.-participation.md). # X. PARTICIPATION How the Nexus Universe participation model works across public-good institutions, governments, providers, capital readers, communities, and lawful handoff pathways. **Where this fits:** all six sectors ([The Model](/organization/model.md)) · [Nexus Universe](/organization/programme/universe.md), [Risk Academy](/organization/programme/academy.md) · GRF governs the programme; the GCRI technical office prepares it; GRA runs the finance-readiness track · Readiness preparation; Action Week of [the programme year](/organization/programme/the-programme-year.md) · doctrine (participation). **In brief.** Who takes part and how: public-good institutions, governments and multilateral bodies, industry and providers, finance and insurance readers, researchers, builders and volunteers, communities and Indigenous actors, media, and sponsors and hosts. Every route starts from a recorded role and ends in a record; participation never buys a seat, a finding or an approval (UN General Assembly 2024; UN Office of the Envoy on Technology and UNDP 2024). "A cycle gate is a programme decision. It is not a public-authority approval, a certification or a deployment authorisation" (the Universe pillar boundary). {% hint style="info" %} **Read with the current programme year (2026-10-21).** * Everything this page describes is a design in formation. No cycle, edition or mission is recorded as run; the current service level is R0, information and enquiries ([Status and service levels](/organization/governance-in-operation/status-and-service-levels.md)). Where the text below reads as operation, read it as the designed cycle. * The canonical programme year runs through twelve phases in four quarters and gates G0 (annual programme authorised) to G7 (renewal reviewed), with eighteen handoffs between the six pillars. GRF holds the mandate (G0), admission (G1), gate decisions and publication (G6), modelled on exercise direction and separate from controllers and evaluators ([The programme year](/organization/programme/the-programme-year.md); [Nexus Universe](/organization/programme/universe.md)). * Earlier text names Geneva and a fixed flagship. No venue, date or edition of a flagship convening is recorded; the live week is Action Week, one controlled week in Q3 wherever a recorded edition places it. The independent Nexus Universe website is in preparation. * "Competence Cells" is an earlier label. Their work is now National Working Group assignments and, by domain, the six CERTs, which are not emergency services, incident command or privileged access teams ([National Working Groups](/organization/governance-in-operation/nwg.md); [historical labels](/organization/reference.md)). * [NXS-RLS](/organization/systems/nxs-rls.md), called `Nexus Rails` in earlier text, is the system for participants, agreements, protocols, obligations and lawful handoffs ([Systems](/organization/systems.md)). * "Regional Clusters" correspond to the six programme regions and fifteen planned hubs, which are coordination roles, never offices, all in formation ([Regions and hubs](/organization/governance-in-operation/regions-and-hubs.md)). * Project vehicles and national companies are structures that competent, lawful actors may form outside the programme under their own law and licences. The programme never forms, arranges, owns or advises on them ([Lawful handoffs](/organization/finance-readiness/lawful-handoffs.md)). * Recognition, scoring and validation record what was shown under stated conditions. None is a certification, licence, rating or approval, and no country or institution is ranked. * Passports are records: each is identified by a UNI under NS-1 and cited under NS-2 ([NS-1](https://nexustandards.com/standards/ns-1/); [NS-2](https://nexustandards.com/standards/ns-2/)). * Completion is recorded, not credentialed, until [Risk Academy](/organization/institutions/risk-academy.md) has an issuer, an assessment method and a revocation path on record; GCRI Canada is issuer of record ([Risk Academy](/organization/programme/academy.md)). * Docket items are routed in the Q4 docket review; items that need a standard or profile go to [Nexus Standards](/organization/institutions/nexus-standards.md) (handoff F07). {% endhint %} This section explains the **Nexus Universe participation model** and its **whole-ecosystem participation architecture**. It defines how governments, public authorities, public-good institutions, providers, manufacturers, capital readers, insurers, researchers, builders, communities, media, sponsors, and lawful handoff actors participate through clear roles, records, safeguards, finance-readiness boundaries, and correction pathways. It also explains **role-based participation**, **participation records**, **AEP Passports**, **NXS-RLS**, [**NXS-NET**](/organization/systems/nxs-net.md) **(network topology and continuity) Network**, and **lawful handoff**. The core principle is simple: participation in Nexus Universe means accountable contribution to a public-good architecture, not attendance, endorsement, procurement status, finance approval, or execution authority. ## Sections This chapter is published in 10 sections. Together they hold the full text of the chapter. | Section | Words | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----- | | [10.1 The Whole-Ecosystem Participation Model](/organization/cooperation/nexus-universe/model/x.-participation/10.1-the-whole-ecosystem-participation-model.md) | 4,877 | | [10.2 Public-Good Institutional Participants](/organization/cooperation/nexus-universe/model/x.-participation/10.2-public-good-institutional-participants.md) | 5,580 | | [10.3 Government, Public Authority, and Multilateral Participants](/organization/cooperation/nexus-universe/model/x.-participation/10.3-government-public-authority-and-multilateral-participants.md) | 5,561 | | [10.4 Industry, Provider, Manufacturer, OEM, and Infrastructure Participants](/organization/cooperation/nexus-universe/model/x.-participation/10.4-industry-provider-manufacturer-oem-and-infrastructure-partic.md) | 5,842 | | [10.5 Capital Readers, Insurers, DFIs, MDBs, Donors, and Philanthropic Participants](/organization/cooperation/nexus-universe/model/x.-participation/10.5-capital-readers-insurers-dfis-mdbs-donors-and-philanthropic.md) | 5,274 | | [10.6 Universities, Researchers, Builders, Scientists, Volunteers, and Open-Source Participants](/organization/cooperation/nexus-universe/model/x.-participation/10.6-universities-researchers-builders-scientists-volunteers-and.md) | 5,312 | | [10.7 Communities, Indigenous Actors, Civil Society, Youth, and Public-Interest Participants](/organization/cooperation/nexus-universe/model/x.-participation/10.7-communities-indigenous-actors-civil-society-youth-and-public.md) | 5,236 | | [10.8 Media, Communications, Storytelling, and Public Narrative Participants](/organization/cooperation/nexus-universe/model/x.-participation/10.8-media-communications-storytelling-and-public-narrative-parti.md) | 5,406 | | [10.9 Sponsors, Hosts, Partners, and Supporters](/organization/cooperation/nexus-universe/model/x.-participation/10.9-sponsors-hosts-partners-and-supporters.md) | 5,705 | | [10.10 Participant Pathways Into Nexus Network, AEP Passports, and Lawful Handoff](/organization/cooperation/nexus-universe/model/x.-participation/10.10-participant-pathways-into-nexus-network-aep-passports-and-la.md) | 7,690 | ## Sources 1. UN General Assembly (2024). The Pact for the Future. A/RES/79/1, adopted 22 September 2024, with the Global Digital Compact (Annex I) and the Declaration on Future Generations (Annex II). 2. UN Office of the Secretary-General's Envoy on Technology and UNDP (2024). Universal DPI Safeguards Framework. New York: United Nations, September 2024. 3. UN General Assembly (2015). Sendai Framework for Disaster Risk Reduction 2015–2030. A/RES/69/283, 3 June 2015. 4. Nexus Standards. NS-13: Open standards development process. Status: PROPOSED; UNI `NXS-STD-ST-000008`. 5. [The Global Risks Forum](/organization/institutions/grf.md). Nexus Universe at GRF. 6. The Global Risks Forum. Programme governance (GRF's role). 7. The Global Risks Forum. Annual operating cycle. 8. GCRI. Nexus Universe technical office. 9. GCRI. Annual programme cycle. 10. GCRI. Programme status. 11. [The Global Risks Alliance](/organization/institutions/gra.md). Universe finance-readiness programme. 12. This documentation: [Nexus Universe](/organization/programme/universe.md); [The programme year](/organization/programme/the-programme-year.md); [Status and service levels](/organization/governance-in-operation/status-and-service-levels.md). --- # 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/cooperation/nexus-universe/model/x.-participation.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.