Skip to content

GCRI · Foundations

Nexus Universe: how GCRI builds the annual technical environment

Nexus Universe tests national and regional missions once a year under exercise control. This page explains how the technical office of The Global Centre for Risk and Innovation (GCRI) prepares, builds, runs and stands down that environment, gate by gate, and what it never claims.

As of
21 October 2026
Reading
13 minutes
Ubungqina
15 sources, cited in order
NEXUS TWIN · WF-1 · NETWORKSEED 611c4139GCRI-MAIN.CONSORTIUM.NEXUS-CYCLExyzSCHEMATIC · NETWORKST-01 · 0.288 0.379ST-02 · 0.250 0.496ST-03 · 0.248 0.465
WF-1 · network Schematic wireframe twin (network, decision under uncertainty). An illustration, not data.

Methods and evidence

Ubungqina
15 sources, cited in order and listed under References
Figures
4 figures
Data availability
Every chart's data is published as a table on this page.
Amasango
8
programme gates, G0 to G7, none an approval3
Tracks
10
Action Week tracks with independent evaluators1
Amandla okwenza
7
states before contributed capacity counts1
Compute
6.7 to 12%
of US electricity projected for data centres by 20284

01What Nexus Universe asks of its technical environment

What Nexus Universe asks of its technical environment

Nexus Universe is the annual programme of the Nexus Consortium, stewarded by The Global Risks Forum (GRF), in which national and regional priorities become missions that are prepared, built, tested under exercise control and renewed each year; The Global Risks Alliance (GRA) runs its finance-readiness track 6,7,1. GRF describes it as "a proving programme, not an event" 1. Its public home is universe.nexus, where the programme's application is being prepared for launch.

The annual technical environment is everything a mission needs to be tested honestly: qualified data, models and software, computing and network capacity, controlled exercise rooms, evidence capture and a clean way to stand everything down. GCRI builds and runs that environment through the Nexus Universe technical office 2. This page explains how it is built, gate by gate, what controls it carries, and what it never claims.

02Why risk systems need a controlled place to be tested

Why risk systems need a controlled place to be tested

Most failures in a crisis are failures of coordination that nobody tested: a warning that reaches the wrong desk, a dataset no one may legally share at night, a model that works until two hazards arrive at once. Exercise practice exists to find those failures first. The World Health Organization's Simulation Exercise Manual treats exercises as a way to validate the core capacities countries report under the International Health Regulations 8. The US Homeland Security Exercise and Evaluation Program, revised in February 2020, ties every exercise to an After-Action Report and Improvement Plan that records strengths, areas for improvement and corrective actions 9.

The scale of serious exercise practice is large. NATO's Cooperative Cyber Defence Centre of Excellence describes Locked Shields as the world's largest and most complex international live-fire cyber defence exercise; its 2026 edition involved about 4,000 participants from 41 nations 10. Systemic risk asks for something harder still: exercises that cross sectors, institutions and borders at once, with the evidence kept so that next year's work starts from what was learned. That is the role Nexus Universe is designed to play, and why its technical environment matters as much as its convening.

03A year to prepare, a month to build, a week to test

A year to prepare, a month to build, a week to test

The programme year runs on five timescales, each with its work and its status 3. One year prepares: national demand, research, institutional participation, monthly working-group delivery, quarterly evidence and the qualification of technology and resources, ending in an approved mission portfolio and an achievable build plan. One month builds: the Core is assembled, authorised resources are bound, software and data are integrated, security and interoperability are tested and teams rehearse, ending in a Core Build Report with measured readiness, known defects and a go or no-go decision. One week acts and tests: controlled exercises, scenario work, benchmarks, independent observation, leadership deliberation and public-safe engagement, ending in run, decision and observation records, stated limitations and an evidence seal.

One day stands down: new work stops, authorised jobs are checkpointed, temporary access is revoked, temporary capacity is isolated or released, equipment is reconciled and transferable evidence is sealed; the model marks this step as proposed. The following period reviews and renews: archives are validated, scientific and editorial review is completed, approved results are published, support is reconciled and corrective actions are closed, ending in reviewed publications and the next cycle's mandate 3.

