ARTICLE I. FOUNDATIONS

GCRI US bylaw foundations for nonprofit corporate governance, public-benefit governance, nonstock corporation structure, legal authority, records governance, and North America public-good stewardship.

This article establishes the legal foundations of the GCRI US Bylaw.

It defines the nonprofit corporate governance framework of The Global Centre for Risk and Innovation - United States. It covers public-benefit governance, nonstock corporation structure, legal identity, United States legal seat, records governance, non-executing institutional authority, and the Corporation’s bounded North America role.

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

1.1 Instrument Title. This instrument shall be titled the “GCRI US Bylaw”. It is the principal internal governance bylaw of The Global Centre for Risk and Innovation - United States 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, fundraising document, promotional document, program description, public authority statement, finance-readiness instrument, certification manual, procurement instrument, or general Nexus ecosystem statement.

The Bylaw governs the Corporation’s internal legal authority, corporate identity, United States legal seat, 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 or Certificate, and any superior legal requirement binding upon the Corporation.

This Bylaw shall be read as a United States nonprofit corporate governance instrument for a nonstock or non-share, non-distributing, public-benefit, non-executing institution. It shall not be read as an instrument that grants market authority, public authority status, finance authority, emergency authority, regulatory authority, procurement authority, certification authority, recognition authority, protocol authority, or execution authority to the Corporation.

1.2 Short Citation. This instrument may be cited as the “GCRI US 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 United States seat and governing corporate-law posture;

c) the Corporation’s nonprofit, nonstock or non-share, non-distributing, public-benefit, tax-exempt or tax-exempt-compatible, 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, verifiable compute, verifiable intelligence, and research-integrity steward;

e) the Corporation’s all-states-and-territories operating posture, subject to applicable qualification, registration, charitable solicitation, tax, employment, privacy, public authority, contracting, grant, lobbying, political activity, sanctions, export-control, and local-law requirements;

f) the Corporation’s bounded United States and North America anchor role within the GCRI family and the Nexus public-good architecture;

g) the legal separateness of the Corporation from GCRI Canada, 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

h) the rule that GCRI US 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, regulated-market effect, or execution authority unless a future lawful instrument expressly and narrowly authorizes a function consistent with applicable law, the Articles or Certificate, and 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, grant, tax, institutional, or Nexus interface 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, certificate 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 or Certificate, applicable United States state nonprofit corporate law, and any other applicable legal requirement.

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, tax review, state-law review, technical reconciliation, Nexus role review, 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, deferred commencement date, tax condition, registration condition, or implementation condition 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, tax, grant, insurance, litigation, governance, 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, legal-hold, 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, public-facing reference, grant narrative, website reference, or repeated institutional use. 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, public reliance, public authority meaning, finance-readiness implication, certification implication, recognition implication, procurement implication, or Nexus-compatible status. 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, governance, audit, tax, or compliance 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 or Certificate;

c) any required member approval;

d) any required filing, confirmation, statutory condition, tax condition, state-law condition, foreign-qualification condition, charitable-solicitation condition, or registration condition;

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

f) any express limitation, suspension, hold, implementation condition, or compliance 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 Certificate, 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, repository update, website update, grant milestone, program launch, public authority meeting, Nexus reference, 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, university briefing, laboratory briefing, investor-facing material, grant narrative, 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, create public authority meaning, create finance-readiness meaning, create certification meaning, create procurement meaning, or convert GCRI US’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 or Certificate, 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, legal continuity, tax, grant, insurance, or records-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, sponsor-facing version, public authority version, grant 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, protocol authority, Grid status, Docket status, provider preference, 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 tax-exempt, charitable, public-benefit, state-registration, charitable-solicitation, or foreign-qualification condition where applicable;

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

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

n) any incorporated schedules, annexes, policies, registers, matrices, controlled vocabularies, or instruments having bylaw-authorized effect;

o) the authoritative repository location;

p) the repository custodian;

q) the access classification;

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

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

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

u) any legally required filing, notice, register entry, corporate record, tax record, grant record, charitable-solicitation 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, cross-reference correction, numbering 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, tax posture, public authority boundary, finance boundary, certification boundary, provider neutrality, sponsor non-control, 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, more recognition-implying, more procurement-implying, more public-authority-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, university expectation, laboratory expectation, funder request, Nexus partner expectation, AI-assisted revision, public-facing update, grant narrative, 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 or Certificate, 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, remediation, ratification, re-performance, or nullification where required by applicable law, public-benefit purpose, fiduciary duty, nonprofit duty, tax-exempt or tax-exempt-compatible posture, 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, university, laboratory, 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) tax, grant, charitable-solicitation, lobbying, political activity, procurement-integrity, and state-registration alignment;

l) data, AI, cybersecurity, privacy, export-control, sanctions, civil rights, accessibility, research-integrity, and safeguards alignment;

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

n) Nexus interface alignment;

o) correction of inconsistent prior materials; and

p) closeout of obsolete structures.

No transitional provision shall weaken the Corporation’s nonprofit character, nonstock or non-share character, non-distribution rule, public-benefit purpose, legal separateness, public-good stewardship burden, non-execution perimeter, GCRI / GRF / GRA role separation, public authority boundary, finance boundary, certification 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, protocol authority, 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, universities, laboratories, funders, hosts, 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, sovereign mandate, federal endorsement, state endorsement, territorial endorsement, Tribal endorsement, local endorsement, university endorsement, laboratory endorsement, funder endorsement, sponsor control, or enterprise execution authority.

1.20 Governing Reading of Section 1. This Section shall be interpreted to preserve documentary integrity, United States 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, funder use, provider 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.

The controlling rule is that this Bylaw has operative force only through lawful adoption, authenticated text, recorded status, and effective date. GCRI US shall remain a United States public-benefit, nonprofit, nonstock or non-share, non-distributing, non-executing, evidence, methods, observability, ontology, public-good R&D, public-good software, open technical baseline, and research-integrity institution, and no document-control ambiguity shall be used to expand the Corporation into recognition, finance-readiness, certification, procurement, public authority action, protocol effect, regulated execution, or enterprise delivery.

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 shall be “The Global Centre for Risk and Innovation - United States”, or such exact legal name as is set forth in the Corporation’s Certificate of Incorporation, Articles of Incorporation, charter, or other governing constituting instrument filed or maintained under applicable United States state nonprofit corporation law.

The official legal name shall control in all matters requiring legal identity, including corporate filings, tax records, charitable solicitation registrations, state qualifications, bank accounts, insurance records, grant agreements, donation agreements, sponsorship agreements, contracts, employment records, contractor agreements, intellectual property records, data-processing agreements, public authority correspondence, litigation, regulatory correspondence, repository authentication, official minutes, board resolutions, officer certificates, public-safe notices, and any other instrument in which legal identity, authority, liability, tax status, fiduciary responsibility, or institutional separateness may reasonably matter.

No public-facing style, abbreviated reference, program name, campaign label, technical asset name, repository name, domain name, email address, logo, seal, badge, dataset label, software package, technical baseline, whitepaper, report, slide, controlled-room label, public authority briefing, or Nexus interface reference shall replace, modify, obscure, or expand the official legal name of the Corporation.

2.2 Approved Short Name. The approved short name of the Corporation shall be “GCRI US.” The short name may be used for convenience in internal governance, public communications, repository materials, program documents, technical materials, research outputs, public-safe publications, board papers, notices, controlled-room materials, Academy materials, Nexus interface materials, and other contexts where the official legal identity of the Corporation is clear or has already been stated.

The approved short name shall be used only as a reference to the Corporation itself. It shall not be used as a reference to GCRI Canada, The Global Centre for Risk and Innovation as a broader institutional family or public-good function, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Standards, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, Global Nexus Consortium, Regional Nexus Consortiums, National Nexus Consortiums, National Consortium Companies, Project SPVs, Qualified Enterprise Providers, sponsors, hosts, public authorities, universities, laboratories, donors, funders, enterprise actors, or any other person or entity.

The approved short name shall not be used to imply that the Corporation has authority beyond its actual lawful authority, including authority to recognize, certify, approve, finance, insure, underwrite, rate, procure, regulate, command emergencies, issue public warnings, act as public authority, act as protocol authority, operate enterprise infrastructure, select providers, bind public authorities, bind investors, or bind any Nexus entity.

2.3 Use of “GCRI US.” The term “GCRI US” may be used as a controlled institutional reference only where the reference is accurate, current, scope-limited, and consistent with the Corporation’s official legal identity, United States seat, nonprofit character, public-benefit purpose, non-distribution rule, non-execution perimeter, public authority boundary, finance boundary, certification boundary, procurement boundary, role-separation obligations, and Nexus interface discipline.

Any use of “GCRI US” shall preserve the following meanings:

a) GCRI US is a United States nonprofit, nonstock or non-share, non-distributing, public-benefit corporation;

b) GCRI US is the United States anchor of the GCRI public-good function;

c) GCRI US may act as a bounded North America anchor for evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, verifiable compute, verifiable intelligence, safeguards, and public authority learning only where lawful and record-supported;

d) GCRI US is an upstream public-good research and technical-stewardship institution;

e) GCRI US is not a regulator, public authority, emergency command body, public warning authority, procurement authority, investment adviser, broker, dealer, finder, lender, insurer, underwriter, rating agency, bank, fund, marketplace, certification body by default, National Consortium Company, Project SPV, Qualified Enterprise Provider, operator, or enterprise execution vehicle; and

f) GCRI US does not become GRF, GRA, Nexus Standards, a protocol authority, a public authority, a capital intermediary, a certification authority, or an enterprise delivery actor by reason of authorship, contribution, participation, proximity, technical centrality, public visibility, sponsorship, funding, or Nexus alignment.

Where “GCRI US” is used in materials likely to be read by external persons, public authorities, sponsors, funders, universities, laboratories, providers, investors, insurers, capital readers, media, communities, or Nexus participants, the Corporation may require a full-name reference, status statement, non-execution statement, non-reliance statement, or controlled vocabulary note.

2.4 Use of “The Global Centre for Risk and Innovation - United States.” The full institutional name “The Global Centre for Risk and Innovation - United States” shall be used where precision, formality, legal identity, public authority clarity, funding clarity, tax clarity, contracting clarity, repository authenticity, or institutional separateness is required.

The full institutional name shall be used, unless the Secretary or another authorized officer approves a shorter reference, in:

a) the Certificate or Articles and any amendment thereto;

b) this Bylaw and any amendment, restatement, schedule, annex, or official certification;

c) board resolutions of constitutional, financial, tax, legal, public authority, or Nexus interface significance;

d) contracts, memoranda of understanding, grant agreements, donation agreements, sponsorship agreements, restricted-fund instruments, procurement documents, employment agreements, contractor agreements, data-processing agreements, intellectual property instruments, licensing instruments, and insurance documents;

e) IRS, state tax, charitable solicitation, corporate annual report, foreign qualification, registered agent, lobbying, political activity, grant compliance, and other legally sensitive filings or records;

f) bank, treasury, audit, financial statement, payment, receivables, payable, reimbursement, and reserve records;

g) public authority correspondence where institutional capacity, legal status, authority, or public meaning could be misunderstood;

h) public-safe notices concerning authority, corrections, status, claims, public authority participation, finance boundaries, provider neutrality, or legal separateness;

i) official repository authentication, software-release authority, controlled vocabulary, public-good asset registers, and technical baseline governance records; and

j) any context where use of “GCRI US” alone could create legal, public authority, finance, certification, procurement, recognition, tax, sponsor, provider, or Nexus role confusion.

2.5 No Alternate Legal Name Without Record. The Corporation shall not adopt, use, file, represent, publish, contract under, receive funds under, issue tax receipts under, open accounts under, register under, or conduct legal acts under any alternate legal name, assumed name, fictitious name, trade name, “doing business as” name, local name, state-specific name, territorial name, public-facing name, campaign name, program name, or North America name unless such use is lawful, authorized by competent corporate action where required, and recorded in the Corporation’s authoritative governance records.

No alternate name shall be used if it would:

a) obscure the Corporation’s official legal identity;

b) imply merger with GCRI Canada or any other GCRI entity;

c) imply that GCRI US is the whole of GCRI, GRF, GRA, Nexus Network, Nexus Standards, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, any consortium, any National Consortium Company, any Project SPV, or any enterprise stack actor;

d) imply public authority, regulator, public warning, emergency command, procurement, finance, insurance, investment, lending, rating, certification, accreditation, recognition, standards, protocol, or execution authority not lawfully conferred;

e) create state, territorial, Tribal, local, federal, North America, or cross-border legal confusion;

f) create donor, funder, sponsor, provider, host, investor, university, laboratory, public authority, or community misunderstanding; or

g) weaken validity-by-record, correctionability, public-safe claims discipline, anti-capture controls, or legal separateness.

Any unauthorized alternate-name use shall be subject to correction, withdrawal, takedown, public or controlled clarification, contract correction, filing correction, repository correction, or other remedial action approved under this Bylaw.

2.6 Use of “GCRI North America” Only Where Specifically Authorized and Not Legally Confusing. The term “GCRI North America” shall not be treated as the legal name of the Corporation unless separately and lawfully adopted as such. The term may be used only as a controlled descriptive reference to a lawful, bounded, and record-supported North America evidence, methods, observability, ontology, technical-baseline, public-good software, research, public authority learning, or coordination function involving GCRI US, and only where the use does not create legal-identity ambiguity.

Use of “GCRI North America” shall require prior authorization under the Corporation’s name-use, public-safe claims, and controlled vocabulary procedures where the term appears in:

a) public-facing materials;

b) public authority materials;

c) sponsor, donor, funder, investor, insurer, lender, or capital-reader materials;

d) contracts, memoranda of understanding, partnership materials, or grant materials;

e) repository, software, dataset, or technical baseline materials;

f) Nexus Universe, Nexus Observatory, Nexus Standards, Nexus Rails, Nexus Grid, or Nexus Academy materials; or

g) cross-border materials involving Canada, Mexico, the Caribbean, Arctic, Great Lakes, Pacific, Atlantic, Gulf, border regions, Tribal or Indigenous interfaces, or other North America contexts.

“GCRI North America” shall not imply that GCRI US owns, governs, controls, represents, supervises, or binds GCRI Canada, Mexico-facing interfaces, Caribbean interfaces, Arctic interfaces, Indigenous governments or knowledge holders, regional Nexus bodies, national Nexus bodies, public authorities, universities, laboratories, enterprise actors, funders, sponsors, hosts, Project SPVs, National Consortium Companies, or Qualified Enterprise Providers.

Where the term is used, the Corporation may require a clarifying statement that GCRI US is a United States legal entity with a bounded North America anchor role and not a North America sovereign authority, treaty body, public authority, regulator, public finance authority, procurement authority, certification authority, recognition authority, finance-readiness authority, protocol authority, or enterprise execution vehicle.

