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

# NXS-STU

**Where this fits:** the sectors each studio serves · the Labs and Foundry pillars · the Nexus Consortium · programme design (sector studios) · see [Use by](/organization/use-by.md); [The Model: sectors](/organization/model/sectors.md); [Systems](/organization/systems.md).

**In brief.** This part sets out the sector studios: what the Nexus model and its systems offer each sector audience. A studio is a design area of this documentation for a sector audience; it is not a product, a service offer or a body with authority. Each studio speaks to a sector audience in the terms of the OECD recommendation on critical risks ([OECD 2014](https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405)) and the Sendai Framework ([UN General Assembly 2015](https://www.undrr.org/publication/sendai-framework-disaster-risk-reduction-2015-2030)).

{% hint style="info" %}
**Read with the current model (2026-10-21).**

* Technology is described as the twenty Nexus systems by their NXS codes (for compute and networks, [NXS-COR](/organization/systems/nxs-cor.md) and [NXS-NET](/organization/systems/nxs-net.md)); "Foundry" is the bare pillar word for the build work ([Systems](/organization/systems.md); [Foundry](/organization/programme/foundry.md)).
* Technology and service providers are described by role only, as external providers at arm's length under written agreements.
* Everything described here is in formation: no national, regional or global programme is recorded as constituted or active, and the current service level is R0, information and enquiries ([Status and service levels](/organization/governance-in-operation/status-and-service-levels.md)).
* [Nexus Standards](/organization/institutions/nexus-standards.md) that bear on this page: [NS-4](https://nexustandards.com/standards/ns-4/) (structure and drafting of nexus standards and documents), [NS-11](https://nexustandards.com/standards/ns-11/) (verification and monitoring). Their text and status on nexustandards.com govern.
  {% endhint %}

***

## Sources

External sources and standards cited in the In brief and the note above. The text below keeps its own internal references.

1. OECD (2014). Recommendation of the Council on the Governance of Critical Risks. OECD/LEGAL/0405, adopted 6 May 2014. <https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405>
2. UN General Assembly (2015). Sendai Framework for Disaster Risk Reduction 2015–2030. A/RES/69/283, 3 June 2015. <https://www.undrr.org/publication/sendai-framework-disaster-risk-reduction-2015-2030>
3. Nexus Standards, NS-4: Structure and drafting of nexus standards and documents. Status as published. <https://nexustandards.com/standards/ns-4/>
4. Nexus Standards, NS-11: Verification and monitoring. Status as published. <https://nexustandards.com/standards/ns-11/>


---

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