GCRI · Foundations
The public-good technical stack for verifiable resilience infrastructure
How the Nexus programme organizes open methods, governed data, twenty documented systems and contributed capacity into a public-good technical stack, and why that stack informs decisions it never takes.
- As of
- 21 October 2026
- Reading
- 11 minutes
- Evidence
- 14 sources, cited in order
Methods and evidence
- Evidence
- 14 sources, cited in order and listed under References
- Figures
- 4 figures
- Data availability
- Every chart's data is published as a table on this page.
01What the public-good technical stack is
What the public-good technical stack is
The public-good technical stack is the shared technical layer of the Nexus programme: the methods, evidence records, open standards, documented systems, testbeds and contributed capacity through which governments, operators, universities, financial institutions, communities and technology providers can examine systemic risk together. It is a public good in the economist's sense that its methods and records gain value as more parties can read and reuse them. It is not a procurement vehicle, an investment platform, a certification scheme or a command system 2,1.
Three institutions carry it in their own roles. GCRI supplies the science, methods, data and technical work; The Global Risks Forum (GRF) stewards Nexus Universe, the annual programme where capabilities are convened and tested; and The Global Risks Alliance (GRA) makes the evidence readable to finance and insurance and carries out no regulated financial activity 1. GCRI Canada is Lead Institution, Consortium Secretariat and lead contracting organization, and its standard agreements are inherited by every deployment 6.
The earlier version of this page described the stack through component passports, continuity rails and a branded annual core. Those are not on the current record. The stack described here is the one the programme documents: twenty systems, six pillars, nine evidence labels and recorded handoffs.
02Why no single actor can hold the stack
Why no single actor can hold the stack
No organization can hold all the data, run all the systems, supply all the compute, build all the models, know every local context and take every decision. The capabilities exist, but they are distributed: computing centres and research networks hold capacity, statistical and meteorological agencies hold authoritative sources, operators understand their systems, and communities hold knowledge no dataset records. A public-good stack is the way those capabilities can converge on one question without one party absorbing the others.
Reach is the first test. The International Telecommunication Union estimates that about 6 billion people used the Internet in 2025, while 2.2 billion did not, 96% of them in low- and middle-income countries 4. Use was 94% in high-income countries and 23% in low-income ones, 85% in urban areas and 58% in rural ones, 77% among men and 71% among women 4. 5G covered 55% of the world's population but only 4% in low-income countries 4. Evidence built only for the best-connected places reproduces the divide it should help close.
Governments have recognised the stake. The Global Digital Compact, negotiated by 193 Member States, commits governments to increase investment in digital public goods and digital public infrastructure 7. The Universal DPI Safeguards Framework, developed through a multi-stakeholder process convened by the UN Secretary-General's Envoy on Technology and UNDP, sets guardrails so that such infrastructure mitigates risks to individuals and societies 8.
Fig. 01A public-good stack has to work where connectivity does not
Figure 1 in words, and its data
Four pairs of horizontal bars on a 0 to 100 per cent scale. Income: high-income countries 94 per cent, low-income countries 23 per cent. Location: urban areas 85 per cent, rural areas 58 per cent. Sex: men 77 per cent, women 71 per cent. Age: 15 to 24 years 82 per cent, rest of population 72 per cent. A side panel: about 6 billion people online in 2025, three quarters of humanity; 2.2 billion offline, 96 per cent of them in low- and middle-income countries; 5G covers 55 per cent of people, 4 per cent in low-income countries.
03Twenty systems, six layers, one trust layer
Twenty systems, six layers, one trust layer
The stack runs on twenty systems, each named by its Nexus Standards display code and registered descriptor and arranged in six layers 1. Command and decision holds NXS-DSS (decision cases and deliberation), NXS-EWS (multi-hazard monitoring and warning) and NXS-AAP (anticipatory action and triggers), among others. Data and intelligence holds NXS-GRX (canonical data, provenance and risk) and NXS-EOP (earth observation and digital twins). Observation and signals, compute and network, build and software, and delivery and work complete the stack.
NXS-NSF (trust, authorization and assurance) spans every layer. It is where identity, policy and access decisions are made, so that the question of who may see, change or release a record is answered once and applied everywhere. A system is a bounded set of functions, records and interfaces, not a product or a service offer, and the systems pages describe designs for reading, not deployments 1.
One distinction matters more than any other here. The Nexus systems are proprietary infrastructure, provided under written agreements, and no Nexus Standard depends on them 1,3. What is public is the method: the standards, their identifiers and the records they define. A country or institution can adopt a standard without using any Nexus system, and the adopt and implement guidance is written on that basis.
Fig. 02Twenty systems, six layers, one trust layer across them
Figure 2 in words
Six horizontal layers with their systems. Command and decision: NXS-CMD (integrated posture and executive synthesis) posture and synthesis, NXS-NST common operating picture, NXS-DSS decision cases, NXS-EWS monitoring and warning, NXS-AAP anticipatory action. Data and intelligence: NXS-GRX data, provenance and risk; NXS-EOP earth observation and twins. Observation and signals: NXS-OPS instruments and sensors; NXS-SIG signal, timing and PNT. Compute and network: NXS-COR compute and runtimes; NXS-NET network continuity. Build and software: NXS-FAC builds and signing; NXS-STU dashboards and workflows; NXS-NXQ (software, models and capability lifecycle); NXS-APP application catalogue. Delivery and work: NXS-HUB knowledge and records; NXS-POR (public, client and partner delivery); NXS-RLS agreements and handoffs; NXS-LAB (research, experiments and simulations). A vertical band, NXS-NSF trust, authorization and assurance, spans every layer.
04Public-good does not mean uncontrolled
Public-good does not mean uncontrolled
Public-good infrastructure is not the same as unrestricted access. The stack protects openness where it strengthens learning: the text of the Nexus Standards is licensed CC BY 4.0 and their code Apache-2.0, under the standards IP and participation policy 3. It protects confidentiality where privacy, security, sovereignty or community safeguards require it: national teams keep ownership of their data, protected Indigenous knowledge never enters public examples or model training, and public previews never reveal restricted topology 1.
The test is whether the arrangement can be read. The FAIR principles ask that data be findable, accessible, interoperable and reusable for machines and people, which does not require that all data be open 9. A restricted record that carries its source, licence, provenance and access rule is more useful to a public decision than an open file with none of them. Some public data sets the benchmark: Copernicus makes the vast majority of its Earth observation data available worldwide on a free, full and open basis 10.
Governed openness also applies to software. Builds of the stack are signed and tested for security and interoperability before a gate accepts them, and secure development practice of the kind set out in NIST SP 800-218, the Secure Software Development Framework published in February 2022, is the reference for how such builds are made 11,1.
05Contributed capacity and how it is recorded
Contributed capacity and how it is recorded
Much of the stack's intensity is borrowed. Computing centres, research and education networks, telecoms and equipment contributors may offer qualified resources for a year's missions, and the Network and Core page records how NXS-COR (compute, nodes and runtimes) and NXS-NET (network topology and continuity) would hold that capacity 5. An offer moves through seven separate states: offered, qualified, reserved, allocated, accessible, measured and accepted 1,5.
None of these states implies the next. Offered capacity is never counted as reserved, consumed or funded; neither membership nor sponsorship guarantees a computing allocation; and evaluation never depends on a high contribution 1. Temporary capacity is released at stand-down, and measured capacity results are reviewed in the fourth quarter of the programme year, as the Foundry pillar page sets out.
Fig. 03Seven states, none of which implies the next
Figure 3 in words
Seven boxes joined by arrows: 1 Offered, a provider proposes capacity; 2 Qualified, a qualification record exists; 3 Reserved, held for a named mission; 4 Allocated, separately approved for use; 5 Accessible, users can reach it; 6 Measured, use and results measured; 7 Accepted, results accepted on record. A note: no state implies the next; offered capacity is never counted as reserved, consumed or funded; neither membership nor sponsorship guarantees a computing allocation; temporary capacity is released at stand-down and measured results are reviewed in the fourth quarter.
06The public-good stack and the enterprise stack
The public-good stack and the enterprise stack
The central feature of the model is a separation. The public-good stack holds evidence, methods, testbeds, open standards, records, teaching and published reports. Lawful enterprise activity, procurement, financing, lending and investment, underwriting, regulatory approval and the operation of production infrastructure, is carried out by actors with their own authority, contracts, licences and risks 2,1.
The programme states the separations as rules. A submitted application is not membership; an infrastructure offer is not an allocation; a planned hub is not an operational site; readiness evidence is not a financing or underwriting decision 2. Testbed participation is not a regulatory sandbox, a certification or a procurement status, and test completion is never presented as accredited certification 1,12. When evidence is handed to an institution that decides, it moves under a written agreement through NXS-RLS (participants, agreements and handoffs), and GRA's handoff page explains what such a handoff can and cannot carry 13.
Digital public goods have their own yardstick outside the programme. The Digital Public Goods Standard sets nine indicators, from relevance to the Sustainable Development Goals and open licensing to platform independence, documentation, data extraction, privacy and do-no-harm by design 14. The programme reads its own open components against such yardsticks; recognition under them is decided by the body that keeps them.
Fig. 04The stack informs decisions it never takes
Figure 4 in words
Left panel, public-good stack inside the programme: evidence with labels, sources and limits; methods, testbeds and reproducible builds; open standards with text under CC BY 4.0 and code under Apache-2.0; records, identifiers and correction history; teaching, published reports and working papers. Right panel, lawful enterprise activity outside the programme: procurement awards and contracts; financing, lending and investment; underwriting and risk transfer; regulatory approval and supervision; operation of production critical infrastructure. An arrow carries evidence to the right under a written agreement; decisions return only if their holder chooses to share them.
07How contribution enters without capture
How contribution enters without capture
Every contribution enters through a route with a stated first outcome and a boundary 1. A technology team responds to a testbed or mission call and receives a documented selection decision, an evaluation plan and controlled results. A standards body proposes methods or interoperability work and receives a scoped profile. An enterprise explores a sector programme, and precompetitive work never shares competitors' confidential information. A foundation supports a defined public-good capability under a contribution agreement and a use-of-resources report, and no support buys appointments, findings, consent or procurement advantage 1.
The Labs gateway applies one protocol to every test, from use case and comparator to reproducible build, test envelope and findings that include failure cases 12. Providers and sponsors are described by role only, hold no vote in the governance of the standards, and hold no decision over personal data or national programmes beyond written instructions 1. The technology providers route explains how an offer is made.
08What is changing
What is changing
- Digital public goods become policy. The Global Digital Compact turns investment in digital public goods and infrastructure into a shared commitment of governments 7.
- Safeguards travel with infrastructure. The Universal DPI Safeguards Framework, now at version 2.0, makes risk mitigation part of DPI design rather than an afterthought 8.
- Quality, not only access. With 5G at 55% coverage worldwide and 4% in low-income countries, the divide is moving from whether people are online to how well 4.
- Secure builds as a baseline. Secure software development practice is now a reference expectation for any build that informs public decisions 11.
09Three institutions reading one stack
Three institutions reading one stack
GCRI reads the stack for science: the methods, data and evidence labels behind each record, documented on the GCRI institution page. GRF reads it for convening: which capabilities a year's missions need and which gate admits them, through Nexus Universe on universe.nexus. GRA reads it for finance: whether evidence produced on the stack can be read by a competent financial institution, through finance readiness 1,13.
All three follow the Nexus cycle, in which Decide sits outside the programme, and teach the method through Risk Academy. Results reach the public record through Reports, with sources, limits and corrections.
What this page does not claim: the public-good technical stack is a documented design; no system is recorded as deployed or offered as a service, and the programme is at service level R0. GCRI does not regulate or certify, GRF does not regulate, finance or procure, and GRA does not lend, underwrite, rate or invest. Naming a framework, standard or data programme is not a claim of partnership, recognition or endorsement. Procurement, financing, underwriting, approval and operation stay with the institutions that hold those mandates; any finance vehicle is formed, if at all, by lawful actors outside the programme, as the lawful handoffs page explains.
Questions
Questions and answers
Is the public-good technical stack open source?
The standards are open: their text is licensed CC BY 4.0 and their code Apache-2.0. The Nexus systems are proprietary infrastructure provided under written agreements, and no standard depends on them, so a standard can be adopted without using any Nexus system.
Does contributing compute or software give a provider a role in decisions?
No. Providers work at arm's length and are described by role only. They hold no vote in the governance of the standards, and offered capacity is never counted as reserved, consumed or funded until each state is separately recorded.
Can sensitive national data be used without leaving the country's control?
That is the design intent. National teams keep ownership of their data, an experiment run for a country does not move its data into a shared pool, and access is decided through NXS-NSF under written agreements.
Does the stack replace digital public infrastructure that governments already run?
No. Governments own their infrastructure and decide what to adopt. The programme's records and standards are designed to be readable alongside national systems and frameworks such as the DPI safeguards, not to replace them.
Can the stack approve a project or make it financeable?
No. Readiness evidence is not a financing or underwriting decision, and testing is not certification. Evidence can be handed to the institution that decides, which then applies its own rules.
Terms
Glossary
- Public-good technical stack
- The shared layer of methods, records, open standards, documented systems and contributed capacity that many actors can use without any one of them controlling it.
- Governed openness
- Openness where it strengthens learning, confidentiality where rights, security or sovereignty require it, with the rule recorded for every record.
- Digital public infrastructure
- Shared digital building blocks, such as identity, payments and data exchange, that let governments deliver services at scale.
- Contributed capacity
- Computing, network or technical resources offered to the programme, recorded through seven states from offered to accepted.
- NXS-NSF
- The system for trust, authorization and assurance that spans every layer and decides who may see, change or release a record.
- Separation
- A recorded rule that one state is not the next, such as an offer not being an allocation or evidence not being a decision.
Related
Further reading across the network
Reuse and cite
Text CC BY 4.0. Cite the page with its date; data tables are linked under each figure.
Sources
References
14 sources, numbered in the order they are first cited
- The Global Centre for Risk and Innovation (2026-10). How Nexus Consortium works. therisk.global. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). Programme status. therisk.global. Accessed 2026-10-21.
- Nexus Standards (2026-10). Standards IP and participation policy. nexustandards.com. Accessed 2026-10-21.
- International Telecommunication Union (ITU) (2025-11-17). Facts and Figures 2025: global Internet use continues to rise but disparities remain. www.itu.int. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). Network and Core. therisk.global. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). GCRI Canada. therisk.global. Accessed 2026-10-21.
- United Nations (2024-09). Global Digital Compact. www.un.org. Accessed 2026-10-21.
- UN Office of the Secretary-General's Envoy on Technology and UNDP (2025). Universal Safeguards for Inclusive Digital Public Infrastructure: the Universal DPI Safeguards Framework, version 2.0. www.dpi-safeguards.org. Accessed 2026-10-21.
- Wilkinson et al., Scientific Data 3, 160018 (2016-03-15). The FAIR Guiding Principles for scientific data management and stewardship. doi.org. Accessed 2026-10-21.
- Copernicus, the Earth observation component of the EU Space Programme (2026). Access to data: the Copernicus free, full and open data policy. www.copernicus.eu. Accessed 2026-10-21.
- U.S. National Institute of Standards and Technology (NIST) (2022-02). SP 800-218, Secure Software Development Framework (SSDF) version 1.1. csrc.nist.gov. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). Labs gateway. therisk.global. Accessed 2026-10-21.
- The Global Risks Alliance (2026-10). Finance readiness: handoff to the institutions that decide. globalriskalliance.com. Accessed 2026-10-21.
- Digital Public Goods Alliance (2026). Digital Public Goods Standard. www.digitalpublicgoods.net. Accessed 2026-10-21.
Record
Editorial record
Facts and programme states are given as of 21 October 2026. This page is reviewed at least every 180 days and whenever a cited figure or a programme state changes. It replaces an earlier version of the same page, whose component passports, continuity rails, branded annual core and observatory product are not on the programme's current record; those structures have been removed.
Published by the GCRI editorial desk under the editorial integrity policy. To report an error or request a correction, use the corrections route; corrections are dated and listed with the page. Participation is recorded in the programme's participation records.
Cite this article
GCRI editorial desk (2026, June 8). The public-good technical stack for verifiable resilience. The Global Centre for Risk and Innovation. https://therisk.global/the-public-good-technical-stack-for-verifiable-resilience-infrastructure/
@online{gcri2026thepublicgoodtechnica,
author = {{GCRI editorial desk}},
title = {{The public-good technical stack for verifiable resilience}},
publisher = {The Global Centre for Risk and Innovation},
year = {2026},
month = {6},
url = {https://therisk.global/the-public-good-technical-stack-for-verifiable-resilience-infrastructure/},
language = {en}
} TY - ELEC AU - GCRI editorial desk TI - The public-good technical stack for verifiable resilience PB - The Global Centre for Risk and Innovation PY - 2026 DA - 2026/06/08 UR - https://therisk.global/the-public-good-technical-stack-for-verifiable-resilience-infrastructure/ LA - en ER -
Republish
Republish or translate this article free of charge, in print or online, under CC BY 4.0: keep the byline and The Global Centre for Risk and Innovation, link to the original and note any change. Figures, maps and twins made by the institutions carry the same licence; third-party data keeps its own credit line.
Attribution to paste
<p>The public-good technical stack for verifiable resilience infrastructure — GCRI editorial desk, The Global Centre for Risk and Innovation. First published 8 June 2026 at <a href="https://therisk.global/the-public-good-technical-stack-for-verifiable-resilience-infrastructure/">https://therisk.global/the-public-good-technical-stack-for-verifiable-resilience-infrastructure/</a>. Republished under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).</p>