Fig. 01A year to prepare, a month to build, a week to test

A year to prepare, a month to build, a week to test Five panels in sequence: one year to prepare, one month to build, one week to act and test (highlighted), one day to stand down (proposed) and a following period to review and renew, each listing its work and its exit record, from an approved mission portfolio to the next-cycle mandate.
Each timescale has an entry condition and an exit record; the one-day stand-down is proposed in the model. No cycle has yet run.3,1Sources: Consortium model, annual cycle; programme documentation, Nexus Universe. As of 21 October 2026.
Figure 1 in words

Five connected panels. One year, Prepare: national demand, research, working groups, quarterly evidence and qualification; exit record an approved mission portfolio, qualified inputs and a build plan. One month, Build: assemble the Core, bind authorised resources, test security and rehearse; exit record the Core Build Report and a go or no-go decision. One week, Act and test, highlighted: controlled exercises, independent observation and leadership deliberation; exit record run and decision records, an evidence seal and stated limitations. One day, Stand down, marked as proposed in the model: stop new work, revoke temporary access and release temporary capacity; exit record a stand-down receipt and evidence manifest. Following period, Review and renew: validate archives, review, publish approved results and close corrections; exit record reviewed publications and the next-cycle mandate.

04Eight gates and who holds them

Eight gates and who holds them

Eight gates divide the year: G0 annual programme authorised, G1 missions admitted, G2 data and resources qualified, G3 build accepted for exercise, G4 controlled live operation authorised, G5 evidence sealed and stand-down recorded, G6 publication authorised and G7 renewal reviewed 3. G0 falls in the first quarter; G1 to G3 in the second; G4 and G5 in the third, when Action Week runs; G6 and G7 in the fourth 1.

Decision rights are split on purpose. GRF holds four kinds of decision, the annual mandate (G0), the admission of missions (G1), the gate decisions through the year and the authorisation of publication (G6), and it holds them in the manner of exercise direction, separate from the controllers who run an exercise and the evaluators who judge it 11,1. The steward of the programme is therefore never also the judge of its results. GCRI's technical office prepares the scientific and data readiness of each mission and runs the build; GRA's finance-readiness track adds injects such as a parametric trigger being crossed or a sovereign spread widening, so that finance and insurance institutions can see what a mission means for them without any transaction taking place 7,1. A gate is a programme decision about the cycle; it is "not a public-authority approval, a certification or a deployment authorisation" 1.

Fig. 02Eight gates, four quarters, one controlled week

Eight gates, four quarters, one controlled week Timeline of the four quarters with eight gates: G0 annual programme authorised in Q1; G1 missions admitted, G2 data and resources qualified and G3 build accepted in Q2; G4 controlled live operation authorised and G5 evidence sealed in Q3; G6 publication authorised and G7 renewal reviewed in Q4.
Gates G0 to G7 are programme decisions about the cycle, never public-authority approvals; GRF holds the mandate, admission and publication decisions.3,11,1Sources: Nexus Consortium model, annual gates; GRF, Programme governance. As of 21 October 2026.
Figure 2 in words

A horizontal timeline across four quarters labelled with their Reports editions: Q1 State and Agenda, Q2 Evidence and Build, Q3 Stress Test and Readiness (highlighted), Q4 Synthesis and Renewal. Gate markers: G0 annual programme authorised (Q1); G1 missions admitted, G2 data and resources qualified, G3 build accepted for exercise (Q2); G4 controlled live operation authorised, highlighted as the opening of Action Week, and G5 evidence sealed and stand-down recorded (Q3); G6 publication authorised and G7 renewal reviewed (Q4). A note explains that a gate is a programme decision recorded with its evidence and dissent, never a public-authority approval, a certification or a deployment authorisation, and that GRF holds the mandate (G0), mission admission (G1) and publication (G6) decisions.