2.7 Name Use in Contracts, Filings, IRS Records, State Registrations, Charitable Solicitation Registrations, Public Materials, Repositories, Board Papers, Program Materials, and Notices. The Corporation’s official legal name shall be used in all contracts, legal filings, IRS records, state registrations, charitable solicitation registrations, foreign qualification records, tax records, bank records, insurance records, grant agreements, donation agreements, sponsorship agreements, restricted-fund instruments, public authority correspondence, employment records, contractor records, repository governance records, formal board papers, official notices, and any instrument where legal identity, authority, liability, fiduciary duty, tax status, public-benefit purpose, or enforceability may be implicated.

The approved short name may be used in secondary references after the full name has been stated, provided that no ambiguity is created. Where a document is executed, filed, certified, or relied upon for legal effect, the full legal name shall appear in the execution block, signature block, certification block, title block, or other appropriate legal-identity field.

Any use of the Corporation’s name in a contract or filing shall be reviewed for consistency with:

a) the Corporation’s official legal identity;

b) the Corporation’s state of incorporation or organization;

c) registered agent and registered office records;

d) federal tax status records;

e) state tax, charitable solicitation, foreign qualification, and local registration requirements where applicable;

f) donor, grant, restricted-fund, sponsorship, or public support restrictions;

g) non-execution, public authority, finance, procurement, certification, recognition, and provider-neutrality boundaries;

h) data, AI, cyber, privacy, export-control, sanctions, research integrity, accessibility, civil rights, and safeguards obligations; and

i) any relevant Nexus interface, GCRI Canada interface, GRF interface, GRA interface, or public-good stack compatibility record.

No person shall use the Corporation’s name in a filing, contract, public authority communication, public-facing material, technical repository, software artifact, grant narrative, fundraising material, investor-facing material, sponsor deck, provider document, or Nexus interface record in a manner that implies a legal status, authority, purpose, role, endorsement, approval, recognition, readiness, certification, procurement implication, or public authority relationship not supported by competent records.

2.8 Translation, Abbreviation, Program Name, Campaign Label, Project Label, Technical Asset Name, Repository Name, and Operating-Style Controls. Translations, abbreviations, program names, campaign labels, project labels, technical asset names, repository names, operating styles, public-safe publication titles, domain names, account names, email aliases, data-room names, controlled-room names, software package names, dataset titles, benchmark names, proof-receipt labels, dashboards, maps, Academy labels, Nexus Universe labels, Nexus Observatory labels, or other derivative naming conventions shall be treated as controlled institutional naming surfaces.

No such naming surface shall:

a) misstate the Corporation’s legal identity;

b) imply that a program, project, repository, controlled room, software asset, technical baseline, dataset, report, whitepaper, or dashboard is a separate legal entity unless lawfully constituted and recorded;

c) imply that a technical asset, method, evidence artifact, proof receipt, ledger entry, signal, AI output, digital twin, benchmark, or dashboard has legal authority beyond its recorded status;

d) imply that a GCRI US program is a GRF recognition program, GRA finance-readiness program, Nexus Standards certification program, public authority program, procurement program, investment program, insurance program, emergency command program, or provider-selection program unless separately and lawfully structured and recorded;

e) imply public authority endorsement, public authority adoption, public funding, sovereign obligation, public warning authority, emergency readiness, public finance approval, procurement approval, or regulatory approval;

f) imply provider preference, sponsor control, donor control, funder control, commercial exclusivity, market status, investment suitability, bankability, insurability, rating, certification, or compliance approval; or

g) weaken public-safe claims discipline, validity-by-record, correctionability, anti-capture rules, or the GCRI / GRF / GRA role separation.

The Corporation may require review, approval, controlled vocabulary mapping, legal review, translation review, accessibility review, public-safe review, safeguards review, or repository review before any naming surface is used externally or in a controlled room.

2.9 Prohibition on Legal-Identity Ambiguity. No director, officer, member, participant, employee, contractor, fellow, advisor, volunteer, contributor, sponsor, donor, funder, provider, host, university, laboratory, public authority participant, partner, or other person shall use the Corporation’s name, short name, mark, logo, seal, badge, repository name, program name, report title, technical asset name, public-good software name, or Nexus reference in a manner that creates legal-identity ambiguity.

Legal-identity ambiguity includes any use that could reasonably cause a person to believe that:

a) GCRI US is GCRI Canada;

b) GCRI US is the same legal person as any other GCRI entity;

c) GCRI US is GRF, GRA, Nexus Standards, Nexus Network, Nexus Universe, Nexus Observatory, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Risk Management, or Nexus Competence Cells;

d) GCRI US owns, controls, supervises, represents, or binds any Nexus entity, consortium, National Consortium Company, Project SPV, provider, sponsor, host, public authority, university, laboratory, donor, funder, investor, insurer, lender, contractor, or operator;

e) GCRI US has public authority status, public finance status, procurement authority, emergency authority, public warning authority, certification authority, recognition authority, protocol authority, investment authority, insurance authority, banking authority, rating authority, or enterprise execution authority; or

f) a person using the Corporation’s name is authorized to bind, speak for, certify, approve, recognize, finance, procure, select, endorse, or act on behalf of GCRI US without written authority.

Where ambiguity exists, the narrower, less official, less authority-conferring, less finance-signaling, less certification-implying, less procurement-implying, less public-authority-implying, and more public-good-preserving interpretation shall govern pending correction.

2.10 Distinction From The Global Centre for Risk and Innovation Generally. The name of the Corporation shall not be used to collapse the distinction between The Global Centre for Risk and Innovation - United States as a United States legal entity and The Global Centre for Risk and Innovation as a broader mission family, public-good function, institutional architecture, or global evidence, methods, observability, ontology, public-good R&D, and technical-stewardship concept.

References to the broader GCRI function may be used only where the context makes clear whether the reference concerns:

a) the Corporation as a United States legal entity;

b) GCRI Canada as a separate Canadian legal entity;

c) another national, regional, or specialized GCRI entity where lawfully constituted;

d) a shared doctrine, ontology, method, technical baseline, public-good software asset, research theme, or public-good function; or

e) a Nexus public-good stack interface.

No reference to the broader GCRI function shall create mutual authority to bind, shared liability, common treasury, shared tax status, common employer status, agency, partnership, joint venture, merger, branch status, parent-subsidiary status, or alter ego status among GCRI US, GCRI Canada, or any other GCRI-related entity.

2.11 Distinction From GCRI Canada. GCRI US shall preserve legal and public-description distinction from The Global Centre for Risk and Innovation - Canada. The two entities may share mission orientation, public-benefit doctrine, Nexus architecture alignment, controlled vocabulary, evidence structures, methods, ontology, public-good software, open technical baselines, Academy learning materials, public-safe publications, and interoperability commitments, but such alignment shall not create legal fusion.

Any use of the GCRI US name in relation to GCRI Canada shall preserve:

a) separate legal personality;

b) separate boards and fiduciary duties;

c) separate corporate records;

d) separate treasury, accounting, tax, grant, donation, sponsorship, and reporting obligations;

e) separate employment, contractor, volunteer, fellow, advisor, and service arrangements unless lawfully shared under written instrument;

f) separate authority to bind;

g) separate public claims;

h) separate compliance with United States and Canadian law respectively;

i) separate public authority interfaces; and

j) separate liability.

No shared name, logo, publication, event, platform, repository, dataset, technical baseline, controlled room, program, funder, sponsor, donor, advisor, director, officer, employee, contractor, public authority contact, or Nexus interface shall be used to imply that GCRI US and GCRI Canada are branches, agents, alter egos, parent and subsidiary, common employer, joint employer, merged entities, or one another’s fiduciary representatives unless an express lawful instrument provides otherwise.

2.12 Distinction From Other National or Regional GCRI Entities. GCRI US shall be distinguished from any other national, regional, state, territorial, sectoral, thematic, or specialized GCRI entity or interface that may be lawfully constituted or described from time to time. No other GCRI entity or interface shall use the GCRI US name in a manner that suggests authority over the Corporation, and the Corporation shall not use another GCRI name in a manner that suggests authority over that entity, except where expressly authorized by lawful instrument.

Where GCRI US participates in a shared GCRI mission, public-good asset, research line, public-safe publication, technical baseline, software project, controlled vocabulary, Nexus Universe activity, Nexus Observatory activity, or cross-border coordination, each participating entity’s name, capacity, contribution, authority, records, and limitation shall be separately identified where needed to prevent legal, public authority, finance, certification, procurement, tax, or liability confusion.

2.13 Distinction From The Global Risks Forum (GRF). GCRI US shall be distinguished from The Global Risks Forum (GRF). GRF is the public-good registry, recognition, maturity-records, standing, claims-discipline, stakeholder-formation, public-safe reporting, and public-facing legitimacy steward within the Nexus public-good stack.

GCRI US may provide evidence, methods, observability records, ontology references, technical baseline inputs, challenge signals, correction signals, Docket evidence inputs, Grid maturity evidence inputs, and public-safe technical summaries to GRF. Such support shall not permit use of the GCRI US name to imply that GCRI US issues GRF recognition, creates standing, determines public-facing maturity, approves public claims, confers public legitimacy, controls registry status, or substitutes for GRF.

No GCRI US document, logo, report, proof receipt, dataset, method, dashboard, Nexus Observatory output, Nexus Universe output, technical baseline, public-good software asset, or public authority learning material shall be described as GRF recognition, GRF maturity status, GRF standing, GRF claims approval, GRF registry entry, or GRF public legitimacy unless GRF has lawfully and expressly recorded that status.

2.14 Distinction From The Global Risks Alliance (GRA). GCRI US shall be distinguished from The Global Risks Alliance (GRA). GRA is the finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, capital-reader room, and regulated-perimeter discipline steward within the Nexus public-good stack.

GCRI US may provide technical evidence, method integrity notes, observability artifacts, node evidence, host-readiness evidence, uncertainty records, limitation notes, technical baselines, public-good software references, resilience evidence, and public authority learning context to GRA. Such support shall not permit use of the GCRI US name to imply that GCRI US issues finance-readiness determinations, capital-readability determinations, investment suitability, bankability, insurability, underwriting views, ratings, public finance approvals, capital commitments, securities offerings, brokerage, lending, insurance placement, or transaction recommendations.

No GCRI US artifact shall be labeled, marketed, represented, or used as a GRA proof pack, GRA finance-readiness determination, GRA capital-reader output, GRA insurance-readiness output, RNFD approval, NFD approval, UNFSD approval, investment memorandum, rating, underwriting basis, lending approval, public finance approval, or capital solicitation unless a competent GRA record and applicable law support the exact status and use.

2.15 Distinction From Nexus Network. GCRI US shall be distinguished from Nexus Network, which is the permanent public-good infrastructure rail connecting systemic-risk evidence, observability, standards discipline, public-safe claims, maturity records, readiness inputs, public authority capacity classification, finance-readiness interfaces, regional legitimacy, national mandate, investible infrastructure, Project SPVs, qualified providers, and open enterprise delivery.

GCRI US may contribute United States-relevant evidence, methods, ontology, observability systems, public-good software, open technical baselines, research integrity, technical review, and correction signals to Nexus Network. Such contribution shall not mean that GCRI US owns Nexus Network, operates Nexus Network as an enterprise system, controls all Nexus rails, admits assets to the Nexus Grid, approves Docket advancement, determines provider eligibility, or binds public authorities, consortiums, National Consortium Companies, Project SPVs, or Qualified Enterprise Providers.

Use of the Corporation’s name in connection with Nexus Network shall be role-specific, record-based, and non-executing.

2.16 Distinction From Nexus Standards, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, and Nexus Competence Cells. GCRI US shall be distinguished from Nexus Standards, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, and Nexus Competence Cells, each of which may have distinct functions, governance instruments, records, operating protocols, maturity concepts, authority surfaces, and public-facing meanings.

GCRI US may support those functions through evidence, methods, observability, ontology, public-good software, technical baselines, technical review, safeguarded data practices, public authority learning, research integrity, challenge methods, benchmark methods, public-safe publication inputs, Docket evidence inputs, Grid maturity evidence inputs, Academy technical learning inputs, and correction signals. Such support shall not permit the GCRI US name to imply that:

a) GCRI US is Nexus Standards or protocol authority;

b) GCRI US certifies conformance by default;

c) GCRI US operates the Nexus Observatory as a public warning authority or emergency command body;

d) GCRI US controls Nexus Universe or converts annual build evidence into permanent adoption;

e) GCRI US issues Nexus Risk Management decisions as public authority commands;

f) GCRI US operates Nexus Rails as finance execution rails;

g) GCRI US admits assets into Nexus Grid by itself;

h) GCRI US issues regulated Academy credentials by default; or

i) GCRI US converts competence-cell participation into certification, licensure, procurement qualification, public authority recognition, or provider preference.

Use of the Corporation’s name in these contexts shall preserve the rule that evidence support is not recognition, methods support is not certification, observability support is not public warning, finance-readiness input is not finance execution, Docket preparation is not Docket approval, and Grid input is not Grid integration.

2.17 Distinction From Global, Regional, National, State, Territorial, Tribal, Metropolitan, and Sectoral Nexus Consortiums. GCRI US shall be distinguished from Global Nexus Consortium, Regional Nexus Consortiums, National Nexus Consortiums, state or territorial Nexus consortiums, Tribal or Indigenous Nexus interfaces, metropolitan Nexus structures, sectoral Nexus bodies, public-good consortiums, leadership councils, investor councils, Helix councils, working groups, and any other consortium or coordinating body formed within or adjacent to the Nexus architecture.

GCRI US may participate in or support such consortiums through public-good evidence, methods, technical review, observability, ontology, public-good software, open technical baselines, research integrity, safeguards, controlled vocabulary, public authority learning, and correction signals. Such participation shall not permit use of the GCRI US name to imply that GCRI US:

a) controls the consortium;

b) serves as the consortium’s legal parent;

c) carries the consortium’s liabilities;

d) holds the consortium’s mandate;

e) serves as public authority for the consortium;

f) approves national mandate, regional mandate, state mandate, territorial mandate, Tribal mandate, public finance, procurement, recognition, certification, or provider status;

g) owns any National Consortium Company or Project SPV by default; or

h) converts consortium participation into legal authority, enterprise execution, or public authority adoption.

Regional public-good mandate, national consolidation, investible infrastructure, and open enterprise delivery shall remain distinct stages and shall not be collapsed by use of the GCRI US name.

2.18 Distinction From National Consortium Companies, State or Regional Operating Companies, Project SPVs, Qualified Enterprise Providers, Sponsors, Hosts, Donors, Public Authorities, Universities, Laboratories, and Enterprise Execution Actors. GCRI US shall be distinguished from all National Consortium Companies, state or regional operating companies, Project SPVs, Qualified Enterprise Providers, sponsors, hosts, donors, funders, public authorities, universities, laboratories, vendors, contractors, investors, insurers, lenders, banks, underwriters, operators, systems integrators, technology providers, cloud providers, telecommunications providers, AI providers, cybersecurity providers, sensor providers, infrastructure providers, media partners, and other enterprise execution actors.

