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

# SYSTEMS

The twenty Nexus systems as systems: what each does, how they connect, the areas they serve and the boundaries that govern them.

**Where this fits:** all six sectors · all six pillars, above all the Foundry pillar, where systems are built, simulated and prepared · the Nexus Consortium · systems reference.

**In brief.** The programme runs on twenty systems, each named by its [Nexus Standards](/organization/institutions/nexus-standards.md) display code ([NXS-CMD](/organization/systems/nxs-cmd.md) to [NXS-NSF](/organization/systems/nxs-nsf.md)) and a registered descriptor. A system is a bounded set of functions, records and interfaces, defined by what it receives, what it produces and which other systems it depends on. It is not a product, a service offer or a deployment. This part documents the systems as a target architecture for reading: their purpose and context, their rooms and areas, their inputs and outputs, their interfaces, the standards that apply to them, their role in the six sectors and the six pillars, and the governance boundaries that hold for all of them.

{% hint style="warning" %}
**Status.** These pages describe designs. Nothing here records that a system is deployed, in production use or offered as a service, and no readiness level is claimed. Technology, infrastructure and service providers work with the Nexus Consortium at arm's length under written agreements; they are described by role only.
{% endhint %}

## The twenty systems

Each system has a Nexus Standards display code and a registered descriptor. NXS-NSF (trust, authorization, mandate, policy and assurance) spans every layer. The systems are arranged in six layers, from command and decision at the top to delivery and work at the base; a decision case in [NXS-DSS](/organization/systems/nxs-dss.md), for example, draws on governed evidence in [NXS-GRX](/organization/systems/nxs-grx.md), which in turn holds observations from [NXS-EOP](/organization/systems/nxs-eop.md) (earth observation and digital twins) and [NXS-OPS](/organization/systems/nxs-ops.md) (instruments, sensors and calibration).

<figure><picture><source srcset="/files/qEOcIDsZyjeLw6FamoqN" 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-911614103bef9b094fe024bae6562f6f74e17a92%2Fnexus-twenty-systems-light.svg?alt=media" alt="The twenty canonical systems in six layers, with their registered descriptors. Command and decision: NXS-CMD, NXS-NST, NXS-DSS, NXS-EWS, NXS-AAP. Data and intelligence: NXS-GRX, NXS-EOP. Observation and signals: NXS-OPS, NXS-SIG. Compute and network: NXS-COR, NXS-NET. Build and software: NXS-FAC, NXS-STU, NXS-NXQ, NXS-APP. Delivery and work: NXS-HUB, NXS-POR, NXS-RLS, NXS-LAB. NXS-NSF, trust, authorization, mandate, policy and assurance, spans every layer."></picture><figcaption><p><strong>The twenty Nexus systems.</strong> Target architecture as documented in the V3 constitutional set; a design for reading, not a record of any deployed system. Names and descriptors from the name register; release is on hold. Source: D-V3-0003 and the name register (NS-16). As of 2026-10-21.</p></figcaption></figure>

<details>

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

| Element | Description                                                                 |
| ------- | --------------------------------------------------------------------------- |
| NXS-CMD | Integrated posture, mission and portfolio intelligence, executive synthesis |
| NXS-NST | Civilian common operating picture, incidents and coordination               |
| NXS-DSS | Decision cases, scenarios, options and deliberation                         |
| NXS-EWS | Multi-hazard monitoring, impact forecasting and warning support             |
| NXS-AAP | Anticipatory-action frameworks, triggers and readiness                      |
| NXS-GRX | Canonical data, provenance, risk and federation                             |
| NXS-EOP | Earth observation, imagery, terrain and observational digital twins         |
| NXS-OPS | Physical instruments, sensors, calibration and primary observation evidence |
| NXS-SIG | Authorized signal, spectrum, timing and PNT integrity                       |
| NXS-COR | Compute, nodes, runtimes, placement and infrastructure lifecycle            |
| NXS-NET | Network topology, connectivity and communications continuity                |
| NXS-FAC | Blueprints, builds, verification, signing and assembly                      |
| NXS-STU | Visual composition, dashboards, forms and workflow experiences              |
| NXS-NXQ | Software, packages, models, agents and capability lifecycle                 |
| NXS-APP | Application catalogue, installation, health and lifecycle                   |
| NXS-HUB | Institutional knowledge, records, collaboration, learning and support       |
| NXS-POR | Public, citizen, client, regulator, partner and developer delivery          |
| NXS-RLS | Participants, agreements, protocols, obligations and lawful handoffs        |
| NXS-LAB | Research, experiments, simulations and frontier-technology evaluation       |
| NXS-NSF | Trust, authorization, mandate, policy and assurance, for every layer.       |

</details>

