ARTICLE I. FOUNDATION

Section 1. Title, Citation, Version, Status, Issue Date, and Effective Date

1.1 Instrument Title. This instrument shall be titled the “GCRI Canada Bylaw”. It is the principal internal governance bylaw of The Global Centre for Risk and Innovation Canada and shall be read as an adopted corporate governance instrument of the Corporation, not as a policy note, operating manual, strategic memorandum, public-facing charter, technical specification, promotional document, program description, or Nexus ecosystem statement.

The Bylaw governs the Corporation’s internal legal authority, corporate identity, board governance, officer authority, committee and council architecture, member and participant status where applicable, records discipline, evidence and methods governance, public-good technical stewardship, data and safeguards controls, Nexus interface discipline, non-execution perimeter, fiscal controls, public-safe publication, correctionability, and all other matters properly governed by bylaw, subject always to applicable law, the Articles, and any superior legal requirement binding upon the Corporation.

1.2 Short Citation. This instrument may be cited as the “GCRI Canada Bylaw” or, where the context is internal to the Corporation and no ambiguity may reasonably arise, as the “Bylaw.” The short citation shall not be used in a manner that obscures, softens, expands, or misstates:

a) the official legal identity of the Corporation;

b) the Corporation’s Canadian seat and governing corporate-law posture;

c) the Corporation’s nonprofit, non-share, non-distributing, public-benefit, and non-executing character;

d) the Corporation’s role as an upstream public-good research, evidence, methods, observability, ontology, technical truth, public-good software, open technical baseline, and research-integrity steward;

e) the legal separateness of the Corporation from GCRI US, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Universe, Nexus Standards, Nexus Observatory, Nexus Grid, Nexus Academy, Nexus Risk Management, Nexus Rails, Nexus Competence Cells, Global Nexus Consortium, Regional Nexus Consortiums, National Nexus Consortiums, National Consortium Companies, Project SPVs, qualified enterprise providers, sponsors, hosts, vendors, funders, public authorities, universities, laboratories, contractors, operators, or other partners; or

f) the rule that GCRI Canada does not itself issue public recognition, finance-readiness determinations, protocol authority, certification, public authority action, procurement approval, investment recommendation, insurance approval, public warning, emergency command, or execution authority unless a future lawful instrument expressly and narrowly authorizes a function consistent with this Bylaw.

1.3 Version Identifier. Each adopted, amended, restated, consolidated, corrected, superseded, withdrawn, or archived form of this Bylaw shall bear a unique version identifier. The version identifier shall be recorded in the Corporation’s authoritative governance repository, minute book, bylaw register, amendment history, and any controlled circulation record through which the Bylaw is made available for governance, legal, audit, operational, technical, public-safe, or institutional use.

The version identifier shall include, at minimum, a version number, date of issue, status classification, and effective-date reference. Where the Board determines that greater integrity controls are required, the version identifier may also include a repository reference, adoption resolution number, document-control number, hash, checksum, signature reference, or other tamper-evident marker approved for governance-record purposes.

A version identifier is an evidence-control device only. It shall not confer authority unless the corresponding text has been adopted and brought into force by competent authority in accordance with this Bylaw, the Articles, and applicable law.

1.4 Status Classification. Each version of this Bylaw shall be assigned one and only one status classification at any time. The permitted status classifications are:

a) Draft, meaning a version under preparation, consultation, legal review, board review, member review where applicable, technical reconciliation, correction, or other pre-adoption handling, and having no operative effect except as a clearly identified non-binding working instrument;

b) Adopted, meaning a version formally approved by the competent adopting authority but not necessarily yet in force where the adoption record, applicable law, filing requirement, member approval requirement, transitional provision, or deferred commencement date provides otherwise;

c) In Force, meaning the current operative version of this Bylaw, binding upon the Corporation and its directors, officers, members where applicable, committees, councils, working groups, authorized delegates, employees, contractors, fellows, advisors, volunteers, contributors, and other persons within the scope of the Bylaw according to its terms;

d) Superseded, meaning a version replaced in whole or in part by a later adopted and in-force instrument, while remaining preserved for historical, legal, audit, interpretive, correction, transition, and evidentiary purposes;

e) Withdrawn, meaning a draft, proposed, adopted, or circulated version removed from use by competent recorded act and having no operative effect except for archival, audit, correction, investigation, or historical-integrity purposes; and

f) Archived, meaning a version preserved as part of the Corporation’s institutional record and not available for present operative reliance unless restored, re-adopted, or expressly incorporated by competent recorded act.

No status classification shall arise by file name, folder location, email circulation, repository upload, draft watermark omission, board discussion, committee use, counsel review, partner reliance, sponsor use, public authority familiarity, operational practice, technical implementation, AI-assisted drafting, or repeated institutional reference. Status arises only by competent record.

1.5 Issue Date. Each version of this Bylaw shall state an issue date. The issue date shall identify the date on which the authenticated text was issued for the status assigned to it and deposited into the Corporation’s authoritative governance record.

The issue date shall not, by itself, establish legal effectiveness, operative force, adoption, amendment, supersession, withdrawal, or public reliance. Where the issue date and effective date differ, the effective date shall govern operative effect. Where the issue date, adoption date, and effective date are inconsistent, incomplete, or unclear, the matter shall be escalated to the Secretary, the Chair, and such legal or governance authority as the Board may designate, and the most protective lawful interpretation shall apply pending correction.

1.6 Effective Date. Each adopted version of this Bylaw shall state an effective date. The effective date shall determine the date from which the relevant version or provision becomes operative, subject to:

a) applicable law;

b) the Articles;

c) any required member approval;

d) any required filing, confirmation, or statutory condition;

e) any transitional, deferred, conditional, phased, or savings provision approved by competent authority; and

f) any express limitation, suspension, or implementation condition contained in the adoption record.

Where the adoption record does not state a separate effective date, the effective date shall be the date of formal adoption, unless applicable law, the Articles, or the adopting resolution provides otherwise. No person shall rely on a draft effective date, proposed commencement schedule, working assumption, board-paper date, public announcement, website update, or operational implementation date as a substitute for the effective date recorded in the authoritative governance record.

1.7 Operative Text Rule. Only the authenticated, adopted, and in-force text of this Bylaw shall have operative effect. No draft, excerpt, table of contents, outline, summary, prompt, memorandum, comment, slide, board deck, legal mark-up, redline, unofficial consolidation, implementation checklist, translation, public-safe explanation, website description, email, message, repository note, AI-generated draft, training material, meeting note, policy template, program document, partner-facing communication, sponsor-facing communication, public authority briefing, or derivative communication shall be treated as operative bylaw text unless expressly adopted or incorporated by competent recorded act.

Where a public or controlled summary is prepared to explain this Bylaw, the summary shall be clearly identified as non-operative unless the Board expressly approves a different status. A summary shall not expand powers, soften boundaries, create reliance, change legal meaning, override the authenticated text, or convert GCRI Canada’s public-good stewardship role into execution authority.

1.8 Draft, Adopted, In Force, Superseded, Withdrawn, and Archived Statuses. The lifecycle status of this Bylaw and each version of this Bylaw shall be explicit, recorded, traceable, and capable of verification. No version shall move from one status to another except through the procedure required by this Bylaw, the Articles, applicable law, and the relevant adoption, amendment, correction, supersession, withdrawal, or archival record.

A draft version shall remain non-operative even if it is complete, polished, circulated to directors, reviewed by counsel, discussed by the Board, used for planning, referenced in a meeting, stored in an official repository, or relied upon by a program team. An adopted version shall not be treated as in force until the applicable effective conditions are satisfied. A superseded version shall not be used for current authority except to interpret historical actions taken while it was in force or where the Board expressly authorizes limited reference for transition, audit, investigation, correction, or continuity purposes.

1.9 No Operative Effect by Circulation Alone. Circulation of this Bylaw, or of any draft, excerpt, table of contents, redline, translation, public-safe summary, extracted clause, implementation checklist, working copy, AI-assisted draft, board-paper attachment, partner-facing version, or archived version, shall not create operative effect, governance authority, legal authority, delegation authority, institutional status, public-facing reliance, public authority meaning, finance-readiness implication, certification implication, recognition implication, procurement implication, or Nexus-compatible status.

Any person circulating a non-operative version shall identify its status where there is any reasonable risk of confusion. Any circulation that creates or may create misunderstanding shall be subject to correction, withdrawal, access restriction, clarification, supersession notice, repository reconciliation, public or controlled notice where appropriate, and any other remedial action authorized under this Bylaw.

1.10 Record of Current In-Force Version. The Corporation shall maintain a record of the current in-force version of this Bylaw in its authoritative governance repository and corporate records. The record shall identify, at minimum:

a) the full instrument title;

b) the approved short citation;

c) the version identifier;

d) the status classification;

e) the issue date;

f) the adoption date;

g) the effective date;

h) the adopting authority;

i) the adoption resolution or approval record;

j) any member approval, filing, or legal condition where applicable;

k) any transitional, savings, deferred-effect, or phased-implementation provisions;

l) any prior version superseded in whole or in part;

m) any incorporated schedules, annexes, policies, registers, or instruments having bylaw-authorized effect;

n) the authoritative repository location;

o) the repository custodian;

p) the access classification;

q) any public, internal, controlled, restricted, confidential, or archived publication status;

r) any correction, supersession, withdrawal, restatement, consolidation, or archival notation;

s) any integrity, signature, hash, certification, or tamper-evident reference used for authentication; and

t) any legally required filing, notice, register entry, corporate record, or statutory compliance record.

1.11 Custody of Authoritative Text. The Secretary, or such other officer or governance-record custodian as the Board may designate by recorded act, shall maintain custody of the authoritative current in-force text of this Bylaw. Custody includes responsibility for preserving the authenticated text, adoption record, amendment history, repository record, supersession chain, access classification, official copies, controlled copies, archival copies, and any correction or clarification record.

The custodian shall not alter the Bylaw except through a recorded process authorized by this Bylaw. Clerical formatting, pagination, typographical correction, or consolidation may be made only where permitted under the versioning and correction provisions of this Bylaw and shall not change substantive meaning, legal effect, institutional authority, role separation, or non-execution boundary.

1.12 Authentication of the Bylaw. The authenticated version of this Bylaw may be evidenced by one or more of the following, as approved by the Board or required by law:

a) a certificate of adoption signed by the Chair, Secretary, or other authorized officer;

b) an adoption resolution recorded in the minute book;

c) a signed or sealed authoritative copy where a seal or signature process is used;

d) a repository entry approved for governance-record purposes;

e) a version-control and amendment-history record;

f) a hash, checksum, digital signature, or other integrity reference where used;

g) a filing, confirmation, or statutory record where applicable; or

h) such other authentication process as the Board may approve consistently with applicable law and this Bylaw.

Authentication shall confirm text identity and status. It shall not expand the authority of the Bylaw beyond its adopted terms.

1.13 Relationship Between Version and Authority. A later version number, more recent date, broader circulation, more complete drafting style, or more detailed text shall not supersede an earlier in-force version unless the later version has been validly adopted and brought into force. A draft marked with a higher version number shall remain non-operative unless adopted.

Where two versions appear to conflict, the Secretary shall determine the authoritative record in accordance with the adoption record, effective date, repository record, and applicable law. Pending determination, no person shall rely on the broader, riskier, more authority-expanding, more execution-facing, more public-facing, more finance-signaling, more certification-implying, or more role-collapsing interpretation.

1.14 No Silent Amendment. This Bylaw shall not be amended, restated, corrected in a material way, superseded, localized, translated with operative effect, consolidated, withdrawn, or replaced by silent edit, repository overwrite, unapproved formatting change, informal consolidation, officer instruction, committee practice, board custom, counsel draft, staff implementation, project urgency, sponsor request, provider request, public authority expectation, Nexus partner expectation, AI-assisted revision, public-facing update, or operational necessity.

Every amendment, restatement, material correction, supersession, localization, operative translation, withdrawal, or replacement shall be approved, recorded, authenticated, and deposited in accordance with this Bylaw, the Articles, and applicable law.

1.15 Continuity of Prior Lawful Acts. Unless the adopting record expressly provides otherwise and applicable law permits, adoption, amendment, restatement, correction, supersession, or replacement of this Bylaw shall not invalidate lawful acts, records, delegations, decisions, appointments, resolutions, notices, publications, contracts, filings, or governance actions taken under a prior in-force bylaw while that prior bylaw was operative.

Prior acts shall remain subject to correction, clarification, limitation, withdrawal, supersession, investigation, or remediation where required by applicable law, public-benefit purpose, fiduciary duty, evidence integrity, research integrity, public authority boundary discipline, finance-readiness boundary discipline, data or safeguards obligations, non-execution discipline, Nexus role separation, or this Bylaw.

1.16 Transitional Application. Where a new version of this Bylaw enters into force, the Board may approve transitional provisions for implementation. Transitional provisions may address:

a) policy adoption or replacement;

