> 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/standards.md). # NEXUS STANDARDS The Nexus Standards: the open standards of the programme, where they are published, and how this documentation relates to them. The [Nexus Standards](/organization/institutions/nexus-standards.md) are the open standards of the programme: its constitution and principles ([NS-0](https://nexustandards.com/standards/ns-0/)), the UNI identifier and artefact catalogue ([NS-1](https://nexustandards.com/standards/ns-1/)), the risk record, metadata, figure, policy, verification, conformance and system-model standards, and the Nexus Risk Standards (NRS). The standards are published and maintained on [nexustandards.com](https://nexustandards.com/standards/). Their text, status and versions on that site govern; this documentation explains and links to them and does not restate them. Public material, registries and machine-readable data are distributed through nexustandards.com; see [Adopt and implement the Nexus Standards](https://nexustandards.com/adopt-and-implement/).

The Nexus Standards by function. 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.

Figure data (text alternative)

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

How a UNI travels from allocation to a landing page, in four lanes. In the catalog, a UNI is minted through a catalog or a record allocation authority and is never typed by hand (NS-1 rule R2); the catalog holds one record per UNI with the required metadata, and the legal state defaults to review required (NS-1 section 4). The UNI is then embedded in the artefact itself: a Nexus-UNI header line in source files and documents, front matter, a figure caption suffix, a nexus-uni meta tag on pages and an X-Nexus-UNI header on API responses (NS-1 section 6, NS-16). The context name is derived from the UNI by removing the category and serial, and is never minted; the NS-9 contextual record is the record of truth for a context. A citing work cites the artefact by its UNI, with a version when it cites one state; a name alone does not cite (NS-2). The resolver answers at /uni/{uni} for published, non-restricted records only, and every cited UNI must resolve (NS-2 rule R5, NS-7). It returns an HTML landing page for browsers, with the nexus-uni meta tag and Schema.org JSON-LD, or the catalog record as JSON for machines; /ctx/{context name} lists every published record of a context. — **From minting to resolving a UNI.** NS-1, NS-2, NS-9 and NS-16 are PROPOSED, as recorded in the standards index; NS-7 is recorded as specified in NS-1 section 1, with no standalone text. Their text and status on nexustandards.com govern. A design for reading, not a record of any deployed resolver. Source: NS-1 sections 1, 4, 5 and 6; NS-2 sections 1 and 3; NS-9 sections 1 to 3; NS-16 sections 1, 6 and 7; NS-7 as the resolver entry of the standards registry. As of 2026-10-21.

Figure data (text alternative)

| Element | Description | Connected to | | ------------------------ | -------------------------------------------------------- | ------------------------------------------------- | | Mint | Through a catalog, never typed by hand | Catalog record; Embedded in the artefact | | Catalog record | Required fields; legal state review-required by default | Mint; Resolve /uni/{uni} | | Embedded in the artefact | Header line, front matter, caption, meta tag, API header | Mint; Context name; Cite by UNI | | Context name | Derived, never minted; the NS-9 record is the truth | Embedded in the artefact | | Cite by UNI | UNI\@version; a name alone does not cite | Embedded in the artefact; Resolve /uni/{uni} | | Resolve /uni/{uni} | Published, non-restricted records only | Catalog record; Cite by UNI; Landing page or JSON | | Landing page or JSON | HTML with JSON-LD for browsers; the record for machines | Resolve /uni/{uni} |

## Where to go | To | Go to | | ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Read a standard | [Standards catalogue](/organization/standards/catalogue.md), then its page on nexustandards.com | | Find which standards apply to a case | [Which standards apply](https://nexustandards.com/which-standards-apply/) | | Resolve a UNI | [The UNI: catalog and resolver](https://nexustandards.com/uni/) | | Adopt or implement | [Adopt and implement the Nexus Standards](https://nexustandards.com/adopt-and-implement/) | | Propose or develop a standard | [Develop a standard](https://nexustandards.com/develop-a-standard/) | | Governance and participation | [Governance of the Nexus Standards](https://nexustandards.com/governance/) and the [Standards IP and Participation Policy](https://nexustandards.com/standards-ip-policy/) | ## Read further * [Standardization](/organization/standardization.md): the standardization doctrine of the programme. Where it and the published standards differ, the published standards govern. --- # 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/standards.md?ask=&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.