The Global Risks Index
NXS-GRX · Contribute

Make the index better

Correct a value, reply for a country, review a method, offer data or take part in the perception survey.

Page GRX-CTBEdition Baseline Edition 2026Evidence close 2026-09-30Values not yet publishedSnapshot 31a753f76
FIG 1 · What happens to a contribution
ReceivedAcknowledgedTriagedReviewedDispositionLogged
6
ways to contribute
195
country rights of reply
20
indices open for review
7
instruments open for review
01Contribute

Six ways to contribute

Anyone

Correction

Reviewed in public; logged with its effect on each value

Governments and national institutions

Right of reply

Published beside the profile with the review outcome

Anyone

Method comment

Answered in the methodology review record

Invited and volunteer experts

Expert review

Recorded with a conflict-of-interest declaration and credit

Data holders

Data offer

Registered, licence-checked, then used only as its licence admits

Experts and the public

Perception survey

Feeds the Perception instrument only

The contribution form appears here when the NXS-GRX (canonical data, provenance and risk) gateway is connected. Until then, open an issue in the canonical repository or write to the Secretariat. No account or personal data beyond a contact is needed; ORCID is used for credit.
02Journeys

Follow your contribution

Choose what you are submitting to see every job it passes through and where it waits for people.

on: correction submitted
Submit a correction
In progressTriggered by You10 jobs1 approval gate1 matrix job
Graph
01Intake
02Intake
03Verify
04Recompute
05Recompute
06Review
07Publish
08Publish
100%
Timeline
Job0 d5 d10 d15 d20 dTarget
Correction receivedYouinstant
AcknowledgedSecretariat2 d
TriageIndex editors5 d
Evidence checkData stewards5 d
Recompute dependent valuesNXS-GRX run service1 d
What changed and whyNXS-GRX run service1 h
Steward reviewStewards10 d
Correction log entrySecretariat1 d
Propagate to profiles, tiles and APIFoundry1 h
Reply to youSecretariat1 d

End to end on the longest path: about 20 d of proposed target service levels. Gates wait for the people named; bars with a fading end have no fixed length.

Steps
  1. Correction received
    Intake · You · instant
    Page ID and value captured · Evidence and source attached · Contact for the reply
    NXS-GRX gateway
  2. Acknowledged
    Intake · Secretariat · 2 days
    Receipt sent · Request logged in the ledger
    NXS-GRX gatewayPostgreSQL ledger (row-level security)
  3. Triage
    Verify · Index editors · 5 days
    Scope: value, definition or method · Affected definitions resolved · Priority set
    PostgreSQL ledger (row-level security)indicator standard
  4. Evidence check
    Verify · Data stewards · 5 days
    Source release verified · Licence admits the use · Lineage traced to the value
    Licence registerProvenance (W3C PROV)
  5. Recompute dependent values matrix · every dependent value
    Recompute · NXS-GRX run service · 1 day
    Dependency graph walked · Values recomputed with 1,000 draws · Intervals and classes updated
    NXS-GRX run serviceTested model kernelsMonte Carlo engine
  6. What changed and why
    Recompute · NXS-GRX run service · 1 hour
    Before and after per value · Driver decomposition
    NXS-GRX run serviceProvenance (W3C PROV)
  7. Steward review approval
    Review · Stewards · 10 days
    Method and evidence reviewed · Disposition recorded
    PostgreSQL ledger (row-level security)
  8. Correction log entry
    Publish · Secretariat · 1 day
    Public log entry · Record version bumped
    Correction logNS-1 UNI catalogue
  9. Propagate to profiles, tiles and API
    Publish · Foundry · 1 hour
    Profiles republished · Tiles invalidated · API caches refreshed
    Public cut APIVector tilesAttribution service
  10. Reply to you
    Publish · Secretariat · 1 day
    Outcome and effect on each value
    NXS-GRX gateway