b) committee and council reconstitution;

c) officer appointment or delegation alignment;

d) records migration;

e) member, supporter, participant, contributor, public authority, provider, sponsor, donor, host, and partner register alignment;

f) controlled vocabulary reconciliation;

g) repository migration;

h) public-facing claims review;

i) contract template revision;

j) public authority protocol alignment;

k) data, AI, cybersecurity, privacy, and safeguards alignment;

l) research, evidence, methods, ontology, software, and technical baseline records alignment;

m) Nexus interface alignment;

n) correction of inconsistent prior materials; and

o) closeout of obsolete structures.

No transitional provision shall weaken the Corporation’s nonprofit character, non-distribution rule, public-benefit purpose, legal separateness, public-good stewardship burden, non-execution perimeter, GCRI / GRF / GRA role separation, public authority boundary, provider neutrality, sponsor support-without-control, data and safeguards obligations, validity-by-record, or correctionability.

1.17 Defective, Ambiguous, or Incomplete Version Records. Where a version record is defective, ambiguous, incomplete, inconsistent, inaccessible, corrupted, duplicated, incorrectly labeled, or inconsistent with the adoption record, the matter shall be escalated to the Secretary and, where material, to the Chair, the Board, legal counsel, or the appropriate governance committee. Pending correction, the Corporation shall apply the most protective lawful interpretation and shall avoid any interpretation that creates unauthorized governance authority, public authority meaning, finance-readiness implication, certification implication, procurement implication, recognition implication, provider preference, sponsor control, or execution authority.

1.18 Correction of Version Confusion. Where confusion arises concerning the current in-force version, the status of a draft, the effect of a superseded version, the use of an unauthorized copy, the existence of conflicting versions, or the meaning of an unofficial summary, the Corporation shall take corrective action proportionate to the risk. Corrective action may include:

a) repository correction;

b) access restriction;

c) withdrawal of unauthorized copies;

d) issuance of a controlled clarification;

e) issuance of a public-safe clarification where public reliance risk exists;

f) notice to directors, officers, members, committees, councils, staff, contractors, partners, sponsors, providers, public authorities, or affected Nexus interfaces;

g) correction of downstream documents;

h) amendment, restatement, or supersession where required; and

i) archival preservation of the defective or superseded record for traceability.

1.19 Public-Facing Use of Bylaw Status. The Corporation may disclose the existence, adoption, amendment, or public-facing status of this Bylaw where lawful and appropriate. Any public-facing reference shall be accurate, current, scope-limited, and non-misleading. No public-facing statement shall imply that this Bylaw constitutes public authority approval, regulatory approval, procurement approval, finance-readiness approval, insurance approval, investment suitability, certification, recognition by GRF, finance-readiness by GRA, protocol authority, Nexus Grid admission, Nexus Docket approval, provider endorsement, or sovereign mandate.

1.20 Governing Reading of Section 1. This Section shall be interpreted to preserve documentary integrity, Canadian corporate-law discipline, fiduciary accountability, legal certainty, traceability, validity-by-record, correctionability, public-benefit trust, and institutional continuity. No person shall rely on appearance, possession, circulation, repository visibility, authorship, seniority, technical centrality, sponsor use, public authority familiarity, partner reliance, repeated practice, operational convenience, AI-generated text, or strategic usefulness as a substitute for recorded status, lawful adoption, effective date, and authoritative custody.

Section 2. Official Name, Short Name, Controlled Naming Protocol, and Name-Use Discipline

2.1 Official Legal Name. The official legal name of the Corporation is The Global Centre for Risk and Innovation - Canada.

The official legal name shall be used in the Articles, statutory filings, corporate registers, board resolutions, member resolutions where applicable, material contracts, banking and treasury records, tax records, audit records, insurance records, grant agreements, donation agreements, sponsorship agreements, restricted-fund instruments, employment and contractor agreements, intellectual property instruments, data-sharing agreements, public authority interface instruments, Nexus interface instruments, and any other document or record in which legal identity, authority to bind, ownership, liability, public representation, regulatory posture, fiscal status, or institutional standing may be relevant.

The official legal name shall not be shortened, translated, stylized, abbreviated, reformatted, merged with another institutional name, used as a program label, used as a trading style, or embedded into a wider Nexus mark in any manner that creates uncertainty as to the Corporation’s separate legal personality, Canadian seat, nonprofit character, non-distributing status, public-benefit purpose, non-execution boundary, or institutional role.

2.2 Approved Short Name. The approved short name of the Corporation is “GCRI Canada.”

The approved short name may be used in internal governance materials, public-safe communications, program materials, technical documentation, evidence artifacts, publications, websites, presentations, correspondence, reports, memoranda, controlled-room materials, repositories, software documentation, public authority learning materials, and Nexus interface materials where the context makes clear that the reference is to The Global Centre for Risk and Innovation - Canada and not to GCRI US, the broader GCRI function, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), any Nexus body, any regional or national consortium, any national consortium company, any Project SPV, any provider, any sponsor, or any partner.

The approved short name is a naming convenience only. It shall not alter the Corporation’s legal identity, corporate form, governing law, rights, obligations, liabilities, fiduciary structure, ownership of records, public-good stewardship duties, or legal separateness.

2.3 Use of “GCRI Canada.” “GCRI Canada” may be used as the operational short form of the Corporation only where such use is accurate, authorized, non-misleading, and consistent with this Bylaw.

In any context involving legal execution, formal authority, external reliance, statutory filing, fiscal receipt, tax treatment, liability, indemnification, ownership, intellectual property, restricted funds, sponsorship recognition, public authority participation, finance-readiness boundary, public-facing institutional status, contractual commitment, or Nexus interface effect, the first reference should use the official legal name, followed by the approved short name in parentheses, unless a previously defined usage in the same instrument makes further repetition unnecessary.

No use of “GCRI Canada” shall imply that the Corporation:

a) is the same legal person as GCRI US or any other GCRI-related entity;

b) is the whole of the GCRI function globally;

c) controls The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Universe, Nexus Standards, Nexus Observatory, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, any consortium, any national consortium company, any Project SPV, or any qualified enterprise provider;

d) possesses public authority, regulatory authority, procurement authority, standards authority with external legal force, finance-readiness authority, investment authority, insurance authority, emergency authority, public-warning authority, recognition authority, or certification authority by reason of name, mission, participation, public reference, or Nexus alignment; or

e) may bind any other entity, public authority, sponsor, host, provider, funder, university, laboratory, partner, participant, or Nexus body unless expressly authorized by lawful written instrument.

2.4 No Alternate Name Without Record. The Corporation shall not adopt, use, register, publish, contract under, raise funds under, sponsor under, receive funds under, employ personnel under, operate a program under, issue publications under, release software under, host repositories under, or present itself under any alternate legal name, assumed name, business name, trade name, style, acronym, campaign name, project name, platform name, program name, mark, translated name, or public-facing identity unless such name or style has been reviewed, approved, recorded, and controlled in accordance with this Bylaw and applicable law.

No officer, director, committee, council, working group, fellow, advisor, employee, contractor, volunteer, sponsor, donor, provider, host, public authority participant, academic partner, media partner, technical contributor, or Nexus interface participant may create or authorize an alternate name for the Corporation by practice, convenience, publication, public announcement, domain registration, repository creation, social media use, event branding, sponsor request, deck title, software release, dataset label, public authority briefing, or AI-generated material.

Where an alternate name is approved, the approval record shall identify:

a) the exact name, style, abbreviation, translation, mark, label, or usage approved;

b) the permitted use cases;

c) the prohibited use cases;

d) the legal entity to which the name refers;

e) the period of authorization;

f) the responsible custodian;

g) the public-facing disclaimer, if required;

h) any registration, filing, trademark, domain, repository, or intellectual property control required;

i) any translation or bilingual-use protocol; and

j) the correction or withdrawal pathway.

2.5 Name Use in Contracts, Filings, Registers, Publications, Repositories, Board Papers, and Notices. The official legal name shall be used in any document or system where the Corporation’s legal personality, authority, fiduciary governance, financial responsibility, corporate status, statutory compliance, ownership, liability, data responsibility, intellectual property responsibility, or public-benefit purpose may be material.

The approved short name may be used in secondary references, provided that the relevant instrument or system clearly identifies the Corporation at first instance or otherwise preserves legal certainty. The following minimum rules shall apply:

a) Contracts and Legal Instruments. The official legal name shall be used in all contracts, memoranda of understanding, interface agreements, data-sharing agreements, sponsorship agreements, donation agreements, grant agreements, restricted-fund agreements, employment agreements, contractor agreements, intellectual property agreements, licenses, indemnities, releases, waivers, insurance documents, procurement documents, public authority interface documents, and settlement or dispute-resolution documents.

b) Statutory and Fiscal Filings. The official legal name shall be used in all filings, annual returns, tax records, corporate registers, bank records, audit records, receipts, invoices, government-facing forms, legal notices, and compliance submissions.

c) Governance Records. The official legal name or the approved short name, once clearly defined, may be used in board papers, minutes, resolutions, committee records, council records, registers, Gazette or notice-stream entries, case IDs, decision packs, action logs, and internal governance instruments, provided that legal identity remains clear.

d) Publications and Public-Safe Materials. Public reports, white papers, dashboards, maps, datasets, software releases, technical baselines, method notes, evidence notes, public-safe summaries, Academy materials, public authority learning materials, and media materials shall use the official legal name or approved short name in accordance with approved public-communications, publication, claims-discipline, and public authority reference protocols.

e) Repositories and Technical Systems. Code repositories, model repositories, dataset repositories, ontology repositories, schema registries, software packages, dashboards, APIs, SDKs, technical libraries, test harnesses, public-good baselines, evidence systems, observability environments, and controlled rooms shall identify whether they are owned, maintained, sponsored, hosted, contributed to, or merely referenced by the Corporation.

f) Notices. Notices of adoption, amendment, correction, supersession, withdrawal, appointment, delegation, suspension, termination, publication status change, public authority correction, claims correction, or other governance-significant acts shall use the legal name or approved short name in a manner sufficient to identify the Corporation and the relevant authority surface.

2.6 Translation, Abbreviation, Program Name, Campaign Label, and Trading-Style Controls. No translation, abbreviation, acronym, program name, campaign label, event label, working title, repository name, dataset name, software package name, dashboard title, report series title, domain name, social media handle, public-facing tagline, or trading-style expression shall be used in a manner that suggests that it is a separate legal person, a public authority, a charity, a regulator, a certification body, a procurement authority, a finance-readiness authority, a market intermediary, a standards authority with legal force, a Nexus-wide governing body, or an execution vehicle.

A translated name may be used only where approved under the Corporation’s bilingual and translation protocol. A translation shall not be treated as an authoritative legal name unless it is adopted, filed, registered, or otherwise made legally operative in accordance with applicable law and a recorded corporate act.

A program name, campaign label, platform label, laboratory name, Academy label, challenge name, technical-baseline name, evidence-pack name, Observatory-related name, Nexus Universe-related name, or other operating label shall be subordinate to the Corporation’s official legal identity and shall not:

a) imply separate incorporation;

b) imply public authority delegation;

c) imply charitable status unless lawfully obtained and accurately stated;

d) imply certification, accreditation, conformance approval, or regulatory approval;

e) imply finance-readiness, investment suitability, insurability, bankability, underwriting, guarantee, or capital placement;

f) imply procurement preference, vendor selection, preferred-provider status, or public-private partnership;

g) imply that a sponsor, donor, provider, host, investor, insurer, lender, public authority, university, laboratory, community body, or partner controls the Corporation; or

h) obscure which entity owns, maintains, funds, operates, publishes, hosts, or is responsible for the relevant activity.

2.7 Prohibition on Legal-Identity Ambiguity. The Corporation shall not permit any use of name, mark, abbreviation, logo, seal, badge, publication title, repository label, public statement, public authority reference, sponsor acknowledgment, provider acknowledgment, technical baseline, software release, dataset, dashboard, evidence artifact, Academy material, event material, capital-reader material, or Nexus interface material that creates legal-identity ambiguity.

Legal-identity ambiguity includes any circumstance in which a reasonable reader, participant, public authority, sponsor, provider, funder, investor, insurer, lender, community participant, researcher, media actor, contractor, or partner could misunderstand:

a) which legal entity is acting;

b) which legal entity is responsible;

c) which legal entity owns or controls a record, asset, system, publication, dataset, software component, method, technical baseline, public-good asset, or repository;

d) whether the Corporation is acting as itself or on behalf of another entity;

e) whether the Corporation has authority to bind another entity;

f) whether another entity has authority to bind the Corporation;

g) whether an output is a GCRI Canada output, a GRF output, a GRA output, a Nexus Standards output, a Nexus Universe output, a Nexus Network output, a consortium output, a national company output, a Project SPV output, a provider output, a sponsor output, or a joint output; or

