> 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/acceleration/nexus-campaigns.md).

# NEXUS CAMPAIGNS

**Where this fits:** all six sectors · the Universe pillar, with Labs, Reports and Academy · The Global Risks Forum (GRF) as programme steward · Q1 mandate to Q4 renewal · programme design · see [Nexus Universe](/organization/programme/universe.md); [The programme year](/organization/programme/the-programme-year.md); [Scenarios](/organization/model/scenarios.md).

**In brief.** This page sets out NEXUS CAMPAIGNS for campaigns, now read as Universe mission families. A campaign is a family of Universe missions; a cycle gate is a programme decision, not a public-authority approval, a certification or a deployment authorisation. Mission families follow the priorities of the Sendai Framework ([UN General Assembly 2015](https://www.undrr.org/publication/sendai-framework-disaster-risk-reduction-2015-2030)) and the Early Warnings for All initiative ([United Nations 2022](https://www.un.org/en/climatechange/early-warnings-for-all)), and the UN's case for coordinated responses to complex shocks ([United Nations 2023](https://www.un.org/sites/un2.un.org/files/our-common-agenda-policy-brief-emergency-platform-en.pdf)).

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

* Earlier pages define a campaign four ways (a thematic programme, a cross-border initiative, an infrastructure deployment track and a funding drive). Read each as a **Universe mission family**: a set of missions admitted at G1 and tested in Action Week, with funding and deployment decided by competent actors outside the programme ([Nexus Universe](/organization/programme/universe.md)).
* Finance vehicles and instruments on this page (special-purpose vehicles, funds, credits, guarantees, pools or tokens) are structures that competent, lawful actors may form outside the programme, under their own law and licences. The programme prepares evidence, standards and readiness; it never forms, arranges, owns or advises on a vehicle or a transaction ([Lawful handoffs](/organization/finance-readiness/lawful-handoffs.md); [Finance readiness](/organization/finance-readiness.md)).
* Technology is described as the twenty Nexus systems by their NXS codes (for compute and networks, [NXS-COR](/organization/systems/nxs-cor.md) and [NXS-NET](/organization/systems/nxs-net.md)); "Foundry" is the bare pillar word for the build work ([Systems](/organization/systems.md); [Foundry](/organization/programme/foundry.md)).
* DAO, token, NFT and on-chain governance language describes earlier design concepts. No DAO, token or on-chain body exists or governs any part of the programme; National Working Groups are expert working groups under [National Nexus](/organization/governance-in-operation/national-nexus.md), with bounded, supervised assignments and no fee for ordinary participation ([National Working Groups](/organization/governance-in-operation/nwg.md)).
* Everything described here is in formation: no national, regional or global programme is recorded as constituted or active, and the current service level is R0, information and enquiries ([Status and service levels](/organization/governance-in-operation/status-and-service-levels.md)).
* [Nexus Standards](/organization/institutions/nexus-standards.md) that bear on this page: [NS-11](https://nexustandards.com/standards/ns-11/) (verification and monitoring), [NS-10](https://nexustandards.com/standards/ns-10/) (policies and clauses), [NS-8](https://nexustandards.com/standards/ns-8/) (nS-8). Their text and status on nexustandards.com govern.
  {% endhint %}

## Sources

External sources and standards cited in the In brief and the note above. The text below keeps its own internal references.

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 (2022). Early Warnings for All initiative, launched by the UN Secretary-General on 23 March 2022; Executive Action Plan 2023–2027 (WMO, 2022). <https://www.un.org/en/climatechange/early-warnings-for-all>
3. United Nations (2023). Our Common Agenda Policy Brief 2: Strengthening the International Response to Complex Global Shocks – An Emergency Platform. New York: United Nations, March 2023. <https://www.un.org/sites/un2.un.org/files/our-common-agenda-policy-brief-emergency-platform-en.pdf>
4. Nexus Standards, NS-11: Verification and monitoring. Status as published. <https://nexustandards.com/standards/ns-11/>
5. Nexus Standards, NS-10: Policies and clauses. Status as published. <https://nexustandards.com/standards/ns-10/>
6. Nexus Standards, NS-8: NS-8. Status as published. <https://nexustandards.com/standards/ns-8/>


---

# 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/acceleration/nexus-campaigns.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.
