> 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 ### Summary The **Nexus Standardization** section explains how Nexus defines common language, common states, and common outputs across the ecosystem. It covers order, ontology, status, registry, protocol, and standardized outputs. This section supports readers working on **interoperability**, **standards architecture**, **controlled vocabularies**, and **governed outputs**. ### What this section covers * **Ontology and status logic** for shared meaning across Nexus. * **Registry and protocol structure** for standardized coordination. * **Outputs and artifacts** that carry standardized information through the ecosystem. ### Related topics * [I. Order](/organization/introduction/standardization/i.-order.md) + for the ordering logic behind standardization. * [II. Ontology](/organization/introduction/standardization/ii.-ontology.md) + for controlled terminology and semantic structure. * [III. Status](/organization/introduction/standardization/iii.-status.md) + for status logic and state definitions. * [IV. Registry](/organization/introduction/standardization/iv.-registry.md) + for the registry layer and record structure. * [V. Protocol](/organization/introduction/standardization/v.-protocol.md) + for protocol rules and exchange logic. * [VI. Outputs](/organization/introduction/standardization/vi.-outputs.md) + for standardized deliverables and artifacts. * [Interoperability by Default](/organization/standardization/nexus-ecosystem/iii.-infrastructure/principles/interoperability-by-default-in-the-nexus-ecosystem.md) + for how standards support sovereign interoperability and portability. ### Why it matters Nexus needs shared standards to keep governance, operations, and infrastructure aligned. Without common ontology, status, registry, and protocol rules, the ecosystem would fragment across pages, systems, and institutions. This section gives readers the standardization layer that makes Nexus searchable, interoperable, and durable. ### Next steps * Read [II. Ontology](/organization/introduction/standardization/ii.-ontology.md) for semantic structure. * Read [IV. Registry](/organization/introduction/standardization/iv.-registry.md) for record logic. * Read [V. Protocol](/organization/introduction/standardization/v.-protocol.md) for the governing protocol layer. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` 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 optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.