NS-0: Constitution and principles

01Overview

Summary

NS-0record

Statusproposed
Responsible scopetrust, authorization and assurance
IdentifierNXS-STD-ST-000004
Rules stated12
Programme areas55
Documentstandards/NS-0-constitution-and-principles.md
Source filesrepository

Nexus Standards · proposed

02Status

Status of NS-0

Preparatory working draft, circulated for review and comment. Not for implementation. Prepared and circulated by The Secretariat of the Nexus Standards, Global Centre for Risk and Innovation (GCRI Canada) (public@therisk.global), 17 October 2026. Technical review area: TR-01. This document is not a Nexus Standard; it may change without notice and is not to be implemented, relied upon or cited as a Nexus Standard. Its stage is designated only by the Global Standards Council and its technical committees under NS-13. Recipients are invited to submit comments with supporting reasons, and to notify any patent rights of which they are aware. See the notice of circulation.

03Earth observation

Population, settlement and hazards worldwide

The map is framed on the world as context for the subject of NS-0. Shown at first: population density, 2020 (Gridded Population of the World v4.11, NASA SEDAC, CIESIN, Columbia University) and night-time lights, daily (VIIRS Black Marble, VNP46A2, NASA LAADS DAAC). The layer drawer adds flood water, 3-day composite (VIIRS Global Flood Product); active fires and thermal anomalies, last day (VIIRS NOAA-20 375 m, FIRMS); and true colour (VIIRS NOAA-20 corrected reflectance). NASA products are served through NASA GIBS under NASA's open data policy, with acknowledgement; population density is GPW v4.11 by CIESIN, Columbia University, under CC BY 4.0; coastlines, boundaries and place names come from NASA GIBS reference layers (© OpenStreetMap contributors, ODbL) and Natural Earth (public domain). Each layer shows its own observation date; full credits are given under the map.

The interactive map needs JavaScript; the layer list and sources are below.

Layers 2

People and hazards

Latest available

NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © OpenStreetMap contributors (ODbL) · Natural Earth

Loading the latest NASA imagery.

Drag to move. Ctrl or ⌘ and scroll, pinch or the buttons to zoom; hover for the values under the pointer; reset returns to the region.

Where people live, night-time lights and the floods and fires public institutions answer to, framed on World.Satellite and model products as NASA publishes them, each with its own date; indicators, not assessments of any place.

Data: NASA GIBS · ASTER GDEM · Blue Marble · © OpenStreetMap contributors · Natural Earth · NASA EONETSources and licences

We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
Center for International Earth Science Information Network (CIESIN), Columbia University. 2018. Gridded Population of the World, Version 4 (GPWv4): Population Density, Revision 11. NASA Socioeconomic Data and Applications Center (SEDAC). Licensed under CC BY 4.0. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). doi:10.7927/H49C6VHW. CC BY 4.0
VIIRS Black Marble night-time lights, NASA Goddard Space Flight Center; distributed by the NASA Level-1 and Atmosphere Archive and Distribution System (LAADS DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
VIIRS near-real-time products (flood, land surface temperature, snow cover, corrected reflectance), NASA LANCE; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
NASA Fire Information for Resource Management System (FIRMS), VIIRS 375 m active fire product, NASA LANCE; vector tiles via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
ASTER GDEM is a product of METI and NASA (ASTER Global Digital Elevation Model V003, NASA LP DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). Cite as: NASA/METI/AIST/Japan Spacesystems and U.S./Japan ASTER Science Team (2019). ASTER Global Digital Elevation Model V003. doi:10.5067/ASTER/ASTGTM.003. NASA open data
Made with Natural Earth. Free vector and raster map data @ naturalearthdata.com. Public domain
© OpenStreetMap contributors (ODbL), via NASA GIBS (coastlines, boundaries, roads and place names). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). ODbL
Blue Marble, NASA Earth Observatory; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
Context on the globe and flat map: coastlines, boundaries, roads and place names from NASA GIBS reference layers (OpenStreetMap data, ODbL, © OpenStreetMap contributors); Blue Marble imagery as an optional base; 3D terrain and the elevation read-out from the ASTER GDEM elevation colour index (5 m to 200 m classes, exaggerated for legibility). Boundaries are drawn as published and imply no position on any territory.
Globe: MapLibre GL JS 6.9.1, BSD-3-Clause, © MapLibre contributors.
Live: NASA EONET Events are indicative, not authority warnings.
NASA GIBS: We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS).
Optional layers (3 sources in the layer list: live, forecast, observed and context) print their provider credit on the map and here when switched on; forecasts are model output and derived indices are estimates.

