- Missions admitted from national and regional programmes
- A temporary technical backbone, Nexus Core, built for each edition
- Controlled exercises with independent evaluation
- Leadership deliberation on what the tests reveal
- Reviewed findings, failures and corrections
One year of work, tested together.
Nexus Universe is the annual programme of Nexus Consortiums, governed by The Global Risks Forum (GRF). Work prepared through the year is built into a temporary technical environment in one month, tested in one week of controlled exercises, then stood down in a planned stage, reviewed and published.
Prepare: demand, evidence and qualification.
National demand, research, institutional participation, monthly working-group delivery, quarterly evidence, and the qualification of technology and resources. It ends with an approved mission portfolio and an achievable build plan.
Build: assemble and test the temporary Nexus Core.
Bind authorised resources, integrate software and data, test security and interoperability, train teams and rehearse. It ends with a Core Build Report, measured readiness, known defects and go or no-go decisions.
Act and test: controlled exercises under stop-work authority.
Scenario work, benchmarks, independent observation, leadership deliberation and public-safe engagement. It ends with run, decision and observation records, limitations and improvement items.
Stand down: seal the evidence and release the capacity.
Stop new work, checkpoint authorised jobs, revoke temporary access, release temporary capacity and seal transferable evidence. Review, reconciliation and corrections continue afterwards.
Fig. 01The Nexus Universe year, from preparation to stand-down. Design, not a schedule.
The short answer.
Nexus Universe is the annual operating, integration, exercise and learning programme of Nexus Consortiums, governed by GRF and published on its own website at universe.nexus. It runs on one year of work, one month to build, one week to test and a planned stand-down, through recorded gate decisions; no edition is on record yet.
- Programme gates
- 8
- G0 to G7, each with a recorded decision
- Action week tracks
- 10
- From methods to public evidence
- Regions
- 6
- Contributing national and regional work
- Foundry systems
- 20
- Where the year's work persists
A proving programme, not an event.
Institutions rarely get to test their arrangements before a real crisis does it for them. Nexus Universe gives them a governed, controlled setting in which to do so once a year, and a public record of what held and what did not.
- Not a trade show or a procurement fair
- Not a funding platform or an investment forum
- Not a permanent supercomputer: Nexus Core is temporary
- Not an emergency service or incident command
- Not a schedule of confirmed dates or hosts until an edition record exists
Hosting is not ownership. Sponsorship is not authority. A listed mission is not a success, and a simulated loss is not an observed impact.
From the first gate to the published record.
Each station is designed with an entry condition and an exit record, so that work moves on only when the record shows it is ready. GRF records each gate decision within its instruments; a gate that is not passed stops the work it governs.
- Gate G0 to G2 · the preparation year
Missions are proposed, qualified and admitted.
Missions come from national and regional programmes, which keep their own agenda authority and may decline participation or data sharing at any point. A mission is admitted at gate G1 against recorded criteria, with the reasons kept on record. Neither membership nor sponsorship secures admission or a computing allocation.
Mission board · an edition pipelineIllustrative · no edition on recordFig. 02Missions from proposal to publication. Mission names are placeholders.
MaterialityNational demandCross-system dependenceEvidence gapTractabilityCapability valueSafeguardsResource feasibilityA competent recipient - Gate G3 · the build month
A backbone built for one edition, then stood down.
Nexus Core is the temporary technical environment of an edition: contributed computing, networks and data bound together for one month, tested for security and interoperability, and released in a planned stand-down. It is not a permanent supercomputer and never a service.
Nexus Core build · week three of fourIllustrativeFig. 03The month an edition's technical environment is built and checked. Illustrative values.
Seven states of contributed capacity
An infrastructure offer is not an allocation. Each state is recorded separately, and none implies the next.
Offered
Qualified
Reserved
Allocated
Accessible
Measured
Accepted
- Gate G4 · the action week
Ten tracks, run under exercise controls.
The action week brings every part of the year's work into one controlled setting, from scientific methods to leadership deliberation and public challenge. Independent evaluators test objectives and observable performance, not attendance. Simulated warnings never reach live audiences, and real infrastructure is never an unapproved target.
Exercise control · day four, cross-systemIllustrativeFig. 04The action week, with its safety controls and evaluation. Illustrative values.
The ten tracks
- 01Scientific methods and dataEvidence
- 02National compute and network integrationCore
- 03Sector and country missionsMissions
- 04Frontier technology evaluationEvaluation
- 05Public-authority learningLearning
- 06Leadership and policy deliberationCouncils
- 07Finance and insurance readinessGRA
- 08Academy and workforceLearning
- 09Rights, safeguards and integrityTrust
- 10Public evidence and challengePublic
- Gate G5 to G7 · stand-down, publication, renewal
Evidence sealed, results reviewed, the next mandate set.
Temporary access and capacity are released in a planned stand-down, which becomes a programme commitment only when the annual programme records its purpose, clock, scope and exceptions. Retained evidence is preserved. Scientific and editorial review, financial reconciliation and corrections continue afterwards, and improvement items return to the next annual agenda.
- G0Annual programme authorised
- G1Missions admitted
- G2Data and resources qualified
- G3Build accepted for exercise
- G4Controlled live operation authorised
- G5Evidence sealed, stand-down recorded
- G6Publication authorised
- G7Renewal reviewed
No edition is on record, so no gate above has been passed. Each gate is a decision GRF records within its instruments.
Fig. 04aThe year's work and the decisions that gate it. Design, not dates; no edition is on record.
GRF governs; each pillar institution keeps its own role.
The programme is led by three pillar institutions with separate responsibilities. None of them takes the decisions that belong to the governments, operators and licensed institutions taking part. Hosts provide venues and support under written safeguards.
Fig. 05Where GRF records the decisions of an edition. Wireframe, not a live screen.
Programme governance
The annual mandate, mission admission, gate decisions and publication authorisation, with leadership dialogue throughout the year. GRF tests inclusion, institutional fit and public-purpose legitimacy.
Technical office
Mission scoping, data and method qualification, the Core build, exercise control and evidence capture. See GCRI's programmes.
Finance-readiness dialogues
The finance and insurance readiness track: protection gaps and diligence questions, never an approval or a transaction. See finance readiness at GRA.
Roles for every kind of contributor.
National and regional programmes
Propose a mission once an edition is authorised.
Computing and network contributors
Offer qualified resources; offered capacity is never counted as allocated.
Hosts and venues
Propose hosting; no event is confirmed before host authority and readiness are evidenced.
Evaluators and reviewers
Observe and evaluate; a reviewer with a declared conflict never signs the acceptance concerned.
Leaders and experts
Contribute through the Leadership Council and working groups on Participate.
No edition is on record yet. Enquiries are open and receive a reference. Mission calls, hosting decisions and registration open only when an edition is authorised and its terms and review capacity are in place. Governance questions go to universe@globalriskforum.com, hosting proposals to partnerships@globalriskforum.com.
Terms used on this page.
Each term as this institution uses it on this page.
| Term | Definition |
|---|---|
| Nexus Universe | The annual operating, integration, exercise and learning programme of Nexus Consortiums, governed by GRF. |
| Nexus Core | The temporary technical environment of one edition: contributed computing, networks and data bound together for one month, tested, and released in a planned stand-down. |
| Gate | One of eight recorded decisions, G0 to G7, by which GRF moves the annual programme from authorisation to publication; work moves on only when the record allows it. |
| Stop-work authority | The standing power to halt a controlled exercise at once, for safety or a real-world emergency, whatever stage it has reached. |
| Planned stand-down | The proposed one-day stage that releases temporary capacity after the action week; review, reconciliation and corrections continue afterwards. |
Questions about Nexus Universe.
When and where is the next Nexus Universe?
What is the Nexus Universe website address?
Is everything torn down after the action week?
Does sponsorship or membership secure a mission place?
Are exercise results binding findings?
How is GCRI involved?
Around the annual programme.
Prepare a mission worth testing.
The Secretariat answers Nexus Universe enquiries and names the next step. An enquiry receives a reference; it does not create a mission place, an allocation or a registration.