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

# IX. FRONTIERS

Nexus Universe uses a three-force model that connects GCRI, GRF, and GRA across public-good systems-build, public authority learning, finance-readiness, and lawful handoff.

**Where this fits:** all six sectors ([The Model](/organization/model.md)) · [Nexus Universe](/organization/programme/universe.md) · GRF governs the programme; the GCRI technical office prepares it; GRA runs the finance-readiness track · every phase of [the programme year](/organization/programme/the-programme-year.md) · doctrine (institutions).

**In brief.** The three-force model: GCRI (GCRI Canada, with GCRI US as a separate organization) drives evidence, methods and the technical office; [The Global Risks Forum](/organization/institutions/grf.md) (GRF) governs the programme, holds its gate decisions and convenes; [The Global Risks Alliance](/organization/institutions/gra.md) (GRA) makes risk evidence readable to finance and insurance. They share governance without merging roles, and none is the parent, agent or regulator of another (OECD 2014). "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 %}

Nexus Universe depends on a three-force institutional model that connects GCRI, GRF, and GRA across public-good systems-build, disaster risk reduction, disaster risk finance, disaster risk intelligence, and WEFH-B systems.

This institutional arc links public authority learning, finance-readiness, capital-readability, public-safe reporting, AEP Passports, NXS-RLS, Nexus Observatory, Docket discipline, Public-Good Stack boundaries, Enterprise Stack handoff, and correctionability into one annual de-risking engine.

## Sections

This chapter is published in 10 sections. Together they hold the full text of the chapter.

| Section                                                                                                                                                                                                                                                  | Words |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----- |
| [9.1 The Three-Force Model](/organization/cooperation/nexus-universe/model/ix.-froniers/9.1-the-three-force-model.md)                                                                                                                                    | 4,245 |
| [9.2 GCRI Canada and GCRI US as Technical and Evidence Drivers](/organization/cooperation/nexus-universe/model/ix.-froniers/9.2-gcri-canada-and-gcri-us-as-technical-and-evidence-drivers.md)                                                            | 4,574 |
| [9.3 The Global Risks Forum (GRF) as Public-Good, Policy, Standards-Interface, Convening, and Claims-Discipline Driver](/organization/cooperation/nexus-universe/model/ix.-froniers/9.3-the-global-risks-forum-grf-as-public-good-policy-standards-i.md) | 4,462 |
| [9.4 GRA US as Finance-Readiness and Financial-Service-Integration Driver](/organization/cooperation/nexus-universe/model/ix.-froniers/9.4-gra-us-as-finance-readiness-and-financial-service-integratio.md)                                              | 4,360 |
| [9.5 Shared Governance Without Role Merger](/organization/cooperation/nexus-universe/model/ix.-froniers/9.5-shared-governance-without-role-merger.md)                                                                                                    | 4,616 |
| [9.6 Public-Good / Enterprise-Stack Boundary Stewardship](/organization/cooperation/nexus-universe/model/ix.-froniers/9.6-public-good-enterprise-stack-boundary-stewardship.md)                                                                          | 5,021 |
| [9.7 Claims, Records, and AEP Passport Joint Discipline](/organization/cooperation/nexus-universe/model/ix.-froniers/9.7-claims-records-and-aep-passport-joint-discipline.md)                                                                            | 4,685 |
| [9.8 Institutional Interfaces With Regions, Nations, Providers, Capital Readers, and Communities](/organization/cooperation/nexus-universe/model/ix.-froniers/9.8-institutional-interfaces-with-regions-nations-providers-capi.md)                       | 6,034 |
| [9.9 Institutional Legitimacy, Legal Separateness, and Non-Execution](/organization/cooperation/nexus-universe/model/ix.-froniers/9.9-institutional-legitimacy-legal-separateness-and-non-executio.md)                                                   | 5,783 |
| [9.10 Institutional Arc Statement](/organization/cooperation/nexus-universe/model/ix.-froniers/9.10-institutional-arc-statement.md)                                                                                                                      | 5,051 |

## Sources

1. OECD (2014). Recommendation of the Council on the Governance of Critical Risks. OECD/LEGAL/0405, adopted 6 May 2014. <https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405>
2. OECD (2018). OECD DAC Blended Finance Principles for Unlocking Commercial Finance for the Sustainable Development Goals. Paris: OECD, December 2018. <https://www.oecd.org/en/publications/2018/12/oecd-dac-blended-finance-principles_898d3549.html>
3. Nexus Standards. NS-0: Constitution and principles. Status: PROPOSED; UNI `NXS-STD-ST-000004`. <https://nexustandards.com/standards/ns-0/>
4. The Global Risks Forum. Nexus Universe at GRF. <https://globalriskforum.com/nexus-universe/>
5. The Global Risks Forum. Programme governance (GRF's role). <https://globalriskforum.com/nexus-universe/grf-role/>
6. The Global Risks Forum. Annual operating cycle. <https://globalriskforum.com/nexus-universe/annual-cycle/>
7. GCRI. Nexus Universe technical office. <https://therisk.global/programmes/nexus-universe/>
8. GCRI. Annual programme cycle. <https://therisk.global/programmes/annual-cycle/>
9. GCRI. Programme status. <https://therisk.global/consortium/programme-status/>
10. The Global Risks Alliance. Universe finance-readiness programme. <https://globalriskalliance.com/engagement/nexus-universe/>
11. 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/ix.-froniers.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.