Layers and dates

Population density, 2020: Population: CIESIN, Columbia University, Gridded Population of the World v4.11 (2018), NASA SEDAC, CC BY 4.0 · static
Night-time lights, daily: VIIRS Black Marble (VNP46A2), NASA LAADS DAAC · 12 Oct 2026
Flood water, 3-day composite: VIIRS Global Flood Product, NASA LANCE · 14 Oct 2026
Active fires and thermal anomalies, last day: VIIRS NOAA-20 375 m (FIRMS), NASA LANCE FIRMS · 13 Oct 2026
True colour: VIIRS NOAA-20 corrected reflectance, NASA LANCE · 13 Oct 2026

04Canvas

NS-0 among the standards.

Canvas · NS-0 among the standardsProcess diagram

Fig.The standards on which NS-0 builds, those that cite it and the programme areas where it applies, from the texts and the registry.

05Process

The standard as a process

A consumer names the canonical repository and the versions it applies, uses the registries without forking them, runs the validator, resolves any conflict by the order of precedence, records its implementation status, carries the status fields on every record and submits its statement to verification under NS-11. 8 operations in 4 phases; each states its actor, its decision rule, the record it leaves and the rule identifiers it implements (11 rules of NS-0 and the standards it applies). Records and artifacts are cited by UNI (Unique Nexus Identifier) and version.

Process · Applying NS-0: from a consumer's declaration to a verifiable conformance statement8 operations · 4 phases

All operations in order (8)

01
Name the repository start · Declaration
The consumer states which repository it follows and which edition of each Nexus Standard it applies. Standards, registries, schemas and reference tools are published openly under recorded licences.
Who
the consumer (a system, site or institution applying the standards)
Decision rule
the consumer names the canonical repository and each standard's version (section 6, item 1)
Record
a declaration of the canonical repository and of the versions applied
Implements
NS0-P1, NS0-P2
02
Use, never fork step · Declaration
Registries are copied with their digests and read as data. Data governs and prose explains, so a local change to a registry is a proposal under NS-13, not an edit.
Who
the consumer
Decision rule
a registry is used as published and never forked (section 6, item 2)
Record
a vendored copy of the registries with its digest
Implements
NS0-P2, NS0-P10
03
Run the validator exercise · Validation
The repository validator checks identifiers, codes and records against the registries and schemas. A failing check is recorded with its reason.
Who
the consumer, with the repository validator or a tool that runs the same checks
Decision rule
the validator runs on every vendored copy (section 6, item 3)
Record
a validator run with the tool version and the time
Implements
NS0-P4, NS0-P12
04
Order of precedence decision · Validation
Where a standard conflicts with law, contract or the consumer's constitution, the conflict is recorded as a blocking record with a typed reason; it is never resolved silently in code.
Who
the consumer's legal function
Decision rule
mandatory law and executed contracts, then the consumer's legal and IP constitution, then NS-0, then the other Nexus Standards, then local directives (section 5)
Record
a blocking conflict record where a conflict exists
Implements
NS0-P12
05
Record the status record · Publication
Each standard the consumer applies is listed with its implementation status; a planned implementation reads as planned.
Who
the consumer
Decision rule
implementation status is recorded per standard as it is (section 6, item 4)
Record
an entry per standard in the consumers register
Implements
NS0-P8, NS0-P11
06
Carry status fields step · Publication
Each record states what it was derived from, who produced it, under which release and decision, and which corrections apply. A UNI identifies and resolves; it never certifies.
Who
the consumer, on every published record
Decision rule
every published record carries its status fields and provenance (section 6, item 5)
Record
records that carry their legal state, claim level and provenance
Implements
NS0-P3, NS0-P7, NS0-P8
07
Independent check gate · Verification
The consumer's statement is checked against evidence by an evaluator that is not the consumer. Missing evidence, legal state or policy decision yields a typed refusal.
Who
an evaluator with a mandate, outside the consumer's trust boundary
Decision rule
authenticated is not authorized; deny by default; missing evidence is a refusal, never a pass
Record
attestations per clause, with evidence and digests
Implements
NS0-P4, NS0-P5, NS0-P12
08
Consumer statement end · Verification
Conformance to NS-0 is the consumer's own statement, supported by attestations that anyone can check.
Who
the consumer
Decision rule
a statement by the consumer, verifiable under NS-11; it is not a certification
Record
a statement of conformance to NS-0, verifiable under NS-11
Implements
NS0-P4, NS0-P6