h) whether a name reference creates recognition, standing, finance-readiness, certification, procurement approval, public authority action, public warning, emergency command, investment recommendation, insurance approval, or other consequence beyond the record.

Where ambiguity exists, the use shall be held, corrected, clarified, restricted, re-labeled, withdrawn, or escalated before reliance or publication.

2.8 Distinction From The Global Centre for Risk and Innovation Generally. The expression “The Global Centre for Risk and Innovation” may describe the broader GCRI mission family, doctrine, public-good R&D function, institutional lineage, or coordinated global evidence-and-methods role only where the context does not misstate the legal identity of the Corporation.

GCRI Canada shall not represent itself as the whole of the GCRI mission family unless expressly authorized by a recorded instrument and only within the limits of that instrument. GCRI Canada may serve as a Canadian and global public-good anchor for evidence, methods, observability, ontology, technical truth, public-good software, open technical baselines, research integrity, and upstream R&D, but such role shall not imply ownership of all GCRI-related entities, automatic authority over GCRI US, control over future national or regional GCRI entities, or power to bind the broader GCRI mission family.

Where references to the broader GCRI function are necessary, the Corporation shall distinguish between:

a) the Corporation as a Canadian legal person;

b) GCRI Canada’s own corporate acts;

c) GCRI Canada’s public-good stewardship outputs;

d) any shared GCRI doctrine, vocabulary, methods, or technical baselines;

e) any GCRI US or other GCRI entity acts;

f) any cross-entity collaboration; and

g) any public-facing description of the broader GCRI function.

2.9 Distinction From GCRI US. GCRI Canada is legally distinct from GCRI US and from any United States entity using or associated with the GCRI name. Shared mission, shared doctrine, shared personnel, shared founders, shared advisors, shared methods, shared ontology, shared publications, shared technical baselines, shared repositories, shared programs, shared public-good assets, shared public authority interfaces, shared funders, shared sponsors, shared partners, or shared Nexus alignment shall not create merger, agency, branch status, alter ego status, parent-subsidiary status, single-employer status, joint-employer status, partnership, joint venture, shared treasury, shared liability, or mutual authority to bind.

All name uses involving GCRI US shall identify the relevant entity, role, authority surface, record owner, publication owner, asset owner, contractual party, data controller or processor role where applicable, and public-facing responsibility where such identification is material. Joint references shall be used only where accurate and supported by a recorded cooperation instrument, joint publication record, interface agreement, or other lawful record.

No director, officer, staff member, contractor, advisor, fellow, contributor, sponsor, donor, provider, host, public authority participant, or partner shall describe GCRI Canada and GCRI US as one legal entity, one treasury, one employer, one contracting party, one liability surface, or one governance body unless a lawful instrument expressly establishes the specific relationship described.

2.10 Distinction From The Global Risks Forum (GRF). GCRI Canada is legally, institutionally, and functionally distinct from The Global Risks Forum (GRF).

GRF is recognized within the Nexus public-good stack as the public-good registry, recognition, maturity-records, standing, claims-discipline, stakeholder-formation, public-safe reporting, and public-facing legitimacy steward. GCRI Canada may provide evidence, methods, observability, ontology, technical baselines, public-safe technical summaries, correction signals, Docket evidence inputs, Grid evidence inputs, and other upstream technical or research support to GRF-compatible processes where lawful and authorized.

No use of the GCRI Canada name, mark, output, evidence artifact, method, technical baseline, public-good software, publication, Academy material, Observatory method, Nexus Universe output, Docket input, Grid input, or public-safe report shall imply that GCRI Canada has issued GRF recognition, conferred standing, created public-facing legitimacy, determined maturity, approved claims, granted registry status, or performed any GRF function. Evidence support is not recognition issuance. Methods support is not standing. Technical review is not public legitimacy.

Any joint or sequential GCRI Canada / GRF reference shall identify the respective roles of GCRI Canada and GRF and shall preserve the distinction between upstream evidence stewardship and public-facing recognition or claims discipline.

2.11 Distinction From The Global Risks Alliance (GRA). GCRI Canada is legally, institutionally, and functionally distinct from The Global Risks Alliance (GRA).

GRA is recognized within the Nexus public-good stack as the finance-readiness, capital-readability, proof-pack, diligence-translation, insurance-readiness preparation, capital-reader engagement, common-business-interest, and resilience-finance interface steward. GCRI Canada may provide evidence quality records, technical baselines, methods notes, observability inputs, host-readiness evidence, resilience evidence, uncertainty notes, public-safe technical references, and correction signals to GRA-compatible processes where lawful and authorized.

No use of the GCRI Canada name, mark, evidence artifact, publication, method, technical baseline, dataset, software, dashboard, Observatory output, Nexus Universe output, Docket input, Grid input, or public-safe summary shall imply that GCRI Canada has made a finance-readiness determination, capital-readability determination, insurance-readiness determination, investment recommendation, underwriting decision, lending decision, credit decision, public finance approval, bankability determination, insurability determination, guarantee, rating, capital placement, investor solicitation, or transaction routing.

Technical evidence may support capital readability; it shall not become capital execution. GCRI Canada strengthens evidence; it does not sell, place, underwrite, rate, insure, lend, broker, advise on investments, approve public finance, or determine routeability.

2.12 Distinction From Nexus Network, Nexus Observatory, Nexus Standards, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, Consortiums, National Consortium Companies, Project SPVs, and Qualified Enterprise Providers. GCRI Canada is legally and functionally distinct from every Nexus network, program, instrument, operating surface, consortium, company, project vehicle, and provider structure, including Nexus Network, Nexus Observatory, Nexus Standards, Nexus Risk Management, Nexus Rails, Nexus Universe, Nexus Grid, Nexus Academy, Nexus Competence Cells, the Global Nexus Consortium, Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, National Consortium Companies, Project SPVs, qualified enterprise providers, sponsors, hosts, operators, vendors, contractors, and public authority participants.

GCRI Canada may support such bodies, systems, or instruments through evidence, methods, observability, ontology, technical baselines, public-good software, open reference architectures, research integrity, data governance methods, AI governance methods, cybersecurity methods, public-safe technical publication, public authority learning, Academy content, Docket evidence inputs, Grid evidence inputs, standards-supporting materials, Observatory methods, Nexus Universe technical review, and correction signals.

Such support shall not imply that GCRI Canada:

a) owns or operates the whole of Nexus Network;

b) operates Observatory Nodes, hubs, clusters, hotspots, national dense cores, regional clusters, or network infrastructure as an execution actor by default;

c) issues Nexus Standards certification, protocol entitlements, smart licenses, role keys, conformance approvals, ledger authority, or protocol-force determinations by default;

d) controls Nexus Risk Management outputs as public authority decisions, public warnings, or emergency commands;

e) controls Nexus Rails or determines finance-readiness, routeability, bankability, insurability, or capital placement;

f) grants Nexus Grid maturity, infrastructure status, participation status, or capability status;

g) issues Nexus Academy professional certification or regulated credentials by default;

h) converts Nexus Competence Cells into certification authorities, public authorities, procurement bodies, or provider-selection bodies;

i) controls consortiums, national consortium companies, Project SPVs, or qualified enterprise providers;

j) confers procurement preference, provider preference, sponsor benefit, public-private partnership status, public authority endorsement, commercial exclusivity, or market advantage; or

k) becomes an execution actor by reason of technical contribution, authorship, interoperability, annual build participation, public-good importance, public authority participation, sponsorship, or operational proximity.

2.13 Mark, Logo, Seal, Badge, Dataset, Software, Report, and Technical Baseline Name-Use Controls. All names, marks, logos, seals, badges, emblems, visual identities, dataset titles, software names, package names, repository names, API names, SDK names, dashboard names, report titles, method titles, evidence-pack titles, benchmark titles, public-good technical baseline titles, open reference architecture names, Academy labels, public authority learning labels, Nexus Universe labels, Observatory labels, Docket labels, Grid labels, and related identifiers associated with the Corporation shall be governed by name-use discipline.

The Board may approve policies governing name and mark use, including permissions, prohibitions, attribution rules, trademark or official mark registration where applicable, open-source naming rules, repository naming rules, software package naming rules, contributor attribution, public-safe publication labels, sponsor acknowledgment rules, provider acknowledgment rules, public authority reference rules, and correction procedures.

No mark, logo, seal, badge, dataset label, software name, report title, or technical baseline name shall be used to imply:

a) legal authority beyond the Corporation’s recorded authority;

b) certification, conformance approval, accreditation, compliance approval, or maturity status;

c) GRF recognition, GRA finance-readiness, Nexus Standards conformance, Nexus Grid admission, Nexus Docket approval, or public authority endorsement;

d) procurement approval, provider preference, preferred-provider status, public-private partnership, or commercial exclusivity;

e) investment approval, underwriting, insurance approval, lending approval, guarantee, rating, bankability, insurability, financeability, or routeability;

f) emergency command, public warning, public health order, evacuation instruction, dispatch authority, or incident-management authority;

g) sponsor, donor, funder, host, provider, investor, insurer, lender, public authority, university, laboratory, media, civil society, Indigenous, community, or partner control; or

h) ownership or control of assets, records, systems, repositories, datasets, software, methods, or technical baselines not actually owned or controlled by the Corporation.

2.14 Unauthorized Name Use, Misleading Use, Sponsor-Driven Use, Provider-Driven Use, Public Authority-Confusing Use, Finance-Signaling Use, and Certification-Implying Use. The following uses of the Corporation’s official legal name, approved short name, marks, logos, seals, badges, publications, records, software labels, dataset labels, technical baselines, or Nexus-related references are prohibited unless expressly authorized by competent recorded act and lawful under applicable law:

a) unauthorized use by any person or entity;

b) use suggesting that the Corporation has endorsed, certified, approved, selected, preferred, procured, financed, insured, rated, guaranteed, validated, recognized, or authorized a person, entity, product, service, technology, project, SPV, provider, sponsor, host, public authority, investment, insurance product, fund, procurement bid, or commercial offering;

c) use suggesting that participation in a GCRI Canada program, council, committee, working group, fellowship, Academy activity, controlled room, public authority learning room, Nexus Universe activity, Observatory activity, challenge, benchmark, repository, publication, or technical project creates recognition, certification, maturity, standing, public authority approval, finance-readiness, insurance-readiness, procurement advantage, or provider preference;

d) use in securities materials, investor decks, offering documents, project finance materials, lender materials, insurer materials, public finance materials, grant applications, bid documents, procurement responses, marketing materials, websites, social media, press releases, public authority submissions, or media statements in a manner that implies a status or authority not recorded;

e) sponsor-driven use that suggests sponsor control, sponsor endorsement by the Corporation, sponsor ownership of public-good outputs, pay-to-play influence, publication influence, research influence, evidence influence, Docket influence, Grid influence, standards influence, public authority access purchase, or outcome purchase;

f) provider-driven use that suggests preferred-provider status, required-provider status, provider certification, provider validation, procurement advantage, technical superiority determination, public authority endorsement, or standards approval by participation;

g) public authority-confusing use that suggests regulatory approval, public finance approval, procurement approval, public warning authority, emergency authority, official adoption, sovereign mandate, public-private partnership, statutory delegation, or public authority endorsement;

h) finance-signaling use that suggests investment suitability, capital-readiness, financeability, bankability, insurability, underwriting approval, lending approval, guarantee, rating, MDB approval, DFI approval, sovereign finance approval, or public finance approval;

i) certification-implying use that suggests technology certification, professional certification, standards certification, node certification, provider certification, AI system certification, cyber system certification, resilience outcome certification, or maturity certification by default; and

j) any use that is confusing, incomplete, stale, superseded, unsupported, unrecorded, unsafe, misleading, reputationally exploitative, legally inaccurate, or inconsistent with the Corporation’s public-benefit purpose and non-execution boundary.

2.15 Correction, Withdrawal, Takedown, and Public Clarification for Misuse. Where the Corporation becomes aware of unauthorized, misleading, stale, superseded, overbroad, finance-signaling, certification-implying, public authority-confusing, sponsor-driven, provider-driven, procurement-signaling, recognition-implying, or otherwise improper use of its official legal name, approved short name, marks, logos, seals, badges, records, publications, software, datasets, technical baselines, evidence artifacts, method notes, Observatory references, Nexus references, Academy references, Docket references, Grid references, or public authority references, the Corporation shall take corrective action proportionate to the nature, seriousness, reliance risk, public risk, legal risk, financial risk, public authority confusion, sponsor or provider capture risk, and reputational risk of the misuse.

Corrective action may include, without limitation:

a) internal correction;

b) controlled clarification;

c) public-safe clarification;

d) written notice to the misusing person or entity;

e) withdrawal of permission;

f) takedown demand;

g) revision or removal of marketing, investor, insurance, lending, procurement, public authority, media, website, social media, or public-facing materials;

h) correction of repository labels, dataset labels, software package names, report titles, dashboard labels, technical baseline names, or public-good asset references;

