> 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/xi.-evidence-ledger.md). # XI. Evidence Ledger Learn how the Nexus Leadership Ledger records contribution claims, evidence, verification, attribution, outcomes, and institutional learning. **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-GRX](/organization/systems/nxs-grx.md) · framework page (NLS). **In brief.** We use an evidence model because leadership within Nexus is intended to create institutional capability rather than remain a matter of reputation, presence or narrative. 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 %} ## Leadership Evidence Ledger and Contribution Tracking ### 11.1 Why NLS Uses an Evidence Model #### 11.1.1 Leadership requires evidence because leadership claims have institutional consequence We use an evidence model because leadership within Nexus is intended to create institutional capability rather than remain a matter of reputation, presence or narrative. As soon as a Leadership Council claims that a member helped strengthen a National programme, established a material institutional relationship, developed a method, led a Mission, validated a proposition or contributed to another significant outcome, the claim begins to shape institutional memory. It may influence future programme design, leadership pathways, recognition, replication, resource allocation or the interpretation of what worked. A leadership system that cannot distinguish what actually occurred from what is merely remembered, implied or asserted will eventually become unreliable. Evidence therefore protects more than the accuracy of individual profiles. It protects the integrity of the institution's own learning. If Nexus cannot determine who contributed what, which proposition was tested, what evidence emerged, which institution adopted the result and what changed afterward, it cannot learn systematically from its own history. Future Councils will repeat work, successful methods may be misattributed, failures may disappear from the record and the institution may gradually confuse narrative confidence with demonstrated capability. For this reason, our evidence discipline is not an administrative add-on to leadership. It is part of the operating architecture through which leadership becomes cumulative. *** #### 11.1.2 Evidence makes contribution intelligible without reducing leadership to metrics Leadership is too complex to be represented adequately through a single score, a count of meetings or a catalogue of activities. Some of the most consequential leadership interventions may be brief. A member may identify one hidden dependency that prevents a major error, create one relationship that enables a National programme, challenge one assumption that materially changes a Portfolio or mentor one future leader who later carries substantial institutional responsibility. We therefore use evidence to improve interpretation, not to create false numerical precision. The question is not, **“How much did the member do?”** The question is, **“What material contribution occurred, what supports that conclusion, how should it be attributed, what institutional state resulted and what does the institution now understand that it did not understand before?”** This approach allows NLS to remain rigorous without adopting the logic of activity surveillance. Evidence creates context around contribution. It does not turn leadership into a productivity contest. *** #### 11.1.3 Evidence protects the distinction between participation, contribution and outcome A mature Leadership System must distinguish several states that are often collapsed in ordinary institutional narratives. A member can participate in a Working Group without having created its output. A leader can make a substantive contribution to a programme without the programme ultimately being adopted. An institutional introduction can be important without becoming a partnership. A test can generate useful evidence without validating the entire proposition. A member can help shape a National Portfolio priority without becoming responsible for every later implementation outcome associated with it. NLS therefore separates **presence, participation, contribution, verification, adoption, scale and institutionalization** conceptually so that the meaning of each remains clear. This distinction protects both the member and the institution. It prevents under-recognition of genuine contribution while also preventing later outcomes from being attributed automatically to the most visible person connected to the work. *** #### 11.1.4 Evidence supports learning from failure and correction An evidence model is especially important when work does not proceed as expected. Leadership systems that recognize only success create incentives to conceal weakness. Tests that fail disappear from public narratives. Programmes that are discontinued become difficult to study. Leaders may become reluctant to challenge their own earlier positions because correction appears inconsistent with a record built around uninterrupted achievement. NLS takes the opposite view. A well-designed test that demonstrates that a proposition should not advance can create significant institutional value. A leader who changes position because stronger evidence has emerged may demonstrate greater systems maturity than one who protects the original proposal. The evidence architecture should therefore preserve material negative, limiting and inconclusive findings where they affect the institutional interpretation of the work. We do not seek a Ledger containing only victories. We seek an institutional memory capable of explaining **how the system learned**. *** #### 11.1.5 Evidence protects leadership from prestige effects Senior people carry influence. That influence can improve the institution, but it can also create situations in which assertions acquire more authority than the underlying evidence supports. NLS therefore applies evidence discipline precisely because members may be highly accomplished. Professional experience deserves serious consideration. It should not silently convert every leadership judgment into an institutional fact. Where a senior member identifies a risk, proposes an intervention or interprets an outcome, the system should preserve both the value of the judgment and the evidentiary state supporting it. This allows other leaders to engage the proposition seriously without being required either to defer automatically or to disregard valuable experience because it is not yet formally proven. Evidence and leadership judgment thereby become complementary rather than competing sources of institutional intelligence. *** ### 11.2 Purpose of the Leadership Ledger #### 11.2.1 The Ledger as longitudinal institutional memory We establish the **Leadership Ledger** as the longitudinal institutional memory of the Nexus Leadership System. Its purpose is to preserve the material history of the leadership relationship in a form that can remain intelligible across annual cycles, Council transitions, institutional change and leadership succession. The Ledger is not a social profile, public leaderboard, member-ranking system or comprehensive log of every interaction. It records the institutional facts and contribution states required for NLS to understand how a member's relationship with the system has developed. A mature Ledger should allow a future reviewer to understand where the member was institutionally situated, what contribution was proposed, what role the member actually performed, what evidence exists, how the contribution was attributed, what state it reached, what dependencies affected it, what corrections occurred, what value was created and what outcome ultimately followed. This makes the Ledger one of the principal mechanisms through which individual leadership becomes institutional memory. *** #### 11.2.2 The Ledger connects facts that conventional profiles separate Traditional leadership profiles usually describe a person, their biography and perhaps their current role. NLS requires a richer institutional model because the significance of leadership depends on the relationship among several kinds of fact. The Ledger therefore connects **Claim, Role, Evidence, Attribution, State, Institutional Context, Value, Dependencies, Correction and Outcome**. A contribution claim without role context may exaggerate responsibility. A role without evidence may reveal little about what the member actually contributed. Evidence without attribution may not explain who did what. An outcome without state history may obscure how the work matured. Value without dependencies may suggest that a result arose from one person's capability when the surrounding institution was equally important. The Ledger therefore does not merely store information. It preserves the relationships required to interpret information responsibly. *** #### 11.2.3 The Ledger supports continuity through multiple capacities Senior leaders frequently participate in several Nexus capacities over time. A member may begin in a National Council, lead a Working Group, later serve as Chair, contribute to a Regional Mission and participate in a separate research or programme environment. Without a longitudinal record, each new context can cause the institutional history to fragment. The Leadership Ledger preserves continuity while keeping the different capacities intelligible. It allows the institution to understand that the same individual participated in several legitimate contexts without pretending that one title describes the whole history. This becomes increasingly important as NLS matures. A system operating over several years must be able to understand not only who its current leaders are, but how their capabilities, contributions and responsibilities developed. *** #### 11.2.4 The Ledger is an evidence system, not a reputation score We deliberately reject the idea that the Leadership Ledger should produce one universal leadership score. Leadership quality is multidimensional. A National Chair, technical specialist, systems scientist, mentor and Regional federation leader may create value in fundamentally different ways. Compressing those contributions into one score would create false comparability and strong incentives for members to optimize visible metrics rather than institutional value. The Ledger therefore records state and evidence rather than attempting to rank human worth. It should make it possible to answer questions such as whether a contribution was verified, whether a Plan matured, whether a Working Group produced a durable output, whether the member supported succession or whether an initiative was adopted. These are useful institutional facts. They do not require us to declare that one leader is universally better than another. *** #### 11.2.5 The Ledger serves the institution beyond the member's tenure The most important test of the Ledger may occur after a member has changed role, paused participation or left the active Council. The institution should still be able to understand which capabilities the person helped build, which relationships they initiated, what evidence was generated, which work remains active and what successor leaders need to know. A strong Ledger therefore reduces dependence on institutional memory held informally by staff or founding members. The person may leave the active system. The useful institutional memory should remain. *** ### 11.3 The Leadership Record #### 11.3.1 The record begins with context, not achievement The Leadership Record begins when the member enters NLS, not when a visible achievement occurs. This is important because later contribution can only be interpreted properly if the institution understands the starting context. The record should therefore preserve the member's initial Council, participation scope, primary institutional home, leadership baseline, contribution thesis and relevant institutional context. As the Annual Leadership Contribution Plan develops, the record should then connect that Plan to subsequent work, evidence, learning and review. This creates a coherent institutional narrative from **entry through development**, rather than a retrospective list assembled only after successes become visible. The member's record should therefore tell the story of a leadership relationship, not merely display its most favorable moments. *** #### 11.3.2 The record should distinguish stable facts from changing states Some leadership facts are relatively stable. The person's identity and historical professional experience do not change each year. Other facts are intentionally dynamic. Council assignment, professional affiliation, Annual Leadership Contribution Plan, Council office, Working Group participation and contribution states may change frequently. NLS should preserve these different temporal characteristics. A mature record allows the current state to remain clear without erasing significant prior states. If a member moved from National to Regional contribution, the earlier National history should not disappear. If a Plan was substantially redesigned, the current Plan should be visible while the material history of the change remains understandable. This balance between current accuracy and historical continuity is essential to the value of the Ledger. *** #### 11.3.3 The record should preserve institutional context around contribution A contribution rarely occurs in isolation. A member may help lead a Working Group supported by a National Desk, drawing on GCRI evidence and later entering Nexus Universe. Another member may contribute to a Regional proposition initiated through several National Councils. The record should preserve enough of this surrounding context that the member's role remains interpretable. The purpose is not to make every record excessively complex. It is to avoid the opposite error, where a short achievement statement removes all institutional context and makes a collective effort appear to be an individual accomplishment. A mature leadership record should therefore preserve both **the contribution and the system around the contribution**. *** #### 11.3.4 The record should include development and correction Leadership development is itself part of the institutional history. A member may become more capable in systems thinking, strategic foresight, finance-readiness, frontier technology or cross-institutional leadership. A first-year contribution thesis may be corrected substantially. A Council role may evolve. A leader may discover that their greatest value lies in a different pathway from the one initially imagined. These changes should be visible where they materially affect the leadership relationship. The purpose is not to document every learning moment. It is to preserve significant transitions that help the institution understand how the member's contribution became more mature. NLS thereby recognizes development as part of leadership value rather than treating the member as a static profile. *** ### 11.4 Contribution Claims #### 11.4.1 A contribution claim is a statement requiring institutional interpretation A **contribution claim** is any substantive statement that a member helped create, change, strengthen, develop, test, connect or advance something within the Nexus system. Claims may originate from the member, Council, Desk, Working Group, programme team, Leadership Ledger process or another relevant institutional source. The existence of a claim is not the same as verification. A claim begins the evidence process by stating what is believed to have occurred. The next question is what evidence and institutional context support that interpretation. This distinction is particularly important because many leadership contributions are qualitative and collaborative. NLS requires a mechanism through which they can be recognized without simply converting every assertion into institutional fact. *** #### 11.4.2 Claims should be specific enough to be evaluated A useful contribution claim should describe the member's actual role with enough precision that another competent reviewer can understand what is being asserted. Statements such as **“advanced resilience”** or **“supported innovation”** may be directionally true but provide little basis for institutional memory. A stronger claim might explain that the member convened specific institutional perspectives around a National infrastructure dependency, led the development of a Working Group proposition, contributed specialist analysis to a Nexus Universe test, or mentored successor leaders through a defined Council formation period. Specificity improves both recognition and evidence. It allows the institution to distinguish what the leader actually did from the broader outcome to which the contribution may have related. *** #### 11.4.3 Claims should respect the boundary of the member's role A contribution claim should not imply that the member controlled an outcome that depended materially on other institutions. If a member introduced two institutions and those institutions later created a programme, the leader's contribution may have been consequential, but it is not identical to having created or delivered the entire programme. If a leader helped shape a public-policy option, the claim should not imply that the member made the public decision. If a Council Member contributed to programme readiness, the claim should not imply ownership of later implementation. This discipline is particularly important for non-executive leadership. NLS should recognize high-value influence without transforming influence into fictional control. *** #### 11.4.4 Claims may describe intellectual, relational, institutional and developmental contribution Not every valuable contribution produces a material object. A member may provide an intellectual contribution by reframing a problem. They may provide relational contribution by connecting institutions. They may provide institutional contribution by strengthening Council formation or succession. They may provide developmental contribution through mentoring. They may provide technical or substantive contribution through research, analysis or a Mission. The evidence model should remain capable of recognizing these different forms without requiring them to be forced into one template. The common discipline is that the claim should describe **what changed or became possible because of the contribution** and remain proportionate to the evidence available. *** #### 11.4.5 Claims should not be inflated by later success Leadership records are particularly vulnerable to retrospective inflation. A small early contribution can become associated with a much larger later programme, and institutional memory may gradually attribute the final outcome to the original contributor. NLS should resist this. The Ledger should preserve the contribution at the state and scope in which it occurred. If the member later contributes again as the programme matures, those later contributions can also be recorded. This creates a more accurate longitudinal account than rewriting the earliest record after the eventual outcome becomes known. *** ### 11.5 Evidence and Verification #### 11.5.1 Evidence supports interpretation rather than replacing judgment Evidence within NLS provides the basis through which contribution claims and maturity states can be interpreted credibly. Some evidence will be highly structured, such as a completed research output, test record, approved Working Group product or documented programme artifact. Other evidence may be qualitative, such as institutional testimony, meeting records, mentoring records, peer observation or documented contribution to a complex collective process. The strength of evidence should be judged according to the nature of the claim. We do not impose one evidence type on every form of leadership. We require enough evidence for the institution to understand why the claim is credible. This preserves rigor without creating artificial uniformity. *** #### 11.5.2 Verification is a separate institutional act We distinguish **submission of evidence** from **verification**. A member may submit a contribution claim and supporting material. A Working Group may provide evidence of work completed. Foundry may associate records automatically. An AI system may help organize relevant documentation. These actions can support verification. They do not necessarily complete it. Where a claim materially affects institutional state, recognition, maturity or another consequential interpretation, the system should preserve an appropriate review step by a person or institutional function capable of assessing the claim independently. The governing principle is: > **A person may claim contribution. The same assertion should not become verified merely because the claimant entered it into the system.** *** #### 11.5.3 Verification should be proportionate Not every contribution requires the same level of review. A modest internal mentoring contribution may require simple confirmation. A material claim that a proposition was validated, that an institutional programme was adopted or that a National capability reached a new maturity state may require significantly stronger evidence and review. Verification should therefore be proportionate to consequence. The objective is not to create maximum bureaucracy around every contribution. It is to apply enough evidentiary discipline that the meaning of consequential states remains credible. This allows NLS to operate efficiently while preserving the integrity of the records that matter most. *** #### 11.5.4 Verification should examine the claim that was actually made Reviewers should verify the specific contribution claim rather than allowing general confidence in the member to substitute for evidence. An accomplished leader may be highly credible overall while a particular contribution claim remains weakly supported. Conversely, a new member may provide exceptionally strong evidence for a specific contribution. Verification therefore attaches to the claim and evidence, not to prestige. This is one of the ways NLS protects institutional memory from hierarchy effects. The same discipline should apply regardless of whether the contributor is a founding member, Chair, specialist, National leader or Global participant. *** #### 11.5.5 Evidence should preserve context and provenance Where material to interpretation, evidence should retain enough information to understand where it came from, when it was produced, what institutional environment it concerns and what limitations affect its use. A test conducted in one country may not support the same conclusion elsewhere. A document created before a major programme change may no longer describe the current state. A testimonial from a direct collaborator may provide useful evidence of contribution but should not be interpreted as independent proof of a wider institutional outcome. Context gives evidence meaning. The Ledger should therefore connect material evidence to the conditions required to interpret it responsibly. *** #### 11.5.6 Verification can conclude with uncertainty Verification does not require the institution to pretend certainty where the evidence remains incomplete. A claim may be partially supported. Evidence may establish that the member contributed but not the scale of the resulting effect. Different participants may interpret the member's role differently. Where material uncertainty remains, the record should preserve it. This is preferable to either rejecting every contribution that lacks perfect proof or converting ambiguous evidence into an overly confident institutional statement. NLS values **accurate uncertainty over artificial certainty**. *** ### 11.6 Contribution States #### 11.6.1 States provide a common grammar for the lifecycle of contribution We use contribution states so that the institution can distinguish what a member proposed, what Nexus accepted for development, what entered active work, what the member delivered, what was verified and what later happened to the resulting contribution. The common contribution lifecycle is: > **Proposed → Accepted → Active → Delivered → Verified → Adopted → Scaled** These states should not be interpreted as an automatic progression. A contribution may stop after testing. It may be delivered and verified without being adopted. It may be adopted locally without being scaled. It may be redesigned and return to an earlier state. The value of the model lies in making those differences visible. *** #### 11.6.2 Proposed A contribution is **Proposed** when the member or relevant NLS process has articulated a substantive contribution that may warrant development but has not yet been accepted into active institutional work. Proposed status protects the distinction between individual intention and institutional commitment. A leader may have an excellent idea that requires further diagnosis, different timing or a different institutional route. Recording it as Proposed allows the idea to enter institutional consideration without implying that Nexus has already committed resources or endorsed the proposition. This creates space for initiative without collapsing initiative into adoption. *** #### 11.6.3 Accepted A contribution becomes **Accepted** when the appropriate NLS environment has determined that the proposition is sufficiently relevant and coherent to enter the member's Plan, Working Group, Mission or another legitimate development pathway. Acceptance does not establish that the contribution will succeed. It establishes that the institution is prepared to work with the proposition. This state is particularly useful because it marks the point at which an individual idea becomes an institutional object. From that point forward, reciprocal responsibilities around support, evidence and review become more meaningful. *** #### 11.6.4 Active A contribution becomes **Active** when substantive work is underway. This may involve research, Council development, Working Group activity, relationship-building, programme design, mentoring, testing, Mission participation or another form of work connected to the accepted contribution. Active state should not be inferred merely because time has passed since acceptance. The record should reflect that material activity has actually begun. This distinction prevents the Ledger from presenting dormant propositions as though they were progressing. *** #### 11.6.5 Delivered A contribution becomes **Delivered** when the member has completed the substantive contribution they were expected to provide within the defined scope. Delivery describes the member's action, not the later response of the institution. A leader may deliver a research paper, relationship architecture, Working Group output, mentoring cycle, programme design, decision packet or another agreed contribution. Whether that contribution is later verified, adopted or scaled is a separate question. This state is essential because it prevents the member's record from being dependent entirely on decisions made by other institutions after the member has completed their part. *** #### 11.6.6 Verified A contribution becomes **Verified** when the institution has reviewed sufficient evidence to conclude that the material contribution described in the record occurred substantially as stated. Verification strengthens the institutional reliability of the claim. It does not imply that the output was correct in every respect, that every recommendation was adopted or that a larger outcome followed. The state answers a narrower question: **did the contribution occur at the scope and in the role represented?** This discipline helps preserve accurate recognition. *** #### 11.6.7 Adopted A contribution becomes **Adopted** when the relevant institution, Council, programme or operating environment has taken up the resulting method, output, proposition or capability in a substantive way. Adoption is different from verification because it describes what happened after the contribution was delivered. A verified recommendation may not be adopted. A Working Group product may be adopted by a National Portfolio. A method may become part of Council practice. A technical proposition may become part of an active programme. The Ledger should preserve this distinction so that the member's contribution and the institutional response remain intelligible as separate but related facts. *** #### 11.6.8 Scaled A contribution becomes **Scaled** when an adopted capability or approach has expanded materially in scope, geography, institutional use or another relevant dimension beyond its initial application. Scaling should be evidenced rather than inferred from intention. A National method may be replicated across several jurisdictions. A programme may expand substantially. A Working Group method may become a common NLS practice. The Ledger should recognize the member's relationship to the scaled outcome accurately. If the member's involvement concluded before scale, the record should not imply that they personally delivered the expansion. It should preserve the earlier contribution while connecting it to the later institutional history. *** #### 11.6.9 Contribution states and Plan maturity are related but distinct Contribution states should not be confused with the ALCP maturity model established in Part VII. The maturity model describes the state of a **proposition or capability**, such as Concept, Testing, Validated, Scale-Ready or Institutionalized. Contribution states describe the relationship between the **member's contribution and the institution**, such as Proposed, Active, Delivered or Verified. A leader may deliver and verify their contribution while the underlying programme remains at Pre-Scale. A technology may reach Validation while several member contributions within that workstream occupy different states. Preserving both models allows NLS to understand the work and the human contribution to that work without collapsing them into one timeline. *** ### 11.7 Attribution #### 11.7.1 Attribution is the discipline of describing who contributed what Attribution is central to NLS because systemic work is inherently collaborative. Leadership Councils, Desks, technical teams, researchers, Working Groups, institutions, communities and implementation partners may all contribute to one outcome. A credible institutional record must recognize this complexity without making contribution impossible to understand. Attribution therefore asks a precise question: > **What did this person or institution materially contribute within the wider architecture of the work?** The answer should be specific enough to recognize genuine contribution while preserving the roles of others. *** #### 11.7.2 Attribution should follow function, not visibility The most visible participant is not necessarily the largest contributor, and the largest contributor is not necessarily the person who carried the work publicly. A Chair may represent a Working Group's output while several members and researchers performed much of the substantive development. A technical specialist may create critical analysis while a senior leader secures the institutional relationship necessary for adoption. A Desk may provide the continuity without which neither contribution would become operational. NLS should therefore attribute according to actual function. Visibility can be relevant to communication. It should not become the architecture of institutional memory. *** #### 11.7.3 Intellectual, relational and operating contribution should remain distinguishable Different forms of contribution can coexist around the same outcome. One person may provide the central intellectual framework. Another may develop the institutional relationship. Another may lead technical testing. Another may coordinate implementation. Another may preserve evidence and continuity. The Ledger should be capable of representing these contributions without forcing them into one generic category. This produces a more useful history of how institutional capability was actually created. Future teams can then understand which combination of capabilities was required rather than believing that one person or one institution produced the whole result independently. *** #### 11.7.4 Attribution should preserve collective authorship Some Nexus outputs are genuinely collective. A Council position, multi-institutional framework, Working Group report or Nexus Universe finding may not have one principal author in the conventional sense. Where collective authorship is substantively accurate, NLS should preserve it. This does not mean individual contributions disappear. The Ledger can recognize significant roles internally while the public output remains appropriately collective. The purpose of attribution is truthfulness, not maximum individualization. *** #### 11.7.5 Attribution should be capable of correction Institutional understanding of contribution may evolve. A person initially credited with a major role may later clarify that another team performed substantial work. A previously invisible contributor may become apparent. New evidence may show that the member's influence was narrower or broader than first understood. NLS should therefore allow attribution to be corrected where the evidence warrants it. Recognition loses credibility when the institution protects earlier statements simply because they are already public or convenient. Accurate correction strengthens the integrity of both the Ledger and the people represented in it. *** ### 11.8 Outcomes and Adoption #### 11.8.1 Contribution and outcome are not the same fact One of the most important distinctions in the Leadership Ledger is between **what the member contributed and what eventually happened to the work**. A leader can make an excellent contribution that the receiving institution does not adopt. Adoption may depend on political priorities, resources, timing, operating capacity or another condition outside the member's control. Conversely, an initiative may later succeed for reasons extending far beyond the member's initial contribution. NLS should therefore evaluate the contribution at the level of the member's actual role while separately recording subsequent institutional outcomes. This creates a fairer and more analytically useful leadership record. *** #### 11.8.2 Adoption is evidence of institutional uptake Adoption occurs when a relevant institution begins using, integrating, applying or operationalizing a contribution in a meaningful way. The form of adoption will vary. A Council may adopt a method. A National Portfolio may incorporate a recommendation. A Working Group may use a framework. A programme may implement a technical capability. A National Desk may incorporate a process into recurring operations. Adoption should therefore be defined according to the nature of the contribution rather than one universal threshold. The essential condition is that the contribution has moved beyond delivery and into substantive institutional use. *** #### 11.8.3 Non-adoption does not erase contribution value A delivered and verified contribution can create value even where it is not adopted. Research may clarify why a programme should not proceed. An institutional mapping exercise may reveal that another pathway is required. A member may develop a sound proposal that remains unimplemented because resources are unavailable. The Ledger should preserve these distinctions. Otherwise, NLS would create an incentive for leaders to pursue only activities likely to generate visible adoption and neglect difficult diagnostic work whose value may consist precisely in showing that an intervention should not advance. Institutional learning can be valuable even where uptake does not occur. *** #### 11.8.4 Adoption does not automatically establish scale An adopted capability may remain narrow, experimental or context-specific. A National Council may adopt a process within one Working Group. A technology may become operational in one controlled environment. A methodology may be integrated into one National Portfolio without yet being transferable elsewhere. The Ledger should therefore avoid treating adoption as evidence of scaling. This distinction becomes particularly important as Nexus moves from Adopt into Replicate, Federate, Institutionalize and Scale. Different maturity states should remain visible so that the wider institution can understand what has actually been demonstrated. *** #### 11.8.5 Outcomes should connect back to institutional learning Where a contribution produces a material outcome, the institution should ask what can be learned from it. Why was the contribution adopted? Which dependencies mattered? Which relationships were essential? What should be preserved? Which conditions may limit replication? The Ledger should therefore connect outcomes to the wider learning architecture rather than treating adoption as the endpoint of the record. An outcome becomes more valuable when the institution can explain how it happened and which parts of that explanation are transferable. *** ### 11.9 Uncertainty and Dissent #### 11.9.1 Leadership records should preserve uncertainty honestly Not every contribution can be evaluated with complete certainty. The effect of leadership on complex institutional outcomes is often distributed, indirect and difficult to isolate. Several people may influence the same decision. A relationship may matter without producing a visible immediate outcome. A mentorship contribution may reveal its significance years later. NLS should therefore avoid pretending that every contribution can be measured precisely. Where uncertainty is material, the record should preserve it. This does not weaken the Leadership Ledger. It strengthens it by ensuring that the level of confidence attached to the record remains proportionate to what the institution actually knows. *** #### 11.9.2 Dissent is part of the evidence architecture Leadership contribution may be interpreted differently by different participants. A member may believe their intervention was central to an outcome while a programme team interprets it as one of several contributing factors. A Council may disagree about whether a test established sufficient readiness. Different institutions may draw different lessons from the same Nexus Universe exercise. Where such disagreement affects the institutional meaning of the record, NLS should not force artificial consensus simply to create a clean narrative. Material dissent can be preserved alongside the evidence and final institutional state. The institution should know not only what conclusion was reached, but where credible disagreement remained. *** #### 11.9.3 Dissent should be substantive rather than performative Preserving dissent does not mean recording every disagreement indefinitely. The purpose is to retain alternative interpretations where they materially affect the validity, maturity or institutional meaning of the contribution. A dissenting view should therefore be connected to a clear substantive issue, evidence or institutional perspective. This prevents the Ledger from becoming a repository of unresolved interpersonal disagreement while still protecting important intellectual challenge. The standard is materiality. *** #### 11.9.4 Uncertainty should affect the strength of the claim A leadership claim supported by strong direct evidence can be represented more confidently than one inferred from several qualitative sources. NLS should allow that difference to remain visible. The institutional system does not need to reject useful qualitative evidence. It needs to avoid describing uncertain contribution with the same confidence used for directly documented contribution. This principle aligns the Leadership Ledger with the wider Nexus evidence doctrine. Confidence should follow evidence rather than reputation, convenience or narrative appeal. *** ### 11.10 Correction #### 11.10.1 Correction is a normal function of institutional memory No multi-year leadership record will remain perfectly static. People change roles. Programmes evolve. Evidence improves. Earlier statements may prove incomplete. Attribution may require refinement. A contribution originally described as adopted may later be discontinued. An outcome initially attributed narrowly may prove to have been more collective. The Leadership Ledger therefore treats correction as normal. A correctable record is more trustworthy than one that protects historical wording at the expense of current accuracy. The purpose is to preserve both the current truth and enough relevant history to understand how the record changed. *** #### 11.10.2 Correction should distinguish error from evolution Not every change means the earlier record was wrong. A Plan can move to a new maturity state. A contribution can become adopted after previously being only verified. A member can change professional affiliation. These are evolutions. Other changes correct an actual error, such as inaccurate attribution, mistaken identity, incorrect dates or an overstated description. NLS should preserve this distinction where material. Evolution shows the system progressing. Correction shows the record becoming more accurate. Both belong in institutional memory, but they mean different things. *** #### 11.10.3 Members should be able to identify material errors in their record Because the Leadership Ledger concerns the member's institutional history, the member should have an appropriate mechanism to identify inaccurate or incomplete information and request review. Member input is important because leaders may be well positioned to notice misattribution, outdated affiliation or missing context. The member's request should not automatically rewrite the record. Where the disputed matter affects institutional state or another contributor, NLS may need to examine the evidence and context before changing it. This balance preserves both member dignity and institutional integrity. *** #### 11.10.4 Correction should not erase inconvenient evidence The correction function should not become a mechanism for removing valid but unfavorable institutional history merely because a later narrative would appear cleaner without it. A failed test, withdrawn contribution, corrected assumption or disputed interpretation may remain materially relevant to the leadership journey. Where such information is accurate and legitimately part of the institutional record, the appropriate response may be to add context, later evidence or a corrected state rather than pretend the earlier event never occurred. Institutional memory becomes useful precisely because it preserves learning, not only favorable outcomes. *** #### 11.10.5 Corrections should propagate coherently Where a material Ledger fact appears in several governed views, correction should propagate sufficiently that the institution does not maintain contradictory versions of the same fact indefinitely. A corrected professional affiliation should not remain outdated in one Council environment. A revised attribution should not continue appearing incorrectly in a public contribution profile where the public record is derived from the same underlying fact. This is one reason NLS prefers a coherent underlying leadership record with governed projections rather than multiple independent copies. One material fact should have one authoritative institutional source and many appropriate views. *** ### 11.11 Member Access to the Leadership Record #### 11.11.1 Members should be able to understand their institutional record The Leadership Ledger should not operate as an opaque internal assessment system whose contents are hidden from the member whose contribution it describes. Members should have meaningful access to the portions of their leadership record appropriate to their relationship with NLS so that they can understand current standing, Plan state, material contribution history, evidence, annual reviews and significant transitions. This transparency supports trust. It also improves accuracy because members can identify missing or incorrect context before errors become embedded across several annual cycles. A leadership record should be something the member can understand, not a hidden score being maintained about them. *** #### 11.11.2 Access should provide context, not raw information without interpretation A sophisticated Ledger may contain several types of state, evidence and institutional relationship. Member access should therefore be designed so that the information is intelligible. The member should be able to understand why a contribution is recorded in a particular state, what evidence supports it, whether verification has occurred, what maturity applies to the related proposition and which changes arose during review. This is another reason the Leadership Cockpit matters. Digital access should reduce ambiguity rather than expose the member to an undifferentiated internal data structure. *** #### 11.11.3 Member access supports reflective leadership development The Leadership Record can also become a leadership-development tool. Over several years, a member should be able to see how their contributions evolved, which types of work created the strongest value, where repeated dependencies emerged, how their Council roles changed and which learning or mentoring activities shaped later contribution. This creates a longitudinal view of leadership that is rarely available through conventional professional biographies. The record becomes not only a record of what the leader did, but a mirror through which the leader can understand how their systems leadership developed. *** #### 11.11.4 Access should remain proportionate to institutional context Member access to their own leadership history does not imply access to all internal information associated with every institution or person involved in that history. A contribution record may reference collective work, internal institutional assessments or other records whose wider disclosure would be inappropriate. NLS should therefore provide sufficient transparency for the member to understand and engage their own record while preserving the legitimate information boundaries of the wider institution. Transparency and responsible information stewardship are compatible when access is designed around context. *** ### 11.12 Public and Institutional Views #### 11.12.1 One leadership history can support several legitimate views The Leadership Ledger may support different views for different institutional purposes. The member needs a personal leadership view. The Council may need a Council-specific view. GCRI Canada may require a wider NLS operating view. A Working Group may need information relevant to its current work. A public audience may appropriately see selected approved biography and contribution information. These different views should not become independent biographies that gradually contradict one another. They should remain governed projections of one coherent underlying institutional history. This is the Nexus principle of **one fact family, one authoritative owner, many appropriate views** applied to leadership. *** #### 11.12.2 The public view should be selective and accurate The public leadership profile should provide enough information for external audiences to understand who the member is, the Council context in which they participate and selected public-safe areas of contribution. It should not expose the full Leadership Ledger. Internal planning, development, unfinished tests, sensitive institutional relationships, restricted evidence, internal review and other operational information may be essential to NLS while inappropriate for public publication. The public record should therefore be selective without becoming misleading. A concise accurate profile is preferable to an expansive public narrative containing claims whose institutional state is difficult to defend. *** #### 11.12.3 Public claims should reflect the underlying evidence state Where the public profile describes contribution, the language should remain consistent with what the Ledger can support. A contribution that has been delivered should not be described publicly as scaled merely because the wider programme later became prominent. A test should not be represented as full implementation. Participation should not be described as adoption. A member's involvement in a collaborative project should not be represented as sole ownership. This discipline protects the credibility of the member as much as Nexus. Strong institutions do not need to inflate contribution in order to recognize it. *** #### 11.12.4 Council and institutional views may contain more operational context Internal Council and institutional views can appropriately contain more information where that information is required for leadership planning, contribution review, succession, Working Group design or annual renewal. The purpose of internal visibility is not unrestricted transparency among all members. It is to ensure that the people responsible for supporting and reviewing leadership possess enough context to perform those functions well. The appropriate view therefore follows the institutional purpose. This allows NLS to preserve coherence without assuming that every legitimate participant requires the same information. *** #### 11.12.5 Different views should never create different underlying truths The system may present information differently according to audience, but the underlying facts should not change merely because the audience changes. A public profile may omit sensitive context, but it should not contradict the internal record. An internal Council view may provide more detail, but it should not invent a stronger contribution state than the verified evidence supports. This principle is fundamental to Nexus information integrity. Different views may have different levels of detail. They should not contain different realities. *** ### 11.13 Annual Contribution Review #### 11.13.1 The Annual Contribution Review synthesizes the leadership year We use the **Annual Contribution Review** to bring together the distributed evidence of the member's annual participation into one coherent institutional assessment. The review should not duplicate the Year-One Review defined in Part VI, although the two processes may overlap for first-year members. The Annual Contribution Review is the recurring longitudinal mechanism through which NLS examines contribution, evidence, development, Four-Way Value, institutional learning and future focus across every annual cycle. Its purpose is synthesis. Council participation, Working Groups, Missions, mentoring, research, Foundry activity, Universe contributions and institutional relationships may have developed in different environments. The annual review brings the material elements together and determines what they mean as one leadership year. *** #### 11.13.2 Review begins from the Plan but is not confined to it The Annual Leadership Contribution Plan provides the primary frame for review because it established the year's intended contribution. The review should examine which outcomes progressed, which dependencies emerged, which tests occurred, which evidence was generated and how the Plan changed. The member may also have created legitimate value outside the original Plan. An unexpected Council need may have required substantial contribution. A member may have mentored another leader, supported a Regional issue or helped resolve a material institutional problem that could not have been predicted at the beginning of the year. The Annual Contribution Review should be structured enough to preserve Plan accountability and flexible enough to recognize consequential leadership that emerged from real institutional conditions. *** #### 11.13.3 Review examines contribution, not performance theatre The review should avoid rewarding activity that is visible merely because Foundry can count it. Numbers of meetings, comments, introductions or documents may provide context but should not become the core measure of leadership quality. The review should concentrate on what the member helped understand, develop, connect, test, strengthen or institutionalize. This requires professional judgment. A serious Leadership System cannot outsource annual review entirely to dashboards. The evidence architecture should support human interpretation, not attempt to eliminate it. *** #### 11.13.4 Review should examine Four-Way Value The Annual Contribution Review should revisit the Four-Way Value architecture. What became stronger within Nexus? What value emerged for the relevant country, region or system? What legitimate value accrued to the member's principal institution? How did the member develop personally? These questions help determine whether the relationship remains sufficiently reciprocal to sustain. A strong contribution that repeatedly creates value in only one direction may eventually require redesign. The review therefore examines not only whether the member did useful work, but whether the institutional relationship remains healthy. *** #### 11.13.5 Review should examine development and future capability Annual review should also consider how the leader changed. Did the member become more capable of working across systems? Did their understanding of evidence improve? Did they develop new institutional literacy, technology fluency, foresight capability or finance-readiness understanding? Did they become more effective at mentoring, chairing, Working Group leadership or federation? This matters because NLS is intended to create stronger leaders as well as stronger institutional outputs. The member's future value may therefore increase even in a year where the visible programme outcomes remained limited. *** #### 11.13.6 Review should examine the institution's contribution to the member Reciprocity requires Nexus to examine its own performance. Did the member receive useful Leadership Intelligence? Was the Council environment substantive? Did the Desk provide adequate continuity? Were Working Group and Foundry interfaces effective? Did Universe create genuine learning? Were institutional support and expectations sufficiently clear? A leadership relationship can underperform because the member contributed weakly, because the institution supported the member poorly, or because both conditions occurred. The annual review should be mature enough to distinguish among them. NLS should not use the Ledger as a mechanism through which the institution evaluates everyone except itself. *** #### 11.13.7 Review should preserve correction and dissent Where contribution remains disputed or evidence is incomplete, annual review should not manufacture certainty merely because the year is ending. The record may appropriately conclude that a contribution occurred but its effect remains uncertain, that several participants interpret the outcome differently or that another cycle is required before the institution can determine the value of the proposition. These are legitimate conclusions. A mature institutional record should prefer an accurate incomplete conclusion to a confident but weakly supported one. Annual review is therefore a moment of synthesis, not forced closure. *** #### 11.13.8 Review should produce the next contribution state The Annual Contribution Review should conclude by establishing the best current interpretation of the member's contribution and the appropriate next state. A contribution may remain Active, become Delivered, move into Verification, be recorded as Adopted or connect to a later Scaled outcome. A Plan may renew around the same mission, narrow, expand, enter Strategic Delivery, move toward a Council office, continue in validation or conclude. The review therefore links evidence to future institutional design. It should tell the member and the institution not only what happened, but what the accumulated evidence implies for the next leadership cycle. *** #### 11.13.9 Review contributes to Council and system learning Individual annual reviews should also generate aggregate institutional intelligence. If several leaders encounter the same dependency, the problem may belong to the Council or National system rather than to the individuals. If multiple Plans struggle to access the same technical capability, Foundry or programme infrastructure may require improvement. If leaders repeatedly create strong value through one type of Mission, NLS may have identified a method worth formalizing. The Leadership Ledger should therefore support learning across the leadership system without reducing members to comparative rankings. Aggregate patterns can help Nexus understand **where its architecture is enabling contribution and where it is constraining it**. This is one of the most important long-term values of the evidence model. *** #### 11.13.10 The contribution and evidence proposition The full contribution architecture of NLS can therefore be expressed as a continuous chain: > **Leadership intention becomes a contribution claim. The claim becomes an institutional proposition. The proposition enters work. Work generates evidence. Evidence enables verification. Verification clarifies contribution. Institutional response determines adoption. Continued use may lead to scale. Learning and correction return to the Leadership System and shape the next cycle.** At every stage, attribution remains proportionate, uncertainty remains visible where material and the member's contribution is distinguished from the actions of institutions that follow. The objective is not to bureaucratize leadership. It is to ensure that a leadership system operating across many years, countries, institutions and people can still explain what it has learned and how its capabilities were created. *** ## PART XI FRAMEWORK PRINCIPLES #### Evidence before institutional narrative We preserve the distinction between what is asserted, what is evidenced, what is verified and what later institutions do with the resulting contribution. Leadership reputation, seniority and visibility may help the institution interpret context, but none should silently substitute for evidence where a material institutional claim is being made. #### Contribution without reductionism We do not reduce leadership to counts of meetings, documents, platform activity or one universal score. Evidence exists to improve understanding of contribution, not to manufacture a numerical hierarchy among people whose roles, contexts and forms of value may be fundamentally different. #### One longitudinal leadership history The Leadership Ledger preserves one coherent institutional history across changes in Council, professional affiliation, Annual Leadership Contribution Plan, Council office, Working Group, Mission and annual cycle. Different audiences may receive different governed views of that history, but those views should remain derived from the same underlying institutional facts. #### Claims, evidence and verification remain distinct A member, Council or programme environment may make a contribution claim and provide supporting evidence. Verification is a separate institutional act where the significance of the claim requires it. The person making the claim should not be treated as the sole verifier of that same claim merely because digital infrastructure makes self-reporting easy. #### Attribution follows actual function We recognize intellectual, relational, institutional, technical, operating, developmental and other legitimate forms of contribution according to the role actually performed. Visibility, seniority or later programme success should not erase the contributions of others or convert collective institutional work into an individual claim. #### Contribution state and programme maturity remain separate The contribution lifecycle of Proposed, Accepted, Active, Delivered, Verified, Adopted and Scaled describes what happened to the member's contribution. The ALCP maturity architecture describes the state of the underlying proposition or capability. Preserving both allows NLS to understand human contribution and institutional maturity without confusing one for the other. #### Uncertainty and dissent remain legitimate institutional facts Where contribution, attribution or outcome remains materially uncertain or contested, the Leadership Ledger should preserve that condition proportionately. An accurate record can contain uncertainty. Institutional credibility is weakened, not strengthened, when ambiguity is hidden merely to create a cleaner narrative. #### Correction strengthens the Ledger Leadership records should remain correctable as better evidence, changed context or more accurate attribution emerges. Correction should improve the current institutional truth while preserving enough relevant history to understand significant transitions and avoid erasing valid but inconvenient learning. #### Reciprocity includes transparent review Members should be able to understand their leadership record and raise material inaccuracies. Annual review should examine not only what the member contributed but whether NLS provided the Council environment, intelligence, infrastructure and institutional support required around that contribution. #### Institutional memory is the final purpose The deepest purpose of contribution evidence is not recognition alone. It is to ensure that Nexus can learn from its own leadership history. A future Council, Desk, country or leadership cohort should be able to understand which capabilities were built, how they were built, what evidence supported them, what failed, what changed and what remains useful. *** ## OPERATING RELATIONSHIP Part XI establishes the evidence and institutional-memory architecture through which the Nexus Leadership System can remain credible as it grows across members, Councils, jurisdictions and annual cycles. The architecture begins by distinguishing **participation from contribution, contribution from verification, verification from adoption and adoption from scale**. These distinctions allow us to recognize meaningful leadership accurately without attributing to an individual outcomes that depended upon other actors, and without allowing later success to inflate the meaning of an earlier contribution. The **Leadership Ledger** provides the longitudinal institutional record. It connects Claim, Role, Evidence, Attribution, State, Institutional Context, Value, Dependencies, Correction and Outcome so that leadership history can be understood as an evolving system rather than a collection of achievements. The Ledger records institutional states rather than creating a universal reputation score. It preserves enough context for future Councils, Desks and leadership cohorts to understand how capability was created and what remains transferable. Contribution claims enter a proportionate evidence process. The member or another legitimate institutional source may state what occurred and provide supporting evidence. Where the consequence of the claim requires it, verification remains a distinct institutional act. The governing discipline is simple: **a person may claim contribution, but self-assertion does not automatically become institutional verification**. The contribution lifecycle of **Proposed → Accepted → Active → Delivered → Verified → Adopted → Scaled** allows Nexus to understand how individual contribution relates to later institutional response. This remains distinct from the maturity state of the underlying Plan or programme. Attribution then preserves the collective nature of systems work by identifying the actual function each contributor performed rather than allocating credit according to visibility or hierarchy. Uncertainty, dissent and correction remain part of the architecture. NLS does not require a false appearance of certainty in order to maintain a credible leadership record. Where evidence remains incomplete, the record can say so. Where credible interpretations differ, the disagreement can remain visible. Where stronger information changes the understanding of a contribution, the record can be corrected. Members receive appropriate access to their Leadership Record, while public, Council and wider institutional views remain governed according to their purpose. Different views may contain different levels of detail, but they should not create different underlying truths. The **Annual Contribution Review** completes the cycle. It synthesizes the member's Plan, Council participation, Working Groups, Missions, evidence, development, Four-Way Value, institutional support and material corrections into a coherent annual interpretation. It also returns aggregate learning to the wider NLS architecture so that repeated dependencies, successful methods and institutional weaknesses can be recognized across members rather than rediscovered individually. The governing proposition of Part XI is therefore: > **Nexus does not ask leaders merely to contribute. We build an institutional memory capable of understanding what was contributed, what supports the claim, how the work should be attributed, what the receiving institution did with it, what was learned, what changed and what future leaders should inherit from the experience.** ## NEXT ## PART XII: NATIONAL NEXUS LEADERSHIP ### National Ownership, Council Formation, Public-Private-Planet Capability, the National Desk, National Model, National Portfolio and the Route to Regional Federation Part XII will move from the common leadership architecture into the country-level operating system where Nexus leadership becomes nationally grounded. It will define the National Nexus model, the meaning of National ownership, the distinction between nationally grounded capability and external direction, the initial leadership nucleus and development toward a full National Leadership Council, the relationship among Public-Private-Planet and Five-Helix formation, the National Desk and Secretariat, the National Model, National Portfolio and twelve-domain National risk docket, institutional engagement, National capability and sustainability, succession, and the conditions through which functioning National systems become capable of federating regionally. ## 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); [Data and Evidence](https://nexustandards.com/data/) (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/xi.-evidence-ledger.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.