> 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-cmd.md). # NXS-CMD NXS-CMD, the integrated posture, mission and portfolio intelligence, executive synthesis 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-CMD** is one of the twenty systems of the Nexus ecosystem: the integrated posture, mission and portfolio intelligence, executive synthesis 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. ## Purpose and context Cross-subsystem synthesis, portfolio, registries, readiness, governance memory and handoffs. Its domain is institutional command, accountable portfolio coordination and executive synthesis. A typical setting is a national port-resilience portfolio with several institution-owned initiatives. ## What it is the authority for | Record | What the system must keep | | ------------------ | ------------------------------------------------------------------------------------------------- | | institution | Resolve a real institution and its accountable role; a display label grants no mandate. | | objective | Preserve the measurable objective and source project, rather than a free-text success claim. | | dependency refs | Cross-project links require permission on both ends; keep inaccessible targets redacted. | | decision horizon | Distinguish the institutional decision deadline from forecast valid time. | | benefit allocation | Retain currency, price basis, units and overlap assumptions; do not double-count shared benefits. | ## 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 | | Portfolios | Specialist | Records: portfolio, portfolio objective, initiative binding, portfolio dependency, portfolio baseline | | Council | Specialist | Records: council session, docket item, deliberation record, resolution | **Kinds of work it carries:** Mission portfolios; Executive briefings; Institutional Posture Product; Mission Readiness Product; Portfolio Risk Brief; Executive Decision Brief; Cross-System Handoff Package; Enterprise risk portfolios; Multi-country programmes; Investor / ESG portfolios; Critical-infrastructure portfolios; Climate / development finance programmes; Institutional risk registers; Board risk postures; Executive crisis cells; Supervisory climate postures; City resilience programmes; National resilience strategies; Systemic risk watches; Group continuity programmes; Supply chain networks; Acquisition due-diligence targets; Infrastructure investment pipelines; Real-estate portfolios; Cross-system missions; Inter-agency handovers; Sendai progress programmes. **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 | Integrated posture, mission and portfolio intelligence, executive synthesis | | 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-S1](https://nexustandards.com/standards/nrs/#nrs-s1): NXS-CMD (Integrated posture and executive synthesis) (status OPEN) | | Nexus Risk Standards that apply | 24 in 9 series: core: [NRS-C6](https://nexustandards.com/standards/nrs/#nrs-c6), [NRS-C12](https://nexustandards.com/standards/nrs/#nrs-c12), [NRS-C14](https://nexustandards.com/standards/nrs/#nrs-c14), [NRS-C16](https://nexustandards.com/standards/nrs/#nrs-c16); development: [NRS-D1](https://nexustandards.com/standards/nrs/#nrs-d1), [NRS-D5](https://nexustandards.com/standards/nrs/#nrs-d5), [NRS-D9](https://nexustandards.com/standards/nrs/#nrs-d9); programme: [NRS-E1](https://nexustandards.com/standards/nrs/#nrs-e1), [NRS-E2](https://nexustandards.com/standards/nrs/#nrs-e2), [NRS-E6](https://nexustandards.com/standards/nrs/#nrs-e6), [NRS-E8](https://nexustandards.com/standards/nrs/#nrs-e8); finance: [NRS-F4](https://nexustandards.com/standards/nrs/#nrs-f4), [NRS-F9](https://nexustandards.com/standards/nrs/#nrs-f9); intelligence: [NRS-I1](https://nexustandards.com/standards/nrs/#nrs-i1), [NRS-I6](https://nexustandards.com/standards/nrs/#nrs-i6), [NRS-I7](https://nexustandards.com/standards/nrs/#nrs-i7); nexus-stream: [NRS-N6](https://nexustandards.com/standards/nrs/#nrs-n6), [NRS-N7](https://nexustandards.com/standards/nrs/#nrs-n7); policy: [NRS-P1](https://nexustandards.com/standards/nrs/#nrs-p1), [NRS-P2](https://nexustandards.com/standards/nrs/#nrs-p2), [NRS-P8](https://nexustandards.com/standards/nrs/#nrs-p8), [NRS-P11](https://nexustandards.com/standards/nrs/#nrs-p11); system: [NRS-S1](https://nexustandards.com/standards/nrs/#nrs-s1); technology: [NRS-T12](https://nexustandards.com/standards/nrs/#nrs-t12) | | Nexus Reports technology streams | ENE Energy transition technologies | ## Inputs What it receives, and from whom. Each interface carries its context (estate, tenant, workspace, purpose, jurisdiction, time and place) and is checked under the policy authority. | From | What it receives | | ------------------------------------------- | ------------------------------------------------------------------------ | | [NXS-GRX](/organization/systems/nxs-grx.md) | systemic risk/evidence products; correction and supersession propagation | | [NXS-DSS](/organization/systems/nxs-dss.md) | decision support package | | [NXS-AAP](/organization/systems/nxs-aap.md) | anticipatory readiness package | | [NXS-NST](/organization/systems/nxs-nst.md) | COP/mission operational posture | ## 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 | | ------------------------------------------- | --------------------------------------- | | [NXS-RLS](/organization/systems/nxs-rls.md) | authorized handoff preparation | | [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: agentic intelligence fabric ([NXS-STU](/organization/systems/nxs-stu.md)); trust root and key custody ([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 | | [Business continuity](/organization/systems/areas.md) | Management | Keep essential services running through disruption | | [Crisis management](/organization/systems/areas.md) | Management | Decision-making and coordination when events escalate | | [Capital resilience](/organization/systems/areas.md) | Finance | Long-horizon evidence for pensions and public funds | | [Risk reduction](/organization/systems/areas.md) | Policy | National disaster risk reduction strategy and targets | | [Climate adaptation](/organization/systems/areas.md) | Policy | Adaptation planning, finance and progress tracking | | [Country programmes](/organization/systems/areas.md) | Development | Nationally owned programmes across fifteen hubs | | [Development finance](/organization/systems/areas.md) | Development | Resilience project preparation with development banks | | [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 22301 Business continuity management systems, Requirements | ISO | 2019 | Management-system requirements | | ISO 22313 Business continuity management systems, Guidance | ISO | 2020 | Practical guidance for implementation | | Principles for Operational Resilience | Basel Committee on Banking Supervision (BCBS) | 2021 | Operational resilience for banks | | Digital Operational Resilience Act, Regulation (EU) 2022/2554 | European Union | 2022 | ICT resilience for EU financial entities, applied from 2025 | | ISO 22361 Security and resilience, Crisis management, Guidelines | ISO | 2022 | Crisis capability and decision-making | | ISO 22320 Emergency management, Guidelines for incident management | ISO | 2018 | Incident command and coordination | | National Incident Management System, third edition | United States Federal Emergency Management Agency (FEMA) | 2017 | Comparator for scalable incident structures | | Principles for Responsible Investment | PRI, with UNEP FI and the UN Global Compact | 2006 | Incorporating material risks | | Santiago Principles | International Forum of Sovereign Wealth Funds (IFSWF) | 2008 | Governance of sovereign funds | | G20/OECD Principles of Corporate Governance | OECD | 2023 | Board oversight of sustainability risks | | 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 | | Paris Agreement, Article 7 | United Nations Framework Convention on Climate Change (UNFCCC) | 2015 | Global goal on adaptation | | UAE Framework for Global Climate Resilience | UNFCCC, COP28 | 2023 | Targets for adaptation progress | | National Adaptation Plan process (Cancun Adaptation Framework) | UNFCCC | 2010 | Planning process for adaptation | | 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 | | Environmental and Social Framework | World Bank | 2018 | Safeguards and stakeholder engagement | | Performance Standards on Environmental and Social Sustainability | International Finance Corporation (IFC) | 2012 | Private-sector project standards | | Equator Principles 4 | Equator Principles Association | 2020 | Project-finance risk management | | 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 Universe](/organization/programme/universe.md) | Council | Mandate, gate decisions and dissent on record | | [Nexus Reports](/organization/programme/reports.md) | Reports | Edition assembly, review and release workflow | ## 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: * compute runtime (NXS-NXS-COR) * app runtime (Apps) * portals (Hub) * policy authority (NXS-NSF) **Method boundary.** Portfolio aggregation must preserve denominators, overlap and correlation. Report vector trade-offs before any composite index, and publish the allocation rule used to avoid counting one improvement several times. Do not conflate an executive priority with a legally competent institutional resolution. [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-cmd.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.