> 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/xx.-information-governance.md). # XX. Information Governance Information governance for the Nexus Leadership System, covering data privacy, knowledge governance, public representation, attribution, restricted information and institutional memory. **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.** This framework defines information governance, data privacy, knowledge governance and public representation across the Nexus Leadership System. 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 %} ## 20. INFORMATION, PRIVACY, KNOWLEDGE AND PUBLIC REPRESENTATION This framework defines information governance, data privacy, knowledge governance and public representation across the Nexus Leadership System. ### 20.1 Information Governance #### 20.1.1 Information is part of the operating infrastructure of NLS We treat information as institutional infrastructure. The Leadership System cannot function coherently without maintaining information about members, Councils, Plans, contributions, Working Groups, institutional relationships, opportunities, evidence, governance states, annual reviews and the wider operating history through which leadership becomes cumulative. The relevant question is therefore not whether NLS should hold information. It is **which information is required, for what institutional purpose, under whose responsibility, for how long, and through which governed views it should become visible**. This purpose-based approach allows us to create a useful leadership system without assuming that every piece of information should become universally accessible simply because it exists. *** #### 20.1.2 Information governance follows institutional purpose Information should be collected, maintained and shared according to a legitimate purpose within the Nexus Leadership System. A member's professional biography may support selection, Council composition and public representation. Their Annual Leadership Contribution Plan may support leadership development and programme design. Contribution evidence may support verification and annual review. Information concerning a separate professional assignment may support programme administration. These objects have different purposes. They should not automatically acquire identical access, retention or public visibility merely because they relate to the same person. Information governance therefore begins with context. The system should understand **why an information object exists before determining how it should be used**. *** #### 20.1.3 Information architecture should preserve authoritative sources The same factual statement may appear in several environments. A member's Council office may appear in Foundry, the Leadership Ledger, a public profile and an event programme. Their institutional affiliation may appear in internal and public views. A governance appointment may need to be represented in several systems. NLS should avoid turning these projections into independent truths. Where a material fact has a competent owner, that source should remain authoritative and downstream representations should derive from it appropriately. The operating principle remains: > **One fact family → one authoritative owner → many governed projections.** This reduces contradiction and makes correction more reliable. *** #### 20.1.4 Information should remain understandable in context Data without context can create institutional error. A document may be obsolete. A contribution may have been made under a prior capacity. A role may have ended. A claim may remain unverified. A National finding may not generalize across Regions. Important information should therefore retain enough temporal, institutional and evidentiary context for future users to understand what it means. This is especially important because NLS is designed to operate over several annual cycles. Institutional memory becomes misleading when the information survives but the context required to interpret it does not. *** #### 20.1.5 Information governance should support correction A useful information system must be capable of correcting itself. Professional affiliations change. Council offices conclude. public biographies require updating. Contribution attribution may be refined. Evidence may change the interpretation of an earlier claim. NLS should therefore maintain sufficiently coherent source relationships that material corrections can propagate to the relevant views without requiring every representation to be rediscovered and edited independently. Correctability is one of the qualities that distinguishes institutional information from static publication. *** ### 20.2 Personal and Institutional Information #### 20.2.1 Personal information should be proportionate to the leadership relationship NLS requires certain information about the people who participate in it. This may include identity, professional affiliation, contact information, biography, areas of expertise, Council assignment, leadership interests, participation state, Plan information and other details necessary to operate the leadership relationship. We should not treat membership as permission to collect unlimited information merely because additional data might someday become useful. Information should remain proportionate to a legitimate NLS purpose. The fact that technology can collect or infer something does not establish that the Leadership System needs it. This principle becomes increasingly important as Foundry and AI make richer contextualization technically possible. *** #### 20.2.2 Professional context is distinct from private life Senior leaders bring substantial professional identities into NLS. Their institutional roles, professional experience, sector expertise, public responsibilities and relevant organizational affiliations may be directly material to Council composition, contribution and institutional fit. These professional facts should not become a reason to treat unrelated aspects of private life as ordinary institutional information. The Leadership System should preserve a meaningful boundary between **what Nexus needs to understand about the member as an institutional leader and what remains outside the legitimate scope of the leadership relationship**. This supports dignity as well as information discipline. *** #### 20.2.3 Institutional information may concern organizations as well as people NLS also maintains information about participating institutions, programmes, National systems, Working Groups, research environments and external relationships. Such information may include institutional roles, programme context, capabilities, relationships, evidence and operating dependencies. Institutional information should receive the same contextual discipline applied to personal records. The fact that information concerns an organization rather than an individual does not automatically make it public or unrestricted. Certain institutional information may be sensitive because it concerns strategy, infrastructure, early-stage relationships, programme design, technical capability or another legitimate interest. *** #### 20.2.4 Publicly available information does not automatically become unrestricted NLS data Information may already be publicly available through websites, reports or professional profiles. That does not remove the need for contextual accuracy when NLS uses it. A public biography may be outdated. A professional title may have changed. Information published for one purpose may be misleading if reproduced in another context without qualification. NLS should therefore treat public availability as one factor in information handling, not as a substitute for institutional judgment. The objective is accurate and purposeful use. *** #### 20.2.5 Member-submitted information remains subject to institutional context Members should be able to provide and update appropriate information about themselves. The system may accept biographies, areas of expertise, professional changes, contribution claims, interests and other relevant inputs. Submission does not automatically make every item an official NLS fact. Where the information concerns an institutional state such as Council office, governance appointment, contribution verification or other consequential status, the authoritative record should follow the process that legitimately establishes that state. This preserves the distinction between **information supplied by the person and information established by the institution**. *** ### 20.3 Leadership and Public Profiles #### 20.3.1 Public profiles are governed projections, not complete leadership records We establish the public Leadership Profile as a selective, approved representation of the member's NLS relationship. It is not a public copy of the Leadership Ledger. The full leadership record may contain Plan history, internal contribution states, evidence references, institutional relationships, annual review information and other material inappropriate for public disclosure. The public profile should contain only those facts necessary to represent the leader accurately and usefully in the public institutional environment. This creates a disciplined distinction between **institutional memory and public representation**. *** #### 20.3.2 Public profiles should reflect current institutional state A public profile should identify the leader according to roles they actually hold. If the member's Council assignment changes, the public record should change. If a Chair term concludes, the profile should no longer present the individual as current Chair. If the member transitions to Alumni, current representation should reflect that state appropriately. Historical roles may still be described where relevant. They should be described as historical. The public profile should not preserve outdated authority merely because older language appears more prestigious. *** #### 20.3.3 Public biography should distinguish external affiliation from Nexus capacity A member's external professional position may be central to understanding their expertise. The public profile should nevertheless distinguish that affiliation from their Nexus role. A member employed by a major institution should not be represented as though that institution itself has formally joined or endorsed Nexus unless an institutional relationship separately exists. Likewise, the member's Nexus title should not imply that Nexus endorses all external activities associated with the member's professional organization. Clear biography protects both institutions. *** #### 20.3.4 Public contribution statements should follow verified state Where the public profile includes selected contributions, those descriptions should remain proportionate to the evidence and state recorded within NLS. A delivered contribution should not be presented as scaled if the institution has not established scale. A tested proposition should not be represented as implementation. A leader who contributed to a collective initiative should not be presented as sole author or owner unless that is factually correct. Strong contribution does not require exaggerated language. Public credibility increases when claims remain narrower than or equal to the evidence, never stronger than it. *** #### 20.3.5 Public visibility should not determine institutional value Some leaders will have more extensive public profiles because their work is externally visible. Others may create substantial value in research, institutional formation, technical work, mentoring or confidential environments. The public profile should therefore never become the institutional scorecard by which NLS measures contribution. It is one governed projection designed for external understanding. The Leadership Ledger remains the richer longitudinal record. Visibility and value are related in some contexts. They are not the same fact. *** ### 20.4 Council and Working Group Information #### 20.4.1 Councils require spaces for serious institutional work Leadership Councils should be capable of discussing emerging ideas, incomplete evidence, unresolved risks, institutional relationships and dissent without assuming that every contribution immediately becomes a public statement. This requires appropriate Council information environments. The objective is not secrecy. It is to create enough institutional space for leaders to think seriously before propositions have reached a state suitable for wider dissemination. A Council incapable of working with unfinished material will either become superficial or push substantive work into informal channels where institutional memory is weaker. *** #### 20.4.2 Council records should preserve material decisions and learning proportionately Not every remark made in a Council meeting requires permanent detailed preservation. The record should focus on information necessary to maintain institutional continuity: substantive questions, agreed next steps, material dissent where relevant, decisions appropriate to the Council's function, Working Group mandates, significant evidence and other context required for future work. This approach preserves cumulative institutional memory without creating an indiscriminate archive of every conversational exchange. Information governance should support deliberation as well as accountability. *** #### 20.4.3 Working Group information should follow mandate and maturity Working Groups often handle more detailed information than the full Council because their purpose is to develop a bounded question. Their records may include drafts, technical material, evidence, research, institutional mapping and other working information. Visibility should therefore follow the Working Group's mandate and the sensitivity of the material. As the work matures, selected findings may move to the Council, Portfolio, Foundry, Universe, research publication or another appropriate institutional environment. The information should move with enough context that later users understand **what stage of work produced it**. *** #### 20.4.4 Preliminary work should not be represented as final institutional position A draft prepared by a Working Group does not automatically represent the position of the full Leadership Council or another Nexus institution. A discussion paper remains a discussion paper until a legitimate process establishes another state. This distinction is especially important where draft materials circulate digitally beyond their original audience. Information systems and document labels should help preserve maturity and institutional context. The clearer the state of the document, the less likely others are to rely on it incorrectly. *** #### 20.4.5 Dissent can remain part of the institutional record Where disagreement materially affects the meaning of Council or Working Group work, the information architecture should be capable of preserving it. This does not require publishing every difference publicly. It means future institutional users should not inherit a false impression that unanimous certainty existed where material disagreement remained unresolved. Dissent is sometimes part of the knowledge produced by the institution. Preserving it can strengthen later analysis and prevent future teams from repeating questions that earlier participants had already identified. *** ### 20.5 Restricted Information #### 20.5.1 Some information requires bounded access NLS may encounter information whose wider distribution would be inappropriate because it concerns personal matters, institutional strategy, security-sensitive systems, proprietary knowledge, public-sector context, restricted research, technical vulnerabilities, contractual material, Board matters or another legitimate interest. We use **restricted information** as a broad institutional concept rather than assuming all non-public information carries the same sensitivity. Restriction should follow purpose and risk. The objective is not to classify information excessively. It is to recognize when ordinary Council or public access is insufficiently bounded for the information involved. *** #### 20.5.2 Restricted status should preserve purpose A person receiving restricted information should understand the context in which access is being provided. Information shared for one Working Group may not be appropriate for another. Board information may not belong in Council discussion. Technical information provided for a defined assessment may not be reusable in an unrelated research project. This reflects the wider zero-trust doctrine. Access to information for one legitimate purpose does not establish unrestricted permission for every future purpose. *** #### 20.5.3 Restricted information should remain usable by the institution Protection should not make information so difficult to use that legitimate institutional work becomes impossible. The system should seek proportionate handling. Where full records cannot be shared, summaries, aggregated findings, redacted material, restricted workspaces or another suitable mechanism may allow necessary leadership work to proceed while protecting sensitive details. Information governance should therefore be designed around **responsible use**, not merely restriction. A protected fact that can never inform legitimate institutional judgment may have limited operational value. *** #### 20.5.4 Restricted evidence can support a narrower public conclusion A contribution or programme may be supported by evidence that cannot itself become public. NLS should be capable of representing this responsibly. A verified public-safe statement may be possible even where the detailed underlying evidence remains restricted. The public view should not imply that restricted evidence is publicly available, and the internal record should preserve enough provenance that eligible reviewers can understand the basis of the conclusion. This enables evidence-informed public communication without requiring every evidentiary object to be disclosed universally. *** #### 20.5.5 Restricted information should not become informal privilege Access to restricted information can create status. NLS should resist allowing access itself to become a marker of personal prestige or hierarchy. A member should receive sensitive information because they require it for a legitimate function, not because their seniority creates an expectation of universal visibility. This protects both the information and Council culture. Institutional importance should not be measured by how much restricted material a person can access. *** ### 20.6 Cross-Border Information #### 20.6.1 Federation requires information to move across jurisdictions carefully National, Regional and Global leadership necessarily involves information crossing institutional and geographic boundaries. The federation cannot function if every National system remains informationally isolated. Neither should cross-border collaboration imply that all information becomes globally transferable by default. The appropriate architecture should distinguish which information can travel, what level of detail is required, what context should accompany it and whether another form of representation can achieve the same institutional purpose with less unnecessary exposure. Federation depends on **interoperability with discipline**. *** #### 20.6.2 National context should remain attached to cross-border information A National risk finding can change meaning when removed from the conditions in which it was produced. Data quality, institutional arrangements, geography, infrastructure, social conditions and legal context may all affect interpretation. Where National information enters Regional or Global environments, enough context should remain attached that users understand its limitations. The federation should not create global comparability by stripping away the very context required for accurate comparison. Comparability becomes credible when differences remain visible. *** #### 20.6.3 Cross-border sharing should support National ownership Regional and Global systems should strengthen National capability rather than create a permanent flow through which National information is extracted into external systems that the country cannot understand or influence. Where material National information contributes to shared analysis, the country should retain enough institutional understanding of how that information is being used and what analytical conclusions are being generated. The principle is consistent with Part XII: **National ownership with Regional and Global interoperability.** Shared analysis should add capability around National systems, not hollow them out. *** #### 20.6.4 Centralization is not a prerequisite for federation Cross-border information architectures may use centralized, distributed, federated or hybrid approaches according to the nature of the data, institutional requirements and technical environment. NLS does not assume that interoperability requires all source information to reside in one central repository. A shared model may operate through governed exchange. Common analytical methods may work across distributed environments. Certain sensitive objects may remain within National systems while their permitted projections become available elsewhere. The architectural goal is to make legitimate cooperation possible without treating technical centralization as synonymous with institutional maturity. *** #### 20.6.5 Cross-border information should preserve provenance Regional and Global users should remain capable of understanding where material information originated, which institution owns or maintains it, when it was produced and what limitations affect its use. Provenance becomes more important as information travels farther from its source. A polished Global dashboard can otherwise create the impression that every displayed fact was generated or validated by the same institution. Shared presentation should not erase differentiated origin. *** ### 20.7 Retention and Institutional Memory #### 20.7.1 Retention should follow institutional purpose NLS requires longitudinal memory. Leadership development, contribution evidence, Council history, Working Groups, governance pathways and succession all depend on the ability to understand earlier states. This does not mean every information object should be preserved indefinitely. Retention should reflect the purpose and continuing institutional value of the information. Some records may be necessary to preserve a durable leadership history. Others may lose relevance once an operating process concludes. Drafts may have limited long-term value unless they explain a material institutional transition. Retention should therefore be designed around **institutional memory rather than indiscriminate accumulation**. *** #### 20.7.2 Historical leadership states should remain distinguishable from current states The Leadership Ledger should preserve material historical contributions, offices, assignments and transitions. Current interfaces should represent present state accurately. A former Chair remains historically a former Chair. A concluded Working Group remains part of the institutional history. A former professional assignment may remain relevant to capability evidence without appearing active. This temporal distinction allows NLS to preserve the journey without creating stale authority signals. *** #### 20.7.3 Exit does not require erasure of legitimate institutional history When a member leaves active NLS participation, the system should update their current standing and public representation appropriately. Their verified contributions, historical Council service, authorship, governance history and other legitimate institutional records may continue to form part of the history of Nexus. Institutional memory cannot function if every departure causes the past to disappear. The relevant distinction is between **continued historical record and continued active status**. The former may remain valuable after the latter ends. *** #### 20.7.4 Unnecessary information should not be preserved merely because storage is inexpensive Digital systems make indefinite retention technically easy. That convenience should not become the governing principle. Data without continuing institutional purpose creates complexity, increases exposure and can make future interpretation more difficult. NLS should periodically examine whether information still serves the purpose for which it was collected or another legitimate archival function. Information stewardship includes knowing what not to preserve. *** #### 20.7.5 Institutional memory should survive platform change The durable value of NLS records should not depend exclusively on one application interface or technology provider. Critical institutional objects such as Council history, Leadership Ledger states, Plans, Portfolios and material governance records should be maintainable through sufficiently durable information architectures. Technology will change during and beyond the 2026-2030 cycle. Institutional memory should remain recoverable and intelligible even as interfaces, platforms and technical implementations evolve. This is another form of institutional resilience. *** ### 20.8 Knowledge and Intellectual Contribution #### 20.8.1 NLS is a knowledge-producing leadership system Leadership within Nexus produces more than meetings and relationships. Members develop concepts, frameworks, research questions, Working Group outputs, systems models, programme architectures, methods, institutional designs, scenario insights, evidence interpretations and other forms of intellectual contribution. NLS should therefore treat knowledge creation as a first-class form of leadership contribution. The system should be capable of identifying who contributed, how the knowledge was developed, what evidence supports it, what institutional environment produced it and where it can appropriately be reused. Knowledge becomes more valuable when provenance and contribution remain intelligible. *** #### 20.8.2 Contribution does not require surrender of all prior intellectual rights Leaders enter NLS with substantial pre-existing knowledge, methods, research, professional tools and intellectual assets developed outside Nexus. Participation should not be interpreted as transferring all such materials into common Nexus ownership merely because the member uses or references them during Council work. The institution should distinguish **pre-existing material** from work newly developed through the Nexus relationship. This protects the legitimate interests of members and their institutions and makes collaboration easier because contributors do not need to fear that ordinary participation silently absorbs their entire intellectual history. *** #### 20.8.3 New knowledge may be individual, collaborative or institutional Not every NLS knowledge object has the same authorship structure. A member may individually develop a paper. A Working Group may produce a collective framework. A research team may generate a formally authored study. A Council may develop a collective position. Foundry or Universe may produce a systems insight based on many contributions. The architecture should allow these distinctions to remain visible. The goal is not to force every intellectual output into one ownership model. It is to ensure that attribution, rights, reuse and public representation correspond to how the knowledge was actually created. *** #### 20.8.4 Knowledge state matters as much as authorship A draft hypothesis is different from a tested method. A Working Group proposal differs from a Council-approved framework. A Nexus Universe finding may remain preliminary. A formally published research output carries another state. NLS should preserve the maturity and institutional status of knowledge objects alongside authorship. Without this distinction, early ideas can be cited as settled institutional doctrine or exploratory findings can acquire authority they were never intended to carry. Knowledge governance therefore connects directly to the evidence architecture. *** #### 20.8.5 Knowledge should become cumulative One of the strongest purposes of Nexus is to prevent useful institutional knowledge from being repeatedly rediscovered. A method developed in one National Nexus may become relevant to another country. A Regional comparison may reveal a transferable framework. Universe may expose a recurring institutional weakness that informs a future common method. Knowledge governance should therefore make reuse possible where appropriate while preserving origin, limitations and contextual adaptation. The goal is not merely to archive knowledge. It is to make the federation capable of **learning cumulatively across time and geography**. *** ### 20.9 Existing Materials #### 20.9.1 Existing materials retain their historical identity Where a member, institution or partner introduces pre-existing research, methodology, software, publications, data, frameworks or other intellectual material into NLS work, the material should retain its origin and prior identity. Participation in a Working Group does not retroactively transform a previously published external method into a Nexus-created asset. This distinction supports accurate attribution and respectful collaboration. It also makes later public communication clearer because audiences can understand which components originated externally and which were created within Nexus. *** #### 20.9.2 Use of existing material should remain connected to its permitted purpose The fact that a member shares pre-existing material in one NLS environment does not necessarily authorize unrestricted reuse throughout the federation. The permissible use may depend on the nature of the material, the rights held by the member or another institution, the context in which it was shared and any relevant restrictions. NLS should therefore avoid assuming that contribution equals unrestricted transfer. Where wider reuse becomes desirable, the institution should establish an appropriate basis. This makes knowledge sharing more trustworthy because contributors can engage without losing control through ambiguity. *** #### 20.9.3 Existing material can become part of a new collective work without losing provenance A Working Group may build upon several existing methods, papers or frameworks and produce a new synthesis. The resulting work may legitimately become a new collective Nexus output while still identifying the earlier materials upon which it depends. This is normal knowledge development. The important discipline is to preserve enough provenance that the new work does not imply original authorship of concepts that clearly predated it. Synthesis can create new institutional value without erasing intellectual history. *** #### 20.9.4 External knowledge should be evaluated, not merely imported Prestigious external material should not enter Nexus as unquestionable doctrine simply because it comes from a respected institution or leader. The Council or relevant research environment should still consider whether the method applies to the current context, what assumptions it contains and how it fits the evidence available. NLS seeks interoperability with external knowledge, not passive absorption. A credible federation should be capable of learning from the world's strongest institutions while still exercising its own evidence discipline. *** ### 20.10 Collaborative Work #### 20.10.1 Collaborative work should preserve the structure of contribution Many Nexus outputs will be genuinely collaborative. A National Portfolio framework may involve Council Members, Desk staff, technical specialists and institutional partners. A research paper may combine several authors and reviewers. A Nexus Universe finding may emerge through scenario design, technical observation and institutional interpretation. The resulting work should preserve enough contribution structure that major forms of input remain visible. This does not require naming every minor interaction. It requires avoiding institutional narratives in which collective work becomes attributed solely to the most senior or visible participant. *** #### 20.10.2 Collaboration should clarify the institutional home of the output A multi-institutional group can produce one coherent output while the resulting work still needs an institutional home. The relevant institution may maintain the final document, method, model or programme object. This should be sufficiently clear that future users know where the authoritative version resides and who is responsible for maintaining it. Collaborative authorship and institutional stewardship are related but different. Several people may create the work. One competent environment may maintain the controlled version. *** #### 20.10.3 Collaborative work should preserve dissent where it is material Collective outputs sometimes require a common synthesis. That synthesis should not erase material disagreement whose existence affects the interpretation of the work. A research output may identify limitations. A Working Group report may record a minority interpretation. A Council framework may state areas requiring further evidence. This does not weaken collaboration. It demonstrates that the group was capable of producing shared work without manufacturing false unanimity. Knowledge integrity depends partly on preserving the boundaries of consensus. *** #### 20.10.4 Collaboration should avoid title-based appropriation A Chair, senior executive, founder or institutional sponsor should not automatically receive authorship merely because of position. Likewise, junior or less visible contributors should not disappear from the record where their intellectual contribution was substantive. Authorship, acknowledgement and institutional credit should reflect actual contribution and the conventions appropriate to the output. NLS should model the same contribution discipline in knowledge production that it expects within the Leadership Ledger. *** #### 20.10.5 Collaborative knowledge should be designed for future use where appropriate A major advantage of producing work through Nexus is the possibility that it may become useful beyond the original team. Where an output is intended to support future National, Regional or Global work, the group should consider documentation, provenance, contextual assumptions and future maintainability. Knowledge that only its original authors can understand remains fragile. A mature collaborative output becomes increasingly useful as the institution can preserve and adapt it without depending exclusively on the original contributors. *** ### 20.11 Attribution #### 20.11.1 Attribution protects intellectual and institutional truth Attribution tells future users who contributed what and under which institutional context. This matters for fairness, but also for knowledge integrity. A method developed by one research institution has a different provenance from a collective Council synthesis. A Working Group product has a different institutional history from a paper written independently by one member. A programme architecture contributed through a separate professional assignment should remain identifiable as such. Attribution therefore helps the institution interpret the knowledge itself. It is not merely recognition attached after the substantive work has been completed. *** #### 20.11.2 Attribution should be proportionate to actual contribution NLS should distinguish among forms such as authorship, co-authorship, technical contribution, review, institutional sponsorship, facilitation, leadership, data contribution, convening and acknowledgement where relevant. These labels carry different meanings. The appropriate form should follow the work actually performed. This prevents broad association with a project from becoming authorship and prevents intellectual contribution from disappearing because a person did not hold the most visible leadership role. *** #### 20.11.3 Seniority should not absorb intellectual credit Knowledge production is particularly vulnerable to hierarchy effects. A senior leader may have initiated the project while others performed substantial analytical or technical work. A Chair may have stewarded the group without writing the output. A sponsor may have funded the activity without contributing to the conclusion. Each contribution can be important. They should not be conflated. NLS should preserve the integrity of intellectual credit even where organizational hierarchy would make broader attribution socially convenient. *** #### 20.11.4 Attribution can be corrected New information may reveal that an attribution was incomplete or inaccurate. A contributor may have been omitted. An institutional role may have been described incorrectly. Later review may clarify that a supposedly individual contribution was actually collective. Where the correction is material, NLS should update the relevant record and, where appropriate, public representation. Accurate attribution is more important than protecting the convenience of the first published version. *** ### 20.12 Public-Good Knowledge #### 20.12.1 Public-good knowledge is central to the Nexus mission A significant portion of Nexus knowledge is intended to improve institutional capability beyond one organization. Systems methods, public-interest research, leadership frameworks, risk-intelligence approaches, readiness models and other knowledge may create greater value when they can be shared, adapted and used across countries and institutions. NLS should therefore support the development of **public-good knowledge** where that is consistent with the nature of the work and the rights, restrictions and safeguards attached to its inputs. This reflects the broader Nexus public-good architecture. Knowledge can become infrastructure. *** #### 20.12.2 Public-good orientation does not mean everything becomes public immediately A public-good mission can still require restricted development environments, protected research, confidential institutional dialogue or controlled release. The timing and form of publication matter. Early disclosure may undermine a sensitive National relationship. Security-sensitive technical detail may require protection. Preliminary findings may need additional validation. The distinction is therefore between **public-good purpose and universal immediate disclosure**. Knowledge can be developed for public benefit while still moving through appropriate maturity and release stages. *** #### 20.12.3 Public-good release should preserve evidence and provenance When knowledge becomes public, the release should preserve enough information for users to understand its basis, limitations, authorship or institutional source where relevant. Open publication without provenance can reduce rather than increase institutional value because future users cannot determine whether the material remains current or applicable. Public-good knowledge should therefore aim for usability and trustworthiness, not publication volume alone. A method that can be interpreted responsibly is more useful than a large volume of decontextualized material. *** #### 20.12.4 Public-good knowledge should support adaptation Methods and frameworks developed through Nexus should often be adaptable across countries and sectors rather than treated as rigid templates. Where possible, public-good materials should distinguish the common architecture from the elements that require contextual design. This reflects the federation doctrine established in Part XIII. The goal is to make knowledge reusable without implying that implementation should be identical everywhere. Public-good infrastructure becomes stronger when it teaches institutions **how to adapt**, not merely what to copy. *** #### 20.12.5 Public-good knowledge should return learning to Nexus External use can generate new evidence. A framework adopted in another National system may reveal limitations. A research method may be improved by outside scholarship. A public tool may receive corrections from practitioners. Where appropriate, NLS should create pathways through which this external learning can return to the common knowledge base. Publication should therefore not be the end of the knowledge lifecycle. It can become the beginning of a wider learning cycle. *** ### 20.13 Restricted and Proprietary Knowledge #### 20.13.1 Some knowledge should remain bounded Nexus will work with institutions that possess proprietary methods, commercially sensitive information, protected research, security-sensitive systems, unpublished intellectual work and other knowledge that cannot appropriately become public-good material. The Leadership System should be capable of working responsibly with such knowledge. A public-good architecture does not require every contributor to surrender legitimate proprietary interests. The federation becomes more capable when institutions can contribute relevant expertise without assuming that everything shared will later be published or generalized. *** #### 20.13.2 Restricted knowledge should be clearly differentiated from public-good outputs A Working Group or programme may contain both public and restricted components. The architecture should preserve that distinction. A public synthesis may draw upon several sources without disclosing proprietary details. A National Portfolio may contain a public-safe description alongside restricted evidence. A research programme may publish findings while protecting underlying data where required. This layered approach supports collaboration across different institutional environments. The important condition is that users understand which layer they are working with. *** #### 20.13.3 Proprietary contribution should not silently become Nexus ownership Where a provider, member or institution contributes a proprietary method or tool to Nexus work, participation should not be interpreted automatically as transfer of ownership. The relevant arrangement should preserve the rights attached to the contribution while establishing whatever legitimate use is required for the programme. This creates stronger incentives for serious institutions to contribute valuable capability. Ambiguous ownership discourages collaboration and can create conflict long after the work begins. *** #### 20.13.4 Nexus-created knowledge can contain restricted components without becoming wholly restricted A collaborative output may include certain protected elements while its broader framework remains suitable for public release. The institution should therefore avoid binary thinking in which an entire body of work must be either fully open or fully closed. Layered knowledge architecture can preserve both public value and legitimate restriction. This is particularly relevant to systems models, technical infrastructure, security, proprietary datasets and sensitive National information. *** #### 20.13.5 Restricted status should be reviewed where circumstances change Some material may require restriction only temporarily. A draft may become publishable after formal release. A sensitive programme architecture may become public after launch. A research result may become available once the relevant institutional process concludes. Where appropriate, the institution should be capable of reviewing whether the original restriction remains necessary. This does not mean every restricted object should eventually become public. It means information state should remain connected to current institutional reality rather than historical inertia. *** ### 20.14 Corrections and Public Record Integrity #### 20.14.1 Information correction is part of institutional trust No long-running leadership system can guarantee that every record will remain correct without active maintenance. NLS therefore treats correction as part of normal information governance. A member should be able to identify a materially inaccurate biography, outdated affiliation, incorrect role, misattributed contribution or another relevant error and request appropriate review. Institutions should likewise be able to correct information when stronger evidence emerges. The objective is a record capable of becoming more accurate over time. *** #### 20.14.2 Public corrections should follow materiality Not every typographical error requires a formal public correction process. Where a public statement materially misrepresents a person's role, institutional relationship, contribution, authority or another substantive fact, the public projection should be updated proportionately. If an inaccurate statement has propagated significantly, broader correction may sometimes be appropriate. The response should follow the consequence of the error. The objective is to restore an accurate institutional record, not perform correction theatrically. *** #### 20.14.3 Corrections should preserve source responsibility The institution responsible for the underlying fact should ordinarily determine the corrected state. GCRI Canada can correct NLS operational records under its stewardship. A competent Nexus entity should establish the truth of its own governance appointment. A National institution should remain the appropriate source for its own formal relationship where that fact belongs to it. This prevents the common NLS infrastructure from becoming an unauthorized editor of other institutions' authoritative facts. Again: > **We operate the common system. The competent institution retains the responsibility that belongs to it.** *** #### 20.14.4 Material corrections should preserve appropriate history Where a material institutional record changes, the system should preserve enough history to explain the transition without continuing to present the earlier state as current. A former Chair remains part of the historical record. A corrected attribution may preserve the prior version and subsequent change where important. A programme previously recorded as Active may later be Concluded. This temporal architecture prevents two equally serious failures: erasing institutional history and retaining obsolete states as though they remain current. *** #### 20.14.5 Corrections should propagate through governed projections If the authoritative underlying fact changes, dependent member, Council, operational and public views should update coherently. A corrected Council office should not remain wrong on the public profile. A changed affiliation should not be accurate in one environment and obsolete in another indefinitely. A corrected contribution state should not continue producing an inflated public claim. This is why NLS treats public profiles and other interfaces as projections of governed records rather than independent publications. Correction becomes scalable when the architecture understands dependency. *** #### 20.14.6 The information and knowledge proposition The complete NLS information architecture can therefore be expressed as: > **Purpose → authoritative source → appropriate collection → contextual use → proportionate access → governed projection → evidence and provenance → retention where justified → correction where required → cumulative institutional learning** Knowledge follows a parallel path: > **Contribution → provenance → authorship or attribution → institutional state → appropriate rights and restrictions → public-good or bounded use → adaptation → correction → future learning** The architecture is designed to make information and knowledge useful without assuming that usefulness requires universal visibility, unlimited reuse or centralized ownership. NLS succeeds when leaders can work across a shared institutional system while still understanding **what information they hold, why they hold it, which institution owns the underlying fact, which knowledge can travel, what remains restricted, and how public representation relates to the richer record beneath it**. *** ## PART XX FRAMEWORK PRINCIPLES **Purpose before collection and access.** We maintain information because the Leadership System requires institutional memory, evidence, coordination, development and accurate public representation. The fact that data can be collected, inferred or shared does not mean it should be. Information should remain connected to a legitimate institutional purpose, and access should follow the role and context in which that purpose exists. **One fact family, many governed views.** Member, Council, operational, governance and public interfaces may require different levels of detail, but they should derive from coherent underlying institutional facts. Public profiles are selective projections rather than complete Leadership Ledger records. Restricted evidence may support narrower public-safe conclusions. Corrections should occur through the authoritative source and propagate coherently to the views that depend upon it. **Knowledge with provenance and attribution.** NLS is a knowledge-producing leadership system. Existing materials retain their prior identity, collaborative work should preserve the structure of contribution, and authorship or acknowledgement should follow actual intellectual input rather than hierarchy, sponsorship or visibility. Seniority does not absorb credit, and contribution does not silently transfer ownership of all pre-existing intellectual assets. **Public-good purpose with legitimate boundaries.** Nexus seeks to create knowledge that can strengthen institutions across countries and systems, but public-good orientation does not require every draft, dataset, technical detail or institutional record to become public. Restricted, proprietary, protected and security-sensitive knowledge can coexist with public-good outputs through layered information architecture and context-appropriate release. **Cross-border interoperability without informational collapse.** National, Regional and Global leadership requires information to travel. Federation should preserve National context, provenance, legitimate restrictions and institutional responsibility as information moves. Shared infrastructure and coherent interfaces should increase usability without implying that all information must become centrally stored, globally visible or owned by the institution operating the common platform. *** ## OPERATING RELATIONSHIP Part XX establishes the information and knowledge architecture beneath the leadership system defined in the preceding Parts. Part XI created the **Leadership Ledger** as durable institutional memory. Part XVIII established **Zero-Trust Leadership**, including identity, capacity and contextual access. Part XIX established the integrity principles governing confidentiality, public representation and responsible information use. Part XX integrates those doctrines into a common information-governance model. The architecture begins with purpose. NLS collects and maintains information because it requires coherent member records, Council continuity, Plans, evidence, Working Groups, governance pathways, opportunity routing and institutional learning. Information should not be accumulated merely because digital systems make accumulation inexpensive. Personal information remains proportionate to the leadership relationship. Professional and institutional context can be highly relevant, but NLS does not treat membership as a license to absorb unrelated private life into the institutional record. Member-submitted information can enrich the system while consequential institutional states remain controlled by the processes that legitimately establish them. The **public Leadership Profile** is a governed projection of selected approved facts. It is not the full Leadership Ledger. Council and Working Group environments can contain deeper operational and deliberative information. Governance environments may contain more restricted information still. Public, member, Council, Desk and governance views therefore differ in visibility while remaining connected to coherent underlying facts. Cross-border federation adds another dimension. Information may move from National into Regional and Global contexts, but provenance and National context should survive that movement. Interoperability does not require indiscriminate centralization. Federated or layered architectures may preserve sensitive source information while exposing the views required for legitimate shared analysis. NLS also produces knowledge. Members arrive with substantial pre-existing intellectual assets and may create new research, frameworks, methods, programmes and institutional designs through the leadership system. Existing materials retain their provenance. Collaborative work should preserve actual contribution. Authorship should follow substantive intellectual work rather than hierarchy or sponsorship. New Nexus knowledge may be public-good, restricted, proprietary, or composed of several layers according to its origin and purpose. Public-good knowledge remains a core institutional objective because the wider Nexus mission depends on cumulative learning and reusable capability. Public-good orientation does not mean immediate universal disclosure. Maturity, rights, sensitivity, National ownership and legitimate restrictions still matter. Publication should preserve enough evidence, context and provenance to make future use responsible. Finally, information remains correctable. A multi-year institution will inevitably encounter outdated roles, changed affiliations, corrected attribution and evolving programme states. The system should update current truth while preserving legitimate historical memory. Correction should propagate through the governed projections that depend on the authoritative fact. The governing proposition of Part XX is therefore: > **Nexus treats information and knowledge neither as private property to be trapped inside silos nor as raw material that becomes universally accessible once it enters the system. We govern information according to purpose, provenance, institutional responsibility, legitimate access, attribution and public value so that the federation can learn cumulatively without losing context, rights, trust or institutional truth.** ## NEXT ## PART XXI: VALUE PROPOSITION ### Mutual Value, Value to Nexus, Countries and Regions, Leaders and Their Institutions, Strategic Intelligence, Leadership Development, Networks, Applied Contribution, Recognition and the Limits of What NLS Can Promise Part XXI will define the reciprocal value architecture of the Nexus Leadership System in full. It will establish the Four-Way Value model across Nexus, country or Region, the leader's institution or enterprise, and the leader personally; distinguish value creation from benefit entitlement; define the strategic-intelligence, leadership-development, peer-network, applied-work, recognition and opportunity value created through NLS; explain what leaders are expected to contribute in return; and state clearly what Council membership, participation, recognition and institutional proximity cannot legitimately promise. ## 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/xx.-information-governance.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.