> For the complete documentation index, see [llms.txt](https://docs.therisk.global/organization/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.therisk.global/organization/standardization.md).

# STANDARDIZATION

Nexus standardization for ontology, protocol, registry, sovereign interoperability, conformance, public-good infrastructure, and lawful handoff.

**Where this fits:** all six sectors · all six pillars · [the twenty systems](/organization/systems.md) · [the Nexus Consortium](/organization/institutions/nexus-consortium.md) · doctrine and architecture.

**In brief.** This part holds the Nexus standardization doctrine and specifications: the Nexus Ecosystem model, the [NXS-NSF](/organization/systems/nxs-nsf.md) Sovereignty Framework, the Nexus OSI reference model and the [NXS-RLS](/organization/systems/nxs-rls.md) interoperability profile. All of it is [Nexus Standards](/organization/institutions/nexus-standards.md) work in progress. The standards themselves are published on [nexustandards.com](https://nexustandards.com/standards/), whose text and status govern; this part explains the designs behind them and links to the standards by identifier ([OECD, 2014](https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405); [UN Office of the Secretary-General's Envoy on Technology, 2024](https://www.dpi-safeguards.org/)). A design described here is not a deployed system, a certification or an approval; the competent authority decides, outside the programme.

<figure><picture><source srcset="https://2655483226-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEQtittnb4JJQ2YOtd2tk%2Fuploads%2Fgit-blob-096b872b02b7cf4d5f74a6d04eb21ddd5487d4a9%2Fnexus-standards-family-dark.svg?alt=media" media="(prefers-color-scheme: dark)"><img src="https://2655483226-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEQtittnb4JJQ2YOtd2tk%2Fuploads%2Fgit-blob-65c0c2ca0f16bea37f297cf04315a865b3de4dfe%2Fnexus-standards-family-light.svg?alt=media" alt="The Nexus Standards grouped by what they standardise. NS-0 sets the constitution and principles. Identifiers and citation: NS-1 the UNI and artefact catalogue, NS-2 citation and attribution, NS-3 risk record UNIs, NS-9 contextual UNIs and NS-16 the UNI application profile. Records and documents: NS-3b dataset and product metadata, NS-4 structure and drafting, NS-5 figures, maps and visualization. Surfaces and publishing: NS-6 surface wiring, NS-7 resolver landing pages, NS-8 the publishing workflow. Obligations and assurance: NS-10 policies and clauses, NS-11 verification and monitoring, NS-12 software, model and AI/ML artefacts, NS-14 conformance and crosswalks. NS-15 binds the system model; NS-13 is the standards development process; the Nexus Risk Standards (NRS) apply them by subject."></picture><figcaption><p><strong>The Nexus Standards by function.</strong> Grouped by the published titles; each standard's status and text on nexustandards.com govern. Source: nexustandards.com standards index, via the canonical URL registry. As of 2026-10-20.</p></figcaption></figure>

<details>

<summary>Figure data (text alternative)</summary>

| Element | Description                                                            |
| ------- | ---------------------------------------------------------------------- |
| NS-0    | Constitution and principles                                            |
| NS-13   | Standards development process: proposals, review, versioning, adoption |
| NS-1    | The UNI and the artefact catalogue                                     |
| NS-2    | Citation and attribution format for UNIs                               |
| NS-3    | Risk record UNIs                                                       |
| NS-9    | Contextual UNIs: deployments, instances, programme instances           |
| NS-16   | UNI application profile                                                |
| NS-3b   | Dataset and product metadata profile                                   |
| NS-4    | Structure and drafting of standards and documents                      |
| NS-5    | Figure, map and visualization standard                                 |
| NS-6    | Surface wiring: API header, panel provenance, passports                |
| NS-7    | Resolver landing pages, page meta tags, sitemap                        |
| NS-8    | Publishing workflow with legal gate and archival                       |
| NS-10   | Policies and clauses as machine-readable obligations                   |
| NS-11   | Verification and monitoring                                            |
| NS-12   | Software, model and AI/ML artefacts                                    |
| NS-14   | Conformance and crosswalk to external standards                        |
| NS-15   | System model binding                                                   |
| NRS     | Nexus Risk Standards across subject areas                              |

</details>

{% hint style="info" %}
**Read with the current model.** The Nexus Ecosystem is defined once, on [the Nexus Ecosystem page](/organization/standardization/nexus-ecosystem.md): the governed public-good architecture that connects institutions, technologies, standards, evidence and lawful implementation pathways across the twenty systems. Technology here is described as [the twenty systems](/organization/systems.md) by NXS code; technology readiness uses the nine levels of ISO 16290, never ten. Finance vehicles are structures competent, lawful actors may form outside the programme ([Lawful handoffs](/organization/finance-readiness/lawful-handoffs.md)). Everything is in formation (service level R0).
{% endhint %}

## Nexus standardization overview

This section defines the Nexus standardization layer for ontology, protocol, registry, conformance, and sovereign interoperability across public-good infrastructure. It gives the ecosystem one controlled grammar for meaning, status, trust, and lawful coordination.

It also links standards to implementation. The section connects digital public infrastructure, sovereign compute, verification, routeability, and lawful handoff through records-valid rules that stay usable across institutions, jurisdictions, and technical systems.

### Section map

* [NEXUS ECOSYSTEM](/organization/standardization/nexus-ecosystem.md)\
  Defines the core Nexus Ecosystem model for public-good digital infrastructure, systemic risk governance, DRR, DRF, DRI, early warning, and anticipatory action.
* [NEXUS SOVEREIGNTY](/organization/standardization/nexus-sovereignty.md)\
  Sets the sovereignty framework for verifiable governance, zero-trust public infrastructure, the NXS-NSF trust and policy system, and machine-readable institutional trust.
* [NEXUS OSI](/organization/standardization/nexus-osi.md)\
  Establishes the standards system for conformance, layered architecture, testable minima, reference implementation, and standards-aware delivery.
* [NXS-RLS](/organization/standardization/nexus-rail.md)\
  Defines the common rail for risk governance, validity-by-record, routeability, lifecycle integrity, standards continuity, and global-to-local interoperability.
* [NEXUS PROGRAMS](/organization/acceleration/nexus-programs.md)\
  Covers standardized program structures for fellowships, research, policy, media, and working-group pathways across the Nexus ecosystem.
* [NXS-STU](/organization/acceleration/nexus-studio.md)\
  Shows how standardized studio environments support sector-specific design, simulation, collaboration, and applied public-good systems work.
* [ACCELERATORS](/organization/acceleration/accelerators.md)\
  Maps the acceleration layer for innovation pathways, frontier technologies, cohort design, risk management, funding mechanisms, and adoption at scale.
* [CHARTER](/organization/acceleration/charter.md)\
  Provides the foundational charter for acceleration, readiness, safeguards, public-good system formation, national ownership, and lawful handoff.

## Sources

* Nexus Standards. NS-0: Constitution and principles. Proposed. [nexustandards.com/standards/ns-0/](https://nexustandards.com/standards/ns-0/)
* Nexus Standards. NS-15: System model binding (subjects, passports, chronotopes, routes, engines, cells and agents). Proposed. [nexustandards.com/standards/ns-15/](https://nexustandards.com/standards/ns-15/)
* Nexus Standards. NS-14: Conformance and crosswalk to external standards. Proposed. [nexustandards.com/standards/ns-14/](https://nexustandards.com/standards/ns-14/)
* Nexus Standards. [NRS-S0](https://nexustandards.com/standards/nrs/#nrs-s0): System and stack passports and platform conformance. [nexustandards.com](https://nexustandards.com/standards/nrs/#nrs-s0)
* OECD (2014). Recommendation of the Council on the Governance of Critical Risks. OECD/LEGAL/0405, adopted 6 May 2014. [legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405](https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405)
* UN Office of the Secretary-General's Envoy on Technology and UNDP (2024). Universal DPI Safeguards Framework. New York: United Nations, September 2024. [www.dpi-safeguards.org](https://www.dpi-safeguards.org/)
* Rose, S., Borchert, O., Mitchell, S. and Connelly, S. (2020). Zero Trust Architecture. NIST Special Publication 800-207. Gaithersburg, MD: NIST. [csrc.nist.gov/pubs/sp/800/207/final](https://csrc.nist.gov/pubs/sp/800/207/final)
* ISO (2018). ISO 31000:2018 Risk management — Guidelines. Geneva: International Organization for Standardization. [www.iso.org/standard/65694.html](https://www.iso.org/standard/65694.html)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.therisk.global/organization/standardization.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.