> 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.md).

# ACCELERATION

Nexus acceleration for nationally controlled compute, innovation infrastructure, accelerator programs, startup pathways, and resilient technology deployment.

**Where this fits:** all six sectors · all six pillars · the Nexus Consortium · overview · see [The Model](https://docs.therisk.global/organization/model.md); [Programme](https://docs.therisk.global/organization/programme.md); [Systems](https://docs.therisk.global/organization/systems.md).

**In brief.** The Nexus Acceleration section defines how Nexus moves from architecture into implementation. It connects nationally controlled compute, innovation infrastructure, accelerator programs, technology deployment, and resilience-focused growth into one coordinated acceleration model. Acceleration describes designs in formation; nothing here records that a programme is running or a system is deployed. See the OECD recommendation on the governance of critical risks ([OECD 2014](https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405)).

<figure><picture><source srcset="https://2655483226-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEQtittnb4JJQ2YOtd2tk%2Fuploads%2Fgit-blob-1a51e756c178d8a73ee383d8677f142ef4e8c8be%2Fevidence-to-decision-dark.svg?alt=media" 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-328a50d456aab7583da4b132425f1d57a12c4e16%2Fevidence-to-decision-light.svg?alt=media" alt="Observatories capture a signal and structure it into an observation under Nexus Observatory Protocol. NXS-GRX holds it as governed evidence with quality and provenance, and an evidence review checks it. NXS-EWS may prepare a warning-support candidate and NXS-AAP a trigger check; NXS-DSS assembles a decision-support package. The NXS-NSF policy gate releases it, and NXS-RLS hands it off under written agreements. The competent authority alone decides and issues any warning; corrections return to the observatories."></picture><figcaption><p><strong>From observation to decision.</strong> Indicative material only, never an official warning; a design of the sequence, not a record of any run. Source: D-V3-0003 and D-V3-0004. As of 2026-10-20.</p></figcaption></figure>

<details>

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

| Element                   | Description                        | Connected to                                 |
| ------------------------- | ---------------------------------- | -------------------------------------------- |
| Signal captured           | Remote, in-situ or edge            | Observation                                  |
| Observation               | Under Nexus Observatory Protocol   | Signal captured; Governed evidence           |
| Governed evidence         | Quality and provenance             | Observation; Evidence review                 |
| Evidence review           | Checked before use                 | Governed evidence; Warning-support candidate |
| Warning-support candidate | NXS-EWS; never an alert            | Evidence review; Decision-support package    |
| Decision-support package  | NXS-DSS with NXS-AAP trigger check | Warning-support candidate; Policy gate       |
| Policy gate               | NXS-NSF release                    | Decision-support package; Lawful handoff     |
| Lawful handoff            | NXS-RLS under written agreements   | Policy gate; Decision                        |
| Decision                  | The authority alone decides        | Lawful handoff; Any warning issued           |
| Any warning issued        | By the authority, not by Nexus     | Decision                                     |

</details>

{% 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](https://docs.therisk.global/organization/systems/nxs-cor.md) and [NXS-NET](https://docs.therisk.global/organization/systems/nxs-net.md)); "Foundry" is the bare pillar word for the build work ([Systems](https://docs.therisk.global/organization/systems.md); [Foundry](https://docs.therisk.global/organization/programme/foundry.md)).
* 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](https://docs.therisk.global/organization/governance-in-operation/status-and-service-levels.md)).
* [Nexus Standards](https://docs.therisk.global/organization/institutions/nexus-standards.md) that bear on this page: [NS-0](https://nexustandards.com/standards/ns-0/) (constitution and principles). Their text and status on nexustandards.com govern.
  {% endhint %}

The **Nexus Acceleration** section defines how Nexus moves from architecture into implementation. It connects **nationally controlled compute**, **innovation infrastructure**, **accelerator programs**, **technology deployment**, and **resilience-focused growth** into one coordinated acceleration model.

This section is designed for governments, institutions, builders, and partners working on high-impact technology pathways. It explains how Nexus supports sovereign-scale infrastructure, accelerator programs, studio development, and applied innovation.

### What this section covers

* **Nationally controlled compute acceleration** for national, regional, and public-interest infrastructure.
* **Innovation acceleration** for frontier technologies, resilient systems, and public-good deployment.
* **Program acceleration** through fellowships, research, policy, media, and development tracks.
* **Studio and venture pathways** for application design, product development, and implementation readiness.
* **Accelerator models** for risk reduction, sustainability, and mission-aligned technology scaling.

### Core acceleration themes

* **Nationally controlled compute infrastructure** for secure, resilient, and locally grounded digital systems.
* **Technology acceleration** for AI, cyber, climate, communications, and systems innovation.
* **Innovation programs** that connect research, policy, media, and operations.
* **Deployment readiness** for real-world infrastructure, pilot programs, and implementation pathways.
* **Resilience and sustainability** as the operating logic behind scalable acceleration.

### Explore this section

* [OVERVIEW](https://docs.therisk.global/organization/acceleration/overview.md) - the top-level overview of Nexus acceleration.
* [SOVEREIGN COMPUTE](https://docs.therisk.global/organization/acceleration/nexus-compute.md) - the nationally controlled compute thesis, doctrine, architecture, and whole-of-chain model.
* [NEXUS PROGRAMS](https://docs.therisk.global/organization/acceleration/nexus-programs.md) - fellowship, research, DevOps, policy, media, and national working group tracks.
* [NXS-STU](https://docs.therisk.global/organization/acceleration/nexus-studio.md) - the studio layer for sector applications, product design, and implementation.
* [NEXUS ACCELERATORS](https://docs.therisk.global/organization/acceleration/accelerators.md) - the accelerator model for global risk, innovation, governance, and scaling impact.

The **Nexus Acceleration** page is the entry point for applied growth across Nexus. It connects nationally controlled compute, startup and studio pathways, accelerator programming, and deployment-ready innovation into one searchable framework.

## 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. Nexus Standards, NS-0: Constitution and principles. Status as published. <https://nexustandards.com/standards/ns-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/acceleration.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.