Fig.Phases read left to right; each card names the operation, its actor and the record it leaves, and each edge label names the hand-over. Play, step or scrub; the detail panel gives the full text of the selected operation. Sources: NS-0: Constitution and principles.

06Specification

NS-0 clause by clause

6 clauses and 12 rules as stated in the standard, presented with numbered clauses, stable rule anchors, versions and changes.

Versions0.1.016 October 2026current versionchangelog0.6.0 (2026-10-19), complete release

1

Purpose

The Nexus Standards are universal open standards for all areas of risk. They are the shared, machine-readable rules by which any person, institution, implementation or agent identifies, describes, verifies, monitors and cites what it produces: systems, data, software, documents, visualizations, maps, models, policies, clauses, services and sites. They apply in every sector, hazard, domain, region and jurisdiction, in every language and on every technology platform. They exist so that one artifact means the same thing to a person, a machine, a regulator, a researcher and a community anywhere, and so that conformance can be observed rather than asserted.

The Nexus Standards are implementation-neutral. They specify behaviour at interfaces and the content of records. They do not require any particular product, programming language, database, cloud provider, account or mark, and conformance is determined in the same way for every implementation, open or proprietary.

2

The nexus of standards

Established standards already cover most of the concerns of risk practice: enterprise risk, continuity, security, zero trust, supply chain, climate and nature disclosure, disaster risk and early warning, financial prudence, geospatial data, provenance, identifiers and software supply chains (the landscape is recorded in research/STANDARDS_LANDSCAPE.md and registry/external-standards.yaml). Many are closed to participation, change slowly, are published as static documents and are assessed for conformance only by periodic audit.

A Nexus Standard does not replace them. It is the nexus: the layer that (a) crosswalks an artifact to every external standard it satisfies or relates to, (b) expresses the obligations of those standards as machine-readable clauses, (c) verifies conformance continuously from evidence instead of periodically from attestation, and (d) lets every stakeholder take part in developing the standard itself. Where no external standard exists for a cross-cutting concern (cross-domain cascades, real-time verification, open participation, provenance across the whole lifecycle), a Nexus Standard specifies it.

A Nexus Standard does not reproduce the copyrighted text of another body's standard; it cites by identifier, version and URL (NS-14). The names of standards bodies and their standards are their marks and are used only to refer to them.

3

Principles (binding)

