GCRI · Foundations
Nexus Standards: how technical evidence becomes an open, correctable method
A method that works once is a demonstration; a method that others can repeat, check and correct is a standard. This page explains how the Nexus Standards are drafted, reviewed and adopted, and why every one of them is still a proposal.
- As of
- 21 October 2026
- Reading
- 13 minutes
- Evidence
- 17 sources, cited in order
Methods and evidence
- Evidence
- 17 sources, cited in order and listed under References
- Figures
- 5 figures
- Data availability
- Every chart's data is published as a table on this page.
01What the Nexus Standards are
What the Nexus Standards are
The Nexus Standards are the open standards through which the programme identifies, describes, verifies, monitors and cites what it produces. They are published and governed on nexustandards.com, whose text and status govern; this page explains and links, and does not restate any standard. The catalogue holds 19 foundation standards, from NS-0, the constitution and principles, to NS-16, the UNI application profile, and 349 Nexus Risk Standards in 15 series, with the NHS-1 risk atlas of 905 hazard types across twenty subject subsites 1.
Every one of them is a proposal. Each is "drafted here and applied by consuming systems, not adopted by a recorded authority decision" 1. A UNI, the identifier the catalogue gives each artefact, identifies and resolves; it "never certifies truth, readiness, approval, legal compliance or production status" 1. The Methods and standards page of the Nexus Ecosystem presents the same proposals from the side of the methods they would govern.
Nexus Standards is also one of the six pillars of the programme: the pillar that codifies, corrects and applies. Findings from a programme year enter as change proposals, and adopted standards return to the build of the next year and to Risk Academy as course modules 5. The earlier version of this page described a "standards interface" without bodies, stages or deciders. The current model names each of them, and the sections below follow it.
02Why coupled risk needs repeatable, open methods
Why coupled risk needs repeatable, open methods
A dashboard, a simulation or a model can be useful once. It becomes infrastructure only when another team, in another country, can repeat it and get a comparable answer, and when an error found by anyone can be corrected in the method itself rather than in one copy of it. Coupled risks make this harder, because the evidence comes from many institutions at once: a flood assessment draws on hydrology, asset registers, insurance exposure and public finance, each described in its own way.
Governments have recognised the problem in their own instruments. In the Global Digital Compact, adopted with the Pact for the Future on 22 September 2024, Member States committed by 2030 to develop and maintain open standards and to promote the adoption of open standards and interoperability across platforms and systems 6,7. The European Interoperability Framework sets 47 recommendations around 12 principles for public services that must work together 8. The UNESCO Recommendation on Open Science, adopted on 23 November 2021, asks for verifiable, reproducible and openly licensed knowledge 9.
An open standard is how those commitments become something a ministry, a utility or a research team can actually use. It says what a record must contain, how a method must be described and how a claim must be checked, and it can be read, implemented and challenged by anyone. The companion pages on open source, open standards and interoperability and on the Labs, where methods are tested first take the argument further.
Fig. 01Where the drafting effort has gone
Figure 1 in words, and its data
Twenty bars sorted from largest to smallest: Digital, Cyber and AI 46; Hazards and Disaster Risk Reduction 41; Energy and Critical Infrastructure 29; Finance, Insurance and the Economy 29; Health and Biosecurity 28; Climate and Earth Systems 27; Governance, Security and Society 27; Open Infrastructure and Developers 25; Data and Evidence 16; Humanitarian Action and Development 12; Systemic Risks 12; Industry, Trade and Supply Chains 11; Water and Food Systems 10; Trust, Verification and Assurance 9; Communities, Learning and Contribution 8; Space and Earth Observation 5; Cities and the Built Environment 4; Early Warning and Anticipatory Action 4; Readiness and Adoption 4; Foundations and Governance 2.
| Subsite | Risk standards |
|---|---|
| Digital, Cyber and AI | 46 1 |
| Hazards and Disaster Risk Reduction | 41 1 |
| Energy and Critical Infrastructure | 29 1 |
| Finance, Insurance and the Economy | 29 1 |
| Health and Biosecurity | 28 1 |
| Climate and Earth Systems | 27 1 |
| Governance, Security and Society | 27 1 |
| Open Infrastructure and Developers | 25 1 |
| Data and Evidence | 16 1 |
| Humanitarian Action and Development | 12 1 |
| Systemic Risks | 12 1 |
| Industry, Trade and Supply Chains | 11 1 |
| Water and Food Systems | 10 1 |
| Trust, Verification and Assurance | 9 1 |
| Communities, Learning and Contribution | 8 1 |
| Space and Earth Observation | 5 1 |
| Cities and the Built Environment | 4 1 |
| Early Warning and Anticipatory Action | 4 1 |
| Readiness and Adoption | 4 1 |
| Foundations and Governance | 2 1 |
03What the catalogue contains
What the catalogue contains
The foundation standards set the common machinery: how an artefact is identified (NS-1 and NS-16), cited (NS-2), described (NS-3b), drafted (NS-4), drawn (NS-5), published (NS-8), bound to obligations (NS-10), verified and monitored (NS-11), how software and models are recorded (NS-12), how a standard is made (NS-13) and how conformance is mapped to external standards (NS-14). The standards catalogue of the documentation lists each with its UNI.
The Nexus Risk Standards apply that machinery by subject. Across the twenty subsites, the largest groups are Digital, Cyber and AI with 46, Hazards and Disaster Risk Reduction with 41, and Energy and Critical Infrastructure and Finance, Insurance and the Economy with 29 each; the smallest are Foundations and Governance with 2 and four subsites with 4 1. The counts show where the drafting effort has gone, not where the need is greatest or where any standard is mature. All of them are open for comment.
A practitioner who wants to know which of them bears on a given question can start from which standards apply, and resolve any identifier through the UNI catalogue and resolver.
Fig. 02One decider at each step
Figure 2 in words
Five stages left to right. Open: anyone may propose; a technical committee accepts the work item (DR-02). Community draft: the working group decides the content (DR-04) and editors dispose of comments (DR-05). Proposed: the technical committee moves the draft into review and sets the stage after last call (DR-06, DR-07). Candidate: the technical committee decides the candidate stage with the conformance panel consulted (DR-08). Adopted, highlighted: the Global Standards Council adopts after a 90-day last call by two thirds of all voting members, with two independent implementations and published test vectors (DR-09). Beneath: national adoption belongs to each National Standards Council (DR-20 to DR-25); an erratum has a fourteen-day last call.
04How a standard is made, and who decides each step
How a standard is made, and who decides each step
A standard moves along an open track: open, community draft, proposed, candidate and adopted 5. Each step has exactly one decider, set out in the decision rights of the programme: working groups decide the content of their drafts, editors dispose of comments, technical committees accept work items, move drafts into review and set the stage after last call, and the Global Standards Council adopts 3. How a standard is made on the standards site walks through the same path.
Adoption has two hard conditions. The Council adopts after a 90-day last call by two thirds of all voting members, with no unresolved national objection or a recorded override; and two independent implementations with published test vectors must exist first 3. Smaller changes move faster but in the open: an erratum is itself a proposal under NS-13, with a fourteen-day last call, and every comment receives a written disposition 4.
None of these bodies is constituted. The decision-rights matrix is a proposed working model, and until the Council ratifies it the Secretariat runs the open process 3. GCRI Canada, as Secretariat, maintains the records and publishes the standards; four Technical Management Divisions would coordinate thirteen technical committees 4. Anyone may comment and contribute without membership or fee, through develop a standard, under the Standards IP and Participation Policy.
05From a finding in the field to a change proposal
From a finding in the field to a change proposal
Standards are meant to learn from use. In the programme year, method and correction findings pass from the Reports platform to the standards as change proposals (handoff F06), docket items that need a standard or a profile pass from Nexus Universe (F07), and validation and monitoring evidence passes from the Foundry build (F13); composed mission profiles go back to the Foundry (F08), and each adopted standard becomes a Risk Academy module (F09) 5. The programme year places each handoff in its phase.
What travels is evidence, never a verdict. A validator report against a profile is evidence for review, not a conformance claim; no claim of certification, accreditation, approval or compliance is made without a decision of a competent authority 10. That is why the Nexus of Observatories labels every observation, and why a method tested in the Labs keeps an exploratory label until it has been rebuilt and tested.
Fig. 03The roadmap to a first release
Figure 3 in words
A Gantt chart with years 2026 to 2031 across the top and six bars. P0 Founding, October 2026 to March 2027, highlighted as the current phase: calls for experts, Council seats formed. P1 Proposals and first operational versions, January 2027 to June 2029. P2 Deliberation, last call and national discussion, July 2027 to December 2029, with a 90-day last call for every new standard. P3 Field simulations and exercises, September 2027 to June 2030. P4 Adoption decisions of the Global Standards Council, March 2028 to September 2030. P5 First release, October to December 2030, with DOIs, opened for national adoption. A marker shows 21 October 2026.
06The roadmap to a first release
The roadmap to a first release
The roadmap runs in six phases, each a target, not a commitment 2. P0, Founding, from October 2026 to March 2027, opens calls for experts and forms the Council's seats. P1, from January 2027 to June 2029, moves each standard from OPEN to a proposal with a first operational version, wave by wave. P2, from July 2027 to December 2029, holds open review and a 90-day last call for every new standard, with national discussion. P3, from September 2027 to June 2030, runs field simulations and exercises with host institutions. P4, from March 2028 to September 2030, holds the Council's adoption decisions; P5, from October to December 2030, releases the catalogue with DOIs and opens it for national adoption 2.
The phases overlap by design: a standard drafted early can reach last call while others are still being proposed. Before adoption, each first operational version is tested in practice through discussion-based and operations-based exercises in the working groups' own jurisdictions and industries, in coordination with competent national authorities where appropriate 2.
Fig. 04Four ways a country can use a standard
Figure 4 in words
Four cards in a row. Adopt as is: the national council adopts the published text. Adopt with a profile: adoption with a national application profile under NS-16. Adapt: the council adapts the standard to national law and practice. Reference only: the council refers to it without adopting it. Above, the National Standards Council is shown as the decider, the standards function of the National Nexus Consortium. Beneath, a highlighted bar: the Global Standards Council has no veto over a national decision; national law and language prevail.
07National adoption: four modes, and no global veto
National adoption: four modes, and no global veto
A standard adopted globally binds no one. In each country that takes part, a National Standards Council, the standards function of the National Nexus Consortium, decides whether to adopt a standard as is, adopt it with a national application profile under NS-16, adapt it to national law and practice, or refer to it without adopting it 10. "The GSC has no veto over a national decision"; national law and language prevail 4.
The rule follows the way disaster risk is governed. The Sendai Framework states that each State has the primary responsibility to prevent and reduce disaster risk 11. A method for assessing that risk can be shared; the decision to use it in law belongs to the State. The National Nexus page explains the national structures, and the companion page on public authority interfaces explains how a public authority engages without ceding its mandate.
08The principles for judging a standards body
The principles for judging a standards body
International trade law already says what a credible standards process looks like. In 2000 the WTO Committee on Technical Barriers to Trade agreed six principles for the development of international standards: transparency, openness, impartiality and consensus, effectiveness and relevance, coherence, and attention to the concerns of developing countries 12. The roadmap of the Nexus Standards includes a governance dossier against those principles in its first three phases 2. The dossier is planned work, and until it is published no claim of alignment is made.
The Internet's standards process offers the clearest precedent for implementation evidence. RFC 2026 required at least two independent and interoperable implementations from different code bases before a specification could advance 13; RFC 6410 reduced the track to two maturity levels and kept the rule of at least two independent interoperating implementations, confirmed after an IETF-wide last call of at least four weeks 14. The Nexus Standards ask for the same evidence before adoption, with a longer last call 3.
Fig. 05Read against established practice
Figure 5 in words
Two blocks. Upper block compares the IETF standards track (RFC 6410) with the proposed Nexus Standards process on three rows: implementation evidence (two independent interoperating implementations with widespread deployment, against two independent implementations with published test vectors); last call (IETF-wide, at least four weeks, against 90 days, fourteen days for an erratum); deciding body (IESG, against the Global Standards Council by two thirds). Lower block lists four of the WTO six principles with the recorded feature of the Nexus Standards that addresses each: transparency (every comment receives a written disposition), openness (participation without membership or fee), impartiality and consensus (one decider per decision; providers hold no vote), coherence (external standards cited and crosswalked under NS-14).
| Instrument | Issuer | What it sets | Status |
|---|---|---|---|
| Six Principles for international standards | WTO TBT Committee | Transparency, openness, impartiality and consensus, relevance, coherence, development 12 | Decision of 2000 |
| RFC 2026 and RFC 6410 | IETF | Independent interoperable implementations before advancement 13,14 | BCP 9, as updated 2011 |
| Global Digital Compact, paragraph 17 | UN Member States | Open standards and interoperability by 2030 6 | Adopted 22 September 2024 |
| European Interoperability Framework | European Commission | 47 recommendations, 12 principles 8 | In use |
| Interoperable Europe Act | European Union | Mandatory interoperability assessments in the public sector 15 | In force since 11 April 2024 |
| PROV-O | W3C | Provenance, profiled in NS-3b 16 | W3C Recommendation, 2013 |
09How the catalogue is counted
How the catalogue is counted
The figures on this page are those of the About page of the standards site, generated from the corpus on 17 October 2026: 19 foundation standards and 349 risk standards 1. Other pages of the same site give 348 risk standards, and the roadmap lists NS-0 to NS-16 with 348 2. The difference reflects pages generated from different builds of the corpus; the site's own index governs, and this page will follow it when it changes.
A count of standards is a count of drafts, not of capability. No standard has a first operational version on record, no implementation has been tested against one, and the service level of the programme as a whole is R0, information and enquiries 17.
10Liaison, licences and the open boundary
Liaison, licences and the open boundary
Work with other standards bodies is planned in a stated order: a W3C Community Group and Research Data Alliance working groups first; then OGC Associate membership and an OASIS Open Project; and ISO liaison through the Standards Council of Canada only once two Nexus Standards have been adopted with two independent implementations each 4. No liaison of any category is recorded today 4. External standards are named in text and cited, never reproduced.
The standards are open by licence as well as by process. Standards text, registries, schemas and data are published under CC BY 4.0, code under Apache-2.0, and contributions are made under the Developer Certificate of Origin with a royalty-free patent commitment 4. The adopt and implement page sets out how public material is distributed. The Nexus systems are separate infrastructure; no standard depends on them, and no provider holds a vote, chair or Secretariat role in the governance of the standards 10.
11What is changing
What is changing
- Evidence through transparency services. The roadmap's first wave revises NS-11 to register evidence through transparency services (IETF SCITT) with continuous verification 2.
- Cryptographic agility. NS-11 and NS-12 are to gain cryptographic agility, with a new standard on post-quantum migration 2.
- Data sovereignty and consent fields. NS-10 and NS-11 are to carry fields that record sovereignty and consent with the data they govern 2.
- Public-sector interoperability becomes law. The Interoperable Europe Act makes interoperability assessments mandatory for changes to European public digital services 15.
12Three faces of the standards
Three faces of the standards
GCRI stewards the evidence, methods, data and open research behind the standards, and GCRI Canada is Secretariat and publisher of record 5; its methods and technical papers are where methods are first set out. GRF convenes participation and keeps the public record of recognition and standing 5, including through its industry and standards constituency and its GRF standards and IPR policy. GRA makes the standards readable to finance and insurance 5, through the finance, insurance and capital markets standards and its own GRA standards and IPR policy.
What this page does not claim: every Nexus Standard is a proposal; none is adopted, and none of the governing bodies named is constituted. A UNI identifies and never certifies. A validator report is evidence for review, not a conformance claim, and no programme body certifies, accredits or approves anything. Adoption is final for each jurisdiction. The roadmap dates are targets. GCRI does not regulate or certify, GRF does not regulate, finance or procure, and GRA does not lend, underwrite, rate or invest. Naming an external standard or body is not a claim of liaison, alignment or endorsement.
Questions
Questions and answers
Are any of the Nexus Standards adopted?
No. Every foundation standard and every Nexus Risk Standard is at the PROPOSED stage, and the Global Standards Council that would adopt them is not yet constituted. The roadmap targets adoption decisions between 2028 and 2030.
Can a country be bound by a Nexus Standard it did not adopt?
No. A National Standards Council decides whether to adopt, profile, adapt or only reference a standard, national law and language prevail, and the Global Standards Council has no veto over a national decision.
Does a UNI or a validator report certify anything?
No. A UNI identifies and resolves an artefact; it never certifies truth, readiness, approval, legal compliance or production status. A validator report is evidence for review by the institution that reads it, not a conformance claim.
Who can contribute, and on what terms?
Anyone, without membership or fee. Comments and proposals go through the develop-a-standard route; text and data are licensed CC BY 4.0, code Apache-2.0, and contributions carry a Developer Certificate of Origin sign-off with a royalty-free patent commitment.
How is a standard proven before adoption?
By implementation evidence. Two independent implementations and published test vectors must exist, first operational versions are tested in field simulations and exercises, and the Council adopts only after a 90-day last call by two thirds of its voting members.
Terms
Glossary
- Foundation standard
- One of the NS-0 to NS-16 standards that set how artefacts are identified, described, verified and cited.
- Nexus Risk Standard (NRS)
- A standard that applies the foundation standards to a subject, such as a hazard family, a system or a sector.
- UNI
- The identifier the catalogue gives an artefact; it identifies and resolves, and never certifies.
- Last call
- The final public review period before a decision; 90 days for a new standard, fourteen days for an erratum.
- National application profile
- The national adaptation of a standard under NS-16, maintained by a National Standards Council.
- Global Standards Council
- The proposed governing body that would adopt each standard after last call and implementation evidence.
Reuse and cite
Text CC BY 4.0. Cite the page with its date; data tables are linked under each figure.
Sources
References
17 sources, numbered in the order they are first cited
- Nexus Standards (2026-10-17). About the Nexus Standards. nexustandards.com. Accessed 2026-10-21.
- Nexus Standards (2026-10). Roadmap. nexustandards.com. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). Decision rights. docs.therisk.global. Accessed 2026-10-21.
- Nexus Standards (2026-10). Governance of the Nexus Standards. nexustandards.com. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). Nexus Standards, the pillar. docs.therisk.global. Accessed 2026-10-21.
- United Nations (2024-09-22). Global Digital Compact. www.un.org. Accessed 2026-10-21.
- United Nations General Assembly (2024-09-22). Pact for the Future (A/RES/79/1). www.un.org. Accessed 2026-10-21.
- European Commission, Interoperable Europe (2025). The European Interoperability Framework in detail. interoperable-europe.ec.europa.eu. Accessed 2026-10-21.
- UNESCO General Conference (2021-11-23). Recommendation on Open Science. www.unesco.org. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). Nexus Standards (institutional reference). docs.therisk.global. Accessed 2026-10-21.
- United Nations General Assembly (2015-06-03). Sendai Framework for Disaster Risk Reduction 2015–2030 (A/RES/69/283). docs.un.org. Accessed 2026-10-21.
- World Trade Organization, TBT Committee (2000). Principles for the Development of International Standards, Guides and Recommendations. www.wto.org. Accessed 2026-10-21.
- Internet Engineering Task Force (IETF) (1996-10). RFC 2026: The Internet Standards Process, Revision 3. www.rfc-editor.org. Accessed 2026-10-21.
- Internet Engineering Task Force (IETF) (2011-10). RFC 6410: Reducing the Standards Track to Two Maturity Levels. www.rfc-editor.org. Accessed 2026-10-21.
- European Commission, Interoperable Europe (2024-04-11). Interoperable Europe Act. interoperable-europe.ec.europa.eu. Accessed 2026-10-21.
- World Wide Web Consortium (W3C) (2013-04-30). PROV-O: The PROV Ontology. www.w3.org. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). Status and service levels. docs.therisk.global. Accessed 2026-10-21.
Record
Editorial record
Facts and statuses are given as of 21 October 2026. This page is reviewed at least every 120 days and whenever a standard changes stage, a body is constituted or the roadmap changes. It replaces an earlier version that described the Nexus Standards as a general standards interface without bodies, stages, deciders or a roadmap; those are now on record and the page follows them.
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.
Cite this article
GCRI editorial desk (2026, June 8). Nexus Standards: from technical evidence to open methods. The Global Centre for Risk and Innovation. https://therisk.global/nexus-standards-turning-technical-evidence-into-repeatable-methods-for-systemic-risk-readiness/
@online{gcri2026nexusstandardsturning,
author = {{GCRI editorial desk}},
title = {{Nexus Standards: from technical evidence to open methods}},
publisher = {The Global Centre for Risk and Innovation},
year = {2026},
month = {6},
url = {https://therisk.global/nexus-standards-turning-technical-evidence-into-repeatable-methods-for-systemic-risk-readiness/},
language = {en}
} TY - ELEC AU - GCRI editorial desk TI - Nexus Standards: from technical evidence to open methods PB - The Global Centre for Risk and Innovation PY - 2026 DA - 2026/06/08 UR - https://therisk.global/nexus-standards-turning-technical-evidence-into-repeatable-methods-for-systemic-risk-readiness/ 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>Nexus Standards: how technical evidence becomes an open, correctable method — GCRI editorial desk, The Global Centre for Risk and Innovation. First published 8 June 2026 at <a href="https://therisk.global/nexus-standards-turning-technical-evidence-into-repeatable-methods-for-systemic-risk-readiness/">https://therisk.global/nexus-standards-turning-technical-evidence-into-repeatable-methods-for-systemic-risk-readiness/</a>. Republished under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).</p>