The Nexus Ecosystem is the whole architecture that The Global Centre for Risk and Innovation (GCRI) keeps technically coherent: the consortiums, the Nexus Foundry operating environment, the annual Nexus Universe programme, the Nexus Network and its temporary Core, the Nexus Registry, the Academy and Nexus Reports. Each part has a different job, and none of them is a product sold separately. This page is the gateway to each part and states, part by part, what operates today and what is designed to open later. See also the Consortium overview and the GCRI home page.
GCRI · Institution · service level R0
The Nexus Ecosystem is the whole architecture that GCRI keeps technically coherent: the consortiums, the Nexus Foundry work environment, the annual Nexus Universe programme, the Nexus Network and its temporary Core, the Nexus Registry, the Academy and Nexus Reports. Each part has one job, none is sold separately, and the service level is R0.
Mountain ranges, deserts, wetlands, glaciers and reefs, and how remote each division is from large cities, shown for Mozambique and Malawi as an example geography for this subject.
| Part | Its job | Gateway |
|---|---|---|
| Nexus Foundry | The persistent work environment: projects, models, evidence, decisions and programme memory, in twenty systems. | Foundry technical gateway |
| Nexus Network and Nexus Core | A durable federation of retained sites, and each year a temporary technical backbone for the annual programme. | Network and Core |
| Nexus Universe | The annual operating, integration, exercise and learning programme, governed by The Global Risks Forum (GRF). | Nexus Universe website |
| Nexus Registry | Public-safe records of programmes, evidence, publication status and correction histories. | Registry gateway |
| Nexus Labs | Test protocols and reproducible evaluation of candidate technologies. | Labs gateway |
| Academy | Leadership baselines, specialist learning and supervised work. | Academy and learning |
| Nexus Reports | One governed publication programme with methods and corrections. | Reports gateway |
The parts are designed to run as one cycle. A national question becomes a Foundry project; selected work is tested in the annual programme on temporary Core capacity; reviewed findings are published in Nexus Reports; handoffs and receipts are kept by the Rails system; and the federation of retained sites carries the capability into the next year.
The cycle is written one year of work, one month to build, one week to test and one day to stand down. The last stage is a planned stand-down; review, reconciliation and corrections continue afterwards. See the annual programme cycle.
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 independently operated systems whose interaction delivers capabilities none provides alone. |
| Digital public good | Open-source software, data, models, standards or content that meet the Digital Public Goods Standard. |
| Service level R0 | The current service level of Nexus pages: information and enquiries only. An enquiry receives a reference and a named next step; it creates no membership, contract, assignment or commitment. |
The current service level is R0: information and enquiries. The public pages of each part describe its design and current state. Workspace access, computing allocations and event registration open only when their team, terms and review capacity are in place. Planned reports appear as publication intentions, never as releases.
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.