i) suspension or termination of participation, access, sponsorship, provider participation, contributor rights, council participation, fellowship, controlled-room access, or other relationship;

j) notice to affected public authorities, GRF, GRA, GCRI US, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Grid, Nexus Rails, Nexus Universe, consortiums, national consortium companies, Project SPVs, qualified enterprise providers, sponsors, donors, funders, hosts, partners, or other affected interfaces where necessary;

k) publication of a correction, clarification, retraction, withdrawal, supersession notice, or non-endorsement notice;

l) legal action where appropriate; and

m) preservation of a misuse record, correction record, reliance-risk assessment, and closeout record.

No corrective action shall be withheld merely because the misuse benefits the Corporation’s reputation, fundraising, visibility, sponsor relationship, provider relationship, public authority relationship, strategic positioning, media profile, or Nexus ecosystem influence. The Corporation’s name-use discipline shall be interpreted to preserve legal certainty, public trust, role separation, public-benefit fidelity, non-execution, provider neutrality, support-without-control, validity-by-record, and correctionability.

Section 3. Governing Statute, Corporate Form, Registered Office, and Canadian Seat

3.1 Governing Statute. The Corporation shall be governed by the statute under which it is incorporated, continued, amalgamated, revived, or otherwise constituted as a Canadian corporation without share capital, together with all regulations, statutory instruments, ministerial requirements, filing requirements, common-law principles, equitable principles, and other applicable Canadian federal, provincial, territorial, or municipal laws binding upon the Corporation.

For purposes of this Bylaw, the governing statute shall be read together with the Articles, this Bylaw, any required member resolution where applicable, any board resolution of constitutional or structural effect, and any superior legal requirement binding upon the Corporation. No provision of this Bylaw shall be interpreted to displace, avoid, narrow, or override a mandatory requirement of applicable law.

Where the governing statute is amended, replaced, re-enacted, interpreted by a competent authority, or supplemented by applicable regulation, guidance, filing requirement, or compliance obligation, this Bylaw shall be read in a manner that preserves lawful continuity, public-benefit purpose, nonprofit character, corporate capacity, director and officer accountability, record integrity, and the Corporation’s non-executing public-good stewardship function.

3.2 Canadian Not-for-Profit Corporate Character. The Corporation shall be maintained as a Canadian not-for-profit corporation. Its corporate character is public-benefit, nonprofit, non-share, non-distributing, non-executing, and public-good in orientation.

The Corporation exists to steward public-good research, evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, controlled vocabulary, research integrity, public-safe technical outputs, safeguards, and correctionable institutional memory. It shall not be operated for private profit, private inurement, commercial extraction, shareholder return, sponsor control, provider control, founder benefit, political control, market intermediation, public authority substitution, financial execution, procurement execution, or emergency-command execution.

The Corporation may receive lawful revenue, grants, donations, sponsorships, subscriptions, cost-recovery payments, fees, in-kind support, technical support, compute support, software support, facility support, equipment support, and other lawful support only in a manner consistent with its not-for-profit character, public-benefit purpose, non-distribution rule, support-without-control discipline, and this Bylaw.

3.3 Corporation Without Share Capital. The Corporation shall have no share capital. No director, officer, member, supporter, subscriber, donor, sponsor, funder, provider, host, vendor, contractor, employee, fellow, advisor, contributor, public authority participant, university, laboratory, community participant, Indigenous participant, civil society participant, media participant, founder, partner, national consortium company, Project SPV, investor, insurer, lender, or other person shall hold any share, equity interest, profit interest, residual claim, carried interest, capital account, beneficial ownership interest, or transferable ownership interest in the Corporation.

No person shall acquire any ownership interest in the Corporation’s name, mission, records, registers, methods, evidence systems, observability systems, ontologies, schemas, controlled vocabularies, data dictionaries, software, repositories, technical baselines, public-good technical assets, public-safe outputs, governance instruments, institutional standing, or Nexus interface position by reason of contribution, authorship, funding, sponsorship, membership, subscription, participation, technical integration, hosting, collaboration, employment, contracting, advisory role, public authority participation, or operational proximity.

The absence of share capital shall be interpreted broadly to protect the Corporation from equity-like capture, private benefit, sponsor-driven control, provider-driven control, donor-driven control, founder inurement, hidden extraction, mission enclosure, and conversion of public-good institutional assets into private cap-table value.

3.4 Registered Office. The Corporation shall maintain its registered office in Canada at the place recorded in the Corporation’s statutory filings, corporate register, minute book, and authoritative governance records.

The registered office shall serve as the formal address for statutory notices, corporate filings, service of documents where applicable, custody references, corporate-record references, and other legal purposes required by applicable law. The registered office may also serve as the Corporation’s governance seat where so designated by the Board, but the Board may designate additional administrative, programmatic, technical, repository, or operational locations where lawful and consistent with this Bylaw.

The existence of program offices, hosted workspaces, laboratories, controlled rooms, cloud systems, technical repositories, data environments, public authority rooms, Academy rooms, Nexus Universe workspaces, Observatory-related sites, sponsor-provided facilities, university-hosted spaces, regional hubs, national interfaces, or foreign activity locations shall not change the Corporation’s registered office unless a lawful change is approved and recorded.

3.5 Canadian Governance Seat. The Corporation’s governance seat shall be Canada. The Canadian governance seat is the primary internal corporate-law anchor for the Corporation’s board governance, officer authority, member rights where applicable, fiduciary duties, corporate records, bylaw authority, delegation architecture, register discipline, statutory filings, corporate continuity, and internal legal acts.

The Canadian governance seat shall not prevent the Corporation from conducting lawful international, regional, cross-border, virtual, hybrid, technical, research, publication, learning, public authority, Academy, Observatory, Nexus Universe, Nexus Standards, Nexus Rails, Nexus Grid, consortium-interface, or partner-interface activities. Such activities shall remain subject to the Corporation’s Canadian corporate identity, applicable local law, lawful contractual controls, data and safeguards requirements, public authority boundary discipline, non-execution boundary, and this Bylaw.

No person shall use the Corporation’s global reach, Nexus alignment, international partnerships, public authority participation, regional consortium interface, national consortium interface, or technical presence in another jurisdiction to claim that the Corporation has abandoned, diluted, transferred, fractured, or subordinated its Canadian governance seat.

3.6 Canada as Record-of-Record Jurisdiction. Canada shall be the Corporation’s record-of-record jurisdiction for internal corporate acts. The Corporation’s Articles, Bylaw, board records, member records where applicable, director register, officer register, committee and council records, corporate resolutions, statutory filings, official registers, bylaw adoption records, amendment records, supersession records, corporate notices, and authoritative governance instruments shall be maintained under the discipline of the Canadian corporate-law record.

For internal corporate purposes, the authoritative record shall be the record approved, held, authenticated, or referenced in accordance with this Bylaw and applicable Canadian law. Foreign copies, partner copies, sponsor copies, public authority copies, technical repository copies, working copies, translations, extracts, summaries, decks, project files, data-room copies, controlled-room copies, AI-generated copies, or unofficial circulating versions shall not displace the Canadian record-of-record unless expressly adopted or incorporated by lawful recorded act.

Where records are mirrored, dual-logged, interoperable, stored in cloud environments, anchored to ledgers, referenced in Nexus-compatible systems, shared with GRF, GRA, GCRI US, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Grid, Nexus Rails, Nexus Universe, consortiums, national companies, Project SPVs, providers, public authorities, sponsors, hosts, universities, laboratories, or other partners, the Canadian record-of-record shall remain identifiable, authoritative, and correctionable.

3.7 Canada as Custody Location for Authoritative Governance Records. The Corporation shall maintain custody, control, or lawful access to its authoritative governance records in a manner consistent with its Canadian corporate obligations. The Board may approve physical, digital, cloud, encrypted, distributed, mirrored, or backup custody systems, provided that such systems preserve authenticity, integrity, confidentiality, accessibility, retention, legal hold capability, auditability, correctionability, and lawful control.

The Corporation’s authoritative governance records may be stored or backed up in secure digital systems, including systems physically or logically located outside Canada, only where such storage is lawful, risk-reviewed, access-controlled, contractually governed where applicable, and consistent with privacy, cybersecurity, sanctions, export-control, public authority, protected knowledge, and records-retention obligations.

No technical custody system, cloud platform, repository provider, database, ledger, file-sharing environment, collaboration tool, AI system, vendor platform, sponsor-provided system, provider-hosted system, university-hosted system, or public authority system shall become the legal custodian of the Corporation’s governance authority by hosting, indexing, mirroring, backing up, processing, or anchoring records.

3.8 Canada as Conflict-of-Law Anchor for Internal Corporate Acts. For internal corporate acts, Canada shall serve as the conflict-of-law anchor. Questions concerning the Corporation’s internal governance, board authority, director duties, officer authority, member rights where applicable, bylaw interpretation, corporate records, internal delegations, registered office, corporate status, statutory filings, adoption of governance instruments, amendment of governance instruments, and corporate continuity shall be determined by applicable Canadian law, the Articles, this Bylaw, and the Corporation’s authoritative Canadian governance record.

This conflict-of-law rule shall not be used to evade local law applicable to the Corporation’s activities outside Canada, including laws concerning contracts, employment, tax, privacy, cybersecurity, data residency, export controls, sanctions, research ethics, controlled technologies, public authority interaction, procurement, competition, intellectual property, consumer protection, health and safety, Indigenous rights, community safeguards, environmental protection, or other locally applicable requirements.

Where a conflict or apparent conflict arises between Canadian internal corporate governance requirements and foreign operational, contractual, public authority, data, research, technology, or participation requirements, the matter shall be escalated in accordance with this Bylaw. Pending resolution, the Corporation shall adopt the most protective lawful posture and shall not proceed in a manner that creates unauthorized execution, public authority confusion, finance-readiness overclaim, certification overclaim, procurement implication, data or safeguards harm, sponsor or provider capture, or role collapse.

3.9 Non-Extraterritorial Effect. The Corporation’s Canadian incorporation, Canadian governance seat, Canadian record-of-record jurisdiction, public-benefit purpose, public-good stewardship role, Nexus alignment, international collaboration, or cross-border technical activity shall not be interpreted as a claim of extraterritorial governmental, regulatory, sovereign, treaty, public authority, procurement, certification, financial, insurance, emergency, public-warning, or enforcement power.

The Corporation may lawfully conduct, support, publish, convene, research, educate, maintain repositories, develop technical baselines, steward methods, operate controlled rooms, provide technical evidence support, and collaborate across borders, but such activity shall not convert the Corporation into:

a) a foreign public authority;

b) a supranational authority;

c) a treaty organization;

d) a regulator;

e) a procurement authority;

f) a standards body with compulsory legal force;

g) a certification authority by default;

h) an emergency-management authority;

i) a public-warning authority;

j) a finance, insurance, securities, lending, rating, or capital-placement intermediary;

k) a public finance approval body; or

l) an execution vehicle.

All cross-border outputs shall be classified, described, limited, and corrected as required to prevent false extraterritorial meaning.

3.10 Cross-Border Operations Without Foreign Sovereign Authority. The Corporation may operate, support, or participate in lawful cross-border activities, including research collaborations, public authority learning, technical workshops, Academy activities, Nexus Universe activities, Nexus Observatory methods support, Nexus Standards support, data and AI governance work, cybersecurity work, climate and disaster resilience work, public-good software development, controlled-room work, evidence review, public-safe publication, consortium-interface support, and partner-interface support.

Such activities shall be conducted as nonprofit, public-benefit, evidence, methods, observability, ontology, research, technical, educational, public-good, or governance-support activities within the Corporation’s lawful capacity. They shall not be represented as foreign sovereign authority, public authority delegation, emergency command, public warning, regulatory approval, procurement approval, certification, public finance approval, investment approval, insurance approval, market authorization, legal compliance approval, or mandated standards adoption.

Where a foreign government, public authority, multilateral body, development finance institution, regulator, public infrastructure operator, emergency-management body, public health body, utility, port, telecom authority, energy authority, water authority, food authority, cyber authority, public safety body, Indigenous authority, or community governance body participates in a Corporation activity, the Corporation shall classify the participation capacity and preserve non-endorsement, non-delegation, and non-execution boundaries.

3.11 Local Law Respect in Foreign Operations. The Corporation shall respect applicable local law in every jurisdiction where it conducts, supports, funds, convenes, publishes, contracts, employs, collects data, processes data, transfers data, deploys systems, hosts rooms, releases software, maintains repositories, engages public authorities, conducts research, involves participants, receives funds, provides training, or otherwise acts.

Local law respect shall include, where applicable:

a) corporate registration, extra-provincial, foreign registration, licensing, notice, or filing requirements;

b) tax, fiscal, invoicing, withholding, and payment requirements;

c) employment, contractor, volunteer, workplace, health, safety, immigration, and labour requirements;

d) privacy, data protection, data residency, cybersecurity, breach notification, secure processing, AI governance, and digital services requirements;