05What the technical office builds

What the technical office builds

The technical office's work follows the mission from scoping to closeout 2. In scoping, a national, regional or institutional priority becomes a testable question with stated criteria, the first step of the Nexus cycle 12. In qualification, before G2, data sources, models, software and contributed resources are checked against the mission: who owns them, under which rights, with what known limits. In the Core build, the month before Action Week, the environment is assembled and tested for security and interoperability, and the Core Build Report records what works, what does not and whether the exercise should go ahead (G3) 3.

The environment draws on the programme's systems, each documented as a design with its limits: NXS-COR (compute, nodes and runtimes) for computation, NXS-EOP (earth observation and digital twins) for observation and simulation, and NXS-DSS (decision cases and deliberation) for the decision record. During the week the office supports the exercise and captures evidence; after it, the office checkpoints jobs, revokes temporary access and seals the evidence that will feed Reports 2,3.

06Contributed capacity counts only once it is measured

Contributed capacity counts only once it is measured

Missions need temporary technical intensity: computing for a weekend of coupled runs, a data room for a basin model, people to observe a control room. Data, compute, people and facilities offered to a mission therefore pass through seven states: offered, qualified, reserved, allocated, accessible, measured and accepted, and capacity is counted only once it is measured and accepted 1. The rule is stated as a separation: an infrastructure offer is not an allocation 13. Neither membership nor sponsorship guarantees a computing allocation 13.

The discipline is not bureaucratic caution; compute has become a scarce public input. US data centres used about 176 TWh of electricity in 2023, about 4.4% of national consumption, against 58 TWh in 2014, and the US Department of Energy projects 325 to 580 TWh, or 6.7% to 12% of US electricity, by 2028 4. An exercise that assumed capacity it had not measured would test nothing but its own optimism.

Fig. 03Seven states before capacity counts

Seven states before capacity counts A rising staircase of seven states of contributed capacity: offered, qualified, reserved, allocated, accessible, measured and accepted, with the last two highlighted to show that capacity counts only once it has been measured and accepted.
Each step is a separate record; capacity counts only once it is measured and accepted, and an offer is never counted as reserved, consumed or funded.1,13Sources: Nexus documentation, Nexus Universe and Status and service levels. As of 21 October 2026.
Figure 3 in words

Seven steps rising left to right, each with a short definition: 1 Offered, a provider states what it could contribute; 2 Qualified, checked against the mission scope at G2; 3 Reserved, held for a named mission and period; 4 Allocated, assigned to the mission by its owner; 5 Accessible, usable by authorised mission users; 6 Measured, use and performance recorded; 7 Accepted, counted as delivered capacity. Steps 6 and 7 are shaded in the accent colour. A note states that capacity counts only once measured and accepted and that an offer is not an allocation.

Fig. 04Compute is a scarce input, so it is qualified before use

Compute is a scarce input, so it is qualified before use Two bar charts. US data-centre electricity use: 58 terawatt-hours in 2014, about 176 in 2023 and a projected 325 to 580 in 2028. Share of US electricity: about 4.4 per cent in 2023 and a projected 6.7 to 12 per cent in 2028. 201458 TWh2023176 TWh2028 (low)325 TWh2028 (high)580 TWh
Two measures on two separate scales. The 2028 values are the projected range in the US Department of Energy report, not a single forecast.4Sources: US Department of Energy and Lawrence Berkeley National Laboratory, 20 December 2024. As of 21 October 2026.
Figure 4 in words, and its data

Left panel, US data-centre electricity use in terawatt-hours a year: 58 in 2014; about 176 in 2023; a projected range of 325 to 580 in 2028, drawn as a solid bar to the low end and a dashed extension to the high end. Right panel, share of total US electricity: about 4.4 per cent in 2023 and a projected 6.7 to 12 per cent in 2028. Source: US Department of Energy and Lawrence Berkeley National Laboratory, December 2024.

