> 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/nexus-osi.md).

# NEXUS OSI

**Where this fits:** all six sectors · [the Standards pillar](/organization/programme/standards.md) · [NXS-NET](/organization/systems/nxs-net.md) and [NXS-NSF](/organization/systems/nxs-nsf.md) · [Nexus Standards](/organization/institutions/nexus-standards.md) · protocol specification (v0.1).

**In brief.** This page is part of the Nexus OSI (NXOSI) reference model. This page belongs to the Nexus OSI (NXOSI) reference model, a Nexus Standards design in progress whose governing texts are published on [nexustandards.com](https://nexustandards.com/standards/) ([Birkholz et al., 2023](https://www.rfc-editor.org/rfc/rfc9334); [OpenSSF, 2023](https://slsa.dev/spec/v1.0/)). A conformance profile is a basis for review, not a certification; the external standards it draws on are governed by their own bodies.

{% hint style="info" %}
**Read with the current model.** This is a draft specification in the Nexus Standards programme; [nexustandards.com](https://nexustandards.com/standards/) governs the text and status of every standard it cites. Concepts taken from IETF work on remote attestation and transparency logs and from the OpenSSF SLSA framework are attributed in the Sources below; the specification profiles them and does not restate them as its own. No submitting foundation exists: the specification is developed under the Nexus Standards process ([NS-13](https://nexustandards.com/standards/ns-13/)).
{% endhint %}

***

## Sources

* Nexus Standards. NS-11: Verification and monitoring. Proposed. [nexustandards.com/standards/ns-11/](https://nexustandards.com/standards/ns-11/)
* Nexus Standards. NS-12: Software, models and AI/ML artifacts. Proposed. [nexustandards.com/standards/ns-12/](https://nexustandards.com/standards/ns-12/)
* 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-S10](https://nexustandards.com/standards/nrs/#nrs-s10): System profile: NXS-NET (Network topology and continuity). [nexustandards.com](https://nexustandards.com/standards/nrs/#nrs-s10)
* Nexus Standards. [NRS-S13](https://nexustandards.com/standards/nrs/#nrs-s13): System profile: NXS-NSF (Trust, authorization and assurance). [nexustandards.com](https://nexustandards.com/standards/nrs/#nrs-s13)
* Birkholz, H., Thaler, D., Richardson, M., Smith, N. and Pan, W. (2023). Remote ATtestation procedureS (RATS) Architecture. RFC 9334. IETF. [www.rfc-editor.org/rfc/rfc9334](https://www.rfc-editor.org/rfc/rfc9334)
* OpenSSF (2023). Supply-chain Levels for Software Artifacts (SLSA) specification v1.0. [slsa.dev/spec/v1.0](https://slsa.dev/spec/v1.0/)


---

# 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/nexus-osi.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.