e) sanctions, anti-corruption, anti-bribery, anti-money-laundering, export-control, controlled-technology, and restricted-party requirements;

f) research ethics, human-subjects, public health, environmental, Indigenous, community, cultural, and protected-knowledge requirements;

g) public authority interaction, lobbying, procurement, freedom-of-information, records, official-language, accessibility, and public communications requirements;

h) intellectual property, open-source, licensing, standards, data rights, moral rights, and attribution requirements;

i) competition, antitrust, market-conduct, benchmarking, clean-room, and competitively sensitive information requirements; and

j) emergency-management, public warning, public safety, critical infrastructure, telecom, energy, water, food, health, cyber, geospatial, and security-sensitive requirements.

Where compliance is uncertain, the Corporation shall hold, narrow, compartmentalize, externalize, re-scope, or suspend the relevant activity until a lawful and boundary-safe path is recorded.

3.12 Change of Registered Office or Governance Seat. The registered office may be changed only in accordance with applicable law, the Articles, this Bylaw, and a duly authorized corporate record. The Board may approve a change of registered office where lawful, unless member approval, filing, notice, or other legal requirement applies.

Any proposed change of registered office, governance seat, record-of-record jurisdiction, custody location for authoritative records, or internal corporate-law anchor shall be treated as a governance-significant act. Before approval, the Board shall consider:

a) statutory authority and filing requirements;

b) effect on corporate status;

c) effect on board and member governance;

d) effect on director and officer duties;

e) effect on nonprofit, non-share, non-distributing, and public-benefit character;

f) effect on tax, fiscal, audit, grant, donation, sponsorship, and restricted-fund obligations;

g) effect on corporate records, repositories, retention, legal holds, access, and continuity;

h) effect on privacy, data, AI, cybersecurity, controlled-room, protected knowledge, and cross-border transfer controls;

i) effect on public authority interfaces and public-facing claims;

j) effect on GCRI US, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Grid, Nexus Rails, Nexus Academy, consortiums, national companies, Project SPVs, providers, sponsors, hosts, universities, laboratories, and other interfaces;

k) effect on non-execution, role separation, public-benefit mission lock, validity-by-record, and correctionability; and

l) any transitional, correction, notice, or supersession steps required.

No change of office, seat, custody, or jurisdictional reference shall be used to weaken the Corporation’s mission lock, public-good stewardship burden, non-execution boundary, legal separateness, provider neutrality, support-without-control rule, data and safeguards duties, or Canadian corporate-record discipline unless a lawful reorganization expressly and transparently provides otherwise.

3.13 Records of Seat, Filings, and Statutory Compliance. The Corporation shall maintain complete, current, and correctionable records of its registered office, governance seat, corporate filings, annual returns, director and officer records, member records where applicable, statutory registers, minute books, resolutions, Bylaw versions, Articles, filings, notices, confirmations, corporate-status documents, tax-status documents, nonprofit-status records, insurance records, registered-agent or service records where applicable, and other statutory compliance records.

The records required under this Section shall identify:

a) the legal name used in each filing or record;

b) the filing authority or recipient;

c) the filing date;

d) the effective date, if different;

e) the person or office responsible for the filing;

f) the statutory basis or requirement;

g) the current status of the filing or record;

h) any deadline, renewal, annual return, confirmation, amendment, correction, or follow-up requirement;

i) any discrepancy, rejection, amendment, correction, or supersession;

j) any public, internal, controlled, confidential, or restricted access classification; and

k) the repository location and custodian.

The Secretary, or such other officer or governance-record custodian as the Board may designate, shall maintain the seat, filing, and statutory compliance record. Any inconsistency between statutory filings, the Articles, this Bylaw, the registered office record, the governance repository, public-facing materials, partner materials, public authority materials, or Nexus interface materials shall be corrected through the Corporation’s correction and supersession process.

No person shall represent the Corporation’s seat, governing law, registered office, statutory status, tax status, nonprofit status, public-benefit status, or legal capacity in a manner inconsistent with the authoritative record. Any inaccurate or misleading representation shall be corrected, withdrawn, clarified, or publicly corrected where necessary to preserve legal certainty, public trust, role separation, and the Corporation’s Canadian governance discipline.

Section 4. Nonprofit, Non-Share, Non-Charitable, Non-Distributing, and Public-Benefit Character

4.1 Nonprofit Character. The Corporation shall be maintained as a nonprofit corporation and shall be organized, governed, operated, funded, administered, represented, and interpreted exclusively in a manner consistent with its nonprofit character, public-benefit purpose, non-share form, non-distributing status, and public-good stewardship burden.

The Corporation shall not be operated for the pecuniary gain, private profit, private inurement, capital appreciation, commercial control, sponsor advantage, provider advantage, founder benefit, donor control, investor return, market intermediation, or proprietary extraction of any director, officer, member, participant, supporter, subscriber, donor, sponsor, funder, provider, host, vendor, contractor, employee, fellow, advisor, contributor, public authority participant, university, laboratory, partner, national consortium company, Project SPV, investor, insurer, lender, operator, affiliate, related person, or private person.

The Corporation may generate, receive, hold, manage, apply, and reinvest lawful funds, grants, donations, sponsorships, subscriptions, dues, cost-recovery fees, service fees, training fees, technical-support payments, in-kind contributions, software support, compute support, equipment support, facility support, restricted funds, unrestricted funds, and other lawful support, provided that all such resources are used to advance the Corporation’s lawful purposes and are subject to this Bylaw, applicable law, fiscal controls, restricted-fund obligations, conflict controls, anti-capture rules, public-benefit discipline, and the non-distribution rule.

The nonprofit character of the Corporation shall not be weakened by the scale, sophistication, commercial relevance, technical value, strategic importance, fundability, sponsor interest, public authority interest, enterprise utility, or Nexus-wide importance of its research, evidence systems, methods, observability systems, ontologies, software, repositories, technical baselines, publications, Academy activities, controlled rooms, public authority learning, Nexus Universe support, Observatory methods, Docket inputs, Grid inputs, or finance-readiness evidence inputs.

4.2 Non-Share Capital Character. The Corporation shall be a corporation without share capital. No share, unit, equity instrument, membership interest in the nature of equity, profit participation, carried interest, residual economic claim, liquidation preference, ownership token, governance token, beneficial ownership interest, capital account, convertible interest, derivative economic right, or similar ownership instrument shall be issued by or in respect of the Corporation.

No person shall acquire ownership, economic entitlement, control right, or proprietary governance right in the Corporation by reason of:

a) incorporation, founding, sponsorship, donation, grant-making, funding, subscription, membership, participation, contribution, authorship, employment, contracting, volunteering, advisory service, fellowship, hosting, technical integration, public authority participation, public reputation, or Nexus alignment;

b) contribution of money, equipment, compute, data, software, code, models, datasets, sensors, AI-RAN assets, O-RAN assets, telecommunications assets, cybersecurity tools, dashboards, repositories, facilities, cloud credits, professional services, strategic advice, public authority access, media visibility, research capacity, or technical infrastructure;

c) participation in the Board, any committee, council, working group, advisory body, Academy activity, controlled room, public authority room, evidence room, data room, Nexus Universe activity, Observatory activity, Nexus Standards activity, Nexus Rails activity, Nexus Grid activity, Nexus Docket activity, or Nexus Competence Cell activity; or

d) relationship with GCRI US, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Observatory, Nexus Standards, Nexus Risk Management, Nexus Rails, Nexus Universe, Nexus Grid, Nexus Academy, Global Nexus Consortium, Regional Nexus Consortiums, National Nexus Consortiums, National Consortium Companies, Project SPVs, qualified enterprise providers, sponsors, hosts, public authorities, universities, laboratories, or partners.

The non-share character of the Corporation shall be interpreted to prevent equity-like capture, tokenized capture, contractual capture, governance-right capture, sponsor capture, provider capture, donor capture, founder capture, public authority capture, or conversion of the public-good rail into private cap-table value.

4.3 Non-Distribution Rule. No part of the income, property, surplus, accumulated funds, public-good assets, technical assets, evidence systems, methods, observability systems, ontologies, schemas, controlled vocabularies, software, repositories, data tools, technical baselines, public-safe outputs, institutional records, registers, goodwill, name, marks, or institutional standing of the Corporation shall be distributed, transferred, assigned, applied, pledged, encumbered, licensed, released, used, or made available for the private benefit of any person except as expressly permitted by applicable law, the Articles, this Bylaw, and a duly authorized corporate record.

The Corporation may make lawful payments, transfers, reimbursements, grants, stipends, awards, scholarships, fellowships, salaries, benefits, honoraria, contractor payments, vendor payments, indemnification payments, insurance payments, settlement payments, refunds, cost-sharing payments, or other payments where such payments are:

a) fair, reasonable, documented, and approved under the Corporation’s authority matrix;

b) consistent with the Corporation’s public-benefit purpose and nonprofit character;

c) not a disguised dividend, profit distribution, equity return, success fee for prohibited capital raising, hidden inurement, control payment, influence payment, or outcome purchase;

d) subject to conflict-of-interest, related-party, procurement, fiscal, audit, restricted-fund, and private-benefit review where applicable;

e) recorded in the Corporation’s financial and governance records; and

f) compliant with applicable law.

The non-distribution rule shall apply during the Corporation’s existence and upon dissolution, wind-up, amalgamation, continuance, reorganization, transfer of public-good assets, transfer of technical assets, or other structural change. No dissolution, reorganization, transfer, license, project closeout, repository migration, national localization, cross-entity interface, or Nexus transition shall be used to divert public-good assets to private benefit.

4.4 No Private Inurement. No director, officer, member, participant, supporter, subscriber, founder, donor, sponsor, funder, provider, host, vendor, contractor, employee, fellow, advisor, contributor, public authority participant, university, laboratory, community participant, Indigenous participant, civil society participant, media participant, partner, national consortium company, Project SPV, investor, insurer, lender, operator, affiliate, related person, or other private person shall receive improper private inurement from the Corporation.

Improper private inurement includes, without limitation:

a) excessive compensation, unreasonable reimbursement, disguised bonus, unauthorized benefit, below-market transfer, above-market payment, preferential contract, unjustified consulting arrangement, unsupported stipend, unapproved honorarium, or related-party advantage;

b) sponsor, donor, provider, host, public authority, investor, insurer, lender, national company, Project SPV, or partner control over research findings, evidence classification, methods, technical baselines, publications, public-safe summaries, Academy content, public authority access, Docket inputs, Grid inputs, Nexus-compatible claims, standards-supporting materials, or correction decisions;

c) private appropriation of public-good software, open technical baselines, reference architectures, schemas, ontologies, evidence systems, observability systems, controlled vocabularies, technical libraries, data tools, dashboards, benchmark harnesses, proof-receipt logic, training materials, or other public-good technical assets;

d) preferential access to non-public data, controlled rooms, evidence rooms, public authority rooms, capital-reader rooms, technical repositories, vulnerability information, protected knowledge, public authority contacts, sponsor intelligence, provider intelligence, or other restricted materials without lawful authorization and recorded access controls;

e) use of the Corporation’s name, marks, outputs, records, publications, technical baselines, datasets, software, Academy materials, Nexus references, Observatory references, Docket references, Grid references, public authority references, or public-good standing to imply endorsement, certification, finance-readiness, procurement advantage, public authority approval, provider preference, or investment suitability beyond the record; and

f) any other benefit inconsistent with the Corporation’s nonprofit character, public-benefit purpose, fiduciary governance, non-execution boundary, support-without-control rule, provider neutrality, procurement neutrality, or role-separation obligations.

The Board shall cause the Corporation to maintain policies, registers, review procedures, approvals, recusals, reasonableness checks, comparability records, related-party records, restricted-fund controls, and correction processes sufficient to detect, prevent, address, and record private inurement risk.

4.5 Non-Charitable Status Unless Lawfully Changed. Unless and until the Corporation is lawfully registered, recognized, or otherwise confirmed as a charity under applicable law, the Corporation shall not represent itself as a registered charity, charitable corporation, charitable donee, qualified donee, tax-credit-issuing charity, foundation, charitable trust, or charitable fundraising vehicle.

The Corporation may be nonprofit and public-benefit in character without being a registered charity. No director, officer, member, participant, donor, sponsor, funder, provider, host, public authority participant, contractor, employee, fellow, advisor, contributor, partner, or representative shall state, imply, advertise, receipt, invoice, solicit, contract, or correspond as if the Corporation possesses charitable status unless such status has been lawfully obtained, recorded, and authorized for use.

Until charitable status is lawfully obtained, all donations, grants, sponsorships, subscriptions, dues, cost-recovery fees, in-kind contributions, and other support shall be described, receipted, accounted for, taxed, acknowledged, and publicly represented in a manner consistent with the Corporation’s actual legal and tax status.

