> 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-sovereignty/i.-foundations.md).

# I. Foundations

I. Foundations: part of the NXS-NSF Sovereignty Framework, a Nexus Standards design in progress; nexustandards.com governs the standards it cites.

**Where this fits:** all six sectors · [the Standards pillar](/organization/programme/standards.md), with [the Foundry pillar](/organization/programme/foundry.md) where systems are built · [NXS-NSF](/organization/systems/nxs-nsf.md) (trust, authorization, mandate, policy and assurance) · [Nexus Standards](/organization/institutions/nexus-standards.md) · protocol specification.

**In brief.** This page is part of the NXS-NSF Sovereignty Framework (NSF). This page belongs to the NXS-NSF Sovereignty Framework (NSF), a Nexus Standards design in progress whose governing texts are published on [nexustandards.com](https://nexustandards.com/standards/) ([W3C, 2025](https://www.w3.org/TR/vc-data-model-2.0/); [UN Office of the Secretary-General's Envoy on Technology, 2024](https://www.dpi-safeguards.org/)). A validator report is evidence for review, not a conformance claim; adoption of any standard is final for each jurisdiction, and no global body holds a veto.

{% hint style="info" %}
**Read with the current model.** **NSF** in this part names the `Nexus Sovereignty Framework`, a design for verifiable, policy-bound execution. It is implemented by the [NXS-NSF](/organization/systems/nxs-nsf.md) system and specified through Nexus Standards; it is not an institution, a foundation or a standards body. Nexus Standards, governed by the Global Standards Council with [The Global Centre for Risk and Innovation](/organization/institutions/gcri.md) (GCRI) Canada as secretariat and publisher of record, develops the standards, and [nexustandards.com](https://nexustandards.com/standards/) governs their text and status. Where this part names an external body (ISO, IEC, ITU, WHO, FATF and others), it describes Nexus alignment work with that body's published texts; it is not a proposal to, a submission to or an endorsement by that body. Earlier wording about DAOs, automatic enforcement, payouts or official signers is read as the boundary-safe governance and evidence functions the page now sets out. Everything here is a design in formation (programme service level R0); nothing records a deployment or a certification.
{% endhint %}

## Sources

* Nexus Standards. NS-0: Constitution and principles. Proposed. [nexustandards.com/standards/ns-0/](https://nexustandards.com/standards/ns-0/)
* Nexus Standards. NS-10: Policies and clauses. Proposed. [nexustandards.com/standards/ns-10/](https://nexustandards.com/standards/ns-10/)
* Nexus Standards. NS-11: Verification and monitoring. Proposed. [nexustandards.com/standards/ns-11/](https://nexustandards.com/standards/ns-11/)
* Nexus Standards. NS-14: Conformance and crosswalk to external standards. Proposed. [nexustandards.com/standards/ns-14/](https://nexustandards.com/standards/ns-14/)
* Nexus Standards. NS-16: UNI application profile (articles, documents, code, data, APIs, interfaces). Proposed. [nexustandards.com/standards/ns-16/](https://nexustandards.com/standards/ns-16/)
* 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)
* W3C (2025). Verifiable Credentials Data Model v2.0. W3C Recommendation, 15 May 2025. [www.w3.org/TR/vc-data-model-2.0](https://www.w3.org/TR/vc-data-model-2.0/)
* UN Office of the Secretary-General's Envoy on Technology and UNDP (2024). Universal DPI Safeguards Framework. New York: United Nations, September 2024. [www.dpi-safeguards.org](https://www.dpi-safeguards.org/)


---

# 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-sovereignty/i.-foundations.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.