| System  | What it does                                                                |
| ------- | --------------------------------------------------------------------------- |
| NXS-CMD | Integrated posture, mission and portfolio intelligence, executive synthesis |
| NXS-NST | Civilian common operating picture, incidents and coordination               |
| NXS-DSS | Decision cases, scenarios, options and deliberation                         |
| NXS-COR | Compute, nodes, runtimes, placement and infrastructure lifecycle            |
| NXS-NXQ | Software, packages, models, agents and capability lifecycle                 |
| NXS-GRX | Canonical data, provenance, risk and federation                             |
| NXS-EOP | Earth observation, imagery, terrain and observational digital twins         |
| NXS-EWS | Multi-hazard monitoring, impact forecasting and warning support             |
| NXS-AAP | Anticipatory-action frameworks, triggers and readiness                      |
| NXS-NET | Network topology, connectivity and communications continuity                |
| NXS-OPS | Physical instruments, sensors, calibration and primary observation evidence |
| NXS-SIG | Authorized signal, spectrum, timing and PNT integrity                       |
| NXS-NSF | Trust, authorization, mandate, policy and assurance                         |
| NXS-HUB | Institutional knowledge, records, collaboration, learning and support       |
| NXS-STU | Visual composition, dashboards, forms and workflow experiences              |
| NXS-FAC | Blueprints, builds, verification, signing and assembly                      |
| NXS-APP | Application catalogue, installation, health and lifecycle                   |
| NXS-RLS | Participants, agreements, protocols, obligations and lawful handoffs        |
| NXS-POR | Public, citizen, client, regulator, partner and developer delivery          |
| NXS-LAB | Research, experiments, simulations and frontier-technology evaluation       |

Names and descriptors are generated from the name register; they record names, not readiness.

## The Nexus of Observatories

"Nexus Observatory" names a capability and a protocol, never a company. Every Nexus platform and system includes its own observatory capability, covering remote sensing, in-situ instruments and edge deployments. Across every area where these observatories are implemented, including implementation pilots in programme areas, they form the Nexus of Observatories, part of the not-for-profit programme architecture. Nexus Observatory Protocol is the observation protocol owned by NXS-OPS, in collaboration with NXS-EOP and [NXS-SIG](/organization/systems/nxs-sig.md) (signal, spectrum, timing and PNT).

<figure><picture><source srcset="/files/vM71YbpRRgXON5iHDXL8" 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-715d1f97f97775c649d0bb92fffdfcdfdb8eac7f%2Fnexus-of-observatories-light.svg?alt=media" alt="Every Nexus platform and system includes its own observatory capability. Remote sensing through NXS-EOP, in-situ instruments and observatory nodes through NXS-OPS, edge deployments on NXS-COR and NXS-NET, and authorized signals through NXS-SIG all follow Nexus Observatory Protocol, owned by NXS-OPS. Across every area where they are implemented, including implementation pilots in programme areas, these observatories form the Nexus of Observatories in the not-for-profit programme architecture. Their observations become governed evidence in NXS-GRX, pass the NXS-NSF policy gate, and reach competent authorities as evidence only. The name never denotes a company."></picture><figcaption><p><strong>The Nexus of Observatories.</strong> A target design for reading, not a record of any installed observatory or run; "Nexus Observatory" names a capability and a protocol, never a company. Source: Owner ruling OQ-08 (third revision) and D-V3-0003. As of 2026-10-20.</p></figcaption></figure>

<details>

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

| Element                    | Description                                                                           | Connected to                                                                                                                                                              |
| -------------------------- | ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Nexus of Observatories     | Every platform's observatory capability, together, in the not-for-profit architecture | Nexus Observatory Protocol; Remote sensing; In-situ instruments; Edge deployments; Signals and spectrum; Platform observatories; Implementation pilots; Governed evidence |
| Nexus Observatory Protocol | Owned by NXS-OPS, with NXS-EOP and NXS-SIG                                            | Nexus of Observatories                                                                                                                                                    |
| Remote sensing             | NXS-EOP: Earth observation, geospatial and digital twins                              | Nexus of Observatories                                                                                                                                                    |
| In-situ instruments        | NXS-OPS observatory nodes and their environments                                      | Nexus of Observatories                                                                                                                                                    |
| Edge deployments           | NXS-COR and NXS-NET at the edge                                                       | Nexus of Observatories                                                                                                                                                    |
| Signals and spectrum       | NXS-SIG: authorized signal and communications integrity                               | Nexus of Observatories                                                                                                                                                    |
| Platform observatories     | One observatory capability in each Nexus platform and system                          | Nexus of Observatories                                                                                                                                                    |
| Implementation pilots      | Pilots in programme areas, run under written agreements                               | Nexus of Observatories                                                                                                                                                    |
| Governed evidence          | NXS-GRX: quality and provenance                                                       | Nexus of Observatories; Policy gate                                                                                                                                       |
| Policy gate                | NXS-NSF: identity, policy and access decisions                                        | Governed evidence; Competent authorities                                                                                                                                  |
| Competent authorities      | Decide; receive evidence only                                                         | Policy gate                                                                                                                                                               |

</details>

## From observation to decision

Observations become governed evidence; decision support is indicative; the competent authority alone decides and issues any warning.

<figure><picture><source srcset="/files/W4ykxuEifvmSaWBJizyj" 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>

## Read further

* [The Model](/organization/model.md): the six sectors and six pillars the systems serve.
* [The Foundry pillar](/organization/programme/foundry.md): where the systems are built, simulated and prepared in the programme year.
* [Nexus Standards](/organization/standards.md): the standards that identify, describe and govern the systems' records.
* [Start here](/organization/introduction/start-here.md): status in plain words.


---

# 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/systems.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.