Id	Principle	What it requires
NS0-P1	Open	The standards, their registries, schemas, catalogs and reference tools are published in the canonical repository under the licences recorded in `LICENSING.md`. Participation in development is open to every community and stakeholder under `GOVERNANCE.md`. No standard depends on a proprietary artifact, product, account or mark to be applied.
NS0-P2	Machine-readable first	Every normative element exists as data (registry, schema, clause) before it exists as prose; prose explains, data governs. A standard with no machine form is not a Nexus Standard.
NS0-P3	Identified	Every artifact, record, deployment, policy and clause carries a UNI (NS-1, NS-3, NS-9). Nothing is cited by a name alone.
NS0-P4	Verified, not asserted	Conformance is a claim with evidence: receipts, digests, signed attestations and observations (NS-11). A claim without evidence is recorded as a claim, never as a fact, and the claim ceiling of the implementation bounds every statement it makes.
NS0-P5	Zero trust	Authenticated is not authorized; entitled is not authorized; access is denied by default. Every verification, monitoring and enforcement path assumes no implicit trust between systems, tenants, sites or agents, and records who verified what under which mandate.
NS0-P6	Real-time	Standards express obligations that can be evaluated continuously against live records (observations, releases, corrections, deployments), and the standards themselves are versioned so that an implementation can state exactly which version it conforms to at any instant.
NS0-P7	Provenance everywhere	Every artifact records what it was derived from, who produced it, under which release and policy decision, and what corrected it (NS-3b, PROV-O profile). Corrections supersede; nothing is silently rewritten.
NS0-P8	Honest	A UNI identifies and resolves; it never certifies. `legalState` defaults to review-required. Readiness, approval and production status are never implied by a standard, a status, a page, a score or a badge.
NS0-P9	Nexus-aware	Standards address cross-domain interdependence (water, energy, food, health, biodiversity, climate and the sectors they touch) explicitly: an obligation can reference artifacts in another domain, and cascades are first-class.
NS0-P10	Names are governed	Codes are never names. Public names follow the marks policy (`governance/OPEN_BOUNDARY_IPR_AND_LICENSING.md`, section 7). A system or component is shown by its neutral display name and its UNI; the UNI may change with context (NS-9), and no name infringes anyone's mark.
NS0-P11	Community-owned development	Proposals, comments, decisions and versions of every standard are themselves artifacts with UNIs. The development process is specified (NS-13) and open, and authority to adopt is recorded, never assumed.
NS0-P12	Fail closed	Missing evidence, a missing legal state, a missing policy decision or unavailable verification results in a refusal with a typed reason, never in a pass.

4

The standard set

Id	Standard	Governs
NS-0	Constitution and principles	This document
NS-1	The UNI and the artifact catalog	Identification and cataloguing of artifacts; embedding (NS-6) and resolution (NS-7)
NS-2	Citation and attribution	How a UNI is cited by people and machines
NS-3	Risk record UNIs	Identification of risk records (observations, source releases, indicators, measures, boundaries, chronotopes, corrections, analytical products, subjects)
NS-3b	Dataset and product metadata profile	STAC, DCAT and PROV-O crosswalks
NS-4	Structure and drafting	Structure, verbal forms and registered requirements of standards; front matter of documents
NS-5	Figure, map and visualization	Visual artifacts, maps and GIS products, with their captions, provenance and accessibility
NS-6	Surface wiring	How APIs, panels, passports and pages carry UNIs (specified in NS-1 section 6 and NS-16)
NS-7	Resolver	Landing pages, meta tags and sitemaps (specified in NS-1 section 1 and NS-16 section 6)
NS-8	Publication workflow	Zenodo and DOI publication with the legal gate
NS-9	Contextual UNIs	Deployments and instances: a system in a region, domain, sector or jurisdiction
NS-10	Policies and clauses	Machine-readable policy and clause artifacts: their obligations, binding, evaluation and enforcement
NS-11	Verification and monitoring	Evidence, attestations, conformance observation and reporting; zero-trust verification services
NS-12	Software, model and AI/ML artifacts	Software supply chain, model cards, dataset sheets and AI governance crosswalks
NS-13	Standards development process	How standards are proposed, reviewed, versioned and adopted in the open
NS-14	Conformance and crosswalk to external standards	How an artifact claims and evidences its relation to external standards
NS-15	System model binding	How subjects, passports, chronotopes, relationships, risk routes, engines and agents are identified and bound to the standards
NS-16	UNI application profile	How articles, documents, code, data, APIs and interfaces carry the UNI and the context name

