ARTICLE XVII. TRANSITIONS
Section 480. Amendment Purpose and Authority
480.1 Amendment Purpose.
480.1.1 Amendment under these Bylaws shall provide the lawful, record-based, public-benefit-compatible, governance-controlled, and correctionable process by which the Corporation may revise, supplement, clarify, restate, renumber, technically correct, or otherwise modify its Bylaws while preserving the Corporation’s nonprofit character, nonstock and non-share structure, public-good technical mission, legal separateness, role separation, non-execution doctrine, public authority boundary discipline, finance-boundary discipline, certification and recognition boundary discipline, procurement neutrality, data / AI / cyber / privacy controls, safeguards, protected knowledge controls, validity-by-record, and correctionability.
480.1.2 Amendment shall be used to keep these Bylaws current with lawful governance needs, public-benefit purpose, United States nonprofit requirements, applicable state law, federal law, tax posture, public authority interface requirements, Nexus coordination requirements, technological change, risk controls, records discipline, research integrity, evidence integrity, public-safe publication, and institutional learning.
480.1.3 Amendment shall not be used to evade fiduciary duties, weaken nonprofit restrictions, authorize private inurement, create impermissible private benefit, collapse the public-good stack into the enterprise stack, permit sponsor or provider control, blur GCRI / GRF / GRA role separation, create unauthorized public authority status, create regulated finance activity, create certification authority, create recognition authority, create procurement authority, create public warning authority, create emergency command authority, or convert the Corporation into an enterprise execution vehicle.
480.2 Amendment Authority.
480.2.1 Amendment Authority shall mean the power to adopt, amend, repeal, restate, or otherwise modify these Bylaws according to applicable law, the Corporation’s certificate or articles, these Bylaws, and competent governance records.
480.2.2 Amendment Authority shall be exercised only by the body or persons lawfully empowered to act, and only through a recorded process satisfying notice, approval, conflict review, required voting thresholds, reserved matter treatment, member approval where required, filing distinctions where applicable, repository controls, and effective-date records.
480.2.3 No person, officer, director acting alone, committee, council, working group, contributor, maintainer, advisor, fellow, sponsor, provider, donor, funder, public authority participant, Nexus participant, GRA participant, GRF participant, or external actor shall possess Amendment Authority unless such authority is expressly provided by law, the articles or certificate, these Bylaws, or competent Board record.
480.3 Board Amendment Authority.
480.3.1 Subject to applicable law, the Corporation’s certificate or articles, member approval requirements where applicable, and any reserved matter restrictions, the Board shall have authority to amend these Bylaws.
480.3.2 Board Amendment Authority shall include authority to adopt amendments, repeal provisions, restate provisions, approve consolidated texts, correct technical errors, approve non-substantive revisions, approve substantive revisions, and direct repository publication or controlled notice, provided that the Board acts within lawful scope.
480.3.3 Board Amendment Authority shall be exercised by resolution, written consent, or other lawful Board action and shall be recorded in the corporate books.
480.3.4 Board Amendment Authority shall not be delegated to officers, committees, advisors, counsel, staff, technical maintainers, repository custodians, AI tools, or external drafting teams except for drafting, review, formatting, preparation, publication, repository administration, certification, or technical correction functions expressly authorized and subject to Board control.
480.4 Member Approval Where Required by Law, Articles, Certificate, or Bylaw.
480.4.1 Where applicable law, the certificate or articles, these Bylaws, or any lawful member-rights provision requires member approval for a Bylaw amendment, the Corporation shall obtain such approval before the amendment becomes effective.
480.4.2 Member approval records shall identify the members entitled to approve, notice given, text or summary provided, voting method, voting threshold, votes cast, abstentions, approvals, objections where recorded, effective date, and any filing or repository action.
480.4.3 Where the Corporation has no voting members, no member approval shall be required unless applicable law, the certificate or articles, or a future lawful Bylaw amendment creates such requirement.
480.5 Incorporator or Initial Director Authority During Formation Where Applicable.
480.5.1 During formation and prior to the organization of the initial Board, incorporators or initial directors may exercise amendment or organizational authority only to the extent permitted by applicable law and formation records.
480.5.2 Incorporator or initial director authority shall be recorded and shall terminate or narrow upon organization of the Board, adoption of initial Bylaws, appointment of directors and officers, or completion of formation actions, unless continuing authority is separately recorded.
480.5.3 Historical incorporator records shall not create continuing Amendment Authority after the Board is organized unless competent records expressly provide otherwise.
480.6 Reserved Matter Treatment.
480.6.1 Bylaw amendments shall be treated as reserved matters requiring Board-level review unless applicable law, the certificate or articles, or these Bylaws require a higher approval.
480.6.2 Amendments affecting nonprofit purpose, tax posture, director or officer authority, member rights where applicable, indemnification, advancement, limitation of liability, public authority boundaries, finance boundaries, certification and recognition boundaries, procurement neutrality, GCRI / GRF / GRA role separation, legal separateness, data / AI / cyber / privacy controls, safeguards, protected knowledge, Nexus coordination, dissolution, or amendment procedure shall receive heightened review.
480.6.3 Reserved matter treatment shall require clear records of authority, review, approval, effective date, repository status, and any required notice.
480.7 Amendment of Articles or Certificate Distinguished From Amendment of Bylaw.
480.7.1 Amendment of the certificate or articles shall be distinguished from amendment of these Bylaws and shall comply with applicable filing requirements, statutory approval requirements, member approval requirements where applicable, and state records requirements.
480.7.2 A Bylaw amendment shall not amend the certificate or articles unless the amendment process for the certificate or articles is separately satisfied.
480.7.3 Where a proposed Bylaw amendment conflicts with the certificate or articles, the certificate or articles shall control to the extent legally required, and the proposed Bylaw amendment shall be revised, rejected, or accompanied by a lawful amendment of the certificate or articles where appropriate.
480.8 Amendment of Policies Distinguished From Amendment of Bylaw.
480.8.1 Policies, procedures, schedules, authority matrices, templates, clause libraries, manuals, playbooks, protocols, registers, technical baselines, public-safe publication matrices, controlled vocabulary schedules, repository rules, and operating instruments may be amended according to their own authority records and shall not require Bylaw amendment unless these Bylaws, applicable law, Board resolution, or the governing instrument so requires.
480.8.2 No policy amendment may override, narrow, expand, repeal, or contradict these Bylaws.
480.8.3 Where a policy amendment materially affects a Bylaw-controlled matter, the policy amendment shall be reviewed for consistency with these Bylaws and escalated to the Board where required.
480.9 Amendment of Schedules, Forms, Registers, Protocols, and Operating Instruments Distinguished From Amendment of Bylaw.
480.9.1 Schedules, forms, registers, protocols, operating instruments, interface instruments, repository templates, technical profiles, evidence templates, model cards, dataset cards, system cards, benchmark cards, publication approval forms, public authority reference forms, finance-boundary language, and controlled-room forms may be updated without Bylaw amendment where the update is within recorded authority and does not alter rights, duties, authority, purpose, prohibited functions, reserved matters, boundaries, liabilities, or governance structure.
480.9.2 Such operating instruments shall be subordinate to these Bylaws and shall be interpreted consistently with these Bylaws.
480.9.3 Where an operating instrument is inconsistent with these Bylaws, the Bylaws shall control and the instrument shall be corrected, withdrawn, superseded, or escalated.
480.10 No Informal Amendment.
480.10.1 These Bylaws may not be amended informally.
480.10.2 No informal conversation, course of dealing, repeated practice, officer instruction, committee recommendation, public statement, public authority meeting, sponsor request, provider request, donor preference, staff custom, repository practice, AI-generated revision, or operational workaround shall amend these Bylaws.
480.10.3 A person relying on an alleged informal amendment bears no authority to bind the Corporation unless a competent Amendment Record exists.
480.11 No Amendment by Custom, Practice, Draft, Slide, Summary, Public Statement, AI Output, Translation, Email, Meeting Note, or Unapproved Operating Instrument.
480.11.1 No custom, practice, draft, redline, slide, presentation, summary, public statement, AI output, AI summary, translation, email, chat, meeting note, transcript, repository comment, issue, pull request, website page, training material, media statement, or unapproved operating instrument shall amend these Bylaws.
480.11.2 Public-facing summaries, translations, GitBook materials, knowledge-base pages, diagrams, public notices, and plain-language explanations may support understanding but shall not control over the official Bylaw text unless adopted as authoritative by competent amendment record.
480.11.3 Where such materials conflict with these Bylaws, the official Bylaw text shall control and the conflicting material shall be corrected.
480.12 Amendment Must Be Record-Based.
480.12.1 Every amendment, repeal, restatement, technical correction, renumbering, consolidation, or non-substantive revision shall be supported by records sufficient to establish authority, text, approval, effective date, version, repository location, supersession, notice, and correction path.
480.12.2 The Corporation shall maintain an authoritative amendment history and shall preserve prior versions unless lawful deletion, sealing, or other restriction is required.
480.12.3 No amendment shall have public meaning, governance effect, repository effect, or legal effect within the Corporation unless supported by an Amendment Record.
480.13 Amendment Records.
480.13.1 The Corporation shall maintain Amendment Records, including amendment purpose records, Amendment Authority records, Board Amendment Authority records, member approval records where required, incorporator or initial director authority records where applicable, reserved matter records, certificate or articles distinction records, policy amendment distinction records, schedule / form / register / protocol / operating instrument distinction records, no-informal-amendment records, no-amendment-by-unapproved-material records, record-based amendment records, notices, redlines, approvals, effective-date records, repository records, supersession records, correction records, and archive records.
Section 481. Amendment Procedure
481.1 Amendment Proposal.
481.1.1 An Amendment Proposal shall identify the proposed amendment, reason for amendment, affected provisions, proposed text, affected definitions, affected policies, affected registers, affected schedules, affected records, affected roles, affected authorities, affected boundaries, affected Nexus interfaces, and requested effective date.
481.1.2 An Amendment Proposal may be initiated by the Board, a Board committee acting within delegation, an authorized officer, counsel, a governance reviewer, a compliance reviewer, a records custodian, or another person authorized by competent record.
481.1.3 An Amendment Proposal shall not create amendment effect until approved according to these Bylaws.
481.2 Sponsor of Amendment.
481.2.1 Each Amendment Proposal shall identify a Sponsor of Amendment responsible for coordinating drafting, review, record preparation, Board submission, conflict disclosures, approval routing, repository publication, notices, and implementation.
481.2.2 The Sponsor of Amendment may be a director, officer, committee chair, governance officer, legal counsel, records custodian, or other authorized person.
481.2.3 Sponsorship of an amendment shall not itself confer authority to adopt, approve, publish, or certify the amendment.
481.3 Drafting Record.
481.3.1 Each substantive amendment shall have a Drafting Record identifying drafter, source of instructions, prior text, proposed text, affected provisions, drafting rationale, reviewed materials, related records, and version history.
481.3.2 Where AI tools or external drafting support are used, the Drafting Record shall identify such use where material, confirm human review, protect confidential and privileged materials, and confirm that no unauthorized data, protected knowledge, public authority data, or restricted materials were used in violation of these Bylaws.
481.3.3 Drafting Records shall be classified appropriately and shall not be treated as adopted Bylaws.
481.4 Redline Requirement Where Appropriate.
481.4.1 A redline, comparison table, or equivalent change record shall be prepared where appropriate to show the difference between current text and proposed text.
481.4.2 A redline shall identify additions, deletions, moved provisions, renumbering, cross-reference changes, defined-term changes, controlled vocabulary changes, and substantive effects where practicable.
481.4.3 Redlines shall be aids to review and shall not control over the adopted amendment text unless expressly adopted.
481.5 Explanation of Purpose.
481.5.1 The Amendment Proposal shall include an explanation of purpose sufficient for the approving body to understand why the amendment is proposed, what problem it addresses, what risk it mitigates, what governance need it serves, and how it supports the Corporation’s public-benefit mission.
481.5.2 The explanation shall identify whether the amendment is substantive, non-substantive, technical, corrective, harmonizing, legally required, Nexus-coordination-related, public authority-related, data / AI / cyber-related, safeguards-related, or compliance-related.
481.6 Legal Review.
481.6.1 Legal Review shall be conducted where the amendment may affect applicable law, governing state law, federal law, tax posture, nonprofit status, member rights, director or officer duties, indemnification, advancement, limitation of liability, employment, contracts, grants, public authority interfaces, privacy, cybersecurity, sanctions, export-control, competition, IP, professional boundaries, litigation risk, or regulatory risk.
481.6.2 Legal Review may be performed by counsel or other qualified reviewer as appropriate.
481.6.3 Legal Review records may be privileged and shall be protected accordingly.
481.7 Governance Review.
481.7.1 Governance Review shall assess whether the amendment is consistent with the certificate or articles, these Bylaws, Board reserved powers, officer authority, committee authority, member rights where applicable, delegation records, authority matrices, conflict rules, corporate books, and legal separateness.
481.7.2 Governance Review shall identify whether Board approval, member approval, filing, notice, repository update, policy update, or register update is required.
481.8 Public-Benefit Purpose Review.
481.8.1 Public-Benefit Purpose Review shall assess whether the amendment advances or preserves the Corporation’s public-benefit purpose, nonprofit character, public-good technical role, evidence stewardship, methods stewardship, observability methods role, ontology role, technical truth role, public-good software role, public authority learning support role, safeguards role, and Nexus coordination role.
481.8.2 An amendment inconsistent with the Corporation’s public-benefit purpose shall be rejected, revised, or escalated for legal and Board review.
481.9 Nonprofit and Tax Status Review.
481.9.1 Nonprofit and Tax Status Review shall assess whether the amendment could affect nonprofit status, nonstock status, non-share status, tax classification, tax-exempt status where applicable, charitable purpose where applicable, public-benefit restrictions, private inurement controls, private benefit controls, excess benefit rules where applicable, unrelated business income issues, charitable solicitation, donor restrictions, public support, or public inspection obligations.
481.9.2 No amendment shall be adopted if it would knowingly create unlawful private inurement, impermissible private benefit, or tax-status inconsistency.
481.10 Non-Execution Review.
481.10.1 Non-Execution Review shall assess whether the amendment could convert, imply conversion, or allow drift of the Corporation into an execution body, operator, public authority, emergency command body, public warning body, procurement authority, finance authority, certification body, recognition body, provider, national company, Project SPV, fund, lender, insurer, broker, dealer, investment adviser, rating agency, or enterprise execution vehicle.
481.10.2 Any amendment creating execution ambiguity shall be revised to preserve the Corporation’s non-executing public-good technical role.
481.11 GCRI / GRF / GRA Role-Separation Review.
481.11.1 Role-Separation Review shall assess whether the amendment preserves the distinct roles of The Global Centre for Risk and Innovation (GCRI), The Global Risks Forum (GRF), and The Global Risks Alliance (GRA).
481.11.2 The amendment shall not assign GRF recognition, standing, maturity, public legitimacy, registry, or claims-discipline authority to GCRI US unless lawfully and explicitly authorized by competent cross-institutional records and consistent with governing instruments.
481.11.3 The amendment shall not assign GRA finance-readiness, capital-readability, insurance-readiness, proof-pack, diligence translation, public finance, or capital-reader authority to GCRI US unless lawfully and explicitly authorized by competent records and consistent with regulated-perimeter discipline.
481.12 Public Authority Boundary Review.
481.12.1 Public Authority Boundary Review shall assess whether the amendment could imply public authority status, public authority delegation, official public authority decision-making, public warning authority, emergency command authority, regulatory authority, procurement authority, public finance approval, public funding approval, public-private partnership, sovereign obligation, public infrastructure command, public health order authority, or public safety command authority.
481.12.2 Any amendment affecting public authority participation, public authority data, public authority references, public authority rooms, public grants, lobbying, government ethics, public records, FOIA, sunshine laws, open meetings, procurement, public finance, emergency management, public safety, or public health shall receive heightened review.
481.13 Finance, Securities, Insurance, Lending, Rating, Public Finance, Procurement, Certification, Recognition, Docket, Grid, Nexus-Compatible, Provider-Preference, and Professional Boundary Review.
481.13.1 Boundary Review shall assess whether the amendment could create or imply finance-readiness, capital-readability, insurance-readiness, investment advice, securities activity, broker-dealer activity, finder activity, underwriting, lending, banking, insurance placement, insurance underwriting, rating, public finance approval, public guarantee, public credit, grant approval, tax credit approval, procurement approval, approved vendor status, provider preference, certification, accreditation, conformance approval, compliance approval, recognition, standing, maturity, Docket approval, Grid guarantee, Nexus-compatible status, legal advice, engineering certification, public health advice, medical advice, accounting advice, tax advice, or other professional assurance.
481.13.2 Amendments shall be drafted to preserve GRA role separation, GRF role separation, Nexus Standards role separation, procurement neutrality, provider neutrality, public authority boundaries, and professional boundary controls.
481.14 Data / AI / Cyber / Privacy Review.
481.14.1 Data / AI / Cyber / Privacy Review shall assess whether the amendment affects data governance, lawful basis, consent, public authority data, rights-bearing data, health-sensitive data, youth data, cyber-sensitive data, infrastructure-sensitive data, community-protected data, Tribal / Indigenous data, protected knowledge, cross-border transfers, AI governance, model registers, inference records, compute workload records, proof receipts, agentic AI controls, AI training restrictions, cybersecurity controls, repository security, incident response, breach notification, legal holds, or controlled rooms.
481.14.2 Amendments shall preserve privacy by design, security by design, human review, AI-use restrictions, incident response, record integrity, and public-safe publication.
481.15 Research Integrity and Evidence Methods Review.
481.15.1 Research Integrity and Evidence Methods Review shall assess whether the amendment affects research integrity, research ethics, human-subjects review, community review, Tribal / Indigenous review, protected knowledge review, evidence doctrine, methods doctrine, observability methods, ontology, controlled vocabulary, technical truth, Truth Engine methods, peer review, research misconduct, evidence challenge, method challenge, publication challenge, or correctionability.
481.15.2 Amendments shall preserve evidence as record-based technical support and shall not convert evidence or methods into recognition, finance-readiness, certification, procurement approval, public authority action, public warning, emergency command, rating, or legal compliance approval.
481.16 Public-Good Software and Technical Asset Review.
481.16.1 Public-Good Software and Technical Asset Review shall assess whether the amendment affects public-good software, open technical baselines, schemas, APIs, SDKs, technical profiles, reference architectures, repositories, contributor terms, IP ownership, licensing, restricted assets, secure development, SBOMs, vulnerabilities, secrets, release governance, forks, compatibility claims, Nexus-compatible claims, anti-enclosure, marks, datasets, models, benchmarks, technical asset registers, or public-safe release.
481.16.2 Amendments shall preserve public-good technical asset stewardship without creating certification, procurement mandate, public authority adoption, provider preference, finance-readiness, recognition, rating, or operational guarantee.
481.17 Civil Rights, Accessibility, Community Safeguards, Tribal / Indigenous, Local, Territorial, Cultural, Environmental, and Protected Knowledge Review.
481.17.1 Safeguards Review shall assess whether the amendment affects civil rights, accessibility, non-discrimination, community safeguards, vulnerable populations, public-safe mapping, Tribal / Indigenous interfaces, Indigenous data, Indigenous knowledge, local knowledge, territorial knowledge, cultural knowledge, environmental knowledge, ecological knowledge, sacred knowledge, protected knowledge, consent, non-consent, attribution, non-attribution, withdrawal, restriction, correction, grievance, protected participation, non-retaliation, or do-no-harm controls.
481.17.2 Amendments shall be interpreted and drafted to preserve the most protective lawful safeguards where ambiguity exists.
481.18 Nexus Coordination and Legal Separateness Review.
481.18.1 Nexus Coordination and Legal Separateness Review shall assess whether the amendment affects coordination with GCRI Canada, other GCRI entities, GRF, GRA, Nexus Standards, protocol authorities, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, public authorities, national companies, Project SPVs, providers, hosts, sponsors, universities, laboratories, communities, civil society, media, or enterprise stack actors.
481.18.2 Amendments shall preserve no merger, no agency, no partnership, no joint venture, no shared liability, no implied authority to bind another entity, no public authority delegation, no finance-readiness by implication, no recognition by implication, no certification by implication, no procurement approval by implication, and no enterprise execution by GCRI US.
481.19 Conflict and Related-Party Review.
481.19.1 Conflict and Related-Party Review shall be conducted where an amendment may affect the interests, powers, duties, protections, compensation, indemnification, contract rights, access rights, recognition, finance-facing position, procurement position, sponsor position, provider position, donor position, funder position, or institutional role of a director, officer, insider, related party, sponsor, provider, funder, donor, partner, vendor, or affiliated entity.
481.19.2 Persons with material conflicts shall disclose conflicts and recuse where required by law, policy, or Board determination.
481.19.3 Conflict and related-party review shall preserve fiduciary integrity, private benefit controls, sponsor non-control, provider neutrality, procurement neutrality, and public trust.
481.20 Notice of Amendment.
481.20.1 Notice of Amendment shall be provided to directors and other required recipients according to applicable law, the certificate or articles, these Bylaws, Board practice, and member rights where applicable.
481.20.2 Notice shall include the proposed amendment text or adequate summary, affected provisions, meeting date or consent process, required approvals, review materials where appropriate, and voting procedure.
481.20.3 Notice records shall be retained with Amendment Records.
481.21 Approval Vote.
481.21.1 The approving body shall vote or consent on the amendment according to applicable law, the certificate or articles, these Bylaws, and required thresholds.
481.21.2 Approval records shall identify approving body, quorum where applicable, vote threshold, votes, abstentions, recusals, written consents where applicable, member approvals where required, approval conditions, and final text approved.
481.21.3 Amendments shall not be effective unless approval records are sufficient to establish lawful adoption.
481.22 Effective Date.
481.22.1 Each amendment shall identify an effective date.
481.22.2 If no effective date is specified, the amendment shall become effective upon lawful approval unless applicable law, filing requirement, member approval, Board condition, repository publication, or implementation requirement provides otherwise.
481.22.3 Effective-date records shall distinguish adoption date, approval date, filing date, notice date, publication date, and operational implementation date.
481.23 Repository Publication or Controlled Notice.
481.23.1 Approved amendments shall be placed in the Official Repository and included in the authoritative version-control system.
481.23.2 The Corporation may issue public, public-safe, internal, controlled, Board-restricted, member-facing where applicable, funder-facing, public authority-facing, or Nexus-facing notice depending on the amendment’s classification and audience.
481.23.3 Repository publication or controlled notice shall not disclose privileged, confidential, public authority restricted, cyber-sensitive, infrastructure-sensitive, finance-sensitive, protected knowledge, controlled technology, export-controlled, sanctions-sensitive, personal, health-sensitive, or investigation-sensitive information beyond authorized scope.
481.24 Amendment Procedure Records.
481.24.1 The Corporation shall maintain Amendment Procedure Records, including Amendment Proposal records, Sponsor of Amendment records, Drafting Records, redline records where appropriate, explanation-of-purpose records, Legal Review records, Governance Review records, Public-Benefit Purpose Review records, Nonprofit and Tax Status Review records, Non-Execution Review records, GCRI / GRF / GRA Role-Separation Review records, Public Authority Boundary Review records, finance / securities / insurance / lending / rating / public finance / procurement / certification / recognition / Docket / Grid / Nexus-compatible / provider-preference / professional boundary review records, Data / AI / Cyber / Privacy Review records, Research Integrity and Evidence Methods Review records, Public-Good Software and Technical Asset Review records, civil rights / accessibility / community safeguards / Tribal / Indigenous / local / territorial / cultural / environmental / protected knowledge review records, Nexus Coordination and Legal Separateness Review records, Conflict and Related-Party Review records, Notice of Amendment records, approval vote records, effective-date records, repository publication or controlled notice records, correction records, and archive records.
Section 482. Restatement, Consolidation, Renumbering, Technical Corrections, and Non-Substantive Revisions
482.1 Restatement Purpose.
482.1.1 Restatement, consolidation, renumbering, technical corrections, and non-substantive revisions shall permit the Corporation to maintain a clear, accurate, readable, indexed, internally consistent, and operationally usable Bylaw text without altering substantive rights, duties, authority, purpose, prohibited functions, reserved matters, boundaries, liabilities, or governance structure except through formal amendment.
482.1.2 This Section shall support record integrity, public-safe publication, repository discipline, controlled vocabulary consistency, cross-reference accuracy, version control, accessibility, translation accuracy, and correctionability.
482.2 Consolidated Bylaw.
482.2.1 The Corporation may maintain a Consolidated Bylaw incorporating all duly adopted amendments into a single current text.
482.2.2 A Consolidated Bylaw shall identify version, effective date, amendment history, consolidation authority, and repository location.
482.2.3 A Consolidated Bylaw shall not alter the substance of adopted amendments and shall be subordinate to the underlying amendment records if a discrepancy exists, unless the Consolidated Bylaw itself is adopted as the authoritative restatement by the Board or other competent authority.
482.3 Renumbering Authority.
482.3.1 The Corporation may renumber sections, subsections, clauses, schedules, appendices, exhibits, cross-references, and internal references where renumbering is non-substantive and supports readability, consistency, citation, or repository organization.
482.3.2 Renumbering shall not alter meaning, authority, rights, duties, obligations, limitations, approvals, reserved matters, boundaries, liabilities, or effective dates.
482.3.3 Renumbering shall be recorded and, where material, mapped from prior numbering to new numbering.
482.4 Cross-Reference Correction.
482.4.1 The Corporation may correct internal or external cross-references where references are incorrect, outdated, broken, renumbered, miscaptioned, or otherwise technically defective.
482.4.2 Cross-reference correction shall not alter substantive meaning.
482.4.3 Where cross-reference correction may affect interpretation, reliance, authority, or boundary meaning, the matter shall be escalated for Board ratification or formal amendment.
482.5 Typographical Correction.
482.5.1 The Corporation may correct spelling errors, typographical errors, punctuation errors, obvious grammatical errors, spacing errors, capitalization errors, numbering mistakes, and similar scrivener’s errors.
482.5.2 Typographical corrections shall not change legal meaning.
482.5.3 Where correction of wording could change meaning, authority, boundary, obligation, liability, or interpretation, the correction shall not be treated as typographical and shall require proper amendment or Board ratification where appropriate.
482.6 Formatting Correction.
482.6.1 The Corporation may correct formatting, heading style, indentation, table of contents alignment, page layout, hyperlink formatting, style consistency, bolding, spacing, numbering format, citation format, accessibility formatting, and repository display formatting.
482.6.2 Formatting corrections shall not alter substantive meaning.
482.6.3 Formatting corrections shall preserve the user-facing and official document structure needed for readability, indexing, public-safe publication, repository integrity, and authoritative version control.
482.7 Defined-Term Harmonization.
482.7.1 The Corporation may harmonize defined terms where a term is inconsistently capitalized, pluralized, abbreviated, translated, cross-referenced, or formatted, provided the harmonization does not alter substantive meaning.
482.7.2 Defined-term harmonization shall preserve the meaning of institutional terms, including The Global Centre for Risk and Innovation (GCRI), The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, public-good stack, enterprise stack, public authority, finance-readiness, recognition, technical truth, public-safe publication, validity-by-record, and correctionability.
482.7.3 Where harmonization could affect role separation, public authority boundaries, finance boundaries, certification or recognition boundaries, procurement neutrality, safeguards, data / AI / cyber obligations, or liability, formal review shall be required.
482.8 Controlled Vocabulary Harmonization.
482.8.1 Controlled Vocabulary Harmonization may be used to align Bylaw text with approved controlled vocabulary records and to prevent semantic drift.
482.8.2 Harmonization may include replacing ambiguous terms with approved boundary language, clarifying restricted terms, aligning public authority capacity terms, aligning GRA finance-boundary terms, aligning GRF recognition-boundary terms, aligning Nexus-compatible terms, or correcting inconsistent terminology.
482.8.3 Controlled Vocabulary Harmonization shall not create certification, recognition, finance-readiness, procurement approval, public authority adoption, public warning, emergency command, or Nexus-compatible status by implication.
482.9 Citation or Reference Update.
482.9.1 The Corporation may update citations, statutory references, policy references, repository links, document references, schedule references, form references, and external references where the update is non-substantive and preserves intended meaning.
482.9.2 If an external reference is replaced, repealed, materially changed, or no longer appropriate, the update shall be reviewed for substantive effect.
482.9.3 Citation or reference updates shall not import external obligations, standards, certifications, public authority approvals, finance meanings, or recognition meanings unless adopted by competent amendment.
482.10 Schedule or Appendix Update Where Non-Substantive.
482.10.1 Schedules, appendices, forms, templates, matrices, controlled vocabulary tables, repository indexes, retention schedules, access schedules, and similar instruments may be updated as non-substantive revisions where authorized and where the update does not alter rights, duties, authority, purpose, prohibited functions, reserved matters, boundaries, liabilities, or governance structure.
482.10.2 Non-substantive schedule or appendix updates shall be recorded, versioned, and linked to the Bylaw provision or policy authorizing the update.
482.10.3 Substantive schedule or appendix updates shall require Board approval or formal amendment where required.
482.11 No Non-Substantive Revision May Alter Rights, Duties, Authority, Purpose, Prohibited Function, Reserved Matter, Boundary, or Liability.
482.11.1 No revision shall be treated as non-substantive if it alters, expands, narrows, waives, or creates any right, duty, authority, purpose, prohibited function, reserved matter, boundary, liability, indemnification protection, advancement protection, limitation of liability, access right, public authority meaning, finance meaning, recognition meaning, certification meaning, procurement meaning, data right, AI right, safeguards right, protected knowledge right, or Nexus interface meaning.
482.11.2 If doubt exists, the revision shall be treated as substantive unless the Board, Secretary, counsel, or other competent authority determines and records that the revision is non-substantive.
482.12 Secretary Certification of Non-Substantive Revision Where Appropriate.
482.12.1 Where the Corporation has a Secretary or equivalent governance officer, the Secretary may certify that a restatement, consolidation, renumbering, technical correction, or non-substantive revision does not alter substantive meaning, if authorized by Board policy or resolution.
482.12.2 Secretary Certification shall identify the revision, basis, date, record reviewed, limitation, and repository version.
482.12.3 Secretary Certification shall not cure an actually substantive amendment, unauthorized revision, or legal defect requiring Board or member approval.
482.13 Board Ratification Where Doubt Exists.
482.13.1 Where doubt exists whether a revision is substantive, the matter shall be submitted to the Board for ratification, approval, amendment, or direction.
482.13.2 Board ratification may confirm non-substantive status, approve a formal amendment, require further review, reject the revision, or direct correction of affected records.
482.13.3 Ratification shall not validate conduct or revisions that cannot lawfully be ratified.
482.14 Restatement and Technical Correction Records.
482.14.1 The Corporation shall maintain Restatement and Technical Correction Records, including restatement purpose records, Consolidated Bylaw records, renumbering records, cross-reference correction records, typographical correction records, formatting correction records, defined-term harmonization records, controlled vocabulary harmonization records, citation or reference update records, schedule or appendix update records where non-substantive, no-substantive-change records, Secretary Certification records where appropriate, Board ratification records where doubt exists, repository records, supersession records, correction records, and archive records.
Section 483. Interpretation Principles
483.1 Interpretation Purpose.
483.1.1 These Interpretation Principles shall govern the reading, application, implementation, enforcement, correction, and amendment of these Bylaws.
483.1.2 These Bylaws shall be interpreted as a unified governance instrument for a United States nonprofit, nonstock, non-share, non-distributing, non-executing, public-benefit, public-good technical institution that stewards evidence, methods, observability methods, ontology, technical truth, public-good software, open technical baselines, verifiable compute and intelligence methods, public authority learning support, public-safe publication, safeguards, and Nexus coordination within a legally separated multi-institution ecosystem.
483.2 Public-Benefit Interpretation.
483.2.1 These Bylaws shall be interpreted to advance the Corporation’s public-benefit purposes and not to advance private inurement, impermissible private benefit, sponsor control, provider control, public authority capture, finance capture, enterprise capture, or public-good asset enclosure.
483.2.2 Where two lawful interpretations are available, the interpretation that better preserves public-benefit purpose, public trust, technical integrity, safeguards, and correctionability shall be preferred.
483.3 Nonprofit Character Interpretation.
483.3.1 These Bylaws shall be interpreted to preserve the Corporation’s nonprofit character, nonstock and non-share structure, non-distribution constraint, public-benefit orientation, fiscal integrity, and mission alignment.
483.3.2 No provision shall be interpreted to authorize distributions, equity-like rights, profit-sharing, private ownership of corporate surplus, private capture of public-good assets, or impermissible private benefit.
483.4 United States Legal Compliance Interpretation.
483.4.1 These Bylaws shall be interpreted consistently with applicable United States federal, state, territorial, local, and other legal requirements.
483.4.2 United States legal compliance includes corporate, nonprofit, tax, charitable solicitation where applicable, employment, civil rights, accessibility, privacy, cybersecurity, public authority, public records, lobbying, government ethics, grants, contracts, sanctions, export-control, competition, IP, insurance, litigation, and professional boundary compliance.
483.5 Governing State Law Interpretation.
483.5.1 These Bylaws shall be interpreted consistently with the Corporation’s governing state nonprofit corporation law and the certificate or articles.
483.5.2 Where state law provides mandatory requirements, such requirements shall control.
483.5.3 Where state law permits Bylaw flexibility, these Bylaws shall be interpreted according to their text, public-benefit purpose, and governance records.
483.6 Federal Law Compliance Interpretation.
483.6.1 These Bylaws shall be interpreted consistently with applicable federal law, including tax law, employment law, civil rights law, privacy and sectoral data law where applicable, cybersecurity obligations where applicable, sanctions, export controls, controlled technology restrictions, grants law, public funding requirements, public authority requirements, competition law, and regulated-activity boundaries.
483.6.2 No Bylaw provision shall be interpreted to authorize conduct prohibited by federal law.
483.7 Tax-Exempt or Tax-Exempt-Compatible Interpretation.
483.7.1 Where the Corporation has or seeks tax-exempt status, these Bylaws shall be interpreted to preserve tax-exempt or tax-exempt-compatible purposes, restrictions, public-benefit orientation, private inurement prohibitions, private benefit restrictions, unrelated business income controls, public support requirements where applicable, charitable solicitation compliance where applicable, and public inspection obligations where applicable.
483.7.2 Where tax status is not yet determined or is subject to change, these Bylaws shall be interpreted to preserve lawful nonprofit and public-benefit compatibility and avoid representations unsupported by tax records.
483.8 Non-Execution Interpretation.
483.8.1 These Bylaws shall be interpreted to preserve the Corporation as a non-executing public-good technical institution.
483.8.2 No provision shall be interpreted to make the Corporation an operator, public authority, emergency command body, public warning body, regulator, procurement authority, finance authority, certification body, recognition body, provider, national company, Project SPV, fund, lender, insurer, broker, dealer, investment adviser, rating agency, public infrastructure operator, or enterprise execution vehicle.
483.8.3 Evidence, methods, observability outputs, dashboards, maps, technical baselines, public-good software, proof receipts, AI outputs, Nexus interface outputs, and public authority learning materials shall be interpreted as support functions only within recorded scope.
483.9 GCRI / GRF / GRA Role-Separation Interpretation.
483.9.1 These Bylaws shall be interpreted to preserve the separate roles of The Global Centre for Risk and Innovation (GCRI), The Global Risks Forum (GRF), and The Global Risks Alliance (GRA).
483.9.2 GCRI US provisions shall be interpreted as evidence, methods, observability, ontology, technical truth, public-good software, open technical baseline, verifiable compute and intelligence methods, and public authority learning support provisions.
483.9.3 GRF recognition, standing, maturity, public legitimacy, registry, claims-discipline, stakeholder-formation, and public-facing legitimacy functions shall not be attributed to GCRI US unless adopted by competent record and lawful authority.
483.9.4 GRA finance-readiness, capital-readability, insurance-readiness, proof-pack, diligence translation, RNFD, NFD, UNFSD, capital-reader room, and regulated-perimeter functions shall not be attributed to GCRI US unless adopted by competent record and lawful authority.
483.10 Public-Good Stack and Enterprise Stack Separation Interpretation.
483.10.1 These Bylaws shall be interpreted consistently with the one rail / two stacks doctrine: one common public-good rail supporting distinct public-good and enterprise stack functions without collapse.
483.10.2 GCRI US shall be interpreted as part of the public-good stack and shall not be interpreted as an enterprise stack actor unless a specific activity is lawfully and expressly structured without violating nonprofit, non-execution, role-separation, or public-good constraints.
483.10.3 Enterprise stack actors, including national companies, state operating companies, regional companies, Project SPVs, providers, hosts, operators, asset owners, and capital actors, shall remain legally and functionally distinct from GCRI US.
483.11 Legal Separateness Interpretation.
483.11.1 These Bylaws shall be interpreted to preserve legal separateness among GCRI US, GCRI Canada, any other GCRI entity, GRF, GRA, Nexus Standards, protocol authorities, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, public authorities, national companies, Project SPVs, providers, hosts, sponsors, universities, laboratories, communities, and enterprise actors.
483.11.2 No coordination, shared mission, shared record, shared room, shared publication, shared technical asset, common terminology, common rail, or Nexus interface shall be interpreted as merger, agency, partnership, joint venture, shared liability, or authority to bind another entity unless a competent written instrument expressly provides otherwise.
483.12 Public Authority Boundary Interpretation.
483.12.1 These Bylaws shall be interpreted to preserve the Corporation’s public authority boundary.
483.12.2 No provision shall be interpreted to create public authority status, public authority delegation, official government decision-making, public warning authority, emergency command authority, regulatory authority, procurement authority, public finance approval, funding approval, grant approval, tax credit approval, public guarantee, sovereign obligation, public-private partnership, public health order authority, safety command authority, or public infrastructure command authority.
483.12.3 Public authority participation shall be interpreted according to capacity classification records and not by implication.
483.13 Finance, Securities, Insurance, Lending, Rating, Public Finance, Procurement, Certification, Recognition, Docket, Grid, Nexus-Compatible, Provider-Preference, and Professional Boundary Interpretation.
483.13.1 These Bylaws shall be interpreted to preserve all finance, securities, insurance, lending, rating, public finance, procurement, certification, recognition, Docket, Grid, Nexus-compatible, provider-preference, and professional boundaries.
483.13.2 No provision shall be interpreted as investment advice, securities offering, securities solicitation, broker-dealer activity, finder activity, underwriting, lending, banking, insurance placement, insurance underwriting, rating, credit opinion, public finance approval, public guarantee, public credit, procurement approval, approved vendor status, provider preference, certification, accreditation, conformance approval, compliance approval, recognition, standing, maturity determination, Docket approval, Grid guarantee, Nexus-compatible approval, legal advice, medical advice, engineering certification, accounting advice, tax advice, or professional opinion unless a competent authorized body separately provides such meaning.
483.14 Data / AI / Cyber / Privacy Interpretation.
483.14.1 These Bylaws shall be interpreted to preserve data governance, lawful basis, permission, consent where required, purpose limitation, data minimization, privacy by design, security by design, AI governance, human review, cybersecurity, incident response, breach assessment, cross-border transfer control, public authority data protection, health-sensitive data protection, rights-bearing data protection, cyber-sensitive and infrastructure-sensitive protection, and protected knowledge protection.
483.14.2 AI outputs, automated outputs, dashboards, maps, proof receipts, ledger entries, sensor signals, AI-RAN / O-RAN signals, DePIN records, digital twin outputs, model outputs, and compute outputs shall not be interpreted as authority without competent records and review.
483.15 Research Integrity, Evidence, Methods, Observability, Ontology, and Technical Truth Interpretation.
483.15.1 These Bylaws shall be interpreted to preserve research integrity, evidence integrity, methods integrity, observability methods discipline, ontology discipline, controlled vocabulary discipline, technical truth discipline, peer review where appropriate, uncertainty disclosure, limitation disclosure, source lineage, reproducibility where appropriate, replicability where appropriate, and correctionability.
483.15.2 Evidence shall be interpreted as record-based technical support and not as recognition, finance-readiness, certification, procurement approval, public authority action, public warning, emergency command, rating, or legal compliance approval.
483.16 Civil Rights, Accessibility, Community Safeguards, Tribal / Indigenous, Local, Territorial, Cultural, Environmental, and Protected Knowledge Interpretation.
483.16.1 These Bylaws shall be interpreted to preserve civil rights, accessibility, non-discrimination, community safeguards, vulnerable population protections, Tribal / Indigenous protocols, Indigenous data protections, Indigenous knowledge protections, local knowledge protections, territorial knowledge protections, cultural knowledge protections, environmental knowledge protections, ecological knowledge protections, sacred knowledge protections, public-safe mapping, protected participation, non-retaliation, and do-no-harm controls.
483.16.2 Where ambiguity exists concerning protected knowledge, public-safe mapping, consent, non-consent, attribution, non-attribution, withdrawal, restriction, or correction, the more protective lawful interpretation shall be preferred.
483.17 Validity-by-Record Interpretation.
483.17.1 These Bylaws shall be interpreted according to the doctrine of validity-by-record.
483.17.2 Material authority, status, approval, claim, reference, access, release, technical baseline status, software release status, AI-use status, controlled-room access, safeguards permission, public authority meaning, finance meaning, recognition meaning, certification meaning, procurement meaning, Docket meaning, Grid meaning, Nexus-compatible meaning, and correction status shall exist only to the extent supported by an Authoritative Record.
483.18 Correctionability Interpretation.
483.18.1 These Bylaws shall be interpreted to preserve the Corporation’s continuing duty and ability to correct, supersede, withdraw, retract, restrict, reclassify, clarify, annotate, notify, archive, and learn from errors, omissions, overclaims, outdated records, invalid records, unsafe outputs, boundary failures, data errors, AI errors, cybersecurity incidents, public authority misstatements, finance-boundary misstatements, protected knowledge concerns, and other defects.
483.18.2 No interpretation shall prevent lawful correction, public-safe correction, controlled correction, downstream correction, or record correction.
483.19 Most Protective Lawful Reading Where Ambiguity Exists.
483.19.1 Where ambiguity exists, the interpretation that most lawfully protects public-benefit purpose, nonprofit character, non-execution, role separation, legal separateness, public authority boundaries, finance and regulated-activity boundaries, data / AI / cyber / privacy safeguards, civil rights, accessibility, protected knowledge, public-safe publication, validity-by-record, correctionability, and institutional integrity shall be preferred.
483.19.2 The most protective lawful reading shall not be used to create powers, authorities, liabilities, restrictions, or obligations beyond law where such creation would be unlawful, but shall guide interpretation within lawful discretion.
483.20 Interpretation Records.
483.20.1 The Corporation shall maintain Interpretation Records, including interpretation purpose records, public-benefit interpretation records, nonprofit character interpretation records, United States legal compliance interpretation records, governing state law interpretation records, federal law compliance interpretation records, tax-exempt or tax-exempt-compatible interpretation records, non-execution interpretation records, GCRI / GRF / GRA role-separation interpretation records, public-good stack and enterprise stack separation interpretation records, legal separateness interpretation records, public authority boundary interpretation records, finance / securities / insurance / lending / rating / public finance / procurement / certification / recognition / Docket / Grid / Nexus-compatible / provider-preference / professional boundary interpretation records, Data / AI / Cyber / Privacy Interpretation records, research integrity / evidence / methods / observability / ontology / technical truth interpretation records, civil rights / accessibility / community safeguards / Tribal / Indigenous / local / territorial / cultural / environmental / protected knowledge interpretation records, validity-by-record interpretation records, correctionability interpretation records, most-protective-lawful-reading records, legal opinions, Board interpretations, officer interpretations within authority, correction records, and archive records.
Section 484. Governing Instrument Hierarchy and Conflict Rules
484.1 Governing Instrument Hierarchy Purpose.
484.1.1 Governing Instrument Hierarchy and Conflict Rules shall determine how the Corporation resolves conflicts among applicable law, the certificate or articles, these Bylaws, Board resolutions, member approvals where applicable, policies, schedules, operating instruments, contracts, grants, donor restrictions, Nexus instruments, GCRI Canada instruments, GRF instruments, GRA instruments, public authority instruments, and other external instruments.
484.1.2 The hierarchy shall preserve lawful governance, nonprofit character, legal separateness, public-benefit purpose, non-execution, role separation, public authority boundaries, finance boundaries, certification and recognition boundaries, procurement neutrality, data / AI / cyber / privacy safeguards, protected knowledge controls, validity-by-record, and correctionability.
484.2 Applicable Law Controls.
484.2.1 Applicable law shall control over any inconsistent provision of the certificate or articles, these Bylaws, policies, contracts, grants, Nexus instruments, operating instruments, or external materials.
484.2.2 Applicable law includes mandatory corporate law, nonprofit law, tax law, charitable solicitation law where applicable, employment law, civil rights law, accessibility law, privacy law, cybersecurity law, sanctions law, export-control law, competition law, public authority law, public records law where applicable, grants law, procurement law where applicable, IP law, insurance law, litigation obligations, and other binding legal requirements.
484.3 Certificate or Articles Control Where Legally Required.
484.3.1 The certificate or articles shall control over these Bylaws where applicable law requires such control or where the certificate or articles lawfully reserve, limit, or define powers.
484.3.2 These Bylaws shall be interpreted consistently with the certificate or articles wherever possible.
484.3.3 Any Bylaw provision inconsistent with the certificate or articles shall be narrowed, corrected, amended, or treated as inoperative to the extent of the inconsistency.
484.4 Bylaw Controls Over Policies, Schedules, Forms, Protocols, Operating Instruments, Templates, Guides, Playbooks, Summaries, Decks, Websites, and Public Materials.
484.4.1 These Bylaws shall control over policies, schedules, forms, protocols, operating instruments, templates, guides, playbooks, summaries, slides, decks, websites, public materials, training materials, AI summaries, translations, repository readme files, public notices, and unofficial explanations.
484.4.2 Subordinate instruments shall be interpreted consistently with these Bylaws and shall be corrected where inconsistent.
484.4.3 No subordinate instrument may amend, waive, override, or contradict these Bylaws unless adopted through a lawful Bylaw amendment.
484.5 Board Resolutions Control Within Lawful Scope.
484.5.1 Board resolutions shall control within their lawful scope and may adopt policies, approve actions, create committees, delegate authority, approve contracts, approve grants, approve amendments, approve corrections, and make governance determinations.
484.5.2 Board resolutions shall not override applicable law, the certificate or articles, or these Bylaws unless the resolution is itself a lawful Bylaw amendment or authorized implementation of these Bylaws.
484.5.3 Where Board resolutions conflict, the later resolution shall control to the extent lawful unless the earlier resolution is specifically reserved, contractually committed, legally required, or otherwise not subject to later modification without additional action.
484.6 Member Approvals Control Where Required.
484.6.1 Where member approval is required by applicable law, the certificate or articles, or these Bylaws, such approval shall control for the matter requiring member action.
484.6.2 Member approval shall not create authority beyond the matter approved and shall not override mandatory law, the certificate or articles, or limitations contained in these Bylaws.
484.6.3 Where the Corporation has no voting members, no member approval shall be implied.
484.7 Contracts Control Only Between Parties and Within Lawful Scope.
484.7.1 Contracts shall control only between the parties and only within lawful scope.
484.7.2 No contract shall amend these Bylaws, alter corporate governance, create public authority status, create finance-readiness authority, create recognition authority, create certification authority, create procurement authority, authorize private inurement, create impermissible private benefit, collapse role separation, or convert the Corporation into an execution vehicle unless lawful amendment and competent authority exist.
484.7.3 Contract provisions inconsistent with these Bylaws shall be interpreted narrowly, corrected, amended, terminated, or escalated where appropriate.
484.8 Grant and Donor Restrictions Control Only Within Lawful and Accepted Scope.
484.8.1 Grant, donor, funder, sponsor, and restricted support terms shall control only to the extent lawfully accepted, recorded, and consistent with nonprofit purpose, tax requirements, public-benefit character, private benefit restrictions, sponsor non-control, provider neutrality, public-safe publication, evidence independence, methods independence, and these Bylaws.
484.8.2 No grant, donation, sponsorship, in-kind support, cloud credit, compute credit, software credit, or other support shall control the Corporation’s evidence, methods, findings, corrections, public authority access, Nexus interface meaning, recognition meaning, finance-readiness meaning, certification meaning, procurement meaning, provider status, or public-safe publication except through lawful, recorded, public-benefit-compatible scope terms.
484.9 Nexus Constitutional Documents Guide Mission Alignment Where Not Inconsistent With Law, Articles, Certificate, or This Bylaw.
484.9.1 Nexus constitutional documents, doctrines, charters, memoranda, frameworks, protocols, and architecture instruments may guide mission alignment, role separation, public-good stack design, federation, interoperability, public-safe publication, correctionability, and Nexus coordination where not inconsistent with applicable law, the certificate or articles, or these Bylaws.
484.9.2 Nexus documents shall not override the Corporation’s governing law, certificate or articles, or these Bylaws unless adopted or incorporated through competent record and lawful authority.
484.9.3 Nexus alignment shall be interpreted as coordination and mission coherence, not merger, agency, partnership, shared liability, public authority delegation, finance-readiness, recognition, certification, procurement approval, public warning, emergency command, or enterprise execution.
484.10 GCRI Canada Instruments Do Not Govern GCRI US Unless Adopted or Incorporated by Record.
484.10.1 Instruments, bylaws, policies, charters, records, statements, approvals, or decisions of GCRI Canada shall not govern GCRI US unless adopted or incorporated by competent GCRI US record.
484.10.2 Coordination with GCRI Canada shall preserve legal separateness, jurisdictional distinction, cross-border data controls, public authority boundaries, Indigenous and protected knowledge safeguards, and correctionability.
484.11 GRF Instruments Do Not Govern GCRI US Evidence Functions Unless Adopted or Incorporated by Record.
484.11.1 Instruments, recognition decisions, maturity records, standing records, registry records, claims-discipline instruments, public legitimacy instruments, or public-facing GRF determinations of The Global Risks Forum (GRF) shall not govern GCRI US evidence functions unless adopted or incorporated by competent GCRI US record.
484.11.2 GCRI US may provide technical evidence, methods, observability, ontology, public-good software, and correction signals to GRF interfaces without becoming the GRF recognition authority.
484.12 GRA Instruments Do Not Govern GCRI US Evidence Functions Unless Adopted or Incorporated by Record.
484.12.1 Instruments, proof packs, finance-readiness records, capital-readability records, insurance-readiness records, diligence translation instruments, capital-reader room instruments, RNFD instruments, NFD instruments, UNFSD instruments, or regulated-perimeter instruments of The Global Risks Alliance (GRA) shall not govern GCRI US evidence functions unless adopted or incorporated by competent GCRI US record.
484.12.2 GCRI US may provide technical evidence, methods, observability, ontology, public-good software, technical baselines, proof receipt support, and correction signals to GRA interfaces without becoming a finance-readiness, capital-readability, insurance-readiness, investment, securities, lending, insurance, rating, public finance, or capital execution authority.
484.13 Public Authority Instruments Control Only Where Lawfully Applicable.
484.13.1 Public authority instruments, laws, regulations, grants, contracts, permits, data agreements, public records obligations, procurement rules, emergency management rules, public finance rules, or public authority instructions shall control only where lawfully applicable to the Corporation and within the instrument’s scope.
484.13.2 Public authority instruments shall not be interpreted to convert the Corporation into a public authority, regulator, emergency command body, public warning body, procurement authority, public finance authority, or public infrastructure operator unless applicable law expressly requires such legal effect.
484.13.3 Public authority instruments shall be reviewed for confidentiality, public records, FOIA, sunshine laws, open meetings, procurement integrity, public finance, privacy, cybersecurity, protected knowledge, and public-safe communication implications.
484.14 No External Instrument May Convert GCRI US Into a Regulator, Public Authority, Emergency Command Body, Public Warning Body, Procurement Authority, Finance Authority, Certification Body, Recognition Body, Provider, Operator, National Company, Project SPV, Fund, Lender, Insurer, Broker, Dealer, Investment Adviser, Rating Agency, or Enterprise Execution Vehicle.
484.14.1 No contract, grant, donor restriction, sponsor agreement, provider agreement, public authority instrument, Nexus instrument, GCRI Canada instrument, GRF instrument, GRA instrument, consortium instrument, technical baseline, policy, public statement, repository record, room charter, or external communication shall be interpreted to convert the Corporation into a regulator, public authority, emergency command body, public warning body, procurement authority, finance authority, certification body, recognition body, provider, operator, national company, Project SPV, fund, lender, insurer, broker, dealer, investment adviser, rating agency, or enterprise execution vehicle.
484.14.2 Any external instrument creating such ambiguity shall be rejected, revised, restricted, clarified, corrected, or escalated to the Board and counsel.
484.15 Conflict Escalation and Resolution.
484.15.1 Where conflict exists among governing instruments, the matter shall be escalated to the appropriate owner, officer, committee, counsel, or Board according to severity.
484.15.2 Conflict resolution shall consider applicable law, certificate or articles, these Bylaws, Board resolutions, member approvals where required, contracts, grants, public authority instruments, Nexus instruments, legal separateness, public-benefit purpose, non-execution, role separation, public authority boundaries, finance boundaries, certification and recognition boundaries, procurement neutrality, data / AI / cyber / privacy controls, safeguards, protected knowledge, validity-by-record, and correctionability.
484.15.3 Resolution may include interpretation record, legal opinion, Board action, amendment, contract amendment, grant notice, policy correction, public-safe correction, controlled correction, withdrawal, retraction, takedown, repository correction, or referral.
484.16 Governing Instrument Hierarchy Records.
484.16.1 The Corporation shall maintain Governing Instrument Hierarchy Records, including hierarchy purpose records, applicable law control records, certificate or articles control records, Bylaw control records, Board resolution control records, member approval records where required, contract scope records, grant and donor restriction records, Nexus constitutional document alignment records, GCRI Canada instrument records, GRF instrument records, GRA instrument records, public authority instrument records, no-external-conversion records, conflict escalation and resolution records, legal review records, Board action records, correction records, and archive records.
Section 485. Severability
485.1 Severability Purpose.
485.1.1 Severability shall preserve the maximum lawful effect of these Bylaws if any provision, clause, sentence, subsection, section, article, application, requirement, condition, or instrument incorporated by reference is determined to be invalid, unlawful, void, unenforceable, overbroad, inoperative, or otherwise incapable of full enforcement.
485.1.2 Severability shall support continuity of governance, public-benefit purpose, nonprofit character, non-execution, role separation, legal separateness, public authority boundaries, finance and regulated-activity boundaries, data / AI / cyber / privacy controls, safeguards, protected knowledge controls, validity-by-record, correctionability, and institutional resilience.
485.2 Invalid Provision.
485.2.1 If any provision of these Bylaws is determined by a court, regulator, public authority, arbitrator, competent legal authority, or Board legal review to be invalid, such invalidity shall affect only the invalid provision or application to the extent required.
485.2.2 The remaining provisions shall continue in effect to the fullest extent permitted by law.
485.2.3 Invalidity shall not be used to expand authority, create prohibited functions, eliminate safeguards, or collapse role separation.
485.3 Unenforceable Provision.
485.3.1 If any provision is determined to be unenforceable in whole or part, the provision shall be enforced to the maximum lawful extent and the unenforceable portion shall be severed, narrowed, reformed, or treated as inoperative to the extent required.
485.3.2 Unenforceability in one jurisdiction, circumstance, application, record class, actor class, public authority interface, finance interface, data context, or technology context shall not render the provision unenforceable in other lawful applications unless required by law.
485.4 Partially Invalid Provision.
485.4.1 Where a provision is partially invalid, the valid portion shall remain effective if it can be given lawful effect consistent with the Corporation’s public-benefit purpose and the structure of these Bylaws.
485.4.2 The Corporation shall interpret partially invalid provisions to preserve lawful duties, boundaries, restrictions, safeguards, records requirements, correction obligations, and governance controls.
485.5 Narrowing Construction.
485.5.1 Where a provision may be interpreted broadly or narrowly, and the broad interpretation would create invalidity, illegality, or unenforceability, the provision shall be construed narrowly to preserve validity.
485.5.2 Narrowing construction may apply to authority, access, publication, public authority references, finance-boundary statements, certification or recognition terms, procurement implications, data processing, AI use, cybersecurity controls, protected knowledge, technical assets, Nexus interfaces, indemnification, advancement, limitation of liability, and enforcement.
485.6 Reformation to Lawful Scope Where Permitted.
485.6.1 Where permitted by law, an invalid, overbroad, or unenforceable provision may be reformed to the maximum lawful scope that most closely reflects the original public-benefit intent, non-execution structure, role separation, legal separateness, safeguards, and boundary discipline.
485.6.2 Reformation shall not create authority, liability, member rights, public authority status, finance authority, certification authority, recognition authority, procurement authority, or enterprise execution authority not otherwise lawfully authorized.
485.6.3 Reformation may require Board review, legal review, amendment, public-safe notice, controlled notice, or repository correction.
485.7 Preservation of Remaining Provisions.
485.7.1 The invalidity, unenforceability, narrowing, or reformation of one provision shall not affect the validity or enforceability of the remaining provisions unless the remaining provisions cannot operate lawfully or coherently without the affected provision.
485.7.2 The Corporation shall continue to apply all remaining governance, records, public authority boundary, finance boundary, certification and recognition boundary, procurement neutrality, data / AI / cyber / privacy, safeguards, protected knowledge, Nexus coordination, correction, and enforcement provisions to the fullest lawful extent.
485.8 Preservation of Public-Benefit Purpose.
485.8.1 Severability shall be applied to preserve the Corporation’s public-benefit purpose.
485.8.2 No severability interpretation shall be used to convert the Corporation into a private-benefit vehicle, sponsor-controlled vehicle, provider-controlled vehicle, enterprise execution vehicle, public authority, finance authority, certification authority, recognition authority, procurement authority, or public warning body.
485.9 Preservation of Non-Execution.
485.9.1 If any provision affecting non-execution is invalid or unenforceable, the remaining Bylaws shall be interpreted to preserve the Corporation’s non-executing public-good technical role.
485.9.2 Severance of any phrase or clause shall not imply authorization for the Corporation to operate, command, finance, procure, certify, recognize, regulate, warn, insure, lend, rate, broker, underwrite, or execute projects unless lawful authority exists.
485.10 Preservation of Role Separation.
485.10.1 If any provision concerning role separation is invalid, unclear, or unenforceable, the Bylaws shall continue to preserve the separation among GCRI US, GCRI Canada, other GCRI entities, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, protocol authorities, public authorities, consortiums, national companies, Project SPVs, providers, sponsors, hosts, and enterprise stack actors.
485.10.2 Severability shall not be used to assign GRF recognition functions, GRA finance-readiness functions, Nexus Standards certification functions, public authority functions, or enterprise execution functions to GCRI US by implication.
485.11 Preservation of Public Authority Boundaries.
485.11.1 If any provision concerning public authority interfaces is invalid or unenforceable, the Bylaws shall continue to preserve non-delegation, non-endorsement, non-procurement, non-public-finance-approval, non-regulatory, non-public-warning, non-emergency-command, and public authority capacity classification rules.
485.11.2 No severed or invalidated provision shall be interpreted to create public authority status, official public decision authority, emergency command authority, public warning authority, procurement authority, public finance authority, regulatory authority, or sovereign obligation.
485.12 Preservation of Finance and Regulated-Activity Boundaries.
485.12.1 If any provision concerning finance, securities, insurance, lending, rating, public finance, procurement, certification, recognition, Docket, Grid, Nexus-compatible, provider-preference, or professional boundaries is invalid or unenforceable, the remaining Bylaws shall continue to prohibit unauthorized regulated activity and overclaim.
485.12.2 Severability shall not be used to create investment advice, securities activity, broker-dealer activity, finder activity, lending, insurance placement, underwriting, rating, public finance approval, public guarantee, public credit, procurement approval, certification, recognition, or professional advice authority.
485.13 Preservation of Data / AI / Cyber / Privacy Controls.
485.13.1 If any provision concerning data, AI, cybersecurity, privacy, verifiable compute, verifiable intelligence, controlled rooms, repositories, or technical security is invalid or unenforceable, the remaining Bylaws shall continue to preserve lawful basis, permission, consent, classification, access control, AI-use restrictions, human review, cybersecurity controls, privacy protections, incident response, breach assessment, record integrity, and correctionability.
485.13.2 Severability shall not be used to authorize unauthorized data processing, unauthorized AI training, unauthorized embeddings, unauthorized disclosure, insecure release, public authority data misuse, or protected knowledge misuse.
485.14 Preservation of Safeguards and Protected Knowledge Controls.
485.14.1 If any provision concerning civil rights, accessibility, community safeguards, Tribal / Indigenous interests, Indigenous data, Indigenous knowledge, local knowledge, territorial knowledge, cultural knowledge, environmental knowledge, protected knowledge, public-safe mapping, consent, non-consent, attribution, withdrawal, grievance, protected participation, or non-retaliation is invalid or unenforceable, the remaining Bylaws shall continue to preserve the most protective lawful safeguards.
485.14.2 Severability shall not be used to expose protected knowledge, disregard consent limits, bypass public-safe mapping controls, suppress grievances, permit retaliation, or weaken civil rights and accessibility obligations.
485.15 Board Review After Invalidity Determination.
485.15.1 After any determination that a Bylaw provision is invalid, unlawful, void, unenforceable, overbroad, or inoperative, the Board or an authorized committee shall review the determination and determine whether amendment, restatement, correction, notice, controlled notice, legal review, public-safe publication update, policy update, repository correction, or other action is required.
485.15.2 Board review shall assess affected provisions, affected records, affected policies, affected contracts, affected grants, affected public authority interfaces, affected finance-boundary statements, affected technical assets, affected safeguards, affected Nexus interfaces, affected publications, and downstream dependencies.
485.15.3 The Corporation shall preserve records of the invalidity determination and any corrective action.
485.16 Severability Records.
485.16.1 The Corporation shall maintain Severability Records, including severability purpose records, invalid provision records, unenforceable provision records, partially invalid provision records, narrowing construction records, reformation records where permitted, preservation of remaining provisions records, preservation of public-benefit purpose records, preservation of non-execution records, preservation of role separation records, preservation of public authority boundary records, preservation of finance and regulated-activity boundary records, preservation of data / AI / cyber / privacy control records, preservation of safeguards and protected knowledge control records, Board review records after invalidity determination, legal review records, amendment records, correction records, repository records, notices, and archive records.
Section 486. Localization and State / Territorial / Tribal / Local Adaptation
486.1 Localization Purpose.
486.1.1 Localization and State / Territorial / Tribal / Local Adaptation shall provide the lawful, record-based, public-benefit-compatible, and safeguards-preserving process by which the Corporation may adapt these Bylaws, policies, schedules, protocols, forms, registers, matrices, public-safe materials, public authority interface language, data / AI / cyber controls, research integrity controls, technical asset controls, and Nexus coordination instruments to applicable jurisdictional, legal, public authority, community, cultural, territorial, operational, and technical contexts.
486.1.2 Localization shall support the Corporation’s role as a United States public-good technical institution operating across all states and territories and interfacing, where lawful and appropriate, with federal, state, District of Columbia, territorial, Tribal / Indigenous, local, county, municipal, metropolitan, utility, port, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, infrastructure, university, laboratory, civil society, community, and North America interfaces.
486.1.3 Localization shall be used to increase lawful fit, public-safe comprehension, accessibility, community safeguards, technical interoperability, public authority boundary clarity, data protection, privacy compliance, AI governance, cybersecurity, and Nexus coordination, and shall not be used to weaken the Corporation’s public-benefit purpose, nonprofit character, non-execution doctrine, role separation, legal separateness, public authority boundaries, finance boundaries, validity-by-record, correctionability, provider neutrality, sponsor non-control, or safeguards.
486.2 United States Localization.
486.2.1 United States Localization shall ensure that the Corporation’s governance, records, programs, public-safe publications, data / AI / cyber controls, research practices, technical asset stewardship, public authority interfaces, and Nexus coordination are implemented consistently with United States federal, state, territorial, Tribal / Indigenous where applicable, and local legal requirements.
486.2.2 United States Localization shall recognize the Corporation’s United States legal seat and public-good role while preserving national interoperability across state, territorial, Tribal / Indigenous, local, sectoral, infrastructure, and North America interfaces.
486.2.3 United States Localization shall not imply federal designation, national public authority status, public warning authority, public finance authority, procurement authority, regulatory authority, emergency command authority, or sovereign mandate unless supported by competent public authority records.
486.3 Governing State Localization.
486.3.1 Governing State Localization shall ensure compliance with the nonprofit corporation law, corporate filing requirements, registered office requirements, registered agent requirements, director and officer rules, indemnification rules, advancement rules, limitation of liability rules, records rules, member rules where applicable, and charitable or tax-related requirements of the Corporation’s governing state.
486.3.2 Where governing state law imposes mandatory requirements, such requirements shall control over inconsistent subordinate instruments.
486.3.3 Governing State Localization shall be recorded in corporate books, compliance registers, legal review records, policy records, and repository records where material.
486.4 Foreign Qualification State Localization.
486.4.1 Where the Corporation registers, qualifies, solicits, contracts, employs, operates programs, holds events, receives grants, maintains offices, conducts public authority interfaces, or otherwise triggers legal obligations in a state other than its governing state, the Corporation shall review and record applicable foreign qualification, charitable solicitation, tax, employment, privacy, public authority, lobbying, grant, procurement, and records requirements.
486.4.2 Foreign Qualification State Localization shall not convert the Corporation into a state public authority, state procurement actor, state finance authority, public warning body, emergency command body, certification body, recognition body, provider, operator, or enterprise execution vehicle.
486.4.3 Where state-specific localization is required, the Corporation may adopt state addenda, state operating protocols, state public authority language, state privacy controls, state records procedures, or state-specific public-safe notices, provided they remain subordinate to applicable law, the certificate or articles, and these Bylaws.
486.5 District of Columbia Localization.
486.5.1 District of Columbia Localization shall apply where the Corporation engages with District of Columbia public authorities, public-sector institutions, public universities, public health bodies, emergency management bodies, public safety bodies, public works bodies, local infrastructure operators, community organizations, funders, grantors, or legal requirements.
486.5.2 District of Columbia Localization shall review charitable solicitation, lobbying, government ethics, public authority reference, public records, procurement-sensitive, public finance, privacy, accessibility, and public-safe publication considerations where applicable.
486.5.3 District of Columbia participation or interface shall not imply District approval, adoption, funding approval, procurement approval, public finance approval, regulatory approval, public warning, emergency command, or sovereign obligation without competent records.
486.6 Territorial Localization.
486.6.1 Territorial Localization shall apply to interfaces involving United States territories and other territorial contexts where the Corporation’s work may involve public authorities, communities, infrastructure, disaster risk, climate risk, public health, energy, water, food, telecom, cyber, ports, transportation, environmental systems, universities, laboratories, civil society, or public-safe observability.
486.6.2 Territorial Localization shall account for local law, federal law, territorial authority, language access, accessibility, public records considerations, public authority capacity, public health sensitivity, infrastructure sensitivity, community safeguards, Indigenous and local knowledge, climate and disaster vulnerability, and cross-border or regional coordination.
486.6.3 Territorial Localization shall preserve local dignity, lawful authority, public-safe mapping, protected knowledge controls, and public authority boundaries.
486.7 Tribal and Indigenous Interface Localization.
486.7.1 Tribal and Indigenous Interface Localization shall apply where the Corporation engages with Tribal governments, Indigenous governments, Indigenous communities, Indigenous institutions, Indigenous knowledge holders, Indigenous data, Indigenous knowledge, sacred knowledge, cultural knowledge, ecological knowledge, language materials, sensitive sites, or Indigenous-related public authority interfaces.
486.7.2 Such Localization shall require review of legal status, government-to-government considerations where applicable, data sovereignty, consent, non-consent, attribution, non-attribution, withdrawal, restriction, protected knowledge, public-safe mapping, AI-use restrictions, publication restrictions, transfer restrictions, community review, grievance pathways, and correction obligations.
486.7.3 The Corporation shall not infer Tribal / Indigenous approval, consent, endorsement, participation, knowledge permission, public-safe release permission, mapping permission, or data-use permission from attendance, public availability, historical publication, external citation, third-party possession, or technical accessibility.
486.7.4 Tribal and Indigenous Interface Localization shall be interpreted according to the most protective lawful reading where law, ethics, community protocols, public authority considerations, and protected knowledge safeguards overlap.
486.8 Local, County, Municipal, Metropolitan, Utility, Port, Public Health, Emergency Management, Public Safety, Public Works, Telecom, Energy, Water, Food, Cyber, and Infrastructure Localization.
486.8.1 Local and Infrastructure Localization shall apply where the Corporation interfaces with local, county, municipal, metropolitan, utility, port, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, transportation, housing, environmental, or other infrastructure systems.
486.8.2 Localization shall address public authority capacity classification, public infrastructure operator status, public records constraints, procurement sensitivity, emergency management boundaries, public warning boundaries, public health order boundaries, safety command boundaries, infrastructure-sensitive data, cyber-sensitive data, public-safe mapping, community safeguards, accessibility, civil rights, and controlled disclosure.
486.8.3 No local or infrastructure localization shall authorize the Corporation to direct operations, dispatch resources, issue alerts, order evacuations, approve procurement, regulate systems, certify infrastructure, issue ratings, provide finance-readiness, or assume public authority command.
486.9 North America Interface Localization.
486.9.1 North America Interface Localization shall apply where the Corporation coordinates with GCRI Canada, Canadian institutions, Mexican institutions where lawfully structured, Caribbean institutions where lawfully structured, Arctic interfaces where lawfully structured, Great Lakes interfaces, Atlantic interfaces, Pacific interfaces, Gulf interfaces, border interfaces, port interfaces, energy interfaces, water interfaces, food interfaces, public health interfaces, cyber interfaces, telecom interfaces, transportation interfaces, supply chain interfaces, disaster interfaces, and other cross-border or regional contexts.
486.9.2 North America Interface Localization shall address conflict-of-law review, privacy, AI, cybersecurity, sanctions, export-control, controlled technology, public authority capacity, Indigenous rights and protocols, protected knowledge, cross-border data transfer, localization requirements, public-safe publication, and legal separateness.
486.9.3 North America Interface Localization shall not create treaty authority, sovereign authority, intergovernmental decision authority, cross-border public warning authority, emergency command authority, procurement authority, public finance authority, regulatory authority, or sovereign obligation.
486.10 Privacy Localization.
486.10.1 Privacy Localization shall address federal, state, territorial, sectoral, health, education, children’s data, employment, public authority data, cross-border, and contractual privacy requirements applicable to the Corporation’s activities.
486.10.2 Privacy Localization shall include review of lawful basis, notice, consent, rights handling, data minimization, purpose limitation, retention, deletion, transfer, de-identification, aggregation, public-safe publication, AI-use restrictions, privacy impact assessments, data protection impact assessments where appropriate, and complaint pathways.
486.10.3 The most protective lawful privacy rule shall be applied where multiple privacy requirements apply and no less protective rule is legally required.
486.11 AI Governance Localization.
486.11.1 AI Governance Localization shall address jurisdiction-specific AI governance requirements, public authority expectations, sectoral rules, procurement rules, civil rights implications, accessibility obligations, privacy obligations, model risk requirements, human review, incident reporting, transparency, bias review, prompt-injection controls, red-team review, and AI-use restrictions.
486.11.2 AI Governance Localization shall preserve model register discipline, inference records, compute workload records, proof receipt limitations, human review, no autonomous public authority communication without authorization, no autonomous finance or certification action, no autonomous public-safe publication, and no AI output as public authority decision, public warning, emergency command, finance-readiness, recognition, certification, procurement approval, rating, or professional advice.
486.12 Cybersecurity Localization.
486.12.1 Cybersecurity Localization shall address jurisdiction-specific cybersecurity obligations, public authority expectations, sectoral security requirements, breach notification rules, critical infrastructure sensitivity, incident reporting, vendor security, repository security, secure development, vulnerability disclosure, and controlled disclosure.
486.12.2 Cybersecurity Localization shall protect cyber-sensitive information, infrastructure-sensitive information, public authority data, secrets, keys, tokens, credentials, repositories, proof receipts, dashboards, maps, AI systems, and controlled rooms.
486.12.3 Cybersecurity Localization shall not disclose vulnerabilities, infrastructure details, incident artifacts, system configurations, or threat intelligence beyond public-safe and authorized channels.
486.13 Research Ethics Localization.
486.13.1 Research Ethics Localization shall address jurisdictional, institutional, public authority, community, Tribal / Indigenous, university, laboratory, funder, human-subjects, public health, health-sensitive, youth, vulnerable population, environmental, protected knowledge, and rights-bearing data review requirements.
486.13.2 Research Ethics Localization shall determine whether IRB review, equivalent ethics review, community review, Tribal / Indigenous review, protected knowledge review, consent, non-consent, attribution, non-attribution, withdrawal, grievance, data minimization, or public-safe mapping review is required.
486.13.3 No research activity shall avoid ethics review by being labeled observability, technical support, dashboarding, public authority learning, AI analysis, or public-safe reporting where review is required.
486.14 Public Authority Boundary Localization.
486.14.1 Public Authority Boundary Localization shall adapt public authority capacity language, observer language, regulator-listening language, public finance reader language, emergency-learning language, public authority reference language, public authority room rules, public authority data controls, and public-safe publication limits to the applicable public-sector context.
486.14.2 Localization shall preserve no endorsement, no adoption, no funding approval, no procurement approval, no public finance approval, no regulatory approval, no public warning, no emergency command, no sovereign obligation, no public-private partnership, and no public authority decision unless competent public authority records expressly provide otherwise.
486.15 Public Records, FOIA, Sunshine, Open Meetings, Public Procurement, Grant, Lobbying, Government Ethics, and Public Sector Confidentiality Localization.
486.15.1 The Corporation shall localize public-sector compliance review where public records laws, FOIA, sunshine laws, open meetings laws, public procurement rules, grant rules, lobbying rules, government ethics rules, gift rules, honoraria rules, travel support rules, sponsored attendance rules, revolving-door rules, public official conflict rules, or public-sector confidentiality rules may apply.
486.15.2 Localization shall document whether Corporation records may become subject to public records requests through public authority possession, grant terms, contract terms, public authority rooms, or public-sector collaboration.
486.15.3 Localization shall preserve privilege, confidentiality, public-safe redaction, controlled disclosure, procurement neutrality, public authority boundary discipline, and public trust.
486.16 Civil Rights, Accessibility, Community Safeguards, Tribal / Indigenous, Local, Territorial, Cultural, Environmental, and Protected Knowledge Localization.
486.16.1 Safeguards Localization shall adapt civil rights, accessibility, non-discrimination, language access, disability access, community safeguards, Tribal / Indigenous protocols, local knowledge protections, territorial knowledge protections, cultural knowledge protections, environmental knowledge protections, ecological knowledge protections, sacred knowledge protections, sensitive site controls, public-safe mapping, grievance pathways, protected participation, non-retaliation, and do-no-harm review to the relevant context.
486.16.2 Localization shall not reduce safeguards to generic notice or symbolic consultation where the activity requires substantive review, permission, restriction, or correction.
486.16.3 Localization shall preserve the ability of affected persons, communities, and knowledge holders to raise concerns, challenge records, request correction, restrict attribution, request withdrawal where applicable, and access grievance pathways.
486.17 No Localization That Weakens Public-Benefit Purpose, Nonprofit Character, Non-Execution, Role Separation, Legal Separateness, Public Authority Boundaries, Finance Boundaries, Data / AI / Cyber Controls, Validity-by-Record, Correctionability, Provider Neutrality, Sponsor Non-Control, or Safeguards.
486.17.1 No localization, adaptation, addendum, operating protocol, public authority language, state supplement, territorial supplement, Tribal / Indigenous interface note, local protocol, North America coordination note, public-safe publication adaptation, technical profile, data rule, AI rule, cybersecurity rule, or safeguards instrument may weaken the Corporation’s public-benefit purpose, nonprofit character, non-execution, GCRI / GRF / GRA role separation, public-good stack and enterprise stack separation, legal separateness, public authority boundaries, finance boundaries, certification and recognition boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber / privacy controls, validity-by-record, correctionability, civil rights, accessibility, community safeguards, Tribal / Indigenous safeguards, protected knowledge controls, or public-safe publication obligations.
486.17.2 Any localization that creates such weakening, ambiguity, or conflict shall be rejected, revised, restricted, escalated, superseded, withdrawn, or corrected.
486.18 Localization Records.
486.18.1 The Corporation shall maintain Localization Records, including localization purpose records, United States Localization records, governing state localization records, foreign qualification state localization records, District of Columbia Localization records, Territorial Localization records, Tribal and Indigenous Interface Localization records, local / county / municipal / metropolitan / utility / port / public health / emergency management / public safety / public works / telecom / energy / water / food / cyber / infrastructure localization records, North America Interface Localization records, Privacy Localization records, AI Governance Localization records, Cybersecurity Localization records, Research Ethics Localization records, Public Authority Boundary Localization records, public records / FOIA / sunshine / open meetings / public procurement / grant / lobbying / government ethics / public-sector confidentiality localization records, civil rights / accessibility / community safeguards / Tribal / Indigenous / local / territorial / cultural / environmental / protected knowledge localization records, no-weakening review records, legal review records, public-safe review records, correction records, supersession records, and archive records.
Section 487. Schedules, Appendices, Policies, Protocols, Forms, Registers, Matrices, and Implementing Instruments
487.1 Implementing Instrument Purpose.
487.1.1 Implementing Instruments shall provide the operational, administrative, technical, procedural, records-based, and public-safe means by which the Corporation implements these Bylaws without altering their legal meaning or overriding their requirements.
487.1.2 Implementing Instruments may include schedules, appendices, policies, protocols, forms, registers, matrices, checklists, playbooks, controlled vocabulary instruments, public-safe notice libraries, technical profiles, delegation matrices, authority matrices, retention schedules, data classification schedules, risk taxonomies, clause libraries, repository templates, public authority language, finance-boundary language, safeguards templates, and other instruments approved or maintained under these Bylaws.
487.1.3 Implementing Instruments shall be versioned, owned, access-controlled, correctionable, and maintained in or linked to the Official Repository where material.
487.2 Board-Adopted Schedules.
487.2.1 The Board may adopt schedules to these Bylaws or to policies where schedules are needed to implement record classes, approval thresholds, reserved matters, authority matrices, retention rules, public authority language, data classifications, risk taxonomies, technical asset classes, safeguards requirements, or other governance requirements.
487.2.2 Board-adopted schedules shall identify authority, version, effective date, owner, custodian, review cycle, supersession path, correction path, and relationship to these Bylaws.
487.2.3 Schedules shall not amend the Bylaws unless adopted through the amendment procedure.
487.3 Appendices.
487.3.1 Appendices may provide explanatory, technical, operational, reference, or implementation detail supporting these Bylaws.
487.3.2 Appendices may include definitions, diagrams, tables, controlled terms, reference workflows, public-safe notice language, technical asset classifications, Nexus interface mappings, public authority capacity examples, and safeguards guidance.
487.3.3 Appendices shall be subordinate to the Bylaws unless expressly adopted as part of the Bylaw text by competent amendment.
487.4 Policies.
487.4.1 Policies shall establish required rules, controls, review pathways, approval requirements, restrictions, and implementation standards for matters within the Corporation’s operations.
487.4.2 Policies may cover conflicts, related-party transactions, financial controls, procurement and contracting, grant and support acceptance, document retention and legal holds, data governance, privacy, AI use, cybersecurity, incident response, research integrity, protected knowledge, public-safe publication, public authority boundaries, public-good software, repository governance, IP, contributor terms, secure release, safeguards, sanctions, export-control, competition, professional boundaries, Nexus coordination, legal separateness, and other matters.
487.4.3 Policies shall identify approving authority, owner, custodian, effective date, review cycle, enforcement mechanism, and correction path.
487.5 Protocols.
487.5.1 Protocols shall establish structured technical, governance, records, review, interface, publication, observability, repository, public authority, data, AI, cybersecurity, safeguards, or Nexus coordination processes.
487.5.2 Protocols may include observability protocols, public authority boundary protocols, controlled-room protocols, evidence protocols, method protocols, proof receipt protocols, public-safe mapping protocols, AI-use protocols, repository release protocols, incident protocols, correction protocols, and Nexus interface protocols.
487.5.3 Protocols shall not create public authority status, finance-readiness authority, certification authority, recognition authority, procurement authority, provider preference, public warning authority, emergency command authority, or execution authority unless such authority exists by competent external record and is lawfully within the Corporation’s role.
487.6 Forms.
487.6.1 Forms may be used to standardize record creation, approvals, notices, disclosures, consents, restrictions, reviews, access requests, public authority references, publication reviews, data processing, AI use, cybersecurity incidents, protected knowledge reviews, corrections, legal holds, and assurance reviews.
487.6.2 Forms shall be designed to capture required metadata, authority, approvals, classifications, limitations, review status, and correction paths.
487.6.3 Failure of a form to capture required Bylaw information shall not waive the requirement to create an adequate record.
487.7 Registers.
487.7.1 Registers shall provide structured record systems for corporate records, Board records, directors, officers, members where applicable, delegations, committees, conflicts, related parties, fiscal matters, grants, donations, sponsorships, contracts, procurement, research, evidence, methods, ontology, controlled vocabulary, data, processing, models, inference, compute workloads, cybersecurity, incidents, technical assets, repositories, publications, public authorities, Nexus interfaces, compliance, risk, corrections, safeguards, and protected knowledge.
487.7.2 Registers shall be assigned an owner and custodian and shall include record identifiers, status, access class, correction path, retention class, and related records where material.
487.7.3 Register entries shall not create authority beyond the underlying Authoritative Record.
487.8 Matrices.
487.8.1 Matrices may be used to express approval thresholds, authority levels, risk classifications, publication approval requirements, public authority capacity classifications, data classifications, AI risk classes, cybersecurity severity levels, incident severity levels, safeguards review triggers, technical asset release classes, and assurance review scopes.
487.8.2 Matrices shall be interpreted according to these Bylaws and the policy or record adopting them.
487.8.3 Where a matrix conflicts with these Bylaws or a Board resolution, the higher governing instrument shall control.
487.9 Checklists.
487.9.1 Checklists may be used to support consistent completion of reviews, approvals, filings, publications, data processing, AI use, cybersecurity, repository releases, technical baseline releases, public authority references, finance-boundary reviews, safeguards reviews, legal holds, closeouts, and corrections.
487.9.2 Checklists are implementation aids and shall not substitute for substantive review, judgment, approval, or record creation where required.
487.9.3 A completed checklist shall not create certification, public authority approval, finance-readiness, recognition, procurement approval, rating, public warning, or emergency command meaning.
487.10 Playbooks.
487.10.1 Playbooks may provide step-by-step implementation guidance for recurring workflows, including incident response, publication review, public authority engagement, controlled rooms, repository release, correction, legal holds, assurance, safeguards review, and Nexus coordination.
487.10.2 Playbooks shall remain subordinate to these Bylaws, applicable law, Board resolutions, and approved policies.
487.10.3 Playbooks shall include escalation instructions where legal, public authority, finance, data / AI / cyber, protected knowledge, safeguards, or public-safe risks arise.
487.11 Controlled Vocabulary Instruments.
487.11.1 Controlled Vocabulary Instruments shall define, restrict, approve, or prohibit terms used in governance records, public-safe publications, public authority references, finance-boundary statements, certification and recognition boundary statements, technical assets, Nexus interface records, dashboards, maps, and public claims.
487.11.2 Controlled Vocabulary Instruments shall prevent semantic drift and misuse of terms including verified, validated, recognized, finance-ready, capital-readable, insurance-ready, certified, accredited, compliant, approved, Nexus-compatible, Docket, Grid, official, public authority, public warning, emergency command, rating, bankable, investable, provider-preferred, and similar terms.
487.11.3 Controlled Vocabulary Instruments shall be updated when institutional meaning, law, Nexus interface design, public authority language, finance-boundary language, or public-safe language changes.
487.12 Public-Safe Notice Libraries.
487.12.1 Public-Safe Notice Libraries may contain approved language for non-reliance notices, limitation notices, public authority boundary notices, finance-boundary notices, certification and recognition boundary notices, procurement neutrality notices, public warning boundary notices, emergency command boundary notices, public-safe mapping notices, AI-use notices, dashboard notices, dataset notices, technical baseline notices, software release notices, correction notices, withdrawal notices, retraction notices, and archive notices.
487.12.2 Public-Safe Notice Libraries shall be reviewed for accuracy, accessibility, controlled vocabulary, public authority boundaries, finance boundaries, safeguards, and correctionability.
487.12.3 Use of notice language shall not cure an output that must be held, restricted, corrected, withdrawn, retracted, or taken down.
487.13 Technical Profiles.
487.13.1 Technical Profiles may define structured requirements, metadata, schemas, APIs, SDKs, interoperability interfaces, observability node profiles, Nexus Hub profiles, Nexus Cluster profiles, Nexus Hotspot profiles, Regional Cluster profiles, National Dense Nexus Core profiles, AI-RAN / O-RAN signal profiles, DePIN and DLT telemetry profiles, digital twin profiles, cyber telemetry profiles, proof receipt profiles, inference record profiles, compute workload profiles, and public-safe dashboard or map profiles.
487.13.2 Technical Profiles shall be versioned, validated where appropriate, documented, public-safe classified, and linked to applicable technical asset records.
487.13.3 Technical Profiles shall not be represented as certification, procurement mandate, public authority adoption, finance-readiness, recognition, rating, public warning, emergency command, or provider preference unless competent external authority separately provides such meaning.
487.14 Delegation Matrix.
487.14.1 The Delegation Matrix shall identify delegated authority by role, function, threshold, subject matter, limitation, duration, reporting requirement, escalation trigger, and revocation path.
487.14.2 The Delegation Matrix may cover spending, contracting, grants, publications, public authority references, data access, AI use, cybersecurity response, repository releases, controlled-room access, technical asset releases, corrections, legal holds, and public-safe notices.
487.14.3 Delegation shall be interpreted narrowly and shall not include authority to amend Bylaws, approve reserved matters, create public authority status, determine finance-readiness, issue recognition, certify, approve procurement, or execute enterprise functions unless expressly and lawfully authorized.
487.15 Authority Matrix.
487.15.1 The Authority Matrix shall identify who may approve, sign, publish, release, access, spend, contract, hire, terminate, refer, correct, restrict, hold, escalate, archive, certify records, or communicate externally by role, threshold, risk class, and subject matter.
487.15.2 The Authority Matrix shall distinguish Board authority, officer authority, committee authority, advisory authority, technical maintainer authority, publication authority, public authority reference authority, data authority, AI authority, cybersecurity authority, repository authority, controlled-room authority, safeguards authority, and assurance authority.
487.15.3 Authority Matrix entries shall be supported by underlying authority and shall not create substantive authority where none exists.
487.16 Record Retention Schedule.
487.16.1 The Record Retention Schedule shall identify retention periods, permanent record classes, long-term record classes, minimum retention requirements, conditional retention requirements, legal hold rules, archival rules, deletion eligibility, secure disposal requirements, and exceptions.
487.16.2 The Record Retention Schedule shall address corporate, Board, fiscal, tax, grant, contract, research, evidence, data, AI, cybersecurity, privacy, public authority, publication, technical asset, safeguards, Nexus coordination, incident, legal hold, assurance, and correction records.
487.16.3 The Record Retention Schedule shall be subordinate to legal holds, litigation holds, regulatory holds, investigation holds, public authority holds, funder holds, cybersecurity or data incident holds, research integrity holds, publication challenge holds, technical asset holds, and protected knowledge holds.
487.17 Data Classification Schedule.
487.17.1 The Data Classification Schedule shall define data classes, access requirements, handling requirements, AI-use restrictions, publication restrictions, transfer restrictions, retention rules, deletion rules, and incident response rules for public data, public-safe data, internal data, confidential data, restricted data, rights-bearing data, personal information, sensitive personal information, health-sensitive data, public authority data, cyber-sensitive data, infrastructure-sensitive data, finance-sensitive data, commercially sensitive data, research-sensitive data, community-protected data, Tribal / Indigenous data, protected knowledge data, controlled technology data, export-controlled data, sanctions-sensitive data, children’s or youth data where applicable, and archived data.
487.17.2 The Data Classification Schedule shall be applied consistently with privacy, cybersecurity, public authority, protected knowledge, safeguards, and public-safe publication requirements.
487.18 Risk Taxonomy.
487.18.1 The Risk Taxonomy shall define risk classes, severity levels, likelihood levels, impact levels, control categories, escalation triggers, incident categories, assurance categories, public-safe risks, boundary risks, data / AI / cyber risks, public authority risks, finance risks, certification and recognition risks, procurement risks, protected knowledge risks, and Nexus coordination risks.
487.18.2 The Risk Taxonomy shall support consistent risk registers, issue registers, control registers, incident triage, assurance reviews, MEAIR reviews, publication review, and enforcement.
487.19 No Implementing Instrument May Override Law, Articles, Certificate, or Bylaw.
487.19.1 No Implementing Instrument may override, amend, waive, contradict, narrow, expand, or evade applicable law, the certificate or articles, these Bylaws, Board reserved powers, member approval requirements where applicable, or mandatory legal duties.
487.19.2 Any Implementing Instrument inconsistent with applicable law, the certificate or articles, or these Bylaws shall be corrected, superseded, withdrawn, restricted, or escalated.
487.19.3 No Implementing Instrument may convert the Corporation into a regulator, public authority, emergency command body, public warning body, procurement authority, finance authority, certification body, recognition body, provider, operator, national company, Project SPV, fund, lender, insurer, broker, dealer, investment adviser, rating agency, or enterprise execution vehicle.
487.20 Implementing Instrument Versioning, Approval, Supersession, Withdrawal, and Archive.
487.20.1 Implementing Instruments shall be versioned, approved, superseded, withdrawn, corrected, and archived according to their authority records.
487.20.2 Each material Implementing Instrument shall identify owner, custodian, version, effective date, approving authority, review cycle, classification, public-safe status, supersession path, withdrawal path, correction path, and archive status.
487.20.3 Superseded, withdrawn, retired, or archived Implementing Instruments shall not be used as current unless re-entry is approved by competent record.
487.21 Implementing Instrument Records.
487.21.1 The Corporation shall maintain Implementing Instrument Records, including implementing instrument purpose records, Board-adopted schedule records, appendix records, policy records, protocol records, form records, register records, matrix records, checklist records, playbook records, controlled vocabulary instrument records, public-safe notice library records, technical profile records, delegation matrix records, authority matrix records, Record Retention Schedule records, Data Classification Schedule records, Risk Taxonomy records, no-override records, versioning records, approval records, supersession records, withdrawal records, archive records, correction records, and repository records.
Section 488. Supersession of Prior Instruments and Outdated Materials
488.1 Supersession Purpose.
488.1.1 Supersession shall establish the authoritative transition from prior, outdated, incomplete, inconsistent, draft, obsolete, superseded, or inaccurate instruments and materials to current, approved, record-based, and public-safe instruments.
488.1.2 Supersession shall protect the Corporation against reliance on outdated Bylaws, outdated charters, outdated policies, outdated methods, outdated technical baselines, outdated public-good software releases, outdated Nexus interface descriptions, outdated public authority references, outdated finance language, outdated recognition language, outdated certification language, outdated procurement language, outdated Docket or Grid language, outdated Nexus-compatible language, outdated public materials, and outdated summaries.
488.1.3 Supersession shall preserve historical traceability, correctionability, public-safe transparency, and technical memory without allowing outdated materials to create current authority.
488.2 Supersession of Prior Bylaws Where Approved.
488.2.1 Upon lawful adoption of these Bylaws or any restated Bylaws, prior Bylaws shall be superseded to the extent stated in the approval record.
488.2.2 Superseded Bylaws shall be archived and shall not govern current Corporation action except where needed to interpret historical actions, legal rights, obligations, or records from the period in which such Bylaws were effective.
488.2.3 Supersession of prior Bylaws shall not impair vested rights, legal holds, indemnification rights, advancement rights, limitation of liability provisions, contract obligations, grant obligations, or legal duties except to the extent permitted by law and approved records.
488.3 Supersession of Prior Charters Where Applicable.
488.3.1 Prior committee charters, council charters, advisory charters, working group charters, room charters, public authority room charters, Nexus interface charters, technical asset charters, or project charters shall be superseded only by competent authority.
488.3.2 Supersession records shall identify the superseded charter, superseding charter, affected body, continuing authority if any, discontinued authority, membership status, records transfer, access changes, and closeout obligations.
488.3.3 Superseded charters shall not be used to claim current authority, public authority approval, finance-readiness, recognition, certification, procurement approval, provider preference, public warning, emergency command, or execution authority.
488.4 Supersession of Outdated Public Materials.
488.4.1 Outdated public materials, including websites, decks, presentations, public summaries, GitBook pages, media statements, newsletters, social media posts, event materials, speeches, public notices, public-safe summaries, diagrams, infographics, FAQs, and public repository descriptions, shall be superseded, corrected, archived, or withdrawn where they no longer accurately reflect current Bylaws, policies, role separation, public authority boundaries, finance boundaries, technical asset status, safeguards, or Nexus interfaces.
488.4.2 Supersession of public materials shall include public-safe correction where continued public reliance is reasonably foreseeable.
488.4.3 Archived public materials shall include current-status limitations where appropriate.
488.5 Supersession of Outdated Policies.
488.5.1 Outdated policies shall be superseded by current approved policies according to the relevant approval record.
488.5.2 Supersession records shall identify prior policy, new policy, effective date, owner, affected procedures, affected training, affected records, affected systems, and transition requirements.
488.5.3 Superseded policies shall remain available for historical interpretation and legal holds where needed.
488.6 Supersession of Outdated Methods.
488.6.1 Outdated methods, including research methods, evidence methods, observability methods, ontology methods, Truth Engine methods, AI evaluation methods, dashboard methods, mapping methods, benchmark methods, technical baseline methods, and Nexus interface methods, shall be superseded where revised methods are adopted.
488.6.2 Method supersession shall identify affected outputs, affected evidence, affected datasets, affected models, affected dashboards, affected maps, affected public-safe publications, affected public authority learning materials, affected GRF inputs, affected GRA inputs, affected Docket inputs, affected Grid inputs, and affected Nexus interfaces.
488.6.3 Method supersession shall trigger downstream dependency review where prior method status materially affects current reliance.
488.7 Supersession of Outdated Technical Baselines.
488.7.1 Outdated technical baselines shall be superseded by current approved versions according to Technical Asset Records and repository notice.
488.7.2 Supersession records shall identify baseline version, effective date, review basis, changed requirements, known limitations, migration guidance, compatibility implications, public-safe status, and archive status.
488.7.3 Superseded technical baselines shall not be represented as current, official, Nexus-supporting, public-safe, certification-equivalent, procurement-mandating, public authority-adopted, finance-ready, recognized, or provider-preferential.
488.8 Supersession of Outdated Public-Good Software Releases.
488.8.1 Outdated public-good software releases, APIs, SDKs, schemas, dashboards, tools, repositories, evaluation harnesses, proof receipt tools, and other technical artifacts shall be superseded through Release Records and repository notices.
488.8.2 Supersession records shall identify release version, superseding version, security implications, vulnerability implications, dependency implications, migration notes, deprecation status, support status, known issues, known limitations, rollback guidance, and public-safe notice requirements.
488.8.3 Superseded releases shall not be represented as current, supported, secure, public-safe, official, Nexus-compatible, certified, recognized, finance-ready, procurement-approved, or public authority-adopted except according to their recorded status.
488.9 Supersession of Outdated Nexus Interface Descriptions.
488.9.1 Outdated Nexus interface descriptions shall be superseded where they no longer accurately describe coordination with GCRI Canada, other GCRI entities, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, protocol authorities, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, public authorities, enterprise stack actors, or other Nexus participants.
488.9.2 Supersession shall preserve legal separateness, role separation, non-execution, public-good stack and enterprise stack separation, public authority boundaries, finance boundaries, recognition boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, and correctionability.
488.10 Supersession of Outdated Public Authority References.
488.10.1 Outdated public authority references shall be superseded or corrected where they misstate capacity, title, agency, participation, authority, approval, adoption, funding, procurement, regulatory status, public finance status, emergency management status, public warning status, data contribution, quote permission, name-use approval, logo-use approval, or event participation.
488.10.2 Supersession may require direct notice to affected public authorities, public-safe correction, controlled correction, takedown, or archive annotation.
488.10.3 Public authority reference supersession shall preserve no endorsement, no adoption, no funding approval, no procurement approval, no regulatory approval, no public finance approval, no public warning, no emergency command, and no sovereign obligation.
488.11 Supersession of Outdated Finance, Recognition, Certification, Procurement, Docket, Grid, or Nexus-Compatible Language.
488.11.1 Outdated language concerning finance-readiness, capital-readability, insurance-readiness, proof packs, diligence translation, RNFD, NFD, UNFSD, recognition, standing, maturity, public legitimacy, certification, accreditation, conformance, compliance, procurement approval, approved vendor status, provider preference, Docket, Grid, Nexus-compatible status, rating, public finance, public warning, emergency command, or professional boundaries shall be superseded or corrected where inaccurate or boundary-defective.
488.11.2 Supersession shall coordinate with GRA where finance meaning is implicated, GRF where recognition meaning is implicated, Nexus Standards or protocol authorities where standards meaning is implicated, and public authorities where public authority meaning is implicated.
488.12 Supersession Notice.
488.12.1 Supersession Notices shall identify the superseded instrument or material, superseding instrument or material, effective date, authority, reason, affected dependencies, public-safe status, access class, archive location, and any required action by users or stakeholders.
488.12.2 Supersession Notices may be public, public-safe, internal, controlled, repository-based, funder-facing, public authority-facing, Nexus-facing, community-facing, or restricted depending on classification.
488.13 Public-Safe Correction Where Needed.
488.13.1 Public-Safe Correction shall be issued where superseded materials may mislead public audiences, public authorities, funders, sponsors, providers, communities, media, capital readers, users, contributors, or Nexus participants if not corrected.
488.13.2 Public-Safe Correction shall avoid overdisclosure of privileged, confidential, cyber-sensitive, infrastructure-sensitive, public authority restricted, finance-sensitive, protected knowledge, personal, health-sensitive, controlled technology, export-controlled, sanctions-sensitive, or investigation-sensitive information.
488.14 Controlled Correction Where Needed.
488.14.1 Controlled Correction shall be used where affected recipients need correction but public correction would create confidentiality, privilege, privacy, cybersecurity, infrastructure, public authority, finance-sensitive, protected knowledge, legal, or public-safe risks.
488.14.2 Controlled Correction shall identify recipients, scope, restrictions, further disclosure limits, AI-use restrictions, retention requirements, and correction path.
488.15 Archive of Superseded Materials.
488.15.1 Superseded materials shall be archived where legal, governance, historical, technical memory, audit, reliance, legal hold, or correctionability value exists.
488.15.2 Archived superseded materials shall be marked as superseded, withdrawn, retracted, archived, or otherwise not current, as applicable.
488.15.3 Archive access shall be controlled according to classification and legal requirements.
488.16 Supersession Records.
488.16.1 The Corporation shall maintain Supersession Records, including supersession purpose records, prior Bylaw supersession records, prior charter supersession records, outdated public material supersession records, outdated policy supersession records, outdated method supersession records, outdated technical baseline supersession records, outdated public-good software release supersession records, outdated Nexus interface description supersession records, outdated public authority reference supersession records, outdated finance / recognition / certification / procurement / Docket / Grid / Nexus-compatible language supersession records, Supersession Notices, Public-Safe Correction records, Controlled Correction records, archive records, dependency review records, and correction records.
Section 489. Transitional Implementation
489.1 Transitional Implementation Purpose.
489.1.1 Transitional Implementation shall provide the orderly, lawful, record-based, risk-prioritized, and public-benefit-compatible process by which the Corporation implements these Bylaws after adoption, restatement, or major amendment.
489.1.2 Transitional Implementation shall allow the Corporation to build required governance systems, records systems, policies, registers, protocols, training, public authority boundary controls, data / AI / cyber controls, research integrity controls, technical asset controls, fiscal controls, conflicts controls, Nexus coordination instruments, and public materials review without weakening the immediate legal effect of these Bylaws.
489.1.3 During transition, the Corporation shall prioritize high-risk controls involving legal existence, Board authority, officer authority, fiscal controls, conflicts, public authority boundaries, finance boundaries, data / AI / cyber / privacy, public-safe publication, protected knowledge, repository access, legal holds, and correctionability.
489.2 Initial Implementation Period.
489.2.1 The Board may establish an Initial Implementation Period after adoption or major restatement of these Bylaws.
489.2.2 The Initial Implementation Period shall identify priority actions, responsible owners, timelines, interim controls, required Board actions, policy adoption sequence, register setup, training schedule, public materials review, technical asset review, Nexus coordination review, and closeout criteria.
489.2.3 The Initial Implementation Period shall not suspend the Corporation’s duties under applicable law, fiduciary obligations, public authority boundary rules, finance-boundary rules, data / AI / cyber / privacy rules, safeguards, legal holds, or correction requirements.
489.3 Interim Governance Authority.
489.3.1 During transition, interim governance authority may be exercised by the Board, authorized officers, initial officers, committees, counsel, records custodians, or other authorized persons according to applicable law, the certificate or articles, these Bylaws, Board resolutions, and authority matrices.
489.3.2 Interim authority shall be narrowly construed, recorded, time-limited where appropriate, and subject to Board ratification where required.
489.3.3 Interim authority shall not create informal amendment, execution authority, public authority status, finance-readiness authority, recognition authority, certification authority, procurement authority, or provider preference.
489.4 Initial Board Actions.
489.4.1 Initial Board Actions may include adoption or confirmation of Bylaws, appointment of officers, adoption of priority policies, creation of committees, approval of authority matrices, approval of bank and fiscal controls, approval of records systems, approval of insurance review, approval of public authority boundary protocol, approval of data / AI / cyber controls, approval of research integrity controls, approval of technical asset controls, and approval of Nexus coordination instruments.
489.4.2 Initial Board Actions shall be recorded through minutes, resolutions, written consents, authority records, repository records, and implementation records.
489.5 Initial Officer Appointments.
489.5.1 Initial Officer Appointments shall identify officer title, appointment authority, duties, authority, limitations, reporting line, signature authority, fiscal authority, records duties, public authority communication authority, publication authority if any, data / AI / cyber authority if any, and term or review date.
489.5.2 Initial officers shall not exercise authority beyond recorded authority and shall ensure that transitional actions are recorded, reviewable, and correctionable.
489.6 Initial Committee Formation.
489.6.1 Initial Committee Formation may include creation of governance, audit or finance, compliance, risk, research integrity, data / AI / cyber, public-safe publication, technical asset, safeguards, public authority boundary, Nexus coordination, or other committees.
489.6.2 Each committee shall have a charter identifying purpose, authority, limitations, membership, chair, reporting obligations, records requirements, conflicts, confidentiality, public authority boundaries, finance boundaries, data / AI / cyber responsibilities, safeguards responsibilities, and sunset or review date.
489.7 Initial Policy Adoption.
489.7.1 Initial Policy Adoption shall prioritize policies necessary to operationalize these Bylaws and control high-risk activities.
489.7.2 Initial policies may be adopted in final, interim, pilot, controlled, or provisional form, provided that their status, authority, limitations, review date, and correction path are recorded.
489.7.3 Interim policies shall be reviewed and either finalized, amended, superseded, or withdrawn during transition closeout.
489.8 Initial Registers.
489.8.1 The Corporation shall establish initial registers required for governance, records, compliance, risk, conflicts, related parties, fiscal controls, grants, contracts, research, evidence, data, models, cybersecurity, incidents, technical assets, repositories, publications, public authorities, Nexus interfaces, safeguards, and corrections.
489.8.2 Initial registers may begin with minimum metadata and shall be progressively completed according to risk, reliance, and operational priority.
489.8.3 Missing or incomplete register entries shall be tracked and corrected.
489.9 Initial Record System.
489.9.1 The Corporation shall establish an initial record system, including Official Repository, repository custodian, version control, access controls, metadata rules, retention schedule, legal hold process, correction process, archive process, and backup process.
489.9.2 The initial record system may be staged, provided that authoritative records are protected, traceable, retrievable, and not confused with drafts or unofficial copies.
489.10 Initial Public Authority Boundary Protocol.
489.10.1 The Corporation shall adopt an Initial Public Authority Boundary Protocol before engaging in material public authority-facing activities.
489.10.2 The Protocol shall address capacity classification, official capacity records, observer status, regulator-listening status, public finance reader status, emergency-learning status, public authority references, public authority data, public authority rooms, public records considerations, procurement neutrality, public finance boundaries, regulatory boundaries, public warning boundaries, emergency command boundaries, and correction obligations.
489.11 Initial Data / AI / Cyber / Privacy Controls.
489.11.1 The Corporation shall adopt initial controls for data governance, privacy, AI use, cybersecurity, model registers, inference records, compute workload records, proof receipt limitations, access controls, public authority data, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, protected knowledge data, incident response, breach assessment, vendor security, repository security, and controlled rooms.
489.11.2 Initial controls shall restrict unauthorized AI training, fine-tuning, embeddings, retrieval use, model improvement, external sharing, public-safe publication, and data transfer until authority is recorded.
489.12 Initial Research Integrity Controls.
489.12.1 The Corporation shall adopt initial controls for research protocols, evidence records, method records, source lineage, ethics review, IRB or equivalent review where required, community review, Tribal / Indigenous review, protected knowledge review, peer review where appropriate, conflicts, sponsor independence, provider independence, limitation disclosure, uncertainty disclosure, and correctionability.
489.12.2 Initial research outputs shall not be published or used for material public claims without record support and public-safe review.
489.13 Initial Public-Good Software and Technical Asset Controls.
489.13.1 The Corporation shall adopt initial controls for public-good software, technical asset registers, repositories, contributor terms, IP ownership, licensing, secure development, dependency review, SBOMs where appropriate, vulnerability handling, secrets management, release governance, technical baselines, schemas, APIs, SDKs, technical profiles, forks, compatibility claims, Nexus-compatible claims, and takedown processes.
489.13.2 Technical assets created or released before full controls are operational shall be reviewed, classified, corrected, superseded, restricted, archived, or re-released according to Technical Asset Records.
489.14 Initial Fiscal Controls.
489.14.1 The Corporation shall adopt initial fiscal controls for bank accounts, budget approval, spending authority, dual controls where appropriate, expense reimbursement, procurement, contracting, grants, donations, sponsorships, in-kind support, restricted funds, accounting records, tax records, audit readiness, and financial reporting.
489.14.2 Fiscal controls shall prevent private inurement, impermissible private benefit, sponsor control, provider preference, procurement advantage, and unsupported finance-facing claims.
489.15 Initial Conflicts and Related-Party Controls.
489.15.1 The Corporation shall adopt initial conflict of interest and related-party controls covering directors, officers, employees, contractors, fellows, advisors, volunteers, contributors, maintainers, committee members, council members, sponsors, providers, funders, donors, hosts, partners, universities, laboratories, public authority participants, and Nexus participants where relevant.
489.15.2 Initial controls shall require disclosure, review, recusal, mitigation, approval, records, and correction where conflicts or related-party matters arise.
489.16 Initial Nexus Coordination Instruments.
489.16.1 The Corporation may adopt initial Nexus coordination instruments governing interfaces with GCRI Canada, other GCRI entities, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, protocol authorities, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, public authorities, and enterprise stack actors.
489.16.2 Initial Nexus coordination instruments shall preserve legal separateness, no merger, no agency, no partnership, no joint venture, no shared liability, role separation, public-good stack and enterprise stack separation, public authority boundaries, finance boundaries, recognition boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, and correctionability.
489.17 Initial Public Materials Review.
489.17.1 The Corporation shall review initial public materials, including website content, public decks, GitBook pages, public summaries, media materials, public authority references, sponsor references, provider references, technical asset descriptions, Nexus descriptions, public-safe publications, dashboards, maps, repository readme files, and social media.
489.17.2 Initial Public Materials Review shall correct outdated, unsupported, overclaimed, misleading, public authority-confusing, finance-confusing, certification-confusing, recognition-confusing, procurement-confusing, provider-preferential, public-warning-confusing, inaccessible, or safeguards-defective materials.
489.18 Initial Training.
489.18.1 The Corporation shall provide initial training to directors, officers, staff, contractors, fellows, advisors, volunteers, contributors, maintainers, committee members, council members, working group participants, panel participants, public authority interface participants, and other relevant persons according to role and risk.
489.18.2 Initial Training shall cover public-benefit purpose, nonprofit character, non-execution, role separation, public authority boundaries, finance boundaries, procurement neutrality, certification and recognition boundaries, validity-by-record, correctionability, records systems, confidentiality, privilege, data / AI / cyber controls, public-safe publication, safeguards, protected knowledge, legal holds, and impact claims.
489.19 Transition Closeout.
489.19.1 Transition Closeout shall occur when the Board or authorized body determines that initial implementation actions have been completed, superseded, deferred with controls, or transferred to ordinary governance.
489.19.2 Transition Closeout shall include review of initial Board actions, officer appointments, committee formation, policy adoption, registers, record systems, public authority boundary protocol, data / AI / cyber controls, research integrity controls, technical asset controls, fiscal controls, conflict controls, Nexus coordination instruments, public materials review, training, open issues, risk register entries, corrective actions, and remaining obligations.
489.20 Transitional Implementation Records.
489.20.1 The Corporation shall maintain Transitional Implementation Records, including transitional implementation purpose records, Initial Implementation Period records, Interim Governance Authority records, Initial Board Action records, Initial Officer Appointment records, Initial Committee Formation records, Initial Policy Adoption records, Initial Register records, Initial Record System records, Initial Public Authority Boundary Protocol records, Initial Data / AI / Cyber / Privacy Control records, Initial Research Integrity Control records, Initial Public-Good Software and Technical Asset Control records, Initial Fiscal Control records, Initial Conflicts and Related-Party Control records, Initial Nexus Coordination Instrument records, Initial Public Materials Review records, Initial Training records, Transition Closeout records, open issue records, corrective action records, and archive records.
Section 490. Priority Policies for Initial Adoption
490.1 Conflict of Interest Policy.
490.1.1 The Corporation shall prioritize adoption of a Conflict of Interest Policy governing disclosure, review, recusal, mitigation, approval, monitoring, correction, and records for conflicts involving directors, officers, employees, contractors, fellows, advisors, volunteers, contributors, maintainers, committee members, council members, public authority participants, sponsors, providers, funders, donors, hosts, partners, vendors, universities, laboratories, communities, Nexus participants, and related parties.
490.1.2 The Conflict of Interest Policy shall preserve fiduciary integrity, research independence, evidence integrity, public-good independence, sponsor non-control, provider neutrality, procurement neutrality, public authority boundary discipline, finance-boundary discipline, safeguards, and public trust.
490.2 Related-Party Transaction Policy.
490.2.1 The Corporation shall prioritize adoption of a Related-Party Transaction Policy governing identification, disclosure, review, approval, fairness, comparability, documentation, recusals, Board oversight, tax compliance, private benefit review, private inurement prevention, and correction of related-party transactions.
490.2.2 Related-party transactions shall not be used to transfer public-good assets, create sponsor capture, create provider preference, create procurement advantage, weaken role separation, or create impermissible private benefit.
490.3 Financial Controls Policy.
490.3.1 The Corporation shall prioritize adoption of a Financial Controls Policy governing budgeting, accounting, banking, spending authority, approvals, dual controls where appropriate, segregation of duties where practicable, reimbursements, payroll, restricted funds, reserves, reporting, audit readiness, tax records, fraud prevention, and financial closeout.
490.3.2 Financial controls shall support nonprofit compliance, public-benefit use of resources, restricted fund compliance, grant compliance, donor trust, sponsor non-control, provider neutrality, and Board oversight.
490.4 Procurement and Contracting Policy.
490.4.1 The Corporation shall prioritize adoption of a Procurement and Contracting Policy governing vendor selection, contracting authority, conflicts, related-party review, competition where appropriate, procurement records, data protection terms, AI-use restrictions, cybersecurity terms, IP terms, public authority restrictions, protected knowledge restrictions, termination rights, and contract closeout.
490.4.2 The Policy shall preserve procurement neutrality and shall not create public procurement authority, approved vendor status, provider preference, sponsor procurement advantage, public authority procurement approval, or certification meaning.
490.5 Grant, Donation, Sponsorship, In-Kind, and Public-Good Support Acceptance Policy.
490.5.1 The Corporation shall prioritize adoption of a Support Acceptance Policy governing grants, donations, sponsorships, restricted gifts, in-kind support, cloud credits, compute credits, software credits, equipment, services, hosted resources, public-good support, and other contributions.
490.5.2 The Policy shall require mission alignment, legal review where appropriate, restrictions review, conflict review, private benefit review, sponsor non-control, provider neutrality, public authority reference review, data / AI / cyber review, publication independence, correction independence, and records.
490.5.3 Support shall not purchase outcomes, control evidence, control methods, control findings, create public authority access, create provider preference, create procurement advantage, create finance-readiness, create recognition, create certification, or create public legitimacy by implication.
490.6 Document Retention and Legal Hold Policy.
490.6.1 The Corporation shall prioritize adoption of a Document Retention and Legal Hold Policy governing record classes, retention periods, permanent records, archival, deletion, secure disposal, legal holds, litigation holds, regulatory holds, investigation holds, public authority holds, funder holds, cybersecurity or data incident holds, research integrity holds, publication challenge holds, technical asset holds, protected knowledge holds, hold notices, custodian duties, and release of holds.
490.6.2 The Policy shall preserve validity-by-record, correctionability, evidence integrity, public-safe publication, legal compliance, privilege, confidentiality, protected knowledge, and technical memory.
490.7 Data Governance Policy.
490.7.1 The Corporation shall prioritize adoption of a Data Governance Policy governing data inventory, data registers, processing registers, data owners, data custodians, data stewards, lawful basis, authority, permission, consent, classification, access, minimization, purpose limitation, quality, provenance, retention, deletion, transfer, public authority data, rights-bearing data, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, community-protected data, Tribal / Indigenous data, protected knowledge data, and correction.
490.7.2 The Policy shall prohibit unauthorized reuse for AI training, fine-tuning, embeddings, publication, finance-readiness inputs, provider development, sponsor benefit, or external sharing.
490.8 Privacy Policy.
490.8.1 The Corporation shall prioritize adoption of a Privacy Policy governing notice, consent where required, rights handling, privacy by design, privacy impact assessment where required or appropriate, data protection impact assessment where required or appropriate, complaint and appeal pathways where applicable, cross-border privacy, sectoral privacy, public authority data privacy, health privacy, children’s data, education data, employment data, and breach assessment.
490.8.2 The Privacy Policy shall be public-safe where public-facing and shall not overpromise legal status, certification, compliance approval, or public authority approval.
490.9 AI-Use and Model Governance Policy.
490.9.1 The Corporation shall prioritize adoption of an AI-Use and Model Governance Policy governing AI system inventory, model register, model risk classification, AI-use approval, model owners, model custodians, data steward interface, AI vendor review, AI procurement review, AI public-safe review, human review, inference records, compute workload records, proof receipts, AI incident response, training restrictions, fine-tuning restrictions, embedding restrictions, retrieval restrictions, model improvement restrictions, leakage review, bias review, hallucination review, prompt-injection review, and agentic AI controls.
490.9.2 The Policy shall prohibit autonomous public authority communication, autonomous finance action, autonomous procurement action, autonomous certification action, autonomous recognition action, autonomous public warning, autonomous emergency command, and autonomous public-safe publication without required authority and human review.
490.10 Cybersecurity Policy.
490.10.1 The Corporation shall prioritize adoption of a Cybersecurity Policy governing asset inventory, identity and access management, secure configuration, endpoint security, network security, cloud security, application security, repository security, data security, logging and monitoring, vulnerability management, incident response, backup, disaster recovery, business continuity, vendor security, training, and control testing.
490.10.2 The Policy shall protect public authority data, rights-bearing data, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, protected knowledge, repositories, secrets, keys, tokens, credentials, technical assets, dashboards, maps, AI systems, proof receipt tools, and controlled rooms.
490.11 Incident Response Policy.
490.11.1 The Corporation shall prioritize adoption of an Incident Response Policy governing incident taxonomy, intake, Case ID assignment, triage, severity classification, containment, access restriction, credential rotation, system isolation, publication holds, repository holds, data holds, AI holds, controlled-room holds, investigation, legal and privilege review, notification assessment, correction, remediation, root cause review, closeout, and records.
490.11.2 The Policy shall cover data incidents, privacy incidents, personal information breaches, public authority data incidents, health-sensitive data incidents, cyber-sensitive incidents, infrastructure-sensitive incidents, protected knowledge incidents, AI incidents, hallucination incidents, unsafe output incidents, bias incidents, civil rights incidents, data leakage, unauthorized agentic action, cybersecurity incidents, repository incidents, supply-chain incidents, vulnerability incidents, service disruption, and public-safe publication incidents.
490.12 Research Integrity Policy.
490.12.1 The Corporation shall prioritize adoption of a Research Integrity Policy governing research purpose, evidence purpose, methods purpose, observability purpose, ontology purpose, technical truth purpose, public-benefit R&D, research agenda independence, research ethics, evidence doctrine, source records, dataset records, method records, peer review where appropriate, limitation disclosure, uncertainty disclosure, sponsor and provider independence, research misconduct, evidence challenge, method challenge, correction, supersession, withdrawal, retraction, archive, and technical memory.
490.12.2 The Policy shall prohibit fabrication, falsification, plagiarism, improper source omission, unsupported confidence claims, suppression of material limitations, misleading public-safe summaries, sponsor distortion, provider distortion, and AI-generated fabrication.
490.13 Human-Subjects, Community Review, Tribal / Indigenous, and Protected Knowledge Review Policy Where Applicable.
490.13.1 The Corporation shall prioritize adoption of a Human-Subjects, Community Review, Tribal / Indigenous, and Protected Knowledge Review Policy where applicable to its activities.
490.13.2 The Policy shall govern IRB or equivalent review where required or appropriate, public health-sensitive review, youth and vulnerable population review, rights-bearing data review, community review, Tribal / Indigenous review, local knowledge review, territorial knowledge review, cultural knowledge review, environmental knowledge review, consent, non-consent, attribution, non-attribution, withdrawal, restriction, grievance pathways, data minimization, do-no-harm review, and public-safe mapping.
490.14 Public-Safe Publication and Claims Policy.
490.14.1 The Corporation shall prioritize adoption of a Public-Safe Publication and Claims Policy governing publication authority, approval matrices, publication classes, access classes, claims substantiation, controlled vocabulary, technical claims, public authority references, finance-boundary references, certification / procurement / recognition / Docket / Grid / Nexus-compatible references, sponsor and provider references, dashboards, maps, AI-generated or AI-assisted content, media relations, digital channels, public-safe release, disclaimers, non-reliance, corrections, withdrawals, retractions, takedowns, and records.
490.14.2 The Policy shall ensure no publication or public claim is treated as certification, recognition, finance-readiness, procurement approval, rating, public authority endorsement, public warning, emergency command, or professional advice without competent authority.
490.15 Public Authority Boundary Protocol.
490.15.1 The Corporation shall prioritize adoption of a Public Authority Boundary Protocol governing public authority definitions, covered public-sector interfaces, participation principles, capacity classification, official capacity records, observer status, regulator-listening status, public finance reader status, emergency-management participation, public authority data contributions, public authority references, public authority rooms, public grants, lobbying, government ethics, public records, FOIA, sunshine, open meetings, procurement neutrality, regulatory boundaries, public warning boundaries, emergency command boundaries, and correction.
490.15.2 The Protocol shall preserve non-delegation, non-endorsement, non-procurement, non-public-finance-approval, non-regulatory, non-public-warning, non-emergency-command, and no sovereign obligation principles.
490.16 Public-Good Software, Repository, IP, Contributor, and Secure Release Policy.
490.16.1 The Corporation shall prioritize adoption of a Public-Good Software, Repository, IP, Contributor, and Secure Release Policy governing technical asset registers, public-good software, open technical baselines, reference architectures, schemas, APIs, SDKs, profiles, IP ownership, copyright, patent, trademark, trade secret, data rights, model rights, contributor terms, contributor license agreements, assignments, moral rights, attribution, maintainer duties, licensing, restricted assets, secure development, repository governance, supply-chain assurance, SBOMs, provenance, artifact signing, vulnerabilities, secrets, release governance, forks, compatibility claims, commercial use boundaries, anti-enclosure, marks, datasets, models, benchmarks, takedown, and enforcement.
490.16.2 The Policy shall preserve public-good technical asset stewardship without creating certification, procurement approval, public authority adoption, provider preference, finance-readiness, recognition, rating, public warning, emergency command, or operational guarantee.
490.17 Safeguards, Civil Rights, Accessibility, Grievance, Protected Participation, and Non-Retaliation Policy.
490.17.1 The Corporation shall prioritize adoption of a Safeguards, Civil Rights, Accessibility, Grievance, Protected Participation, and Non-Retaliation Policy governing civil rights, accessibility, non-discrimination, language access, disability access, community safeguards, Tribal / Indigenous interfaces, protected knowledge, public-safe mapping, consent, non-consent, attribution, withdrawal, restriction, correction, grievance pathways, remedy, protected participation, whistleblowing, non-retaliation, do-no-harm review, and safeguards stop-the-line authority.
490.17.2 The Policy shall protect good-faith reporters, challengers, reviewers, affected persons, communities, knowledge holders, and participants from retaliation.
490.18 Sanctions, Export-Control, Controlled Technology, Competition, Professional Boundary, and Regulatory-Perimeter Policy.
490.18.1 The Corporation shall prioritize adoption of a Sanctions, Export-Control, Controlled Technology, Competition, Professional Boundary, and Regulatory-Perimeter Policy governing sanctions screening, export-control review, controlled technology review, cross-border technical assistance, restricted technical materials, competition and antitrust review, public authority rooms, provider rooms, capital-reader rooms, professional boundary review, regulated finance perimeter review, securities perimeter review, insurance perimeter review, lending perimeter review, rating perimeter review, public finance perimeter review, public procurement boundary review, and legal compliance approval boundaries.
490.18.2 The Policy shall prevent unauthorized regulated activity and preserve the Corporation’s non-executing public-good technical role.
490.19 Nexus Coordination and Legal Separateness Policy.
490.19.1 The Corporation shall prioritize adoption of a Nexus Coordination and Legal Separateness Policy governing coordination with GCRI Canada, other GCRI entities, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, protocol authorities, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, global, regional, national, state, territorial, Tribal, local, and sector consortiums, public authorities, national companies, Project SPVs, providers, hosts, sponsors, universities, laboratories, communities, civil society, media, and enterprise stack actors.
490.19.2 The Policy shall preserve no merger, no agency, no partnership, no joint venture, no shared liability, no implied authority to bind another entity, public-good stack and enterprise stack separation, role separation, non-execution, public authority boundaries, finance boundaries, recognition boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, validity-by-record, and correctionability.
490.20 Priority Policy Adoption Records.
490.20.1 The Corporation shall maintain Priority Policy Adoption Records, including Conflict of Interest Policy records, Related-Party Transaction Policy records, Financial Controls Policy records, Procurement and Contracting Policy records, Grant / Donation / Sponsorship / In-Kind / Public-Good Support Acceptance Policy records, Document Retention and Legal Hold Policy records, Data Governance Policy records, Privacy Policy records, AI-Use and Model Governance Policy records, Cybersecurity Policy records, Incident Response Policy records, Research Integrity Policy records, Human-Subjects / Community Review / Tribal / Indigenous / Protected Knowledge Review Policy records where applicable, Public-Safe Publication and Claims Policy records, Public Authority Boundary Protocol records, Public-Good Software / Repository / IP / Contributor / Secure Release Policy records, Safeguards / Civil Rights / Accessibility / Grievance / Protected Participation / Non-Retaliation Policy records, Sanctions / Export-Control / Controlled Technology / Competition / Professional Boundary / Regulatory-Perimeter Policy records, Nexus Coordination and Legal Separateness Policy records, adoption records, interim policy records, version records, review records, training records, supersession records, correction records, and archive records.
Section 491. Transitional Public Materials, Name Use, Claims, and Interface Correction
491.1 Transitional Public Materials Review.
491.1.1 During any initial implementation period, restatement period, major amendment period, institutional transition, Nexus coordination transition, public-facing launch period, repository migration, technical asset release transition, or other period in which legacy materials may remain in circulation, the Corporation shall conduct a Transitional Public Materials Review to identify, classify, correct, supersede, withdraw, retract, take down, archive, or publicly clarify public-facing, semi-public, controlled, proposal-facing, funder-facing, sponsor-facing, provider-facing, public authority-facing, Nexus-facing, community-facing, and media-facing materials.
491.1.2 Transitional Public Materials Review shall apply to websites, GitBook pages, public knowledge-base pages, decks, one-pagers, whitepapers, proposals, grant applications, sponsorship materials, donor materials, public authority references, provider references, finance-readiness references, certification references, recognition references, Docket references, Grid references, Nexus-compatible claims, technical baseline claims, software claims, repository descriptions, dashboards, maps, public-safe summaries, social media, newsletters, press materials, event materials, media statements, public notices, training materials, and any other material that could create public meaning.
491.1.3 Transitional Public Materials Review shall be records-based and shall preserve public-benefit purpose, nonprofit character, non-execution, GCRI / GRF / GRA role separation, GCRI US / GCRI Canada distinction, public-good stack and enterprise stack separation, legal separateness, public authority boundaries, finance boundaries, certification and recognition boundaries, procurement neutrality, provider neutrality, sponsor non-control, public-safe publication, data / AI / cyber / privacy controls, safeguards, protected knowledge controls, validity-by-record, and correctionability.
491.2 Website Review.
491.2.1 The Corporation shall review all websites, public pages, GitBook pages, knowledge-base pages, landing pages, program pages, publication pages, dashboard pages, map pages, repository pages, contributor pages, event pages, sponsor acknowledgment pages, partner pages, public authority reference pages, and archived public pages for accuracy, authority, current status, public-safe language, accessibility, privacy, and boundary discipline.
491.2.2 Website Review shall identify unsupported claims, outdated institutional descriptions, incorrect name use, unclear legal status, public authority overclaims, finance overclaims, certification or recognition overclaims, procurement implications, provider preference, sponsor control implication, unsupported Nexus-compatible claims, outdated technical baseline claims, outdated software release claims, data / AI / cyber risks, public-safe mapping risks, protected knowledge exposure, and missing correction notices.
491.2.3 Website materials requiring correction shall be revised, annotated, superseded, withdrawn, redirected, restricted, archived, or taken down according to risk and authority.
491.3 Deck Review.
491.3.1 The Corporation shall review decks, slide presentations, pitch materials, briefing materials, public authority briefing decks, sponsor decks, donor decks, provider decks, capital-reader decks, conference decks, Academy decks, technical decks, Nexus coordination decks, and internal decks used externally or likely to be circulated.
491.3.2 Deck Review shall examine titles, subtitles, logos, institutional names, public authority references, sponsor references, provider references, diagrams, architecture descriptions, impact claims, finance language, recognition language, certification language, procurement language, Docket language, Grid language, Nexus-compatible language, public-safe disclaimers, and correction notices.
491.3.3 No deck shall be used externally during transition unless it is current, approved for its audience, public-safe or controlled as applicable, and supported by records.
491.4 Proposal Review.
491.4.1 The Corporation shall review proposals, statements of work, concept notes, letters of interest, expressions of interest, partnership proposals, consortium proposals, public authority proposals, technical proposals, university proposals, laboratory proposals, provider-facing proposals, host-facing proposals, and Nexus interface proposals.
491.4.2 Proposal Review shall determine whether the proposal accurately states the Corporation’s role, legal status, nonprofit character, non-executing posture, public-good function, evidence and methods role, public authority boundaries, finance boundaries, certification and recognition boundaries, procurement neutrality, sponsor non-control, provider neutrality, data / AI / cyber obligations, safeguards, technical asset status, and Nexus coordination relationships.
491.4.3 Proposals shall not represent the Corporation as an executor, operator, public authority, finance-readiness authority, certification body, recognition body, procurement authority, provider, fund, lender, insurer, broker, rating agency, national company, Project SPV, public warning body, emergency command body, or enterprise execution vehicle.
491.5 Grant Application Review.
491.5.1 The Corporation shall review grant applications, cooperative agreement applications, public grant applications, foundation applications, research funding applications, in-kind support applications, cloud-credit applications, compute-credit applications, software-credit applications, and public-good support applications for accuracy and boundary compliance.
491.5.2 Grant Application Review shall examine mission statements, organizational descriptions, program descriptions, budgets, deliverables, impact claims, public authority references, sponsor references, provider references, data rights, IP rights, publication terms, public-safe limitations, evidence and methods independence, research integrity, public authority boundaries, finance boundaries, procurement neutrality, and restricted fund requirements.
491.5.3 Grant applications shall not promise outcomes, public authority approvals, public finance approvals, finance-readiness, recognition, certification, procurement results, provider preference, public warnings, emergency commands, or operational delivery beyond the Corporation’s lawful non-executing role.
491.6 Sponsor and Donor Material Review.
491.6.1 The Corporation shall review sponsor materials, donor materials, funder materials, acknowledgment materials, recognition materials, sponsorship packages, donor decks, public support descriptions, naming opportunities, in-kind support descriptions, hosted-resource descriptions, and public-good support language.
491.6.2 Sponsor and Donor Material Review shall ensure that materials do not imply sponsor control, donor control, funder control, purchase of outcomes, provider preference, procurement advantage, public authority access, public authority endorsement, recognition, finance-readiness, certification, technical approval, public-safe publication control, research finding control, evidence control, methods control, or correction control.
491.6.3 Sponsor and donor acknowledgment shall be accurate, proportionate, non-misleading, public-safe, and supported by contribution records.
491.7 Public Authority Reference Review.
491.7.1 The Corporation shall review all public authority references in transitional materials, including names, logos, titles, quotes, attendance references, photographs, recordings, event references, data contribution statements, grant references, room references, observer references, regulator-listening references, public finance reader references, emergency-learning references, and public infrastructure operator references.
491.7.2 Public Authority Reference Review shall verify capacity classification, official capacity records, approval to use names or logos, quote permission, data contribution permission, confidentiality, public records considerations, public-safe language, non-endorsement language, non-adoption language, non-funding-approval language, non-procurement-approval language, non-regulatory-approval language, non-public-finance-approval language, non-public-warning language, and non-emergency-command language.
491.7.3 Unsupported public authority references shall be corrected, restricted, removed, withdrawn, or directly clarified to the affected authority where appropriate.
491.8 Provider Reference Review.
491.8.1 The Corporation shall review provider references, vendor references, technology provider references, cloud provider references, AI provider references, cybersecurity provider references, repository provider references, hosting provider references, software vendor references, implementation partner references, and enterprise stack actor references.
491.8.2 Provider Reference Review shall ensure that no provider is described as preferred, approved, certified, recognized, finance-ready, procurement-ready, Nexus-compatible, public authority-approved, officially selected, or technically endorsed unless competent records authorize the exact claim.
491.8.3 Provider participation, sponsorship, contribution, technical support, repository contribution, room participation, or event participation shall not create provider preference or procurement advantage.
491.9 Finance-Readiness Reference Review.
491.9.1 The Corporation shall review transitional references to finance-readiness, capital-readability, insurance-readiness, bankability, investability, financeability, proof packs, diligence translation, RNFD, NFD, UNFSD, capital-reader rooms, public finance, grants, tax credits, public guarantees, public credit, ratings, investment, lending, insurance, securities, and capital execution.
491.9.2 Finance-Readiness Reference Review shall verify GRA role separation, non-reliance language, regulated-perimeter review where required, public authority finance boundary language, sponsor and funder independence, and absence of investment advice, securities solicitation, brokerage, underwriting, lending, insurance placement, rating, or public finance approval.
491.9.3 GCRI US technical evidence, methods, observability outputs, public-good software, proof receipts, dashboards, maps, or technical baselines shall not be described as finance-readiness determinations.
491.10 Certification, Recognition, Docket, Grid, and Nexus-Compatible Claim Review.
491.10.1 The Corporation shall review all transitional references to certification, accreditation, conformance, compliance, approval, recognition, standing, maturity, registry status, public legitimacy, GRF status, Docket status, Grid status, Nexus-compatible status, standards support, protocol authority, and technical validation.
491.10.2 The Review shall verify whether the claim is supported by competent records from the proper authority, including The Global Risks Forum (GRF) for recognition-related meaning, The Global Risks Alliance (GRA) for finance-related meaning, Nexus Standards or protocol authority for standards or protocol meaning, and competent public authority records for public authority meaning.
491.10.3 No transitional material shall imply that GCRI US certifies, recognizes, approves procurement, grants Docket or Grid status, issues Nexus-compatible status, or provides maturity standing unless expressly and lawfully authorized by competent record.
491.11 Technical Baseline and Software Claim Review.
491.11.1 The Corporation shall review technical baseline claims, software claims, repository claims, API claims, SDK claims, schema claims, dashboard claims, map claims, dataset claims, model claims, benchmark claims, evaluation harness claims, proof receipt claims, and public-good technical asset claims.
491.11.2 Technical Baseline and Software Claim Review shall verify asset identity, owner, custodian, version, release status, license, security status, vulnerability status, dependency status, public-safe status, known limitations, support status, deprecation status, archive status, and correction path.
491.11.3 Technical baseline or software references shall not imply certification, procurement mandate, public authority adoption, provider preference, finance-readiness, recognition, rating, public warning, emergency command, or operational guarantee.
491.12 GCRI US / GCRI Canada Distinction Review.
491.12.1 The Corporation shall review transitional materials to ensure that GCRI US and GCRI Canada are accurately distinguished by legal identity, jurisdiction, role, authority, records, public authority interfaces, data controls, public-safe materials, and Nexus coordination functions.
491.12.2 No material shall imply that GCRI US governs GCRI Canada, that GCRI Canada governs GCRI US, that either entity is liable for the other by implication, that one entity’s records automatically authorize the other, or that cross-border coordination creates merger, agency, partnership, joint venture, shared liability, public authority delegation, finance-readiness, recognition, certification, procurement approval, public warning, or emergency command.
491.13 GCRI / GRF / GRA Role-Separation Review.
491.13.1 The Corporation shall review transitional materials for accurate separation among The Global Centre for Risk and Innovation (GCRI), The Global Risks Forum (GRF), and The Global Risks Alliance (GRA).
491.13.2 Materials shall describe GCRI US as an evidence, methods, observability methods, ontology, technical truth, public-good R&D, public-good software, open technical baseline, verifiable compute and intelligence methods, Nexus Truth Engine methods, Nexus Observatory methods, and public authority learning support institution.
491.13.3 Materials shall not assign GRF recognition, standing, maturity, public legitimacy, registry, stakeholder-formation, or public-facing legitimacy stewardship functions to GCRI US.
491.13.4 Materials shall not assign GRA finance-readiness, capital-readability, insurance-readiness, proof-pack, diligence translation, public finance, capital-reader, investment, lending, insurance, rating, or capital execution functions to GCRI US.
491.14 Nexus Coordination Description Review.
491.14.1 The Corporation shall review descriptions of Nexus Network, Nexus Universe, Nexus Observatory, Nexus Standards, Nexus Risk Management, Nexus Truth Engine, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, global consortiums, regional consortiums, national consortiums, national companies, Project SPVs, providers, hosts, sponsors, public authorities, capital actors, universities, laboratories, communities, and enterprise stack actors.
491.14.2 Nexus Coordination Description Review shall ensure descriptions preserve one rail / two stacks discipline, legal separateness, role separation, non-execution, public-good stack integrity, enterprise stack boundaries, public authority boundaries, finance boundaries, recognition boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, validity-by-record, and correctionability.
491.14.3 Nexus descriptions shall not imply that GCRI US owns, governs, controls, finances, certifies, recognizes, procures, executes, operates, warns, commands, or legally binds the entire Nexus ecosystem.
491.15 Public-Safe Disclaimer Review.
491.15.1 The Corporation shall review transitional public materials for appropriate public-safe disclaimers, limitation statements, non-reliance language, public authority boundary language, finance-boundary language, certification and recognition boundary language, procurement neutrality language, public warning boundary language, emergency command boundary language, AI-use limitation language, dashboard limitation language, map limitation language, software limitation language, technical baseline limitation language, and correction pathways.
491.15.2 Disclaimers shall be accurate, accessible, readable, context-appropriate, and not buried where reliance risk is foreseeable.
491.15.3 Disclaimer language shall not be used to preserve materials that must be corrected, withdrawn, retracted, restricted, or taken down.
491.16 Correction, Supersession, Withdrawal, Retraction, Takedown, or Public Clarification Where Required.
491.16.1 Where Transitional Public Materials Review identifies materials that are inaccurate, unsupported, outdated, overclaimed, public authority-confusing, finance-confusing, certification-confusing, recognition-confusing, procurement-confusing, provider-preferential, public-warning-confusing, emergency-command-confusing, data-defective, AI-defective, cyber-sensitive, privacy-defective, protected-knowledge-defective, inaccessible, discriminatory, or inconsistent with these Bylaws, the Corporation shall take corrective action.
491.16.2 Corrective action may include correction, supersession, withdrawal, retraction, takedown, restriction, archive annotation, public-safe clarification, controlled clarification, direct notice, repository notice, website notice, dashboard notice, map notice, public authority notice, sponsor notice, provider notice, funder notice, community notice, GRF notice, GRA notice, Nexus Standards notice, or other appropriate action.
491.16.3 Transitional correction may be made without admission where appropriate and lawful, but non-admission language shall not prevent accurate public-safe correction.
491.17 Transitional Public Materials Records.
491.17.1 The Corporation shall maintain Transitional Public Materials Records, including Transitional Public Materials Review records, Website Review records, Deck Review records, Proposal Review records, Grant Application Review records, Sponsor and Donor Material Review records, Public Authority Reference Review records, Provider Reference Review records, Finance-Readiness Reference Review records, Certification / Recognition / Docket / Grid / Nexus-Compatible Claim Review records, Technical Baseline and Software Claim Review records, GCRI US / GCRI Canada Distinction Review records, GCRI / GRF / GRA Role-Separation Review records, Nexus Coordination Description Review records, Public-Safe Disclaimer Review records, correction records, supersession records, withdrawal records, retraction records, takedown records, public clarification records, controlled clarification records, notice records, closeout records, and archive records.
Section 492. Dissolution Purpose and Authority
492.1 Dissolution Purpose.
492.1.1 Dissolution provisions shall ensure that, if the Corporation is dissolved, wound up, merged out of existence where lawful, administratively dissolved, judicially dissolved, voluntarily dissolved, or otherwise terminated, its affairs are concluded in a manner consistent with applicable law, the certificate or articles, these Bylaws, nonprofit character, public-benefit purpose, tax requirements, restricted funds, grant obligations, contract obligations, public-good technical asset stewardship, data protection, public authority material protection, protected knowledge safeguards, legal holds, creditor rights, and correctionability.
492.1.2 Dissolution shall not be used to distribute public-good assets for private benefit, evade legal obligations, destroy records subject to preservation, bypass restricted fund obligations, erase correction duties, expose protected knowledge, transfer public authority data without authority, transfer restricted technical assets without review, or collapse public-good assets into sponsor, provider, donor, founder, insider, or enterprise control.
492.2 Dissolution Authority.
492.2.1 Dissolution Authority shall be exercised only according to applicable law, the certificate or articles, these Bylaws, Board approval requirements, member approval requirements where applicable, state filing requirements, court requirements, Attorney General requirements where applicable, regulator requirements where applicable, tax requirements, grant requirements, and other competent approvals.
492.2.2 No director acting alone, officer acting alone, committee, council, advisor, sponsor, provider, donor, funder, public authority participant, Nexus participant, repository custodian, or external actor may dissolve the Corporation without lawful authority.
492.2.3 Dissolution Authority shall be recorded in Dissolution Records.
492.3 Board Approval.
492.3.1 Dissolution shall require Board approval according to applicable law, the certificate or articles, these Bylaws, and any reserved matter requirements.
492.3.2 Board approval records shall identify the proposed dissolution, reasons, alternatives considered where appropriate, financial condition, known liabilities, restricted funds, grants, contracts, public authority interfaces, technical assets, data and protected knowledge, employees and contractors, legal holds, insurance, claims, asset distribution plan, wind-up plan, required approvals, and vote.
492.3.3 Directors with conflicts shall disclose such conflicts and recuse where required.
492.4 Member Approval Where Required.
492.4.1 Where applicable law, the certificate or articles, or these Bylaws require member approval for dissolution, such approval shall be obtained before dissolution is effective.
492.4.2 Member approval records shall identify members entitled to vote, notice, information provided, vote threshold, votes, abstentions, objections where recorded, approval date, and conditions.
492.4.3 Where the Corporation has no voting members, no member approval shall be implied unless required by law or governing instruments.
492.5 State Law Requirements.
492.5.1 Dissolution shall comply with governing state law and any other state law applicable to the Corporation’s registration, foreign qualification, charitable solicitation, tax, employment, property, contracts, grants, public authority interfaces, or operations.
492.5.2 State law requirements may include articles or certificate of dissolution, notices, claims procedures, tax clearance where applicable, Attorney General notice where applicable, asset distribution restrictions, filing fees, public records, and other statutory steps.
492.5.3 State filings shall be supported by Board records and legal review where appropriate.
492.6 Attorney General, Regulator, Court, IRS, or Other Approval Where Required.
492.6.1 The Corporation shall obtain or provide required notice to any Attorney General, regulator, court, IRS, tax authority, charitable regulator, grantor, public authority, data protection authority, employment authority, funder, or other body where required by law, grant, contract, tax status, restricted fund terms, charitable trust doctrine, or court order.
492.6.2 Required approvals or notices shall be recorded and shall not be bypassed by private agreement, asset transfer, repository migration, or informal wind-up.
492.7 Notice to Required Parties.
492.7.1 The Corporation shall provide notice of dissolution or wind-up to required parties according to law, contract, grant, insurance, employment, public authority instruments, data agreements, controlled-room instruments, repository instruments, donor restrictions, and other applicable obligations.
492.7.2 Required parties may include directors, officers, members where applicable, employees, contractors, fellows, advisors, volunteers, contributors, maintainers, creditors, vendors, grantors, funders, donors, sponsors, hosts, partners, public authorities, insurers, counsel, auditors, data contributors, affected communities, Tribal / Indigenous representatives where applicable, Nexus institutions, repository users, and regulators.
492.7.3 Notices shall be public-safe, accurate, and limited to authorized information.
492.8 Public-Benefit Wind-Up Principle.
492.8.1 The Corporation shall wind up in a manner that preserves public-benefit purpose and avoids waste, private capture, sponsor capture, provider capture, public-good asset enclosure, unlawful distribution, data misuse, protected knowledge exposure, public authority confusion, finance reliance, certification or recognition overclaim, and technical asset abandonment.
492.8.2 Public-benefit wind-up shall prioritize lawful satisfaction of obligations, preservation of records, continuity or responsible disposition of public-good technical assets, protection of restricted funds, protection of data, protection of public authority materials, protection of protected knowledge, and public-safe correction of outstanding materials.
492.9 Restricted Fund Protection.
492.9.1 Restricted funds, grants, donations, sponsorships, in-kind support, public-good support, and donor-restricted assets shall be identified, segregated where appropriate, reviewed, used, returned, reallocated, transferred, or otherwise disposed of according to law and the restriction governing the asset.
492.9.2 Restricted funds shall not be diverted to private persons, insiders, sponsors, providers, enterprise stack actors, unrelated purposes, or unrestricted wind-up purposes unless lawfully permitted and recorded.
492.10 Public-Good Technical Asset Protection.
492.10.1 Public-good technical assets, including software, repositories, technical baselines, schemas, APIs, SDKs, technical profiles, public-safe dashboards, maps, datasets, models, evaluation harnesses, benchmark libraries, ontologies, controlled vocabularies, documentation, and public-good software releases, shall be reviewed for lawful continuation, transfer, archive, open release, restricted transfer, deprecation, withdrawal, or secure disposal.
492.10.2 Technical asset protection shall consider license terms, contributor terms, IP ownership, public-good mission, security, vulnerabilities, secrets, keys, tokens, credentials, controlled technology, export controls, sanctions, public authority data, protected knowledge, public-safe status, and Nexus dependencies.
492.10.3 No public-good technical asset shall be transferred to a private person, sponsor, provider, host, founder, related party, or enterprise actor in a manner that creates impermissible private benefit, provider preference, public-good enclosure, or role-separation collapse.
492.11 Data, Public Authority Material, and Protected Knowledge Protection.
492.11.1 Dissolution shall include review and protection of data, public authority materials, personal information, health-sensitive data, rights-bearing data, cyber-sensitive data, infrastructure-sensitive data, public authority data, community-protected data, Tribal / Indigenous data, Indigenous knowledge, local knowledge, territorial knowledge, cultural knowledge, environmental knowledge, protected knowledge, and controlled-room materials.
492.11.2 Such materials shall be retained, returned, deleted, transferred, sealed, archived, or securely disposed of according to law, consent, permission, data contribution agreements, public authority restrictions, protected knowledge restrictions, retention schedules, legal holds, and public-safe requirements.
492.11.3 Dissolution shall not authorize unauthorized AI training, embedding, transfer, publication, commercialization, mapping, or external sharing of restricted data or protected knowledge.
492.12 No Dissolution Distribution to Private Persons Except Lawful Payment of Debts, Obligations, Compensation, Reimbursement, or Contractual Amounts.
492.12.1 Upon dissolution, no part of the Corporation’s net assets shall be distributed to directors, officers, members, founders, sponsors, donors, funders, providers, hosts, contractors, employees, volunteers, advisors, fellows, contributors, maintainers, related parties, or private persons except for lawful payment of debts, obligations, reasonable compensation, reimbursement, contractual amounts, indemnification, advancement, settlement, or other amounts lawfully owed.
492.12.2 No distribution shall constitute private inurement, impermissible private benefit, disguised distribution, equity return, profit share, liquidation preference, sponsor return, provider preference, or founder benefit.
492.12.3 Remaining assets shall be distributed according to applicable law, the certificate or articles, tax requirements, donor restrictions, grant restrictions, public-benefit purpose, and Board-approved asset disposition records.
492.13 Dissolution Records.
492.13.1 The Corporation shall maintain Dissolution Records, including dissolution purpose records, Dissolution Authority records, Board approval records, member approval records where required, state law compliance records, Attorney General / regulator / court / IRS / other approval records where required, notices to required parties, public-benefit wind-up records, restricted fund protection records, public-good technical asset protection records, data / public authority material / protected knowledge protection records, no-private-distribution records, filings, legal review records, tax review records, insurance records, creditor records, asset distribution records, wind-up records, correction records, closeout records, and archive records.
Section 493. Wind-Up Governance
493.1 Wind-Up Purpose.
493.1.1 Wind-Up Governance shall provide the governance structure for concluding the Corporation’s affairs after dissolution approval or during an orderly termination, merger, restructuring, administrative dissolution cure, or other wind-up event.
493.1.2 Wind-Up Governance shall preserve lawful authority, Board oversight, fiduciary duty, creditor rights, restricted fund compliance, contract compliance, grant compliance, employment compliance, public authority boundaries, data / AI / cyber / privacy controls, protected knowledge safeguards, repository security, technical asset stewardship, legal holds, insurance rights, claims handling, public-safe communication, and correctionability.
493.2 Wind-Up Plan.
493.2.1 The Corporation shall adopt a Wind-Up Plan where dissolution or material wind-up occurs.
493.2.2 The Wind-Up Plan shall identify wind-up authority, timeline, responsible persons, creditor process, contract review, grant review, restricted fund review, employee and contractor closeout, fellow / advisor / volunteer / contributor closeout, data and privacy closeout, AI and model closeout, cybersecurity closeout, repository closeout, public authority interface closeout, community and protected knowledge closeout, technical asset disposition, asset distribution, insurance and claims handling, legal holds, litigation, public-safe communications, record retention, archive, deletion, secure disposal, and final reporting.
493.2.3 The Wind-Up Plan shall be approved by the Board or other competent authority and updated as circumstances require.
493.3 Board Oversight During Wind-Up.
493.3.1 The Board shall retain oversight during wind-up unless a court, receiver, trustee, statutory process, or other competent authority lawfully provides otherwise.
493.3.2 Board oversight shall include review of material payments, asset dispositions, restricted funds, grants, contracts, settlements, insurance claims, data disposition, technical asset disposition, public authority communications, protected knowledge disposition, public-safe communications, and final dissolution filings.
493.3.3 Board members shall continue to comply with fiduciary duties, conflicts rules, confidentiality, privilege, legal holds, and non-retaliation obligations during wind-up.
493.4 Officer Authority During Wind-Up.
493.4.1 Officers may exercise wind-up authority only as authorized by the Board, applicable law, the certificate or articles, these Bylaws, court order, or other competent record.
493.4.2 Officer wind-up authority may include paying debts, collecting receivables, preserving records, terminating contracts, issuing notices, handling filings, coordinating with counsel, securing repositories, closing accounts, managing employee closeout, preserving legal holds, coordinating insurance, and preparing reports.
493.4.3 Officer authority shall not include unauthorized asset distribution, private benefit transfer, public authority representation, finance-readiness representation, recognition representation, certification representation, procurement approval, public warning, emergency command, or release of restricted materials.
493.5 Wind-Up Committee Where Created.
493.5.1 The Board may create a Wind-Up Committee to oversee or support wind-up.
493.5.2 A Wind-Up Committee charter shall identify purpose, members, authority, limitations, reporting obligations, conflicts, confidentiality, privilege, public-safe communication, data / AI / cyber duties, protected knowledge duties, public authority boundary duties, finance-boundary duties, and records duties.
493.5.3 The Wind-Up Committee shall not possess authority beyond its charter and shall report material matters to the Board.
493.6 Creditor Notice.
493.6.1 The Corporation shall provide creditor notices where required or appropriate under applicable law.
493.6.2 Creditor Notice records shall identify known creditors, disputed creditors, contingent claims, notice date, claim deadline where applicable, claims received, claims accepted, claims rejected, settlements, payment records, and unresolved claims.
493.6.3 Creditor processes shall not impair restricted fund protections, legal holds, public authority restrictions, data protections, or protected knowledge obligations except as lawfully required.
493.7 Contract Review.
493.7.1 The Corporation shall review contracts, MoUs, grants, sponsorship agreements, donor agreements, vendor agreements, data agreements, AI agreements, cloud agreements, repository agreements, software agreements, licenses, contributor agreements, public authority agreements, room instruments, consortium instruments, Nexus interface instruments, insurance contracts, employment agreements, contractor agreements, leases, and service agreements.
493.7.2 Contract Review shall identify termination rights, survival obligations, payment obligations, notice obligations, data return or deletion, confidentiality, IP rights, license continuity, publication rights, audit rights, indemnity, insurance, assignment, transfer, restricted materials, public authority restrictions, protected knowledge restrictions, and dispute provisions.
493.8 Grant and Restricted Fund Review.
493.8.1 The Corporation shall review all grants, restricted funds, donations, sponsorships, in-kind support, public-good support, public grants, cooperative agreements, subawards, and restricted assets.
493.8.2 Review shall determine restrictions, allowable uses, reporting duties, return obligations, reallocation possibilities, transfer possibilities, public authority requirements, audit requirements, data rights, IP rights, publication rights, and closeout steps.