UnyakaElectricity useShare of US electricity
201458 TWh 4Not stated
2023About 176 TWh 4About 4.4% 4
2028 (projected range)325 to 580 TWh 46.7% to 12% 4
Data of Figure 4. US data-centre electricity use, as estimated by the US Department of Energy and Lawrence Berkeley National Laboratory 4.

07Action Week: ten tracks under exercise control

Action Week: ten tracks under exercise control

The week of controlled exercise runs in ten tracks, each with independent evaluators who assess it against its stated objectives 1. Exercise controls and stop-work events keep the week controlled 1. Nothing simulated is reported as observed impact 1.

TrackIgamaWhat it examines
1Scientific methods and dataWhether the evidence and models behind a mission hold under test
2Sovereign compute and network integrationWhether qualified computing and networks perform as measured
3Sector and country missionsThe admitted missions themselves, on named places and systems
4Frontier technology evaluationCandidate technologies under representative conditions
5Public-authority learningWhat authorities learn within their own mandates
6Leadership and policy deliberationHow leaders decide with the evidence in front of them
7Finance and insurance readinessWhat a mission means for finance, led by GRA, with no transaction
8Academy and workforceAssessed tasks that become completion evidence
9Rights-holder and public-interest challengeChallenge from those affected, recorded with the result
10Public evidence and communicationHow findings and limits are communicated in public
The ten tracks of Action Week, as set out in the programme spine on 21 October 2026, with what each track examines 1.

08Controls that keep an exercise an exercise

Controls that keep an exercise an exercise

An exercise environment carries real data and real people, so it carries controls. Participation gives the programme no control of operational technology, and exercises carry no live actuation, incident command or warning authority 13. Public-safety exercises carry clear simulation marking and stop-work controls, and the programme is not an emergency-dispatch service 13. Simulation messages are never presented as warnings from an authority 13.

Alerting standards show how such marking works in practice. In the Common Alerting Protocol, the format used by many alerting authorities and carried by ITU-T Recommendation X.1303, every message has a required status: Actual, Exercise, System, Test or Draft. A message marked Exercise is for designated exercise participants only, and a Test message is to be ignored by all recipients 14,15. The environment follows the same principle: every artefact produced in Action Week carries its status, and a scenario output is labelled as a scenario wherever it travels.

Rights travel with the data. National counterparts own the agenda, the data and the decisions; data and intellectual-property permissions are one of the ten readiness dimensions checked before any service moves up a level, and protected knowledge never enters public examples or model training 1,13. The responsibilities are set out in data and privacy responsibilities and the safeguarding route.

09What an exercise result can and cannot show

What an exercise result can and cannot show

An exercise produces three kinds of record: what was run, what was decided and what was observed, with the limitations stated and the evidence sealed at G5 3. Every finding drawn from it carries one of nine evidence labels, from observed to unknown, and a scenario result keeps its scenario label 13. After-action review records what worked, what failed and what was not tested, preserving dissent 1.

The findings then move through the year's other pillars. After-action and scenario findings go to Reports for the third-quarter edition and the annual synthesis; docket items that need a standard go to Nexus Standards; assessed tasks become completion evidence in Risk Academy; and the fourth-quarter synthesis informs the next year's mandate at G7 1. GRF's page on evidence and outcomes sets out what each edition is designed to produce.

10Standards and instruments the environment follows

Standards and instruments the environment follows

The environment aligns with exercise and alerting practice the participating institutions already use, and with the proposed Nexus Standards for the programme year.

IsixhoboRelevanceImeko
NRS-E1Annual programme cycle, exercises and gatesProposed Nexus Risk Standard
NRS-I2Risk communication and public-safe dashboardsProposed Nexus Risk Standard
NS-11Verification and monitoringProposed foundation standard
NS-12Software, models and AI/ML artefactsProposed foundation standard
WHO Simulation Exercise ManualPlanning, conducting and evaluating simulation exercisesWHO guidance, 2017 8
HSEEPExercise design, evaluation and After-Action Report/Improvement PlanFEMA doctrine, 2020 revision 9
Common Alerting Protocol 1.2Status marking of alert, exercise and test messagesOASIS Standard, 2010 14
Selected standards and instruments for the annual technical environment, with status as of 21 October 2026.