standards/INDEX.md carries the current status of every document.

5

Precedence

Mandatory law and executed contracts take precedence over the legal and intellectual property instruments of the implementing institution, which take precedence over NS-0, which takes precedence over the other Nexus Standards, which take precedence over the implementing institution's own internal policies. An implementation shall record a conflict between these levels as a blocking record with a typed reason; it shall not resolve the conflict in code.

6

Conformance to NS-0

An implementation conforms to NS-0 when it:

names the canonical repository and the versions of the standards it applies;
does not fork a registry;
runs the repository validator, or an equivalent, on the copies of the registries it uses;
records its implementation status per standard in registry/consumers.yaml truthfully; and
carries the honesty fields (legalState, claimCeiling, status) on every record it publishes.

Conformance to NS-0 is a statement by the implementation, verifiable under NS-11. It is not a certification by the Secretariat or by the Global Standards Council.

Δ

Changes between versions

One published version is available (0.1.0); a comparison between versions is shown once a second version is published.

Clause numbers follow the sections of the document; rule identifiers (NS0-P1, NS0-P2, NS0-P3…) are stable anchors. With script enabled, each clause and rule has a permalink and a machine-readable view (YAML and JSON), and the j and k keys move between clauses.

07Where it applies

Programme areas that list NS-0

55 programme areas list NS-0.

08Research hub

Recent research on NS-0

Recent peer-reviewed articles, preprints, datasets and reports on the subject of this standard, retrieved at the time of reading from open scholarly metadata services (OpenAlex, Crossref, DataCite, Zenodo, arXiv, Europe PMC, OpenAIRE Graph) with search terms composed from the registry. Each work is listed with its authors, venue, year, type, open-access status and licence, and links to its DOI or landing page. Sources not yet enabled for live display on this site are listed for reference and are not queried.

Search termsopen standards; FAIR principles; open science; standards governance; open data principles; Open Definition; The Open Source Definitioncombined with: governance; risk; data; interoperabilityDerived from the subject of the standard and its rules, and the external standards of its crosswalk domains.

OpenAlexlisted for reference; not queried
Crossreflisted for reference; not queried
DataCitelisted for reference; not queried
Zenodolisted for reference; not queried
arXivlisted for reference; not queried
Europe PMClisted for reference; not queried
OpenAIRE Graphlisted for reference; not queried

No source is enabled for live display on this site yet: the sources are listed for reference and none is queried. Once the publisher of record enables a source after its terms are reviewed, recent works are listed here. Metadata and links only: title, authors, venue, year, type, open-access status and licence as each source records them; works are listed for orientation, not reviewed or endorsed.

09Source

NS-0 in the standards repository

The text, schemas, machine-readable files, registry rows, tests and history behind NS-0, on the main branch of the canonical repository. Text, registry, schemas and catalog are CC BY 4.0; tools and tests are Apache-2.0.

Source text

File	What it holds	Links
`standards/NS-0-constitution-and-principles.md`	NXS-STD-ST-000004	Raw · History · Suggest an edit
`standards/INDEX.md`	status and document of every standard	History

Schemas

File	What it holds	Links
`schemas/nexus-clause.v1.json`	Nexus clause (NS-10)	Raw

Machine-readable files

File	What it holds	Links
`catalog/artifact-catalog.yaml`	catalog records · 2 mentions	First mention, line 255

Registry rows

