> 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/xix.-leadership-integrity.md). # XIX. Leadership Integrity Learn how NLS manages leadership integrity through conflicts of interest, recusal, anti-capture, procurement neutrality, fair process, and responsible technology. **Where this fits:** all six sectors · [Nexus Universe](/organization/programme/universe.md), [Risk Academy](/organization/programme/academy.md) · The Global Risks Forum (GRF), with GCRI Canada as Consortium Secretariat · the programme year (quarterly NLC alignment; the Year-One Gateway) · systems [NXS-HUB](/organization/systems/nxs-hub.md), [NXS-RLS](/organization/systems/nxs-rls.md), [NXS-NSF](/organization/systems/nxs-nsf.md) · framework page (NLS). **In brief.** We establish integrity as an operating condition of the Nexus Leadership System rather than a ceremonial statement of values. 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 %} ## 19. LEADERSHIP INTEGRITY ### 19.1 The NLS Integrity Framework #### 19.1.1 Integrity is an operating condition of leadership We establish integrity as an operating condition of the Nexus Leadership System rather than a ceremonial statement of values. NLS brings together people whose professional lives may span government, enterprise, academia, civil society, finance, infrastructure, technology and other influential institutional environments. This diversity is one of the system's greatest strengths. It also creates complexity. A mature leadership architecture cannot assume that complexity disappears because accomplished people act in good faith. The system must be capable of recognizing competing responsibilities, managing overlapping interests, preserving institutional independence, supporting challenge and responding to concerns without converting every complexity into suspicion. Integrity therefore concerns the design of the system as much as the character of the individual. We seek to create conditions in which leaders can contribute fully while the institution remains capable of asking **who is acting, in what capacity, with what relevant interests, on whose behalf and toward what institutional purpose**. *** #### 19.1.2 Integrity is more than absence of misconduct A leadership system can remain free from obvious misconduct while still becoming institutionally weak. One organization may dominate agenda formation. A highly visible leader may influence opportunities disproportionately. Sponsors may shape attention without formally directing outcomes. Members may hesitate to challenge people with greater prestige. Public relationships may be represented more strongly than the underlying evidence supports. Professional assignments may circulate repeatedly through a small network. None of these conditions necessarily begins as intentional wrongdoing. They can emerge gradually from convenience, familiarity, social hierarchy and accumulated influence. NLS therefore treats integrity as the continuous maintenance of conditions under which institutional judgment remains credible. The relevant standard is not merely **“Has anyone done something wrong?”** It is also **“Is the architecture still capable of producing trustworthy judgment?”** *** #### 19.1.3 Integrity should preserve contribution rather than suppress complexity Senior leaders often possess the most value precisely because they hold substantial external responsibilities, relationships and interests. An executive understands the private sector because they participate in it. A public official understands government because they operate inside public institutions. A scientist brings research networks. A finance leader brings understanding of capital systems. NLS should not seek integrity by excluding everyone with consequential institutional relationships. Instead, we design for transparent and proportionate management of complexity. The objective is **not conflict elimination**. It is sufficient visibility and institutional discipline that relevant relationships can be understood and managed without unnecessarily excluding expertise. *** #### 19.1.4 Integrity belongs to individuals and institutions Members carry responsibilities for how they participate, describe their roles, identify relevant interests, use information and interact with other members. NLS also carries responsibilities. We should design fair processes, avoid creating incentives for hidden conflicts, preserve evidence, maintain appropriate boundaries, treat similar situations consistently and provide meaningful pathways through which concerns can be raised and reviewed. Integrity therefore cannot be outsourced to personal ethics alone. The architecture itself must make responsible conduct easier and institutional overreach harder. *** #### 19.1.5 Integrity should remain proportionate Not every issue requires escalation. A minor overlapping professional interest may simply need to be noted. A significant relationship may require additional transparency. A specific decision may justify recusal. A structural conflict may require a role change. Serious conduct may require formal review. NLS should be capable of distinguishing these conditions. An integrity system that treats every complexity as a major violation will encourage defensive participation and excessive bureaucracy. A system that treats every issue informally will eventually lose credibility. Proportionality allows the response to follow the actual institutional consequence. *** ### 19.2 Conflicts of Interest #### 19.2.1 Conflict is a relationship condition, not automatically misconduct We define a **conflict of interest** broadly as a situation in which a member's other interests, responsibilities or relationships could materially affect, or reasonably be understood as affecting, their judgment within a particular Nexus matter. The existence of such a conflict does not automatically mean the member has acted improperly. In a network of accomplished leaders, conflicts and competing responsibilities will arise regularly. The integrity question is therefore what the institution does once the relevant condition becomes visible. A well-managed conflict may permit continued valuable participation. An undisclosed or poorly managed conflict can undermine trust even where the underlying decision was technically sound. *** #### 19.2.2 Conflicts are contextual A relationship that creates no meaningful conflict in one matter may become significant in another. A member employed by an infrastructure company may contribute effectively to many Council discussions and require additional management only when a specific programme directly concerns that company. A finance leader may contribute broadly to readiness architecture while requiring greater care around a particular transaction or opportunity. A researcher may participate freely in most work while facing a specific issue involving their own institution's competing proposal. We therefore examine the **matter, relationship and institutional consequence together**. This contextual approach avoids unnecessary blanket exclusion while preserving seriousness where the actual circumstances require it. *** #### 19.2.3 Conflicts can arise from several kinds of relationship Relevant conditions may arise through employment, directorships, public office, professional services, supplier relationships, investments, related organizations, research interests, programme participation, competition, family or close professional relationships, access to confidential information, prospective assignments or other circumstances that could affect the member's position in a particular matter. The importance of the relationship depends on context. NLS should not seek an unlimited catalogue of every interest in a member's life. The purpose is to identify those relationships sufficiently connected to Nexus activity that the institution needs to understand them in order to preserve credible judgment. *** #### 19.2.4 Members share responsibility for surfacing material conflicts The institution cannot identify every relevant relationship independently. Members should therefore raise a material conflict or competing interest when they know, or reasonably should understand, that it could affect their participation in a Nexus matter. This expectation should be understood as part of professional leadership rather than an accusation of impropriety. Strong leaders are capable of saying, **“I have relevant context here, and the institution should know it.”** Such transparency often allows the person to continue contributing more credibly because peers understand the relationship rather than having to speculate about it. *** #### 19.2.5 Disclosure does not decide the response automatically A disclosed conflict does not necessarily require recusal. The institution may determine that the relationship is immaterial, that disclosure is sufficient, that the person should contribute factual expertise but not participate in a specific recommendation, or that full recusal is appropriate. The response should follow the nature of the matter. This distinction encourages disclosure. If every disclosed interest automatically removes the member from participation, leaders may become reluctant to identify ordinary complexity that the institution could have managed easily. Disclosure opens the integrity process. It does not predetermine the outcome. *** ### 19.3 Recusal #### 19.3.1 Recusal is a protective mechanism We use **recusal** where a member should step aside from a defined part of a process because their participation could impair, or reasonably be understood as impairing, the integrity of the institutional judgment being made. Recusal protects the member, the institution and the resulting decision. It should not be interpreted automatically as a finding of wrongdoing. A person may possess exactly the expertise that makes the matter relevant to them professionally. Stepping aside from a consequential decision while providing factual context through an appropriate route may be the most responsible form of participation. Recusal is therefore a **leadership discipline**, not a punishment. *** #### 19.3.2 Recusal should be scoped to the actual conflict Where possible, recusal should remain proportionate to the specific matter. A member may need to leave one decision while remaining fully active in the wider Working Group. They may provide technical background while not participating in candidate selection. They may contribute to a National risk discussion while stepping aside from a particular procurement-related matter involving their institution. This avoids unnecessary loss of capability. The objective is to protect the integrity of the affected decision while preserving legitimate contribution elsewhere. Broad exclusion should be used only where the conflict itself is broad enough to require it. *** #### 19.3.3 Recusal should preserve enough record for institutional clarity Where a material recusal affects a consequential process, the institution should preserve sufficient record that future reviewers can understand why the person's participation differed from the ordinary process. The record need not expose unnecessary personal detail. It should be enough to show that the integrity mechanism operated. This prevents later ambiguity about whether the person influenced a process from which they were expected to step aside. It also protects the member from incorrect assumptions about their involvement. *** #### 19.3.4 Recusal should not be used strategically to silence difficult expertise Integrity mechanisms themselves can be misused. A member should not be pushed out of substantive participation simply because their expertise creates inconvenient challenge, their institution holds a different perspective, or their dissent is unwelcome. The fact that a person has relevant professional experience does not automatically constitute a disabling conflict. The institution should distinguish a legitimate interest requiring management from an attempt to remove a perspective from the room. Fair integrity practice protects challenge as well as neutrality. *** ### 19.4 Related Interests #### 19.4.1 Related interests matter when they change the institutional context Some interests do not create a direct conflict but still provide important context for understanding the member's participation. A leader may serve on another Board, advise a relevant programme, invest in a sector, maintain a longstanding institutional relationship or hold a public role that affects how peers interpret their contribution. Where such interests are materially relevant to Nexus work, appropriate disclosure can improve institutional understanding even where recusal is unnecessary. The purpose is contextual clarity. NLS should neither ignore significant related interests nor create a surveillance model in which every professional relationship becomes part of an institutional file. *** #### 19.4.2 Related interests can create positive capability An overlapping relationship is not only a source of risk. It may also explain why the member is uniquely capable of helping the Council understand a system. A leader with experience across government and industry may see dependencies others miss. A university leader participating in an emerging research network may bring valuable scientific context. A finance professional may understand how a programme is likely to be interpreted by capital markets. The integrity architecture should therefore preserve the positive informational value of related interests while remaining capable of managing situations where the same relationship affects impartial institutional judgment. *** #### 19.4.3 Changes in circumstances should update the integrity context Professional roles change. A member may join a supplier, enter public office, become a director of another institution, accept a separate Nexus assignment or develop another relationship materially relevant to current work. The integrity context should evolve accordingly. NLS should not assume that a disclosure made at admission remains sufficient several years later. Annual review and significant changes in circumstance provide natural points for updating relevant information. This keeps integrity architecture connected to current reality rather than historical assumptions. *** ### 19.5 Anti-Capture #### 19.5.1 Capture can occur without formal transfer of control We use **anti-capture** as a structural principle because institutions can lose independence without any formal document transferring authority. A large funder can shape the agenda through repeated dependence. A technology provider can become so operationally central that alternatives become unrealistic. A founding institution can dominate interpretation of the architecture. A small group of leaders can control opportunity routing because everyone else depends on their networks. These patterns may develop gradually and without malicious intent. Anti-capture therefore asks whether the system remains capable of independent judgment despite asymmetries in money, technology, access, reputation or institutional position. *** #### 19.5.2 Economic support does not purchase constitutional control Nexus requires resources to operate. Members, institutions, sponsors, partners and funders may provide substantial support. That support should not purchase Council authority, Board status, research conclusions, procurement preference, technology preference, public-sector influence or control over evidence. The public-good integrity of Nexus depends on maintaining this separation. The principle remains: > **Support the arena. Never buy the outcome.** Economic contribution can strengthen the institution. It should not silently rewrite who governs it or what its evidence is allowed to conclude. *** #### 19.5.3 Technology centrality should not become governance centrality A technology provider may become deeply important to Foundry, Nexus Universe or another operating environment. Technical importance should not create control over Council priorities, institutional findings or future sourcing decisions by implication. The same applies to hosting, data infrastructure, compute or other operating capability. We should preserve enough architectural portability, documented dependency and institutional visibility that operational centrality can be understood and managed. The stronger a dependency becomes, the more important it is that the institution recognizes it explicitly rather than allowing technological convenience to become hidden governance. *** #### 19.5.4 Founder influence should evolve into institutional capability Founders may carry disproportionate knowledge, relationships and legitimacy during early formation. This can be necessary. The long-term system should nevertheless become less dependent on personal founder influence as institutions mature. Records should replace private memory. Councils should develop independent leadership depth. Desks should preserve operating continuity. Successors should understand the architecture. Opportunity routing should extend beyond founder networks. Anti-capture therefore applies even to benevolent founding influence. Institutionalization requires the system eventually to become stronger than its founders. *** #### 19.5.5 Capture risk should be examined at National, Regional and Global levels A National Nexus may become dependent on one government relationship or enterprise. A Regional architecture may become dominated by its largest country. A Global Council may become disproportionately shaped by the institutions with the greatest resources or visibility. Anti-capture therefore belongs at every scale. The relevant safeguards may differ, but the central question remains the same: **Can the system still exercise independent, evidence-informed judgment when an influential participant strongly prefers a particular outcome?** If the answer becomes increasingly uncertain, the architecture requires correction. *** ### 19.6 Public-Institution Engagement #### 19.6.1 Engagement with public institutions should be substantive and precise Government ministries, public agencies, municipalities, regulators, international organizations and other public institutions are essential participants in systemic-risk and readiness work. NLS leaders may engage these institutions through Council activity, Working Groups, technical assistance, research, Nexus Universe, National Nexus formation or other legitimate pathways. These relationships should be represented accurately. A meeting is a meeting. A dialogue is a dialogue. Participation is participation. Technical assistance is technical assistance. A formal institutional relationship should be described as such only where the relevant institutions have actually created it. Precision protects both Nexus and the public institution involved. *** #### 19.6.2 Individual participation does not create government mandate A public official may participate in a Leadership Council, Working Group or Nexus Universe environment in an individual, professional or formally institutional capacity depending on the circumstances. NLS should not infer a wider government mandate merely from the person's position. Likewise, a former public official may contribute significant expertise without representing their former institution. The active capacity matters. This protects the system from accidental claims of public endorsement and allows public-sector leaders to contribute within legitimate boundaries. *** #### 19.6.3 Nexus leadership does not create public authority A National Leadership Council may include highly influential leaders and maintain serious relationships with public institutions. The Council does not thereby become a public authority. It can provide evidence, systems intelligence, strategic challenge, institutional coordination and readiness support. Public decisions remain with the institutions legitimately responsible for them. This distinction should remain visible especially where Nexus work concerns public policy, public infrastructure, emergency management, regulated systems or sovereign capability. Influence and usefulness should never be represented as statutory authority. *** #### 19.6.4 Public engagement should avoid implied endorsement The participation of a public institution in one Nexus activity should not be generalized into endorsement of the entire Nexus architecture, a technology, a supplier, a Council position or another programme. The same applies to international institutions, universities, enterprises and other participants. Institutional engagement is often bounded. Public communication should preserve those boundaries. This discipline can initially appear conservative, but it creates stronger long-term credibility because external institutions can engage Nexus without fear that limited participation will be transformed into expansive public claims. *** #### 19.6.5 Public-institution relationships should become institutional rather than personal where appropriate Senior leaders often open important public-sector relationships through personal networks. Where the relationship becomes material to the National Nexus or another persistent programme, it should progressively acquire institutional continuity through the relevant Desk, programme team or institutional interface. This reduces dependency on one leader's access and makes the relationship more resilient to professional transition. Personal trust may open the door. Institutional capability should sustain the work. *** ### 19.7 Competition and Fairness #### 19.7.1 Leadership networks should not become closed opportunity networks NLS intentionally creates strong peer relationships. Those relationships can accelerate institutional work, but they can also create a risk that opportunities, recognition and influence circulate disproportionately among people already closest to the centre. We therefore treat fairness as an architectural concern. Members should be capable of understanding that substantive contribution, capability and fit matter more than social proximity to founders, Chairs or operating teams. This does not require every opportunity to be open to everyone. It requires the process to remain connected to legitimate institutional purpose rather than favoritism. *** #### 19.7.2 Similar situations should be treated through similar principles No two leaders or programmes are identical. NLS should nevertheless seek consistency in the principles applied to comparable situations. A prominent Global leader should not receive materially different conflict treatment from a less visible National member merely because of status. A founder's professional assignment should not be exempt from the separation between Council membership and professional work. A sponsor should not receive privileges unavailable to another participant where the underlying institutional basis is the same. Consistency creates trust. Absolute uniformity is unnecessary. Comparable principle is essential. *** #### 19.7.3 Fairness includes access to institutional process A member affected materially by a decision should ordinarily be able to understand the process through which the relevant state was reached at a level appropriate to the context. This may concern a Council-office decision, an opportunity pathway, contribution verification, a conduct matter or another institutional process. Fairness does not require disclosure of every internal deliberation or another person's protected information. It does require enough procedural intelligibility that NLS does not become an opaque system in which important states simply appear without understandable institutional basis. *** #### 19.7.4 Competition should not undermine collaboration Some Nexus opportunities may require competitive selection. The wider Leadership System remains collaborative. Members should therefore be able to compete legitimately for a particular assignment without turning the Council itself into a continuous competitive marketplace. The institution should make clear when members are peers contributing collectively and when they are candidates in a specific selection process. This capacity separation reduces the risk that professional competition contaminates ordinary Council trust. *** ### 19.8 Procurement Neutrality #### 19.8.1 Council participation does not create procurement preference NLS should not be used as a pathway through which members, their employers or associated providers receive automatic preference for technology, services or programme opportunities. A member's expertise may make their organization highly relevant to a need. The appropriate sourcing or procurement process should still determine whether and how that provider participates where such a process applies. This protects the Council from becoming a commercial access mechanism. It also protects legitimate providers by ensuring that their selection can be defended on substantive grounds rather than perceived insider status. *** #### 19.8.2 Technical contribution and provider selection are different processes A technology leader may contribute valuable expertise to a Working Group or help the Council understand a capability category. That intellectual contribution should not automatically position their company as the preferred provider. Where provider selection later occurs, the institution should distinguish the earlier knowledge contribution from the subsequent commercial or implementation decision. In some cases, the leader may continue contributing appropriately. In others, additional separation or recusal may be useful. The objective is not to exclude vendors from systems leadership. It is to prevent expertise from becoming an unexamined pathway to commercial preference. *** #### 19.8.3 Nexus architecture should remain provider-neutral where appropriate Foundry, Universe and other Nexus environments may integrate technology from multiple providers. The architecture should seek interoperability and modularity where these qualities strengthen resilience, National choice and institutional independence. Provider neutrality does not mean every technology is equally suitable. It means the institutional architecture is not designed so that participation by one provider predetermines all subsequent technical choices. Evidence, operational requirements, National context and programme needs should guide selection. *** #### 19.8.4 Public procurement retains its own institutional process Where a National government or public institution is responsible for procurement, Nexus participation does not replace or supersede that institution's applicable process. NLS may help clarify requirements, evidence, system dependencies or programme readiness. The public institution retains the responsibility belonging to it. A Nexus Council Member, supplier, sponsor or programme participant should not imply that engagement within Nexus creates public procurement preference. This is an important boundary between readiness support and public decision-making. *** ### 19.9 Specialized Institutional Interfaces #### 19.9.1 Specialized domains require domain-specific integrity Some Nexus interfaces carry additional complexity because they operate near specialized financial, technical, scientific, security or regulated systems. The Leadership System should therefore avoid assuming that one generic integrity rule is sufficient for every domain. The common principles remain evidence, role clarity, institutional responsibility and truthful claims. The application may become more specific according to the field. A finance-readiness discussion creates different risks from a research peer review. Cybersecurity work creates different information conditions from a public convening. Technical certification, where applicable, differs from Nexus testing. Institutional literacy requires these differences to remain visible. *** #### 19.9.2 Finance-readiness should not be represented as finance GRA and relevant Nexus programmes may help make physical risks, projects or institutional needs more intelligible to financial systems. This may include protection-gap analysis, programme readiness, risk evidence, fiscal-risk understanding or other finance-readiness functions. Such work does not automatically create financing, investment approval, underwriting or another regulated financial outcome. Leadership communications should preserve the distinction. A programme can become significantly more finance-ready without having secured finance. Accuracy here protects institutions from turning readiness support into an implied promise of capital. *** #### 19.9.3 Insurance-readiness should not be represented as underwriting The same distinction applies to insurance-related work. Nexus may help institutions understand risk, exposure, resilience, protection gaps or evidence relevant to insurance-readiness. This does not mean Nexus itself has underwritten the risk, created coverage or guaranteed insurability. Where actual insurance decisions are involved, the relevant competent actors retain their responsibilities. NLS leaders should therefore use language proportionate to the institutional function being performed. *** #### 19.9.4 Testing should not be represented as certification Labs and Nexus Universe may provide sophisticated testing environments. A successful test can generate important evidence. It does not automatically create certification, regulatory approval or another externally authoritative state unless a separate competent mechanism explicitly provides that consequence. This distinction is particularly important where technologies, infrastructure or methods enter regulated environments. Testing demonstrates what the evidence supports. Certification, authorization or approval belong to the institutions competent to create those states. *** #### 19.9.5 Research participation should preserve scholarly and evidentiary independence Research supported through Nexus should remain capable of producing findings inconvenient to sponsors, members or programme advocates. Authorship should follow contribution. Methodological limitations should remain visible. Negative and inconclusive evidence should be preservable. The integrity of Nexus research depends substantially on whether its processes can distinguish institutional support from intellectual control. Public-good knowledge loses value quickly when readers cannot trust that conclusions were allowed to follow evidence. *** ### 19.10 Cross-Border Leadership #### 19.10.1 Cross-border leadership requires contextual humility Regional and Global leaders may contribute across countries whose institutional, cultural, economic and political environments differ significantly from their own. Expertise should therefore travel with humility. A method successful in one country may require substantial adaptation elsewhere. A leader familiar with one legal or institutional system should not assume that similar-looking structures function identically in another jurisdiction. NLS should use cross-border leadership to increase comparative intelligence, not to export certainty. The leader's role is strongest when they combine transferable expertise with serious respect for local context. *** #### 19.10.2 National ownership remains relevant to external leadership contribution A Regional or Global leader supporting a National Nexus should strengthen the country's own capability. Their contribution should not displace National leaders from understanding or owning the programme merely because the external contributor possesses greater international visibility. Where possible, cross-border work should build domestic capability, document methods, support successor leadership and connect with the National Desk and Portfolio. The objective is contribution to a stronger National system. External expertise becomes most valuable when it reduces long-term dependency. *** #### 19.10.3 Cross-border participation does not create representation of the country A member's work in another country does not make them a representative of that government, National Council or population unless the relevant institutional relationship explicitly establishes such a capacity. The same applies to participation in Regional or Global environments. A leader may provide comparative expertise without speaking for the country from which they come. NLS should preserve this distinction carefully because international work can easily generate representational assumptions that the underlying institutional facts do not support. *** #### 19.10.4 Protected and context-sensitive knowledge deserves care Cross-border work may involve Indigenous knowledge, community knowledge, sensitive environmental information, critical-infrastructure details, security-relevant information or other forms of knowledge that should not move freely merely because they are useful to a Regional or Global programme. The federation should respect legitimate restrictions, context and appropriate stewardship. Interoperability is not unrestricted extraction. A credible Global system should become better at connecting knowledge without assuming that all knowledge should become globally centralized. *** ### 19.11 Public Claims and Representation #### 19.11.1 Public representation should follow actual institutional state Leadership titles, public profiles, presentations, event descriptions and external communications should reflect the role the member actually holds. A Council Member should not be represented as a director unless a valid Board appointment exists. A former Chair should not continue appearing as current Chair. A professional adviser should not be represented as an executive unless that capacity exists. The credibility of the Leadership System depends partly on disciplined titles. Precision in representation is not cosmetic. It is a visible expression of institutional integrity. *** #### 19.11.2 Members should distinguish personal, professional and Nexus views Senior leaders frequently speak through several legitimate identities. A public statement may reflect the member's personal analysis, the position of their employer, their role as a Nexus Leadership Council Member or a formally authorized Nexus institutional position. These are not automatically identical. Where the context could create confusion, members should use enough clarity that audiences can understand the capacity in which the statement is being made. This protects both the member's independence and the institutions with which they are affiliated. *** #### 19.11.3 Nexus affiliation should not be used to imply unsupported endorsement A member may appropriately describe their NLS role. That title should not be used to imply that Nexus endorses an external product, political position, investment, commercial service or other proposition merely because the individual supports it. Likewise, external organizations should not infer institutional endorsement from the presence of a Nexus leader unless the relevant Nexus institution has actually established that position. Leadership affiliation creates identity and contribution context. It is not an unrestricted endorsement instrument. *** #### 19.11.4 Corrections should be made when public claims become materially inaccurate Public information can become outdated or overstated. Where a material Nexus claim is inaccurate, the responsible institution or member should support appropriate correction. The objective is not perfection in every minor communication. It is to ensure that material errors concerning role, institutional relationship, evidence, adoption or authority do not remain active after the institution knows they are wrong. Correction strengthens credibility when handled promptly and proportionately. *** ### 19.12 Confidentiality and Information Stewardship #### 19.12.1 Access to information creates stewardship responsibility Leadership Council Members may encounter information not available publicly. This can include early-stage programme ideas, institutional relationships, Council deliberations, member information, research, technical material, National context or other sensitive information. Access should be understood as stewardship rather than ownership. The member receives information for a legitimate institutional purpose. They should use it within that purpose and the relevant information conditions. This principle allows NLS to support serious substantive work without requiring every environment to become public. *** #### 19.12.2 Confidentiality should not be used to conceal legitimate institutional concerns Confidentiality protects sensitive information. It should not become a device through which legitimate concerns about integrity, misconduct, safety or institutional risk are suppressed. The NLS concern and review pathways should provide appropriate mechanisms through which a member can raise a serious issue without being told that the mere existence of confidentiality prevents institutional examination. This balance matters. Strong institutions protect sensitive information and remain capable of hearing necessary concerns. *** #### 19.12.3 Information obtained through one capacity should not migrate automatically into another A leader participating across several institutions may lawfully possess information through multiple roles. They should not assume that information received in one capacity can be introduced freely into another. A Board-restricted matter should not be moved into ordinary Council discussion merely because the same person participates in both. Proprietary professional information should not become Working Group material without an appropriate basis. Multiple capacities increase the need for information discipline. The person is a bridge. They should not become an uncontrolled conduit. *** #### 19.12.4 Institutional need should guide information sharing The strongest rule is not secrecy for its own sake. It is purposeful information stewardship. NLS should share enough information for leaders to perform their roles well, while protecting information whose wider distribution would create unnecessary risk, violate legitimate expectations or undermine another institution's responsibilities. As established in Part XVIII, access should follow active capacity and institutional purpose. Information integrity depends as much on **why information is being used** as on whether the person can technically access it. *** ### 19.13 Responsible Advanced Technology #### 19.13.1 Frontier capability requires stronger institutional judgment, not weaker judgment Nexus engages advanced technologies because systemic-risk and readiness challenges increasingly depend on AI, geospatial intelligence, digital twins, sensors, automation, sovereign compute, cybersecurity and other rapidly evolving capabilities. Technological sophistication should not reduce the rigor of institutional judgment. The fact that a system can perform a function does not establish that it should be used in every context. NLS leaders should examine purpose, evidence, reliability, security, human consequence, institutional dependence and appropriate oversight alongside performance. Responsible innovation therefore begins from the system the technology enters, not the novelty of the technology itself. *** #### 19.13.2 AI should augment leadership without becoming institutional authority AI can summarize evidence, support research, identify dependencies, assist scenario design, compare options, prepare briefs and make leadership information more usable. It should not autonomously determine consequential leadership states. AI should not appoint Council officers, verify material self-claims, clear conflicts, select formal governors, award professional assignments, authorize representation or convert a test result into institutional adoption. These are human institutional judgments. AI may help leaders see more. It should not silently become the institution that decides. *** #### 19.13.3 Data quality and provenance affect technological integrity Advanced systems can create highly persuasive outputs from weak or incomplete inputs. Leaders should therefore remain attentive to provenance, temporal relevance, geographic applicability, uncertainty, model limitations and missing data. A visually sophisticated dashboard is not necessarily stronger evidence. A confident model output is not necessarily an authoritative conclusion. Nexus technology should help preserve these limitations visibly where they affect interpretation. Responsible technology requires **epistemic humility built into the operating environment**. *** #### 19.13.4 Testing environments should preserve outcome ceilings Frontier technology often performs impressively in demonstrations. NLS should maintain the distinctions established in Nexus Universe between prototype, simulation, test, validation, production readiness, deployment and institutionalization. Leaders should resist promotional pressure to collapse these states. A successful test establishes only what the conditions and evidence support. This discipline is especially important when technology providers, investors, governments or public audiences are highly interested in rapid deployment. Institutional excitement should not outrun evidence. *** #### 19.13.5 Responsible innovation includes the ability to stop Innovation culture often rewards movement. Leadership integrity also requires the ability to say **not yet**, **not in this form**, or **not here**. A proposition may require stronger safeguards. The data may be insufficient. The National infrastructure may be unready. The social consequence may be poorly understood. A dependency may create unacceptable concentration. Stopping or redesigning a technology pathway can therefore represent mature leadership. NLS should not define innovation success as uninterrupted acceleration. *** ### 19.14 Communities, Rights and Protected Knowledge #### 19.14.1 Systemic-risk leadership should understand affected people as part of the system Infrastructure, technology, climate, resource, health and economic programmes affect people differently. NLS should therefore avoid designing systemic interventions solely from institutional or technical abstraction. Communities may possess knowledge about local systems, vulnerabilities, implementation realities and consequences that are invisible at National or Global level. Where materially relevant, leadership architecture should create appropriate pathways through which those perspectives can inform the work. This is not merely an engagement exercise. It can materially improve evidence and institutional design. *** #### 19.14.2 Participation and consent are different institutional states The presence of community representatives, rightsholders or affected groups in a workshop, Working Group or Nexus Universe activity should not be represented automatically as consent to the resulting programme. Participation demonstrates participation. Consultation demonstrates consultation. Consent, where relevant, is a distinct institutional condition requiring whatever process legitimately establishes it. NLS should preserve these distinctions in the same way it distinguishes dialogue from partnership or testing from adoption. Accurate state matters especially where power asymmetries are significant. *** #### 19.14.3 Rights considerations should influence design early Where a programme may materially affect rights, communities, personal data, access to essential services or other protected interests, those considerations should enter early enough to shape the proposition. Safeguards added only after technical or programme design is complete may be less effective. Leadership integrity therefore includes the ability to identify where a wider systems intervention has human consequences not visible through operational metrics alone. Public-Private-Planet should remain connected to people as well as institutions and physical systems. *** #### 19.14.4 Protected knowledge should not be treated as open institutional input by default Certain knowledge may be culturally protected, community-governed, security-sensitive, proprietary or otherwise inappropriate for unrestricted reuse. NLS should not assume that information shared for one bounded purpose automatically becomes available for broader research, technology development, AI training, federation or publication. The terms under which knowledge enters the system matter. Responsible knowledge stewardship requires attention to **source, purpose, permission, attribution and continued context**. *** #### 19.14.5 Community engagement should avoid extractive participation Nexus should not repeatedly seek knowledge from communities while leaving no visible capability, feedback, benefit or institutional continuity behind. Where sustained engagement is material to the work, the relationship should become reciprocal enough that participation is not experienced merely as extraction into an external programme. The form of reciprocity will vary by context. The underlying integrity principle remains that affected people should not be treated simply as data sources for systems designed elsewhere. *** ### 19.15 Concerns and Grievances #### 19.15.1 Members need a credible pathway for raising concerns A Leadership System cannot depend on everyone feeling comfortable with every institutional decision. Members should have an identifiable route through which they can raise concerns about conduct, conflicts, representation, information use, unfair treatment, institutional process or another material NLS matter. The existence of such a pathway improves institutional intelligence. Leaders frequently see issues from different positions in the system. A concern that initially appears individual may reveal a wider architectural weakness. NLS should therefore treat concerns as potential sources of institutional learning as well as matters requiring appropriate response. *** #### 19.15.2 Concerns should be raised through the most appropriate level Not every disagreement requires formal escalation. Many issues can be resolved through direct clarification, the Council Chair, Desk, Secretariat or another relevant operating interface. More significant matters may require a separate integrity or governance review route. The system should encourage proportionate resolution while ensuring that members are not trapped within the same reporting relationship where the concern itself involves that relationship. A credible architecture needs **more than one route where necessary**. *** #### 19.15.3 Raising a concern should not create automatic retaliation or stigma Members should be able to raise a good-faith concern without the mere act of doing so becoming evidence that they are difficult, disloyal or unsuitable for future participation. This is particularly important in a senior leadership environment where informal reputation can have significant effect. The concern may ultimately prove unsupported. The institution should distinguish the content and manner of the concern from the legitimate use of the process itself. A system that discourages concerns through social penalty will eventually lose access to important information. *** #### 19.15.4 Concerns should be specific enough to examine A concern becomes easier to address when the member can identify the issue, relevant context, affected process, available evidence and the outcome or clarification being sought. NLS should support members in framing concerns without requiring legalistic precision. The objective is to move from generalized dissatisfaction toward an issue the institution can understand and respond to. Where important evidence remains unavailable, the concern can still be raised. The institution should distinguish lack of complete proof from lack of legitimacy to ask the question. *** #### 19.15.5 Confidentiality should be proportionate to the process Concern processes may involve sensitive information. NLS should manage that information carefully while avoiding absolute promises that could prevent fair review or necessary institutional response. The people involved should understand that information may need to be shared with those responsible for examining or resolving the matter. The objective is responsible handling, not secrecy that makes resolution impossible. *** ### 19.16 Conduct #### 19.16.1 Seniority increases responsibility for institutional conduct NLS brings together accomplished people who are accustomed to influence and autonomy. Council membership requires those capabilities to operate within a collegial institutional environment. Members should therefore engage peers respectfully, challenge ideas seriously, protect sensitive information, avoid misrepresenting roles, contribute in good faith and recognize that professional prominence does not entitle one person to dominate others. These expectations are not etiquette for its own sake. They create the interpersonal conditions through which plural systems leadership becomes possible. *** #### 19.16.2 Constructive challenge is expected Integrity does not require politeness that suppresses substantive disagreement. NLS expects leaders to question assumptions, challenge weak evidence, identify institutional risk and disagree where necessary. The standard concerns how that challenge is exercised. Serious critique should remain focused on the issue, evidence and institutional consequence rather than humiliation, intimidation or personalized attacks. A Council incapable of challenge will become intellectually weak. A Council incapable of respectful challenge will become institutionally unstable. NLS requires both rigor and professionalism. *** #### 19.16.3 Members should not exploit Nexus relationships improperly Leadership relationships created through NLS should be treated responsibly. Members may develop legitimate professional opportunities, partnerships, research collaborations and personal relationships through the network. They should not use Council access as a mechanism for coercive solicitation, unsupported claims of Nexus endorsement, misuse of confidential information or conduct inconsistent with the trust placed in the leadership environment. The Council is designed to create useful relationships. Integrity ensures that those relationships remain relationships others can enter without unreasonable institutional risk. *** #### 19.16.4 Conduct expectations apply across digital and physical environments The same principles apply in meetings, Working Groups, Foundry, messaging environments, Nexus Universe, institutional travel and other NLS contexts. Digital communication does not reduce the standard merely because interactions are less formal. Records can travel quickly, context can disappear and misunderstandings can amplify. Members should therefore use the same institutional judgment across communication channels. The platform may change. The leadership responsibility does not. *** #### 19.16.5 Repeated low-level conduct issues can become system-relevant One minor interaction may not justify formal intervention. Repeated behavior can nevertheless undermine participation, trust and institutional effectiveness. The integrity architecture should therefore be capable of identifying patterns without treating every isolated issue as severe misconduct. This allows NLS to respond proportionately while avoiding a situation in which significant cultural problems remain invisible because each individual event appears too small to matter on its own. Leadership culture is created cumulatively. Conduct review should understand cumulative effects. *** ### 19.17 Review and Reconsideration #### 19.17.1 Material integrity decisions should be capable of review Human institutional judgment can be mistaken. Where an integrity decision materially affects a member's standing, office, access, pathway or participation, NLS should provide an appropriate mechanism through which the relevant decision can be reconsidered where new information, procedural error or another legitimate basis exists. This does not mean every routine decision requires a formal appeal structure. The degree of review should follow consequence. A correctable system is more credible than one in which the first institutional judgment becomes permanently unchallengeable regardless of later evidence. *** #### 19.17.2 Reconsideration is not automatic reversal A request for review reopens examination of the relevant issue at the appropriate level. It does not create a presumption that the original decision was wrong. The institution may confirm, modify or reverse the earlier conclusion according to the information and process available. This distinction protects the integrity of both the original process and the reconsideration pathway. Review should be meaningful without becoming an endless loop through which no institutional state can ever settle. *** #### 19.17.3 New evidence should matter One of the strongest bases for reconsideration is material evidence that was unavailable or not properly understood during the original process. NLS should remain capable of correcting itself when the underlying factual picture changes. The same principle applies throughout the Leadership System. Contribution records can be corrected. Governance states can change. Programme evidence can alter maturity. Integrity findings should likewise remain responsive to better information. Institutional consistency means applying correction across domains, not only where the result is convenient. *** #### 19.17.4 Review should preserve appropriate independence Where the original concern involves the person or function that would normally review it, another appropriate institutional route should be available. This is especially important in small or early-stage systems where several responsibilities may initially sit close together. The objective is not to create a large adjudicative bureaucracy. It is to prevent the integrity process from becoming structurally circular. No person should be expected to provide the only meaningful review of a consequential complaint about their own conduct or decision. *** ### 19.18 Fair Process #### 19.18.1 Fairness begins with knowing what issue is being considered Where a material conduct or integrity matter concerns a member, the person should ordinarily understand the substance of the issue sufficiently to respond meaningfully. This does not require disclosure of information that legitimately must remain protected. It does require avoiding opaque processes in which a member is materially affected by conclusions they cannot understand at all. Procedural clarity protects the individual and improves institutional decision quality because relevant context has a better chance of being heard. *** #### 19.18.2 Opportunity to respond is part of serious review Where a consequential conclusion may be reached about a member's conduct, standing or integrity, the process should ordinarily allow the member an appropriate opportunity to provide relevant context or evidence. The purpose is not adversarial formalism. It is to reduce avoidable error. Senior leadership environments are complex, and apparently problematic conduct may look different once the relevant institutional context is understood. A fair process gives the institution a stronger factual basis before creating a consequential state. *** #### 19.18.3 Decisions should follow the evidence and institutional consequence The seriousness of the response should reflect the seriousness of the issue. Possible institutional responses may range from clarification and guidance through disclosure, recusal, role adjustment, correction, pathway change, standing review or other proportionate action appropriate to the circumstances. NLS should resist both extremes: trivializing material integrity problems and escalating minor issues into unnecessarily severe institutional responses. The objective is correction, protection of the system and preservation of credible leadership. Punishment for its own sake is not the organizing purpose. *** #### 19.18.4 Similar cases should be informed by common principles while preserving context Fairness requires enough consistency that members can trust the system. It also requires enough judgment that materially different situations are not forced into identical outcomes merely because they share one surface feature. NLS should therefore use common principles, institutional records and prior learning to improve consistency while allowing contextual distinctions where they are genuinely relevant. This is the same balance applied throughout the wider architecture: **common grammar, contextual judgment**. *** #### 19.18.5 Records should be proportionate and accurate Material integrity processes may require institutional records. Those records should contain enough information to preserve the relevant decision and future institutional context without accumulating unnecessary personal detail. Where a finding is later corrected, the current institutional state should update appropriately while significant history remains available where legitimately required. Records should serve institutional memory. They should not become repositories of indefinite reputational punishment. *** #### 19.18.6 Fair process protects the institution as well as the member A transparent and proportionate integrity process is not merely a benefit granted to individuals. It improves the institution itself. It reduces decisions driven by rumor, hierarchy, convenience or personal relationships. It creates a stronger record. It improves consistency. It makes correction easier. It reduces the likelihood that difficult issues are handled through informal exclusion or reputational signaling instead of institutional process. Fairness is therefore a systems-control function. It allows a federation built on trust to respond credibly when trust is tested. *** #### 19.18.7 The leadership integrity proposition The full NLS integrity architecture can therefore be expressed as: > **Identify relevant interests → establish active capacity → disclose material context → manage proportionately → preserve competition and institutional independence → protect information and affected people → allow concerns to surface → review evidence fairly → correct where required → return learning to the system** The objective is not to create a leadership environment free from complexity. Such an environment would be impossible and probably undesirable. The objective is to build a system sophisticated enough that complexity does not quietly become capture, favoritism, authority leakage, misrepresentation or institutional distrust. Integrity is what allows Nexus to use powerful networks without becoming controlled by them. *** ## PART XIX FRAMEWORK PRINCIPLES **Complexity with transparency.** We expect senior leaders to bring substantial professional relationships, institutional affiliations and interests into NLS. These connections create value as well as risk. Our integrity architecture therefore seeks enough visibility to manage material conflicts intelligently without treating every external relationship as disqualifying. Disclosure, recusal and role adjustment are tools for preserving contribution and institutional trust, not presumptions of misconduct. **Independence without isolation.** Nexus depends on governments, enterprises, universities, communities, funders, providers, researchers and financial institutions. Deep engagement with these actors is compatible with institutional independence when roles remain clear, economic support does not buy outcomes, technology centrality does not become governance centrality, and National, Regional and Global systems retain the ability to exercise evidence-informed judgment even where powerful participants prefer a particular result. **Fairness before favoritism.** Council standing, founder status, prestige, sponsorship, professional proximity and economic contribution should never operate as hidden currencies through which members acquire Council authority, procurement preference, professional assignments, Board pathways or disproportionate influence. Similar situations should be governed by common principles, while opportunity, sourcing and selection remain connected to real institutional need and substantive fit. **Truthful representation and responsible technology.** We preserve distinctions among meeting, participation, collaboration, endorsement, testing, validation, adoption, certification, finance-readiness, financing, insurance-readiness and underwriting. The same discipline applies to advanced technology. AI and other frontier systems may augment analysis and leadership, but they do not become institutional authority merely because their outputs are sophisticated or persuasive. **Rights, concerns and fair process.** Public-interest leadership requires attention to communities, affected people, legitimate rights, protected knowledge and the ability of participants to raise concerns without unnecessary retaliation or stigma. Integrity decisions should be proportionate, sufficiently intelligible, responsive to evidence and capable of appropriate review. A trustworthy institution protects sensitive information while remaining capable of correcting itself when stronger evidence emerges. *** ## OPERATING RELATIONSHIP Part XIX establishes the integrity architecture required for the complex leadership relationships defined throughout Parts XIV through XVIII to remain credible. NLS intentionally convenes leaders who possess multiple affiliations, significant professional responsibilities and substantial institutional influence. Rather than attempting to eliminate that complexity, we make it governable. Material conflicts can be disclosed. Recusal can be scoped to the relevant matter. Related interests can provide useful context. Multiple capacities can remain visible. Institutional records can preserve how consequential integrity decisions were handled. The architecture also protects Nexus from **capture**. Funding, sponsorship, technology, hosting, prestige, founder status and institutional access can all create asymmetries of influence. None should silently become constitutional control. Economic contribution does not buy governance. Technology centrality does not buy institutional authority. Council membership does not create procurement preference. Public-institution engagement does not create public mandate. The same discipline extends into specialized interfaces. Finance-readiness remains distinct from finance. Insurance-readiness remains distinct from underwriting. Nexus testing remains distinct from certification or regulatory approval. Research support remains distinct from control over findings. Participation remains distinct from consent, and community engagement should not be treated as permission to extract protected knowledge into wider programmes without an appropriate basis. Leadership integrity also requires accurate public representation. Titles should correspond to actual institutional states. A Council office is not a Board office. A dialogue is not a partnership. An introduction is not institutional adoption. A member's external position does not automatically make them a representative of that external institution within Nexus. Advanced technology adds another integrity layer. Foundry, AI and other Nexus capabilities may support evidence synthesis, scenario analysis, risk intelligence and leadership work. They should not replace the competent human institution in consequential decisions involving Council office, governance, opportunity selection, conflict management, representation or other leadership states. Finally, NLS provides pathways through which concerns and conduct questions can be raised, reviewed and corrected proportionately. Integrity is not credible if it exists only as a set of expectations for members while the institution itself is unable to examine its own processes. Fairness, reconsideration and correctable records are therefore part of system integrity. The governing proposition of Part XIX is: > **Nexus integrity does not depend on pretending that powerful leaders have no interests, relationships or competing responsibilities. It depends on making those realities sufficiently visible and governable that contribution can remain deep while evidence, institutional independence, fair participation and public-interest purpose remain credible.** ## NEXT ## PART XX: INFORMATION, PRIVACY, KNOWLEDGE AND PUBLIC REPRESENTATION ### Personal and Institutional Information, Leadership Profiles, Council and Working Group Records, Restricted Information, Cross-Border Data, Knowledge and Intellectual Contribution, Attribution, Public-Good Knowledge and Corrections Part XX will establish how NLS handles information across the full leadership lifecycle. It will define the distinction among personal information, professional and institutional information, Leadership Ledger data, Council records, Working Group material, restricted information and public profiles; establish principles for access, retention, cross-border information and responsible digital use; define how existing intellectual contributions, collaboratively developed knowledge and attribution should be handled; distinguish public-good knowledge from restricted or proprietary material; and establish the relationship between one governed institutional record and the several member, Council, operational and public views through which that record may legitimately be represented. ## 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/xix.-leadership-integrity.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.