Artifacts
ArtifactJobWhoStage
Request record GRX-REQ-…Correction receivedYouIntake
AcknowledgementAcknowledgedSecretariatIntake
Triage noteTriageIndex editorsVerify
Evidence recordEvidence checkData stewardsVerify
Run record with seed and digestRecompute dependent valuesNXS-GRX run serviceRecompute
Change reportWhat changed and whyNXS-GRX run serviceRecompute
DispositionSteward reviewStewardsReview
Correction GRX-COR-…Correction log entrySecretariatPublish
Release notePropagate to profiles, tiles and APIFoundryPublish
ReplyReply to youSecretariatPublish
DoneIn progressWaiting for approvalQueuedApproval gateMatrix jobYou are here
A correction to a value or a definition travels from the gateway to a recomputed, steward-reviewed and logged result. The canvas shows where a request stands at the marked job; it is an illustration, not the status of a real request. Durations are proposed target service levels. Select a job for its steps, the people who act, the technology it runs on and what it produces.
on: reply submitted by a national institution
Country right of reply
In progressTriggered by National institution7 jobs1 approval gate1 matrix job
Graph
01Intake
02Intake
03Review
04Decide
05Decide
06Publish
100%
Timeline
Job0 d5 d10 d15 d20 d25 dTarget
Reply receivedNational institutioninstant
Institution verifiedSecretariat3 d
Evidence reviewData stewards10 d
Method reviewIndex editors10 d
Steward decisionStewards10 d
Recompute if acceptedNXS-GRX run service1 d
Reply published beside the profileSecretariat2 d

End to end on the longest path: about 26 d of proposed target service levels. Gates wait for the people named; bars with a fading end have no fixed length.

Steps
  1. Reply received
    Intake · National institution · instant
    Institution identified · Reply and evidence attached
    NXS-GRX gateway
  2. Institution verified
    Intake · Secretariat · 3 days
    Mandate checked · Contact confirmed
    ORCID and RORPostgreSQL ledger (row-level security)
  3. Evidence review matrix · per indicator raised
    Review · Data stewards · 10 days
    Each point mapped to indicators · Sources checked · Licence admits the use
    Licence registerProvenance (W3C PROV)indicator standard
  4. Method review
    Review · Index editors · 10 days
    Method questions answered
    Tested model kernels
  5. Steward decision approval
    Decide · Stewards · 10 days
    Accept, partly accept or keep · Reasons written
    PostgreSQL ledger (row-level security)
  6. Recompute if accepted
    Decide · NXS-GRX run service · 1 day
    Dependent values recomputed
    NXS-GRX run serviceMonte Carlo engine
  7. Reply published beside the profile
    Publish · Secretariat · 2 days
    Reply and outcome public · Log entry
    Correction logPublic cut API
Artifacts
ArtifactJobWhoStage
Request recordReply receivedNational institutionIntake
Verification noteInstitution verifiedSecretariatIntake
Evidence recordEvidence reviewData stewardsReview
Method noteMethod reviewIndex editorsReview
DecisionSteward decisionStewardsDecide
Run recordRecompute if acceptedNXS-GRX run serviceDecide
Public replyReply published beside the profileSecretariatPublish
DoneIn progressWaiting for approvalQueuedApproval gateMatrix jobYou are here
A government or national institution replies to a profile; the reply is reviewed in public and published beside the profile. The canvas shows where a request stands at the marked job; it is an illustration, not the status of a real request. Durations are proposed target service levels. Select a job for its steps, the people who act, the technology it runs on and what it produces.
on: dataset offered
Offer a dataset
Waiting for approvalTriggered by Data holder8 jobs1 approval gate1 matrix job
Graph
01Intake
02Intake
03Rights
04Harmonise
05Quality
06Admit
07Admit
100%
Timeline
Job0 d5 d10 d15 d20 d25 dTarget
Dataset offeredYouinstant
Source registeredData stewards3 d
Licence reviewCounsel15 d
Harmonise seriesNXS-GRX run service2 d
Map to indicatorsIndicator editors5 d
Quality checksNXS-GRX run service1 d
Admitted to the fabricFoundry1 d
Credit on every valueAttribution serviceinstant

End to end on the longest path: about 25 d of proposed target service levels. Gates wait for the people named; bars with a fading end have no fixed length.