The Corporation may collaborate with, receive support from, provide public-good evidence to, accept data from, host controlled-room participation with, publish public-safe summaries involving, or otherwise interact with such persons or entities where lawful and record-supported. Such interaction shall not permit any use of the GCRI US name that implies:

a) provider preference;

b) procurement advantage;

c) public authority endorsement;

d) investment suitability;

e) finance-readiness;

f) insurance-readiness;

g) bankability;

h) public finance approval;

i) rating;

j) certification;

k) recognition;

l) commercial exclusivity;

m) sponsorship control;

n) donor control;

o) research outcome control;

p) operational control;

q) ownership of enterprise assets;

r) merger, agency, partnership, joint venture, common treasury, or shared liability; or

s) authority to bind GCRI US.

No enterprise actor shall become constitutional to GCRI US or to Nexus by reason of early participation, funding, contribution, technical centrality, demonstration, benchmark performance, host relationship, public authority relationship, repository contribution, data-room access, controlled-room access, or proximity to leadership.

2.19 Mark, Logo, Seal, Badge, Dataset, Software, Report, Whitepaper, Technical Baseline, Public-Good Asset, and Public Statement Name-Use Controls. All marks, logos, seals, badges, dataset names, software names, report titles, whitepaper titles, technical baseline titles, public-good asset names, public statements, public-safe summaries, dashboards, maps, proof receipts, repository names, digital identifiers, domains, social media handles, event names, program names, Academy labels, and Nexus interface labels associated with GCRI US shall be governed name-use surfaces.

No mark, logo, seal, badge, dataset, software package, report, whitepaper, technical baseline, public-good asset, or public statement shall be used to imply legal status, authority, endorsement, certification, recognition, finance-readiness, procurement approval, public authority action, public warning, emergency command, protocol effect, Docket status, Grid status, provider preference, sponsor control, donor control, public-good ownership by a private party, or enterprise execution unless the exact meaning is supported by competent record and approved under applicable procedures.

The Corporation may adopt naming guides, mark-use rules, logo-use rules, seal-use rules, badge-use rules, public-safe claim rules, attribution rules, licensing rules, repository naming rules, software naming rules, dataset naming rules, technical baseline naming rules, and public statement templates to preserve institutional clarity and prevent misuse.

2.20 Unauthorized Name Use. Unauthorized name use includes any use of the Corporation’s official name, short name, abbreviation, mark, logo, seal, badge, report title, dataset name, software name, technical baseline, public-good asset, controlled vocabulary, repository name, public-safe statement, proof receipt, or Nexus reference without authority or outside the scope of authority granted.

Unauthorized name use may occur in contracts, filings, websites, public statements, social media, press materials, grant applications, fundraising materials, sponsor materials, investor materials, insurance materials, lending materials, procurement materials, public authority materials, provider materials, marketing materials, conference materials, academic materials, repository materials, code comments, dataset metadata, dashboards, maps, controlled rooms, data rooms, or AI-generated summaries.

The Corporation may respond to unauthorized name use through correction, restriction, withdrawal, takedown, access revocation, suspension, termination, contract remedy, legal notice, public-safe clarification, controlled clarification, repository correction, public authority clarification, funder notice, sponsor notice, provider notice, or other lawful action proportionate to the risk.

2.21 Misleading Use. Misleading use includes any name use that is technically accurate in form but misleading in implication, context, emphasis, omission, audience, timing, placement, visual design, co-branding, sequencing, metadata, hyperlinking, AI-generated summary, dashboard presentation, or public authority proximity.

Misleading use includes any communication that causes or could reasonably cause misunderstanding concerning:

a) the Corporation’s legal identity;

b) the Corporation’s United States seat;

c) the Corporation’s nonprofit or tax-exempt status;

d) the Corporation’s relationship with GCRI Canada;

e) the Corporation’s relationship with GRF, GRA, Nexus Standards, Nexus Network, or other Nexus bodies;

f) the Corporation’s authority over public authorities, funders, universities, laboratories, providers, sponsors, hosts, National Consortium Companies, Project SPVs, or enterprise actors;

g) the status of evidence, methods, technical baselines, software, datasets, dashboards, maps, benchmarks, proof receipts, Docket records, Grid records, or Academy records;

h) the existence of recognition, certification, finance-readiness, procurement approval, public authority approval, public warning authority, emergency readiness, provider preference, or commercial exclusivity; or

i) the role of sponsors, donors, funders, providers, hosts, or enterprise actors in institutional decision-making.

Misleading use shall be corrected even where no intent to mislead is proven.

2.22 Sponsor-Driven Use. Sponsors, donors, funders, grantmakers, in-kind contributors, supporters, or other financial contributors shall not use the Corporation’s name, marks, logos, reports, public-good assets, technical baselines, software, datasets, controlled vocabulary, public-safe summaries, or Nexus references except as expressly authorized under written terms or approved public acknowledgment rules.

Sponsor-driven use shall not imply:

a) governance rights;

b) editorial control;

c) research conclusion control;

d) method-control rights;

e) evidence-control rights;

f) publication veto or suppression rights;

g) public authority access rights;

h) Docket influence;

i) Grid influence;

j) finance-readiness influence;

k) recognition influence;

l) certification influence;

m) procurement advantage;

n) provider preference;

o) commercial exclusivity;

p) public-good authority;

q) protocol authority; or

r) institutional endorsement of the sponsor’s products, services, policies, investments, public positions, or commercial offerings.

Any sponsor acknowledgment shall be accurate, proportionate, non-misleading, and consistent with the support-without-control doctrine.

2.23 Provider-Driven Use. Providers, vendors, contractors, systems integrators, telecom operators, AI providers, cloud providers, cybersecurity providers, sensor providers, data providers, infrastructure providers, software providers, consultants, operators, National Consortium Companies, Project SPVs, and other enterprise actors shall not use the Corporation’s name or associated marks, logos, reports, public-good assets, technical baselines, software, datasets, dashboards, public-safe summaries, proof receipts, or Nexus references to imply preferred status, procurement advantage, public authority approval, technical certification, recognition, finance-readiness, investment suitability, insurance-readiness, bankability, Docket approval, Grid integration, or Nexus-compatible status unless the exact status is supported by competent record and authorized use.

Provider participation, technical contribution, benchmark performance, challenge participation, controlled-room access, data-room access, sponsorship, host relationship, public authority relationship, early involvement, repository contribution, or technical centrality shall not authorize provider-driven name use beyond the scope expressly approved.

The Corporation may require provider materials to include disclaimers, status limits, non-endorsement language, public authority boundary language, finance boundary language, certification boundary language, and correction obligations.

2.24 Public Authority-Confusing Use. No person shall use the Corporation’s name in a manner that implies federal, state, territorial, Tribal, local, municipal, county, port, utility, public health, emergency management, public safety, public works, telecom, water, energy, food, cyber, infrastructure, public finance, development finance, regulator, university, laboratory, or other public-sector approval, adoption, endorsement, funding, procurement, regulatory comfort, public warning authority, emergency readiness, sovereign obligation, statutory certification, public-private partnership, Docket approval, Grid approval, Academy credential recognition, or public authority delegation unless expressly and lawfully recorded by competent authority.

Where public authority participation is referenced, the communication shall identify the capacity of participation where needed to prevent misunderstanding, including whether the public authority or public-sector person participated as official participant, observer, technical contributor, regulator-listening participant, public finance reader, emergency-management participant, public infrastructure operator, academic representative, personal-capacity participant, invited guest, data provider, reviewer, simulation participant, controlled-room participant, Docket-context contributor, Grid-context contributor, or other recorded capacity.

Where capacity is unclear, the least official and least authority-conferring interpretation shall apply pending correction.

2.25 Finance-Signaling Use. No person shall use the Corporation’s name in a manner that signals or implies finance-readiness, investment suitability, bankability, insurability, underwriting support, rating, creditworthiness, public finance approval, capital-readability, routeability, securities offering, capital solicitation, lending approval, insurance placement, guarantee, tax credit approval, grant approval, MDB or DFI approval, sovereign finance approval, or public budget commitment.

GCRI US evidence, methods, observability records, host-readiness records, node records, technical baselines, public-good software, Nexus Observatory outputs, Nexus Universe outputs, proof receipts, Docket evidence inputs, Grid maturity inputs, and technical notes may support downstream finance-readiness work by the proper institution, including GRA where applicable, but shall not be labeled or marketed as finance-readiness determinations by GCRI US.

Any finance-adjacent reference shall preserve the distinction between upstream evidence production, downstream finance-readiness translation, and lawful capital execution by separate actors.

2.26 Certification-Implying Use. No person shall use the Corporation’s name to imply certification, accreditation, compliance approval, legal conformance, technical conformance approval, standards approval, regulatory safe harbor, professional credential, provider qualification, public authority approval, procurement eligibility, Docket approval, Grid integration, or Nexus-compatible status unless the exact status is authorized by a competent institution and recorded under the applicable procedure.

GCRI US may produce evidence, methods, public-good software, technical baselines, benchmark methods, test harnesses, evaluation sets, proof-receipt logic, model cards, dataset cards, system cards, public-safe technical summaries, and technical review notes. None of those outputs shall constitute certification merely because they are produced, maintained, published, referenced, or technically relied upon by GCRI US.

Where a GCRI US output is used in a certification, conformance, standards, procurement, or public authority context by another competent body, the GCRI US role shall be described as evidence, method, technical, or public-good support only unless a separate lawful instrument expressly provides otherwise.

2.27 Procurement-Implying Use. No person shall use the Corporation’s name to imply procurement approval, vendor selection, public contract award, preferred-provider status, public authority buying recommendation, public authority procurement compliance, bid advantage, sole-source justification, procurement readiness, public purchasing endorsement, or public-sector adoption.

GCRI US shall not select vendors for public authorities, rank providers for procurement purposes, approve procurements, issue buying recommendations, or use its public-good evidence role to confer market advantage. Technical participation, research collaboration, benchmark performance, sponsorship, public authority presence, host relationship, or Nexus involvement shall not be represented as procurement preference.

Any use of GCRI US materials in bid, procurement, vendor, grant, infrastructure, public authority, or market-facing contexts shall be subject to public-safe claims discipline and may require express written permission, non-endorsement language, and correction obligations.

2.28 North America Anchor Overclaim. No person shall use the Corporation’s bounded North America anchor role to imply North America-wide legal authority, regional sovereignty, treaty authority, intergovernmental authority, public authority status, regulatory authority, public finance authority, procurement authority, emergency command authority, public warning authority, certification authority, recognition authority, finance-readiness authority, protocol authority, enterprise execution authority, or control over GCRI Canada, Mexico-facing interfaces, Caribbean interfaces, Arctic interfaces, Indigenous interfaces, regional Nexus bodies, national Nexus bodies, public authorities, universities, laboratories, hosts, sponsors, providers, investors, insurers, lenders, National Consortium Companies, Project SPVs, or Qualified Enterprise Providers.

North America anchor language shall be limited to the Corporation’s lawful and record-supported role in evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, verifiable compute, verifiable intelligence, research integrity, public authority learning, cross-border evidence alignment, and safeguarded public-good technical infrastructure.

Any North America anchor reference shall be corrected if it suggests ownership, control, legal fusion, official public authority status, finance execution, regional regulator status, treaty body status, procurement authority, public warning role, emergency command role, or enterprise delivery role.

2.29 Correction, Withdrawal, Takedown, and Public Clarification for Misuse. Where the Corporation determines that its name, short name, mark, logo, seal, badge, program name, technical asset name, repository name, dataset name, software name, report title, whitepaper title, public-good asset, public statement, public-safe notice, proof receipt, dashboard, map, domain, social media reference, or Nexus reference has been used without authority, outside authorized scope, inaccurately, misleadingly, or in a manner inconsistent with this Bylaw, the Corporation may require correction, withdrawal, restriction, retraction, takedown, access revocation, public-safe clarification, controlled clarification, contract correction, repository correction, metadata correction, search-index correction, public authority clarification, sponsor clarification, provider clarification, funder clarification, or other lawful remedy proportionate to the risk.

Corrective action may be required where misuse creates or may create confusion concerning:

a) legal identity;

b) authority to bind;

c) relationship to GCRI Canada or other GCRI entities;

d) relationship to GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, National Consortium Companies, Project SPVs, providers, sponsors, hosts, public authorities, universities, laboratories, or enterprise actors;

e) public authority status or public authority approval;

f) finance-readiness, insurance-readiness, investment suitability, rating, bankability, routeability, public finance approval, or capital-readability;

g) certification, accreditation, conformance, compliance approval, procurement status, provider preference, or Nexus-compatible status;

h) research integrity, evidence status, methods status, technical truth, public-safe publication, Docket status, Grid status, Academy credential status, or proof-receipt meaning;

i) sponsor, donor, funder, provider, host, or enterprise influence;

j) data, AI, cyber, privacy, export-control, sanctions, protected knowledge, civil rights, accessibility, community safeguards, or public-safe mapping status; or

k) non-execution, public-benefit, nonprofit, tax, or legal-separateness boundaries.

The Corporation may preserve a record of the misuse, the corrective action taken, the persons notified, the materials corrected or withdrawn, the public or controlled clarification issued, the legal or contractual steps taken, and any recurrence controls adopted. The governing rule of this Section is that the Corporation’s name is a public-good trust surface: it shall identify the Corporation accurately, preserve its legal separateness, prevent authority inflation, protect public-safe meaning, and remain correctionable at all times.

Section 3. Governing Statute, Legal Form, Registered Office, Principal Office, and United States Seat

3.1 Governing Statute. The Corporation shall be organized, governed, maintained, and operated under the nonprofit corporation law of the United States state in which it is incorporated or otherwise lawfully formed, together with the Corporation’s Certificate of Incorporation, Articles of Incorporation, charter, or other constituting instrument, this Bylaw, all validly adopted Board resolutions, all policies and instruments adopted under this Bylaw, and all applicable federal, state, territorial, Tribal-interface, District of Columbia, local, tax, nonprofit, charitable solicitation, corporate, employment, privacy, cybersecurity, AI, research, export-control, sanctions, public authority, grant, lobbying, political activity, procurement-integrity, civil rights, accessibility, and other laws applicable to the Corporation.

The governing statute shall provide the Corporation’s internal corporate-law foundation, including rules concerning corporate existence, Board authority, director duties, officer authority, member rights where applicable, records, meetings, filings, registered office, registered agent, indemnification, amendment, merger, dissolution, and other matters of nonprofit corporate governance.

