The Global Centre for Risk and Innovation (GCRI)
Nexus Foundry is built from 20 technical systems, each with a defined contribution and a defined limit. This page, published by The Global Centre for Risk and Innovation (GCRI), groups the systems by capability and states the access boundary of each. Nexus Foundry is operated at national and regional level by Nexus Consortiums through their host and lead organizations, within a multilateral programme led by GCRI, The Global Risks Forum (GRF) and The Global Risks Alliance (GRA). The current service level is R0: information and enquiries.
GCRI · Established · service level R0
Nexus Foundry capabilities are the twenty technical systems grouped into seven capability groups, from command and decision to research and innovation, each with a defined contribution and a stated limit. National and regional Nexus Consortiums operate Foundry through their host and lead organizations, within the multilateral programme led by GCRI, GRF and GRA.
Urban demand centres and the hubs that anchor digital and data infrastructure, shown for Southeast Asia as an example geography for this subject.
| Group | Systems | What the group does |
|---|---|---|
| Command and decision | Nexus, NorthStar, DSS | Command home, common operating picture and human decision support |
| Data and compute | NEXCORE, NEXQ, GRIx | Compute, ingestion, semantic risk intelligence and data products |
| Observation, warning and action | EOP, EWS, AAP | Observation, warning support and anticipatory action workflows |
| Networks and signals | NET, OP, SIG | Network, observatory and signal-integrity systems |
| Governance and workspace | NSF, Hub, Studio | Policy, collaboration and composition workspaces |
| Mission applications | Factory, Apps, Rails, Portals | Software factory, application runtime, institutional rails and portals |
| Research and innovation | Labs | Experiments, testbeds, benchmarks and research handoffs |
| System | Contribution | Boundary |
|---|---|---|
| Nexus | Portfolio and institutional project coordination | No substitute for external decision authority |
| NorthStar | Common operating picture and field coordination | Civilian scope only |
| DSS | Scenarios, options, uncertainty and decision analysis | Analysis is not the decision |
| GRIx | Data, ontology, evidence, lineage and risk products | Source rights and limitations persist |
| EWS | Forecast verification and warning support | Official issuance stays with authorized parties |
| AAP | Trigger evaluation and preparedness | No automatic release of funds or dispatch |
| SIG | Authorized signal and positioning integrity observation | No unauthorized collection |
| Rails | Protocols, obligations, handoffs and receipts | A receipt is not settlement or external acceptance |
| Portals | Public and audience-specific delivery | Publication never overrides source permission |
| Labs | Reproducible research, testbeds and benchmarks | Experiment results are not certification |
The full directory, with every system, is on technical systems.
Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.
| Term | Definition |
|---|---|
| System of systems | A set of independent systems that work together to deliver capabilities none can deliver alone, each keeping its own management and purpose, in the sense ISO/IEC/IEEE 21839 uses. |
| Least privilege | Granting each user or process only the access needed for its current task. |
| Claim ceiling | The strongest statement a page may make about a capability, set by the evidence on record; without operating evidence a page describes a design or an integration, never readiness. |
No system is open to the public by default. Access requires an authorized project with an accountable owner, data terms and a review plan, and the policy gates of NSF decide each request. A membership, a payment or an infrastructure offer is not an allocation.
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.