The Global Centre for Risk and Innovation (GCRI)
Public gateway to the technical work environment while keeping project permissions and privileged services within Foundry. Nexus Foundry is an established platform published by The Global Centre for Risk and Innovation.
Project space 12 · Cluster east
| J-81914 | Flood model ensemble | Project owner | 00:50:12 | Running |
| J-26094 | Tile render, zoom 0 to 12 | GIS workspace | 00:03:40 | Running |
| J-78537 | Evidence export | Model steward | 00:00:25 | Done |
| J-72519 | Agent tool call batch | Agent sandbox | 00:01:19 | Policy block |
Nexus Foundry · Workspace and job consoleWorkspace and job console, in outline: domain structure with placeholder names and illustrative values, not a record.
A risk modelling environment is the combination of compute, data pipelines, models, access controls and records in which risk analyses are built and run. Nexus Foundry is designed as that environment for national risk models and digital twins, and its pages set out the risks inside such work, from silent data transformation to permission drift, overreaching agents and compute that fails when needed.
Engineers; model builders; researchers; technology operators; project owners.
System specifications; APIs; geospatial model workflows; authorization.
Capability catalogue; installation guidance; public technical examples.
For nexus foundry, in GCRI's spatial-intelligence reading, the map opens on night lights, true-colour imagery and population density with true colour from NASA GIBS, framed on North America; every other NASA layer, live feed and forecast waits in the layer list.
The interactive map needs JavaScript; the layer list and sources are below.
Layers 3
Connected activity, for this page
Keyboard, with the map focused
Hold Ctrl or ⌘ and scroll to zoom
Latest available
NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © OpenStreetMap contributors (ODbL) · Natural Earth
Loading the latest NASA imagery.
Drag to move. Ctrl or ⌘ and scroll, pinch or the buttons to zoom; hover for the values under the pointer; reset returns to the region.
For nexus foundry, in GCRI's spatial-intelligence reading, the map opens on night lights, true-colour imagery and population density with true colour from NASA GIBS, framed on North America; every other NASA layer, live feed and forecast waits in the layer list.Satellite and model products as NASA publishes them, each with its own date; indicators, not assessments of any place; claim ceiling INTEGRATED.
Layers and dates
Project onboarding, persistent context and permissions.
TopicCanonical Foundry system inventory.
TopicApproved geospatial public views.
TopicData, ontology, Chronotopes and lineage.
TopicWorkloads, reproducibility and limits.
TopicAI tools, authority and risk controls.
TopicCloud, local nodes and edge technical capacity.
TopicService units, credits, quotas and tenant charges.
Systemic risk is studied across water, energy, food, health, finance and infrastructure at once, and the analysis that supports a decision usually passes through many hands: a hydrologist's flood model, a utility's asset register, a satellite product, a household survey, an economist's loss estimate. Each step transforms data, and each transformation carries assumptions. When those steps sit in personal folders, unversioned scripts and email attachments, three failures follow. Results cannot be reproduced, because nobody can say which data cut and which model version produced them. Permissions leak, because sensitive layers travel further than their owners agreed. And errors cascade, because a correction to an upstream source never reaches the products built on it.
These are engineering problems as much as scientific ones. Distributed computing, data stewardship, geospatial processing, machine learning and safety-critical software engineering each have mature practices for traceability, access control and verification. Nexus Foundry brings those practices into one environment designed for risk work, so that a figure in a published brief can be traced back to its sources, licences, transformations and model runs, and so that the people who own data keep control of it throughout.
All work in Nexus Foundry is designed to happen inside a project: a bounded workspace with a question, an accountable owner, data terms, a review plan and an openness profile. Authentication proves who someone is; authorization, decided request by request by the Nexus Sovereignty Framework (NSF), decides what they may do.
Workspaces keep data, models, maps, decisions and programme memory together across the year, with permissions set by the project rather than by the room.
GRIx registers sources with their owners and licences, keeps originals unchanged and binds every risk record to place, time and scenario.
NEXCORE is designed to schedule workloads across cloud, private infrastructure and edge nodes, so analysis can run where data is allowed to sit.
Identity, mandate, policy gates and receipts work the same way for people, applications and AI agents.
Nexus Foundry is for engineers, model builders, researchers, technology operators and project owners working on authorized projects. No system is open to the public by default, and a membership, payment or infrastructure offer is not an allocation.
The platform applies six methods from the STEM Commons: high-performance, cloud and edge computing, data engineering, interoperability and stewardship, geospatial information systems, artificial intelligence and machine learning, systems engineering and software and safety-critical systems engineering. Each method page says how the method is used here and links to its canonical description.
Every platform in the network names the systems it relies on on its own Foundry page, and Nexus Foundry serves all 63 platforms of the three institutions. Its closest counterpart is Actuarial and Quantitative Risk at The Global Risks Alliance (GRA), which shares the methods and modelling field and works on the validation of quantitative models. Governance questions about programme gates are convened by The Global Risks Forum (GRF) through the Governance Nexus. Build readiness is reported in the Foundry Build and Readiness series, and the build is exercised in the Nexus Universe through the Nexus Core build theme.
Nexus Foundry is operated at national and regional level by Nexus Consortiums through their host and lead organizations, within a multilateral programme led by three pillar not-for-profit institutions, GCRI, GRF and GRA, on a public-private-planet partnership.
Nexus Foundry is the compute and methods environment where national risk models, data pipelines and digital twins are built and run. It studies the risks inside that work: models that fit the past for the wrong reasons, pipelines that transform data silently, permissions that drift, agents that overreach and compute that fails when it is needed. Its pages set out the engineering, the data, the methods and the decisions for each part, with every value labelled by its evidence.
Ingestion, validation, standardisation and provenance, from the source passport to the published figure.
Ensembles, coupling, calibration, validation and reproducible runs for physical, statistical and agent-based models.
Coordinate reference, catalogues, OGC and STAC services, and the public-safe release of maps.
Cloud, private infrastructure and edge nodes scheduled as one capacity, with placement by data location and policy.
Machine learning models and tool-using agents, their evaluation, authority records and human review.
Projects, roles, mandates and policy gates that deny by default and record a receipt for every consequential action.
Contracts, software bills of materials, build provenance, testing and the evidence that a release is what it claims to be.
Service units, quotas and credits attributed to projects and kept independent of scientific state.
Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.
| Term | Definition |
|---|---|
| Digital twin | A computational representation of a physical system that is updated with data from it and used to explore its behaviour. |
| Data pipeline | A sequence of automated steps that ingests, validates, transforms and publishes data. |
| Fail closed | A design in which a control that cannot decide denies the request rather than allowing it. |
| Software bill of materials | A machine-readable inventory of the components and dependencies in a piece of software, in formats such as SPDX or CycloneDX. |
Every claim on Nexus Foundry rests on methods with a canonical page in the STEM Commons, so readers can see what a finding depends on and where its limits lie.
A question becomes evidence, a governed build, an organized community, a controlled test, a reviewed publication and, finally, a decision taken by the competent authority under its own rules.
Fig.The Nexus cycle on this platform, from question to renewal. Design, not a record of a run.
The platform does not set standards. It reads its evidence against the frameworks that competent bodies have adopted, so a finding can be placed where a decision-maker already works.
| Framework or standard | Body | What it sets |
|---|---|---|
| ISO/IEC 25010 and ISO/IEC 27001 | ISO and IEC | A product quality model for software and systems, and requirements for an information security management system and its controls |
| NIST AI Risk Management Framework | US National Institute of Standards and Technology | Functions to govern, map, measure and manage risks from AI systems across their life cycle |
| ISO/IEC 42001 artificial intelligence management system | ISO and IEC | Requirements for establishing, operating and improving an organisation's management of AI |
| OGC API standards and the SpatioTemporal Asset Catalog | Open Geospatial Consortium, STAC community | Interoperable web access to features, maps, tiles and coverages, and searchable catalogues of imagery and derived rasters |
| Climate and Forecast (CF) metadata conventions | CF conventions community | Standard names, units and coordinate descriptions for gridded scientific data in netCDF |
| FAIR guiding principles | FORCE11 and GO FAIR | Findable, accessible, interoperable and reusable data and metadata, for machines as well as people |
| SLSA and software bill of materials practice | OpenSSF; SPDX (ISO/IEC 5962) and OWASP CycloneDX | Levels of build provenance and integrity, and standard inventories of software components and licences |
| Model cards and datasheets for datasets | Research and practitioner community | Structured documentation of a model's intended use, evaluation and limits, and of a dataset's origin and composition |
| ISO 9001 quality management applied to models | ISO | Documented process, review, corrective action and continual improvement for model development and use |
| ACM artifact review and badging | Association for Computing Machinery | Criteria for research artefacts that are available, functional, and whose results have been reproduced by others |
GCRI studies a field as science, GRF governs it and GRA builds shared financial understanding of it. Nexus Foundry links to its counterparts so that work on one side is visible on the others.
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.