The governing statute shall not be interpreted to expand the Corporation beyond its public-benefit purpose, nonprofit character, nonstock or non-share character, non-distribution rule, tax-exempt or tax-exempt-compatible posture where applicable, non-execution perimeter, role-separation obligations, public authority boundary, finance boundary, certification boundary, procurement boundary, provider-neutrality rule, sponsor support-without-control rule, validity-by-record doctrine, correctionability doctrine, or the limitations set forth in this Bylaw.

Where the governing statute permits flexibility, discretion, waiver, delegation, electronic action, officer authority, committee authority, member action, indemnification, compensation, asset use, dissolution, or other governance choice, such flexibility shall be exercised only in a manner consistent with the Corporation’s public-benefit mission, United States seat discipline, Nexus role separation, non-execution status, records discipline, and anti-capture obligations.

3.2 State of Incorporation or Organization. The Corporation shall be incorporated, organized, or otherwise legally constituted in one United States state selected by the competent incorporator, initial Board, or Board, as applicable, and recorded in the Corporation’s authoritative corporate records.

The state of incorporation or organization shall be the Corporation’s corporate-law home jurisdiction for internal governance purposes unless and until lawfully changed by competent action. Such state shall be identified in the Corporation’s Certificate or Articles, corporate register, bylaw register, Board records, registered agent records, tax records, banking records, insurance records, grant records, and other governance-significant records.

The Corporation may operate, qualify, register, solicit, employ, contract, convene, publish, maintain repositories, operate programs, conduct research, receive support, hold controlled rooms, engage public authorities, collaborate with universities and laboratories, support Nexus interfaces, and conduct lawful public-benefit activities outside its state of incorporation where lawful and where required registrations, qualifications, filings, notices, tax reviews, charitable solicitation reviews, employment reviews, data reviews, public authority reviews, and local-law reviews are completed or appropriately escalated.

No operation outside the state of incorporation shall create a new state of incorporation, legal seat, principal governance seat, foreign branch, state agency, territorial agency, Tribal governmental relationship, local public authority status, public-private partnership, public authority delegation, tax status, charitable status, or separate legal personality unless expressly and lawfully recorded by competent authority.

3.3 United States Nonprofit Corporate Character. The Corporation shall be maintained as a United States nonprofit corporation. It shall be organized and operated for lawful public-benefit, scientific, educational, research, evidence, methods, observability, ontology, public-good R&D, public-good software, open technical baseline, public authority learning, technical literacy, safeguards, and systemic-risk purposes, and not for the private profit of any director, officer, member, founder, sponsor, donor, funder, provider, host, contractor, employee, advisor, contributor, participant, related person, or private person.

The Corporation’s nonprofit corporate character shall apply to all programs, platforms, research activities, repositories, datasets, software, technical baselines, publications, controlled rooms, public authority learning activities, Academy activities, Nexus interface activities, sponsorships, grants, donations, subscriptions, cost-recovery receipts, fee-based programs, in-kind contributions, and public-good support arrangements.

The Corporation may receive revenue, grants, donations, sponsorships, subscriptions, fees, reimbursements, in-kind support, cost-recovery payments, awards, program support, restricted funds, unrestricted funds, and other lawful support where such support is used for lawful corporate purposes and does not create private inurement, impermissible private benefit, sponsor control, donor control, provider preference, public authority access purchase, recognition purchase, finance-readiness purchase, certification purchase, procurement advantage, or prohibited execution activity.

The nonprofit corporate character of the Corporation shall not be weakened by operational sophistication, technical centrality, public authority participation, enterprise collaboration, sponsorship, support from commercial actors, open-source software activity, fee-based learning, cost-recovery arrangements, controlled-room access, public-good infrastructure support, or participation in Nexus-aligned systems.

3.4 Corporation Without Share Capital. The Corporation shall have no share capital, no equity owners, no shareholders, no profit participation interests, no dividend rights, no equity appreciation rights, no liquidation preference for private persons, and no ownership interests capable of being held, traded, transferred, pledged, encumbered, inherited, sold, securitized, tokenized, or otherwise treated as private property.

No person shall acquire any ownership interest in the Corporation, its mission, legal identity, name, marks, records, repositories, evidence artifacts, methods, ontologies, taxonomies, controlled vocabularies, public-good software, technical baselines, public-good technical assets, datasets, model cards, system cards, public-safe publications, Academy materials, Nexus interface outputs, public authority learning materials, goodwill, institutional standing, or public-benefit purpose by reason of contribution, authorship, employment, contract, donation, sponsorship, funding, participation, membership, subscription, advisory role, public authority participation, hosting, repository maintenance, technical centrality, program leadership, or Board service.

Assets of the Corporation shall be dedicated to its lawful nonprofit and public-benefit purposes. Upon dissolution or winding up, assets shall be distributed only as permitted by applicable law, the Articles or Certificate, tax-exempt or tax-exempt-compatible requirements where applicable, donor restrictions where lawful, and this Bylaw, and not for the private benefit of directors, officers, members, founders, sponsors, donors, funders, providers, hosts, contractors, employees, advisors, contributors, or private persons.

3.5 Non-Stock Character Where Applicable. Where the governing state law uses the term “nonstock corporation,” the Corporation shall be treated as a nonstock nonprofit corporation. Where the governing law uses a different formulation, the equivalent non-share, non-equity, non-distributing nonprofit character shall govern.

No membership category, supporter category, subscription category, donor category, sponsorship tier, advisory role, fellowship, contributor role, public authority participation category, provider participation category, host status, Academy status, controlled-room access class, repository role, technical maintainer status, or Nexus interface role shall be treated as stock, equity, beneficial ownership, voting security, economic ownership, transferable ownership interest, investment contract, security, partnership interest, fund interest, or property interest in the Corporation.

Where statutory members exist, if any, their rights shall be governance rights only to the extent expressly conferred by applicable law, the Articles or Certificate, this Bylaw, or a competent recorded act. Such rights shall not include any ownership of the Corporation or its assets, profits, reserves, public-good assets, records, technical baselines, or institutional outputs.

3.6 Registered Office. The Corporation shall maintain a registered office in its state of incorporation or organization as required by applicable law. The registered office shall be recorded in the Corporation’s corporate register, state filings, registered agent records, bylaw register, and other records required by law or approved by the Board.

The registered office may be a physical office, registered agent address, statutory office, or other address permitted by applicable law. It shall not necessarily be the Corporation’s principal office, operational headquarters, governance seat, records repository, public-facing address, controlled-room location, data-processing location, research location, public authority interface location, or Nexus interface location unless the Corporation’s records expressly provide otherwise.

The registered office shall be used for statutory notice, service of process, state filing, registered agent coordination, corporate status maintenance, and other legally required purposes. It shall not by itself confer operational authority, program location, public authority relationship, public-service area, public-private partnership status, tax-exempt status, charitable solicitation status, federal authority, state authority, territorial authority, local authority, Tribal authority, or Nexus role.

3.7 Registered Agent. The Corporation shall maintain a registered agent in its state of incorporation or organization as required by applicable law. The registered agent shall be authorized to receive service of process, legal notices, statutory notices, and other communications required or permitted under governing law.

The identity and contact information of the registered agent shall be maintained in the Corporation’s corporate records and updated in accordance with applicable law. Any change of registered agent shall be approved and recorded as required by law, the Articles or Certificate, this Bylaw, Board resolution, or delegated authority.

The registered agent shall not have authority to bind the Corporation, speak for the Corporation, approve filings beyond the scope of engagement, accept restricted funds, approve contracts, make public statements, approve name use, issue evidence artifacts, release public-good software, approve public authority references, approve data access, conduct regulatory engagement, certify records, or exercise any governance, fiduciary, executive, technical, financial, public authority, Nexus, or program authority unless separately and lawfully delegated by competent record.

3.8 Principal Office. The Corporation may maintain a principal office at such location within or outside its state of incorporation as the Board may determine, subject to applicable law, corporate records, state registration requirements, tax requirements, employment requirements, charitable solicitation requirements, privacy and cybersecurity obligations, and public authority interface considerations.

The principal office may serve as the Corporation’s primary administrative office, governance office, executive office, program coordination location, records coordination location, or public-facing institutional address, as recorded by the Board or authorized officers. The principal office may be physical, hybrid, distributed, virtual, hosted, shared, or otherwise structured where lawful and operationally appropriate.

The existence of a principal office in any state, territory, District of Columbia, Tribal-interface context, local jurisdiction, host institution, university, laboratory, public authority facility, controlled room, or partner facility shall not by itself create state incorporation, public authority delegation, public-private partnership, branch status, agency, employment relationship, local public authority status, tax registration, charitable solicitation authorization, procurement status, provider preference, or enterprise execution authority.

The Corporation shall maintain accurate principal-office records and shall correct public materials, filings, contracts, repositories, notices, public authority communications, and funding documents where office descriptions create confusion concerning legal seat, operating authority, public authority status, or institutional control.

3.9 Principal United States Governance Seat. The Corporation shall maintain a principal United States governance seat for internal corporate governance purposes. The governance seat shall identify the primary jurisdictional and institutional point of reference for Board governance, officer authority, corporate records, bylaw administration, internal authority, fiduciary oversight, and United States legal discipline.

The principal United States governance seat may be the same as, or different from, the registered office or principal office, provided that the distinction is recorded and does not create ambiguity. Where the registered office, principal office, and principal governance seat differ, the Corporation’s records shall identify the function of each location and the applicable custody, notice, filing, tax, employment, and operational implications.

The governance seat shall not be represented as a federal seat, public authority seat, public warning center, emergency command center, procurement authority, finance authority, certification authority, protocol authority, standards monopoly, national company, Project SPV, provider office, or enterprise operating center.

The governance seat shall be interpreted as the Corporation’s internal corporate governance anchor, not as a claim to sovereign power, national mandate, regional supremacy, state authority, territorial authority, Tribal authority, or public authority delegation.

3.10 Board Authority to Change Registered Office, Registered Agent, Principal Office, or Governance Seat Where Lawful. The Board may change the registered office, registered agent, principal office, or principal United States governance seat where permitted by applicable law, the Articles or Certificate, this Bylaw, and any required state filing, registration, tax, charitable solicitation, employment, privacy, data, public authority, or contractual condition.

A change of registered office or registered agent shall be made in accordance with the governing state statute and any required filing. A change of principal office or governance seat shall be recorded in the Corporation’s official records and, where material, approved by Board resolution.

Before approving a material change, the Board or authorized officers shall consider, as applicable:

a) corporate filing requirements;

b) registered agent requirements;

c) state qualification implications;

d) charitable solicitation registration implications;

e) tax and franchise tax implications;

f) employment and contractor implications;

g) banking, insurance, grant, and restricted-fund implications;

h) data, privacy, AI, cybersecurity, export-control, sanctions, and controlled-technology implications;

i) public authority interface implications;

j) public records, open meetings, procurement, government ethics, or grant-compliance implications where public authorities are involved;

k) continuity of corporate records and authoritative repositories;

l) accessibility, civil rights, and public participation implications;

m) community, Tribal, Indigenous, territorial, local, and protected knowledge safeguards where relevant;

n) Nexus interface, GCRI Canada interface, GRF interface, GRA interface, and other cross-entity implications; and

o) risk of legal-identity ambiguity, public authority confusion, finance signaling, certification overclaim, procurement implication, provider preference, or sponsor control.

No office or seat change shall be used to weaken the Corporation’s nonprofit character, non-distribution rule, public-benefit purpose, non-execution perimeter, United States legal discipline, records integrity, anti-capture posture, or role separation.

3.11 United States as Record-of-Record Jurisdiction for Internal Corporate Acts. For internal corporate governance purposes, the Corporation shall maintain the United States as its record-of-record jurisdiction, and its state of incorporation or organization as the corporate-law anchor jurisdiction, unless lawfully changed.

The Corporation’s internal corporate acts, including Board actions, officer appointments, bylaw amendments, corporate records, delegations, committee charters, member actions where applicable, indemnification decisions, conflict determinations, major policies, adoption records, corporate filings, and dissolution actions, shall be recorded through the Corporation’s United States governance records.

The Corporation may maintain mirrored, interoperable, controlled, or duplicate records in other jurisdictions, repositories, systems, ledgers, controlled rooms, public authority rooms, Nexus interfaces, or partner systems where lawful and approved. Such records shall not displace the Corporation’s United States record-of-record jurisdiction unless expressly and lawfully adopted by competent authority.

No foreign, cross-border, regional, Nexus, repository, ledger, protocol, proof receipt, controlled-room, public authority, sponsor, provider, host, university, laboratory, or partner record shall override the Corporation’s United States internal corporate governance records unless applicable law requires otherwise or the Board lawfully adopts the record into the Corporation’s governance system.

3.12 State Law as Corporate-Law Anchor Subject to Federal Law. The law of the Corporation’s state of incorporation or organization shall serve as the corporate-law anchor for internal affairs, subject to applicable federal law and any mandatory law applicable to the Corporation’s activities, tax status, employment, grants, public authority interactions, data, AI, cybersecurity, export controls, sanctions, controlled technology, civil rights, accessibility, lobbying, political activity, charitable solicitation, research, public health, public safety, competition, antitrust, and other regulated matters.

State corporate-law anchoring shall not excuse compliance with federal law, the law of other states or territories where the Corporation operates or solicits support, the District of Columbia law where applicable, Tribal-interface respect where applicable, local law where applicable, contractual obligations, donor restrictions, grant conditions, public authority conditions, or cross-border obligations where lawful and binding.

Where state corporate law and another applicable legal obligation appear to conflict, the matter shall be escalated through the Corporation’s legal, compliance, Board, and records procedures. Pending resolution, the Corporation shall apply the most protective lawful posture and shall avoid any interpretation that creates unauthorized public authority meaning, finance-readiness implication, certification implication, procurement implication, provider preference, sponsor control, data misuse, protected knowledge exposure, or execution authority.

3.13 Federal Law Compliance. The Corporation shall comply with all applicable United States federal laws, regulations, rules, guidance where binding or contractually adopted, grant conditions, tax requirements, employment requirements, civil rights requirements, accessibility requirements, privacy requirements, cybersecurity requirements, AI-related requirements, sanctions requirements, export-control requirements, controlled-technology requirements, national security-related requirements, lobbying and political activity restrictions, procurement-integrity requirements, government ethics requirements, research requirements, intellectual property requirements, competition and antitrust laws, consumer protection laws, and other federal legal obligations applicable to its activities.

Federal compliance shall be especially reviewed where the Corporation engages in:

a) tax-exempt or tax-exempt-compatible activities;

b) grants, cooperative agreements, restricted funds, public funding, or federally connected support;

c) public authority learning, public authority participation, regulator-listening, emergency-management learning, or public finance reader activities;

d) data, AI, cybersecurity, privacy, health-sensitive, youth-related, infrastructure-sensitive, cyber-sensitive, public-sector, rights-bearing, or protected knowledge activities;

