> 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/introduction/standardization.md). # STANDARDIZATION How Nexus keeps meaning, status, records, permissions and outputs consistent. This section introduces ontology, status, registry, protocol and outputs. **Where this fits:** all six sectors · the [Nexus Standards pillar](/organization/programme/standards.md) and the [Labs](/organization/programme/labs.md) and [Foundry](/organization/programme/foundry.md) pillars that feed it · GCRI Canada as Secretariat, the Global Standards Council and each country's [National Standards Council](/organization/governance-in-operation/national-standards-council.md) · the Correction, Docket review and Renewal phases of [the programme year](/organization/programme/the-programme-year.md) · introduction to the deep doctrine. Canonical homes: [The Model](/organization/model.md) · [Nexus Standards](/organization/standards.md) · [Systems](/organization/systems.md).
Document record · Draft · Legal review required · Updated 21 October 2026 | | | | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Status** | Draft. Explanatory page; it creates no rights or obligations. | | **Legal review** | Required before final publication. | | **Version** | 2026.10.21-r3 | | **Updated** | 21 October 2026 · reviewed every 180 days | | **Owner** | Documentation desk (named reviewer pending) | | **Based on** | Nexus constitutional directives D-V3-0001, D-V3-0003, D-V3-0004 and D-V3-0005; [Nexus Standards](/organization/institutions/nexus-standards.md), as published at nexustandards.com (PROPOSED); the Nexus model and the Nexus Consortium model as published on the GCRI, GRF and GRA sites; Nexus Standards as published at nexustandards.com | | **Corrections** | Public corrections route to be announced; corrections are published as new dated versions. |
## In brief Standardization, in this documentation, is the governed discipline that keeps meaning, status, records, technical permissions and published outputs consistent across the Nexus programme. This introduction explains that discipline in six steps: the order behind it, shared vocabulary (ontology), honest status, durable records (registry), technical permissions (protocol) and typed outputs. It is explanatory only. It adopts no standard, certifies nothing and grants no authority; the binding sources are the V3 constitutional directives and registers it cites \[1]\[2]\[3]. ## Current position (21 October 2026) This section brings the page up to date with the published sites, the Nexus Standards and the owner's rulings of October 2026. Where the older text below differs, this section and the canonical pages it links govern. Nexus Standards is now published at [nexustandards.com](https://nexustandards.com/standards/): the foundation standards [NS-0](https://nexustandards.com/standards/ns-0/) to [NS-16](https://nexustandards.com/standards/ns-16/) and [NS-3b](https://nexustandards.com/standards/ns-3b/), the Nexus Indicator Standard NIS-1, and 348 Nexus Risk Standards in 15 series, of which the hazard family standards of NHS-1 are one. Every standard carries the status PROPOSED and a legal-review flag; none is adopted, and a UNI never certifies anything \[9]\[10]. Governance sits with a Global Standards Council, Technical Management Divisions and Technical Committees, with GCRI Canada as Secretariat and publisher of record and a National Standards Council in each country that forms one \[11]. National adoption is final: a country may adopt a standard as is, adopt it with a profile (NS-16), adapt it, or reference it only, and no global body holds a veto \[12]. This introduction explains the discipline behind those standards: order, ontology, status, registry, protocol and outputs. It does not restate any standard. Where a page here and a published standard differ, the standard on nexustandards.com governs, and the [Standards catalogue](/organization/standards/catalogue.md) lists every standard with its UNI. Earlier versions of this section described Nexus Standards as a draft programme with no publisher of record. That is superseded: the standards are published, GCRI Canada is publisher of record, and the governance bodies are described above \[11]. **Status.** Every programme is in formation and the current service level is R0, information and enquiries; no edition of [Nexus Reports](/organization/programme/reports.md) has been released and no [Risk Academy](/organization/programme/academy.md) credential has been issued \[13]\[14]. ## What this section covers The six pages keep their existing addresses. Each page has one job and links to the page that owns a shared concept, so each definition is stated once.
PageWhat it answersLink
I. OrderWhat standardization means here, why it comes before operations, and the sequence from meaning to effect.I. Order
II. OntologyHow shared terms, relationships and units are defined, versioned and extended without forking.II. Ontology
III. StatusHow status is stated per dimension (target, implemented, verified, observed, accepted) and never merged into one score.III. Status
IV. RegistryHow records and identifiers make status traceable, and why resolving an identifier authorizes nothing.IV. Registry
V. ProtocolHow recorded permissions become technical effect, and why technical effect never creates authority.V. Protocol
VI. OutputsHow outputs are typed, scoped, versioned and corrected, and what each kind of output does not do.VI. Outputs
## How to read this section * **Authority.** Every page here is explanatory (authority level L5). Where a page and a binding record disagree, the record prevails and the page is corrected \[1]\[4]. * **Nexus Standards.** Nexus Standards is published at [nexustandards.com](https://nexustandards.com/standards/): NS-0 to NS-16 and NS-3b, NIS-1 and 348 Nexus Risk Standards, every one at status PROPOSED with legal review required. GCRI Canada, as Secretariat, is publisher of record; no standards foundation is constituted, and the governance bodies are described in [Nexus Standards](/organization/standards.md) \[5]\[6]. One related standard, NIS-1 (Nexus Indicator Standard v1.0.0), is recorded as a draft that requires expert review \[7]. * **Names.** The twenty Nexus systems are named by their Nexus Standards display codes, for example [NXS-NSF](/organization/systems/nxs-nsf.md), the trust, sovereignty and assurance plane for identity, policy gates and access decisions. The first mention on a page carries a short description; later mentions use the code alone. NXS-NSF is a software system, not an institution \[2]\[4]. * **Three different "rails".** [NXS-RLS](/organization/systems/nxs-rls.md), the technical rails and protocol infrastructure for protocol-governed work across institutions, is system 18; One Rail-Two Stacks is the doctrine that separates the public-good rail from execution; [NXS-RLS](/organization/standardization/nexus-rail.md) is a section of the Standardization part of this site. Each page says which one it means \[4]. {% hint style="info" %} **Status.** System capabilities described on this page are target architecture under development. Nothing here states that a capability is in production use, certified or offered as a service. {% endhint %} ## Key relationships
Section map of the Standardization introduction. Binding records (V3 directives, registers) outrank the pages and lead into I. Order. Reading runs through Ontology, Status, Registry, Protocol and Outputs; each explains one V3 construct, from the Ontology Fabric to the Passport and Evidence fabrics. Nexus Standards, published as PROPOSED at nexustandards.com, informs the Registry page.

