> 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/operations/frameworks/nexus-leadership-system-nls/xxv.-leader-guide.md). # XXV. Leader Guide Practical Nexus Leadership System (NLS) guide for Leadership Council members, Annual Leadership Contribution Plans, evidence, governance, and National, Regional, and Global leadership. **Where this fits:** all six sectors · [Nexus Universe](/organization/programme/universe.md), [Risk Academy](/organization/programme/academy.md) · The Global Risks Forum (GRF), with GCRI Canada as Consortium Secretariat · the programme year (quarterly NLC alignment; the Year-One Gateway) · systems [NXS-HUB](/organization/systems/nxs-hub.md), [NXS-RLS](/organization/systems/nxs-rls.md), [NXS-NSF](/organization/systems/nxs-nsf.md) · framework page (NLS). **In brief.** The previous Parts establish what the Nexus Leadership System (NLS) is, why it exists and how its institutions, Leadership Councils, Annual Leadership Contribution Plans, evidence, Foundry, Universe, governance pathways, integrity architecture and federation fit together. This page belongs to the Nexus Leadership System (NLS), read as the leadership method of the operating model: it describes how leaders selected in a personal capacity contribute through the National Leadership Council (NLC), alongside the Helix councils of the National Nexus Consortium (NNC) and the National Working Groups (NWG). 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; no council decides for a public authority. The method aligns with international practice ([ISO 2018](https://www.iso.org/standard/65694.html); [OECD 2014](https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405)). {% hint style="info" %} **Read with the current model (21 October 2026).** The "Leadership Councils" of this framework correspond, at national level, to the [National Leadership Council (NLC)](/organization/governance-in-operation/nlc.md), the leadership pillar of [National Nexus](/organization/governance-in-operation/national-nexus.md); the regional and global leadership councils are the councils of the GRF council architecture, in formation ([Councils](/organization/governance-in-operation/councils.md)). Institutions take part through the six Helix councils of the [NNC](/organization/governance-in-operation/nnc.md) (SPC, IOC, ARC, CMC, CIC and the FIR pathway); expert work runs through [NWG](/organization/governance-in-operation/nwg.md) assignments, with the six CERTs under them. Earlier labels are mapped in running text: Competence Cells are the atomic units of the NWG fabric, formed at institution, community or agency level; a Competence Cell can serve as a CERT, Investors Councils are the Financial Institutions and Regulators (FIR) pathway, `Nexus Grid` is the `Nexus Network` and [NXS-NET](/organization/systems/nxs-net.md), Protocol Authority is NXS-NSF ([Reference](/organization/reference.md)). Leadership work follows [the programme year](/organization/programme/the-programme-year.md): mandate at G0, quarterly alignment, Action Week, renewal at G7. {% endhint %} ## 25. PRACTICAL LEADER GUIDE The previous Parts establish what the Nexus Leadership System (NLS) is, why it exists and how its institutions, Leadership Councils, Annual Leadership Contribution Plans, evidence, Foundry, Universe, governance pathways, integrity architecture and federation fit together. Part XXV addresses a more immediate question: **What should I actually do as a Nexus leader?** This practical leader guide supports Leadership Council members through orientation, contribution planning, evidence management, quarterly review, governance pathways and National, Regional and Global leadership. We design NLS so that a member should not need to understand every part of the full institutional architecture before making a useful contribution. At the same time, serious leadership requires more than attending meetings and waiting for instructions. The leader needs to understand their institutional home, contribution pathway, relevant systems, responsibilities, evidence and the practical rhythm through which work moves. The operating journey is therefore deliberately progressive. The first 30 days establish context. The first 90 days establish a credible leadership proposition. The Annual Leadership Contribution Plan turns that proposition into structured work. Quarterly review creates correction. Foundry preserves continuity. Nexus Universe tests and integrates. The Leadership Ledger preserves contribution. The Year-One Gateway determines what should happen next. The practical doctrine is: **Understand the system → define the contribution → test it → record the evidence → correct the work → determine the next legitimate state.** *** ### 25.1 Your First 30 and 90 Days #### 25.1.1 The first 30 days are for institutional orientation During the first 30 days, we do not expect a new member to arrive with a fully developed solution to a systemic problem. We expect the leader to understand the environment they have entered. This includes the purpose of NLS, the role of the Leadership Council, the differentiated responsibilities of GCRI, GRF and GRA, the function of GCRI Canada as Lead Operating Steward of the common leadership system, the relationship between Council, Desk, Foundry, Universe, Working Groups and Portfolios, and the National, Regional or Global context in which the member will operate. The objective is institutional literacy before ambitious commitment. A leader who begins by understanding how the system works is better positioned to contribute in a way that Nexus can actually use. *** #### 25.1.2 Establish your active institutional identity early The first month should make clear who the member is inside NLS. This includes the member's primary Council assignment, primary institutional home, external professional affiliation, broad contribution domain and any existing institutional capacities that materially affect participation. We also seek early clarity concerning how the member wishes to be described publicly, what expertise they bring and which claims about their role are appropriate. This protects the leader from role ambiguity later. A National Leadership Council Member should understand that Council membership does not itself make them a representative of government or of every Nexus institution. A Global leader should understand that geographic scope does not create superior authority over National leaders. Identity is established first because almost every later pathway depends upon it. *** #### 25.1.3 Use the first 30 days to listen before over-designing A new member will often see opportunities quickly. That is valuable. We nevertheless encourage leaders to spend enough early time understanding the existing National Portfolio, Council priorities, institutional relationships, unresolved questions and other member contributions before defining a major new programme. Many apparently new ideas already connect to existing work. Others depend on institutional conditions that are not immediately visible. Early listening reduces duplication and helps the leader determine whether their greatest contribution is a new proposition, support for an existing one, a Working Group, a relationship, research, mentoring or another form of leadership. The objective is not passivity. It is informed entry. *** #### 25.1.4 The first 30 days should identify your strongest contribution horizon A member should begin identifying the area in which their expertise, relationships and leadership capacity can create the strongest legitimate value. The relevant horizon may be a domain such as water, energy, AI, infrastructure, health, finance-readiness or governance. It may be a geographic contribution. It may concern institution building, research, leadership development, risk intelligence or federation. The first contribution should be sufficiently focused that it can become testable. A broad ambition such as "improve resilience" is usually too large to guide the first year. A bounded proposition such as developing a cross-sector National capability around a defined dependency can become more operational. The purpose of the early period is to move from **general interest toward a plausible leadership proposition**. *** #### 25.1.5 The first 90 days convert orientation into an operating proposition By approximately the first 90 days, the member should ordinarily have progressed from general orientation into a more structured view of their intended contribution. This does not mean the work is fixed. It means the leader should increasingly understand the problem they wish to address, why it matters, which geography or institutional system is relevant, who else needs to participate, what evidence currently exists, what remains uncertain and what a realistic first-year outcome could be. The first 90 days therefore bridge orientation and Annual Leadership Contribution Planning. The leader should emerge with enough context that a substantive Plan can be developed without pretending that every dependency is already known. *** #### 25.1.6 Establish relationships before you need them The first 90 days are also the period in which a leader should begin understanding the people and institutional interfaces relevant to their contribution. This may include Council peers, the National Desk, Working Group Leads, relevant technical teams, institutional partners, Regional leaders or domain specialists. Relationships should follow substantive work rather than conventional networking for its own sake. The strongest early relationships help the leader understand the system, challenge assumptions and identify where capability already exists. NLS becomes more valuable when leaders know **who understands which part of the system and how to work with them responsibly**. *** #### 25.1.7 Do not measure the first 90 days by visibility New members should not feel pressure to secure a public role, Chair position, speaking opportunity or high-profile programme immediately. The first 90 days are successful when the leader develops institutional understanding, credible relationships and a well-grounded contribution proposition. Visible leadership may follow later. Early substance matters more than early profile. A Leadership System designed around long-term stewardship should reward leaders who build the foundations of useful work before seeking recognition for it. *** ### 25.2 Building and Using Your Annual Leadership Contribution Plan #### 25.2.1 The Plan is the practical centre of your leadership year The **Annual Leadership Contribution Plan**, or ALCP, converts the member's participation from broad intent into a structured leadership proposition. We use the Plan to answer several practical questions at once. What are you trying to contribute? Why does it matter? Which system or geography is involved? Who needs to participate? What decision or institutional pathway matters? Which dependencies could prevent progress? What evidence would tell us whether the work is improving? What can reasonably be achieved during this cycle? The Plan is not a performance contract guaranteeing an outcome. It is the principal working compact through which the member and NLS organize a year of purposeful leadership. *** #### 25.2.2 Begin with the problem, not the solution A strong Plan usually begins with a clear description of the problem or opportunity rather than a preferred intervention. This matters because experienced leaders often arrive with methods or technologies they know well. NLS asks whether the proposed solution actually fits the system in which it would operate. A technology may be impressive while the institutional owner remains unclear. A finance concept may be premature because the underlying programme is not ready. A governance solution may address symptoms rather than the actual dependency. The Plan should therefore make the problem sufficiently visible that the solution can change if the evidence requires it. *** #### 25.2.3 Define a realistic contribution that you can personally influence The member should distinguish the contribution they can reasonably make from the wider system outcome they hope eventually to support. A leader may be able to create a National Working Group, develop a method, build an institutional relationship, test a proposition, produce evidence or strengthen a Portfolio item. They may not control whether a government adopts the proposal, a financier funds it or an operator implements it. The Plan should therefore be ambitious without becoming institutionally fictional. A useful Plan identifies **what the member can contribute, what Nexus can support and what remains dependent on other competent institutions**. *** #### 25.2.4 Map the institutional pathway Every serious Plan should ask who matters to the work. Which institution owns the underlying issue? Which organizations can contribute knowledge? Which institution would need to authorize later implementation? Which actors are affected by the proposition? Which relationships already exist? Which ones need to be developed? This institutional map can be more important than the technical solution. Many otherwise strong programmes fail because the leadership architecture around them remains poorly understood. The Plan should therefore identify the route from idea to legitimate institutional consequence rather than assuming that technical quality alone will create adoption. *** #### 25.2.5 Define evidence before the work becomes difficult to evaluate The Plan should identify what evidence would help determine whether the contribution is progressing. Evidence need not always be quantitative. It may include a completed institutional map, functioning Working Group, validated method, successful scenario, formal institutional response, technical test, improved Portfolio state or another observable condition appropriate to the work. Defining evidence early reduces the risk that success is redefined afterward around whatever happened to occur. The Plan becomes stronger when the leader knows **what would cause them to believe the proposition is working and what would cause them to reconsider it**. *** #### 25.2.6 Identify major dependencies and constraints The member should ask what the work depends upon. Does it require public-institution access? Technical capability? Data? Another National node? Finance-readiness analysis? Foundry support? A separate professional assignment? A community relationship? A Working Group? Legal or regulatory context? Dependencies do not weaken the Plan. Making them visible strengthens it. A proposition whose success depends on ten unstated conditions is far less mature than one that understands those conditions explicitly. *** #### 25.2.7 Build Four-Way Value into the Plan The Plan should consider value across the Four-Way architecture established in Part XXI. How does the work create value for Nexus? How might it strengthen the relevant country, Region or system? What legitimate value may return to the leader's institution? What should the leader learn or develop personally? Not every dimension requires equal emphasis. The purpose is to ensure that the contribution does not become persistently extractive or purely self-serving. A strong Plan creates a credible field of reciprocal value. *** #### 25.2.8 Treat the Plan as a living institutional object The Plan should change when the evidence changes. Quarterly review may reveal that a dependency was misunderstood. A new institution may need to join. A technology may fail testing. A better contribution pathway may emerge. The member's professional capacity may change. These are reasons to update the Plan, not reasons to preserve an obsolete version for the appearance of consistency. NLS values **disciplined correction over performative adherence to the original idea**. The Plan is successful when it helps the member navigate reality intelligently. *** ### 25.3 Quarterly Review #### 25.3.1 Quarterly review is the main correction rhythm of the Plan We use quarterly review to prevent the ALCP from becoming an annual document that is forgotten between onboarding and Year-One Review. The quarterly rhythm allows the member and the relevant NLS support environment to examine what has changed, what evidence has emerged and what the next quarter should prioritize. The review should remain proportionate. It is not intended to become a large reporting exercise. Its purpose is to preserve institutional learning while enough time remains to change direction meaningfully. *** #### 25.3.2 Review the state of the contribution, not merely completed activity The most important quarterly question is not **“How many things did you do?”** It is **“What state has the contribution reached?”** Has the problem become clearer? Has a Working Group formed? Has the proposition moved from Concept to Designed? Has a test been completed? Has institutional ownership become stronger? Has evidence shown that the original approach needs revision? Activity matters insofar as it helps explain state change. NLS seeks progress in institutional maturity rather than accumulation of tasks. *** #### 25.3.3 Review the evidence honestly Quarterly review should create room for evidence that does not support the preferred narrative. A member may discover that an institutional relationship is weaker than expected. A test may fail. A proposed partner may withdraw. A National context may make the original approach impractical. These findings should enter the review. The purpose is to improve the next quarter. A review process that rewards only positive reporting encourages leaders to hide precisely the information NLS most needs in order to learn. *** #### 25.3.4 Review the dependencies around the member A contribution may stall even when the member is performing well. The Desk may lack capacity. Foundry functionality may be needed. Another institution may not yet be ready. Resources may remain unavailable. Quarterly review should distinguish a member-performance issue from a system dependency. This allows NLS to ask what it must change around the leader. Reciprocity requires the institution to examine its own contribution to the success or failure of the Plan. *** #### 25.3.5 Use the review to narrow priorities where necessary As the year develops, the member may discover that the Plan contains too many parallel ambitions. Quarterly review is an appropriate place to reduce scope. One well-developed priority often creates more value than several partially advanced ones. Strategic narrowing should not be interpreted as reduced ambition. It can be evidence that the leader now understands the problem more deeply. *** #### 25.3.6 Record material corrections Where the Plan changes materially, the institutional record should capture the revised state. This preserves the learning path. At Year-One Review, the member and institution should be able to understand not only where the contribution ended but how the reasoning changed during the year. The correction history can itself become useful evidence of leadership development. A leader who adapts intelligently may demonstrate greater capability than one whose original Plan survived only because difficult evidence was ignored. *** ### 25.4 Working with Nexus Universe #### 25.4.1 Universe is the annual proving environment for relevant leadership work Nexus Universe is not simply an event a leader attends. Where a member's Plan, Mission, Working Group or Portfolio priority is relevant to the annual cycle, Universe provides an opportunity to integrate the proposition with a more demanding environment of scenarios, technical capability, institutional interaction, observation, evidence and after-action learning. Not every member needs the same Universe role. The purpose is to connect the right leadership work to the right proving environment. Universe should serve the contribution rather than become an annual visibility requirement. *** #### 25.4.2 Preparation begins before the annual Action programme Members should not arrive at Nexus Universe with an undeveloped proposition and expect the annual programme to solve it automatically. The strongest Universe contributions are prepared during the year. The objective, hypothesis, scope, authority, participants, environment, evidence requirements, risks, safeguards, acceptance criteria and intended learning should be understood sufficiently before intensive testing begins. This preparation improves the quality of the annual cycle. It also ensures that the resulting evidence can be interpreted afterward. *** #### 25.4.3 Know what your Universe role actually is A leader may participate as a Mission Lead, scenario contributor, observer, reviewer, technical specialist, institutional challenger, research contributor, Council representative or another legitimate capacity. The role should remain explicit. Participation does not mean the leader owns the whole exercise. Observation does not mean approval. A speaking role does not create operational authority. A test participant does not become a certifier. Active capacity remains important during Universe precisely because many institutions and roles come together in one environment. *** #### 25.4.4 Use Universe to test assumptions, not to defend them The member should enter Universe prepared for the possibility that the proposition will need to change. A successful annual cycle may expose a serious weakness. A scenario may reveal that the institutional owner is unprepared. A technology may fail. A cross-border dependency may emerge. A safeguard may prove inadequate. These are useful results. Universe is valuable because it places propositions under enough pressure to reveal what ordinary planning can miss. The leader's responsibility is to learn from the result, not to protect the appearance of success. *** #### 25.4.5 Participate seriously in after-action review The annual cycle is incomplete without after-action review. The member should help identify what happened, which assumptions changed, what evidence is credible, which findings remain uncertain and what should enter the Upgrade Docket or next Annual Leadership Contribution Plan. This closes the learning loop. Without after-action discipline, Universe risks becoming a memorable experience whose institutional value dissipates afterward. The leadership objective is to convert annual intensity into persistent capability. *** #### 25.4.6 Carry Universe learning back into the year-round system After Universe, relevant learning should return to Foundry, the Leadership Ledger, National or Regional Portfolios, Working Groups and the member's Plan. A tested proposition may become ready for deeper validation. Another may return to redesign. A Regional issue may require a new Working Group. A recurring technical problem may justify a Foundry improvement. Universe therefore ends by changing the persistent system. Its purpose is renewal, not closure. *** ### 25.5 Recording Contribution #### 25.5.1 Record material contribution while context is still available Members should not wait until Year-One Review to reconstruct everything they contributed. Important work should enter the Leadership Ledger or relevant institutional record close enough to the activity that evidence, attribution and context remain understandable. This does not mean recording every meeting or minor interaction. The focus should remain on material contributions that help explain the member's leadership journey and the evolution of the work. A strong record reduces dependence on memory and makes annual review substantially more meaningful. *** #### 25.5.2 Distinguish activity from contribution Attending a meeting is activity. Providing a substantive analysis that changes the Working Group's direction may be a contribution. Making an introduction is an activity that may later become a contribution if it materially advances an institutional pathway. Delivering a verified method is stronger still. Members should therefore avoid treating every act as equivalent. The Ledger becomes more useful when it records **what the leader actually contributed and what state that contribution reached**. *** #### 25.5.3 State your role accurately Where work is collaborative, members should identify the role they actually performed. Did you initiate, author, co-author, advise, review, convene, facilitate, mentor, provide data, lead a Working Group or support institutional routing? These functions can all be valuable. Accurate attribution protects the leader and peers. NLS should not reward inflated claims over precise ones. *** #### 25.5.4 Preserve evidence proportionately Material contributions should be supported by evidence appropriate to the claim. A public publication provides clear evidence of authorship. A Working Group record may support another form of contribution. A National institution's response may support evidence of engagement. A test report may support validation. The member can submit or identify evidence. Where verification is required, the member should not self-create the final verified state merely because they supplied the evidence. The distinction remains: **Claim → evidence → review where appropriate → verified institutional state.** *** #### 25.5.5 Record negative and corrective learning A Leadership Ledger containing only achievements would provide a misleading history. Where a material contribution reveals that a proposition should change, pause or conclude, that learning can be recorded appropriately. The objective is not to create a negative record about the member. It is to preserve institutional intelligence. A strong leader's history may include important ideas that were tested and rejected. That can demonstrate judgment, not failure. *** #### 25.5.6 Review your record before the annual gateway Before Year-One Review or annual renewal, members should examine the material leadership record for accuracy. Important contributions may be missing. An attribution may require correction. A Plan state may have changed. A completed role may still appear active. This is not an invitation to optimize the record cosmetically. It is an opportunity to ensure that the institutional picture is sufficiently accurate for the next-state decision. A good gateway depends on a trustworthy history. *** ### 25.6 Raising a Concern #### 25.6.1 Raise concerns early where possible Members should not assume that raising a concern is incompatible with collegial leadership. If something appears materially wrong, unclear or inconsistent with the integrity of NLS, early clarification is usually preferable to allowing uncertainty to accumulate. The issue may concern a role, contribution attribution, conflict, public claim, information handling, opportunity process, conduct issue or another part of the Leadership System. Many concerns can be resolved before they become larger institutional problems. Responsible challenge is part of leadership. *** #### 25.6.2 Use the most appropriate route A routine operational concern may belong with the Desk or Secretariat. A Council-deliberation issue may be raised with the Chair. A contribution-record question may belong with the relevant NLS operating function. A more serious integrity or conduct concern may require another appropriate institutional route. Members should not be expected to navigate the full architecture alone where the correct route is unclear. The common principle is to place the concern where it can be examined without requiring the member to report exclusively through the person or function the concern itself involves. *** #### 25.6.3 Separate disagreement from misconduct Members will disagree frequently. Disagreement about strategy, evidence, timing or institutional priorities does not automatically create an integrity concern. A mature leader should be capable of challenging an idea through ordinary Council processes without escalating every difference into a grievance. At the same time, the language of "strategic disagreement" should not be used to dismiss genuine concerns about conduct, conflict, misrepresentation or unfair process. The member should ask what kind of issue is actually present. This distinction helps NLS respond proportionately. *** #### 25.6.4 Provide enough context to make the issue examinable Where possible, a concern should identify the relevant event, process, relationship or institutional state and why it matters. The member does not need to prepare a legal brief. The goal is to move from general unease toward a question the institution can investigate or clarify. Where complete evidence is unavailable, the member can still raise the concern and identify the uncertainty. A credible concern process should allow the institution to determine what further information is required. *** #### 25.6.5 Use reconsideration where a material decision appears wrong If a material NLS decision affecting the member's standing, contribution record, office, access or pathway appears to have been based on incomplete information or procedural error, the member may raise the issue through the appropriate reconsideration route. Reconsideration is not automatic reversal. It allows the institution to examine whether the original state remains justified. The ability to correct meaningful error is part of institutional maturity. *** ### 25.7 Contributing to a National Nexus #### 25.7.1 Begin with the country as a system National leadership should not begin from the assumption that one sector can be understood independently. Members should examine how their domain interacts with the wider National risk and readiness architecture. An energy leader should understand relevant water, cyber, finance and infrastructure dependencies. An AI leader should understand compute, data, energy, public-institution, rights and security conditions. A finance leader should understand the physical systems and programme-readiness evidence beneath the financial proposition. The National Nexus exists partly to create these connections. The member contributes most effectively when they bring deep expertise without treating their domain as isolated. *** #### 25.7.2 Understand the National Portfolio The National Portfolio is one of the principal objects through which country-level leadership becomes cumulative. Members should understand which priority risks, programmes, capability gaps and opportunities are already represented within it and how their own Plan relates to those objects. The member may deepen an existing Portfolio priority, identify a missing one or help clarify the institutional route of a current item. The objective is to connect individual leadership contribution to a shared National field of work. *** #### 25.7.3 Work through the National Desk The National Desk provides persistent operating continuity. Members should therefore avoid conducting significant National Nexus work entirely through personal relationships without the Desk understanding the institutional context. The Desk does not need to control every interaction. It should know enough to preserve continuity, connect relevant actors, maintain records and support handoff. This is particularly important where the member's relationship or professional role later changes. The Desk helps convert personal leadership leverage into institutional capability. *** #### 25.7.4 Use Working Groups for bounded substantive work Where a National issue requires deeper attention from several relevant contributors, a Working Group may be more effective than repeatedly using full Council time. Members should help ensure that the Working Group has a clear purpose, appropriate capability, evidence discipline and an understood route back into the Council, Portfolio, Foundry, Universe or another institutional pathway. Working Groups are not smaller Councils. They exist to develop bounded questions. The member should enter them prepared to contribute substantively rather than simply represent status or affiliation. *** #### 25.7.5 Government engagement should remain precise National leaders may develop important relationships with government institutions. They should distinguish dialogue, technical assistance, consultation, participation, formal collaboration and actual government mandate. A meeting with an official does not make Nexus a government programme. A public official participating in a Council does not make the Council a government body. The National Nexus should build credibility through usefulness and institutional discipline rather than through inflated claims of public authority. *** #### 25.7.6 National ownership includes developing others External and globally experienced leaders should help strengthen National capability where possible. A contribution is stronger when National leaders, institutions or staff understand the method and can continue the work afterward. This may involve mentoring, documentation, Working Group development, Desk support or knowledge transfer. The member's goal should not be to become permanently indispensable to the National system. The goal is to make the National system more capable. *** ### 25.8 Working Across Regions and Globally #### 25.8.1 Wider geographic work should follow actual system need Members should enter Regional or Global work because the problem requires that scale, not because wider geography appears more prestigious. A shared watershed, infrastructure corridor, supply chain, cyber dependency or frontier technology may require Regional or Global analysis. A purely National question may not. The member should therefore ask what additional capability becomes possible by widening the operating scale. If the answer is unclear, the work may belong primarily at National level. *** #### 25.8.2 Carry National context upward National leaders participating Regionally should bring enough country context that the Regional system does not flatten National differences. The member may explain why the same Regional proposition has different implications across countries, where National readiness differs or which institutions hold responsibility domestically. This contextual translation is one of the most valuable federation functions a National leader can perform. The Region requires National grounding to remain useful. *** #### 25.8.3 Carry Regional and Global learning back downward Federation should not become an extractive process in which leaders contribute National knowledge upward but little value returns. Members participating Regionally or Globally should consider which comparative insights, methods, relationships or frontier developments may be useful to their primary Council or National system. This does not mean transferring restricted information indiscriminately. It means using the federation to improve local capability. The learning loop should remain multidirectional. *** #### 25.8.4 Direct Regional or Global leaders still need institutional grounding Members whose work is inherently Regional or Global may enter those levels directly. They should still understand how their propositions encounter National systems. A Global AI architecture, for example, may need to be interpreted through different National data, infrastructure and governance conditions. A Global finance perspective may need to understand country-level programme readiness. Wide scope does not remove the need for context. It increases the need for disciplined translation. *** #### 25.8.5 Use cross-Regional work selectively Some challenges connect countries across conventional Regional boundaries. Members may participate in cross-Regional Missions or Working Groups where such a system justifies it. NLS should avoid creating a permanent new institutional layer for every cross-regional topic. The existing federation can organize bounded cross-Regional work while preserving the member's primary home and the authority of participating institutions. Matrixed cooperation is often more appropriate than additional hierarchy. *** ### 25.9 Operating in Multiple Capacities #### 25.9.1 Know which capacity is active A mature NLS leader may hold several legitimate roles simultaneously. You may be a Leadership Council Member, Chair, Working Group Lead, formal governor of one Nexus institution, external executive and separately assigned professional. The practical rule is simple: **Know which capacity explains your participation in the current matter.** This affects what information you can use, what you can claim, what responsibility you hold and which institution you represent. Role complexity is manageable when active capacity remains clear. *** #### 25.9.2 Do not let one role silently expand another A Council Chair should not assume that the office creates Board authority. A Board member should not treat ordinary Council dialogue as formal governance. A contracted professional should not use Council status to broaden the scope of the assignment. A senior external executive should not assume that the prestige of their employer creates additional Nexus authority. Each role may create legitimate value. The system becomes fragile when one role begins absorbing responsibilities that belong to another. *** #### 25.9.3 Separate information appropriately Where multiple capacities provide access to different information, members should be careful about moving material among them. Board information may not belong in Council discussion. Confidential professional information may not belong in a Working Group. Restricted National information may not be appropriate for a Global forum. The leader should not become an uncontrolled information bridge simply because they personally have access in several contexts. Information follows institutional purpose. *** #### 25.9.4 Surface relevant conflicts early Multiple capacities can create specific conflicts or competing responsibilities. Members should identify these where materially relevant rather than waiting until a difficult decision occurs. A Council Member whose employer may become a provider, a governor who also undertakes a professional assignment or a public official participating in a National Nexus may require additional contextual clarity. Disclosure often allows the person to continue contributing credibly. The objective is management, not blanket exclusion. *** #### 25.9.5 Avoid collecting roles beyond realistic capacity NLS values capable leaders, but the system should not reward role accumulation for its own sake. Holding several important offices can create workload, concentration and succession risk. Members should consider whether accepting another role will improve institutional value or merely concentrate responsibility around the people already most visible. Leadership maturity sometimes means declining a role so another capable person can develop. *** ### 25.10 Preparing for the Year-One Gateway #### 25.10.1 The Gateway begins with evidence, not aspiration As the first twelve months approach completion, the member should review the year as it actually occurred. What contribution was designed? What was tested? What evidence exists? What changed? What remains unresolved? Which institutional relationships strengthened? What did the member learn? What value did Nexus provide? What value did the member create? The Gateway should not begin by selecting a preferred title for Year Two. It should begin by understanding the evidence. The next pathway follows from that picture. *** #### 25.10.2 Prepare the Year-One Evidence Package The member should work with the relevant NLS environment to ensure that the principal Year-One objects are sufficiently current. These include the Leadership Baseline, institutional home and scope, relevant disclosures, Annual Leadership Contribution Plan, testing and evidence history, pre-scale state where applicable, stakeholder and authority map, key dependencies, contribution record, Four-Way Value reflection, Scale Readiness Profile and a proposed next-state recommendation. The purpose is not bureaucratic completeness for its own sake. The package should allow the Year-One Review to make a defensible next-state decision. *** #### 25.10.3 Assess both the proposition and yourself The member should distinguish their own readiness from the maturity of the proposition. You may be ready for deeper responsibility while the programme still requires additional validation. The proposition may be strong while your professional availability has decreased. The Council may need a particular capability that is different from the pathway you originally imagined. The Gateway therefore considers the relationship among **leader readiness, contribution maturity and system readiness**. All three matter. *** #### 25.10.4 Consider the full range of legitimate next pathways The member should approach the Gateway understanding that several outcomes can represent success. These include Strategic Delivery, continuing substantive Council service, Council office, governance consideration where the separate conditions exist, a professional assignment where a real need and process exist, Extended Validation, Pause, Alumni or Exit. The member may also combine compatible pathways. There is no universal best outcome. The best next state is the one most consistent with evidence, capacity, institutional need and long-term value. *** #### 25.10.5 Use the Gateway to correct expectations The first year may reveal that the member initially misunderstood some aspect of NLS. A leader may have expected a Regional role and discovered that their strongest contribution is National. Another may have expected a Board pathway and discovered that Council service itself provides the greater value. Another may have joined with a narrow technical idea and developed a much broader systems leadership proposition. The Gateway should make room for this learning. A changed ambition can represent development. The purpose of Year One is partly to replace pre-entry assumptions with lived institutional evidence. *** #### 25.10.6 Leave the Gateway with a clear next state The Year-One Review should conclude with enough clarity that the member understands what the next cycle requires. If continuing through Strategic Delivery, what is the next maturity objective? If remaining a Council Member, what substantive contribution continues? If entering Extended Validation, which unresolved uncertainty must be tested? If moving toward Council office or governance consideration, what separate process applies? The member should not leave the Gateway in an ambiguous state between several implied roles. A clear next state is one of the principal outputs of the review. *** ### 25.11 Preparing for Council Office #### 25.11.1 Seek the function, not the title Members considering Chair, Vice-Chair, Rapporteur, Working Group Lead or another Council office should begin by understanding what the institution actually needs. A Council office exists because a recurring function requires stewardship. The strongest candidate is therefore not necessarily the member with the highest external title or greatest public visibility. The relevant question is whether the leader can perform the institutional function well. Members should ask: **What responsibility does this office carry, and am I actually suited and available to carry it?** *** #### 25.11.2 Demonstrate stewardship before seeking office Council-office suitability becomes visible through ordinary participation. Can the member create space for others? Do they prepare seriously? Can they preserve strategic focus? Do they challenge constructively? Can they work across competing perspectives? Do they develop peers rather than centralize every contribution around themselves? These behaviors matter because office amplifies how the leader affects the institution. The strongest pathway into office is therefore a demonstrated record of stewardship rather than lobbying for the title. *** #### 25.11.3 Understand that office changes responsibility A Chair must sometimes place the needs of the Council above their own preferred initiative. A Working Group Lead becomes responsible for the coherence of a group rather than merely the strength of their own ideas. A Vice-Chair carries continuity and succession responsibilities. Members should therefore consider whether they genuinely want the function attached to the office, not merely the recognition associated with it. Office creates obligation. The title is secondary. *** #### 25.11.4 Consider succession from the beginning A member entering office should think immediately about how the function can become stronger and more transferable. Who else should develop leadership capability? What records need to improve? Which relationships should become institutional rather than personal? How will the next officeholder understand the current state? Office is temporary. The member's success should therefore include making the eventual transition easier than the transition they inherited. *** #### 25.11.5 Office does not displace the member's substantive leadership identity A Chair remains a Council Member and may continue a bounded substantive contribution where capacity permits. The office does not need to consume the leader's entire NLS identity. At the same time, the member should recognize that office creates collective responsibilities that may require narrowing personal work. The correct balance depends on context. NLS values officeholders who remain substantive leaders without allowing their own programme to dominate the Council they steward. *** ### 25.12 Governance Consideration in Practice #### 25.12.1 Council service comes before any general governance eligibility A member considering future governance should understand the threshold clearly. After at least **twelve consecutive months in good standing**, the member may become eligible for consideration where an actual governance need exists and the relevant GCRI, GRF, GRA or other competent institution's governing framework permits it. This means eligibility can emerge. It does not mean a nomination process has started. The distinction should shape expectations from the beginning of NLS participation. *** #### 25.12.2 Do not design your first year as a Board campaign The purpose of the first year is formation, planning, testing and validation. Members who treat every Council activity as a step toward Board appointment risk distorting the leadership relationship. Council service should have value independently. A strong first year creates evidence about how the member operates, but that evidence may support Strategic Delivery, continuing Council service, office, mentoring, federation or another pathway rather than formal governance. The best preparation for possible future governance is therefore **excellent Council service**, not title-seeking. *** #### 25.12.3 Understand the B0-B4 states The NLS governance pathway distinguishes: **B0:** Eligible for Consideration\ **B1:** Pre-Nomination Review\ **B2:** Formal Nominee\ **B3:** Selected, Elected or Appointed Governor\ **B4:** Not Selected, Deferred, Withdrawn or Concluded These states are deliberately separate. A member at B0 is not a nominee. A member under B1 review is not a director. A B2 nominee still does not hold the governance role. Only the competent institution can create B3 through its valid process. Members should use these states accurately in both internal and public contexts. *** #### 25.12.4 Governance need comes before candidate ambition A formal pathway begins because the competent institution needs a particular governance capability. The institution may require experience in systems science, leadership, finance-readiness, technology, institution building, geography, succession or another dimension relevant to its current Board composition. The member's interest is relevant. It does not create the vacancy or determine the need. This protects the governance system from becoming an automatic destination for experienced Council Members. *** #### 25.12.5 Governance consideration is entity-specific Suitability for one Nexus institution does not automatically imply suitability for another. GCRI, GRF and GRA have differentiated institutional purposes. A member whose record is especially relevant to evidence, technical assistance and systems science may have a different fit from one whose strengths centre on leadership formation, federation or finance-readiness. The competent institution determines the capability it needs. NLS provides a common evidence architecture around the candidate. It does not make governance roles interchangeable. *** #### 25.12.6 Appointment creates a new capacity, not an upgraded Council title If formal appointment eventually occurs, the member enters a new institutional capacity. Their Board or governance responsibility belongs to the competent entity. Council membership, if continuing, remains a separate role. The same person may therefore participate as a Council Member in one context and a formal governor in another. Members should understand this distinction before appointment because it affects information, responsibility, access and public representation. Formal governance does not absorb the Council. The Council does not become a Board. *** #### 25.12.7 Non-selection does not invalidate Council success Formal governance roles are limited and based on specific institutional needs. A highly capable Council Member may never enter B1 or B2. Another may be nominated but not selected. Another may withdraw because professional circumstances change. These outcomes do not erase the value of the member's leadership journey. The wider NLS architecture deliberately provides many consequential pathways beyond governance. The member should therefore evaluate their contribution through the full leadership system rather than one possible office. *** #### 25.12.8 The practical leader journey The practical NLS journey can therefore be summarized as: **Orient → Establish Identity and Context → Diagnose → Build the ALCP → Contribute → Review Quarterly → Test Where Appropriate → Record Evidence → Correct → Participate in Universe → Prepare the Year-One Package → Enter the Gateway → Select the Next Legitimate Pathway → Continue, Deepen, Lead, Federate, Transition or Conclude** The journey is structured but not rigid. Different leaders will move through it differently. The common discipline is that each stage should make the next stage more informed. Leadership becomes institutional when experience is converted into evidence, evidence into better judgment, judgment into capability and capability into durable stewardship. *** ## PART XXV FRAMEWORK PRINCIPLES **Start with context before ambition.** The first 30 and 90 days are designed to help leaders understand their Council, institutional home, National or wider system, existing Portfolios, relevant peers and the boundaries of their role before committing to major propositions. Early listening, orientation and accurate identity reduce duplication and make later contribution more useful. **Plan, test and correct rather than merely participate.** The Annual Leadership Contribution Plan is the practical centre of the leadership year. Quarterly review, Working Groups, Foundry and Nexus Universe turn that Plan into a learning cycle. Leaders should define realistic outcome ceilings, make dependencies visible, test assumptions and allow evidence to change the work. Progress is measured through improved institutional state, not simply activity volume. **Record contribution accurately and preserve institutional truth.** Material contribution should enter the Leadership Ledger with appropriate role, evidence, attribution and state. Members may submit claims and evidence but should not self-create consequential verified states. Negative findings, corrections and incomplete outcomes can remain valuable parts of the leadership record when they improve future institutional judgment. **Operate through the right capacity and scale.** National, Regional and Global work should follow genuine system need. Multiple roles are legitimate, but the member should understand which capacity is active, what information belongs to it and which institution retains responsibility. Council office, professional assignment, governance capacity and external professional position remain distinct even when the same person holds several of them. **Use the Year-One Gateway to choose the next useful state.** The first twelve months do not culminate in automatic promotion. They culminate in evidence sufficient to determine whether the strongest next pathway is Strategic Delivery, continuing Council service, Council office, governance consideration, separate assignment, Extended Validation, Pause, Alumni or Exit. The aim is not movement toward the highest-sounding title. It is movement toward the form of leadership that can create the strongest legitimate institutional value next. *** ## OPERATING RELATIONSHIP Part XXV translates the full Nexus Leadership System into practical guidance for each Leadership Council member. It provides a working guide for systems leadership, Annual Leadership Contribution Plans, evidence management, leadership governance and federated National, Regional and Global coordination. The journey begins with orientation. During the first 30 days, the member learns the institutional architecture, establishes identity and begins understanding the Council and wider system. During the first 90 days, that understanding develops into a bounded leadership proposition capable of entering the **Annual Leadership Contribution Plan**. The ALCP becomes the principal working object for the year. It defines the problem, contribution, context, institutional pathway, evidence, dependencies, safeguards and intended value. It remains a living object and should change when stronger evidence appears. **Quarterly review** prevents the Plan from becoming static. It asks what institutional state has changed, which evidence matters, what dependencies remain unresolved and what should happen next. The review examines both the member and the support environment around the member. **Nexus Universe** provides the annual proving environment for relevant work. Leaders enter Universe with defined roles and prepared propositions, use the cycle to test rather than defend assumptions, and return resulting evidence into Foundry, Portfolios, Working Groups and the next Plan. The **Leadership Ledger** preserves the material contribution journey. Members should distinguish activity from contribution, describe their role accurately and preserve proportionate evidence. This record supports annual review, pathway decisions, opportunity routing, succession and longer-term institutional memory. Where concerns arise, the member should use the appropriate institutional route and distinguish ordinary strategic disagreement from integrity, conduct or process concerns. Fair review and correction remain part of the Leadership System. At National level, leaders work through the National Council, Desk, Model, Portfolio and Working Groups to strengthen sovereign-grounded capability. Regional and Global participation broadens the operating scale where actual system dependencies require it. Federation should move learning in both directions rather than extract National intelligence upward. Where the member holds several capacities, Part XVIII's zero-trust doctrine applies continuously. Membership is not office. Office is not governance. Governance is not executive management. Council access is not unrestricted information authority. Professional assignments remain separate. The first year culminates in the **Year-One Gateway**. The member prepares a credible evidence package and, together with the relevant institutional process, identifies the strongest next pathway. Council office may follow demonstrated stewardship and institutional need. Formal governance consideration can become possible only after at least twelve consecutive months in good standing and remains subject to a separate entity-specific pathway. The governing proposition of Part XXV is therefore: **A Nexus leader should always be able to answer five practical questions: What system am I working in? What am I actually contributing? What evidence tells us whether it is working? In which capacity am I acting? What is the next legitimate institutional state? When those questions remain clear, leadership can become cumulative rather than episodic.** ## NEXT ## PART XXVI: MODEL LEADERSHIP JOURNEYS ### National, Regional and Global Pathways; Council Formation; AI and Frontier Technology; Infrastructure and Systems; Risk Finance and Readiness; Governance and Institution Building; Year-One Gateways; Governance Transitions and Separate Professional Assignments Part XXVI will demonstrate how the NLS architecture works through a set of model leadership journeys. These are not mandatory scripts or promises of outcome. They will show how different leaders can enter the system, build an Annual Leadership Contribution Plan, work through National or Regional Councils, use Foundry and Universe, generate evidence, encounter Year-One Gateway decisions and move into Strategic Delivery, federation, Council office, governance consideration or separate professional assignments according to the needs and maturity of the work. ## Sources 1. ISO (2018). ISO 31000:2018 Risk management — Guidelines. Geneva: International Organization for Standardization. [www.iso.org/standard/65694.html](https://www.iso.org/standard/65694.html) 2. OECD (2014). Recommendation of the Council on the Governance of Critical Risks. OECD/LEGAL/0405. [legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405](https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405) 3. UN General Assembly (2024). The Pact for the Future, with the Global Digital Compact. A/RES/79/1. [undocs.org/A/RES/79/1](https://undocs.org/A/RES/79/1) **Standards that apply.** Masters: [Communities, Learning and Contribution](https://nexustandards.com/communities/) (PLANNED); [Governance, Security and Society](https://nexustandards.com/society/) (PLANNED). Standards: [NS-0](https://nexustandards.com/standards/ns-0/) (PROPOSED), [NS-1](https://nexustandards.com/standards/ns-1/) (PROPOSED), [NS-2](https://nexustandards.com/standards/ns-2/) (PROPOSED), [NS-3](https://nexustandards.com/standards/ns-3/) (PROPOSED), [NS-3b](https://nexustandards.com/standards/ns-3b/) (PROPOSED), [NS-4](https://nexustandards.com/standards/ns-4/) (PROPOSED), [NS-5](https://nexustandards.com/standards/ns-5/) (PROPOSED), [NS-8](https://nexustandards.com/standards/ns-8/) (PROPOSED), [NS-9](https://nexustandards.com/standards/ns-9/) (PROPOSED), [NS-10](https://nexustandards.com/standards/ns-10/) (PROPOSED), [NS-11](https://nexustandards.com/standards/ns-11/) (PROPOSED), [NS-12](https://nexustandards.com/standards/ns-12/) (PROPOSED), [NS-13](https://nexustandards.com/standards/ns-13/) (PROPOSED). Statuses are registry statuses on nexustandards.com, never adoption or certification. **In the GitBook.** [Programme](/organization/programme.md) · [Governance in operation](/organization/governance-in-operation.md) · [Systems](/organization/systems.md) · [Reference](/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/operations/frameworks/nexus-leadership-system-nls/xxv.-leader-guide.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.