e) export-controlled, sanctions-sensitive, controlled technology, dual-use, national security-sensitive, compute, AI-RAN, O-RAN, DePIN, DLT, cyber, geospatial, satellite, robotics, sensor, semiconductor, or quantum-adjacent activities;

f) lobbying, political activity, public policy engagement, public communications, or public authority correspondence;

g) research, human-subjects, community-sensitive, Tribal or Indigenous, health-sensitive, biosecurity-relevant, or public-safety-relevant activities;

h) competition-sensitive convenings, benchmarking, clean rooms, industry councils, provider comparisons, market baselines, or standards-support activities; and

i) finance-adjacent, insurance-adjacent, investment-adjacent, lending-adjacent, public finance-adjacent, procurement-adjacent, certification-adjacent, or rating-adjacent outputs.

Federal compliance shall not be treated as certification, public authority approval, regulatory approval, public finance approval, procurement approval, or public endorsement unless the competent federal authority lawfully records such consequence.

3.14 State, Territorial, Tribal, District of Columbia, and Local Law Compliance Where Applicable. The Corporation shall comply with applicable state, territorial, District of Columbia, Tribal-interface, and local laws where its activities, presence, solicitation, employment, contracting, data processing, public authority engagement, research, controlled rooms, events, publications, public-safe reporting, public-good software release, technical deployment support, fundraising, fee collection, sponsorship, or other activities create legal obligations.

The Corporation shall review and, where required, complete state or territorial foreign qualification, charitable solicitation registration, tax registration, employment registration, contractor compliance, public authority contracting registration, data privacy compliance, cybersecurity compliance, event permitting, lobbying registration, government ethics compliance, grant compliance, sales or use tax review, and other local requirements before conducting activities that require such steps.

Engagement with Tribal Nations, Indigenous governments, Indigenous communities, Tribal instrumentalities, Indigenous knowledge holders, or Indigenous data contexts shall be conducted with respect for sovereignty, consent, non-consent, protected knowledge, data governance, cultural protocols, local law, federal Indian law where applicable, and community safeguards. No Tribal or Indigenous participation shall be represented as endorsement, delegation, consent, public authority approval, or data permission unless expressly and lawfully recorded.

No state, territorial, District of Columbia, Tribal, local, county, municipal, metropolitan, port, utility, public health, emergency management, public safety, public works, water, energy, food, telecom, cyber, infrastructure, university, laboratory, or public-sector interface shall be treated as public authority delegation, procurement approval, funding approval, public finance approval, emergency authority, public warning authority, regulatory authority, certification authority, or official adoption unless expressly and lawfully recorded by competent authority.

3.15 North America Anchor Function Without Foreign Legal Merger. The Corporation may serve as a bounded North America anchor for evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, verifiable compute, verifiable intelligence, research integrity, public authority learning, and safeguarded public-good technical infrastructure where such role is lawful, record-supported, and consistent with this Bylaw.

The North America anchor function shall not create merger, agency, branch status, parent-subsidiary status, alter ego status, common treasury, shared liability, shared tax status, joint employment, common employer status, foreign registration by implication, treaty status, intergovernmental status, regional regulator status, public authority status, sovereign status, procurement authority, public finance authority, emergency command authority, public warning authority, certification authority, finance-readiness authority, recognition authority, protocol authority, or enterprise execution authority.

The Corporation may coordinate with GCRI Canada, Mexico-facing interfaces, Caribbean interfaces, Arctic interfaces, Great Lakes interfaces, Atlantic interfaces, Pacific interfaces, Gulf interfaces, border-region interfaces, Tribal and Indigenous interfaces, universities, laboratories, public authorities, civil society, communities, hosts, sponsors, providers, regional Nexus bodies, national Nexus bodies, and other lawful partners, provided that the exact legal capacity, authority, records, data controls, public authority status, public-safe claims, and correction path are identified where needed.

The Corporation shall preserve the rule: North America coordination may align evidence and methods, but it shall not fuse legal entities, merge treasuries, transfer authority, override domestic law, create public authority status, or convert public-good stewardship into execution.

3.16 Cross-Border Operations Without Foreign Sovereign Authority. The Corporation may engage in cross-border activities, collaborations, research, evidence-sharing, methods alignment, observability design, ontology coordination, public-good software development, public-safe publication, Academy activity, public authority learning, controlled-room participation, Nexus interface support, and other lawful public-benefit activities outside the United States where permitted by applicable law and approved under the Corporation’s records and compliance procedures.

Such cross-border operations shall not confer foreign sovereign authority, treaty status, intergovernmental status, diplomatic status, foreign regulator status, public warning authority, emergency command authority, public finance approval authority, public procurement authority, certification authority, finance-readiness authority, recognition authority, protocol authority, or enterprise execution authority.

Cross-border operations shall be subject to legal and safeguards review where they involve:

a) foreign public authorities;

b) Indigenous, Tribal, local, territorial, cultural, environmental, or protected knowledge;

c) personal data, public authority data, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, geospatial data, satellite data, AI data, model outputs, controlled technology, or sensitive compute;

d) export controls, sanctions, national security, controlled technology, dual-use technologies, defense-adjacent systems, AI-RAN, O-RAN, sovereign compute, DLT, DePIN, cyber, robotics, drones, sensing, geospatial systems, semiconductors, quantum-adjacent systems, or other sensitive technologies;

e) grants, donations, sponsorships, in-kind support, foreign funding, public funding, public finance readers, capital readers, investors, insurers, lenders, or development finance actors;

f) public-safe publications, dashboards, maps, reports, datasets, software, technical baselines, proof receipts, or public authority references; or

g) any activity that could create legal-identity ambiguity, public authority confusion, finance signaling, certification overclaim, procurement implication, provider preference, or sponsor control.

3.17 Local Law Respect in Canada, Mexico, Caribbean, Arctic, Indigenous, Cross-Border, and International Interfaces. In all Canada, Mexico, Caribbean, Arctic, Indigenous, cross-border, and international interfaces, the Corporation shall respect applicable local law, public authority competence, community protocols, Indigenous governance, data sovereignty, privacy, cybersecurity, export-control, sanctions, research ethics, protected knowledge, public safety, cultural, environmental, and human rights obligations.

The Corporation shall not represent that United States incorporation, United States governance seat, North America anchor status, Nexus alignment, technical authorship, public-good function, donor support, sponsor support, public authority participation, university collaboration, laboratory collaboration, or repository centrality permits it to disregard foreign law, local law, public authority protocols, Indigenous protocols, community safeguards, data localization requirements, consent requirements, public-safe mapping restrictions, protected knowledge restrictions, or cross-border transfer limits.

Where local law or protocol conflicts with proposed activity, the Corporation shall suspend, narrow, compartmentalize, localize, re-scope, route through a lawful local partner, refer to a competent authority, obtain legal review, or terminate the activity as appropriate. No cross-border ambition, Nexus alignment, donor expectation, sponsor expectation, public authority interest, technical urgency, operational convenience, or publication timeline shall override local law respect.

3.18 Records of Seat, Filings, Registered Agent, State Qualifications, Charitable Solicitation Registrations, and Foreign Registrations. The Corporation shall maintain complete and current records of its legal seat, state of incorporation or organization, registered office, registered agent, principal office, principal United States governance seat, corporate filings, annual reports, certificates of good standing, tax registrations, state qualifications, foreign qualifications, charitable solicitation registrations, fundraising registrations, employment registrations, lobbying registrations where applicable, public authority registrations where applicable, data protection registrations where applicable, and any foreign registrations or cross-border legal authorizations.

Such records shall include, as applicable:

a) jurisdiction;

b) filing authority;

c) filing date;

d) effective date;

e) renewal date;

f) responsible officer or custodian;

g) registered agent or local representative;

h) legal status;

i) tax status;

j) charitable solicitation status;

k) good-standing status;

l) permitted activities;

m) restricted activities;

n) reporting obligations;

o) renewal obligations;

p) public-facing name approved for use;

q) local-law conditions;

r) public authority conditions;

s) data, AI, cyber, privacy, sanctions, export-control, research, safeguards, or protected knowledge conditions;

t) suspension, lapse, correction, withdrawal, or termination status; and

u) repository location and evidence of filing.

No person shall represent that the Corporation is authorized, registered, qualified, tax-exempt, charitable, licensed, approved, certified, public authority endorsed, procurement-ready, finance-ready, legally operating, or formally present in any jurisdiction unless the relevant record supports that exact claim.

The governing rule of this Section is that the Corporation’s United States legal seat shall provide corporate-law clarity, not authority inflation. GCRI US may operate broadly and coordinate across North America where lawful, but its seat, offices, registered agent, filings, qualifications, and cross-border interfaces shall remain record-based, jurisdictionally bounded, non-executing, public-benefit aligned, and correctionable at all times.

Section 4. United States All-States-and-Territories Operating Posture

4.1 United States Operating Posture. The Corporation shall be capable of operating, coordinating, convening, publishing, researching, stewarding evidence, maintaining repositories, supporting public-good software, conducting public authority learning, engaging universities and laboratories, receiving lawful support, maintaining controlled rooms, supporting Nexus interfaces, and carrying out its nonprofit and public-benefit purposes across the United States, subject at all times to applicable federal law, the governing law of the state of incorporation or organization, the law of any state, territory, District of Columbia, Tribal-interface context, local jurisdiction, or other jurisdiction in which the Corporation operates, this Bylaw, the Certificate or Articles, Board-approved policies, and competent records.

The Corporation’s United States operating posture is national in reach but bounded in legal authority. It permits lawful public-benefit activity across the United States; it does not create federal authority, state authority, territorial authority, Tribal authority, local authority, emergency command authority, public warning authority, procurement authority, public finance authority, certification authority, recognition authority, finance-readiness authority, standards authority, protocol authority, or enterprise execution authority.

The Corporation may organize its United States activities through programs, projects, laboratories, public authority learning rooms, controlled rooms, evidence rooms, data rooms, public-safe publications, public-good software repositories, technical baselines, state or regional interface notes, Nexus Observatory methods, Nexus Universe activities, Academy activities, working groups, advisory bodies, fellowships, partnerships, grant activities, sponsorship-supported activities, and other lawful structures. No such activity shall create a separate legal entity, branch, public authority instrumentality, state office, territorial office, Tribal office, local government office, public-private partnership, procurement vehicle, regulated intermediary, national company, Project SPV, provider, operator, or execution vehicle unless separately and lawfully constituted and recorded.

4.2 All Fifty States. The Corporation may conduct lawful activities in or concerning all fifty states of the United States, including activities involving state public authorities, state universities, state laboratories, state agencies, local governments, utilities, ports, public health systems, emergency management bodies, public safety bodies, public works systems, infrastructure operators, communities, civil society, media, sponsors, hosts, providers, donors, funders, and research partners.

Before engaging in activity in any state that may trigger legal obligations, the Corporation shall review and, where required, complete state qualification, charitable solicitation registration, tax registration, employment registration, contractor compliance, grant compliance, public authority contracting review, lobbying registration, government ethics review, public records review, privacy review, cybersecurity review, AI-use review, procurement-integrity review, event permitting, data processing review, or other state-law compliance steps.

No state-facing activity shall imply that the Corporation has been adopted, endorsed, funded, approved, certified, retained, delegated, authorized, or preferred by a state government or state public authority unless the competent state authority has expressly and lawfully recorded the exact status and the Corporation’s records support the claim.

4.3 District of Columbia. The Corporation may conduct lawful activities in or concerning the District of Columbia, including federal-interface work, nonprofit engagement, university and research collaboration, public authority learning, policy-adjacent education, civil society engagement, public-safe publication, public-good technology coordination, and Nexus-compatible activities, subject to applicable District of Columbia law and any federal-law overlay.

District of Columbia activity shall not be used to imply federal endorsement, federal delegation, congressional approval, agency approval, public finance approval, grant approval, procurement approval, regulatory approval, lobbying authorization beyond lawful registration where required, or public authority status.

Where District of Columbia activity involves federal agencies, embassies, international organizations, development finance actors, capital readers, public authorities, public policy settings, government ethics-sensitive contexts, grant-funded activities, lobbying-sensitive communications, public procurement-sensitive communications, or public records-sensitive materials, the Corporation shall apply enhanced legal, compliance, public authority boundary, and public-safe claims review.

4.4 Puerto Rico. The Corporation may conduct lawful activities in or concerning Puerto Rico, including research, public authority learning, disaster resilience evidence, climate and energy systems evidence, water and food systems evidence, health and public safety learning, communications resilience, AI-RAN and telecommunications evidence, port and supply-chain evidence, community safeguards, and Nexus Observatory methods support, subject to applicable federal and Puerto Rico law.

No Puerto Rico-facing activity shall imply territorial government approval, emergency command authority, public warning authority, public finance approval, procurement approval, public-private partnership status, official adoption, or territorial mandate unless expressly and lawfully recorded.

The Corporation shall apply public-safe publication, language access, accessibility, community safeguards, disaster-sensitivity, infrastructure-sensitivity, data protection, and public authority capacity controls where Puerto Rico-facing activity involves communities, critical infrastructure, public health, energy, water, ports, telecommunications, disaster response, or government participation.

4.5 Guam. The Corporation may conduct lawful activities in or concerning Guam, including activities involving climate, disaster, energy, water, food, telecommunications, port, supply-chain, public health, public safety, cyber, infrastructure, geospatial, sensor, and public authority learning contexts, subject to applicable federal and Guam law.

Because Guam may involve strategic, defense-adjacent, Pacific, telecommunications, cyber, infrastructure, disaster, port, or national security-sensitive contexts, the Corporation shall apply enhanced review where activities involve controlled technology, export controls, sanctions, sensitive geospatial information, cyber-sensitive information, public authority data, infrastructure-sensitive data, military-adjacent settings, or public-safe mapping.

No Guam-facing activity shall imply federal authority, territorial authority, military authority, emergency authority, public warning authority, procurement authority, infrastructure operating authority, or public finance authority unless the competent authority has expressly and lawfully recorded that status.

4.6 U.S. Virgin Islands. The Corporation may conduct lawful activities in or concerning the U.S. Virgin Islands, including activities involving climate resilience, disaster resilience, energy, water, food, health, ports, tourism-related systems, public infrastructure, telecommunications, public authority learning, observability methods, public-safe publication, and community safeguards, subject to applicable federal and territorial law.

The Corporation shall treat U.S. Virgin Islands-facing activity as jurisdictionally specific and shall review territorial registration, charitable solicitation, tax, public authority, privacy, cybersecurity, grant, contracting, public-safe communication, community safeguards, and disaster-sensitive publication requirements where applicable.

No activity in or concerning the U.S. Virgin Islands shall be represented as territorial endorsement, public authority adoption, emergency readiness, public warning authority, procurement approval, public finance approval, provider preference, certification, or recognition unless supported by competent records.

