The Global Centre for Risk and Innovation (GCRI)
Nexus Foundry is designed to be integrated through versioned, documented interfaces rather than through private arrangements. This page, published by The Global Centre for Risk and Innovation (GCRI), explains how interfaces, software releases and documentation are managed, and what developers can expect as each is released. Interfaces open to external developers only with authorized projects. The current service level is R0: information and enquiries.
GCRI · Established · service level R0
Developing for Nexus Foundry means integrating through versioned, documented interfaces rather than private arrangements. The page explains how interfaces, software releases and documentation are managed and what developers can expect as each is released; interfaces open to external developers only within authorized projects.
Urban demand centres and the hubs that anchor digital and data infrastructure, shown for Western Europe as an example geography for this subject.
Interfaces are described as machine-readable contracts, such as OpenAPI, with a version and a change log.
Breaking changes take a new version. Earlier versions are deprecated with notice, not withdrawn silently.
Every call is authorized by the policy gates of NSF, with OpenID Connect and OAuth for identity and delegation.
| Area | Standards | Systems |
|---|---|---|
| Geospatial | OGC API Features, OGC API Records, STAC, Cloud Optimized GeoTIFF, GeoJSON, GeoPackage | EOP, NorthStar |
| Warning | Common Alerting Protocol 1.2 | EWS |
| Provenance and catalogues | W3C PROV, DCAT 3, JSON-LD, SKOS | GRIx, Portals, Hub |
| Software supply chain | SPDX, CycloneDX, SLSA provenance, in-toto, OCI images | Factory |
| Observability | OpenTelemetry | Factory |
The Factory system turns blueprints into tested applications with a software bill of materials and provenance.
Releases are signed and attestable. A release is not a deployment authorization.
The Apps system checks entitlement and compatibility and installs into a declared tenant environment, with rollback.
Defects and security fixes are released as new versions with notes.
Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.
| Term | Definition |
|---|---|
| Contract-first design | Defining an interface's specification before implementing either side of it. |
| Interface control document | A record of the variables, units, timing and owners at an interface between systems. |
| Versioning | Keeping each changed state of a record as a distinct, dated version linked to the ones before and after 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. |
Public technical documentation, examples and change logs are published on Nexus Foundry as each is reviewed for public release. Restricted documentation stays inside authorized projects. Each document states the version of the interface or release it describes, its date and its owner, and corrections are published as new versions rather than silent edits. Security issues go to security@therisk.global, the security disclosure route.
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.