> 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/consortiums/frontiers.md).

# FRONTIERS

Nexus frontier governance for AI, sovereign interoperability, public-good infrastructure, and systemic risk.

**Where this fits:** all six sectors ([The Model](/organization/model.md)) · [Labs](/organization/programme/labs.md), [Risk Academy](/organization/programme/academy.md) · earlier frontier layers of GCRI, GRF and GRA ([Institutions](/organization/institutions.md)) · historical layer (2024-25).

**In brief.** FRONTIERS defines the Nexus frontier agenda for global governance, public-good infrastructure, sovereign interoperability, systemic risk, and frontier technologies in the age of exponential systems. Read against the international frameworks it serves ([UN General Assembly 2015](https://www.undrr.org/publication/sendai-framework-disaster-risk-reduction-2015-2030); [United Nations 2021](https://www.un.org/en/common-agenda); [UN General Assembly 2024](https://undocs.org/A/RES/79/1)) and the [Nexus Standards](/organization/institutions/nexus-standards.md) that govern its records ([NS-0](https://nexustandards.com/standards/ns-0/)). Frontier texts describe earlier designs: none records a treaty, legal personality, immunity, regulator status, issued credential or adopted instrument, and no institution holds supranational authority.

{% hint style="info" %}
**Read with the current model (2026-10-21).**

* Everything this page describes is a design in formation. No national, regional or global consortium is recorded as constituted or active; 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 design.
  {% endhint %}

FRONTIERS defines the Nexus frontier agenda for global governance, public-good infrastructure, sovereign interoperability, systemic risk, and frontier technologies in the age of exponential systems.

It connects frontier science, AI, sovereign compute, observability, finance-readiness, public-safe reporting, and the Nexus Consortium architecture.

### What FRONTIERS covers

This section explains how Nexus approaches frontier technologies and high-consequence systems.

It focuses on the institutional architecture needed to turn technical capability into evidence, public legitimacy, finance-readable readiness, and lawful handoff.

Key themes include:

* frontier technologies and public-good infrastructure
* sovereign interoperability and systemic risk governance
* observability, standards, and finance-readiness

### Core institutions

FRONTIERS is organized around four core pages.

* [MISSION](/organization/cooperation/consortiums/frontiers/mission.md) defines the overall doctrine for Nexus frontier governance.
* [GCRI](/organization/cooperation/consortiums/frontiers/gcri.md) covers the technical evidence and innovation layer.
* [GRF](/organization/cooperation/consortiums/frontiers/grf.md) covers public legitimacy, convening, and public-safe reporting.
* [GRA](/organization/cooperation/consortiums/frontiers/gra.md) covers finance-readiness, capital-readability, and development pathways.

### Why this section matters

Frontier systems now shape resilience, infrastructure, public authority capacity, and long-horizon development.

Nexus provides a public-good operating model that helps governments, institutions, and partners govern those systems without collapsing evidence, legitimacy, and capital into one layer.

### Related topics

FRONTIERS connects closely with the wider Nexus consortium model and operating definitions.

* [CONSORTIUMS](/organization/cooperation/consortiums.md) places FRONTIERS in the broader Nexus cooperation and consortium structure.
* [III. FOUNDERS](/organization/cooperation/consortiums/model/iii.-founders.md) explains the GCRI, GRF, and GRA three-force model behind this section.
* [IV. GLOBAL](/organization/cooperation/consortiums/model/iv.-global.md) shows how frontier governance connects to the global consortium layer, Nexus Universe, and global coordination.
* [Nexus Network](/organization/organization/architecture/ii.-definitions/ii.-nexus-network.md) explains the permanent federated infrastructure layer behind frontier deployment.
* [Nexus Observatory](/organization/organization/architecture/ii.-definitions/iv.-nexus-observatory.md) defines the observability and public-safe reporting layer referenced across FRONTIERS.

### Summary

FRONTIERS introduces the Nexus approach to frontier governance, sovereign interoperability, public-good infrastructure, and systemic risk.

It links technical evidence, public legitimacy, and finance-readiness across the core institutions that govern high-consequence systems.

### Next steps

* Start with [MISSION](/organization/cooperation/consortiums/frontiers/mission.md) for the full frontier governance doctrine.
* Continue to [GCRI](/organization/cooperation/consortiums/frontiers/gcri.md), [GRF](/organization/cooperation/consortiums/frontiers/grf.md), and [GRA](/organization/cooperation/consortiums/frontiers/gra.md) to see how the triad works in practice.
* Use [Nexus Standards](/organization/organization/architecture/ii.-definitions/xii.-nexus-standards.md) and [Nexus Risk Management](/organization/organization/architecture/ii.-definitions/xiii.-nexus-risk-management.md) for the operating layers behind readiness and interoperability.

## Sources

1. UN General Assembly (2015). Sendai Framework for Disaster Risk Reduction 2015–2030. A/RES/69/283, 3 June 2015. <https://www.undrr.org/publication/sendai-framework-disaster-risk-reduction-2015-2030>
2. United Nations (2021). Our Common Agenda: Report of the Secretary-General. New York: United Nations. <https://www.un.org/en/common-agenda>
3. 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). <https://undocs.org/A/RES/79/1>
4. Nexus Standards. NS-0: Constitution and principles. Status: PROPOSED; UNI `NXS-STD-ST-000004`. <https://nexustandards.com/standards/ns-0/>
5. GCRI. GCRI, GRF and GRA. <https://therisk.global/consortium/institutions/>
6. GCRI. GCRI Canada. <https://therisk.global/about/gcri-canada/>
7. [The Global Risks Forum](/organization/institutions/grf.md). GRF in the Consortium. <https://globalriskforum.com/about/consortium-role/>
8. [The Global Risks Alliance](/organization/institutions/gra.md). GRA in the Consortium. <https://globalriskalliance.com/about/consortium-role/>
9. This documentation: [Governance in operation](/organization/governance-in-operation.md); [The Model](/organization/model.md); [historical labels](/organization/reference.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/consortiums/frontiers.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.