4.7 American Samoa. The Corporation may conduct lawful activities in or concerning American Samoa, including public-benefit research, community safeguards, climate and disaster evidence, telecommunications resilience, energy and water systems evidence, public health learning, geospatial methods, public authority learning, and Nexus-compatible observability methods, subject to applicable federal, territorial, local, cultural, community, and legal requirements.

The Corporation shall apply heightened respect for local governance, cultural context, community protocols, language access, accessibility, public-safe mapping, protected knowledge, data minimization, and public authority capacity classification in American Samoa-facing activities.

No American Samoa-facing activity shall imply territorial authority, local authority, public authority delegation, cultural consent, community consent, emergency command, public warning, procurement authority, public finance approval, or official adoption unless expressly and lawfully recorded.

4.8 Northern Mariana Islands. The Corporation may conduct lawful activities in or concerning the Commonwealth of the Northern Mariana Islands, including activities involving climate and disaster systems, energy, water, food, ports, telecommunications, public health, public safety, cyber, infrastructure, geospatial, public authority learning, and community safeguards, subject to applicable federal and Commonwealth law.

The Corporation shall conduct legal, safeguards, public authority, data, cybersecurity, public-safe publication, and local-context review before activities that may affect sensitive infrastructure, public authorities, communities, protected knowledge, public safety, public health, climate resilience, disaster response, or strategic systems.

No Northern Mariana Islands-facing activity shall imply Commonwealth approval, federal approval, emergency command, public warning, public finance approval, procurement approval, provider preference, certification, recognition, or official adoption unless supported by competent records.

4.9 Tribal Nations and Indigenous Governments Where Lawfully and Respectfully Engaged. The Corporation may engage with Tribal Nations, Indigenous governments, Indigenous communities, Indigenous organizations, Indigenous knowledge holders, and Tribal or Indigenous public authority interfaces only where lawful, respectful, capacity-classified, safeguard-governed, and record-supported.

Such engagement shall respect sovereignty, self-determination, applicable law, federal Indian law where applicable, Tribal law where applicable, Indigenous data governance, cultural protocols, community protocols, consent and non-consent pathways, protected knowledge, local knowledge, territorial knowledge, culturally sensitive knowledge, environmental knowledge, sacred-site sensitivity, public-safe mapping restrictions, attribution rules, withdrawal pathways, correction pathways, grievance pathways, non-retaliation, and do-no-harm obligations.

No Tribal or Indigenous participation, consultation, contribution, data sharing, site participation, public authority learning participation, public-safe publication review, controlled-room participation, observatory methods activity, Nexus interface activity, or public statement shall be represented as consent, endorsement, delegation, adoption, authority transfer, public authority approval, procurement approval, public finance approval, certification, recognition, finance-readiness, or public-private partnership unless the competent Tribal or Indigenous authority or relevant rights-holder has expressly and lawfully recorded the exact status.

Where there is uncertainty concerning Tribal or Indigenous status, authority, representation, consent, protected knowledge, data rights, publication safety, or public meaning, the Corporation shall apply the most protective lawful posture and shall suspend, narrow, localize, re-scope, or decline the activity pending appropriate review.

4.10 Federal Public Authority Interfaces. The Corporation may interface with federal departments, agencies, offices, laboratories, commissions, authorities, instrumentalities, public finance entities, emergency management bodies, public health bodies, public safety bodies, infrastructure bodies, research bodies, procurement-related bodies, regulator-listening participants, and other federal public-sector actors for public-benefit research, evidence literacy, technical literacy, public authority learning, scenario learning, public-safe communication, methods review, observability methods, data governance learning, AI governance learning, cybersecurity learning, and other lawful non-executing purposes.

Federal public authority participation shall be capacity-classified before public meaning is created. The Corporation shall distinguish, as applicable, among official-capacity participation, observer participation, regulator-listening participation, public finance reader participation, emergency-management learning participation, public infrastructure operator participation, technical contributor participation, data contributor participation, reviewer participation, controlled-room participation, and personal-capacity participation.

Federal participation shall not imply federal endorsement, federal adoption, regulatory approval, procurement approval, grant approval, public finance approval, sovereign obligation, statutory certification, emergency command authority, public warning authority, public-private partnership, data permission, official use, or public authority delegation unless expressly and lawfully recorded by competent federal authority.

4.11 State Public Authority Interfaces. The Corporation may interface with state public authorities, including governors’ offices, state agencies, state emergency management bodies, state public health bodies, state public safety bodies, state energy, water, food, environment, transportation, telecommunications, cyber, infrastructure, finance, insurance, economic development, research, university, and regulatory bodies, for lawful public-benefit purposes.

State public authority interfaces shall be governed by capacity classification, public authority reference controls, data contribution controls, public-safe publication controls, procurement neutrality, lobbying and government ethics review where applicable, grant compliance review where applicable, and state-law compliance.

No state public authority interface shall create state mandate, state adoption, state procurement approval, state public finance approval, state emergency authority, state public warning authority, state regulatory approval, state certification, state funding commitment, state public-private partnership, state provider preference, or state endorsement unless expressly and lawfully recorded.

4.12 Territorial Public Authority Interfaces. The Corporation may interface with territorial public authorities in Puerto Rico, Guam, the U.S. Virgin Islands, American Samoa, the Northern Mariana Islands, and any other United States territorial or insular context where lawful and appropriate.

Territorial public authority interfaces shall be treated as jurisdictionally specific, with attention to local law, federal law, public authority capacity, language access, accessibility, community safeguards, climate and disaster sensitivity, infrastructure sensitivity, public-safe mapping, data governance, cybersecurity, public finance, procurement, and public authority reference controls.

No territorial interface shall create territorial authority, emergency command authority, public warning authority, procurement approval, public finance approval, official adoption, public-private partnership, certification, recognition, provider preference, or legal mandate unless expressly and lawfully recorded.

4.13 Tribal Public Authority Interfaces. The Corporation may interface with Tribal public authorities, Indigenous governmental authorities, Tribal agencies, Tribal utilities, Tribal colleges and universities, Tribal emergency management bodies, Tribal health bodies, Tribal public safety bodies, Tribal infrastructure bodies, and other Tribal or Indigenous governance institutions where lawful, invited, appropriate, and safeguard-governed.

Each Tribal public authority interface shall identify the relevant capacity, authority, jurisdiction, consent or non-consent posture, data governance requirements, protected knowledge restrictions, publication rules, public-safe mapping limits, records custodian, and correction pathway.

No Tribal public authority interface shall imply delegation, consent, endorsement, public authority adoption, data permission, protected knowledge permission, public finance approval, procurement approval, certification, recognition, public warning authority, emergency command authority, or public-private partnership unless expressly and lawfully recorded by the competent Tribal or Indigenous authority and accepted by the Corporation within its non-executing role.

4.14 Local, County, Municipal, Metropolitan, Port, Utility, Public Health, Emergency Management, Public Safety, Public Works, Water, Energy, Food, Telecom, Cyber, and Infrastructure Interfaces. The Corporation may lawfully engage with local, county, municipal, metropolitan, port, utility, public health, emergency management, public safety, public works, water, energy, food, telecommunications, cyber, infrastructure, transportation, housing, environmental, resilience, and public-service bodies for evidence, methods, observability, technical literacy, public-safe reporting literacy, scenario learning, public-good technology, and systemic-risk learning purposes.

Such interfaces shall be structured to support public authority learning and evidence discipline without public authority substitution. The Corporation may support scenario design, tabletop learning, after-action evidence methods, public-safe technical explanation, observability methods, data governance literacy, AI governance literacy, cyber hygiene learning, public-good technical baselines, and controlled-room evidence review where lawful.

No local or infrastructure-facing activity shall constitute emergency command, incident command, dispatch, evacuation instruction, public warning, utility operating authority, infrastructure operating authority, public health order, public safety command, procurement recommendation, public finance approval, regulatory approval, certification, provider selection, or public authority decision.

Where local or infrastructure-facing activity involves sensitive infrastructure, cyber vulnerabilities, public safety, health data, utility operations, emergency response, community mapping, protected knowledge, or public-safe communication, the Corporation shall apply heightened security, confidentiality, classification, and publication controls.

4.15 Interstate and Interjurisdictional Systems. The Corporation may support evidence, methods, observability, ontology, public-good software, technical baselines, and public authority learning concerning interstate and interjurisdictional systems, including watersheds, energy grids, telecommunications networks, ports, supply chains, transportation corridors, cyber systems, public health systems, climate and disaster corridors, wildfire and flood systems, air quality systems, food systems, emergency management mutual aid contexts, cross-state infrastructure, and multi-state public authority learning.

Interstate or interjurisdictional activity shall not create authority over any participating state, territory, Tribal Nation, public authority, utility, operator, sponsor, provider, host, or community. It shall not create interstate compact authority, mutual aid authority, emergency authority, public warning authority, procurement authority, regulatory authority, public finance authority, or standards authority unless separately and lawfully constituted by competent authorities.

Where interstate activity involves multiple public authorities or public-sector actors, the Corporation shall classify the capacity of each participant, identify the relevant legal and data boundaries, maintain public-safe claims discipline, and preserve separate records for roles, authorities, data rights, publication rights, limitations, and correction pathways.

4.16 Cross-Border North America Systems. The Corporation may support evidence, methods, observability, ontology, public-good software, technical baselines, and public authority learning concerning cross-border North America systems where lawful, including Canada–United States, United States–Mexico, Arctic, Great Lakes, Pacific, Atlantic, Gulf, Caribbean, border, supply-chain, port, energy, water, food, telecommunications, cyber, climate, disaster, public health, biodiversity, Indigenous, and regional Nexus contexts.

Cross-border North America work shall be conducted in coordination with appropriate legal, institutional, public authority, community, Indigenous, data, AI, cyber, privacy, export-control, sanctions, controlled-technology, public-safe publication, and safeguards review. Coordination with GCRI Canada, Mexico-facing interfaces, Caribbean interfaces, regional Nexus bodies, public authorities, universities, laboratories, communities, hosts, sponsors, providers, or other partners shall not create merger, agency, parent-subsidiary status, alter ego status, shared treasury, shared liability, foreign public authority status, treaty status, intergovernmental status, public finance authority, emergency authority, procurement authority, certification authority, finance-readiness authority, recognition authority, or enterprise execution authority.

Cross-border work shall preserve the rule that GCRI US may support North America evidence and methods alignment, but it shall not speak for foreign authorities, bind foreign partners, override local law, determine public finance, approve projects, issue warnings, certify systems, or execute infrastructure.

4.17 State Qualification, Registration, Charitable Solicitation, Tax, Employment, Privacy, Public Records, Procurement, Lobbying, Grant, and Contracting Review Where Applicable. Before operating, soliciting, hiring, contracting, collecting fees, accepting funds, hosting events, conducting public authority learning, maintaining controlled rooms, processing data, issuing public materials, engaging in grant activity, or forming state-, territorial-, Tribal-, local-, or cross-border interfaces, the Corporation shall determine whether legal review, registration, qualification, filing, approval, notice, or compliance controls are required.

The Corporation shall review, as applicable:

a) foreign qualification to do business or conduct nonprofit activity;

b) charitable solicitation registration or exemption;

c) state and local tax registration, sales tax, franchise tax, use tax, employment tax, and unrelated business income considerations;

d) federal and state tax-exempt or tax-exempt-compatible requirements;

e) employment, contractor, volunteer, fellow, workplace, workers’ compensation, unemployment insurance, wage and hour, and workplace safety requirements;

f) public authority contracting, grant, procurement-integrity, government ethics, gifts, lobbying, political activity, and public records obligations;

g) privacy, data protection, cybersecurity, AI governance, health data, youth data, public-sector data, cyber-sensitive data, infrastructure-sensitive data, and controlled-room obligations;

h) export controls, sanctions, controlled technology, national security-sensitive, dual-use, geospatial, satellite, AI-RAN, O-RAN, DePIN, DLT, cyber, robotics, drone, semiconductor, quantum-adjacent, and compute-sensitive requirements;

i) civil rights, accessibility, language access, disability access, nondiscrimination, community safeguards, Indigenous knowledge, Tribal protocol, and protected knowledge requirements;

j) insurance, indemnification, liability, safety, event, facility, host-site, and fieldwork requirements; and

k) contract, grant, sponsorship, donation, in-kind support, data-sharing, IP, public-good software, repository, and publication obligations.

Where review identifies uncertainty, the Corporation shall apply the most protective lawful posture and shall suspend, narrow, re-scope, localize, or delay the activity until the relevant authority, filing, registration, exemption, approval, or risk treatment is recorded.

4.18 No Assumption of Authority in Any State, Territory, Tribal Jurisdiction, or Public Authority Context Without Record. The Corporation shall not assume, imply, represent, accept, or exercise authority in any state, territory, District of Columbia, Tribal jurisdiction, local jurisdiction, public authority context, public institution, public infrastructure context, public finance context, public procurement context, emergency management context, public health context, public safety context, utility context, port context, or regulated context unless the authority is expressly lawful, within the Corporation’s non-executing purpose, and recorded by competent authority.

No title, role, public authority relationship, participation, meeting, letter of support, memorandum, data contribution, public statement, shared logo, event, dashboard, controlled room, repository, proof receipt, public-safe publication, whitepaper, benchmark, public authority learning session, Nexus Universe activity, Nexus Observatory output, Nexus Standards input, Docket input, Grid input, or finance-readiness evidence input shall create authority by implication.

Where authority is ambiguous, the narrower and less authority-conferring interpretation shall apply. The Corporation shall not rely on operational convenience, urgency, public authority interest, sponsor pressure, provider request, technical capacity, emergency context, community need, media attention, or Nexus alignment as a substitute for lawful authority and competent records.

4.19 State and Territorial Localization Without Fragmentation. The Corporation may adopt state-specific, territorial-specific, District of Columbia-specific, Tribal-interface-specific, local-specific, sector-specific, or public authority-specific procedures, notices, templates, public-safe summaries, interface terms, controlled vocabulary notes, compliance schedules, registration records, data handling schedules, public authority protocols, grant compliance addenda, or operating practices to comply with applicable law and local context.

Localization shall be used to make the Corporation lawful, legible, accessible, and safe in specific jurisdictions. Localization shall not create a separate Corporation, separate mission, separate treasury, separate governance system, undisclosed bylaw, competing authority, state franchise, territorial franchise, public authority office, procurement arm, finance arm, certification arm, recognition arm, public warning arm, emergency command arm, national company, Project SPV, provider, or enterprise execution vehicle.

No localization shall weaken:

a) the Corporation’s official legal identity;

b) United States seat discipline;

c) nonprofit and non-distribution character;

d) public-benefit purpose;

e) public-good stewardship burden;

f) non-execution perimeter;

