> 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-ecosystem/ii.-structure.md). # II. STRUCTURE Nexus Ecosystem structure for digital public infrastructure, sovereign interoperability, lawful handoff, public-good governance, finance-readiness, and non-executing system architecture. **Where this fits:** all six sectors · all six pillars · [the twenty systems](/organization/systems.md) · [the Nexus Consortium](/organization/institutions/nexus-consortium.md) · doctrine and architecture. **In brief.** This section defines the structural architecture of Nexus Ecosystem across digital public infrastructure, sovereign interoperability, lawful handoff, finance-readiness, and non-executing public-good governance. This page belongs to the Nexus Ecosystem, a [Nexus Standards](/organization/institutions/nexus-standards.md) design in progress whose governing texts are published on [nexustandards.com](https://nexustandards.com/standards/) ([OECD, 2014](https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405); [UN Office of the Secretary-General's Envoy on Technology, 2024](https://www.dpi-safeguards.org/)). A design described here is not a deployed system, a certification or an approval; the competent authority decides, outside the programme. {% hint style="info" %} **Read with the current model.** The Nexus Ecosystem is defined once, on [the Nexus Ecosystem page](/organization/standardization/nexus-ecosystem.md): the governed public-good architecture that connects institutions, technologies, standards, evidence and lawful implementation pathways across the twenty systems. Technology here is described as [the twenty systems](/organization/systems.md) by NXS code; technology readiness uses the nine levels of ISO 16290, never ten. Finance vehicles are structures competent, lawful actors may form outside the programme ([Lawful handoffs](/organization/finance-readiness/lawful-handoffs.md)). Everything is in formation (service level R0). {% endhint %} ## Nexus Ecosystem structure This section defines the structural architecture of Nexus Ecosystem across digital public infrastructure, sovereign interoperability, lawful handoff, finance-readiness, and non-executing public-good governance. It maps how foundations, doctrines, institutions, stacks, mechanisms, objects, software, data, AI, intelligence, portfolios, people, competence, campaigns, universe, finance, public interfaces, safeguards, localization, technology, infrastructure, operations, handoff, security, metrics, templates, adoption, and declaration fit together as one coherent system. ### Section map * [I. FOUNDATIONS](/organization/standardization/nexus-ecosystem/ii.-structure/i.-foundations.md)\ Establishes first principles, public-good purpose, sovereign compatibility, and lawful handoff logic. * [II. DOCTRINES](/organization/standardization/nexus-ecosystem/ii.-structure/ii.-doctrines.md)\ Defines the operating doctrines that keep the ecosystem bounded, correctionable, and records-first. * [III. INSTITUTIONS](/organization/standardization/nexus-ecosystem/ii.-structure/iii.-institutions.md)\ Maps governance bodies, role separation, pillar institutions, and consortium architecture. * [IV. FEDERATION](/organization/standardization/nexus-ecosystem/ii.-structure/iv.-federation.md)\ Explains how global, regional, national, and local layers coordinate without collapsing sovereignty. * [V. STACKS](/organization/standardization/nexus-ecosystem/ii.-structure/v.-stacks.md)\ Separates the public-good stack, enterprise stack, and One Rail routing model. * [VI. MECHANISMS](/organization/standardization/nexus-ecosystem/ii.-structure/vi.-mechanisms.md)\ Covers the records, ledgers, registers, dockets, rooms, and proof structures that govern system flow. * [VII. PILLARS](/organization/standardization/nexus-ecosystem/ii.-structure/vii.-pillars.md)\ Organizes the core operating pillars, including Foundry, Academy, Reports, Studio, Grid, Registry, Marketplace, and Universe. * [VIII. OBJECTS](/organization/standardization/nexus-ecosystem/ii.-structure/viii.-objects.md)\ Defines the object model, identity, metadata, relationships, and lifecycle states across the ecosystem. * [IX. SOFTWARE](/organization/standardization/nexus-ecosystem/ii.-structure/ix.-software.md)\ Governs public-good software records, releases, repositories, controls, and non-executing boundaries. * [X. DATA](/organization/standardization/nexus-ecosystem/ii.-structure/x.-data.md)\ Defines data commons, rights, metadata, lifecycle controls, secure rooms, and compute-to-data discipline. * [XI. AI](/organization/standardization/nexus-ecosystem/ii.-structure/xi.-ai.md)\ Covers AI systems, model records, agent workflows, safety controls, human review, and boundary rules. * [XII. INTELLIGENCE](/organization/standardization/nexus-ecosystem/ii.-structure/xii.-intelligence.md)\ Explains how [NXS-GRX](/organization/systems/nxs-grx.md), DRI, Observatory, and Studio produce risk intelligence and public-safe outputs. * [XIII. PORTFOLIOS](/organization/standardization/nexus-ecosystem/ii.-structure/xiii.-portfolios.md)\ Structures national, regional, thematic, challenge, and readiness portfolios for routing and status truth. * [XIV. PEOPLE](/organization/standardization/nexus-ecosystem/ii.-structure/xiv.-people.md)\ Defines contributors, teams, participation records, work units, and whole-of-society pathways. * [XV. COMPETENCE](/organization/standardization/nexus-ecosystem/ii.-structure/xv.-competence.md)\ Connects learning records, contribution recognition, workforce transition, and qualification boundaries. * [XVI. CAMPAIGNS](/organization/standardization/nexus-ecosystem/ii.-structure/xvi.-campaigns.md)\ Covers mobilization, volunteer pathways, support records, and campaign boundaries. * [XVII. UNIVERSE](/organization/standardization/nexus-ecosystem/ii.-structure/xvii.-universe.md)\ Defines the annual systems-build arena for convergence, readiness, and learning without execution. * [XVIII. FINANCE](/organization/standardization/nexus-ecosystem/ii.-structure/xviii.-finance.md)\ Structures finance-readiness, capital-readability, donor relevance, insurance-readiness, and public finance learning. * [XIX. PUBLIC](/organization/standardization/nexus-ecosystem/ii.-structure/xix.-public.md)\ Defines public authority learning, public-safe reporting, and bounded public-sector interfaces. * [XX. SAFEGUARDS](/organization/standardization/nexus-ecosystem/ii.-structure/xx.-safeguards.md)\ Covers protected knowledge, participation safety, public-safe summaries, and safeguard controls. * [XXI. LOCALIZATION](/organization/standardization/nexus-ecosystem/ii.-structure/xxi.-localization.md)\ Explains language, cultural adaptation, and jurisdiction-aware expression across sovereign contexts. * [XXII. TECHNOLOGY](/organization/standardization/nexus-ecosystem/ii.-structure/xxii.-technology.md)\ Maps AI, compute, cyber, networks, geospatial systems, and verification infrastructure. * [XXIII. INFRA](/organization/standardization/nexus-ecosystem/ii.-structure/xxiii.-infra.md)\ Covers distributed systems, sovereign compute, storage, networking, and infrastructure boundaries. * [XXIV. OPERATIONS](/organization/standardization/nexus-ecosystem/ii.-structure/xxiv.-operations.md)\ Defines workflows, controls, continuity, routing, and service coordination across the ecosystem. * [XXV. HANDOFF](/organization/standardization/nexus-ecosystem/ii.-structure/xxv.-handoff.md)\ Explains controlled transfer, recipient responsibility, downstream dependency awareness, and non-executing limits. * [XXVI. SECURITY](/organization/standardization/nexus-ecosystem/ii.-structure/xxvi.-security.md)\ Covers zero-trust controls, access, incidents, correction, archive governance, and security boundaries. * [XXVII. METRICS](/organization/standardization/nexus-ecosystem/ii.-structure/xxvii.-metrics.md)\ Defines learning signals, system health, reuse intelligence, correction, and boundary-aware metrics. * [XXVIII. TEMPLATES](/organization/standardization/nexus-ecosystem/ii.-structure/xxviii.-templates.md)\ Standardizes records, notices, review structures, correction pathways, and archive governance. * [XXIX. ADOPTION](/organization/standardization/nexus-ecosystem/ii.-structure/xxix.-adoption.md)\ Defines staged formation, records-first scaling, national ownership, and correction pathways. * [XXX. DECLARATION](/organization/standardization/nexus-ecosystem/ii.-structure/xxx.-declaration.md)\ Closes the structure with no-conversion rules, final operating formula, and role-separation boundaries. ## Sources * Nexus Standards. NS-0: Constitution and principles. Proposed. [nexustandards.com/standards/ns-0/](https://nexustandards.com/standards/ns-0/) * Nexus Standards. NS-15: System model binding (subjects, passports, chronotopes, routes, engines, cells and agents). Proposed. [nexustandards.com/standards/ns-15/](https://nexustandards.com/standards/ns-15/) * 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-S0](https://nexustandards.com/standards/nrs/#nrs-s0): System and stack passports and platform conformance. [nexustandards.com](https://nexustandards.com/standards/nrs/#nrs-s0) * OECD (2014). Recommendation of the Council on the Governance of Critical Risks. OECD/LEGAL/0405, adopted 6 May 2014. [legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405](https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405) * UN Office of the Secretary-General's Envoy on Technology and UNDP (2024). Universal DPI Safeguards Framework. New York: United Nations, September 2024. [www.dpi-safeguards.org](https://www.dpi-safeguards.org/) * Rose, S., Borchert, O., Mitchell, S. and Connelly, S. (2020). Zero Trust Architecture. NIST Special Publication 800-207. Gaithersburg, MD: NIST. [csrc.nist.gov/pubs/sp/800/207/final](https://csrc.nist.gov/pubs/sp/800/207/final) --- # 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-ecosystem/ii.-structure.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.