Any future proposal to seek, obtain, surrender, alter, preserve, suspend, restrict, or publicly represent charitable status shall be treated as a reserved governance matter requiring legal, tax, fiscal, mission-lock, public-benefit, private-benefit, restricted-fund, sponsorship, public-communications, and Nexus-interface review. No charitable-status change shall be used to weaken the Corporation’s non-execution boundary, provider neutrality, public authority boundary, role separation, data and safeguards obligations, public-safe publication discipline, or public-good technical stewardship burden.

4.6 Public-Benefit Purpose. The Corporation shall be operated for public-benefit purposes. Its public-benefit purpose is to steward and advance public-good research, evidence, methods, observability, ontology, technical truth, public-good software, open technical baselines, research integrity, public-safe reporting inputs, public authority learning, safeguards, correctionability, and systems-intelligence capacity for complex systemic risks and mission-critical technologies.

The Corporation’s public-benefit purpose shall include, without limitation, lawful activities directed to:

a) improving evidence quality, evidence provenance, source lineage, evidence classification, evidence challengeability, evidence correction, and evidence-to-decision-support translation without decision substitution;

b) developing, reviewing, publishing, and preserving methods for validation, corroboration, uncertainty, confidence scoring, sensor fusion, AI output review, AI-RAN signal interpretation, DePIN validation, digital twin assumption review, geospatial evidence, cyber evidence, climate and disaster evidence, public health evidence, infrastructure evidence, and systemic-risk evidence;

c) stewarding observability approaches for physical, digital, cyber-physical, human-machine, environmental, infrastructure, public authority, community, and mission-critical systems;

d) maintaining ontologies, schemas, taxonomies, data dictionaries, controlled vocabularies, AI-readable knowledge structures, and semantic interoperability across GCRI, GRF, GRA, Nexus Network, Nexus Observatory, Nexus Standards, Nexus Risk Management, Nexus Rails, Nexus Universe, Nexus Grid, Nexus Academy, consortiums, national companies, Project SPVs, qualified providers, and public authority interfaces;

e) developing public-good software, open technical baselines, reference architectures, test harnesses, dashboards, APIs, SDKs, data tools, proof-receipt-supporting logic, and technical libraries under lawful governance and anti-enclosure protections;

f) supporting public authority learning, evidence literacy, technical literacy, AI governance literacy, cybersecurity literacy, Observatory literacy, and public-safe reporting literacy without exercising public authority;

g) supporting Nexus-compatible evidence inputs to GRF, GRA, Nexus Standards, Nexus Observatory, Nexus Docket, Nexus Grid, Nexus Rails, Nexus Universe, and related public-good interfaces without exercising the downstream functions of those bodies;

h) protecting data, privacy, cybersecurity, AI governance, research ethics, Indigenous, local, territorial, cultural, environmental, community, health-sensitive, and protected knowledge safeguards; and

i) preserving validity-by-record, correctionability, public-safe publication, institutional memory, and role separation.

The public-benefit purpose shall be interpreted expansively enough to permit world-class technical stewardship, but narrowly enough to prevent the Corporation from becoming a market actor, public authority substitute, finance intermediary, certification body by default, procurement authority, emergency-command actor, public-warning actor, or execution vehicle.

4.7 Public-Good Stewardship Burden. The Corporation shall bear an affirmative public-good stewardship burden. Public-good stewardship is not passive observation, branding, convening, commentary, consultancy, event management, advocacy, publication, sponsorship administration, or ecosystem narration. It is active custodianship of the upstream evidence, methods, observability, ontology, technical-truth, software, open-baseline, safeguards, and correction infrastructure necessary for trusted public-benefit use of complex technologies.

The Corporation’s public-good stewardship burden shall require the Corporation to:

a) preserve public-good assets against private enclosure, dependency lock-in, sponsor control, provider capture, donor capture, founder capture, public authority confusion, pay-to-play influence, and commercial overclaim;

b) maintain records sufficient to identify ownership, custody, authority surface, access class, publication class, version, limitation, correction path, supersession status, and public-safe status of material public-good assets;

c) ensure that public-good outputs remain usable, interoperable, reviewable, challengeable, correctionable, and portable where lawful and appropriate;

d) distinguish public-good stewardship from operation, ownership, execution, certification, recognition, finance-readiness, procurement, public authority action, or market intermediation;

e) protect public-safe publication from unsafe disclosure, overclaim, under-contextualization, sponsor influence, provider influence, public authority confusion, or unsupported public meaning;

f) provide clear boundaries for enterprise-stack actors, national consortium companies, Project SPVs, qualified providers, sponsors, hosts, operators, investors, insurers, lenders, and public authorities; and

g) maintain institutional memory across leadership, funding, technology, partner, program, repository, jurisdictional, and Nexus-interface changes.

The Corporation shall treat public-good stewardship as a constitutional obligation of governance, not as a discretionary program activity.

4.8 Public-Good Technical Institution Character. The Corporation shall be maintained as a public-good technical institution. Its technical character shall include scientific, engineering, computational, evidentiary, data, AI, cyber, telecommunications, observability, ontology, software, systems, standards-supporting, and public-safe publication functions, but shall remain subordinate to its public-benefit purpose and non-execution boundary.

The Corporation may develop, steward, test, document, review, maintain, and publish technical artifacts, including reference architectures, public-good software, open technical baselines, schemas, APIs, SDKs, data dictionaries, dashboards, test harnesses, benchmark cards, system cards, model cards, dataset cards, evidence-pack templates, confidence methods, proof-receipt-supporting logic, observability methods, AI governance methods, cyber methods, AI-RAN methods, DePIN validation methods, digital twin review methods, geospatial methods, and secure release procedures.

The technical character of the Corporation shall not cause it to become:

a) a vendor, systems integrator, managed-service provider, cloud provider, telecom operator, AI provider, cybersecurity provider, infrastructure operator, sensor operator, DePIN operator, token issuer, marketplace operator, or commercial platform;

b) a standards authority with external legal force unless separately and lawfully constituted;

c) a certification, accreditation, compliance-approval, maturity-approval, conformance-approval, or provider-approval body by default;

d) a public authority, regulator, emergency-management body, public-warning body, procurement authority, or official incident-management body;

e) a finance, insurance, lending, underwriting, rating, securities, fund, capital-placement, or public-finance actor; or

f) the owner or operator of the entire Nexus Network, Nexus Observatory, Nexus Universe, Nexus Grid, Nexus Rails, Nexus Standards, Nexus Academy, national consortium company layer, Project SPV layer, or qualified enterprise provider layer.

Technical competence shall strengthen public-good stewardship. It shall not inflate institutional authority.

4.9 Research, Evidence, Methods, Observability, Ontology, and Technical Truth Character. The Corporation’s core institutional character shall be upstream research, evidence, methods, observability, ontology, and technical truth.

For purposes of this Bylaw:

a) research shall mean public-benefit inquiry, analysis, experimentation, prototyping, evaluation, synthesis, publication, and learning directed to systemic-risk, resilience, public-good technology, institutional, and mission-critical questions;

b) evidence shall mean recorded, source-linked, context-bearing, classified, reviewable, challengeable, confidence-aware, limitation-aware, and correctionable material capable of supporting public-benefit understanding without becoming decision authority by itself;

c) methods shall mean structured approaches for collecting, validating, comparing, interpreting, testing, reproducing, challenging, correcting, and communicating evidence and technical outputs;

d) observability shall mean the disciplined design, collection, correlation, review, and public-safe interpretation of signals across physical, digital, cyber-physical, environmental, infrastructure, social, institutional, and AI-mediated systems;

e) ontology shall mean the controlled semantic infrastructure by which categories, relationships, evidence classes, maturity concepts, technology families, public authority capacities, finance-readiness boundaries, certification boundaries, and Nexus role meanings are made interoperable; and

f) technical truth shall mean confidence-bounded, provenance-bearing, method-supported, reviewable, limitation-aware, and correctionable technical understanding, not absolute certainty, public authority decision, official warning, recognition, certification, finance-readiness, procurement approval, or market recommendation.

The Corporation shall preserve the sequence: evidence before recognition, methods before claims, observability before public meaning, ontology before interoperability, technical baselines before deployment, and correctionability before reliance.

4.10 Public-Good Software and Open Technical Baseline Character. The Corporation may develop, steward, maintain, release, license, govern, and retire public-good software and open technical baselines in furtherance of its public-benefit purpose.

Public-good software and open technical baselines may include, without limitation, schemas, APIs, SDKs, reference implementations, ontology tools, data dictionaries, dashboards, evidence tools, observability tools, AI governance tools, cyber tools, test harnesses, benchmark assets, validation scripts, gold vectors, negative tests, documentation, method libraries, model cards, dataset cards, system cards, benchmark cards, proof-receipt-supporting components, secure release processes, and interoperability profiles.

All such assets shall be subject to governance controls addressing:

a) ownership, authorship, contribution, licensing, attribution, moral rights, copyright, patent, trademark, open-source compliance, defensive publication, and anti-enclosure posture;

b) secure development lifecycle, code review, dependency management, software bill of materials, vulnerability handling, signing, provenance, release, rollback, deprecation, retirement, and incident response;

c) data, AI, cybersecurity, privacy, export-control, sanctions, controlled-technology, public authority, and protected-knowledge review;

d) public-safe publication class, access class, handling class, version status, maintenance status, limitation language, and correction pathway;

e) compatibility with Nexus Standards, Nexus Observatory, Nexus Network, Nexus Grid, Nexus Rails, Nexus Universe, Nexus Academy, GRF, GRA, GCRI US, consortiums, national companies, Project SPVs, and qualified providers where applicable; and

f) express boundary language stating that software release, baseline publication, interoperability mapping, reference implementation, test harness, proof receipt, or technical compatibility does not by itself constitute certification, conformance approval, public authority approval, procurement approval, finance-readiness determination, insurance approval, investment approval, provider preference, or operational mandate.

The Corporation shall not permit public-good software or open technical baselines to be converted into private lock-in instruments, sponsor-controlled infrastructure, provider-controlled standards, hidden commercial gateways, or de facto procurement mandates.

4.11 Non-Market and Non-Executing Character. The Corporation shall be non-market and non-executing in institutional character. It may support markets, public authorities, public-good institutions, enterprise actors, investors, insurers, lenders, universities, communities, and Nexus interfaces with evidence, methods, observability, technical baselines, public-safe summaries, learning, and correctionable records, but it shall not itself act as a market intermediary, execution vehicle, transaction platform, public authority substitute, or regulated execution actor.

The Corporation shall not:

a) offer, sell, place, distribute, solicit, broker, arrange, recommend, underwrite, rate, insure, reinsure, lend, guarantee, custody, clear, settle, manage, advise upon, or intermediate securities, investments, insurance, loans, guarantees, public finance, funds, payments, capital flows, or financial products;

b) award procurement, select public vendors, determine preferred providers, approve bidders, issue procurement recommendations, or act as a public procurement authority;

c) issue public warnings, emergency alerts, evacuation instructions, public health orders, incident commands, dispatch instructions, operational commands, or emergency-management directions;

d) regulate, enforce, inspect, license, permit, certify legal compliance, grant safe harbor, or replace public regulators;

e) certify technologies, providers, nodes, AI systems, cyber systems, resilience outcomes, professional competence, standards compliance, maturity, or conformance by default;

f) operate as a national consortium company, Project SPV, enterprise platform, infrastructure owner, provider, operator, vendor, systems integrator, managed-service provider, or commercial delivery actor by default; or

g) treat AI outputs, dashboards, digital twins, DePIN records, AI-RAN signals, sensor signals, compute attestations, proof receipts, blockchain entries, public-safe reports, or technical baselines as final authority.

Where an activity may be interpreted as market-facing, finance-facing, procurement-facing, certification-facing, public authority-facing, emergency-facing, or execution-facing, the Corporation shall apply the regulatory-perimeter escalation, hold, quarantine, re-scope, externalize, or terminate rules set out in this Bylaw.

4.12 No Representation as Charity, Public Authority, Regulator, Treaty Organization, Sovereign Standards Body, Financial Intermediary, Market Operator, Insurer, Lender, Fund, Broker, Dealer, or Execution Vehicle. The Corporation shall not represent itself, and no person acting for or in relation to the Corporation shall represent the Corporation, as any of the following unless such status has been lawfully obtained, expressly authorized, accurately described, and recorded:

a) registered charity, charitable foundation, qualified donee, charitable trust, tax-credit-issuing entity, or charitable fundraising vehicle;

b) public authority, government agency, Crown entity, municipal body, Indigenous government, regulator, enforcement body, statutory delegate, treaty organization, intergovernmental organization, public-private partnership authority, sovereign standards body, emergency-management authority, public-warning authority, or official incident-command body;

c) certification body, accreditation body, compliance approval body, professional credentialing body, maturity authority, public-facing recognition authority, standards authority with compulsory legal force, or protocol authority by default;