g) GCRI / GRF / GRA role separation;

h) public-good stack and enterprise stack separation;

i) public authority boundary;

j) finance, securities, insurance, lending, rating, public finance, procurement, and certification boundaries;

k) provider neutrality;

l) sponsor, donor, and funder non-control;

m) data, AI, cyber, privacy, and secure computing controls;

n) community, Tribal, Indigenous, local, territorial, protected knowledge, civil rights, accessibility, and public-safe mapping safeguards;

o) competition, sanctions, export-control, controlled-technology, and professional boundary controls;

p) validity-by-record; or

q) correctionability.

Where localization creates divergence from general Corporation practice, the Corporation shall maintain compatibility notes, divergence logs, supersession records, public-safe explanatory notes where appropriate, and correction paths.

4.20 U.S. Operating Posture Records. The Corporation shall maintain records sufficient to evidence its United States all-states-and-territories operating posture, including records of jurisdictions in which it operates, registers, qualifies, solicits, hires, contracts, holds events, processes data, engages public authorities, accepts support, hosts controlled rooms, issues public materials, conducts research, or maintains active program interfaces.

Such records shall include, as applicable:

a) state, District of Columbia, territorial, Tribal-interface, local, and cross-border activity maps;

b) state qualification records;

c) charitable solicitation registrations, exemptions, renewal dates, and filing records;

d) tax registrations and tax-review records;

e) employment and contractor compliance records;

f) public authority capacity records;

g) grant, contract, procurement-integrity, lobbying, political activity, government ethics, and public records review records;

h) privacy, data, AI, cybersecurity, health data, youth data, infrastructure-sensitive data, cyber-sensitive data, and controlled-room records;

i) sanctions, export-control, controlled-technology, national security-sensitive, dual-use, and sensitive technology review records;

j) civil rights, accessibility, language access, community safeguards, Tribal and Indigenous protocol, protected knowledge, and public-safe mapping records;

k) public-safe publication, dashboard, map, report, dataset, software release, repository, and technical baseline jurisdictional review records;

l) sponsor, donor, funder, host, provider, university, laboratory, community, civil society, and media interface records;

m) GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortium, national company, Project SPV, and qualified provider interface records where relevant;

n) localization instruments, compatibility notes, divergence logs, and correction records; and

o) records of suspension, withdrawal, correction, termination, or re-scoping of activities where jurisdictional, legal, public authority, finance, certification, procurement, data, AI, cyber, safeguards, or public-safe risks require action.

The governing rule of this Section is that GCRI US may operate nationally and coordinate across all United States states, territories, Tribal-interface contexts, local systems, and North America-facing systems where lawful, but every such activity shall remain jurisdictionally bounded, non-executing, public-benefit aligned, public-safe where published, provider-neutral, sponsor-independent, validity-by-record based, and correctionable.

Section 5. North America Anchor Role

5.1 North America Anchor Purpose. The Corporation may serve as a bounded North America anchor for the GCRI public-good function, provided that such role is lawful, record-supported, consistent with the Corporation’s United States legal personality, and limited to evidence, methods, observability, ontology, technical truth, public-good R&D, open technology, public-good software, open technical baselines, verifiable compute, verifiable intelligence, research integrity, public authority learning, safeguards, and Nexus public-good stack alignment.

The North America anchor role is intended to provide continuity, coherence, and public-benefit discipline for cross-border evidence architecture and methods alignment across United States-facing and North America-facing systemic-risk domains. It shall support lawful coordination among United States, Canadian, Mexico-facing, Caribbean, Arctic, Great Lakes, Pacific, Atlantic, Gulf, border, Indigenous, university, laboratory, public authority, civil society, community, and Nexus interfaces where appropriate and record-supported.

The North America anchor role shall be interpreted as a stewardship role, not an ownership role; as an evidence and methods role, not a recognition role; as an observability and technical-baseline role, not a public warning or emergency command role; as a public authority learning role, not a public authority delegation; and as a Nexus public-good compatibility role, not an enterprise execution, finance-readiness, procurement, certification, or regulated-market role.

No statement, document, public communication, grant narrative, sponsorship material, public authority briefing, repository label, technical baseline, dashboard, map, proof receipt, AI output, Nexus reference, or cross-border convening shall describe the Corporation’s North America anchor role in a manner that expands the Corporation beyond its lawful authority, nonprofit character, non-execution perimeter, public authority boundary, finance boundary, certification boundary, procurement neutrality, provider neutrality, sponsor non-control, legal separateness, validity-by-record discipline, or correctionability.

5.2 GCRI US as United States Anchor of the GCRI Evidence, Methods, Observability, Ontology, Technical Truth, Public-Good R&D, Open Technology, and Public-Good Software Function. The Corporation shall serve as the United States anchor of the GCRI evidence, methods, observability, ontology, technical truth, public-good R&D, open technology, public-good software, open technical baseline, verifiable compute, verifiable intelligence, research-integrity, and public authority learning function.

As United States anchor, the Corporation may develop, maintain, review, publish, correct, and preserve public-good evidence architectures, methods libraries, observability models, ontology and controlled vocabulary systems, technical truth methods, public-good R&D outputs, public-good software, open technical baselines, technical schemas, reference architectures, test harnesses, data dictionaries, confidence and uncertainty frameworks, public-safe technical summaries, and public authority learning materials, subject to applicable law and this Bylaw.

The United States anchor function may include work concerning artificial intelligence, AI-RAN, O-RAN, private wireless, telecommunications, sovereign compute, high-performance compute, edge compute, confidential computing, cybersecurity, blockchain, distributed ledger technology, Web3, DePIN, proof systems, quantum-relevant systems, robotics, drones, sensing, Earth observation, geospatial systems, digital twins, biosecurity, climate, nature, biodiversity, water, energy, food, health, disaster, ports, supply chains, advanced manufacturing, semiconductors, public infrastructure, critical services, and other exponential, convergent, or mission-critical systems.

The United States anchor function shall not cause the Corporation to become the whole of GCRI, GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Standards, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, any consortium, any National Consortium Company, any Project SPV, any Qualified Enterprise Provider, any sponsor, any host, any public authority, any university, any laboratory, or any enterprise execution actor.

The Corporation’s anchor function shall remain upstream, non-executing, public-benefit oriented, record-based, and correctionable. It may support downstream recognition, maturity, finance-readiness, public authority learning, standards support, Docket evidence, Grid maturity, and enterprise delivery only through lawful evidence, methods, observability, ontology, technical baseline, and correction inputs, and not through direct exercise of the downstream functions themselves.

5.3 GCRI US as North America Anchor for Cross-Border Evidence Architecture Where Lawful. The Corporation may act as a North America anchor for cross-border evidence architecture where such activity is lawful, properly recorded, safeguard-governed, and consistent with the Corporation’s United States legal seat and nonprofit public-benefit purpose.

Cross-border evidence architecture may include shared evidence classifications, source-lineage practices, provenance methods, confidence methods, uncertainty methods, sensor-fusion methods, AI-output review methods, observability schemas, public-safe reporting methods, public authority capacity semantics, data-protection controls, cyber-sensitive handling rules, protected-knowledge safeguards, and correction pathways for North America-relevant systems.

The Corporation may support cross-border evidence architecture concerning hazards, infrastructure, climate, cyber, public health, energy, water, food, biodiversity, telecommunications, AI-RAN, O-RAN, DePIN, ports, supply chains, borders, wildfire, flood, drought, heat, Arctic systems, Great Lakes systems, coastal systems, island systems, remote communities, Indigenous territories, and other systemic-risk contexts.

No cross-border evidence architecture shall be treated as a treaty instrument, intergovernmental instrument, public authority decision, legal standard, public warning, emergency command, certification, recognition, finance-readiness determination, procurement approval, regulatory approval, public finance approval, or investment basis unless a competent authority separately and lawfully records such status outside the Corporation’s non-executing role.

Where cross-border evidence work involves foreign law, public authority data, Indigenous data, protected knowledge, cyber-sensitive information, infrastructure-sensitive information, health-sensitive data, export-controlled technology, sanctions-sensitive contexts, controlled technology, national security-sensitive contexts, public-safe mapping, or community-sensitive publication, the Corporation shall apply heightened legal, data, AI, cyber, safeguards, public-safe, and local-law review.

5.4 Coordination With GCRI Canada. The Corporation may coordinate with GCRI Canada as a separate Canadian public-benefit anchor within the GCRI family. Such coordination may include evidence architecture, methods alignment, observability models, ontology, controlled vocabulary, public-good software, open technical baselines, public-good R&D, verifiable compute, verifiable intelligence, Nexus Truth Engine methods, Nexus Observatory methods, public authority learning, safeguards, public-safe publication, correction pathways, and technical memory.

Coordination with GCRI Canada shall preserve separate legal personality, separate boards, separate fiduciary duties, separate treasuries, separate tax posture, separate records, separate employment and contractor relationships, separate authority to bind, separate public authority interfaces, separate data compliance obligations, separate liability, and separate domestic law obligations.

The governing rule for coordination with GCRI Canada shall be: one mission family, shared doctrine where appropriate, interoperable evidence and methods where lawful, separate legal anchors, separate corporate governance, separate fiduciary obligations, separate compliance, separate records, separate treasuries, separate authority, and no legal fusion.

No shared director, officer, advisor, fellow, contractor, employee, repository, dataset, public-good software asset, technical baseline, event, publication, funder, sponsor, donor, public authority participant, host, university, laboratory, controlled room, working group, Nexus interface, or public statement shall create agency, partnership, joint venture, branch status, parent-subsidiary status, common treasury, alter ego status, joint employer status, single employer status, shared liability, or authority to bind unless expressly and lawfully recorded.

Where GCRI US and GCRI Canada coordinate on North America matters, each institution’s capacity, contribution, authority, records, data rights, publication rights, public authority interface, public-safe limitations, correction path, and legal boundary shall be identified where needed to avoid confusion.

5.5 Coordination With Mexico, Caribbean, Arctic, Great Lakes, Pacific, Atlantic, Gulf, Border, and Regional Nexus Interfaces Where Lawfully Structured. The Corporation may coordinate with Mexico-facing, Caribbean-facing, Arctic, Great Lakes, Pacific, Atlantic, Gulf, border-region, Indigenous, regional Nexus, university, laboratory, public authority, civil society, community, host, sponsor, provider, and public-interest interfaces where such coordination is lawful, respectful, record-supported, and consistent with this Bylaw.

Such coordination may support evidence alignment, hazard mapping methods, public-safe observability models, public-good software, technical baselines, cross-border learning, data governance practices, public authority learning, scenario learning, systemic-risk review, research collaboration, safeguards, and correction pathways.

Coordination shall not create foreign legal presence, foreign public authority status, treaty authority, regional regulator status, cross-border procurement authority, public finance authority, public warning authority, emergency command authority, certification authority, recognition authority, finance-readiness authority, protocol authority, enterprise execution authority, or control over any foreign, regional, public authority, Indigenous, community, provider, host, sponsor, university, laboratory, national company, Project SPV, or Nexus entity.

Each coordination interface shall be classified by jurisdiction, role, legal capacity, public authority status where any, data posture, safeguards posture, publication posture, technical scope, permitted uses, restricted uses, correction pathway, and responsible record custodian where material.

Where coordination involves Mexico, the Caribbean, Arctic systems, Indigenous territories, border regions, or other sensitive cross-border settings, the Corporation shall respect local law, public authority competence, Indigenous governance, community protocols, protected knowledge, cultural context, public-safe mapping, privacy, cybersecurity, export-control, sanctions, controlled-technology, and public safety obligations.

5.6 North America Hazard, Infrastructure, Climate, Cyber, Public Health, Energy, Water, Food, Biodiversity, Telecom, Supply Chain, Disaster, Port, Border, and Systemic Risk Evidence Support. The Corporation may provide North America evidence support for systemic-risk domains that affect public safety, public welfare, resilience, infrastructure continuity, public trust, public authority learning, community safeguards, and mission-critical systems.

Such evidence support may include evidence frameworks, risk typologies, source-lineage methods, sensor and data interpretation methods, geospatial methods, cyber evidence methods, AI-assisted evidence review rules, observability indicators, resilience indicators, degraded-mode indicators, public-safe reporting methods, dashboard governance, data-card templates, model-card templates, system-card templates, incident-learning methods, and correction processes.

The domains for North America evidence support may include, without limitation:

a) climate hazards, wildfire, flood, drought, heat, storms, coastal risk, Arctic risk, and compound disasters;

b) energy, water, food, health, biodiversity, nature, built environment, public works, utilities, ports, transportation, and supply chains;

c) cyber systems, telecommunications, AI-RAN, O-RAN, private wireless, satellite systems, non-terrestrial networks, public safety communications, edge compute, sovereign compute, and critical digital infrastructure;

d) public health, emergency management, public safety, hospitals, remote communities, Indigenous communities, border systems, and island systems;

e) geospatial, Earth observation, sensing, drones, robotics, digital twins, data platforms, AI systems, DePIN, DLT, blockchain, and proof-receipt systems; and

f) cross-sector, cascading, convergent, and compounding systemic-risk conditions.

The Corporation shall not convert hazard, infrastructure, climate, cyber, public health, energy, water, food, biodiversity, telecom, supply-chain, disaster, port, border, or systemic-risk evidence support into public warning, public health order, emergency command, incident command, public authority decision, procurement recommendation, regulated advice, certification, recognition, finance-readiness, rating, or public finance approval.

5.7 North America Public Authority Learning Support Without Public Authority Delegation. The Corporation may provide public authority learning support to federal, state, territorial, District of Columbia, Tribal, Indigenous, local, municipal, county, port, utility, public health, emergency management, public safety, public works, infrastructure, telecom, water, energy, food, cyber, university, laboratory, public finance reader, regulator-listening, and cross-border public-sector participants where lawful and properly classified.

Public authority learning support may include evidence literacy, technical literacy, AI governance literacy, cyber literacy, public-safe reporting literacy, scenario learning, tabletop learning, simulation support, after-action evidence methods, observability method explanation, data governance learning, technical-baseline learning, public-good software demonstration, and controlled-room learning.

Every public authority learning interface shall be capacity-classified before public meaning is created. The Corporation shall distinguish official-capacity participation, observer participation, personal-capacity participation, regulator-listening participation, public finance reader participation, emergency-management participant participation, technical contributor participation, public infrastructure operator participation, simulation participant participation, data contributor participation, and public authority room participation.

Public authority learning support shall not constitute public authority delegation, public warning, emergency command, incident command, dispatch, evacuation instruction, public health order, public safety command, regulatory approval, procurement approval, public finance approval, grant approval, funding commitment, official adoption, sovereign obligation, public-private partnership, certification, recognition, finance-readiness, or legal mandate.

