> 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/pathways/leadership.md). # LEADERSHIP National Leadership Council governance for national leadership, stewardship pipelines, stakeholder participation, public-good coordination, cross-helix alignment, and lawful handoff. **Where this fits:** all six sectors ([The Model](/organization/model.md)) · [Nexus Universe](/organization/programme/universe.md), [Risk Academy](/organization/programme/academy.md) · the National Leadership Council (NLC), the leadership pillar of National Nexus; GRF council architecture ([NLC](/organization/governance-in-operation/nlc.md)) · participation pathway (NLC). **In brief.** The National Leadership Council defines national leadership inside the Nexus Consortium architecture. 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); [ISO 2018](https://www.iso.org/standard/65694.html)) and the [Nexus Standards](/organization/institutions/nexus-standards.md) that govern its records ([NS-0](https://nexustandards.com/standards/ns-0/), [NS-10](https://nexustandards.com/standards/ns-10/)). "Selection precedes payment. Council standing does not buy office, employment, a Board seat or restricted data, and an employer does not own a personal seat." (NLC boundary, the Nexus Consortium model). {% 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](/organization/governance-in-operation/status-and-service-levels.md)). Where the text below reads as operation, read it as design. * 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](/organization/governance-in-operation/councils.md)). {% endhint %} The **National Leadership Council** defines national leadership inside the Nexus Consortium architecture. This section covers stewardship pipelines, stakeholder participation, public-good coordination, public authority learning, finance-readiness, cross-helix alignment, and lawful handoff. ### Key topics * [Identity](/organization/cooperation/consortiums/pathways/leadership/i.-identity.md) - role, purpose, and national ownership. * [Functions](/organization/cooperation/consortiums/pathways/leadership/v.-functions.md) - duties, coordination, and leadership responsibilities. * [Pipeline](/organization/cooperation/consortiums/pathways/leadership/vii.-pipeline.md) - leadership pipeline, stewardship pipeline, and succession flow. * [Handoff](/organization/cooperation/consortiums/pathways/leadership/ix.-handoff.md) - lawful handoff, continuity, and transfer of responsibility. ### Related topics * [0. Context](/organization/cooperation/consortiums/pathways/leadership/0.-context.md) - charter scope, purpose, and operating boundaries. * [Position](/organization/cooperation/consortiums/pathways/leadership/ii.-position.md) - placement in the national, regional, and global architecture. * [Standing](/organization/cooperation/consortiums/pathways/leadership/iii.-standing.md) - eligibility, participation status, and leadership visibility. ### Summary The National Leadership Council is the national leadership gateway inside the National Council. It supports leadership formation, stewardship pipelines, agenda discipline, cross-helix coordination, and lawful handoff without creating authority by default. ### Next steps 1. Start with [0. Context](/organization/cooperation/consortiums/pathways/leadership/0.-context.md) for scope and definitions. 2. Review [Position](/organization/cooperation/consortiums/pathways/leadership/ii.-position.md) and [Functions](/organization/cooperation/consortiums/pathways/leadership/v.-functions.md). 3. Continue to [Pipeline](/organization/cooperation/consortiums/pathways/leadership/vii.-pipeline.md) and [Handoff](/organization/cooperation/consortiums/pathways/leadership/ix.-handoff.md). ## Sources 1. UN General Assembly (2015). Sendai Framework for Disaster Risk Reduction 2015–2030. A/RES/69/283, 3 June 2015. 2. OECD (2014). Recommendation of the Council on the Governance of Critical Risks. OECD/LEGAL/0405, adopted 6 May 2014. 3. ISO (2018). ISO 31000:2018 Risk management — Guidelines. Geneva: International Organization for Standardization. 4. Nexus Standards. NS-0: Constitution and principles. Status: PROPOSED; UNI `NXS-STD-ST-000004`. 5. Nexus Standards. NS-10: Policies and clauses. Status: PROPOSED; UNI `NXS-STD-ST-000006`. 6. GCRI. Leadership pathway (NLC). 7. [The Global Risks Forum](/organization/institutions/grf.md). Leadership and councils. 8. The Global Risks Forum. National leadership. 9. GCRI. [National Nexus](/organization/governance-in-operation/national-nexus.md). 10. This documentation: [Governance in operation](/organization/governance-in-operation.md); [The Model](/organization/model.md); [historical labels](/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/pathways/leadership.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.