Nexus Universe Annual programme Governed by GRF
The annual operating, exercise and learning programme

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.

Eleven months

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.

One month

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.

One week

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.

One day, planned

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.

The year · select a stageDesign, not a schedule
The Nexus Universe yearA ring of one year: eleven months of preparation, one month to build, one week to act and test, and one day of planned stand-down, with the eight programme gates G0 to G7 placed around it. Selecting a stage highlights its arc. No edition is on record; the ring shows the design, not a schedule.

Fig. 01The Nexus Universe year, from preparation to stand-down. Design, not a schedule.

01In brief

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
02What it is

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.

It is
  • 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
It is 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.

03The year, station by station

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.

  1. 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 record
    Mission board, illustrative interfaceAn illustrative mission pipeline for a Nexus Universe edition: proposed, qualified, admitted, built, tested and published columns with mission cards from six regions, the build column current at gate G3 and the published column still empty. Names are placeholders; no edition is on record.

    Fig. 02Missions from proposal to publication. Mission names are placeholders.

    MaterialityNational demandCross-system dependenceEvidence gapTractabilityCapability valueSafeguardsResource feasibilityA competent recipient
  2. 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 fourIllustrative
    Nexus Core build, illustrative interfaceAn illustrative Core build console: contributed capacity moving through offered, qualified, reserved, allocated, accessible, measured and accepted states, a temporary backbone topology with compute, network, data, identity and observability nodes, readiness meters and a build report with open defects and a pending go or no-go decision. Values are placeholders.

    Fig. 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.

    1. Offered

    2. Qualified

    3. Reserved

    4. Allocated

    5. Accessible

    6. Measured

    7. Accepted

  3. 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-systemIllustrative
    Exercise control, illustrative interfaceAn illustrative exercise control room for the action week: a scenario events list with timed injects, a safety panel with stop-work authority, a safety hold, a real-world override and sealed live audiences, an evaluation grid of objectives against observed performance by day, and an after-action record counting observations, preserved dissent, adverse findings and improvement items. Values are placeholders.

    Fig. 04The action week, with its safety controls and evaluation. Illustrative values.

    The ten tracks

    1. 01Scientific methods and dataEvidence
    2. 02National compute and network integrationCore
    3. 03Sector and country missionsMissions
    4. 04Frontier technology evaluationEvaluation
    5. 05Public-authority learningLearning
    6. 06Leadership and policy deliberationCouncils
    7. 07Finance and insurance readinessGRA
    8. 08Academy and workforceLearning
    9. 09Rights, safeguards and integrityTrust
    10. 10Public evidence and challengePublic
  4. 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.

    1. G0Annual programme authorised
    2. G1Missions admitted
    3. G2Data and resources qualified
    4. G3Build accepted for exercise
    5. G4Controlled live operation authorised
    6. G5Evidence sealed, stand-down recorded
    7. G6Publication authorised
    8. G7Renewal reviewed

    No edition is on record, so no gate above has been passed. Each gate is a decision GRF records within its instruments.

Gate canvas · G0 to G7 across the lanesDesign, not a record
The Nexus Universe year as a gated graphGates G0 to G7 as decision nodes between the preparation, build, action-week and close-out tasks. Design of the year, not a schedule.

Fig. 04aThe year's work and the decisions that gate it. Design, not dates; no edition is on record.

04Who does what

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.

Council agenda · the governance viewIllustrative
Council and edition agenda, illustrative interfaceAn illustrative GRF console: council participation across six constituencies, the annual programme from dialogues and mission selection to the Core build, the test week, a planned stand-down and synthesis, a dialogue record from adopted agenda to open corrections, and the three participation pillars.

Fig. 05Where GRF records the decisions of an edition. Wireframe, not a live screen.

GRF

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.

GCRI

Technical office

Mission scoping, data and method qualification, the Core build, exercise control and evidence capture. See GCRI's programmes.

GRA

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.

05How to take part

Roles for every kind of contributor.

Programmes

National and regional programmes

Propose a mission once an edition is authorised.

Infrastructure

Computing and network contributors

Offer qualified resources; offered capacity is never counted as allocated.

Hosts

Hosts and venues

Propose hosting; no event is confirmed before host authority and readiness are evidenced.

Evaluation

Evaluators and reviewers

Observe and evaluate; a reviewer with a declared conflict never signs the acceptance concerned.

People

Leaders and experts

Contribute through the Leadership Council and working groups on Participate.

Public

Readers and critics

Read published results and challenge them through Governance and trust.

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.

06Key terms

Terms used on this page.

Each term as this institution uses it on this page.

TermDefinition
Nexus UniverseThe annual operating, integration, exercise and learning programme of Nexus Consortiums, governed by GRF.
Nexus CoreThe temporary technical environment of one edition: contributed computing, networks and data bound together for one month, tested, and released in a planned stand-down.
GateOne 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 authorityThe standing power to halt a controlled exercise at once, for safety or a real-world emergency, whatever stage it has reached.
Planned stand-downThe proposed one-day stage that releases temporary capacity after the action week; review, reconciliation and corrections continue afterwards.
07Questions

Questions about Nexus Universe.

When and where is the next Nexus Universe?
No edition is on record yet. Dates, hosts and locations are published only with an edition record, after the host's authority and readiness are evidenced. Until then, any date you see elsewhere is not confirmed by GRF.
What is the Nexus Universe website address?
Nexus Universe has its own website at universe.nexus. This gateway on globalriskforum.com explains how GRF governs the programme. Treat any other address presented as the programme's website as not confirmed by GRF.
Is everything torn down after the action week?
Temporary access and capacity are released in a planned stand-down, which becomes a programme commitment only when the annual programme records it. Retained evidence is preserved, and scientific review, financial reconciliation and corrections continue afterwards.
Does sponsorship or membership secure a mission place?
No. Missions are admitted at gate G1 against the criteria set out on this page. Neither membership nor sponsorship secures admission or a computing allocation.
Are exercise results binding findings?
No. Exercise results are evidence with stated limits. Simulated loss or performance is not observed impact, and results are published only after review. Decisions based on them remain with competent authorities.
How is GCRI involved?
GCRI provides the technical office: mission scoping, data and method qualification, the Core build, exercise control and evidence capture. GRF governs the programme, and GRA leads the finance-readiness track.
Consortium Secretariat

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.

Have questions?