11What is changing

What is changing

  • Compute is the binding constraint. Projected data-centre demand of 6.7% to 12% of US electricity by 2028 makes qualified, measured capacity a precondition of any large exercise 4.
  • Frontier technology needs honest testbeds. Testbed participation is not a regulatory sandbox, a certification or a procurement status, and sponsorship never influences a result 13.
  • Cyber exercises have set the scale. Exercises with thousands of participants from dozens of nations show what multi-party coordination can test, and what it costs to run 10.
  • Exercise marking matters more as channels multiply. A scenario output that loses its status label becomes misinformation; status fields such as CAP's are the model 14.

12Three institutions in one programme

Three institutions in one programme

GCRI builds and runs the technical environment and edits Reports. GRF stewards the programme and holds its decisions, as set out in Nexus Universe at GRF, programme governance, the annual operating cycle, exercises and learning and hosts and supporters. GRA runs the finance-readiness track and reads mission evidence for finance and insurance readiness; readiness evidence is not a financing decision 7,1. Each institution's mandate is set out on its home page: GCRI, GRF and GRA.

13How institutions can take part now

How institutions can take part now

At service level R0, participation begins with a question: enquiries receive a reference, and applications, contribution payments, computing allocations and event registration open only when their service team, terms and review capacity are in place 13,5.

What this page does not claim: no Nexus Universe cycle has yet run, no Action Week has been held and no environment described here is installed; the programme is at service level R0. A gate is a programme decision, never a public-authority approval, a certification or a deployment authorisation. Exercises carry no live actuation, incident command or warning authority. GCRI does not regulate or certify, GRF does not regulate, finance or procure, and GRA does not lend, underwrite, rate or invest. Naming an exercise programme, agency or standard is not a claim of partnership or endorsement.

Imibuzo

Imibuzo neempendulo

Has a Nexus Universe cycle already taken place?

No. The annual cycle, its gates and Action Week are a designed programme. No cycle has yet run, and the programme is at service level R0, information and enquiries.

Who decides whether an exercise goes ahead?

GRF holds the gate decisions as exercise direction, on the evidence of GCRI's Core Build Report, which records measured readiness, known defects and a go or no-go recommendation. Controllers and independent evaluators are kept separate from that decision.

Can an exercise issue warnings or control real systems?

No. Exercises carry no live actuation, incident command or warning authority, simulation messages are never presented as warnings from an authority, and only the competent public authority may warn or command.

Does offering computing capacity guarantee a role in a mission?

No. Offered capacity passes through qualification, reservation and allocation, and it is counted only once measured and accepted. Neither membership nor sponsorship guarantees an allocation.

Where do the results of Action Week go?

Run, decision and observation records are sealed at G5. Reviewed findings go to the Reports platform, docket items to Nexus Standards and assessed tasks to Risk Academy, and the year's synthesis sets the next mandate at G7.

Terms

Glossary

Action Week
The week of controlled exercise in the third quarter, in ten tracks with independent evaluators.
Ingxelo Yokwakha Esisiseko
The record of the month-long build: measured readiness, known defects and the go or no-go decision at G3.
Isango
A programme decision about the cycle, G0 to G7, recorded with its evidence and dissent; never an approval.
Stand-down
The proposed one-day step that stops new work, revokes temporary access and seals transferable evidence.
Technical office
GCRI's function for scoping, qualification, the Core build, exercise support, evidence capture and closeout.
Contributed capacity
Data, compute, people and facilities offered to a mission; counted only once measured and accepted.

Reuse and cite

Text CC BY 4.0. Cite the page with its date; data tables are linked under each figure.

Imithombo

References

