M01 · foundationsProposed
Foundations and Governance
Every area rests on the same few commitments: a single identifier that identifies an artefact without certifying it.
Standards · Open standards for systemic risk
Proposed · open for review and comment
Open, machine-readable standards that help institutions identify, describe, verify and cite risk information across sectors and borders. They connect existing international standards rather than replace them. A validator report is evidence for review, not a conformance claim.
Risk information crosses sectors and borders. One open, machine-readable set of rules lets every institution identify, describe, verify and cite it the same way, and connects the international standards already in use instead of replacing them.
Counts from the Nexus Standards registry (standards index pinned 2026-10-21; external standards and bodies from the catalogue’s crosswalk register). Every standard is proposed until the Global Standards Council adopts it; licence CC BY 4.0.
The risk standards and their crosswalks in 3D, and where the bodies behind the 253 external standards sit, region by region; the globe of the 169 issuing bodies opens the page.
Each ring is a series. Drag to turn the figure. Select a standard to see its crosswalks and dependencies.
FIG. 1 · The risk standards by series, with their crosswalks to external standards and their dependencies. Source: the Standards registry.
Three ways in: the foundation standards every area rests on, the risk standards by series, and the programmes that group the areas by field.
Foundations and trust4 programmes · 39 areas.
M01 · foundationsProposed
Every area rests on the same few commitments: a single identifier that identifies an artefact without certifying it.
M16 · capabilityProposed
Every claim in the ecosystem is only as reliable as the record behind it.
M17 · capabilityProposed
Assurance in this programme means evidence that any party can check: who evaluated what, against which clause, with which result and when.
M18 · infrastructureProposed
Standards are used through registries, resolvers, APIs, deployments and monitors.
Earth and living systems6 programmes · 36 areas.
M02 · domainProposed
Climate, atmosphere, oceans, land and biodiversity are one coupled system: heat, water and carbon move between them.
M03 · domainProposed
Water allocation, crop production and food access fail together: a drought shows first in a basin, then in a harvest.
M05 · domainProposed
Human, animal and environmental health share pathogens, data systems and surge capacity, so an outbreak is also a logistics.
M04 · domainProposed
Power, fuel, telecommunications, water and transport are interdependent networks.
M06 · domainProposed
Cities concentrate exposure: people, buildings and networks share the same streets, codes and service footprints.
M15 · sectorProposed
Satellites observe every other system and depend on a space environment that can itself fail.
Hazards and warning3 programmes · 18 areas.
M07 · hazardProposed
Hazards rarely arrive alone: an earthquake triggers landslides, a cyclone a flood, a heatwave a wildfire and a power failure.
M08 · hazardProposed
A warning helps only if it reaches people with time to act and if the action it triggers was agreed in advance.
M14 · disciplineProposed
Some risks live in the connections between systems, or on horizons beyond any budget cycle.
Economy and society5 programmes · 48 areas.
M09 · sectorProposed
Risk becomes financial when it is priced, insured, lent against or disclosed, and it becomes systemic when those positions move together.
M10 · sectorProposed
Production and trade run on long chains of suppliers, carriers and chokepoints; a disruption at one node reaches firms that never knew it existed.
M11 · sectorProposed
Digital systems, cyber threats and AI models now sit inside the records and decisions of every other system.
M12 · hazardProposed
Institutions, conflict, information integrity and public trust determine whether any other risk can be managed.
M13 · multilateralProposed
Humanitarian response and development planning serve the same people and places at different horizons.
Adoption and community2 programmes · 22 areas.
M19 · readinessProposed
Adoption is a process rather than a designation: an institution, a country or a chapter determines what evidence it requires and assesses it under.
M20 · communityProposed
Standards remain current through the people who draft, review, teach and translate them.
Select a scenario and press Play: how the catalogue is built, how an identifier is allocated and resolved, how a standard moves from open to adopted, how conformance is verified, how external standards are related, who decides, how a release is published and how to take part. Design, not a register.
Standards · codify and correct
Standard lifecycle · NS-11 lifecycle · NS-1 lifecycle · NS-2 lifecycle · NS-13 track · Contribution channels · IETF track · W3C track · OGC track · OASIS track · ISO and IEC stages · Conformance · Record lifecycle · Routing · Monitoring.
Cycle findings become change proposals, the Global Standards Council adopts after a public last call, and each country decides its own adoption.
Nexus Standards · Nexus Standards (institution) · National Standards CouncilAn outline of the designed programme cycle, not a record of operation: no cycle has run and every programme is at service level R0. Every Nexus Standard is at the PROPOSED stage and nexustandards.com governs the text and status of each one. A UNI identifies and never certifies; a validator report is evidence for review, not a conformance claim.
The registers first; the programme’s role, the full set, the principles, the crosswalk graph, the licence, readiness, implementations and the source files one tab away.
The foundation standards set the shared rules. The risk standards apply them to a field of risk. None is adopted yet: every document is a proposed draft, open for review and comment.
| Series | Scope | Standards |
|---|---|---|
| NRS-C | Risk coreShared by every other series: vocabulary, method, data, evidence, models, clauses. | 16 |
| NRS-N | Anchor nexus streamsWater, energy, food, health, biodiversity and infrastructure, and the nexus that couples them. | 7 |
| NRS-T | Exponential technologyThe risk of each technology and the assurance of its use in risk work. | 18 |
| NRS-F | Finance and insuranceHow risk enters, moves through and is transferred by the financial system. | 9 |
| NRS-P | Policy and governanceRisk in policy, regulation, public registers, institutions, foresight, rights and procurement. | 11 |
| NRS-D | Development, society and humanitarian actionRisk-informed development, inclusion, humanitarian response, livelihoods. | 10 |
| NRS-X | Cross-cutting domainsClimate, disasters, oceans, supply chains, cities, cyber, information integrity and continuity. | 12 |
| NRS-I | Risk intelligence, evidence and communicationIntelligence products and modalities, communication, model and data cards. | 7 |
| NRS-E | Programme and institutionalUniverse, Reports, Academy, campaigns, participation, national adoption. | 8 |
| NRS-S | System implementation profilesOne profile per functional system class of a risk information ecosystem. | 21 |
| NRS-H | Hazard family standards (NHS-1)One standard per family of the Nexus Hazard Standard NHS-1. | 120 |
| NRS-M | Risk method fabrics (Risk Master)One standard per fabric of the Risk Master, covering its capabilities, bindings, models. | 23 |
| NRS-U | Universe platform profilesOne profile per Universe platform (stewarded by the Global Risks Forum (GRF)), naming the standards, hazards. | 27 |
| NRS-K | Applied domain pack profilesThe standards profile and risk profile every Universe applied domain pack requires. | 50 |
| NRS-A | AI-native, ontology-native standards infrastructureStandards as code and as an ontology, the agent interface, zero-trust verification. | 9 |
Much of systemic-risk practice is already addressed by external standards. A Nexus Standard complements them: it adopts, profiles and crosswalks them for the systemic-risk nexus, assigns each artefact an identifier, expresses obligations as machine-readable clauses, evaluates conformance from evidence and directs the reader to the issuing body. Where no external standard addresses a nexus concern, a Nexus Standard specifies it (NS-0, section 2).
An artefact records each external standard to which it relates, by identifier and URL, with the relation given in the register, under NS-14.
Obligations are expressed as machine-readable clauses and policies under NS-10.
Conformance is evaluated continuously from evidence and recorded as attestations with named evaluators, under NS-11.
Proposals, comments, decisions and versions are identified artefacts under the NS-13 process; participation requires no membership fee.
Licences: CC BY 4.0 (standards text, registries, schemas, data); Apache-2.0 (reference code).
Applying the standards makes artefacts readable as evidence by three institutional readiness pathways. Each institution decides under its own rules.
What a project, dataset or model must carry to be admissible evidence in the GCRI Canada research and intelligence pipelines. Open the pathway.
What an institution, programme or deployment must evidence for GRF recognition records; records, not reputation. Open the pathway.
What a project or portfolio must evidence for capital-readiness assessment; never investment advice or endorsement. Open the pathway.
Implementation status as recorded in the registry: in progress means the integration exists and is under test; planned means it is specified but not yet built.
| Implementation | Role | Standards and status |
|---|
Entry points by community, then how the twenty programmes connect, the programme cards and the six pillars.
Six entry points present, for each community of practice, the standards, programme areas, tools and readiness pathways most relevant to its work, as selected from the registry.
Frameworks, disclosure, governance and the standards that express obligations in machine-readable form.
ForData, models, Earth observation, provenance and the identifiers that make research citable.
ForDisclosure, prudential and climate-risk standards, and the records read by the capital readiness pathway.
ForEarly warning, disaster risk, humanitarian data and the alerting standards adopted in the Nexus Standards.
ForThe UNI (Unique Nexus Identifier) grammar, the record schema, the reference command-line tool, exports and the WordPress integration.
ForFor the communities of the Global Centre for Risk and Innovation (GCRI Canada and GCRI US), The Global Risks Forum (GRF) and The Global Risks Alliance (GRA): what each institution’s pathway reads from the standards, and where the three sites already publish on each area.
The development stages, open calls and contribution routes, how to use the standards, who decides, the latest changes, learning at Risk Academy, the institutions of the network and common questions.
A standard moves through 6 stages in the open under NS-13. Each stage has an entry condition and a body that decides. Adoption is a decision of the Global Standards Council and, in each country, of its National Standards Council.
| Stage | To enter the stage | Who decides |
|---|---|---|
| OPEN | Area named in the registry | Anyone may propose the area |
| COMMUNITY DRAFT | A chartered working group with chairs, scope, exclusions, deliverables, meeting cadence and decision rule | The working group, by consensus |
| PROPOSED | Working-group consensus recorded; the four horizontal reviews completed; crosswalk entries complete with source links. | The editors, after public last call |
| CANDIDATE | Two independent implementations pass the test suite; all comments dispositioned | The technical committee, on implementation evidence |
| ADOPTED | Adoption by the Global Standards Council recorded under GOVERNANCE.md, with the reference cited in the front matter | The Global Standards Council |
| SUPERSEDED or WITHDRAWN | A later edition or a withdrawal decision | The Global Standards Council |
The standards are free to use. They connect the international standards you already apply rather than replace them.
Repository structure, national adoption modes, citation and attribution. Adopt and implement.
Route a sector, hazard or system to the standards and clauses that apply, with reasons. Which standards apply.
Record how each requirement relates to an external standard, by identifier and link. NS-14 conformance and crosswalk.
Give each artefact a UNI (Unique Nexus Identifier) and resolve it to its record. A UNI identifies; it does not certify. The UNI resolver.
Start by communityPolicySTEM communitiesFinance and insuranceHumanitarian and public sectorDevelopersInstitutional communities.
Reports is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
The Index is the Consortium’s indexing system for risk data. Every indicator, hazard, series and country profile carries its Nexus Standards identifier, its source and its licence, so what this page shows can be traced, corrected and reused.
global, sector, strategic, technology, thematichazards, climate, conflictEvery country profile carries the source and licence of each value. Correct a value or reply.
Open layers on an equal-area hexagon grid, shown as densities per km² or as symbols: People · GHSL 2025People · WorldPop 2025Built-up areaPortsAirportsRoadsRailwaysRivers and lake centrelines.
/api/v1/public/grix · https://nexustandards.com/uni/{uni}
Developers · Data · Made with Natural Earth, Public domain; GHSL and WorldPop, CC BY 4.0.
Snapshot of the Index registries pinned 2026-10-23 · 22c6eed. Research and risk-analytics information: not a rating, an official classification, a warning, a benchmark or advice.
Governments, regulators, standards bodies, industry, academia and communities are invited to comment on drafts and propose new work.
Status and use. The Nexus Standards are proposed standards developed through an open process under NS-13 and published for voluntary use; they do not constitute certification, accreditation or regulatory approval, and adoption remains a decision of the Global Standards Council and, in each country, of its National Standards Council. A UNI (Unique Nexus Identifier) identifies an artefact; it does not certify it. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.
Licences: CC BY 4.0 for standards text, registries, schemas and data; Apache-2.0 for reference code. External standards are cited by name, number and link under their own licences. Third-party data, libraries and fonts keep their own licences: see Third-party notices.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information. We run no advertising. You can review your choices at any time through Privacy choices at the foot of every page.