Skip to content

GRF · How Nexus works

Avakirin

An option from a dialogue becomes a text concrete enough to test: an interagency protocol, an escalation table, a data-sharing agreement. The Global Risks Forum (GRF) drafts the institutional text with the people who will operate it; the Global Centre for Risk and Innovation (GCRI) builds the technical parts in Foundry.

01Rêzik

Rêza ku tişt tê de diqewimin.

  1. 01PirsPêşengiya neteweyî, herêmî an sazûmanî
  2. 02DelîlBingeha STEM a platformê
  3. 03BuildFoundry
  4. 04Organîze bikeEkosîstema Nexus
  5. 05CeribandinUniverse (malpera serbixwe)
  6. 06Weşandinrêzeya Pergalên Stratejîk
  7. 07BiryarDesthilat û saziyên jêhatî, bi riya NXS-RLS (beşdar, lihevkirin û radestkirin)
  8. 08NûkirinRastkirin û ajandaya salane ya pêş
02Xwedî

Who owns the build step.

Foundry. Foundry holds the models, twins and data pipelines the question needs, and records every version.

03What gets built

Institutional arrangements as designed objects.

At the build step, an option from a dialogue becomes something concrete enough to test: a draft protocol between two agencies, a revised escalation table, a data-sharing agreement, a communication template. GCRI’s technical teams build any software or model components. GRF’s part is the institutional text, drafted with the participants who will have to operate it.

BerhemDrafted byChecked by
Interagency protocolThe agencies concerned, with GRF facilitationEach agency’s legal adviser
Escalation tableOperators and the authority that receives escalationBoth sides, in a walk-through
Data-sharing agreementData holders and usersData protection authority where personal data is involved
Public message templateCommunications leadsA sample of the audience in a readability test
04Pêvajo

Pêvajo çawa dimeşe.

Process explorer · Process

Build: Build, sign and accept

10 steps4 stages2 gates

Pêvajo

Build: Build, sign and accept

An admitted mission becomes a cycle project; the build is pinned, verified and signed, and GRF records acceptance for exercise, not permission to deploy.

  1. 01 Request and sources

    1. 01Admitted mission becomes a cycle projectRecord · Universe to FoundryAn admitted mission becomes a cycle project with a decision case.
    2. 02Qualify data sources and resourcesStep · GCRIGCRI qualifies data sources and resource offers and builds the scenario models. An offer is not an allocation.
  2. 02 Build and verify

    1. 03Source snapshotRecord · NXS-FAC (blueprints, builds and signing)The snapshot pins the commit, dependencies and generator versions.
    2. 04Build contractRecord · NXS-FAC (blueprints, builds and signing)The build contract declares the artefact kind, environment and reproducibility envelope.
    3. 05Integrate and buildModel · GCRIGCRI integrates software and data, signs builds, and tests security and interoperability.
    4. 06Verification suiteGate · NXS-FAC (blueprints, builds and signing)Required and advisory checks stay separate. Reproducibility needs pinned inputs, declared nondeterminism and independent rebuilds.
  3. 03 Sign and admit

    1. 07Sign the exact artefactStep · NXS-FAC (blueprints, builds and signing)NXS-FAC builds, attests and requests a signature via a scoped signer identity. It holds no key material.
    2. 08Package admissionStep · NXS-NXQ (software, models and capability lifecycle)NXS-NXQ receives the signed package and keeps admission evidence that binds the task, data class, evaluation suite and expiration.
  4. 04 Accept

    1. 09Core Build ReportRecord · GCRIThe Core Build Report is the go or no-go record. Universe assembles the Core and holds the decision for the exercise.
    2. 10G3 · Build accepted for exerciseGate · The Global Risks ForumGRF records whether the build is accepted for exercise. A signed build or release candidate is not permission to deploy to production.

The programme year · NXS-FAC · UniverseDesigned programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. The record order follows the Builds and Releases room lists of NXS-FAC.

05Versioning

Every draft carries its version and its owners.

Drafts are versioned so that the exercise tests a known text and the lesson can be traced back to it. The Foundry at GCRI holds the build environment for technical components.

06Şeş stûn

This step runs in Foundry.

Where the evidence behind a mandate or commitment is built, with its owner and limits on record. Go to Foundry.

Stûnan hilbijêre · li xetan bigere18 / 18 radestkirin

Rê

Around Foundry

The pillars Foundry hands work to and receives it from.

L · F · U · S · R · A

Stûn
6 ji 6
Radestkirin
18 ji 18
Çerx
17 girtî

Radestkirinên di xebatê de

  • 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

û 14 yên din

F01 heta F14 radestkirinên tomarkirî yên salê bernameyê ne, her yek bi hunera ku diguhere û qonaxa wê; R1, R2, R3 û R4 kar li dora xelekê digerînin. Xelek tê jimartin dema ku her stûnek li ser wê were hilbijartin. Her stûn ji hêla Nexus Consortium ve tê birêvebirin.
  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
09Çavkanî

Where this page’s references lead.

Sazî û belgeyên ku ev rûpel li hember wan tê xwendin. Rewş û çap diguherin; her girêdan diçe ba saziya derxistinê.

Global Risks Forum

Pirsek ya rêveberiyê bînin Forumê.

Agahî û pirs îro vekirî ne. Pirsek referansekê distîne û gava piştî wê dide nasîn; serlêdan, drav, veqetandina hesabkirinê û tomarkirin tenê dema ku tîm, mercên wê û kapasîteya vekolînê hebin vedibin.