> 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/ii.-architecture.md).

# II. Architecture

II. Architecture: 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 %}

<figure><picture><source srcset="/files/55Bz9e7JZSlqQTem6pOU" media="(prefers-color-scheme: dark)"><img src="https://2655483226-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEQtittnb4JJQ2YOtd2tk%2Fuploads%2Fgit-blob-2ac7d74f7c782da74ed3c42477bc40ea584b80c6%2Fnsf-architecture-layers-light.svg?alt=media" alt="The ten layers of the NXS-NSF Sovereignty Framework architecture, in the order of Part II. The Data Layer, described as the evidentiary foundation (sovereign data zones, provenance and compute-to-data), covers Sovereign Data Zones, Provenance metadata bundles, Data classification, Compute-to-data. The Compute Layer, described as the execution and verification substrate (governed rules run under controlled conditions), covers Governance-bound compute, Trusted execution, Clause-attested compute, Failure modes. The Governance Layer, described as governance as a protocol function (role-bound, versioned, correctionable), covers Governance objects, Quorum logic, Lifecycle governance, Disputes and failsafes. The Credential Layer, described as the identity, authority and role-binding fabric, covers Verifiable credentials, Decentralized identifiers, Revocation and status, Selective disclosure. The Clause Layer, described as the logic engine (Smart Clauses as atomic units of verifiable governance), covers Clause anatomy, Lifecycle and lineage, Jurisdictional forking, Clause testing. The Simulation Layer, described as foresight memory (simulation as a governance validation requirement), covers Simulation packages, Reproducible runners, Multi-scenario forecasting, Simulation-driven clause governance. The Communication Layer, described as the coordination substrate (invocation, events and risk communication), covers Secure invocation, Message integrity, Event types and routing, Public-safe message classes. The Audit Layer, described as real-time traceability and longitudinal risk memory, covers Audit records, Hash-linked audit chains, Review classes, Public and private streams. The Registry Layer, described as the memory graph (namespaces, status and relationships), covers Global Clause Registry, Clause IDs and versions, Fork lineage, Schema binding. The Interop Layer, described as institutional continuity (translating existing standards without replacing them), covers Standards parsing, Schema wrappers, Credential equivalence, Ontology and metadata mapping. Two concerns run through every layer page: each layer operates through the global, regional and national consortium architecture (GNC, RNC, NNC), and each closes with a boundary statement that it supports evidence, proof and correction but does not by itself create legal authority, approval or public warning."></picture><figcaption><p><strong>The NXS-NSF Sovereignty Framework architecture.</strong> A reading of the ten layer pages of Part II; a design for reading, not a record of any deployed system. The order is the Part's and implies no stacking. Source: Nexus Sovereignty, Part II (Architecture): the Data, Compute, Governance, Credential, Clause, Simulation, Communication, Audit, Registry and Interop Layer pages, their purpose, boundary and closing sections. As of 2026-10-21.</p></figcaption></figure>

<details>

<summary>Figure data (text alternative)</summary>

| Element                             | Description                                                                                                              |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Sovereign Data Zones                | Primary storage and control architecture                                                                                 |
| Provenance metadata bundles         | With canonical hash anchoring                                                                                            |
| Data classification                 | The control plane of sovereignty                                                                                         |
| Compute-to-data                     | Data mobility without extraction                                                                                         |
| Governance-bound compute            | Execution environments and compute profiles                                                                              |
| Trusted execution                   | Confidential computing, enclaves, zero-knowledge execution                                                               |
| Clause-attested compute             | A proof-bound record of each run                                                                                         |
| Failure modes                       | Safe execution                                                                                                           |
| Governance objects                  | With audit records                                                                                                       |
| Quorum logic                        | Decision thresholds                                                                                                      |
| Lifecycle governance                | Clauses, credential schemas, simulations                                                                                 |
| Disputes and failsafes              | Time-bounded emergency exceptions                                                                                        |
| Verifiable credentials              | The canonical credential format                                                                                          |
| Decentralized identifiers           | Identity types and governance                                                                                            |
| Revocation and status               | Suspension and live status                                                                                               |
| Selective disclosure                | Privacy-preserving presentations                                                                                         |
| Clause anatomy                      | Metadata and semantic integrity                                                                                          |
| Lifecycle and lineage               | Versioning and governance trace                                                                                          |
| Jurisdictional forking              | And override                                                                                                             |
| Clause testing                      | And formal verification                                                                                                  |
| Simulation packages                 | Anatomy and clause typology                                                                                              |
| Reproducible runners                | Execution environments                                                                                                   |
| Multi-scenario forecasting          | Risk surfacing                                                                                                           |
| Simulation-driven clause governance | Bound to clause-attested compute                                                                                         |
| Secure invocation                   | Interfaces for calling clauses                                                                                           |
| Message integrity                   | Verification of every message                                                                                            |
| Event types and routing             | Under rights and agent classes                                                                                           |
| Public-safe message classes         | Risk communication                                                                                                       |
| Audit records                       | Structured governance evidence                                                                                           |
| Hash-linked audit chains            | Integrity and zero-knowledge audit proofs                                                                                |
| Review classes                      | Dispute resolution and forensic query                                                                                    |
| Public and private streams          | With an audit anchor layer                                                                                               |
| Global Clause Registry              | The reference registry, within a federated system                                                                        |
| Clause IDs and versions             | Status and lifecycle resolution                                                                                          |
| Fork lineage                        | And jurisdiction mapping                                                                                                 |
| Schema binding                      | Simulations and credential schemas                                                                                       |
| Standards parsing                   | Smart Clause candidate generation                                                                                        |
| Schema wrappers                     | Data translation                                                                                                         |
| Credential equivalence              | Across standards                                                                                                         |
| Ontology and metadata mapping       | With version drift control                                                                                               |
| GNC, RNC and NNC architecture       | Every layer operates through the global, regional and national consortium architecture.                                  |
| Boundary statement                  | Every layer supports evidence, proof and correction; none by itself creates legal authority, approval or public warning. |

</details>

## 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/)
* W3C (2022). Decentralized Identifiers (DIDs) v1.0. W3C Recommendation, 19 July 2022. [www.w3.org/TR/did-core](https://www.w3.org/TR/did-core/)
* 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)


---

# 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/ii.-architecture.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.