Skip to content
Universe Annual programme Governed by GRF
The annual operating, exercise and learning programme

One year of work, tested together.

Universe is the annual programme of the Nexus Consortium, governed by The Global Risks Forum (GRF). A year of national and regional work is built into a temporary technical environment in one month, tested in one week of controlled exercises, then stood down, 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 edition 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 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 Universe year, from preparation to stand-down. Design, not a schedule.

Programpoorte
8
G0 to G7, each with a recorded decision
Action week tracks
10
From methods to public evidence
Streke
6
Contributing national and regional work
Foundry systems
20
Where the year’s work persists
01Wat dit is

A proving programme, not an event.

Institutions rarely test their arrangements before a real crisis does it for them. Universe gives them a governed, controlled setting to do it once a year, and a public record of what held and what broke.

It is
  • Missions admitted from national and regional programmes
  • A temporary technical backbone, edition 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: edition 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.

02The year, station by station

From the first gate to the published record.

Each station has an entry condition and an exit record; work moves on only when the record shows it is ready. GRF records every gate decision within its instruments, and a gate 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, example screenAn illustrative mission pipeline for a 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 examples; no edition is on record.

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

    MaterialityNational demandCross-system dependenceEvidence gapTractabilityCapability valueSafeguardsResource feasibilityA competent recipient
  2. Gate G3 · the build month

    A backbone built for one edition, then stood down.

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

    edition Core build · week three of fourIllustrative
    edition Core build, example screenAn 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 examples.

    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, example screenAn 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 examples.

    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. 07Finansiële en versekeringsgereedheidGRA
    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 en hulpbronne gekwalifiseer
    4. G3Bou aanvaar vir oefening
    5. G4Controlled live operation authorised
    6. G5Evidence sealed, stand-down recorded
    7. G6Publikasie gemagtig
    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.

03Who does what

GRF governs. GCRI runs the technical office. GRA reads it for finance.

The Global Centre for Risk and Innovation (GCRI) is the Lead Institution of the Nexus Consortium; GRF and the Global Risks Alliance (GRA) are independent consortium stewards with it. 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, example screenAn 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

Programbeheer

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.

Ses pilare

How this works across the six pillars.

GRF works through six pillars of one annual programme, led by the Nexus Consortium, with GCRI, GRF and GRA each contributing in its role: explore, experiment and prototype in Labs, build, simulate and prepare in Foundry, convene and test in Universe, codify, correct and apply in Nexus Standards, publish in every format in Reports, teach in the open in Risk Academy.

Select pillars · hover lines16 / 18 handoffs

Roete

Around Universe

The pillars Universe hands work to and receives it from.

L · F · U · S · R · A

Pilare
5 of 6
Oordragte
16 of 18
Lusse
16 closed

Handoffs in play

  • F01Universe → Foundry · Admitted mission becomes a cycle project with a decision caseReadiness preparation
  • F02Foundry → Universe · Core Build Report and go or no-go evidenceControlled build
  • F03Foundry → Reports · Sealed observations and indicator series behind a profileCloseout
  • F04Universe → Reports · After-action and scenario findings for chapters 10 and 13After-action review

and 12 more

F01 to F14 are the recorded handoffs of the programme year, each with the artefact that moves and its phase; R1, R2, R3 and R4 carry work around the ring. A loop counts when every pillar on it is selected. Every pillar is led by the Nexus Consortium.
  1. LabsWhere questions become experiments and prototypes: new methods, data and tools are tried in the open, with their limits on record, before the Foundry builds them, under the Nexus Consortium.Labs
  2. FoundryWhere the evidence behind a mandate or commitment is built, with its owner and limits on record.Foundry at GRF: BuildFoundry
  3. UniverseWhere mandates become missions: GRF records each gate, convenes the parties and keeps implementation accountable.Universe at GRF: Universe at GRFuniverse.nexus
  4. Nexus StandardsWhere shared rules are agreed in the open; each jurisdiction decides adoption, and no global body holds a veto.Nexus Standards
  5. ReportsWhere governance analysis and the year’s results are published, so commitments can be followed and checked.Reports at GRF: PublishReports
  6. Risk AcademyWhere policymakers, diplomats and agency staff learn the programme roles and decision-making on the record, on Risk Academy.Risk Academy

What each institution brings to each pillar

PillarGCRIGRFGRA
LaboratoriumsRuns the experiments: its science and technology teams design prototypes, record the method and publish what failed as well as what worked.Brings the questions that policy and governance need answered, and admits an experiment to the programme at a recorded gate.Brings finance questions to test, so a prototype is tried on evidence that financial institutions can read.
FoundryIts science and technical platforms bring the methods, data and evidence that the Foundry builds on.Admits missions and accepts the build for exercise at a recorded gate, so Foundry work enters the programme on the record.Brings finance-readiness questions, so builds produce evidence that financial institutions can read.
UniversumIts technical office prepares the scientific and data readiness of each mission.Stewards and governs the programme: the mandate, gates G0 to G7, convening and Action Week.Runs finance-readiness dialogues on what each mission means for finance and insurance.
StandaardeGCRI Canada is publisher of record and secretariat; GCRI stewards the evidence, methods, data and open research behind the standards.Convenes participation and keeps the public record of recognition and standing.Makes the standards readable to finance and insurance.
VerslaeHosts the canonical Reports site and publishes evidence on countries, sectors and methods.Publishes governance analysis and authorises publication of the year’s results at gate G6.Publishes sector analysis and the finance and insurance readiness series.
AkademieAuthors courses on methods, data and the Foundry systems, hosted on Risk Academy.Authors courses on governance, policy and programme roles, hosted on Risk Academy.Authors courses on finance, insurance and readiness, hosted on Risk Academy.

The pillars through the programme year

PillarQ1 · State and AgendaQ2 · Evidence and BuildQ3 · Stress Test and ReadinessQ4 · Annual Synthesis and Renewal
LaboratoriumsOpens the year’s experiments on the questions the mandate namesRuns prototypes in short cycles; hands reproducible ones to the FoundryTests ideas alongside Action Week; records what failed and whyWrites up every experiment; proposes next year’s questions
FoundryOpens cycle projects; National Portfolio baselineQualifies sources; one-month controlled buildRuns simulations in Action Week; releases temporary capacitySupplies data bundles; registers capability gaps
UniversumAnnual mandate (G0)Missions admitted (G1), qualified (G2), build accepted (G3)Action Week (G4), stand-down, evidence sealed (G5)Publication authorised (G6), renewal (G7)
StandaardeRoutes missions to standardsComposes profiles; validates the buildMonitors conformance; findings become proposalsCouncil review; adopted changes published
VerslaeState and Agenda editionEvidence and Build editionStress Test and Readiness editionAnnual Synthesis, the flagship
AkademiePathways open; cohorts enrolQualification courses; learning on the buildExercise assessments; completion recordsCourse revisions; next cohorts open
04How to take part

Roles for every kind of contributor.

Programme

Nasionale en streeksprogramme

Propose a mission once an edition is authorised.

Infrastruktuur

Computing and network contributors

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

Gashere

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.

Openbaar

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 the contact form, hosting proposals to the partnership form.

05Vrae

Questions about Universe.

When and where is the next 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 Universe website address?
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, the Lead Institution of the Nexus Consortium, 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.
VerslaeDra by

Dra bewyse vanaf hierdie bladsy by.

Reports is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.

Global Risks Forum
Konsortiumsekretariaat

Prepare a mission worth testing.

The Secretariat answers Universe enquiries and names the next step. An enquiry receives a reference; it does not create a mission place, an allocation or a registration.