> 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/overview.md). # OVERVIEW Nexus cooperation overview for consortium governance, guild coordination, frontier collaboration, public-good coordination, and multistakeholder implementation across the ecosystem. ## Nexus cooperation overview Nexus cooperation defines how the Nexus Ecosystem organizes consortium governance, guild coordination, frontier collaboration, and multistakeholder implementation. It connects public-good coordination across consortiums, Nexus Guilds, and [Nexus Universe](/organization/programme/universe.md). This cooperation model links governance, participation, and delivery. It supports lawful implementation, sovereign interoperability, national ownership, and cross-sector collaboration across the ecosystem. ### What Nexus cooperation covers * Consortium governance for global, regional, and national coordination. * Guild coordination for domain collaboration, membership, and platform-based work. * Frontier collaboration through Nexus Universe, research, and implementation pathways. ### Core cooperation pillars * [CONSORTIUMS](/organization/cooperation/consortiums.md) * [NEXUS GUILDS](/organization/cooperation/nexus-guilds.md) * [NEXUS UNIVERSE](/organization/cooperation/nexus-universe.md) ### Why the cooperation model matters Nexus cooperation turns parallel initiatives into a coordinated public-good system. It gives institutions, members, and partners clear paths for governance, contribution, and implementation across the Nexus Ecosystem. --- # 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/overview.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.