Steps
  1. Dataset offered
    Intake · You · instant
    Description, coverage and licence
    NXS-GRX gateway
  2. Source registered
    Intake · Data stewards · 3 days
    Source record and UNI · Vintage and checksum
    PostgreSQL ledger (row-level security)NS-1 UNI catalogue
  3. Licence review approval
    Rights · Counsel · 15 days
    Terms read · Public, isolated or restricted use decided
    Licence register
  4. Harmonise series matrix · per series
    Harmonise · NXS-GRX run service · 2 days
    Units, areas and time aligned · No imputation
    NXS-GRX run serviceindicator standard
  5. Map to indicators
    Harmonise · Indicator editors · 5 days
    Crosswalks with relation and confidence
    indicator standard
  6. Quality checks
    Quality · NXS-GRX run service · 1 day
    Coverage vector · Outliers and breaks · Evidence class
    NXS-GRX run serviceProvenance (W3C PROV)
  7. Admitted to the fabric
    Admit · Foundry · 1 day
    Available to the next evidence cut
    FoundryPostgreSQL ledger (row-level security)
  8. Credit on every value
    Admit · Attribution service · automatic
    Attribution rows rendered
    Attribution service
Artifacts
ArtifactJobWhoStage
Offer recordDataset offeredYouIntake
Source recordSource registeredData stewardsIntake
Register rowLicence reviewCounselRights
HAR seriesHarmonise seriesNXS-GRX run serviceHarmonise
Crosswalk rowsMap to indicatorsIndicator editorsHarmonise
Quality reportQuality checksNXS-GRX run serviceQuality
Admission recordAdmitted to the fabricFoundryAdmit
CreditCredit on every valueAttribution serviceAdmit
DoneIn progressWaiting for approvalQueuedApproval gateMatrix jobYou are here
A dataset enters NXS-GRX only through a registered source with a recorded licence, then is harmonised and mapped to indicators. The canvas shows where a request stands at the marked job; it is an illustration, not the status of a real request. Durations are proposed target service levels. Select a job for its steps, the people who act, the technology it runs on and what it produces.
on: reviewer application
Become an expert reviewer
Waiting for approvalTriggered by Expert5 jobs1 approval gate1 matrix job
Graph
01Apply
02Check
03Review
04Review
05Credit
100%
Timeline
Job0 d10 d20 d30 d40 dTarget
ApplicationYouinstant
Conflict-of-interest declarationSecretariat5 d
AssignmentIndex editors5 d
ReviewYou30 d
CreditedSecretariatwith the edition

End to end on the longest path: about 44.8 d of proposed target service levels, before the jobs that run with no fixed end. Gates wait for the people named; bars with a fading end have no fixed length.

Steps
  1. Application
    Apply · You · instant
    Expertise and ORCID
    NXS-GRX gatewayORCID and ROR
  2. Conflict-of-interest declaration approval
    Check · Secretariat · 5 days
    Interests declared and recorded
    PostgreSQL ledger (row-level security)
  3. Assignment
    Review · Index editors · 5 days
    Index, instrument or region
    indicator standardTested model kernels
  4. Review matrix · per item
    Review · You · 30 days
    Comments with evidence
    Tested model kernels
  5. Credited
    Credit · Secretariat · with the edition
    CRediT role on the release
    ORCID and RORZenodo deposit
Artifacts
ArtifactJobWhoStage
ApplicationApplicationYouApply
DeclarationConflict-of-interest declarationSecretariatCheck
AssignmentAssignmentIndex editorsReview
Review recordReviewYouReview
CreditCreditedSecretariatCredit
DoneIn progressWaiting for approvalQueuedApproval gateMatrix jobYou are here
Experts review domain indices, instruments and regions, with declared interests and credit. The canvas shows where a request stands at the marked job; it is an illustration, not the status of a real request. Durations are proposed target service levels. Select a job for its steps, the people who act, the technology it runs on and what it produces.
03Reply

Corrections and right of reply

Name the page ID (for example GRX-PRF-KEN), the value or definition, the evidence and its source. Every submission is acknowledged, triaged and given a recorded disposition; accepted corrections propagate to every dependent value.

04Experts

Expert review

Reviewers are sought for every domain index, the instruments (nowcasting, forecast verification, scenario pathways, catastrophe modelling, network contagion) and every region. Review is credited and declared.

05Data

Data contributions

Data enters only through registered sources with a recorded licence. Contributors keep their rights; NXS-GRX uses data only as its licence admits and credits it on every value it reaches.

06Credit

Credit and licence

Contributors are credited by role (CRediT) with ORCID and ROR identifiers. Nexus-authored text is intended for CC BY 4.0 on release; contributed material keeps its own licence.

Every contribution is answered

Acknowledged, triaged and given a recorded disposition, in public.