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

# OVERVIEW

**Where this fits:** all six sectors · [the six pillars](/organization/programme.md) · the Nexus Consortium · the programme year · part landing.

**In brief.** This page is the landing of OVERVIEW. Operations describe designs in formation; nothing here is a deployment, a certification or a decision for a public authority.

{% hint style="info" %}
**Read with the current model (21 October 2026).** Operations holds the earlier operating layer: pillars, mechanisms, [Nexus Reports](/organization/programme/reports.md) guides, media, the forum and the networks. Read it with the current model: the six pillars ([Programme](/organization/programme.md)), the programme year ([The programme year](/organization/programme/the-programme-year.md)), [National Nexus](/organization/governance-in-operation/national-nexus.md) and its participation pillars ([Governance in operation](/organization/governance-in-operation.md)) and the systems by NXS code ([Systems](/organization/systems.md)). Risk practice follows ISO 31000 ([ISO, 2018](https://www.iso.org/standard/65694.html)). Everything here is in formation; the current service level is R0, information and enquiries ([Programme status](https://therisk.global/consortium/programme-status/)).
{% endhint %}

***

## Sources

1. ISO (2018). ISO 31000:2018 Risk management — Guidelines. Geneva: International Organization for Standardization. <https://www.iso.org/standard/65694.html>
2. How Nexus works. <https://therisk.global/nexus-cycle/>
3. Programme status. <https://therisk.global/consortium/programme-status/>
4. How Nexus Consortium works. <https://therisk.global/consortium/>


---

# 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/operations/overview.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.