d) securities dealer, broker, finder, placement agent, underwriter, investment adviser, portfolio manager, asset manager, fund, fund manager, lender, bank, credit provider, payment intermediary, custodian, clearing agency, settlement system, insurer, reinsurer, insurance broker, insurance agent, guarantor, rating agency, credit assessor, investment-grade assessor, bankability assessor, insurability assessor, or public finance approval body;

e) marketplace, exchange, commercial platform, procurement platform, project developer, project sponsor, national consortium company, Project SPV, asset owner, infrastructure operator, telecom operator, AI provider, cybersecurity provider, cloud provider, managed-service provider, systems integrator, vendor, or enterprise delivery vehicle; or

f) any other status inconsistent with the Corporation’s actual legal character, nonprofit status, public-benefit purpose, non-share form, non-distribution rule, public-good technical stewardship burden, role separation, and non-execution boundary.

All public-facing descriptions, contracts, grant applications, sponsorship materials, donor materials, public authority briefings, Academy materials, publications, websites, social media, investor-facing materials, insurance-facing materials, lending-facing materials, procurement-facing materials, media materials, and Nexus interface materials shall be reviewed and corrected as necessary to prevent misrepresentation of the Corporation’s status.

4.13 Status Records, Tax Records, and Public-Representation Controls. The Corporation shall maintain accurate, current, and correctionable records of its nonprofit status, non-share status, non-distributing character, non-charitable status unless lawfully changed, tax posture, public-benefit purpose, corporate filings, annual returns, registered office, directors and officers, member records where applicable, donation and sponsorship treatment, grant treatment, restricted funds, cost-recovery revenue, invoices, receipts, public representations, public claims, and status-related communications.

The Corporation’s status records shall identify, at minimum:

a) the governing statute and corporate number or equivalent identifier;

b) the Articles and any amendments;

c) the current Bylaw and status of adoption;

d) the registered office and governance seat;

e) the current directors and officers;

f) member structure where applicable;

g) tax registration, tax filing, nonprofit tax treatment, and charitable-status status, if any;

h) any restrictions applicable to donations, sponsorships, grants, subscriptions, dues, cost-recovery fees, and in-kind support;

i) public-facing descriptions approved for use;

j) prohibited descriptions and required disclaimers;

k) public authority reference restrictions;

l) finance, insurance, investment, procurement, certification, recognition, and public-warning boundary language;

m) correction, supersession, withdrawal, or clarification records relating to status representations; and

n) the custodian responsible for maintaining the record.

The Corporation shall maintain public-representation controls sufficient to ensure that its legal status, tax status, nonprofit character, non-charitable posture where applicable, public-benefit purpose, non-distribution rule, non-execution boundary, public-good technical role, and Nexus role separation are accurately described. Where any representation is inaccurate, stale, incomplete, misleading, authority-inflating, finance-signaling, certification-implying, public authority-confusing, provider-preferencing, sponsor-influenced, or otherwise inconsistent with this Bylaw, the Corporation shall correct, withdraw, reissue, restrict, or publicly clarify the representation as appropriate.

No status record, tax record, receipt, invoice, public representation, public authority reference, sponsor acknowledgment, provider acknowledgment, Nexus-compatible statement, Academy certificate, publication, report, dashboard, software release, technical baseline, evidence artifact, Docket input, Grid input, or finance-readiness evidence input shall be used to imply a legal, tax, public authority, market, charitable, certification, recognition, finance-readiness, procurement, or execution status that the Corporation does not possess.

Section 5. Adopting Authority, Adoption Resolution, Certificate of Adoption, and Authority Record

5.1 Competent Adopting Authority. This Bylaw, and any amendment, restatement, consolidation, replacement, correction of material effect, supersession, withdrawal, or re-adoption of this Bylaw, shall be adopted only by the competent corporate authority authorized under applicable law, the Articles, and this Bylaw.

Unless applicable law, the Articles, or a higher approval requirement provides otherwise, the Board shall be the primary adopting authority for this Bylaw and for amendments to this Bylaw. Where member approval, special resolution, filing, statutory confirmation, class approval, regulator notice, court approval, governmental confirmation, or other legal condition is required, Board approval shall be necessary but not sufficient until the required additional approval or condition has been satisfied.

No founder, incorporator, director acting alone, officer, executive, committee, council, working group, advisor, fellow, employee, contractor, donor, sponsor, funder, provider, host, public authority participant, university, laboratory, partner, GCRI US representative, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards body, Nexus Network body, Nexus Universe body, regional consortium, national consortium, national consortium company, Project SPV, qualified enterprise provider, or other person may adopt, amend, waive, override, or operationally replace this Bylaw except through the competent corporate process required by this Section.

5.2 Adoption as a Corporate Act. Adoption of this Bylaw shall be a formal corporate act. It shall not arise by circulation, drafting maturity, counsel review, board discussion, operational reliance, repository placement, institutional practice, public-facing use, funder expectation, sponsor reliance, public authority familiarity, Nexus ecosystem use, technical implementation, signature on a draft, email approval, informal consensus, silence, or absence of objection.

The adopting act shall be recorded in a resolution, written consent, meeting minutes, certificate of adoption, or other legally sufficient record approved under applicable law. The adoption record shall identify with precision the text adopted, the adopting authority, the date of adoption, the effective date, any required further approval, any transition rule, and the status of any prior bylaw or governance instrument affected by the adoption.

Adoption shall be read as approval of the legal-governance text only. It shall not be read as approval of any separate strategy, budget, transaction, regulated activity, public authority action, finance-readiness determination, certification, recognition, procurement action, project approval, public-warning function, emergency-command function, or Nexus ecosystem consequence unless such matter is expressly approved by separate competent act.

5.3 Board Authority to Adopt Initial Bylaw. The Board may adopt the initial form of this Bylaw where permitted by applicable law and the Articles. In adopting the initial Bylaw, the Board shall confirm that the Bylaw is intended to serve as the Corporation’s principal internal governance instrument and to govern the Corporation as a Canadian nonprofit, non-share, non-distributing, public-benefit, non-executing, public-good technical-stewardship corporation.

The initial adoption record shall confirm, at minimum, that the Board has considered the Corporation’s legal form, nonprofit character, Canadian seat, public-benefit purpose, non-share structure, non-distribution rule, non-charitable status unless lawfully changed, public-good stewardship burden, non-execution perimeter, Nexus role separation, Canada–US separateness, public authority boundary, finance-readiness boundary, provider neutrality, sponsor support-without-control rule, records discipline, correctionability, and the need for a governance instrument suitable for legal review, board adoption, public-good institutional operation, audit, assurance, and long-horizon continuity.

5.4 Member Approval Where Required. Where the Corporation has members and applicable law, the Articles, or this Bylaw requires member approval for the adoption, amendment, repeal, confirmation, or continuation of this Bylaw or any provision of it, such approval shall be obtained in the form, threshold, notice period, meeting procedure, written-resolution procedure, voting class, and filing sequence required by applicable law.

Where member approval is required, the materials provided to members shall identify:

a) the text proposed for adoption, amendment, repeal, confirmation, or continuation;

b) the status of the existing bylaw or affected provision;

c) the reason for the proposed action;

d) the legal effect of the proposed action;

e) any provisions affecting member rights, director powers, officer authority, corporate purpose, public-benefit character, non-distribution, dissolution, amendment procedure, or reserved matters;

f) any provisions affecting the Corporation’s non-execution perimeter, role separation, public authority boundary, finance-readiness boundary, public-good asset protection, data and safeguards obligations, or correctionability;

g) any effective date, transition rule, savings rule, or deferred implementation condition; and

h) any required filing, confirmation, or statutory follow-up.

Member approval shall not authorize any action outside applicable law, the Articles, or the Corporation’s lawful purposes. No member vote shall convert the Corporation into a public authority, regulator, charity, financial intermediary, market operator, certification body, procurement authority, emergency authority, national consortium company, Project SPV, provider, or commercial execution vehicle unless a lawful reorganization expressly and validly establishes such status and all required legal steps are completed.

5.5 Form of Adoption Resolution. Any resolution adopting, amending, restating, consolidating, replacing, correcting, superseding, withdrawing, or re-adopting this Bylaw shall be sufficiently precise to identify the corporate act taken. The resolution should include, as applicable:

a) the full legal name of the Corporation;

b) the title of the instrument;

c) the version identifier;

d) the issue date;

e) the adoption date;

f) the effective date;

g) the adopting authority;

h) the approval threshold satisfied;

i) confirmation of quorum or written-consent sufficiency;

j) the text or location of the text adopted;

k) any prior version superseded, repealed, amended, continued, or preserved;

l) any provisions requiring member approval, filing, statutory confirmation, or other condition;

m) any transition, savings, continuation, or implementation rule;

n) the officer or custodian authorized to authenticate, maintain, file, circulate, publish, or restrict the Bylaw;

o) any authorized public-facing description or publication status;

p) any limits on reliance, public claims, translation, circulation, or external use;

q) any direction to update registers, repositories, policies, manuals, templates, websites, public-facing materials, Nexus interface records, contracts, or controlled vocabularies; and

r) any legal counsel, governance committee, audit, compliance, or assurance follow-up required.

A resolution shall not be treated as defective merely because it does not use the exact language of this Section, provided that it satisfies applicable law and clearly identifies the corporate act taken. Where ambiguity exists, the resolution shall be interpreted in the narrowest lawful manner that preserves the Corporation’s public-benefit purpose, non-execution perimeter, role separation, legal certainty, and correctionability.

5.6 Minimum Adoption Determination. The adoption record for this Bylaw shall include, either expressly or by necessary implication, the following minimum determinations:

a) that the Corporation requires a principal bylaw suitable for Canadian nonprofit governance and public-good technical stewardship;

b) that the Bylaw is intended to govern the Corporation’s internal authority, legal identity, board and officer structure, records, finances, public-benefit stewardship, member or participant arrangements where applicable, committees, councils, delegations, conflict controls, safeguards, and Nexus interfaces;

c) that the Corporation is to be maintained as a nonprofit corporation without share capital and not operated for private profit or private inurement;

d) that the Corporation’s public-benefit role is upstream research, evidence, methods, observability, ontology, technical truth, public-good software, open technical baselines, scientific-operational discipline, safeguards, and correctionable institutional memory;

e) that the Corporation is non-executing, non-market, non-dealing, non-custodial, non-brokerage, non-underwriting, non-insurance, non-bank, non-fund, non-payment-intermediation, non-procurement, non-regulatory, non-sovereign, and non-emergency-command in institutional character;

f) that GCRI Canada is legally separate from GCRI US and from every other Nexus-related institution or implementation vehicle;

g) that GCRI Canada’s evidence and methods role does not become GRF recognition, GRA finance-readiness, Nexus Standards protocol authority, Nexus Grid maturity, Nexus Docket approval, public authority decision, procurement approval, certification, insurance approval, investment recommendation, or commercial execution by implication;

h) that public-good technical assets shall be stewarded under anti-capture, anti-enclosure, rights, licensing, security, access, correction, and continuity controls;

i) that sponsors, donors, funders, hosts, providers, public authorities, universities, laboratories, partners, contributors, and members shall support without control; and

j) that validity shall arise by record, not by status narrative, appearance, sponsorship, public authority presence, technical importance, operational proximity, or repeated use.

5.7 Certificate of Adoption. The Board may require, and the Secretary or other authorized officer may issue, a certificate of adoption confirming that this Bylaw or any amendment, restatement, consolidation, replacement, correction, supersession, withdrawal, or re-adoption has been duly approved.

A certificate of adoption may identify:

a) the name of the Corporation;

b) the title and version of the Bylaw;

c) the adopting authority;

d) the date and manner of adoption;

e) the effective date;

f) any member approval or statutory filing requirement;

g) any prior version superseded or repealed;

h) the repository location of the authenticated text;

i) the officer or custodian responsible for the authoritative record; and

j) any limits on certification, including that the certificate confirms corporate adoption only and does not certify compliance with every external legal, tax, regulatory, public authority, financing, insurance, procurement, or Nexus-interface requirement.

The certificate of adoption shall be evidence of the corporate record. It shall not expand the substantive powers of the Corporation, create public authority status, create charitable status, create finance-readiness, create certification authority, create GRF recognition, create GRA determination, create Nexus Standards conformance, create Docket approval, create Grid maturity, create public procurement status, or create execution authority.

5.8 Authentication of Adopted Text. Upon adoption, the Secretary or authorized governance-record custodian shall authenticate the adopted text. Authentication shall establish the identity of the text adopted and shall connect that text to the adoption record.

Authentication may be evidenced by:

a) signature of the Chair, Secretary, or other authorized officer;

b) certificate of adoption;

c) inclusion in the minute book;

d) entry in the bylaw register;

e) repository certification;

f) version-control record;

g) digital signature;

h) hash, checksum, or tamper-evident marker;

i) legal counsel certification where obtained;

j) filing record where applicable; or

k) any other method approved by the Board and consistent with applicable law.

