> 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/viii.-cadence.md).

# VIII. CADENCE

Nexus Universe runs on an annual cadence that connects one-year preparation, NXS-COR Core build, live public-good operations, 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), [Foundry](/organization/programme/foundry.md), [Nexus Reports](/organization/programme/reports.md), [Nexus Standards](/organization/programme/standards.md), [Risk Academy](/organization/programme/academy.md) · GRF governs the programme; the GCRI technical office prepares it; GRA runs the finance-readiness track · all twelve phases of [the programme year](/organization/programme/the-programme-year.md) · doctrine (cadence).

**In brief.** The year, not the event, is the programme: one year to prepare, one month to build, one week to act and test, one day planned to stand down, then the period that reviews and renews. This page describes each stage in depth, and the crosswalk below binds its ten sections to the twelve phases, four quarters, gates G0 to G7 and handoffs of the programme year as the sites publish it (ISO 2018; UN General Assembly 2015). "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-NET](/organization/systems/nxs-net.md) Network" in this part names the maturity and readiness layer; it is reviewed in the Q4 network review, and readiness is fitness for a stated next step, never approval, bankability or certification ([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 follows an annual public-good systems-build cadence that links one-year preparation, one-month [NXS-COR](/organization/systems/nxs-cor.md) (compute, nodes and runtimes) Core Build, and one-week live operating work across disaster risk reduction, disaster risk finance, disaster risk intelligence, and WEFH-B systems.

This annual de-risking engine connects public authority learning, finance-readiness, public-safe reporting, AEP Passports, NXS-RLS, Nexus Observatory, Regional Clusters, National Models, Docket pathways, and lawful handoff through one correctionable operating architecture.

## The cadence and the programme year

The ten sections of this chapter, bound to the phases, quarters, gates and handoffs of [the programme year](/organization/programme/the-programme-year.md). Handoffs are listed in [Applied response](/organization/model/applied-response.md).

| Section                                                                                                                                                                                 | Programme-year phases                                                                         | Quarter | Gates      | Handoffs                |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | ------- | ---------- | ----------------------- |
| [8.1 The one-year preparation cycle](/organization/cooperation/nexus-universe/model/viii.-cadence/8.1-the-one-year-preparation-cycle.md)                                                | Planning; Readiness preparation                                                               | Q1–Q2   | G0, G1, G2 | F14, F01, F08           |
| [8.2 Regional and national preparation](/organization/cooperation/nexus-universe/model/viii.-cadence/8.2-regional-and-national-preparation.md)                                          | Planning (profile scope agreed before Q1; National Portfolio baseline); Readiness preparation | Q1–Q2   | G0, G1     | F14                     |
| [8.3 Technical preparation](/organization/cooperation/nexus-universe/model/viii.-cadence/8.3-technical-preparation.md)                                                                  | Readiness preparation                                                                         | Q2      | G2         | F01, F08                |
| [8.4 Resource and contribution mobilization](/organization/cooperation/nexus-universe/model/viii.-cadence/8.4-resource-and-contribution-mobilization.md)                                | Readiness preparation (capacity offered, qualified, reserved)                                 | Q2      | G2         | –                       |
| [8.5 The one-month build](/organization/cooperation/nexus-universe/model/viii.-cadence/8.5-the-one-month-nexus-core-build-phase.md)                                                     | Controlled build (Core Build Report)                                                          | Q2      | G3         | F02, F13                |
| [8.6 The one-week live operating week](/organization/cooperation/nexus-universe/model/viii.-cadence/8.6-the-one-week-live-operating-week.md)                                            | Action Week                                                                                   | Q3      | G4         | –                       |
| [8.7 Live testing, training, optimization and simulation](/organization/cooperation/nexus-universe/model/viii.-cadence/8.7-live-testing-training-optimization-and-simulation.md)        | Action Week (tracks 1 to 4)                                                                   | Q3      | G4         | –                       |
| [8.8 Public arena, controlled rooms and finance rooms](/organization/cooperation/nexus-universe/model/viii.-cadence/8.8-public-arena-controlled-rooms-and-capital-rooms-during-live.md) | Action Week (tracks 5, 6, 7, 9 and 10)                                                        | Q3      | G4         | –                       |
| [8.9 Post-event teardown, return and transition](/organization/cooperation/nexus-universe/model/viii.-cadence/8.9-post-event-teardown-return-and-transition.md)                         | Stand-down (one day, proposed); Closeout; After-action review                                 | Q3      | G5         | F03, F10, F04, F05      |
| [8.10 Annual renewal](/organization/cooperation/nexus-universe/model/viii.-cadence/8.10-annual-renewal.md)                                                                              | Reporting; Correction; Docket review; Network review; Renewal                                 | Q4      | G6, G7     | F06, F07, F09, F11, F12 |

## Sections

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

| Section                                                                                                                                                                                                   | Words |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----- |
| [8.1 The One-Year Preparation Cycle](/organization/cooperation/nexus-universe/model/viii.-cadence/8.1-the-one-year-preparation-cycle.md)                                                                  | 6,472 |
| [8.2 Regional and National Preparation](/organization/cooperation/nexus-universe/model/viii.-cadence/8.2-regional-and-national-preparation.md)                                                            | 6,566 |
| [8.3 Technical Preparation](/organization/cooperation/nexus-universe/model/viii.-cadence/8.3-technical-preparation.md)                                                                                    | 6,412 |
| [8.4 Resource and Contribution Mobilization](/organization/cooperation/nexus-universe/model/viii.-cadence/8.4-resource-and-contribution-mobilization.md)                                                  | 6,130 |
| [8.5 The One-Month NXS-COR Core Build Phase](/organization/cooperation/nexus-universe/model/viii.-cadence/8.5-the-one-month-nexus-core-build-phase.md)                                                    | 5,994 |
| [8.6 The One-Week Live Operating Week](/organization/cooperation/nexus-universe/model/viii.-cadence/8.6-the-one-week-live-operating-week.md)                                                              | 6,011 |
| [8.7 Live Testing, Training, Optimization, and Simulation](/organization/cooperation/nexus-universe/model/viii.-cadence/8.7-live-testing-training-optimization-and-simulation.md)                         | 5,513 |
| [8.8 Public Arena, Controlled Rooms, and Capital Rooms During Live Week](/organization/cooperation/nexus-universe/model/viii.-cadence/8.8-public-arena-controlled-rooms-and-capital-rooms-during-live.md) | 5,555 |
| [8.9 Post-Event Teardown, Return, and Transition](/organization/cooperation/nexus-universe/model/viii.-cadence/8.9-post-event-teardown-return-and-transition.md)                                          | 6,139 |
| [8.10 Annual Renewal](/organization/cooperation/nexus-universe/model/viii.-cadence/8.10-annual-renewal.md)                                                                                                | 5,751 |

## Sources

1. ISO (2018). ISO 31000:2018 Risk management — Guidelines. Geneva: International Organization for Standardization. <https://www.iso.org/standard/65694.html>
2. 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>
3. ISO (2019). ISO 22301:2019 Security and resilience — Business continuity management systems — Requirements. Geneva: ISO. <https://www.iso.org/standard/75106.html>
4. 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>
5. Nexus Standards. NS-1: The uni and the artifact catalog. Status: PROPOSED; UNI `NXS-STD-ST-000001`. <https://nexustandards.com/standards/ns-1/>
6. Nexus Standards. NS-8. Status: PROPOSED. <https://nexustandards.com/standards/ns-8/>
7. Nexus Standards. NS-11: Verification and monitoring. Status: PROPOSED; UNI `NXS-STD-ST-000007`. <https://nexustandards.com/standards/ns-11/>
8. [The Global Risks Forum](/organization/institutions/grf.md). Nexus Universe at GRF. <https://globalriskforum.com/nexus-universe/>
9. The Global Risks Forum. Programme governance (GRF's role). <https://globalriskforum.com/nexus-universe/grf-role/>
10. The Global Risks Forum. Annual operating cycle. <https://globalriskforum.com/nexus-universe/annual-cycle/>
11. GCRI. Nexus Universe technical office. <https://therisk.global/programmes/nexus-universe/>
12. GCRI. Annual programme cycle. <https://therisk.global/programmes/annual-cycle/>
13. GCRI. Programme status. <https://therisk.global/consortium/programme-status/>
14. [The Global Risks Alliance](/organization/institutions/gra.md). Universe finance-readiness programme. <https://globalriskalliance.com/engagement/nexus-universe/>
15. 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/viii.-cadence.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.