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

# NEXUS RAIL

**Where this fits:** all six sectors · [the Standards pillar](/organization/programme/standards.md) and [Finance readiness](/organization/finance-readiness.md) · [NXS-RLS](/organization/systems/nxs-rls.md) (participants, agreements, protocols and lawful handoffs) · The Global Risks Alliance (GRA) for finance readability · interoperability profile.

**In brief.** This page is part of the NXS-RLS interoperability profile. This page belongs to the NXS-RLS interoperability profile, a [Nexus Standards](/organization/institutions/nexus-standards.md) design in progress whose governing texts are published on [nexustandards.com](https://nexustandards.com/standards/) ([CPMI and IOSCO, 2012](https://www.bis.org/cpmi/publ/d101.htm); [FSB, 2020](https://www.fsb.org/2020/10/enhancing-cross-border-payments-stage-3-roadmap/); [ISO 20022](https://www.iso20022.org/)). The rail is an interoperability and readiness profile: it is not a fund, a lender, a payment system or an executor, and every regulated activity rests with licensed actors under their own law. Readiness evidence is not a financing decision.

{% hint style="info" %}
**Read with the current model.** Read this part as an interoperability profile for evidence and readiness records that finance, insurance and public-finance actors can rely on under bounded terms. Rail as a system is [NXS-RLS](/organization/systems/nxs-rls.md). National, regional and universal financing structures (NFD, RNFD, UNFSD) are structures that competent, lawful actors may form outside the programme, under their own law and licences; the programme never forms, arranges, owns or advises on them (see [Lawful handoffs](/organization/finance-readiness/lawful-handoffs.md)). Technology and service providers are described by role only. Messaging and payment networks are not compared or ranked; the profile maps to their standards (ISO 20022) instead.
{% endhint %}

***

## Sources

* 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. [NRS-S18](https://nexustandards.com/standards/nrs/#nrs-s18): System profile: NXS-RLS (Participants, agreements and handoffs). [nexustandards.com](https://nexustandards.com/standards/nrs/#nrs-s18)
* CPMI and IOSCO (2012). Principles for financial market infrastructures. Basel: Bank for International Settlements. [www.bis.org/cpmi/publ/d101.htm](https://www.bis.org/cpmi/publ/d101.htm)
* Financial Stability Board (2020). Enhancing Cross-border Payments: Stage 3 roadmap. Basel: FSB, 13 October 2020. [www.fsb.org/2020/10/enhancing-cross-border-payments-stage-3-roadmap](https://www.fsb.org/2020/10/enhancing-cross-border-payments-stage-3-roadmap/)
* ISO 20022 Registration Authority. ISO 20022 — Universal financial industry message scheme. [www.iso20022.org](https://www.iso20022.org/)


---

# 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-rail.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.