15 sources, numbered in the order they are first cited
  1. Nexus documentation (docs.therisk.global) (2026-10-21). Nexus Universe. docs.therisk.global. Accessed 2026-10-21.
  2. The Global Centre for Risk and Innovation (2026-10). Nexus Universe technical office. therisk.global. Accessed 2026-10-21.
  3. Nexus documentation (docs.therisk.global) (2026-10-21). The programme year. docs.therisk.global. Accessed 2026-10-21.
  4. U.S. Department of Energy and Lawrence Berkeley National Laboratory (2024-12-20). DOE releases new report evaluating increase in electricity demand from data centers. www.energy.gov. Accessed 2026-10-21.
  5. The Global Centre for Risk and Innovation (2026-10). Programme status. therisk.global. Accessed 2026-10-21.
  6. The Global Risks Forum (2026-10). Nexus Universe at GRF. globalriskforum.com. Accessed 2026-10-21.
  7. The Global Risks Alliance (2026-10). Universe finance-readiness programme. globalriskalliance.com. Accessed 2026-10-21.
  8. World Health Organization (2017-02-01). WHO Simulation Exercise Manual (WHO/WHE/CPI/2017.10). www.who.int. Accessed 2026-10-21.
  9. US Federal Emergency Management Agency (2020-02). Homeland Security Exercise and Evaluation Program (HSEEP). www.fema.gov. Accessed 2026-10-21.
  10. NATO Cooperative Cyber Defence Centre of Excellence (2026). Locked Shields. ccdcoe.org. Accessed 2026-10-21.
  11. The Global Risks Forum (2026-10). Programme governance. globalriskforum.com. Accessed 2026-10-21.
  12. Nexus documentation (docs.therisk.global) (2026-10-21). The Nexus cycle. docs.therisk.global. Accessed 2026-10-21.
  13. Nexus documentation (docs.therisk.global) (2026-10-21). Status and service levels. docs.therisk.global. Accessed 2026-10-21.
  14. OASIS Open (2010-07-01). Common Alerting Protocol Version 1.2 (OASIS Standard). docs.oasis-open.org. Accessed 2026-10-21.
  15. International Telecommunication Union (2007-09). Recommendation ITU-T X.1303: Common alerting protocol (CAP 1.1). www.itu.int. Accessed 2026-10-21.

Irekhodi

Editorial record

Facts and programme states are given as of 21 October 2026. This page replaces an earlier version that described a "Nexus Core" operating environment with operating rooms, protocol labs, cyber ranges and safety holds. The recorded model keeps the Core build, exercise control and stop-work authority; operating rooms, protocol labs and cyber ranges as named structures have no record and are not described here. The page is reviewed at least every 180 days and whenever a programme state, a gate or a cited figure changes.

Published by the GCRI editorial desk under the scientific and editorial integrity policy and the AI-use statement. To report an error or request a correction, use corrections and concerns; corrections are dated and listed with the page. Programme states are kept in the claims and readiness register.

Cite this article

GCRI editorial desk (2026, June 8). Nexus Universe: how GCRI builds the annual technical environment. The Global Centre for Risk and Innovation. https://therisk.global/nexus-universe-building-the-annual-technical-environment-for-systemic-risk-readiness/

Republish

Republish or translate this article free of charge, in print or online, under CC BY 4.0: keep the byline and The Global Centre for Risk and Innovation, link to the original and note any change. Figures, maps and twins made by the institutions carry the same licence; third-party data keeps its own credit line.

Attribution to paste
<p>Nexus Universe: how GCRI builds the annual technical environment — GCRI editorial desk, The Global Centre for Risk and Innovation. First published 8 June 2026 at <a href="https://therisk.global/nexus-universe-building-the-annual-technical-environment-for-systemic-risk-readiness/">https://therisk.global/nexus-universe-building-the-annual-technical-environment-for-systemic-risk-readiness/</a>. Republished under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).</p>

Izihloko

Related across the Consortium

Share

EmailLinkedInBlueskyMastodon