The Global Centre for Risk and Innovation (GCRI)
The research behind Nexus Foundry: the questions it asks, the methods it uses and how evidence is reviewed before it is published.
GCRI · Established · service level R0
Nexus Foundry research is the evidence work behind the platform: questions such as project workstations and twenty technical systems, answered with high-performance, cloud and edge computing as well as data engineering, interoperability and stewardship and reviewed before publication. Every result carries an evidence label, from observed to modelled or expert judgement, and missing data is shown as missing, never filled silently.
Fig.How a finding is reviewed before it is published. Design, not a record.
Urban demand centres and the hubs that anchor digital and data infrastructure, shown for the United Kingdom and Ireland as an example geography for this subject.
Project onboarding, persistent context and permissions.
Canonical Foundry system inventory.
Approved geospatial public views.
Data, ontology, Chronotopes and lineage.
Workloads, reproducibility and limits.
AI tools, authority and risk controls.
Foundry research concerns the engineering of trustworthy analytical infrastructure: how builds stay reproducible, how agents stay within scope and how access stays lawful across institutions.
Results are labelled as observed, officially reported, estimated, modelled, forecast, scenario or expert judgement. Missing data is shown as missing, never filled silently.
Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.
| Term | Definition |
|---|---|
| Research integrity | Conduct of research in line with principles of reliability, honesty, respect and accountability, as the European Code of Conduct for Research Integrity sets them out. |
| Evidence label | A tag on an assertion naming the kind of evidence behind it, such as observed, officially reported or modelled. |
| Reproducibility | Obtaining consistent results using the same data and analysis code as the original study. |
| Interface contract | A versioned specification of the requests and responses a system accepts, such as an OpenAPI or Protocol Buffers definition. |
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
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.