ARTICLE II. PURPOSES
Section 31. Legal Name, Corporate Identity, and United States Legal Personality
31.1 Legal Name. The legal name of the Corporation shall be The Global Centre for Risk and Innovation - United States, or such other legal name as may be set forth in the Corporation’s Certificate of Incorporation, Articles of Incorporation, charter, or other constituting instrument, as amended only in accordance with applicable law, the governing state nonprofit corporation statute, the Corporation’s governing instruments, and this Bylaw.
The legal name shall be the controlling institutional identifier for all matters requiring legal precision, including incorporation records, corporate filings, tax records, applications for tax-exempt or tax-exempt-compatible status, state registrations, charitable solicitation registrations where applicable, bank accounts, insurance records, grant agreements, sponsorship agreements, donation records, employment records, contractor records, intellectual property records, data-processing agreements, public authority interface records, litigation or regulatory records, Board resolutions, officer delegations, repository notices, controlled-room terms, publications, and official public descriptions.
No person shall alter, abbreviate, translate, stylize, brand, combine, localize, or otherwise present the Corporation’s legal name in a manner that creates uncertainty regarding the Corporation’s separate United States legal personality, nonprofit character, public-benefit purpose, North America anchor role, non-execution status, or separateness from GCRI Canada, any other GCRI-related entity, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Standards, any consortium, national company, Project SPV, provider, sponsor, host, donor, funder, public authority, university, laboratory, community, or enterprise actor.
31.2 Exact Incorporated Name Controls. The exact incorporated name appearing in the Corporation’s current constituting instrument, as accepted by the governing filing authority, shall control in the event of inconsistency among public materials, internal drafts, fundraising materials, websites, slide decks, AI-generated summaries, repository labels, public-good software notices, program descriptions, short names, translations, or informal usage.
Where the exact incorporated name differs from the name customarily used in public or operational materials, the Corporation shall maintain a record identifying the exact incorporated name, approved public name, approved short name, approved operating references, effective date, governing filing, repository location, and responsible custodian.
No contract, filing, tax record, bank account, insurance policy, grant agreement, sponsorship agreement, donation record, employment instrument, intellectual property assignment, software license, data-sharing agreement, public authority interface agreement, or controlled-room instrument shall intentionally use an imprecise or outdated name where legal enforceability, tax status, corporate authority, records integrity, public authority clarity, finance-boundary discipline, or third-party reliance may be affected.
31.3 Use of “The Global Centre for Risk and Innovation - United States” as Full Institutional Name. The full institutional name The Global Centre for Risk and Innovation - United States shall be used where institutional clarity, legal identity, public-facing authority, public-benefit description, public authority interface, cross-border coordination, donor or sponsor understanding, provider-neutrality discipline, Nexus role separation, or records integrity requires precision.
The full institutional name shall be used in first reference in formal public materials, governance instruments, Bylaw schedules, Board resolutions of structural effect, public authority materials, grant and sponsorship instruments, public-safe publications, formal reports, whitepapers, repository notices, public-good software license headers where appropriate, and any material where confusion could arise between the Corporation and GCRI Canada, the broader GCRI function, GRF, GRA, Nexus Network, Nexus Standards, consortiums, national companies, Project SPVs, providers, sponsors, hosts, or enterprise actors.
The full institutional name may be accompanied by the approved short name “GCRI US,” provided that the short name is not used to obscure legal identity or imply a different entity, branch, affiliate, public authority, regional sovereign function, or enterprise execution vehicle.
31.4 Use of “GCRI US” as Approved Short Name. “GCRI US” shall be the approved short name of the Corporation for operational, public-facing, internal, technical, repository, educational, and Nexus-interface use, provided that such use remains consistent with the Corporation’s legal identity, United States seat, nonprofit and public-benefit character, non-execution boundary, and role separation.
“GCRI US” may be used in minutes, agendas, program materials, technical assets, software repositories, dashboards, public-good tools, public-safe reports, event materials, public authority learning materials, academy materials, controlled-room labels, data-room references, and public communications where the legal identity of the Corporation is otherwise clear.
The use of “GCRI US” shall not imply that the Corporation is a branch, office, division, subsidiary, parent, agent, representative, regional command, public authority, public warning body, regulator, standards monopoly, certification body, recognition body, finance-readiness body, procurement body, national company, Project SPV, provider, operator, or enterprise execution actor.
Where the short name appears in a context involving contracts, public authority materials, finance-adjacent materials, certification-sensitive materials, procurement-sensitive materials, sponsor materials, provider materials, investor-facing materials, technical baselines, public-safe publications, or cross-border coordination, the Corporation shall include sufficient full-name, capacity, and limitation language to prevent legal or institutional confusion.
31.5 United States Legal Personality. The Corporation shall have and maintain separate United States legal personality. It may sue and be sued, enter into contracts, receive and hold assets, maintain bank accounts, employ or engage persons, own or license intellectual property, publish materials, maintain repositories, adopt policies, hold records, convene programs, receive support, and exercise lawful nonprofit corporate powers only in its own name and within the limits of applicable law, its constituting instrument, this Bylaw, Board resolutions, delegations, tax status, public-benefit purpose, and non-execution boundary.
The Corporation’s United States legal personality shall be distinct from the persons who form, govern, fund, advise, support, staff, host, sponsor, contract with, participate in, or collaborate with it. No founder, director, officer, member, non-voting member, supporter, subscriber, donor, sponsor, funder, provider, host, public authority participant, university, laboratory, contractor, employee, fellow, advisor, volunteer, contributor, capital reader, national company, Project SPV, or enterprise actor shall be treated as the Corporation merely by reason of association, contribution, participation, influence, appointment, access, authorship, or public visibility.
The Corporation’s separate legal personality shall be preserved in all corporate records, public descriptions, legal instruments, public authority references, data and AI governance records, cybersecurity records, technical repositories, software assets, public-good baselines, grant records, sponsorship records, donation records, fiscal records, and Nexus-interface records.
31.6 Corporate Existence Under Governing State Law. The Corporation shall exist under the governing nonprofit corporation law of its state of incorporation or organization and shall possess only such powers as are permitted by applicable law, the Corporation’s constituting instrument, this Bylaw, and properly authorized governance acts.
The Corporation’s existence under state law shall be subject to applicable United States federal law, including federal tax law, sanctions law, export-control law, privacy and cybersecurity obligations where applicable, civil rights obligations where applicable, employment law, grant compliance, lobbying and political activity rules where applicable, and other legal requirements applicable to the Corporation’s activities.
The Corporation may qualify, register, or obtain authority to conduct activities in other states, the District of Columbia, territories, Tribal-interface contexts, local jurisdictions, Canada, Mexico, Caribbean, Arctic, cross-border, or international settings where lawful and necessary. Such registration, qualification, presence, engagement, event, controlled room, public authority interface, repository location, or program activity shall not displace the Corporation’s governing state law for internal corporate acts unless a competent legal process lawfully provides otherwise and the Board records the change.
31.7 Separate Legal Personality From Founders, Directors, Officers, Members, Donors, Sponsors, Providers, Hosts, Public Authorities, Nexus Entities, and Partners. The Corporation shall be legally separate from its founders, incorporators, directors, officers, members where applicable, non-voting members, supporters, subscribers, donors, sponsors, funders, providers, vendors, contractors, hosts, public authority participants, universities, laboratories, communities, Indigenous knowledge holders, civil society participants, media participants, advisors, fellows, volunteers, contributors, partners, Nexus entities, consortiums, national companies, Project SPVs, and enterprise actors.
No such person or entity shall have authority to bind the Corporation unless such authority is expressly granted by applicable law, the constituting instrument, this Bylaw, Board resolution, officer delegation, written contract, authority matrix, or other competent record. No such person or entity shall acquire governance rights, property rights, fiduciary authority, publication control, research control, public authority access rights, provider preference, finance-readiness rights, recognition rights, certification rights, procurement advantage, or Nexus-compatible status by association with the Corporation.
The Corporation shall not be liable for the acts, omissions, statements, contracts, debts, employment matters, public authority interactions, technical releases, finance-related statements, procurement-related statements, certification-related statements, recognition-related statements, or enterprise execution activities of such persons or entities unless liability is expressly assumed by competent written instrument or imposed by applicable law.
31.8 No Identity Confusion With GCRI Canada. The Corporation shall not be identified, described, governed, funded, represented, or interpreted as GCRI Canada. GCRI Canada shall be treated as a separate Canadian legal person, public-benefit anchor, governing entity, record holder, and compliance subject.
The Corporation may coordinate with GCRI Canada concerning evidence, methods, observability, ontology, technical baselines, public-good software, public-good R&D, verifiable compute, Nexus Truth Engine methods, Nexus Observatory methods, public authority learning, public-safe publication support, cross-border evidence architecture, North America hazard contexts, and correction signals. Such coordination shall not create merger, parent-subsidiary status, branch status, alter ego status, agency, shared treasury, shared liability, single employer status, joint employer status, public authority delegation, finance-readiness authority, recognition authority, certification authority, procurement authority, or enterprise execution responsibility.
Any public description referencing both GCRI US and GCRI Canada shall identify each entity’s separate legal status, jurisdictional seat, role, authority, and limitations where context requires clarity. Shared mission shall not override legal separateness.
31.9 No Identity Confusion With Other GCRI Entities. The Corporation shall not be identified, described, governed, funded, represented, or interpreted as any other national, regional, state, territorial, local, cross-border, global, or function-specific GCRI-related entity unless a competent legal instrument lawfully creates such relationship and the Corporation records it through the required governance process.
The use of a common GCRI mission, doctrine, ontology, technical method, software asset, evidence framework, publication style, repository structure, logo family, event format, academy material, or Nexus-compatible vocabulary shall not merge legal identity. Each GCRI-related entity shall remain responsible for its own formation, governance, tax status, filings, records, finances, employment, data practices, public authority interfaces, public descriptions, contracts, liabilities, and correction pathways.
Where the Corporation participates in shared GCRI functions or cross-entity work, the Corporation shall use compatibility notes, divergence logs, role maps, capacity statements, written interface agreements, public-safe language, and records sufficient to avoid identity confusion.
31.10 No Identity Confusion With The Global Centre for Risk and Innovation as a Broader Function or Brand Family. The phrase “The Global Centre for Risk and Innovation,” the abbreviation “GCRI,” and any associated mission, doctrine, brand family, public-good function, ecosystem reference, or technical architecture shall not be interpreted to collapse the distinction between the broader GCRI function and the Corporation as a specific United States nonprofit legal person.
The Corporation may be described as the United States expression and North America anchor of the GCRI evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, and public authority learning function where accurate and properly bounded. Such description shall not imply that the Corporation is the sole global GCRI entity, the legal owner of all GCRI functions, the parent of all GCRI entities, the agent of all GCRI entities, or the legal successor to all GCRI activities.
Where public materials use “GCRI” as shorthand, the materials shall avoid ambiguity between the Corporation, GCRI Canada, other GCRI-related entities, and the broader GCRI function. When legal, financial, tax, public authority, data, AI, cyber, grant, sponsorship, provider, or Nexus-interface consequences may arise, the full legal name or a clarifying capacity statement shall be used.
31.11 Legal Name Use in Filings, Contracts, IRS Records, State Registrations, Charitable Solicitation Registrations, Bank Accounts, Insurance Records, Grant Agreements, Sponsorship Agreements, Repository Notices, Publications, and Public Materials. The Corporation’s legal name shall be used accurately in all filings, corporate records, tax records, IRS records, state registrations, charitable solicitation registrations where applicable, foreign qualifications where applicable, bank accounts, payment accounts, insurance policies, grant agreements, sponsorship agreements, donation agreements, restricted fund instruments, contracts, employment agreements, contractor agreements, memoranda of understanding, interface agreements, data-sharing agreements, software licenses, repository notices, public-good asset notices, publications, reports, public authority materials, and public-facing institutional materials.
Where a document uses the approved short name “GCRI US,” the document shall include the full legal name where necessary to establish legal identity, contracting party identity, payment identity, tax identity, public authority capacity, publication responsibility, repository responsibility, data controller or processor status where applicable, intellectual property ownership or license status, or liability boundary.
No person shall knowingly use an incorrect, obsolete, unofficial, translated, stylized, abbreviated, sponsor-branded, provider-branded, Nexus-branded, public authority-branded, or finance-signaling name in a manner that may mislead counterparties, public authorities, donors, sponsors, providers, participants, funders, capital readers, media, communities, or the public.
Errors in legal name usage shall be corrected promptly through amendment, notice, clarification, repository update, public-safe correction, contract correction, filing correction, or other appropriate record.
31.12 Operating Name Controls. The Corporation may adopt operating names, program names, initiative names, repository names, public-good software names, technical asset names, academy names, lab names, controlled-room names, challenge names, event names, publication series names, public authority learning names, state or territorial interface names, North America interface names, and Nexus-compatible labels only where such names are approved through the applicable authority and do not obscure legal identity.
An operating name shall not create a separate legal person, subsidiary, branch, agency, public authority, regulated body, certification body, recognition body, finance-readiness body, procurement body, national company, Project SPV, provider, operator, or enterprise execution vehicle unless separately and lawfully constituted by competent instrument.
Operating names shall be reviewed for legal identity clarity, trademark and IP risk, public authority confusion, finance-signaling risk, certification implication, procurement implication, recognition implication, provider-preference implication, sponsor-control implication, data / AI / cyber risk, safeguards risk, public-safe publication risk, and Nexus role-separation risk.
The Corporation shall maintain an operating-name register identifying approved name, purpose, owner, legal entity, scope, limitations, effective date, approval authority, review date, and retirement or supersession status.
31.13 Name Use Authorization. Authority to use the Corporation’s legal name, approved short name, marks, logos, seals, badges, public-good software names, technical asset names, report names, repository names, or Nexus-compatible references shall be granted only by applicable law, this Bylaw, Board resolution, officer delegation, contract, license, participation terms, public-safe claim permission, or other competent written record.
Name-use authorization may be general, limited, conditional, revocable, time-bound, purpose-bound, jurisdiction-bound, platform-bound, publication-bound, event-bound, repository-bound, sponsor-bound, provider-bound, public authority-bound, controlled-room-bound, or otherwise restricted. The Corporation may require disclaimers, capacity statements, non-endorsement language, non-reliance language, no-certification language, no-finance-readiness language, no-procurement language, no-public-authority language, no-provider-preference language, and no-execution language as conditions of name use.
No authorization to use the Corporation’s name shall authorize a person to bind the Corporation, speak for the Corporation, imply endorsement, imply certification, imply recognition, imply finance-readiness, imply procurement advantage, imply public authority approval, imply provider preference, imply sponsor control, or imply Nexus-wide status unless such authority is expressly granted in the same or another competent record.
The Corporation may suspend, revoke, condition, modify, or terminate name-use authorization where misuse, overclaim, public confusion, legal risk, public authority confusion, finance-boundary risk, certification-boundary risk, procurement-boundary risk, provider-preference risk, sponsor-control risk, data / AI / cyber risk, safeguards risk, or reputation risk arises.
31.14 Unauthorized Name Use Correction. Any unauthorized, inaccurate, misleading, overbroad, obsolete, sponsor-driven, provider-driven, public authority-confusing, finance-signaling, certification-implying, procurement-implying, recognition-implying, Nexus-compatible status-implying, or enterprise-execution-implying use of the Corporation’s name, short name, marks, logos, seals, badges, reports, datasets, software, technical baselines, public-good assets, public authority references, or public statements shall be subject to correction.
Correction may include private notice, controlled notice, public-safe clarification, amendment, takedown request, withdrawal, retraction, supersession, repository update, contract notice, license enforcement, access restriction, suspension, termination, legal response, public authority clarification, donor or sponsor clarification, provider clarification, or other action proportionate to the risk.
Where unauthorized name use creates public authority confusion, finance overclaim, certification overclaim, recognition overclaim, procurement implication, provider-preference implication, sponsor-control implication, public warning implication, emergency command implication, data / AI / cyber risk, safeguards risk, or public-safe publication risk, the Corporation shall treat the matter as a governance and boundary incident and record the review, corrective action, responsible owner, and closure.
No delay in correcting unauthorized use shall be deemed consent, waiver, ratification, apparent authority, course of dealing, estoppel, or approval unless the Board or other competent authority expressly records ratification where lawful.
31.15 Legal Name and Identity Records. The Corporation shall maintain legal name and identity records sufficient to demonstrate its incorporated name, approved short name, operating names, name-use authorizations, public description approvals, corrections, withdrawals, takedowns, clarifications, and legal identity boundaries.
Such records shall include, as applicable:
a) the constituting instrument showing the exact incorporated name;
b) amendments affecting legal name or corporate identity;
c) approved short-name records;
d) approved operating-name records;
e) public description approvals;
f) contracts and filings using the legal name;
g) IRS and tax records;
h) state, territorial, District of Columbia, charitable solicitation, and foreign qualification records where applicable;
i) bank, insurance, grant, sponsorship, donation, and restricted fund records;
j) repository, software, technical asset, dataset, dashboard, publication, and public-good asset name records;
k) public authority interface name-use records;
l) Nexus-interface name-use records;
m) GCRI Canada and other GCRI entity distinction records;
n) GRF and GRA distinction records;
o) sponsor, donor, funder, provider, host, public authority, university, laboratory, community, and enterprise actor name-use controls;
p) unauthorized-use reports;
q) correction, withdrawal, takedown, retraction, supersession, clarification, suspension, termination, or legal-response records; and
r) responsible owner, custodian, authority, effective date, review date, retention class, access class, publication class, legal hold status, repository location, and metadata.
The governing rule of this Section is that the Corporation’s name is not merely a label. It is the legal identity through which the Corporation’s nonprofit character, public-benefit purpose, United States seat, North America anchor role, non-execution boundary, role separation, public authority boundary, finance boundary, certification and procurement boundary, data / AI / cyber discipline, safeguards, validity-by-record, correctionability, and anti-capture architecture are made legible and enforceable. The name shall therefore be used with precision, protected against misuse, and corrected wherever ambiguity would weaken the Corporation’s institutional integrity.
Section 32. Short Names, Operating References, Brand Family, and Public Description Controls
32.1 Short Name Use. The approved short name “GCRI US” may be used as an operational, public-facing, technical, educational, repository, programmatic, and administrative reference to the Corporation, provided that such use remains subordinate to the Corporation’s exact legal name and does not create legal, institutional, public authority, finance, certification, procurement, recognition, sponsor, provider, or Nexus-role confusion.
Short name use shall be permitted where the full legal name has already been introduced, where context clearly identifies the Corporation, or where the document, system, interface, repository, notice, agenda, dashboard, public-safe publication, or technical asset includes metadata or contextual language sufficient to preserve the Corporation’s legal identity.
Short name use shall not be permitted where it would obscure the Corporation’s separate United States legal personality, nonprofit status, public-benefit purpose, North America anchor boundary, non-execution status, public authority boundary, finance boundary, certification boundary, procurement neutrality, provider neutrality, sponsor non-control, role separation from The Global Risks Forum (GRF) and The Global Risks Alliance (GRA), or separateness from GCRI Canada and other GCRI-related entities.
Where short name use creates uncertainty, the Corporation shall use the full legal name, a capacity statement, a limitation statement, a non-reliance statement, a public authority boundary statement, a finance-boundary statement, a certification-boundary statement, or other clarifying language sufficient to remove ambiguity.
32.2 Approved Abbreviations. The approved abbreviation of the Corporation shall be “GCRI US.” No other abbreviation, acronym, shortened label, translation, stylization, brand mark, project label, public authority label, finance label, regional label, technical label, or Nexus-facing label shall be treated as an approved abbreviation unless adopted by competent authority and entered into the applicable name-use, controlled-vocabulary, or public-description record.
Abbreviations such as “GCRI-USA,” “GCRI United States,” “GCRI North America,” “Global Centre US,” “GCRI America,” “GCRI National,” “GCRI Public Authority,” “GCRI Standards,” “GCRI Observatory,” “GCRI Registry,” “GCRI Finance,” or similar expressions shall not be used as legal or institutional substitutes unless specifically approved and recorded. Any abbreviation that suggests a different legal entity, regional authority, public authority, standards authority, registry authority, finance-readiness authority, certification body, procurement body, emergency command body, public warning body, provider, operator, national company, Project SPV, or enterprise execution vehicle shall be prohibited unless separately and lawfully constituted and expressly authorized.
Approved abbreviations shall be used consistently across Board records, officer records, committee records, public materials, GitBook pages, websites, repositories, public-good software documentation, technical baselines, controlled-room labels, data rooms, public authority materials, grant materials, sponsorship materials, donor materials, provider materials, academy materials, and public-safe publications.
32.3 Program-Specific Operating References. The Corporation may use program-specific operating references for programs, platforms, labs, academy offerings, observability methods, evidence initiatives, technical repositories, controlled rooms, public authority learning activities, research streams, public-good software projects, open technical baselines, Nexus-interface activities, state or territorial interfaces, North America coordination activities, and public-safe publication series.
Each program-specific operating reference shall be treated as a label for an activity of the Corporation, not as a separate legal person, fiduciary body, public authority, regulated actor, certification body, recognition body, registry body, finance-readiness body, procurement body, provider, national company, Project SPV, or enterprise execution vehicle.
Program-specific references shall be approved, classified, recorded, and reviewed for:
a) legal identity clarity;
b) consistency with the Corporation’s public-benefit purpose;
c) consistency with nonprofit and tax-exempt or tax-exempt-compatible requirements;
d) consistency with the non-execution boundary;
e) consistency with GCRI / GRF / GRA role separation;
f) public authority boundary risk;
g) finance, securities, insurance, lending, rating, public finance, and capital-reader boundary risk;
h) certification, procurement, recognition, maturity, Docket, Grid, and Nexus-compatible claim risk;
i) data / AI / cyber / privacy implications;
j) community safeguards, Tribal / Indigenous, local, territorial, civil rights, accessibility, and protected knowledge implications;
k) sponsor, donor, funder, provider, host, and enterprise actor capture risk;
l) public-safe publication implications; and
m) correctionability and records requirements.
No program-specific operating reference shall be used to imply that participation in a program creates membership, governance rights, public authority endorsement, procurement advantage, certification, recognition, finance-readiness, insurance-readiness, Nexus-approved status, provider preference, official public warning status, or execution authority.
32.4 Repository and Technical Asset Naming. Repository names, software names, dataset names, dashboard names, schema names, API names, SDK names, model-card names, system-card names, benchmark names, test-harness names, reference-architecture names, technical-baseline names, observability-tool names, evidence-register names, and public-good technical asset names shall be governed by legal identity, public-safe claims, controlled vocabulary, IP, data / AI / cyber, security, publication, and Nexus role-separation controls.
A repository or technical asset name may identify the Corporation as author, steward, custodian, contributor, maintainer, sponsor, or public-good publisher only where the relevant authority and record support that status. Technical asset naming shall not imply certification, conformance approval, procurement approval, provider preference, recognition, finance-readiness, insurance-readiness, capital-readability, public authority adoption, public warning status, operational deployment, emergency command function, or enterprise execution.
Repository and technical asset names shall include, where appropriate, version, status, custodian, public-safe classification, license class, access class, release status, deprecation status, correction pathway, and relation to the Corporation’s public-good function.
Where a technical asset interoperates with Nexus Network, Nexus Standards, Nexus Observatory, Nexus Rails, Nexus Grid, GRF, GRA, consortiums, national companies, Project SPVs, public authorities, or enterprise actors, the asset name and documentation shall distinguish between technical support, evidence support, standards support, protocol support, registry support, recognition support, finance-readiness support, and execution.
32.5 Public-Good Software Naming. Public-good software developed, maintained, funded, released, contributed to, or stewarded by the Corporation shall be named in a manner that reflects public-good purpose, technical function, status, license posture, release maturity, security posture, public-safe limitations, and the Corporation’s non-executing role.
Public-good software naming shall not imply that the software is certified, procurement-approved, government-approved, public authority-adopted, finance-ready, insurance-ready, bankable, recognized, Docket-approved, Grid-approved, Nexus-compatible by final authority, operationally safe for all uses, legally compliant for all jurisdictions, cyber-secure in all deployments, or professionally endorsed by the Corporation.
Software names shall avoid language that could mislead users into treating code, models, agents, dashboards, proof receipts, inference records, ledgers, AI-RAN signals, O-RAN signals, DePIN records, digital twin outputs, sensor feeds, or automated results as institutional authority. Any software output with material consequence shall remain subject to human review, record support, limitation, classification, and correction.
Where software is experimental, reference, demonstrative, educational, research, alpha, beta, sandboxed, deprecated, archived, withdrawn, restricted, controlled, public-safe, or non-production, such status shall be reflected in documentation and, where appropriate, in naming or metadata.
32.6 Open Technical Baseline Naming. Open technical baselines issued by the Corporation shall be named and described as public-good technical guidance, methods support, evidence support, interoperability support, research support, or public authority learning support, unless a competent authority has expressly adopted a different status by lawful record.
No open technical baseline shall be named or described as a mandatory standard, legal requirement, public authority mandate, certification, accreditation, procurement requirement, finance-readiness requirement, insurance-readiness requirement, bankability rule, public finance approval condition, Nexus-wide protocol, GRF recognition requirement, GRA finance-readiness requirement, or official compliance rule unless separately and lawfully adopted by the competent body.
Open technical baseline names shall clearly distinguish among draft baselines, proposed baselines, reference baselines, controlled baselines, public-safe baselines, superseded baselines, withdrawn baselines, archived baselines, localized baselines, and adopted baselines. The Corporation shall maintain baseline records identifying status, version, authority, custodian, scope, limitations, public-safe language, affected jurisdictions, technical dependencies, correction pathway, and relation to Nexus Standards or other competent bodies where applicable.
32.7 Public-Facing Report Naming. Public-facing reports, whitepapers, public-safe summaries, technical notes, evidence briefs, learning briefs, observability notes, methods notes, academy materials, public authority learning materials, dashboards, maps, indexes, data releases, and publication series shall be named in a manner that accurately reflects their source, status, purpose, evidentiary basis, limitations, and non-executing character.
A public-facing report name shall not imply that the Corporation has issued a public warning, emergency command, regulatory determination, public authority decision, certification, recognition, finance-readiness determination, investment recommendation, insurance approval, procurement recommendation, vendor selection, provider ranking, official maturity determination, Docket approval, Grid approval, or Nexus-wide adoption.
Where a report is intended for public-safe learning, controlled circulation, restricted audience, public authority learning, technical review, pre-publication review, draft consultation, research discussion, controlled-room use, data-room use, clean-room use, or non-public evidence review, its name, cover, metadata, file name, repository entry, and notice language shall reflect the applicable status and limitations.
Public-facing report naming shall also preserve separateness from GRF public-facing legitimacy functions and GRA finance-readiness functions. A GCRI US report may support GRF or GRA processes, but shall not name itself in a way that suggests GRF recognition or GRA finance-readiness unless such status is separately issued by the competent body.
32.8 State, Territorial, Tribal, Local, North America, and Cross-Border Interface Naming. Names used for state, territorial, District of Columbia, Tribal-interface, Indigenous, local, county, municipal, metropolitan, port, utility, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, infrastructure, North America, Canada, Mexico, Caribbean, Arctic, Great Lakes, Pacific, Atlantic, Gulf, border, or cross-border interfaces shall be reviewed and approved for jurisdictional clarity.
Such names may describe the interface, geography, learning context, evidence context, observability context, technical context, or coordination context, but shall not imply that the Corporation has governmental authority, sovereign authority, treaty status, intergovernmental status, official public authority status, public finance authority, public warning authority, emergency command authority, procurement authority, regulatory authority, certification authority, recognition authority, finance-readiness authority, or execution authority.
Where a public authority, Tribal Nation, Indigenous government, public infrastructure operator, public university, public laboratory, public agency, public corporation, Crown entity, state entity, territorial entity, or local government appears in an interface name, the Corporation shall ensure that the name does not imply endorsement, adoption, delegation, public-private partnership, funding approval, procurement approval, public finance approval, sovereign obligation, official public warning, emergency command, or regulatory status unless expressly and lawfully recorded by the competent public authority.
The Corporation shall maintain interface naming records, capacity classifications, public authority reference approvals, localization notes, divergence logs, compatibility notes, and public-safe descriptions for such interfaces.
32.9 “North America Anchor” Reference Controls. The expression “North America Anchor” may be used to describe the Corporation’s bounded role as a United States and North America anchor for evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, verifiable compute methods, Nexus Truth Engine methods, Nexus Observatory methods, public authority learning, public-safe publication support, safeguards, and correctionable technical memory where accurate and properly bounded.
“North America Anchor” shall not mean, imply, or be used to suggest that the Corporation is a North America sovereign authority, treaty body, intergovernmental organization, regional regulator, public finance authority, emergency command body, public warning authority, procurement body, certification body, recognition body, finance-readiness authority, standards monopoly, regional operating company, national company, Project SPV, infrastructure owner, operator, lender, insurer, underwriter, broker, dealer, investment adviser, rating agency, public authority, or enterprise execution vehicle.
Any use of “North America Anchor” in public materials, public authority materials, sponsor materials, donor materials, provider materials, grant materials, capital-reader materials, technical baselines, reports, decks, GitBook pages, websites, repositories, controlled-room materials, data-room materials, or Nexus-interface materials shall include context sufficient to preserve the role boundary.
Where “North America Anchor” language may be misunderstood, the Corporation shall use one or more of the following clarifiers: “bounded public-good role,” “non-executing,” “evidence and methods anchor,” “public authority learning support,” “not a public authority,” “not a finance-readiness body,” “not a certification body,” “not a procurement authority,” “not an emergency command body,” “not a public warning authority,” and “not an enterprise execution vehicle.”
32.10 No Use of Short Name to Obscure Legal Identity. The approved short name “GCRI US” shall not be used to obscure the Corporation’s exact legal name, corporate status, governing law, tax status, state of incorporation, registered office, principal office, authority, responsibility, or legal separateness.
No person shall use the short name in a manner that makes it unclear whether the acting entity is GCRI US, GCRI Canada, another GCRI-related entity, the broader GCRI function, GRF, GRA, Nexus Network, Nexus Standards, a consortium, a national company, a Project SPV, a provider, a sponsor, a host, a public authority, a university, a laboratory, a community body, or an enterprise actor.
Where legal, financial, tax, regulatory, public authority, procurement, certification, recognition, finance-readiness, public-safe, data / AI / cyber, safeguards, or cross-border consequences may arise, the full legal name shall be used or cross-referenced with the short name.
Any document that uses only the short name in a context requiring legal precision shall be corrected, supplemented, reissued, or annotated where necessary to preserve legal identity.
32.11 No Use of Brand Family to Create Apparent Merger. No GCRI brand family reference, shared logo family, shared design language, shared doctrine, shared GitBook style, shared website architecture, shared repository structure, shared publication style, shared public-good vocabulary, shared Nexus visual identity, shared event name, shared academy name, shared public authority learning format, shared observability language, shared proof-receipt language, or shared technical baseline label shall be used to create apparent merger among GCRI US, GCRI Canada, other GCRI-related entities, GRF, GRA, Nexus entities, consortiums, national companies, Project SPVs, or enterprise actors.
Brand family use shall preserve legal separateness, separate treasury, separate authority, separate records, separate liabilities, separate governance, separate tax status, separate employment relationships, separate data responsibilities, separate public authority interfaces, and separate correction pathways.
Where common design, branding, doctrine, vocabulary, or architecture is used across entities, the Corporation shall maintain public description controls, entity labels, role descriptions, disclaimers, repository metadata, publication metadata, and interface records sufficient to avoid apparent merger, agency, parent-subsidiary status, branch status, alter ego status, shared liability, single employer status, joint employer status, or shared authority.
Brand family materials shall be corrected where they imply that one entity controls, guarantees, approves, recognizes, finances, certifies, procures, executes, or supervises another entity without competent legal basis.
32.12 No Use of Nexus Naming to Imply Whole-System Control. The Corporation may use Nexus-related naming where accurate, authorized, and consistent with the Corporation’s role as a public-good technical institution supporting evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, verifiable compute methods, public authority learning, public-safe publication support, safeguards, and correctionability.
No Nexus-related name shall be used to imply that the Corporation owns, operates, controls, governs, regulates, certifies, recognizes, finances, procures, commands, or executes the whole Nexus Network, Nexus Standards, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, qualified providers, public authorities, or enterprise actors.
Nexus names shall distinguish between architectural alignment, technical support, evidence support, methods support, interoperability support, standards support, observability support, public authority learning support, GRF recognition functions, GRA finance-readiness functions, and enterprise execution functions.
No reference to Nexus Network, Nexus Standards, Nexus Observatory, Nexus Rails, Nexus Grid, proof receipts, role keys, smart licenses, Dockets, maturity records, capital-reader rooms, or public-good stack compatibility shall be used to imply binding authority by GCRI US unless such authority is separately and lawfully designated and recorded.
32.13 No Use of GRF or GRA Naming to Imply Recognition or Finance-Readiness Authority. The Corporation shall not use GRF-related naming in a manner that implies that GCRI US performs the public-facing registry, recognition, maturity-records, standing, claims-discipline, stakeholder-formation, public-safe reporting, or legitimacy-stewardship functions of The Global Risks Forum (GRF).
The Corporation shall not use GRA-related naming in a manner that implies that GCRI US performs finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, capital-reader room, investment, lending, insurance, underwriting, rating, public finance, brokerage, securities, or regulated-perimeter functions of The Global Risks Alliance (GRA).
Where GCRI US materials support GRF or GRA, the materials shall identify the support as evidence support, methods support, observability support, ontology support, technical-baseline support, public-good software support, public authority learning support, correction signal support, or other bounded support. Such materials shall not state or imply that GCRI US has issued recognition, standing, maturity, public legitimacy, finance-readiness, capital-readability, proof pack, insurance-readiness, bankability, investability, rating, underwriting approval, lending approval, public finance approval, or capital recommendation.
Misuse of GRF or GRA naming shall be corrected promptly through limitation language, re-labeling, withdrawal, routing, public-safe clarification, or other appropriate action.
32.14 No Use of Public Authority Naming to Imply Endorsement, Adoption, Funding, Procurement, Regulation, Public Warning, or Sovereign Obligation. The Corporation shall not use the name, seal, logo, insignia, office title, agency title, public authority title, public official title, public body title, Tribal government title, Indigenous government title, public infrastructure operator name, public university name, public laboratory name, port authority name, utility name, emergency management body name, public health body name, regulator name, public finance body name, or governmental program name in a manner that implies endorsement, adoption, delegation, funding approval, procurement approval, regulatory approval, public finance approval, official public warning, emergency command, public-private partnership, sovereign obligation, or governmental decision unless such status is expressly and lawfully recorded by the competent public authority.
Public authority references shall be subject to capacity classification. Public authority participation may be described as official-capacity participation, observer participation, regulator-listening participation, public finance reader participation, emergency-management participant participation, simulation participant participation, technical-learning participation, or other approved capacity only where accurate and recorded.
No public authority name may be used to sell access, imply influence, purchase legitimacy, confer provider preference, imply procurement advantage, imply public funding approval, or create a false appearance of governmental backing.
Where public authority naming creates confusion, the Corporation shall correct the record, notify affected parties where appropriate, restrict further use, and preserve public authority clarification records.
32.15 No Use of Provider or Sponsor Naming to Imply Preferred Status or Control. Provider, vendor, contractor, donor, sponsor, funder, host, investor, insurer, lender, underwriter, bank, capital reader, national company, Project SPV, enterprise actor, university, laboratory, or partner names shall not be used in a manner that implies governance control, research control, publication control, public authority access, provider preference, procurement advantage, recognition, certification, finance-readiness, insurance-readiness, bankability, investability, rating, public finance approval, Nexus-compatible status, or market endorsement.
The Corporation may acknowledge lawful support, sponsorship, funding, hosting, technical contribution, in-kind contribution, research collaboration, software contribution, data contribution, equipment contribution, compute contribution, venue support, or participation, provided that the acknowledgment is accurate, proportionate, non-misleading, consistent with tax and nonprofit requirements, and accompanied by limitation language where necessary.
Sponsor or provider naming shall not be permitted to dominate public-good publications, public authority learning materials, technical baselines, controlled-room materials, evidence outputs, reports, dashboards, academy materials, repository documentation, or public-safe communications in a manner that compromises independence, creates capture risk, or suggests outcome purchase.
Any sponsor or provider name use shall remain subject to anti-capture review, conflict review, public-safe claims review, competition review, procurement-neutrality review, and correctionability.
32.16 Public Description Review. Public descriptions of the Corporation, its status, purpose, programs, powers, limitations, public-good role, North America anchor role, Nexus alignment, relationship to GCRI Canada, relationship to GRF, relationship to GRA, relationship to Nexus entities, relationship to public authorities, relationship to providers and sponsors, relationship to universities and laboratories, and relationship to enterprise stack actors shall be reviewed for accuracy, legal clarity, public-safe wording, and role separation.
Public description review shall apply to websites, GitBook pages, slide decks, grant applications, sponsorship materials, donor materials, public authority materials, provider materials, press releases, media statements, conference materials, social media profiles, repository readme files, software documentation, technical baselines, whitepapers, public-safe reports, public-facing summaries, public authority learning materials, academy materials, controlled-room notices, data-room notices, public-good software notices, and AI-generated public summaries where used.
A public description shall not overstate the Corporation’s authority, soften prohibited-purpose boundaries, obscure legal identity, imply public authority status, imply emergency command or public warning authority, imply finance-readiness, imply certification, imply procurement approval, imply recognition, imply provider preference, imply sponsor control, imply Nexus-wide control, imply GRF or GRA functions, or imply enterprise execution.
Public descriptions shall be corrected, withdrawn, superseded, annotated, restricted, or reissued where they become inaccurate, incomplete, misleading, stale, overbroad, legally risky, public authority-confusing, finance-signaling, certification-implying, procurement-implying, recognition-implying, or inconsistent with this Bylaw.
32.17 Brand Family and Public Description Records. The Corporation shall maintain records sufficient to demonstrate approval, control, limitation, correction, and supersession of short names, abbreviations, operating references, brand family uses, public descriptions, public authority references, sponsor references, provider references, Nexus references, GRF references, GRA references, repository names, software names, technical asset names, public-facing report names, and North America anchor references.
Such records shall include, as applicable:
a) approved short-name and abbreviation records;
b) operating-reference records;
c) program, lab, academy, challenge, event, controlled-room, data-room, evidence-room, clean-room, public authority room, and no-download room name records;
d) repository, software, dataset, dashboard, schema, API, SDK, model-card, system-card, benchmark, test-harness, reference-architecture, and technical-baseline name records;
e) public-facing report and publication series name records;
f) state, territorial, Tribal-interface, local, North America, and cross-border interface name records;
g) North America Anchor reference records;
h) GCRI brand family use records;
i) Nexus naming and compatibility records;
j) GRF and GRA reference records;
k) public authority reference and capacity-classification records;
l) sponsor, donor, funder, provider, host, enterprise actor, university, laboratory, and partner reference records;
m) public description approvals;
n) public-safe limitation language approvals;
o) non-reliance, non-endorsement, no-certification, no-recognition, no-finance-readiness, no-procurement, no-public-authority, no-public-warning, and no-execution disclaimer records;
p) public description review records;
q) unauthorized, misleading, overbroad, or stale description reports;
r) corrections, withdrawals, retractions, takedowns, supersessions, public-safe clarifications, access restrictions, license actions, contract actions, or legal responses; and
s) responsible owner, custodian, authority, effective date, review date, retention class, access class, publication class, legal hold status, repository location, and metadata.
The governing rule of this Section is that the Corporation’s names, descriptions, brands, operating references, public authority references, Nexus references, GRF references, GRA references, sponsor references, provider references, reports, repositories, software assets, and public-facing labels shall make the Corporation more legible, not more ambiguous. No short name, brand family, public description, technical label, or ecosystem reference shall be used to weaken legal identity, mission lock, nonprofit discipline, role separation, public authority boundaries, finance boundaries, certification and procurement boundaries, provider neutrality, sponsor non-control, safeguards, validity-by-record, or correctionability.
Section 33. United States Nonprofit Corporate Status
33.1 Nonprofit Corporate Status. The Corporation shall be organized, governed, operated, represented, recorded, and interpreted as a United States nonprofit corporation, subject to applicable United States federal law, the governing state nonprofit corporation statute, the Corporation’s Certificate of Incorporation, Articles of Incorporation, charter, or other constituting instrument, and this Bylaw.
The Corporation’s nonprofit corporate status shall be a structural condition of its legal identity and shall not be treated as a temporary label, fundraising description, branding convention, program status, Nexus-facing classification, or public-good style. It shall control the Corporation’s governance, treasury, records, contracting, asset ownership, tax posture, public descriptions, support acceptance, compensation, conflicts, dissolution, and public-benefit discipline.
The Corporation shall not be operated for private profit, private inurement, impermissible private benefit, shareholder return, sponsor control, provider preference, capital placement, enterprise execution, public authority substitution, or market capture. Its corporate status shall exist to support lawful public-benefit purposes, including evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, verifiable compute methods, public authority learning, public-safe publication support, community safeguards, validity-by-record, and correctionability.
33.2 Non-Stock or Non-Share Character. The Corporation shall be non-stock, non-share, or otherwise non-equity in character to the extent provided by its governing state law and constituting instrument. No shares, stock, equity interests, ownership units, profit interests, tokenized ownership interests, dividend rights, capital appreciation rights, revenue-participation rights, voting securities, membership interests with economic ownership rights, or similar instruments shall be issued by or on behalf of the Corporation.
No donor, sponsor, funder, provider, host, contractor, employee, director, officer, member, supporter, subscriber, public authority participant, university, laboratory, community participant, contributor, advisor, fellow, national company, Project SPV, investor, insurer, lender, underwriter, capital reader, or enterprise actor shall acquire any ownership interest in the Corporation by reason of contribution, participation, payment, support, authorship, technical access, repository contribution, public authority room attendance, controlled-room participation, grant funding, sponsorship, or collaboration.
The Corporation may recognize rights of statutory members, voting members, non-voting members, supporters, subscribers, participants, donors, sponsors, fellows, advisors, contributors, or other categories only where such rights are created by law, the constituting instrument, this Bylaw, Board resolution, member resolution where applicable, or written instrument. Such rights shall not be economic ownership rights unless expressly permitted by law and compatible with nonprofit status, and no such right shall permit private distribution of the Corporation’s net earnings or assets.
33.3 Non-Distribution Principle. The Corporation shall be governed by a non-distribution principle. No part of the Corporation’s net earnings, surplus, reserves, assets, software assets, data assets, technical assets, public-good repositories, publications, controlled-room materials, grant proceeds, sponsorship proceeds, donation proceeds, fee revenues, subscription revenues, or other property shall be distributed to private persons except as lawful compensation, reimbursement, grant, stipend, scholarship, award, fellowship support, contractual payment, vendor payment, program payment, or other lawful payment made in furtherance of the Corporation’s public-benefit purposes and consistent with applicable law, tax status, this Bylaw, and approved controls.
The non-distribution principle shall apply during the Corporation’s existence, during any wind-up, and upon dissolution, subject to applicable law and the governing dissolution provisions. Corporate assets shall remain dedicated to lawful nonprofit, public-benefit, charitable, educational, scientific, public-good, or similarly compatible purposes as required by the Corporation’s status and governing instruments.
No private person shall have a claim to residual assets, retained earnings, technical assets, repositories, public-good software, open technical baselines, datasets, brands, marks, goodwill, grants, restricted funds, or public-good infrastructure support merely because that person contributed money, services, data, equipment, compute, facilities, code, methods, evidence, publications, or institutional support.
33.4 Public-Benefit Orientation. The Corporation’s nonprofit status shall be interpreted through a public-benefit orientation. The Corporation shall conduct its affairs for public-good, educational, scientific, research, technical, evidence, methods, observability, data / AI / cyber, public authority learning, safeguards, and systemic de-risking purposes, and not for private commercial advantage, private control, market preference, provider capture, sponsor capture, investor benefit, or enterprise execution.
Public-benefit orientation shall require that the Corporation’s programs, records, assets, publications, software, technical baselines, controlled rooms, public authority interfaces, sponsorships, grants, donations, partnerships, state interfaces, territorial interfaces, Tribal-interface activities, North America interfaces, Nexus interfaces, and public descriptions remain aligned with public-good stewardship.
The Corporation may interact with enterprise actors, providers, sponsors, funders, public authorities, universities, laboratories, national companies, Project SPVs, communities, media, and capital readers where lawful and role-separated. Such interaction shall not alter the Corporation’s public-benefit orientation or convert the Corporation into an enterprise execution vehicle, capital intermediary, public authority, procurement body, certification body, recognition body, finance-readiness body, or market operator.
33.5 State Law Compliance. The Corporation shall comply with the governing state nonprofit corporation law applicable to its formation, governance, records, filings, registered agent, registered office, principal office, directors, officers, members where applicable, meetings, notices, votes, written consents, committees, conflicts, indemnification, amendments, mergers, asset transfers, dissolution, and internal corporate acts.
The Board shall ensure that the Corporation maintains good standing with the governing state filing authority, including required annual or periodic reports, registered agent continuity, registered office continuity, filing fee compliance, franchise or similar obligations where applicable, and any other state-law requirement applicable to the Corporation.
Where the Corporation operates, qualifies, registers, solicits support, employs personnel, contracts, conducts programs, convenes public authority learning, maintains controlled rooms, holds events, or conducts other activities outside its state of incorporation, the Corporation shall review and comply with applicable state, District of Columbia, territorial, local, Tribal-interface, and cross-border requirements as provided in this Bylaw.
33.6 Federal Law Compliance. The Corporation shall comply with applicable United States federal law, including federal tax law, employment law, civil rights law, accessibility requirements where applicable, privacy and data protection requirements where applicable, cybersecurity requirements where applicable, sanctions, export controls, controlled-technology requirements, research compliance requirements, lobbying and political activity rules where applicable, grant requirements, anti-corruption requirements, competition and antitrust requirements, and any other federal law applicable to the Corporation’s activities.
Federal law compliance shall be treated as a governing condition of the Corporation’s nonprofit status and public-benefit character. No program, technical asset, public-good software release, public authority interface, sponsor relationship, provider relationship, cross-border activity, data transfer, AI model use, repository practice, grant term, publication, controlled-room activity, Nexus-interface activity, or public description shall override applicable federal law.
Where federal-law uncertainty exists, the Corporation shall apply the most protective lawful posture pending review, including hold, stop, quarantine, re-scope, access restriction, publication freeze, implementation freeze, technical isolation, counsel review, Board review, externalization, referral, or termination.
33.7 Articles or Certificate Controls. The Corporation’s Certificate of Incorporation, Articles of Incorporation, charter, or other constituting instrument shall control as the higher-order corporate instrument beneath mandatory applicable law and above this Bylaw to the extent required by law. This Bylaw shall be interpreted consistently with the constituting instrument wherever possible.
No provision of this Bylaw, policy, protocol, schedule, annex, register, matrix, committee charter, council mandate, public summary, technical baseline, software documentation, public authority material, grant document, sponsorship material, public statement, AI-generated summary, Nexus instrument, or operating practice shall amend, contradict, weaken, or override the constituting instrument unless the constituting instrument is lawfully amended by competent authority and the change is properly recorded.
Where a conflict appears between the constituting instrument and this Bylaw, the Corporation shall identify the conflict, apply the governing precedence rule, preserve the Corporation’s nonprofit status and public-benefit purpose, and undertake correction, amendment, clarification, supersession, or restatement as needed.
33.8 Bylaw Controls Subject to Law and Articles. This Bylaw shall control the internal governance of the Corporation subject to mandatory applicable law and the Corporation’s constituting instrument. The Bylaw shall bind the Board, directors, officers, committees, councils, working groups, members where applicable, non-voting members, supporters, subscribers, participants, advisors, fellows, contributors, contractors, employees, volunteers, controlled-room participants, repository participants, sponsors, donors, funders, providers, hosts, and other persons acting within or through the Corporation to the extent applicable by law, contract, policy, or recorded terms.
No lower-order instrument may override this Bylaw. Policies, protocols, schedules, annexes, matrices, registers, forms, templates, manuals, playbooks, public summaries, program terms, participation terms, public authority materials, repository rules, controlled-room rules, grant terms, sponsorship terms, donor terms, provider terms, or Nexus-interface materials shall implement the Bylaw and shall not displace it.
Operational practice, repeated usage, informal approval, public expectation, sponsor expectation, provider expectation, public authority interest, technical convenience, AI-generated drafting, repository presence, dashboard display, or Nexus reference shall not amend this Bylaw.
33.9 IRS Status To Be Maintained by Record. The Corporation shall maintain records of its federal tax classification, federal employer identification number, IRS filings, tax-exemption application where applicable, IRS determination letter where applicable, annual information returns where applicable, unrelated business income review where applicable, donor-receipting authority where applicable, lobbying or political activity status where applicable, and any federal tax correspondence or determination affecting the Corporation.
No person shall represent that the Corporation holds charitable status, tax-exempt status, Section 501(c)(3) recognition, Section 501(c)(4) status, Section 501(c)(6) status, supporting organization status, fiscal sponsorship status, sponsored project status, public charity status, private foundation status, tax-deductible donation status, or any other federal tax status unless such status is supported by current record and authorized public description.
Where federal tax status is pending, uncertain, not yet obtained, changed, revoked, suspended, limited, or otherwise conditional, the Corporation shall use accurate language and shall not issue misleading donation receipts, fundraising statements, grant representations, public descriptions, sponsor materials, or tax statements.
33.10 State Tax and Registration Status To Be Maintained by Record. The Corporation shall maintain records of state tax registrations, state tax exemptions where applicable, franchise tax obligations where applicable, sales and use tax obligations where applicable, state employer registrations, state nonprofit filings, foreign qualifications, certificates of good standing, charitable solicitation registrations where applicable, and other state-level status records required for lawful operation.
State tax and registration status shall be reviewed before the Corporation conducts material activity in a state, including fundraising, charitable solicitation, employment, program delivery, controlled-room activity, public authority engagement, contracting, event hosting, data collection, repository administration, or other activity that may trigger registration, tax, employment, solicitation, or compliance requirements.
No public representation, solicitation, event notice, contract, grant document, sponsorship material, or state-interface material shall imply state registration, state approval, state endorsement, tax exemption, public authority status, procurement eligibility, or public funding approval unless supported by competent record.
33.11 Charitable Solicitation Status Where Applicable. Where the Corporation solicits donations, charitable contributions, grants, sponsorships, in-kind support, restricted funds, public-good infrastructure support, or similar support in any jurisdiction that regulates charitable solicitation, the Corporation shall review and comply with applicable charitable solicitation registration, exemption, disclosure, reporting, renewal, and professional fundraiser requirements.
No fundraising material shall state or imply charitable deductibility, charitable registration, public charity status, government approval, public authority endorsement, public finance approval, or tax benefit unless supported by competent record and approved language.
Sponsorship, donation, grant, and public-good support materials shall distinguish among charitable contributions, non-charitable payments, sponsorship payments, subscriptions, program fees, cost-recovery payments, restricted grants, in-kind contributions, and other forms of support as required by law and tax controls.
The Corporation shall correct any solicitation, receipt, acknowledgment, website, deck, grant proposal, sponsor acknowledgment, donor communication, or public statement that misstates the Corporation’s charitable solicitation status.
33.12 Foreign Qualification in States or Territories Where Required. The Corporation may qualify, register, or obtain authority to conduct activities in states, the District of Columbia, territories, or other jurisdictions where required or advisable under applicable law. Such qualification shall be understood as compliance with local requirements and not as a change in legal seat, merger, public authority delegation, state agency status, territorial agency status, or creation of a separate legal entity unless expressly and lawfully recorded.
Before undertaking activities that may require qualification or registration, the Corporation shall review the nature, duration, location, and legal significance of the activity, including programs, controlled rooms, research, public authority learning, fundraising, employment, contracting, data collection, repository activity, local offices, events, and public-facing representation.
Foreign qualification or registration shall not authorize prohibited functions, including regulation, emergency command, public warning, procurement approval, certification, recognition, finance-readiness determination, capital placement, insurance approval, rating, public finance approval, or enterprise execution.
The Corporation shall maintain qualification records, exemption records, renewal records, withdrawals, jurisdictional limitations, registered agents, local notices, compliance calendars, and related correspondence.
33.13 Registered Agent and Registered Office Status. The Corporation shall maintain a registered agent and registered office as required by its governing state law and by any jurisdiction in which the Corporation is qualified or registered to do business or conduct regulated activities.
The registered agent and registered office shall be used for service of process, official notices, state correspondence, compliance communications, and other legal communications as required by law. The Corporation shall ensure continuity of registered agent service, timely handling of notices, escalation of legal communications, and preservation of related records.
Any change in registered agent or registered office shall be authorized as required by law, the constituting instrument, this Bylaw, Board resolution, or delegated authority. Such change shall be filed, recorded, and reflected in the Corporation’s legal identity records, compliance calendar, public descriptions where necessary, and internal authority records.
Failure of registered agent service, missed notices, rejected service, inaccurate registered office information, or loss of good standing shall be treated as a compliance incident requiring prompt correction and record.
33.14 Good Standing Maintenance. The Corporation shall maintain good standing in its state of incorporation and in each jurisdiction where good standing, qualification, registration, tax, charitable solicitation, employment, or other status is required for lawful activity.
Good standing maintenance shall include timely filings, fees, reports, renewals, registered agent continuity, tax compliance, annual or periodic reports, charitable solicitation renewals where applicable, state registrations, territorial registrations, foreign qualifications, employer registrations, and correction of deficiencies.
The Board, officers, Secretary, Treasurer or Chief Financial Officer, compliance function, and any delegated custodian shall ensure that good standing obligations are tracked through a compliance calendar, records register, authority matrix, and escalation process.
Loss of good standing, administrative dissolution, registration lapse, charitable solicitation lapse, tax delinquency, registered agent failure, filing deficiency, or material compliance failure shall be escalated promptly. The Corporation may suspend affected activity, restrict public descriptions, pause fundraising, pause state or territorial activity, correct filings, seek reinstatement, notify affected parties where appropriate, and preserve records of the remediation.
33.15 Corporate Status Records. The Corporation shall maintain corporate status records sufficient to demonstrate its legal existence, nonprofit status, non-stock or non-share character, non-distribution discipline, public-benefit orientation, tax status, state status, charitable solicitation status where applicable, foreign qualification status where applicable, registered agent status, registered office status, good standing, and corrections.
Corporate status records shall include, as applicable:
a) Certificate of Incorporation, Articles of Incorporation, charter, or constituting instrument;
b) amendments, restatements, certificates of correction, and filings affecting corporate existence or status;
c) bylaws, adopted versions, amendments, supersession records, and archive records;
d) state formation records and certificates of good standing;
e) registered agent and registered office records;
f) principal office and governance seat records;
g) foreign qualification, state registration, District of Columbia registration, territorial registration, and withdrawal records;
h) charitable solicitation registrations, exemptions, renewals, disclosures, and correspondence where applicable;
i) federal tax records, IRS filings, determination letters, applications, correspondence, and annual returns where applicable;
j) state tax records, franchise tax records, sales and use tax records, employer registration records, and exemption records where applicable;
k) Board resolutions, member resolutions where applicable, officer certifications, and authority records affecting status;
l) nonprofit, non-stock, non-share, non-distribution, no-private-inurement, and no-impermissible-private-benefit records;
m) support, donation, sponsorship, grant, subscription, fee, and restricted fund classification records relevant to nonprofit and tax status;
n) public description approvals concerning status;
o) corrections, withdrawals, public-safe clarifications, takedowns, retractions, supersessions, reinstatements, and remedial filings concerning status; and
p) responsible owner, custodian, authority, effective date, review date, retention class, access class, publication class, legal hold status, repository location, and metadata.
The governing rule of this Section is that the Corporation’s United States nonprofit corporate status is not merely a filing condition. It is the legal platform through which GCRI US preserves public-benefit purpose, non-distribution, anti-capture, role separation, non-execution, public authority boundary discipline, finance-boundary discipline, provider neutrality, sponsor non-control, data / AI / cyber integrity, safeguards, validity-by-record, and correctionability. No program, support arrangement, public description, Nexus interface, technical asset, controlled room, state or territorial presence, North America activity, or enterprise relationship shall be interpreted or operated in a manner that weakens that status.
Section 34. Tax-Exempt-Compatible Character and Federal Tax Status Discipline
34.1 Federal Tax Status Discipline. The Corporation shall maintain disciplined federal tax-status governance as a core condition of its United States nonprofit identity, public-benefit character, non-distribution rule, support-acceptance controls, public representations, grant eligibility, donation treatment, revenue treatment, compensation practices, conflict controls, and dissolution planning.
The Corporation’s federal tax status shall be determined, maintained, described, and changed only by competent record. No director, officer, member, non-voting member, supporter, subscriber, donor, sponsor, funder, provider, host, contractor, employee, advisor, fellow, volunteer, public authority participant, technical contributor, repository maintainer, program lead, public communications lead, AI-generated summary, public-facing deck, website, GitBook page, grant proposal, sponsorship package, donor communication, or Nexus-interface material shall represent a federal tax status not supported by current records.
The Corporation shall maintain federal tax discipline in a manner consistent with its role as a United States public-benefit technical institution and North America anchor for evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, verifiable compute methods, public authority learning, public-safe publication support, community safeguards, validity-by-record, and correctionability.
Federal tax status discipline shall not be used to soften or bypass the Corporation’s non-execution boundary, public authority boundary, finance boundary, certification boundary, procurement neutrality, provider neutrality, sponsor non-control, anti-capture discipline, data / AI / cyber controls, safeguards, or Nexus role separation.
34.2 Tax-Exempt-Compatible Purposes. The Corporation shall be operated for purposes compatible with United States nonprofit and tax-exempt or tax-exempt-compatible treatment as determined by applicable law, governing records, Board-approved strategy, and the Corporation’s constituting instrument.
Tax-exempt-compatible purposes may include scientific, educational, research, charitable, public-benefit, public-good technology, public authority learning, systemic-risk literacy, evidence stewardship, methods stewardship, open technical baseline development, public-good software stewardship, safeguards, civil rights, accessibility, data / AI / cyber public-good governance, technical literacy, workforce formation, and public-safe publication purposes, where conducted within lawful limits and without impermissible private benefit.
Tax-exempt-compatible purposes shall be interpreted strictly against private inurement, private control, commercial capture, pay-to-play access, provider preference, sponsor control, outcome purchase, finance-readiness sale, recognition sale, certification sale, procurement advantage, capital placement, emergency command, public warning authority, public authority substitution, regulated execution, or enterprise delivery.
No activity shall be treated as tax-exempt-compatible merely because it uses public-good language, Nexus language, technical vocabulary, AI governance language, climate language, resilience language, public authority language, or innovation language. The activity must be substantively aligned with the Corporation’s public-benefit purpose, supported by record, and bounded by applicable law and this Bylaw.
34.3 Public-Benefit Research and Education Character. The Corporation may conduct and support public-benefit research and education concerning systemic risk, resilience infrastructure, exponential technologies, mission-critical systems, public-good technology, evidence systems, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, public authority learning, verifiable compute, AI governance, cybersecurity, data governance, community safeguards, and public-safe reporting.
Public-benefit research and education may include whitepapers, public-safe reports, technical notes, learning briefs, academy materials, curriculum, workshops, fellowships, scenario learning, simulation materials, tabletop materials, public authority learning sessions, public-good software documentation, benchmark documentation, dataset cards, model cards, system cards, technical baselines, repository documentation, and other materials designed to advance public understanding and public-good capability.
Public-benefit research and education shall be conducted with research integrity, evidentiary discipline, uncertainty disclosure, conflict disclosure, publication review, safeguards review, data / AI / cyber review, correctionability, and public-safe communication.
No research or education activity shall be used as a disguised pathway for regulated advice, professional certification, investment recommendation, insurance approval, procurement endorsement, provider ranking, sponsor promotion, public authority decision, emergency command, public warning, or enterprise execution.
34.4 Scientific and Educational Character Where Applicable. Where the Corporation conducts scientific or educational activity, such activity shall be structured, recorded, and described in a manner consistent with applicable federal tax law, nonprofit law, research integrity expectations, public-benefit purpose, and this Bylaw.
Scientific activity may include hypothesis development, evidence collection, method development, evaluation, peer review, reproducibility work, benchmarking, uncertainty analysis, simulation, technical prototyping, validation methods, sensor-fusion methods, AI-output review methods, verifiable compute methods, observability methods, public-good software development, technical baseline drafting, and publication of public-safe findings.
Educational activity may include technical literacy, public authority literacy, data / AI / cyber literacy, evidence literacy, risk literacy, safeguards literacy, workforce formation, academy programming, fellowships, community learning, civil society learning, and public-facing explanations of complex systemic-risk and technology-governance issues.
Scientific and educational character shall be undermined by outcome purchase, sponsor veto, provider control, suppression rights, undisclosed conflicts, deceptive claims, public authority overclaim, finance overclaim, certification overclaim, procurement overclaim, or publication without correction pathway.
34.5 Charitable Status Not Assumed Without IRS Recognition or Lawful Record. The Corporation shall not represent that it is recognized as a charitable organization, Section 501(c)(3) organization, public charity, private foundation, tax-deductible donee, or holder of any other charitable federal tax status unless such status is supported by current IRS recognition, lawful record, or competent legal determination.
Where charitable status has not yet been obtained, is pending, has been denied, has been revoked, has been suspended, has lapsed, is uncertain, or is limited, all public descriptions, donor communications, grant applications, sponsorship materials, receipts, acknowledgments, websites, GitBook pages, public-facing decks, and public authority materials shall use accurate language.
No donation receipt, acknowledgment, grant statement, sponsorship material, supporter communication, public website, public-safe publication, repository notice, or AI-generated summary shall imply deductibility or charitable status unless the Corporation has authority to make that statement.
Any mistaken charitable-status statement shall be corrected promptly through amended communication, public-safe clarification, donor notice where appropriate, internal record correction, revised receipt, website correction, repository correction, or other lawful remedial action.
34.6 Section 501(c)(3) Compatibility Where Adopted or Sought. Where the Corporation adopts, seeks, maintains, or operates under Section 501(c)(3)-compatible status or recognition, the Corporation shall preserve charitable, scientific, educational, and public-benefit purposes; avoid private inurement; avoid impermissible private benefit; comply with restrictions on lobbying and political campaign intervention; maintain required records; file required returns; and operate consistently with applicable federal tax law.
Section 501(c)(3)-compatible operation shall require particular discipline over sponsorship, restricted grants, donor benefits, publication independence, research independence, public authority interactions, technical baselines, provider participation, software licensing, revenue programs, academy fees, subscription fees, fellowship support, scholarships, controlled-room access, public-good infrastructure support, and private-party participation.
No sponsor, donor, funder, provider, host, investor, insurer, lender, public finance actor, capital reader, national company, Project SPV, public authority participant, university, laboratory, contractor, employee, director, officer, member, or related party shall receive impermissible private benefit from the Corporation’s Section 501(c)(3)-compatible posture.
Where Section 501(c)(3) compatibility would be impaired by an activity, the Corporation shall decline, restructure, restrict, externalize, refer, suspend, terminate, or obtain competent review before proceeding.
34.7 Section 501(c)(4), Section 501(c)(6), Fiscal Sponsorship, Sponsored Project, Supporting Organization, or Other Structure Not Assumed Without Record. The Corporation shall not represent itself as a Section 501(c)(4) social welfare organization, Section 501(c)(6) business league, supporting organization, fiscal sponsor, sponsored project, fiscally sponsored project, public charity, private foundation, donor-advised fund sponsor, trade association, coalition vehicle, public-private partnership vehicle, or any other specialized tax or legal structure unless such structure is lawfully adopted, supported by current records, and approved for public description.
No public-benefit program, public authority interface, Nexus interface, consortium coordination, sponsorship arrangement, grant arrangement, fiscal hosting arrangement, project support arrangement, academy program, repository structure, or controlled-room activity shall be described as a fiscal sponsorship, sponsored project, supporting organization relationship, trade association function, lobbying vehicle, coalition vehicle, or business-league function unless supported by competent record.
Where a fiscal sponsorship, sponsored project, supporting organization, affiliated structure, or other tax structure is proposed, the Corporation shall conduct legal, tax, nonprofit, accounting, conflict, control, private-benefit, records, and public-description review before use.
The Corporation shall maintain clear distinctions between its own legal identity and any fiscal sponsor, sponsored project, grantee, subgrantee, partner, consortium, national company, Project SPV, Nexus entity, GCRI Canada interface, GRF interface, GRA interface, public authority, or enterprise actor.
34.8 No Private Inurement. No part of the Corporation’s net earnings, assets, revenues, grants, donations, sponsorships, restricted funds, public-good support, software assets, data assets, technical baselines, public-good repositories, intellectual property, goodwill, or other property shall inure to the benefit of any director, officer, member, founder, incorporator, donor, sponsor, funder, provider, host, contractor, employee, advisor, fellow, volunteer, related party, insider, private person, or private entity.
Private inurement shall include direct or indirect transfer of unreasonable compensation, excess benefit, inflated contract payment, below-market asset transfer, preferential licensing, unsupported reimbursement, special access, controlled-room advantage, public authority access purchase, provider preference, sponsor control, research outcome purchase, publication veto, recognition purchase, finance-readiness purchase, certification purchase, procurement advantage, or other private benefit inconsistent with the Corporation’s nonprofit and public-benefit character.
Reasonable compensation, lawful reimbursement, fair-value vendor payment, lawful grant, stipend, scholarship, award, fellowship support, program payment, licensing arrangement, or contracted service payment may be permitted where aligned with public-benefit purpose, approved under applicable controls, documented, and not excessive.
Private inurement risk shall require conflict review, related-party review, comparability review where appropriate, independent approval, recusal, documentation, limitation, correction, repayment, termination, or other remedy.
34.9 No Impermissible Private Benefit. The Corporation shall not confer impermissible private benefit on any private person or entity, whether or not an insider. Public-good activity may create incidental private benefit only where such benefit is qualitatively and quantitatively incidental to the Corporation’s public-benefit purpose and lawful under applicable tax and nonprofit rules.
Impermissible private benefit may arise through preferential provider treatment, sponsor-controlled outputs, donor-directed institutional advantage, exclusive commercial use of public-good assets, selective access to public authority learning, controlled-room access that creates market advantage, publication bias, suppressed negative findings, technical baselines designed for a single market actor, dataset access that unfairly privileges a private party, licensing terms that enclose public-good work, or Nexus-compatible claims used for market advantage without authority.
The Corporation shall structure programs, sponsorships, grants, subscriptions, fees, fellowships, academy offerings, technical baselines, public-good software releases, data rooms, controlled rooms, public authority rooms, benchmarking, challenge programs, and provider interfaces to prevent impermissible private benefit.
Where private-benefit risk cannot be managed, the Corporation shall refuse, return, restrict, re-scope, diversify, ring-fence, public-safe publish, open access where appropriate, impose fair access terms, externalize, or terminate the activity.
34.10 Lobbying and Political Activity Controls Where Applicable. The Corporation shall comply with all applicable federal, state, territorial, local, tax, nonprofit, grant, charitable solicitation, lobbying, campaign finance, government ethics, gift, and public authority rules governing lobbying, political activity, advocacy, public policy education, testimony, comments, public authority engagement, and election-related activity.
Where the Corporation is subject to Section 501(c)(3)-compatible restrictions, it shall not participate or intervene in any political campaign on behalf of or in opposition to any candidate for public office, and lobbying activity shall be limited, tracked, approved, and reported as required by law.
The Corporation may conduct nonpartisan research, public-benefit education, technical briefings, public authority learning, public-safe reporting support, scenario learning, evidence literacy, methods education, public comments, and policy-relevant technical education where lawful, nonpartisan where required, and consistent with its mission.
No director, officer, member, participant, fellow, advisor, employee, contractor, volunteer, sponsor, donor, funder, provider, host, or public authority participant shall use the Corporation’s name, assets, platform, controlled rooms, public authority interfaces, public-good software, technical baselines, publications, or Nexus references for unauthorized lobbying, partisan activity, campaign support, public authority influence, procurement influence, or political endorsement.
34.11 Unrelated Business Income Review Where Applicable. The Corporation shall review revenue-generating activity for unrelated business income, tax exposure, nonprofit compatibility, private-benefit risk, mission alignment, public description accuracy, and boundary compliance.
Activities requiring review may include sponsorships, subscriptions, academy fees, training fees, event fees, publication fees, benchmarking subscriptions, controlled-room access fees, repository access fees, software support fees, data service fees, consulting-like arrangements, technical service arrangements, licensing revenue, challenge fees, fellowship sponsorships, cost-recovery arrangements, public authority learning fees, and enterprise-facing participation fees.
Revenue activity shall not be permitted to convert the Corporation into an enterprise provider, consultancy, professional services firm, market operator, certification body, procurement body, finance-readiness body, broker, investment adviser, lender, insurer, rating agency, public finance approver, or execution vehicle.
Where unrelated business income risk or mission-drift risk exists, the Corporation may restructure the activity, limit it, route it through a lawful structure, record it as taxable where appropriate, decline it, or terminate it.
34.12 Donation Receipt Controls. Donation receipts, acknowledgments, sponsor acknowledgments, grant acknowledgments, in-kind contribution acknowledgments, restricted fund acknowledgments, and public-good support acknowledgments shall be issued only by authorized persons and only in language consistent with the Corporation’s current tax status, charitable solicitation status, donor-receipting authority, and applicable law.
No receipt shall state or imply that a contribution is tax-deductible, charitable, unrestricted, restricted, grant-like, sponsorship-like, non-charitable, exchange-value-free, or quid-pro-quo-free unless the classification is supported by record.
Where a donor, sponsor, funder, provider, host, or supporter receives goods, services, access, sponsorship benefits, acknowledgments, tickets, subscriptions, training, controlled-room access, data access, publication access, technical access, public authority learning participation, or other benefits, the Corporation shall review whether disclosure, allocation, valuation, or limitation is required.
Incorrect receipts shall be corrected promptly. The Corporation shall preserve receipt records, donor communications, classification notes, benefit descriptions, valuation support where applicable, restrictions, acknowledgment text, and corrections.
34.13 Grant and Restricted Fund Tax Controls. Grants and restricted funds shall be accepted, administered, expended, reported, and closed out in accordance with applicable law, tax rules, donor restrictions, grant terms, accounting controls, public-benefit purpose, private-benefit restrictions, conflict controls, and this Bylaw.
Restricted grants shall not be accepted where restrictions require prohibited functions, sponsor control, donor control, funder control, provider preference, outcome purchase, publication suppression, research finding purchase, recognition purchase, finance-readiness purchase, certification purchase, procurement advantage, public authority access purchase, impermissible private benefit, political activity inconsistent with status, or execution-facing conduct.
Restricted fund records shall identify donor or grantor, purpose, restriction, budget, reporting obligation, expenditure authority, responsible owner, tax treatment, private-benefit review, public authority boundary review, data / AI / cyber review where applicable, safeguards review where applicable, and closeout requirements.
Where a grant term conflicts with applicable law, tax status, constituting instrument, this Bylaw, non-execution, role separation, public authority boundaries, finance boundaries, certification boundaries, data / AI / cyber controls, safeguards, validity-by-record, or correctionability, the Corporation shall decline, amend, re-scope, suspend, return, or terminate the grant.
34.14 Sponsorship, Subscription, Fee, Training, Fellowship, Academy, Publication, and Cost-Recovery Revenue Treatment. The Corporation may receive sponsorship, subscription, fee, training, fellowship, academy, publication, controlled-room, repository, benchmarking, event, challenge, public-good software support, technical support, or cost-recovery revenue where lawful, mission-aligned, properly classified, and consistent with nonprofit and tax-status discipline.
Such revenue shall not purchase governance control, Board access, officer influence, research outcomes, publication outcomes, public authority access, controlled-room dominance, provider preference, recognition, finance-readiness, certification, procurement advantage, Nexus-compatible status, Docket status, Grid status, public legitimacy, or enterprise execution.
The Corporation shall classify each revenue stream as charitable contribution, sponsorship payment, grant, fee for service, cost recovery, subscription, program fee, training fee, fellowship support, in-kind support, restricted fund, unrestricted support, or other category as appropriate. Classification shall be supported by record and reviewed for tax, accounting, private-benefit, public-description, and boundary implications.
Fee and revenue structures shall be designed to preserve fair access where appropriate, public-benefit purpose, anti-capture discipline, competition-law compliance, public authority neutrality, provider neutrality, sponsor non-control, and public-safe claims discipline.
34.15 Cross-Border Tax Review. Cross-border activity shall be reviewed for United States federal tax implications, state tax implications, foreign tax implications where applicable, charitable solicitation rules, withholding obligations, permanent establishment risk, transfer-pricing-like concerns where relevant, foreign registration requirements, grant restrictions, donation treatment, data transfer obligations, sanctions, export controls, and local law.
Cross-border activity may include coordination with GCRI Canada, Mexico, Caribbean, Arctic, Indigenous, regional, or international interfaces; foreign public authority learning; cross-border evidence architecture; cross-border datasets; cross-border public-good software development; cross-border grants; foreign donations; sponsorships; events; fellowships; contractor engagements; cloud or repository hosting; and Nexus-interface activity.
Cross-border tax review shall not imply foreign legal merger, foreign branch status, treaty status, intergovernmental status, public authority status, foreign public finance authority, or cross-border enterprise execution status.
Where cross-border tax or legal uncertainty exists, the Corporation shall apply a protective lawful posture, including localization, compartmentalization, separate instrument, foreign counsel review, U.S. counsel review, suspension, re-scope, externalization, or refusal.
34.16 Tax Status Change Controls. Any proposed change to the Corporation’s federal tax status, state tax status, charitable status, public charity status, private foundation status, fiscal sponsorship status, supporting organization status, lobbying election, donation receipting authority, unrelated business income posture, tax reporting approach, or other material tax classification shall be treated as a material or constitutional matter unless the Board determines otherwise by recorded act consistent with applicable law.
Tax status change controls shall require review of legal authority, tax consequences, public-benefit purpose, nonprofit status, donor and sponsor communications, grant obligations, public authority materials, public descriptions, controlled-room terms, subscription terms, fee structures, dissolution provisions, private-benefit risks, political activity limits, lobbying limits, state and territorial registration effects, and Nexus-interface implications.
No officer, committee, council, working group, sponsor, donor, funder, provider, host, public authority participant, external accountant, public-facing communication, AI-generated summary, website update, grant application, or operational practice shall change or imply a change in tax status without Board authority and required records.
Upon any tax status change, the Corporation shall update public descriptions, receipts, grant materials, sponsorship materials, donation materials, accounting records, compliance calendars, state registrations, charitable solicitation records, repository notices where needed, and public-safe summaries.
34.17 Tax Status Records. The Corporation shall maintain tax status records sufficient to demonstrate the basis, limits, representations, compliance, changes, corrections, and public descriptions of its federal, state, territorial, local, and cross-border tax status.
Tax status records shall include, as applicable:
a) federal employer identification number records;
b) IRS applications, determination letters, acknowledgment notices, correspondence, annual returns, exemption records, revocation or reinstatement records, and tax-status memoranda;
c) state tax registrations, exemption records, franchise tax records, sales and use tax records, employer tax records, and state correspondence;
d) charitable solicitation registrations, exemptions, renewals, disclosures, and filings;
e) donation receipts, acknowledgments, sponsorship acknowledgments, in-kind contribution records, restricted fund records, and benefit valuation records;
f) grant records, restricted fund records, public support records, donor communications, and grantor communications;
g) sponsorship, subscription, fee, academy, training, fellowship, publication, controlled-room, repository, benchmarking, event, challenge, and cost-recovery revenue classification records;
h) unrelated business income review records;
i) lobbying, political activity, public policy education, public comment, testimony, and public authority engagement classification records where applicable;
j) private inurement, excess benefit, impermissible private benefit, related-party, comparability, conflict, and independent approval records;
k) cross-border tax review records, withholding records, foreign registration records, foreign counsel records where applicable, and compatibility notes;
l) tax status change records, Board approvals, member approvals where required, transition rules, public description updates, receipt updates, and donor or sponsor notices;
m) corrections, restatements, amended receipts, amended returns, public-safe clarifications, withdrawals, supersessions, and remedial filings; and
n) responsible owner, custodian, authority, effective date, review date, retention class, access class, publication class, legal hold status, repository location, and metadata.
The governing rule of this Section is that tax status is a governance discipline, not a marketing claim. The Corporation’s federal tax posture shall be supported by record, constrained by law, aligned with public-benefit purpose, protected from private inurement and impermissible private benefit, and integrated with non-execution, role separation, public authority boundary discipline, finance-boundary discipline, certification and procurement boundary discipline, provider neutrality, sponsor non-control, safeguards, validity-by-record, and correctionability.
Section 35. United States Public-Benefit Character
35.1 Public-Benefit Character. The Corporation shall be organized, governed, operated, represented, and interpreted as a United States public-benefit nonprofit institution dedicated to lawful public-good purposes. Its public-benefit character shall be a controlling condition of its legal identity, corporate powers, tax-exempt or tax-exempt-compatible posture, program design, treasury, records, public descriptions, public authority interfaces, sponsorships, grants, donations, technical assets, controlled rooms, publications, and Nexus-compatible relationships.
The Corporation’s public-benefit character shall require that all activities be directed toward public-good evidence, methods, observability, ontology, technical truth, public-good research and development, public-good software, open technical baselines, verifiable compute methods, public authority learning, public-safe publication support, community safeguards, civil rights, accessibility, correctionability, validity-by-record, and systemic de-risking across the United States and, where lawfully structured, North America.
The Corporation shall not be operated for the private benefit of directors, officers, members, founders, donors, sponsors, funders, providers, hosts, contractors, employees, advisors, fellows, volunteers, public authority participants, investors, insurers, lenders, capital readers, national companies, Project SPVs, enterprise actors, or any other private person. Public benefit shall control over institutional convenience, sponsor preference, provider preference, market opportunity, fundraising opportunity, public authority interest, capital-reader interest, technical novelty, publication speed, reputational advantage, or Nexus-interface convenience.
The Corporation’s public-benefit character shall be preserved through Board oversight, officer duties, conflict controls, support-acceptance review, public-safe claims discipline, public authority boundary discipline, finance-boundary discipline, certification-boundary discipline, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards review, records discipline, and correction pathways.
35.2 Public-Good Mission. The mission of the Corporation shall be to advance public-good capability for understanding, evidencing, governing, and de-risking systemic risks and exponential technologies through disciplined public-benefit methods, research, education, technical stewardship, observability, public-good software, open technical baselines, and public authority learning.
The public-good mission shall include support for all relevant domains of systemic risk and exponential technology, including AI, AI-RAN, O-RAN, private wireless, DePIN, distributed ledger technology, blockchain, Web3, quantum-relevant systems, high-performance computing, sovereign compute, cybersecurity, robotics, drones, sensing systems, geospatial systems, Earth observation, digital twins, biosecurity, climate, nature, biodiversity, energy, water, food, health, disaster resilience, telecommunications, supply chains, ports, borders, advanced manufacturing, semiconductors, mission-critical infrastructure, and future exponential technologies.
The public-good mission shall not authorize the Corporation to act as a regulator, emergency command body, public warning authority, public authority, public finance approver, procurement authority, certification body, accreditation body, recognition body, registry steward where reserved to The Global Risks Forum (GRF), finance-readiness steward where reserved to The Global Risks Alliance (GRA), fund, broker, dealer, investment adviser, lender, insurer, rating agency, national company, Project SPV, provider, operator, asset owner, deployment company, or enterprise execution vehicle.
The Corporation may translate research, evidence, methods, technical baselines, and public-good software into public-benefit learning and usable public-good tools, provided that such translation remains non-executing, record-supported, public-safe, role-separated, and correctionable.
35.3 Public Trust Orientation. The Corporation shall maintain a public trust orientation in all governance, programs, publications, technical assets, public authority interfaces, sponsor relationships, provider relationships, donor relationships, controlled rooms, data rooms, evidence rooms, repositories, and Nexus interfaces.
Public trust orientation shall require transparency where lawful and safe, accuracy, controlled vocabulary, conflict disclosure, independence, correctionability, public-safe limitations, records integrity, non-exaggeration of authority, respect for vulnerable and affected communities, and careful distinction between evidence, method, recognition, finance-readiness, certification, procurement, public authority action, and execution.
The Corporation shall not trade public trust for funding, publicity, access, speed, provider support, sponsor support, political convenience, public authority proximity, market relevance, capital-reader interest, or technical influence. Where public trust and institutional opportunity conflict, the Corporation shall apply the more protective public-benefit interpretation.
Public trust orientation shall require the Corporation to correct public-facing confusion promptly, including confusion regarding legal identity, tax status, public authority status, finance-readiness, certification, recognition, procurement, provider preference, sponsor control, Nexus-compatible status, automated outputs, proof receipts, dashboards, AI systems, digital twins, DePIN records, DLT entries, AI-RAN signals, or other technical artifacts.
35.4 Public Safety Support Without Emergency Command. The Corporation may support public safety through evidence literacy, technical literacy, scenario learning, observability methods, public-safe reporting literacy, data / AI / cyber methods, public authority learning, resilience indicators, systemic-risk methods, and post-event learning, provided that such support does not constitute emergency command, incident command, dispatch, evacuation instruction, public warning, public health order, safety command, operational control, or replacement of competent public authorities.
Public safety support may include research, simulations, tabletop support, public-safe publications, after-action learning, evidence synthesis, methods notes, technical baselines, public-good software tools, controlled-room learning environments, and public authority learning sessions. Such support shall be framed as public-benefit learning or technical support and shall not be represented as official emergency instruction.
No dashboard, map, digital twin, model output, AI inference, AI-RAN signal, O-RAN signal, DePIN record, blockchain or ledger entry, sensor signal, observability node, proof receipt, public-safe report, public authority room, controlled-room exchange, or technical baseline shall be treated as an official public warning, emergency command, safety order, public health order, evacuation notice, dispatch instruction, or operational resource direction by reason of its existence or use within the Corporation’s systems.
Where public safety support creates risk of public confusion, the Corporation shall use clear limitation language, restrict access, delay publication, aggregate or redact outputs, coordinate with competent public authorities where lawful, and preserve records of the decision.
35.5 Public Authority Learning Support Without Public Authority Substitution. The Corporation may support federal, state, District of Columbia, territorial, Tribal-interface, Indigenous governance, local, municipal, county, metropolitan, port, utility, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, infrastructure, public finance reader, and regulator-listening participants through public authority learning and technical literacy.
Public authority learning may include briefings, workshops, tabletop exercises, scenario materials, technical baselines, evidence literacy, data / AI / cyber literacy, public-safe reporting literacy, public-good software demonstrations, observability methods, Nexus Observatory methods, Nexus Truth Engine methods, verifiable compute methods, and controlled-room learning.
Such learning shall not constitute delegation of governmental authority, public authority adoption, procurement approval, funding approval, public finance approval, regulatory approval, emergency command, official public warning, sovereign obligation, public-private partnership, permit, compliance determination, certification, recognition, or governmental decision unless separately and lawfully recorded by the competent public authority.
The Corporation shall classify public authority capacity, maintain public authority participation records, use public authority reference controls, protect public-sector data, respect public records and open meetings sensitivities where applicable, and correct public authority confusion promptly.
35.6 Community Safeguards and Rights-Respecting Purpose. The Corporation’s public-benefit character shall include a standing duty to respect communities, Tribal Nations, Indigenous governments, Indigenous knowledge holders, local knowledge holders, territorial communities, vulnerable communities, remote communities, civil society participants, research participants, and persons affected by observability, evidence collection, public-safe mapping, data systems, AI systems, digital twins, public authority learning, and publication activity.
Community safeguards and rights-respecting purpose shall include respect for Tribal sovereignty, Indigenous governance, Indigenous data governance, protected knowledge, local knowledge, consent and non-consent pathways where applicable, withdrawal pathways where applicable, attribution requirements, confidentiality, non-retaliation, grievance and remedy pathways, accessibility, civil rights, non-discrimination, public-safe mapping limits, do-no-harm review, and protection against extractive use of knowledge.
The Corporation shall not collect, expose, commercialize, train models on, map, infer, publish, or route protected knowledge for sponsor convenience, provider convenience, donor convenience, funder convenience, institutional convenience, public authority convenience, media convenience, technical convenience, or AI convenience.
Where safeguards risk exists, the Corporation shall apply the more protective posture, including non-public treatment, aggregation, redaction, restricted access, community review, Tribal-interface review, Indigenous governance review, delay, withdrawal, sealing, correction, or termination.
35.7 Scientific, Technical, Educational, Research, and Public-Good Technology Purpose. The Corporation may conduct scientific, technical, educational, research, and public-good technology activities in furtherance of its public-benefit mission. Such activities may include applied research, evidence synthesis, method development, technical prototyping, public-good software development, open technical baseline drafting, public authority learning, academy programs, fellowships, educational materials, standards-support inputs, observability methods, verifiable compute methods, Nexus Truth Engine methods, Nexus Observatory methods, and public-safe publications.
Scientific and technical purpose shall be exercised with research integrity, reproducibility where appropriate, source lineage, uncertainty disclosure, validation methods, peer or expert review where appropriate, data / AI / cyber controls, safeguards review, publication discipline, and correctionability.
Educational purpose shall be exercised through public-benefit learning and technical literacy and shall not be used to create professional licensure, regulated credentials, certification, accreditation, procurement status, finance-readiness status, public authority approval, recognition, or provider preference unless separately and lawfully authorized by a competent body.
Public-good technology purpose shall not convert the Corporation into a software vendor, systems integrator, cloud provider, telecom operator, asset owner, infrastructure operator, managed services provider, national company, Project SPV, or enterprise execution vehicle. The Corporation may create and steward public-good technology assets, but such assets shall remain subject to non-execution, public-safe claims, secure release, licensing, anti-enclosure, and correction controls.
35.8 Systemic De-Risking Purpose. The Corporation shall advance systemic de-risking by improving the quality, comparability, traceability, accessibility, and correctionability of evidence, methods, observability, technical baselines, public authority learning, public-good software, and public-safe communication concerning systemic risks and mission-critical technologies.
Systemic de-risking may include work on climate risk, disaster risk, cyber risk, AI risk, infrastructure risk, supply-chain risk, public health risk, biosecurity risk, energy risk, water risk, food risk, biodiversity risk, telecom risk, digital infrastructure risk, compute risk, model risk, data risk, geospatial risk, border and port risk, public trust risk, and other interconnected risks that require cross-sector evidence and methods.
Systemic de-risking shall not be represented as risk elimination, guarantee, insurance approval, bankability, financeability, rating, compliance approval, certification, procurement approval, public authority decision, public warning, emergency command, or operational control.
The Corporation shall maintain uncertainty statements, limitation language, method records, version records, correction pathways, and public-safe presentation controls for systemic de-risking outputs.
35.9 Evidence Integrity Purpose. The Corporation shall preserve evidence integrity as a central public-benefit purpose. Evidence integrity shall require attention to source lineage, provenance, custody, data quality, uncertainty, corroboration, validation, limitation, classification, public-safe status, versioning, accessibility, reproducibility where appropriate, and correctionability.
Evidence integrity shall apply to documents, datasets, sensor signals, AI outputs, model results, digital twin outputs, geospatial layers, Earth observation materials, cyber telemetry, AI-RAN and O-RAN signals, DePIN records, DLT or blockchain records, public authority submissions, community inputs, protected knowledge materials, research outputs, public-safe reports, technical baselines, and proof receipts.
No evidence artifact shall be treated as final authority merely because it is technical, automated, signed, hashed, timestamped, placed in a repository, entered into a ledger, displayed on a dashboard, referenced by a public authority participant, cited by a sponsor, used by a provider, or routed through a Nexus-compatible interface.
Evidence integrity shall be enforced through records, review, controlled vocabulary, limitation language, correction pathways, withdrawal authority, supersession authority, and public-safe publication discipline.
35.10 Methods Integrity Purpose. The Corporation shall preserve methods integrity as a central public-benefit purpose. Methods integrity shall require that methods used by the Corporation be described, versioned, bounded, reviewed, recorded, corrected, superseded, withdrawn, or retired as appropriate.
Methods integrity shall apply to validation methods, confidence scoring, uncertainty handling, source comparison, sensor fusion, AI-output review, AI-RAN and O-RAN signal interpretation, DePIN validation, DLT validation, digital twin assumption review, geospatial methods, cyber evidence methods, verifiable compute methods, public-safe publication methods, safeguards methods, and correction methods.
No method shall be treated as certification, procurement approval, regulatory approval, public authority decision, recognition, finance-readiness determination, insurance-readiness determination, rating, public warning, emergency command, or operational instruction unless separately and lawfully issued by the competent body.
Methods integrity shall require transparent limitation language, appropriate review, public-safe publication classification, version control, applicability statements, exclusions, records of known defects, and correction pathways.
35.11 Open Technical Baseline Purpose. The Corporation may develop, maintain, publish, revise, localize, supersede, withdraw, or archive open technical baselines to support public-benefit learning, interoperability, evidence quality, data governance, AI governance, cybersecurity, observability, public authority literacy, public-good software, verifiable compute, safeguards, and systemic de-risking.
Open technical baselines shall be understood as public-good technical guidance or reference baselines unless a competent authority has separately and lawfully adopted a different status. They shall not be represented as mandatory standards, legal requirements, regulatory requirements, procurement requirements, certification criteria, recognition criteria, finance-readiness requirements, insurance-readiness requirements, Nexus-wide protocol mandates, GRF determinations, GRA determinations, or public authority determinations.
Open technical baselines shall include status, version, scope, limitations, authority, custodian, public-safe classification, data / AI / cyber considerations, safeguards considerations, correction pathway, effective date, review cycle, and supersession information where appropriate.
Where an open technical baseline is used by GRF, GRA, Nexus Standards, a public authority, consortium, national company, Project SPV, provider, sponsor, host, university, laboratory, or community, such use shall not alter the Corporation’s role unless separately and lawfully recorded.
35.12 Public-Good Software Purpose. The Corporation may develop, maintain, publish, license, restrict, secure, deprecate, withdraw, or archive public-good software and related technical assets in furtherance of its public-benefit mission.
Public-good software may include tools, schemas, APIs, SDKs, dashboards, data tools, reference architectures, model cards, system cards, dataset cards, evaluation tools, test harnesses, benchmark libraries, observability tools, public authority learning tools, verifiable compute tools, evidence tools, public-safe publication tools, and technical baselines.
Public-good software shall be managed under secure development, repository governance, licensing, contribution, vulnerability management, SBOM, signing, provenance, access-control, data / AI / cyber, export-control, sanctions, controlled-technology, IP, public-safe claims, and correction controls.
No public-good software release, reference implementation, technical asset, dashboard, model, API, SDK, test harness, or proof-receipt tool shall constitute certification, procurement approval, public authority adoption, finance-readiness, insurance-readiness, recognition, provider preference, rating, public warning, emergency command, or operational control.
35.13 AI, Cyber, Data, Observability, and Verifiable Compute Public-Good Purpose. The Corporation shall advance public-good purposes concerning AI, cyber, data governance, observability, and verifiable compute by developing methods, literacy, technical baselines, evidence records, model governance practices, inference records, compute workload records, public-safe outputs, and correctionable technical memory.
AI public-good purpose shall include AI governance, model evaluation, system cards, model cards, dataset cards, inference records, human review for material outputs, agentic AI controls, AI-output limitation language, and correction pathways.
Cyber public-good purpose shall include secure development, vulnerability management, incident response methods, repository security, identity and access controls, infrastructure-sensitive information controls, controlled-room rules, and cyber-safe publication discipline.
Data and observability public-good purpose shall include data minimization, lawful basis where applicable, access controls, retention and deletion rules, public authority data controls, community-protected data controls, Indigenous data safeguards, sensor and signal methods, geospatial and Earth observation methods, digital twin assumption review, degraded-mode awareness, and public-safe mapping.
Verifiable compute purpose shall include compute workload records, secure enclaves, confidential computing where appropriate, sovereign compute considerations, proof receipts, auditability, model and inference records, and human review for material outputs. No AI, cyber, data, observability, or compute output shall be authority without competent record, classification, limitation, and correction pathway.
35.14 Civil Rights, Accessibility, Indigenous Knowledge, Community Protection, and Public-Safe Communication Orientation. The Corporation shall conduct its activities with orientation toward civil rights, accessibility, Indigenous knowledge respect, community protection, protected knowledge safeguards, non-discrimination, protected participation, non-retaliation, and public-safe communication.
Civil rights and accessibility orientation shall require the Corporation to consider inclusion, accessible formats, language access where approved, reasonable participation accommodations where applicable, nondiscrimination, avoidance of disparate harm, respectful engagement, and complaint pathways.
Indigenous knowledge and community protection orientation shall require respect for Tribal sovereignty, Indigenous governance, Indigenous data governance, local and territorial knowledge, protected knowledge classifications, consent and non-consent pathways where applicable, attribution, confidentiality, withdrawal, correction, and non-extractive handling.
Public-safe communication orientation shall require the Corporation to present technical outputs, evidence, dashboards, maps, AI outputs, risk summaries, public authority materials, sponsor materials, provider materials, public-good software, technical baselines, and Nexus-interface materials in a manner that avoids panic, false certainty, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider preference, sponsor control, protected knowledge exposure, cybersecurity exposure, or operational misuse.
35.15 Public-Benefit Purpose Records. The Corporation shall maintain public-benefit purpose records sufficient to demonstrate that its programs, powers, assets, revenues, relationships, publications, technical assets, public authority interfaces, support arrangements, and Nexus-compatible activities are aligned with public-benefit purpose and constrained by applicable law, nonprofit character, tax-exempt or tax-exempt-compatible status, non-execution, role separation, safeguards, validity-by-record, and correctionability.
Public-benefit purpose records shall include, as applicable:
a) corporate purpose records;
b) Board resolutions and officer approvals concerning public-benefit purpose;
c) program purpose records;
d) research, education, evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, public authority learning, safeguards, and public-safe publication purpose records;
e) public authority learning capacity records;
f) community safeguards, Tribal / Indigenous, local, territorial, civil rights, accessibility, protected knowledge, and public-safe mapping records;
g) tax-exempt or tax-exempt-compatible purpose records;
h) private inurement, private benefit, excess benefit, conflict, related-party, support-acceptance, sponsorship, grant, donation, and fee-classification records;
i) public-safe claims records;
j) non-execution, public authority boundary, finance boundary, certification boundary, procurement neutrality, provider neutrality, sponsor non-control, and anti-capture records;
k) data / AI / cyber / privacy, verifiable compute, observability, model, inference, dashboard, signal, and automated-output boundary records;
l) Nexus public-good stack compatibility records;
m) GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, consortium, national company, Project SPV, provider, sponsor, host, university, laboratory, public authority, and enterprise-interface records;
n) corrections, withdrawals, retractions, takedowns, supersessions, public-safe clarifications, and restatements affecting public-benefit purpose; and
o) responsible owner, custodian, authority, effective date, review date, retention class, access class, publication class, legal hold status, repository location, and metadata.
The governing rule of this Section is that the Corporation’s public-benefit character shall govern every use of its name, powers, treasury, records, technical assets, public authority relationships, support relationships, research outputs, software releases, open technical baselines, public-safe publications, controlled rooms, and Nexus-interface activities. No activity shall be validly conducted by or through the Corporation unless it can be defended as a lawful, record-supported, non-executing, role-separated, public-benefit activity consistent with this Bylaw.
Section 36. United States All-States-and-Territories Character
36.1 All-States-and-Territories Character. The Corporation shall be organized, governed, represented, and operated as a United States public-benefit nonprofit institution with a lawful all-states-and-territories character. This character shall mean that the Corporation may, subject to applicable law, Board authority, officer delegation, tax status, state and territorial compliance, charitable solicitation rules, public authority boundary discipline, data / AI / cyber controls, community safeguards, and this Bylaw, conduct public-benefit activities across the United States, including all fifty states, the District of Columbia, Puerto Rico, Guam, the U.S. Virgin Islands, American Samoa, the Northern Mariana Islands, Tribal-interface contexts, Indigenous governance interfaces, local jurisdictions, metropolitan regions, public authority settings, and mission-critical infrastructure contexts.
The all-states-and-territories character shall not create automatic authority to operate in any jurisdiction without review. It shall instead establish the Corporation’s lawful institutional posture: GCRI US may serve as a United States-wide evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, verifiable compute, public authority learning, and safeguards institution only where its activity is properly authorized, classified, localized, recorded, and compliant with applicable federal, state, territorial, Tribal-interface, local, tax, employment, privacy, AI, cyber, public records, procurement, grant, lobbying, charitable solicitation, and contracting requirements.
The all-states-and-territories character shall not fragment the Corporation into separate state or territorial legal persons, public authorities, state agencies, territorial agencies, procurement bodies, certification bodies, recognition bodies, finance-readiness bodies, providers, operators, national companies, Project SPVs, or execution vehicles. State-specific or territorial presence shall be treated as localized activity of the Corporation unless a separate legal entity is lawfully created by competent instrument.
36.2 Fifty-State Applicability. The Corporation may conduct lawful public-benefit activities in or relating to any of the fifty states of the United States, subject to applicable qualification, registration, tax, charitable solicitation, employment, data, AI, cyber, public authority, public records, procurement, lobbying, grant, contracting, civil rights, accessibility, research ethics, and safeguards requirements.
Fifty-state applicability may include public-benefit research, evidence mapping, methods development, public authority learning, technical literacy, observability methods, public-good software development, open technical baseline localization, public-safe publication, state interface support, academy programming, fellowships, controlled-room participation, data-room participation, university and laboratory coordination, community safeguards engagement, sponsor and donor support, provider-neutral technical input, and Nexus-compatible public-good stack alignment.
No state-facing activity shall be represented as state approval, state funding approval, state procurement approval, regulatory adoption, public finance approval, emergency command, public warning, certification, recognition, finance-readiness, or official state action unless separately and lawfully recorded by the competent state authority.
Where a state-specific activity may trigger legal obligations, the Corporation shall review the activity before launch, record the review, and apply the most protective lawful posture pending resolution.
36.3 District of Columbia Applicability. The Corporation may conduct lawful public-benefit activities in or relating to the District of Columbia, including federal public authority learning, policy-relevant technical education, nonprofit operations, public-good research, events, controlled-room sessions, public authority interface activity, academic collaboration, public-safe publication, and Nexus-compatible public-good coordination, subject to applicable District of Columbia and federal law.
District of Columbia applicability shall be especially sensitive to public authority boundaries, lobbying and political activity rules, government ethics, gifts, procurement integrity, grant compliance, public authority reference controls, charitable solicitation requirements, tax registrations, employment rules, privacy and cybersecurity requirements, and public-facing description discipline.
The Corporation shall not use District of Columbia presence, federal proximity, public authority participation, public policy engagement, public finance reader attendance, regulator-listening participation, or government-adjacent convening to imply federal endorsement, District approval, regulatory authority, public finance authority, procurement advantage, official public-private partnership, sovereign obligation, public warning authority, or emergency command authority.
All District of Columbia activity shall remain subject to capacity classification, non-reliance language, public-safe claims discipline, and records sufficient to distinguish public-benefit learning from public authority action.
36.4 Puerto Rico Applicability. The Corporation may conduct lawful public-benefit activities in or relating to Puerto Rico, including disaster resilience, climate, energy, water, food, telecom, cyber, ports, public health, infrastructure, community safeguards, public authority learning, observability methods, and public-safe publication support, subject to applicable federal, Puerto Rico, municipal, tax, employment, procurement-sensitive, charitable solicitation, privacy, data, AI, cyber, civil rights, accessibility, language, and safeguards requirements.
Puerto Rico applicability shall require localization that respects the territory’s legal, linguistic, cultural, infrastructure, climate, disaster, public authority, and community contexts. Spanish-language materials, accessibility materials, local explanatory notes, or public-safe summaries may be used where approved, provided that English remains the authoritative Bylaw text unless otherwise lawfully adopted.
No Puerto Rico-facing activity shall imply territorial government endorsement, public authority delegation, emergency command, official public warning, procurement approval, funding approval, regulatory approval, certification, recognition, finance-readiness, or operational control.
Where Puerto Rico activity involves vulnerable communities, disaster-exposed communities, infrastructure-sensitive data, public authority data, protected knowledge, or public-safe mapping, the Corporation shall apply heightened safeguards and documented review.
36.5 Guam Applicability. The Corporation may conduct lawful public-benefit activities in or relating to Guam, including climate, disaster, public health, telecom, cyber, supply chain, port, defense-sensitive, infrastructure, community safeguards, public authority learning, observability methods, and technical baseline support, subject to applicable federal, territorial, local, tax, employment, charitable solicitation, data, AI, cyber, national security, controlled-technology, public authority, civil rights, accessibility, and safeguards requirements.
Guam applicability shall require particular attention to territorial law, critical infrastructure sensitivity, defense and national security sensitivity where applicable, cross-Pacific logistics, telecommunications resilience, community safeguards, and public-safe communication.
No Guam-facing activity shall imply territorial public authority delegation, federal defense authority, emergency command, public warning authority, procurement approval, public finance approval, certification, recognition, finance-readiness, provider preference, or operational control.
The Corporation shall maintain records of any territorial localization, capacity classification, public authority interface, protected knowledge review, public-safe publication review, and cross-border or Pacific-interface compatibility note.
36.6 U.S. Virgin Islands Applicability. The Corporation may conduct lawful public-benefit activities in or relating to the U.S. Virgin Islands, including climate resilience, hurricane and disaster learning, energy, water, food, public health, ports, telecom, cyber, tourism-economy resilience, infrastructure, public authority learning, community safeguards, observability methods, and public-safe publication support, subject to applicable federal, territorial, local, tax, employment, charitable solicitation, data, AI, cyber, civil rights, accessibility, public authority, and safeguards requirements.
U.S. Virgin Islands applicability shall require localization sensitive to island infrastructure, disaster exposure, water and energy systems, supply-chain dependencies, public authority capacity, and local community safeguards.
The Corporation shall not represent territorial participation, public authority attendance, technical mapping, observability outputs, dashboards, public-safe reports, or controlled-room activity as territorial adoption, emergency instruction, public warning, public finance approval, procurement approval, certification, recognition, or finance-readiness.
Where public-facing materials concern disaster, infrastructure, public health, or sensitive community conditions, the Corporation shall ensure public-safe communication, limitation language, non-reliance language, and correction pathways.
36.7 American Samoa Applicability. The Corporation may conduct lawful public-benefit activities in or relating to American Samoa, subject to applicable federal, territorial, local, cultural, community, tax, employment, charitable solicitation, data, AI, cyber, public authority, civil rights, accessibility, and safeguards requirements.
American Samoa applicability shall require heightened respect for local governance, cultural context, community protocols, protected knowledge, language needs, remote-island infrastructure conditions, climate and disaster exposure, public health context, and public-safe communication.
No activity of the Corporation in or relating to American Samoa shall imply territorial government authority, public authority delegation, public warning, emergency command, procurement approval, funding approval, regulatory approval, certification, recognition, finance-readiness, provider preference, or operational control.
Where American Samoa activity involves community knowledge, local knowledge, cultural knowledge, public health information, infrastructure-sensitive information, public-safe mapping, or public authority data, the Corporation shall apply safeguards review, public authority capacity classification, access restrictions where needed, and records sufficient to support validity-by-record and correctionability.
36.8 Northern Mariana Islands Applicability. The Corporation may conduct lawful public-benefit activities in or relating to the Northern Mariana Islands, including climate, disaster, telecom, cyber, public health, infrastructure, ports, supply chains, community safeguards, public authority learning, observability methods, and public-safe publication support, subject to applicable federal, territorial, local, tax, employment, charitable solicitation, data, AI, cyber, public authority, civil rights, accessibility, and safeguards requirements.
Northern Mariana Islands applicability shall require localization sensitive to island infrastructure, remote logistics, disaster exposure, cultural and community context, public authority capacity, and public-safe communication.
No activity of the Corporation in or relating to the Northern Mariana Islands shall be represented as territorial adoption, public authority delegation, public warning, emergency command, procurement approval, funding approval, regulatory approval, certification, recognition, finance-readiness, provider preference, or operational control.
The Corporation shall maintain records of territorial review, public authority capacity, data and safeguards controls, public-safe communication review, and any compatibility notes needed to preserve the Corporation’s United States seat and non-execution status.
36.9 Federal Interface Applicability. The Corporation may engage with federal departments, agencies, offices, laboratories, public corporations, federally funded research and development centers where applicable, public finance readers, regulators in regulator-listening capacity, emergency management participants, public health participants, infrastructure participants, and other federal public authority participants for public-benefit learning, evidence literacy, methods literacy, public-safe reporting literacy, technical education, research, observability methods, public-good software, and technical baseline support.
Federal interface applicability shall not create federal delegation, federal endorsement, federal procurement approval, federal funding approval, public finance approval, regulatory safe harbor, official public warning, emergency command, public authority decision, or sovereign obligation.
The Corporation shall classify federal participant capacity, maintain federal interface records, respect federal ethics, gift, procurement, grant, lobbying, public records, confidentiality, data, AI, cyber, national security, controlled-technology, export-control, and sanctions-related requirements where applicable, and use approved public description language.
Federal participation in any meeting, room, report, simulation, technical baseline, dashboard, data room, public-safe publication, or Nexus-compatible activity shall not be described as official adoption unless the competent federal authority has separately and lawfully issued such adoption by record.
36.10 State Interface Applicability. The Corporation may engage with state public authorities, state universities, state laboratories, state public corporations, state infrastructure actors, state emergency management participants, state public health participants, state public safety participants, state telecom, energy, water, food, cyber, public works, transportation, port, environmental, climate, disaster, finance, and regulator-listening participants in support of public-benefit learning and technical literacy.
State interface applicability shall require careful attention to state law, public records laws, sunshine and open meetings concerns where applicable, procurement restrictions, lobbying and government ethics rules, gift rules, grant rules, tax and registration requirements, charitable solicitation rules, privacy and cybersecurity rules, civil rights and accessibility requirements, and public authority capacity classifications.
No state interface shall create state endorsement, state public authority delegation, public warning, emergency command, procurement approval, public finance approval, funding approval, regulatory approval, certification, recognition, finance-readiness, provider preference, or execution authority.
The Corporation shall maintain state interface records sufficient to identify the state, participating body, participant capacity, activity purpose, applicable limitations, public-safe language, records restrictions, and correction pathway.
36.11 Territorial Interface Applicability. The Corporation may engage with territorial public authorities, territorial universities, territorial laboratories, territorial infrastructure actors, territorial emergency management participants, territorial public health and public safety participants, territorial utilities, ports, telecom, energy, water, food, cyber, climate, disaster, and community bodies in support of public-benefit learning and technical literacy.
Territorial interface applicability shall require localization to territorial law, language, infrastructure context, public authority structure, community safeguards, climate and disaster exposure, public-safe communication, charitable solicitation, tax, employment, data, AI, cyber, civil rights, accessibility, and records requirements.
Territorial participation shall not imply territorial public authority delegation, public warning, emergency command, public finance approval, procurement approval, funding approval, regulatory approval, certification, recognition, finance-readiness, provider preference, or operational control.
The Corporation shall record territorial interfaces, capacity classifications, limitations, data controls, public-safe publication reviews, and safeguards determinations.
36.12 Tribal and Indigenous Interface Applicability. The Corporation may engage with Tribal Nations, Indigenous governments, Indigenous knowledge holders, Indigenous data stewards, Native organizations, community bodies, and other Indigenous-interface participants only where lawfully, respectfully, and appropriately structured.
Tribal and Indigenous interface applicability shall require respect for Tribal sovereignty, Indigenous governance, Indigenous data governance, Indigenous knowledge protocols, consent and non-consent pathways where applicable, attribution, withdrawal, confidentiality, protected knowledge restrictions, community-defined limitations, cultural protocols, public-safe mapping restrictions, grievance pathways, and non-retaliation.
No Tribal or Indigenous interface shall be interpreted as GCRI US authority over Tribal governance, Indigenous governance, Indigenous knowledge, Indigenous data, protected knowledge, land, resources, public authority decisions, emergency management, public warning, certification, recognition, finance-readiness, procurement, or execution.
The Corporation shall not assume consent from participation, attendance, public statements, public information, technical availability, map availability, dataset availability, public authority interest, sponsor interest, provider interest, or Nexus-interface need. Consent, non-consent, withdrawal, restriction, attribution, and correction shall be handled by record where applicable.
Tribal and Indigenous interface records shall include capacity, scope, permissions, restrictions, protected knowledge classifications, data conditions, publication limits, responsible custodians, review dates, correction pathways, and any compatibility or divergence notes.
36.13 Local, County, Municipal, Metropolitan, Utility, Port, Public Health, Emergency Management, Public Safety, Public Works, Telecom, Energy, Water, Food, Cyber, and Infrastructure Interface Applicability. The Corporation may engage with local, county, municipal, metropolitan, regional, utility, port, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, transportation, environmental, school, hospital, infrastructure, and other mission-relevant local or sectoral interfaces in support of public-benefit learning, evidence literacy, technical literacy, observability methods, safeguards, and public-safe communication.
Such local and sectoral interfaces shall be governed by public authority boundary discipline, local law, public records and open meetings sensitivities where applicable, procurement restrictions, grant requirements, data-sharing rules, privacy and cybersecurity controls, public health and safety rules, infrastructure-sensitive information controls, community safeguards, civil rights, accessibility, and public-safe mapping requirements.
No local, utility, port, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, or infrastructure interface shall create operational control, emergency command, public warning, dispatch authority, resource direction, procurement approval, provider selection, public finance approval, regulatory approval, certification, recognition, finance-readiness, or official adoption.
Where local or sectoral activity involves operationally sensitive systems, the Corporation shall maintain non-execution, non-reliance, and public-safe limitations and shall not permit dashboards, models, AI outputs, digital twins, sensor signals, AI-RAN signals, DePIN records, proof receipts, or observability outputs to be used as authority without competent external authority, record, and lawful process.
36.14 State-by-State Localization. The Corporation shall localize its activities state by state where required or advisable. State-by-state localization may include legal qualification, charitable solicitation registration, tax registration, employment compliance, contracting terms, public authority capacity language, privacy notices, AI governance provisions, cyber requirements, public records-sensitive language, open meetings-sensitive language, procurement-neutrality language, lobbying and government ethics review, grant compliance, civil rights and accessibility provisions, research ethics requirements, and public-safe communication limits.
State-by-state localization shall not create separate governance systems, separate boards, shadow branches, state-level public authorities, state certification bodies, state procurement bodies, state finance-readiness functions, provider-preference systems, or state-specific deviations from the Corporation’s mission lock unless separately and lawfully authorized.
Where state law or local practice requires adaptation, the adaptation shall be documented through localized terms, compatibility notes, divergence logs, public-safe summaries, state-specific notices, or Board or officer approvals where required.
No state localization shall weaken public-benefit purpose, nonprofit character, non-distribution, non-execution, GCRI / GRF / GRA role separation, public-good stack and enterprise stack separation, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, data / AI / cyber controls, safeguards, validity-by-record, correctionability, or anti-capture discipline.
36.15 Territorial Localization. The Corporation shall localize its activities for territories where required or advisable. Territorial localization may include territorial registration, charitable solicitation review, tax and employment review, local counsel review, language access, public authority capacity language, privacy and cybersecurity controls, disaster-sensitive publication rules, infrastructure-sensitive information controls, community safeguards, civil rights and accessibility provisions, and public-safe communication protocols.
Territorial localization shall preserve the Corporation’s United States legal identity, nonprofit status, public-benefit purpose, United States governance seat, North America anchor boundary, non-execution character, and role separation. It shall not create a territorial branch, territorial public authority, territorial emergency command function, public warning function, finance-readiness function, certification function, procurement function, recognition function, provider-preference function, or enterprise execution function unless separately and lawfully constituted.
Where territorial localization creates a divergence from ordinary United States operating practice, the Corporation shall maintain a divergence log explaining the legal, cultural, public authority, language, infrastructure, data, safeguards, or public-safe basis for the divergence and the limits of its effect.
Territorial localization shall remain correctionable and subject to periodic review.
36.16 Tribal Interface Respect. The Corporation shall respect Tribal Nations, Indigenous governments, Indigenous communities, Indigenous knowledge holders, and Indigenous data stewards as distinct governance, legal, cultural, and knowledge authorities. Tribal-interface activity shall be designed around respect, restraint, lawful process, record discipline, non-extraction, and public-safe treatment.
Tribal interface respect shall include recognition that participation in a GCRI US program, public authority learning session, observability discussion, technical review, controlled room, data room, academy activity, research activity, publication review, or Nexus-compatible interface shall not itself constitute consent, approval, endorsement, adoption, waiver, data license, knowledge license, public authority delegation, or permission to publish protected knowledge.
The Corporation shall not treat Tribal or Indigenous information as freely usable merely because it is observable, publicly discussed, technically accessible, present in a dataset, inferable through AI, contained in geospatial layers, referenced by a public authority, or relevant to a public-good technology question.
Tribal interface respect shall require approved protocols for capacity classification, consent and non-consent, confidentiality, protected knowledge, publication, attribution, withdrawal, correction, grievance, remedy, and non-retaliation where applicable.
36.17 No State or Territorial Operation Without Required Qualification, Registration, Tax, Employment, Solicitation, Public Authority, Data, AI, Cyber, or Contract Review. The Corporation shall not undertake material state or territorial operation without review of whether qualification, registration, charitable solicitation registration, tax registration, employer registration, local licensing, contracting authority, data processing terms, privacy notices, cybersecurity controls, AI governance controls, public authority terms, public records-sensitive terms, open meetings-sensitive terms, procurement-sensitive terms, lobbying or government ethics review, grant compliance, insurance, research ethics review, civil rights or accessibility measures, or safeguards controls are required.
Material state or territorial operation may include maintaining an office or repeated physical presence, hiring personnel, engaging contractors, soliciting support, conducting events, entering contracts, launching programs, collecting data, maintaining controlled rooms, conducting public authority learning, publishing state-specific outputs, releasing state-specific dashboards, running academy programs, convening public authorities, establishing state or territorial interfaces, receiving restricted funds, or entering host-site arrangements.
No officer, committee, council, working group, program lead, sponsor, donor, provider, host, public authority participant, university, laboratory, community participant, or external partner may bypass this review by describing an activity as informal, pilot, experimental, temporary, technical, advisory, virtual, educational, Nexus-aligned, public-good, or noncommercial.
Where review identifies uncertainty, the Corporation shall apply a protective lawful posture, including hold, stop, quarantine, re-scope, counsel review, capacity clarification, access restriction, publication freeze, implementation freeze, separate instrument, externalization, referral, or termination.
36.18 All-States-and-Territories Records. The Corporation shall maintain all-states-and-territories records sufficient to demonstrate lawful authority, compliance posture, localization, public authority capacity, public-safe communication, safeguards, and correctionability for state, territorial, District of Columbia, Tribal-interface, local, and sectoral activity.
All-states-and-territories records shall include, as applicable:
a) state qualification, registration, exemption, withdrawal, and good-standing records;
b) District of Columbia registration, tax, charitable solicitation, employment, and public authority interface records;
c) territorial qualification, registration, exemption, tax, charitable solicitation, employment, and public authority interface records;
d) Puerto Rico, Guam, U.S. Virgin Islands, American Samoa, and Northern Mariana Islands localization records;
e) Tribal and Indigenous interface records, including capacity, permissions, restrictions, consent or non-consent pathways where applicable, protected knowledge classifications, data conditions, publication limits, and correction pathways;
f) local, county, municipal, metropolitan, utility, port, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, infrastructure, and sectoral interface records;
g) federal interface records;
h) public authority capacity classification records;
i) public records, open meetings, procurement, lobbying, government ethics, gift, grant, and public authority boundary review records where applicable;
j) charitable solicitation, tax, employment, contractor, volunteer, fellow, insurance, and contracting review records;
k) privacy, data, AI, cyber, public authority data, health-sensitive data, infrastructure-sensitive data, community-protected data, Indigenous data, and protected knowledge review records;
l) civil rights, accessibility, language access, public-safe mapping, community safeguards, and do-no-harm review records;
m) state-by-state and territorial localization terms, compatibility notes, divergence logs, equivalence notes, public-safe summaries, and limitation language;
n) records of holds, stops, quarantines, access restrictions, publication freezes, implementation freezes, technical isolations, re-scopes, referrals, externalizations, withdrawals, takedowns, supersessions, corrections, and public-safe clarifications affecting state or territorial activity; and
o) responsible owner, custodian, authority, effective date, review date, retention class, access class, publication class, legal hold status, repository location, and metadata.
The governing rule of this Section is that the Corporation’s United States reach shall be expansive in public-benefit purpose and disciplined in legal effect. GCRI US may serve the full United States and its territories as a public-good evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, public authority learning, and safeguards institution, but it shall do so only through lawful localization, capacity clarity, role separation, non-execution, public-safe claims, data / AI / cyber discipline, community safeguards, validity-by-record, and correctionability.
Section 37. North America Anchor Status
37.1 North America Anchor Status. The Corporation may be described, governed, represented, and operated as the United States and North America anchor of the GCRI public-good evidence, methods, observability, ontology, technical truth, public-good research and development, public-good software, open technical baseline, verifiable compute, Nexus Truth Engine methods, Nexus Observatory methods, public authority learning, public-safe publication, community safeguards, and correctionable technical memory function, but only within the limits of applicable law, the Corporation’s constituting instrument, this Bylaw, Board authority, tax status, public-benefit purpose, non-execution discipline, role separation, public authority boundaries, finance boundaries, certification and procurement boundaries, data / AI / cyber controls, safeguards, validity-by-record, and correctionability.
North America anchor status shall be a bounded institutional status. It shall identify the Corporation’s role in supporting lawful cross-border public-benefit learning, evidence comparability, methods continuity, technical vocabulary, public-good software, open technical baselines, observability practices, and public-safe coordination across the United States, Canada, Mexico, the Caribbean, Arctic, Great Lakes, Pacific, Atlantic, Gulf, border, Indigenous, regional, and other North America-relevant interfaces where lawfully and respectfully structured.
North America anchor status shall not create a North America sovereign role, treaty role, intergovernmental role, regional regulatory role, public finance role, emergency command role, public warning role, procurement role, certification role, recognition role, finance-readiness role, standards-monopoly role, enterprise operating role, national company role, Project SPV role, provider role, asset-owner role, or infrastructure-operator role.
The Corporation shall maintain public description discipline whenever North America anchor status is referenced. Such descriptions shall make clear that the Corporation supports evidence, methods, observability, technical baselines, public-good software, public authority learning, safeguards, and public-safe publication, and does not exercise governmental authority, regulated execution, public finance authority, capital placement, procurement authority, certification authority, recognition authority, public warning authority, or emergency command.
37.2 United States Anchor of GCRI Evidence Function. The Corporation shall serve as the United States anchor of the GCRI evidence function. This function shall include the lawful development, stewardship, comparison, classification, versioning, limitation, publication, correction, and preservation of evidence relevant to systemic risk, resilience infrastructure, exponential technologies, public authority learning, public-good software, open technical baselines, safeguards, and public-safe reporting.
The United States anchor role shall include responsibility for ensuring that United States-facing evidence work is properly localized to federal, state, District of Columbia, territorial, Tribal-interface, local, sectoral, public authority, community, data, AI, cyber, privacy, civil rights, accessibility, research ethics, export-control, sanctions, competition, charitable solicitation, tax, employment, and contracting requirements where applicable.
The Corporation may support evidence comparability between United States contexts and other North America contexts, including Canada, Mexico, Caribbean, Arctic, Great Lakes, Pacific, Atlantic, Gulf, border, Indigenous, infrastructure, climate, cyber, public health, energy, water, food, telecom, port, supply-chain, and disaster contexts. Such comparability shall not create legal merger, common authority, shared liability, public authority delegation, or cross-border regulatory status.
No evidence artifact, evidence register, evidence pack, dashboard, map, proof receipt, AI output, model output, digital twin output, sensor signal, AI-RAN signal, O-RAN signal, DePIN record, DLT entry, blockchain entry, repository entry, or public-safe publication generated or supported by the Corporation shall be treated as recognition, finance-readiness, certification, procurement approval, public authority decision, emergency command, public warning, rating, investment opinion, underwriting opinion, insurance approval, public finance approval, or operational instruction.
37.3 North America Evidence Architecture Support. The Corporation may support a North America evidence architecture for cross-border systemic-risk learning, public-good methods, observability, and technical memory. Such architecture may include shared taxonomies, controlled vocabulary, evidence classes, data dictionaries, schemas, model cards, system cards, dataset cards, provenance rules, public-safe publication classes, community safeguard classes, public authority capacity classes, observability method records, verifiable compute records, and correction pathways.
North America evidence architecture support may address hazards and systems that cross or connect jurisdictions, including climate, nature, biodiversity, water, food, energy, public health, biosecurity, disaster resilience, telecom, AI-RAN, O-RAN, DePIN, DLT, blockchain, Web3, sovereign compute, HPC, cyber, geospatial systems, Earth observation, digital twins, ports, borders, logistics, supply chains, semiconductors, advanced manufacturing, critical infrastructure, and other mission-critical or exponential technology systems.
The Corporation shall ensure that any North America evidence architecture support preserves lawful separateness among GCRI US, GCRI Canada, other GCRI-related entities, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Standards, regional and national consortiums, national companies, Project SPVs, public authorities, universities, laboratories, communities, providers, sponsors, hosts, donors, and enterprise actors.
Evidence architecture support shall be implemented through records. Each material evidence architecture element shall identify status, scope, steward, jurisdictional applicability, public-safe classification, data / AI / cyber classification, safeguards classification, review cycle, limitation, correction pathway, and relationship to any GRF, GRA, Nexus Standards, Nexus Network, consortium, national company, Project SPV, public authority, provider, sponsor, host, university, laboratory, or community interface.
37.4 North America Methods Continuity. The Corporation may support continuity of methods across North America-facing work. Methods continuity shall mean that evidence methods, validation methods, confidence methods, uncertainty methods, source-lineage methods, sensor-fusion methods, AI-output review methods, AI-RAN and O-RAN signal interpretation methods, DePIN and DLT validation methods, digital twin assumption-review methods, geospatial evidence methods, cyber evidence methods, verifiable compute methods, public-safe publication methods, safeguards methods, and correction methods remain comparable, versioned, limited, and correctionable across jurisdictions and interfaces.
Methods continuity shall not require uniformity where local law, Tribal or Indigenous governance, protected knowledge, data localization, public authority requirements, privacy law, cyber obligations, public records constraints, public-safe risk, language needs, infrastructure conditions, climate hazards, disaster context, community safeguards, or other lawful circumstances require divergence.
Where divergence is required, the Corporation shall maintain divergence logs, compatibility notes, localization notes, equivalence notes, method limitations, and public-safe explanations sufficient to preserve clarity without collapsing legal or institutional boundaries.
No method shall be treated as authoritative outside its recorded scope. No method shall be used to create certification, recognition, finance-readiness, procurement approval, public authority decision, rating, emergency command, public warning, insurance approval, lending approval, investment recommendation, public finance approval, or operational control unless such function is separately and lawfully performed by a competent body other than the Corporation or by the Corporation only where separately and lawfully authorized.
37.5 North America Observability and Ontology Alignment. The Corporation may support North America observability and ontology alignment to improve shared understanding of systemic risk, infrastructure resilience, public-good technology, public authority learning, evidence classification, technical baselines, and correctionable technical memory.
Observability alignment may include methods for observatory nodes, Nexus hubs, Nexus clusters, Nexus hotspots, regional clusters, national dense Nexus cores, state interfaces, territorial interfaces, Tribal-interface contexts, public authority learning environments, controlled rooms, cyber observability, geospatial observability, Earth observation, AI-RAN observability, O-RAN observability, DePIN observability, digital twin observability, sensor observability, and dashboard outputs.
Ontology alignment may include controlled terms, taxonomies, schemas, data dictionaries, technology-family classifications, risk categories, maturity concepts, public authority capacity semantics, finance boundary semantics, certification boundary semantics, recognition boundary semantics, Nexus-compatible claim semantics, evidence classifications, and public-safe publication terms.
Observability and ontology alignment shall not convert observability into surveillance authority, ontology into legal authority, dashboards into public warnings, maps into official public decisions, technical baselines into mandatory standards, proof receipts into certifications, or AI outputs into institutional truth without human authorization, lawful record, limitation, classification, and correction pathway.
37.6 North America Public-Good Software and Technical Baseline Support. The Corporation may support North America public-good software and technical baseline continuity by developing, maintaining, publishing, localizing, restricting, deprecating, withdrawing, superseding, or archiving software, schemas, APIs, SDKs, dashboards, data tools, reference architectures, model cards, system cards, dataset cards, evaluation tools, test harnesses, benchmark libraries, observability tools, verifiable compute tools, public authority learning tools, and open technical baselines.
Public-good software and technical baseline support shall be conducted under secure development, repository governance, licensing, contribution, vulnerability management, SBOM, signing, provenance, access-control, data / AI / cyber, export-control, sanctions, controlled-technology, IP, public-safe claims, and correction controls.
The Corporation may make public-good technical assets available for use by public authorities, universities, laboratories, communities, GRF, GRA, Nexus Standards, Nexus Network, consortiums, national companies, Project SPVs, providers, sponsors, hosts, and enterprise actors, but such availability shall not constitute certification, recognition, finance-readiness, procurement approval, public authority adoption, provider preference, operational suitability, security guarantee, insurance approval, rating, public warning, emergency command, or execution.
Any North America-facing public-good software or technical baseline shall include appropriate notices identifying status, version, custodian, scope, limitations, jurisdictional assumptions, public-safe classification, data / AI / cyber classification, safeguards classification, release status, deprecation status, vulnerability reporting pathway, correction pathway, and relation to Nexus instruments where applicable.
37.7 North America Nexus Observatory Methods Support. The Corporation may support North America Nexus Observatory methods as a public-benefit technical function. Such support may include methods for observatory nodes, Nexus hubs, clusters, hotspots, regional clusters, national dense Nexus cores, state and territorial observatory interfaces, Tribal-interface observability, public authority learning environments, controlled rooms, sensor systems, edge compute, AI-RAN signals, O-RAN signals, DePIN records, digital twins, cyber telemetry, geospatial layers, Earth observation, resilience indicators, degraded-mode awareness, and public-safe observability outputs.
North America Nexus Observatory methods support shall be limited to evidence, methods, observability, technical baselines, public-good software, public authority learning, safeguards, and correctionability. It shall not constitute ownership, command, operation, dispatch, emergency response, public warning, infrastructure control, telecommunications operation, public health order, safety command, resource allocation, procurement approval, certification, recognition, finance-readiness, or enterprise execution.
Where observability outputs may affect public understanding, public authority learning, community safety, infrastructure sensitivity, cyber exposure, protected knowledge, market behavior, finance interpretation, or operational reliance, the Corporation shall use public-safe publication review, access controls, aggregation, redaction, delay, limitation language, non-reliance language, and correction pathways.
The Corporation shall maintain observatory methods records identifying method version, applicability, source assumptions, data classes, public-safe status, limitations, human review requirements, correction triggers, and any relationship to Nexus Observatory Protocol or other Nexus-compatible instruments.
37.8 North America Truth Engine Methods Support. The Corporation may support North America Nexus Truth Engine methods as non-oracle methods for source comparison, confidence assessment, corroboration, disputed evidence handling, failed-signal handling, spoof-indicator handling, correction trigger identification, public-safe truth output design, and auditability.
Truth Engine methods support shall not create official truth, legal truth, regulatory truth, public authority truth, public warning truth, finance truth, certification truth, recognition truth, procurement truth, rating truth, insurance truth, or operational truth. The Truth Engine shall be treated as a confidence and corroboration system whose outputs require records, limitation, classification, human review where material, and correction pathway.
The Corporation shall ensure that Truth Engine methods do not overstate automated authority. No automated score, confidence rating, model output, proof receipt, ledger entry, AI inference, sensor signal, dashboard display, or digital twin output shall be treated as final institutional authority merely because it was produced through a Truth Engine method.
Truth Engine methods records shall include source classes, confidence rules, corroboration logic, disputed-evidence handling, failure modes, spoof indicators, human review requirements, public-safe publication rules, correction triggers, audit trails, and limitations.
37.9 North America Cross-Border Public Authority Learning Support. The Corporation may support North America cross-border public authority learning where lawful and appropriately structured. Such support may include evidence literacy, technical literacy, public-safe reporting literacy, scenario learning, simulation learning, tabletop exercises, after-action learning, methods briefings, technical baseline explainers, public-good software demonstrations, data / AI / cyber literacy, observability literacy, Nexus Observatory methods, Nexus Truth Engine methods, verifiable compute methods, and cross-border risk literacy.
Cross-border public authority learning may involve federal, state, District of Columbia, territorial, Tribal-interface, Indigenous governance, local, Canadian, Mexican, Caribbean, Arctic, regional, metropolitan, port, utility, emergency management, public health, public safety, telecom, energy, water, food, cyber, infrastructure, public finance reader, and regulator-listening participants, subject to lawful participation and capacity classification.
Such learning shall not constitute public authority delegation, intergovernmental decision, treaty function, official adoption, public-private partnership, procurement approval, funding approval, public finance approval, regulatory approval, emergency command, official public warning, sovereign obligation, certification, recognition, finance-readiness, or execution.
The Corporation shall record participant capacity, jurisdictional context, learning purpose, non-reliance language, public-safe limits, data and confidentiality controls, public authority reference permissions, and any correction, withdrawal, or clarification needed after the activity.
37.10 North America Climate, Disaster, Cyber, Public Health, Energy, Water, Food, Biodiversity, Telecom, AI-RAN, DePIN, Supply Chain, Port, Border, Arctic, Great Lakes, Atlantic, Pacific, Gulf, and Critical Infrastructure Context. The Corporation’s North America anchor status may be applied to public-benefit work concerning climate, disaster, cyber, public health, biosecurity, energy, water, food, biodiversity, nature, telecom, AI-RAN, O-RAN, private wireless, DePIN, DLT, blockchain, Web3, supply chains, ports, borders, Arctic systems, Great Lakes systems, Atlantic systems, Pacific systems, Gulf systems, critical infrastructure, semiconductors, advanced manufacturing, sovereign compute, HPC, geospatial systems, Earth observation, digital twins, robotics, drones, sensors, and other interconnected systems.
The Corporation may support evidence, methods, observability, ontology, technical baselines, public-good software, public authority learning, safeguards, public-safe publications, and correctionable technical memory across these domains, but shall not represent such support as operational control, public warning, emergency command, public authority decision, regulatory approval, procurement approval, certification, recognition, finance-readiness, insurance approval, rating, investment recommendation, public finance approval, or provider selection.
Because these domains may involve infrastructure-sensitive information, cyber-sensitive information, public health information, community-protected knowledge, Tribal or Indigenous knowledge, public authority data, market-sensitive information, national security sensitivity, controlled technology, sanctions or export-control sensitivity, civil rights implications, accessibility implications, and disaster-related public safety risk, the Corporation shall apply heightened review where needed.
North America contextual work shall remain subject to public-safe claims, non-reliance, data minimization, access control, aggregation, redaction, protected knowledge handling, public authority capacity classification, competition discipline, legal review, and correctionability.
37.11 Coordination With GCRI Canada. The Corporation may coordinate with GCRI Canada as a separate Canadian public-benefit anchor concerning evidence, methods, observability, ontology, technical baselines, public-good software, public-good R&D, verifiable compute, Nexus Truth Engine methods, Nexus Observatory methods, technical memory, public authority learning, safeguards, public-safe publication support, and cross-border evidence architecture.
Coordination with GCRI Canada shall preserve separate legal personality, separate governance, separate treasury, separate tax status, separate filings, separate employment relationships, separate liabilities, separate records, separate data responsibilities, separate public authority interfaces, separate support arrangements, and separate correction pathways.
No coordination with GCRI Canada shall create parent-subsidiary status, branch status, agency, alter ego status, single employer status, joint employer status, common treasury, shared liability, mutual authority, merger, partnership, joint venture, public authority delegation, finance-readiness authority, certification authority, recognition authority, procurement authority, public warning authority, emergency command, or enterprise execution responsibility unless separately and lawfully constituted by competent instrument.
The Corporation shall maintain GCRI Canada interface records, including cooperation instruments, role maps, compatibility notes, divergence logs, dual-role person controls, shared-method records, data-transfer records, public description approvals, and correction paths.
37.12 Coordination With Mexico, Caribbean, Arctic, Indigenous, Regional, and Cross-Border Interfaces Where Lawfully Structured. The Corporation may coordinate with Mexico, Caribbean, Arctic, Indigenous, regional, border, Great Lakes, Pacific, Atlantic, Gulf, and other North America-relevant interfaces where lawfully structured and consistent with public-benefit purpose, non-execution, role separation, data / AI / cyber requirements, public authority boundaries, community safeguards, and this Bylaw.
Such coordination may include evidence comparison, method alignment, public authority learning, climate and disaster learning, infrastructure resilience learning, cyber learning, telecom and AI-RAN methods, DePIN and DLT methods, public-good software interoperability, public-safe publication support, observability methods, technical baseline comparison, safeguards learning, and correction signal sharing.
No such coordination shall imply foreign legal registration, treaty authority, intergovernmental status, public authority delegation, cross-border regulatory role, public finance role, procurement role, certification role, recognition role, finance-readiness role, public warning role, emergency command role, provider role, operator role, or enterprise execution role unless separately and lawfully established.
Where cross-border coordination involves data transfer, controlled technology, sanctions, export control, national security sensitivity, Indigenous knowledge, protected knowledge, public authority data, health-sensitive information, infrastructure-sensitive information, cyber-sensitive information, or community-sensitive information, the Corporation shall conduct and record appropriate review before proceeding.
37.13 No North America Sovereign Authority. North America anchor status shall not confer and shall not be interpreted to confer sovereign authority. The Corporation is not a sovereign, treaty body, intergovernmental organization, state actor, public authority, public finance authority, regional regulator, public warning body, emergency command body, procurement authority, certification authority, recognition authority, standards monopoly, finance-readiness body, or official North America governmental institution.
The Corporation shall not claim, imply, accept, or permit others to claim that its North America anchor status gives it authority to bind any government, public authority, Tribal Nation, Indigenous government, state, territory, province, municipality, regional body, public infrastructure operator, public university, public laboratory, donor, sponsor, provider, host, national company, Project SPV, consortium, or enterprise actor.
No public authority participation, public authority attendance, public authority consultation, public authority data contribution, public authority learning session, public authority room, controlled room, simulation, tabletop exercise, report, dashboard, map, public-safe publication, technical baseline, proof receipt, or Nexus-compatible interface shall be described as sovereign action or official adoption merely because it involves or references the Corporation.
The Corporation shall correct any overclaim of North America sovereign authority through clarification, withdrawal, takedown, correction, re-labeling, public-safe notice, access restriction, contractual action, or legal response where appropriate.
37.14 No North America Regulator, Treaty Body, Public Finance Approver, Public Warning Authority, Certification Body, or Execution Vehicle Status. The Corporation shall not be a North America regulator, treaty body, public finance approver, public warning authority, certification body, accreditation body, procurement body, recognition body, finance-readiness body, insurance-readiness body, investment adviser, broker, dealer, lender, insurer, rating agency, bank, underwriter, public finance intermediary, fund, national company, Project SPV, provider, operator, asset owner, deployment company, infrastructure operator, systems integrator, telecommunications carrier, emergency management body, or execution vehicle.
No North America anchor function shall authorize the Corporation to issue permits, approve compliance, grant regulatory safe harbor, approve public procurement, approve public finance, certify vendors, accredit systems, recognize maturity, determine standing, determine finance-readiness, determine insurance-readiness, rate resilience, recommend investments, place capital, underwrite risk, bind insurance, originate loans, guarantee revenues, command emergency response, issue evacuation instructions, operate public infrastructure, control telecom systems, operate AI-RAN systems, execute DePIN deployments, or manage Project SPVs.
The Corporation may support the public-good stack through evidence, methods, observability, ontology, technical baselines, public-good software, public authority learning, safeguards, public-safe publication, and correction signals. Execution, finance-readiness, recognition, standards authority, procurement, certification, public authority decision-making, and enterprise delivery shall remain with the competent bodies or actors lawfully responsible for those functions.
Any activity that may be interpreted as crossing into prohibited North America regulator, treaty-body, public finance, public warning, certification, or execution status shall be escalated for regulatory-perimeter review and may be held, stopped, quarantined, re-scoped, externalized, referred, or terminated.
37.15 North America Anchor Status Records. The Corporation shall maintain North America anchor status records sufficient to demonstrate the lawful basis, scope, limits, localization, interfaces, public descriptions, compatibility notes, divergence logs, safeguards, and corrections associated with the Corporation’s United States and North America anchor role.
North America anchor status records shall include, as applicable:
a) Board resolutions, officer delegations, policies, schedules, protocols, public descriptions, and notices referencing North America anchor status;
b) records of United States anchor functions for evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, verifiable compute, Nexus Truth Engine methods, Nexus Observatory methods, public authority learning, safeguards, and public-safe publication support;
c) GCRI Canada interface records, cooperation instruments, compatibility notes, divergence logs, role maps, public description approvals, dual-role person controls, and correction paths;
d) Mexico, Caribbean, Arctic, Great Lakes, Pacific, Atlantic, Gulf, border, Indigenous, regional, and cross-border interface records where applicable;
e) North America evidence architecture records, methods continuity records, ontology records, observability records, Truth Engine methods records, verifiable compute records, and public-good software records;
f) public authority learning records, capacity classifications, public authority reference permissions, non-reliance notices, public-safe publication records, and controlled-room records;
g) data / AI / cyber / privacy, export-control, sanctions, controlled-technology, national security sensitivity, public authority data, health-sensitive data, infrastructure-sensitive data, community-protected data, Indigenous data, and protected knowledge review records;
h) community safeguards, Tribal / Indigenous, local, territorial, civil rights, accessibility, language access, public-safe mapping, do-no-harm, grievance, remedy, withdrawal, and correction records;
i) public descriptions, website language, GitBook language, repository notices, decks, reports, grant materials, sponsorship materials, donor materials, public authority materials, provider materials, and Nexus-interface materials using North America anchor language;
j) records of any overclaim, public authority confusion, finance overclaim, certification overclaim, procurement implication, recognition implication, provider-preference implication, sponsor-control implication, public warning implication, emergency command implication, or execution implication involving North America anchor status;
k) holds, stops, quarantines, access restrictions, publication freezes, implementation freezes, technical isolations, re-scopes, externalizations, referrals, withdrawals, takedowns, supersessions, corrections, public-safe clarifications, contractual actions, legal responses, and closure records; and
l) responsible owner, custodian, authority, effective date, review date, retention class, access class, publication class, legal hold status, repository location, and metadata.
The governing rule of this Section is that North America anchor status shall expand the Corporation’s public-benefit service horizon while narrowing any claim of authority. GCRI US may anchor evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, verifiable compute methods, public authority learning, safeguards, public-safe publication, and correctionable technical memory across North America-relevant contexts, but it shall not become a sovereign, regulator, finance-readiness body, certification body, public warning body, emergency command body, procurement body, recognition body, standards monopoly, provider, operator, national company, Project SPV, or execution vehicle by reason of that role.
Section 38. Public-Good Technical Institution Status
38.1 Public-Good Technical Institution Status. The Corporation shall be governed, represented, and operated as a United States public-good technical institution. This status shall mean that the Corporation’s lawful institutional role is to steward evidence, methods, observability, ontology, technical truth, public-good research and development, public-good software, open technical baselines, verifiable compute and verifiable intelligence methods, Nexus Truth Engine methods, Nexus Observatory methods, public authority learning, technical literacy, public-safe publication, community safeguards, protected knowledge controls, and correctionable technical memory.
Public-good technical institution status shall not be a commercial, execution, regulatory, certification, procurement, finance, recognition, public warning, or emergency command status. It shall not authorize the Corporation to operate as a regulator, public authority, public finance approver, emergency command body, public warning authority, certification body, accreditation body, recognition body, finance-readiness body, insurance-readiness body, procurement authority, standards monopoly, broker, dealer, investment adviser, lender, insurer, rating agency, national company, Project SPV, provider, operator, asset owner, deployment company, telecommunications carrier, systems integrator, managed services provider, or enterprise execution vehicle.
The Corporation’s technical status shall be public-benefit and non-executing. It may create, maintain, interpret, improve, publish, restrict, correct, withdraw, or archive technical assets in furtherance of its purposes, but no technical asset shall be treated as legal authority, public authority decision, certification, recognition, finance-readiness determination, procurement approval, provider preference, emergency instruction, public warning, investment recommendation, insurance approval, rating, underwriting basis, or operational command unless separately and lawfully issued by a competent body with authority to do so.
Public-good technical institution status shall be preserved through records, controlled vocabulary, public-safe claims discipline, security controls, research integrity, data / AI / cyber governance, safeguards review, jurisdictional localization, non-reliance notices, versioning, public description controls, and correction pathways.
38.2 Evidence Institution Status. The Corporation shall have evidence institution status within its public-good technical mandate. Evidence institution status shall authorize the Corporation to collect, receive, classify, compare, structure, document, analyze, preserve, publish, restrict, correct, supersede, withdraw, or archive evidence where lawful and mission-aligned.
Evidence institution status shall apply to evidence concerning systemic risk, resilience infrastructure, exponential technologies, public-good software, open technical baselines, observability systems, Nexus Observatory methods, Nexus Truth Engine methods, verifiable compute, public authority learning, community safeguards, protected knowledge, public-safe publication, and correctionable technical memory.
Evidence may include documents, datasets, public records, research outputs, sensor signals, AI outputs, model outputs, digital twin outputs, geospatial layers, Earth observation materials, cyber telemetry, AI-RAN signals, O-RAN signals, DePIN records, DLT or blockchain records, public authority submissions, community inputs, expert inputs, technical artifacts, software records, benchmark results, system cards, model cards, dataset cards, inference records, proof receipts, and controlled-room materials.
Evidence institution status shall not convert evidence into recognition, finance-readiness, certification, procurement approval, public authority decision, public warning, emergency command, rating, investment advice, underwriting opinion, insurance approval, lending approval, public finance approval, operational instruction, or provider endorsement. Evidence shall remain bounded by source lineage, provenance, custody, quality, uncertainty, limitation, classification, public-safe status, human review where material, and correctionability.
38.3 Methods Institution Status. The Corporation shall have methods institution status within its public-good technical mandate. Methods institution status shall authorize the Corporation to develop, maintain, review, version, localize, publish, restrict, correct, supersede, withdraw, or archive methods for evidence, validation, confidence scoring, uncertainty handling, source lineage, sensor fusion, AI-output review, AI-RAN and O-RAN signal interpretation, DePIN validation, DLT validation, blockchain validation, digital twin assumption review, geospatial evidence, cyber evidence, verifiable compute, public-safe publication, safeguards, and correction.
Methods institution status shall require that methods be documented by record, linked to an identified scope, assigned a status, assigned a custodian where appropriate, bounded by limitations, reviewed according to a cycle or trigger, and subject to correction when defects, ambiguity, changed conditions, public-safe risk, legal risk, data risk, AI risk, cyber risk, safeguards risk, or misuse is identified.
Methods may support GRF, GRA, Nexus Network, Nexus Standards, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, public authorities, universities, laboratories, communities, providers, sponsors, hosts, and enterprise actors, but such support shall not transfer authority to the Corporation to recognize, certify, finance, procure, regulate, command, warn, rate, approve, underwrite, lend, insure, execute, or operate.
No method shall be represented as universal, final, self-executing, jurisdiction-free, risk-free, legally sufficient, certification-conferring, procurement-conferring, finance-conferring, recognition-conferring, public authority-conferring, or operationally authoritative without competent record and lawful authority.
38.4 Observability Institution Status. The Corporation shall have observability institution status within its public-good technical mandate. Observability institution status shall authorize the Corporation to steward methods, technical baselines, public-good software, data structures, controlled vocabularies, dashboards, indicators, review pathways, and public-safe publication practices that help lawful actors see, compare, learn from, and correct systemic risk signals.
Observability institution status may include methods for observatory nodes, Nexus hubs, Nexus clusters, Nexus hotspots, regional clusters, national dense Nexus cores, state interfaces, territorial interfaces, Tribal-interface contexts, metropolitan interfaces, port interfaces, utility interfaces, public health interfaces, emergency management learning interfaces, public safety learning interfaces, telecom interfaces, energy interfaces, water interfaces, food interfaces, cyber interfaces, infrastructure interfaces, AI-RAN and O-RAN signals, DePIN records, digital twins, geospatial systems, Earth observation, sensors, edge compute, dashboards, degraded-mode awareness, and resilience indicators.
Observability institution status shall not be surveillance authority, emergency command authority, public warning authority, public health authority, telecommunications operating authority, infrastructure operating authority, cyber command authority, public authority decision authority, public finance authority, procurement authority, certification authority, recognition authority, finance-readiness authority, or enterprise execution authority.
No observability output shall be treated as an official warning, evacuation instruction, incident command, public health order, safety order, regulatory decision, procurement decision, finance-readiness determination, recognition, certification, rating, provider approval, or operational instruction merely because it is displayed, computed, timestamped, signed, hashed, recorded, mapped, routed, or referenced in a Nexus-compatible environment.
38.5 Ontology Institution Status. The Corporation shall have ontology institution status within its public-good technical mandate. Ontology institution status shall authorize the Corporation to steward controlled vocabulary, taxonomies, schemas, data dictionaries, semantic maps, technology-family classifications, evidence classifications, risk categories, maturity concepts, public authority capacity semantics, finance boundary semantics, certification boundary semantics, recognition boundary semantics, Nexus-compatible claim semantics, and other meaning-bearing structures necessary for public-good technical clarity.
Ontology institution status shall be exercised to reduce ambiguity, prevent overclaim, preserve role separation, support comparability, enable machine-readable and human-readable interpretation, and maintain lawful distinctions among evidence, method, observability, recognition, finance-readiness, certification, procurement, public authority action, public-safe publication, and execution.
The Corporation may support semantic interoperability across 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, consortiums, national companies, Project SPVs, public authorities, universities, laboratories, communities, providers, sponsors, hosts, and enterprise actors.
Ontology institution status shall not permit the Corporation to create legal status by vocabulary, certification by label, procurement approval by category, finance-readiness by term, public authority adoption by metadata, recognition by taxonomy, or operational authority by schema. Controlled terms shall have only the meaning assigned by lawful record and shall remain subject to correction, restriction, supersession, and withdrawal.
38.6 Technical Truth Institution Status. The Corporation shall have technical truth institution status within its public-good technical mandate. Technical truth institution status shall mean that the Corporation may steward methods for corroboration, confidence, source comparison, evidence challenge, uncertainty disclosure, limitation, correction, and public-safe presentation of technical claims.
Technical truth shall not mean infallible truth, legal truth, regulatory truth, public authority truth, market truth, finance truth, certification truth, recognition truth, procurement truth, rating truth, insurance truth, operational truth, or emergency truth. It shall mean disciplined, record-supported, correctionable, bounded, and public-safe treatment of technical claims.
The Corporation shall preserve the distinction between:
a) evidence and conclusion;
b) signal and interpretation;
c) model output and institutional decision;
d) proof receipt and authority;
e) dashboard display and public warning;
f) technical baseline and mandatory standard;
g) confidence level and rating;
h) public authority learning and public authority action;
i) GRF recognition input and GRF recognition;
j) GRA finance-readiness input and GRA finance-readiness; and
k) Nexus-compatible support and Nexus-wide authority.
Technical truth institution status shall require correction when evidence changes, methods fail, assumptions become invalid, sources are challenged, signals are spoofed, data quality is degraded, public-safe risks emerge, automated systems overstate certainty, or public claims exceed record support.
38.7 Public-Good R&D Institution Status. The Corporation shall have public-good research and development institution status within its public-good technical mandate. Public-good R&D institution status shall authorize the Corporation to conduct, support, coordinate, publish, restrict, translate, and preserve lawful research and development for evidence systems, methods, observability, ontology, public-good software, open technical baselines, verifiable compute, AI governance, cybersecurity, data governance, public authority learning, community safeguards, and systemic de-risking.
Public-good R&D may include applied research, technical prototyping, reference architectures, schemas, APIs, SDKs, dashboards, data tools, test harnesses, benchmark libraries, gold vectors, negative tests, evaluation sets, model cards, system cards, dataset cards, secure release processes, reproducibility methods, and public-safe publication methods.
Public-good R&D institution status shall not convert the Corporation into a commercial R&D vendor, product company, systems integrator, deployment company, asset owner, infrastructure operator, managed services provider, telecom operator, AI-RAN operator, DePIN operator, capital intermediary, public authority, procurement body, certification body, recognition body, finance-readiness body, or enterprise execution vehicle.
The Corporation shall maintain research integrity, sponsor independence, publication review, conflict disclosure, data / AI / cyber review, safeguards review, IP review, export-control and sanctions review where applicable, competition review, and correction pathways for public-good R&D.
38.8 Public-Good Software Institution Status. The Corporation shall have public-good software institution status within its public-good technical mandate. Public-good software institution status shall authorize the Corporation to develop, maintain, publish, license, restrict, secure, deprecate, withdraw, supersede, fork, accept contributions to, or archive software and related technical assets in furtherance of public-benefit purposes.
Public-good software may include evidence tools, methods tools, observability tools, ontology tools, public authority learning tools, dashboards, schemas, APIs, SDKs, data tools, reference architectures, model-card tools, system-card tools, dataset-card tools, evaluation harnesses, benchmark tools, verifiable compute tools, proof-receipt tools, public-safe publication tools, and correction tools.
Public-good software institution status shall require repository governance, secure development, contributor controls, licensing controls, dependency management, vulnerability management, secrets and credential controls, software bill of materials where appropriate, signing and provenance controls where appropriate, release classification, export-control and sanctions review where applicable, data / AI / cyber review, public-safe claims review, and correction pathways.
No software release, reference implementation, dashboard, API, SDK, model, schema, tool, library, benchmark, test harness, proof-receipt tool, or technical asset shall be treated as certification, procurement approval, provider preference, public authority adoption, finance-readiness, insurance-readiness, recognition, rating, public warning, emergency command, operational approval, or enterprise execution merely because it was developed, released, maintained, referenced, or used by the Corporation.
38.9 Open Technical Baseline Institution Status. The Corporation shall have open technical baseline institution status within its public-good technical mandate. Open technical baseline institution status shall authorize the Corporation to develop, maintain, publish, localize, revise, restrict, supersede, withdraw, or archive public-good technical baselines.
Open technical baselines may address evidence quality, data governance, AI governance, cybersecurity, observability, verifiable compute, public-good software, technical interoperability, public authority learning, public-safe publication, safeguards, model governance, inference records, compute workload records, repository security, secure release, public-safe mapping, and systemic-risk learning.
Open technical baselines shall be public-good technical guidance or reference baselines unless a competent authority has separately and lawfully adopted a different status. They shall not be represented as mandatory legal standards, regulatory requirements, procurement requirements, certification criteria, recognition criteria, finance-readiness requirements, insurance-readiness requirements, bankability rules, rating criteria, public finance conditions, emergency instructions, public warning protocols, or public authority decisions.
Each material open technical baseline shall identify status, version, scope, custodian, effective date, review cycle, applicability, exclusions, limitations, public-safe classification, data / AI / cyber classification, safeguards classification, correction pathway, supersession relationship, localization notes, and relationship to Nexus Standards or other competent bodies where applicable.
38.10 Verifiable Compute and Verifiable Intelligence Methods Institution Status. The Corporation shall have verifiable compute and verifiable intelligence methods institution status within its public-good technical mandate. This status shall authorize the Corporation to steward methods, records, baselines, software, and public-safe practices concerning compute workload records, inference records, model registers, dataset cards, model cards, system cards, evaluation records, secure enclaves, confidential computing, compute-to-data, sovereign compute, proof receipts, auditability, and correctionable intelligence outputs.
Verifiable compute and verifiable intelligence methods shall be used to improve traceability, accountability, reproducibility where appropriate, security, public-safe communication, and correctionability of AI-enabled, compute-enabled, and intelligence-enabled systems. Such methods shall not be used to make automated outputs self-authorizing.
No compute record, inference record, proof receipt, model card, system card, dataset card, benchmark result, AI evaluation, secure enclave output, confidential computing receipt, sovereign compute attestation, or verifiable intelligence output shall constitute public authority decision, legal approval, certification, recognition, finance-readiness, insurance-readiness, procurement approval, rating, investment recommendation, underwriting basis, public warning, emergency command, or operational instruction without competent human authorization, lawful authority, record support, limitation, classification, and correction pathway.
The Corporation shall maintain model and compute records sufficient to support accountability, including model identity, model version, data lineage where available, inference context, prompt or query class where appropriate, output class, human review status, public-safe status, limitation, access class, retention class, correction trigger, and responsible custodian.
38.11 Nexus Truth Engine Methods Institution Status. The Corporation shall have Nexus Truth Engine methods institution status within its public-good technical mandate. This status shall authorize the Corporation to support methods for confidence, corroboration, source comparison, disputed evidence handling, failed signal handling, spoof indicator handling, correction triggers, public-safe truth output design, auditability, and technical claim discipline.
The Nexus Truth Engine shall be understood as a method family and confidence-support environment, not as an oracle, legal authority, regulator, public authority, certifier, recognizer, finance-readiness body, procurement authority, rating agency, public warning body, emergency command body, or execution system.
Truth Engine methods may support public authority learning, GRF inputs, GRA inputs, Nexus Standards inputs, Nexus Observatory methods, Nexus Grid inputs, Nexus Docket inputs, public-safe reporting, public-good software, technical baselines, and controlled-room analysis. Such support shall not convert the Corporation into the body responsible for recognition, finance-readiness, standards authority, procurement, certification, public authority action, public warning, emergency command, rating, insurance approval, investment advice, or execution.
Truth Engine outputs shall be presented with confidence, uncertainty, source lineage, dispute status, known limitations, human review status where material, public-safe classification, and correction pathway. Any output that is uncertain, disputed, degraded, spoof-risked, safety-sensitive, public authority-sensitive, finance-sensitive, community-sensitive, cyber-sensitive, infrastructure-sensitive, protected-knowledge-sensitive, or potentially misleading shall be restricted, delayed, corrected, or withdrawn as appropriate.
38.12 Nexus Observatory Methods Institution Status. The Corporation shall have Nexus Observatory methods institution status within its public-good technical mandate. This status shall authorize the Corporation to steward methods, baselines, software, records, and public-safe practices concerning observatory nodes, Nexus hubs, Nexus clusters, Nexus hotspots, regional clusters, national dense Nexus cores, state and territorial observatory interfaces, Tribal-interface observability, public authority learning environments, controlled rooms, sensor systems, edge compute, AI-RAN, O-RAN, DePIN, digital twins, cyber telemetry, geospatial systems, Earth observation, resilience indicators, degraded-mode awareness, and observability outputs.
Nexus Observatory methods institution status shall be limited to method stewardship, evidence support, technical baseline support, public-good software support, public authority learning support, safeguards support, and correction support. It shall not authorize the Corporation to own, operate, command, dispatch, control, regulate, certify, procure, recognize, finance, insure, rate, warn, or execute observatory infrastructure or connected systems unless separately and lawfully authorized within a role that remains compatible with this Bylaw.
Observatory methods shall distinguish between sensing, observation, signal, evidence, inference, confidence, alert-like display, public-safe report, public authority learning, and official public warning. No observatory signal or dashboard shall be treated as official public warning, emergency command, evacuation instruction, dispatch, safety order, operational resource direction, or public authority decision by reason of its existence, technical reliability, public relevance, or use in a learning environment.
The Corporation shall maintain observatory method records identifying data sources, signal classes, confidence methods, latency assumptions, failure modes, degraded-mode assumptions, public-safe classification, cyber sensitivity, infrastructure sensitivity, community sensitivity, protected knowledge restrictions, human review requirements, correction triggers, and publication limits.
38.13 Public Authority Learning Institution Status. The Corporation shall have public authority learning institution status within its public-good technical mandate. This status shall authorize the Corporation to support public authorities and public authority participants through evidence literacy, technical literacy, public-safe reporting literacy, scenario learning, simulation support, tabletop support, after-action learning, methods briefings, technical baseline explainers, observability literacy, data / AI / cyber literacy, verifiable compute literacy, and Nexus-compatible public-good learning.
Public authority learning institution status may apply to federal, state, District of Columbia, territorial, Tribal-interface, Indigenous governance, local, municipal, county, metropolitan, port, utility, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, infrastructure, public finance reader, and regulator-listening contexts where lawfully structured and properly classified.
Public authority learning institution status shall not create public authority delegation, official adoption, public-private partnership, sovereign obligation, regulatory decision, procurement approval, funding approval, public finance approval, emergency command, public warning, public health order, certification, recognition, finance-readiness, insurance-readiness, or execution. Participation by a public authority shall be described only according to the recorded capacity in which the public authority participates.
The Corporation shall maintain public authority learning records identifying participant capacity, jurisdictional context, learning purpose, data conditions, confidentiality conditions, public authority reference permissions, public-safe limitations, non-reliance language, correction pathways, and any required clarification or withdrawal.
38.14 Academy, Training, Fellowship, and Technical Literacy Support Institution Status. The Corporation shall have academy, training, fellowship, and technical literacy support institution status within its public-good technical mandate. This status shall authorize the Corporation to design, conduct, support, publish, restrict, evaluate, and improve educational programs, academy offerings, fellowships, technical residencies, workshops, learning modules, curricula, simulations, exercises, public authority learning sessions, community learning materials, and technical literacy materials.
Such activities may address evidence literacy, methods literacy, AI governance literacy, cybersecurity literacy, data governance literacy, observability literacy, public-good software literacy, open technical baseline literacy, verifiable compute literacy, public-safe claims literacy, public authority boundary literacy, finance-boundary literacy, certification-boundary literacy, community safeguards literacy, Indigenous knowledge respect, civil rights, accessibility, research integrity, and correctionability.
Academy, training, fellowship, and technical literacy support institution status shall not constitute professional licensure, regulated credentialing, certification, accreditation, procurement qualification, provider approval, public authority authorization, finance-readiness, insurance-readiness, investment suitability, rating, public finance approval, or legal compliance approval unless separately and lawfully issued by a competent body with authority to do so.
Learning records may identify attendance, completion, competence exposure, learning outcomes, curriculum version, instructor, assessment where applicable, limitations, access class, and correction status, but shall not be marketed or used as certification, professional license, official public authority qualification, procurement qualification, or regulated credential unless separately authorized.
38.15 Public-Safe Publication Institution Status. The Corporation shall have public-safe publication institution status within its public-good technical mandate. This status shall authorize the Corporation to publish, withhold, restrict, redact, aggregate, delay, correct, supersede, withdraw, retract, archive, or clarify public-facing and controlled materials in a manner that advances public-benefit purpose while reducing risk of harm.
Public-safe publications may include reports, whitepapers, methods notes, technical notes, evidence briefs, learning briefs, public authority learning materials, academy materials, dashboards, maps, datasets, software documentation, repository notices, baseline documents, public-safe summaries, controlled-room summaries, and Nexus-compatible materials.
Public-safe publication institution status shall require review for legal accuracy, evidentiary support, source lineage, uncertainty, public authority confusion, finance overclaim, certification overclaim, procurement implication, recognition implication, provider preference, sponsor control, cyber sensitivity, infrastructure sensitivity, health sensitivity, community sensitivity, Indigenous knowledge, protected knowledge, civil rights, accessibility, privacy, data protection, AI output limitations, competition concerns, sanctions, export control, and correction pathways.
No publication shall be treated as professional advice, legal advice, engineering opinion, clinical or medical advice, public health order, public warning, emergency instruction, regulatory approval, public authority decision, certification, recognition, finance-readiness, insurance approval, rating, investment recommendation, procurement recommendation, provider endorsement, or operational instruction unless expressly and lawfully authorized by a competent body and accurately described.
38.16 Non-Executing Technical Stewardship Institution Status. The Corporation’s public-good technical institution status shall at all times be non-executing technical stewardship status. Non-executing technical stewardship shall mean that the Corporation may steward technical evidence, methods, software, baselines, records, learning, safeguards, and correction, but shall not execute regulated, governmental, emergency, finance, procurement, certification, recognition, infrastructure, provider, or enterprise functions.
The Corporation shall not become an execution actor by reason of technical centrality, authorship, software release, repository control, dashboard operation, data-room administration, controlled-room administration, proof-receipt generation, AI-system use, model evaluation, digital twin use, sensor interpretation, AI-RAN signal interpretation, O-RAN signal interpretation, DePIN validation, ledger interaction, public authority meeting attendance, sponsor support, provider contribution, public recognition, media reference, or Nexus-interface participation.
Non-executing technical stewardship shall require the Corporation to separate:
a) research from deployment;
b) evidence from recognition;
c) methods from certification;
d) technical baselines from mandatory standards;
e) public authority learning from public authority decision-making;
f) finance-readiness inputs from finance-readiness determinations;
g) proof receipts from legal authority;
h) dashboards from public warnings;
i) software tools from operational command;
j) competence records from professional licenses;
k) public-good support from sponsor control; and
l) provider participation from provider preference.
Any activity that may cause the Corporation to be perceived as executing a prohibited or regulated function shall be escalated, held, stopped, quarantined, re-scoped, externalized, referred, restricted, corrected, or terminated as appropriate.
38.17 Public-Good Technical Institution Records. The Corporation shall maintain public-good technical institution records sufficient to demonstrate the basis, scope, limits, custody, security, publication status, public-safe status, safeguards status, and correction status of its public-good technical institution activities.
Public-good technical institution records shall include, as applicable:
a) public-good technical institution status records;
b) evidence institution records, evidence registers, source-lineage records, provenance records, confidence records, uncertainty records, evidence challenge records, and evidence correction records;
c) methods institution records, method registers, version records, validation records, limitation records, localization records, divergence logs, compatibility notes, and method correction records;
d) observability institution records, observatory method records, signal class records, dashboard records, sensor records, AI-RAN and O-RAN method records, DePIN records, DLT and blockchain validation records, digital twin assumption records, cyber telemetry records, geospatial records, and public-safe observability records;
e) ontology institution records, controlled vocabulary records, taxonomy records, schema records, data dictionary records, semantic change records, no-silent-meaning-shift records, and controlled-term correction records;
f) technical truth records, corroboration records, disputed evidence records, Truth Engine method records, failed-signal records, spoof-indicator records, confidence-output records, and truth-output correction records;
g) public-good R&D records, research records, prototype records, benchmark records, test harness records, evaluation records, reproducibility records, peer review records, research ethics records, and publication integrity records;
h) public-good software records, repository records, contribution records, licensing records, IP records, SBOM records, dependency records, vulnerability records, signing records, provenance records, secure release records, deprecation records, withdrawal records, takedown records, and archive records;
i) open technical baseline records, baseline status records, scope records, custodian records, applicability records, public-safe classification records, localization notes, supersession records, and withdrawal records;
j) verifiable compute and verifiable intelligence records, model registers, inference records, compute workload records, proof receipt records, secure enclave records, confidential computing records, sovereign compute records, human review records, and correctionable output records;
k) public authority learning records, capacity classifications, learning materials, participant records, non-reliance notices, public authority reference permissions, and clarification records;
l) academy, training, fellowship, technical literacy, competence exposure, curriculum, attendance, completion, assessment, limitation, and credential-boundary records;
m) public-safe publication records, publication review records, redaction records, aggregation records, delay records, release records, correction records, withdrawal records, retraction records, public clarification records, and archive records;
n) data / AI / cyber / privacy, export-control, sanctions, controlled-technology, national security sensitivity, public authority data, health-sensitive data, infrastructure-sensitive data, community-protected data, Indigenous data, and protected knowledge review records;
o) civil rights, accessibility, community safeguards, Tribal / Indigenous, local, territorial, public-safe mapping, do-no-harm, grievance, remedy, non-retaliation, withdrawal, and correction records;
p) role-separation, non-execution, public authority boundary, finance boundary, certification boundary, procurement neutrality, recognition boundary, provider neutrality, sponsor non-control, anti-capture, and regulated-perimeter review records;
q) records of holds, stops, quarantines, access restrictions, publication freezes, implementation freezes, technical isolations, re-scopes, referrals, externalizations, withdrawals, supersessions, takedowns, corrections, public-safe clarifications, legal responses, and closure actions; and
r) responsible owner, custodian, authority, effective date, review date, retention class, access class, publication class, legal hold status, repository location, and metadata.
The governing rule of this Section is that the Corporation’s technical power is a stewardship power, not an execution power. GCRI US may build public-good technical memory, software, methods, evidence, baselines, learning systems, and correction pathways for systemic-risk and exponential-technology contexts, but every such technical act shall remain bounded by public-benefit purpose, legal authority, role separation, non-execution, public-safe claims, data / AI / cyber discipline, community safeguards, validity-by-record, and correctionability.
Section 39. Relationship to The Global Centre for Risk and Innovation Function
39.1 GCRI Function Recognition. The Corporation recognizes that The Global Centre for Risk and Innovation function is a broader public-good institutional, technical, evidentiary, methodological, observability, ontology, technical truth, open technology, public-good research and development, public-good software, technical memory, public authority learning, and safeguards function that may be expressed through more than one lawful entity, jurisdictional anchor, cooperation instrument, public-good program, technical asset, repository, method family, or Nexus-compatible interface.
The recognition of the GCRI function shall not merge the Corporation with any other entity, instrument, program, interface, national expression, regional expression, public authority, Nexus entity, consortium, national company, Project SPV, provider, sponsor, host, university, laboratory, donor, funder, or enterprise actor. The Corporation shall remain a separate United States nonprofit corporation with its own legal personality, governing law, Board, officers, treasury, tax status, books, records, filings, liabilities, controls, and correction pathways.
The GCRI function shall be interpreted as a mission and role family, not as a single legal person unless a specific legal person is identified by record. No reference to “GCRI,” “the GCRI function,” “the Global Centre,” “GCRI North America,” “GCRI technical function,” “GCRI evidence function,” “GCRI methods function,” or similar expression shall substitute for the exact legal name, authority, capacity, and records of the entity acting.
39.2 GCRI as Evidence, Methods, Observability, Ontology, Technical Truth, Open Technology, Public-Good R&D, and Technical Memory Function. The GCRI function shall be understood as the public-good function responsible, within lawful and role-separated limits, for evidence stewardship, methods stewardship, observability stewardship, ontology stewardship, technical truth discipline, open technology stewardship, public-good research and development, public-good software, open technical baselines, verifiable compute and verifiable intelligence methods, correctionable technical memory, public authority learning support, and safeguards support.