File	What it holds	Links
`registry/subsites.yaml`	Nexus Standards subsites - the systemic architecture of nexustandards.com · 37 rows or mentions	Line 19
`registry/governance.yaml`	Governance, legal structure, national adoption, open boundary and disclaimers of the Nexus Standards · 2 rows or mentions	Line 9
`registry/review-investigations.yaml`	Circulation for technical review and comment, and the technical review areas · 2 rows or mentions	Line 48
`registry/dags.yaml`	Process and pipeline graphs rendered by the site's DAG component (nxs-dag) · 1 row or mentions	Line 38
`registry/risk-standards.source.yaml`	'Nexus Risk Standards: the systemic catalogue' · 1 row or mentions	Line 22
`registry/risk-standards.yaml`	'Nexus Risk Standards: the systemic catalogue' · 1 row or mentions	Line 21
`registry/standard-packages.yaml`	Standard packages - one package per external open standard on nexustandards.com · 1 row or mentions	Line 69

Tests and validators

File	What it holds	Links
`tools/build-risk-standards.mjs`	tool or validator	Line 117
`tools/build-site-pages.mjs`	tool or validator	Line 289
`tools/validate.mjs`	tool or validator	Line 150

Change history

File	What it holds	Links
Commits to the text	every change to the text	·
`CHANGELOG.md`	notable changes, by version	·
`release/manifest.json`	release manifest with file digests	in-toto statement
Releases	tagged releases of the repository	·
`proposals/NXS-STD-PC-000005.json`	Nexus Risk Standards: the systemic catalogue of 124 risk standards across the risk core, the six anchor nexus streams, technology, finance, policy, development, cross-cutting domains, hazards, intelligence, programme and systems	History

Propose a change

File	What it holds	Links
Open a proposal on NS-0	issue form: target, kind, rationale (NS-13)	Template
Issue form: comment	issue form	Template
Issue form: errata	issue form	Template
Issues that mention NS-0	open and closed	·
Pull request template	what a change must carry: target, kind, rationale, validation	·
`CONTRIBUTING.md`	pull requests, sign-off and checks	·
`GOVERNANCE.md`	how registry codes and texts change	·

10Develop and take part

How NS-0 is developed, and how to take part

NS-0 is developed in the open under NS-13 (the stages and gates of NS-13). Working groups draft, councils decide the reserved matters, and anyone may propose a change, comment, submit an implementation report, object or appeal, without membership or fee.

Who decides what: the decision-rights matrix.
The process: stages, gates, review windows and appeals.
Open gateways and calls: how to propose, comment, join a working group or request activation.
Develop a standard: the development track and the lifecycle of each standard.
NS-13 in the canonical repository.

11External standards

Relation to external standards

NS-0 relates to external standards by identifier, clause number and URL (NS14-R1), and directs the reader to the issuing body.

12Research

Recent research and sources

Peer-reviewed articles, preprints, reports and datasets on the subject of this standard, retrieved at the time of reading from open scholarly metadata services (OpenAlex and Crossref) and listed with authors, venue, year, type and access status, with a link to each work. Curated references and related standards are listed first; recent works matched by subject follow and are listed for orientation.

Curated references

Standard Setting Committees: Consensus Governance for Shared Technology Platforms
American Economic Review · 2012 · Peer-reviewed
RFC 6852 Affirmation of the Modern Paradigm for Standards
IETF · 2013 · Standard
W3C Process Document
W3C · 2025 · Official publication
A Quick Guide to Software Licensing for the Scientist-Programmer
PLOS Computational Biology · 2012 · Peer-reviewed
Open Definition 2.1
Open Knowledge Foundation · 2015 · Standard
The Open Source Definition
Open Source Initiative · 2007 · Official publication
The Sendai Framework for Disaster Risk Reduction and Persons with Disabilities
International Journal of Disaster Risk Science · 2015 · Peer-reviewed
Web Content Accessibility Guidelines (WCAG) 2.2
W3C · 2023 · Standard