Authentication shall not create authority beyond the adopted text. If the authenticated text and an unofficial circulating copy differ, the authenticated text shall govern.

5.9 Deposit in Authoritative Repository and Minute Book. The authenticated adopted text of this Bylaw shall be deposited in the Corporation’s authoritative governance repository and minute book. The deposit record shall identify the custodian, access classification, version identifier, adoption record, effective date, and any superseded prior version.

Where the Corporation maintains both physical and digital records, the Board may designate which record is authoritative or how authority is determined between them. Where mirrored records, backup records, cloud records, distributed records, ledger references, or external counsel records are maintained, such records shall support, not displace, the Corporation’s authoritative governance record unless expressly designated by competent corporate act.

No repository upload shall be treated as adoption. No absence from a repository shall invalidate an otherwise lawful adoption if the adoption is supported by legally sufficient records. However, repository failure, duplicate versions, missing metadata, access errors, or inconsistent copies shall be corrected promptly because record discipline is part of the Corporation’s institutional integrity.

5.10 Adoption Record Register. The Corporation shall maintain an adoption record register for this Bylaw. The register shall preserve the lifecycle of the Bylaw from initial adoption through all amendments, restatements, consolidations, corrections, supersessions, withdrawals, archival actions, and re-adoptions.

The register shall include, where applicable:

a) adoption resolution records;

b) meeting minutes or written consents;

c) quorum and voting records;

d) member approval records where required;

e) legal filing records where required;

f) certificates of adoption;

g) version identifiers;

h) effective dates;

i) supersession notes;

j) amendment summaries;

k) transition provisions;

l) correction records;

m) withdrawal records;

n) archival references;

o) legal-review references;

p) public-facing release approvals;

q) notice records; and

r) custodian records.

The adoption record register shall be maintained as a corporate governance record. It shall be accessible to directors and such officers, auditors, counsel, members, regulators, or other persons as applicable law, the Articles, this Bylaw, or Board-approved access controls require or permit.

5.11 Legal Review and Governance Review Before Adoption. Before adopting or materially amending this Bylaw, the Board should obtain or consider legal, governance, tax, fiscal, records, data, cybersecurity, public authority, nonprofit, and Nexus-interface review appropriate to the nature and significance of the proposed action.

Legal or governance review shall be required where the proposed adoption or amendment materially affects:

a) the Corporation’s nonprofit, non-share, non-distributing, or public-benefit character;

b) member rights or member approval thresholds;

c) director powers, duties, appointment, removal, term, quorum, voting, conflicts, indemnification, or reserved matters;

d) officer authority, signature authority, delegation, employment, or management controls;

e) public-good asset ownership, licensing, open-source posture, software, datasets, methods, ontologies, technical baselines, evidence systems, or observability systems;

f) fiscal controls, restricted funds, donations, sponsorships, grants, cost-recovery fees, treasury, audit, or tax status;

g) private benefit, private inurement, related-party transactions, sponsor influence, provider influence, or founder influence;

h) data, privacy, cybersecurity, AI governance, protected knowledge, community safeguards, or controlled-room arrangements;

i) GCRI Canada / GCRI US separateness;

j) GCRI / GRF / GRA role separation;

k) Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Grid, Nexus Rails, Nexus Academy, consortium, national company, Project SPV, or provider interfaces;

l) public authority participation, public authority capacity classification, public claims, or public-safe publication;

m) regulated-perimeter risk, including finance, insurance, securities, lending, public finance, procurement, certification, emergency management, public warning, or regulated professional status; or

n) dissolution, reorganization, continuance, amalgamation, asset lock, or public-good continuity.

Failure to obtain a particular review shall not automatically invalidate an otherwise lawful adoption unless required by applicable law, the Articles, this Bylaw, or the adoption record. However, where review was required and omitted, the matter shall be escalated for cure, ratification where lawful, correction, amendment, restricted implementation, or other remedial action.

5.12 No Adoption by Operational Necessity. No provision of this Bylaw, amendment to this Bylaw, or replacement governance rule shall become operative because an activity needs it, a deadline requires it, a sponsor expects it, a public authority requests it, a grant condition assumes it, a provider depends on it, a Nexus Universe cycle requires it, a Docket or Grid process would benefit from it, a technical system has already implemented it, a public-facing statement has already used it, or a manager has acted as if it exists.

Operational necessity may justify urgent Board action, interim controls, temporary delegations, risk holds, restricted implementation, or emergency governance measures where permitted by law and this Bylaw. It shall not substitute for adoption authority.

Where urgency requires temporary action before formal bylaw amendment, the Corporation shall act through the narrowest lawful temporary mechanism available, record the basis for action, preserve the non-execution boundary, avoid public overclaim, and bring the matter to the competent authority for confirmation, amendment, correction, or termination as soon as practicable.

5.13 No Adoption by External Reliance. No external reliance shall adopt, amend, confirm, or expand this Bylaw. Reliance by donors, sponsors, funders, providers, hosts, public authorities, universities, laboratories, banks, insurers, investors, development finance institutions, multilateral bodies, media, communities, partners, GCRI US, GRF, GRA, Nexus bodies, consortiums, national companies, Project SPVs, or qualified enterprise providers shall not create bylaw authority.

External actors may receive, review, cite, or rely upon the Bylaw only to the extent that the authenticated, in-force text permits and only within its actual legal effect. No external actor shall use this Bylaw as evidence of:

a) government approval;

b) public authority delegation;

c) procurement approval;

d) regulatory approval;

e) emergency authority;

f) public-warning authority;

g) investment suitability;

h) financeability;

i) bankability;

j) insurability;

k) underwriting support;

l) public finance approval;

m) certification;

n) accreditation;

o) GRF recognition;

p) GRA finance-readiness;

q) Nexus Standards conformance;

r) Docket approval;

s) Grid maturity;

t) preferred-provider status; or

u) commercial exclusivity.

5.14 Notice of Adoption. The Corporation may provide notice of adoption of this Bylaw to directors, officers, members where applicable, employees, contractors, committees, councils, working groups, fellows, advisors, contributors, donors, sponsors, providers, hosts, public authorities, universities, laboratories, partners, GCRI US, GRF, GRA, Nexus bodies, consortiums, or other affected persons where the Board or authorized officer determines that notice is necessary or useful.

Any notice of adoption shall be accurate, bounded, and non-misleading. It shall identify whether the full Bylaw, an excerpt, a public-safe summary, or a controlled version is being provided. A notice shall not imply that recipients obtain governance rights, approval rights, enforcement rights, reliance rights, public status, commercial rights, public authority meaning, finance-readiness status, certification, Docket status, Grid status, or provider preference merely by receiving the notice.

Where the Bylaw contains obligations affecting a person’s role, access, participation, authority, confidentiality, data handling, public claims, sponsor conduct, provider conduct, public authority participation, publication rights, or correction duties, the notice may require acknowledgement, onboarding, training, certification of understanding, or controlled access procedures.

5.15 Public-Safe Publication of Adoption. The Corporation may publish a public-safe notice that this Bylaw has been adopted, provided that the publication is approved under the Corporation’s public-communications and claims-discipline controls.

Any public-safe publication shall distinguish between:

a) adoption of a governance bylaw;

b) legal status of the Corporation;

c) public-benefit purpose;

d) internal governance authority;

e) public-good stewardship role;

f) Nexus ecosystem relationship;

g) non-execution boundary; and

h) matters not approved by the adoption.

Public-safe publication shall not include restricted governance information, confidential deliberations, personal information, protected knowledge, cybersecurity-sensitive information, non-public fiscal details, privileged legal analysis, donor or sponsor confidential terms, public authority confidential terms, internal risk registers, controlled-room procedures, or sensitive Nexus interface details unless disclosure is lawful, approved, and safe.

5.16 Adoption Does Not Ratify Unauthorized Prior Acts Unless Expressly Stated. Adoption of this Bylaw shall not by itself ratify, approve, cure, validate, release, or excuse any prior unauthorized act, overclaim, contract, publication, public authority statement, sponsor commitment, provider commitment, finance-facing statement, certification-implying statement, name misuse, data misuse, public-safe publication failure, conflict failure, or role-separation breach.

Any ratification of prior acts shall require a separate recorded determination identifying:

a) the act to be ratified;

b) the authority for ratification;

c) the facts known to the adopting authority;

d) any legal, fiscal, data, safeguards, public authority, finance-readiness, certification, procurement, sponsor, provider, or Nexus-interface risk;

e) any corrective action required;

f) any limits on the ratification; and

g) any notice, amendment, withdrawal, correction, or public clarification required.

Unauthorized acts that cannot lawfully be ratified shall be corrected, terminated, withdrawn, limited, or otherwise remediated.

5.17 Adoption Does Not Create External Legal Capacity Beyond Lawful Corporate Powers. Adoption of this Bylaw shall not create powers, rights, privileges, exemptions, statuses, approvals, licenses, registrations, permissions, tax consequences, public authority delegations, regulated permissions, market permissions, or execution rights beyond those available under applicable law, the Articles, and lawful corporate acts.

The Corporation shall not rely on this Bylaw as a substitute for:

a) corporate registration or filing;

b) tax registration or confirmation;

c) charitable registration;

d) fundraising registration;

e) employment registration;

f) privacy, data, or cybersecurity compliance;

g) export-control or sanctions compliance;

h) securities, insurance, banking, lending, payment, or financial-services licensing;

i) procurement authority;

j) public authority delegation;

k) standards accreditation;

l) certification body accreditation;

m) professional credential authority;

n) emergency authority;

o) public-warning authority;

p) research ethics approval;

q) human-subjects approval;

r) data-sharing authorization;

s) intellectual property license;

t) open-source compliance;

u) local operating registration; or

v) any other legal condition required for a specific activity.

5.18 Adoption of Schedules, Policies, Mandates, and Incorporated Instruments. The Board may adopt schedules, policies, mandates, codes, registers, protocols, matrices, authority maps, committee charters, council terms of reference, public-safe publication rules, evidence policies, research governance policies, data policies, cybersecurity policies, AI governance policies, privacy policies, conflict policies, sponsorship policies, finance policies, procurement-neutrality policies, name-use policies, public authority protocols, Nexus interface policies, Canada–US interface policies, and other instruments to implement this Bylaw.

Such instruments shall not amend the Bylaw unless adopted with the authority and procedure required for amendment. Where a schedule or policy is expressly incorporated into the Bylaw, the adoption record shall state whether it has bylaw-level effect, policy-level effect, interpretive effect, implementation effect, or evidentiary effect.

No incorporated instrument shall be used to weaken the Bylaw’s public-benefit purpose, non-distribution rule, non-execution perimeter, legal separateness, role separation, provider neutrality, support-without-control rule, public authority boundary, finance-readiness boundary, data and safeguards obligations, public-good asset protection, validity-by-record, or correctionability.

5.19 Conflict Between Adoption Record and Text. Where the adoption record and the adopted text appear to conflict, the Corporation shall interpret them together in the manner most consistent with applicable law, the Articles, the actual corporate act taken, the authenticated text, and the Corporation’s public-benefit purpose.

If the conflict is material, the Secretary or other authorized custodian shall escalate the matter to the Chair, the Board, legal counsel, or the appropriate governance committee for correction, clarification, ratification where lawful, amendment, restatement, or controlled notice.

Pending correction, no person shall rely on the conflict to expand authority, weaken controls, create execution capacity, imply public authority, imply finance-readiness, imply certification, imply procurement approval, imply recognition, imply provider preference, or override a limitation expressed elsewhere in this Bylaw.

5.20 Defective Adoption Record. A defective, incomplete, ambiguous, misplaced, inconsistent, corrupted, unsigned, misfiled, or inaccessible adoption record shall be corrected as soon as discovered. The Corporation shall preserve evidence of the defect, the investigation, the corrective action, and any reliance risk.

Where the defect affects the validity, effective date, operative scope, authority, or legal status of the Bylaw, the matter shall be escalated to the Board and legal counsel where appropriate. Corrective action may include:

a) reconstruction of the record;

b) officer certificate;

c) board confirmation;

d) member confirmation where required;

e) ratification where lawful;

f) amendment;

g) restatement;

h) republication;

i) withdrawal of defective copies;

j) correction of public-facing materials;

k) statutory filing correction;

l) repository reconciliation; and

m) notice to affected persons.

No person shall exploit a defective adoption record to advance a broader authority claim than the authenticated and lawfully supported record permits.

5.21 Adoption and Fiduciary Responsibility. Directors participating in the adoption, amendment, restatement, replacement, or material correction of this Bylaw shall act in accordance with their fiduciary duties, applicable law, the Articles, and the Corporation’s public-benefit purpose.

In considering adoption or amendment, directors shall give due attention to:

a) legal compliance;

b) corporate capacity;

c) public-benefit purpose;

d) mission integrity;

e) nonprofit and non-distribution requirements;

f) director and officer accountability;

g) member rights where applicable;

h) records integrity;

i) fiscal controls;

j) conflicts and related-party risks;