> 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.md). # CONSORTIUMS Nexus consortiums for global, regional, and national consortium governance, public-good coordination, sovereign interoperability, and lawful implementation. ## Nexus consortiums Nexus consortiums define the cooperation model for global, regional, and national coordination. They connect consortium governance, public-good infrastructure, sovereign interoperability, and lawful implementation across institutions and jurisdictions. This structure helps partners move from shared agenda to accountable execution. It keeps stewardship, coordination, ownership, and delivery aligned. ### What Nexus consortiums do * organize global, regional, and national consortium governance * align institutions around public-good coordination and shared implementation * support sovereign interoperability, national ownership, and lawful deployment ### Consortium levels Nexus works through three connected consortium layers. * **Global consortium** sets shared doctrine, standards, stewardship, and cross-system coordination. * **Regional consortiums** align neighboring jurisdictions, regional priorities, and corridor-level implementation. * **National consortiums** anchor local ownership, lawful execution, and institutional accountability. ### Core consortium surfaces Two pages define the main operating view for this section. * [MODEL](/organization/cooperation/consortiums/model.md) covers the consortium model for governance, ownership, councils, boards, and operating vehicles. * [FRONTIERS](/organization/cooperation/consortiums/frontiers.md) covers frontier governance, systemic risk, public-good infrastructure, and sovereign interoperability. ### Related topics Use these pages to move from the consortium model to each operating layer. * [IV. GLOBAL](/organization/cooperation/consortiums/model/iv.-global.md) and [XXI. Global Nexus Consortium (GNC)](/organization/organization/architecture/ii.-definitions/xxi.-global-nexus-consortium-gnc.md) explain global stewardship and cross-system coordination. * [V. REGIONAL](/organization/cooperation/consortiums/model/v.-regional.md) and [XX. Regional Nexus Consortium (RNC)](/organization/organization/architecture/ii.-definitions/xx.-regional-nexus-consortium-rnc.md) show how regional alignment and corridor implementation work. * [VI. NATIONAL](/organization/cooperation/consortiums/model/vi.-national.md) and [XIX. National Nexus Consortium (NNC)](/organization/organization/architecture/ii.-definitions/xix.-national-nexus-consortium-nnc.md) cover national ownership, lawful deployment, and local accountability. ### Why consortiums matter Complex cooperation fails when governance and implementation split apart. Nexus consortiums keep strategy, legitimacy, finance-readiness, and execution in one institutional model. That makes multilateral coordination easier to govern. It also makes national adoption easier to implement. ### Summary Nexus consortiums provide the institutional architecture for cooperation across global, regional, and national levels. They support consortium governance, public-good coordination, sovereign-compatible deployment, and accountable implementation. ### Next steps * Start with [MODEL](/organization/cooperation/consortiums/model.md) to understand the governance design. * Continue to [FRONTIERS](/organization/cooperation/consortiums/frontiers.md) to see the wider operating context. * Open [IV. GLOBAL](/organization/cooperation/consortiums/model/iv.-global.md), [V. REGIONAL](/organization/cooperation/consortiums/model/v.-regional.md), and [VI. NATIONAL](/organization/cooperation/consortiums/model/vi.-national.md) to review each layer in practice. --- # 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.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.