> 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/cooperation/consortiums/model/i.-identity/1.4-one-rail-two-stacks-three-levels-global-regional-national.md).

# 1.4 One Rail, Two Stacks, Three Levels: Global, Regional, National

Identity: One Rail, Two Stacks, Three Levels: Global, Regional, National. Nexus consortium model, read with the current model.

**Part of** [I. IDENTITY](https://docs.therisk.global/organization/cooperation/consortiums/model/i.-identity.md) · section 4 of 11 · previous: [1.3 Nexus Consortiums as the Agenda Engine for Nexus Ecosystem, Nexus Standards, Nexus Acceleration, and Nexus Universe](https://docs.therisk.global/organization/cooperation/consortiums/model/i.-identity/1.3-nexus-consortiums-as-the-agenda-engine-for-nexus-ecosystem-n.md) · next: [1.5 Public-Good Coordination Without Enterprise or Public Authority Substitution](https://docs.therisk.global/organization/cooperation/consortiums/model/i.-identity/1.5-public-good-coordination-without-enterprise-or-public-author.md)

**Where this fits:** all six sectors ([The Model](https://docs.therisk.global/organization/model.md)) · [Nexus Universe](https://docs.therisk.global/organization/programme/universe.md), [Nexus Standards](https://docs.therisk.global/organization/programme/standards.md), [Nexus Reports](https://docs.therisk.global/organization/programme/reports.md), [Risk Academy](https://docs.therisk.global/organization/programme/academy.md) · the Nexus Consortium, stewarded by The Global Centre for Risk and Innovation (GCRI), The Global Risks Forum (GRF) and The Global Risks Alliance (GRA); global, regional, national and local layers ([Institutions](https://docs.therisk.global/organization/institutions.md)) · consortium doctrine.

**In brief.** Read against the international frameworks it serves ([UN General Assembly 2015](https://www.undrr.org/publication/sendai-framework-disaster-risk-reduction-2015-2030); [OECD 2014](https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405); [United Nations 2021](https://www.un.org/en/common-agenda)) and the [Nexus Standards](https://docs.therisk.global/organization/institutions/nexus-standards.md) that govern its records ([NS-0](https://nexustandards.com/standards/ns-0/), [NS-13](https://nexustandards.com/standards/ns-13/), [NS-10](https://nexustandards.com/standards/ns-10/)). "Nexus Consortiums are an organizing architecture, not one legal person or one membership club," and "no upper level can override a national council on a national question" (the Nexus Consortium model, as published on the GCRI and GRF sites).

{% hint style="info" %}
**Read with the current model (2026-10-21).**

* Everything this page describes is a design in formation. No national, regional or global consortium is recorded as constituted or active; 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)). Where the text below reads as operation, read it as design.
* National Nexus is the country programme: a National Desk, a National Model, a National Portfolio and three participation pillars, the NNC (institutions, through five Helix pathways or the Financial Institutions and Regulators pathway), the NLC (leaders in a personal capacity) and the NWG (expert work, with the six CERTs). The [National Standards Council](https://docs.therisk.global/organization/governance-in-operation/national-standards-council.md) is the standards function of the NNC ([National Nexus](https://docs.therisk.global/organization/governance-in-operation/national-nexus.md)).
* The councils are the six Helix councils: SPC State and Public Authorities, IOC Industry and Operators, ARC Academia and Research, CMC Civil Society and Media, CIC Community and Indigenous, and FIR Financial Institutions and Regulators, a cross-cutting pathway led with GRA. Earlier "Helix Council" usage on this page maps to them ([Councils](https://docs.therisk.global/organization/governance-in-operation/councils.md)).
* "Investors Council" and "National Stewardship Council" are earlier labels. Their finance-readiness work is now the Financial Institutions and Regulators (FIR) pathway of the NNC, led with GRA; no council or pathway arranges, approves or advises on a transaction ([NNC](https://docs.therisk.global/organization/governance-in-operation/nnc.md); [Finance readiness](https://docs.therisk.global/organization/finance-readiness.md)).
* "Competence Cells" is an earlier label. Their work is now National Working Group assignments and, by domain, the six CERTs, which are not emergency services, incident command or privileged access teams ([NWG](https://docs.therisk.global/organization/governance-in-operation/nwg.md)).
* Project vehicles and national companies 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 ([Lawful handoffs](https://docs.therisk.global/organization/finance-readiness/lawful-handoffs.md)).
* Recognition, scoring and validation record what was shown under stated conditions. None is a certification, licence, rating or approval, and no country or institution is ranked.
* No institution of the programme has supranational authority, legal personality under international law, immunities or treaty status; earlier text that reads so is historical design language.
* Systems are named by their NXS display codes (for example [NXS-RLS](https://docs.therisk.global/organization/systems/nxs-rls.md) for participants, agreements, protocols, obligations and lawful handoffs); see [Systems](https://docs.therisk.global/organization/systems.md).
  {% endhint %}

## 1.4.1 The One-Rail Principle

1.4.1.1 Common NXS-RLS. Nexus Consortiums operate on one common NXS-RLS. The one rail is the shared institutional grammar through which global, regional, national, enterprise, technical, public-good, public authority, community, capital, and project-level actors can participate in Nexus without fragmenting the architecture into disconnected initiatives, incompatible records, competing claims, or locally improvised systems that cannot interoperate across jurisdictions. In whitepaper terms, the one rail is the discipline that allows Nexus to remain one architecture even when it is expressed through many countries, regions, programs, councils, standards-interface workstreams, annual events, observatory pathways, acceleration tracks, enterprise vehicles, and project-level structures.

1.4.1.2 Rail Components. The one rail provides the common language, controlled vocabulary, participation records, council records, board records, AEP Passport discipline, standards-interface logic, public-safe reporting, maturity-readable status, finance-readiness notes, proof receipts, safeguard records, public authority status records, correction pathways, and lawful handoff structure through which Nexus remains coherent. It is the connective discipline that allows Nexus Ecosystem, [NXS-NET](https://docs.therisk.global/organization/systems/nxs-net.md) (network topology and continuity) Network, Nexus Standards, Nexus Acceleration, Nexus Universe, Nexus Observatory, NXS-RLS, Nexus Network, [Risk Academy](https://docs.therisk.global/organization/institutions/risk-academy.md), Competence Cells, National Models, Regional Cluster Program Plans, National Consortium Companies, Project SPVs, qualified providers, public authorities, capital readers, and communities to operate as parts of one system rather than as isolated initiatives.

1.4.1.3 Coordination Without Legal Merger. The one rail enables global, regional, and national actors to coordinate without becoming one legal body. A Global Nexus Consortium, Regional Nexus Consortium, National Nexus Consortium, National Nexus Council, National Consortium Company, Project SPV, provider, investor, insurer, public authority, university, community participant, sponsor, host, operator, technical contributor, or public-good institution may operate through compatible rail discipline while retaining its own legal identity, governance, mandate, liability, authority, internal controls, fiduciary obligations, and jurisdictional responsibilities. The rail creates interoperability; it does not create merger.

1.4.1.4 No Centralized Control. The one rail does not mean centralized control. Common rail discipline creates shared meaning, records coherence, claims discipline, evidence comparability, AEP Passport compatibility, finance-readiness intelligibility, public-safe reporting continuity, and handoff discipline. It does not create a global command authority, regulatory hierarchy, procurement authority, financial platform, public authority, certification regime, sovereign body, investment platform, insurance facility, or execution body. The rail is the connective architecture of Nexus, not the command structure of Nexus.

1.4.1.5 Institutional Grammar. The one rail is the common institutional grammar of Nexus. It allows participants to understand what a record means, what an AEP Passport layer does and does not do, what a council recommendation can support, what a standards-interface output may evidence, what finance-readiness may indicate, what public authority participation does not imply, what a National Model can and cannot claim, what a Regional Cluster Program Plan does and does not approve, and when a matter must be corrected, localized, escalated, or handed off to lawful actors. This grammar is what allows Nexus to scale without becoming ambiguous.

## 1.4.2 The Two-Stack Principle

1.4.2.1 Public-Good Stack and Enterprise Stack. Nexus Consortiums operate through a two-stack principle: the Public-Good Stack and the Enterprise Stack. The Public-Good Stack creates legitimacy, evidence, readiness, participation, standards-interface discipline, public-safe reporting, safeguard awareness, public authority learning, finance-readiness framing, and correction. The Enterprise Stack performs lawful implementation, contracting, finance, insurance, delivery, operations, maintenance, and project execution through separate competent actors. The two-stack principle is the core role-separation mechanism that allows Nexus to be public-good rooted and enterprise-capable at the same time.

1.4.2.2 Public-Good Stack. The Public-Good Stack includes councils, agenda formation, stakeholder participation, evidence, methods, ontology, observability, public authority learning, claims discipline, public-safe reporting, standards-interface work, AEP Passports, proof receipts, participation records, maturity-readable records, readiness records, safeguard layers, finance-readiness notes, public authority status records, correction pathways, and lawful handoff records. It is the trust-producing side of Nexus. It clarifies what is known, what is not known, what has been evidenced, what may be claimed, what remains bounded, what requires correction, and what may be handed off.

1.4.2.3 Enterprise Stack. The Enterprise Stack includes National Consortium Companies, Project SPVs, qualified providers, manufacturers, OEMs, systems integrators, contractors, operators, investors, insurers, lenders, sponsors, hosts, licensed professionals, procurement responses, implementation contracts, finance documents, insurance arrangements, service agreements, delivery obligations, operating arrangements, and asset-level governance structures. It is the execution-capable side of Nexus. It is where actors capable of assuming contracts, liabilities, financing obligations, delivery obligations, performance obligations, insurance responsibilities, and operational duties may act under applicable law.

1.4.2.4 Handoff Without Merger. The two stacks interact through lawful handoff but do not merge. Public-good records may make enterprise activity more legible, prepared, evidence-bearing, finance-readable, safeguard-aware, and accountable, but they do not themselves constitute procurement, investment approval, insurance approval, certification, public authority approval, contract award, project authorization, regulatory approval, public finance allocation, or execution. Handoff means a bounded transfer of readiness information to a competent actor. It does not mean that the Public-Good Stack has become the Enterprise Stack.

1.4.2.5 Consortium Position. Nexus Consortiums sit primarily in the public-good coordination layer while enabling enterprise pathways. They organize agenda, records, participation, councils, public authority learning, standards-interface work, observability pathways, AEP Passport logic, finance-readiness framing, public-safe reporting, correction, and handoff. They do not become National Consortium Companies, Project SPVs, providers, procurement bodies, financial actors, insurers, underwriters, operators, contractors, or project executors by default. Their role is to prepare the pathway; lawful enterprise actors carry the execution responsibility.

## 1.4.3 The Three-Level Principle

1.4.3.1 Global, Regional, and National Levels. Nexus Consortiums operate at three coordinated levels: global, regional, and national. These levels allow Nexus to preserve universal architecture, adapt to regional systems, and localize ownership through national stakeholders while maintaining one common rail and two separated stacks. The three-level principle is the spatial logic of the Consortium system: global coherence, regional relevance, and national legitimacy must all exist for Nexus to become operationally meaningful.

1.4.3.2 Global Level. The global level mobilizes universal participation and common architecture. It convenes global institutions, global companies, public-good actors, multilateral and supranational actors, capital readers, manufacturers, technical networks, universities, foundations, standards-interface participants, experts, and media into a common Nexus agenda without converting global participation into national authority. The global level is where Nexus creates common direction, common language, annual global activation, shared standards-interface logic, and global capability mobilization.

1.4.3.3 Regional Level. The regional level clusters countries and adapts the architecture to regional systems. Regional Nexus Consortiums organize cross-border priorities, regional councils, regional investor councils, regional Helix Councils, regional observatory pathways, Regional Cluster Program Plans, regional Nexus Universe preparation, regional Nexus Acceleration pathways, and regional finance-readiness mapping while respecting national sovereignty, national public authority status, national data rules, community safeguards, Indigenous and protected-knowledge rules, and national stakeholder ownership. The regional level makes the global rail regionally useful without turning regional coordination into regional supremacy.

1.4.3.4 National Level. The national level owns domestic organization, national stakeholder participation, public authority interface, National Nexus Councils, National Leadership Councils, National Investor Councils, National Helix Councils, National Working Groups, National Models, national data and safeguard rules, national company formation, Project SPV pathways, provider localization, public-safe reporting localization, and national delivery. This is where Nexus becomes domestically legitimate. Global architecture may frame, and regional clusters may adapt, but national structures provide the ownership and lawful pathway required for implementation inside a country.

1.4.3.5 Spatial Structure. The three-level principle is the spatial structure of the Consortium system. It prevents over-centralization by requiring national ownership, prevents fragmentation by preserving a common rail, and prevents weak regional coordination by giving regional layers a defined clustering role without allowing them to override national authority. The system is designed to be global enough to mobilize the world, regional enough to see cross-border systems, and national enough to be lawful, trusted, and accountable.

## 1.4.4 One Rail Across Three Levels

1.4.4.1 Cross-Level Rail Discipline. The same rail discipline applies globally, regionally, and nationally. The Global Nexus Consortium, Regional Nexus Consortiums, National Nexus Consortiums, National Nexus Councils, National Consortium Companies, Project SPVs, and lawful implementation actors should use compatible logic for participation, evidence, readiness, claims, public-safe reporting, finance-readiness, standards-interface work, correction, and handoff. This cross-level compatibility is what makes Nexus cumulative: records created at one level can be understood, bounded, corrected, and routed at another.

1.4.4.2 Compatible Record Objects. AEP Passports, participation records, council records, board records, committee records, standards-interface records, finance-readiness notes, public authority status records, safeguard records, National Models, Regional Cluster Program Plans, public-safe reports, proof receipts, maturity-readable records, and correction pathways should use compatible logic across levels. Compatibility does not require identical legal form, identical language, identical governance documents, or identical institutional structures in every jurisdiction. It requires that each record can be interpreted, routed, corrected, and bounded within the common Nexus architecture.

1.4.4.3 Localization Without Fragmentation. Regional and national variations may exist, and in many cases are necessary. A national law, data localization requirement, public authority protocol, community safeguard, Indigenous protected-knowledge rule, language requirement, procurement condition, finance regulation, privacy obligation, cybersecurity rule, or regional implementation condition may localize the rail without breaking it. Nexus does not require uniformity for its own sake. It requires disciplined compatibility so that local legal and institutional realities can be respected without losing system coherence.

1.4.4.4 Coherence and Localization. The common rail prevents fragmentation while respecting localization. It allows a national record to be nationally owned and locally lawful while remaining intelligible to regional and global Nexus structures. It allows a regional plan to reflect regional realities while remaining connected to global architecture. It allows a global standards-interface output to be adapted nationally without becoming a foreign command. It allows an AEP Passport layer to carry comparable meaning while still reflecting local data, safeguard, public authority, and finance-readiness conditions.

1.4.4.5 Institutional Interoperability. Interoperability under Nexus is institutional as well as technical. It concerns not only systems, data, software, APIs, ledgers, dashboards, models, sensors, digital twins, observability tools, or compute environments, but also roles, records, claims, public authority status, finance-readiness boundaries, correction pathways, council governance, national ownership, enterprise handoff, and lawful implementation. The one rail is therefore a governance technology as much as a technical architecture.

## 1.4.5 Two Stacks at Each Level

1.4.5.1 Stack Separation Across Levels. Public-good and enterprise-stack separation applies at global, regional, and national levels. The fact that global, regional, or national Consortium activity may involve companies, investors, providers, insurers, sponsors, public authorities, hosts, operators, or implementation actors does not collapse public-good coordination into enterprise execution. The same actor may participate in both public-good and enterprise contexts, but its role, authority, rights, and claims must be separately recorded.

1.4.5.2 Global Public-Good Agenda Is Not Global Project Execution. Global public-good agenda does not become global project execution. The Global Nexus Consortium may convene global actors, define global themes, support standards-interface work, activate Nexus Universe, mobilize global capability, organize global council inputs, and prepare records and methods, but it does not directly own, finance, procure, build, operate, insure, or deliver national projects by default. Global visibility is not global execution authority.

1.4.5.3 Regional Coordination Is Not Regional Authority. Regional coordination does not become regional procurement, regional sovereign authority, regional public finance allocation, regional certification, regional public warning, regional regulation, or regional execution. Regional Nexus Consortiums may prepare Regional Cluster Program Plans, align countries, organize regional councils, support regional readiness, and identify cross-border priorities, but they do not override national councils, national public authorities, national companies, national data rules, national safeguards, national procurement systems, or national stakeholder ownership.

1.4.5.4 National Public-Good Consortiums Are Not Automatically Companies. National public-good Consortiums do not automatically become national enterprise companies unless separate vehicles are created under applicable law and governance. A National Nexus Consortium may organize national agenda, records, councils, public authority learning, AEP Passport pathways, National Models, standards-interface localization, public-safe reporting, and handoff, while a National Consortium Company may separately receive lawful enterprise handoff for implementation-facing activity. The national public-good body and the national enterprise vehicle may interact, but they should not be confused.

1.4.5.5 Execution-Company Misreading Prohibited. Public-good bodies shall not be read as execution companies. Nexus Consortiums may prepare readiness, but readiness is not delivery. They may support finance-readiness, but finance-readiness is not finance execution. They may coordinate providers, but coordination is not procurement. They may convene public authorities, but convening is not delegation. They may support AEP Passports, but AEP Passports are not certification, approval, guarantee, funding commitment, insurance approval, or permission to execute. This boundary protects the credibility of both stacks.

## 1.4.6 Global Level Function

1.4.6.1 Global Nexus Consortium Function. Within the one-rail / two-stack / three-level model, the Global Nexus Consortium is the universal agenda, global convening, global standards-interface, global Nexus Universe, global capability-mobilization, global public-good alignment, and global-to-regional coordination layer of the Nexus Consortium system. It provides the common surface through which the world’s institutions and capabilities can be brought into one architecture without turning the global layer into a government, regulator, financier, certifier, procurer, or project operator.

1.4.6.2 Global Activities. The Global Nexus Consortium drives universal agenda, global councils, global standards-interface priorities, global Nexus Universe participation, global sponsor and provider engagement, global public authority learning surfaces, global capital-reader participation, global technology contribution, [NXS-COR](https://docs.therisk.global/organization/systems/nxs-cor.md) (compute, nodes and runtimes) Core mobilization, common records, public-safe reporting logic, AEP Passport architecture, and global-to-regional alignment. It is the place where common direction, common language, and common rail discipline are maintained.

1.4.6.3 No Direct National Execution. The Global Nexus Consortium does not directly execute national projects. It does not act as a national implementation vehicle, national procurement body, national public authority, national finance platform, national project developer, national operator, national insurer, national lender, national contractor, or national delivery company. Where national implementation is at issue, the pathway must move through national structures and, where appropriate, enterprise or project-level vehicles capable of assuming lawful responsibility.

1.4.6.4 No Bypass of Regional or National Structures. The Global Nexus Consortium shall not bypass Regional Nexus Consortiums, National Nexus Consortiums, National Nexus Councils, national public authority protocols, National Consortium Companies, Project SPVs, or national stakeholder structures where those pathways are applicable. Global architecture may support and accelerate formation, but it should not displace the structures required for regional adaptation and national legitimacy.

1.4.6.5 Powerful but Bounded Global Layer. The global level is powerful because it mobilizes the world’s institutions, technology actors, capital readers, public-good systems, standards-interface actors, and annual agenda into one common rail. It is bounded because it does not convert global visibility, global funding, global sponsorship, global expertise, global event participation, or global institutional prestige into control over national implementation. Its authority is architectural and convening, not sovereign or executional.

## 1.4.7 Regional Level Function

1.4.7.1 Regional Consortiums as Cluster Engines. Regional Nexus Consortiums are regional cluster engines within the Nexus Consortium architecture. They translate global architecture into regional priorities, cross-border coordination, regional public authority learning, regional finance-readiness, regional technology mapping, regional safeguard awareness, regional standards-interface adaptation, regional observability pathways, and Regional Cluster Program Plans. Their role is to make the common rail usable in regions with distinct risk patterns, legal systems, infrastructure corridors, markets, cultures, languages, and public authority structures.

1.4.7.2 Regional Structures. Regional Consortiums organize countries, regional councils, regional investor councils, regional Helix Councils, regional standards-interface groups, regional acceleration pathways, regional observatory pathways, Regional Cluster Program Plans, regional Nexus Universe preparation, regional NXS-RLS priorities, regional public-safe reporting logic, and regional-to-national handoff priorities. These structures allow regional intelligence to be organized without absorbing national authority.

1.4.7.3 Regional Adaptation. Regional Consortiums may adapt global architecture to APAC, GCC, MENA, Eurasia, Africa, Europe, North America, Latin America, the Caribbean, Pacific Islands, the Arctic, and other continental or strategic regions designated by Nexus governance. Regional adaptation may address legal systems, trade corridors, climate exposures, disaster-risk profiles, WEFH-B systems, finance ecosystems, data sovereignty conditions, language, culture, public authority structures, technology ecosystems, infrastructure realities, and regional implementation capacity. Adaptation is what makes global architecture practical.

1.4.7.4 No Override of National Authority. Regional Consortiums do not override National Nexus Councils, National Nexus Consortiums, national public authorities, national law, national data rules, national community safeguards, Indigenous rights, national procurement processes, national finance rules, National Consortium Companies, or Project SPV pathways. A regional plan may describe a country, cluster, corridor, portfolio, or risk pattern, but it does not approve national action unless the competent national actor separately and lawfully does so.

1.4.7.5 Cluster Without Supremacy. The regional level is a cluster without supremacy. Its legitimacy comes from organizing regional coherence while preserving national ownership. Its value comes from connecting countries without absorbing them. Its discipline comes from adapting the common rail without turning regional coordination into regional control. Regional Nexus Consortiums are strongest when they help national pathways mature rather than when they attempt to replace them.

## 1.4.8 National Level Function

1.4.8.1 National Consortiums as Gateway and Ownership Layer. National Nexus Consortiums are the national gateway and ownership layer of the Nexus Consortium system. They are the primary national surface through which Nexus becomes domestically organized, locally legitimate, public authority aware, stakeholder-owned, safeguard-sensitive, data-responsible, and capable of lawful implementation handoff. The national layer is where Nexus stops being an external architecture and becomes a national institutional pathway.

1.4.8.2 National Structures. National Nexus Consortiums organize National Nexus Councils, National Leadership Councils, National Investor Councils, National Helix Councils, National Working Groups, National Models, national public authority protocols, national standards-interface pathways, national Nexus Universe participation, national Nexus Acceleration pathways, national observatory node candidates, national safeguard processes, national public-safe reporting pathways, national provider localization, and national implementation pathways. These structures give domestic stakeholders a formal surface through which they can shape, challenge, localize, and govern Nexus activity.

1.4.8.3 Interface With National Companies and SPVs. National Nexus Consortiums interface with National Consortium Companies and Project SPVs through AEP Passports, readiness records, public authority status records, safeguard layers, finance-readiness notes, handoff memoranda, National Models, standards-interface records, public-safe reports, and board-approved pathways. Such interface does not itself constitute approval, procurement, investment, insurance, certification, financeability, public authority adoption, or execution. It is the disciplined pathway through which public-good readiness may become available to lawful enterprise actors.

1.4.8.4 National Ownership. National Nexus Consortiums are owned, operated, governed, stewarded, or led by national stakeholders according to national rules, national law, national governance instruments, and applicable Nexus public-good discipline. National stakeholders may include public authorities, universities, research institutions, civil society, communities, Indigenous actors, national companies, providers, manufacturers, investors, insurers, technical experts, media, youth, sponsors, hosts, operators, and implementation actors. National ownership must be substantive, not merely symbolic.

1.4.8.5 National Ownership Principle. National ownership is not an administrative preference. It is a constitutional operating principle of the Nexus Consortium system. No global or regional Nexus body should operate inside a country as an implementation actor without a national consortium and / or national SPV pathway owned, governed, or operated by national stakeholders, except where a lawful, temporary, public-good-justified, recorded, and bounded exception applies. This protects sovereignty, legitimacy, safeguard integrity, public authority independence, data governance, procurement fairness, and local accountability.

## 1.4.9 Project-Level Pathway

1.4.9.1 Project-Level Delivery Actors. Project-level delivery occurs through Project SPVs, National Consortium Companies, qualified providers, public authorities, sponsors, investors, insurers, contractors, operators, hosts, licensed professionals, community-facing structures where appropriate, and lawful implementation actors. These are the actors capable of assuming project-specific obligations, including contracts, financing, insurance, operations, permits, service levels, technical performance, data governance, community commitments, and lifecycle accountability.

1.4.9.2 Project-Level Support Records. Project-level pathways are supported by AEP Passports, readiness records, technical evidence layers, finance-readiness notes, public authority status records, safeguard layers, community and Indigenous participation records where applicable, data condition records, standards-interface records, public-safe reporting, proof receipts, correction records, and handoff records. These records make the project pathway more legible, but they do not replace the legal acts required for project execution.

1.4.9.3 No Default Execution by Global or Regional Public-Good Bodies. Project-level delivery is not performed by the global or regional public-good Consortium by default. Global and regional bodies may support, align, convene, train, provide methods, connect resources, mobilize capability, maintain common rail discipline, and help prepare records. Implementation-facing activity must be routed through national and project-level pathways where legal responsibility, financial responsibility, operational responsibility, and public authority interfaces can be properly held.

1.4.9.4 Execution Localization. Execution must be localized through lawful structures. This may include national companies, Project SPVs, public authority instruments, licensed providers, procurement processes, host agreements, finance documents, insurance arrangements, operating contracts, data governance agreements, safeguard processes, community benefit arrangements, Indigenous engagement processes where applicable, and project-specific governance. Localization is not only a legal requirement; it is a trust requirement.

1.4.9.5 Protection Against Liability and Role Confusion. The project-level pathway protects public-good bodies from execution liability and role confusion. It ensures that public-good records support readiness without becoming implementation commands, that national stakeholders own national delivery pathways, and that enterprise actors execute only through lawful authority, contracts, finance arrangements, permits, procurement processes, insurance obligations, and operating duties. This is how Nexus can be implementation-capable without turning the public-good stack into a project company.

## 1.4.10 One Rail / Two Stacks / Three Levels Thesis

1.4.10.1 Section Thesis. Nexus Consortiums operate through one common rail, two separated stacks, and three coordinated levels. This is the core operating model that allows Nexus to combine global reach, regional adaptation, national ownership, public-good legitimacy, and enterprise-capable implementation without role collapse.

1.4.10.2 Coherence, Discipline, and Ownership. The rail creates coherence. The stacks preserve role discipline. The levels preserve global scale, regional relevance, and national ownership. Together, they solve the central institutional problem that Nexus is designed to address: how to mobilize many actors across many jurisdictions and technologies without creating confusion about who records, who validates, who convenes, who finances, who approves, who procures, who operates, and who is legally responsible.

1.4.10.3 Operating Logic. One rail allows Nexus actors to share language, records, AEP Passport discipline, standards-interface logic, correction pathways, public-safe reporting, finance-readiness structures, and handoff models. Two stacks keep public-good coordination separate from enterprise execution. Three levels ensure that global ambition becomes regional relevance and national legitimacy before moving into project-level delivery. The operating logic is simple but strict: coherence without centralization, readiness without approval, participation without authority overclaim, and handoff without merger.

1.4.10.4 Global Mobilization, National Delivery. This structure allows Nexus to mobilize globally while delivering nationally. It enables global institutions, technologies, capital readers, public-good actors, public authorities, universities, communities, providers, sponsors, and implementation partners to participate in one architecture without creating a global execution body or bypassing national stakeholders. The global layer mobilizes; the regional layer translates; the national layer owns; the project layer executes through competent actors.

1.4.10.5 Foundational Conceptual Clause. The one-rail / two-stack / three-level model is one of the defining constitutional ideas of the Nexus Consortium system: one common rail for coherence, two separated stacks for legitimacy and execution discipline, and three coordinated levels for global reach, regional clustering, and national ownership. It is the architecture that lets Nexus be ambitious without being centralized, practical without being captured, finance-readable without being financialized, and implementation-ready without turning public-good coordination into execution.

## Sources

1. UN General Assembly (2015). Sendai Framework for Disaster Risk Reduction 2015–2030. A/RES/69/283, 3 June 2015. <https://www.undrr.org/publication/sendai-framework-disaster-risk-reduction-2015-2030>
2. 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>
3. United Nations (2021). Our Common Agenda: Report of the Secretary-General. New York: United Nations. <https://www.un.org/en/common-agenda>
4. UN General Assembly (2024). The Pact for the Future. A/RES/79/1, adopted 22 September 2024, with the Global Digital Compact (Annex I) and the Declaration on Future Generations (Annex II). <https://undocs.org/A/RES/79/1>
5. UN Office of the Secretary-General's Envoy on Technology and UNDP (2024). Universal DPI Safeguards Framework. New York: United Nations, September 2024. <https://www.dpi-safeguards.org/>
6. Nexus Standards. NS-0: Constitution and principles. Status: PROPOSED; UNI `NXS-STD-ST-000004`. <https://nexustandards.com/standards/ns-0/>
7. Nexus Standards. NS-13: Open standards development process. Status: PROPOSED; UNI `NXS-STD-ST-000008`. <https://nexustandards.com/standards/ns-13/>
8. Nexus Standards. NS-10: Policies and clauses. Status: PROPOSED; UNI `NXS-STD-ST-000006`. <https://nexustandards.com/standards/ns-10/>
9. GCRI. How Nexus Consortium works. <https://therisk.global/consortium/>
10. GCRI. Global programme. <https://therisk.global/consortium/global/>
11. GCRI. Six programme regions. <https://therisk.global/consortium/regions/>
12. GCRI. National Nexus. <https://therisk.global/consortium/national/>
13. [The Global Risks Forum](https://docs.therisk.global/organization/institutions/grf.md). Council architecture. <https://globalriskforum.com/leadership/council-model/>
14. GCRI. Programme status. <https://therisk.global/consortium/programme-status/>
15. This documentation: [Governance in operation](https://docs.therisk.global/organization/governance-in-operation.md); [The Model](https://docs.therisk.global/organization/model.md); [historical labels](https://docs.therisk.global/organization/reference.md).


---

# 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/cooperation/consortiums/model/i.-identity/1.4-one-rail-two-stacks-three-levels-global-regional-national.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.