Related standards and frameworks

W3C Process Document (2025)
World Wide Web Consortium
OGC Technical Committee Policies and Procedures
Open Geospatial Consortium
ISO/IEC Directives, Part 1 (procedures) with Consolidated ISO Supplement, and Part 2 (drafting)
ISO and IEC
The Open Source AI Definition
Open Source Initiative
W3C Software and Document License (2023 version)
World Wide Web Consortium
Open Definition 2.1
Open Knowledge Foundation
Creative Commons Attribution 4.0 International (CC BY 4.0) as used for specification text
Creative Commons
RFC 6852 Affirmation of the Modern Paradigm for Standards (OpenStand principles)
IAB, IEEE-SA, IETF, Internet Society, W3C

Search terms, derived from the subject of the standard and its rules: open standards; FAIR principles; open science; standards governance; open data principles; combined with: governance; risk; data; interoperability. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

13Education and training

Risk Academy courses and disciplines

2 courses and 2 disciplines of Risk Academy (risksacademy.com) that teach the knowledge and methods of NS-0. Each course lists its level, stream and learning hours.

Courses

Course RAF-103 · Governance and policyScience Policy 101Bringing evidence on risk to decision makers honestly, clearly and usefullyIntroductory · Foundation stream · 19.5 learning hoursTake this course · risksacademy.com Course RAN-307 · Governance and policyPolicy and GovernanceHow institutions, laws and people decide about risk, and how to tell whether policy worksIntermediate · Nexus stream · 21.5 learning hoursTake this course · risksacademy.com

Disciplines

Discipline · Governance and policyRisk governance and institutionsrisksacademy.com Discipline · Governance and policyResearch, evidence and the science-policy interfacerisksacademy.com

The correspondence between courses, disciplines and the Nexus Standards is maintained with Risk Academy and is subject to its academic review.

14Across the network

Programmes, tracks and courses for this standard

GCRI Canada, The Global Risks Forum (GRF) and Risk Academy work on the subject of NS-0 in distinct roles (research and evidence; governance, policy and convening; education and training). Each entry states why it corresponds and the step it offers; each institution sets its own terms of participation.

Research and evidence

GCRI Canada

Research programmes that produce the observations, models and assessments these records describe.

Nexus RegistryRecords decisions and their authority.Apply to this programme therisk.globalAll programmes of GCRI Canada

Governance, policy and convening

The Global Risks Forum (GRF)

Tracks that convene public authorities, researchers and institutions on the governance of shared risks.

Governance NexusExamines anti-capture and integrity, the safeguards behind the founding commitments.Join this track globalriskforum.comAll tracks of The Global Risks Forum

Education and training

Risk Academy

Courses and disciplines that teach the knowledge and methods practitioners need to apply these standards.

Science Policy 101RAF-103 · Introductory · 19.5 learning hoursBringing evidence on risk to decision makers honestly, clearly and usefullyTake this course Policy and GovernanceRAN-307 · Intermediate · 21.5 learning hoursHow institutions, laws and people decide about risk, and how to tell whether policy worksTake this course All courses and disciplinesListed in the education and training section of this page

15Questions

Questions and answers.

What is the status of NS-0?

NS-0 is proposed. It may be applied voluntarily; adoption follows last call and a decision of the Global Standards Council, and national adoption is decided by each National Standards Council.

What does applying NS-0 establish?

Applying NS-0 is a statement by the implementer, verifiable under NS-11 where machine-readable clauses exist.

How is a change to NS-0 proposed?

By a proposal naming NS-0, the section concerned and the rationale; it passes review and last call under NS-13.

NRNexus Reports gateway · GW-STD

Contribute to Nexus Reports from this page.

Nexus 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.

Nexus Standards

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.

Across the Consortium

The same subject across the Consortium.

Risk Academyrisksacademy.comRisk information standards and interoperabilityWhere it is taught