> 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/vi.-first-year.md). # VI. First Year Understand the first-year Leadership Council journey, including formation, contribution planning, testing, validation, and Year-One Review. **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), [NXS-CMD](/organization/systems/nxs-cmd.md), [NXS-DSS](/organization/systems/nxs-dss.md) · framework page (NLS). **In brief.** We establish the first twelve months of Nexus Leadership Council membership as the Formation, Planning, Testing and Validation Year. 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 %} ## First Year in the Nexus Leadership System ### 6.1 The Formation Year #### 6.1.1 The first year as active institutional formation We establish the first twelve months of Nexus Leadership Council membership as the **Formation, Planning, Testing and Validation Year**. This period begins after admission into NLS and therefore takes place while the individual is already an active Leadership Council Member. The first year is not a provisional waiting period, an extended candidate assessment or a passive interval before "real" participation begins. It is the first full operating cycle through which the member learns the architecture, develops a substantive contribution proposition, participates in the Council, engages relevant Nexus capabilities and creates an evidence base from which deeper future responsibility can be considered. The distinction matters because a serious leadership institution should not invite experienced leaders into nominal standing and then defer meaningful participation for twelve months. Formation should occur through participation. The member learns Nexus by engaging with its systems, institutions, people and work. At the same time, NLS learns enough about the member's capabilities, interests, institutional context and contribution pattern to support a more mature long-term relationship. The first year is therefore simultaneously a **leadership-contribution cycle and an institutional-learning cycle**. The member is learning how Nexus operates, and Nexus is learning how the member can contribute most effectively. *** #### 6.1.2 Why a formation year is necessary Experienced leaders arrive with substantial capabilities, but prior seniority does not automatically establish how those capabilities should be applied within a new institutional architecture. A person may understand infrastructure deeply while having limited familiarity with Public-Private-Planet systems. A governance leader may possess extensive institutional experience while being less familiar with risk intelligence, digital systems or sovereign technology. A finance leader may bring strong capital-markets expertise while needing deeper exposure to physical-system dependencies or National Portfolio architecture. The purpose of the formation year is therefore not to test whether the leader is accomplished. Selection has already considered that question. The purpose is to determine how the leader's capability should be **situated, supported, challenged and developed within Nexus**. This requires time because meaningful leadership fit cannot be inferred reliably from a biography, interview or initial proposition alone. Institutional contribution becomes clearer through Council participation, peer interaction, Working Groups, evidence, National and Regional context and the practical experience of attempting to move an idea from broad ambition toward a more mature state. Formation is therefore a mechanism for reducing uncertainty in the leadership relationship before either the member or the institution assumes that a particular long-term pathway is appropriate. *** #### 6.1.3 Formation is not remediation We do not use the term formation to imply that incoming leaders are deficient and require correction before they can contribute. NLS is designed for accomplished people who already possess substantial experience and institutional value. Formation means placing those capabilities within a **new system of relationships, methods and responsibilities**. A highly experienced public official may need to understand how Nexus distinguishes Council leadership from the National Desk. A technology executive may need to understand how Foundry, Labs and Universe relate to institutional readiness. A systems scientist may need to understand how evidence becomes actionable through a National Portfolio. A senior finance leader may need to understand how the GRA readiness function connects to, but does not replace, GCRI evidence or GRF governance and leadership formation. Formation therefore develops interoperability between the leader and the institution. It is not remedial education. *** #### 6.1.4 The first-year institutional objective The central objective of the first year is to move the leadership relationship from **potential contribution to evidenced institutional readiness**. At admission, Nexus possesses a reasonable basis for believing that the leader can contribute meaningfully. By the end of the first year, we should know considerably more. We should understand where the leader creates distinctive value, which systems and institutions are most relevant to their work, how effectively they operate within the Council, what dependencies surround their proposed contribution, what support Nexus must provide, what evidence has been generated and which next pathway is justified. The first year should therefore produce greater clarity for both the member and the institution. A successful formation year does not require every Leadership Plan to become a large programme. It requires the leadership relationship to become more **intelligible, evidence-informed and institutionally useful**. *** #### 6.1.5 The first year as a bounded experiment in institutional fit We treat the first year partly as a bounded institutional experiment. The member and NLS begin with hypotheses about where the relationship may create value. Those hypotheses are then tested through real participation. The member may discover that the contribution initially imagined is too broad, too narrow, insufficiently differentiated or dependent on institutional conditions that do not yet exist. Another contribution may emerge that is more valuable than the original proposition. A National focus may reveal Regional implications. A technical proposition may prove to be primarily an institutional-development problem. A member recruited for one form of expertise may create unexpected value as a mentor, Council builder or cross-sector translator. NLS should make space for those discoveries. We do not regard movement away from an initial hypothesis as evidence that formation failed. In many cases it is evidence that formation worked. *** #### 6.1.6 Formation within an active Council The member's development does not occur in isolation from the Council. The Council itself is one of the principal formation environments. Through participation, the member encounters the Council's current priorities, institutional culture, systems context, Working Groups and leadership relationships. The member begins to understand what kinds of contribution the Council already possesses, where gaps exist and which forms of institutional value may be most useful. This is why the formation process cannot be completed entirely through one-to-one onboarding. The individual relationship matters, but Council fit becomes visible through participation in the collective leadership environment. The Council is therefore both the place in which the leader contributes and one of the environments through which the leader's NLS role is formed. *** #### 6.1.7 Formation within the wider Nexus architecture The first year should also progressively introduce the member to the wider system in proportion to their actual contribution. A leader does not need to become an expert in every Nexus institution, platform or programme. They do need enough institutional literacy to understand how their contribution relates to the broader architecture. This may involve GCRI evidence and systems science, GRF leadership formation and Nexus Universe, GRA finance and insurance-readiness, National or Regional Desks, Working Groups, National Models, National Portfolios, Foundry and other relevant capabilities. The purpose is not to maximize exposure. It is to ensure that the leader understands the parts of Nexus that materially affect their contribution. Formation therefore follows relevance rather than institutional tourism. *** ### 6.2 The First-Year Journey #### 6.2.1 The six-stage formation sequence We organize the first twelve months through six connected stages: > **Establish → Diagnose → Design → Test → Pre-Scale Validate → Review** These stages provide the common formation grammar of NLS. They do not require every member to progress according to identical dates or to complete one stage fully before any aspect of the next begins. Senior leadership development is rarely linear. Diagnosis may continue while the Plan is being designed. Testing may reveal new diagnostic questions. Quarterly review may cause the Plan to return temporarily to an earlier maturity state. The value of the sequence lies in preserving the institutional purpose of each stage. **Establish** creates the leadership baseline and institutional context. **Diagnose** examines the systems, capabilities, relationships and constraints surrounding the member's potential contribution. **Design** converts that understanding into the Annual Leadership Contribution Plan. **Test** exposes material assumptions to controlled challenge. **Pre-Scale Validate** determines what the available evidence supports and what remains immature. **Review** brings the complete first-year record together and determines the next institutional pathway. The sequence creates disciplined progression without pretending that leadership development is a mechanical process. *** #### 6.2.2 Formation operates through evidence, not elapsed time alone Completion of twelve calendar months does not by itself establish that the first-year institutional objectives have been achieved. Time matters because serious formation requires lived participation. Evidence matters because the system must be able to determine what occurred during that time. A member who has completed one year of nominal affiliation without a coherent Plan, substantive Council participation, relevant evidence or an intelligible contribution record has reached an anniversary, not necessarily a mature formation state. Conversely, a member may have made substantial progress while still requiring further testing before a particular proposition should advance. NLS therefore distinguishes **elapsed time from institutional maturity**. The first twelve months provide the normal formation window. The Year-One Review evaluates what that period actually produced. *** #### 6.2.3 Formation is individualized within a common architecture No two first-year journeys will be identical. A National Council Member helping form an early country system may spend considerable time on institutional mapping, relationship-building and National Portfolio development. A Regional infrastructure leader may focus on cross-border dependencies and comparative institutional analysis. A Global frontier-technology leader may spend more time in research, systems foresight and controlled testing. The common sequence remains useful because each of those journeys still requires a baseline, diagnosis, a defined contribution proposition, evidence and an informed next state. NLS therefore standardizes the **questions that must become answerable**, not the precise activity through which every leader answers them. *** #### 6.2.4 The member and institution develop together The first-year journey is reciprocal. It is not only the member who is being formed. NLS may also discover that the Council lacks a capability required to support the member's contribution, that a Working Group needs to be created, that Foundry functionality should be developed, that a National Portfolio requires a new category or that the institution needs a stronger relationship with an external actor. This means the member's formation can expose weaknesses in Nexus itself. We regard that as valuable institutional intelligence. A strong first-year programme should therefore improve both the leader and the system through which the leader participates. *** #### 6.2.5 The first year should reduce ambiguity At entry, several aspects of the leadership relationship may appropriately remain open. The member's precise annual contribution may still be developing. The balance among Council, Working Group, National or Regional activity may be uncertain. The strongest pathway for the second year may not yet be visible. By the end of the first year, these ambiguities should have been reduced materially. The system should have enough evidence to explain what the member contributed, where they created value, which capabilities they developed, what Nexus provided, which dependencies remain material and what should happen next. A successful Year One therefore produces **clarity before scale**. *** ### 6.3 Establish #### 6.3.1 Establishing the member within the institution The **Establish** stage converts admission into an operational leadership relationship. The member has already entered NLS. Establishment ensures that the relevant institutional context is sufficiently clear for active participation to begin coherently. This includes understanding the applicable Leadership Council, National, Regional or Global scope, primary institutional home, key institutional interfaces, first-year purpose and Council operating rhythm. It also begins the Leadership Ledger and establishes the initial leadership baseline from which development can later be understood. The objective is not to produce an exhaustive administrative file. It is to ensure that the member does not begin substantive contribution from an institutionally ambiguous position. *** #### 6.3.2 The leadership baseline The leadership baseline records the member's starting condition within NLS. It should provide a structured picture of the person's relevant professional experience, institutional context, principal domains of expertise, geographic scope, systems interests, material relationships, leadership-development interests and plausible areas of contribution. The baseline should be sufficiently substantive to inform formation while remaining proportionate. NLS does not require a complete reconstruction of the member's career. It requires enough understanding to identify the capabilities and contexts most relevant to the future leadership relationship. The baseline also provides a reference point for later review. Without knowing where the leader began, it is difficult to understand how the member or institution developed during the year. *** #### 6.3.3 Establishing institutional context A member cannot design a serious contribution without understanding the institutional environment they are joining. Establishment therefore includes orientation to the relevant Nexus architecture. The leader should understand the relationship among GCRI Canada, GCRI, GRF, GRA and the wider Consortium, the role of their Council, the distinction between Council leadership and persistent operations, and the basic relationships among the Desk, Working Groups, Model, Portfolio, Foundry and Universe where those objects are relevant. This institutional context should not be delivered as abstract theory alone. The member should increasingly encounter it through actual work. The purpose of the Handbook and onboarding is to provide enough conceptual architecture that those encounters make sense when they occur. *** #### 6.3.4 Establishing the initial contribution thesis During establishment, the member should begin articulating an **initial contribution thesis**. The contribution thesis is the early proposition about where the member's capabilities may create distinctive institutional value. It is intentionally less developed than the Annual Leadership Contribution Plan. The thesis might concern a particular systemic-risk domain, National institution-building, Regional federation, research, technology, governance, finance-readiness, mentorship or another field relevant to Nexus. At this stage, the thesis should remain open to challenge. Its purpose is to give diagnosis a starting point. *** #### 6.3.5 Establishing reciprocal expectations The member should also understand what NLS expects from active Council participation and what the member can reasonably expect from NLS. The member is expected to engage seriously, develop a Leadership Plan, contribute according to the role and Plan, participate in appropriate review, work constructively with other leaders and help preserve institutional continuity. NLS is expected to provide institutional orientation, relevant Council access, Leadership Plan support, appropriate intelligence, pathways into substantive work, evidence infrastructure, review and other support relevant to the member's contribution. Establishment should therefore create clarity about **reciprocal responsibility**. A leadership relationship becomes healthier when neither side assumes that the other is solely responsible for creating its value. *** ### 6.4 Diagnose #### 6.4.1 Diagnosis as institutional inquiry The **Diagnose** stage asks what the system needs to understand before the member's contribution can be designed credibly. This is not a diagnosis of the person in a clinical or remedial sense. It is a structured inquiry into the relationship among the leader's capabilities, the Nexus mission, relevant systems, institutional needs and realistic operating conditions. Diagnosis prevents the Leadership Plan from being constructed solely from enthusiasm or professional biography. It asks what contribution is actually needed, what the member can credibly provide, what dependencies surround that contribution and which assumptions require further evidence. *** #### 6.4.2 Diagnosing the systemic context The member's contribution should be situated within a relevant system. Where the contribution concerns water, infrastructure, AI, health, finance, governance or another domain, diagnosis should examine the wider dependencies that shape the problem. A resilience proposition may depend on energy, data, institutions and finance. An AI proposition may depend on compute, cybersecurity, public trust, governance and workforce capability. A National food-security initiative may depend on water, energy, logistics, finance, trade and climate. The purpose is to identify enough of the system that the member does not begin with a proposition defined too narrowly to survive real institutional conditions. Systems diagnosis therefore establishes the context within which the Leadership Plan should be designed. *** #### 6.4.3 Diagnosing institutional context A serious contribution also requires understanding the institutions involved. The member and NLS should identify which public institutions, operators, enterprises, research bodies, communities, finance and insurance actors, professional organizations or other stakeholders materially shape the proposition. The objective is not to create the largest possible stakeholder list. It is to understand the institutional architecture relevant to the work. We ask which institutions possess knowledge, which are affected, which can implement, which must cooperate and which may carry the work after the member's own leadership cycle changes. This begins the stakeholder and institutional map that will later form part of the mature Leadership Plan and Year-One evidence package. *** #### 6.4.4 Diagnosing the member's distinctive capability Diagnosis should also identify the capabilities the member brings that are difficult to reproduce through other parts of the institution. This may be specialist knowledge, operating experience, a particular institutional perspective, trusted relationships, systems understanding, leadership maturity, cross-sector translation, geographic knowledge or another form of capability. The question is not only what the member has done historically. It is what the member can contribute **uniquely or unusually well within the current Nexus context**. This distinction helps prevent Leadership Plans from becoming generic portfolios of worthy activities that could be assigned to almost anyone. *** #### 6.4.5 Diagnosing development needs NLS is also a leadership-development system. Diagnosis should therefore identify areas in which the member may benefit from additional capability. A leader may need deeper exposure to systems science, strategic foresight, frontier technology, finance-readiness, institutional architecture, Public-Private-Planet, evidence methods or another relevant field. These development needs should not be treated as weaknesses in the pejorative sense. They identify opportunities for the institution to increase the member's effectiveness. A mature leader should be able to enter NLS with substantial expertise and still expect to learn. *** #### 6.4.6 Diagnosing resources and dependencies A contribution proposition is credible only if the conditions required to support it are understood. Diagnosis should therefore examine what the member can contribute personally and what must be assembled around the member through Nexus or external institutions. A Plan may require research capability, technical specialists, institutional relationships, data, Foundry support, a Working Group, finance-readiness expertise, National Desk capacity or access to a particular operating environment. This prevents NLS from confusing the quality of the leader with the readiness of the system around the leader. A strong member cannot compensate indefinitely for missing institutional infrastructure. *** #### 6.4.7 Diagnosing constraints and risks Diagnosis should also identify conditions that may limit, distort or delay the proposed contribution. These may include insufficient evidence, unavailable institutional partners, conflicting professional commitments, uncertain technology, immature programme infrastructure, financial constraints, geopolitical conditions, community concerns or other material factors. The objective is not to eliminate every constraint before the Plan begins. It is to make material constraints visible enough that the Plan can be designed realistically. This creates a more mature relationship between ambition and readiness. *** #### 6.4.8 Diagnosing reciprocal value The member and NLS should also consider where value may emerge for Nexus, the relevant country, region or system, the member's institution and the leader personally. This Four-Way Value assessment should begin before the Plan is finalized because a contribution that creates value in only one direction may be difficult to sustain. The most durable leadership relationships usually develop where the member can see how their contribution matters, Nexus becomes stronger through the contribution, and the relevant institutional or geographic system benefits from the work. Diagnosis therefore examines not only what the member can give, but why the relationship is worth sustaining. *** ### 6.5 Design #### 6.5.1 From diagnosis to an Annual Leadership Contribution Plan The **Design** stage converts the learning produced through establishment and diagnosis into the **Annual Leadership Contribution Plan**, or ALCP. The Plan is the central work-design object of NLS. It provides the member, Council and supporting institution with a common understanding of the leadership proposition for the year. A strong Plan should explain what the member intends to strengthen, why the contribution matters, which systems and institutions are involved, what meaningful progress would look like, what dependencies exist, what Nexus support is required, how the work may be tested and what evidence should inform review. The Plan creates focus without requiring false certainty. It is therefore neither a static contract for a fixed set of outputs nor a broad statement of ambition. It is a governed leadership proposition capable of learning. *** #### 6.5.2 Designing for outcomes rather than activity We encourage members to design Plans around a small number of material outcomes rather than a large inventory of activities. Leadership activity is easy to generate. Institutional consequence is harder. A member may attend many meetings without creating a durable contribution. Another may lead one strategically important institutional process that materially changes the capability of a National system. The Plan should therefore begin with the change the member seeks to help create and work backward toward the activities required to support it. This outcome orientation prevents the first-year programme from becoming an exercise in filling calendars. *** #### 6.5.3 Designing bounded contribution The Plan should be sufficiently bounded to be credible within the member's available time, institutional role and first-year horizon. Senior leaders often enter with ambitions touching several sectors, institutions and geographies. Nexus should help convert that breadth into a contribution that can be developed seriously rather than allowing the Plan to become a catalogue of everything the member cares about. Bounded does not mean trivial. A well-defined strategic contribution can be highly consequential. The purpose of bounding the Plan is to create enough focus for evidence, support and learning to accumulate around it. *** #### 6.5.4 Designing the institutional architecture around the contribution A mature Plan should identify the institutions and operating environments required around the member. The member may contribute through the Leadership Council, but the proposition may also require a Working Group, National Desk support, GCRI research, GRF leadership or foresight capability, GRA finance-readiness analysis, Foundry, Labs, Nexus Universe or external institutional collaboration. The Plan therefore designs not only **what the leader will do**, but also **how the institution must organize itself around the work**. This is important because leadership contribution is rarely a purely individual act. The quality of the surrounding institutional architecture often determines whether the contribution can mature. *** #### 6.5.5 Designing for evidence The Plan should make clear what forms of evidence would indicate that the proposition is progressing and what evidence might show that an assumption is wrong. This does not require every leadership outcome to become quantitative. Some contributions concern institutional relationships, strategic coherence, leadership development, programme design or policy understanding. These may require qualitative and documentary evidence. The key requirement is that the system should be able to distinguish between activity, interpretation and demonstrated progress. Evidence should therefore be designed into the Plan rather than reconstructed at the end of the year. *** #### 6.5.6 Designing for learning and correction Every significant Leadership Plan should contain an explicit learning dimension. The institution should know what it expects to discover during the year. This may concern technical feasibility, stakeholder response, cross-sector dependencies, leadership fit, financial readability, institutional appetite or another material uncertainty. Designing for learning changes the meaning of failure. If a controlled test demonstrates that a proposition should not scale, the institution may have gained highly valuable information. The Plan should therefore allow correction without forcing the member to defend the original proposition for reputational reasons. *** #### 6.5.7 Designing the support architecture The Plan should identify the support required from Nexus. This creates accountability in both directions. If the Plan requires systems analysis, relevant expertise should be identified. If it requires an institutional relationship, the pathway for developing that relationship should be considered. If it requires Foundry, Labs or Universe support, the relevant maturity and availability of those environments should be understood. A Plan should not assign ambitious outcomes to a member while leaving the institutional dependencies around those outcomes invisible. The Plan is therefore both a leadership object and a resource-planning object. *** ### 6.6 Controlled Testing #### 6.6.1 Why NLS tests leadership propositions The **Controlled Testing** stage is one of the defining features of the first-year model. We do not assume that a proposition should move directly from senior leadership interest into large-scale activity. Experienced leaders can identify significant opportunities, but seniority does not remove uncertainty. Controlled testing creates a disciplined environment in which material assumptions can encounter evidence before the system becomes deeply committed to a particular pathway. The objective is not to slow good ideas unnecessarily. It is to increase the quality of scale. *** #### 6.6.2 What can be tested Testing may concern the proposition itself, the institutional environment around it, the leader's role within it or the support architecture required for success. A technology proposition may need technical validation. A National programme may need institutional mapping and stakeholder engagement. A governance model may need scenario testing. A Regional initiative may need evidence that participating National systems possess sufficient shared need. A finance-readiness proposition may require greater clarity about risks, data and programme maturity. Testing is therefore broader than laboratory experimentation. It means exposing a material hypothesis to a bounded environment in which evidence can change the next decision. *** #### 6.6.3 Testing through Council challenge The Leadership Council itself is one testing environment. A member can bring a proposition into peer challenge and discover how leaders from different sectors and institutions interpret it. A strong Council can reveal dependencies, implementation concerns, competing institutional priorities or evidence gaps that were not visible in the initial Plan. Council challenge is particularly valuable because it exposes the proposition to experienced judgment without requiring immediate implementation. This is one of the ways plural leadership reduces institutional risk. *** #### 6.6.4 Testing through Working Groups Working Groups provide deeper testing where a proposition requires sustained specialist or institutional examination. The group can analyze evidence, develop options, engage relevant experts, examine implementation conditions and produce a more mature view of the proposition. A Working Group should therefore not exist merely to endorse the initiating member's idea. Its value lies partly in its ability to demonstrate that the proposition requires modification or should not advance. The legitimacy of testing depends on the possibility of genuine correction. *** #### 6.6.5 Testing through Foundry and Labs [The Foundry pillar](/organization/systems.md) and Labs can provide more technical or analytical testing where appropriate. A proposition may require scenario analysis, modelling, geospatial intelligence, data integration, simulation, digital experimentation or another capability through which assumptions can be examined under controlled conditions. For the Leadership System, the significance is not simply access to technology. It is the ability to connect a senior leadership hypothesis to an evidence-producing environment. This prevents technology from becoming a demonstration layer detached from institutional questions. The test should answer something the leadership system actually needs to know. *** #### 6.6.6 Testing through Nexus Universe Nexus Universe provides an annual environment for more concentrated cross-system testing, integration and learning. A Leadership Plan may enter Universe where the proposition benefits from scenario work, cross-sector challenge, institutional exercise, technical demonstration, simulation or another structured annual test. Universe should not be used to manufacture proof through visibility. Its purpose is to expose the proposition to conditions demanding enough to generate useful evidence. The correct question after a Universe test is not, **“Was it showcased successfully?”** It is, **“What did we learn that changes the institutional state of the proposition?”** *** #### 6.6.7 Testing the leader-system relationship The first year also tests the relationship between the leader and NLS. A member may discover that they create greatest value through Council strategy rather than programme delivery. Another may become an exceptional Working Group leader. Another may prove especially effective in National institution-building, mentoring or Regional federation. This is part of formation. NLS should not force the member toward the contribution imagined at entry if real participation demonstrates that another pathway creates greater value. The first year tests not only the Plan. It tests the fit between **leader, institution and contribution**. *** #### 6.6.8 Controlled tests should have outcome ceilings Testing should remain bounded enough that participants understand what a successful test can legitimately establish. A positive scenario result does not establish permanent institutional adoption. A successful technology demonstration does not prove production readiness in every environment. A constructive institutional meeting does not establish a durable partnership. A promising Working Group does not prove that a full programme should scale. NLS therefore applies an **outcome ceiling** to testing. The evidence generated should advance the proposition only to the state the test can reasonably support. This protects the integrity of the maturity model. *** ### 6.7 Pre-Scale Validation #### 6.7.1 The purpose of pre-scale validation The **Pre-Scale Validation** stage asks whether the first-year proposition has become sufficiently credible to justify a more consequential next state. Validation is not a ceremonial approval at the end of testing. It is a structured assessment of what the available evidence supports, what remains uncertain and which dependencies must still be resolved before broader activity. The term **pre-scale** is deliberate. The member may have developed a strong proposition without yet demonstrating that it should be replicated, institutionalized or expanded materially. The purpose is to determine whether the work is ready for deeper commitment, requires further validation, should remain bounded or should stop. *** #### 6.7.2 Validation is not the same as success A successful first year does not require the proposition to reach scale-ready status. The institution may discover that the most valuable outcome of the year is a well-evidenced decision not to proceed with an immature approach. A programme may need another year of testing. A National Council may determine that an institutional dependency must be addressed first. A technology may be promising but not yet ready for the intended environment. We therefore separate the quality of the first-year leadership process from the maturity state of the proposition. A leader who surfaces a critical weakness and prevents premature scale may have created significant institutional value. *** #### 6.7.3 Validation of the contribution thesis Pre-scale validation should examine whether the member's contribution thesis remains credible after a year of lived participation. We ask whether the problem remains material, whether the member's contribution is distinctive, whether the institutional environment around it is viable, whether relevant evidence supports further activity and whether the contribution continues to fit the member's Council and wider Nexus mission. The first year may confirm the original thesis. It may also produce a materially different conclusion. Both are legitimate if the result is evidence-informed. *** #### 6.7.4 Validation of institutional readiness A proposition can be technically mature while the surrounding institution remains unready. Pre-scale validation should therefore examine organizational and institutional readiness alongside substantive quality. Are relevant institutions engaged? Does an operating owner exist? Is there sufficient Desk or programme capacity? Are critical dependencies understood? Can the evidence be maintained? Is the next stage financially and operationally plausible? Is the required leadership available? This prevents NLS from interpreting the maturity of one component as readiness of the entire system. *** #### 6.7.5 Validation of support requirements The validation stage should also assess the support architecture required for the next cycle. A proposition may be strong but require resources, technical capability, institutional relationships, a new Working Group, Regional federation or another condition that is not yet in place. The next-state recommendation should therefore identify not only what the member is expected to do, but what Nexus must provide or assemble if the contribution is to advance credibly. This maintains reciprocity as the contribution becomes more consequential. *** #### 6.7.6 Scale readiness as a profile, not a single score We do not reduce pre-scale validation to one universal readiness score. A proposition may be technically advanced and institutionally immature. Another may have strong leadership support but weak evidence. Another may possess compelling evidence but insufficient implementation capacity. The system should therefore develop a **Scale Readiness Profile** that explains the relative maturity of the material dimensions of the contribution. The purpose is diagnosis of the next state, not ranking. A multidimensional profile is more useful than a single number where several different types of readiness must align before scale. *** ### 6.8 Quarterly Review #### 6.8.1 Why quarterly review is necessary We use quarterly review to prevent the Annual Leadership Contribution Plan from becoming a document written at the beginning of the year and rediscovered at its conclusion. Systemic work changes. Evidence develops. Institutional relationships evolve. Professional circumstances shift. Testing exposes assumptions. A serious Leadership System therefore requires recurring opportunities to compare the Plan against the state of the work. Quarterly review creates that rhythm. It is frequent enough to support correction and spaced sufficiently for substantive activity to occur between reviews. *** #### 6.8.2 Quarterly review as a learning conversation The quarterly review should not become a mechanical performance inspection. Its primary purpose is learning. The member and NLS should consider what has progressed, what has not, what evidence has emerged, which assumptions changed, whether the contribution remains correctly scoped and what support is required during the next quarter. The review should also provide a structured opportunity for the member to identify weaknesses in the institutional support they are receiving. Reciprocity requires Nexus to examine its own performance as part of the leadership relationship. *** #### 6.8.3 Reviewing outcomes rather than activity volume Quarterly review should focus on the quality and significance of progress rather than the quantity of visible activity. A quarter containing several meetings may produce less institutional value than one focused intervention that resolves a critical dependency. The review should therefore ask what materially changed. This might involve clearer evidence, a stronger relationship, a refined Plan, a Working Group output, a corrected assumption, a better understanding of institutional readiness or another meaningful shift. NLS should reward substantive progress rather than calendar density. *** #### 6.8.4 Reviewing the Plan itself The Annual Leadership Contribution Plan is a living institutional object. Quarterly review should therefore examine whether the Plan still reflects the best understanding of the contribution. Objectives may need narrowing. A stakeholder map may need expansion. An intended test may no longer be useful. A National proposition may reveal Regional implications. A planned outcome may prove dependent on another institution whose participation has not yet been secured. The Plan should be amended where necessary. We do not interpret disciplined amendment as failure to follow the Plan. A Plan that cannot respond to evidence is not a serious systems-leadership instrument. *** #### 6.8.5 Reviewing member development Quarterly review should also consider the leader's own development. Has the member gained greater understanding of Nexus architecture? Has systems literacy increased? Is the member becoming more effective at working across institutions? Has exposure to other leaders or domains changed the way they understand their own contribution? This dimension matters because NLS is designed to create stronger leaders, not merely outputs. Leadership development should therefore become part of the evidence considered at Year One. *** #### 6.8.6 Reviewing institutional support NLS should use the quarterly cycle to examine whether its support architecture is adequate. Is the member receiving relevant intelligence? Are Working Group or Desk interfaces functioning? Is the Council making effective use of the member's expertise? Are technical or institutional dependencies being addressed? Is the member encountering unnecessary administrative friction? The review should therefore generate corrections on both sides. The member may need to change how they contribute. Nexus may need to change how it supports the contribution. This is one of the mechanisms through which the Leadership System itself learns. *** ### 6.9 The Year-One Evidence Package #### 6.9.1 Purpose of the evidence package The first-year cycle should culminate in a coherent **Year-One Evidence Package** that allows the member and institution to understand what the formation period actually produced. The package is not intended to become an oversized administrative dossier. Its purpose is synthesis. A mature evidence package should make it possible for a competent reviewer to understand where the member started, what contribution was designed, what work occurred, what evidence emerged, what the institution learned, what value was created and what next state is recommended. The package converts a year of distributed leadership activity into a durable institutional record. *** #### 6.9.2 Leadership baseline and institutional context The evidence package should begin from the leadership baseline established at entry. This allows the Year-One Review to compare the member's initial institutional context, expertise, contribution thesis and development interests with the state reached after twelve months. The baseline gives meaning to development. Without it, review risks favouring visible outputs while overlooking significant growth in systems leadership, institutional relationships or strategic capability. *** #### 6.9.3 The Annual Leadership Contribution Plan The evidence package should include the mature state of the member's Annual Leadership Contribution Plan together with material revisions made during the year. This provides a record of how the contribution proposition evolved. A strong first year may involve meaningful correction, and those changes should remain intelligible. The objective is not to demonstrate that the member predicted the year perfectly at the beginning. It is to demonstrate that the member and institution used evidence to improve the Plan as the year unfolded. *** #### 6.9.4 Contribution and participation record The evidence package should provide a proportionate account of substantive Council, Working Group, mission, research, mentoring, National, Regional, Foundry or Universe contribution relevant to the member's Plan. The purpose is not to record every interaction. It is to identify the material activities through which the contribution developed. This record should preserve collective context where the work was collaborative. NLS should recognize contribution accurately without converting collective institutional work into individual ownership claims. *** #### 6.9.5 Testing and evidence record Where the Plan involved testing, the package should explain what was tested, through which environment, what evidence was generated and what the test can reasonably establish. This may include Council challenge, Working Group analysis, research, scenario work, Foundry or Labs activity, Nexus Universe or another controlled environment. The record should also preserve negative or inconclusive results. A serious institutional evidence system does not record only successful tests. It records what the system learned. *** #### 6.9.6 Stakeholder and institutional map The Year-One package should include a sufficiently mature view of the institutional environment around the contribution. This should identify the material public institutions, operators, enterprises, research bodies, communities, finance and insurance actors or other organizations that influence the work. The map should help clarify which relationships are established, which remain prospective, where dependencies exist and which institution is likely to carry the work if it advances. This is essential to pre-scale readiness. A proposition without an institutional route remains an idea regardless of its technical quality. *** #### 6.9.7 Resource and support profile The evidence package should identify the resources and capabilities required for the next state. This may include research, technical support, programme management, National Desk capacity, institutional relationships, Foundry functionality, finance-readiness work, a Regional interface or another material dependency. The purpose is to prevent a positive Year-One assessment from being interpreted as evidence that scale can occur without additional institutional capacity. A validated proposition still requires an operating architecture. *** #### 6.9.8 Risks, constraints and safeguards The package should preserve the principal risks and constraints associated with advancing the contribution. A mature first-year record should not present only the case for continuation. It should identify what could make the next stage fail, where evidence remains weak, which dependencies are fragile and what safeguards or additional tests may be required. This creates a more credible basis for the Year-One Gateway. Leadership readiness is demonstrated partly through the ability to state clearly what remains unresolved. *** #### 6.9.9 Four-Way Value record The evidence package should include a reflective assessment of the value created through the first year across the Four-Way Value Framework. For Nexus, the review should ask what capability, knowledge, relationships or institutional strength the member helped create. For the relevant country, region or system, it should examine what practical or strategic value emerged. For the member's principal institution, it should consider legitimate knowledge, insight or capability generated through the relationship. For the leader personally, it should examine development, peer learning, systems perspective and other meaningful value. The purpose is not to manufacture equal benefits across all four dimensions. It is to understand whether the leadership relationship is sufficiently reciprocal to remain durable. *** #### 6.9.10 Scale Readiness Profile The Year-One evidence package should synthesize the state of the contribution through a **Scale Readiness Profile**. The profile should consider the maturity of the substantive proposition, evidence, institutional relationships, leadership capacity, dependencies, technical readiness where relevant, financial and insurance-readiness where relevant, operating support and continuity requirements. It should make clear which dimensions are strong and which remain immature. This allows the Year-One Review to make a more nuanced recommendation than a binary pass or fail. *** #### 6.9.11 Year-Two recommendation The evidence package should conclude with a clear recommendation for the next institutional state. That recommendation may support deeper strategic delivery, continuation as a substantive Council Member, assumption of a Council office where appropriate, consideration for another governance pathway where a genuine institutional need exists, separate professional work through an appropriate process, extended validation, a temporary pause or another legitimate state. The recommendation should arise from the complete Year-One record rather than one moment of visibility or one individual's preference. This is the bridge between evidence and the Year-One Gateway. *** ### 6.10 Year-One Review #### 6.10.1 The purpose of the Year-One Review The **Year-One Review** is the formal institutional synthesis of the first formation cycle. Its purpose is to answer three questions. First, what has the member contributed and learned? Second, what has Nexus learned about the member and the surrounding institutional environment? Third, what should the leadership relationship become next? The review therefore looks backward only in order to make a better forward decision. It is not a retrospective performance appraisal in the conventional employment sense. It is an institutional readiness review. *** #### 6.10.2 Review of the leadership relationship The review should consider the quality of the overall relationship rather than examining only the success of one project or Plan outcome. A member may have contributed strongly even where the initial proposition did not advance. Another may have delivered visible outputs but demonstrated weak Council participation or poor institutional fit. Another may have created exceptional peer, mentoring or institution-building value that is not captured adequately through project metrics. The review should therefore consider contribution, systems leadership, Council engagement, evidence discipline, reciprocity, institutional reliability and future potential together. No single metric should define the conclusion. *** #### 6.10.3 Review of the Annual Leadership Contribution Plan The Plan should be reviewed according to what it taught the institution. Was the problem well defined? Did the member's contribution prove distinctive? Were relevant institutions engaged? Were material dependencies identified? Did testing change the proposition? Did evidence justify deeper activity? Did the Plan create meaningful Four-Way Value? The objective is not to reward adherence to the original document. It is to assess the quality of the leadership process through which the Plan matured. A Plan that changed substantially because of strong evidence may demonstrate more sophisticated leadership than one that remained unchanged despite contradictory information. *** #### 6.10.4 Review of institutional readiness The Year-One Review should determine whether the surrounding institutional system can support the next state. A strong leader and validated proposition may still require additional Desk capacity, technical infrastructure, funding, Working Groups, partnerships or National or Regional institutional development before deeper delivery becomes realistic. We therefore separate **leader readiness**, **proposition readiness** and **system readiness**. These states may mature at different rates. The next pathway should reflect the weakest material dependency rather than the strongest visible success. *** #### 6.10.5 Review of good standing and contribution record The member's standing and contribution record should form part of the Year-One Review, but the process should remain proportionate and evidence-informed. Good standing reflects the functioning quality of the leadership relationship. Contribution reflects what the member actually added. These concepts overlap but should not be treated as identical. A member may remain in good standing while a particular proposition is still immature. Another may have delivered a strong contribution but decide that future professional circumstances make continuation impractical. The Year-One Review should preserve these distinctions so that the next-state recommendation accurately reflects the whole relationship. *** #### 6.10.6 Review as a reciprocal institutional process The review should also ask whether Nexus fulfilled its side of the leadership compact. Did the member receive appropriate orientation? Was Council access useful? Did the institution support the Plan adequately? Were relevant capabilities available? Did administrative or technical limitations constrain the contribution? Was the member's expertise used intelligently? This reciprocal dimension matters because a weak Year-One outcome may reflect institutional limitations rather than lack of member capability. A serious Leadership System must be prepared to review itself. *** #### 6.10.7 The review should produce an explicit next state The Year-One Review is incomplete if it concludes with general praise but no institutional decision about what happens next. The review should identify the recommended pathway, contribution focus, support requirements and material conditions for the next cycle. This creates continuity. The member should not enter Year Two wondering whether they are expected to repeat Year One. The next cycle should begin from a more mature institutional proposition. *** ### 6.11 The Year-One Gateway #### 6.11.1 Gateway rather than automatic promotion We establish the **Year-One Gateway** as the transition between the initial formation cycle and the member's subsequent NLS pathway. The Gateway is not an automatic promotion mechanism. Completion of the first year does not by itself create a Chair office, Board role, executive position, paid assignment, expanded geographic scope or any other predetermined outcome. The Gateway asks what next state is justified by demonstrated contribution, institutional need, readiness and the member's own leadership trajectory. This protects the Leadership System from becoming a status ladder. *** #### 6.11.2 Multiple legitimate post-Year-One pathways NLS recognizes several legitimate pathways after the first year because leadership contribution can mature in different directions. A member may continue and deepen **Strategic Delivery**, carrying a validated Plan or substantive Council contribution into a more mature operating state. A member may be considered for a **Council Office** where the Council requires additional leadership and the member's contribution demonstrates fit. A member may become eligible for **Governance Consideration** where an actual institutional need exists and the relevant institutional process supports consideration. A member may undertake a **Separate Professional Assignment** where a genuine programme need, capability fit and appropriate independent process exist. A member may enter **Extended Validation** where the contribution remains promising but requires additional evidence. A member may also **Pause, transition to an alumni relationship or conclude participation** where that state best reflects the member's circumstances and the needs of the system. These pathways are not ranks. They are different responses to different institutional conditions. *** #### 6.11.3 Strategic Delivery pathway Strategic Delivery is appropriate where the member's first-year contribution has become sufficiently mature to justify deeper work. The next cycle may focus on implementation support, expansion of a Working Group, development of a National or Regional programme, deeper research, additional testing or another validated form of contribution. The member remains a Leadership Council Member while the Plan becomes more mature. This is likely to be one of the most common and valuable long-term NLS pathways. The objective is depth of institutional contribution rather than constant role change. *** #### 6.11.4 Council Office pathway A Council Office pathway may become appropriate where the Council requires additional leadership and the member has demonstrated the capability to serve the collective institution. Chair, Vice-Chair, Rapporteur, Working Group Lead or another legitimate Council function should follow actual institutional need. The first year can provide useful evidence concerning how the member engages peers, handles disagreement, understands the Nexus architecture, supports institutional continuity and contributes beyond their own individual Plan. Council office should therefore be approached as **service to the institution**, not recognition detached from responsibility. *** #### 6.11.5 Governance consideration pathway A first-year member may later become eligible for consideration for a formal governance pathway where an actual need exists within the relevant institution. The key term is **consideration**. NLS does not establish an automatic route from Council membership into a formal governing body. The first year may create an evidence base that allows the institution to consider a member's suitability where such a need arises, but formal governance remains a distinct institutional pathway with its own requirements. Council service should therefore remain valuable independently of whether another governance pathway ever becomes relevant. This preserves the integrity of both Council membership and formal governance. *** #### 6.11.6 Separate professional assignment pathway A member's expertise may also become relevant to separately constituted professional work. Where a programme, country initiative, technical-assistance requirement, research activity or another institutional need requires professional delivery, an experienced Council Member may be among the people whose capability is relevant. Such work should remain distinct from the basic Council relationship. The appropriate route is: > **Institutional need → defined scope → capability fit → resource availability → appropriate review → separate assignment** The purpose is to allow Nexus to use relevant leadership capability where it genuinely fits without turning Council membership into an entitlement to professional work. *** #### 6.11.7 Extended Validation pathway Extended Validation is appropriate where the member and proposition remain promising but the first year has not produced enough evidence to justify deeper scale. This should not be treated as failure. Systemic work frequently requires more than one cycle to mature, particularly where external institutions, technology, finance, National formation or other dependencies develop slowly. The next Plan should identify precisely what remains uncertain and what evidence the additional cycle is intended to produce. Extended Validation is valuable only where it is purposeful. It should not become indefinite postponement of difficult decisions. *** #### 6.11.8 Pause, alumni or exit pathway A mature Leadership System must also provide legitimate ways for members to reduce or conclude participation. Professional demands may change. The member's contribution may reach a natural conclusion. The institution's priorities may evolve. Another form of relationship may become more appropriate. A pause can preserve the relationship while recognizing temporary limits on participation. An alumni relationship can maintain institutional connection after active Council service concludes. Exit can conclude the active relationship while preserving the member's contribution history and appropriate institutional memory. The quality of a leadership institution is visible not only in how it admits members, but in how it manages transition with clarity and respect. *** #### 6.11.9 Compatible pathways may coexist Some post-Year-One pathways can coexist where the responsibilities remain compatible. A member may continue Strategic Delivery while holding a Council office. A Council Member may mentor others while leading a Working Group. A Regional leader may remain active in National work while contributing upward within the federation. NLS should therefore avoid assuming that the Gateway produces one exclusive label describing the entire second-year relationship. The key requirement is role clarity. The member, Council and operating teams should understand which capacities apply and how the responsibilities interact. *** #### 6.11.10 The Gateway as the beginning of a mature leadership portfolio The first-year Gateway marks the point at which the member's NLS journey begins moving from general formation toward a more differentiated leadership portfolio. Year One asks broadly, **“Where can this person create distinctive institutional value within Nexus?”** Subsequent cycles can ask the more mature question: > **“Given the evidence now available, where should this leader's contribution deepen, expand, federate, institutionalize or conclude?”** That shift is one of the principal outcomes of the Formation Year. The system moves from hypothesis to an increasingly evidence-informed leadership relationship. *** ## PART VI FRAMEWORK PRINCIPLES **6.A Active formation.** The first twelve months begin after admission and are therefore an active Council-membership period, not a provisional waiting room before membership becomes substantive. **6.B Formation as interoperability.** We use the first year to connect an experienced leader's existing capability to the institutional architecture, systems methods, evidence disciplines and contribution pathways of Nexus. **6.C Formation through participation.** Leaders develop within NLS by engaging the Council and wider institutional system rather than completing formation entirely through preliminary orientation. **6.D Six-stage journey.** The common first-year sequence is Establish → Diagnose → Design → Test → Pre-Scale Validate → Review, with iteration permitted where evidence requires earlier assumptions to be revisited. **6.E Time and maturity.** Twelve months provide the normal formation window, but elapsed time and institutional maturity are not equivalent. **6.F Leadership baseline.** We establish a proportionate baseline of relevant experience, institutional context, capabilities, relationships and development interests so that later contribution and growth can be understood. **6.G Initial contribution thesis.** Formation begins with a plausible contribution hypothesis that is expected to improve through diagnosis rather than being treated as a fixed commitment from the moment of admission. **6.H Diagnosis before scale.** We examine systemic context, institutional context, distinctive member capability, development needs, resources, dependencies, constraints and reciprocal value before treating a contribution proposition as mature. **6.I Plan as the organizing object.** The Annual Leadership Contribution Plan converts diagnosis into a bounded, outcome-oriented and evidence-aware leadership proposition. **6.J Outcome orientation.** We design Plans around material institutional outcomes and learning rather than the accumulation of activities. **6.K Support architecture.** A Leadership Plan must identify what Nexus and other institutions must provide around the member, not merely what the member is expected to contribute personally. **6.L Controlled testing.** We expose important leadership propositions to proportionate challenge before deeper institutional commitment. **6.M Multiple testing environments.** Council challenge, Working Groups, research, Foundry, Labs, Nexus Universe and other appropriate environments may all contribute to testing depending on the proposition. **6.N Outcome ceilings.** Evidence from a test should advance the proposition only to the maturity state the test can legitimately support. **6.O Pre-scale validation.** Validation determines whether deeper commitment is justified, what remains unresolved and what support architecture the next stage requires. **6.P Validation is not automatic success.** A decision to narrow, redesign, continue testing or stop a proposition may represent a high-quality first-year outcome where the evidence supports it. **6.Q Multidimensional readiness.** We assess leader readiness, proposition readiness, institutional readiness and relevant technical or financial readiness as related but distinct conditions. **6.R Quarterly learning.** Quarterly review exists to compare the Plan with emerging evidence, revise assumptions, examine member development and correct institutional support before the annual cycle concludes. **6.S Reciprocal review.** NLS reviews not only the member's contribution but also the quality of the support, Council environment and institutional infrastructure provided around that contribution. **6.T Year-One evidence package.** The first-year record should synthesize the leadership baseline, mature Plan, contribution evidence, testing, institutional map, resources, constraints, Four-Way Value, readiness profile and recommended next state. **6.U Proportionate evidence.** The evidence package should preserve material contribution and learning without turning leadership into bureaucratic activity counting. **6.V Scale Readiness Profile.** Readiness should be expressed through a multidimensional profile rather than a single score where several forms of institutional maturity must align. **6.W Gateway, not promotion.** Completion of the first year creates a decision point about the appropriate next pathway and does not automatically create a Council office, governance role, professional assignment or expanded geographic scope. **6.X Multiple successful pathways.** Strategic Delivery, Council Office, Governance Consideration, Separate Professional Assignment, Extended Validation, Pause, Alumni or Exit can each be legitimate post-Year-One states where supported by the institutional context. **6.Y Council service as a complete pathway.** Continued substantive Leadership Council membership is itself a successful long-term leadership pathway and does not require progression into another office. **6.Z Evidence-informed renewal.** The next annual cycle should begin from the strongest institutional state established through Year One rather than restarting the leadership relationship from the beginning. *** ## OPERATING RELATIONSHIP Part VI establishes the first twelve months as the period in which admission becomes a mature leadership relationship. We use the Formation Year to move from broad potential toward a clearer understanding of how the member can contribute, how Nexus must support that contribution and what evidence should determine the next state. The first-year architecture begins with **Establish**, where we create the leadership baseline, institutional context and initial contribution thesis. **Diagnose** then examines the relevant systems, institutions, member capabilities, development needs, dependencies, constraints and reciprocal value. **Design** translates this understanding into the Annual Leadership Contribution Plan. **Controlled Testing** places material assumptions into Council, Working Group, research, Foundry, Labs, Universe or another appropriate evidence-producing environment. **Pre-Scale Validation** determines what the evidence supports and whether the proposition, leader and surrounding institutional system are ready for deeper commitment. **Quarterly Review** makes correction continuous rather than retrospective. The **Year-One Evidence Package** brings the complete formation record together, and the **Year-One Review** converts that evidence into an explicit institutional recommendation. The cycle culminates in the **Year-One Gateway**. The Gateway is not a promotion event. It is the point at which evidence determines the most appropriate next leadership pathway. A member may deepen Strategic Delivery, continue substantive Council service, assume a Council office where needed, become eligible for consideration within another institutional pathway, undertake separately constituted professional work where appropriate, extend validation, pause or conclude active participation. The first year therefore performs a foundational institutional function. It replaces assumptions about leadership fit with a progressively evidenced understanding of the relationship. The next Part examines the central instrument around which that first-year contribution is organized. ## NEXT ## PART VII: THE ANNUAL LEADERSHIP CONTRIBUTION PLAN ### Proposal-Based Leadership, Contribution Architecture, Institutional Mapping, Dependencies, Evidence, Maturity and the Route from Concept to Scale Part VII will define the Annual Leadership Contribution Plan as the principal work-design object of NLS. It will explain how the Leadership Contribution Questionnaire informs the Plan, how leaders define material outcomes rather than activity lists, how geographic and institutional context are mapped, how stakeholder relationships and decision environments are understood, how resources and dependencies are surfaced, how risks and safeguards are incorporated, how evidence and success are defined, how Plans are amended through learning, and how contribution progresses from Concept through Design, Testing, Validation, Scale Readiness, Active Delivery, Demonstration, Replication and Institutionalization. ## 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/vi.-first-year.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.