> 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/catalogue.md). # Standards catalogue The Nexus Standards, NS-0 to NS-16 and the Nexus Risk Standards, each linked to its page on nexustandards.com. {% hint style="info" %} This page is generated from the canonical URL registry of the public sites (as of 2026-10-20). Edit the registry or `tools/gitbook/parts.mjs`, not this page. {% endhint %} Each standard is published on [nexustandards.com](https://nexustandards.com/standards/), where its status, versions and text are kept. Status on that site governs; this list only points to it. Machine-readable registries and data are distributed through nexustandards.com; see [Adopt and implement the Nexus Standards](https://nexustandards.com/adopt-and-implement/). | Standard | UNI | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | | [NS-0: Constitution and principles](https://nexustandards.com/standards/ns-0/) | `NXS-STD-ST-000004` | | [NS-1: The UNI and the artifact catalog (grammar v0.2)](https://nexustandards.com/standards/ns-1/) | `NXS-STD-ST-000001` | | [NS-2: Citation and attribution format for UNIs](https://nexustandards.com/standards/ns-2/) | `NXS-STD-ST-000009` | | [NS-3: Risk record UNIs (grammar, legacy crosswalk, allocation authority)](https://nexustandards.com/standards/ns-3/) | `NXS-STD-ST-000003` | | [NS-3b: Dataset and product metadata profile (STAC, DCAT, PROV-O)](https://nexustandards.com/standards/ns-3b/) | `NXS-STD-SW-000005` | | [NS-4: Structure and drafting of Nexus Standards and documents (v0.2)](https://nexustandards.com/standards/ns-4/) | `NXS-STD-ST-000010` | | [NS-5: Figure, map and visualization standard (with the UI/UX kit)](https://nexustandards.com/standards/ns-5/) | `NXS-STD-ST-000011` | | [NS-6: Surface wiring (API header, panel provenance, passports, OpenAPI)](https://nexustandards.com/standards/ns-6/) | | | [NS-7: Resolver landing pages, page meta tags, sitemap](https://nexustandards.com/standards/ns-7/) | | | [NS-8: Zenodo publishing workflow with legal gate, DOI write-back, Software Heritage archival](https://nexustandards.com/standards/ns-8/) | | | [NS-9: Contextual UNIs (deployments, instances, programme instances)](https://nexustandards.com/standards/ns-9/) | `NXS-STD-ST-000005` | | [NS-10: Policies and clauses (machine-readable obligations)](https://nexustandards.com/standards/ns-10/) | `NXS-STD-ST-000006` | | [NS-11: Verification and monitoring (evidence, attestations, zero-trust conformance observation)](https://nexustandards.com/standards/ns-11/) | `NXS-STD-ST-000007` | | [NS-12: Software, model and AI/ML artifacts (supply chain, model cards, dataset sheets)](https://nexustandards.com/standards/ns-12/) | `NXS-STD-ST-000012` | | [NS-13: Standards development process (open proposals, review, versioning, adoption)](https://nexustandards.com/standards/ns-13/) | `NXS-STD-ST-000008` | | [NS-14: Conformance and crosswalk to external standards](https://nexustandards.com/standards/ns-14/) | `NXS-STD-ST-000013` | | [NS-15: System model binding (identity levels, passports, chronotopes, relationships, risk routes and engines, cell intelligence, agent genomes)](https://nexustandards.com/standards/ns-15/) | `NXS-STD-ST-000014` | | [NS-16: UNI application profile (context names such as NXS-GRX-WAT-CAN; how articles, documents, code, data, APIs and interfaces carry the UNI)](https://nexustandards.com/standards/ns-16/) | `NXS-STD-ST-000015` | | [NRS: Nexus Risk Standards](https://nexustandards.com/standards/nrs/) | `NXS-STD-DS-000004` | A UNI is the identifier the catalogue gives an artefact; see [The UNI: catalog and resolver](https://nexustandards.com/uni/). --- # 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/catalogue.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.