GCRI · How Nexus works
Publish
Publishing is where an analysis becomes citable: an edited text, its evidence labels, its uncertainty, its version and the route for anyone to challenge it.
This step runs in Reports.
Where findings are published with their method, uncertainty and evidence class, and corrected as new versions. Go to Reports.
handoff in playrecorded handoffno direct handoff
Programme yearAll phases
L · F · U · S · R · A
- Pillars
- 5 of 6
- Handoffs
- 16 of 18
- Loops
- 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
- 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 at GCRI: Labs
- FoundryWhere methods, data and models become reproducible builds, each run with its inputs, version and limits on record.Foundry at GCRI: Foundry
- UniverseWhere a build is tested under controlled conditions with independent evaluators, so a method’s skill is measured, not assumed.Universe at GCRI: Universe technical officeuniverse.nexus
- Nexus StandardsWhere methods, identifiers and data schemas are codified in the open and corrected when a test finds a fault.Nexus Standards
- ReportsWhere findings are published with their method, uncertainty and evidence class, and corrected as new versions.Reports at GCRI: PublishReports
- Risk AcademyWhere methods and systems are taught on real data and real places, by working the case, on Risk Academy.Risk Academy
What happens between a result and a report.
- A named editor checks that each claim carries its evidence label and that the uncertainty language is consistent across the text.
- Review by people who did not do the work, chosen for the methods the finding depends on.
- Figures and maps are checked against the build that produced them; an illustration is captioned as one.
- Limits are written into the body, not a footnote: what the analysis cannot say, and where it would be wrong to apply it.
The series and their methods are on Reports; the Global Centre for Risk and Innovation (GCRI) edits the series and answers for what they publish.
The workspace for the publish step.
Action week
Universe · GCRI · Week 35 · Example interface, not a record
Tracks
controlled sessions
Observer notes
- O-1Escalation path unclear between cellsTrack 13 h
- O-2Data hand-off worked as designedTrack 23 h
- O-3Public message drafted before verificationTrack 33 h
GCRI · Action week. Action week: example names and illustrative values, not a record.
Versions, corrections and retractions.
A correction is a new version with its history, linked from the old one. Errors that change a conclusion are flagged at the top of the text. Concerns go to corrections, and the integrity rules are on editorial integrity. No funder, member or contributor can buy or block a finding.
How the process runs.
Process
Publish: Risk management process
ISO 31000:2018 sets out an iterative risk management process, from scope, context and criteria through assessment and treatment to monitoring, review and reporting.
01 Frame
- 01Scope, context and criteriaDataset · National DeskThe frame for the process: the scope, the external and internal context, and the risk criteria. Later steps are read against this frame.
02 Risk assessment
- 04Risk identificationStep · National DeskThe first part of risk assessment. Risk is usually expressed by risk sources, potential events, their consequences and likelihood.
- 05Risk analysisModel · National DeskThe second part of risk assessment. It considers consequences and likelihood of the identified risks, with guidelines, not a formula.
- 06Risk evaluationStep · National DeskThe last part of risk assessment. Results of the analysis are compared with the risk criteria to see where more action is needed.
03 Treatment
- 07Risk treatmentStep · National DeskTreatment options are selected, then plans are prepared and implemented. Residual risk is documented and goes to monitoring and review.
04 Across the process
- 02Communication and consultationStep · National DeskCommunication and consultation with stakeholders is its own process element. The standard draws it alongside the others, not in sequence.
- 03Monitoring and reviewStep · National DeskMonitoring and review take place at every stage. New experience, knowledge and analysis can revise elements, actions and controls.
05 Record and report
- 08Recording and reportingRecord · National DeskThe process and its outcomes are documented and reported. The standard does not name who receives the report in the clauses read.
Outline of an external standard or method, from its public sources. It describes what the framework says, not a record of any run. It does not show that Nexus or any partner performs, certifies or approves a step. A gate is a step of the method, never a Nexus approval.
Each pillar’s contribution.
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.
Bring a method, a dataset or a question.
Information and enquiries are open today. 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.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.