> 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/systems/nxs-hub.md). # NXS-HUB NXS-HUB, the institutional knowledge, records, collaboration, learning and support system of the Nexus ecosystem: purpose, rooms, inputs and outputs, areas, standards and boundaries. {% hint style="info" %} This page is generated from the twenty-system charters, the system profiles, the interface and authority registers, the room register, the areas of work, the systems article of the constitution set and the programme spine. Do not edit it in GitBook: change the source and export again. {% endhint %} **NXS-HUB** is one of the twenty systems of the Nexus ecosystem: the institutional knowledge, records, collaboration, learning and support system. It is described here as a system of the ecosystem, with its purpose, its rooms, what it receives and provides, the areas it serves, the standards that apply and its boundaries. Earlier pages may use the retired name `Nexus Hub`. ## Purpose and context Portals & Access — every controlled external/internal audience surface. Its domain is institutional knowledge, collaboration, human learning and support. A typical setting is an institutional workspace with an expert network, support cases and learning programme. ## What it is the authority for | Record | What the system must keep | | ------------------ | ----------------------------------------------------------------- | | community scope | Separate community participation from project/data authorization. | | record class | Respect confidentiality, source ACL and publication conditions. | | learning objective | Keep human assessment evidence separate from completion clicks. | | support case refs | Preserve reporter privacy and responsible service owner. | | citation refs | Support correction, withdrawal and source-quality review. | ## Rooms and areas of work Every system has ten rooms: eight shared rooms, which work the same way across systems with this system's domain, and two specialist rooms. | Room | Kind | Purpose | | ------------ | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | Station | Shared | The system's home: posture of the system's own records, freshness, refusals and next actions; never a summary of another system's truth | | Mission | Shared | Mission and task work for the system's domain, linked to Universe missions and Project OS plans | | Builder | Shared | Composition of the system's artifacts and configurations from admitted packages (NXS-STU, NXS-FAC and NXS-NXQ boundaries apply) | | Maps | Shared | Spatial views of the system's records and NXS-GRX products, under the boundary licence gate | | Data | Shared | The system's datasets, sources and lineage as NXS-GRX products or system-owned records | | Commons | Shared | Shared methods, standards, templates and reusable artifacts, including Nexus Standards (NXS, a programme of the Nexus Consortium) participation | | Reports | Shared | Reports and editions built from the system's evidence, with cutoffs and correction history | | Knowledge | Shared | Institutional knowledge, records, runbooks and learning linked to NXS-HUB | | Academy | Specialist | Records: learning pathway, learning cohort, enrollment, assessment submission, completion record | | Service Desk | Specialist | Records: service case, service commitment, case activity, resolution proposal, problem record | **Kinds of work it carries:** Institutional workspaces; Learning programmes; Knowledge Space; Runbook Set; Support Knowledge; Institutional Record Package; Learning Path; Collaboration workspaces; Partner coordination networks; Committee secretariats; Knowledge programmes; Research evidence bases; Policy & procedure libraries; Terminology programmes; Runbook libraries; Service desks; After-action programmes; Institutional records programmes; Role learning paths; Staff inductions; Exercise programmes; Community engagement initiatives. **This system in the Nexus model.** Generated from the Nexus Standards index and the programme spine; statuses are registry statuses, never adoption or certification. | | | | -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Descriptor | Institutional knowledge, records, collaboration, learning and support | | In the programme | Built, simulated and prepared in the [Foundry pillar](/organization/programme/foundry.md); its records serve the other pillars through the handoffs of [the programme year](/organization/programme/the-programme-year.md), and the competent authority decides outside the programme. | | System profile | [NRS-S14](https://nexustandards.com/standards/nrs/#nrs-s14): NXS-HUB (Knowledge, records and learning) (status OPEN) | | Nexus Risk Standards that apply | 16 in 8 series: ai-native: [NRS-A2](https://nexustandards.com/standards/nrs/#nrs-a2), [NRS-A7](https://nexustandards.com/standards/nrs/#nrs-a7); core: [NRS-C1](https://nexustandards.com/standards/nrs/#nrs-c1); development: [NRS-D4](https://nexustandards.com/standards/nrs/#nrs-d4), [NRS-D7](https://nexustandards.com/standards/nrs/#nrs-d7), [NRS-D10](https://nexustandards.com/standards/nrs/#nrs-d10); programme: [NRS-E2](https://nexustandards.com/standards/nrs/#nrs-e2), [NRS-E3](https://nexustandards.com/standards/nrs/#nrs-e3), [NRS-E5](https://nexustandards.com/standards/nrs/#nrs-e5); intelligence: [NRS-I4](https://nexustandards.com/standards/nrs/#nrs-i4), [NRS-I5](https://nexustandards.com/standards/nrs/#nrs-i5), [NRS-I6](https://nexustandards.com/standards/nrs/#nrs-i6); policy: [NRS-P6](https://nexustandards.com/standards/nrs/#nrs-p6); system: [NRS-S14](https://nexustandards.com/standards/nrs/#nrs-s14); cross-cutting: [NRS-X7](https://nexustandards.com/standards/nrs/#nrs-x7), [NRS-X9](https://nexustandards.com/standards/nrs/#nrs-x9) | | Nexus Reports technology streams | None | ## Outputs What it provides, and to whom. Consumers read projections; the system stays the authority for its own records and their corrections. | To | What it provides | | ------------------------------------------- | --------------------------------------- | | every system | knowledge/runbook/citation references | | [NXS-POR](/organization/systems/nxs-por.md) | published knowledge content | | [NXS-NSF](/organization/systems/nxs-nsf.md) | authorization/policy evaluation request | | the evidence fabric | append consequential receipt/evidence | ## Interfaces with other systems Beyond its interfaces, it relies on fact families owned elsewhere: semantic root (the ontology fabric); external delivery ([NXS-POR](/organization/systems/nxs-por.md)); regulated protocol state ([NXS-RLS](/organization/systems/nxs-rls.md)); consent authority ([NXS-NSF](/organization/systems/nxs-nsf.md)); delegation authority ([NXS-NSF](/organization/systems/nxs-nsf.md)). ## Areas it serves | Area | Category | What the area covers | | ---------------------------------------------------- | ----------- | ----------------------------------------------------------- | | [Enterprise risk](/organization/systems/areas.md) | Management | Risk governance, appetite and oversight across institutions | | [Foresight](/organization/systems/areas.md) | Research | Emerging risks, horizon scanning and long-term scenarios | | [Risk reduction](/organization/systems/areas.md) | Policy | National disaster risk reduction strategy and targets | | [Digital governance](/organization/systems/areas.md) | Policy | AI, data and digital public infrastructure policy | | [Country programmes](/organization/systems/areas.md) | Development | Nationally owned programmes across fifteen hubs | | [Capacity building](/organization/systems/areas.md) | Development | Technical assistance and institutional skills | | [Leadership](/organization/systems/areas.md) | Development | Leaders, specialists and workforce capability | ## Standards that apply Every record of the system is identified through the UNI identifier fabric of Nexus Standards (NS-1), and its public name follows the Nexus Standards naming rules. The areas it serves reference these external standards; naming a standard records where it is referenced and is not a claim of certification, accreditation, conformance or endorsement. | Standard | Issuer | Year | Use | | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | ---- | ------------------------------------------------- | | ISO 31000 Risk management, Guidelines | International Organization for Standardization (ISO) | 2018 | Principles, framework and process | | Enterprise Risk Management, Integrating with Strategy and Performance | Committee of Sponsoring Organizations of the Treadway Commission (COSO) | 2017 | Linking risk appetite to strategy and performance | | Recommendation on the Governance of Critical Risks | Organisation for Economic Co-operation and Development (OECD) | 2014 | Whole-of-government governance of critical risks | | Sendai Framework for Disaster Risk Reduction 2015-2030, Priority 2 | United Nations Office for Disaster Risk Reduction (UNDRR) | 2015 | Strengthening disaster risk governance | | ISO 31050 Guidance for managing emerging risks to enhance resilience | ISO | 2023 | Emerging-risk management | | Declaration on Future Generations | United Nations General Assembly | 2024 | Long-term thinking in policy | | Strategic Foresight for Better Policies | OECD | 2019 | Foresight in government practice | | Sendai Framework for Disaster Risk Reduction 2015-2030 | United Nations | 2015 | Seven global targets | | Political Declaration of the Midterm Review of the Sendai Framework | United Nations General Assembly | 2023 | Priorities to 2030 | | Global Assessment Report | UNDRR | 2025 | Global evidence on risk and resilience | | Global Digital Compact | United Nations General Assembly | 2024 | Shared principles for digital cooperation | | Framework Convention on Artificial Intelligence and Human Rights, Democracy and the Rule of Law | Council of Europe | 2024 | Binding AI treaty framework | | OECD AI Principles, updated | OECD | 2024 | Trustworthy AI principles | | General Data Protection Regulation, Regulation (EU) 2016/679 | European Union | 2016 | Data protection benchmark | | Paris Declaration on Aid Effectiveness | OECD Development Assistance Committee | 2005 | Country ownership | | Busan Partnership for Effective Development Co-operation | Fourth High Level Forum on Aid Effectiveness | 2011 | Use of country systems | | UN Sustainable Development Cooperation Framework guidance | United Nations Sustainable Development Group | 2019 | Alignment with UN country planning | | Capacity Development: A UNDP Primer | United Nations Development Programme (UNDP) | 2009 | Assessing and developing capacity | | The Challenge of Capacity Development: Working Towards Good Practice | OECD Development Assistance Committee | 2006 | Principles for capacity development | | ISO 30414 Human capital reporting | ISO | 2018 | Workforce capability reporting | | ISO 22301, clause 7.2 (competence) | ISO | 2019 | Competence for continuity roles | | Recommendation on Open Science | UNESCO | 2021 | Inclusive skills and participation | ## In the programme | Pillar | Room | What happens there | | --------------------------------------------------- | --------- | --------------------------------------------------------------- | | [Nexus Reports](/organization/programme/reports.md) | Knowledge | Sources, methods and the rights register | | [Risk Academy](/organization/programme/academy.md) | Academy | Pathways, cohorts, assessments and issuer-controlled completion | ## Governance boundaries Policy authority for the system sits with [NXS-NSF](/organization/systems/nxs-nsf.md); identifiers come from the UNI identifier fabric. The system exports read projections and commands through typed contracts, and no other system writes its records. It does not own, and never stands in for: * protocol orchestration (Rails) * app runtime (Apps) * autonomous public publication (prohibited) **Method boundary.** Learning completion is not competence or certification. Retrieval quality must be evaluated against permitted sources; engagement metrics must not become covert individual profiling. Do not confuse a learning resource, attendance record and issuer-controlled qualification. [All twenty systems](/organization/systems.md) · [Areas](/organization/systems/areas.md) *** *Generated page. It records names, roles and design for reading, not readiness: release is on hold, and nothing here is presented as ready, certified or official.* --- # 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/systems/nxs-hub.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.