Nexus Standards · NS-10 · Proposed

NS-10

NS-10: Policies and clauses (machine-readable obligations

NS-10 is a proposed Nexus Standard; the artifacts it governs are identified by UNIs (Unique Nexus Identifier). NS-10 makes obligations machine-readable. A clause is one obligation: whom it binds (contextual UNIs, NS-9), what shall hold (a predicate over records), how and by whom it is evaluated, what evidence satisfies it and what happens when it fails. A policy is an ordered, versioned set of clauses with an owner, an adoption decision and a conformance profile. Users define policies and clauses and bind them to their contexts; an implementation evaluates and enforces them. External obligations (legislation, regulation, sector standards, treaty commitments) are expressed as clauses that cite their source; the source text is never reproduced.

Where it applies All standards

01Overview

Summary

NS-10record

Statusproposed
Responsible scopetrust, authorization and assurance; integrated posture and executive synthesis
IdentifierNXS-STD-ST-000006
Rules stated7
Programme areas21
Documentstandards/NS-10-policies-and-clauses.md
Source filesrepository

Nexus Standards · proposed

02Status

Status of NS-10

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-04. 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 in Latin America and the Caribbean

The map frames Latin America and the Caribbean as an example geography for the subject of NS-10; the frame gives context and is not a statement of where the standards apply. 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 Latin America and the Caribbean.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-10 among the standards.

Canvas · NS-10 among the standardsProcess diagram

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

05Process

The standard as a process

An obligation is identified at its source and written as a clause with modality, subjects, condition, evaluation, evidence and failure effect; clauses are composed into a policy and enter through a proposal; the policy is bound to contexts; evaluators with mandates evaluate each clause and the failure effect applies; conformance is a projection of attestations. 9 operations in 6 phases; each states its actor, its decision rule, the record it leaves and the rule identifiers it implements (12 rules of NS-10 and the standards it applies). Records and artifacts are cited by UNI (Unique Nexus Identifier) and version.

Process · Writing, binding and enforcing a clause9 operations · 6 phases

All operations in order (9)

01
Identify obligation start · Source
The source is cited by identifier, clause number and URL; its text stays with its body.
Who
a working group or a policy author
Decision rule
external obligations are cited, never copied
Record
derivedFrom: the Nexus or external standard and clause, cited by identifier and URL
Implements
NS10-R4, NS14-R1
02
Write the clause model · Clause
Modality follows RFC 2119; the condition is a predicate over named record inputs in a declared language, so that two conformant evaluators reach the same result.
Who
the policy author
Decision rule
every enforced obligation is a clause with a UNI; the predicate is data in a declared language
Record
a clause with its UNI: modality, condition, evaluation, evidence, onFailure
Implements
NS10-R1, NS10-R3
03
Select subjects step · Clause
Selectors may name UNIs, scopes, categories, domains, sectors, jurisdictions or environments.
Who
the policy author
Decision rule
subjects are contextual UNIs; names never bind
Record
selectors that resolve to contextual UNIs
Implements
NS10-R2
04
Compose policy record · Policy
A policy names its issuer, the clauses, what it applies to, its conformance levels, its reporting interval and the decision that adopted it.
Who
the issuing institution
Decision rule
clauses carry weights: blocking, required, recommended, informative
Record
a policy (PC) with ordered clauses, weights and conformance levels
Implements
NS10-R7
05
Proposal gate · Policy
Each edit is a version; proposals follow the open process.
Who
the editors, under NS-13
Decision rule
every change enters through a proposal
Record
a proposal with a UNI and its disposition
Implements
NS13-R1
06
Bind to contexts step · Binding
A policy is bound to a deployment, a programme instance, a jurisdiction or a tenant.
Who
the competent authority for the context
Decision rule
binding is a record with its own authority decision
Record
a binding record with its decision
Implements
NS10-R2, NS9-R1
07
Evaluate exercise · Evaluation
The evaluator runs each clause on its declared mode: continuous, on record, scheduled or on demand.
Who
an evaluator with a mandate, never the subject
Decision rule
evaluation never runs on the subject's own authority; engine and version are recorded
Record
attestations per clause (NS-11)
Implements
NS10-R3, NS11-R2
08
Failure effect decision · Evaluation
A refusal blocks the action at the point of action with a typed reason; results of clauses not yet approved are shown as claims under review.
Who
the context's command surface
Decision rule
failure effects are typed; refuse is the default for blocking clauses in production
Record
record, warn, degrade the claim, refuse, escalate or revoke
Implements
NS10-R5, NS10-R6
09
Conformance view end · Reporting
Levels are self-declared, verified, attested or recognized; recognition is conferred by the authority, not by the policy.
Who
any reader
Decision rule
conformance is a projection of attestations, never a stored verdict
Record
conformance per policy per context, with evaluation time and evaluator
Implements
NS11-R5, NS10-R7

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-10: Policies and clauses · NS-14: Conformance and crosswalk to external standards · NS-13: Standards development process · NS-9: Contextual UNIs.

06Specification

NS-10 clause by clause

6 clauses and 7 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

Artifacts

Artifact	Category	UNI example	Schema
Clause	`CL`	`NXS-EWS-CL-000012`	`nexus-clause.v1.json`
Policy	`PC`	`NXS-GCR-PC-KEN-000003` (a GCRI Canada policy for Kenya)	`nexus-policy.v1.json`
Attestation (result of an evaluation)	`AT`	`NXS-NSF-AT-000911`	`nexus-attestation.v1.json` (NS-11)

Clauses and policies are catalogued like any artifact (NS-1): allocated by the owner's catalog, append-only and versioned, with legalState and claimCeiling. A clause is reusable across policies; a policy references clauses by UNI and version and gives each a weight (blocking, required, recommended, informative).

The clause

Field	Content
`modality`	One of the machine tokens MUST, MUST_NOT, SHOULD, SHOULD_NOT and MAY, as defined in RFC 2119 and clarified by RFC 8174. In prose they correspond to the NS-4 verbal forms: MUST to "shall", SHOULD to "should", MAY to "may".
`subjects`	Selectors that resolve to contextual UNIs: explicit UNIs, scopes, categories, domains, sectors, jurisdictions and environments. A name is never a selector (NS0-P10).
`condition`	A predicate in a declared language (`jsonlogic`, `cel`, `sql-view`, `rego`, `jsonschema`) over named inputs, each a record kind (NS-3) or an artifact category with a selector and a time window. The predicate is data; an implementation evaluates it with an engine for that language and records which engine and version it used.
`evaluation`	`continuous` (on every relevant record), `on-record`, `scheduled` or `on-demand`. The `evaluatorRef` is never the subject itself and shall hold the `verifierMandate` (NS0-P5).
`evidence`	The evidence kinds that satisfy the clause (record refs `recordUni@recordVersion`, receipts, digests, signed attestations, observations, external reports, human decisions), the retention period and the publicity.
`onFailure`	`record`, `warn`, `degrade-claim` (lower the subject's claim ceiling), `refuse` (block the action at the point of action), `escalate` (to a role or mandate, never to a named person) or `revoke`, with a grace period where the law permits.
`derivedFrom`	The Nexus or external standard and clause that the obligation implements, cited by identifier and URL.
`authority`	The issuer and the recorded decision that adopted the clause.

The policy

A policy names its owner, its clauses with their weights, what it applies to (appliesTo selectors), its conformance levels and reporting interval, the standards it derives from and the decision that adopted it. Conformance levels are a fixed vocabulary:

Level	Meaning
`SELF_DECLARED`	The subject states conformance; no evaluation has run. Displayed as a claim.
`VERIFIED`	Every `blocking` and `required` clause has a current `PASS` attestation from an evaluator with a mandate (NS-11).
`ATTESTED`	As VERIFIED, with signed attestations and published evidence digests.
`RECOGNIZED`	As ATTESTED, with a recorded decision of an authority entitled to recognise conformance. The authority, not the policy, confers recognition.

No level means "certified" or "compliant" in the legal sense unless the decision of the issuing authority says so in its own terms.

Define, bind, evaluate, enforce and report

Define. A user creates clauses and policies as catalogued artifacts (mint, edit, version, propose). Every edit is a version; proposals follow NS-13.
Bind. A policy is bound to contexts (NS-9): a system deployment, a programme instance, an operational environment, a tenant or a jurisdiction. A binding is a record with its own authority decision.
Evaluate. For each bound context, the implementation runs the evaluator for each clause in the declared mode, under the evaluator's own mandate, and writes attestations (NS-11). Evaluation never runs on the subject's own authority.
Enforce. refuse blocks the action at the point of action with a typed reason; degrade-claim lowers the context's claim ceiling; escalate opens a decision case (decision support class, DSS). Every outcome is visible on the surface where the action was attempted, with the clause UNI and the attestation UNI.
Report. Conformance per policy per context is a projection of attestations, never a stored verdict, and carries the evaluation timestamp and the evaluator.

Rules

Rule	Text
NS10-R1	Every obligation that an implementation enforces shall be a clause with a UNI; code may implement a rule, but no rule shall be enforced without a clause record that names it.
NS10-R2	Subjects shall be contextual UNIs; names, labels or free text shall not bind.
NS10-R3	The predicate shall be data in a declared language; evaluators shall record the engine and its version; two conformant evaluators shall reach the same result for the same clause and the same inputs.
NS10-R4	External obligations shall be cited, not copied.
NS10-R5	Failure effects shall be typed; `refuse` is the default for `blocking` clauses in production contexts.
NS10-R6	A clause or policy whose `legalState` is other than `APPROVED` may be evaluated, but its results shall be displayed as claims under review.
NS10-R7	Policies and clauses shall be append-only artifacts: withdrawal and supersession keep the record.

Adoption by implementations

An implementation adopts this standard by providing: artifact types for clauses and policies; catalog allocation under each tenant's scopes; an evaluator whose mandates are issued by the implementation's trust authority (NS-11); surfaces for binding and for results; and a recorded policy decision as its adoption record. It reports its status in registry/consumers.yaml.

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 (NS10-R1, NS10-R2, NS10-R3…) 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-10

21 programme areas list NS-10.

08Research hub

Recent research on NS-10

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 termsrules as code; machine-readable legislation; policy as code; machine-readable regulation; legal informatics; normative reasoning; Regulation 2024/1689; Directive 2022/2555combined with: regulation; law; policy; obligations; rulesDerived 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-10 in the standards repository

The text, schemas, machine-readable files, registry rows, tests and history behind NS-10, 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-10-policies-and-clauses.md`	NXS-STD-ST-000006	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
`schemas/nexus-policy.v1.json`	Nexus policy (NS-10)	Raw

Machine-readable files

File	What it holds	Links
`machine/catalogue.jsonld`	JSON-LD · 1 mention	Raw · First mention, line 1402
`machine/catalogue.oscal.json`	OSCAL JSON · 1 mention	Raw · First mention, line 2509
`machine/catalogue.ttl`	Turtle (RDF) · 1 mention	Raw · First mention, line 1956
`catalog/artifact-catalog.yaml`	catalog records · 3 mentions	First mention, line 315

Registry rows

File	What it holds	Links
`registry/subsites.yaml`	Nexus Standards subsites - the systemic architecture of nexustandards.com · 19 rows or mentions	Line 37
`registry/ecosystem-coverage.yaml`	Nexus ecosystem coverage register (programme B corpus read) · 12 rows or mentions	Line 125
`registry/review-investigations.yaml`	Circulation for technical review and comment, and the technical review areas · 2 rows or mentions	Line 78
`registry/dags.yaml`	Process and pipeline graphs rendered by the site's DAG component (nxs-dag) · 1 row or mentions	Line 220
`registry/domains.yaml`	Nexus domains (NS-9 context.domains, NS-10 subject selectors) · 1 row or mentions	Line 2
`registry/nexus-standards.yaml`	Nexus Standards NS-1 - the UNI (Unique Nexus Identifier) and artifact catalog · 1 row or mentions	Line 180
`registry/risk-standards.source.yaml`	'Nexus Risk Standards: the systemic catalogue' · 1 row or mentions	Line 599
`registry/risk-standards.yaml`	'Nexus Risk Standards: the systemic catalogue' · 1 row or mentions	Line 1263
`registry/sectors.yaml`	Sectors and industries (NS-9 context.sectors, NS-10 subject selectors) · 1 row or mentions	Line 2

Tests and validators

File	What it holds	Links
`tools/build-risk-standards.mjs`	tool or validator	Line 97
`tools/build-site-pages.mjs`	tool or validator	Line 292
`tools/site-open-standards.mjs`	tool or validator	Line 317
`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	·

Propose a change

File	What it holds	Links
Open a proposal on NS-10	issue form: target, kind, rationale (NS-13)	Template
Issue form: comment	issue form	Template
Issue form: errata	issue form	Template
Issues that mention NS-10	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-10 is developed, and how to take part

NS-10 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-10 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

RFC 6852: Affirmation of the Modern Paradigm for Standards
IETF / RFC Editor · 2013 · Standard
The FAIR Guiding Principles for scientific data management and stewardship
Scientific Data · 2016 · Peer-reviewed
The CARE Principles for Indigenous Data Governance
Data Science Journal · 2020 · Peer-reviewed
Making the rules: the governance of standard development organisations and their policies on intellectual property rights
European Commission Joint Research Centre · 2019 · Official publication
RFC 2026: The Internet Standards Process, Revision 3
IETF / RFC Editor · 1996 · Standard
RFC 7282: On Consensus and Humming in the IETF
IETF / RFC Editor · 2014 · Standard
Standard setting committees: consensus governance for shared technology platforms
American Economic Review · 2012 · Peer-reviewed
W3C Process Document
W3C · 2025 · Official publication

Related standards and frameworks

Regulation (EU) 2024/1689 (Artificial Intelligence Act)
European Parliament and Council
CEN-CENELEC JTC 21 harmonised standards in support of the EU AI Act (incl. prCEN/CLC/TR 18347)
CEN-CENELEC JTC 21
Regulation (EU) 2024/2847 (Cyber Resilience Act)
European Parliament and Council
Universal Digital Public Infrastructure Safeguards Framework
UN Office of the Secretary-General's Envoy on Technology and UNDP
United Nations Global Principles for Information Integrity
United Nations
Directive (EU) 2022/2555 (NIS2)
European Parliament and Council
Regulation (EU) 2016/679 (General Data Protection Regulation)
European Parliament and Council
OECD Recommendation of the Council on Regulatory Policy and Governance
OECD

Search terms, derived from the subject of the standard and its rules: rules as code; machine-readable legislation; policy as code; machine-readable regulation; legal informatics; normative reasoning; combined with: regulation; law; policy; obligations; rules. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

13Education and training

Risk Academy courses and disciplines

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

Courses

Course RAT-202 · Governance and policyClausecraft and LicensingLicences, attribution, data-sharing agreements and risk-transfer clauses for risk tools, at a methods levelIntermediate · Technical stream · 20 learning hoursTake this course · risksacademy.com

Disciplines

Discipline · Governance and policyContracts, intellectual property and licensingrisksacademy.com Discipline · Risk scienceRisk information standards and interoperabilityrisksacademy.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

The Global Risks Forum (GRF), The Global Risks Alliance (GRA) and Risk Academy work on the subject of NS-10 in distinct roles (governance, policy and convening; capital, finance and markets; education and training). Each entry states why it corresponds and the step it offers; each institution sets its own terms of participation.

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 decision rights and how obligations are assigned.Join this track globalriskforum.comAll tracks of The Global Risks Forum

Capital, finance and markets

The Global Risks Alliance (GRA)

Industry programmes in which financial institutions build a shared understanding of systemic risk.

Financial Regulation NexusCompares how prudential and conduct obligations are specified.Join this programme globalriskalliance.comAll programmes of The Global Risks Alliance

Education and training

Risk Academy

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

Clausecraft and LicensingRAT-202 · Intermediate · 20 learning hoursLicences, attribution, data-sharing agreements and risk-transfer clauses for risk tools, at a methods levelTake 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-10?

NS-10 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-10 establish?

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

How is a change to NS-10 proposed?

By a proposal naming NS-10, 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.

Around the Nexus Standards.

Nexus Standards

Take part in the standards.

Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.

Propose a change Roadmap to 2030 Adopt and implement

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 artifact; 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.