Where any public authority participant, document, meeting, dashboard, public-safe publication, repository, proof receipt, controlled-room record, or Nexus reference could create public authority confusion, the Corporation shall apply clarifying language, capacity records, non-reliance language, public-safe limitations, and correction pathways.

5.8 North America Observatory Methods Support. The Corporation may support North America observability methods for Nexus Observatory, Nexus Observatory Nodes, Nexus Hubs, Nexus Clusters, Nexus Hotspots, Regional Clusters, National Dense Nexus Cores, state interfaces, territorial interfaces, Tribal and Indigenous interfaces, metropolitan interfaces, sectoral interfaces, public authority learning environments, host sites, and other lawful observability contexts.

Observatory methods support may include guidance for evidence intake, source lineage, provenance, signal classification, sensor-fusion methods, AI-output review, edge-compute records, AI-RAN and O-RAN signal interpretation, DePIN and DLT record interpretation, digital twin assumptions, geospatial methods, dashboard limitations, degraded-mode awareness, resilience indicators, public-safe mapping, access controls, correction triggers, and observability record retention.

North America Observatory methods shall be designed to improve evidence quality, interpretability, safety, comparability, public authority learning, and correctionability. They shall not transform GCRI US into an operator of public infrastructure, emergency command body, public warning center, regulator, procurement authority, certification authority, finance-readiness authority, public authority, or provider.

No Observatory method, dashboard, sensor signal, AI-RAN signal, DePIN record, blockchain entry, proof receipt, digital twin output, model output, score, map, or alerting artifact shall be treated as final authority, public warning, public authority decision, certification, recognition, finance-readiness, procurement approval, rating, or emergency instruction unless separately and lawfully authorized by competent authority outside the Corporation’s default role.

5.9 North America Data, AI, Cyber, Sovereign Compute, and Cross-Border Safeguards Support. The Corporation may support North America data, AI, cyber, sovereign compute, verifiable compute, verifiable intelligence, and cross-border safeguards methods where lawful and consistent with its public-benefit purpose.

Such support may include data classification methods, privacy-preserving data practices, data minimization, de-identification, aggregation, public authority data handling, health-sensitive data handling, cyber-sensitive data handling, infrastructure-sensitive data handling, Indigenous data safeguards, protected knowledge controls, model registers, inference records, compute workload records, secure enclave methods, confidential computing methods, compute-to-data methods, cross-border transfer review, AI-use restrictions, cybersecurity baselines, secure release practices, identity and access controls, logging, monitoring, incident response, and correction pathways.

The Corporation shall apply heightened safeguards where North America-facing activities involve rights-bearing data, youth data, health data, public-sector data, Indigenous data, Tribal data, community-protected data, cyber-sensitive information, infrastructure-sensitive information, geospatial information, satellite information, AI-RAN systems, O-RAN systems, DePIN systems, DLT systems, sovereign compute, controlled technology, export controls, sanctions, national security-sensitive systems, or public-safe mapping.

No data, AI, cyber, compute, model, dashboard, digital twin, proof receipt, or automated output shall become institutional authority by technical operation alone. Material outputs shall require record support, classification, limitation, human review where required, public-safe review where published, and correctionability.

5.10 North America Public-Good Software and Technical Baseline Support. The Corporation may develop, maintain, publish, license, restrict, correct, deprecate, retire, or archive public-good software, open technology, schemas, APIs, SDKs, dashboards, reference architectures, data dictionaries, technical profiles, test harnesses, gold vectors, negative tests, benchmark libraries, interoperability profiles, model cards, system cards, dataset cards, and open technical baselines for North America-facing evidence, methods, observability, ontology, technical truth, public authority learning, safeguards, and Nexus compatibility purposes.

Public-good software and technical baseline support shall be governed by secure development, repository discipline, contributor governance, IP chain-of-title review, licensing review, data rights review, AI-use review, cybersecurity review, export-control review, sanctions review, controlled-technology review, public-safe publication review, and anti-enclosure controls where applicable.

The Corporation may support open use, public-interest use, academic use, public authority learning use, community use, and Nexus-compatible use of public-good software and technical baselines, subject to lawful licenses, restrictions, access controls, disclaimers, safeguards, public-safe limitations, and correction requirements.

No public-good software, technical baseline, repository, reference implementation, schema, API, dashboard, benchmark, test harness, proof-receipt logic, role-key logic, ledger logic, smart-license logic, or compatibility profile shall constitute certification, standards approval, legal compliance approval, procurement approval, provider preference, public authority decision, finance-readiness, recognition, public warning, emergency command, or protocol authority by default.

Where the Corporation’s public-good software or technical baseline is used by GRF, GRA, Nexus Standards, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, a consortium, a National Consortium Company, a Project SPV, a provider, a sponsor, a host, a university, a laboratory, a public authority, or an enterprise actor, the Corporation’s role shall remain as recorded and shall not be expanded by downstream reliance, technical centrality, market uptake, public authority familiarity, or Nexus alignment.

5.11 North America Nexus Universe, Nexus Observatory, Nexus Standards, Nexus Grid, Nexus Rails, Nexus Academy, and Nexus Competence Cell Alignment Support. The Corporation may support alignment among North America-facing Nexus Universe, Nexus Observatory, Nexus Standards, Nexus Grid, Nexus Rails, Nexus Academy, Nexus Competence Cells, Nexus Risk Management, Nexus Network, consortium interfaces, public authority learning environments, host sites, universities, laboratories, communities, and enterprise-facing public-good interfaces.

Such alignment support may include evidence and methods inputs, technical baseline inputs, ontology and controlled vocabulary inputs, observability methods, public authority learning materials, Academy learning content, competence-cell materials, public-safe reporting methods, safeguards guidance, data and AI governance methods, cyber baseline methods, Docket evidence support, Grid maturity evidence support, and correction signals.

The Corporation shall not, through alignment support, become Nexus Standards, protocol authority, certification authority, recognition authority, finance-readiness authority, public authority, public finance authority, procurement authority, emergency command body, public warning authority, Nexus Grid admitting authority, Nexus Docket approving authority, Nexus Rails execution authority, Nexus Universe operator of record, Academy credentialing authority by default, National Consortium Company, Project SPV, Qualified Enterprise Provider, or enterprise execution actor.

Alignment support shall preserve the role-separation rule: GCRI US may produce and steward evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, and open technical baselines; GRF may steward registry, recognition, maturity records, standing, claims discipline, stakeholder formation, public-safe reporting, and public-facing legitimacy; GRA may steward finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence translation, RNFD, NFD, UNFSD, capital-reader rooms, and regulated-perimeter discipline; and enterprise stack actors may execute projects only within their own lawful authority.

5.12 No North America Sovereign Authority. The Corporation’s North America anchor role shall not confer sovereign authority, quasi-sovereign authority, treaty authority, intergovernmental authority, diplomatic authority, supranational authority, regional regulator status, federal authority, state authority, territorial authority, Tribal authority, Indigenous governance authority, local authority, public authority status, emergency authority, public warning authority, public finance authority, procurement authority, certification authority, recognition authority, finance-readiness authority, standards authority, protocol authority, or enterprise execution authority.

The Corporation shall not represent itself as speaking for North America, the United States, Canada, Mexico, the Caribbean, the Arctic, any border region, any Indigenous people, any Tribal Nation, any public authority, any regional body, any public finance body, any Nexus body, any consortium, any community, any provider, any host, any sponsor, or any enterprise actor unless a competent written record authorizes the exact statement within lawful scope.

No North America anchor language shall be used to override local law, foreign law, state law, territorial law, Tribal law, Indigenous protocol, public authority competence, data governance obligations, protected knowledge restrictions, public-safe mapping limits, public authority capacity classification, or the Corporation’s non-execution perimeter.

Where North America anchor language creates or may create overclaim, ambiguity, public authority confusion, finance signaling, certification implication, procurement implication, provider preference, sponsor control, or legal-identity confusion, the Corporation shall require correction, withdrawal, rewording, public-safe clarification, controlled clarification, access restriction, or other remedial action.

5.13 No Treaty, Intergovernmental, Regional Regulator, Public Finance, Emergency Command, Procurement, Certification, Recognition, or Finance-Readiness Authority by Anchor Role. The North America anchor role shall not authorize the Corporation to create or enter a treaty, bind governments, constitute an intergovernmental organization, act as a regional regulator, approve public finance, allocate public funds, issue grants on behalf of public authorities, approve tax credits, approve procurement, select vendors for public authorities, certify legal compliance, accredit systems, issue recognition, determine standing, confer maturity, approve Docket status, admit assets to Grid status, issue finance-readiness, determine capital-readability, approve insurance-readiness, provide investment advice, underwrite, lend, insure, rate, broker, place capital, command emergencies, issue public warnings, or operate public infrastructure.

The Corporation may participate in discussions, research, learning sessions, scenarios, controlled rooms, public-safe publications, methods alignment, technical-baseline development, and Nexus interface support concerning such matters only as a non-executing public-benefit evidence and methods institution.

No public authority, sponsor, donor, funder, provider, host, investor, insurer, lender, underwriter, bank, National Consortium Company, Project SPV, Qualified Enterprise Provider, university, laboratory, community, or Nexus entity may use the Corporation’s North America anchor role to imply authority, endorsement, approval, reliance, certification, recognition, finance-readiness, procurement advantage, public authority adoption, or execution status beyond the exact competent record.

Where a North America-facing activity approaches a regulated perimeter, public authority perimeter, public finance perimeter, emergency command perimeter, procurement perimeter, certification perimeter, recognition perimeter, finance-readiness perimeter, investment perimeter, insurance perimeter, banking perimeter, lending perimeter, rating perimeter, securities perimeter, or professional advice perimeter, the Corporation shall hold, quarantine, re-scope, externalize, refer, or terminate the activity unless lawful authority, role separation, disclaimers, records, and controls are established.

5.14 North America Anchor Role Records. The Corporation shall maintain records sufficient to evidence the scope, authority, limits, interfaces, outputs, safeguards, and correction pathways of its North America anchor role.

Such records shall include, as applicable:

a) North America anchor role register entries;

b) Board resolutions or delegated approvals authorizing North America-facing functions;

c) GCRI Canada coordination records;

d) Mexico-facing, Caribbean-facing, Arctic, Great Lakes, Pacific, Atlantic, Gulf, border, regional Nexus, Indigenous, public authority, university, laboratory, host, sponsor, provider, community, and civil society interface records;

e) cross-border legal review records;

f) public authority capacity records;

g) evidence architecture records;

h) methods records;

i) observability records;

j) ontology and controlled vocabulary records;

k) public-good software and technical baseline records;

l) data, AI, cyber, privacy, sovereign compute, verifiable compute, verifiable intelligence, export-control, sanctions, controlled-technology, and cybersecurity review records;

m) community safeguards, Indigenous knowledge, Tribal protocol, protected knowledge, civil rights, accessibility, public-safe mapping, consent, non-consent, grievance, and correction records;

n) public-safe publication records;

o) Nexus Universe, Nexus Observatory, Nexus Standards, Nexus Grid, Nexus Rails, Nexus Academy, Nexus Competence Cell, Nexus Risk Management, Nexus Network, GRF, and GRA alignment records;

p) finance-boundary, certification-boundary, procurement-boundary, public authority-boundary, public warning-boundary, emergency command-boundary, and regulated-perimeter review records;

q) compatibility notes, divergence logs, localization notes, equivalence notes, limitation notes, and reliance limitations;

r) correction, supersession, withdrawal, retraction, takedown, public-safe clarification, and controlled clarification records; and

s) records of any refused, suspended, narrowed, localized, quarantined, externalized, referred, terminated, or re-scoped North America-facing activity.

The governing rule of this Section is that the Corporation’s North America anchor role exists to preserve lawful evidence coherence, methods integrity, observability discipline, technical truth, public-good software, public authority learning, safeguards, and Nexus public-good compatibility across North America-facing systems. It shall never be used to create sovereignty, public authority, treaty power, regional regulation, emergency command, public warning, public finance, procurement, certification, recognition, finance-readiness, market execution, enterprise delivery, or control over any separate institution.

Section 6. Federal, State, Territorial, Tribal, Local, and Cross-Border Legal Orientation

6.1 Federal Law Orientation. The Corporation shall conduct its affairs with full regard to the Constitution, laws, regulations, orders, binding rules, and legally applicable requirements of the United States, as they may apply to the Corporation’s formation, governance, tax status, activities, records, fundraising, employment, contracting, research, publication, data processing, public authority engagement, technical systems, controlled technology, public-good software, public communications, and cross-border interfaces.

Federal law shall be treated as a mandatory compliance layer for all Corporation activities where applicable. The Corporation shall not rely on its nonprofit character, public-benefit mission, technical purpose, public-good role, Nexus alignment, public authority familiarity, sponsor support, academic collaboration, or public-interest character as a basis to avoid federal legal obligations.

The Corporation shall maintain a federal-law orientation covering, as applicable:

a) federal tax law and tax-exempt or tax-exempt-compatible operation;

b) charitable, educational, scientific, research, public-benefit, and public-support requirements where applicable;

c) lobbying, political activity, campaign intervention, public policy, grant, and government ethics requirements;

d) privacy, data protection, cybersecurity, AI governance, consumer protection, research, health data, youth data, public-sector data, and rights-bearing data obligations;

e) civil rights, accessibility, nondiscrimination, employment, contractor, volunteer, fellow, and workplace obligations;

f) sanctions, export controls, controlled technology, dual-use, defense-adjacent, national security-sensitive, CFIUS-relevant, cyber-sensitive, infrastructure-sensitive, AI-RAN, O-RAN, DePIN, DLT, sovereign compute, HPC, geospatial, satellite, robotics, drone, quantum-relevant, semiconductor, and other sensitive-technology requirements;

g) competition, antitrust, unfair competition, procurement-integrity, anti-corruption, gifts, hospitality, conflicts, and market-conduct requirements;

h) federal public records, Freedom of Information Act, federal advisory, open-government, public procurement, grant, cooperative agreement, public authority, and federally connected confidentiality constraints where applicable; and

i) any other federal law applicable to the Corporation’s actual activities.

The Corporation shall not describe federal interaction, federal participation, federal funding, federal grant interest, federal technical review, federal laboratory collaboration, federal agency attendance, federal public authority learning, or federal regulator-listening participation as federal approval, adoption, endorsement, public finance approval, procurement approval, emergency authority, public warning authority, certification, recognition, finance-readiness, regulatory comfort, safe harbor, or public authority delegation unless a competent federal authority has expressly and lawfully recorded that exact status.

6.2 State Law Orientation. The Corporation shall maintain a state-law orientation appropriate to its state of incorporation or organization and to each state in which it operates, solicits support, employs personnel, contracts, holds events, processes data, maintains facilities, collaborates with public authorities, conducts public-benefit activities, publishes state-facing materials, receives restricted funds, or otherwise creates legal obligations.