> 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/regional-nexus-financing-for-development-rnfd.md). # Regional Nexus Financing for Development (RNFD) Regional Nexus Financing for Development (RNFD): part of the NXS-RLS interoperability profile, a Nexus Standards design in progress; nexustandards.com governs the standards it cites. **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.** F1.1 Mandate. 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 %} #### F1. One-Page Executive Brief F1.1 Mandate. RNFD is the regional operating discipline by which the RNC organizes cross-border financing-for-development readiness into execution-ready packages—lawful, auditable, competition-neutral, and sovereign-primacy preserving—and routes execution exclusively to properly licensed entities under applicable national law.\ F1.2 What RNFD unlocks. RNFD reduces transaction friction by standardizing Proof Packs, Verification Annexes, covenant modules, escrow/priority-of-payments specifications, and dispute clocks, thereby compressing diligence, strengthening enforceability posture, improving terms, and accelerating time-to-cash without expanding the RNC into a regulated executor.\ F1.3 What RNFD is. RNFD is an interoperability rail for readiness: it produces recorded determinations, documentary readiness, comparability discipline (where consented), controlled handling, and defensible publication through safe summaries.\ F1.4 What RNFD is not. RNFD is not a fund, lender, placement agent, insurer/reinsurer, underwriter, investment adviser, broker, custodian, escrow operator, payments operator, procurement authority, or market coordinator. All pricing, placement, custody, settlement, and claims occur only through licensed partners and national institutions.\ F1.5 Operating promise. RNFD does not promise outcomes; it promises disciplined readiness and validity—so that only gated, correctly labeled, correctly recorded outputs may be routed to money-in-motion.\ F1.6 What to do first (30/60/90).\ (a) Day 0–30: Constitute the governance spine; appoint the Records & Register Officer; execute safe-meeting and procurement-neutrality undertakings; stand up controlled repositories and distribution logs; open the first dockets and assign Case IDs.\ (b) Day 31–60: Activate the first instrument modules and Verification Annex library; execute partner MoUs for licensed execution pathways; complete national PFM/DMO and regulator crosswalks; pre-clear the first pilots for end-to-end routing or simulation.\ (c) Day 61–90: Run the first proof cycle; conduct a drill (readiness → verification → escrow/PoP simulation → corrections); issue the first publishable safe summary; certify the readiness scorecard level and permitted instruments.\ F1.7 Default first three lanes.\ (a) Contingent Liquidity lane: rapid draw capability linked to verification clocks and escrow/PoP patterns.\ (b) Guarantees/Credit Enhancement lane: portfolio and program credit support aligned to PFM/DMO controls and IFI co-financing.\ (c) Parametric/Index Program lane: multi-hazard programs with basis-risk governance and independent calc-agent rotation. *** #### F2. Intended Users F2.1 Regional leadership. Regional President, Secretariat, Hub/Lane Leads, Council Chairs, Records & Register Officer, second-line functions, and designated counsel/security escalation points.\ F2.2 National counterparts. Ministries of Finance, Debt Management Offices, line ministries, procurement authorities, regulators, statistical agencies, and critical-sector agencies operating within sovereign primacy.\ F2.3 Regulators and central banks. Users responsible for perimeter assurance, prudential considerations, market conduct, and licensed-execution routing expectations.\ F2.4 IFIs/MDBs/DFIs and donors. Users requiring fiduciary, safeguards, disbursement readiness, supervision hooks, and repeatable packaging across project/program/RBF modalities.\ F2.5 Markets. Investors, (re)insurers, intermediaries, and custodians requiring disclosure minima, verification annexes, covenants, dispute clocks, and bounded reliance language.\ F2.6 Operators and utilities. Users responsible for continuity, outage-linked metrics, feasibility constraints, monitoring obligations, and sensitive infrastructure handling.\ F2.7 Civil society, communities, and academia. Users admitted by handling class for protected participation, grievance/remedy, do-no-harm accountability, and safe-summary transparency. *** #### F3. How to Use This Framework F3.1 Modular and lane-driven. RNFD is applied by selecting an instrument lane, opening a docket, passing non-bypassable gates, assembling the Proof Pack and Verification Annexes, routing execution to licensed partners, and closing the loop through records reconciliation and corrections where required.\ F3.2 Lane selection. Lane choice is made using the instrument selection tree based on risk type, sector/corridor priority, fiscal posture, market capacity, regulator perimeter, and safeguards readiness.\ F3.3 Docket opening. Each lane activation begins with a Case ID, sector/corridor tags, handling class assignment, appointment of the lane lead and record owner, and declaration of applicable clocks.\ F3.4 Non-bypassable gates. Lawful basis, evidence integrity, safeguards, feasibility, market sensitivity, sanctions/export routing, and procurement neutrality gates are conditions precedent to any determination, authorization, execution routing, or publication.\ F3.5 Execution routing. Execution occurs only by licensed entities under national law, using RNFD’s standardized interfaces (escrow/PoP, covenants, monitoring schedules, verification hooks, dispute clocks).\ F3.6 Closure discipline. Each docket closes with completeness tests, distribution reconciliation, publishable safe summary (where permitted), and correction/retraction readiness preserved for the full retention period.\ F3.7 Deviations. Any deviation from the authoritative sequencing requires recorded justification, updated risk acceptance (if any), and approval per the Force-and-Effect Matrix. *** #### F4. Handling & Confidentiality F4.1 Controlled-by-default. Docket-linked artifacts are Controlled unless expressly reclassified through the release ladder and recorded by the Records & Register Officer.\ F4.2 Handling classes.\ (a) Public: approved for broad release; excludes market-sensitive, security-sensitive, or personally sensitive information.\ (b) Internal: limited to authorized members/staff; distribution logged; onward sharing restricted.\ (c) Controlled: limited to named recipients; access reviewed; watermarking as required; onward sharing prohibited absent written authorization.\ (d) Privileged: legally/regulatorily/security sensitive or integrity-sensitive; strict compartmentation; minimal distribution; full logging.\ F4.3 Most restrictive wins. Where multiple jurisdictions, counterparties, or regimes apply, the highest restriction governs access, storage, processing, and onward sharing.\ F4.4 Distribution logs. All Internal/Controlled/Privileged distributions are logged with recipient identity, purpose, timestamp, authority basis, record reference, and onward-sharing restrictions. *** #### F5. Definitions and Interpretive Rules F5.1 Defined terms govern. Capitalized terms carry the meanings in the Defined Terms Index, and reserved terms shall not be used outside their defined meanings.\ F5.2 Interpretive hierarchy. In the event of conflict: (a) governing charter and recognition/licensing instruments; (b) applicable national law and regulator requirements; (c) this RNFD instrument; (d) annexes; (e) templates and guidance.\ F5.3 Two glossaries. The plain-language glossary governs stakeholder communications; the technical glossary governs evidence, schema, verification, and system operations.\ F5.4 Reserved terms of art. “Decision-grade,” “determination,” “authorization,” “verification,” “calc-agent,” “facility,” “escrow,” “priority-of-payments (PoP),” “supported,” and “comparable” are controlled terms and trigger labeling and record rules when used. *** #### F6. Nexus Institutional Relationship Map F6.1 Two-stack alignment. RNFD operates within the Nexus dual-stack architecture: the governance-only public-good core produces standards, evidence integrity, validity discipline, safeguards, controlled handling, and correction clocks; the delivery stack performs all regulated and commercial execution through properly licensed entities.\ F6.2 Licensed-delivery boundary. The RNC coordinates readiness and documentation and routes execution; it does not conduct regulated activities unless separately licensed and explicitly authorized under applicable law.\ F6.3 National primacy preserved. National institutions retain authority for fiscal commitments, procurement, sovereign attribution, security constraints, and regulated market actions; RNFD provides opt-in standardization and corridor coordination without override. *** #### F7. Document Hierarchy and Primacy Rule F7.1 Primacy of law. National law and regulator requirements control within each jurisdiction and for each regulated activity.\ F7.2 Charter and license precedence. Charter provisions and recognition/licensing instruments control institutional roles, separation of duties, validity requirements, and enforcement posture.\ F7.3 Severability. RNFD modules are severable; an unlawful or impracticable module is marked “Not Applicable” for the affected jurisdiction or lane without impairing the remainder.\ F7.4 Conflict handling. Conflicts are recorded as Validity Incidents and resolved through correction and re-issuance under the change control rules. *** #### F8. Validity, Authority, and Change Control F8.1 Record classes. Outputs are classified as discussion artifacts, procedural decisions, determinations, authorizations, publishable summaries, and controlled annexes, each with mandatory labels and permitted reliance posture.\ F8.2 Force and effect. Only determinations and authorizations—correctly labeled, correctly approved, correctly recorded in the designated systems, and passing completeness tests—carry RNFD force and effect.\ F8.3 Approval authorities. Approval authority is role-based and lane-specific; external-facing authorizations and designated matters require multi-key minimums per the Force-and-Effect Matrix.\ F8.4 No silent edits. Changes require version increment, change log entry, distribution reconciliation, and re-issuance where required; superseded artifacts remain available for audit with clear supersession notices.\ F8.5 Correction clocks. Material errors, omissions, mislabeling, mishandling, or integrity incidents trigger mandatory correction clocks and may require retraction, re-issuance, and recipient notifications.\ F8.6 Deprecation. Deprecated schemas/templates remain accessible for audit and legacy interpretation but are prohibited for new dockets after the deprecation date absent recorded exception authority. *** #### F9. Reliance, Liability, and Non-Endorsement F9.1 No advice. RNFD artifacts are governance and readiness documents and do not constitute legal, regulatory, investment, underwriting, procurement, or placement advice.\ F9.2 Bounded reliance only. Reliance is permitted only where expressly stated in the relevant Proof Pack or Verification Annex, and only for the stated purpose, scope, duration, and handling class.\ F9.3 No endorsement. References to instruments, entities, service providers, or counterparties do not constitute endorsement, ranking, preferred status, or procurement steering.\ F9.4 Licensed execution only. Issuance, placement, underwriting, custody, escrow operations, payments, settlement, and claims are performed only by appropriately licensed entities under national law.\ F9.5 Limitation posture. Liability is limited to the maximum extent permitted by law; remedies run through the correction, breach, and dispute mechanisms applicable to the relevant instrument and record class. *** #### F10. Competition/Antitrust and Procurement Neutrality F10.1 Safe-meeting discipline. Convenings operate under safe-meeting scripts; prohibited topics include prices, spreads, commissions, allocations, bid strategies, competitor-sensitive plans, and any market coordination outside approved controlled rooms and lawful channels.\ F10.2 Procurement neutrality. RNFD specifies requirements, interfaces, and quality thresholds; it does not select vendors, steer competitions, confer preferred status, or influence commercial outcomes.\ F10.3 No market coordination. RNFD shall not be used to coordinate market behavior, to create preferential access, or to distort pricing through collusion, signaling, or exclusivity.\ F10.4 Escalation. Suspected competition or procurement breaches trigger stop-the-line authority, validity incident logging, and counsel routing. *** #### F11. Records Retention and Preservation Schedule F11.1 Retention by class. Governance decisions, determinations, authorizations, Proof Packs, Verification Annexes, distribution logs, correction/retraction logs, dispute records, and audit artifacts are retained by record class for the prescribed period and preserved for admissibility and audit defensibility.\ F11.2 Immutability. Determinations, authorizations, correction/retraction records, and distribution logs are preserved in tamper-evident form; access and retrieval are logged.\ F11.3 Holds override disposal. Litigation, investigation, and regulatory holds override disposal rules and are recorded by scope, authority, and duration.\ F11.4 Disposal discipline. Disposal requires recorded authorization, confirmation of hold status, and secure deletion appropriate to handling class. *** #### F12. Reader Pathways (“Start Here” Maps) F12.1 Minister/DMO lane. Fiscal risk posture, contingent liability governance, authorization pathways, guarantee and debt registers, appropriation alignment, disclosure posture, and debt-clause interfaces.\ F12.2 Regulator/Central Bank lane. Regulatory perimeter mapping, prudential considerations, market conduct controls, inside-information handling, and licensed execution routing discipline.\ F12.3 IFI/MDB lane. Project/program/RBF alignment, fiduciary and safeguards compatibility, disbursement readiness packaging, supervision hooks, and reporting crosswalks.\ F12.4 Investor/Insurer lane. Disclosure minima, verification annexes, covenants, dispute clocks, PoP/escrow patterns, refresh cadence, and bounded reliance language.\ F12.5 Operator/Utility lane. Continuity requirements, feasibility routing, outage-linked metrics, performance covenants, monitoring obligations, and sensitive infrastructure rules.\ F12.6 Safeguards/Community lane. Protected participation, non-retaliation, grievance and remedy clocks, do-no-harm gates, knowledge protection, and escalation pathways.\ F12.7 Secretariat/Records lane. Case ID issuance, completeness tests, distribution logs, validity statements, correction/retraction workflows, and audit pack assembly. *** #### F13. Quick Reference Maps F13.1 Role separation map. A single view of permitted and prohibited acts across the public-good core, the delivery stack, the RNC delivery layer, national stacks, and licensed execution partners, including prohibited overlaps and mandatory recusal triggers.\ F13.2 Where-to-record-what map. Authoritative routing by record class: Register entries; ledger anchoring where designated; controlled repository storage; publishable safe summary routing; and distribution log requirements.\ F13.3 Escalation ladder. Escalation paths for safeguards incidents, security incidents, legal/perimeter issues, validity incidents, market sensitivity breaches, and dispute escalation from national to regional to global.\ F13.4 Glossary of clocks. Decision clocks, correction clocks, dispute clocks, publication clocks, emergency sunset clocks, and audit remediation clocks, including mandatory start/stop triggers and closure criteria.\ F13.5 Critical-sector map. Sector and corridor dependency map, cascade pathways, continuity priorities, and lane eligibility guidance by sector. *** #### F14. Indexes F14.1 Template index. Templates indexed by lane, record class, handling class, required approvals, and required minimum fields.\ F14.2 Annex index. Annexes indexed by function: financial model, legal archetypes, proof packs, integrity controls, safeguards, security, cross-region protocols, regulatory overlays, conformance and certification, and crosswalks.\ F14.3 Instrument shelf index. Instruments indexed by eligibility, required Proof Pack modules, Verification Annexes, covenant modules, dispute clocks, and execution pathway archetypes.\ F14.4 Regulatory overlay index. Modular overlays indexed for securities/capital markets, banking/prudential, insurance/reinsurance, AML/CFT and sanctions, cyber/operational resilience, privacy/data protection, procurement/public integrity, and civic space/safeguarding.\ F14.5 Crosswalk index. Crosswalks aligning RNFD artifacts to IFI/MDB cycles, national PFM/DMO processes, safeguards systems, disclosure standards, and reporting packages. ## Sections This chapter is split into 34 sections, each on its own page; nothing was removed. | # | Section | | -- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | [Part 1 — Regional Purpose and Why the Regional Layer Exists](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/01-part-1-regional-purpose-and-why-the-regional-layer-exists.md) | | 2 | [Part 2 — System Architecture: One Rail, Two Stacks, Regional Execution Perimeter](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/02-part-2-system-architecture-one-rail-two-stacks-regional-execution-peri.md) | | 3 | [Part 3 — Regional Consortium Constitution, Licensing, and Participation Types](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/03-part-3-regional-consortium-constitution-licensing-and-participation-ty.md) | | 4 | [Part 4 — Regional Governance Spine: Councils, Records, and Decision Validity](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/04-part-4-regional-governance-spine-councils-records-and-decision-validit.md) | | 5 | [Part 5 — Regional Financing Mandate: What the Region Can Enable](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/05-part-5-regional-financing-mandate-what-the-region-can-enable.md) | | 6 | [Part 6 — Regional Facility Architecture: The Regional Nexus Financing Facility (RNFF)](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/06-part-6-regional-facility-architecture-the-regional-nexus-financing-fac.md) | | 7 | [Part 7 — Regional Revenue Model, Contributions, and Mathematical Soundness](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/07-part-7-regional-revenue-model-contributions-and-mathematical-soundness.md) | | 8 | [Part 8 — Regional Instrument Shelf: Products the Region Can Offer (Through Licensed Execution)](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/08-part-8-regional-instrument-shelf-products-the-region-can-offer-through.md) | | 9 | [Part 9 — Evidence-to-Capital Standards at Regional Level](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/09-part-9-evidence-to-capital-standards-at-regional-level.md) | | 10 | [Part 10 — Market Integrity: Competition, Procurement Neutrality, Anti-Capture](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/10-part-10-market-integrity-competition-procurement-neutrality-anti-captu.md) | | 11 | [Part 11 — Safeguards: Protecting People and Trust Region-Wide](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/11-part-11-safeguards-protecting-people-and-trust-region-wide.md) | | 12 | [Part 12 — Security, Data Sovereignty, and Controlled Handling](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/12-part-12-security-data-sovereignty-and-controlled-handling.md) | | 13 | [Part 13 — Diligence Room, Deal Packaging, and Investor/IFI Readiness](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/13-part-13-diligence-room-deal-packaging-and-investor-ifi-readiness.md) | | 14 | [Part 14 — Multilateral and Regional Institutional Integration](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/14-part-14-multilateral-and-regional-institutional-integration.md) | | 15 | [Part 15 — Regional Operating Rhythm and Proof Cycle](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/15-part-15-regional-operating-rhythm-and-proof-cycle.md) | | 16 | [Part 16 — Implementation Plan: 30/60/90 and 2026–2028 Scale](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/16-part-16-implementation-plan-30-60-90-and-2026-2028-scale.md) | | 17 | [Part 17 — Training, Accreditation, and Regional Talent Pipeline](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/17-part-17-training-accreditation-and-regional-talent-pipeline.md) | | 18 | [Part 18 — Regional Risk Management, Continuity, and Preservation](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/18-part-18-regional-risk-management-continuity-and-preservation.md) | | 19 | [Part 19 — Cross-Region Interfaces and Joint Docket Protocol](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/19-part-19-cross-region-interfaces-and-joint-docket-protocol.md) | | 20 | [Part 20 — Legal, Tax, and Accounting Defensibility Pack](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/20-part-20-legal-tax-and-accounting-defensibility-pack.md) | | 21 | [Part 21 — Templates and Tools (Regional Ready-to-Use Library)](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/21-part-21-templates-and-tools-regional-ready-to-use-library.md) | | 22 | [Annex A — Regional Financial Model Workbook (Unit Economics + Stress Tests)](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/22-annex-a-regional-financial-model-workbook-unit-economics-stress-tests.md) | | 23 | [Annex B — RNFF Legal Archetypes Pack](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/23-annex-b-rnff-legal-archetypes-pack.md) | | 24 | [Annex C — Regional Instrument Shelf Library (Term Sheets + Covenants)](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/24-annex-c-regional-instrument-shelf-library-term-sheets-covenantsand-x20.md) | | 25 | [Annex D — Regional Proof Pack Standard (Finance-Facing Modules)](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/25-annex-d-regional-proof-pack-standard-finance-facing-modulesand-x20.md) | | 26 | [Annex E — Comparability Rulebook (Supported vs Comparable)](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/26-annex-e-comparability-rulebook-supported-vs-comparable.md) | | 27 | [Annex F — Integrity Controls Pack (Competition, Procurement, Anti-Capture)](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/27-annex-f-integrity-controls-pack-competition-procurement-anti-capturean.md) | | 28 | [Annex G — Safeguards Pack (People and Trust)](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/28-annex-g-safeguards-pack-people-and-trust.md) | | 29 | [Annex H — Security and Controlled Handling Pack](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/29-annex-h-security-and-controlled-handling-pack.md) | | 30 | [Annex I — Joint Docket Protocol Pack (Cross-Region)](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/30-annex-i-joint-docket-protocol-pack-cross-region.md) | | 31 | [Annex J — Regulatory Overlay Registry Pack (Modular Regional Adoptions)](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/31-annex-j-regulatory-overlay-registry-pack-modular-regional-adoptions.md) | | 32 | [Annex K — Conformance and Certification Pack](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/32-annex-k-conformance-and-certification-pack.md) | | 33 | [Annex L — Crosswalk Pack (IFI/MDB + National Systems)](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/33-annex-l-crosswalk-pack-ifi-mdb-national-systems.md) | | 34 | [Closing](/organization/standardization/nexus-rail/regional-nexus-financing-for-development-rnfd/34-closing.md) | ## 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/) * Birkholz, H., Thaler, D., Richardson, M., Smith, N. and Pan, W. (2023). Remote ATtestation procedureS (RATS) Architecture. RFC 9334. IETF. [www.rfc-editor.org/rfc/rfc9334](https://www.rfc-editor.org/rfc/rfc9334) * FATF (2012–2025). International Standards on Combating Money Laundering and the Financing of Terrorism and Proliferation (the FATF Recommendations), as updated. Paris: FATF. [www.fatf-gafi.org/en/publications/Fatfrecommendations/Fatf-recommendations.html](https://www.fatf-gafi.org/en/publications/Fatfrecommendations/Fatf-recommendations.html) * GovStack Initiative (ITU, Estonia, Germany, Digital Impact Alliance) (2020–). GovStack building-block specifications. [www.govstack.global](https://www.govstack.global/) * Basel Committee on Banking Supervision (2022). Principles for the effective management and supervision of climate-related financial risks. Basel: BIS, 15 June 2022. [www.bis.org/bcbs/publ/d532.htm](https://www.bis.org/bcbs/publ/d532.htm) * ISO (2018). ISO 31000:2018 Risk management — Guidelines. Geneva: International Organization for Standardization. [www.iso.org/standard/65694.html](https://www.iso.org/standard/65694.html) * ISO (2019). ISO 22301:2019 Security and resilience — Business continuity management systems — Requirements. Geneva: ISO. [www.iso.org/standard/75106.html](https://www.iso.org/standard/75106.html) * World Bank and GFDRR. Disaster Risk Financing and Insurance Program; Global Risk Financing Facility; Financial Protection Forum. [www.financialprotectionforum.org](https://www.financialprotectionforum.org/) * OECD (2018). OECD DAC Blended Finance Principles for Unlocking Commercial Finance for the Sustainable Development Goals. Paris: OECD, December 2018. [www.oecd.org/en/publications/2018/12/oecd-dac-blended-finance-principles\_898d3549.html](https://www.oecd.org/en/publications/2018/12/oecd-dac-blended-finance-principles_898d3549.html) --- # 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/regional-nexus-financing-for-development-rnfd.md?ask=&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.