G06 · INTEGRITY · correctionsGCRI dossier · service level R0
GCRINexus RegistryEstablished
Corrections and concerns

Corrections and version history

How to challenge content on Nexus Registry, report an error or raise a concern, and what happens next.

Nexus RegistryRegister
  1. PublisherThe Global Centre for Risk and Innovation
  2. FieldGovernance and institutions, Research and evidence
  3. StatusEstablished
  4. Service levelR0: information and enquiries

GCRI · Established · service level R0

01In brief

The short answer.

Corrections and concerns is the Nexus Registry route for challenging a finding, reporting an error or raising a privacy or safeguarding concern about its work on governance and institutions. Each report receives a reference and is reviewed, where possible, by someone not involved in the work; the outcome is a published new version with its history, or a reasoned decline.

02Canvas

Report to outcome.

Canvas · report to outcomeDesign, not a record
How a correction moves on Nexus RegistryA report is acknowledged and triaged; a reviewer not involved in the original work assesses it; the outcome is a new version with its history or a reasoned decline, and the reporter is told either way. Design of the workflow, not a record.

Fig.How a reported error is reviewed and corrected. Design, not a record.

03Geography

Jurisdictions in Western Europe.

The jurisdictions that hold authority over this question: countries, their first-level divisions and capitals, shown for Western Europe as an example geography for this subject.

The jurisdictions that hold authority over this question: countries, their first-level divisions and capitals.Boundaries as drawn by Natural Earth; no position on disputed areas.
GCRI · Nexus Registry · fieldDESIGN FIGURE
04Routes

Where to write.

ConcernWrite to
An error or a challenge to a findingintegrity@therisk.global
Privacyprivacy@therisk.global
A safeguarding concernsafeguarding@therisk.global
05Record corrections

How a registry record is corrected.

StepWhat happens
ReportThe error is reported with the record identifier and evidence
ReviewSomeone who did not create the record reviews it
New versionA corrected version is created; the old one stays, marked as superseded
PropagationRecords that cite the old version are flagged for review

Identifiers never change meaning; a correction creates a new version under the same identifier family.

06Process

What happens next.

  1. 01

    Acknowledgement

    You receive a reference and the next step.

  2. 02

    Review

    The concern is reviewed by someone not involved in the original work, where possible.

  3. 03

    Outcome

    A correction is published as a new version with its history; a declined challenge receives reasons.

07Key terms

Terms used on this page.

Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.

TermDefinition
CorrectionA published notice that amends an error in a work whose main findings stand.
RetractionThe formal withdrawal of a published work whose findings are unreliable, with a notice that stays visible.
Expression of concernA notice that alerts readers to serious doubts about a work while they are investigated.
Silent editA change to a published record made without a new version, notice or date.
08Sources

Where this page's references lead.

The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.

09Questions

Questions and answers.

Can I raise a concern anonymously?
Yes, though we may not be able to follow up without a way to reach you.
Nexus Registry

Bring your expertise to this field.

The current service level is R0: information and enquiries. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.

Have questions?