Figure 1. The six pages of this section and the V3 constructs each one explains. Editorial structure, not an authority or status claim: the V3 constructs are target architecture, and Nexus Standards is published with every standard at status PROPOSED. Source: D-V3-0001 §3, D-V3-0005 and Nexus Standards, as of 2026-10-16.

Text description of Figure 1 The figure has three columns. On the left, binding records (the V3 constitutional directives and the registers) sit outside the site and outrank every page; an arrow labelled "outrank pages" leads to I. Order, the entry page, which explains why meaning comes before output. Below them sits Nexus Standards, a programme whose standards are published at nexustandards.com, all at status PROPOSED. In the middle column, reading runs from I. Order to II. Ontology, III. Status, IV. Registry, V. Protocol and VI. Outputs. In the right column, each page points to the V3 construct it explains: Ontology explains the Ontology Fabric; Status explains the V3 truth dimensions and the claim ceiling; Registry explains the UNI Identifier Fabric; Protocol explains NXS-NSF policy decisions; Outputs explains the Passport Projection Fabric and the Evidence and Receipt Fabric. A line labelled "draft" runs from Nexus Standards to IV. Registry, which it informs through its draft identifier grammar.
## Canonical definitions used in this section * The sequence "meaning, status, record, effect, output" is defined once, in [I. Order](/organization/introduction/standardization/i.-order.md). * The five-state status grammar is defined in [III. Status](/organization/introduction/standardization/iii.-status.md); other pages link to it. * Identifier and record terms (UNI, record reference, correction reference) are defined in [IV. Registry](/organization/introduction/standardization/iv.-registry.md). * Institutional roles are explained in the [Organization introduction](/organization/introduction/organization.md), not in this section. * How to read authority, status words and boundary formulas across the site is explained in [III. Reading rules](/organization/introduction/knowledge/iii.-reading-rules.md). ## Related pages * Up: [Introduction](/organization/introduction.md) * Across: [Knowledge](/organization/introduction/knowledge.md) · [Organization](/organization/introduction/organization.md) · [Operations](/organization/introduction/operations.md) · [Cooperation](/organization/introduction/cooperation.md) · [Acceleration](/organization/introduction/acceleration.md) * Counterparts: [Standardization part](/organization/standardization.md) · [Nexus OSI](/organization/standardization/nexus-osi.md) · [Nexus Standards definition](/organization/organization/architecture/ii.-definitions/xii.-nexus-standards.md) · [Interoperability by default](/organization/standardization/nexus-ecosystem/iii.-infrastructure/principles/interoperability-by-default-in-the-nexus-ecosystem.md) ## Sources 1. Nexus constitutional directive D-V3-0001, *Master Architecture, Product and Production Build Directive V3.0*, section 3 (shared constitutional fabrics). Internal record, cited by identifier. 2. Nexus constitutional directive D-V3-0003, *Canonical Twenty-System Constitution and Authority Matrix*. Internal record, cited by identifier. 3. Nexus constitutional directive D-V3-0004, *One Rail-Two Stacks, Non-Execution and Lawful Handoff Constitution*, boundary formulas. Internal record, cited by identifier. 4. Nexus Documentation Standard, draft of 16 October 2026: authority and status, naming and the landing-page template, with the owner decisions of 16 October 2026. Internal editorial standard. 5. Nexus Standards, as published at nexustandards.com (every standard PROPOSED; legal review required): standards register and [NS-1](https://nexustandards.com/standards/ns-1/) (UNI and artifact catalog), status proposed. Draft source. 6. Owner decision of 16 October 2026: Nexus Standards cited as proposed; no publisher of record named. Internal record. 7. Nexus Indicator Standard NIS-1, version 1.0.0, a draft that requires expert review. Internal record, cited by identifier. 8. Nexus release hold policy (active since 21 July 2026) and claim registry. Internal record. 9. Nexus Standards (2026). *The standards*: foundation standards NS-0 to NS-16 and NS-3b, the Nexus Indicator Standard NIS-1 and the Nexus Risk Standards. Every standard at status PROPOSED. [nexustandards.com/standards](https://nexustandards.com/standards/). Read 2026-10-21. 10. Nexus Standards (2026). *Nexus Risk Standards (NRS)*: 348 standards in 15 series, including the hazard family standards of NHS-1; one retired standard (NRS-U20). [nexustandards.com/standards/nrs](https://nexustandards.com/standards/nrs/). Read 2026-10-21. 11. Nexus Standards (2026). *Governance of the Nexus Standards*: Global Standards Council, Technical Management Divisions, Technical Committees, working groups, Editors, Registrar, Conformance and Assurance Panel, Ethics, Conflicts and Appeals Panel, Secretariat (GCRI Canada, publisher of record) and National Standards Councils. Status PROPOSED; legal review required. [nexustandards.com/governance](https://nexustandards.com/governance/). Read 2026-10-21. 12. Nexus Standards (2026). *Adopt and implement the Nexus Standards*: adopt as is, adopt with a profile (NS-16), adapt, or reference only; national adoption is final and no global body holds a veto. [nexustandards.com/adopt-and-implement](https://nexustandards.com/adopt-and-implement/). Read 2026-10-21. 13. GCRI (2026). *Programme status*: Exploration, In formation, Constituted, Active programme, Paused, Closed, Historical record; current service level R0. [therisk.global/consortium/programme-status](https://therisk.global/consortium/programme-status/). Read 2026-10-21. 14. GCRI (2026). *Nexus Reports programme*: quarterly country editions, an annual flagship and specialist series; current approved releases: none. [therisk.global/publications/nexus-reports](https://therisk.global/publications/nexus-reports/). Read 2026-10-21. ## Editorial record * As of: 2026-10-16. Refresh: every 180 days, or sooner when a governing source changes. * Drafting: AI-assisted. Human review: pending; no named reviewer or approver yet. * Corrections: a public corrections route has not yet been published. Corrections will be recorded as new dated versions, not silent edits. * Change log: 2026-10-16 r1, upgraded to the documentation standard (Record block, In brief, cards to every child page, section map, status sentence, Nexus Standards stated as proposed, sources, editorial record). * Change: 2026-10-16 r2, readable document record and status note; systems named by Nexus Standards display codes with a first-mention description; system naming; internal identifiers, paths and commit references removed from reader text; sources restated as internal records cited by identifier. * Change: 2026-10-21 r3, brought up to date with the published sites, Nexus Standards and the owner's rulings of October 2026: Where this fits line; a Current position section; Nexus Standards described as published (NS-0 to NS-16 and NS-3b, NIS-1, 348 NRS in 15 series, all PROPOSED; GCRI Canada publisher of record; governance bodies and adoption modes); the national vocabulary of [National Nexus](/organization/governance-in-operation/national-nexus.md), the NNC with its six [Helix councils](/organization/governance-in-operation/councils.md), the NLC and the NWG; the finance boundary on every vehicle passage; the systems named as systems; all original sections kept. --- # 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/introduction/standardization.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.