ARTICLE IV. BOARD
Section 103. Board Authority and Role
103.1 Board as Governing Authority. The Board of Directors shall be the governing authority of the Corporation and shall exercise ultimate supervision, direction, fiduciary stewardship, constitutional oversight, mission-lock protection, public-benefit accountability, records discipline, and institutional boundary control over the affairs of The Global Centre for Risk and Innovation - United States.
The Board shall act as the highest internal authority of the Corporation except to the extent that applicable law, the Articles or Certificate, this Bylaw, or any member approval right required by law assigns a matter to another competent authority. The Board’s authority shall include the power and duty to govern the Corporation’s purposes, strategy, legal status, officers, committees, councils, finances, records, policies, public-good assets, evidence systems, methods, observability functions, ontology functions, technical baselines, public-good software, public authority learning interfaces, safeguards, Nexus interfaces, public-safe publications, and correction systems.
The Board shall not be a symbolic, advisory, ceremonial, sponsor-facing, public authority-facing, or technical-review body. It shall be the fiduciary governance organ of the Corporation and shall remain responsible for ensuring that all corporate powers are exercised lawfully, prudently, independently, transparently where appropriate, and consistently with the Corporation’s nonprofit, non-distributing, non-executing, public-benefit, evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, verifiable compute, verifiable intelligence, public authority learning, and Nexus-compatible public-good stewardship purposes.
The Board may act directly, through duly authorized officers, through Board committees, through authorized councils, through approved policies, through delegated authority matrices, through approved operating instruments, or through lawful written instruments; however, delegation shall not relieve the Board of its oversight duties, fiduciary responsibilities, boundary-protection responsibilities, or duty to preserve the Corporation’s legal and institutional character.
103.2 Authority Subject to Applicable Law. The Board’s authority shall be subject at all times to applicable law, including the governing nonprofit corporation statute of the Corporation’s state of incorporation or organization, applicable United States federal law, state law, territorial law, District of Columbia law where applicable, local law where applicable, Tribal and Indigenous governance respect obligations where lawfully engaged, federal tax law, state tax law, charitable solicitation law where applicable, employment law, privacy law, data protection law, cybersecurity law, AI-related legal requirements where applicable, export-control law, sanctions law, competition and antitrust law, government ethics law where applicable, lobbying and political activity law where applicable, grant compliance rules, public authority interaction rules, public records sensitivities where applicable, professional-boundary rules, and any other legal requirement binding upon the Corporation.
The Board shall not authorize, ratify, permit, tolerate, or fail to correct any act that is unlawful merely because the act is mission-aligned, technically valuable, sponsor-supported, funder-supported, publicly useful, urgent, strategically important, requested by a public authority, requested by a partner, beneficial to Nexus alignment, or convenient for implementation. Legal compliance shall be a condition of Board authority, not an external formality.
Where a proposed Board act, officer act, committee act, publication, technical release, controlled-room activity, public authority interface, finance-adjacent output, public-safe report, data handling activity, AI use, cyber operation, software release, grant, sponsorship, donation, provider interface, host interface, cross-border engagement, or Nexus interface raises legal uncertainty, the Board shall cause the matter to be reviewed through an appropriate legal, compliance, risk, safeguards, or counsel process before authorizing reliance, publication, launch, scaling, or public representation.
103.3 Authority Subject to Certificate or Articles of Incorporation. The Board’s authority shall be subject to the Articles or Certificate of Incorporation, charter, or other constituting instrument of the Corporation. The Board shall preserve the purposes, limitations, nonprofit character, public-benefit character, non-distribution character, corporate powers, member rights where applicable, director rules, dissolution requirements, and any other mandatory corporate-law provisions contained in the Articles or Certificate.
No Board resolution, policy, committee charter, officer delegation, program instrument, grant agreement, sponsorship agreement, public authority memorandum, Nexus interface instrument, repository rule, technical profile, proof receipt, controlled vocabulary, public-safe notice, operating procedure, or external communication shall amend, override, narrow, expand, or contradict the Articles or Certificate unless the Articles or Certificate are lawfully amended by competent authority and all required records, approvals, filings, notices, and effective-date conditions are satisfied.
Where the Articles or Certificate and this Bylaw appear to conflict, the Articles or Certificate shall control to the extent required by law, and the Board shall promptly cause the inconsistency to be reviewed, corrected, clarified, amended, superseded, or otherwise resolved through lawful governance action.
103.4 Authority Subject to This Bylaw. The Board shall exercise its authority subject to this Bylaw. This Bylaw shall govern the internal legal authority, fiduciary structure, public-benefit duties, governance processes, role boundaries, committee and council architecture, officer delegations, records discipline, evidence and methods stewardship, public-safe publication, data / AI / cyber controls, community safeguards, public authority boundaries, finance boundaries, certification boundaries, procurement-neutrality rules, provider-neutrality rules, sponsor non-control rules, Nexus interface discipline, validity-by-record, correctionability, and amendment processes of the Corporation.
The Board shall not exercise authority by informal custom, operational convenience, leadership assumption, technical centrality, sponsor expectation, provider expectation, public authority expectation, funding pressure, grant milestone, public statement, website description, board-deck reference, AI-generated summary, repository practice, or Nexus alignment unless such authority is supported by applicable law, the Articles or Certificate, this Bylaw, and a competent record.
The Board shall preserve this Bylaw as a binding governance instrument and shall ensure that lower-order instruments implement rather than alter it. Where an officer, committee, council, program, working group, controlled room, technical repository, public authority session, public-good software release, or Nexus interface acts inconsistently with this Bylaw, the Board shall cause the matter to be held, corrected, restricted, superseded, withdrawn, re-scoped, escalated, or otherwise remediated.
103.5 Authority Subject to Member Approval Where Required. Where the Corporation has statutory members, voting members, or any other member category with approval rights under applicable law, the Articles or Certificate, this Bylaw, or a competent corporate record, the Board shall respect such rights and shall not treat Board approval as sufficient where member approval is legally required.
Member approval may be required, depending on applicable law and governing instruments, for matters including amendment of the Articles or Certificate, merger, consolidation, conversion, dissolution, sale or disposition of substantially all assets, amendment or repeal of certain bylaws, election or removal of directors, changes to membership rights, or other fundamental corporate actions. The Board shall identify and record any member approval requirement before acting on a matter that may trigger such rights.
No officer, committee, council, sponsor, donor, funder, provider, public authority participant, Nexus entity, advisor, staff member, contractor, contributor, host, university, laboratory, national company, Project SPV, or enterprise actor shall substitute for a member approval where member approval is required by law or governing instrument.
103.6 Authority Subject to Federal Tax-Exempt or Tax-Exempt-Compatible Obligations. The Board shall exercise its authority in a manner consistent with the Corporation’s federal tax status, tax-exempt application status, tax-exempt-compatible posture, or other tax classification as recorded by the Corporation. The Board shall protect the Corporation against private inurement, impermissible private benefit, excess benefit transactions, improper political activity, unlawful lobbying activity where applicable, unrelated business activity risks where applicable, donor misrepresentation, improper receipting, restricted-fund misuse, and any act that may jeopardize tax-exempt or tax-exempt-compatible status.
The Board shall ensure that grants, donations, sponsorships, subscriptions, fees, cost recovery, in-kind support, fellowships, scholarships, awards, challenge support, public-good infrastructure support, and restricted funds are accepted, used, recorded, acknowledged, and reported in a manner consistent with applicable tax rules, nonprofit obligations, donor restrictions, public-benefit purposes, anti-capture controls, sponsor non-control, provider neutrality, public authority boundaries, and this Bylaw.
The Board shall not permit tax status to be represented inaccurately. If the Corporation has not obtained a particular tax-exempt status, charitable status, public charity status, private foundation status, supporting organization status, fiscal sponsorship status, or other legal classification, no Board member, officer, employee, contractor, donor, sponsor, funder, supporter, participant, or public-facing material shall represent that such status exists without competent record.
103.7 Authority Subject to State Nonprofit Corporate Obligations. The Board shall preserve the Corporation’s good standing and compliance under the governing state nonprofit corporation law and any other state, territorial, District of Columbia, or local law applicable to the Corporation’s activities. The Board shall ensure that the Corporation maintains required filings, registered agent records, registered office records, annual or periodic reports, franchise tax filings where applicable, charitable solicitation registrations where applicable, state tax records, director and officer records, minutes, resolutions, corporate books, member records where applicable, conflict records, and other legally required corporate records.
Where the Corporation operates, fundraises, employs personnel, contracts, maintains programs, conducts public authority learning, runs controlled rooms, receives data, publishes materials, hosts events, or otherwise represents itself in multiple states or territories, the Board shall require review of qualification, registration, charitable solicitation, tax, employment, privacy, procurement, public records, lobbying, government ethics, grant, contracting, and local-law obligations where applicable.
No all-states-and-territories operating posture shall be treated as legal permission to operate everywhere without required qualification, registration, review, safeguards, localized limitation language, or compliance records.
103.8 Authority Subject to Charitable Solicitation, Grant, Donation, Public Support, and Restricted Fund Obligations Where Applicable. The Board shall oversee charitable solicitation compliance where applicable, grant compliance, donation handling, sponsorship handling, restricted fund management, public support records, donor acknowledgment, funder reporting, sponsor acknowledgment, and in-kind contribution handling. The Board shall ensure that all such support is accepted and used only for lawful nonprofit, public-benefit, tax-compatible, mission-faithful, non-executing, anti-capture, provider-neutral, sponsor non-control, public-safe, and record-supported purposes.
The Board shall not permit any grant, donation, sponsorship, restricted fund, in-kind contribution, subscription, fee, or public-good support arrangement to purchase, condition, control, influence, suppress, predetermine, or distort:
a) research findings;
b) evidence classifications;
c) methods outcomes;
d) observability outputs;
e) ontology or controlled vocabulary meaning;
f) public-good software releases;
g) open technical baseline content;
h) public-safe publication decisions;
i) public authority access;
j) provider preference;
k) certification, recognition, finance-readiness, procurement advantage, Grid status, Docket status, or Nexus-compatible claim;
l) committee or council outcomes;
m) Board decisions; or
n) the Corporation’s legal, tax, public-benefit, non-execution, or Nexus role-separation posture.
Where a support arrangement creates risk of control, capture, private benefit, public authority confusion, finance overclaim, provider preference, procurement implication, certification implication, recognition implication, or protected knowledge harm, the Board shall require refusal, narrowing, restriction, ring-fencing, independent review, modified acknowledgment, return, termination, correction, or public-safe clarification.
103.9 Board Responsibility for Mission Lock. The Board shall preserve the Corporation’s mission lock. Mission lock means the binding governance obligation to maintain the Corporation as a United States nonprofit, nonstock or non-share, non-distributing, public-benefit, non-executing technical institution and United States / North America anchor for evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, verifiable compute and intelligence methods, public authority learning, community safeguards, and public-safe publication.
The Board shall reject any interpretation, transaction, program, partnership, technical integration, public authority interface, support arrangement, operating instrument, or Nexus interface that would convert the Corporation into:
a) a regulator;
b) an emergency command body;
c) an official public warning authority;
d) a procurement authority;
e) a certification or accreditation body by default;
f) a recognition or public-facing legitimacy body;
g) a finance-readiness, insurance-readiness, bankability, rating, or capital-readability body;
h) an investment adviser, broker, dealer, finder, lender, insurer, underwriter, rating agency, fund, bank, marketplace, or public finance approver;
i) a public authority or delegated governmental decision-maker;
j) a National Consortium Company, state or regional operating company, Project SPV, provider, operator, asset owner, or enterprise execution vehicle; or
k) a standards monopoly or protocol authority unless separately and lawfully constituted by competent authority and consistent with the Articles or Certificate and this Bylaw.
Mission lock shall be preserved through Board oversight, controlled vocabulary, authority matrices, approval thresholds, public-safe notices, policy review, legal review, records discipline, correctionability, and periodic review of institutional drift.
103.10 Board Responsibility for Public-Benefit Purpose. The Board shall ensure that the Corporation is operated for public-benefit purposes and not for private gain, private control, sponsor advantage, provider advantage, public authority substitution, political capture, market positioning, capital execution, procurement advantage, or institutional self-expansion inconsistent with its purposes.
The Board shall require that major programs, publications, technical releases, research initiatives, public authority learning sessions, controlled rooms, grants, sponsorships, data activities, AI activities, cyber activities, public-good software projects, observability work, ontology work, Nexus interfaces, and stakeholder participation systems be assessed for public-benefit alignment. Public-benefit alignment shall include, as applicable:
a) evidence integrity;
b) methods integrity;
c) research integrity;
d) public-good technical utility;
e) public authority learning value without public authority substitution;
f) community safeguards;
g) civil rights and accessibility protection;
h) Indigenous, Tribal, local, territorial, cultural, environmental, and protected knowledge respect;
i) public-safe publication;
j) correctionability;
k) validity-by-record;
l) anti-capture discipline;
m) provider neutrality;
n) sponsor non-control; and
o) consistency with the Corporation’s nonprofit and non-executing character.
The Board shall not permit public-benefit language to be used as a pretext for unlawful activity, private benefit, unsupported claims, unsafe publication, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, or enterprise execution.
103.11 Board Responsibility for Nonprofit and Non-Distribution Character. The Board shall protect the Corporation’s nonprofit and non-distribution character. The Board shall ensure that no part of the Corporation’s net earnings, assets, funds, technical assets, software assets, data assets, intellectual property assets, repository assets, public-good assets, restricted funds, or public-support resources inures to the benefit of any director, officer, member, sponsor, donor, funder, provider, host, contractor, founder, related party, private person, enterprise actor, national company, Project SPV, or other private interest except as lawful, reasonable, documented, conflict-reviewed, purpose-aligned, and permitted by applicable law and governing instruments.
The Board may authorize reasonable compensation, reimbursement, grants, stipends, scholarships, awards, fellowships, contractor payments, vendor payments, public-good support, and program expenditures where lawful and documented. Such payments shall not be used to disguise private inurement, sponsor control, provider preference, improper private benefit, procurement advantage, finance-readiness purchase, recognition purchase, certification purchase, or public authority access purchase.
The Board shall maintain or require appropriate records showing that the Corporation’s assets are dedicated to lawful public-benefit purposes and that any distribution, transfer, payment, license, grant, contract, support arrangement, or asset use is consistent with nonprofit law, tax posture, fiduciary duty, and this Bylaw.
103.12 Board Responsibility for Evidence, Methods, Observability, Ontology, Technical Truth, Public-Good R&D, Public-Good Software, and Open Technical Baselines. The Board shall oversee the Corporation’s core public-good technical functions, including evidence doctrine, methods stewardship, observability, ontology, semantic interoperability, technical truth methods, public-good research and development, public-good software, open technical baselines, verifiable compute and verifiable intelligence methods, public authority learning tools, public-safe publications, and correctionable technical memory.
The Board shall ensure that these functions are governed by records, source lineage, versioning, custodianship, method status, confidence and uncertainty handling, data quality controls, human review rules, public-safe classification, access classification, correction pathways, and boundary language. The Board shall require heightened review where outputs relate to AI, agentic AI, AI-RAN, O-RAN, private wireless, DePIN, DLT, blockchain, Web3, sovereign compute, edge compute, HPC, cybersecurity, cyber-physical systems, robotics, drones, sensors, geospatial systems, Earth observation, digital twins, biosecurity, climate, nature, biodiversity, energy, water, food, health, disaster resilience, telecommunications, supply chains, ports, borders, advanced manufacturing, semiconductors, quantum-relevant systems, public trust, or other exponential and mission-critical technologies.
The Board shall ensure that no evidence output, method, observability signal, ontology term, technical truth output, public-good software release, technical baseline, benchmark, proof receipt, dashboard, model output, digital twin, sensor signal, AI-RAN signal, DePIN record, DLT or blockchain entry, or public-safe report is represented as public authority action, public warning, emergency command, recognition, maturity status, finance-readiness, insurance-readiness, rating, certification, procurement approval, provider approval, or enterprise execution unless separately and lawfully authorized by competent authority and supported by record.
103.13 Board Responsibility for United States All-States-and-Territories Posture. The Board shall oversee the Corporation’s United States all-states-and-territories posture. This posture permits the Corporation, where lawful and properly recorded, to operate, engage, learn, publish, convene, support public-good technical work, coordinate with public authorities, and maintain interfaces across the fifty states, the District of Columbia, Puerto Rico, Guam, the U.S. Virgin Islands, American Samoa, the Northern Mariana Islands, Tribal and Indigenous governance contexts where lawfully and respectfully engaged, and local, county, municipal, metropolitan, utility, port, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, and infrastructure contexts.
The Board shall ensure that all-states-and-territories posture does not become an assertion of state authority, territorial authority, Tribal authority, federal authority, public finance authority, procurement authority, regulatory authority, emergency command authority, public warning authority, certification authority, recognition authority, or operational control. The Board shall require state-specific, territorial-specific, District of Columbia-specific, Tribal-interface, local, and sectoral review where activities may trigger legal, public authority, privacy, public records, open meetings, procurement, lobbying, charitable solicitation, tax, employment, data, AI, cyber, accessibility, civil rights, protected knowledge, or public-safe communication obligations.
The Board shall cause the Corporation to maintain records sufficient to show where and how the Corporation operates, represents itself, solicits support, convenes programs, handles data, engages public authorities, publishes outputs, maintains controlled rooms, or interfaces with Nexus systems within the United States and its territories.
103.14 Board Responsibility for North America Anchor Role. The Board shall oversee the Corporation’s North America anchor role as a bounded public-good technical function. The North America anchor role may support evidence architecture, methods continuity, observability and ontology alignment, public-good software, open technical baselines, Nexus Observatory methods, Nexus Truth Engine methods, verifiable compute and intelligence methods, public authority learning, technical literacy, cross-border learning, and safeguards for North America-relevant risk and resilience contexts.
The Board shall ensure that North America anchor language is used only where lawful, accurate, record-supported, and not legally confusing. The North America anchor role shall not imply that the Corporation owns, governs, controls, represents, supervises, or binds GCRI Canada, any Mexico-facing interface, Caribbean interface, Arctic interface, Great Lakes interface, Pacific interface, Atlantic interface, Gulf interface, Indigenous government, public authority, regional Nexus body, national Nexus body, university, laboratory, sponsor, provider, host, Project SPV, national company, or enterprise actor.
The Board shall ensure that the North America anchor role is not represented as North America sovereign authority, treaty authority, intergovernmental authority, public finance authority, regional regulator, public procurement authority, public warning authority, emergency command authority, certification authority, recognition authority, finance-readiness authority, protocol authority, or enterprise execution authority. Cross-border coordination shall be lawful, bounded, recorded, public-safe, and compatible with the legal separateness of GCRI US, GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus entities, public authorities, and enterprise actors.
103.15 Board Responsibility for Nexus Role Separation. The Board shall preserve role separation within the Nexus public-good architecture. The Board shall ensure that the Corporation remains within the GCRI function as evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, verifiable compute and intelligence methods, public authority learning, and research-integrity steward.
The Board shall ensure that the Corporation does not collapse or assume the functions of:
a) The Global Risks Forum (GRF), which is the public-good registry, recognition, maturity-records, standing, claims-discipline, stakeholder-formation, public-safe reporting, and public-facing legitimacy steward;
b) The Global Risks Alliance (GRA), which is the finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, capital-reader-room, and regulated-perimeter discipline steward;
c) Nexus Standards or any protocol authority where separately constituted;
d) Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, or Nexus Competence Cells;
e) Global, regional, national, state, territorial, Tribal, metropolitan, local, or sectoral Nexus consortiums;
f) National Consortium Companies, state or regional operating companies, Project SPVs, Qualified Enterprise Providers, hosts, sponsors, vendors, contractors, operators, asset owners, investors, insurers, lenders, underwriters, banks, public finance actors, or enterprise execution vehicles; or
g) public authorities or regulated decision-makers.
The Board shall require compatibility notes, divergence logs, interface records, controlled vocabulary, limitation language, public-safe notices, and correction pathways where Nexus interfaces create risk of role confusion.
103.16 Board Responsibility for Non-Execution. The Board shall preserve the Corporation’s non-execution character. The Corporation may produce evidence, methods, public-good software, technical baselines, controlled vocabulary, observability methods, ontology structures, public authority learning materials, public-safe publications, proof-support materials, Nexus-compatible technical inputs, and correction signals; however, it shall not execute regulated or reserved functions unless separately and lawfully authorized in a manner consistent with applicable law, the Articles or Certificate, this Bylaw, and competent records.
The Board shall ensure that the Corporation does not conduct, offer, arrange, intermediate, broker, advise on as a regulated actor, underwrite, distribute, custody, clear, settle, guarantee, insure, reinsure, lend, rate, procure, certify, recognize, command, warn as a public authority, regulate, approve legal compliance, approve public finance, approve investment, select providers for public authorities, operate infrastructure as public authority, or execute enterprise delivery by implication, technical integration, controlled-room design, data-room operation, dashboard display, AI output, digital twin, proof receipt, blockchain record, DePIN record, AI-RAN signal, public-safe report, grant relationship, sponsor relationship, public authority participation, or Nexus association.
Where non-execution risk arises, the Board shall require hold, quarantine, legal review, re-scoping, externalization to a lawful actor, referral to a competent authority, corrected language, withdrawal, or termination.
103.17 Board Responsibility for Public Authority Boundaries. The Board shall ensure that the Corporation’s public authority interfaces remain learning, evidence, methods, technical literacy, public-safe communication, and public-good support interfaces only, unless a lawful and recorded instrument establishes a narrower and permitted role.
The Board shall ensure that public authority participation, public authority room attendance, regulator-listening participation, public finance reader participation, emergency-management learning participation, public infrastructure operator participation, simulation participation, tabletop exercises, after-action learning, public authority data contribution, public authority comments, public authority requests, or public authority familiarity do not create public authority delegation, official adoption, public procurement approval, funding approval, regulatory approval, public finance approval, sovereign obligation, public-private partnership status, public warning authority, emergency command authority, or authority to speak for a public authority.
The Board shall require public authority capacity classification, official-reference controls, public-safe notices, meeting records, access controls, limitation language, and correction mechanisms for material public authority interfaces.
103.18 Board Responsibility for Finance, Securities, Insurance, Lending, Rating, Public Finance, Procurement, and Certification Boundaries. The Board shall oversee and preserve the Corporation’s finance, securities, insurance, lending, rating, public finance, procurement, certification, accreditation, recognition, and professional-boundary discipline. The Board shall ensure that the Corporation does not act as an investment adviser, broker, dealer, finder, underwriter, lender, bank, fund, marketplace, insurer, reinsurer, insurance producer, rating agency, credit opinion provider, public finance approver, procurement authority, certification body, accreditation body, or legal compliance approver unless a future lawful instrument expressly and narrowly authorizes a function consistent with applicable law and this Bylaw.
The Board shall ensure that GCRI US outputs, including evidence records, methods, technical baselines, observability outputs, proof receipts, public-good software, dashboards, risk categories, resilience indicators, benchmark outputs, public authority learning materials, controlled-room materials, and Nexus interface inputs, are not represented as:
a) securities offerings;
b) investment recommendations;
c) financing approvals;
d) capital-readability determinations;
e) finance-readiness determinations;
f) insurance-readiness determinations;
g) bankability determinations;
h) ratings;
i) credit opinions;
j) underwriting bases;
k) public finance approvals;
l) procurement approvals;
m) vendor selections;
n) certification or accreditation outcomes;
o) recognition or maturity status; or
p) public authority approvals.
The Board shall require review of finance-adjacent, procurement-adjacent, certification-adjacent, rating-adjacent, public finance-adjacent, and public authority-adjacent materials before publication, controlled release, sponsor use, provider use, grant use, capital-reader use, or public representation.
103.19 Board Responsibility for Data / AI / Cyber / Privacy Controls. The Board shall oversee the Corporation’s data governance, privacy, AI governance, cybersecurity, secure compute, model governance, inference record, compute workload, repository, software release, controlled-room, data-room, public authority data, rights-bearing data, and incident-response controls.
The Board shall ensure that the Corporation maintains appropriate policies, registers, access controls, security measures, privacy controls, AI-use rules, model registers, inference records, compute workload records, dataset cards, model cards, system cards, benchmark cards, SBOM records, vulnerability records, key and credential controls, incident records, backup and disaster recovery plans, business continuity plans, legal holds, retention rules, deletion rules, and correction pathways.
The Board shall require heightened review for personal information, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, public authority-sensitive data, commercially sensitive data, finance-sensitive data, community-protected data, Tribal or Indigenous data, local or territorial knowledge, protected knowledge, cross-border data, sovereign-sensitive data, AI training or fine-tuning materials, embedding or retrieval systems, agentic AI workflows, public repositories, open releases, public dashboards, public maps, on-chain artifacts, DLT records, DePIN records, digital twins, and AI-RAN or O-RAN signals.
No AI system, automated workflow, model output, agentic action, dashboard state, ledger entry, proof receipt, digital twin, sensor output, AI-RAN signal, DePIN record, or cyber telemetry output shall be treated as Board decision, officer decision, public authority decision, public warning, emergency command, certification, recognition, finance-readiness, procurement approval, provider approval, or final institutional truth unless supported by competent human authorization, record, review, limitation, and correction pathway.
103.20 Board Responsibility for Community, Tribal, Indigenous, Local, Territorial, Protected Knowledge, Civil Rights, Accessibility, and Public-Safe Safeguards. The Board shall oversee safeguards for communities, Tribal and Indigenous interfaces, local and territorial knowledge, cultural knowledge, environmental knowledge, protected knowledge, civil rights, non-discrimination, accessibility, vulnerable persons, remote communities, protected participants, whistleblowers, confidential sources, public-safe mapping, grievance pathways, remedy pathways, protected participation, and non-retaliation.
The Board shall ensure that the Corporation does not extract, expose, publish, tokenize, commercialize, map, operationalize, train AI on, transfer, or repurpose protected knowledge, Indigenous knowledge, Tribal data, local knowledge, territorial knowledge, community-protected information, sensitive environmental information, sensitive cultural information, or rights-bearing data except under recorded authority, lawful basis, safeguards, access controls, limitation language, and correction pathways.
The Board shall ensure that accessibility and civil rights are treated as substantive governance obligations and not as secondary communications preferences. Where the Corporation’s activities may affect persons, communities, public authorities, protected participants, or knowledge holders, the Board shall require review proportionate to the risk of harm, exposure, discrimination, stigmatization, displacement, retaliation, surveillance, re-identification, cultural harm, public safety harm, or protected knowledge misuse.
103.21 Board Responsibility for Provider Neutrality and Sponsor Non-Control. The Board shall preserve provider neutrality and sponsor non-control. The Corporation may interact with providers, vendors, contractors, sponsors, donors, funders, hosts, universities, laboratories, public authorities, national companies, Project SPVs, and enterprise actors where lawful and mission-aligned; however, no such actor shall control the Corporation’s governance, agenda, evidence, methods, observability, ontology, technical baselines, public-good software, public-safe publications, public authority access, controlled rooms, research findings, committee outcomes, Board decisions, personnel appointments, Nexus interface outputs, or correction processes.
The Board shall ensure that provider participation does not create preferred provider status, required provider status, procurement advantage, public authority endorsement, certification, recognition, finance-readiness, Grid status, Docket status, Nexus-compatible status, or technical monopoly. The Board shall ensure that sponsor, donor, funder, or host support does not create agenda control, outcome purchase, publication veto, public authority access purchase, provider preference, research finding purchase, recognition purchase, finance-readiness purchase, certification purchase, procurement advantage, or public-safe claim control.
Where a provider, sponsor, donor, funder, host, contractor, investor, insurer, lender, national company, Project SPV, or enterprise actor relationship creates actual, potential, or perceived capture risk, the Board shall require disclosure, independent review, recusal, ring-fencing, influence caps, diversification, access restriction, limitation language, public-safe clarification, refusal, return of support, termination, or other corrective action.
103.22 Board Responsibility for Validity-by-Record. The Board shall preserve validity-by-record as a governing principle of the Corporation. No material institutional claim, authority, status, publication, record, approval, delegation, appointment, technical baseline, method, evidence output, observability output, public-safe report, public authority capacity, controlled-room status, public-good software release, proof receipt, correction, supersession, withdrawal, or Nexus interface output shall be treated as valid merely by assertion, reputation, seniority, authorship, technical centrality, sponsor use, provider use, public authority familiarity, website presence, repository presence, meeting reference, AI-generated summary, or repeated practice.
Validity shall arise from competent authority, recorded process, evidence, provenance, source lineage, version control, custody, approval, effective date, review, limitation, public-safe classification, access classification, correction history, and accountable stewardship.
The Board shall require that material governance and technical acts be traceable to records sufficient to show:
a) who acted;
b) under what authority;
c) on what evidence;
d) under what method or policy;
e) with what limitations;
f) with what public-safe status;
g) with what access and publication class;
h) with what correction pathway;
i) with what effective date; and
j) with what supersession, withdrawal, archival, or review status.
103.23 Board Responsibility for Correctionability. The Board shall preserve correctionability as a binding institutional discipline. The Corporation’s governance records, evidence records, methods, observability outputs, ontology terms, technical truth outputs, public-good software, open technical baselines, public-safe publications, dashboards, maps, proof receipts, model outputs, compute outputs, public authority learning materials, controlled-room records, Nexus interface inputs, public claims, and participation records shall be correctable where error, incompleteness, ambiguity, overclaim, misuse, boundary breach, data issue, AI issue, cyber issue, research integrity issue, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, protected knowledge issue, civil rights issue, accessibility issue, safeguards concern, or legal defect is identified.
The Board shall ensure that correction mechanisms include, as applicable:
a) challenge intake;
b) review;
c) hold;
d) access restriction;
e) clarification;
f) correction;
g) limitation;
h) supersession;
i) withdrawal;
j) suspension;
k) downgrade;
l) retraction;
m) takedown;
n) archival;
o) public-safe notice;
p) controlled notice;
q) legal or safeguards escalation;
r) post-correction review; and
s) recurrence prevention.
The Board shall ensure that correction is not treated as reputational weakness. Correctionability is a condition of public trust, evidence integrity, technical truth, public-safe reporting, and Nexus-compatible legitimacy.
103.24 Board Authority Records. The Corporation shall maintain Board Authority Records sufficient to demonstrate the lawful source, scope, exercise, delegation, limitation, review, and correction of Board authority.
Board Authority Records shall include, as applicable:
a) Articles or Certificate records, bylaw records, Board resolution records, member approval records where applicable, adoption records, amendment records, restatement records, supersession records, withdrawal records, and effective-date records;
b) director register records, officer register records, committee charter records, council charter records, delegation matrix records, authority matrix records, reserved matter records, policy approval records, protocol approval records, schedule approval records, technical profile approval records, controlled vocabulary approval records, and public-safe notice library approval records;
c) mission-lock records, public-benefit purpose records, nonprofit character records, non-distribution records, private inurement review records, private benefit review records, tax-exempt or tax-exempt-compatible records, charitable solicitation records, grant records, donation records, sponsorship records, restricted fund records, and public support records;
d) evidence oversight records, methods oversight records, observability oversight records, ontology oversight records, technical truth oversight records, public-good R&D oversight records, public-good software oversight records, open technical baseline oversight records, verifiable compute oversight records, verifiable intelligence oversight records, Nexus Truth Engine methods oversight records, Nexus Observatory methods oversight records, and public-safe publication oversight records;
e) United States all-states-and-territories records, state qualification records, territorial records, District of Columbia records, Tribal-interface records, local interface records, North America anchor records, cross-border records, GCRI Canada interface records, GRF interface records, GRA interface records, Nexus interface records, compatibility notes, divergence logs, and equivalence notes;
f) non-execution records, public authority boundary records, finance-boundary records, securities-boundary records, insurance-boundary records, lending-boundary records, rating-boundary records, public finance-boundary records, procurement-neutrality records, certification-boundary records, recognition-boundary records, provider-neutrality records, sponsor non-control records, anti-capture records, and regulatory-perimeter review records;
g) data governance records, privacy records, AI governance records, cybersecurity records, secure compute records, model register records, inference record records, compute workload records, repository records, software release records, SBOM records, vulnerability records, incident records, business continuity records, disaster recovery records, access records, and controlled-room records;
h) community safeguard records, Tribal and Indigenous protocol records, Indigenous data safeguard records, protected knowledge records, local and territorial knowledge records, civil rights records, accessibility records, public-safe mapping records, grievance records, remedy records, protected participation records, non-retaliation records, and stop-the-line records;
i) records of Board review, Board deliberation, Board vote, Board abstention, Board recusal, Board dissent where recorded, Board ratification, Board correction, Board hold, Board quarantine, Board restriction, Board withdrawal, Board public-safe clarification, Board legal referral, and Board escalation; and
j) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that the Board is the Corporation’s fiduciary and constitutional governance authority, but its authority is bounded. The Board may govern, steward, supervise, approve, delegate, correct, and preserve the Corporation’s public-benefit technical mission; it may not use governance authority to authorize prohibited execution, public authority substitution, finance-readiness determinations, certification, procurement approval, recognition, provider preference, sponsor control, private inurement, unsafe publication, protected knowledge misuse, or Nexus role collapse. Board authority shall be lawful, recorded, bounded, reviewable, public-safe where relevant, and correctionable.
Section 104. Fiduciary Duties of Directors
104.1 Fiduciary Duty Purpose. Each director shall serve the Corporation as a fiduciary and shall exercise the powers of office in a manner consistent with applicable law, the Articles or Certificate, this Bylaw, Board resolutions, duly adopted policies, the Corporation’s public-benefit purposes, nonprofit and non-distribution character, tax-exempt or tax-exempt-compatible obligations, mission lock, non-execution perimeter, public authority boundaries, finance and regulated-activity boundaries, data / AI / cyber controls, community safeguards, public-safe publication discipline, validity-by-record, correctionability, and Nexus role separation.
The fiduciary duties of directors shall be interpreted in light of the Corporation’s institutional character as a United States nonprofit, public-benefit, non-executing 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 and intelligence methods, public authority learning, community safeguards, and public-safe reporting support. A director’s duty shall not be measured only by ordinary corporate efficiency, fundraising success, market influence, technical output, sponsor satisfaction, public authority attention, provider adoption, or ecosystem visibility, but by faithful stewardship of the Corporation’s lawful public-good mandate and the controls required to preserve trust.
Directors shall govern with disciplined independence, informed judgment, recorded process, lawful authority, public-benefit orientation, and correctionable decision-making. A director shall not use the office to advance private interest, sponsor interest, provider interest, political interest, public authority substitution, finance-readiness overclaim, recognition overclaim, certification overclaim, procurement influence, enterprise execution, or any other purpose inconsistent with the Corporation’s mission lock.
104.2 Duty of Care. Each director shall discharge the duties of office with the care that an ordinarily prudent person in a comparable position would reasonably exercise under similar circumstances, taking into account the Corporation’s nonprofit, public-benefit, technical, evidence, research, public authority learning, data / AI / cyber, safeguards, multi-jurisdictional, and Nexus-interface context.
The duty of care shall require a director, as applicable, to:
a) prepare for Board meetings and material decisions;
b) review relevant materials with sufficient diligence;
c) ask reasonable questions;
d) consider legal, financial, technical, evidence, public authority, safeguards, data, AI, cyber, privacy, competition, sanctions, export-control, protected knowledge, public-safe publication, and Nexus role-separation risks;
e) request additional information where the record is materially incomplete;
f) cause expert, counsel, technical, compliance, financial, safeguards, or community review where reasonably necessary;
g) monitor implementation of Board decisions;
h) require correction where facts, methods, authority, boundary assumptions, or outputs prove defective;
i) preserve institutional records sufficient to demonstrate informed decision-making; and
j) avoid passive approval of matters that materially affect the Corporation’s mission, legal status, tax posture, public-benefit purpose, public authority boundaries, finance boundaries, certification boundaries, data / AI / cyber controls, safeguards, public-safe claims, or Nexus interfaces.
A director may rely in good faith on officers, employees, committees, counsel, accountants, technical experts, safeguards experts, researchers, public authority interface records, or other competent persons where such reliance is reasonable, informed, conflict-reviewed where appropriate, and not contradicted by facts known to the director.
104.3 Duty of Loyalty. Each director shall act loyally in the best interests of the Corporation and its public-benefit purposes, and shall not subordinate the Corporation’s interests to personal, professional, financial, political, institutional, sponsor, donor, funder, provider, host, contractor, public authority, investor, insurer, lender, national company, Project SPV, university, laboratory, employer, affiliate, or enterprise interests.
The duty of loyalty shall require a director to:
a) disclose actual, potential, and perceived conflicts of interest;
b) disclose related-party relationships;
c) disclose dual roles across GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus entities, public authorities, sponsors, providers, national companies, Project SPVs, universities, laboratories, hosts, donors, funders, investors, insurers, lenders, contractors, or enterprise actors;
d) refrain from using confidential, privileged, controlled, technical, research, protected knowledge, public authority, data-room, clean-room, controlled-room, repository, or Board information for personal or third-party advantage;
e) refrain from diverting corporate opportunities, public-good opportunities, grants, donors, sponsors, technical assets, software assets, datasets, repositories, public authority relationships, research opportunities, or Nexus interfaces for private or conflicted advantage;
f) refrain from causing the Corporation to prefer a provider, sponsor, donor, funder, host, employer, affiliate, national company, Project SPV, or enterprise actor without lawful, recorded, conflict-reviewed, mission-aligned basis; and
g) submit to recusal, access restriction, independent review, or other mitigation where required.
A director shall not use loyalty to the broader Nexus mission as a basis to weaken loyalty to the Corporation’s legal separateness, fiduciary governance, United States nonprofit obligations, Board authority, records discipline, or mission lock.
104.4 Duty of Obedience to Mission and Law Where Applicable. Each director shall owe a duty of obedience to the Corporation’s lawful purposes, applicable law, the Articles or Certificate, this Bylaw, and the Corporation’s public-benefit mission. The duty of obedience shall require directors to ensure that the Corporation acts within its purposes and does not drift into prohibited, unauthorized, unlawful, or role-collapsing activity.
The duty of obedience shall include the duty to preserve:
a) the Corporation’s nonprofit, nonstock or non-share, non-distributing, and public-benefit character;
b) tax-exempt or tax-exempt-compatible purposes;
c) evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, and open technical baseline functions;
d) non-execution;
e) public authority boundary discipline;
f) finance, securities, insurance, lending, rating, public finance, procurement, certification, accreditation, recognition, and professional-boundary discipline;
g) data / AI / cyber / privacy controls;
h) research integrity and public-safe publication;
i) community safeguards, civil rights, accessibility, Tribal and Indigenous protocol respect, and protected knowledge safeguards;
j) GCRI / GRF / GRA role separation;
k) public-good stack and enterprise stack separation;
l) United States all-states-and-territories localization without fragmentation;
m) North America anchor role boundaries;
n) validity-by-record; and
o) correctionability.
A director shall not knowingly approve or fail to challenge an act that converts the Corporation into a regulator, emergency command body, public warning authority, procurement body, certification body, recognition body, finance-readiness body, broker, dealer, finder, investment adviser, lender, insurer, rating agency, public finance approver, public authority, provider, operator, asset owner, national company, Project SPV, or enterprise execution vehicle.
104.5 Duty of Good Faith. Each director shall act in good faith, with honest purpose, lawful intent, public-benefit orientation, institutional seriousness, and reasonable belief that the action taken is in the best interests of the Corporation and consistent with its mission and governing instruments.
Good faith shall not exist where a director knowingly:
a) authorizes unlawful action;
b) ignores material legal, financial, technical, safeguards, data, AI, cyber, privacy, public authority, finance, certification, procurement, recognition, competition, sanctions, export-control, protected knowledge, or public-safe publication risk;
c) conceals conflicts;
d) permits sponsor or provider control;
e) approves private inurement or impermissible private benefit;
f) tolerates unsupported status claims;
g) permits public authority confusion;
h) permits finance-readiness, certification, procurement, or recognition overclaim;
i) suppresses material corrections;
j) allows misleading public statements;
k) permits misuse of the Corporation’s name, marks, records, reports, datasets, software, technical baselines, controlled rooms, proof receipts, public authority references, or Nexus-compatible claims; or
l) treats institutional convenience, fundraising pressure, sponsor preference, provider pressure, publication urgency, technical momentum, public authority request, or reputational concern as superior to law, mission lock, fiduciary duty, and this Bylaw.
Good faith shall require timely escalation where a director becomes aware of a material boundary issue, conflict, defect, misuse, harm, legal issue, technical vulnerability, safeguards breach, data incident, AI incident, cyber incident, public-safe publication issue, or correction need.
104.6 Duty of Prudence. Each director shall act prudently in the stewardship of the Corporation’s assets, relationships, technical systems, records, public-good software, datasets, repositories, controlled rooms, public authority interfaces, grants, donations, sponsorships, restricted funds, human resources, intellectual property, public reputation, and Nexus interfaces.
Prudence shall require directors to consider:
a) whether an activity is lawful and within corporate purposes;
b) whether it creates undue financial, operational, technical, cyber, data, AI, privacy, legal, public authority, safeguards, public-safe publication, or reputation risk;
c) whether the Corporation has adequate capacity, controls, budget, personnel, insurance, records, counsel, technical safeguards, and governance oversight;
d) whether the activity creates sponsor, donor, funder, provider, host, public authority, investor, insurer, lender, national company, Project SPV, or enterprise capture risk;
e) whether public-good assets are protected against enclosure, misuse, misrepresentation, unsupported commercialization, unauthorized licensing, or technical compromise;
f) whether restricted funds and public support are used for permitted purposes;
g) whether public authority and finance-adjacent materials are properly bounded;
h) whether data, AI, cyber, privacy, and protected knowledge risks are controlled; and
i) whether correction pathways exist.
Prudence shall not require risk elimination, but shall require risks to be identified, bounded, recorded, monitored, escalated, and corrected in proportion to their seriousness.
104.7 Duty of Diligence. Each director shall exercise diligence in attending meetings, reviewing materials, monitoring the Corporation’s condition, participating in Board deliberations, discharging committee assignments where applicable, reviewing major risks, and following up on material matters within the director’s knowledge or assigned responsibilities.
Diligence shall include attention to:
a) Board agendas and materials;
b) financial reports and budgets;
c) grant, donation, sponsorship, restricted fund, and public support reports;
d) legal and compliance reports;
e) tax status and state compliance reports;
f) risk, issue, incident, and control registers;
g) evidence, methods, observability, ontology, technical truth, public-good software, and technical baseline reports;
h) data / AI / cyber / privacy reports;
i) safeguards and protected knowledge reports;
j) public authority interface reports;
k) finance-boundary, procurement-neutrality, certification-boundary, recognition-boundary, provider-neutrality, and sponsor non-control reports;
l) Nexus interface, compatibility note, divergence log, and correction reports; and
m) Board action items and implementation records.
Persistent failure to participate, persistent failure to review materials, persistent failure to disclose conflicts, or persistent failure to engage with known material risks may constitute a breach of duty and may be grounds for corrective action, restriction, non-renewal, or removal where permitted by law and governing instruments.
104.8 Duty of Independence. Each director shall exercise independent judgment and shall not permit judgment to be compromised by personal benefit, employment relationship, consulting relationship, funding relationship, political pressure, public authority relationship, sponsor relationship, provider relationship, host relationship, investor relationship, insurer relationship, lender relationship, national company relationship, Project SPV relationship, institutional affiliation, reputational interest, social pressure, technical allegiance, donor preference, or Nexus ecosystem pressure.
Independence shall require directors to distinguish between:
a) the Corporation’s legal interests and the interests of GCRI Canada;
b) the Corporation’s evidence and methods function and the recognition function of The Global Risks Forum (GRF);
c) the Corporation’s technical input function and the finance-readiness function of The Global Risks Alliance (GRA);
d) the Corporation’s public-good technical stewardship and any Nexus Standards or protocol authority function;
e) the Corporation’s non-executing role and the execution role of national companies, Project SPVs, providers, operators, sponsors, hosts, or enterprise actors;
f) public authority learning and public authority action; and
g) public-good support and sponsor control.
A director who cannot exercise independent judgment on a matter shall disclose the limitation and shall submit to recusal, access restriction, abstention, independent review, committee exclusion, or other mitigation as determined under the Corporation’s conflict and independence rules.
104.9 Duty to Act in the Best Interests of GCRI US. Each director shall act in the best interests of The Global Centre for Risk and Innovation - United States as a separate legal entity. The best interests of the Corporation shall be understood through its lawful purposes, public-benefit mission, nonprofit character, tax posture, fiduciary obligations, records discipline, mission lock, institutional separateness, and public-good role.
A director shall not treat the best interests of any other person or entity as equivalent to the best interests of the Corporation, including:
a) any founder;
b) any director or officer;
c) any member or participant;
d) GCRI Canada;
e) any other GCRI entity;
f) The Global Risks Forum (GRF);
g) The Global Risks Alliance (GRA);
h) Nexus Network, Nexus Standards, or any Nexus entity;
i) any public authority;
j) any sponsor, donor, funder, host, provider, vendor, contractor, university, laboratory, investor, insurer, lender, underwriter, public finance actor, national company, Project SPV, or enterprise actor; or
k) any political, commercial, professional, or community group.
Coordination, shared mission, shared doctrine, shared methods, shared ontology, shared public-good technical assets, shared events, shared councils, shared records, or shared Nexus interfaces shall not eliminate the director’s duty to act in the best interests of the Corporation as a legally separate entity.
104.10 Duty to Preserve Public-Benefit Purpose. Each director shall preserve the Corporation’s public-benefit purpose and shall ensure that programs, transactions, publications, technical releases, controlled rooms, public authority interfaces, data activities, AI activities, cyber activities, research initiatives, grants, sponsorships, donations, contracts, and Nexus interfaces serve lawful public-good purposes.
The duty to preserve public-benefit purpose shall require directors to prevent the Corporation from being used primarily for:
a) private gain;
b) sponsor advantage;
c) provider advantage;
d) donor or funder control;
e) public authority substitution;
f) political or partisan advantage;
g) procurement influence;
h) capital placement;
i) investment, insurance, lending, rating, or public finance execution;
j) certification or recognition sales;
k) technology marketing;
l) enterprise delivery;
m) extraction of protected knowledge;
n) reputational laundering;
o) unsupported public claims; or
p) any purpose inconsistent with the Corporation’s lawful mission.
Where a public-benefit rationale is asserted for a material action, the Board may require a public-benefit record identifying the purpose, beneficiaries, risks, safeguards, legal basis, funding source, conflicts, limitations, and correction pathway.
104.11 Duty to Preserve Nonprofit Character. Each director shall preserve the Corporation’s nonprofit character and shall ensure that the Corporation is not operated for private profit, shareholder return, dividend distribution, enterprise capture, or private control.
The duty to preserve nonprofit character shall include responsibility to prevent:
a) private inurement;
b) impermissible private benefit;
c) excess benefit transactions;
d) disguised distributions;
e) unreasonable compensation;
f) unmanaged related-party transactions;
g) use of restricted funds outside their lawful purpose;
h) sponsor or provider purchase of influence;
i) public-good asset enclosure for private advantage;
j) public authority access purchase;
k) certification, recognition, finance-readiness, or procurement outcome purchase; and
l) conversion of public-good assets into private enterprise assets without lawful authority, independent review, and recorded public-benefit justification.
A director shall support financial controls, compensation review, conflict review, independent approval, restricted fund tracking, audit or review processes, and accurate tax and nonprofit records necessary to preserve nonprofit character.
104.12 Duty to Prevent Private Inurement. Each director shall have an affirmative duty to prevent private inurement to directors, officers, members, founders, related parties, donors, sponsors, funders, providers, hosts, contractors, employees, volunteers, fellows, advisors, public authority participants, universities, laboratories, national companies, Project SPVs, enterprise actors, or other private persons.
Private inurement may arise through direct or indirect transfers, excessive compensation, preferential contracts, below-market asset transfers, inflated service arrangements, controlled access to public-good assets, intellectual property capture, exclusive licensing without public-benefit justification, technical baseline capture, dataset enclosure, software enclosure, sponsored findings, publication suppression, provider preference, sponsor control, public authority access sale, or any other arrangement that improperly diverts the Corporation’s resources or mission.
A director who has reason to believe that private inurement may exist shall cause the matter to be disclosed, reviewed, documented, corrected, restricted, unwound, reported, or escalated as required by law, this Bylaw, tax rules, conflict policy, or Board process.
104.13 Duty to Prevent Impermissible Private Benefit. Each director shall have an affirmative duty to prevent impermissible private benefit. Incidental private benefit may occur in lawful public-benefit programs, but any private benefit shall be no more than incidental, reasonable, necessary, proportionate, recorded, and consistent with the Corporation’s purposes.
Directors shall require review of private benefit risk in connection with:
a) grants, donations, sponsorships, restricted funds, and in-kind support;
b) provider, vendor, contractor, host, and technical partner relationships;
c) public-good software, datasets, dashboards, repositories, technical baselines, and open technology assets;
d) controlled rooms, data rooms, clean rooms, evidence rooms, public authority rooms, and no-download rooms;
e) public authority learning sessions;
f) benchmark, index, challenge, lab, Academy, fellowship, or training programs;
g) public-safe reports, maps, dashboards, and publications;
h) Nexus Docket, Grid, GRF-facing, and GRA-facing technical inputs;
i) use of the Corporation’s name, marks, proof receipts, public authority references, or Nexus-compatible claims; and
j) contracts or arrangements involving related parties or financially interested persons.
Where private benefit risk cannot be cured through limitation, independent review, narrowing, pricing, safeguards, non-exclusivity, open licensing, public-safe notice, or other controls, the Board shall refuse, withdraw, terminate, or restructure the activity.
104.14 Duty to Preserve Tax-Exempt or Tax-Exempt-Compatible Status. Each director shall preserve the Corporation’s tax-exempt or tax-exempt-compatible status as applicable and as recorded. The Board shall ensure that the Corporation does not represent, use, or rely upon a tax classification that has not been obtained, maintained, or recorded.
Directors shall oversee, as applicable:
a) federal tax filings;
b) state tax filings;
c) charitable solicitation registrations;
d) donor acknowledgment practices;
e) grant compliance;
f) restricted fund accounting;
g) unrelated business income review;
h) lobbying and political activity limits;
i) private foundation or public charity classification issues where applicable;
j) fiscal sponsorship or sponsored project issues where applicable;
k) compensation reasonableness;
l) excess benefit transaction controls;
m) dissolution asset restrictions;
n) public support records; and
o) tax status change controls.
A director shall not knowingly approve an activity that materially threatens tax status without appropriate review, recorded mitigation, and Board approval where required.
104.15 Duty to Preserve Non-Execution. Each director shall preserve the Corporation’s non-execution perimeter. The Corporation’s role shall remain evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, public authority learning, and public-safe technical stewardship unless a lawful and recorded change is made by competent authority and is consistent with the Articles or Certificate and this Bylaw.
Directors shall ensure that the Corporation does not conduct or hold itself out as conducting:
a) securities offerings, solicitations, brokerage, dealer activity, finder activity, underwriting, or capital placement;
b) investment advice, asset management, portfolio management, suitability determinations, or transaction recommendations;
c) banking, deposit-taking, payment intermediation, clearing, settlement, escrow, custody, or third-party fund control;
d) lending, credit origination, credit approval, credit brokerage, guarantees, or revenue guarantees;
e) insurance placement, underwriting, pricing, binding, claims handling, approval, or risk-bearing intermediation;
f) ratings, credit opinions, bankability opinions, insurability opinions, financeability determinations, or resilience ratings;
g) public finance approval, grant approval, budget allocation, appropriation, tax credit approval, public guarantee, MDB / DFI approval, or sovereign finance approval;
h) procurement award, vendor selection, procurement approval, or procurement preference;
i) certification, accreditation, legal compliance approval, conformance approval, or regulatory safe harbor;
j) recognition, standing, maturity determination, public-facing legitimacy determination, or Grid / Docket approval; or
k) emergency command, official public warning, evacuation instruction, dispatch, incident management, public health order, safety command, regulation, enforcement, permit issuance, or public authority decision.
A director shall cause suspected execution drift to be held, quarantined, reviewed, re-scoped, externalized, referred, corrected, or terminated.
104.16 Duty to Preserve Nexus Role Separation. Each director shall preserve the separation of functions among GCRI US, 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, global, regional, national, state, territorial, Tribal, metropolitan, local, and sectoral consortiums, national companies, Project SPVs, providers, sponsors, hosts, public authorities, universities, laboratories, and enterprise actors.
Directors shall ensure that:
a) GCRI US does not assume GRF’s recognition, registry, maturity-records, standing, claims-discipline, stakeholder-formation, public-safe reporting, or public-facing legitimacy function;
b) GCRI US does not assume GRA’s finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, capital-reader-room, or regulated-perimeter discipline function;
c) GCRI US does not assume Nexus Standards or protocol authority functions unless separately and lawfully designated;
d) GCRI US does not assume public authority functions;
e) GCRI US does not assume enterprise execution functions;
f) evidence inputs are not converted into recognition determinations;
g) technical inputs are not converted into finance-readiness determinations;
h) public-good software and technical baselines are not converted into procurement mandates or certification outcomes; and
i) Nexus-compatible language is used only with authority, limitation, and record.
Directors shall require role-separation records, compatibility notes, divergence logs, controlled vocabulary, public-safe notices, and correction pathways where confusion may arise.
104.17 Duty to Preserve United States Legal Separateness. Each director shall preserve the Corporation’s United States legal separateness. GCRI US shall remain a separate legal person governed by its own Articles or Certificate, this Bylaw, Board, officers, records, funds, obligations, contracts, tax records, policies, and fiduciary duties.
Directors shall not permit shared mission, shared doctrine, shared ontology, shared methods, shared technical baselines, shared records, shared personnel, shared events, shared systems, shared public materials, shared websites, shared repositories, shared councils, shared controlled rooms, shared public authority interfaces, shared funders, shared sponsors, or shared Nexus interfaces to create or imply legal merger, alter ego status, branch status, agency, partnership, joint venture, common treasury, single employer status, joint employer status, mutual authority, or shared liability without express lawful instrument and Board approval where required.
The Board shall require clear public descriptions, contract clauses, repository notices, governance records, public-safe statements, and correction mechanisms to preserve separateness.
104.18 Duty to Preserve Separateness From GCRI Canada, GRF, GRA, Nexus Entities, National Companies, Project SPVs, Providers, Sponsors, Hosts, and Public Authorities. Each director shall ensure that the Corporation’s legal, financial, operational, governance, records, technical, and public-facing separateness is preserved from GCRI Canada, other GCRI entities, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus entities, national companies, state or regional operating companies, Project SPVs, providers, sponsors, hosts, donors, funders, universities, laboratories, public authorities, and enterprise actors.
Separateness shall be preserved through:
a) distinct corporate records;
b) distinct Board and officer authority;
c) distinct bank accounts and financial controls;
d) distinct contracting authority;
e) distinct tax and filing records;
f) distinct employment or contractor arrangements where applicable;
g) distinct public authority capacity records;
h) distinct role descriptions;
i) distinct intellectual property, data, software, and repository authority records;
j) distinct grant, donation, sponsorship, and restricted fund records;
k) distinct risk, incident, and correction records; and
l) public-safe limitation language.
Coordination shall not be confused with merger. Alignment shall not be confused with control. Interoperability shall not be confused with shared authority. Public-good partnership shall not be confused with shared liability.
104.19 Duty to Preserve Evidence Integrity. Each director shall preserve evidence integrity. Evidence integrity means that evidence-related outputs, records, methods, classifications, confidence statements, uncertainty statements, source-lineage statements, provenance records, proof receipts, public-safe reports, dashboards, maps, and technical inputs shall be produced, reviewed, versioned, limited, corrected, and communicated in a manner that is accurate, supportable, transparent to the degree appropriate, public-safe, and bounded by authority.
Directors shall ensure that evidence integrity is protected from:
a) sponsor influence;
b) provider influence;
c) donor or funder pressure;
d) public authority pressure;
e) political pressure;
f) research misconduct;
g) data misuse;
h) AI hallucination or automated-output inflation;
i) selective publication;
j) suppressed uncertainty;
k) overstated confidence;
l) unsupported validation claims;
m) misleading visualizations;
n) public authority overclaim;
o) finance-readiness overclaim;
p) certification or procurement overclaim;
q) recognition overclaim;
r) protected knowledge misuse; and
s) failure to correct.
Evidence shall remain evidence. It shall not be transformed by Board silence, public repetition, technical packaging, public authority participation, sponsor use, provider use, or Nexus reference into final authority, public warning, recognition, finance-readiness, certification, procurement approval, rating, or emergency command.
104.20 Duty to Preserve Research Integrity. Each director shall preserve research integrity across the Corporation’s research, education, Academy, fellowship, laboratory, challenge, evaluation, benchmark, methods, public-good software, technical baseline, and publication activities.
Research integrity shall require, as applicable:
a) truthful design, conduct, recording, analysis, and reporting;
b) appropriate research ethics review;
c) human-subjects review where required;
d) community review where appropriate;
e) Tribal, Indigenous, local, territorial, health-sensitive, youth, vulnerable population, civil rights, accessibility, and protected knowledge review where applicable;
f) sponsor and funder disclosure;
g) conflict disclosure;
h) peer review or technical review where appropriate;
i) reproducibility and replication discipline where appropriate;
j) AI-use disclosure where material;
k) data rights and privacy compliance;
l) publication integrity;
m) correction, supersession, withdrawal, retraction, takedown, and archive pathways; and
n) protection against retaliation and research suppression.
Directors shall not permit research to be used as a disguised commercial endorsement, provider preference, public authority approval, finance-readiness input overclaim, certification substitute, procurement tool, recognition purchase, or protected knowledge extraction mechanism.
104.21 Duty to Preserve Data / AI / Cyber / Privacy Integrity. Each director shall preserve data, AI, cyber, and privacy integrity. The Board shall ensure that the Corporation’s data, AI, compute, cybersecurity, repository, controlled-room, software, dashboard, sensor, digital twin, DePIN, DLT, blockchain, AI-RAN, O-RAN, and public authority data activities are governed by lawful authority, appropriate controls, access classification, security classification, privacy review, AI governance, cyber safeguards, logging, retention, deletion, incident response, and correction pathways.
The duty shall require directors to oversee, as applicable:
a) data minimization;
b) lawful basis and consent where required;
c) data-use limitation;
d) public authority data controls;
e) health-sensitive, cyber-sensitive, infrastructure-sensitive, commercially sensitive, finance-sensitive, community-protected, Tribal / Indigenous, local, territorial, cultural, environmental, and protected knowledge controls;
f) model registers;
g) inference records;
h) compute workload records;
i) dataset cards, model cards, system cards, benchmark cards, and evaluation records;
j) secure development lifecycle;
k) SBOM, dependency, signing, provenance, vulnerability, key, token, and credential controls;
l) identity and access management;
m) incident response;
n) disaster recovery and business continuity; and
o) restrictions on uploading controlled materials to unapproved AI systems.
Directors shall ensure that no AI, model, dashboard, digital twin, proof receipt, ledger entry, DePIN signal, AI-RAN signal, sensor output, cyber telemetry, or automated score is treated as institutional authority without competent human review, record support, limitation, and correction pathway.
104.22 Duty to Preserve Public Authority Boundary Discipline. Each director shall preserve public authority boundary discipline. The Corporation may support public authority learning, evidence literacy, technical literacy, scenario learning, simulation, tabletop exercises, after-action learning, capacity classification, public-safe reporting support, and public authority interface records, but shall not become or substitute for a public authority.
Directors shall prevent the Corporation from:
a) issuing official public warnings;
b) commanding emergency response;
c) issuing evacuation or dispatch instructions;
d) making public health orders;
e) making regulatory decisions;
f) issuing permits;
g) approving legal compliance;
h) enforcing law;
i) approving public procurement;
j) approving public finance;
k) allocating public budgets;
l) creating sovereign obligations;
m) representing public-private partnership status without lawful authority;
n) speaking on behalf of a public authority without written authorization; or
o) converting public authority participation into official adoption.
The Board shall require capacity classification, public authority reference review, limitation language, meeting records, public-safe notices, and correction pathways for material public authority interfaces.
104.23 Duty to Preserve Finance and Regulated-Activity Boundary Discipline. Each director shall preserve finance and regulated-activity boundary discipline. The Corporation shall not be used to conduct securities, investment advisory, brokerage, dealer, finder, underwriting, lending, banking, insurance, rating, public finance, procurement, certification, or other regulated execution activity outside lawful authority.
Directors shall require heightened review for any activity involving:
a) capital readers;
b) investors;
c) insurers;
d) lenders;
e) underwriters;
f) banks;
g) public finance actors;
h) grant-making public authorities;
i) procurement authorities;
j) ratings, scores, rankings, or maturity claims;
k) finance-readiness, insurance-readiness, bankability, investability, capital-readability, or proof-pack language;
l) Docket, Grid, Nexus-compatible, recognition, certification, accreditation, compliance, or conformance claims;
m) sponsor, provider, host, or enterprise actor materials that may be used in financing, procurement, insurance, grant, or public authority settings; and
n) public-safe reports or technical baselines with potential reliance by third parties.
Directors shall ensure that GRA-facing technical inputs remain technical inputs and do not become finance-readiness determinations by GCRI US. Directors shall ensure that GRF-facing evidence inputs remain evidence inputs and do not become recognition or public-facing legitimacy determinations by GCRI US.
104.24 Duty to Preserve Community Safeguards and Protected Knowledge. Each director shall preserve community safeguards and protected knowledge. The Corporation shall not pursue technical, evidence, public authority, public-safe publication, sponsor, provider, or Nexus objectives in a manner that disregards civil rights, accessibility, Indigenous governance respect, Tribal protocols, local and territorial knowledge, community safeguards, protected knowledge, vulnerable persons, or public safety.
Directors shall require safeguards review where activities involve:
a) Tribal or Indigenous knowledge;
b) Indigenous data;
c) local or territorial knowledge;
d) cultural, environmental, sacred, sensitive, or community-protected information;
e) health-sensitive or youth-related data;
f) vulnerable or remote communities;
g) disaster-exposed or climate-exposed communities;
h) infrastructure-sensitive locations;
i) public-safe mapping;
j) surveillance or re-identification risk;
k) AI training or model improvement using protected materials;
l) publication of maps, dashboards, datasets, or digital twins;
m) sponsor or provider access to community information;
n) grievance, remedy, protected participation, or non-retaliation issues; and
o) public authority or media use of community information.
The Board shall ensure that protected knowledge is not extracted, exposed, commercialized, tokenized, mapped, trained on, transferred, or repurposed without lawful authority, recorded safeguards, and appropriate respect for consent, non-consent, attribution, restriction, withdrawal, correction, and remedy pathways.
104.25 Duty to Disclose Conflicts. Each director shall disclose actual, potential, and perceived conflicts of interest in accordance with law, this Bylaw, the conflict policy, Board procedures, and any applicable committee or controlled-room rules.
Conflict disclosure shall include, as applicable:
a) financial interests;
b) employment, consulting, advisory, board, officer, fiduciary, or ownership roles;
c) sponsor, donor, funder, provider, host, contractor, vendor, investor, insurer, lender, underwriter, bank, public finance actor, public authority, national company, Project SPV, university, laboratory, or enterprise relationships;
d) family, household, close personal, professional, or institutional relationships;
e) research conflicts;
f) publication conflicts;
g) data, AI, cyber, repository, software, technical asset, or intellectual property conflicts;
h) public authority conflicts;
i) political, lobbying, campaign, or government ethics conflicts where applicable;
j) conflicts relating to Tribal, Indigenous, community, protected knowledge, civil rights, accessibility, or safeguards matters;
k) dual roles with GCRI Canada, GRF, GRA, Nexus entities, consortiums, national companies, Project SPVs, providers, sponsors, or hosts; and
l) any circumstance that may reasonably affect independent judgment or public trust.
Disclosure shall be timely, complete, updated when circumstances change, and recorded. Failure to disclose may constitute a breach of fiduciary duty and may support corrective action, recusal, access restriction, committee restriction, non-renewal, removal, or other remedy where lawful.
104.26 Duty to Recuse Where Required. Each director shall recuse from deliberation, recommendation, access, voting, approval, oversight, or implementation where required by law, this Bylaw, Board policy, conflict policy, committee charter, controlled-room rule, counsel determination, independent review, or Board decision.
Recusal may require:
a) abstention from voting;
b) exclusion from deliberation;
c) exclusion from confidential materials;
d) exclusion from controlled-room or data-room access;
e) exclusion from committee participation;
f) restriction from officer or staff instruction;
g) restriction from external communication;
h) restriction from public authority interaction;
i) restriction from sponsor, provider, donor, funder, host, national company, Project SPV, or enterprise interface;
j) restriction from publication approval;
k) restriction from technical release approval;
l) restriction from correction decision-making; or
m) other mitigation appropriate to the conflict.
A recused director shall not attempt to influence the matter indirectly through informal communications, staff pressure, sponsor or provider channels, public authority relationships, technical contributors, public statements, social pressure, funding leverage, or Nexus-interface channels.
104.27 Duty to Support Correction and Supersession. Each director shall support correctionability and supersession discipline. Where a director becomes aware of a material error, incomplete record, unsupported claim, misleading publication, defective method, unreliable evidence, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider preference claim, sponsor control issue, data misuse, AI misuse, cyber issue, privacy issue, protected knowledge concern, safeguards issue, conflict, authority defect, or governance defect, the director shall cause the matter to be escalated through appropriate channels.
The duty to support correction shall include, as applicable:
a) preserving evidence;
b) avoiding concealment;
c) notifying the Chair, Secretary, relevant officer, committee, counsel, compliance function, safeguards function, or Board;
d) supporting hold, quarantine, restriction, or publication freeze where needed;
e) supporting review and root-cause analysis;
f) supporting correction, clarification, limitation, supersession, withdrawal, retraction, takedown, archive, or public-safe notice where appropriate;
g) supporting affected-person, public authority, funder, sponsor, provider, or community notice where required and lawful;
h) supporting recurrence prevention; and
i) ensuring that corrections are recorded and linked to affected records.
No director shall suppress, delay, weaken, or conceal a correction to protect reputation, funding, sponsor relationship, provider relationship, public authority relationship, personal interest, or institutional convenience.
104.28 Fiduciary Duty Records. The Corporation shall maintain Fiduciary Duty Records sufficient to demonstrate that directors have been appointed, informed, trained, disclosed, recused, deliberated, decided, monitored, corrected, and held accountable in accordance with law, the Articles or Certificate, this Bylaw, Board policies, and fiduciary standards.
Fiduciary Duty Records shall include, as applicable:
a) director consent records, appointment records, election records, qualification records, independence records, fit-and-proper records, training records, certification-of-understanding records, and director register entries;
b) Board meeting notices, agendas, materials, minutes, attendance records, quorum records, vote records, abstention records, recusal records, dissent records where recorded, executive session records, controlled-session records, and written consent records;
c) conflict disclosures, related-party disclosures, independence reviews, dual-role reviews, recusal determinations, access restrictions, conflict mitigation records, and conflict violation records;
d) records of legal review, tax review, nonprofit review, public authority boundary review, finance-boundary review, certification-boundary review, procurement-neutrality review, recognition-boundary review, provider-neutrality review, sponsor non-control review, safeguards review, data / AI / cyber review, privacy review, research integrity review, competition review, sanctions review, export-control review, and controlled-technology review;
e) mission-lock records, public-benefit purpose records, nonprofit character records, non-distribution records, private inurement review records, private benefit review records, tax-exempt or tax-exempt-compatible records, all-states-and-territories records, North America anchor records, GCRI Canada interface records, GRF interface records, GRA interface records, Nexus interface records, compatibility notes, divergence logs, and equivalence notes;
f) evidence integrity records, research integrity records, methods records, observability records, ontology records, technical truth records, public-good R&D records, public-good software records, open technical baseline records, verifiable compute records, verifiable intelligence records, proof receipt records, public-safe publication records, correction records, supersession records, withdrawal records, retraction records, takedown records, and archive records;
g) data governance records, privacy records, AI governance records, cybersecurity records, secure compute records, model register records, inference record records, compute workload records, repository records, software release records, SBOM records, vulnerability records, key and credential records, incident records, disaster recovery records, and business continuity records;
h) community safeguard records, Tribal and Indigenous protocol records, Indigenous data safeguard records, protected knowledge records, local and territorial knowledge records, civil rights records, accessibility records, public-safe mapping records, grievance records, remedy records, protected participation records, non-retaliation records, and stop-the-line records;
i) records of fiduciary concern, director inquiry, Board follow-up, corrective action, legal hold, investigation, escalation, restriction, removal, ratification, clarification, public-safe notice, and recurrence prevention; and
j) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that a director’s fiduciary duties are not merely formal corporate duties; they are the legal and institutional discipline by which the Corporation preserves public trust, public-benefit purpose, lawful nonprofit status, evidence integrity, technical truth, public-safe operation, data / AI / cyber integrity, community safeguards, Nexus role separation, non-execution, validity-by-record, and correctionability. Each director shall serve with care, loyalty, obedience, good faith, prudence, diligence, independence, candor, and correctional responsibility, and every material exercise of fiduciary judgment shall be lawful, recorded, bounded, reviewable, public-safe where relevant, and correctionable.
Section 105. Board Composition, Number, Structure, Independence, and Skills Mix
105.1 Board Composition Purpose. The Board shall be composed, structured, maintained, reviewed, renewed, and, where necessary, rebalanced to provide competent fiduciary governance for the Corporation as a United States nonprofit, non-distributing, public-benefit, non-executing technical institution and United States / North America anchor for evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, verifiable compute and intelligence methods, public authority learning, community safeguards, and Nexus-compatible public-good stewardship.
Board composition shall be designed to support informed judgment, fiduciary independence, legal compliance, public-benefit purpose, tax-exempt or tax-exempt-compatible discipline, all-states-and-territories awareness, North America interface awareness, public authority boundary discipline, finance and regulated-activity boundary discipline, data / AI / cyber integrity, research integrity, community safeguards, provider neutrality, sponsor non-control, validity-by-record, correctionability, and durable institutional trust.
The Board shall not be composed for ceremonial prestige, fundraising optics, sponsor satisfaction, provider influence, public authority signaling, political positioning, technical popularity, founder control, affiliate control, ecosystem control, capital-reader influence, or enterprise execution advantage. Board composition shall be mission-governance composition, not marketing composition.
The Board shall maintain a composition sufficient to exercise real oversight over:
a) corporate governance, fiduciary duties, nonprofit compliance, tax posture, corporate records, conflicts, compensation, and internal controls;
b) evidence doctrine, methods stewardship, observability, ontology, technical truth, public-safe publication, public-good R&D, public-good software, open technical baselines, and correction systems;
c) data governance, privacy, AI governance, cybersecurity, secure compute, verifiable compute, verifiable intelligence, model registers, inference records, compute workload records, repositories, software release, SBOM, vulnerability, incident response, and business continuity;
d) public authority learning, public authority capacity classification, regulator-listening participation, public finance reader participation, emergency-management learning participation, public infrastructure operator participation, and public authority boundary records;
e) community safeguards, Tribal and Indigenous protocol respect, Indigenous data safeguards, local and territorial knowledge, protected knowledge, civil rights, accessibility, public-safe mapping, grievance, remedy, protected participation, and non-retaliation;
f) finance, securities, investment adviser, broker-dealer, finder, banking, lending, insurance, underwriting, rating, public finance, procurement, certification, accreditation, recognition, provider-neutrality, sponsor non-control, anti-capture, and regulated-perimeter discipline; and
g) GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, providers, sponsors, hosts, public authorities, universities, laboratories, communities, and enterprise-stack interfaces.
105.2 Minimum Number of Directors. The Board shall have not fewer than the minimum number of directors required by applicable law, the Articles or Certificate, or this Bylaw. If applicable law permits a lower number, the Corporation shall nevertheless maintain a Board size sufficient to support independent fiduciary judgment, lawful quorum, committee formation where needed, conflict recusal capacity, emergency continuity, and oversight of the Corporation’s technical, legal, public-benefit, safeguards, data / AI / cyber, public authority, and Nexus-interface obligations.
The minimum number of directors shall not be set or maintained at a level that creates material risk of:
a) founder control;
b) sponsor control;
c) provider control;
d) donor or funder control;
e) public authority confusion;
f) related-party dominance;
g) inability to form independent review;
h) inability to maintain quorum after recusals;
i) inability to supervise officers;
j) inability to review major transactions;
k) inability to oversee data / AI / cyber, safeguards, public authority, finance-boundary, certification-boundary, procurement-neutrality, recognition-boundary, or Nexus role-separation matters; or
l) inability to preserve continuity during vacancies, emergencies, resignations, removals, conflicts, or access restrictions.
If the number of directors falls below the required minimum, the remaining directors shall act only to the extent permitted by law and this Bylaw to restore lawful governance, fill vacancies, preserve records, maintain essential legal and fiduciary functions, protect assets, prevent harm, and avoid prohibited functions.
105.3 Maximum Number of Directors. The Board may have a maximum number of directors as fixed by the Articles or Certificate, this Bylaw, or Board resolution where lawful. The maximum number shall be set to preserve effective governance, deliberative quality, confidentiality, fiduciary accountability, quorum discipline, conflict management, Board security, and efficient decision-making.
The Board shall not be expanded merely to accommodate sponsors, donors, funders, providers, hosts, public authorities, investors, insurers, lenders, public finance actors, national companies, Project SPVs, universities, laboratories, media figures, political actors, technical vendors, institutional affiliates, or prestige appointments unless each director is independently eligible, mission-aligned, conflict-reviewed, and capable of discharging fiduciary duties to the Corporation.
A large Board shall not be used to dilute accountability, obscure control, create informal factions, mask sponsor or provider influence, create public authority signaling, manufacture legitimacy, avoid difficult fiduciary decisions, or convert advisory participation into governance. Where stakeholder breadth is useful but fiduciary governance would be impaired by Board enlargement, the Corporation may use advisory councils, Helix Councils, public authority forums, scientific panels, working groups, expert panels, or competence cells with clearly bounded non-governance authority.
105.4 Number Fixed by Articles, Bylaw, Board Resolution, or Member Action Where Required. The number of directors shall be fixed in accordance with applicable law, the Articles or Certificate, this Bylaw, Board resolution, member action where required, or other competent governance record. No website statement, public deck, grant proposal, sponsor agreement, donor letter, public authority memorandum, committee charter, advisory council listing, working group roster, Nexus interface record, repository file, AI summary, public announcement, or informal practice shall change the authorized number of directors.
Any action fixing, increasing, reducing, or otherwise modifying the number of directors shall be recorded in the Board Authority Records and shall identify, as applicable:
a) the legal authority for the change;
b) the prior number or range of directors;
c) the new number or range of directors;
d) the effective date;
e) whether member approval is required;
f) whether amendment of the Articles or Certificate or this Bylaw is required;
g) the governance reason for the change;
h) the effect on quorum;
i) the effect on committees;
j) the effect on independence and conflicts;
k) the effect on skills coverage;
l) the effect on continuity and vacancies; and
m) any transition, savings, or implementation rule.
A reduction in the number of directors shall not shorten the term of any incumbent director unless permitted by law and properly recorded. A change in Board size shall not be used to remove a director indirectly, alter voting outcomes improperly, avoid recusals, defeat member rights, concentrate control, or impair independent oversight.
105.5 Independent Director Standard. The Board shall maintain a meaningful independent director standard appropriate to the Corporation’s public-benefit, nonprofit, technical, safeguards, public authority, and Nexus-interface functions. A director shall be considered independent only if the director is capable of exercising objective fiduciary judgment for the Corporation without material compromise by financial interest, employment interest, consulting interest, donor interest, sponsor interest, provider interest, host interest, public authority interest, political interest, investor interest, insurer interest, lender interest, national company interest, Project SPV interest, affiliate interest, family interest, or other relationship that could reasonably impair independence.
Independence shall be assessed with respect to:
a) compensation from the Corporation or related entities;
b) contracts, grants, sponsorships, donations, restricted funds, in-kind support, or other financial arrangements;
c) employment, consulting, advisory, board, officer, fiduciary, or ownership relationships;
d) relationships with GCRI Canada, GRF, GRA, Nexus entities, consortiums, national companies, Project SPVs, providers, sponsors, hosts, public authorities, universities, laboratories, contractors, investors, insurers, lenders, underwriters, banks, public finance actors, and enterprise-stack actors;
e) participation in matters that may generate recognition, finance-readiness, certification, procurement advantage, provider preference, public authority access, technical baseline influence, or public-safe claim value;
f) personal, family, household, professional, or institutional relationships;
g) research conflicts and publication interests;
h) data, AI, cyber, software, repository, intellectual property, model, dataset, or technical asset interests;
i) political, lobbying, campaign, government ethics, or public authority relationships where relevant; and
j) any other circumstance that could reasonably create actual, potential, or perceived capture.
The Board may adopt independence categories, including independent, non-independent, conflicted for specific matters, conditionally independent subject to mitigation, or not eligible for Board service. Independence shall be reviewed at appointment, annually, and upon material change in circumstances.
105.6 Public-Benefit Governance Competence. The Board shall include directors who collectively possess competence in public-benefit governance. Public-benefit governance competence means the ability to govern an institution whose legitimacy depends on public-good purpose, mission fidelity, fiduciary independence, anti-capture discipline, community safeguards, public trust, transparent records where appropriate, correctionability, and lawful restraint.
The Board shall ensure that its members collectively understand that public-benefit governance is not equivalent to commercial growth governance, public relations governance, sponsor relationship management, political access management, public authority substitution, or enterprise delivery governance. Public-benefit governance requires attention to:
a) public mission;
b) beneficiaries and affected communities;
c) trust-preserving boundaries;
d) lawful public-interest purpose;
e) conflict discipline;
f) stakeholder participation without stakeholder control;
g) transparency balanced with confidentiality, privacy, cyber, legal, public authority, and protected knowledge limits;
h) harm avoidance;
i) safeguards;
j) public-safe publication; and
k) correction and accountability.
At least a meaningful portion of the Board shall be able to interrogate whether a proposed strategy, transaction, program, publication, technical release, public authority interface, sponsor arrangement, provider relationship, or Nexus alignment is genuinely public-benefit aligned and not merely public-benefit described.
105.7 United States Nonprofit Governance Competence. The Board shall include directors who collectively possess competence in United States nonprofit governance, including the structure, duties, limitations, records, fiduciary obligations, and compliance expectations of a United States nonprofit corporation.
Such competence shall include awareness of:
a) governing state nonprofit corporation law;
b) Articles or Certificate control;
c) bylaws and Board resolutions;
d) director duties;
e) officer authority;
f) committee authority;
g) member rights where applicable;
h) conflict-of-interest discipline;
i) related-party transaction review;
j) compensation review;
k) private inurement and private benefit rules;
l) corporate records;
m) state qualification and good-standing obligations;
n) charitable solicitation obligations where applicable;
o) restricted fund discipline; and
p) dissolution and public-good asset rules.
The Board shall not rely solely on technical excellence, founder vision, public authority relationships, sponsor support, philanthropic reputation, or Nexus ecosystem familiarity as substitutes for nonprofit governance competence.
105.8 Federal Tax and State Nonprofit Law Competence. The Board shall include, retain access to, or obtain competent advice concerning federal tax and state nonprofit law matters relevant to the Corporation’s status, operations, support arrangements, revenue, compensation, transactions, publications, and public representations.
The Board’s collective competence or advisory access shall cover, as applicable:
a) federal tax-exempt or tax-exempt-compatible status;
b) charitable or non-charitable nonprofit classification;
c) Section 501(c)(3), 501(c)(4), 501(c)(6), fiscal sponsorship, supporting organization, sponsored project, or other classification issues where relevant;
d) private inurement;
e) impermissible private benefit;
f) excess benefit transactions;
g) unrelated business income;
h) donor acknowledgments;
i) sponsorship and advertising distinctions where relevant;
j) restricted funds;
k) public support tests where relevant;
l) lobbying and political activity limits where relevant;
m) state tax and registration obligations;
n) charitable solicitation registration where relevant; and
o) state nonprofit corporate reporting and good standing.
The Board may rely on counsel, accountants, tax advisors, auditors, or qualified nonprofit specialists where appropriate, but ultimate oversight shall remain with the Board.
105.9 All-States-and-Territories Governance Awareness. The Board shall include directors who collectively understand the Corporation’s United States all-states-and-territories posture and the governance risks of operating, convening, publishing, fundraising, employing, contracting, hosting, receiving data, maintaining controlled rooms, or engaging public authorities across multiple United States jurisdictions.
All-states-and-territories governance awareness shall include attention to:
a) state qualification and registration;
b) charitable solicitation registration;
c) state tax and franchise obligations;
d) employment and contractor obligations;
e) privacy and data law variation;
f) cybersecurity and breach notification obligations;
g) public records, open meetings, public procurement, government ethics, lobbying, and grant compliance considerations where applicable;
h) civil rights and accessibility obligations;
i) public authority capacity classification;
j) public-safe communication across jurisdictions;
k) state, territorial, District of Columbia, Tribal, local, municipal, county, metropolitan, port, utility, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, and infrastructure interfaces; and
l) localization without fragmentation of the Corporation’s mission lock and non-execution perimeter.
The Board shall not treat national reach, public-benefit purpose, or Nexus alignment as a substitute for state-by-state and territory-by-territory compliance review where required.
105.10 North America Cross-Border Awareness. The Board shall include directors who collectively understand the Corporation’s North America anchor role and the legal, institutional, technical, data, AI, cyber, public authority, protected knowledge, and public-safe communication boundaries that apply to cross-border coordination.
North America cross-border awareness shall include attention to:
a) coordination with GCRI Canada without merger;
b) Mexico, Caribbean, Arctic, Great Lakes, Pacific, Atlantic, Gulf, border, Indigenous, regional, and cross-border interfaces where lawfully structured;
c) cross-border evidence architecture;
d) cross-border observability and ontology alignment;
e) public authority learning without public authority delegation;
f) data transfer, privacy, cybersecurity, sovereign data, health-sensitive data, infrastructure-sensitive data, and protected knowledge issues;
g) export controls, sanctions, controlled technology, national security sensitivity, and dual-use concerns;
h) cross-border public-safe reporting;
i) climate, disaster, cyber, public health, energy, water, food, biodiversity, telecom, supply chain, port, border, Arctic, Great Lakes, Atlantic, Pacific, Gulf, and critical infrastructure contexts; and
j) legal separateness among GCRI US, GCRI Canada, GRF, GRA, Nexus entities, public authorities, providers, sponsors, hosts, and enterprise actors.
The Board shall ensure that North America anchor composition does not create actual or perceived North America sovereign authority, treaty authority, public finance authority, regional regulator status, certification authority, recognition authority, finance-readiness authority, or enterprise execution authority.
105.11 Evidence and Methods Competence. The Board shall include directors who collectively possess, or can competently supervise through committees and advisors, evidence and methods competence sufficient to oversee the Corporation’s core public-good technical functions.
Evidence and methods competence shall include awareness of:
a) evidence doctrine;
b) source lineage;
c) provenance;
d) chain of custody;
e) confidence and uncertainty;
f) validation and verification;
g) corroboration;
h) contradiction handling;
i) disputed evidence handling;
j) failed-signal handling;
k) spoof indicators;
l) sensor fusion;
m) geospatial evidence;
n) cyber evidence;
o) AI output review;
p) digital twin assumption review;
q) DLT, blockchain, DePIN, AI-RAN, O-RAN, and telemetry interpretation methods;
r) public-safe publication; and
s) correction, supersession, withdrawal, retraction, takedown, and archival.
The Board shall not be required to consist entirely of technical experts, but it shall be capable of asking informed questions and recognizing when technical review, peer review, red-team review, safeguards review, counsel review, or independent validation is required.
105.12 Research Integrity Competence. The Board shall include directors who collectively possess research integrity competence or access to qualified research integrity advice. Research integrity competence shall include understanding of research design, ethics, reproducibility, peer review, publication integrity, conflict disclosure, sponsor independence, data rights, human-subjects review where required, community review, Tribal and Indigenous protocol review, health-sensitive data review, youth and vulnerable population review, protected knowledge safeguards, and correction of research outputs.
The Board shall ensure that research integrity is preserved in connection with:
a) public-benefit R&D;
b) applied research;
c) technical prototyping;
d) public-good software;
e) open technical baselines;
f) benchmarks;
g) test harnesses;
h) evaluation sets;
i) datasets;
j) model evaluation;
k) AI governance methods;
l) cyber methods;
m) observability methods;
n) public authority learning materials;
o) Academy programs;
p) fellowships;
q) labs;
r) challenges; and
s) publications.
Research integrity competence shall include recognition that research outputs shall not be used as disguised endorsement, certification, procurement approval, finance-readiness determination, public authority decision, provider preference, sponsor-controlled finding, or recognition outcome.
105.13 Data Governance, Privacy, AI Governance, Cybersecurity, and Secure Technology Competence. The Board shall include directors who collectively possess, or have reliable access to, competence in data governance, privacy, AI governance, cybersecurity, secure technology, secure compute, and digital infrastructure risk.
This competence shall include awareness of:
a) data classification;
b) lawful basis and consent where required;
c) data minimization;
d) access control;
e) rights-bearing data;
f) public authority data;
g) health-sensitive data;
h) cyber-sensitive and infrastructure-sensitive data;
i) commercially sensitive and finance-sensitive data;
j) community-protected, Tribal / Indigenous, local, territorial, cultural, environmental, and protected knowledge data;
k) cross-border transfer and sovereign data zones;
l) AI-use governance;
m) model registers;
n) dataset cards, model cards, system cards, benchmark cards, and evaluation harnesses;
o) inference records;
p) compute workload records;
q) agentic AI controls;
r) secure development lifecycle;
s) repository security;
t) SBOM, signing, provenance, dependency, vulnerability, key, token, credential, and secret controls;
u) incident response;
v) backup, disaster recovery, and business continuity; and
w) restrictions on use of unapproved AI systems for controlled materials.
The Board shall maintain sufficient competence to understand that automated outputs, models, dashboards, digital twins, proof receipts, DePIN records, ledger entries, AI-RAN signals, O-RAN signals, sensor outputs, and cyber telemetry are not authority without human review, record support, limitation, and correction pathway.
105.14 Public-Good Software, Open Technical Baselines, and Technical Asset Stewardship Competence. The Board shall include directors who collectively understand, or have access to expertise concerning, public-good software, open technology, open technical baselines, technical asset stewardship, software governance, licensing, repository integrity, and anti-enclosure controls.
This competence shall include awareness of:
a) public-good software strategy;
b) open and restricted licensing;
c) contributor governance;
d) contributor license agreements or assignment instruments;
e) intellectual property chain of title;
f) moral rights where applicable;
g) patent, defensive publication, royalty, and standards-essential sensitivity;
h) repository governance;
i) secure development;
j) secure release;
k) SBOM and software supply chain risk;
l) artifact signing and provenance;
m) dependency and vulnerability management;
n) rollback and deprecation;
o) fork governance;
p) compatibility claims;
q) Nexus-compatible claim boundaries;
r) public-good technical baseline stewardship; and
s) commercial use boundaries.
The Board shall ensure that public-good software and technical baselines are not converted by use, adoption, deployment, fork, provider participation, public authority familiarity, sponsor support, or technical centrality into certification, procurement approval, provider preference, public authority decision, finance-readiness determination, or operational control.
105.15 Observatory, AI-RAN, O-RAN, DePIN, DLT, Cyber-Physical Systems, Digital Twin, Geospatial, Edge Compute, Sovereign Compute, and Mission-Critical Technology Competence. The Board shall include directors who collectively possess or can access competence in observability and mission-critical technology domains relevant to the Corporation’s work. The Board’s skills mix shall be sufficient to govern public-good evidence and methods work across all exponential and mission-critical technologies, not only AI-RAN.
Relevant technology competence may include, without limitation:
a) Nexus Observatory methods;
b) observability nodes, hubs, clusters, hotspots, regional clusters, and national dense Nexus cores;
c) AI, agentic AI, AI governance, model evaluation, and verifiable intelligence;
d) AI-RAN, O-RAN, private wireless, telecom, edge networks, and resilient communications;
e) DePIN, DLT, blockchain, Web3, ledgers, proof receipts, role keys, smart licenses, and tokenized infrastructure risks;
f) sovereign compute, confidential computing, secure enclaves, HPC, compute-to-data, and secure workload governance;
g) cybersecurity, cyber-physical systems, operational technology, ICS, critical infrastructure, ports, utilities, energy, water, food, health, public safety, and disaster systems;
h) robotics, drones, sensors, sensing systems, IoT, remote sensing, Earth observation, geospatial systems, and public-safe mapping;
i) digital twins, simulations, scenario systems, degraded-mode awareness, resilience indicators, and dashboard systems;
j) biosecurity, climate, nature, biodiversity, WEFH systems, advanced manufacturing, semiconductors, quantum-relevant systems, and supply chains; and
k) public-safe technology communication.
The Board shall not substitute technology enthusiasm for fiduciary judgment. Technical competence shall be applied to preserve public-benefit purpose, legal boundaries, human review, safeguards, and correctionability.
105.16 Public Authority, Emergency Management, Public Health, Public Safety, Infrastructure, Utility, State, Territorial, Tribal, and Local Interface Competence. The Board shall include directors who collectively understand public authority interfaces and the boundary between public authority learning and public authority action. This competence shall include awareness of federal, state, territorial, District of Columbia, Tribal, local, county, municipal, metropolitan, port, utility, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, and infrastructure contexts.
Board composition shall enable competent oversight of:
a) public authority capacity classification;
b) official-capacity records;
c) observer status;
d) regulator-listening status;
e) public finance reader status;
f) emergency-management participant status;
g) public infrastructure operator participation;
h) scenario, simulation, tabletop, exercise, and after-action learning;
i) public authority data contributions;
j) public authority reference controls;
k) controlled-room and public authority room protocols;
l) public-safe reporting; and
m) no-delegation, no-public-warning, no-emergency-command, no-procurement-approval, no-funding-approval, no-regulatory-approval, no-public-finance-approval, no-sovereign-obligation, and no-official-adoption controls.
The Board shall not be composed in a manner that causes public authorities to appear to control the Corporation, or that causes the Corporation to appear to exercise public authority.
105.17 Community Safeguards, Tribal and Indigenous Knowledge, Civil Rights, Accessibility, Public-Safe Mapping, and Protected Participation Competence. The Board shall include directors who collectively possess competence, lived understanding, professional expertise, or advisory access concerning community safeguards, Tribal and Indigenous protocol respect, Indigenous data safeguards, local and territorial knowledge, protected knowledge, civil rights, accessibility, public-safe mapping, grievance, remedy, protected participation, and non-retaliation.
This competence shall include the ability to recognize and govern risks involving:
a) extraction of knowledge;
b) publication of sensitive maps or dashboards;
c) community stigmatization;
d) surveillance or re-identification;
e) misuse of Indigenous, Tribal, local, territorial, cultural, environmental, or protected knowledge;
f) AI training or model improvement using sensitive materials;
g) civil rights impact;
h) accessibility exclusion;
i) vulnerable and remote communities;
j) disaster-exposed, climate-exposed, health-exposed, infrastructure-exposed, or conflict-exposed communities;
k) retaliation against participants;
l) protected participation and confidential reporting;
m) grievance and remedy systems; and
n) do-no-harm review.
The Board shall ensure that safeguards competence is not treated as optional, symbolic, or secondary to technical, sponsor, public authority, or publication objectives.
105.18 Finance-Boundary, Securities-Boundary, Insurance-Boundary, Lending-Boundary, Public Finance, Procurement, and Certification Boundary Competence. The Board shall include directors who collectively possess, or have reliable access to, competence in finance-boundary, securities-boundary, insurance-boundary, lending-boundary, public finance, procurement, certification, accreditation, rating, and regulated-perimeter discipline.
This competence shall include awareness of the boundary between GCRI US technical evidence inputs and prohibited or externally assigned functions, including:
a) securities offerings and solicitation;
b) broker-dealer, finder, and underwriting activities;
c) investment adviser, asset management, portfolio management, and recommendation activities;
d) banking, deposit-taking, custody, clearing, settlement, escrow, and third-party fund control;
e) lending, credit origination, credit approval, guarantees, and credit brokerage;
f) insurance placement, underwriting, pricing, binding, claims handling, approval, and risk-bearing intermediation;
g) ratings, credit opinions, bankability, insurability, financeability, resilience ratings, and investment grade opinions;
h) public finance approvals, tax credit approvals, budget allocations, appropriations, public guarantees, and sovereign finance approvals;
i) procurement awards, vendor selection, procurement approval, and procurement preference;
j) certification, accreditation, conformance approval, legal compliance approval, and regulatory safe harbor;
k) GRF recognition and maturity functions; and
l) GRA finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, and capital-reader-room functions.
The Board shall be capable of recognizing when finance-adjacent or procurement-adjacent language, scores, dashboards, proof receipts, controlled-room materials, public-safe reports, technical baselines, or Nexus-interface outputs require legal, compliance, or GRA-boundary review.
105.19 Competition, Antitrust, Sanctions, Export-Control, Controlled Technology, and National Security Sensitivity Competence. The Board shall include directors who collectively possess, or have reliable access to, competence in competition, antitrust, sanctions, export-control, controlled technology, and national security sensitivity risks relevant to the Corporation’s meetings, councils, working groups, data sharing, benchmarking, technical comparisons, public authority learning, controlled rooms, software releases, technical baselines, cross-border interfaces, and sponsor or provider participation.
This competence shall include awareness of:
a) prohibited market-sensitive discussions;
b) price, margin, cost, bid, wage, customer, supplier, market allocation, capacity, exclusion, boycott, procurement steering, and collusive strategy risks;
c) competitively sensitive information controls;
d) clean-team and clean-room structures;
e) aggregation, de-identification, delay, and independent administration;
f) sanctions screening;
g) export-control classification;
h) controlled technology handling;
i) defense, dual-use, critical infrastructure, cyber, telecom, AI, semiconductor, quantum-relevant, geospatial, satellite, biosecurity, and sovereign compute sensitivities;
j) foreign influence and national security sensitivity where applicable;
k) cross-border data, technology, and personnel controls; and
l) stop-meeting, hold, quarantine, escalation, and correction duties.
The Board shall not permit committee, council, sponsor, provider, public authority, or technical enthusiasm to displace competition-law discipline, sanctions compliance, export-control discipline, or controlled-technology safeguards.
105.20 Diversity of Skills, Disciplines, Geography, States, Territories, Lived Experience, Institutional Perspective, and Public-Interest Viewpoint. The Board shall seek and maintain diversity of skills, disciplines, geography, states, territories, lived experience, institutional perspective, and public-interest viewpoint to strengthen judgment, reduce blind spots, prevent capture, and improve the Corporation’s capacity to serve a public-benefit mission across the United States and North America.
Board diversity may include, without limitation, diversity in:
a) legal, nonprofit, tax, governance, risk, finance-boundary, compliance, technology, research, public authority, safeguards, community, data, AI, cyber, software, infrastructure, climate, health, disaster, public safety, energy, water, food, telecom, geospatial, biosecurity, and systems disciplines;
b) geographic experience across states, territories, District of Columbia, Tribal interfaces, border regions, Arctic, Great Lakes, Pacific, Atlantic, Gulf, metropolitan, rural, remote, island, and cross-border contexts;
c) public authority, academic, community, technical, civil society, philanthropic, public-interest, and professional perspectives;
d) lived experience relevant to community safeguards, accessibility, civil rights, disaster exposure, infrastructure exposure, climate exposure, health exposure, rural and remote conditions, Indigenous and local knowledge respect, and public trust; and
e) institutional perspective sufficient to challenge assumptions, question overclaims, identify harm, and improve public-safe communication.
Diversity shall not be pursued as tokenization, symbolic participation, sponsor signaling, political alignment, market positioning, or public relations advantage. Directors appointed to strengthen viewpoint, geography, discipline, or lived-experience diversity shall hold equal fiduciary duties to the Corporation and shall not be treated as delegates of a constituency unless the Articles or Certificate, this Bylaw, or applicable law expressly provides otherwise.
105.21 No Board Composition That Creates Sponsor, Provider, Donor, Funder, Host, Public Authority, Investor, Insurer, Lender, National Company, Project SPV, or Enterprise Capture. The Board shall not be composed, expanded, reduced, nominated, elected, appointed, renewed, staggered, or structured in a manner that creates actual, potential, or perceived capture by sponsors, providers, donors, funders, hosts, public authorities, investors, insurers, lenders, underwriters, banks, public finance actors, national companies, state operating companies, regional operating companies, Project SPVs, contractors, vendors, universities, laboratories, political actors, founders, affiliates, or enterprise-stack actors.
Capture risk may arise through:
a) common control;
b) coordinated voting;
c) related-party appointments;
d) sponsor-designated seats;
e) provider-designated seats;
f) donor-designated seats;
g) funder-designated seats;
h) public authority-designated seats;
i) investor, insurer, lender, or capital-reader influence;
j) national company or Project SPV affiliation;
k) shared employment;
l) shared funding dependency;
m) shared counsel or advisor channels;
n) shared data or technical dependency;
o) public authority access dependency;
p) sponsor or provider concentration;
q) founder dominance;
r) family, household, close personal, or professional concentration;
s) committee capture;
t) financial dependency; or
u) informal leadership control.
Where capture risk is identified, the Board shall require mitigation, including one or more of the following:
a) refusal or deferral of appointment;
b) independent director addition;
c) recusal;
d) access restriction;
e) voting restriction where lawful;
f) committee restriction;
g) chair or officer restriction;
h) influence cap;
i) diversification of support;
j) ring-fencing of sponsor or provider relationships;
k) independent review;
l) public-safe clarification;
m) conflict mitigation plan;
n) non-renewal;
o) removal where permitted; or
p) other corrective action.
No sponsor, donor, funder, provider, host, public authority, investor, insurer, lender, national company, Project SPV, or enterprise actor shall receive Board control, veto power, appointment control, publication control, research outcome control, technical baseline control, public authority access control, recognition influence, finance-readiness influence, certification influence, procurement influence, or correction-control rights by reason of support, participation, contract, affiliation, public authority status, technical contribution, or Nexus involvement.
105.22 Board Composition Records. The Corporation shall maintain Board Composition Records sufficient to demonstrate that the Board has been composed, reviewed, renewed, and adjusted in a lawful, independent, skills-balanced, public-benefit-aligned, anti-capture, and record-supported manner.
Board Composition Records shall include, as applicable:
a) director number records, minimum and maximum number records, Board-size resolutions, member approvals where required, Articles or Certificate references, bylaw references, transition records, vacancy records, and quorum impact records;
b) director eligibility records, consent records, appointment records, election records, nomination records, fit-and-proper records, integrity records, independence records, conflict records, related-party records, dual-role records, sanctions records, export-control records, controlled-technology records, and public authority capacity records;
c) skills matrix records, public-benefit governance competence records, United States nonprofit governance competence records, tax and state nonprofit law competence records, all-states-and-territories awareness records, North America cross-border awareness records, evidence and methods competence records, research integrity competence records, data / AI / cyber competence records, public-good software competence records, technology competence records, public authority interface competence records, safeguards competence records, finance-boundary competence records, competition and controlled-technology competence records, and diversity records;
d) independence review records, annual independence records, event-based independence records, capture-risk records, sponsor influence records, provider influence records, donor and funder influence records, host influence records, public authority influence records, investor, insurer, lender, bank, underwriter, public finance actor, national company, Project SPV, contractor, vendor, founder, affiliate, and enterprise actor influence records;
e) recusal records, access restriction records, committee restriction records, voting restriction records where lawful, mitigation records, influence cap records, diversification records, ring-fencing records, independent review records, non-renewal records, removal records, corrective action records, and public-safe clarification records;
f) Board renewal records, succession records, term-staggering records, continuity records, emergency Board composition records, skills-gap records, recruitment records, training records, evaluation records, and Board development records;
g) GCRI Canada interface records, GRF interface records, GRA interface records, Nexus interface records, consortium interface records, national company interface records, Project SPV interface records, provider interface records, sponsor interface records, host interface records, public authority interface records, university and laboratory interface records, and enterprise-stack boundary records;
h) records showing that Board composition does not create public authority delegation, finance-readiness authority, recognition authority, certification authority, procurement authority, provider preference, sponsor control, enterprise execution, shared liability, agency, partnership, alter ego status, or legal fusion with any external actor;
i) records of Board composition review, Board deliberation, Board vote, Board abstention, Board recusal, Board correction, Board hold, Board restriction, Board redesign, Board renewal, and Board public-safe clarification where needed; and
j) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that Board composition is a substantive fiduciary control. The Board shall be large enough to govern, independent enough to resist capture, skilled enough to understand the Corporation’s legal and technical obligations, diverse enough to reduce blind spots, disciplined enough to preserve boundaries, and bounded enough to remain accountable. No Board composition shall be permitted to convert the Corporation into a sponsor-controlled, provider-controlled, donor-controlled, public authority-controlled, capital-controlled, enterprise-controlled, founder-controlled, or Nexus-role-collapsed institution. Board composition shall be lawful, recorded, independent, balanced, public-benefit aligned, anti-capture, reviewable, and correctionable.
Section 106. Director Qualifications
106.1 Legal Eligibility. Each director shall be legally eligible to serve as a director of the Corporation under applicable law, the Articles or Certificate, this Bylaw, Board resolutions, member approvals where required, and any policy governing director eligibility, independence, conflicts, fit-and-proper review, sanctions, export-control, controlled technology, data / AI / cyber access, public authority interface, safeguards, and Nexus role separation.
Legal eligibility shall require that the person:
a) is not disqualified under governing state nonprofit corporation law, federal law, court order, regulatory order, sanctions law, export-control restriction, charitable registration rule, tax-exempt or tax-exempt-compatible requirement, or other applicable legal restriction;
b) is capable of consenting to serve and of discharging fiduciary duties;
c) is capable of acting in good faith, with care, loyalty, obedience to mission where applicable, prudence, diligence, independence, confidentiality, and correctional responsibility;
d) is capable of respecting the Corporation’s public-benefit purpose, nonprofit character, non-distribution rule, tax posture, non-execution perimeter, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, community safeguards, validity-by-record, and correctionability;
e) is not legally barred from accessing, governing, or being briefed on the classes of information, systems, records, or controlled materials reasonably necessary for Board service; and
f) satisfies any additional eligibility criteria adopted by the Board, provided that such criteria are lawful, public-benefit aligned, anti-capture, non-discriminatory where required, and consistent with this Bylaw.
No person shall be eligible to serve as a director merely by reason of founding status, donor status, sponsor status, provider status, public authority status, technical contribution, institutional prominence, academic reputation, capital-reader influence, Nexus ecosystem role, employment relationship, advisory role, public profile, or prior participation.
106.2 Consent to Serve. No person shall serve as a director unless the person has provided a written, electronic, or otherwise legally sufficient consent to serve, in form approved by the Corporation. Consent to serve shall be obtained before appointment, election, reappointment, renewal, or continued service where required by policy or Board resolution.
The consent to serve shall include, as applicable, acknowledgment that the director:
a) accepts the duties of a director under applicable law, the Articles or Certificate, this Bylaw, Board resolutions, and Board-approved policies;
b) understands that the director owes fiduciary duties to GCRI US as a separate legal entity;
c) understands that the director is not a delegate of any sponsor, donor, funder, provider, host, public authority, employer, university, laboratory, investor, insurer, lender, national company, Project SPV, community group, Nexus entity, GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), or other external person or body unless a legally authorized governance structure expressly provides otherwise;
d) agrees to disclose conflicts of interest and related-party relationships;
e) agrees to preserve confidentiality and controlled-material protections;
f) agrees to comply with data / AI / cyber, privacy, repository, controlled-room, public authority, finance-boundary, safeguards, public-safe publication, and competition rules;
g) agrees to support correction, supersession, withdrawal, retraction, takedown, and archival processes where required; and
h) agrees to resign, recuse, restrict access, submit to review, or accept other lawful corrective measures where continued participation would be inconsistent with law, fiduciary duties, independence, eligibility, or the Corporation’s mission lock.
Consent shall not cure legal ineligibility, unmanaged conflict, capture risk, sanctions restriction, export-control restriction, lack of independence where independence is required, or any other disqualification.
106.3 Fit-and-Proper Standard. Each director shall satisfy a fit-and-proper standard appropriate to the Corporation’s role as a United States nonprofit, public-benefit, non-executing technical institution and United States / North America anchor for evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, public authority learning, and community safeguards.
The fit-and-proper standard shall include review of whether the person has:
a) integrity, honesty, and reliability;
b) sound judgment;
c) respect for fiduciary governance;
d) demonstrated ability to act in the public interest;
e) ability to understand and comply with legal, nonprofit, tax, governance, data, AI, cyber, safeguards, and boundary controls;
f) ability to manage conflicts and disclose relevant interests;
g) ability to protect confidential, privileged, public authority, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, personal, community-protected, Tribal / Indigenous, local, territorial, cultural, environmental, or protected knowledge information;
h) absence of material misconduct inconsistent with Board service;
i) absence of unresolved conduct that would create unacceptable reputational, legal, public trust, public authority, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, sponsor non-control, data / AI / cyber, research integrity, or safeguards risk; and
j) willingness to be reviewed, trained, evaluated, corrected, and held accountable.
The fit-and-proper standard shall be applied proportionately, lawfully, and without unlawful discrimination. It shall be applied more restrictively where the proposed director would have access to sensitive records, controlled rooms, public authority interfaces, protected knowledge, data systems, technical assets, finance-adjacent materials, or strategic decisions of material significance.
106.4 Integrity Standard. Each director shall satisfy an integrity standard consistent with fiduciary service. Integrity includes truthfulness, transparency in conflicts, respect for institutional boundaries, respect for law, respect for public-benefit purpose, respect for protected persons and protected knowledge, respect for records, and willingness to correct error.
A person may fail the integrity standard where the Board determines, after appropriate review, that the person has engaged in or presents material unresolved risk relating to:
a) fraud, deception, misrepresentation, false credentials, or false public claims;
b) corruption, bribery, improper gifts, improper influence, or pay-to-play conduct;
c) research misconduct, data manipulation, evidence suppression, publication distortion, or sponsored finding manipulation;
d) misuse of confidential, privileged, controlled, public authority, cyber-sensitive, infrastructure-sensitive, finance-sensitive, personal, community-protected, Tribal / Indigenous, or protected knowledge information;
e) cyber misconduct, data misuse, AI misuse, unauthorized system access, credential misuse, repository misuse, or technical asset compromise;
f) harassment, retaliation, discrimination, civil rights violation, accessibility disregard, or protected participation interference;
g) public authority misrepresentation, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider-preference claim, sponsor-control arrangement, or Nexus-compatible status misuse;
h) sanctions, export-control, controlled-technology, national security, or restricted-party concern;
i) serious misconduct in a nonprofit, public-benefit, public authority, university, laboratory, enterprise, financial, insurance, infrastructure, technology, or community setting; or
j) persistent refusal to correct known error or misleading public meaning.
An integrity concern need not constitute a criminal conviction to be relevant. The Board may consider the seriousness, recency, evidence, pattern, remediation, accountability, legal constraints, and relevance to director service.
106.5 Fiduciary Capacity. Each director shall have the capacity to understand and discharge fiduciary duties to the Corporation. Fiduciary capacity requires more than nominal willingness to serve; it requires ability to exercise informed, independent, loyal, careful, prudent, good-faith, mission-obedient, and correctionable judgment.
A director shall be capable of:
a) understanding the Corporation’s public-benefit purposes;
b) distinguishing fiduciary service from advisory participation, sponsor representation, provider representation, public authority participation, technical authorship, ecosystem leadership, and personal advocacy;
c) reading and questioning Board materials;
d) understanding financial reports, budgets, risk reports, compliance reports, technical reports, safeguards reports, public authority interface reports, and correction records at a level appropriate to the director’s role;
e) asking for additional information when the record is incomplete;
f) recognizing when expert, counsel, compliance, safeguards, tax, technical, data, AI, cyber, or public authority review is needed;
g) recusing where required;
h) preserving confidentiality;
i) supporting lawful Board decisions once made, without waiving dissent rights where permitted; and
j) supporting correction where Board records, outputs, public claims, methods, evidence, data, AI, cyber systems, safeguards, or authority assumptions prove defective.
A person who cannot or will not exercise fiduciary judgment independently from external loyalty, funding dependency, employer interest, public authority position, sponsor interest, provider interest, founder pressure, political pressure, personal benefit, or technical allegiance shall not satisfy the fiduciary capacity requirement.
106.6 Time-Commitment Capacity. Each director shall have sufficient time and practical capacity to discharge the responsibilities of office. The Board shall not appoint or renew a director where the person’s commitments, conflicts, access limitations, availability, travel constraints, institutional duties, public authority restrictions, employment obligations, confidentiality barriers, or other circumstances materially prevent meaningful service.
Time-commitment capacity shall include capacity to:
a) attend Board meetings;
b) review Board materials in advance;
c) participate in deliberation;
d) complete required training;
e) submit annual and event-based disclosures;
f) respond to urgent governance matters where reasonably necessary;
g) serve on committees where appointed;
h) review major risks and reports;
i) support emergency or break-glass governance where applicable;
j) participate in Board evaluation and renewal processes;
k) assist with succession and continuity where needed; and
l) avoid passive service, prestige-only service, or unavailable directorship.
The Board may require a time-commitment acknowledgment, attendance standard, meeting participation record, committee participation record, or corrective plan where a director’s availability becomes materially deficient.
106.7 Confidentiality Capacity. Each director shall have the capacity and willingness to protect confidential, privileged, controlled, sensitive, and restricted information. Confidentiality capacity shall be a continuing qualification.
Confidentiality capacity shall include ability to comply with rules governing:
a) attorney-client privileged information;
b) attorney work product;
c) Board deliberations;
d) executive session materials;
e) controlled-room materials;
f) data-room, clean-room, evidence-room, public authority room, and no-download-room materials;
g) public authority materials;
h) cyber-sensitive and infrastructure-sensitive materials;
i) finance-sensitive and commercially sensitive materials;
j) personal information and rights-bearing data;
k) health-sensitive data;
l) community-protected, Tribal / Indigenous, local, territorial, cultural, environmental, and protected knowledge materials;
m) sponsor, donor, funder, provider, host, university, laboratory, contractor, partner, and third-party confidential information;
n) repository credentials, keys, tokens, secrets, vulnerability information, incident reports, and security controls;
o) research drafts, peer review, model review, red-team materials, and publication embargoes; and
p) nonpublic strategy, legal, risk, compliance, employment, compensation, and investigation records.
A person who cannot protect confidential information, who insists on using unapproved AI tools or shadow systems for controlled materials, who is subject to unmanaged external disclosure obligations, or who has a history of material confidentiality breach may be ineligible or subject to access restriction.
106.8 Conflict Disclosure Capacity. Each director shall have the capacity and willingness to identify, disclose, update, and manage conflicts of interest, related-party relationships, dual roles, institutional affiliations, funding relationships, technical interests, public authority capacities, and other circumstances that may affect fiduciary judgment or public trust.
Conflict disclosure capacity shall include the ability and willingness to disclose, as applicable:
a) employment, consulting, advisory, board, officer, fiduciary, ownership, investor, insurer, lender, underwriter, bank, public finance, contractor, vendor, provider, host, sponsor, donor, funder, university, laboratory, public authority, national company, Project SPV, GCRI Canada, GRF, GRA, Nexus entity, consortium, or enterprise relationships;
b) compensation, grants, donations, sponsorships, restricted funds, in-kind support, research support, technical support, public authority support, or institutional support;
c) intellectual property, data, software, dataset, model, benchmark, repository, license, technical asset, token, ledger, protocol, AI-RAN, O-RAN, DePIN, DLT, blockchain, digital twin, sensor, geospatial, cyber, or observability interests;
c) family, household, close personal, professional, political, or institutional relationships;
d) public authority capacity, regulator-listening status, public finance reader status, emergency-management participation, or official-capacity constraints;
e) research conflicts, publication conflicts, sponsor conflicts, provider conflicts, technical-method conflicts, and evidence conflicts;
f) community, Tribal, Indigenous, protected knowledge, civil rights, accessibility, or safeguards conflicts; and
g) any circumstance that could reasonably create an appearance of influence, capture, divided loyalty, or authority confusion.
A person who refuses to disclose conflicts, materially under-discloses, persistently late-discloses, or denies the relevance of conflicts to fiduciary governance shall not satisfy this qualification.
106.9 Independence Capacity. Each director shall have capacity to exercise independent judgment. Independence capacity means the person can act for the best interests of the Corporation, consistent with public-benefit purpose and law, notwithstanding external affiliations, personal relationships, technical commitments, public authority relationships, professional standing, sponsor pressure, provider pressure, donor expectations, funder expectations, employer expectations, political pressure, or Nexus ecosystem dynamics.
The Board shall assess whether the person can:
a) distinguish the Corporation’s legal interests from the interests of GCRI Canada, GRF, GRA, Nexus entities, public authorities, sponsors, providers, hosts, funders, universities, laboratories, national companies, Project SPVs, and enterprise actors;
b) vote against a sponsor, donor, provider, host, employer, public authority, or affiliate where required by fiduciary duty;
c) support withdrawal, correction, retraction, takedown, quarantine, or limitation of an output even where reputationally inconvenient;
d) preserve non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, and sponsor non-control despite external pressure;
e) decline public authority overclaim, finance-readiness overclaim, recognition overclaim, certification overclaim, procurement overclaim, or provider preference where requested by influential persons;
f) protect community safeguards and protected knowledge where technical, publication, sponsor, provider, or public authority interests press otherwise; and
g) accept recusal, access restriction, committee restriction, or other mitigation where independence is impaired for a matter.
Independence capacity may exist even where a director has affiliations, provided the affiliations are disclosed, reviewed, bounded, and do not materially impair judgment. Independence capacity shall not exist where an affiliation, dependency, expectation, or control right substantially prevents faithful service to the Corporation.
106.10 Public-Benefit Purpose Understanding. Each director shall understand the Corporation’s public-benefit purpose. This understanding shall include recognition that the Corporation exists to advance lawful public-good research, education, evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, verifiable compute and intelligence methods, public authority learning, community safeguards, and public-safe reporting support.
A director shall understand that public-benefit purpose requires:
a) mission fidelity;
b) public trust;
c) nonprofit discipline;
d) no private inurement;
e) no impermissible private benefit;
f) anti-capture controls;
g) public-safe communication;
h) community safeguards;
i) rights-respecting data and technology governance;
j) evidence integrity;
k) research integrity;
l) correctionability;
m) accessibility;
n) civil-rights awareness;
o) protection of Tribal, Indigenous, local, territorial, cultural, environmental, and protected knowledge; and
p) careful distinction between public-good stewardship and public authority or enterprise execution.
A director shall not treat public-benefit purpose as a slogan, branding tool, fundraising phrase, public authority access device, sponsor benefit, provider advantage, or substitute for legal compliance and fiduciary discipline.
106.11 United States Nonprofit Governance Understanding. Each director shall understand, or agree to be trained in, United States nonprofit governance principles relevant to the Corporation. This understanding shall include the relationship among applicable law, the Articles or Certificate, this Bylaw, Board resolutions, Board policies, committee charters, officer delegations, records, and corporate practice.
A director shall understand that:
a) the Board governs the Corporation subject to law and governing instruments;
b) directors owe duties to the Corporation and not to appointing persons, sponsors, donors, providers, public authorities, employers, communities, or external institutions unless otherwise legally required in a specific structure;
c) officers act by appointment and delegation;
d) committees act by charter and delegation;
e) participants, supporters, subscribers, donors, sponsors, fellows, advisors, public authority participants, technical contributors, and providers do not acquire governance rights unless lawfully granted;
f) Board actions require notice, quorum, vote, consent, resolution, minute, or other proper record;
g) conflicts must be disclosed and managed;
h) related-party transactions require review;
i) compensation must be reasonable and controlled;
j) restricted funds must be used for their restricted purposes;
k) corporate records matter; and
l) informal practice, website language, public statements, AI summaries, slide decks, sponsorship documents, grant proposals, or Nexus references do not amend the Bylaw.
Directors shall accept training where needed and shall not claim lack of nonprofit governance familiarity as a basis to disregard fiduciary obligations.
106.12 Tax-Exempt or Tax-Exempt-Compatible Governance Understanding. Each director shall understand, or agree to be trained in, the Corporation’s tax-exempt or tax-exempt-compatible governance obligations as applicable and as recorded. No director shall assume that the Corporation holds a particular tax classification unless the classification is obtained, maintained, and recorded.
A director shall understand that tax-exempt or tax-exempt-compatible governance may require attention to:
a) charitable, educational, scientific, or other exempt purposes where applicable;
b) public-benefit purpose;
c) no private inurement;
d) no impermissible private benefit;
e) excess benefit transaction controls;
f) reasonable compensation;
g) unrelated business income risk;
h) lobbying and political activity limits where applicable;
i) donor acknowledgment rules where applicable;
j) charitable solicitation rules where applicable;
k) restricted funds;
l) sponsorship and advertising distinctions where applicable;
m) public support records where applicable;
n) fiscal sponsorship, sponsored project, supporting organization, or alternative nonprofit structure issues where applicable; and
o) dissolution and asset dedication rules.
A director shall not approve or support public representations about tax status, charitable status, donation deductibility, donor receipts, public support, exemption category, or fundraising treatment unless supported by competent records and review.
106.13 Non-Execution Understanding. Each director shall understand the Corporation’s bright-line non-execution character. The Corporation is not an execution vehicle and shall not become a regulator, public authority, emergency command body, public warning authority, procurement body, certification body, recognition body, finance-readiness body, fund, broker, dealer, finder, investment adviser, lender, insurer, underwriter, rating agency, bank, public finance approver, national company, Project SPV, provider, operator, asset owner, or enterprise delivery company by Board drift, technical centrality, public authority participation, sponsor pressure, provider participation, or Nexus involvement.
A director shall understand that the Corporation may support evidence, methods, public-good software, technical baselines, controlled rooms, public authority learning, Docket support, Grid support, GRF-facing inputs, GRA-facing technical inputs, and Nexus-compatible interoperability only within lawful, recorded, public-safe, non-executing boundaries.
A director shall be capable of identifying execution drift in:
a) public reports;
b) dashboards;
c) maps;
d) proof receipts;
e) controlled rooms;
f) public authority rooms;
g) capital-reader materials;
h) sponsor materials;
i) provider materials;
j) technical baselines;
k) software releases;
l) AI, model, digital twin, DePIN, DLT, blockchain, AI-RAN, O-RAN, sensor, geospatial, cyber, or observability outputs;
m) public statements;
n) contracts;
o) grant proposals;
p) public authority memoranda; and
q) Nexus interface records.
A director shall support hold, stop, quarantine, re-scope, externalization, referral, correction, or termination where execution risk arises.
106.14 GCRI / GRF / GRA Role-Separation Understanding. Each director shall understand the role separation among GCRI US, GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), and the broader Nexus public-good stack.
A director shall understand that:
a) GCRI US is an evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, verifiable compute and intelligence methods, public authority learning, and safeguards institution;
b) GCRI Canada is a separate Canadian public-benefit anchor and not a legal extension of GCRI US;
c) The Global Risks Forum (GRF) is the public-good registry, recognition, maturity-records, standing, claims-discipline, stakeholder-formation, public-safe reporting, and public-facing legitimacy steward;
d) The Global Risks Alliance (GRA) is the finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, capital-reader-room, and regulated-perimeter discipline steward;
e) Nexus Standards, protocol authorities, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, providers, sponsors, hosts, and enterprise actors each have distinct roles where constituted; and
f) technical support, shared mission, shared ontology, shared records, shared public-good instruments, or interoperable systems do not create shared authority, merger, agency, recognition authority, finance-readiness authority, certification authority, procurement authority, public authority status, or execution authority.
A director shall be capable of preventing evidence inputs from becoming recognition determinations, technical inputs from becoming finance-readiness determinations, technical baselines from becoming certification or procurement approvals, and Nexus-compatible language from becoming unsupported authority.
106.15 Public Authority Boundary Understanding. Each director shall understand the Corporation’s public authority boundary. The Corporation may support public authority learning, evidence literacy, technical literacy, public-safe reporting literacy, scenario learning, simulation, tabletop exercises, after-action learning, capacity classification, public authority rooms, regulator-listening participation, public finance reader participation, emergency-management learning participation, and public infrastructure operator participation, but shall not act as or substitute for a public authority.
A director shall understand that the Corporation shall not:
a) issue official public warnings;
b) command emergency response;
c) issue evacuation, dispatch, or safety instructions;
d) issue public health orders;
e) regulate, enforce, permit, inspect as authority, or approve compliance;
f) approve public procurement;
g) approve public finance, grants, budgets, appropriations, guarantees, tax credits, or sovereign obligations;
h) speak for a public authority without written authorization;
i) create public-private partnership status without lawful authority;
j) convert public authority participation into official adoption;
k) create public authority reliance through dashboards, maps, AI outputs, proof receipts, observability signals, digital twins, or public-safe reports; or
l) imply public authority endorsement through naming, attendance, minutes, reports, logos, quotes, or references.
A director shall support capacity classification, public authority reference review, public-safe limitation language, meeting records, correction, and public clarification where public authority confusion arises.
106.16 Finance, Securities, Insurance, Lending, Rating, Public Finance, Procurement, and Certification Boundary Understanding. Each director shall understand the Corporation’s finance, securities, insurance, lending, rating, public finance, procurement, certification, accreditation, and regulated-activity boundaries.
A director shall understand that the Corporation shall not conduct or imply:
a) securities offering, distribution, solicitation, underwriting, brokerage, dealer activity, finder activity, or capital placement;
b) investment advice, investment adviser activity, portfolio management, asset management, suitability determination, capital recommendation, or transaction recommendation;
c) banking, deposit-taking, payment intermediation, custody, clearing, settlement, escrow, or third-party fund control;
d) lending, credit origination, credit approval, credit brokerage, guarantee, revenue guarantee, or performance guarantee;
e) insurance placement, reinsurance placement, underwriting, pricing, binding, claims handling, risk-bearing intermediation, or insurance approval;
f) rating, credit opinion, investment grade opinion, resilience rating, insurability rating, bankability rating, or financeability determination;
g) public finance approval, tax credit approval, grant approval, budget allocation, appropriation, public guarantee, MDB / DFI approval, or sovereign finance approval;
h) procurement award, vendor selection, procurement approval, procurement preference, or public authority vendor recommendation;
i) certification, accreditation, legal compliance approval, standards conformance approval, safe harbor, or professional credential by default;
j) GRF recognition, maturity, standing, legitimacy, Docket approval, Grid standing, or claims-discipline determination; or
k) GRA finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, or capital-reader-room determination.
A director shall be able to identify regulated-perimeter risk in language, scores, dashboards, technical profiles, evidence packs, proof receipts, controlled rooms, public authority materials, capital-reader materials, sponsor materials, provider materials, and public-facing claims.
106.17 Data / AI / Cyber / Privacy Understanding. Each director shall understand, or agree to be trained in, the Corporation’s data / AI / cyber / privacy obligations and the governance significance of technical systems. Such understanding shall include recognition that data, AI, cyber, software, compute, observability, dashboard, digital twin, DePIN, DLT, blockchain, AI-RAN, O-RAN, sensor, geospatial, and repository systems can create material legal, public safety, civil rights, community, protected knowledge, public authority, finance-boundary, and reputational risk.
A director shall understand the need for controls relating to:
a) data classification;
b) lawful basis, consent, non-consent, restriction, and withdrawal where applicable;
c) data minimization;
d) privacy and confidentiality;
e) access control;
f) identity and credential management;
g) model registers;
h) inference records;
i) compute workload records;
j) dataset cards, model cards, system cards, benchmark cards, and evaluation records;
k) agentic AI controls;
l) human review of material automated outputs;
m) secure development;
n) repository security;
o) SBOM, signing, provenance, dependency, vulnerability, key, token, secret, and credential controls;
p) incident response;
q) disaster recovery and business continuity;
r) breach notification where required;
s) restrictions on unapproved AI tools; and
t) public-safe correction of technical outputs.
A director shall understand that no AI system, dashboard, digital twin, proof receipt, ledger entry, DePIN record, AI-RAN signal, O-RAN signal, sensor output, cyber telemetry, model output, or automated score shall be treated as final institutional authority without competent human review, record support, limitation, and correction pathway.
106.18 Research Integrity Understanding. Each director shall understand the Corporation’s research integrity obligations and the role of the Board in preserving truthful, lawful, ethical, reproducible where appropriate, peer-reviewable where appropriate, publicly bounded, and correctionable research.
Research integrity understanding shall include awareness of:
a) research design integrity;
b) research ethics;
c) human-subjects review where required;
d) community review where appropriate;
e) Tribal, Indigenous, local, territorial, health-sensitive, youth, vulnerable population, civil rights, accessibility, and protected knowledge review where applicable;
f) consent, non-consent, restriction, withdrawal, correction, and complaint pathways where applicable;
g) sponsor and funder disclosure;
h) conflict disclosure;
i) publication independence;
j) reproducibility and replication;
k) peer review and technical review;
l) AI-use disclosure where material;
m) data rights and privacy controls;
n) publication integrity; and
o) correction, supersession, withdrawal, retraction, takedown, and archive pathways.
A director shall understand that research outputs shall not be used as disguised commercial endorsements, provider preferences, public authority approvals, finance-readiness determinations, certification substitutes, procurement tools, recognition purchases, sponsor-controlled findings, or protected knowledge extraction mechanisms.
106.19 Civil Rights, Accessibility, Community Safeguards, Tribal and Indigenous Protocol, and Protected Knowledge Understanding. Each director shall understand the Corporation’s obligations concerning civil rights, accessibility, community safeguards, Tribal and Indigenous protocol respect, Indigenous data safeguards, local and territorial knowledge, and protected knowledge.
A director shall understand that the Corporation’s public-benefit mission cannot be discharged through technical excellence alone, and that technical, evidentiary, publication, observability, AI, cyber, public authority, sponsor, provider, or Nexus objectives must be bounded by safeguards where persons, communities, rights, or protected knowledge may be affected.
This understanding shall include awareness of:
a) non-discrimination;
b) accessibility;
c) inclusive participation;
d) vulnerable and remote community safeguards;
e) Tribal sovereignty respect;
f) Indigenous governance respect;
g) Indigenous data safeguards;
h) local and territorial knowledge protections;
i) cultural, environmental, sacred, sensitive, and community-protected knowledge protections;
j) consent, non-consent, attribution, restriction, withdrawal, and correction pathways where applicable;
k) public-safe mapping;
l) surveillance and re-identification risks;
m) AI training, model improvement, embedding, retrieval, or analytics risks involving protected materials;
n) grievance and remedy pathways;
o) protected participation, whistleblowing, dissent protection, and non-retaliation; and
p) do-no-harm review.
A director shall be willing to support hold, restriction, redaction, non-publication, re-scoping, public-safe limitation, community review, correction, withdrawal, takedown, or remedy where safeguards require it.
106.20 Competition, Sanctions, Export-Control, and Controlled Technology Awareness. Each director shall have awareness, or agree to receive training, concerning competition, antitrust, sanctions, export-control, controlled technology, and national security sensitivity issues relevant to the Corporation’s activities.
Such awareness shall include the need to prevent:
a) price, margin, cost, bid, wage, customer, supplier, market allocation, capacity, exclusion, boycott, procurement steering, or collusive strategy discussion;
b) misuse of benchmarking, indices, datasets, labs, challenges, technical comparisons, standards-support activity, controlled rooms, or public authority forums to exchange competitively sensitive information;
c) sponsor or provider influence over competition-relevant outputs;
d) unlawful coordination among providers, vendors, operators, investors, insurers, lenders, underwriters, banks, public finance actors, national companies, Project SPVs, or enterprise actors;
e) sanctions violations;
f) dealings with restricted parties;
g) export-control violations;
h) unauthorized release of controlled technology;
i) inappropriate cross-border transfer of sensitive data, software, models, technical baselines, cyber materials, telecom materials, AI-RAN or O-RAN materials, geospatial materials, satellite or Earth observation materials, sovereign compute materials, semiconductor materials, quantum-relevant materials, biosecurity materials, or dual-use materials; and
j) failure to escalate national security sensitivity or controlled-technology concerns.
A director shall respect clean-team, clean-room, aggregation, de-identification, delay, independent administration, stop-meeting, hold, quarantine, and counsel-review controls where required.
106.21 Willingness to Follow Validity-by-Record and Correctionability. Each director shall be willing to follow validity-by-record and correctionability as core governance disciplines. A director shall understand that institutional validity arises from lawful authority, competent approval, accurate records, proper versioning, controlled vocabulary, limitation language, repository discipline, public-safe notice where required, and correction pathways, not from seniority, informal consensus, technical centrality, public repetition, sponsor support, public authority attendance, AI output, dashboard display, proof receipt, ledger entry, or Nexus reference alone.
A director shall be willing to require records for:
a) Board approvals;
b) officer delegations;
c) committee charters;
d) conflicts and recusals;
e) public authority capacities;
f) finance-boundary reviews;
g) certification-boundary reviews;
h) procurement-neutrality reviews;
i) provider-neutrality and sponsor non-control reviews;
j) data access;
k) AI use;
l) cyber controls;
m) research ethics;
n) community safeguards;
o) protected knowledge;
p) evidence methods;
q) technical baselines;
r) software releases;
s) public-safe publications; and
t) corrections.
A director shall be willing to support correction where a record is defective, absent, misleading, stale, superseded, overclaimed, unauthorized, incomplete, or inconsistent with law, this Bylaw, public-benefit purpose, non-execution, role separation, safeguards, or public-safe communication.
No person shall be qualified to serve as a director if the person rejects correction, treats record discipline as optional, insists that informal authority is sufficient, or uses reputation, urgency, sponsor pressure, provider pressure, public authority interest, technical excitement, or fundraising need to bypass required records.
106.22 Director Qualification Records. The Corporation shall maintain Director Qualification Records sufficient to demonstrate that each director has been reviewed, qualified, appointed, trained, monitored, renewed, restricted, corrected, or removed in accordance with applicable law, the Articles or Certificate, this Bylaw, Board resolutions, policies, and fiduciary standards.
Director Qualification Records shall include, as applicable:
a) legal eligibility records, consent-to-serve records, appointment or election records, member approval records where required, incorporator records where applicable, Board resolution records, director register entries, and effective-date records;
b) fit-and-proper review records, integrity review records, fiduciary capacity records, time-commitment capacity records, confidentiality capacity records, conflict disclosure capacity records, independence capacity records, and good-standing records;
c) public-benefit purpose understanding records, United States nonprofit governance understanding records, tax-exempt or tax-exempt-compatible understanding records, non-execution understanding records, GCRI / GRF / GRA role-separation understanding records, public authority boundary understanding records, finance, securities, insurance, lending, rating, public finance, procurement, and certification boundary understanding records;
d) data / AI / cyber / privacy understanding records, research integrity understanding records, civil rights, accessibility, community safeguards, Tribal and Indigenous protocol, protected knowledge understanding records, competition awareness records, sanctions awareness records, export-control awareness records, controlled-technology awareness records, and national security sensitivity awareness records;
e) training records, certifications of understanding, annual attestations, event-based attestations, policy acknowledgments, confidentiality acknowledgments, AI-use acknowledgments, controlled-room acknowledgments, public authority boundary acknowledgments, finance-boundary acknowledgments, safeguards acknowledgments, non-retaliation acknowledgments, and correctionability acknowledgments;
f) conflict disclosures, related-party disclosures, dual-role disclosures, sponsor relationship disclosures, provider relationship disclosures, donor and funder relationship disclosures, host relationship disclosures, public authority capacity disclosures, investor, insurer, lender, underwriter, bank, public finance actor, national company, Project SPV, university, laboratory, contractor, vendor, employer, affiliate, GCRI Canada, GRF, GRA, Nexus entity, and consortium relationship disclosures;
g) sanctions screening records, export-control screening records, restricted-party screening records, controlled-technology screening records, data access screening records, cyber access screening records, repository access screening records, public authority interface screening records, finance-boundary screening records, safeguards screening records, and protected knowledge screening records;
h) independence determinations, recusal determinations, access restrictions, committee restrictions, voting restrictions where lawful, mitigation plans, corrective training, probation records, non-renewal records, resignation records, removal records, and post-service access revocation records;
i) records of any qualification concern, eligibility challenge, integrity concern, conflict concern, confidentiality concern, public authority boundary concern, finance-boundary concern, certification-boundary concern, procurement-neutrality concern, provider-neutrality concern, sponsor non-control concern, data / AI / cyber concern, research integrity concern, safeguards concern, or correctionability concern, together with the review, decision, mitigation, and outcome; and
j) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that director qualification is an active fiduciary safeguard, not a ceremonial onboarding step. A director must be legally eligible, willing to serve, fit and proper, independent enough to govern, capable of fiduciary judgment, able to protect confidential and controlled materials, able to disclose conflicts, competent or trainable in the Corporation’s public-benefit and nonprofit obligations, and willing to preserve non-execution, role separation, public authority boundaries, finance boundaries, data / AI / cyber controls, safeguards, validity-by-record, and correctionability. Director qualification shall be lawful, recorded, reviewed, updated, bounded, enforceable, and correctionable.
Section 106. Director Qualifications
106.1 Legal Eligibility. Each director shall be legally eligible to serve as a director of the Corporation under applicable law, the Articles or Certificate, this Bylaw, Board resolutions, member approvals where required, and any policy governing director eligibility, independence, conflicts, fit-and-proper review, sanctions, export-control, controlled technology, data / AI / cyber access, public authority interface, safeguards, and Nexus role separation.
Legal eligibility shall require that the person:
a) is not disqualified under governing state nonprofit corporation law, federal law, court order, regulatory order, sanctions law, export-control restriction, charitable registration rule, tax-exempt or tax-exempt-compatible requirement, or other applicable legal restriction;
b) is capable of consenting to serve and of discharging fiduciary duties;
c) is capable of acting in good faith, with care, loyalty, obedience to mission where applicable, prudence, diligence, independence, confidentiality, and correctional responsibility;
d) is capable of respecting the Corporation’s public-benefit purpose, nonprofit character, non-distribution rule, tax posture, non-execution perimeter, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, community safeguards, validity-by-record, and correctionability;
e) is not legally barred from accessing, governing, or being briefed on the classes of information, systems, records, or controlled materials reasonably necessary for Board service; and
f) satisfies any additional eligibility criteria adopted by the Board, provided that such criteria are lawful, public-benefit aligned, anti-capture, non-discriminatory where required, and consistent with this Bylaw.
No person shall be eligible to serve as a director merely by reason of founding status, donor status, sponsor status, provider status, public authority status, technical contribution, institutional prominence, academic reputation, capital-reader influence, Nexus ecosystem role, employment relationship, advisory role, public profile, or prior participation.
106.2 Consent to Serve. No person shall serve as a director unless the person has provided a written, electronic, or otherwise legally sufficient consent to serve, in form approved by the Corporation. Consent to serve shall be obtained before appointment, election, reappointment, renewal, or continued service where required by policy or Board resolution.
The consent to serve shall include, as applicable, acknowledgment that the director:
a) accepts the duties of a director under applicable law, the Articles or Certificate, this Bylaw, Board resolutions, and Board-approved policies;
b) understands that the director owes fiduciary duties to GCRI US as a separate legal entity;
c) understands that the director is not a delegate of any sponsor, donor, funder, provider, host, public authority, employer, university, laboratory, investor, insurer, lender, national company, Project SPV, community group, Nexus entity, GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), or other external person or body unless a legally authorized governance structure expressly provides otherwise;
d) agrees to disclose conflicts of interest and related-party relationships;
e) agrees to preserve confidentiality and controlled-material protections;
f) agrees to comply with data / AI / cyber, privacy, repository, controlled-room, public authority, finance-boundary, safeguards, public-safe publication, and competition rules;
g) agrees to support correction, supersession, withdrawal, retraction, takedown, and archival processes where required; and
h) agrees to resign, recuse, restrict access, submit to review, or accept other lawful corrective measures where continued participation would be inconsistent with law, fiduciary duties, independence, eligibility, or the Corporation’s mission lock.
Consent shall not cure legal ineligibility, unmanaged conflict, capture risk, sanctions restriction, export-control restriction, lack of independence where independence is required, or any other disqualification.
106.3 Fit-and-Proper Standard. Each director shall satisfy a fit-and-proper standard appropriate to the Corporation’s role as a United States nonprofit, public-benefit, non-executing technical institution and United States / North America anchor for evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, public authority learning, and community safeguards.
The fit-and-proper standard shall include review of whether the person has:
a) integrity, honesty, and reliability;
b) sound judgment;
c) respect for fiduciary governance;
d) demonstrated ability to act in the public interest;
e) ability to understand and comply with legal, nonprofit, tax, governance, data, AI, cyber, safeguards, and boundary controls;
f) ability to manage conflicts and disclose relevant interests;
g) ability to protect confidential, privileged, public authority, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, personal, community-protected, Tribal / Indigenous, local, territorial, cultural, environmental, or protected knowledge information;
h) absence of material misconduct inconsistent with Board service;
i) absence of unresolved conduct that would create unacceptable reputational, legal, public trust, public authority, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, sponsor non-control, data / AI / cyber, research integrity, or safeguards risk; and
j) willingness to be reviewed, trained, evaluated, corrected, and held accountable.
The fit-and-proper standard shall be applied proportionately, lawfully, and without unlawful discrimination. It shall be applied more restrictively where the proposed director would have access to sensitive records, controlled rooms, public authority interfaces, protected knowledge, data systems, technical assets, finance-adjacent materials, or strategic decisions of material significance.
106.4 Integrity Standard. Each director shall satisfy an integrity standard consistent with fiduciary service. Integrity includes truthfulness, transparency in conflicts, respect for institutional boundaries, respect for law, respect for public-benefit purpose, respect for protected persons and protected knowledge, respect for records, and willingness to correct error.
A person may fail the integrity standard where the Board determines, after appropriate review, that the person has engaged in or presents material unresolved risk relating to:
a) fraud, deception, misrepresentation, false credentials, or false public claims;
b) corruption, bribery, improper gifts, improper influence, or pay-to-play conduct;
c) research misconduct, data manipulation, evidence suppression, publication distortion, or sponsored finding manipulation;
d) misuse of confidential, privileged, controlled, public authority, cyber-sensitive, infrastructure-sensitive, finance-sensitive, personal, community-protected, Tribal / Indigenous, or protected knowledge information;
e) cyber misconduct, data misuse, AI misuse, unauthorized system access, credential misuse, repository misuse, or technical asset compromise;
f) harassment, retaliation, discrimination, civil rights violation, accessibility disregard, or protected participation interference;
g) public authority misrepresentation, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider-preference claim, sponsor-control arrangement, or Nexus-compatible status misuse;
h) sanctions, export-control, controlled-technology, national security, or restricted-party concern;
i) serious misconduct in a nonprofit, public-benefit, public authority, university, laboratory, enterprise, financial, insurance, infrastructure, technology, or community setting; or
j) persistent refusal to correct known error or misleading public meaning.
An integrity concern need not constitute a criminal conviction to be relevant. The Board may consider the seriousness, recency, evidence, pattern, remediation, accountability, legal constraints, and relevance to director service.
106.5 Fiduciary Capacity. Each director shall have the capacity to understand and discharge fiduciary duties to the Corporation. Fiduciary capacity requires more than nominal willingness to serve; it requires ability to exercise informed, independent, loyal, careful, prudent, good-faith, mission-obedient, and correctionable judgment.
A director shall be capable of:
a) understanding the Corporation’s public-benefit purposes;
b) distinguishing fiduciary service from advisory participation, sponsor representation, provider representation, public authority participation, technical authorship, ecosystem leadership, and personal advocacy;
c) reading and questioning Board materials;
d) understanding financial reports, budgets, risk reports, compliance reports, technical reports, safeguards reports, public authority interface reports, and correction records at a level appropriate to the director’s role;
e) asking for additional information when the record is incomplete;
f) recognizing when expert, counsel, compliance, safeguards, tax, technical, data, AI, cyber, or public authority review is needed;
g) recusing where required;
h) preserving confidentiality;
i) supporting lawful Board decisions once made, without waiving dissent rights where permitted; and
j) supporting correction where Board records, outputs, public claims, methods, evidence, data, AI, cyber systems, safeguards, or authority assumptions prove defective.
A person who cannot or will not exercise fiduciary judgment independently from external loyalty, funding dependency, employer interest, public authority position, sponsor interest, provider interest, founder pressure, political pressure, personal benefit, or technical allegiance shall not satisfy the fiduciary capacity requirement.
106.6 Time-Commitment Capacity. Each director shall have sufficient time and practical capacity to discharge the responsibilities of office. The Board shall not appoint or renew a director where the person’s commitments, conflicts, access limitations, availability, travel constraints, institutional duties, public authority restrictions, employment obligations, confidentiality barriers, or other circumstances materially prevent meaningful service.
Time-commitment capacity shall include capacity to:
a) attend Board meetings;
b) review Board materials in advance;
c) participate in deliberation;
d) complete required training;
e) submit annual and event-based disclosures;
f) respond to urgent governance matters where reasonably necessary;
g) serve on committees where appointed;
h) review major risks and reports;
i) support emergency or break-glass governance where applicable;
j) participate in Board evaluation and renewal processes;
k) assist with succession and continuity where needed; and
l) avoid passive service, prestige-only service, or unavailable directorship.
The Board may require a time-commitment acknowledgment, attendance standard, meeting participation record, committee participation record, or corrective plan where a director’s availability becomes materially deficient.
106.7 Confidentiality Capacity. Each director shall have the capacity and willingness to protect confidential, privileged, controlled, sensitive, and restricted information. Confidentiality capacity shall be a continuing qualification.
Confidentiality capacity shall include ability to comply with rules governing:
a) attorney-client privileged information;
b) attorney work product;
c) Board deliberations;
d) executive session materials;
e) controlled-room materials;
f) data-room, clean-room, evidence-room, public authority room, and no-download-room materials;
g) public authority materials;
h) cyber-sensitive and infrastructure-sensitive materials;
i) finance-sensitive and commercially sensitive materials;
j) personal information and rights-bearing data;
k) health-sensitive data;
l) community-protected, Tribal / Indigenous, local, territorial, cultural, environmental, and protected knowledge materials;
m) sponsor, donor, funder, provider, host, university, laboratory, contractor, partner, and third-party confidential information;
n) repository credentials, keys, tokens, secrets, vulnerability information, incident reports, and security controls;
o) research drafts, peer review, model review, red-team materials, and publication embargoes; and
p) nonpublic strategy, legal, risk, compliance, employment, compensation, and investigation records.
A person who cannot protect confidential information, who insists on using unapproved AI tools or shadow systems for controlled materials, who is subject to unmanaged external disclosure obligations, or who has a history of material confidentiality breach may be ineligible or subject to access restriction.
106.8 Conflict Disclosure Capacity. Each director shall have the capacity and willingness to identify, disclose, update, and manage conflicts of interest, related-party relationships, dual roles, institutional affiliations, funding relationships, technical interests, public authority capacities, and other circumstances that may affect fiduciary judgment or public trust.
Conflict disclosure capacity shall include the ability and willingness to disclose, as applicable:
a) employment, consulting, advisory, board, officer, fiduciary, ownership, investor, insurer, lender, underwriter, bank, public finance, contractor, vendor, provider, host, sponsor, donor, funder, university, laboratory, public authority, national company, Project SPV, GCRI Canada, GRF, GRA, Nexus entity, consortium, or enterprise relationships;
b) compensation, grants, donations, sponsorships, restricted funds, in-kind support, research support, technical support, public authority support, or institutional support;
c) intellectual property, data, software, dataset, model, benchmark, repository, license, technical asset, token, ledger, protocol, AI-RAN, O-RAN, DePIN, DLT, blockchain, digital twin, sensor, geospatial, cyber, or observability interests;
c) family, household, close personal, professional, political, or institutional relationships;
d) public authority capacity, regulator-listening status, public finance reader status, emergency-management participation, or official-capacity constraints;
e) research conflicts, publication conflicts, sponsor conflicts, provider conflicts, technical-method conflicts, and evidence conflicts;
f) community, Tribal, Indigenous, protected knowledge, civil rights, accessibility, or safeguards conflicts; and
g) any circumstance that could reasonably create an appearance of influence, capture, divided loyalty, or authority confusion.
A person who refuses to disclose conflicts, materially under-discloses, persistently late-discloses, or denies the relevance of conflicts to fiduciary governance shall not satisfy this qualification.
106.9 Independence Capacity. Each director shall have capacity to exercise independent judgment. Independence capacity means the person can act for the best interests of the Corporation, consistent with public-benefit purpose and law, notwithstanding external affiliations, personal relationships, technical commitments, public authority relationships, professional standing, sponsor pressure, provider pressure, donor expectations, funder expectations, employer expectations, political pressure, or Nexus ecosystem dynamics.
The Board shall assess whether the person can:
a) distinguish the Corporation’s legal interests from the interests of GCRI Canada, GRF, GRA, Nexus entities, public authorities, sponsors, providers, hosts, funders, universities, laboratories, national companies, Project SPVs, and enterprise actors;
b) vote against a sponsor, donor, provider, host, employer, public authority, or affiliate where required by fiduciary duty;
c) support withdrawal, correction, retraction, takedown, quarantine, or limitation of an output even where reputationally inconvenient;
d) preserve non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, and sponsor non-control despite external pressure;
e) decline public authority overclaim, finance-readiness overclaim, recognition overclaim, certification overclaim, procurement overclaim, or provider preference where requested by influential persons;
f) protect community safeguards and protected knowledge where technical, publication, sponsor, provider, or public authority interests press otherwise; and
g) accept recusal, access restriction, committee restriction, or other mitigation where independence is impaired for a matter.
Independence capacity may exist even where a director has affiliations, provided the affiliations are disclosed, reviewed, bounded, and do not materially impair judgment. Independence capacity shall not exist where an affiliation, dependency, expectation, or control right substantially prevents faithful service to the Corporation.
106.10 Public-Benefit Purpose Understanding. Each director shall understand the Corporation’s public-benefit purpose. This understanding shall include recognition that the Corporation exists to advance lawful public-good research, education, evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, verifiable compute and intelligence methods, public authority learning, community safeguards, and public-safe reporting support.
A director shall understand that public-benefit purpose requires:
a) mission fidelity;
b) public trust;
c) nonprofit discipline;
d) no private inurement;
e) no impermissible private benefit;
f) anti-capture controls;
g) public-safe communication;
h) community safeguards;
i) rights-respecting data and technology governance;
j) evidence integrity;
k) research integrity;
l) correctionability;
m) accessibility;
n) civil-rights awareness;
o) protection of Tribal, Indigenous, local, territorial, cultural, environmental, and protected knowledge; and
p) careful distinction between public-good stewardship and public authority or enterprise execution.
A director shall not treat public-benefit purpose as a slogan, branding tool, fundraising phrase, public authority access device, sponsor benefit, provider advantage, or substitute for legal compliance and fiduciary discipline.
106.11 United States Nonprofit Governance Understanding. Each director shall understand, or agree to be trained in, United States nonprofit governance principles relevant to the Corporation. This understanding shall include the relationship among applicable law, the Articles or Certificate, this Bylaw, Board resolutions, Board policies, committee charters, officer delegations, records, and corporate practice.
A director shall understand that:
a) the Board governs the Corporation subject to law and governing instruments;
b) directors owe duties to the Corporation and not to appointing persons, sponsors, donors, providers, public authorities, employers, communities, or external institutions unless otherwise legally required in a specific structure;
c) officers act by appointment and delegation;
d) committees act by charter and delegation;
e) participants, supporters, subscribers, donors, sponsors, fellows, advisors, public authority participants, technical contributors, and providers do not acquire governance rights unless lawfully granted;
f) Board actions require notice, quorum, vote, consent, resolution, minute, or other proper record;
g) conflicts must be disclosed and managed;
h) related-party transactions require review;
i) compensation must be reasonable and controlled;
j) restricted funds must be used for their restricted purposes;
k) corporate records matter; and
l) informal practice, website language, public statements, AI summaries, slide decks, sponsorship documents, grant proposals, or Nexus references do not amend the Bylaw.
Directors shall accept training where needed and shall not claim lack of nonprofit governance familiarity as a basis to disregard fiduciary obligations.
106.12 Tax-Exempt or Tax-Exempt-Compatible Governance Understanding. Each director shall understand, or agree to be trained in, the Corporation’s tax-exempt or tax-exempt-compatible governance obligations as applicable and as recorded. No director shall assume that the Corporation holds a particular tax classification unless the classification is obtained, maintained, and recorded.
A director shall understand that tax-exempt or tax-exempt-compatible governance may require attention to:
a) charitable, educational, scientific, or other exempt purposes where applicable;
b) public-benefit purpose;
c) no private inurement;
d) no impermissible private benefit;
e) excess benefit transaction controls;
f) reasonable compensation;
g) unrelated business income risk;
h) lobbying and political activity limits where applicable;
i) donor acknowledgment rules where applicable;
j) charitable solicitation rules where applicable;
k) restricted funds;
l) sponsorship and advertising distinctions where applicable;
m) public support records where applicable;
n) fiscal sponsorship, sponsored project, supporting organization, or alternative nonprofit structure issues where applicable; and
o) dissolution and asset dedication rules.
A director shall not approve or support public representations about tax status, charitable status, donation deductibility, donor receipts, public support, exemption category, or fundraising treatment unless supported by competent records and review.
106.13 Non-Execution Understanding. Each director shall understand the Corporation’s bright-line non-execution character. The Corporation is not an execution vehicle and shall not become a regulator, public authority, emergency command body, public warning authority, procurement body, certification body, recognition body, finance-readiness body, fund, broker, dealer, finder, investment adviser, lender, insurer, underwriter, rating agency, bank, public finance approver, national company, Project SPV, provider, operator, asset owner, or enterprise delivery company by Board drift, technical centrality, public authority participation, sponsor pressure, provider participation, or Nexus involvement.
A director shall understand that the Corporation may support evidence, methods, public-good software, technical baselines, controlled rooms, public authority learning, Docket support, Grid support, GRF-facing inputs, GRA-facing technical inputs, and Nexus-compatible interoperability only within lawful, recorded, public-safe, non-executing boundaries.
A director shall be capable of identifying execution drift in:
a) public reports;
b) dashboards;
c) maps;
d) proof receipts;
e) controlled rooms;
f) public authority rooms;
g) capital-reader materials;
h) sponsor materials;
i) provider materials;
j) technical baselines;
k) software releases;
l) AI, model, digital twin, DePIN, DLT, blockchain, AI-RAN, O-RAN, sensor, geospatial, cyber, or observability outputs;
m) public statements;
n) contracts;
o) grant proposals;
p) public authority memoranda; and
q) Nexus interface records.
A director shall support hold, stop, quarantine, re-scope, externalization, referral, correction, or termination where execution risk arises.
106.14 GCRI / GRF / GRA Role-Separation Understanding. Each director shall understand the role separation among GCRI US, GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), and the broader Nexus public-good stack.
A director shall understand that:
a) GCRI US is an evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, verifiable compute and intelligence methods, public authority learning, and safeguards institution;
b) GCRI Canada is a separate Canadian public-benefit anchor and not a legal extension of GCRI US;
c) The Global Risks Forum (GRF) is the public-good registry, recognition, maturity-records, standing, claims-discipline, stakeholder-formation, public-safe reporting, and public-facing legitimacy steward;
d) The Global Risks Alliance (GRA) is the finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, capital-reader-room, and regulated-perimeter discipline steward;
e) Nexus Standards, protocol authorities, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, providers, sponsors, hosts, and enterprise actors each have distinct roles where constituted; and
f) technical support, shared mission, shared ontology, shared records, shared public-good instruments, or interoperable systems do not create shared authority, merger, agency, recognition authority, finance-readiness authority, certification authority, procurement authority, public authority status, or execution authority.
A director shall be capable of preventing evidence inputs from becoming recognition determinations, technical inputs from becoming finance-readiness determinations, technical baselines from becoming certification or procurement approvals, and Nexus-compatible language from becoming unsupported authority.
106.15 Public Authority Boundary Understanding. Each director shall understand the Corporation’s public authority boundary. The Corporation may support public authority learning, evidence literacy, technical literacy, public-safe reporting literacy, scenario learning, simulation, tabletop exercises, after-action learning, capacity classification, public authority rooms, regulator-listening participation, public finance reader participation, emergency-management learning participation, and public infrastructure operator participation, but shall not act as or substitute for a public authority.
A director shall understand that the Corporation shall not:
a) issue official public warnings;
b) command emergency response;
c) issue evacuation, dispatch, or safety instructions;
d) issue public health orders;
e) regulate, enforce, permit, inspect as authority, or approve compliance;
f) approve public procurement;
g) approve public finance, grants, budgets, appropriations, guarantees, tax credits, or sovereign obligations;
h) speak for a public authority without written authorization;
i) create public-private partnership status without lawful authority;
j) convert public authority participation into official adoption;
k) create public authority reliance through dashboards, maps, AI outputs, proof receipts, observability signals, digital twins, or public-safe reports; or
l) imply public authority endorsement through naming, attendance, minutes, reports, logos, quotes, or references.
A director shall support capacity classification, public authority reference review, public-safe limitation language, meeting records, correction, and public clarification where public authority confusion arises.
106.16 Finance, Securities, Insurance, Lending, Rating, Public Finance, Procurement, and Certification Boundary Understanding. Each director shall understand the Corporation’s finance, securities, insurance, lending, rating, public finance, procurement, certification, accreditation, and regulated-activity boundaries.
A director shall understand that the Corporation shall not conduct or imply:
a) securities offering, distribution, solicitation, underwriting, brokerage, dealer activity, finder activity, or capital placement;
b) investment advice, investment adviser activity, portfolio management, asset management, suitability determination, capital recommendation, or transaction recommendation;
c) banking, deposit-taking, payment intermediation, custody, clearing, settlement, escrow, or third-party fund control;
d) lending, credit origination, credit approval, credit brokerage, guarantee, revenue guarantee, or performance guarantee;
e) insurance placement, reinsurance placement, underwriting, pricing, binding, claims handling, risk-bearing intermediation, or insurance approval;
f) rating, credit opinion, investment grade opinion, resilience rating, insurability rating, bankability rating, or financeability determination;
g) public finance approval, tax credit approval, grant approval, budget allocation, appropriation, public guarantee, MDB / DFI approval, or sovereign finance approval;
h) procurement award, vendor selection, procurement approval, procurement preference, or public authority vendor recommendation;
i) certification, accreditation, legal compliance approval, standards conformance approval, safe harbor, or professional credential by default;
j) GRF recognition, maturity, standing, legitimacy, Docket approval, Grid standing, or claims-discipline determination; or
k) GRA finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, or capital-reader-room determination.
A director shall be able to identify regulated-perimeter risk in language, scores, dashboards, technical profiles, evidence packs, proof receipts, controlled rooms, public authority materials, capital-reader materials, sponsor materials, provider materials, and public-facing claims.
106.17 Data / AI / Cyber / Privacy Understanding. Each director shall understand, or agree to be trained in, the Corporation’s data / AI / cyber / privacy obligations and the governance significance of technical systems. Such understanding shall include recognition that data, AI, cyber, software, compute, observability, dashboard, digital twin, DePIN, DLT, blockchain, AI-RAN, O-RAN, sensor, geospatial, and repository systems can create material legal, public safety, civil rights, community, protected knowledge, public authority, finance-boundary, and reputational risk.
A director shall understand the need for controls relating to:
a) data classification;
b) lawful basis, consent, non-consent, restriction, and withdrawal where applicable;
c) data minimization;
d) privacy and confidentiality;
e) access control;
f) identity and credential management;
g) model registers;
h) inference records;
i) compute workload records;
j) dataset cards, model cards, system cards, benchmark cards, and evaluation records;
k) agentic AI controls;
l) human review of material automated outputs;
m) secure development;
n) repository security;
o) SBOM, signing, provenance, dependency, vulnerability, key, token, secret, and credential controls;
p) incident response;
q) disaster recovery and business continuity;
r) breach notification where required;
s) restrictions on unapproved AI tools; and
t) public-safe correction of technical outputs.
A director shall understand that no AI system, dashboard, digital twin, proof receipt, ledger entry, DePIN record, AI-RAN signal, O-RAN signal, sensor output, cyber telemetry, model output, or automated score shall be treated as final institutional authority without competent human review, record support, limitation, and correction pathway.
106.18 Research Integrity Understanding. Each director shall understand the Corporation’s research integrity obligations and the role of the Board in preserving truthful, lawful, ethical, reproducible where appropriate, peer-reviewable where appropriate, publicly bounded, and correctionable research.
Research integrity understanding shall include awareness of:
a) research design integrity;
b) research ethics;
c) human-subjects review where required;
d) community review where appropriate;
e) Tribal, Indigenous, local, territorial, health-sensitive, youth, vulnerable population, civil rights, accessibility, and protected knowledge review where applicable;
f) consent, non-consent, restriction, withdrawal, correction, and complaint pathways where applicable;
g) sponsor and funder disclosure;
h) conflict disclosure;
i) publication independence;
j) reproducibility and replication;
k) peer review and technical review;
l) AI-use disclosure where material;
m) data rights and privacy controls;
n) publication integrity; and
o) correction, supersession, withdrawal, retraction, takedown, and archive pathways.
A director shall understand that research outputs shall not be used as disguised commercial endorsements, provider preferences, public authority approvals, finance-readiness determinations, certification substitutes, procurement tools, recognition purchases, sponsor-controlled findings, or protected knowledge extraction mechanisms.
106.19 Civil Rights, Accessibility, Community Safeguards, Tribal and Indigenous Protocol, and Protected Knowledge Understanding. Each director shall understand the Corporation’s obligations concerning civil rights, accessibility, community safeguards, Tribal and Indigenous protocol respect, Indigenous data safeguards, local and territorial knowledge, and protected knowledge.
A director shall understand that the Corporation’s public-benefit mission cannot be discharged through technical excellence alone, and that technical, evidentiary, publication, observability, AI, cyber, public authority, sponsor, provider, or Nexus objectives must be bounded by safeguards where persons, communities, rights, or protected knowledge may be affected.
This understanding shall include awareness of:
a) non-discrimination;
b) accessibility;
c) inclusive participation;
d) vulnerable and remote community safeguards;
e) Tribal sovereignty respect;
f) Indigenous governance respect;
g) Indigenous data safeguards;
h) local and territorial knowledge protections;
i) cultural, environmental, sacred, sensitive, and community-protected knowledge protections;
j) consent, non-consent, attribution, restriction, withdrawal, and correction pathways where applicable;
k) public-safe mapping;
l) surveillance and re-identification risks;
m) AI training, model improvement, embedding, retrieval, or analytics risks involving protected materials;
n) grievance and remedy pathways;
o) protected participation, whistleblowing, dissent protection, and non-retaliation; and
p) do-no-harm review.
A director shall be willing to support hold, restriction, redaction, non-publication, re-scoping, public-safe limitation, community review, correction, withdrawal, takedown, or remedy where safeguards require it.
106.20 Competition, Sanctions, Export-Control, and Controlled Technology Awareness. Each director shall have awareness, or agree to receive training, concerning competition, antitrust, sanctions, export-control, controlled technology, and national security sensitivity issues relevant to the Corporation’s activities.
Such awareness shall include the need to prevent:
a) price, margin, cost, bid, wage, customer, supplier, market allocation, capacity, exclusion, boycott, procurement steering, or collusive strategy discussion;
b) misuse of benchmarking, indices, datasets, labs, challenges, technical comparisons, standards-support activity, controlled rooms, or public authority forums to exchange competitively sensitive information;
c) sponsor or provider influence over competition-relevant outputs;
d) unlawful coordination among providers, vendors, operators, investors, insurers, lenders, underwriters, banks, public finance actors, national companies, Project SPVs, or enterprise actors;
e) sanctions violations;
f) dealings with restricted parties;
g) export-control violations;
h) unauthorized release of controlled technology;
i) inappropriate cross-border transfer of sensitive data, software, models, technical baselines, cyber materials, telecom materials, AI-RAN or O-RAN materials, geospatial materials, satellite or Earth observation materials, sovereign compute materials, semiconductor materials, quantum-relevant materials, biosecurity materials, or dual-use materials; and
j) failure to escalate national security sensitivity or controlled-technology concerns.
A director shall respect clean-team, clean-room, aggregation, de-identification, delay, independent administration, stop-meeting, hold, quarantine, and counsel-review controls where required.
106.21 Willingness to Follow Validity-by-Record and Correctionability. Each director shall be willing to follow validity-by-record and correctionability as core governance disciplines. A director shall understand that institutional validity arises from lawful authority, competent approval, accurate records, proper versioning, controlled vocabulary, limitation language, repository discipline, public-safe notice where required, and correction pathways, not from seniority, informal consensus, technical centrality, public repetition, sponsor support, public authority attendance, AI output, dashboard display, proof receipt, ledger entry, or Nexus reference alone.
A director shall be willing to require records for:
a) Board approvals;
b) officer delegations;
c) committee charters;
d) conflicts and recusals;
e) public authority capacities;
f) finance-boundary reviews;
g) certification-boundary reviews;
h) procurement-neutrality reviews;
i) provider-neutrality and sponsor non-control reviews;
j) data access;
k) AI use;
l) cyber controls;
m) research ethics;
n) community safeguards;
o) protected knowledge;
p) evidence methods;
q) technical baselines;
r) software releases;
s) public-safe publications; and
t) corrections.
A director shall be willing to support correction where a record is defective, absent, misleading, stale, superseded, overclaimed, unauthorized, incomplete, or inconsistent with law, this Bylaw, public-benefit purpose, non-execution, role separation, safeguards, or public-safe communication.
No person shall be qualified to serve as a director if the person rejects correction, treats record discipline as optional, insists that informal authority is sufficient, or uses reputation, urgency, sponsor pressure, provider pressure, public authority interest, technical excitement, or fundraising need to bypass required records.
106.22 Director Qualification Records. The Corporation shall maintain Director Qualification Records sufficient to demonstrate that each director has been reviewed, qualified, appointed, trained, monitored, renewed, restricted, corrected, or removed in accordance with applicable law, the Articles or Certificate, this Bylaw, Board resolutions, policies, and fiduciary standards.
Director Qualification Records shall include, as applicable:
a) legal eligibility records, consent-to-serve records, appointment or election records, member approval records where required, incorporator records where applicable, Board resolution records, director register entries, and effective-date records;
b) fit-and-proper review records, integrity review records, fiduciary capacity records, time-commitment capacity records, confidentiality capacity records, conflict disclosure capacity records, independence capacity records, and good-standing records;
c) public-benefit purpose understanding records, United States nonprofit governance understanding records, tax-exempt or tax-exempt-compatible understanding records, non-execution understanding records, GCRI / GRF / GRA role-separation understanding records, public authority boundary understanding records, finance, securities, insurance, lending, rating, public finance, procurement, and certification boundary understanding records;
d) data / AI / cyber / privacy understanding records, research integrity understanding records, civil rights, accessibility, community safeguards, Tribal and Indigenous protocol, protected knowledge understanding records, competition awareness records, sanctions awareness records, export-control awareness records, controlled-technology awareness records, and national security sensitivity awareness records;
e) training records, certifications of understanding, annual attestations, event-based attestations, policy acknowledgments, confidentiality acknowledgments, AI-use acknowledgments, controlled-room acknowledgments, public authority boundary acknowledgments, finance-boundary acknowledgments, safeguards acknowledgments, non-retaliation acknowledgments, and correctionability acknowledgments;
f) conflict disclosures, related-party disclosures, dual-role disclosures, sponsor relationship disclosures, provider relationship disclosures, donor and funder relationship disclosures, host relationship disclosures, public authority capacity disclosures, investor, insurer, lender, underwriter, bank, public finance actor, national company, Project SPV, university, laboratory, contractor, vendor, employer, affiliate, GCRI Canada, GRF, GRA, Nexus entity, and consortium relationship disclosures;
g) sanctions screening records, export-control screening records, restricted-party screening records, controlled-technology screening records, data access screening records, cyber access screening records, repository access screening records, public authority interface screening records, finance-boundary screening records, safeguards screening records, and protected knowledge screening records;
h) independence determinations, recusal determinations, access restrictions, committee restrictions, voting restrictions where lawful, mitigation plans, corrective training, probation records, non-renewal records, resignation records, removal records, and post-service access revocation records;
i) records of any qualification concern, eligibility challenge, integrity concern, conflict concern, confidentiality concern, public authority boundary concern, finance-boundary concern, certification-boundary concern, procurement-neutrality concern, provider-neutrality concern, sponsor non-control concern, data / AI / cyber concern, research integrity concern, safeguards concern, or correctionability concern, together with the review, decision, mitigation, and outcome; and
j) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that director qualification is an active fiduciary safeguard, not a ceremonial onboarding step. A director must be legally eligible, willing to serve, fit and proper, independent enough to govern, capable of fiduciary judgment, able to protect confidential and controlled materials, able to disclose conflicts, competent or trainable in the Corporation’s public-benefit and nonprofit obligations, and willing to preserve non-execution, role separation, public authority boundaries, finance boundaries, data / AI / cyber controls, safeguards, validity-by-record, and correctionability. Director qualification shall be lawful, recorded, reviewed, updated, bounded, enforceable, and correctionable.
Section 108. Director Independence, Anti-Capture, Dual Roles, and Affiliation Review
108.1 Independence Purpose. Director independence is a structural safeguard of the Corporation’s fiduciary integrity, public-benefit purpose, nonprofit character, non-distribution rule, tax-exempt or tax-exempt-compatible posture, non-execution perimeter, public authority boundary, finance boundary, certification boundary, procurement neutrality, provider neutrality, sponsor non-control, evidence integrity, research integrity, data / AI / cyber governance, community safeguards, protected knowledge discipline, validity-by-record, correctionability, and Nexus role separation.
Independence shall be understood as the practical, legal, ethical, financial, institutional, technical, and reputational capacity of a director to exercise loyal, careful, informed, good-faith, mission-obedient, public-benefit judgment on behalf of GCRI US as a separate legal entity, without domination, improper influence, divided loyalty, external control, undisclosed allegiance, capture, or role confusion.
Director independence is required to ensure that:
a) the Board governs GCRI US and does not become a representative assembly of sponsors, donors, funders, providers, hosts, public authorities, investors, insurers, lenders, underwriters, banks, public finance actors, national companies, Project SPVs, universities, laboratories, political actors, founders, communities, or Nexus entities;
b) evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, public authority learning, and safeguards remain governed for public-benefit purposes and not for private, institutional, commercial, political, public authority, financial, certification, procurement, recognition, or enterprise-stack advantage;
c) Board decisions remain fiduciary acts of the Corporation and are not converted into sponsor instructions, provider preferences, public authority directives, investor expectations, donor conditions, founder preferences, technical contributor preferences, public campaign positions, or Nexus-system decisions;
d) GCRI US remains separate from 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, providers, sponsors, hosts, public authorities, and enterprise actors; and
e) the Board can approve, refuse, hold, quarantine, re-scope, correct, withdraw, retract, takedown, archive, externalize, refer, or terminate matters where required, even where doing so is inconvenient to external relationships, funding, reputation, technical momentum, public authority interest, sponsor preference, provider preference, or Nexus ecosystem expectations.
Independence shall not require that every director be unaffiliated with all external institutions. It shall require that each affiliation be disclosed, reviewed, classified, managed, bounded, recorded, and made subordinate to the director’s fiduciary duty to the Corporation.
108.2 Independence From Sponsors. A director shall be independent from sponsors in the sense that no sponsor may appoint, remove, direct, control, instruct, reward, punish, veto, condition, purchase, or materially influence the director’s fiduciary judgment, Board vote, committee service, access to information, public statements, or treatment of evidence, methods, publications, technical assets, controlled rooms, public authority learning, GRF-facing inputs, GRA-facing inputs, Nexus interfaces, or correction matters.
Sponsor-related independence concerns include, without limitation:
a) employment, consulting, advisory, board, officer, investor, contractor, vendor, research, grant, donation, sponsorship, in-kind, technical-support, equipment-support, compute-support, facility-support, data-support, or public-relations relationship with a sponsor;
b) compensation, benefits, travel support, honoraria, equity, token interest, research support, lab support, fellowship support, staff secondment, hosted office support, equipment support, cloud support, compute credit, AI system access, telecom access, AI-RAN or O-RAN infrastructure access, DePIN access, DLT infrastructure access, sensor access, dashboard support, cybersecurity support, or other material support from a sponsor;
c) sponsor expectation of preferred access to Board materials, Board members, public authority rooms, controlled rooms, evidence rooms, data rooms, clean rooms, no-download rooms, public-safe reports, technical baselines, datasets, software, repositories, proof receipts, or Nexus interface outputs;
d) sponsor request for publication review, outcome control, finding suppression, public authority access, recognition influence, finance-readiness influence, certification influence, procurement influence, provider preference, or public-facing legitimacy;
e) sponsor use of the director’s role in marketing, investor materials, public authority materials, procurement materials, grant applications, public communications, or reputation signaling; and
f) sponsor concentration or dependency that could reasonably cause a director to hesitate before challenging sponsor conduct, rejecting sponsor requests, correcting sponsor-influenced outputs, or terminating sponsor-supported activity.
A director may have sponsor relationships only where the relationships are disclosed, reviewed, not disqualifying, and subject to recusal, access restriction, committee restriction, voting restriction where lawful, public-claim controls, and anti-capture controls. A sponsor relationship shall be disqualifying where it prevents faithful service to the Corporation or creates unacceptable public-benefit, independence, public authority, finance-boundary, provider-neutrality, certification-boundary, procurement-neutrality, or sponsor non-control risk.
108.3 Independence From Donors and Funders. A director shall be independent from donors and funders in the sense that no donor or funder may control, direct, purchase, condition, or distort Board judgment, mission priorities, research findings, evidence classifications, publication outcomes, technical baselines, public authority learning materials, controlled-room access, staff appointments, officer appointments, committee appointments, GRF-facing inputs, GRA-facing inputs, Nexus interface positions, corrections, or public claims.
Donor and funder independence concerns include, without limitation:
a) donor or funder conditions that seek to determine research conclusions, evidence status, methods outcomes, public-safe publication content, technical asset release, controlled vocabulary, public authority references, public authority access, recognition, finance-readiness, certification, procurement meaning, provider preference, or sponsor benefits;
b) donor or funder expectations that Board membership creates governance rights, reserved powers, veto rights, nomination rights, information rights beyond approved classification, or public influence;
c) funding dependence that could impair willingness to correct, withdraw, re-scope, restrict, or terminate donor-supported work;
d) restricted fund terms that conflict with law, the Articles or Certificate, this Bylaw, public-benefit purposes, nonprofit character, tax-exempt or tax-exempt-compatible requirements, non-execution, role separation, public authority boundaries, finance boundaries, safeguards, or correctionability;
e) donor or funder participation that creates public perception of purchased legitimacy, public authority access, public-good influence, research outcome control, or Nexus status influence; and
f) donor or funder relationships with national companies, Project SPVs, providers, investors, insurers, lenders, underwriters, banks, public finance actors, public authorities, political actors, or enterprise-stack actors materially affected by Board decisions.
A director with donor or funder relationships shall disclose those relationships before appointment and on an event-based and annual basis. Where a donor or funder matter comes before the Board, the director shall recuse, abstain, be restricted from materials, or be subject to other lawful mitigation where required. No director shall allow donor or funder loyalty to prevail over fiduciary loyalty to the Corporation.
108.4 Independence From Providers, Vendors, Contractors, and Hosts. A director shall be independent from providers, vendors, contractors, consultants, integrators, operators, cloud providers, AI providers, cybersecurity providers, telecom providers, AI-RAN providers, O-RAN providers, DePIN providers, DLT or blockchain providers, sensor providers, dashboard providers, data providers, software providers, host institutions, host sites, and other enterprise or operational counterparties.
Provider, vendor, contractor, and host independence concerns include, without limitation:
a) current or recent employment, ownership, compensation, board service, advisory role, consulting role, reseller role, channel role, integration role, commission, referral fee, success fee, finder fee, equity, token interest, revenue share, IP interest, licensing interest, or other financial interest;
b) involvement in proposals, bids, procurements, public authority projects, hosted pilots, controlled-room demonstrations, technical baselines, reference implementations, proof receipts, dashboards, datasets, software, model systems, observability systems, digital twins, AI-RAN / O-RAN systems, DePIN systems, DLT systems, cybersecurity systems, or infrastructure deployments that may be affected by GCRI US outputs;
c) attempt to convert public-good software, open technical baselines, methods, evidence packs, public-safe reports, controlled-room participation, public authority learning, or Nexus-compatible language into provider preference, procurement advantage, certification, recognition, finance-readiness, or market endorsement;
d) host expectation that hosting a program, room, lab, event, observability activity, public authority learning session, or Nexus Universe activity gives governance influence or public authority meaning;
e) contractor or vendor dependence that impairs objective review of performance, renewal, procurement, data security, cyber security, IP rights, publication integrity, or correction requirements; and
f) provider or host participation that creates public confusion regarding operational control, asset ownership, public authority delegation, emergency command, public warning, procurement selection, or enterprise execution.
A director with provider, vendor, contractor, or host relationships shall not participate in selection, evaluation, procurement, contract approval, performance review, renewal, termination, publication, public reference, certification-adjacent, procurement-adjacent, finance-adjacent, or public authority-facing decisions involving such provider, vendor, contractor, or host except where lawful, fully disclosed, independently reviewed, and expressly permitted after mitigation.
108.5 Independence From National Companies, State Operating Companies, Regional Companies, and Project SPVs. A director shall be independent from any national consortium company, national company, state operating company, territorial operating company, regional company, sectoral company, project company, Project SPV, special-purpose vehicle, deployment vehicle, infrastructure vehicle, delivery company, asset owner, operator, integrator, or enterprise-stack execution vehicle that may interact with, rely on, cite, use, benefit from, or be affected by GCRI US evidence, methods, technical baselines, public-good software, public authority learning, GRF-facing inputs, GRA-facing inputs, Nexus Docket support, Nexus Grid support, or Nexus-compatible materials.
Independence from such vehicles is required because GCRI US shall not become, control, manage, finance, certify, procure for, guarantee, rate, endorse, operate, own, or execute through national companies, state operating companies, regional companies, or Project SPVs by Board overlap, shared personnel, technical centrality, shared records, shared public mission, sponsor pressure, provider pressure, or Nexus relationship.
A director shall disclose any relationship with such vehicles, including:
a) founder, promoter, shareholder, member, partner, director, officer, manager, employee, consultant, advisor, sponsor, funder, lender, insurer, underwriter, bank, public finance actor, contractor, vendor, provider, host, or investor relationship;
b) economic interest, equity interest, token interest, warrant, option, debt interest, revenue share, success fee, carried interest, management fee, advisory fee, referral fee, or other benefit;
c) intellectual property, software, data, model, benchmark, repository, technical baseline, dataset, dashboard, sensor, AI-RAN, O-RAN, DePIN, DLT, blockchain, geospatial, digital twin, cyber, or observability interest;
d) public authority relationship, procurement relationship, public finance relationship, grant relationship, concession relationship, PPP relationship, infrastructure relationship, insurance relationship, or guarantee relationship;
e) use of GCRI US materials for capital-readability, insurance-readiness, bankability, public finance, procurement, certification, recognition, or market positioning; and
f) any role that could create confusion between public-good stewardship and enterprise execution.
Where such relationships exist, the Board shall determine whether recusal, access restriction, committee restriction, voting restriction where lawful, public-claim limitation, resignation, non-appointment, non-renewal, or removal is required.
108.6 Independence From Investors, Insurers, Lenders, Underwriters, Banks, Public Finance Actors, and Capital Readers. A director shall be independent from investors, insurers, reinsurers, lenders, underwriters, banks, public finance actors, capital readers, asset managers, funds, advisors, brokers, dealers, finders, rating actors, credit actors, guarantee actors, development finance actors, multilateral finance actors, sovereign finance actors, public finance authorities, and other finance-adjacent persons where such relationships could impair fiduciary judgment or create regulated-perimeter risk.
Independence from capital actors is required to preserve the Corporation’s bright-line boundary against securities offerings, investment advice, brokerage, finder activity, underwriting, banking, lending, insurance placement, rating, public finance approval, capital placement, suitability determinations, investment recommendations, bankability determinations, financeability determinations, insurance-readiness determinations, and GRA finance-readiness functions.
A director shall disclose any capital-related relationship involving:
a) investment, lending, insurance, underwriting, banking, credit, rating, public finance, guarantee, project finance, infrastructure finance, climate finance, resilience finance, blended finance, DFI / MDB finance, sovereign finance, philanthropic finance, or concessionary finance interests;
b) capital-reader rooms, proof packs, finance-readiness materials, insurance-readiness materials, diligence translations, RNFD, NFD, UNFSD, GRA-facing inputs, GRF-facing maturity records, Docket-support records, Grid-support records, or Nexus-compatible materials;
c) investment committee, credit committee, underwriting committee, insurance committee, grant committee, public finance committee, procurement committee, rating committee, or diligence committee roles;
d) compensation or benefit tied to financing outcomes, project closing, insurance placement, public finance approval, grant approval, procurement award, credit approval, guarantee approval, investment approval, or capital deployment;
e) relationship with a sponsor, provider, national company, Project SPV, or public authority seeking capital treatment influenced by GCRI US materials; and
f) any use or proposed use of GCRI US outputs in capital-facing materials.
A director shall not participate in any Board decision that could reasonably be viewed as assisting, validating, recommending, arranging, approving, or influencing financing, insurance, lending, underwriting, rating, public finance, procurement, certification, recognition, or investment decision-making for an actor with whom the director has a material relationship.
108.7 Independence From Public Authorities Where Required for Board Judgment. Public authority experience, public service, regulatory familiarity, emergency-management expertise, infrastructure knowledge, public finance literacy, or governmental participation may benefit the Corporation, but a director shall remain independent from public authorities where required for fiduciary judgment and public authority boundary discipline.
A director who is, was, or is expected to become an official, employee, contractor, advisor, appointee, regulator, public finance reader, emergency-management participant, public infrastructure operator participant, public authority representative, elected official, campaign official, public board member, or public authority consultant shall disclose such status and any legal, ethics, confidentiality, procurement, lobbying, public records, open meetings, grant, public finance, emergency management, public safety, public health, cyber, infrastructure, or conflict restrictions.
Public authority independence concerns include, without limitation:
a) risk that the director will treat the Corporation as an extension of a public authority;
b) risk that public authority participation will be represented as official adoption, endorsement, procurement approval, funding approval, public finance approval, regulation, inspection, public warning, emergency command, sovereign obligation, or public-private partnership status;
c) risk that public authority information, records, confidential materials, official statements, logos, seals, data, public records, public safety information, cyber-sensitive information, infrastructure-sensitive information, or restricted government materials will be mishandled;
d) risk that the director’s public role imposes disclosure, ethics, procurement, lobbying, gifts, sunshine, public records, open-meetings, or conflict rules inconsistent with Board confidentiality or fiduciary service;
e) risk that the director will prefer public authority convenience over public-benefit purpose, safeguards, data restrictions, protected knowledge, or correctionability; and
f) risk that public authority relationships will suppress dissent, criticism, correction, or public-safe limitation.
A director may serve while affiliated with a public authority only where lawful, disclosed, capacity-classified, ethically reviewed, confidentiality-compatible, and bounded. Public authority affiliation shall not create public authority delegation to GCRI US or GCRI US authority to speak for the public authority.
108.8 Independence From Political, Partisan, Campaign, Lobbying, or Government Ethics Conflicts Where Applicable. A director shall be independent from political, partisan, campaign, lobbying, government ethics, gift, public procurement, public grant, public finance, and public authority influence conflicts where such conflicts could impair fiduciary judgment, nonprofit compliance, public-benefit purpose, tax-exempt or tax-exempt-compatible posture, public trust, public authority boundary discipline, or the Corporation’s all-states-and-territories and North America role.
Political and government ethics concerns include, without limitation:
a) campaign roles, elected roles, appointed roles, party roles, lobbying roles, political consulting roles, advocacy roles, public procurement roles, public finance roles, grantmaking roles, or regulatory roles that may be affected by Corporation activities;
b) use of the Corporation’s name, Board role, reports, technical baselines, public-good software, dashboards, public authority rooms, public-safe publications, Nexus references, GRF-facing inputs, or GRA-facing inputs to support partisan, campaign, electoral, lobbying, procurement, funding, or public policy outcomes beyond lawful and approved public-benefit activity;
c) gifts, hospitality, travel, sponsorships, donations, in-kind support, meeting access, speaking roles, public authority access, or public-facing platforms that create government ethics concern;
d) public authority, campaign, or lobbying duties that conflict with Board confidentiality, conflict rules, public-safe limitation, or correction obligations;
e) public representations that imply government endorsement, public authority adoption, public-private partnership status, procurement preference, funding approval, public finance approval, regulatory safe harbor, or sovereign obligation; and
f) any circumstance that could cause the Corporation to be viewed as a partisan instrument, lobbying vehicle, procurement influence vehicle, or public authority proxy contrary to its mission and legal status.
The Board may require recusal, access restriction, public statement restriction, lobbying-law review, government ethics review, counsel review, or non-service where political, partisan, campaign, lobbying, or government ethics conflicts cannot be safely managed.
108.9 Independence From Research Outcome Purchasers. No director shall be dependent on, beholden to, controlled by, or materially influenced by any person seeking to purchase, predetermine, suppress, distort, accelerate, delay, frame, brand, quote, use, or publicize research outcomes, evidence classifications, confidence determinations, uncertainty statements, observability outputs, technical truth findings, benchmark results, model evaluations, public-safe reports, or correction decisions.
Research outcome purchase risk includes, without limitation:
a) sponsor or funder rights to approve findings, veto publications, shape conclusions, suppress unfavorable results, delay correction, or control public release;
b) provider, vendor, host, investor, insurer, lender, public finance actor, public authority, national company, Project SPV, or enterprise actor efforts to influence methods, metrics, evidence classes, benchmark design, model evaluation, public-safe language, technical baseline content, or comparison outputs;
c) compensation, support, funding, authorship, speaking, consulting, advisory, grant, employment, licensing, equity, token, or commercial benefit linked to desired findings;
d) publication plans that support provider preference, procurement advantage, certification, recognition, finance-readiness, capital-readability, insurance-readiness, bankability, public finance approval, public authority adoption, or public legitimacy;
e) use of research to extract protected knowledge, normalize public authority reliance, or create public-facing status beyond recorded authority; and
f) resistance to independent review, peer review, red-team review, model review, evidence challenge, correction, withdrawal, retraction, takedown, or archive.
A director shall not participate in research governance where the director has a material relationship with a research outcome purchaser unless the Board determines that the conflict can be managed and the director is appropriately recused, restricted, or otherwise bounded.
108.10 Independence From Standards Outcome Purchasers. No director shall be dependent on, beholden to, controlled by, or materially influenced by any person seeking to purchase, predetermine, steer, capture, suppress, distort, or commercialize standards-support outcomes, open technical baselines, technical profiles, reference architectures, schemas, APIs, SDKs, benchmarks, test harnesses, gold vectors, negative tests, evaluation sets, public-good software, repository rules, interoperability mappings, or Nexus-compatible claims.
Standards outcome purchase risk includes, without limitation:
a) provider effort to shape a technical baseline around proprietary products, services, data formats, cloud services, AI systems, telecom systems, AI-RAN components, O-RAN components, DePIN components, DLT systems, blockchain systems, digital twin systems, cyber tools, sensors, dashboards, or integration services;
b) sponsor effort to secure branded influence, preferred terminology, public-facing legitimacy, compatibility claims, provider preference, procurement advantage, certification-adjacent status, or standards-adjacent status;
c) investor, insurer, lender, underwriter, bank, public finance actor, national company, Project SPV, or enterprise actor effort to use technical profiles as finance-readiness, insurance-readiness, bankability, rating, public finance, procurement, certification, or market positioning tools;
d) public authority effort to treat standards-support materials as public procurement requirements, regulatory safe harbors, official guidance, public warnings, or public authority decisions without lawful adoption;
e) technical contributor effort to embed hidden governance, private control, license lock-in, proprietary dependency, anti-competitive preference, data enclosure, AI model lock-in, cloud lock-in, compute lock-in, or protocol capture; and
f) refusal to maintain open, public-good, anti-enclosure, versioned, auditable, correctionable, and public-safe technical asset discipline.
A director with material ties to a standards outcome purchaser shall be subject to enhanced disclosure, conflict review, recusal, access restriction, committee restriction, vote restriction where lawful, and public-claim controls.
108.11 Dual-Role Person Controls. A dual-role person is any director who also serves, has served, is expected to serve, or is materially affiliated with another body, entity, project, program, funder, sponsor, provider, host, public authority, consortium, national company, Project SPV, university, laboratory, community body, advisory body, standards body, protocol body, GRF body, GRA body, GCRI Canada body, Nexus body, or enterprise actor whose interests, authority, outputs, or activities may intersect with the Corporation.
Dual roles shall be permitted only where lawful, disclosed, reviewed, classified, recorded, and controlled. Dual-role controls may include, without limitation:
a) role mapping;
b) capacity classification;
c) conflict disclosure;
d) independence review;
e) recusal rules;
f) access restrictions;
g) committee restrictions;
h) voting restrictions where lawful;
i) public statement restrictions;
j) separate email, system, repository, data-room, and controlled-room access rules;
k) confidentiality undertakings;
l) no-use undertakings for protected information;
m) no-authority notices;
n) compatibility notes;
o) divergence logs;
p) public-safe language requirements;
q) correction pathways; and
r) resignation, non-renewal, or removal where conflicts cannot be managed.
A dual-role person shall state the capacity in which the person is acting when participating in meetings, correspondence, public statements, controlled rooms, public authority rooms, GRF-facing matters, GRA-facing matters, Nexus interface matters, technical asset matters, or public-safe publications. Silence shall not be used to create apparent authority.
108.12 GCRI Canada Dual-Role Controls. A director who also holds, has held, or is expected to hold a director, officer, employee, contractor, advisor, fellow, contributor, committee, council, working group, public authority interface, technical, repository, or other role with GCRI Canada shall be subject to specific dual-role controls.
GCRI Canada dual-role controls shall preserve:
a) separate legal personality of GCRI US;
b) separate legal personality of GCRI Canada;
c) distinct United States and Canadian governance records;
d) distinct Board fiduciary duties;
e) distinct tax, nonprofit, charitable, solicitation, employment, privacy, data, AI, cyber, research, public authority, sanctions, export-control, protected knowledge, and local-law obligations;
f) North America coordination without merger;
g) shared mission without legal fusion;
h) shared doctrine without shared liability;
i) shared ontology without shared treasury;
j) shared methods without agency;
k) shared records without automatic mutual authority;
l) shared technical baselines without certification or procurement meaning;
m) cross-border data and controlled-technology discipline; and
n) public description discipline.
A director acting for GCRI US shall not bind GCRI Canada unless separately authorized by GCRI Canada through competent records. A director acting for GCRI Canada shall not bind GCRI US unless separately authorized by GCRI US through competent records. Compatibility notes, divergence logs, cooperation instruments, and public-safe language shall be used where cross-border meaning could otherwise become ambiguous.
108.13 GRF Dual-Role Controls. A director who also holds, has held, or is expected to hold a role with The Global Risks Forum (GRF) shall be subject to controls preserving the distinction between GCRI US evidence / methods functions and GRF registry, recognition, maturity-records, standing, claims-discipline, stakeholder-formation, public-safe reporting, and public-facing legitimacy functions.
GRF dual-role controls shall ensure that:
a) GCRI US evidence support does not become GRF recognition;
b) GCRI US methods support does not become GRF maturity standing;
c) GCRI US technical baselines do not become GRF public legitimacy determinations;
d) GCRI US correction signals do not become GRF final public-facing determinations except through GRF’s competent process;
e) GRF records do not create GCRI US governance authority unless lawfully adopted by GCRI US;
f) GRF recognition, standing, maturity, Docket, Grid, or claims-discipline language is not used by a GCRI US director without competent record;
g) public communications do not imply that GCRI US recognizes, certifies, ranks, approves, or legitimizes persons, projects, providers, technologies, public authorities, national companies, Project SPVs, or enterprise actors; and
h) conflicts between GCRI US records and GRF records are escalated, recorded, corrected, reconciled, or bounded through compatibility notes and divergence logs.
A director with a GRF role shall recuse from GCRI US matters where the director’s GRF responsibilities materially affect the director’s independence or create recognition, maturity, standing, public-facing legitimacy, or claims-discipline confusion.
108.14 GRA Dual-Role Controls. A director who also holds, has held, or is expected to hold a role with The Global Risks Alliance (GRA) shall be subject to controls preserving the distinction between GCRI US technical evidence / methods functions and GRA finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, capital-reader-room, and regulated-perimeter discipline functions.
GRA dual-role controls shall ensure that:
a) GCRI US evidence inputs do not become GRA finance-readiness determinations;
b) GCRI US technical baselines do not become capital-readability approvals;
c) GCRI US proof receipts, records, datasets, dashboards, software, technical profiles, or public-safe reports do not become investment advice, insurance advice, lending advice, underwriting basis, rating, public finance approval, bankability determination, or transaction recommendation;
d) GRA capital-reader rooms do not become GCRI US Board functions;
e) GRA proof packs do not create GCRI US certification or recognition authority;
f) finance-adjacent language is reviewed under regulated-perimeter controls;
g) director communications do not imply that GCRI US endorses, arranges, recommends, approves, rates, finances, insures, underwrites, lends to, brokers, finds, or places capital for any person, project, provider, national company, Project SPV, public authority, or enterprise actor; and
h) GRA-facing technical inputs are recorded with limitations, non-reliance language, and correction pathways.
A director with a GRA role shall recuse from GCRI US matters where the director’s GRA responsibilities create material finance-boundary, regulated-perimeter, capital-reader, insurance, lending, public finance, rating, or investment-advice risk.
108.15 Nexus Entity Dual-Role Controls. A director who also holds, has held, or is expected to hold a role with Nexus Network, Nexus Standards, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, a Global Nexus Consortium, Regional Nexus Consortium, National Nexus Consortium, National Working Group, National Consortium Company, state or regional operating company, Project SPV, protocol authority, standards body, public-good stack body, enterprise-stack body, or other Nexus-compatible entity shall be subject to Nexus dual-role controls.
Nexus dual-role controls shall preserve:
a) one-rail / two-stacks discipline;
b) public-good stack and enterprise stack separation;
c) GCRI / GRF / GRA role separation;
d) evidence, recognition, and finance-readiness separation;
e) standards-support without standards-authority overclaim;
f) observability support without public warning or emergency command;
g) public authority learning without public authority delegation;
h) Docket and Grid support without approval, rating, recognition, procurement, certification, or finance-readiness meaning;
i) public-good software and technical baseline stewardship without provider preference or procurement mandate;
j) protocol support without protocol authority unless separately and lawfully designated;
k) Nexus-compatible language without unsupported legal, public authority, finance, certification, procurement, recognition, or enterprise meaning; and
l) compatibility notes, divergence logs, and correction paths.
No director shall use a Nexus title, role key, proof receipt, ledger entry, smart license, technical profile, public-good asset, committee role, council role, consortium role, national company role, Project SPV role, or public authority interface role to create apparent Board authority, public authority meaning, finance-readiness meaning, certification meaning, procurement meaning, recognition meaning, or execution authority.
108.16 University, Laboratory, Public Authority, Sponsor, Provider, Host, Funder, or Enterprise Dual-Role Controls. A director affiliated with a university, laboratory, research institute, public authority, sponsor, donor, funder, provider, host, contractor, vendor, investor, insurer, lender, underwriter, bank, public finance actor, national company, Project SPV, community organization, Tribal or Indigenous body, media organization, civil society body, or enterprise actor shall be subject to dual-role controls tailored to the affiliation.
Such controls shall address, as applicable:
a) whether the director acts in an individual fiduciary capacity or representative capacity;
b) whether the director has authority to bind the affiliated institution;
c) whether the affiliated institution has authority to bind GCRI US;
d) whether confidentiality obligations are compatible;
e) whether public records, public meetings, open science, institutional review, academic publication, sponsor reporting, public authority reporting, employment, government ethics, procurement, lobbying, grant, or conflict rules apply;
f) whether the director has access to competitively sensitive, public authority, cyber-sensitive, infrastructure-sensitive, finance-sensitive, personal, health-sensitive, community-protected, Tribal / Indigenous, local, territorial, cultural, environmental, or protected knowledge materials;
g) whether the affiliated institution seeks benefits from GCRI US outputs;
h) whether the affiliation creates recurring recusal burdens;
i) whether public descriptions could imply endorsement, adoption, funding, procurement, certification, recognition, finance-readiness, or provider preference; and
j) whether safeguards, corrections, public-safe notices, compatibility notes, or divergence logs are required.
A dual-role affiliation shall not be disqualifying solely because it exists. It shall become disqualifying where it cannot be managed without materially impairing fiduciary judgment, confidentiality, Board effectiveness, public-benefit purpose, safeguards, public trust, or boundary discipline.
108.17 Annual Independence Review. The Corporation shall conduct an annual independence review for each director. The review shall be designed to determine whether the director remains eligible, fit, independent, conflict-manageable, confidentiality-capable, participation-capable, and able to serve in accordance with law, the Articles or Certificate, this Bylaw, Board resolutions, policies, fiduciary duties, public-benefit purpose, and Nexus role separation.
The annual independence review shall include, as applicable:
a) updated conflict disclosure;
b) related-party disclosure;
c) sponsor, donor, funder, provider, host, contractor, vendor, public authority, investor, insurer, lender, underwriter, bank, public finance actor, national company, Project SPV, GCRI Canada, GRF, GRA, Nexus entity, university, laboratory, community, Tribal / Indigenous, civil society, media, political, and enterprise affiliation disclosure;
d) employment, consulting, advisory, board, officer, fiduciary, ownership, compensation, equity, token, IP, data, software, model, repository, technical asset, research, publication, grant, sponsorship, and funding disclosure;
e) independence certification;
f) confidentiality certification;
g) public authority boundary certification;
h) finance-boundary certification;
i) certification-boundary, procurement-neutrality, recognition-boundary, provider-neutrality, and sponsor non-control certification;
j) data / AI / cyber / privacy certification;
k) safeguards and protected knowledge certification;
l) competition, sanctions, export-control, controlled technology, and national security sensitivity certification;
m) attendance and participation review;
n) training completion review;
o) recusal pattern review;
p) access restriction review;
q) committee assignment review; and
r) corrective action, restriction, renewal, non-renewal, or removal recommendation where appropriate.
The annual independence review shall be recorded and shall inform director renewal, committee assignments, access rights, recusals, succession planning, Board composition, training, and corrective action.
108.18 Event-Based Independence Review. In addition to annual review, the Corporation shall conduct an event-based independence review whenever a new circumstance arises that may materially affect director independence, eligibility, conflicts, confidentiality, access, fiduciary judgment, public trust, boundary discipline, or Board effectiveness.
Event-based review shall be triggered, without limitation, by:
a) new employment, consulting, advisory, board, officer, fiduciary, contractor, vendor, sponsor, donor, funder, provider, host, public authority, investor, insurer, lender, underwriter, bank, public finance, national company, Project SPV, GCRI Canada, GRF, GRA, Nexus entity, university, laboratory, political, media, civil society, community, Tribal / Indigenous, or enterprise role;
b) new compensation, grant, donation, sponsorship, in-kind support, equity, token, IP, licensing, data, model, software, repository, technical asset, research, publication, or public authority relationship;
c) new matter before the Board involving a director’s affiliate or related party;
d) proposed major contract, grant, donation, sponsorship, public authority interface, controlled-room admission, data-sharing arrangement, software release, technical baseline, public-safe publication, GRF-facing input, GRA-facing input, Docket support, Grid support, Nexus interface, national company matter, Project SPV matter, provider matter, host matter, or sponsor matter involving a director’s interest;
e) public claim, media statement, marketing use, investor use, public authority use, bid use, grant use, or Nexus-compatible claim involving a director’s name or role;
f) data incident, AI incident, cyber incident, protected knowledge concern, research integrity concern, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider preference, sponsor control, or public-safe publication concern involving the director or affiliate;
g) change in law, regulation, tax status, public authority restriction, sanctions status, export-control status, controlled-technology status, government ethics rule, or public records obligation affecting service; or
h) any circumstance identified by the director, Chair, Board, committee, officer, counsel, compliance function, safeguards function, secretary, or other authorized person as potentially material.
A director subject to event-based review shall promptly disclose the circumstance and shall not participate in affected matters until the review is complete unless the Board determines that participation is lawful, necessary, and appropriately bounded.
108.19 Recusal, Access Restriction, Committee Restriction, Voting Restriction, or Removal Where Required. Where a director’s independence is impaired or reasonably questioned, the Corporation may impose recusal, access restriction, committee restriction, deliberation restriction, recommendation restriction, voting restriction where lawful, public statement restriction, controlled-room restriction, data-room restriction, repository restriction, information barrier, confidentiality undertaking, corrective training, probation, resignation request, non-renewal, or removal where required.
Recusal or restriction may apply to:
a) Board deliberations;
b) Board votes;
c) committee service;
d) executive sessions;
e) controlled-room materials;
f) public authority room materials;
g) finance-adjacent materials;
h) certification-adjacent materials;
i) procurement-adjacent materials;
j) recognition-adjacent materials;
k) sponsor or provider matters;
l) donor or funder matters;
m) host matters;
n) public authority matters;
o) GRF-facing or GRA-facing matters;
p) Nexus interface matters;
q) data, AI, cyber, repository, model, software, technical asset, and observability matters;
r) protected knowledge, Tribal / Indigenous, community, civil rights, accessibility, grievance, remedy, non-retaliation, and safeguards matters; and
s) investigation, enforcement, correction, withdrawal, retraction, takedown, or public clarification matters.
The scope of restriction shall be no broader than necessary where a narrower lawful control is sufficient, but shall be broad enough to protect the Corporation. Where the independence issue is structural, recurring, unmanageable, undisclosed, concealed, or incompatible with fiduciary duty, removal or non-renewal shall be considered.
108.20 Independence and Anti-Capture Records. The Corporation shall maintain Independence and Anti-Capture Records sufficient to demonstrate that director independence, dual roles, affiliations, conflicts, recusal, restrictions, mitigation, annual reviews, event-based reviews, Board determinations, corrective actions, and removal or non-renewal decisions have been managed lawfully, consistently, defensibly, and in accordance with this Bylaw.
Independence and Anti-Capture Records shall include, as applicable:
a) annual independence disclosures, event-based disclosures, related-party disclosures, dual-role disclosures, affiliation maps, role-capacity statements, independence certifications, conflict questionnaires, sponsor relationship disclosures, donor and funder relationship disclosures, provider relationship disclosures, host relationship disclosures, public authority capacity disclosures, capital actor disclosures, enterprise actor disclosures, GCRI Canada disclosures, GRF disclosures, GRA disclosures, Nexus entity disclosures, university disclosures, laboratory disclosures, community disclosures, Tribal / Indigenous disclosures, and political or public authority ethics disclosures;
b) independence review records, anti-capture review records, sponsor-control review records, provider-neutrality review records, donor and funder non-control review records, host-control review records, public authority boundary review records, finance-boundary review records, certification-boundary review records, procurement-neutrality review records, recognition-boundary review records, public warning boundary review records, and enterprise-stack separation review records;
c) records of recusal, abstention, access restriction, committee restriction, deliberation restriction, recommendation restriction, voting restriction where lawful, information barrier, confidentiality undertaking, public statement restriction, controlled-room restriction, data-room restriction, repository restriction, corrective training, probation, resignation request, non-renewal, removal, and post-service access revocation;
d) records of Board determinations, Chair determinations where delegated, committee recommendations, counsel review, compliance review, safeguards review, tax review, public authority review, finance-boundary review, data / AI / cyber review, research integrity review, competition review, sanctions review, export-control review, controlled-technology review, and national security sensitivity review;
e) records of public claims, public descriptions, website references, biographies, press references, sponsor references, provider references, public authority references, grant references, investor references, bid references, procurement references, Nexus-compatible references, GRF references, GRA references, and correction of misleading use;
f) compatibility notes, divergence logs, capacity classifications, no-authority notices, non-reliance notices, controlled vocabulary classifications, public-safe limitation language, correction records, supersession records, withdrawal records, retraction records, takedown records, and archive records relating to director independence or dual-role matters;
g) records of influence concentration, funding concentration, common personnel, shared systems, shared counsel, shared communications, shared treasury risk, shared repository risk, shared publication risk, shared event risk, shared program risk, shared controlled-room risk, shared public authority interface risk, shared Nexus interface risk, and entity-separateness risk;
h) records of exceptions requested, exceptions refused, exceptions approved where lawful, conditions imposed, deadlines, responsible owners, monitoring requirements, review dates, and final disposition; and
i) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that independence is not merely the absence of a disclosed conflict; it is the continuing capacity to govern GCRI US loyally, lawfully, and independently as a public-benefit, non-executing, evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, public authority learning, and safeguards institution. Director affiliations may enrich the Board, but only when bounded by fiduciary duty, records, controlled vocabulary, recusal, access discipline, anti-capture controls, public-safe communication, and correctionability. No sponsor, donor, funder, provider, host, public authority, capital actor, national company, Project SPV, GCRI Canada body, GRF body, GRA body, Nexus entity, university, laboratory, political actor, community body, or enterprise actor may use a director’s role to control, purchase, imply, distort, or overclaim GCRI US authority.
Section 109. Election, Appointment, and Initial Directors
109.1 Election or Appointment Method. Directors shall be elected, appointed, renewed, replaced, or otherwise seated only in the manner authorized by applicable law, the Articles or Certificate, this Bylaw, any lawful member approval requirement where applicable, and a competent corporate record. No person shall become a director by reputation, title, donor status, sponsor status, founder status, technical contribution, authorship, public authority participation, advisory role, committee participation, Nexus role, GRF role, GRA role, GCRI Canada role, public announcement, website listing, slide deck, informal consent, email introduction, meeting attendance, or operational necessity alone.
The method of election or appointment shall be designed to preserve:
a) lawful corporate governance under the Corporation’s governing statute;
b) Board accountability to the Corporation’s nonprofit, non-stock or non-share, non-distributing, public-benefit purposes;
c) fiduciary independence and director eligibility;
d) continuity of governance without entrenchment, capture, or informal control;
e) mission lock, non-execution, role separation, public authority boundary discipline, finance-boundary discipline, certification-boundary discipline, procurement-neutrality discipline, provider neutrality, sponsor non-control, data / AI / cyber controls, community safeguards, validity-by-record, and correctionability;
f) separateness from GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Standards, consortiums, national companies, Project SPVs, providers, sponsors, hosts, public authorities, universities, laboratories, donors, funders, and enterprise-stack actors; and
g) a Board composition capable of governing evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, public authority learning, public-safe publication, protected knowledge, and United States / North America interface responsibilities.
Where more than one lawful method is available, the Board shall use the method that best protects lawful governance, independence, public-benefit accountability, and anti-capture discipline.
109.2 Appointment by Incorporator Where Applicable During Formation. During the Corporation’s formation period, and only to the extent permitted by applicable law and the Articles or Certificate, the incorporator or incorporators may appoint the initial director or directors, adopt initial organizational resolutions, and take such limited organizational acts as are necessary to constitute the Board and place the Corporation into lawful operation.
Incorporator appointment authority shall be transitional, formation-specific, and record-limited. It shall not be used to create permanent founder control, sponsor control, donor control, provider control, public authority control, GCRI Canada control, GRF control, GRA control, Nexus entity control, enterprise-stack control, or informal veto rights over the Board.
An incorporator appointment record shall identify, as applicable:
a) the legal authority for the appointment;
b) the name of each initial director;
c) the effective date of appointment;
d) the consent of each initial director to serve;
e) the initial term or transitional status of each initial director;
f) any required organizational resolutions;
g) any conflicts, affiliations, or dual-role matters disclosed before appointment;
h) any conditions, limitations, access restrictions, committee restrictions, or recusal requirements imposed at appointment; and
i) the transition path from incorporator appointment to ordinary Board governance.
After the Board is duly constituted, incorporator authority shall cease except to the extent expressly preserved by law, the Articles or Certificate, or a competent corporate record.
109.3 Election by Members Where Required. Where applicable law, the Articles or Certificate, this Bylaw, or a lawful membership structure requires director election by statutory members or voting members, such election shall be conducted in accordance with the governing legal requirements and the Corporation’s records, notice, quorum, voting, eligibility, conflict, and public-benefit controls.
Member election of directors, where applicable, shall not permit:
a) vote purchase;
b) sponsored voting;
c) donor-controlled voting;
d) funder-controlled voting;
e) provider-controlled voting;
f) host-controlled voting;
g) public authority-controlled voting;
h) investor, insurer, lender, underwriter, bank, public finance actor, national company, Project SPV, or enterprise-stack controlled voting;
i) coordinated capture through affiliates, related persons, sponsored seats, common representatives, funding arrangements, in-kind dependencies, or shared personnel;
j) election of a legally ineligible or disqualified person;
k) election that defeats independence, fiduciary duty, nonprofit character, public-benefit purpose, tax-exempt or tax-exempt-compatible obligations, non-execution, role separation, safeguards, or Board effectiveness; or
l) election by persons who are not lawful members with voting rights under governing records.
Member election materials shall use controlled vocabulary and shall not represent that a director candidate will serve as the representative of any sponsor, donor, funder, provider, host, public authority, investor, insurer, lender, national company, Project SPV, GRF body, GRA body, GCRI Canada body, Nexus entity, university, laboratory, community, political actor, or enterprise actor unless such representative role is expressly lawful, compatible with fiduciary duty, and recorded.
109.4 Appointment by Board Where Permitted. Where permitted by law, the Articles or Certificate, this Bylaw, and any applicable member approval rule, the Board may appoint directors to fill vacancies, expand the Board within authorized limits, renew directors, seat successor directors, or transition from initial formation governance to ordinary governance.
Board appointment shall require a competent Board act, recorded by resolution, written consent, minutes, or other lawful Board record. The Board shall not appoint a director unless it has considered, or has caused to be considered, the candidate’s eligibility, qualifications, independence, conflicts, dual roles, time commitment, confidentiality capacity, fit-and-proper status, integrity, competence, and ability to serve the Corporation’s public-benefit purposes.
Board appointment shall not be used to:
a) bypass member approval where required;
b) entrench an incumbent group contrary to law or fiduciary duty;
c) satisfy sponsor, donor, funder, provider, public authority, founder, GCRI Canada, GRF, GRA, Nexus, national company, Project SPV, investor, insurer, lender, or enterprise-stack demands;
d) cure a disqualification without proper review;
e) avoid conflict or independence controls;
f) create silent designated seats;
g) create apparent agency or representative authority; or
h) add directors without regard to Board effectiveness, skills mix, quorum, committee needs, safeguards, public trust, and anti-capture discipline.
A Board-appointed director shall have no authority until the appointment is effective, the director has consented to serve, required acknowledgments have been completed, and the director has been entered into the Director Register or equivalent corporate record.
109.5 Initial Directors. The initial directors shall be those persons lawfully named in the Articles or Certificate, appointed by incorporator action, elected by members where applicable, or appointed by other lawful organizational record during formation. Initial directors shall serve subject to applicable law, the Articles or Certificate, this Bylaw, any formation resolutions, and any transition provisions adopted by competent authority.
Initial directors shall have the authority necessary to organize the Corporation, including, where lawful and appropriate:
a) adopting or confirming this Bylaw;
b) appointing initial officers;
c) establishing the official repository, Bylaw register, Board resolution register, director register, officer register, and minute book;
d) approving initial banking, treasury, tax, insurance, registered agent, registered office, and filing arrangements;
e) adopting initial policies necessary for conflicts, confidentiality, records, data / AI / cyber, public-safe claims, support acceptance, non-execution, public authority boundaries, finance boundaries, provider neutrality, sponsor non-control, safeguards, and correctionability;
f) authorizing initial applications, registrations, state qualifications, charitable solicitation registrations, tax filings, or compliance steps where appropriate;
g) establishing initial committees or advisory bodies where needed;
h) approving initial public descriptions, controlled vocabulary, name-use controls, and public-safe notices;
i) approving initial GCRI Canada, GRF, GRA, Nexus, public authority, university, laboratory, community, sponsor, donor, funder, provider, host, and enterprise-interface discipline; and
j) taking other lawful organizational acts consistent with the Corporation’s public-benefit purposes.
Initial director status shall not exempt any person from fiduciary duties, qualification standards, disqualification rules, independence review, conflict disclosure, confidentiality, training, recusal, records discipline, or removal where required.
109.6 Transition From Initial Directors to Regular Governance. The Corporation shall transition from initial director governance to regular governance as soon as reasonably practicable after formation, consistent with applicable law, the Articles or Certificate, this Bylaw, public-benefit purpose, Board continuity, and organizational readiness.
The transition process may include:
a) confirming the number of directors;
b) assigning initial terms;
c) staggering terms where adopted;
d) confirming Board officer roles;
e) completing director qualification, independence, and conflict reviews;
f) adopting a director nomination and renewal process;
g) establishing Board committees;
h) adopting the first annual plan and budget;
i) approving initial policy and register infrastructure;
j) confirming repository and records controls;
k) confirming public-safe name, status, and role descriptions;
l) confirming GCRI Canada, GRF, GRA, Nexus, public authority, and enterprise-stack interface controls;
m) setting the first annual meeting or regular Board calendar;
n) confirming training requirements; and
o) recording any transitional savings, deadlines, conditions, or corrective actions.
The transition shall not create a gap in governance. Until regular governance is fully established, initial directors shall continue to act within lawful authority, subject to fiduciary duty and this Bylaw. No transitional ambiguity shall be used to create founder control, informal authority, sponsor influence, provider preference, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, or enterprise execution.
109.7 Nomination Procedure. The Board may establish a nomination procedure for director candidates through this Bylaw, Board resolution, committee charter, governance policy, or other lawful record. The nomination procedure shall be designed to produce a Board that is competent, independent, diverse in relevant expertise and perspective, capable of governing the Corporation’s mission, and resistant to capture.
A nomination procedure may include:
a) identification of Board needs;
b) skills matrix review;
c) independence and anti-capture review;
d) public-benefit governance needs review;
e) legal, tax, nonprofit, audit, risk, public authority, finance-boundary, data / AI / cyber, evidence, methods, observability, technical asset, safeguards, civil rights, accessibility, Tribal / Indigenous protocol, protected knowledge, public-safe publication, and Nexus interface competence review;
f) candidate sourcing;
g) candidate interviews;
h) background, sanctions, export-control, controlled-technology, integrity, and fit-and-proper screening where appropriate;
i) conflict and related-party disclosure;
j) dual-role and affiliation mapping;
k) reference checks where appropriate;
l) candidate acknowledgment of duties and boundaries;
m) committee recommendation where applicable;
n) Board deliberation and approval; and
o) Director Register entry.
The nomination procedure shall not be controlled by a sponsor, donor, funder, provider, host, public authority, investor, insurer, lender, national company, Project SPV, GCRI Canada, GRF, GRA, Nexus entity, founder group, political actor, university, laboratory, community body, or enterprise actor. External suggestions may be received, but nomination authority shall remain with the competent governance body.
109.8 Nominating Materials. Nominating materials shall be sufficient to permit informed review of a director candidate’s eligibility, qualifications, independence, conflicts, affiliations, competence, reputation, time capacity, confidentiality capacity, and ability to serve the Corporation’s public-benefit purposes.
Nominating materials may include, as applicable:
a) candidate biography;
b) curriculum vitae or equivalent professional history;
c) statement of interest;
d) consent to screening;
e) consent to serve if appointed or elected;
f) conflict disclosure;
g) related-party disclosure;
h) dual-role and affiliation disclosure;
i) sponsor, donor, funder, provider, host, public authority, investor, insurer, lender, national company, Project SPV, GCRI Canada, GRF, GRA, Nexus entity, university, laboratory, community, Tribal / Indigenous, civil society, media, political, and enterprise relationship disclosure;
j) employment, board, advisory, consulting, ownership, investment, IP, data, software, model, technical asset, grant, sponsorship, and publication relationship disclosure;
k) sanctions, export-control, controlled-technology, national security sensitivity, fraud, corruption, misconduct, research integrity, civil rights, harassment, retaliation, data misuse, AI misuse, cyber misconduct, and protected knowledge screening information where appropriate;
l) statement of understanding of fiduciary duties;
m) statement of understanding of non-execution, role separation, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, and correctionability;
n) anticipated committee suitability;
o) time commitment confirmation;
p) confidentiality and secure-system capacity confirmation; and
q) any proposed conditions, recusals, restrictions, or onboarding requirements.
Nominating materials shall be treated as confidential Board materials unless classified otherwise. They shall be retained, sealed, deleted, archived, or disposed of in accordance with applicable law, privacy obligations, records policy, and this Bylaw.
109.9 Eligibility Review. Before appointment, election, renewal, or seating of a director, the Corporation shall conduct an eligibility review sufficient to determine whether the candidate is legally eligible, properly qualified, not disqualified, capable of consent, capable of fiduciary service, and capable of compliance with the Corporation’s governing instruments.
Eligibility review shall include, as applicable:
a) legal eligibility under the governing nonprofit corporation statute;
b) eligibility under the Articles or Certificate;
c) eligibility under this Bylaw;
d) age, capacity, consent, residency, citizenship, public office, employment, regulatory, government ethics, or other status review where legally relevant;
e) sanctions, export-control, controlled-technology, restricted-party, debarment, suspension, exclusion, or national security sensitivity screening where appropriate;
f) nonprofit, tax-exempt or tax-exempt-compatible, charitable solicitation, grant, restricted fund, public support, and private benefit compatibility review where relevant;
g) conflict, related-party, and dual-role review;
h) confidentiality and secure-system capacity review;
i) time commitment and participation capacity review;
j) competence and skills review;
k) public authority boundary, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, sponsor non-control, and role-separation understanding;
l) data / AI / cyber / privacy, research integrity, civil rights, accessibility, community safeguards, Tribal / Indigenous protocol, protected knowledge, and public-safe publication understanding; and
m) any other review required by law, policy, Board resolution, or prudent governance.
No candidate shall be seated while an unresolved eligibility issue presents material legal, fiduciary, public-benefit, public authority, finance-boundary, data / AI / cyber, safeguards, reputational, or anti-capture risk.
109.10 Conflict Review. Before appointment, election, renewal, or seating of a director, the Corporation shall conduct a conflict review. Conflict review shall determine whether actual, potential, or perceived conflicts exist and whether such conflicts are absent, manageable, conditionally manageable, unmanageable, disqualifying, or requiring recusal, access restriction, committee restriction, voting restriction where lawful, public statement restriction, or other mitigation.
Conflict review shall consider, without limitation:
a) financial interests;
b) related-party interests;
c) employment, consulting, advisory, board, officer, fiduciary, contractor, vendor, provider, host, sponsor, donor, funder, investor, insurer, lender, underwriter, bank, public finance actor, national company, Project SPV, university, laboratory, public authority, GRF, GRA, GCRI Canada, Nexus entity, political, community, Tribal / Indigenous, media, civil society, and enterprise affiliations;
d) research conflicts;
e) publication conflicts;
f) data, AI, cyber, model, software, technical asset, repository, IP, licensing, benchmark, dashboard, sensor, AI-RAN, O-RAN, DePIN, DLT, blockchain, digital twin, geospatial, cyber telemetry, public-good software, and open technical baseline conflicts;
g) public authority capacity conflicts;
h) finance, securities, insurance, lending, rating, public finance, procurement, certification, recognition, Docket, Grid, Nexus-compatible, provider-preference, and sponsor-control conflicts;
i) protected knowledge, community, Tribal / Indigenous, local, territorial, civil rights, accessibility, grievance, remedy, and non-retaliation conflicts;
j) public statement and name-use conflicts; and
k) any recurring recusal burden that would materially impair Board service.
A conflict shall be recorded whether or not it is disqualifying. A manageable conflict shall be subject to written mitigation. An unmanageable conflict shall prevent appointment, election, renewal, or continued service unless the conflict is resolved.
109.11 Independence Review. Before appointment, election, renewal, or seating of a director, the Corporation shall conduct an independence review under Section 108 and any applicable policy. Independence review shall determine whether the candidate can exercise fiduciary judgment for GCRI US as a separate legal entity, without improper control, external loyalty, role collapse, capture, or inability to act in the best interests of the Corporation.
Independence review shall consider, without limitation:
a) sponsor independence;
b) donor and funder independence;
c) provider, vendor, contractor, and host independence;
d) public authority independence where required;
e) investor, insurer, lender, underwriter, bank, public finance, and capital-reader independence;
f) national company, state operating company, regional company, and Project SPV independence;
g) GCRI Canada, GRF, GRA, Nexus, consortium, standards, protocol, Docket, Grid, and enterprise-stack dual roles;
h) political, partisan, campaign, lobbying, government ethics, public procurement, public grant, and public finance conflicts;
i) research outcome purchase risk;
j) standards outcome purchase risk;
k) recurring recusal burdens;
l) common personnel, common systems, common communications, common counsel, common treasury, shared repository, shared publication, shared controlled-room, shared event, or shared program risks;
m) public perception of capture; and
n) the candidate’s willingness to comply with limitations, recusals, access restrictions, and controlled vocabulary.
A candidate shall not be treated as independent solely because no financial conflict is disclosed. Independence shall be assessed functionally, structurally, and contextually.
109.12 Fit-and-Proper Review. Before appointment, election, renewal, or seating of a director, the Corporation may conduct, and for material or sensitive roles shall conduct, fit-and-proper review proportionate to the candidate’s expected responsibilities, access, public role, and risk profile.
Fit-and-proper review may include:
a) integrity review;
b) professional history review;
c) governance experience review;
d) fiduciary experience review;
e) nonprofit and public-benefit suitability review;
f) public authority relationship review;
g) research integrity review;
h) data misuse, AI misuse, cyber misconduct, protected knowledge breach, harassment, retaliation, discrimination, civil rights, accessibility, or safeguards concern review;
i) fraud, corruption, bribery, embezzlement, money laundering, terrorist financing, serious misconduct, false credentials, false public claims, or serious dishonesty review;
j) sanctions, export-control, restricted-party, controlled-technology, national security sensitivity, debarment, suspension, or exclusion review;
k) reputation and public trust review;
l) legal proceedings, regulatory matters, investigations, or settlements review where relevant and lawful;
m) willingness to correct errors and support correctionability; and
n) ability to maintain confidentiality and secure access discipline.
Fit-and-proper review shall be conducted fairly, proportionately, confidentially, and with regard to evidence quality, relevance, materiality, recency, remediation, due process, privilege, privacy, public-safe communication, and legal constraints. The absence of a conviction or formal finding shall not require appointment where material risk remains.
109.13 Consent to Act. No person shall serve as a director unless the person has provided valid consent to act as a director in the form and manner required or approved by the Corporation. Consent may be written, electronic, recorded in minutes, or otherwise documented as permitted by law and the Corporation’s records policy.
Consent to act shall include, as applicable:
a) consent to serve as a director of GCRI US;
b) acknowledgment that fiduciary duties are owed to GCRI US as a separate legal entity;
c) confirmation that the candidate is not aware of any legal disqualification not disclosed;
d) agreement to comply with law, the Articles or Certificate, this Bylaw, Board resolutions, policies, registers, controlled vocabulary, notices, and records requirements;
e) agreement to disclose conflicts and update disclosures;
f) agreement to recuse where required;
g) agreement to maintain confidentiality;
h) agreement to use approved systems and protect Board materials;
i) agreement to complete required onboarding and training;
j) agreement to support validity-by-record and correctionability;
k) agreement not to use the director role for public authority, finance, certification, procurement, recognition, provider-preference, sponsor-control, or enterprise-execution overclaims; and
l) agreement to resign or submit to review where eligibility, independence, confidentiality, participation, or fiduciary capacity materially changes.
Conditional consent that reserves loyalty to an external person or institution above fiduciary duty to the Corporation shall not be valid consent.
109.14 Acknowledgment of Duties. Before being seated, each director shall acknowledge the duties and responsibilities of Board service. The acknowledgment shall be designed to ensure that the director understands the legal, fiduciary, institutional, technical, public-benefit, and public-safe character of the role.
The acknowledgment of duties shall include, as applicable:
a) duty of care;
b) duty of loyalty;
c) duty of obedience to mission and law where applicable;
d) duty of good faith;
e) duty of prudence;
f) duty of diligence;
g) duty of independence;
h) duty to act in the best interests of GCRI US;
i) duty to preserve nonprofit and non-distribution character;
j) duty to prevent private inurement and impermissible private benefit;
k) duty to preserve tax-exempt or tax-exempt-compatible posture;
l) duty to preserve public-benefit purpose;
m) duty to preserve evidence integrity, methods integrity, research integrity, observability integrity, ontology integrity, technical truth integrity, public-good software integrity, and technical baseline integrity;
n) duty to preserve legal separateness from GCRI Canada, GRF, GRA, Nexus entities, national companies, Project SPVs, providers, sponsors, hosts, public authorities, and enterprise actors;
o) duty to maintain confidentiality and secure information governance;
p) duty to disclose conflicts and recuse where required;
q) duty to participate actively and prepare for Board matters;
r) duty to preserve public-safe claims discipline; and
s) duty to support correction, supersession, withdrawal, retraction, takedown, and archival where required.
A director who refuses to acknowledge these duties shall not be seated.
109.15 Acknowledgment of Non-Execution, Public Authority Boundaries, Finance Boundaries, Data / AI / Cyber Controls, Safeguards, Validity-by-Record, and Correctionability. Before being seated, each director shall acknowledge the Corporation’s core boundary disciplines. Such acknowledgment shall confirm that the director understands and accepts that GCRI US is a non-executing public-benefit technical institution and shall not be governed or represented as a regulator, public authority, emergency command body, public warning authority, public finance approver, broker, dealer, finder, investment adviser, bank, lender, insurer, underwriter, rating agency, procurement body, certification body, recognition body, protocol authority by default, national company, Project SPV, provider, operator, asset owner, or enterprise execution vehicle.
The acknowledgment shall include, without limitation:
a) non-execution boundary;
b) public authority boundary;
c) emergency command and public warning boundary;
d) finance, securities, investment adviser, broker-dealer, finder, banking, lending, insurance, underwriting, rating, public finance, capital-reader, and regulated-perimeter boundary;
e) procurement-neutrality boundary;
f) certification and accreditation boundary;
g) recognition, maturity, standing, Docket, Grid, GRF, and public-facing legitimacy boundary;
h) GRA finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, and capital-reader-room boundary;
i) provider-neutrality boundary;
j) sponsor, donor, funder, and host non-control boundary;
k) public-good stack and enterprise stack separation;
l) GCRI / GRF / GRA role separation;
m) data governance, privacy, AI governance, cyber, secure compute, model-register, inference-record, compute-workload, and repository controls;
n) research integrity, evidence integrity, methods integrity, public-safe publication, and technical asset controls;
o) civil rights, accessibility, community safeguards, Tribal and Indigenous protocol, Indigenous data safeguards, local and territorial knowledge, protected knowledge, public-safe mapping, grievance, remedy, protected participation, and non-retaliation controls;
p) validity-by-record;
q) correctionability; and
r) controlled vocabulary and public-safe notice discipline.
A director’s acknowledgment shall be retained in the Corporation’s records and may be renewed annually or upon material change in role, law, policy, risk, or Board responsibility.
109.16 Appointment or Election Resolution. Each director appointment or election shall be evidenced by a competent corporate record. Where the Board appoints or confirms a director, the record shall be a Board resolution, written consent, minutes, or other lawful Board record. Where members elect a director, the record shall include the member election record required by law and governing instruments. Where an incorporator appoints an initial director, the record shall include the incorporator action.
The appointment or election record shall identify, as applicable:
a) the appointing or electing authority;
b) the legal basis for appointment or election;
c) the name of the director;
d) the class or category of directorship, if any;
e) whether the director is initial, regular, successor, vacancy-filling, renewed, transitional, or holdover;
f) the term commencement date;
g) the term expiration date or term rule;
h) whether the director is subject to any staggering, term-limit, cooling-off, or continuity rule;
i) confirmation of eligibility review;
j) confirmation of conflict review;
k) confirmation of independence review;
l) confirmation of fit-and-proper review where applicable;
m) confirmation of consent to act;
n) confirmation of duty acknowledgments;
o) recusals, restrictions, conditions, or mitigation measures;
p) committee assignments where approved;
q) access class and onboarding requirements;
r) vote tally or approval record where applicable;
s) effective date; and
t) records custodian.
A defective, incomplete, ambiguous, or unauthorized appointment or election record shall be corrected, ratified where lawful, voided, restricted, or referred for counsel review before the person exercises Board authority.
109.17 Director Register Entry. The Corporation shall maintain a Director Register or equivalent corporate record identifying each person who is currently serving as a director and each person who has previously served as a director, subject to access, privacy, confidentiality, and retention controls.
The Director Register shall include, as applicable:
a) legal name;
b) approved public name where different;
c) contact information;
d) date of appointment or election;
e) appointing or electing authority;
f) term commencement date;
g) term expiration date;
h) term class or staggered term designation where applicable;
i) office held, if any;
j) committee assignments;
k) independence status;
l) conflict status and recusal notes where appropriate;
m) dual-role classifications;
n) access class;
o) onboarding status;
p) training status;
q) confidentiality acknowledgment status;
r) resignation, removal, expiration, renewal, non-renewal, vacancy, suspension, or restriction status;
s) public biography approval status;
t) public claim limitations;
u) records custody notes;
v) legal hold status where applicable;
w) archive status; and
x) metadata necessary to preserve validity-by-record.
Entry in the Director Register shall evidence the recorded status, but shall not cure an unlawful appointment, unresolved disqualification, missing consent, or unauthorized public claim. If the Director Register conflicts with the competent appointing or electing record, the conflict shall be escalated and corrected.
109.18 Election, Appointment, and Initial Director Records. The Corporation shall maintain Election, Appointment, and Initial Director Records sufficient to demonstrate that each director has been lawfully identified, reviewed, elected or appointed, seated, renewed, transitioned, restricted, removed, resigned, or recorded in accordance with law, the Articles or Certificate, this Bylaw, and the Corporation’s public-benefit governance controls.
Election, Appointment, and Initial Director Records shall include, as applicable:
a) incorporator appointment records, initial director records, organizational resolutions, formation minutes, transition records, and initial Board constitution records;
b) nomination records, candidate materials, eligibility review records, conflict review records, independence review records, fit-and-proper review records, sanctions screening records, export-control screening records, controlled-technology review records, integrity review records, public authority boundary review records, finance-boundary review records, certification-boundary review records, procurement-neutrality review records, provider-neutrality review records, sponsor non-control review records, data / AI / cyber review records, safeguards review records, and tax or nonprofit compatibility review records;
c) member election records where applicable, including notice, quorum, voting, proxies where permitted, written consents where permitted, vote tabulation, objections, challenges, and certification of results;
d) Board appointment records, Board resolutions, written consents, minutes, vote records, abstention records, recusal records, appointment conditions, and effective-date records;
e) director consents, acknowledgments of duties, non-execution acknowledgments, public authority boundary acknowledgments, finance-boundary acknowledgments, data / AI / cyber acknowledgments, safeguards acknowledgments, validity-by-record acknowledgments, correctionability acknowledgments, confidentiality acknowledgments, controlled vocabulary acknowledgments, and public-safe claims acknowledgments;
f) Director Register entries, term records, staggered term records, renewal records, holdover records, vacancy-filling records, resignation records, removal records, non-renewal records, transition and handover records, access revocation records, and post-service confidentiality records;
g) public description records, website listing records, biography approval records, public statement permissions, name-use limitations, sponsor / provider / public authority reference controls, Nexus-compatible reference controls, GRF / GRA reference controls, correction records, withdrawal records, takedown records, and public clarification records;
h) records of defects, challenges, disputes, ratifications, voided appointments, conditional appointments, restrictions, recusals, access limitations, committee limitations, legal review, counsel review, compliance review, Board review, and final disposition; and
i) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that no person becomes a director by implication. Director status must be lawfully created, consented to, reviewed, recorded, bounded, and maintained. Election or appointment shall protect the Corporation’s public-benefit mission, fiduciary independence, legal separateness, non-execution perimeter, role separation, public authority boundary, finance boundary, certification boundary, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, and correctionability.
Section 110. Director Terms, Staggering, Renewal, Holdover, and Term Limits
110.1 Term Commencement. A director’s term shall commence on the effective date stated in the competent election, appointment, renewal, vacancy-filling, transition, or holdover record, or, if no later effective date is stated, on the date the director has been lawfully elected or appointed, has consented to serve, has completed required acknowledgments, and has been entered into the Director Register or equivalent corporate record.
No director term shall be deemed to commence merely because a person has been nominated, publicly announced, listed in a slide, included in a website draft, invited to a Board meeting, copied on Board correspondence, granted repository access, granted controlled-room access, described as a founder, described as a director in proposed materials, or treated informally as a director before lawful completion of the required act.
The commencement of a director’s term shall be subject to:
a) applicable law;
b) the Articles or Certificate;
c) this Bylaw;
d) member approval where required;
e) the competent election or appointment record;
f) completion of eligibility, conflict, independence, and fit-and-proper review where applicable;
g) consent to act;
h) acknowledgment of duties;
i) acknowledgment of non-execution, public authority boundaries, finance boundaries, data / AI / cyber controls, safeguards, validity-by-record, and correctionability;
j) confidentiality and secure-system onboarding; and
k) any conditions, recusals, access restrictions, committee restrictions, or public-claim limitations imposed at appointment.
Where a commencement date is uncertain, disputed, defective, or unsupported, the Secretary or other authorized records custodian shall escalate the matter for review, and the narrower, less authority-inflating interpretation shall apply until corrected by competent record.
110.2 Term Length. The term length for directors shall be as provided in the Articles or Certificate, this Bylaw, Board resolution, member resolution where required, or other lawful governing record. Unless a different lawful term is adopted and recorded, directors may serve terms of such duration as the Board determines to be appropriate for continuity, accountability, public-benefit stewardship, legal compliance, Board renewal, institutional memory, anti-capture discipline, and mission stability.
Term length shall be structured to support:
a) continuity of fiduciary oversight;
b) preservation of institutional memory;
c) orderly succession;
d) Board renewal and skills refreshment;
e) public-benefit accountability;
f) independence and anti-capture review;
g) effective committee service;
h) all-states-and-territories and North America governance awareness;
i) continuity of evidence, methods, observability, ontology, public-good software, technical baseline, public authority learning, safeguards, and Nexus interface oversight; and
j) periodic reassessment of director eligibility, independence, conflicts, participation, and fitness.
A director’s term shall not be extended, shortened, renewed, or restarted by implication. Any change in term length shall be made only by lawful authority and recorded in the Director Register, Board records, and any required member or corporate records.
110.3 Initial Staggering. The Board may stagger the terms of initial directors to prevent simultaneous expiration of all director terms and to preserve continuity of governance during the Corporation’s formation, early operation, tax-exempt or tax-exempt-compatible structuring, public-benefit program development, repository establishment, policy adoption, public authority learning setup, and Nexus interface alignment.
Initial staggering may assign directors to different term classes, including shorter initial terms, transitional terms, or ordinary terms, provided that the staggering method is lawful, recorded, and consistent with the Articles or Certificate and this Bylaw.
Initial staggering shall be designed to avoid:
a) concentration of governance authority in a single founder group;
b) sponsor, donor, funder, provider, host, public authority, investor, insurer, lender, national company, Project SPV, GCRI Canada, GRF, GRA, Nexus entity, university, laboratory, political actor, community body, or enterprise-stack capture;
c) simultaneous loss of directors with key nonprofit, legal, evidence, methods, data / AI / cyber, public authority, safeguards, technical, finance-boundary, or Nexus interface competence;
d) informal life tenure;
e) hidden designated seats;
f) uncontrolled holdover service;
g) renewal without review; and
h) ambiguity in Board authority.
The initial staggering record shall identify the term class, commencement date, expiration date, renewal eligibility, transition rule, and any continuity exception applicable to each initial director.
110.4 Staggered Terms for Continuity. The Board may maintain staggered director terms as a continuing governance structure where lawful and beneficial to the Corporation. Staggered terms may be used to preserve institutional continuity, committee continuity, fiduciary stability, long-range public-benefit strategy, technical memory, evidence and methods stewardship, public-good software stewardship, public authority learning continuity, safeguards continuity, and Nexus interface continuity.
A staggered term structure shall be administered in a manner that permits periodic accountability and renewal review. Staggering shall not be used to entrench directors, avoid member rights where applicable, prevent lawful removal, dilute accountability, evade conflict review, evade independence review, or preserve capture by any external person or group.
In administering staggered terms, the Board shall consider:
a) the number of directors in each term class;
b) expiration dates;
c) director skills distribution;
d) committee leadership continuity;
e) director independence and conflict patterns;
f) renewal needs;
g) succession readiness;
h) diversity of expertise, geography, states, territories, public-interest perspective, and lived experience;
i) continuing need for all-states-and-territories and North America governance capacity; and
j) risk of over-concentration by affiliation, funder, sponsor, provider, public authority, technology sector, capital actor, institution, or Nexus role.
Staggered term records shall be maintained with sufficient precision to prevent uncertainty regarding each director’s term, class, renewal eligibility, and expiration.
110.5 Renewal Eligibility. A director may be eligible for renewal only if renewal is permitted by applicable law, the Articles or Certificate, this Bylaw, any term-limit rule, any cooling-off rule, any member approval requirement where applicable, and the competent governance record. Renewal shall not be automatic unless expressly required by law or governing instrument.
Renewal eligibility shall require current review of:
a) legal eligibility;
b) continuing consent to serve;
c) fiduciary performance;
d) attendance and participation;
e) preparedness and diligence;
f) independence;
g) conflicts and related-party relationships;
h) dual roles and affiliations;
i) confidentiality compliance;
j) public-benefit mission alignment;
k) non-execution compliance;
l) role-separation compliance;
m) public authority boundary compliance;
n) finance, securities, insurance, lending, rating, public finance, procurement, certification, recognition, and provider-neutrality boundary compliance;
o) sponsor, donor, funder, and host non-control compliance;
p) data / AI / cyber / privacy compliance;
q) research integrity, evidence integrity, methods integrity, public-safe publication, and technical asset stewardship compliance;
r) civil rights, accessibility, Tribal / Indigenous protocol, community safeguards, protected knowledge, grievance, remedy, and non-retaliation compliance;
s) competition, sanctions, export-control, controlled technology, and professional boundary compliance; and
t) the Corporation’s current Board composition and skills needs.
A director shall not be renewed merely because the director is senior, influential, founder-associated, donor-associated, technically central, publicly visible, sponsor-supported, provider-associated, public authority-connected, or difficult to replace.
110.6 Renewal Review. Before any director is renewed, the Corporation shall conduct a renewal review proportionate to the director’s role, tenure, access, committee service, public profile, conflicts, and risk profile. Renewal review shall determine whether the director should be renewed, renewed conditionally, renewed for a shortened term, renewed with restrictions, deferred, not renewed, or referred for further review.
Renewal review may be conducted by the Board, a governance or nominating committee, an independent committee, or another competent body designated by the Board, subject to applicable law and conflict controls.
Renewal review shall consider, without limitation:
a) attendance and engagement;
b) quality of fiduciary judgment;
c) contribution to Board deliberation;
d) respect for Board process;
e) compliance with confidentiality and secure-system rules;
f) compliance with conflict, recusal, independence, and anti-capture rules;
g) ability to challenge management, sponsors, providers, donors, funders, public authorities, technical leaders, founders, Nexus entities, and external actors where necessary;
h) evidence of over-identification with an external affiliation;
i) use or misuse of GCRI US name, title, materials, outputs, or public status;
j) public communications discipline;
k) responsiveness to correction and dissent;
l) completion of training;
m) service on committees;
n) suitability for continued access to sensitive materials;
o) safeguards awareness and conduct;
p) public-benefit and non-execution fidelity;
q) regulatory-perimeter discipline;
r) Board diversity, skills, renewal, and succession needs; and
s) any matter that may affect the Corporation’s trust, legality, public-benefit mission, tax posture, reputation, or Nexus-compatible role.
The renewal review record shall identify the reviewers, materials considered, conflicts disclosed, recusals applied, determination made, term approved if any, conditions imposed, and effective date.
110.7 Maximum Consecutive Terms Where Adopted. The Board may adopt maximum consecutive term limits for directors where lawful and appropriate to preserve renewal, independence, anti-capture discipline, fiduciary freshness, Board diversity, public-benefit accountability, and institutional legitimacy. Term limits may be contained in this Bylaw, Board policy, Board resolution, governance policy, or other competent record.
A term-limit structure may address:
a) maximum number of consecutive terms;
b) maximum years of continuous service;
c) treatment of partial terms;
d) treatment of initial staggered terms;
e) treatment of vacancy-filling terms;
f) treatment of emergency continuity extensions;
g) cooling-off periods;
h) re-eligibility after cooling-off;
i) exceptions for mission-critical continuity;
j) exceptions required by law or member approval rights where applicable; and
k) records required to support any exception.
Term limits shall not be applied in a manner that violates applicable law, undermines required member rights where applicable, removes all necessary expertise simultaneously, destabilizes the Corporation, or weakens safeguards, data / AI / cyber, public authority, finance-boundary, or technical oversight. Term limits also shall not be waived informally, silently, or for personal convenience.
110.8 Cooling-Off Period Where Adopted. Where a cooling-off period is adopted, a director who has reached the applicable term limit or maximum consecutive service period shall not be eligible for immediate reappointment or reelection until the cooling-off period has expired, unless a lawful continuity exception is approved and recorded.
The cooling-off period may be used to:
a) reduce entrenchment;
b) refresh Board judgment;
c) mitigate capture;
d) manage conflicts;
e) permit new expertise;
f) strengthen public trust;
g) distinguish Board service from founder control or sponsor influence;
h) reduce dependence on any single director; and
i) provide an orderly path for former directors to serve in advisory, committee, fellow, ambassadorial, or other non-fiduciary roles where appropriate and lawful.
During a cooling-off period, a former director shall not exercise Board authority, receive Board materials, access confidential Board systems, act as a de facto director, direct officers, bind the Corporation, represent the Board, or use prior director status to create apparent authority. Any advisory or committee role during a cooling-off period shall be separately authorized, bounded, recorded, and subject to conflict, confidentiality, data / AI / cyber, public authority, finance-boundary, safeguards, and public-claim controls.
110.9 Continuity Exception Where Lawful. The Board may approve a continuity exception to term limits, cooling-off periods, term expiration, or ordinary succession rules only where lawful, necessary or highly advisable for institutional continuity, and consistent with public-benefit purpose, fiduciary duty, independence, anti-capture discipline, and this Bylaw.
A continuity exception may be considered where:
a) simultaneous director departures would materially impair Board function;
b) the Corporation lacks legally required minimum directors;
c) loss of a director would materially impair urgent legal, tax, audit, risk, data / AI / cyber, public authority, safeguards, technical, public-good software, repository, evidence, methods, observability, or Nexus interface continuity;
d) a major investigation, audit, litigation, incident, public-safe correction, public authority matter, cyber incident, protected knowledge matter, or regulatory-perimeter issue requires continuity of Board knowledge;
e) a new director recruitment process is underway but not complete;
f) a transition period is needed for committee leadership, officer succession, repository custody, financial oversight, or public authority interface continuity; or
g) applicable law or governing instruments require continuity until successors are seated.
A continuity exception shall be narrowly tailored, time-limited, recorded, subject to renewed review, and not used to preserve personal status, sponsor influence, donor preference, provider preference, founder control, public authority influence, or external capture.
110.10 Mission-Critical Continuity Extension. A mission-critical continuity extension may be approved where the Board determines that temporary continuation of a director is necessary to protect the Corporation’s lawful existence, tax-exempt or tax-exempt-compatible posture, fiduciary continuity, public-benefit mission, non-execution boundary, public authority boundary, finance boundary, data / AI / cyber controls, protected knowledge, public-safe publication, technical asset continuity, or Nexus interface stability.
Mission-critical continuity may include, without limitation:
a) preservation of quorum;
b) preservation of minimum director number;
c) completion of annual filings, tax filings, audit, review engagement, or financial close;
d) response to data breach, cyber incident, AI incident, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, sponsor-control issue, provider-preference issue, or public-safe publication error;
e) resolution of a major conflict, investigation, enforcement matter, litigation, grant compliance issue, restricted fund issue, or regulatory-perimeter matter;
f) continuity of Board oversight during emergency governance mode;
g) continuity of records, repository, gazette, controlled-room, or public authority room governance;
h) continuity of public-good software, open technical baseline, technical asset, or secure-release governance;
i) continuity of community safeguards, Tribal / Indigenous protocol, protected knowledge, grievance, remedy, non-retaliation, or stop-the-line governance; and
j) continuity of GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cell, national consortium, national company, Project SPV, provider, sponsor, host, public authority, or North America interface boundary discipline.
A mission-critical continuity extension shall specify the reason, scope, duration, limits, review date, sunset date, affected authorities, access rights, recusals, restrictions, and transition obligations.
110.11 Holdover Service Where Permitted by Law. Where permitted by applicable law, the Articles or Certificate, this Bylaw, or competent corporate record, a director whose term has expired may continue as a holdover director until a successor is duly elected or appointed and qualified, or until earlier resignation, removal, disqualification, non-renewal, or termination of holdover authority.
Holdover service shall be a continuity device, not an entitlement. A holdover director shall remain subject to all duties, conflicts, independence requirements, confidentiality obligations, recusal obligations, access controls, Board process requirements, public-safe claims rules, and removal provisions applicable to directors.
Holdover service shall not be used to:
a) avoid succession planning;
b) delay member election where required;
c) entrench directors;
d) preserve sponsor, donor, funder, provider, public authority, founder, Nexus, or enterprise influence;
e) continue a director with unresolved disqualification;
f) continue a director whose conflicts are unmanageable;
g) continue a director who has lost confidentiality capacity or fiduciary capacity;
h) avoid term limits or cooling-off rules except through a lawful and recorded exception; or
i) create ambiguity regarding Board composition.
The Director Register shall clearly identify holdover status, the legal basis for holdover service, the date the ordinary term expired, the anticipated successor or renewal process, and any restrictions applicable during holdover service.
110.12 Term Expiration. A director’s term shall expire at the end of the term stated in the governing record, unless the director is earlier removed, resigns, becomes disqualified, is not renewed, ceases to meet eligibility requirements, or continues in holdover service where lawful.
Upon term expiration, unless holdover service is permitted and recorded, the former director shall cease to have Board authority. Term expiration shall terminate the person’s authority to:
a) attend Board meetings as a director;
b) vote or consent as a director;
c) receive Board materials;
d) access Board systems;
e) participate in executive sessions;
f) participate in Board committees as a director;
g) act for the Board;
h) direct officers or staff;
i) represent the Corporation as a director;
j) bind the Corporation;
k) approve records, publications, contracts, public statements, controlled-room admissions, data access, AI use, public authority references, finance-adjacent materials, technical asset releases, or corrections; and
l) use director status in public, sponsor, provider, funder, public authority, investor, procurement, academic, media, community, Nexus, GRF, GRA, or enterprise contexts.
Any post-term role shall be separately authorized and recorded. Former director status shall not create continuing governance authority.
110.13 Termination of Board Access at End of Service. Upon expiration, resignation, removal, non-renewal, disqualification, death, incapacity, or other end of Board service, the Corporation shall terminate or modify Board access rights promptly and in accordance with law, records policy, data / AI / cyber controls, confidentiality obligations, legal hold requirements, and transition needs.
End-of-service access controls shall include, as applicable:
a) revocation of Board portal access;
b) revocation of email distribution list access;
c) revocation or modification of repository access;
d) revocation of controlled-room, clean-room, data-room, evidence-room, public authority room, and no-download room access;
e) return, deletion, transfer, sealing, or preservation of Board materials;
f) confirmation of legal hold obligations;
g) confirmation of post-service confidentiality duties;
h) revocation of signing authority;
i) revocation of banking authority;
j) revocation of public statement authority;
k) revocation of public authority interface authority;
l) revocation of data, AI, model, compute, cybersecurity, and technical asset authority;
m) revocation of committee authority unless separately reappointed in a non-director capacity;
n) update of public listings, biographies, websites, repositories, notices, and records; and
o) correction of any public materials that continue to represent the person as a current director.
Access termination shall not impair the Corporation’s right to require cooperation in transition, investigation, correction, audit, legal, compliance, tax, grant, repository, data, AI, cyber, safeguards, or records matters where lawful.
110.14 Transition and Handover. A departing director shall cooperate in reasonable transition and handover measures designed to preserve Board continuity, records integrity, committee continuity, institutional memory, public-benefit mission, fiduciary accountability, public-safe communication, and protection of confidential, privileged, cyber-sensitive, infrastructure-sensitive, finance-sensitive, personal, health-sensitive, Tribal / Indigenous, community-protected, local, territorial, cultural, environmental, or protected knowledge materials.
Transition and handover may include:
a) briefing successor directors or committee chairs;
b) identifying pending matters;
c) transferring records to the Secretary or approved custodian;
d) confirming unresolved conflicts or recusals;
e) confirming open action items;
f) identifying sensitive materials previously accessed;
g) returning or deleting confidential materials where required;
h) preserving materials subject to legal hold;
i) assisting with correction, supersession, withdrawal, retraction, takedown, or public clarification matters;
j) assisting with audit, tax, grant, restricted fund, compliance, public authority, data / AI / cyber, safeguards, repository, technical asset, or Nexus interface matters;
k) documenting post-service restrictions;
l) updating public descriptions; and
m) confirming that no continuing authority is implied.
Transition obligations shall be bounded by law, confidentiality, privilege, privacy, conflict rules, employment or contractor status where applicable, and the Corporation’s records policy. No departing director shall retain Board materials or use Board knowledge for private, sponsor, provider, public authority, finance, procurement, certification, recognition, Nexus, GRF, GRA, or enterprise advantage.
110.15 Term Records. The Corporation shall maintain Term Records sufficient to demonstrate the lawful commencement, duration, staggering, renewal, holdover, expiration, extension, cooling-off, transition, and end-of-service handling of each director’s term.
Term Records shall include, as applicable:
a) appointment, election, renewal, vacancy-filling, initial director, and transition records;
b) term commencement date, term expiration date, term class, staggered term designation, partial term designation, and holdover status;
c) term-limit records, consecutive service records, cooling-off records, re-eligibility records, and exception records;
d) renewal review records, eligibility review records, conflict review records, independence review records, fit-and-proper review records, annual review records, event-based review records, training records, participation records, and Board evaluation records;
e) continuity exception records, mission-critical continuity extension records, emergency continuity records, quorum continuity records, and succession records;
f) resignation, removal, non-renewal, disqualification, death, incapacity, vacancy, and successor appointment records;
g) access revocation records, system access records, controlled-room access records, repository access records, signing authority records, banking authority records, committee access records, public authority interface access records, and public statement authority records;
h) transition and handover records, materials return records, deletion records, sealing records, legal hold records, archive records, and post-service confidentiality records;
i) public listing update records, biography update records, website update records, notice records, correction records, withdrawal records, takedown records, and public clarification records;
j) records of disputes, defects, ratifications, corrections, counsel review, Board review, member review where applicable, and final disposition; and
k) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that director service shall be time-bounded, record-supported, reviewable, renewable only through competent authority, and terminable without ambiguity. Term structures shall preserve continuity without entrenchment, independence without isolation, renewal without capture, and public-benefit stewardship without role confusion. No director shall continue, return, hold over, or exercise Board authority except by law, the Articles or Certificate, this Bylaw, and competent record.
Section 111. Resignation, Removal, Vacancy, and Succession
111.1 Director Resignation. A director may resign from the Board at any time by delivering a resignation notice to the Chair, Secretary, Board, or other person authorized by this Bylaw, Board resolution, policy, or applicable law to receive such notice. A resignation may be written, electronic, or otherwise recorded in a reliable form sufficient to evidence the director’s intent to resign, the date of delivery, the person receiving the notice, and any stated effective date.
A director’s resignation shall not require acceptance unless acceptance is required by applicable law, the Articles or Certificate, this Bylaw, the resignation notice, or a competent Board record. Where acceptance is not required, the resignation shall be effective in accordance with its terms. Where acceptance is required, the resignation shall become effective upon acceptance or at such later lawful time as the accepting record provides.
A resignation shall not, by itself, discharge the resigning director from:
a) fiduciary, confidentiality, conflict, non-retaliation, data / AI / cyber, public authority boundary, finance-boundary, safeguards, protected knowledge, records, legal hold, cooperation, correction, or post-service duties that survive service;
b) responsibility for acts or omissions occurring during the director’s term;
c) duties to return, delete, transfer, seal, preserve, or protect Board materials;
d) duties to cooperate in transition, audit, investigation, correction, tax, grant, public authority, data, AI, cyber, protected knowledge, repository, or legal matters where lawful; or
e) duties not to misuse the director’s former title, Board knowledge, confidential information, public authority relationships, technical assets, GCRI US name, Nexus references, GRF references, GRA references, or public-good materials.
A resignation shall be recorded promptly in the Director Register and Board records.
111.2 Effective Date of Resignation. A resignation shall be effective on the date specified in the resignation notice, or, if no date is specified and acceptance is not required, upon delivery to the authorized recipient. A resignation may state a future effective date, transition condition, handover requirement, or earlier effective date if accepted, provided that the condition is lawful and does not create uncertainty inconsistent with Board continuity.
Where a resignation is stated to be effective upon appointment or election of a successor, the director may continue to serve until the successor is duly elected or appointed and qualified, unless the Board determines that earlier effectiveness is required because of disqualification, breach of duty, unmanaged conflict, loss of independence, incapacity, confidentiality risk, public authority confusion, finance-boundary risk, data / AI / cyber risk, safeguards risk, or other material governance concern.
A resignation effective date shall not be manipulated to:
a) preserve quorum artificially;
b) evade removal;
c) avoid conflict review;
d) delay access revocation;
e) prevent correction;
f) preserve sponsor, donor, funder, provider, public authority, founder, GCRI Canada, GRF, GRA, Nexus, national company, Project SPV, or enterprise influence;
g) avoid member action where required; or
h) create ambiguity regarding Board authority.
Where uncertainty exists regarding the effective date, the Secretary or records custodian shall escalate the issue for Board, Chair, counsel, or governance review, and the narrower, less authority-inflating interpretation shall apply pending correction.
111.3 Resignation Notice. A resignation notice shall be sufficient if it clearly communicates the director’s intent to resign and permits the Corporation to identify the resigning director, delivery date, effective date, and any stated conditions. The Corporation may adopt a standard resignation form, but failure to use the form shall not invalidate an otherwise clear and lawful resignation.
A resignation notice may include, as applicable:
a) the director’s legal name;
b) the director’s current Board role and committee roles;
c) effective date and time;
d) whether the resignation applies to Board service only or also to officer, committee, council, advisory, working group, repository, controlled-room, public authority interface, GCRI Canada interface, GRF interface, GRA interface, Nexus interface, or other roles;
e) transition and handover commitments;
f) confirmation of continuing confidentiality obligations;
g) confirmation of return, deletion, preservation, or transfer of materials;
h) disclosure of any unresolved conflicts, recusals, access issues, or governance concerns;
i) statement regarding public descriptions and former director status;
j) contact information for post-service notices; and
k) request for acknowledgment of receipt.
Upon receipt of a resignation notice, the Secretary or authorized records custodian shall record the notice, update relevant registers, initiate access review, notify appropriate Board or officer roles, and begin transition, public-description, and records closeout steps.
111.4 Removal Under Applicable Law. A director may be removed only as permitted by applicable law, the Articles or Certificate, this Bylaw, any lawful member approval requirement, and competent corporate record. Removal may be with or without cause only where the governing law and governing instruments permit such removal. Where cause is required, removal shall be based on grounds sufficient under law, this Bylaw, or the applicable record.
Removal shall be treated as a governance protection mechanism, not as a tool for retaliation, factional control, sponsor influence, donor influence, provider influence, public authority pressure, personal disagreement, suppression of dissent, suppression of minority views, or avoidance of accountability.
The Corporation shall administer removal in a manner consistent with:
a) fiduciary duty;
b) due process or fair process where required or appropriate;
c) confidentiality;
d) privilege;
e) conflict and recusal controls;
f) public-benefit purpose;
g) Board continuity;
h) member rights where applicable;
i) data / AI / cyber and safeguards protections;
j) records integrity;
k) public-safe communication; and
l) correctionability.
No removal shall create authority for any external person to appoint, designate, direct, or control a replacement director unless such authority is expressly provided by law, the Articles or Certificate, this Bylaw, or a competent and lawful record.
111.5 Removal by Members Where Required or Permitted. Where applicable law, the Articles or Certificate, this Bylaw, or a lawful membership structure grants members the right to remove a director, such removal shall be conducted in accordance with the applicable notice, quorum, voting, class, consent, meeting, written action, record, and procedural requirements.
Member removal shall not be conducted by persons who are not lawful voting members. Member removal shall not be purchased, sponsored, directed, coerced, or coordinated by a sponsor, donor, funder, provider, host, public authority, investor, insurer, lender, underwriter, bank, public finance actor, national company, Project SPV, GCRI Canada body, GRF body, GRA body, Nexus entity, political actor, contractor, vendor, or enterprise-stack actor unless such person is lawfully acting only in a capacity permitted by the governing instruments and subject to conflict and anti-capture controls.
Member removal materials shall not misrepresent:
a) the director’s legal status;
b) the Corporation’s public-benefit purpose;
c) the Board’s authority;
d) public authority relationships;
e) finance-readiness, certification, procurement, recognition, Docket, Grid, or Nexus-compatible status;
f) allegations not supported by record;
g) confidential, privileged, protected, cyber-sensitive, infrastructure-sensitive, personal, Tribal / Indigenous, local, territorial, cultural, environmental, or protected knowledge materials; or
h) the effect of removal on corporate authority.
Member removal records shall include notice, materials, quorum, voting results, recusals or conflicts where applicable, effective date, successor process, public-description updates, and Director Register updates.
111.6 Removal by Board Where Permitted. Where permitted by applicable law, the Articles or Certificate, this Bylaw, or a competent corporate record, the Board may remove a director. Board removal may be used to protect the Corporation where continued service is inconsistent with legal eligibility, fiduciary duty, independence, confidentiality, participation, public-benefit purpose, non-execution, role separation, public authority boundary discipline, finance-boundary discipline, certification-boundary discipline, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, or correctionability.
Board removal shall be undertaken only through competent Board action, subject to any required notice, quorum, voting threshold, recusal, conflict, fair process, member approval, counsel review, or other procedural requirement.
In considering Board removal, the Board may consider:
a) the seriousness of the conduct or condition;
b) whether the issue is curable;
c) whether lesser measures are adequate;
d) whether interim access restriction is needed;
e) whether the director has disclosed relevant facts;
f) whether the director has complied with recusal or confidentiality duties;
g) whether the director’s continued service threatens the Corporation;
h) whether the matter involves protected knowledge, public authority confusion, finance overclaim, data / AI / cyber incident, public-safe publication error, or safeguards breach;
i) whether removal is required to preserve legal compliance, public trust, or mission lock; and
j) whether public or controlled correction is required.
A director subject to removal consideration shall not participate in deliberation or vote on the director’s own removal except to the extent required or permitted by law and Board process.
111.7 Removal for Ineligibility. A director may be removed, or shall cease to serve where law so provides, if the director becomes legally ineligible, fails to maintain required qualifications, becomes disqualified under this Bylaw, lacks capacity to consent or serve, fails to maintain good standing where required, or otherwise cannot lawfully continue as a director.
Ineligibility may arise from, without limitation:
a) statutory disqualification;
b) failure to meet minimum legal age, capacity, residency, office, independence, or other legal requirements where applicable;
c) loss of required consent;
d) sanctions, restricted-party, export-control, controlled-technology, debarment, suspension, exclusion, or national security sensitivity status where material;
e) legal restriction arising from public office, employment, government ethics, procurement, lobbying, grant, public records, public finance, or regulatory rules;
f) court order, regulatory order, settlement condition, employment condition, institutional rule, or contractual restriction materially inconsistent with service;
g) incapacity preventing fiduciary service;
h) failure to complete required onboarding, disclosures, acknowledgments, or training after notice and opportunity to cure where appropriate; or
i) any condition that causes continued service to violate law, the Articles or Certificate, this Bylaw, or public-benefit governance requirements.
Removal for ineligibility shall be recorded with the basis, effective date, supporting record, access closeout, and successor process.
111.8 Removal for Breach of Fiduciary Duty. A director may be removed for breach of fiduciary duty where permitted by law and governing instruments. Breach of fiduciary duty includes material failure to act with care, loyalty, good faith, obedience to mission and law where applicable, prudence, diligence, independence, confidentiality, conflict disclosure, recusal, or best-interest judgment for GCRI US as a separate legal entity.
A fiduciary breach may include, without limitation:
a) using the director role for personal, sponsor, donor, funder, provider, public authority, investor, insurer, lender, national company, Project SPV, GRF, GRA, Nexus, political, institutional, or enterprise advantage;
b) placing external loyalty above duty to GCRI US;
c) failing to disclose conflicts or related-party interests;
d) participating despite required recusal;
e) misusing confidential, privileged, protected, cyber-sensitive, infrastructure-sensitive, finance-sensitive, personal, Tribal / Indigenous, community-protected, local, territorial, cultural, environmental, or protected knowledge materials;
f) knowingly supporting authority-inflating public claims;
g) suppressing correction, dissent, minority views, public-safe limitation, or safeguards escalation;
h) directing officers or staff outside Board process;
i) acting as a de facto executive or external representative without authority;
j) approving or promoting private benefit or inurement; or
k) failing to act when required to prevent material harm to the Corporation.
Removal for fiduciary breach may be accompanied by access restriction, investigation, correction, public clarification, legal action, claim preservation, insurance notice, regulatory notice, funder notice, public authority notice, or other lawful response.
111.9 Removal for Unmanaged Conflict. A director may be removed where an actual, potential, or perceived conflict of interest, related-party relationship, dual role, affiliation, financial interest, institutional interest, research interest, public authority relationship, sponsor relationship, provider relationship, capital actor relationship, national company relationship, Project SPV relationship, GCRI Canada role, GRF role, GRA role, Nexus role, or enterprise-stack relationship becomes unmanageable.
A conflict may be unmanageable where:
a) the conflict is recurring and materially impairs Board participation;
b) the conflict affects a material portion of Board business;
c) recusal would prevent effective service;
d) access restriction would prevent meaningful fiduciary participation;
e) the director refuses or fails to disclose;
f) the director refuses or fails to recuse;
g) the director uses Board role to benefit an affiliated person;
h) the conflict creates public authority confusion, finance-boundary risk, certification-boundary risk, procurement-neutrality risk, recognition-boundary risk, provider-preference risk, sponsor-control risk, or enterprise execution risk;
i) the conflict undermines public trust, safeguards, protected knowledge, or correctionability; or
j) no lawful mitigation can preserve the director’s fiduciary independence.
The Board may attempt mitigation before removal where safe and lawful, but removal shall be available where mitigation is insufficient, impracticable, refused, or inconsistent with public-benefit protection.
111.10 Removal for Serious Misconduct. A director may be removed for serious misconduct where permitted by law and governing instruments. Serious misconduct includes conduct that materially harms or threatens the Corporation, its public-benefit mission, legal status, public trust, participants, protected communities, records, technical assets, public authority relationships, data, systems, or Nexus-compatible role.
Serious misconduct may include, without limitation:
a) fraud, corruption, bribery, embezzlement, misappropriation, theft, false credentials, false records, or serious dishonesty;
b) harassment, discrimination, retaliation, bullying, coercion, intimidation, or abuse of position;
c) data misuse, AI misuse, cyber misconduct, unauthorized access, credential misuse, key misuse, repository abuse, secret leakage, vulnerability concealment, or secure-system violation;
d) protected knowledge breach;
e) Indigenous protocol breach;
f) research misconduct;
g) fabrication, falsification, plagiarism, evidence tampering, source-lineage manipulation, or publication suppression;
h) competition, antitrust, sanctions, export-control, controlled-technology, public procurement, government ethics, grant, lobbying, or professional boundary violation;
i) unauthorized public authority representation;
j) unauthorized finance, investment, insurance, lending, rating, public finance, procurement, certification, recognition, or provider-preference claim;
k) deliberate obstruction of investigation, audit, correction, legal review, or Board process;
l) conduct causing material reputational, legal, safety, safeguards, public trust, or public-benefit harm; or
m) conduct materially incompatible with continued fiduciary service.
The Corporation may impose interim restrictions while serious misconduct is reviewed.
111.11 Removal for Persistent Non-Attendance. A director may be removed for persistent non-attendance, failure to prepare, failure to participate, failure to complete required training, failure to respond to Board communications, failure to discharge committee responsibilities, or other sustained inability or unwillingness to perform Board duties.
Persistent non-attendance may be determined by reference to:
a) missed regular meetings;
b) missed special meetings;
c) missed emergency meetings where participation was reasonably possible;
d) missed committee meetings;
e) failure to review Board materials;
f) failure to vote or consent where required;
g) failure to complete assigned actions;
h) failure to complete disclosures;
i) failure to complete training;
j) failure to maintain secure access;
k) failure to respond during time-sensitive legal, tax, cyber, public authority, safeguards, finance-boundary, public-safe publication, or correction matters; and
l) overall impairment of Board functioning.
Before removal for non-attendance, the Corporation may provide notice and opportunity to cure where appropriate. Immediate removal may be considered where non-participation creates material legal, fiduciary, quorum, oversight, records, public-benefit, or continuity risk.
111.12 Removal for Misuse of Name, Marks, Records, Data, Software, Technical Assets, Public Claims, or Nexus-Compatible Claims. A director may be removed for misuse of the Corporation’s name, marks, logos, seal, badges, public descriptions, reports, datasets, software, technical baselines, repositories, proof receipts, public-good assets, controlled vocabulary, public-safe notices, Board records, public authority references, GRF-facing inputs, GRA-facing inputs, Nexus-compatible claims, or other institutional materials.
Misuse includes, without limitation:
a) representing personal views as GCRI US positions without authority;
b) using director status in marketing, fundraising, investor materials, bid materials, procurement materials, grant applications, public authority materials, sponsor materials, provider materials, or media materials without authorization;
c) implying endorsement, recognition, certification, procurement approval, finance-readiness, insurance-readiness, public finance approval, rating, investment suitability, bankability, public authority adoption, official status, or provider preference;
d) using confidential or controlled materials outside approved access class;
e) distributing draft, superseded, withdrawn, restricted, privileged, cyber-sensitive, finance-sensitive, public authority-sensitive, protected, or non-public materials;
f) using public-good software or technical baselines to create proprietary lock-in, provider preference, procurement advantage, or certification overclaim;
g) misusing proof receipts, ledger entries, role keys, smart licenses, dashboards, maps, AI outputs, digital twins, DePIN records, AI-RAN signals, O-RAN signals, or sensor outputs as authority; or
h) refusing to correct, withdraw, retract, takedown, or clarify misuse after notice.
Removal under this subsection may be accompanied by public clarification, takedown demand, contract action, legal response, access revocation, or correction record.
111.13 Removal for Public Authority, Finance, Certification, Procurement, Recognition, or Provider-Preference Overclaim. A director may be removed for any material public authority, finance, certification, procurement, recognition, or provider-preference overclaim, whether made publicly, privately, in controlled rooms, in public authority settings, in investor or capital-reader settings, in sponsorship settings, in provider settings, in grant settings, in procurement settings, or in Nexus-compatible contexts.
Overclaim includes, without limitation, representing or implying that GCRI US:
a) is a public authority, regulator, emergency command body, public warning authority, procurement authority, certification body, accreditation body, recognition body, finance-readiness authority, rating agency, investment adviser, broker, dealer, finder, bank, lender, insurer, underwriter, public finance approver, national company, Project SPV, provider, operator, or enterprise execution vehicle;
b) has approved, certified, recognized, rated, financed, insured, procured, endorsed, selected, guaranteed, or validated a person, product, provider, project, public authority, national company, Project SPV, technology, dataset, model, dashboard, AI-RAN component, O-RAN component, DePIN system, DLT system, blockchain system, digital twin, infrastructure asset, or enterprise actor beyond competent records;
c) has issued official public warning, emergency instruction, public health order, evacuation instruction, incident command, public safety directive, regulatory decision, compliance approval, public finance approval, grant approval, procurement approval, investment recommendation, underwriting basis, or insurance approval;
d) can sell or provide public authority access, finance-readiness, recognition, certification, maturity standing, Docket status, Grid status, Nexus-compatible status, provider preference, or sponsor influence; or
e) can bind GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Standards, public authorities, consortiums, national companies, Project SPVs, providers, sponsors, hosts, funders, universities, laboratories, or enterprise actors without express authority.
A director who causes, knowingly permits, or refuses to correct such overclaim may be removed.
111.14 Removal for Conduct Inconsistent With Public-Benefit Purpose, Non-Execution, or Role Separation. A director may be removed for conduct materially inconsistent with the Corporation’s public-benefit purpose, nonprofit character, non-distribution rule, tax-exempt or tax-exempt-compatible posture, non-execution boundary, GCRI / GRF / GRA role separation, public-good stack and enterprise stack separation, public authority boundary, finance boundary, certification boundary, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, or correctionability.
Such conduct may include, without limitation:
a) attempting to convert GCRI US into an execution vehicle;
b) directing enterprise delivery, deployment, operations, ownership, financing, insurance, procurement, certification, recognition, or capital placement;
c) collapsing GCRI US with GCRI Canada, GRF, GRA, Nexus entities, national companies, Project SPVs, providers, sponsors, hosts, or public authorities;
d) allowing sponsor, donor, funder, provider, host, public authority, investor, insurer, lender, national company, Project SPV, political, founder, university, laboratory, or enterprise interests to control governance;
e) suppressing evidence, methods, research integrity, public-safe limitations, safeguards, protected knowledge, or correction processes;
f) treating AI outputs, dashboards, maps, proof receipts, digital twins, DePIN records, DLT records, AI-RAN signals, sensor signals, or automated scores as final authority without competent records and human review;
g) disregarding civil rights, accessibility, Tribal / Indigenous protocols, community safeguards, protected knowledge, grievance, remedy, protected participation, or non-retaliation; or
h) materially undermining the Corporation’s public trust or legal separateness.
Removal under this subsection shall be available even where no single financial conflict exists, because mission breach and role collapse may be structural, reputational, technical, or institutional.
111.15 Vacancy. A vacancy on the Board shall exist when a director’s seat is unfilled because of expiration without renewal, resignation, removal, death, incapacity, disqualification, failure to qualify, failure to consent, increase in authorized number of directors, creation of a new Board seat, invalid election or appointment, voided appointment, or other lawful cause.
The existence of a vacancy shall not invalidate actions lawfully taken by the remaining directors if the remaining directors have authority and quorum under applicable law, the Articles or Certificate, this Bylaw, and the relevant meeting or consent rules.
A vacancy shall be recorded promptly in the Director Register and Board records, including:
a) seat affected;
b) cause of vacancy;
c) effective date;
d) whether the vacancy affects quorum;
e) whether the vacancy affects committee composition;
f) whether the vacancy affects required skill, independence, public authority, data / AI / cyber, safeguards, finance-boundary, legal, tax, audit, or Nexus interface oversight;
g) interim governance measures;
h) successor process; and
i) access revocation, transition, and public-description updates.
Vacancy management shall preserve continuity without allowing informal substitutes, shadow directors, external controllers, or unauthorized representatives.
111.16 Filling Vacancies. Vacancies shall be filled in the manner required or permitted by applicable law, the Articles or Certificate, this Bylaw, any lawful member approval requirement, and competent corporate record. Where the Board is permitted to fill a vacancy, the Board may appoint a successor director after eligibility, conflict, independence, fit-and-proper, consent, acknowledgment, and records requirements are satisfied.
Vacancy-filling shall consider:
a) legal minimum and maximum director number;
b) quorum continuity;
c) committee continuity;
d) Board composition and skills needs;
e) independence and anti-capture needs;
f) diversity of expertise, geography, states, territories, public-interest perspective, and lived experience;
g) all-states-and-territories and North America anchor responsibilities;
h) evidence, methods, observability, ontology, technical truth, public-good software, data / AI / cyber, public authority, safeguards, finance-boundary, legal, tax, and Nexus interface competence;
i) unresolved conflicts or capture risks; and
j) the remaining term, partial term, renewal eligibility, and term-limit treatment for the successor.
No vacancy shall be filled by sponsor designation, donor designation, provider designation, public authority designation, founder designation, GCRI Canada designation, GRF designation, GRA designation, Nexus designation, national company designation, Project SPV designation, capital actor designation, or enterprise-stack designation unless such designation right is expressly lawful, compatible with fiduciary duty and independence, and recorded in a governing instrument.
111.17 Remaining Directors’ Authority Where Quorum Remains. Where one or more vacancies exist but the remaining directors constitute a quorum, the remaining directors may continue to exercise Board authority, subject to applicable law, the Articles or Certificate, this Bylaw, reserved matters, member approval requirements, conflict rules, recusal rules, and Board process requirements.
The remaining directors shall not use vacancy conditions to:
a) avoid lawful member rights;
b) rush reserved matters without adequate review;
c) entrench incumbents;
d) weaken independence review;
e) approve material sponsor, provider, donor, funder, host, public authority, capital actor, national company, Project SPV, GCRI Canada, GRF, GRA, Nexus, or enterprise-stack matters without proper composition and conflict controls;
f) bypass required committee review where material;
g) weaken data / AI / cyber, safeguards, public-safe publication, public authority, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, or sponsor non-control controls; or
h) create a de facto emergency governance mode without records.
Where vacancies materially impair Board competence or oversight, the remaining directors shall prioritize succession and may defer non-urgent reserved matters until appropriate Board capacity is restored.
111.18 Minimum Board Continuity Where Quorum Does Not Remain. Where vacancies, resignations, removals, recusals, disqualifications, incapacity, death, access restrictions, or other conditions leave the Board without quorum, the remaining director or directors may act only to the extent permitted by applicable law, the Articles or Certificate, this Bylaw, and emergency governance principles to restore lawful governance, preserve corporate existence, protect records, prevent harm, maintain essential compliance, and fill vacancies.
Minimum Board continuity actions may include, where lawful:
a) calling a meeting for vacancy-filling;
b) approving limited actions necessary to appoint successor directors;
c) preserving records and assets;
d) maintaining registered agent, registered office, insurance, tax, filing, and banking continuity;
e) maintaining payroll, critical contracts, cyber protections, repository security, data protection, and legal compliance;
f) imposing temporary holds, access restrictions, publication freezes, repository locks, or controlled-room lockdowns;
g) preserving privilege and confidentiality;
h) responding to urgent legal, tax, cyber, data breach, AI incident, public authority confusion, safeguards, protected knowledge, public-safe publication, or regulatory-perimeter risk; and
i) seeking court, member, counsel, regulatory, or other lawful assistance where necessary.
No minimum continuity authority shall be used to approve non-urgent reserved matters, change mission lock, amend the Bylaw, alter non-execution, create public authority meaning, approve finance-readiness, certify, recognize, procure, select providers, execute enterprise functions, or bind the Corporation beyond what is necessary to restore lawful governance and protect the Corporation.
111.19 Emergency Succession. The Board may adopt an emergency succession plan to address sudden loss, resignation, removal, incapacity, disqualification, death, unavailability, cyber lockout, communications failure, legal restriction, public authority emergency, disaster, conflict recusal, or other disruption affecting directors, officers, committee chairs, records custodians, repository custodians, controlled-room custodians, public authority interface leads, data / AI / cyber leads, safeguards leads, or other critical governance roles.
Emergency succession may include:
a) temporary chair designation;
b) emergency meeting procedures;
c) quorum restoration steps;
d) interim committee leadership;
e) interim records custody;
f) interim signing authority within limits;
g) interim banking authority within limits;
h) interim access control authority;
i) interim data / AI / cyber incident authority;
j) interim public-safe publication hold authority;
k) interim public authority interface restriction authority;
l) interim safeguards stop-the-line authority;
m) interim repository lock or release suspension authority;
n) successor director nomination pipeline;
o) counsel and compliance escalation; and
p) ratification and sunset requirements.
Emergency succession shall be time-limited, record-supported, proportionate, and bounded by non-execution, role separation, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, and correctionability.
111.20 Board Succession Plan. The Board shall maintain a Board succession plan appropriate to the Corporation’s size, complexity, public-benefit mission, United States all-states-and-territories posture, North America anchor role, technical responsibilities, public authority learning activities, public-good software and technical asset stewardship, data / AI / cyber responsibilities, safeguards responsibilities, and Nexus interface obligations.
The Board succession plan may address:
a) director term expiration calendar;
b) skills matrix;
c) committee leadership pipeline;
d) Chair and Vice-Chair succession;
e) officer succession interface;
f) emergency director replacement;
g) director recruitment sources;
h) independence and anti-capture criteria;
i) diversity of expertise, geography, states, territories, public authority literacy, community perspective, technical competence, safeguards competence, and public-interest viewpoint;
j) conflicts and affiliation concentration limits;
k) onboarding and training pathway;
l) continuity packs;
m) public description updates;
n) transition and handover process;
o) post-service role options; and
p) periodic review.
The succession plan shall not create a right to appointment, designated seat, sponsor seat, provider seat, donor seat, funder seat, public authority seat, GCRI Canada seat, GRF seat, GRA seat, Nexus seat, national company seat, Project SPV seat, university seat, laboratory seat, community seat, or enterprise-stack seat unless separately and lawfully adopted.
111.21 Resignation, Removal, Vacancy, and Succession Records. The Corporation shall maintain Resignation, Removal, Vacancy, and Succession Records sufficient to demonstrate that Board departures, removals, vacancies, vacancy-filling, continuity measures, and succession processes have been handled lawfully, consistently, defensibly, and in accordance with this Bylaw.
Such records shall include, as applicable:
a) resignation notices, acknowledgments, effective-date records, acceptance records where required, transition records, handover records, post-service confidentiality records, and access closeout records;
b) removal notices, removal materials, investigation records, eligibility records, conflict records, independence records, misconduct records, fiduciary review records, counsel review records, committee recommendations, Board determinations, member records where applicable, vote records, recusals, abstentions, final decisions, and effective-date records;
c) vacancy records, vacancy cause records, quorum impact records, committee impact records, skill impact records, public authority interface impact records, data / AI / cyber impact records, safeguards impact records, finance-boundary impact records, and Nexus interface impact records;
d) vacancy-filling records, nomination records, candidate review records, eligibility review records, conflict review records, independence review records, fit-and-proper review records, consent records, acknowledgment records, appointment or election records, term records, and Director Register updates;
e) minimum continuity records, emergency succession records, continuity exception records, mission-critical continuity extension records, interim authority records, ratification records, sunset records, and post-event review records;
f) access revocation records, signing authority revocation records, banking authority revocation records, repository access records, controlled-room access records, public authority room access records, data-room access records, Board portal access records, and communications-list access records;
g) public listing updates, biography updates, website updates, public-description records, sponsor / provider / public authority reference corrections, GRF / GRA / Nexus reference corrections, correction records, withdrawal records, takedown records, and public clarification records;
h) legal hold records, return records, deletion records, transfer records, sealing records, archive records, secure disposal records, and preservation records;
i) disputes, objections, challenges, defects, ratifications, voided actions, corrective actions, privilege determinations, confidentiality determinations, public-safe notice decisions, and final dispositions; and
j) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that a Board seat shall never become vacant, filled, preserved, abandoned, transferred, captured, or continued by implication. Director departure and succession shall be record-supported, legally bounded, fiduciary, public-benefit preserving, non-executing, role-separated, anti-capture, public-safe, access-controlled, and correctionable. No resignation, removal, vacancy, holdover, emergency succession, or successor appointment shall be used to create sponsor control, provider preference, public authority confusion, finance-readiness meaning, certification meaning, procurement meaning, recognition meaning, Nexus role collapse, or enterprise execution authority.
Section 112. Board Meetings
112.1 Regular Meetings. The Board shall hold regular meetings at such times, places, intervals, and by such methods as the Board may determine by this Bylaw, Board resolution, annual calendar, governance policy, notice, or other competent Board record. Regular meetings shall be used to discharge the Board’s fiduciary, strategic, legal, financial, technical, public-benefit, public-safe, and oversight responsibilities in a disciplined, documented, and continuing manner.
Regular meetings may address, without limitation:
a) public-benefit mission, mission lock, nonprofit character, tax-exempt or tax-exempt-compatible posture, non-distribution, private benefit, and inurement controls;
b) strategy, annual plan, annual budget, financial reports, restricted funds, grants, donations, sponsorships, subscriptions, fees, cost recovery, in-kind support, support concentration, and anti-capture controls;
c) evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, technical asset stewardship, secure release, and public-safe publication;
d) data governance, privacy, AI governance, cybersecurity, secure compute, verifiable compute, verifiable intelligence, model registers, inference records, compute workload records, repositories, access controls, cyber incidents, AI incidents, and business continuity;
e) public authority learning, regulator-listening participation, public finance reader participation, emergency-management participant participation, public infrastructure operator participation, public authority capacity classification, public authority reference controls, and public authority boundary discipline;
f) community safeguards, Tribal and Indigenous protocol respect, Indigenous data safeguards, protected knowledge, local and territorial knowledge, civil rights, accessibility, public-safe mapping, grievance, remedy, protected participation, non-retaliation, and stop-the-line matters;
g) GCRI Canada interfaces, The Global Risks Forum (GRF) interfaces, The Global Risks Alliance (GRA) interfaces, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, national and regional consortiums, national companies, Project SPVs, qualified providers, sponsors, hosts, public authorities, universities, laboratories, communities, and enterprise-stack interfaces;
h) non-execution, role separation, public-good stack and enterprise stack separation, public authority boundaries, finance boundaries, securities, investment adviser, broker-dealer, finder, banking, lending, insurance, underwriting, rating, public finance, procurement, certification, recognition, provider-neutrality, and sponsor non-control boundaries; and
i) legal, tax, audit, compliance, risk, litigation, investigations, regulatory-perimeter matters, sanctions, export controls, controlled technology, competition, antitrust, professional boundaries, records, correctionability, and validity-by-record.
A regular meeting shall not be treated as informal merely because it occurs on a recurring calendar. Each regular meeting shall remain subject to notice, quorum, agenda, materials, conflict, recusal, confidentiality, records, public-safe, and applicable legal requirements.
112.2 Special Meetings. Special meetings of the Board may be called by the Chair, any Vice-Chair, the President, the Executive Director or Chief Executive Officer where authorized, the Secretary, any number or percentage of directors authorized by law or Board policy, or any other person or body authorized by the Articles or Certificate, this Bylaw, Board resolution, or applicable law.
Special meetings may be called to address matters that should not await the next regular meeting, including:
a) urgent legal, tax, filing, registered agent, qualification, charitable solicitation, grant, public authority, public-safe publication, or corporate-status matters;
b) resignation, removal, vacancy, succession, officer appointment, officer suspension, committee matter, delegation matter, or authority-matrix matter;
c) budget variance, restricted fund issue, material contract, major grant, major donation, sponsorship, in-kind support, private benefit concern, or support concentration issue;
d) data breach, AI incident, cyber incident, repository compromise, key compromise, credential compromise, software release issue, technical asset issue, controlled-room issue, or evidence integrity issue;
e) public authority confusion, emergency command overclaim, public warning overclaim, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider-preference issue, sponsor-control issue, or Nexus role-collapse issue;
f) protected knowledge breach, community harm concern, civil-rights concern, accessibility concern, Indigenous protocol issue, grievance, remedy, protected participation, non-retaliation, or stop-the-line escalation;
g) litigation, investigation, subpoena, regulatory inquiry, public authority inquiry, media issue, public statement issue, correction, supersession, withdrawal, retraction, takedown, or public clarification; and
h) any Board reserved matter requiring action before the next regular meeting.
A special meeting shall be limited to the purpose or purposes stated in the notice unless all directors entitled to notice are present or waive notice and applicable law permits consideration of additional matters. No special meeting shall be used to bypass regular governance discipline, suppress dissent, avoid materials review, weaken recusal controls, or rush a matter for sponsor, provider, donor, funder, public authority, founder, Nexus, GCRI Canada, GRF, GRA, national company, Project SPV, or enterprise-stack convenience.
112.3 Annual Meeting. The Board shall hold an annual meeting, or shall designate one regular meeting each year as the annual Board meeting, for the purpose of reviewing and taking such annual actions as are necessary or appropriate for lawful, serious, and accountable nonprofit governance.
The annual meeting may include, without limitation:
a) review of the Corporation’s public-benefit mission, mission lock, nonprofit character, non-distribution rule, tax-exempt or tax-exempt-compatible posture, and public-good technical institution role;
b) review of annual strategy, annual plan, annual budget, financial statements, financial controls, restricted funds, support concentration, grants, donations, sponsorships, subscriptions, fees, cost recovery, and anti-capture discipline;
c) election, appointment, renewal, non-renewal, resignation, removal, vacancy-filling, or confirmation of directors where applicable;
d) appointment, renewal, removal, or confirmation of officers where applicable;
e) review of Board composition, skills matrix, independence, conflicts, term limits, succession, training, evaluation, and committee assignments;
f) review of committees, councils, advisory bodies, working groups, expert panels, Nexus Competence Cells, controlled rooms, clean rooms, data rooms, public authority rooms, and program bodies;
g) review of legal compliance, state nonprofit compliance, federal tax compliance, state and territorial registrations, charitable solicitation, foreign qualification, lobbying, political activity, government ethics, grant compliance, procurement integrity, sanctions, export controls, controlled technology, competition, antitrust, privacy, AI, cybersecurity, research ethics, employment, accessibility, civil rights, and professional boundary matters;
h) review of evidence, methods, observability, ontology, Truth Engine methods, public-good R&D, public-good software, open technical baselines, technical assets, secure release, repository discipline, public-safe publication, correctionability, and validity-by-record;
i) review of public authority learning, public authority capacity classifications, public authority references, public-safe notices, regulator-listening rooms, public finance reader rooms, emergency-management learning, and public infrastructure operator interfaces;
j) review of community safeguards, Tribal and Indigenous protocol, Indigenous data safeguards, protected knowledge, civil rights, accessibility, public-safe mapping, grievance, remedy, protected participation, non-retaliation, and stop-the-line records;
k) review of GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cell, consortium, national company, Project SPV, provider, sponsor, host, public authority, university, laboratory, community, and enterprise-stack interface records; and
l) adoption or confirmation of annual resolutions, delegation matrices, authority matrices, policy priorities, repository controls, gazette controls, notice controls, training plans, risk plans, correction plans, and annual record certifications.
Failure to hold an annual meeting at a particular time shall not invalidate otherwise lawful Board action, but the Board shall correct the omission promptly, record the reason for delay, and take any required annual actions as soon as practicable.
112.4 Emergency Meetings. Emergency meetings may be called when immediate Board consideration is necessary or highly advisable to protect the Corporation, its lawful existence, public-benefit mission, nonprofit status, tax-exempt or tax-exempt-compatible posture, records, assets, people, data, systems, public authority relationships, safeguards, technical assets, public trust, or Nexus-compatible role.
Emergency meeting triggers may include, without limitation:
a) data breach, cyber incident, AI incident, model failure, agentic AI incident, repository compromise, credential compromise, key compromise, technical asset compromise, controlled technology issue, secure-release failure, vulnerability disclosure, or infrastructure-sensitive incident;
b) public authority confusion, public warning overclaim, emergency command overclaim, regulator confusion, official-capacity misstatement, public finance overclaim, procurement overclaim, certification overclaim, recognition overclaim, rating overclaim, finance-readiness overclaim, provider-preference issue, or sponsor-control issue;
c) protected knowledge breach, Indigenous protocol breach, community harm, civil-rights issue, accessibility failure, retaliation, harassment, grievance, remedy failure, public-safe mapping risk, or stop-the-line escalation;
d) urgent resignation, removal, vacancy, quorum loss, officer unavailability, succession failure, committee failure, delegation failure, records custodian unavailability, or governance continuity issue;
e) urgent legal deadline, tax deadline, filing deadline, grant deadline, litigation event, regulatory inquiry, public authority inquiry, subpoena, enforcement matter, sanctions or export-control issue, competition issue, procurement-integrity issue, or government ethics issue;
f) urgent publication error, false public claim, misinformation risk, public-safe report issue, dashboard issue, map issue, proof receipt issue, AI output issue, digital twin issue, DLT or blockchain record issue, DePIN record issue, AI-RAN or O-RAN signal issue, or sensor signal issue;
g) urgent financial control concern, fraud concern, bank account issue, restricted fund breach, private benefit concern, inurement concern, major contract risk, donor restriction issue, sponsorship-control issue, or public-good asset risk; and
h) any other matter that, if not addressed promptly, may materially impair the Corporation’s lawful governance, mission lock, non-execution boundary, role separation, records integrity, public-safe operation, or correctionability.
Emergency meetings may be convened on shortened notice to the extent permitted by law and this Bylaw. Emergency procedure shall not authorize the Board to exercise prohibited functions, weaken non-execution, create public authority status, issue official public warnings, command emergencies, conduct finance execution, certify, procure, recognize, select providers, confer finance-readiness, or operate enterprise execution.
112.5 In-Person Meetings. The Board may hold meetings in person at the principal office, registered office, approved governance seat, public-benefit meeting location, host institution, university, laboratory, public authority learning venue, controlled-room facility, conference venue, or other location approved by the Board or authorized person, provided that the location is lawful, accessible where required, secure where needed, and consistent with confidentiality, public-safe, data / AI / cyber, public authority, protected knowledge, and safeguards requirements.
In-person meeting arrangements shall consider:
a) director access and participation;
b) accessibility and reasonable accommodation;
c) confidentiality and privilege;
d) physical security;
e) data, device, network, and cyber security;
f) handling of controlled, protected, privileged, cyber-sensitive, infrastructure-sensitive, finance-sensitive, personal, Tribal / Indigenous, local, territorial, cultural, environmental, or protected knowledge materials;
g) public authority capacity classification where public authority participants or observers are present;
h) competition and antitrust meeting discipline where competitors or market actors are present;
i) public-safe signage, badges, room rules, entry controls, no-recording rules, no-download rules, or controlled-room rules where applicable; and
j) records, attendance, quorum, and materials custody.
No in-person meeting location shall create apparent public authority adoption, sponsor control, provider preference, public funding approval, procurement meaning, certification meaning, recognition meaning, finance-readiness meaning, or Nexus-compatible status merely because the meeting occurs at or with a public authority, sponsor, provider, host, university, laboratory, funder, or Nexus-related location.
112.6 Virtual Meetings. The Board may hold meetings by telephone, video conference, secure collaboration platform, or other electronic means to the extent permitted by applicable law, the Articles or Certificate, this Bylaw, and Board policy. Virtual meetings shall be conducted so that participating directors may hear, speak, deliberate, vote, and otherwise participate in real time or in such manner as lawfully satisfies meeting requirements.
Virtual meeting systems shall be selected and operated with regard to:
a) identity verification;
b) access control;
c) confidentiality;
d) privilege protection;
e) secure transmission;
f) recording restrictions;
g) screen-sharing controls;
h) document access controls;
i) chat and transcript retention rules;
j) prevention of unauthorized AI transcription, automated summarization, model training, or data extraction;
k) device and network security;
l) director accessibility and reasonable accommodation;
m) handling of public authority-sensitive, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercial, personal, Tribal / Indigenous, community-protected, local, territorial, cultural, environmental, or protected knowledge materials; and
n) records sufficient to evidence notice, attendance, quorum, deliberation, votes, abstentions, recusals, decisions, and action items.
A virtual meeting shall not be invalid solely because directors participate remotely, if permitted by law and conducted in accordance with applicable requirements. No person shall attend a virtual Board meeting unless authorized and admitted under the applicable access class.
112.7 Hybrid Meetings. The Board may hold hybrid meetings with some participants in person and others participating by virtual or electronic means, provided that all directors entitled to participate can meaningfully hear, speak, deliberate, vote, and receive authorized materials in a manner consistent with applicable law and this Bylaw.
Hybrid meetings shall be administered to avoid unequal access, side-channel deliberation, unauthorized attendance, identity ambiguity, confidentiality leakage, public authority confusion, or incomplete records. The Chair, Secretary, or meeting custodian shall ensure, as applicable:
a) one official meeting is constituted;
b) quorum is calculated accurately;
c) all participating directors are identified;
d) virtual and in-person participants have equivalent access to authorized materials;
e) recused directors are excluded from relevant portions regardless of location;
f) confidential and controlled materials are handled consistently across physical and virtual settings;
g) votes, abstentions, recusals, dissents where permitted, and action items are captured accurately;
h) no unauthorized recording, transcription, AI summarization, screen capture, or redistribution occurs;
i) public authority, finance, certification, procurement, recognition, provider, sponsor, and safeguards boundaries are preserved; and
j) technical failures are addressed by pause, reconnection, adjournment, continuation, or exclusion from affected action where required.
Where a hybrid meeting failure materially impairs a director’s lawful participation on a material matter, the Board shall defer, repeat, ratify, or correct the affected action as appropriate.
112.8 Executive Sessions. The Board may meet in executive session, with only directors and authorized persons present, to consider confidential, privileged, sensitive, strategic, personnel, legal, audit, risk, conflict, independence, investigation, public authority, finance-boundary, data / AI / cyber, safeguards, protected knowledge, or Board governance matters.
Executive sessions may be used for, without limitation:
a) director performance, director renewal, director removal, officer performance, officer compensation, officer removal, succession, and Board evaluation;
b) legal advice, litigation, investigation, regulatory-perimeter review, enforcement matter, settlement, subpoena, legal hold, privilege, or counsel instruction;
c) conflicts, related-party transactions, recusals, independence, anti-capture, sponsor-control risk, provider-preference risk, donor-control risk, funder-control risk, public authority pressure, or enterprise-stack influence;
d) audit, financial controls, fraud, restricted funds, grants, sponsorships, tax, charitable solicitation, private benefit, inurement, or insurance;
e) cyber incidents, AI incidents, data breaches, repository compromise, credential issues, software vulnerabilities, controlled technology, export controls, sanctions, national security sensitivity, or secure-release risks;
f) public authority-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, personal, health-sensitive, Tribal / Indigenous, community-protected, local, territorial, cultural, environmental, or protected knowledge matters;
g) public-safe publication, correction, withdrawal, retraction, takedown, dispute, evidence challenge, or public clarification; and
h) matters requiring candid Board deliberation.
No person shall be present in executive session unless the Board authorizes attendance and the person’s presence is consistent with confidentiality, privilege, conflict, recusal, independence, public authority, data / AI / cyber, safeguards, and records requirements. Executive-session minutes may be limited, sealed, privileged, or separately retained where lawful and appropriate.
112.9 In Camera Sessions. The Board may meet in camera without officers, employees, contractors, advisors, sponsors, providers, public authority participants, observers, or other non-directors present, except for counsel, auditors, independent reviewers, or other persons specifically invited by the Board for a defined purpose.
In camera sessions may be used to protect Board independence, candid fiduciary deliberation, privilege, investigation integrity, director-only judgment, officer accountability, committee accountability, sponsor and provider non-control, public authority independence, and anti-capture discipline.
In camera sessions may address, without limitation:
a) officer performance and compensation;
b) director independence and conflicts;
c) Board composition and succession;
d) concerns about management, staff, contractors, advisors, contributors, sponsors, providers, hosts, donors, funders, public authorities, GCRI Canada, GRF, GRA, Nexus entities, national companies, Project SPVs, or enterprise actors;
e) legal advice requiring director-only deliberation;
f) whistleblower, grievance, retaliation, harassment, civil rights, accessibility, protected knowledge, or safeguards matters;
g) sponsor, provider, donor, funder, host, public authority, political, founder, or enterprise pressure; and
h) Board integrity, accountability, and correction matters.
The Board may record in camera sessions in general minutes, confidential minutes, privileged records, or sealed records, as lawful and appropriate. The existence of an in camera session shall not be used to conceal unlawful action, suppress required records, avoid accountability, or evade correctionability.
112.10 Controlled-Room Board Sessions. The Board may hold a meeting or portion of a meeting as a controlled-room Board session where the materials, subject matter, participants, systems, or risks require enhanced access controls, confidentiality, logging, no-download restrictions, chain-of-custody, public authority restrictions, clean-room controls, evidence-room controls, data-room controls, cybersecurity controls, protected knowledge controls, or public-safe safeguards.
Controlled-room Board sessions may be required for:
a) sensitive evidence, source-lineage, provenance, verification, validation, confidence, uncertainty, proof receipt, Docket-support, Grid-support, GRF-facing input, or GRA-facing input materials;
b) public authority-sensitive materials, regulator-listening materials, public finance reader materials, emergency-management learning materials, public infrastructure operator materials, or official-capacity references;
c) cyber-sensitive, infrastructure-sensitive, controlled-technology, export-control, sanctions, national security, vulnerability, key, credential, repository, SBOM, secure-release, or incident-response materials;
d) personal information, health-sensitive data, rights-bearing data, children’s data, community-protected data, Tribal / Indigenous data, local and territorial knowledge, cultural knowledge, environmental knowledge, protected knowledge, or public-safe mapping materials;
e) finance-sensitive, commercially sensitive, procurement-sensitive, sponsor-sensitive, donor-sensitive, provider-sensitive, grant-sensitive, restricted fund, or private-benefit materials;
f) confidential research, human-subjects research, peer review, model review, red-team review, publication review, correction, withdrawal, retraction, or takedown materials; and
g) any matter that cannot safely be handled in an ordinary Board meeting environment.
A controlled-room Board session shall be governed by written or recorded room rules addressing participant admission, identity verification, access class, permitted devices, recording restrictions, AI-use restrictions, download restrictions, note-taking, exhibit handling, chain-of-custody, logging, retention, closeout, correction, and breach response. Controlled-room status shall not create public authority meaning, finance-readiness meaning, certification meaning, procurement meaning, recognition meaning, provider preference, sponsor control, or operational execution authority.
112.11 Confidential Sessions. The Board may designate any meeting, portion of a meeting, agenda item, record, material, discussion, deliberation, vote, executive session, in camera session, controlled-room session, or Board output as confidential, restricted, privileged, sealed, internal, controlled, public-safe limited, or otherwise access-classified.
Confidential sessions may be used to protect:
a) attorney-client privilege and work product;
b) confidential Board deliberation;
c) personal information and personnel matters;
d) cyber-sensitive and infrastructure-sensitive information;
e) finance-sensitive and commercially sensitive information;
f) public authority-sensitive information;
g) controlled technology, export-control, sanctions, and national security sensitivity;
h) research confidentiality and peer-review integrity;
i) data, AI, model, compute, repository, key, credential, technical asset, and secure-release controls;
j) Tribal / Indigenous, community-protected, local, territorial, cultural, environmental, and protected knowledge;
k) grievance, remedy, whistleblower, protected participation, non-retaliation, civil-rights, accessibility, and safeguards matters; and
l) correction, withdrawal, retraction, takedown, investigation, and public-safe publication decisions.
Confidential designation shall be respected by directors and all authorized participants. Confidentiality shall not be used to hide unlawful conduct, avoid mandatory reporting, defeat member rights where applicable, suppress required correction, obstruct investigation, or prevent lawful oversight. Confidential session records shall be retained, sealed, accessed, disclosed, deleted, or archived only in accordance with law, records policy, privilege, confidentiality, legal hold, data / AI / cyber controls, and this Bylaw.
112.12 Public or Stakeholder Sessions Where Approved. The Board may convene or participate in public, stakeholder, learning, listening, information, consultation, public-safe reporting, public authority learning, community, academic, technical, or ecosystem-facing sessions where approved by the Board or authorized body and where consistent with law, public-benefit purpose, non-execution, confidentiality, privilege, public-safe communication, data / AI / cyber controls, safeguards, and boundary discipline.
Public or stakeholder sessions may be used for:
a) public-benefit education;
b) public-safe summaries;
c) technical literacy;
d) evidence literacy;
e) public authority learning;
f) community listening;
g) Tribal or Indigenous protocol-respecting engagement where lawfully and respectfully structured;
h) public-safe reporting;
i) academy, fellowship, training, or workforce formation;
j) consultation on methods, controlled vocabulary, public-safe mapping, accessibility, safeguards, or public-good software;
k) non-confidential annual or governance summaries; and
l) ecosystem awareness.
Public or stakeholder sessions shall not be used to conduct confidential Board deliberation, make Board decisions unless lawfully noticed and recorded, disclose restricted materials, create public authority action, issue public warning, direct emergency operations, determine finance-readiness, certify, recognize, approve procurement, select providers, sell public authority access, create sponsor control, or conduct enterprise execution.
Public or stakeholder session materials shall be reviewed for public-safe claims, controlled vocabulary, non-reliance language, data / AI / cyber risks, protected knowledge risks, public authority boundary risks, finance-boundary risks, certification-boundary risks, procurement risks, recognition risks, provider-neutrality risks, sponsor non-control, and correction pathways.
112.13 State, Territorial, Tribal, Public Authority, or North America Interface Sessions Where Approved. The Board may convene or participate in sessions focused on United States state, territorial, District of Columbia, Tribal, Indigenous, local, regional, cross-border, or North America interfaces where such sessions are lawful, properly classified, public-safe, and consistent with the Corporation’s all-states-and-territories posture and North America anchor role.
Such sessions may address, without limitation:
a) state or territorial localization;
b) District of Columbia interface matters;
c) Tribal and Indigenous protocol respect;
d) local, county, municipal, metropolitan, port, utility, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, and infrastructure interfaces;
e) North America coordination with GCRI Canada and other lawful interfaces;
f) cross-border evidence architecture;
g) public authority learning;
h) public authority capacity classification;
i) public-safe observability methods;
j) data, AI, cyber, privacy, sovereign compute, cross-border transfer, protected knowledge, and safeguards issues;
k) Nexus Observatory, Nexus Standards, Nexus Network, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cell, consortium, national company, Project SPV, provider, sponsor, host, university, laboratory, community, and enterprise-stack interfaces; and
l) compatibility notes, divergence logs, equivalence notes, and correction pathways.
No state, territorial, Tribal, public authority, or North America interface session shall imply that GCRI US has sovereign authority, treaty authority, regulatory authority, public finance authority, public warning authority, emergency command authority, procurement authority, certification authority, recognition authority, finance-readiness authority, or enterprise execution authority. Public authority participation shall be capacity-classified and shall not be represented as official adoption, endorsement, funding approval, procurement approval, sovereign obligation, public-private partnership, or public authority decision unless a competent public authority record expressly provides otherwise.
112.14 Meeting Calendar. The Board may adopt an annual or rolling meeting calendar identifying regular meeting dates, annual meeting date, committee reporting windows, budget cycle, audit or financial review cycle, tax and filing deadlines, annual strategy review, annual compliance review, annual conflict and independence review, annual training cycle, annual Board evaluation, annual policy review, annual risk review, and such other governance milestones as the Board considers appropriate.
The meeting calendar may include, without limitation:
a) regular Board meetings;
b) annual meeting;
c) budget approval meeting;
d) annual financial review, audit, compilation, or tax review meeting;
e) annual strategy and plan meeting;
f) annual conflict, independence, and director renewal review;
g) annual officer review;
h) committee reporting schedule;
i) public authority learning review schedule;
j) data / AI / cyber and privacy review schedule;
k) research integrity and public-safe publication review schedule;
l) safeguards and protected knowledge review schedule;
m) GCRI Canada, GRF, GRA, Nexus, consortium, provider, sponsor, host, public authority, university, laboratory, community, and enterprise interface review schedule;
n) repository, technical asset, public-good software, open technical baseline, secure-release, and cyber resilience review schedule;
o) state, territorial, Tribal, and North America localization review schedule;
p) risk, incident, correction, supersession, withdrawal, retraction, takedown, and archive review schedule; and
q) emergency governance readiness review.
The meeting calendar shall guide Board discipline but shall not prevent the calling of special or emergency meetings. Failure to place a matter on the calendar shall not waive Board authority or responsibility.
112.15 Meeting Records. The Corporation shall maintain Meeting Records sufficient to demonstrate that Board meetings have been called, noticed, convened, conducted, adjourned, continued, recorded, and closed in accordance with applicable law, the Articles or Certificate, this Bylaw, Board policy, confidentiality obligations, records policy, and validity-by-record.
Meeting Records shall include, as applicable:
a) annual meeting records, regular meeting records, special meeting records, emergency meeting records, executive session records, in camera session records, controlled-room Board session records, confidential session records, public session records, stakeholder session records, state interface session records, territorial interface session records, Tribal interface session records, public authority session records, and North America interface session records;
b) meeting notices, waivers of notice, proofs of delivery, call records, agenda records, calendar records, meeting materials, supplemental materials, late materials, consent agenda materials, public-safe versions, controlled versions, privileged versions, and sealed versions;
c) attendance records, identity verification records, access records, quorum records, recusal records, abstention records, vote records, written consent records, electronic participation records, director participation limitations, technology failure records, and meeting continuation or adjournment records;
d) meeting location records, virtual platform records, hybrid meeting records, room rules, controlled-room admission records, no-download room records, clean-room records, data-room records, evidence-room records, public authority room records, device rules, recording restrictions, AI-use restrictions, transcript rules, and chat retention rules;
e) confidentiality classifications, privilege classifications, public authority classifications, data / AI / cyber classifications, protected knowledge classifications, finance-sensitive classifications, infrastructure-sensitive classifications, commercial sensitivity classifications, publication classifications, and access classes;
f) minutes, resolutions, action items, responsible owners, deadlines, follow-up records, ratification records, correction records, supersession records, withdrawal records, retraction records, takedown records, public clarification records, and archive records;
g) Board decisions concerning public-benefit purpose, mission lock, nonprofit character, tax-exempt or tax-exempt-compatible posture, non-execution, role separation, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, and correctionability;
h) records of public authority capacity classifications, public authority references, regulator-listening status, public finance reader status, emergency-management participant status, public infrastructure operator status, official-capacity records, observer records, and public authority notice limitations;
i) records of sponsor, donor, funder, provider, host, university, laboratory, community, Tribal / Indigenous, civil society, media, public-interest, GCRI Canada, GRF, GRA, Nexus, consortium, national company, Project SPV, and enterprise-stack interface discussions where material;
j) records of any meeting defect, notice defect, quorum defect, access defect, confidentiality breach, conflict breach, recusal error, vote error, technical failure, uncontrolled disclosure, public-safe claim error, or authority overclaim, and the correction, ratification, restriction, or other disposition of such defect; and
k) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that Board meetings are fiduciary governance acts, not informal convenings. Every Board meeting shall be lawful, purposeful, properly classified, access-controlled where required, conflict-managed, public-safe, record-supported, and correctionable. No meeting format, venue, public authority presence, sponsor presence, provider presence, virtual platform, controlled room, emergency posture, public session, or Nexus interface shall create authority, reliance, public authority meaning, finance-readiness meaning, certification meaning, procurement meaning, recognition meaning, provider preference, sponsor control, or enterprise execution authority unless the competent authority and governing record expressly authorize the result.
Section 113. Notice, Waiver, Agenda, and Board Materials
113.1 Notice Requirement. Notice of each meeting of the Board shall be given in the manner, within the time, and to the persons required by applicable law, the Articles or Certificate, this Bylaw, Board resolution, Board policy, or other competent governance record. Notice shall be sufficient to permit directors to understand that a Board meeting has been called, identify the date, time, location or electronic access method, meeting type, principal purposes, access requirements, confidentiality classification, and any matter requiring special preparation, recusal, restricted access, higher approval threshold, or reserved-matter treatment.
Notice may be delivered by any lawful and reliable method, including electronic mail, secure Board portal, calendar invitation, courier, personal delivery, postal delivery, secure messaging system, or other recorded means approved by the Board, provided that the method used is reasonably capable of evidencing delivery, timing, recipient, content, and any access instructions.
Notice discipline shall preserve:
a) lawful Board process;
b) director participation;
c) quorum integrity;
d) fiduciary deliberation;
e) conflict disclosure and recusal readiness;
f) confidentiality and privilege;
g) data / AI / cyber security;
h) public authority boundary discipline;
i) finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control boundaries;
j) community safeguards and protected knowledge controls;
k) public-safe publication discipline;
l) validity-by-record; and
m) correctionability.
No meeting notice, calendar entry, agenda label, public announcement, stakeholder invitation, controlled-room admission, public authority room notice, sponsor communication, provider communication, Nexus interface notice, or automated system notification shall create Board authority, director consent, public authority meaning, finance-readiness meaning, certification meaning, procurement meaning, recognition meaning, provider preference, sponsor control, or enterprise execution authority beyond the lawful meeting process and competent records.
113.2 Regular Meeting Notice. Notice of regular Board meetings shall be given in accordance with the meeting calendar, Board policy, standing notice procedure, or other lawful arrangement approved by the Board. Where the Board has adopted a meeting calendar with fixed dates, times, and access methods, that calendar may constitute standing notice to the extent permitted by law and Board policy, provided that directors receive reasonable updates regarding agenda, materials, access classifications, and any material changes.
Regular meeting notice shall identify, as applicable:
a) meeting date;
b) meeting time and time zone;
c) physical location, virtual access method, or hybrid meeting arrangement;
d) meeting type;
e) principal agenda categories;
f) executive session, in camera session, controlled-room session, confidential session, public session, stakeholder session, public authority session, state interface session, territorial interface session, Tribal interface session, or North America interface session components;
g) anticipated reserved matters;
h) anticipated votes or consents;
i) anticipated conflict, recusal, or independence issues;
j) materials access method;
k) confidentiality, privilege, access, data / AI / cyber, protected knowledge, or no-download restrictions;
l) public-safe notice requirements; and
m) contact person for notice, access, accommodation, or materials issues.
A regular meeting may address any matter within Board authority if lawful notice, quorum, materials, recusal, voting, and approval requirements are satisfied. Where a material matter was not reasonably identified before the meeting and directors require additional time for fiduciary review, the Board shall defer, table, condition, continue, or separately notice the matter unless immediate action is lawful and necessary.
113.3 Special Meeting Notice. Notice of a special Board meeting shall state the purpose or purposes for which the meeting is called, the date, time, location or electronic access method, and any matter requiring director action. The Board shall not take action at a special meeting on matters outside the stated purpose unless permitted by applicable law, the Articles or Certificate, this Bylaw, and waiver or attendance rules.
Special meeting notice shall be sufficiently specific to alert directors to the nature of the matter requiring attention, including whether the matter involves:
a) Board reserved matters;
b) amendment, restatement, repeal, or replacement of governing instruments;
c) director or officer resignation, removal, suspension, vacancy, appointment, renewal, or succession;
d) major financial, grant, donation, sponsorship, restricted fund, in-kind support, contract, debt, lease, banking, insurance, or asset matters;
e) legal, tax, filing, compliance, litigation, investigation, enforcement, public authority, regulatory-perimeter, sanctions, export-control, controlled-technology, competition, or professional-boundary issues;
f) data breach, AI incident, cyber incident, repository compromise, software release issue, model failure, compute record issue, key compromise, credential compromise, vulnerability, or business continuity matter;
g) evidence, methods, observability, ontology, technical truth, public-good software, technical baseline, public-safe publication, correction, withdrawal, retraction, takedown, or archive matter;
h) public authority confusion, official-capacity issue, public warning overclaim, emergency command overclaim, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider-preference issue, or sponsor-control issue;
i) civil rights, accessibility, Tribal or Indigenous protocol, Indigenous data safeguard, protected knowledge, community safeguard, grievance, remedy, protected participation, non-retaliation, or stop-the-line matter; and
j) GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cell, consortium, national company, Project SPV, provider, sponsor, host, public authority, university, laboratory, community, media, or enterprise-stack interface matter.
Special meeting notice shall not be drafted so broadly that it deprives directors of meaningful preparation, nor so narrowly that it conceals material consequences. Where urgency requires abbreviated notice, the record shall identify the urgency and any steps taken to protect fiduciary review.
113.4 Emergency Meeting Notice. Emergency meeting notice may be given on shortened time, through expedited channels, or by any reasonable method permitted by law and this Bylaw where immediate Board consideration is necessary or highly advisable to protect the Corporation, its legal status, tax posture, public-benefit mission, records, assets, people, systems, public trust, public authority relationships, safeguards, technical assets, or Nexus-compatible role.
Emergency notice shall, to the extent practicable, identify:
a) the emergency trigger;
b) date, time, and access method;
c) directors and officers notified;
d) materials available before the meeting;
e) whether privileged, confidential, controlled-room, public authority-sensitive, cyber-sensitive, infrastructure-sensitive, finance-sensitive, personal, health-sensitive, Tribal / Indigenous, community-protected, local, territorial, cultural, environmental, or protected knowledge materials will be considered;
f) whether immediate holds, freezes, quarantines, access restrictions, repository locks, publication freezes, takedowns, corrections, legal referrals, public-safe notices, or emergency delegations may be considered;
g) whether the matter involves public authority confusion, finance-boundary risk, certification-boundary risk, procurement-neutrality risk, recognition-boundary risk, provider-neutrality risk, sponsor non-control risk, data / AI / cyber risk, safeguards risk, or non-execution risk;
h) any director conflicts, recusals, access restrictions, or independence concerns known at the time notice is given; and
i) any post-meeting ratification, sunset, correction, or fuller review expected.
Failure to include every detail in an emergency notice shall not invalidate emergency Board action where the notice was reasonable under the circumstances and action was lawful, necessary, proportionate, and recorded. Emergency notice shall not be used as a pretext to bypass ordinary Board process for matters that are not genuinely urgent.
113.5 Waiver of Notice. A director may waive notice of a Board meeting in any manner permitted by applicable law, the Articles or Certificate, this Bylaw, Board policy, or competent record. Waiver may occur by written waiver, electronic waiver, recorded consent, attendance without objection where lawful, or other legally recognized method.
A waiver of notice shall be interpreted narrowly. Waiver of notice shall not, by itself:
a) waive quorum requirements;
b) waive voting thresholds;
c) waive conflict disclosure or recusal duties;
d) waive confidentiality duties;
e) waive privilege protections;
f) waive access restrictions;
g) waive public authority boundary discipline;
h) waive finance, certification, procurement, recognition, provider-neutrality, or sponsor non-control boundaries;
i) waive data / AI / cyber, privacy, protected knowledge, civil rights, accessibility, Tribal or Indigenous protocol, community safeguard, or public-safe publication controls;
j) waive member approval requirements where applicable;
k) authorize action outside Board authority;
l) cure an unlawful meeting; or
m) approve any matter not lawfully before the Board.
Where a director attends a meeting solely to object to notice, quorum, agenda, access, materials, recusal, meeting classification, or procedural defect, such attendance shall not constitute waiver to the extent the director makes the objection at or before the beginning of the meeting or otherwise as required by law.
Waiver records shall identify the director, meeting, date, method, scope of waiver, and any objection preserved.
113.6 Agenda Preparation. The Chair, President, Executive Director or Chief Executive Officer where authorized, Secretary, committee chairs, officers, or other persons authorized by the Board may prepare a proposed agenda for each Board meeting. The agenda shall organize Board attention, preserve fiduciary time, identify required actions, support record discipline, and prevent material matters from being hidden, mislabeled, rushed, or handled outside authority.
Agenda preparation shall consider, as applicable:
a) Board reserved matters;
b) matters requiring prior committee review;
c) matters requiring counsel, tax, compliance, audit, data / AI / cyber, public authority, finance-boundary, certification-boundary, procurement, competition, sanctions, export-control, controlled-technology, research ethics, safeguards, or protected knowledge review;
d) matters requiring executive session, in camera session, controlled-room session, confidential session, public session, stakeholder session, public authority session, state interface session, territorial interface session, Tribal interface session, or North America interface session classification;
e) matters requiring director conflict disclosure, recusal, access restriction, independence review, or related-party review;
f) matters requiring public-safe claim review, controlled vocabulary review, limitation language, non-reliance language, or correction pathway;
g) matters involving GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, providers, sponsors, hosts, public authorities, universities, laboratories, communities, media, or enterprise-stack actors;
h) matters involving public-good software, repositories, open technical baselines, technical assets, datasets, dashboards, maps, AI systems, model registers, inference records, compute workload records, proof receipts, ledger entries, role keys, smart licenses, digital twins, DePIN records, AI-RAN or O-RAN signals, cyber telemetry, sensor signals, or public-safe outputs; and
i) matters requiring correction, supersession, withdrawal, retraction, takedown, archive, legal hold, retention, sealing, deletion, or public clarification.
The agenda shall distinguish, where practicable, between information items, discussion items, decision items, consent agenda items, executive session items, controlled-room items, emergency items, reserved matters, and matters requiring later ratification.
113.7 Agenda Circulation. The proposed agenda shall be circulated to directors sufficiently in advance of the meeting to support meaningful review, subject to emergency, confidentiality, privilege, controlled-room, public authority, data / AI / cyber, protected knowledge, or legal constraints. Agenda circulation may occur through secure Board portal, electronic mail, calendar attachment, secure messaging system, repository, or other approved method.
Agenda circulation shall preserve:
a) director preparation;
b) lawful notice;
c) identification of decision items;
d) identification of reserved matters;
e) identification of expected votes;
f) identification of consent agenda items;
g) identification of executive session or in camera items;
h) identification of controlled-room, confidential, sealed, or no-download items;
i) identification of public authority-sensitive, finance-sensitive, cyber-sensitive, infrastructure-sensitive, commercially sensitive, personal, health-sensitive, Tribal / Indigenous, community-protected, local, territorial, cultural, environmental, or protected knowledge items;
j) identification of potential conflicts, recusals, access restrictions, or independence issues;
k) identification of public-safe claims, limitation language, and controlled vocabulary implications; and
l) accurate recordkeeping.
A director may request that a governance-significant matter be placed on the agenda in accordance with this Bylaw and Board policy. Refusal, deferral, or reclassification of such a request shall be recorded where the matter is material.
113.8 Board Materials Circulation. Board materials shall be circulated in a manner and timeframe reasonably designed to allow directors to discharge fiduciary duties with care, diligence, independence, and informed judgment. Materials shall be accurate, versioned, complete enough for the decision requested, and classified according to access, confidentiality, privilege, publication, data / AI / cyber, public authority, finance, protected knowledge, and safeguards requirements.
Board materials may include, without limitation:
a) agenda packets;
b) minutes and prior action items;
c) resolutions and written consent forms;
d) officer reports;
e) committee reports;
f) financial statements, budgets, grant reports, sponsorship reports, restricted fund reports, support concentration reports, and audit or review materials;
g) legal, tax, compliance, regulatory-perimeter, sanctions, export-control, controlled-technology, competition, procurement-integrity, government ethics, professional-boundary, or counsel materials;
h) evidence packs, method notes, observability reports, ontology updates, controlled vocabulary materials, public-good software reports, open technical baseline reports, repository reports, secure-release materials, model registers, inference records, compute workload summaries, proof receipt records, and technical asset records;
i) data governance, privacy, AI governance, cybersecurity, incident, business continuity, disaster recovery, access, identity, credential, key, vulnerability, and SBOM materials;
j) public authority learning materials, capacity classifications, public authority reference materials, regulator-listening materials, public finance reader materials, emergency-management participant materials, public infrastructure operator materials, and public authority room records;
k) civil-rights, accessibility, Tribal / Indigenous protocol, Indigenous data safeguard, protected knowledge, community safeguard, grievance, remedy, non-retaliation, public-safe mapping, and stop-the-line materials;
l) GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cell, consortium, national company, Project SPV, provider, sponsor, host, public authority, university, laboratory, community, and enterprise-stack interface materials; and
m) drafts, redlines, issue lists, risk matrices, authority matrices, delegation matrices, policy drafts, technical profiles, public-safe notice libraries, correction records, withdrawal records, retraction records, takedown records, archive records, and implementation plans.
Materials shall not be circulated through unapproved systems where such circulation would create unacceptable confidentiality, privilege, data / AI / cyber, public authority, finance, protected knowledge, safeguards, or record-integrity risk.
113.9 Secure Circulation. Board materials shall be circulated securely where required by their content, classification, legal status, or risk profile. Secure circulation may include use of a Board portal, encrypted transmission, access-controlled repository, no-download room, clean room, data room, evidence room, public authority room, controlled room, secure document link, watermarking, identity verification, multi-factor authentication, device controls, access logging, expiration controls, revocation rights, and prohibition on forwarding, copying, uploading, printing, downloading, recording, or AI processing.
Secure circulation shall be required or considered for materials involving:
a) attorney-client privilege or work product;
b) personal information, rights-bearing data, health-sensitive data, children’s data, or employment matters;
c) cyber-sensitive, infrastructure-sensitive, national security-sensitive, controlled-technology, export-control, sanctions, vulnerability, key, credential, repository, SBOM, secure-release, or incident-response materials;
d) public authority-sensitive, official-capacity, regulator-listening, public finance reader, emergency-management, public infrastructure operator, procurement-sensitive, public records, open meeting, or government ethics materials;
e) finance-sensitive, commercially sensitive, sponsor-sensitive, donor-sensitive, funder-sensitive, provider-sensitive, grant-sensitive, restricted fund, private benefit, or related-party materials;
f) Tribal / Indigenous, community-protected, local, territorial, cultural, environmental, or protected knowledge materials;
g) research ethics, human-subjects, peer-review, model-review, red-team, publication-review, evidence-challenge, correction, withdrawal, retraction, takedown, or investigation materials; and
h) materials that could create public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider preference, sponsor control, or public-safe risk if disclosed without context.
Directors shall comply with secure circulation rules. A director shall not export, copy, upload, forward, train, summarize, translate, process, or redistribute Board materials through unapproved systems, including unapproved AI systems, consumer cloud tools, personal accounts, messaging applications, or shadow IT.
113.10 Confidential, Privileged, Public Authority, Cyber-Sensitive, Infrastructure-Sensitive, Finance-Sensitive, Commercially Sensitive, Personal, Community-Protected, Indigenous, Tribal, Local, Territorial, or Protected Knowledge Materials. Board materials containing confidential, privileged, public authority-sensitive, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, personal, health-sensitive, community-protected, Indigenous, Tribal, local, territorial, cultural, environmental, protected knowledge, or similar sensitive content shall be classified, handled, reviewed, discussed, recorded, retained, sealed, deleted, disclosed, or archived according to law, this Bylaw, Board policy, applicable agreements, access rules, data / AI / cyber controls, safeguards, and public-safe publication requirements.
Such materials shall be subject to heightened controls, including as applicable:
a) need-to-know access;
b) recusal-based access restriction;
c) conflict-based access restriction;
d) public authority capacity classification;
e) privilege labeling and counsel handling;
f) no-download, no-print, no-forward, no-recording, and no-AI-use restrictions;
g) watermarking or traceability;
h) chain-of-custody handling;
i) controlled-room review;
j) secure repository storage;
k) special minute treatment;
l) sealed record treatment;
m) legal hold treatment;
n) public-safe redaction;
o) protected knowledge review;
p) Indigenous protocol review;
q) community consent, non-consent, attribution, withdrawal, restriction, or correction pathway review where applicable; and
r) breach response and correction pathway.
No director, officer, committee member, advisor, participant, observer, public authority participant, sponsor, provider, host, donor, funder, contractor, consultant, volunteer, fellow, or external actor shall receive sensitive Board materials unless authorized and properly classified. Access to sensitive materials shall not be treated as authority to act, speak, certify, recognize, finance, procure, approve, publish, operate, or execute.
113.11 Late Materials. Late materials may be provided to the Board where the matter could not reasonably be prepared earlier, where developments occurred after ordinary circulation, where emergency conditions exist, or where late materials are necessary to correct, supplement, or protect the integrity of the Board record. Late materials shall be clearly identified as late, supplemental, corrected, privileged, confidential, controlled, draft, public-safe, or otherwise classified.
The Board shall consider whether late materials materially affect the Board’s ability to deliberate, satisfy fiduciary duties, obtain required review, identify conflicts, apply recusal, preserve confidentiality, assess public authority boundaries, assess finance or certification boundaries, assess data / AI / cyber risks, assess safeguards, or make a record-supported decision.
Where late materials are material, the Board may:
a) defer the matter;
b) table the matter;
c) continue the meeting;
d) approve only a limited or conditional action;
e) request additional officer, committee, counsel, compliance, tax, audit, data / AI / cyber, public authority, safeguards, or technical review;
f) restrict action to emergency hold, freeze, quarantine, re-scope, access restriction, takedown, correction, legal referral, or protective measures;
g) exclude late materials from decision basis pending review;
h) require post-meeting ratification or confirmation; or
i) record the reasons for proceeding notwithstanding late circulation.
Late materials shall not be used to ambush directors, avoid scrutiny, conceal conflicts, suppress dissent, rush sponsor or provider requests, exploit public authority deadlines, bypass member rights where applicable, or obtain approval for matters that require fuller review.
113.12 Supplemental Materials. Supplemental materials may be provided before, during, or after a Board meeting to clarify, complete, correct, update, contextualize, or preserve the record of a matter before the Board. Supplemental materials shall be versioned, dated, classified, and linked to the relevant agenda item, meeting record, resolution, action item, or decision record.
Supplemental materials may include:
a) corrected drafts;
b) redlines;
c) legal memoranda;
d) officer certifications;
e) committee recommendations;
f) financial schedules;
g) conflict disclosures;
h) recusal notes;
i) public-safe language;
j) controlled vocabulary notes;
k) technical appendices;
l) evidence lineage notes;
m) data / AI / cyber risk notes;
n) public authority capacity notes;
o) finance-boundary notes;
p) certification-boundary notes;
q) procurement-neutrality notes;
r) safeguards notes;
s) protected knowledge notes;
t) compatibility notes;
u) divergence logs; and
v) correction records.
Supplemental materials shall not silently replace prior materials. Where a supplemental material supersedes, corrects, withdraws, or materially modifies a prior material, the supersession or correction shall be recorded. No director shall be expected to rely on conflicting materials without clarification of which version is operative for the requested action.
113.13 Consent Agenda. The Board may use a consent agenda to approve routine, non-controversial, properly reviewed, non-conflicted, non-reserved, and record-ready matters in a single action, provided that any director may request removal of an item from the consent agenda for separate discussion, clarification, recusal, amendment, deferral, or vote.
Consent agenda items may include, where appropriate:
a) approval of prior minutes;
b) routine committee reports;
c) routine officer reports;
d) non-material policy updates within Board-approved frameworks;
e) non-material register updates;
f) routine appointments within approved authority;
g) routine technical housekeeping approvals;
h) routine administrative authorizations;
i) non-material renewals;
j) routine filing confirmations;
k) routine publication of previously approved public-safe summaries; and
l) other matters that do not require substantive deliberation.
The consent agenda shall not be used for:
a) Bylaw amendments;
b) Articles or Certificate amendments;
c) mission-lock matters;
d) tax-status changes;
e) director removal;
f) officer removal for cause;
g) major grants, donations, sponsorships, restricted funds, contracts, debt, asset transfers, IP transfers, repository transfers, or technical asset dispositions;
h) public authority protocols of material significance;
i) data / AI / cyber, privacy, research integrity, safeguards, export-control, sanctions, competition, controlled-technology, or publication policies of material significance;
j) matters involving unresolved conflicts or recusals;
k) matters involving public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider preference, sponsor control, or non-execution boundary risk;
l) matters involving protected knowledge, Tribal or Indigenous protocol, civil rights, accessibility, grievance, remedy, non-retaliation, or stop-the-line risk; or
m) any matter a director reasonably requests to remove.
Consent agenda approval shall be recorded with sufficient detail to identify each item approved and any item removed, deferred, amended, or separately considered.
113.14 Director Right to Raise Governance-Significant Matters. Each director shall have the right, consistent with law, fiduciary duty, Board policy, confidentiality, privilege, access controls, and meeting discipline, to raise governance-significant matters for Board attention. A governance-significant matter includes any matter that may materially affect the Corporation’s legal compliance, public-benefit purpose, nonprofit character, tax-exempt or tax-exempt-compatible status, fiduciary duties, mission lock, non-execution boundary, role separation, public authority boundary, finance boundary, certification boundary, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, records, public-safe publication, validity-by-record, correctionability, or public trust.
Governance-significant matters may include, without limitation:
a) suspected unlawful action;
b) suspected ultra vires action;
c) suspected breach of fiduciary duty;
d) unresolved conflict or related-party concern;
e) suspected sponsor, donor, funder, provider, host, public authority, founder, GCRI Canada, GRF, GRA, Nexus, national company, Project SPV, investor, insurer, lender, or enterprise capture;
f) public authority confusion or official-capacity ambiguity;
g) finance, securities, insurance, lending, rating, public finance, procurement, certification, recognition, or provider-preference overclaim;
h) data breach, AI incident, cyber incident, repository issue, secure-release issue, technical asset issue, model issue, compute workload issue, proof receipt issue, dashboard issue, digital twin issue, DePIN issue, DLT issue, AI-RAN or O-RAN signal issue, or sensor signal issue;
i) evidence integrity, method integrity, research integrity, publication integrity, source-lineage, confidence, uncertainty, or public-safe publication concern;
j) civil-rights, accessibility, Tribal or Indigenous protocol, Indigenous data, protected knowledge, community safeguard, grievance, remedy, non-retaliation, or stop-the-line concern;
k) controlled vocabulary misuse, public claim issue, limitation language deficiency, non-reliance deficiency, correction failure, supersession failure, withdrawal failure, retraction failure, takedown failure, or archive failure; and
l) material records, repository, gazette, notice, versioning, retention, legal hold, deletion, sealing, or integrity issue.
A director’s good-faith request to raise a governance-significant matter shall not be suppressed for convenience, political sensitivity, sponsor sensitivity, provider sensitivity, public authority sensitivity, fundraising sensitivity, public relations sensitivity, management discomfort, technical embarrassment, or reputational concern. The Board may classify, sequence, defer, restrict, or route the matter appropriately, but shall not ignore a material governance-significant matter.
113.15 Emergency Agenda Items. An emergency agenda item may be added to a Board meeting where immediate consideration is necessary or highly advisable and where delaying the matter to a later meeting would create material legal, fiduciary, tax, financial, public-benefit, public authority, data / AI / cyber, safeguards, public-safe publication, repository, technical asset, records, or correction risk.
Emergency agenda items shall be identified as such in the meeting record. The record shall state, to the extent practicable:
a) who raised the item;
b) why the item could not await ordinary notice or agenda process;
c) the risk addressed;
d) materials available;
e) materials unavailable;
f) review completed;
g) review deferred;
h) conflicts identified;
i) recusals applied;
j) access restrictions applied;
k) action requested;
l) limits on action;
m) post-meeting ratification, fuller review, sunset, correction, or follow-up required; and
n) responsible owner and deadline.
Emergency agenda treatment may be appropriate for hold, stop, quarantine, access restriction, publication freeze, repository lock, controlled-room lockdown, takedown, correction, legal referral, public-safe notice, incident response, emergency succession, or preservation measures. Emergency agenda treatment shall not be used to approve major structural changes, mission drift, prohibited functions, finance-readiness determinations, certification, recognition, procurement approval, provider selection, public warning, emergency command, enterprise execution, or public authority action unless separately lawful and within the Corporation’s authority, which this Bylaw generally prohibits.
113.16 Notice, Agenda, and Materials Records. The Corporation shall maintain Notice, Agenda, and Materials Records sufficient to demonstrate that Board meetings were properly called, noticed, prepared, classified, supported, and recorded in accordance with applicable law, the Articles or Certificate, this Bylaw, Board policy, confidentiality obligations, privilege, data / AI / cyber controls, safeguards, and validity-by-record.
Notice, Agenda, and Materials Records shall include, as applicable:
a) notices of regular meetings, special meetings, annual meetings, emergency meetings, executive sessions, in camera sessions, controlled-room sessions, confidential sessions, public or stakeholder sessions, state interface sessions, territorial interface sessions, Tribal interface sessions, public authority sessions, and North America interface sessions;
b) proofs of delivery, delivery logs, electronic mail records, portal notices, calendar notices, secure message notices, waiver records, attendance-based waiver records, objections to notice, preserved objections, correction notices, and supplemental notices;
c) proposed agendas, final agendas, amended agendas, emergency agenda items, consent agendas, removed consent items, deferred items, tabled items, continued items, executive session agenda items, controlled-room agenda items, public authority-sensitive agenda items, finance-sensitive agenda items, safeguards-sensitive agenda items, and protected knowledge agenda items;
d) Board packets, officer reports, committee reports, legal materials, financial materials, grant materials, sponsorship materials, public authority materials, evidence materials, methods materials, observability materials, ontology materials, technical asset materials, public-good software materials, repository materials, secure-release materials, data / AI / cyber materials, model register materials, inference record materials, compute workload materials, proof receipt materials, public-safe publication materials, correction materials, and interface materials;
e) draft materials, adopted materials, corrected materials, superseded materials, withdrawn materials, privileged materials, sealed materials, redacted materials, public-safe materials, restricted materials, no-download materials, and archived materials;
f) classification records, access records, secure circulation records, identity verification records, director access logs, download restrictions, watermark records, expiration records, revocation records, AI-use restriction records, device restriction records, and breach records;
g) conflict notices, recusal notices, access restriction notices, related-party notices, independence concern notices, sponsor-control notes, provider-preference notes, public authority capacity notes, finance-boundary notes, certification-boundary notes, procurement-neutrality notes, recognition-boundary notes, and safeguards notes;
h) director requests to add matters, requests to remove consent agenda items, requests for additional materials, requests for deferral, requests for counsel review, requests for committee review, requests for public-safe review, and responses to such requests;
i) records of late materials, supplemental materials, supersession records, corrected versions, redlines, divergence logs, compatibility notes, limitation language, non-reliance language, controlled vocabulary notes, and public-safe notices;
j) records of any notice defect, agenda defect, materials defect, access defect, classification defect, confidentiality defect, privilege defect, conflict defect, recusal defect, quorum implication, technical failure, public-safe claim defect, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider-preference issue, sponsor-control issue, or safeguard concern, and the correction, ratification, restriction, deferral, withdrawal, takedown, or other disposition of the issue; and
k) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that notice, agenda, and materials are not clerical conveniences; they are fiduciary infrastructure. The Board shall receive and preserve the information necessary to act lawfully, independently, carefully, and in record-supported form. No defective notice, hidden agenda item, late material, unclassified sensitive material, insecure circulation, uncontrolled AI processing, public authority ambiguity, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, sponsor-control pressure, provider-preference pressure, or safeguards omission shall be allowed to create or preserve Board action that requires fuller review, lawful approval, correction, withdrawal, ratification, or refusal.
Section 114. Quorum, Voting, Abstentions, Recusals, Written Consents, and Electronic Participation
114.1 Quorum. A quorum of the Board shall consist of the number or percentage of directors required by applicable law, the Articles or Certificate, this Bylaw, Board resolution, or other competent governing record. Unless a higher standard is required by applicable law, the Articles or Certificate, this Bylaw, member approval requirement where applicable, or Board resolution, a majority of directors then in office shall constitute a quorum for the transaction of Board business.
Quorum shall be determined with reference to directors who are lawfully in office, eligible to participate in the meeting or action, not disqualified from service, and not excluded from the particular matter by mandatory recusal, access restriction, conflict rule, confidentiality classification, law, court order, regulatory restriction, or other binding limitation. The Board shall not inflate quorum by counting persons who are not directors, former directors, advisors, officers, committee members, observers, public authority participants, sponsors, providers, donors, funders, hosts, founders, GCRI Canada representatives, The Global Risks Forum (GRF) representatives, The Global Risks Alliance (GRA) representatives, Nexus representatives, national company representatives, Project SPV representatives, or enterprise-stack participants unless such persons are also duly serving directors.
Quorum discipline shall preserve:
a) lawful Board authority;
b) fiduciary deliberation;
c) director independence;
d) mission-lock protection;
e) non-execution protection;
f) public authority boundary discipline;
g) finance, securities, insurance, lending, rating, public finance, procurement, certification, recognition, provider-neutrality, and sponsor non-control boundaries;
h) data / AI / cyber, privacy, controlled-room, repository, technical asset, and secure-system controls;
i) community safeguards, Tribal and Indigenous protocol respect, protected knowledge, civil-rights, accessibility, grievance, remedy, protected participation, and non-retaliation controls;
j) validity-by-record; and
k) correctionability.
No action shall be treated as Board action unless quorum exists at the time the action is taken or the action is otherwise validly taken by written consent or other lawful method. A quorum defect shall be recorded, reviewed, corrected, ratified where lawful, or treated as void or non-operative to the fullest extent required.
114.2 Higher Quorum for Reserved Matters. The Board may require, or applicable law, the Articles or Certificate, this Bylaw, member approval requirement, Board resolution, or policy may require, a higher quorum for reserved matters, constitutional matters, mission-lock matters, tax-status matters, structural matters, dissolution matters, merger or conversion matters, major asset matters, major funding matters, major public authority matters, major data / AI / cyber matters, major safeguards matters, major Nexus interface matters, or other matters of heightened consequence.
Higher quorum may be required for, without limitation:
a) amendment, restatement, repeal, replacement, or constitutional interpretation of this Bylaw;
b) amendment of the Articles or Certificate;
c) change of legal name, corporate form, state of incorporation, registered office, registered agent, principal governance seat, or United States legal seat where material;
d) application for, change to, surrender of, revocation response for, or restructuring of tax-exempt or tax-exempt-compatible status;
e) adoption, amendment, suspension, or withdrawal of mission-lock, public-benefit, non-execution, role-separation, public authority boundary, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, sponsor non-control, data / AI / cyber, safeguards, validity-by-record, or correctionability instruments;
f) approval of major grants, donations, sponsorships, restricted funds, in-kind contributions, public-good support arrangements, public authority arrangements, major contracts, long-term obligations, debt, credit facilities, leases, asset transfers, intellectual property transfers, repository transfers, technical asset dispositions, or public-good asset dispositions;
g) creation, suspension, dissolution, or material restructuring of major committees, councils, controlled rooms, programs, public authority interfaces, Nexus interfaces, GCRI Canada interfaces, GRF interfaces, GRA interfaces, national consortium interfaces, national company interfaces, Project SPV interfaces, provider interfaces, or sponsor interfaces;
h) adoption of material data, AI, cyber, privacy, research integrity, public-safe publication, sponsorship, safeguards, export-control, sanctions, competition, controlled-technology, protected knowledge, or public authority policies;
i) approval of litigation, settlement, investigation response, regulatory engagement, public authority correction, public-safe correction, retraction, takedown, or public clarification of material significance; and
j) dissolution, merger, consolidation, conversion, sale of substantially all assets, wind-up, or distribution of public-good assets.
Where higher quorum applies, the meeting record shall identify the applicable higher quorum rule, the directors counted, directors excluded, directors recused, and whether the higher quorum was satisfied. No urgency, operational convenience, sponsor request, provider request, public authority request, publication deadline, grant deadline, repository deadline, or event deadline shall waive a higher quorum unless lawful waiver is expressly permitted and recorded.
114.3 Loss of Quorum Through Recusal. If quorum exists at the beginning of a meeting but is lost for a particular matter because one or more directors are recused, disqualified, access-restricted, absent, disconnected, excluded for confidentiality, or otherwise unable to participate lawfully, the Board shall not act on that matter unless applicable law, the Articles or Certificate, this Bylaw, or a competent governing record permits action by the remaining directors.
Loss of quorum through recusal may occur where directors have conflicts involving:
a) personal financial interests;
b) related-party transactions;
c) sponsor, donor, funder, provider, host, contractor, vendor, public authority, investor, insurer, lender, underwriter, bank, public finance actor, capital reader, national company, Project SPV, university, laboratory, community organization, media actor, or enterprise relationship;
d) GCRI Canada, GRF, GRA, Nexus entity, consortium, national company, Project SPV, provider, or sponsor dual role;
e) research authorship, publication interest, technical contribution, repository role, model-review role, software-release role, data contribution, public authority interface, or controlled-room participation;
f) data / AI / cyber, privacy, protected knowledge, public authority-sensitive, infrastructure-sensitive, finance-sensitive, or commercial sensitivity restriction; or
g) any other matter that impairs lawful participation or independent fiduciary judgment.
Where quorum is lost, the Board may:
a) defer the matter;
b) refer the matter to independent directors;
c) obtain member action where required or available;
d) appoint qualified independent directors where lawful;
e) obtain independent committee review;
f) seek counsel, court, regulator, tax, compliance, or other lawful guidance;
g) narrow the matter to a protective hold, quarantine, access restriction, publication freeze, or preservation action where lawful; or
h) decline action.
The Board shall not manipulate recusals, vacancies, committee assignments, access classifications, or meeting attendance to manufacture quorum or avoid independent review.
114.4 Voting Standard. Except as otherwise required by applicable law, the Articles or Certificate, this Bylaw, member approval requirement where applicable, Board resolution, policy, or competent record, an act of the Board shall require the affirmative vote of a majority of directors present at a meeting at which quorum exists. The Board may impose higher approval thresholds for reserved matters, constitutional matters, mission-lock matters, material risk matters, related-party matters, conflict-sensitive matters, public authority matters, finance-boundary matters, certification-boundary matters, procurement-neutrality matters, provider-neutrality matters, sponsor non-control matters, data / AI / cyber matters, safeguards matters, protected knowledge matters, or Nexus interface matters.
Voting shall be conducted in a manner that supports:
a) informed fiduciary judgment;
b) director independence;
c) accurate recordkeeping;
d) conflict disclosure and recusal discipline;
e) confidentiality and privilege;
f) public-safe decision-making;
g) avoidance of sponsor, provider, donor, funder, host, public authority, founder, GCRI Canada, GRF, GRA, Nexus, national company, Project SPV, or enterprise-stack capture;
h) avoidance of public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider preference, sponsor control, and enterprise execution;
i) data / AI / cyber and safeguards controls; and
j) correctionability.
A vote shall be counted only if cast by a director who is eligible to vote on the matter. A person without voting authority shall not vote, direct a vote, condition funding on a vote, condition participation on a vote, purchase a vote, trade a vote, or otherwise exercise improper influence over Board action.
114.5 Majority Vote. Where a majority vote standard applies, the Board shall determine whether the required majority is measured by directors present, directors then in office, directors eligible to vote, independent directors, disinterested directors, committee members, classes of directors, or another lawful category, as required by applicable law, the Articles or Certificate, this Bylaw, Board resolution, or governing record.
A majority vote shall not be distorted by counting:
a) persons who are not directors;
b) directors who are no longer in office;
c) directors who have not consented to serve;
d) directors who are disqualified from service;
e) directors who are mandatorily recused;
f) directors excluded from the matter by access restriction or conflict rule;
g) abstentions as affirmative votes unless the governing rule so provides;
h) proxies where proxies are not permitted;
i) silent non-responses unless written consent rules lawfully permit; or
j) informal indications, polling, comments, chat messages, reactions, AI summaries, meeting transcripts, or operational assumptions as votes.
The minutes or action record shall identify the voting standard applied, votes in favor, votes against, abstentions, recusals, non-participations where material, and whether the standard was satisfied. Where the vote concerns a material boundary, reserved matter, public authority interface, finance-boundary issue, certification-boundary issue, procurement-neutrality issue, provider-neutrality issue, sponsor non-control issue, data / AI / cyber issue, safeguards issue, or protected knowledge issue, the record shall identify any required limitation, condition, review, correction pathway, or implementation control.
114.6 Higher Approval Thresholds. Higher approval thresholds may include approval by two-thirds of directors then in office, two-thirds of directors present, a majority of independent directors, a majority of disinterested directors, unanimous approval of directors present, unanimous approval of directors then in office, member approval where applicable, class approval where applicable, or any other lawful threshold required or adopted for a specified matter.
Higher approval thresholds may be required for:
a) constitutional or structural amendments;
b) mission-lock changes;
c) public-benefit purpose changes;
d) changes affecting nonprofit character, non-distribution, private benefit, inurement, or tax status;
e) non-execution, public authority boundary, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, sponsor non-control, or role-separation matters;
f) major transactions, major assets, major liabilities, major grants, major sponsorships, major public-good support, major restricted funds, major contracts, or major technical asset dispositions;
g) related-party transactions;
h) conflict-sensitive matters;
i) indemnification or advancement decisions where interested directors are involved;
j) dissolution, merger, consolidation, conversion, or sale of substantially all assets;
k) public-good asset distribution;
l) creation or termination of major GCRI Canada, GRF, GRA, Nexus, public authority, national consortium, national company, Project SPV, provider, sponsor, host, or enterprise-stack interface instruments; and
m) any matter for which the Board determines heightened legitimacy, independence, or record discipline is required.
Where higher approval is required and not obtained, the matter shall fail, be deferred, be revised, be escalated, or be treated as non-operative. No officer, committee, council, working group, sponsor, provider, public authority participant, donor, funder, host, or external actor may treat an unsuccessful vote as implied approval.
114.7 Unanimous Written Consent Where Required or Permitted. The Board may act by unanimous written consent, or by such written consent threshold as applicable law, the Articles or Certificate, this Bylaw, or governing record permits, without a meeting, provided that the consent is executed, authenticated, delivered, retained, and recorded in the manner required by law and this Bylaw.
Written consent may be used for matters that are clear, sufficiently documented, non-conflicted or properly recused, within Board authority, and suitable for action without live deliberation. Written consent shall not be used to avoid meaningful discussion where the matter is complex, contested, conflict-sensitive, public authority-sensitive, finance-sensitive, data / AI / cyber-sensitive, safeguards-sensitive, protected knowledge-sensitive, mission-critical, or structurally consequential.
A written consent shall identify, as applicable:
a) text of the resolution or action;
b) effective date;
c) authority for action by consent;
d) directors entitled to consent;
e) directors excluded by recusal or disqualification where applicable;
f) materials reviewed;
g) required approval threshold;
h) signatures or electronic authentication;
i) conditions, limitations, and implementation controls;
j) confidentiality, privilege, public authority, data / AI / cyber, finance, protected knowledge, and safeguards classifications;
k) responsible officer or custodian;
l) repository location; and
m) correction, supersession, withdrawal, ratification, or archive pathway.
No written consent shall be inferred from silence, informal assent, operational compliance, chat message, draft comment, AI summary, calendar response, repository approval, or absence of objection unless applicable law and the governing record expressly permit the specific method.
114.8 Electronic Consent Where Lawful. Electronic consent, electronic signature, secure portal approval, authenticated digital signature, or other electronic approval method may be used to the extent permitted by applicable law, the Articles or Certificate, this Bylaw, Board policy, and applicable electronic transactions law. Electronic consent systems shall be configured to preserve identity verification, authorization, authentication, content integrity, timestamp, version, access class, audit trail, retention, and retrieval.
Electronic consent shall be subject to controls addressing:
a) verified director identity;
b) secure access;
c) multi-factor authentication where appropriate;
d) prevention of unauthorized delegation;
e) prevention of proxy use unless lawful;
f) final text visibility before approval;
g) version locking;
h) record export and retention;
i) confidentiality and privilege;
j) data / AI / cyber security;
k) prevention of unauthorized AI processing;
l) legal hold capacity;
m) revocation or correction pathway where lawful; and
n) system failure procedures.
An electronic approval shall not be valid if cast by an unauthorized person, compromised account, automated agent, AI tool, delegated assistant, staff member, officer, sponsor, provider, public authority participant, or other non-director unless the law and governing instruments expressly authorize the method and person, which shall be disfavored for Board fiduciary action.
114.9 Abstentions. A director may abstain from voting where permitted by law and Board process. Abstention may be appropriate where the director has insufficient information, believes further review is required, has a non-disqualifying concern, wishes to preserve objection, or determines that voting would be inappropriate but recusal is not required.
An abstention shall not be treated as an affirmative vote unless applicable law, the Articles or Certificate, this Bylaw, Board resolution, or governing record expressly so provides. The effect of an abstention on the voting threshold shall be determined according to the applicable voting rule.
Abstention shall not be used to avoid mandatory recusal. A director who has a disqualifying conflict, related-party interest, access restriction, confidentiality limitation, or legal disqualification shall recuse rather than merely abstain where recusal is required.
The minutes or action record shall identify abstentions where material, including whether the abstention was voluntary, conflict-related, information-related, procedural, or based on another stated reason. A director may request that a concise explanation of abstention be recorded, subject to confidentiality, privilege, public-safe, data / AI / cyber, protected knowledge, and legal constraints.
114.10 Mandatory Recusals. A director shall recuse from deliberation, access to materials, recommendation, voting, or any combination of the foregoing where required by applicable law, the Articles or Certificate, this Bylaw, conflict policy, related-party policy, confidentiality rule, data / AI / cyber rule, public authority rule, finance-boundary rule, certification-boundary rule, procurement-neutrality rule, provider-neutrality rule, sponsor non-control rule, safeguards rule, protected knowledge rule, Board resolution, or competent record.
Mandatory recusal may be required where the director has:
a) a personal financial interest;
b) an employment, consulting, contractor, vendor, provider, sponsor, donor, funder, host, investor, insurer, lender, underwriter, bank, public finance, national company, Project SPV, or enterprise-stack relationship;
c) a public authority role or official-capacity relationship that creates legal, ethics, procurement, grant, lobbying, public records, open meetings, public finance, regulatory, or public authority confusion risk;
d) a GCRI Canada, GRF, GRA, Nexus entity, consortium, national company, Project SPV, provider, sponsor, host, or enterprise dual role that impairs independent judgment;
e) an authorship, contribution, maintainer, researcher, model-review, peer-review, software-release, repository, controlled-room, evidence-pack, proof-receipt, dashboard, map, dataset, AI system, digital twin, DePIN, DLT, AI-RAN, O-RAN, or sensor-signal interest in the matter;
f) a fiduciary duty to another person materially affected by the matter;
g) access to protected knowledge, public authority-sensitive materials, data / AI / cyber-sensitive materials, finance-sensitive materials, commercial materials, personal data, health-sensitive data, or privileged materials that requires exclusion;
h) a family, household, business, institutional, political, philanthropic, academic, financial, professional, or other relationship that reasonably impairs independence;
i) involvement in conduct under investigation; or
j) any condition that would cause participation to violate law, fiduciary duty, confidentiality, privilege, safeguards, or public trust.
A director subject to mandatory recusal shall not influence the matter indirectly through side communications, staff direction, officer pressure, sponsor or provider pressure, public authority pressure, informal polling, drafting control, repository control, or post-meeting implementation.
114.11 Voluntary Recusals. A director may voluntarily recuse from a matter where the director reasonably believes participation could create an appearance of conflict, perceived partiality, public authority confusion, sponsor or provider influence concern, institutional pressure, confidentiality risk, protected knowledge concern, data / AI / cyber concern, finance-boundary concern, certification-boundary concern, procurement-neutrality concern, recognition-boundary concern, or public trust concern.
A voluntary recusal may be accepted, recorded, limited, expanded, or converted into a mandatory recusal by the Board, Chair, independent directors, committee, counsel, compliance function, or other authorized process where appropriate. The Board may determine that a director who seeks voluntary recusal may still provide factual information, technical context, or historical background before leaving the deliberation, provided that such participation is lawful, non-advocacy, conflict-managed, and recorded.
Voluntary recusal shall not be used to:
a) avoid fiduciary responsibility without cause;
b) defeat quorum strategically;
c) avoid a difficult vote;
d) conceal a conflict;
e) protect a sponsor, provider, donor, funder, host, public authority, founder, GCRI Canada, GRF, GRA, Nexus, national company, Project SPV, or enterprise actor from scrutiny;
f) suppress dissent;
g) shift responsibility to officers or committees; or
h) create informal influence outside the meeting.
The record shall distinguish voluntary recusal from mandatory recusal where material.
114.12 Effect of Recusal on Deliberation. A recused director shall not participate in deliberation on the recused matter unless the Board, acting lawfully and with conflict controls, permits limited factual presentation, response to questions, or technical explanation before the director leaves the deliberation. Any such limited participation shall be recorded and shall not include advocacy, vote solicitation, pressure, negotiation, drafting control, or implementation direction.
During recusal, the recused director shall not:
a) remain in the meeting room or virtual room unless permitted solely for lawful limited participation;
b) receive restricted materials;
c) participate in executive session or controlled-room deliberation for the matter;
d) communicate privately with directors regarding the matter;
e) direct officers, staff, contractors, advisors, contributors, committee members, or external participants regarding the matter;
f) influence public authority participants, sponsors, providers, donors, funders, hosts, GCRI Canada, GRF, GRA, Nexus actors, national companies, Project SPVs, or enterprise actors regarding the matter;
g) draft or revise decision text unless specifically authorized under controlled process for non-substantive or technical assistance; or
h) implement the decision unless implementation is separately authorized, conflict-managed, and recorded.
The Board may impose conditions on re-entry after recusal, including completion of the agenda item, sealing of records, access review, conflict mitigation, confidentiality acknowledgment, or implementation restriction.
114.13 Effect of Recusal on Access to Materials. A director recused from a matter may be denied access to Board materials for that matter where access would create or increase conflict, confidentiality, privilege, public authority, finance, data / AI / cyber, protected knowledge, safeguards, competition, sanctions, export-control, controlled-technology, procurement, certification, recognition, provider-neutrality, sponsor non-control, investigation, or legal risk.
Access restriction may apply to:
a) agenda materials;
b) Board packets;
c) committee reports;
d) officer reports;
e) legal memoranda;
f) financial schedules;
g) grant, donation, sponsorship, or restricted fund materials;
h) public authority materials;
i) procurement-sensitive materials;
j) capital-reader or finance-sensitive materials;
k) evidence packs;
l) method notes;
m) dataset, model, inference, compute workload, or AI system materials;
n) cyber, vulnerability, key, credential, repository, secure-release, SBOM, or incident materials;
o) Tribal / Indigenous, community-protected, local, territorial, cultural, environmental, or protected knowledge materials;
p) grievance, remedy, whistleblower, non-retaliation, civil-rights, accessibility, or safeguards materials; and
q) investigation, correction, withdrawal, retraction, takedown, or public clarification materials.
Access restriction shall be no broader than reasonably necessary unless law, privilege, confidentiality, data protection, protected knowledge, or safety requires broader restriction. Restricted access shall be logged, and the record shall preserve enough information to demonstrate lawful process without disclosing restricted substance.
114.14 Tie Votes. A tie vote shall fail unless applicable law, the Articles or Certificate, this Bylaw, Board resolution, or governing record provides a lawful tie-breaking mechanism. The Chair shall not have a second or casting vote unless expressly authorized by applicable law, the Articles or Certificate, this Bylaw, or Board resolution.
Where a tie vote occurs, the Board may:
a) defer the matter;
b) revise the proposal;
c) request further information;
d) refer the matter to committee;
e) seek counsel, compliance, tax, audit, technical, public authority, data / AI / cyber, safeguards, or independent review;
f) obtain member approval where required or available;
g) appoint additional directors where lawful and appropriate;
h) decline action; or
i) take only protective, time-limited, non-prejudicial action where lawful and necessary.
A tie vote shall not be treated as implied approval, conditional approval, staff authorization, officer authorization, committee authorization, public authority approval, finance-readiness signal, certification signal, procurement signal, recognition signal, provider preference, sponsor concession, or authority to proceed. Any public or controlled communication about a tied matter shall be public-safe, accurate, and non-misleading.
114.15 Chair Vote Where Applicable. The Chair, if a director, shall have the same voting rights as other directors unless applicable law, the Articles or Certificate, this Bylaw, Board resolution, or governing record provides otherwise. The Chair shall not use agenda control, meeting management, materials control, speaking order, executive session classification, controlled-room classification, emergency classification, or procedural authority to influence votes improperly, suppress dissent, conceal conflicts, rush sponsor or provider matters, privilege public authority pressure, or weaken fiduciary deliberation.
Where the Chair has a conflict, the Chair shall disclose the conflict, recuse where required, and relinquish meeting leadership for the affected matter to an independent Vice-Chair, director, committee chair, or other lawful presiding person. The Chair shall not preside over the Chair’s own compensation, removal, conflict review, misconduct review, related-party matter, independence review, or other matter requiring impartial handling unless applicable law permits and the Board determines no reasonable alternative exists, which shall be recorded.
The Chair’s vote shall not carry greater substantive weight than any other director’s vote unless a lawful tie-breaking or special voting rule expressly provides otherwise. Any such rule shall be narrowly construed and recorded.
114.16 Proxy Voting Only Where Permitted by Law and Governing Instruments. Proxy voting by directors shall be prohibited unless expressly permitted by applicable law, the Articles or Certificate, this Bylaw, and a competent Board record. Because directors owe personal fiduciary duties of care, loyalty, good faith, independence, and informed judgment, director proxy voting shall be disfavored and shall not be used as a substitute for attendance, deliberation, informed consent, or lawful written action.
Where proxy voting is lawfully permitted, any proxy shall be:
a) written or electronically authenticated;
b) specific as to meeting or matter unless broader authority is lawful and approved;
c) revocable where required or permitted;
d) time-limited;
e) conflict-screened;
f) subject to recusal rules;
g) subject to confidentiality and access rules;
h) limited to directors or persons lawfully permitted to hold the proxy;
i) recorded in the meeting records; and
j) insufficient to authorize action beyond the scope of the proxy.
No sponsor, donor, funder, provider, host, public authority participant, officer, employee, contractor, advisor, founder, GCRI Canada representative, GRF representative, GRA representative, Nexus representative, national company representative, Project SPV representative, investor, insurer, lender, bank, capital reader, or enterprise actor may hold, direct, purchase, condition, or control a director proxy unless expressly lawful and consistent with fiduciary duties, which shall be subject to heightened review.
114.17 Electronic Participation. Directors may participate in Board meetings by telephone, video conference, secure collaboration platform, or other electronic means to the extent permitted by applicable law, the Articles or Certificate, this Bylaw, and Board policy. Electronic participation shall constitute presence for quorum and voting purposes where the technology allows directors to hear, speak, deliberate, vote, and otherwise participate in a manner satisfying legal requirements.
Electronic participation shall be conducted to preserve:
a) identity verification;
b) director-only participation where required;
c) confidentiality;
d) privilege;
e) access control;
f) secure document review;
g) recording restrictions;
h) chat and transcript controls;
i) AI-use restrictions;
j) prevention of unauthorized attendance;
k) cyber hygiene;
l) accessibility and reasonable accommodation;
m) recusal exclusion;
n) accurate quorum and vote recording; and
o) meeting continuity during technical failures.
A director participating electronically shall be responsible for using a reasonably secure environment, avoiding unauthorized listeners or viewers, protecting materials, refraining from unapproved recording or AI transcription, and notifying the Chair or Secretary if the director cannot hear, speak, access required materials, preserve confidentiality, or participate meaningfully.
114.18 Identity Verification. The Corporation shall use reasonable identity verification procedures for Board meetings, written consents, electronic approvals, secure portal access, controlled-room admission, data-room admission, executive sessions, in camera sessions, and other director actions requiring confidence that the participating person is the duly serving director.
Identity verification may include:
a) secure login;
b) multi-factor authentication;
c) director-specific credentials;
d) video confirmation;
e) roll call;
f) secure signature;
g) device registration;
h) access tokens;
i) Board portal authentication;
j) call-back verification;
k) meeting host verification;
l) credential rotation;
m) access logs; and
n) other reasonable controls approved by the Board or authorized officer.
A Board action may be held, delayed, repeated, ratified, or corrected where identity cannot be verified with reasonable confidence or where account compromise, impersonation, coercion, unauthorized attendance, delegated attendance, AI-agent participation, or other authenticity concern exists. Identity verification records shall be maintained in a manner that protects security, privacy, and access integrity.
114.19 Secure Meeting Systems. Board meetings, electronic participation, written consents, Board portals, secure repositories, controlled rooms, data rooms, no-download rooms, executive sessions, and electronic voting systems shall use secure meeting systems appropriate to the sensitivity of the matters being considered. The Corporation shall not knowingly use systems that create unacceptable risk to confidentiality, privilege, data protection, cyber security, public authority-sensitive materials, infrastructure-sensitive materials, finance-sensitive materials, protected knowledge, or public-safe records.
Secure meeting system requirements may include:
a) approved platform selection;
b) access control;
c) authentication;
d) encryption where appropriate;
e) waiting room or admission control;
f) participant lock;
g) recording disablement or control;
h) chat retention settings;
i) transcript control;
j) AI transcription and summarization restrictions;
k) screen-sharing control;
l) watermarking;
m) document permissioning;
n) no-download restrictions;
o) audit logging;
p) breach notification procedures;
q) data residency or sovereign compute review where applicable;
r) vendor security review;
s) incident response integration; and
t) backup or alternate meeting procedures.
No director, officer, employee, contractor, advisor, committee member, observer, public authority participant, sponsor, provider, donor, funder, host, or external participant shall move Board deliberation to unapproved channels where doing so would evade records, confidentiality, privilege, cyber, public authority, finance, safeguards, protected knowledge, or public-safe controls.
114.20 Quorum, Vote, Consent, Abstention, Recusal, and Electronic Participation Records. The Corporation shall maintain Quorum, Vote, Consent, Abstention, Recusal, and Electronic Participation Records sufficient to demonstrate that Board actions were taken lawfully, by authorized directors, with required quorum, required approval, proper conflicts management, secure participation, and valid records.
Such records shall include, as applicable:
a) quorum calculations, directors then in office, directors present, directors absent, directors disqualified, directors recused, directors access-restricted, directors participating electronically, directors participating in person, and directors excluded from particular matters;
b) voting standards, higher quorum standards, higher approval thresholds, independent director thresholds, disinterested director thresholds, member approval requirements where applicable, and class approval requirements where applicable;
c) votes in favor, votes against, abstentions, recusals, non-participations where material, tie votes, failed votes, deferred matters, tabled matters, continued matters, conditional approvals, protective holds, ratifications, and corrective actions;
d) written consents, electronic consents, signature records, authentication records, version-locked resolution text, effective-date records, delivery records, consent revocation records where applicable, and consent repository records;
e) conflict disclosures, related-party disclosures, mandatory recusal records, voluntary recusal records, access restriction records, independent review records, limited factual participation records, re-entry records, and recusal violation records;
f) electronic participation records, identity verification records, secure platform records, meeting access logs, virtual waiting room records, recording controls, chat records where retained, transcript records where authorized, AI-use restriction records, device or access exceptions, and technical failure records;
g) proxy records where proxy voting is lawfully permitted, proxy scope records, proxy revocation records, proxy holder records, and proxy validity records;
h) records of any quorum defect, vote defect, consent defect, abstention misclassification, recusal defect, access defect, identity defect, electronic system defect, technical failure, unauthorized attendance, unauthorized AI participation, unauthorized recording, confidentiality breach, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider-preference issue, sponsor-control issue, data / AI / cyber issue, protected knowledge issue, or safeguards concern;
i) records of correction, ratification, restriction, withdrawal, retraction, takedown, supersession, public clarification, legal referral, compliance referral, Board review, member review where applicable, or other disposition of defects or concerns; and
j) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that Board authority is valid only when exercised by duly authorized directors through lawful quorum, lawful voting, valid consent, proper conflict discipline, secure participation, and record-supported action. No informal approval, silent assent, operational assumption, sponsor pressure, provider pressure, public authority pressure, committee recommendation, officer preference, AI-generated summary, dashboard signal, proof receipt, ledger entry, role key, repository approval, technical workflow, or meeting convenience shall substitute for lawful Board action. Every quorum, vote, consent, abstention, recusal, and electronic participation process shall remain bounded by fiduciary duty, public-benefit purpose, non-execution, role separation, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, and correctionability.
Section 115. Board Reserved Matters
115.1 Reserved Matters Purpose. The Board shall retain exclusive authority over the matters reserved to it by applicable law, the Articles or Certificate, this Bylaw, member approval requirements where applicable, Board resolution, or other competent governing record. Reserved matters are those matters that, by their legal, fiduciary, constitutional, financial, institutional, technical, public-benefit, public authority, data / AI / cyber, safeguards, Nexus-interface, or public-trust consequence, shall not be finally approved by any officer, committee, council, working group, advisor, sponsor, provider, donor, funder, host, public authority participant, GCRI Canada interface, The Global Risks Forum (GRF) interface, The Global Risks Alliance (GRA) interface, Nexus actor, national company, Project SPV, or enterprise-stack actor unless the Board has expressly and lawfully delegated a limited authority that does not include final reserved-matter approval.
The purpose of reserved matters is to preserve:
a) the Corporation’s lawful nonprofit, non-stock or non-share, non-distributing, public-benefit, tax-exempt or tax-exempt-compatible character;
b) fiduciary governance by duly authorized directors;
c) mission lock, public-good purpose, and institutional boundedness;
d) United States legal separateness and all-states-and-territories governance discipline;
e) North America anchor role discipline without sovereign, treaty, public authority, finance, certification, procurement, recognition, or execution overclaim;
f) non-execution, role separation, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, and anti-capture controls;
g) evidence integrity, methods integrity, observability integrity, ontology integrity, technical truth integrity, public-good R&D integrity, public-good software integrity, open technical baseline integrity, and public-safe publication integrity;
h) data governance, AI governance, cybersecurity, privacy, secure compute, verifiable compute, verifiable intelligence, repository integrity, and technical asset stewardship;
i) community safeguards, Tribal and Indigenous protocol respect, Indigenous data safeguards, protected knowledge, local and territorial knowledge, civil rights, accessibility, grievance, remedy, protected participation, non-retaliation, and stop-the-line controls;
j) validity-by-record, correctionability, version discipline, repository discipline, gazette discipline, and public-safe claims discipline; and
k) lawful alignment with GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, qualified providers, sponsors, hosts, public authorities, universities, laboratories, communities, and enterprise-stack actors.
A reserved matter shall be interpreted broadly where doubt exists. No matter shall cease to be reserved merely because an officer, committee, council, working group, advisor, sponsor, provider, public authority participant, technology system, dashboard, proof receipt, ledger entry, AI system, or operational workflow has prepared, recommended, routed, scored, validated, or technically enabled it.
115.2 Amendment, Restatement, Repeal, or Replacement of Bylaw. The Board shall reserve authority to approve any amendment, restatement, repeal, replacement, consolidation, re-numbering, constitutional interpretation, official correction, material editorial update, or authoritative version change to this Bylaw, subject to applicable law, the Articles or Certificate, and member approval where required.
No amendment, restatement, repeal, or replacement of this Bylaw shall be effected by:
a) officer practice;
b) committee charter;
c) council recommendation;
d) working group output;
e) policy, protocol, schedule, matrix, checklist, form, register, technical profile, controlled vocabulary, public-safe notice library, manual, template, playbook, dashboard, repository rule, workflow, smart contract, proof receipt, ledger entry, role key, AI output, or software configuration;
f) funding agreement, sponsorship agreement, grant agreement, donor restriction, provider agreement, host agreement, public authority MoU, consortium instrument, national company instrument, Project SPV instrument, or Nexus interface instrument;
g) public statement, website language, slide, proposal, fundraising deck, Gitbook page, AI summary, translation, explainer, redline, draft, or unofficial copy; or
h) custom, course of dealing, silence, operational convenience, emergency practice, or informal consensus.
Any Bylaw change shall identify the text changed, the authority for change, approval threshold, effective date, transition rule, supersession record, repository record, and any required public-safe notice. A change that affects mission lock, nonprofit character, public-benefit purpose, non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, correctionability, GCRI / GRF / GRA role separation, Nexus role separation, United States seat, all-states-and-territories posture, or North America anchor role shall be treated as material or constitutional and shall require heightened review.
115.3 Amendment of Certificate or Articles of Incorporation. The Board shall reserve authority to approve any amendment, restatement, correction, filing, merger-related change, conversion-related change, dissolution-related change, name change, purpose change, registered-agent or registered-office change where reserved, corporate-form change, or other modification of the Articles or Certificate, subject to applicable law and member or incorporator approval where required.
No amendment of the Articles or Certificate shall be initiated, filed, represented as approved, or relied upon unless the Board has reviewed, as applicable:
a) consistency with nonprofit and public-benefit character;
b) consistency with tax-exempt or tax-exempt-compatible purposes;
c) consistency with mission lock and non-distribution;
d) impact on United States legal seat, state corporate law, state qualifications, territorial operations, charitable solicitation, tax, filings, registrations, and good standing;
e) impact on North America anchor role and cross-border interfaces;
f) impact on non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, and anti-capture controls;
g) impact on GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, providers, sponsors, hosts, and enterprise-stack interfaces;
h) impact on data / AI / cyber, research integrity, public-good software, technical assets, public-safe publication, protected knowledge, and safeguards obligations; and
i) required legal, tax, regulatory, filing, repository, gazette, notice, and transition actions.
No officer, counsel, filing service, incorporator after Board transition, registered agent, contractor, sponsor, donor, provider, public authority participant, or external actor may file or authorize a change to the Articles or Certificate without competent Board approval and any other required approval.
115.4 Change of Legal Name. The Board shall reserve authority to approve any change to the Corporation’s legal name, official institutional name, approved short name, public legal identity, assumed name, fictitious name, trade name, operating name, public name-use protocol, seal, mark, or formal corporate naming convention.
A legal name change shall require review of:
a) state corporate filing requirements;
b) federal tax records;
c) state and territorial tax records;
d) charitable solicitation records;
e) bank, insurance, grant, donor, sponsorship, subscription, fee, contract, employment, vendor, repository, IP, domain, data, AI, cyber, and public authority records;
f) public-facing materials, websites, publications, dashboards, maps, reports, datasets, software, technical baselines, proof receipts, public-safe notices, and repository notices;
g) name-use risks involving GCRI Canada, other GCRI entities, GRF, GRA, Nexus Network, Nexus Standards, Nexus Observatory, Nexus Universe, consortiums, national companies, Project SPVs, qualified providers, sponsors, hosts, public authorities, universities, laboratories, and enterprise-stack actors;
h) risks of public authority confusion, finance signaling, certification implication, procurement implication, recognition overclaim, provider preference, sponsor control, or North America anchor overclaim; and
i) correction, transition, supersession, gazette, and public-safe clarification needs.
No program label, campaign label, repository label, public report title, technical asset name, website heading, event name, grant title, sponsor title, public authority room label, or Nexus interface label shall be treated as a change of legal name unless approved and recorded as such by the Board and lawfully filed where required.
115.5 Change of State of Incorporation, Corporate Form, Registered Office, Registered Agent, or Principal Governance Seat Where Material. The Board shall reserve authority to approve any material change to the Corporation’s state of incorporation or organization, corporate form, registered office, registered agent, principal office, principal governance seat, United States seat discipline, or state corporate law anchor.
A material seat or form change shall require review of:
a) governing state nonprofit corporation law;
b) federal tax consequences;
c) state and territorial tax, franchise, qualification, charitable solicitation, employment, privacy, data, AI, cyber, public records, procurement, lobbying, grant, and contract consequences;
d) effect on all-states-and-territories operating posture;
e) effect on North America anchor role;
f) effect on GCRI Canada and cross-border interfaces;
g) effect on Board authority, member rights where applicable, director duties, officer authority, indemnification, insurance, liability, records, inspection rights, public-benefit duties, and dissolution or asset-distribution rules;
h) effect on mission lock, non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, safeguards, validity-by-record, and correctionability; and
i) required filings, approvals, notices, repository updates, gazette entries, continuity plans, and transition records.
Routine registered agent or registered office updates may be delegated if lawful and expressly authorized, but any such delegation shall be narrow, recorded, and subject to Board reporting. No seat-related change shall be used to weaken public-benefit protections, fiduciary accountability, tax discipline, records integrity, safeguards, or Nexus role separation.
115.6 Tax-Exempt Status Application, Change, Revocation, or Structural Shift. The Board shall reserve authority over any application for tax-exempt status, confirmation of tax classification, change of federal tax classification, response to proposed revocation, voluntary surrender of exempt status, structural tax shift, charitable status strategy, lobbying or political activity posture where material, unrelated business income strategy where material, fiscal sponsorship arrangement where material, supporting organization arrangement, sponsored project arrangement, or other tax-status decision materially affecting the Corporation.
The Board shall review, as applicable:
a) federal tax law requirements;
b) state and local tax requirements;
c) nonprofit, charitable, educational, scientific, public-benefit, or other exempt-purpose compatibility;
d) public-benefit mission and non-distribution requirements;
e) private inurement and private benefit controls;
f) grants, donations, sponsorships, subscriptions, fees, cost recovery, in-kind support, restricted funds, academy programs, fellowships, publications, technical assets, software, datasets, controlled rooms, and public authority learning revenue treatment;
g) lobbying, political activity, campaign intervention, public policy education, government ethics, gift, grant, and procurement-integrity constraints;
h) relationship to GCRI Canada, GRF, GRA, Nexus entities, consortiums, national companies, Project SPVs, providers, sponsors, hosts, funders, public authorities, universities, laboratories, and enterprise actors;
i) impact on data / AI / cyber, research integrity, public-safe publication, safeguards, protected knowledge, and public-good software activities; and
j) records, filings, public representation, donor communications, receipts, notices, and transition obligations.
No officer, fundraiser, development lead, sponsor, donor, grant writer, advisor, accountant, fiscal sponsor, public authority participant, or external consultant shall represent that the Corporation has a tax status not supported by competent records.
115.7 Charitable Status, Fiscal Sponsorship, Supporting Organization, or Other Tax Structure Decision. The Board shall reserve authority to approve the adoption, pursuit, rejection, modification, termination, or public representation of any charitable status, fiscal sponsorship, sponsored project, supporting organization, affiliated foundation, donor-advised structure, public charity classification, private foundation classification, 501(c)(3), 501(c)(4), 501(c)(6), or other tax-related structure.
In approving any such structure, the Board shall preserve:
a) public-benefit purpose;
b) nonprofit character;
c) non-distribution;
d) no private inurement;
e) no impermissible private benefit;
f) research and education integrity;
g) independence from donor, sponsor, provider, host, funder, public authority, investor, insurer, lender, national company, Project SPV, and enterprise control;
h) non-execution and regulated-perimeter boundaries;
i) public authority, finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control boundaries;
j) data / AI / cyber, privacy, research ethics, civil-rights, accessibility, community safeguard, Tribal / Indigenous, protected knowledge, and public-safe mapping controls; and
k) records, reporting, auditability, correctionability, and public-safe representation.
No fiscal sponsorship, supporting organization, donor arrangement, grant arrangement, restricted fund, campaign, public-good infrastructure fund, or affiliated structure shall be used to evade Board reserved matters, substitute another body’s control for Board fiduciary oversight, or transform the Corporation into a financing, investment, procurement, certification, recognition, provider-selection, public authority, or enterprise execution body.
115.8 Mission Lock, Public-Benefit Purpose, Nonprofit Character, or Non-Execution Boundary Change. The Board shall reserve authority over any matter that creates, modifies, weakens, interprets, waives, suspends, externalizes, or materially affects the Corporation’s mission lock, public-benefit purpose, nonprofit character, non-distribution rule, tax-exempt or tax-exempt-compatible purpose, public-good technical institution status, or non-execution boundary.
Such matters include, without limitation:
a) adoption or amendment of mission statements, purpose clauses, constitutional rules, public-benefit statements, public-good commitments, public-safe claims, or public-facing descriptions;
b) entry into any arrangement that may alter the Corporation’s role from evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, public authority learning, or safeguards stewardship into execution, operations, finance, certification, procurement, recognition, regulation, emergency command, public warning, provider selection, project ownership, or enterprise delivery;
c) acceptance of support, funding, sponsorship, data, systems, infrastructure, compute, AI-RAN, O-RAN, DePIN, DLT, digital twin, sensor, dashboard, or technical assets that materially condition mission, outputs, access, publications, records, or governance;
d) public authority arrangements that may be misunderstood as delegation, official adoption, procurement approval, funding approval, emergency command, public warning, regulator approval, public-private partnership, sovereign obligation, or public finance approval;
e) finance-adjacent arrangements involving capital readers, investors, insurers, lenders, underwriters, banks, public finance actors, ratings, proof packs, readiness inputs, or diligence translation; and
f) Nexus interface arrangements that may blur GCRI, GRF, GRA, Nexus Standards, Nexus Network, national company, Project SPV, provider, sponsor, host, or enterprise-stack roles.
Any interpretation that would weaken the mission lock or non-execution boundary shall be rejected unless expressly approved by the Board where lawful and consistent with the Articles or Certificate, applicable law, and the Corporation’s public-benefit character.
115.9 United States All-States-and-Territories Operating Posture Change. The Board shall reserve authority over any material change to the Corporation’s United States all-states-and-territories operating posture, including changes affecting operation, qualification, registration, charitable solicitation, tax, employment, data, AI, cyber, privacy, public authority interface, public records, procurement, lobbying, grant, contracting, host-site, observability, public-safe publication, or community safeguard treatment in any state, territory, the District of Columbia, Tribal interface, or local jurisdiction.
A material all-states-and-territories posture change includes, without limitation:
a) entering or withdrawing from a state, territory, Tribal interface, local jurisdiction, or public authority interface in a manner that materially affects legal compliance or public representation;
b) adopting a state-specific, territorial-specific, Tribal-interface-specific, or local operating schedule;
c) creating or materially modifying a state, territorial, Tribal, local, sectoral, metropolitan, port, utility, public health, emergency management, telecom, energy, water, food, cyber, infrastructure, or public authority interface;
d) establishing state or territorial rooms, controlled rooms, data rooms, evidence rooms, public authority rooms, observability nodes, hubs, clusters, hotspots, regional clusters, or national dense Nexus core interfaces;
e) adopting localization language that could fragment the Bylaw, weaken mission lock, or alter role separation; and
f) creating public claims about coverage, authority, participation, official status, readiness, recognition, certification, procurement, provider status, sponsor status, or public authority involvement in a jurisdiction.
Localization may adapt the Corporation’s lawful operation to local legal and safeguards requirements, but shall not weaken public-benefit purpose, non-execution, role separation, public authority boundaries, finance boundaries, data / AI / cyber controls, safeguards, validity-by-record, or correctionability.
115.10 North America Anchor Role Change. The Board shall reserve authority over any material change to the Corporation’s North America anchor role, including any public representation, cross-border interface, GCRI Canada coordination, Mexico or Caribbean interface, Arctic, Great Lakes, Pacific, Atlantic, Gulf, border, Indigenous, regional, public authority, infrastructure, climate, disaster, cyber, public health, energy, water, food, biodiversity, telecom, supply chain, port, or systemic-risk evidence architecture matter that materially affects the Corporation’s bounded North America function.
No North America anchor role change shall be approved unless the Board determines and records that the change:
a) is lawful under United States law and any other applicable law;
b) preserves GCRI US legal separateness;
c) preserves GCRI Canada legal separateness and any other GCRI entity separateness;
d) does not create treaty, sovereign, intergovernmental, regional regulator, public finance, emergency command, public warning, procurement, certification, recognition, or finance-readiness authority;
e) does not create public authority delegation or official adoption by participation;
f) does not create cross-border agency, partnership, merger, alter ego, common treasury, shared liability, single employer, joint employer, or mutual binding authority;
g) preserves non-execution and role separation;
h) preserves data, AI, cyber, privacy, cross-border transfer, sovereign compute, protected knowledge, Indigenous protocol, public-safe mapping, and safeguards controls; and
i) is supported by compatibility notes, divergence logs, interface records, and correction pathways.
No public or controlled communication shall describe the Corporation’s North America anchor role in a manner that implies sovereign authority, public authority authority, financing authority, certification authority, procurement authority, recognition authority, or enterprise execution authority.
115.11 GCRI / GRF / GRA Role-Separation Instrument. The Board shall reserve authority to approve any material instrument, policy, protocol, MoU, charter, interface agreement, operating schedule, records protocol, data sharing arrangement, public claim, repository rule, proof-receipt logic, Docket-support arrangement, Grid-support arrangement, GRF-facing input arrangement, GRA-facing input arrangement, public-safe reporting arrangement, or Nexus compatibility arrangement that affects separation among GCRI US, GCRI Canada, The Global Risks Forum (GRF), and The Global Risks Alliance (GRA).
Such instruments shall preserve the following role separation:
a) GCRI US as evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, verifiable compute, verifiable intelligence methods, public authority learning, and safeguards steward within its lawful United States and North America role;
b) GCRI Canada as a separate Canadian public-benefit evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, and public authority learning institution within its lawful role;
c) The Global Risks Forum (GRF) as public-good registry, recognition, maturity-records, standing, claims-discipline, stakeholder-formation, public-safe reporting, and public-facing legitimacy steward;
d) The Global Risks Alliance (GRA) as finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, capital-reader room, and regulated-perimeter discipline steward; and
e) Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, providers, sponsors, hosts, and enterprise actors as separate role-bearing actors under their own lawful instruments.
No role-separation instrument shall convert evidence into recognition, methods into certification, technical baselines into procurement mandates, observability outputs into public warnings, proof receipts into finance-readiness determinations, Docket inputs into approvals, Grid inputs into guarantees, or GRA-facing technical inputs into regulated financial advice.
115.12 Public-Good Stack or Enterprise Stack Structural Agreement. The Board shall reserve authority over any structural agreement or arrangement that affects the relationship between the Nexus public-good stack and the enterprise stack, including agreements with consortiums, national companies, state or regional operating companies, Project SPVs, qualified enterprise providers, sponsors, hosts, public authorities, funders, capital readers, universities, laboratories, community institutions, or platform actors.
A structural agreement shall require Board approval where it materially affects:
a) public-good governance;
b) enterprise execution separation;
c) national or regional consortium interfaces;
d) national company formation or interface;
e) Project SPV interface;
f) provider qualification, neutrality, participation, or technical interface;
g) sponsor support, benefits, acknowledgments, or non-control controls;
h) host-site participation;
i) public authority learning, capacity classification, or interface rules;
j) public-good software, open technical baseline, repository, technical asset, or IP rights;
k) data, AI, cyber, privacy, sovereign compute, protected knowledge, or secure-room architecture;
l) Docket, Grid, GRF-facing input, GRA-facing input, proof-pack, proof-receipt, capital-reader, or finance-boundary workflows; or
m) public-safe claims, public legitimacy, public reporting, recognition, certification, procurement, provider selection, finance-readiness, insurance-readiness, or enterprise delivery meanings.
No structural agreement shall permit enterprise-stack actors to direct GCRI US governance, evidence conclusions, methods, public-good software, technical baselines, public-safe publications, public authority access, GRF recognition, GRA finance-readiness, Nexus-compatible status, Docket status, Grid status, procurement outcomes, or provider preference.
115.13 Annual Strategy. The Board shall reserve authority to approve the Corporation’s annual strategy, strategic plan, strategic priorities, mission priorities, public-benefit objectives, research priorities, public-good R&D priorities, public-good software priorities, technical baseline priorities, public authority learning priorities, safeguards priorities, Nexus interface priorities, United States all-states-and-territories priorities, and North America anchor priorities.
The annual strategy shall address, as applicable:
a) public-benefit mission and mission lock;
b) evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, Nexus Truth Engine methods, Nexus Observatory methods, verifiable compute, verifiable intelligence, and technical asset stewardship;
c) data, AI, cyber, privacy, secure compute, repositories, model registers, inference records, compute workload records, technical release, and business continuity;
d) public authority learning, regulator-listening, public finance reader, emergency-management participant, public infrastructure operator, public authority room, and capacity-classification priorities;
e) community safeguards, Tribal and Indigenous protocol respect, protected knowledge, civil rights, accessibility, public-safe mapping, grievance, remedy, protected participation, non-retaliation, and do-no-harm priorities;
f) GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortium, national company, Project SPV, provider, sponsor, host, public authority, university, laboratory, and community interface priorities;
g) financial sustainability, support diversification, anti-capture, private benefit, restricted fund, sponsorship, grant, donation, subscription, fee, and cost-recovery discipline; and
h) correctionability, records, repository, gazette, public-safe notice, and public claim discipline.
No officer or committee shall implement a strategic direction materially inconsistent with the Board-approved annual strategy unless the Board approves or ratifies the change where lawful.
115.14 Annual Plan. The Board shall reserve authority to approve the annual plan or equivalent operating plan for the Corporation. The annual plan shall translate the annual strategy into programs, priorities, initiatives, deliverables, budgets, staffing, governance calendars, committee work plans, policy priorities, technical asset priorities, repository priorities, public authority learning activities, safeguards activities, public-safe publication plans, and correction cycles.
The annual plan may include, without limitation:
a) research and evidence work plans;
b) methods and technical truth work plans;
c) observability and ontology work plans;
d) public-good software and open technical baseline work plans;
e) Nexus Truth Engine, Nexus Observatory, verifiable compute, verifiable intelligence, secure compute, AI-RAN, O-RAN, DePIN, DLT, digital twin, sensor, geospatial, Earth observation, cyber, and dashboard method plans;
f) data governance, AI governance, cybersecurity, privacy, repository, secure-release, SBOM, model-register, inference-record, compute-workload, vulnerability, incident-response, disaster-recovery, and business-continuity plans;
g) public authority learning, controlled-room, clean-room, data-room, evidence-room, no-download-room, regulator-listening, public finance reader, emergency-management, and public infrastructure operator plans;
h) community safeguard, Tribal / Indigenous protocol, protected knowledge, civil-rights, accessibility, grievance, remedy, non-retaliation, and stop-the-line plans;
i) development, grants, donations, sponsorship, subscriptions, fee, cost-recovery, and in-kind support plans;
j) state, territorial, Tribal, local, and North America localization plans; and
k) records, training, evaluation, correction, supersession, withdrawal, takedown, archive, and public-safe transparency plans.
The annual plan shall not authorize prohibited functions. Activities in the annual plan shall remain subject to lawful approvals, budget authority, delegation matrix, legal review, data / AI / cyber controls, safeguards review, and Board reserved matters.
115.15 Annual Budget. The Board shall reserve authority to approve the annual budget, including revenue assumptions, expense authority, restricted fund treatment, grant budgets, sponsorship budgets, donation budgets, in-kind support valuation where used, subscription and fee expectations, public-good support expectations, staffing costs, contractor costs, technology costs, insurance costs, legal and compliance costs, program costs, public authority learning costs, controlled-room costs, repository costs, cybersecurity costs, software and technical asset costs, travel, events, academy costs, and reserve planning.
The annual budget shall be reviewed for:
a) public-benefit alignment;
b) nonprofit and tax-exempt or tax-exempt-compatible compliance;
c) non-distribution, private benefit, and inurement controls;
d) restricted fund compliance;
e) grant compliance;
f) sponsorship and donor non-control;
g) provider neutrality;
h) public authority access and support boundaries;
i) finance, securities, insurance, lending, public finance, procurement, certification, recognition, and regulated-perimeter risks;
j) data / AI / cyber, privacy, secure compute, repository, and technical asset risks;
k) community safeguards and protected knowledge costs;
l) legal, compliance, audit, tax, filing, insurance, and risk controls;
m) cash flow, reserves, concentration, sustainability, and continuity; and
n) records, reporting, variance, and correction processes.
No officer shall incur expenditures outside the Board-approved budget except as permitted by law, this Bylaw, delegation matrix, emergency authority, or subsequent Board approval. Budget approval shall not waive contracting authority, conflict review, procurement controls, public-benefit review, tax review, or other approval requirements.
115.16 Material Budget Amendment. The Board shall reserve authority to approve any material amendment, reforecast, reallocation, deficit authorization, restricted fund reclassification, new funding dependency, new major expenditure, major revenue change, program expansion, program contraction, staffing expansion, technology expenditure, public authority learning expenditure, controlled-room expenditure, technical asset commitment, repository transfer, insurance change, reserve use, debt-related action, or other budget change exceeding thresholds established by the Board or otherwise material to the Corporation.
A material budget amendment shall be reviewed for:
a) mission impact;
b) public-benefit necessity;
c) financial sustainability;
d) cash flow and reserve impact;
e) tax and nonprofit implications;
f) private benefit and inurement risk;
g) support concentration and anti-capture risk;
h) donor, sponsor, funder, provider, host, public authority, or enterprise influence;
i) restricted fund and grant compliance;
j) contractual commitments;
k) data / AI / cyber, public authority, safeguards, protected knowledge, and technical asset implications;
l) state, territorial, Tribal, local, or North America interface implications; and
m) corrective action where variance results from error, breach, delay, overrun, or unsupported assumption.
No officer may reclassify a material budget matter as operational to avoid Board approval. Emergency budget measures shall be time-limited, recorded, and submitted for Board ratification where required.
115.17 Major Grants, Donations, Sponsorships, Restricted Funds, In-Kind Contributions, and Public-Good Support Arrangements. The Board shall reserve authority to approve major grants, donations, sponsorships, restricted funds, in-kind contributions, public-good infrastructure support, challenge support, fellowship support, scholarship support, technical support, compute support, data support, AI-RAN support, O-RAN support, DePIN support, DLT support, dashboard support, sensor support, host support, or other support arrangements that are material by amount, source, restriction, condition, public meaning, institutional dependency, conflict risk, public authority involvement, regulated-perimeter risk, data / AI / cyber risk, safeguards risk, protected knowledge risk, or Nexus-interface consequence.
Major support arrangements shall be reviewed for:
a) lawful acceptance;
b) nonprofit and tax compliance;
c) donor restrictions;
d) restricted fund controls;
e) grant compliance;
f) sanctions and export controls;
g) conflicts and related-party issues;
h) anti-corruption, gifts, government ethics, lobbying, procurement-integrity, and public authority constraints where applicable;
i) sponsor, donor, funder, provider, host, public authority, enterprise, investor, insurer, lender, national company, Project SPV, or capital actor capture risk;
j) no support-for-control, support-for-outcome, support-for-public-authority-access, support-for-recognition, support-for-finance-readiness, support-for-certification, support-for-procurement, support-for-provider-preference, or support-for-public-warning;
k) data / AI / cyber, privacy, repository, secure compute, and technical asset conditions;
l) community safeguard, Tribal / Indigenous protocol, protected knowledge, civil-rights, accessibility, public-safe mapping, and do-no-harm implications;
m) public acknowledgment, naming, logo, mark, press, website, publication, dashboard, report, proof receipt, repository, and public-safe claims controls; and
n) refusal, return, restriction, termination, correction, or public clarification pathways.
Support shall be accepted only where the Board determines that the support advances lawful public-benefit purposes and does not compromise independence, role separation, or public trust.
115.18 Major Contracts and Long-Term Obligations. The Board shall reserve authority to approve major contracts, long-term obligations, material MoUs, major vendor agreements, major contractor agreements, employment arrangements for key personnel, leases, licenses, technology agreements, data agreements, AI agreements, cloud agreements, cybersecurity agreements, software agreements, repository agreements, public authority agreements, university agreements, laboratory agreements, host agreements, provider agreements, sponsor agreements, grant agreements, donor agreements, controlled-room agreements, cross-border agreements, Nexus interface agreements, GCRI Canada interface agreements, GRF interface agreements, GRA interface agreements, national consortium agreements, national company interface agreements, Project SPV interface agreements, or other obligations that exceed thresholds or materially affect the Corporation.
Major contract review shall address, as applicable:
a) legal authority and signatory authority;
b) mission and public-benefit alignment;
c) budget authority and financial exposure;
d) tax and nonprofit implications;
e) private benefit and inurement risk;
f) indemnity, liability, insurance, warranty, limitation of liability, dispute resolution, governing law, forum, termination, and survival provisions;
g) data, privacy, AI, cyber, secure compute, incident, confidentiality, IP, repository, audit, access, retention, deletion, and technical controls;
h) public authority, procurement, public records, open meetings, lobbying, government ethics, grant, gift, and public finance implications;
i) sanctions, export-control, controlled-technology, national security, and cross-border constraints;
j) competition and antitrust constraints;
k) community safeguards, protected knowledge, civil rights, accessibility, public-safe mapping, and Indigenous protocol protections;
l) non-execution, finance, certification, procurement, recognition, provider-neutrality, sponsor non-control, public warning, and emergency command boundaries; and
m) records, monitoring, breach, correction, suspension, termination, and closeout.
No contract shall bind the Corporation to perform prohibited functions or permit a counterparty to control the Corporation’s governance, evidence, methods, publications, public authority access, technical baselines, records, or public-safe claims.
115.19 Major Debt, Credit Facility, Lease, Asset Transfer, IP Transfer, Repository Transfer, or Technical Asset Disposition. The Board shall reserve authority to approve any major debt, credit facility, borrowing, guaranty, lien, pledge, security interest, lease, sale, transfer, assignment, license, encumbrance, exclusive arrangement, repository transfer, public-good software transfer, technical baseline transfer, data asset transfer, model transfer, dashboard transfer, AI system transfer, domain transfer, mark transfer, patent transfer, copyright transfer, trade secret transfer, open-source governance transfer, public-good asset disposition, or other material asset action.
Before approval, the Board shall review:
a) legal authority;
b) nonprofit and tax implications;
c) public-benefit purpose;
d) private benefit and inurement risk;
e) donor, grant, sponsor, restricted fund, IP, open-source, data, or public-good restrictions;
f) asset classification, public-good status, access class, publication class, repository class, retention class, archive status, and supersession status;
g) anti-enclosure and public-good stewardship implications;
h) data / AI / cyber, privacy, secure compute, model, inference, compute workload, and repository risks;
i) protected knowledge, Indigenous data, community-protected, local, territorial, cultural, environmental, civil-rights, accessibility, and public-safe mapping implications;
j) finance, securities, lending, insurance, public finance, rating, procurement, certification, recognition, provider preference, sponsor control, and enterprise execution risks;
k) GCRI Canada, GRF, GRA, Nexus, consortium, national company, Project SPV, provider, sponsor, host, public authority, university, laboratory, and community interface implications; and
l) correction, transition, notice, repository, gazette, archival, and continuity requirements.
No public-good asset shall be transferred or encumbered in a manner that defeats the Corporation’s public-benefit purpose, mission lock, anti-enclosure commitments, or legal obligations.
115.20 Appointment or Removal of Key Officers. The Board shall reserve authority to appoint, renew, suspend, remove, replace, or set material terms for key officers, including the Chair where applicable, Vice-Chair, President, Executive Director or Chief Executive Officer where approved, Secretary, Treasurer or Chief Financial Officer, Chief Evidence Officer, Chief Research Officer, Chief Methods Officer, Chief Technology Officer, Chief Data, AI, and Cyber Officer, Chief Public-Good Software and Technical Assets Officer, Chief Public Authority Learning Officer, Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer, Chief Legal, Compliance, and Risk Officer where approved, Chief Operating Officer where approved, Chief Development, Grants, and Public-Good Support Officer where approved, and any other principal officer designated by the Board.
The Board shall review officer matters for:
a) legal eligibility;
b) fit-and-proper status;
c) integrity;
d) competence;
e) independence;
f) conflicts and related-party issues;
g) sanctions, export-control, controlled-technology, public authority, finance-boundary, data / AI / cyber, research integrity, safeguards, and protected knowledge risks;
h) understanding of fiduciary, public-benefit, nonprofit, tax-exempt or tax-exempt-compatible, non-execution, role-separation, public authority, finance, certification, procurement, provider-neutrality, sponsor non-control, validity-by-record, and correctionability obligations;
i) compensation, reimbursement, benefit, and private benefit issues;
j) succession and continuity; and
k) required acknowledgments, delegations, access controls, records, and training.
No key officer shall derive authority from title, founder status, technical centrality, public prominence, donor relationship, sponsor relationship, provider relationship, public authority contact, GCRI Canada interface, GRF interface, GRA interface, Nexus interface, or repository access unless appointed and delegated through competent records.
115.21 Creation or Dissolution of Major Committees, Councils, Programs, Controlled Rooms, or Nexus Interfaces. The Board shall reserve authority to create, materially amend, suspend, sunset, dissolve, or materially restructure any major committee, council, advisory body, Helix Council, leadership council, public authority forum, scientific or technical advisory body, working group, expert panel, peer review panel, model review panel, red-team panel, Nexus Competence Cell, major program, controlled room, clean room, data room, evidence room, public authority room, no-download room, lab, academy program, fellowship program, challenge program, activation docket, public authority learning structure, or Nexus interface.
Board approval shall be required where the body or program materially affects:
a) Board oversight or reserved matters;
b) public-benefit mission;
c) public-good technical institution status;
d) evidence, methods, observability, ontology, technical truth, public-good software, technical baselines, or public-safe publication;
e) data / AI / cyber, privacy, secure compute, repository, technical asset, or controlled materials;
f) public authority participation, regulator-listening, public finance reader, emergency-management participant, public infrastructure operator, or official-capacity records;
g) finance-boundary, certification-boundary, procurement-neutrality, recognition-boundary, provider-neutrality, sponsor non-control, public warning, or emergency command risks;
h) community safeguards, Tribal or Indigenous protocol, protected knowledge, civil rights, accessibility, grievance, remedy, non-retaliation, or stop-the-line functions;
i) GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, consortium, national company, Project SPV, provider, sponsor, host, public authority, university, laboratory, or community interfaces; or
j) public reputation, legal exposure, or institutional continuity.
No body or program shall possess authority beyond its charter, delegation, and records. No major body or program shall be created by announcement alone.
115.22 Adoption of Major Policies. The Board shall reserve authority to adopt, amend, restate, suspend, withdraw, supersede, or archive major policies, including any policy materially affecting governance, fiduciary duties, legal compliance, tax compliance, financial controls, audit, conflicts, ethics, related-party transactions, officer authority, delegation, records, public statements, controlled vocabulary, public-safe notices, evidence, methods, observability, ontology, technical truth, research integrity, public-good software, open technical baselines, data governance, AI governance, cybersecurity, privacy, public authority learning, sponsorship, grants, donations, in-kind support, restricted funds, community safeguards, protected knowledge, civil rights, accessibility, competition, sanctions, export controls, controlled technology, or Nexus interfaces.
Major policy review shall include, as applicable:
a) legal review;
b) tax review;
c) nonprofit and private benefit review;
d) compliance review;
e) data / AI / cyber review;
f) public authority boundary review;
g) finance-boundary review;
h) certification-boundary and procurement-neutrality review;
i) provider-neutrality and sponsor non-control review;
j) research integrity and publication integrity review;
k) safeguards and protected knowledge review;
l) competition, sanctions, export-control, controlled-technology, and professional boundary review;
m) GCRI Canada, GRF, GRA, and Nexus interface review; and
n) implementation, training, repository, gazette, notice, review-cycle, correction, supersession, and archive planning.
No policy shall be treated as Board-approved because it appears in a draft, slide, AI summary, repository issue, public-facing page, operational workflow, committee recommendation, officer email, or unofficial compilation.
115.23 Public Authority Protocols. The Board shall reserve authority to approve any material protocol, policy, room rule, agreement, notice, participation term, data contribution term, public authority reference term, public-safe publication term, capacity classification term, simulation term, tabletop term, after-action learning term, regulator-listening term, public finance reader term, emergency-management participant term, public infrastructure operator term, or official-capacity record that governs or materially affects public authority participation.
Public authority protocols shall preserve:
a) no public authority delegation;
b) no public warning authority;
c) no emergency command authority;
d) no regulatory authority;
e) no procurement approval;
f) no funding approval;
g) no public finance approval;
h) no permit, compliance approval, safe harbor, or enforcement authority;
i) no sovereign obligation;
j) no public-private partnership implication unless separately and lawfully approved by competent public authority record and Board record;
k) no official adoption by attendance, listening, data contribution, room participation, scenario participation, dashboard access, proof receipt, public-safe report, or public authority reference;
l) capacity classification for every public authority participant where material;
m) public-safe language, non-reliance language, and controlled vocabulary; and
n) records sufficient to prevent confusion and support correction.
Any public authority protocol shall be reviewed for federal, state, territorial, Tribal, local, public records, open meetings, procurement, lobbying, government ethics, gifts, grant, privacy, data, AI, cyber, critical infrastructure, protected knowledge, and public-safe constraints where applicable.
115.24 Data, AI, Cyber, Privacy, Research Integrity, Publication, Sponsorship, Safeguards, Export-Control, Sanctions, Competition, and Controlled-Technology Policies. The Board shall reserve authority to approve any material policy, protocol, matrix, schedule, technical profile, notice library, or operating framework governing data, AI, cybersecurity, privacy, research integrity, publication integrity, sponsorship, safeguards, export controls, sanctions, competition, antitrust, controlled technology, national security sensitivity, or similar high-risk domains.
Such policies may include, without limitation:
a) data governance policies;
b) privacy policies;
c) rights-bearing data policies;
d) public authority data policies;
e) health-sensitive data policies;
f) cyber-sensitive and infrastructure-sensitive information policies;
g) AI governance policies;
h) model register, dataset card, model card, system card, benchmark card, evaluation harness, inference record, compute workload, agentic AI, and human-review policies;
i) cybersecurity policies, secure development policies, secure release policies, SBOM policies, vulnerability disclosure policies, incident response policies, backup policies, disaster recovery policies, and business continuity policies;
j) research integrity, research ethics, peer review, red-team review, publication review, AI-use-in-research, correction, withdrawal, retraction, takedown, and archive policies;
k) sponsorship, donation, grant, restricted fund, in-kind contribution, public acknowledgment, sponsor benefit, and anti-capture policies;
l) Tribal / Indigenous protocol, Indigenous data, protected knowledge, local and territorial knowledge, civil-rights, accessibility, public-safe mapping, grievance, remedy, non-retaliation, and stop-the-line policies;
m) sanctions, export-control, controlled-technology, defense / dual-use, national security sensitivity, and CFIUS-relevant sensitivity policies where applicable; and
n) competition, antitrust, clean-room, clean-team, benchmarking, data sharing, standards-support, meeting-discipline, and do-not-discuss policies.
No such policy shall authorize prohibited execution, public authority action, finance execution, certification, procurement approval, recognition, provider preference, sponsor control, public warning, or emergency command.
115.25 Litigation, Investigation, Regulatory Engagement, Settlement, or Enforcement Matter of Material Significance. The Board shall reserve authority over material litigation, threatened litigation, claims, subpoenas, investigations, regulatory inquiries, enforcement matters, settlement decisions, consent orders, compliance undertakings, public authority inquiries, governmental referrals, law-enforcement referrals, administrative proceedings, tax controversy, charitable solicitation matter, sanctions matter, export-control matter, competition matter, employment matter, civil-rights matter, accessibility matter, data breach matter, AI incident matter, cyber incident matter, protected knowledge matter, research misconduct matter, publication integrity matter, fraud matter, private benefit matter, inurement matter, fiduciary matter, or other dispute or investigation of material significance.
Board review shall address, as applicable:
a) legal merits and risks;
b) public-benefit mission impact;
c) nonprofit and tax impact;
d) financial exposure;
e) insurance coverage;
f) privilege and work-product protection;
g) public authority, procurement, grant, lobbying, government ethics, and public records implications;
h) data / AI / cyber, privacy, controlled technology, sanctions, export-control, and national security implications;
i) research integrity, public-safe publication, correction, withdrawal, retraction, takedown, and archive implications;
j) community safeguards, protected knowledge, Tribal / Indigenous protocol, civil-rights, accessibility, grievance, remedy, non-retaliation, and stop-the-line implications;
k) GCRI Canada, GRF, GRA, Nexus, consortium, national company, Project SPV, provider, sponsor, host, public authority, university, laboratory, community, and enterprise-stack interface implications;
l) public-safe communication, controlled notice, public clarification, and non-reliance needs; and
m) records, legal holds, evidence preservation, settlement authority, corrective action, and reporting.
No officer may settle or admit liability in a material matter without Board approval unless emergency authority has been lawfully delegated and ratified as required.
115.26 Dissolution, Merger, Consolidation, Conversion, Sale of Substantially All Assets, Wind-Up, or Public-Good Asset Distribution. The Board shall reserve authority over dissolution, merger, consolidation, conversion, domestication, transfer of corporate seat, sale of substantially all assets, wind-up, receivership, bankruptcy, restructuring, public-good asset distribution, restricted fund disposition, charitable asset disposition where applicable, technical asset disposition, repository transition, public-good software continuity, data disposition, controlled-room closeout, or other existential or structural transaction.
Before approving any such matter, the Board shall review:
a) applicable law;
b) Articles or Certificate requirements;
c) member approval requirements where applicable;
d) tax-exempt or tax-exempt-compatible requirements;
e) charitable trust, restricted fund, donor restriction, grant, sponsorship, public-good, IP, open-source, data, and repository restrictions;
f) public-benefit purpose preservation;
g) public-good asset continuation;
h) anti-enclosure protections;
i) records, archives, legal holds, data retention, deletion, sealing, public-safe publication, and correctionability;
j) obligations to employees, contractors, fellows, volunteers, contributors, members, supporters, subscribers, public authority participants, communities, universities, laboratories, sponsors, donors, funders, providers, hosts, and partners;
k) GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortium, national company, Project SPV, provider, sponsor, host, and enterprise-stack interface consequences;
l) community safeguard, Tribal / Indigenous protocol, protected knowledge, civil-rights, accessibility, grievance, remedy, non-retaliation, and public-safe mapping consequences; and
m) public-safe notice, transition, migration, successor steward, and final records.
No dissolution or structural transaction shall distribute assets for private inurement, impermissible private benefit, sponsor control, provider preference, or enterprise capture.
115.27 Other Matters Reserved by Law, Articles, This Bylaw, Member Approval, Board Resolution, or Policy. The Board shall retain authority over any other matter reserved to it by applicable law, the Articles or Certificate, this Bylaw, member approval requirement where applicable, Board resolution, Board policy, court order, regulatory requirement, grant condition, donor restriction, tax requirement, public authority condition, insurance requirement, contract requirement, or other competent record.
A matter shall be treated as Board-reserved where it materially affects or may materially affect:
a) legal existence;
b) good standing;
c) tax status;
d) public-benefit purpose;
e) nonprofit or non-distribution character;
f) mission lock;
g) fiduciary duty;
h) Board composition or authority;
i) officer appointment or authority;
j) budget or financial sustainability;
k) restricted funds or public support;
l) public authority relationships;
m) finance, insurance, lending, rating, public finance, securities, investment adviser, broker-dealer, finder, procurement, certification, recognition, provider-neutrality, sponsor non-control, or other regulated-perimeter boundaries;
n) data / AI / cyber, privacy, secure compute, repository, public-good software, technical baselines, models, inference records, compute workloads, proof receipts, dashboards, digital twins, AI-RAN, O-RAN, DePIN, DLT, sensors, cyber telemetry, geospatial, or Earth observation systems;
o) research integrity, evidence integrity, methods integrity, observability, ontology, technical truth, public-safe publication, correction, withdrawal, retraction, takedown, or archive;
p) community safeguards, Tribal / Indigenous protocol, protected knowledge, civil rights, accessibility, grievance, remedy, protected participation, non-retaliation, or stop-the-line matters;
q) United States all-states-and-territories posture;
r) North America anchor role; or
s) GCRI Canada, GRF, GRA, Nexus, consortium, national company, Project SPV, provider, sponsor, host, public authority, university, laboratory, community, or enterprise-stack interfaces.
Where uncertainty exists, the matter shall be held, escalated, classified as reserved on an interim basis, and reviewed by the Board or authorized governance process.
115.28 Reserved Matter Records. The Corporation shall maintain Reserved Matter Records sufficient to demonstrate that reserved matters were identified, classified, reviewed, approved, refused, deferred, conditioned, ratified, corrected, superseded, withdrawn, or archived only through lawful authority and in conformity with this Bylaw.
Reserved Matter Records shall include, as applicable:
a) reserved matter classification records;
b) Board agenda records;
c) Board materials;
d) legal review records;
e) tax review records;
f) nonprofit and private benefit review records;
g) financial review records;
h) audit or internal control review records;
i) conflict and recusal records;
j) independence review records;
k) quorum and voting records;
l) member approval records where applicable;
m) committee recommendation records;
n) officer recommendation records;
o) counsel advice records, privileged or sealed where appropriate;
p) compliance review records;
q) public authority boundary review records;
r) finance-boundary, securities-boundary, investment adviser, broker-dealer, finder, banking, lending, insurance, underwriting, rating, public finance, procurement, certification, recognition, provider-neutrality, and sponsor non-control review records;
s) data governance, privacy, AI governance, cybersecurity, secure compute, model register, inference record, compute workload, repository, secure-release, SBOM, vulnerability, incident, disaster recovery, and business continuity review records;
t) research integrity, evidence, methods, observability, ontology, technical truth, public-safe publication, correction, supersession, withdrawal, retraction, takedown, and archive review records;
u) community safeguard, Tribal / Indigenous protocol, Indigenous data, protected knowledge, local and territorial knowledge, civil-rights, accessibility, public-safe mapping, grievance, remedy, protected participation, non-retaliation, and stop-the-line review records;
v) GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cell, consortium, national company, Project SPV, provider, sponsor, host, public authority, university, laboratory, community, and enterprise-stack interface records;
w) resolutions, written consents, approvals, refusals, conditions, implementation controls, ratifications, holds, quarantines, re-scoping actions, external referrals, corrective actions, public-safe notices, controlled notices, and public clarifications;
x) version records, effective date records, transition records, supersession records, repository records, gazette records, notice records, archive records, and legal hold records; and
y) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that reserved matters are constitutional governance controls for the Corporation. They preserve lawful Board authority, fiduciary judgment, public-benefit purpose, nonprofit character, mission lock, non-execution, role separation, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, and correctionability. No officer convenience, committee recommendation, council consensus, public authority pressure, sponsor request, provider request, donor condition, funder deadline, grant deadline, publication deadline, technical urgency, AI output, dashboard signal, proof receipt, ledger entry, repository workflow, smart contract, public statement, or Nexus interface shall substitute for Board approval where Board approval is reserved.
Section 116. Strategic Oversight
116.1 Strategic Oversight Purpose. The Board shall exercise strategic oversight over the Corporation’s public-benefit mission, institutional direction, annual strategy, multi-year strategy, mission-lock discipline, United States all-states-and-territories posture, North America anchor role, public-good technical institution character, evidence function, methods function, observability function, ontology function, technical truth function, public-good R&D function, public-good software function, open technical baseline function, public authority learning function, safeguards function, and Nexus public-good stack compatibility.
Strategic oversight shall ensure that the Corporation remains a lawful United States nonprofit, non-stock or non-share, non-distributing, tax-exempt or tax-exempt-compatible, public-benefit, non-executing technical institution and shall not drift into any role as regulator, emergency command body, official public warning authority, procurement authority, certification body, recognition body, finance-readiness authority, securities actor, investment adviser, broker, dealer, finder, lender, bank, insurer, rating agency, public finance approver, standards monopoly, national company, Project SPV, provider, operator, asset owner, deployment company, infrastructure controller, sponsor-controlled vehicle, donor-controlled vehicle, or enterprise execution actor.
Strategic oversight shall include, without limitation:
a) approving, reviewing, and correcting the Corporation’s strategic direction;
b) ensuring alignment with the Articles or Certificate, this Bylaw, Board-approved policies, applicable law, tax-exempt or tax-exempt-compatible obligations, nonprofit duties, public-benefit purpose, and mission lock;
c) preserving GCRI US separateness from 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, qualified enterprise providers, sponsors, hosts, public authorities, universities, laboratories, communities, and enterprise-stack actors;
d) ensuring that public-good strategy and enterprise-stack interfaces are routed through lawful, recorded, role-separated structures;
e) identifying strategic risks, boundary risks, public authority risks, finance risks, certification risks, procurement risks, provider-neutrality risks, sponsor-control risks, data / AI / cyber risks, safeguards risks, protected knowledge risks, competition risks, tax risks, and regulatory-perimeter risks;
f) ensuring that strategy is supported by records, versioning, controlled vocabulary, public-safe notices, repository discipline, gazette discipline where applicable, and correction pathways; and
g) ensuring that strategic ambition never becomes legal overclaim, role inflation, public reliance, regulated execution, public authority confusion, or private capture.
The Board shall not delegate final responsibility for strategic oversight. Officers, committees, councils, working groups, advisors, public authority participants, sponsors, providers, donors, funders, hosts, and technical systems may assist, recommend, model, simulate, report, or implement within delegated authority, but they shall not substitute for Board strategic judgment.
116.2 Public-Benefit Strategy. The Board shall oversee the Corporation’s public-benefit strategy and shall ensure that every material strategic priority advances lawful public-benefit purposes, supports systemic risk literacy, strengthens evidence integrity, improves technical methods, supports public-safe learning, protects communities, advances public-good technology, and preserves institutional trust.
The public-benefit strategy may include, without limitation:
a) development of public-good evidence systems for systemic risks, resilience infrastructure, exponential technologies, mission-critical systems, public authority learning, and community safeguards;
b) development of methods, technical baselines, public-good software, reference architectures, schemas, data dictionaries, test harnesses, evaluation sets, benchmark libraries, and public-safe knowledge products;
c) support for public authority learning without public authority substitution;
d) support for universities, laboratories, civil society, communities, Tribal and Indigenous interfaces, public-interest organizations, and public-good technology contributors;
e) support for public-safe reporting, public-safe dashboards, public-safe maps, controlled-room learning, evidence-room review, data-room discipline, clean-room structures, and no-download-room controls;
f) support for Nexus-compatible public-good stack development while preserving role separation from recognition, finance-readiness, certification, procurement, and execution functions;
g) development of accessible, inclusive, rights-respecting, civil-rights-aware, community-safeguarded, and protected-knowledge-respecting participation pathways; and
h) creation of public-safe summaries, educational materials, Academy programs, training materials, fellowships, and capability-formation tools.
The public-benefit strategy shall not be used to justify private inurement, impermissible private benefit, donor control, sponsor control, provider preference, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, data misuse, AI misuse, cyber weakness, protected knowledge extraction, or public-safe publication failure.
116.3 Evidence Strategy. The Board shall oversee the Corporation’s evidence strategy and shall ensure that evidence work is lawful, method-supported, source-aware, provenance-aware, confidence-aware, uncertainty-aware, public-safe, correctionable, and aligned with the Corporation’s non-executing public-good role.
The evidence strategy may address, without limitation:
a) evidence for systemic risk, resilience infrastructure, public safety learning, climate, nature, energy, water, food, health, disaster, cyber, telecommunications, supply chain, port, border, public trust, advanced manufacturing, semiconductors, and mission-critical systems;
b) evidence for AI, AI-RAN, O-RAN, DePIN, DLT, blockchain, Web3, quantum-relevant systems, sovereign compute, HPC, robotics, drones, sensors, geospatial systems, Earth observation, digital twins, biosecurity, and other exponential technologies;
c) source-lineage, provenance, custody, traceability, verification, validation, confidence, uncertainty, contradiction, disputed-evidence, stale-evidence, failed-signal, spoof-indicator, and correction methods;
d) evidence intake, evidence classification, evidence registers, proof receipt support, public-safe evidence packs, Docket support, Grid support, GRF-facing inputs, and GRA-facing technical inputs;
e) separation between evidence support and recognition, finance-readiness, certification, procurement, public authority decision, rating, public warning, or emergency command;
f) public authority learning evidence rooms and controlled-room processes that prevent official-capacity confusion;
g) community, Tribal, Indigenous, local, territorial, cultural, environmental, health-sensitive, cyber-sensitive, infrastructure-sensitive, and protected knowledge evidence safeguards; and
h) records sufficient to show why evidence was used, limited, corrected, superseded, withdrawn, retracted, archived, or rejected.
No evidence output shall be represented as final truth, public authority decision, public warning, emergency command, regulatory approval, finance-readiness determination, insurance-readiness determination, rating, certification, recognition, procurement approval, provider preference, or operational authorization unless a separate competent authority lawfully makes and records such determination.
116.4 Methods Strategy. The Board shall oversee the Corporation’s methods strategy and shall ensure that methods are rigorous, repeatable, auditable, reviewable, public-safe, versioned, bounded, and correctionable.
The methods strategy may include, without limitation:
a) validation methods;
b) verification methods;
c) confidence methods;
d) uncertainty methods;
e) source-lineage methods;
f) provenance methods;
g) sensor-fusion methods;
h) AI-output review methods;
i) agentic-AI control methods;
j) AI-RAN and O-RAN signal interpretation methods;
k) DePIN, DLT, blockchain, ledger, proof-receipt, and distributed-record validation methods;
l) digital twin assumption review methods;
m) cyber evidence methods;
n) geospatial and Earth observation methods;
o) observability methods;
p) public-safe publication methods;
q) correction, supersession, withdrawal, retraction, takedown, and archive methods; and
r) methods for public authority learning, controlled rooms, clean rooms, evidence rooms, data rooms, no-download rooms, simulations, tabletop exercises, after-action learning, and capacity classification.
The Board shall ensure that methods do not silently become standards authority, certification authority, procurement approval, public authority action, finance-readiness determination, rating, recognition, public warning, emergency command, or enterprise execution. Every material method shall identify intended use, prohibited use, limitations, review cycle, custodian, version, effective date, repository location, public-safe status, and correction pathway.
116.5 Observability Strategy. The Board shall oversee the Corporation’s observability strategy and shall ensure that observability work supports public-good evidence, systemic risk literacy, resilience awareness, public authority learning, community safeguards, and Nexus Observatory methods without becoming public warning, emergency command, public authority action, surveillance misuse, commercial extraction, or operational control.
The observability strategy may include, without limitation:
a) Nexus Observatory methods;
b) observability node methods;
c) Nexus Hub methods;
d) Nexus Cluster methods;
e) Nexus Hotspot methods;
f) regional cluster methods;
g) national dense Nexus core methods;
h) state, territorial, Tribal, local, metropolitan, port, utility, sectoral, cross-border, and North America observability methods;
i) sensor, edge compute, AI-RAN, O-RAN, DePIN, DLT, digital twin, cyber telemetry, geospatial, Earth observation, dashboard, API, SDK, schema, and public-good software observability methods;
j) degraded-mode awareness;
k) resilience indicators;
l) signal confidence, signal uncertainty, signal latency, signal provenance, signal failure, spoof indicators, contradiction handling, and public-safe presentation;
m) public-safe dashboards and maps;
n) controlled-room, public authority room, evidence-room, data-room, clean-room, and no-download-room observability review; and
o) observability records, correction records, supersession records, withdrawal records, retraction records, takedown records, and archive records.
No observability environment, dashboard, map, node, hub, cluster, hotspot, regional cluster, national dense Nexus core, sensor network, AI-RAN signal, DePIN record, digital twin output, cyber telemetry feed, geospatial layer, Earth observation layer, or model output shall be treated as public warning, emergency command, public authority decision, regulatory approval, procurement approval, certification, recognition, finance-readiness, insurance-readiness, rating, provider approval, or operational authorization merely because it is supported, developed, reviewed, hosted, published, or used by the Corporation.
116.6 Ontology Strategy. The Board shall oversee the Corporation’s ontology, semantic governance, controlled vocabulary, and interoperability strategy and shall ensure that institutional meaning is controlled, traceable, public-safe, legally bounded, and resistant to silent drift.
The ontology strategy may include, without limitation:
a) controlled vocabularies;
b) definitions schedules;
c) semantic registers;
d) taxonomies;
e) schemas;
f) data dictionaries;
g) metadata dictionaries;
h) risk categories;
i) evidence classifications;
j) maturity concepts;
k) public authority capacity classifications;
l) finance-boundary classifications;
m) certification-boundary classifications;
n) procurement-neutrality classifications;
o) provider-neutrality classifications;
p) sponsor non-control classifications;
q) public-safe claim libraries;
r) no-use and restricted-use term lists;
s) limitation language libraries;
t) non-reliance language libraries; and
u) ontology mappings across GCRI US, GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, providers, sponsors, hosts, public authorities, universities, laboratories, communities, and enterprise actors.
The Board shall ensure that terms such as “verified,” “validated,” “technical truth,” “public-safe,” “recognized,” “maturity,” “standing,” “Docket,” “Grid,” “finance-ready,” “insurance-ready,” “bankable,” “investable,” “capital-readable,” “proof pack,” “certified,” “accredited,” “conformant,” “Nexus-compatible,” “public authority,” “official,” “observer,” “regulator-listening,” “public finance reader,” “emergency-management participant,” “North America anchor,” “state interface,” “territorial interface,” “Tribal interface,” and “public-good stack” shall be used only within approved meaning and record-supported authority.
No program team, publication lead, technology vendor, sponsor, provider, donor, funder, public authority participant, state interface, regional team, committee, working group, AI system, dashboard, repository workflow, or informal group may redefine controlled terms outside approved semantic governance.
116.7 Public-Good R&D Strategy. The Board shall oversee the Corporation’s public-good R&D strategy and shall ensure that research and development activities support lawful public-benefit purposes, technical literacy, evidence quality, methods improvement, public-good software, open technical baselines, public authority learning, community safeguards, and Nexus-compatible interoperability without becoming commercial delivery, enterprise execution, regulated advice, certification, procurement approval, recognition, or finance-readiness determination.
The public-good R&D strategy may include, without limitation:
a) applied research;
b) technical prototyping;
c) public-good software development;
d) open technical baselines;
e) reference architectures;
f) interoperability profiles;
g) schemas, APIs, SDKs, data tools, dashboards, maps, and evaluation harnesses;
h) test harnesses, gold vectors, negative tests, benchmark libraries, simulation tools, scenario tools, and model review tools;
i) verifiable compute and verifiable intelligence methods;
j) secure compute, confidential computing, compute-to-data, and sovereign compute methods;
k) AI governance, cybersecurity, privacy, secure-release, SBOM, vulnerability, repository, signing, provenance, dependency, and artifact-integrity methods;
l) public authority learning tools;
m) Observatory, Truth Engine, Docket-support, Grid-support, GRF-facing input, and GRA-facing technical input tools;
n) anti-enclosure controls for public-good technical assets; and
o) correction, supersession, withdrawal, deprecation, takedown, and archival pathways.
The Board shall ensure that R&D is not shaped by sponsor, provider, donor, funder, host, public authority, national company, Project SPV, investor, insurer, lender, or enterprise actor control. Sponsored or supported R&D shall preserve independence, publication integrity, conflict disclosure, public-safe limitations, and correctionability.
116.8 Public-Good Software and Technical Baseline Strategy. The Board shall oversee the Corporation’s public-good software, open technology, open technical baseline, repository, technical asset, and anti-enclosure strategy.
The strategy may include, without limitation:
a) public-good software tools;
b) reference implementations;
c) schemas;
d) APIs;
e) SDKs;
f) dashboards;
g) data tools;
h) test harnesses;
i) benchmark libraries;
j) evaluation sets;
k) public-good repositories;
l) controlled repositories;
m) open-source contribution systems;
n) contributor license agreements;
o) open licensing;
p) restricted licensing where needed to protect rights, safety, protected knowledge, controlled technology, or public-good integrity;
q) SBOM generation;
r) secure release, artifact signing, provenance, dependency review, vulnerability management, rollback, and deprecation controls;
s) fork governance and compatibility claim review; and
t) public-good technical asset registers.
The Board shall ensure that public-good software and technical baselines are not misrepresented as certification, accreditation, legal compliance approval, procurement approval, public authority decision, finance-readiness determination, rating, provider approval, sponsor entitlement, or operational authorization. A reference implementation shall remain a technical artifact unless a separate competent authority lawfully establishes and records certification or conformance authority.
No public-good technical asset shall be transferred, enclosed, exclusively controlled, or commercially captured in a manner inconsistent with donor restrictions, grant restrictions, open licenses, public-good commitments, protected knowledge obligations, data / AI / cyber controls, public authority boundaries, or the Corporation’s mission lock.
116.9 Nexus Truth Engine Methods Strategy. The Board shall oversee the Corporation’s Nexus Truth Engine methods strategy and shall ensure that Truth Engine methods support confidence, corroboration, contradiction detection, public-safe evidence comparison, and correctionability without creating an oracle, final authority, public warning system, public authority decision engine, recognition engine, finance-readiness engine, certification engine, procurement engine, rating engine, or emergency command system.
The strategy may include, without limitation:
a) source comparison methods;
b) evidence corroboration methods;
c) contradiction detection;
d) disputed-evidence classification;
e) stale-evidence handling;
f) failed-signal handling;
g) spoof-indicator handling;
h) model-output review;
i) automated-score limitation;
j) human-review routing;
k) confidence and uncertainty presentation;
l) provenance and source-lineage integration;
m) public-safe truth output methods;
n) correction triggers;
o) challenge pathways;
p) audit logs;
q) proof-receipt support; and
r) controlled vocabulary for truth-related claims.
The Board shall ensure that Truth Engine outputs are bounded by limitation language, non-reliance language, human review where material, access classification, publication classification, correction pathways, and public-safe controls. No Truth Engine output shall be used as final authority without competent human and institutional authorization recorded in accordance with law and this Bylaw.
116.10 Nexus Observatory Methods Strategy. The Board shall oversee the Corporation’s Nexus Observatory methods strategy and shall ensure that observability methods are interoperable, record-supported, rights-respecting, public-safe, correctionable, and compatible with the Corporation’s lawful non-executing role.
The strategy may address, without limitation:
a) Observatory node methods;
b) Nexus Hub methods;
c) Nexus Cluster methods;
d) Nexus Hotspot methods;
e) regional cluster methods;
f) national dense Nexus core methods;
g) public authority learning observability methods;
h) host-site observability methods;
i) community safeguard observability methods;
j) climate, nature, infrastructure, disaster, cyber, public health, energy, water, food, telecom, supply chain, port, border, AI-RAN, O-RAN, DePIN, DLT, sensor, digital twin, geospatial, and Earth observation observability methods;
k) degraded-mode awareness;
l) resilience indicators;
m) dashboard and map public-safe review;
n) sensor, signal, telemetry, and model-output classification;
o) evidence-room, data-room, clean-room, controlled-room, public authority room, and no-download-room review; and
p) Observatory Records.
The Board shall ensure that Nexus Observatory methods do not create public warning authority, emergency command, public authority action, regulatory approval, procurement approval, finance-readiness, certification, recognition, provider preference, sponsor control, or enterprise execution. Observatory methods shall support learning, evidence, technical literacy, and public-safe awareness within bounded institutional authority.
116.11 Data / AI / Cyber / Privacy Strategy. The Board shall oversee the Corporation’s data governance, AI governance, cybersecurity, privacy, secure compute, repository security, model governance, inference record, compute workload, and digital trust strategy.
The data / AI / cyber / privacy strategy shall address, as applicable:
a) data classification;
b) personal information;
c) rights-bearing data;
d) public authority data;
e) health-sensitive data;
f) cyber-sensitive and infrastructure-sensitive data;
g) community-protected data;
h) Tribal, Indigenous, local, territorial, cultural, environmental, and protected knowledge data;
i) cross-border data transfers;
j) sovereign compute and data residency considerations;
k) data minimization, de-identification, pseudonymization, aggregation, redaction, access control, retention, deletion, sealing, and secure disposal;
l) AI governance, model registers, dataset cards, model cards, system cards, benchmark cards, evaluation harnesses, agentic AI controls, model-use approvals, inference records, compute workload records, and human-review requirements;
m) cybersecurity baseline, identity, access, keys, credentials, logging, monitoring, vulnerability management, incident response, backup, disaster recovery, business continuity, secure development, secure release, SBOM, signing, provenance, and repository controls;
n) AI-use restrictions for confidential, privileged, public authority-sensitive, finance-sensitive, cyber-sensitive, infrastructure-sensitive, personal, community-protected, Indigenous, Tribal, local, territorial, cultural, environmental, or protected knowledge materials;
o) incident escalation, breach response, notification discipline, public-safe notice, and correction; and
p) auditability, recordkeeping, legal holds, and review cycles.
The Board shall ensure that no AI system, dashboard, automated score, digital twin, DePIN record, DLT record, blockchain entry, proof receipt, sensor signal, inference output, compute output, or cyber tool becomes institutional authority without lawful human authorization and records. The strategy shall prohibit unapproved AI uploads of restricted materials and shall preserve confidentiality, privilege, security, public trust, and correctionability.
116.12 Public Authority Learning Strategy. The Board shall oversee the Corporation’s public authority learning strategy and shall ensure that engagements with federal, state, territorial, District of Columbia, Tribal, Indigenous government, local, county, municipal, metropolitan, port, utility, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, infrastructure, and other public authority participants remain lawful, classified, bounded, non-executing, public-safe, and record-supported.
The public authority learning strategy may include, without limitation:
a) evidence literacy;
b) technical literacy;
c) public-safe reporting literacy;
d) AI governance literacy;
e) cybersecurity literacy;
f) data governance literacy;
g) resilience and systemic risk literacy;
h) scenario sessions;
i) simulations;
j) tabletop exercises;
k) after-action learning;
l) regulator-listening rooms;
m) public finance reader rooms;
n) emergency-management learning rooms;
o) public infrastructure operator rooms;
p) public authority rooms;
q) controlled rooms, clean rooms, evidence rooms, data rooms, and no-download rooms;
r) capacity classification; and
s) public authority reference controls.
The Board shall ensure that public authority learning does not become public authority delegation, official adoption, sovereign obligation, public-private partnership, procurement approval, funding approval, grant approval, public finance approval, regulatory approval, legal safe harbor, public warning, emergency command, permit, compliance approval, vendor selection, or governmental decision. Every material public authority engagement shall identify capacity, authority, limitations, public-safe language, records, and correction pathways.
116.13 Community Safeguards Strategy. The Board shall oversee the Corporation’s community safeguards, Tribal and Indigenous protocol, protected knowledge, civil rights, accessibility, public-safe mapping, grievance, remedy, protected participation, non-retaliation, and do-no-harm strategy.
The community safeguards strategy shall address, as applicable:
a) Tribal sovereignty respect;
b) Indigenous governance interface respect;
c) Indigenous data safeguards;
d) Indigenous knowledge safeguards;
e) local and territorial knowledge safeguards;
f) cultural, environmental, community-protected, and protected knowledge safeguards;
g) civil rights and non-discrimination;
h) accessibility;
i) vulnerable community protections;
j) remote community protections;
k) disaster-exposed, climate-exposed, health-exposed, infrastructure-exposed, and high-risk community protections;
l) public-safe mapping review;
m) consent, non-consent, attribution, withdrawal, restriction, correction, and complaint pathways;
n) grievance and remedy processes;
o) protected participation, whistleblowing, dissent protection, confidential reporting, and non-retaliation;
p) do-no-harm review;
q) stop-the-line escalation; and
r) records of safeguards review, outcomes, limitations, corrections, and remedies.
The Board shall ensure that research, evidence, observability, public-good software, technical baselines, dashboards, maps, datasets, models, public authority learning, sponsor-supported work, provider-supported work, host-site work, Nexus interfaces, and public-safe publications do not extract, expose, misuse, commercialize, over-map, over-disclose, or overclaim community, Tribal, Indigenous, local, territorial, cultural, environmental, or protected knowledge. Institutional convenience, technical interest, sponsor preference, provider preference, donor pressure, public authority interest, media interest, publication urgency, or funding deadline shall not override safeguards.
116.14 United States All-States-and-Territories Strategy. The Board shall oversee the Corporation’s United States all-states-and-territories strategy and shall ensure that national operation, state localization, territorial localization, District of Columbia engagement, Tribal interface respect, local interface coordination, public authority engagement, charitable solicitation, tax, employment, privacy, data, AI, cyber, public records, open meetings, procurement, lobbying, grant, contract, host-site, public-safe publication, and safeguards matters are managed through lawful and recorded processes.
The United States all-states-and-territories strategy may address, without limitation:
a) all fifty states;
b) the District of Columbia;
c) Puerto Rico;
d) Guam;
e) the U.S. Virgin Islands;
f) American Samoa;
g) the Northern Mariana Islands;
h) Tribal nations and Indigenous governments where lawfully and respectfully engaged;
i) federal public authority interfaces;
j) state public authority interfaces;
k) territorial public authority interfaces;
l) Tribal public authority interfaces;
m) local, county, municipal, metropolitan, port, utility, public health, emergency management, public safety, public works, water, energy, food, telecom, cyber, and infrastructure interfaces;
n) interstate and interjurisdictional systems;
o) state qualification, foreign qualification, charitable solicitation, tax, employment, privacy, public records, procurement, lobbying, grant, contracting, and registration review; and
p) state and territorial localization schedules, compatibility notes, divergence logs, and records.
The Board shall ensure that localization does not fragment the Corporation’s constitutional protections. No state, territorial, Tribal, local, host, sponsor, provider, public authority, or program-specific arrangement shall weaken mission lock, legal identity, United States seat discipline, non-execution, controlled vocabulary, records discipline, public-good purpose, public authority boundary, finance boundary, data / AI / cyber controls, safeguards, validity-by-record, or correctionability.
116.15 North America Anchor Strategy. The Board shall oversee the Corporation’s North America anchor strategy and shall ensure that the Corporation’s cross-border evidence architecture, methods continuity, observability support, ontology alignment, public-good software support, technical baseline support, public authority learning support, and Nexus interface support are lawful, bounded, cooperative, and non-executing.
The North America anchor strategy may address, without limitation:
a) coordination with GCRI Canada;
b) lawful coordination with Mexico, Caribbean, Arctic, Great Lakes, Pacific, Atlantic, Gulf, border, Indigenous, regional, and cross-border interfaces;
c) North America hazard, infrastructure, climate, cyber, public health, energy, water, food, biodiversity, telecom, supply chain, disaster, port, border, and systemic risk evidence support;
d) North America observability methods support;
e) North America data, AI, cyber, sovereign compute, cross-border transfer, protected knowledge, and safeguards support;
f) North America public-good software and technical baseline support;
g) North America Nexus Universe, Nexus Observatory, Nexus Standards, Nexus Grid, Nexus Rails, Nexus Academy, and Nexus Competence Cell alignment support;
h) public authority learning without public authority delegation;
i) compatibility notes, divergence logs, equivalence notes, and cross-border records; and
j) public-safe language preventing North America anchor overclaim.
The Board shall ensure that the North America anchor strategy does not create treaty authority, sovereign authority, intergovernmental authority, regional regulator authority, public finance authority, emergency command authority, public warning authority, procurement authority, certification authority, recognition authority, finance-readiness authority, public authority delegation, merger, agency, partnership, common treasury, shared liability, single employer, joint employer, or enterprise execution authority.
116.16 Nexus Interface Strategy. The Board shall oversee the Corporation’s Nexus interface strategy and shall ensure that all interfaces with GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, Global Nexus Consortium, Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, national companies, Project SPVs, qualified enterprise providers, sponsors, hosts, funders, public authorities, universities, laboratories, communities, and enterprise-stack actors are lawful, role-separated, record-supported, public-safe, and correctionable.
The Nexus interface strategy shall preserve:
a) GCRI US as evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, verifiable compute and intelligence methods, public authority learning, and safeguards steward within its lawful United States and North America role;
b) GRF as public-good registry, recognition, maturity-records, standing, claims-discipline, stakeholder-formation, public-safe reporting, and public-facing legitimacy steward;
c) GRA as finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, capital-reader room, and regulated-perimeter discipline steward;
d) Nexus Standards and protocol authority as separate standards and protocol functions where lawfully constituted;
e) Nexus Network as the public-good infrastructure rail;
f) national companies and Project SPVs as enterprise-stack actors where separately and lawfully formed;
g) qualified enterprise providers as enterprise delivery actors subject to neutrality and non-control rules; and
h) sponsors, hosts, donors, funders, public authorities, universities, laboratories, communities, media, and civil society as participants only within their recorded capacities.
No Nexus interface strategy shall collapse the one rail / two stacks structure, convert evidence into recognition, convert readiness inputs into finance-readiness determinations, convert technical baselines into certification or procurement mandates, convert Observatory outputs into public warnings, convert proof receipts into authority, convert public authority participation into public authority action, or convert public-good support into sponsor control.
116.17 Financial Sustainability Strategy. The Board shall oversee the Corporation’s financial sustainability strategy and shall ensure that the Corporation has lawful, diversified, mission-compatible, non-controlling, tax-compliant, public-benefit-aligned, and record-supported financial resources sufficient to carry out its purposes without compromising independence or public trust.
The financial sustainability strategy may include, without limitation:
a) grants;
b) donations;
c) sponsorships;
d) subscriptions;
e) lawful fees;
f) cost recovery;
g) training and Academy fees;
h) fellowships, scholarships, stipends, awards, and challenge support;
i) restricted funds;
j) unrestricted support;
k) in-kind contributions;
l) public-good infrastructure support;
m) public-benefit collaborations;
n) philanthropic partnerships;
o) university and laboratory support;
p) host support;
q) public authority learning support where lawful; and
r) reserves, insurance, internal controls, financial reporting, and continuity planning.
The Board shall ensure that financial sustainability does not depend on improper private benefit, private inurement, donor control, sponsor control, provider preference, host control, public authority access purchase, research finding purchase, publication veto, outcome purchase, recognition purchase, finance-readiness purchase, certification purchase, procurement advantage, public warning influence, or regulated execution. Support concentration, restricted fund dependence, sponsor dependence, provider dependence, host dependence, donor dependence, grant dependence, and public authority funding dependence shall be reviewed for capture risk.
116.18 Anti-Capture Strategy. The Board shall oversee the Corporation’s anti-capture strategy and shall ensure that governance, evidence, methods, publications, technical assets, public authority learning, controlled rooms, data rooms, software, dashboards, maps, repositories, public claims, funding, sponsorship, provider participation, host participation, Nexus interfaces, and strategic priorities are not captured by private, commercial, political, public authority, sponsor, provider, donor, funder, host, investor, insurer, lender, national company, Project SPV, technology vendor, or enterprise-stack interests.
The anti-capture strategy may include, without limitation:
a) conflict-of-interest policies;
b) related-party transaction controls;
c) independence reviews;
d) sponsor non-control policies;
e) provider-neutrality policies;
f) donor and funder non-control policies;
g) host non-control policies;
h) influence cap review;
i) support concentration review;
j) recusal and access restriction;
k) clean-room and clean-team structures;
l) competition and antitrust discipline;
m) public authority capacity classification;
n) public-safe claims controls;
o) controlled vocabulary;
p) publication independence;
q) research independence;
r) technical asset anti-enclosure controls;
s) public acknowledgment limits;
t) Board reserved matter controls;
u) committee and council authority limits; and
v) correction, withdrawal, retraction, takedown, public clarification, or termination pathways.
The Board shall treat capture risk as a strategic risk. Where capture risk cannot be mitigated through lawful conditions, disclosure, recusal, diversification, ring-fencing, narrowing, independent review, or public-safe limitation, the Corporation shall refuse, return, restrict, terminate, quarantine, re-scope, externalize, or withdraw from the relevant relationship or activity.
116.19 Strategy Records. The Corporation shall maintain Strategy Records sufficient to demonstrate that strategic oversight, annual strategy, multi-year strategy, public-benefit strategy, evidence strategy, methods strategy, observability strategy, ontology strategy, public-good R&D strategy, public-good software strategy, Nexus Truth Engine methods strategy, Nexus Observatory methods strategy, data / AI / cyber / privacy strategy, public authority learning strategy, community safeguards strategy, United States all-states-and-territories strategy, North America anchor strategy, Nexus interface strategy, financial sustainability strategy, and anti-capture strategy were developed, reviewed, approved, implemented, monitored, corrected, superseded, withdrawn, or archived through lawful authority and in conformity with this Bylaw.
Strategy Records shall include, as applicable:
a) Board strategy resolutions;
b) annual strategy records;
c) multi-year strategy records;
d) annual plan records;
e) budget alignment records;
f) strategic risk records;
g) public-benefit alignment records;
h) mission-lock review records;
i) non-execution review records;
j) role-separation review records;
k) public authority boundary review records;
l) finance-boundary, securities-boundary, insurance-boundary, lending-boundary, rating-boundary, public finance-boundary, procurement-boundary, certification-boundary, recognition-boundary, provider-neutrality, and sponsor non-control review records;
m) evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, Nexus Truth Engine, Nexus Observatory, verifiable compute, verifiable intelligence, and technical asset strategy records;
n) data governance, privacy, AI governance, cybersecurity, secure compute, repository, model register, inference record, compute workload, secure release, SBOM, vulnerability, incident response, disaster recovery, and business continuity strategy records;
o) public authority learning, capacity classification, regulator-listening, public finance reader, emergency-management participant, public infrastructure operator, controlled-room, clean-room, data-room, evidence-room, public authority room, and no-download-room strategy records;
p) community safeguard, Tribal / Indigenous protocol, Indigenous data, protected knowledge, local and territorial knowledge, civil-rights, accessibility, public-safe mapping, grievance, remedy, protected participation, non-retaliation, and stop-the-line strategy records;
q) United States all-states-and-territories, state localization, territorial localization, District of Columbia, Tribal interface, local interface, and North America interface records;
r) GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortium, national company, Project SPV, provider, sponsor, host, public authority, university, laboratory, community, and enterprise-stack interface strategy records;
s) financial sustainability, support diversification, grant, donation, sponsorship, subscription, fee, cost-recovery, restricted fund, in-kind support, reserve, audit, insurance, and anti-capture strategy records;
t) committee recommendations, officer reports, counsel reviews, compliance reviews, technical reviews, safeguards reviews, minority views, dissent notes where permitted, public-safe notices, controlled notices, public summaries, and implementation records;
u) strategic corrections, holds, quarantines, re-scoping actions, refusals, terminations, withdrawals, supersessions, public clarifications, and archive records; and
v) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that strategy shall be ambitious but bounded, public-good but legally disciplined, technically serious but non-executing, ecosystem-aware but role-separated, public-facing but public-safe, finance-readable only through proper interfaces, authority-aware without becoming authority, and correctionable by record. No strategic plan, annual plan, board deck, public roadmap, technical roadmap, sponsor proposal, grant proposal, public authority discussion, Nexus interface, dashboard, proof receipt, AI output, repository milestone, event commitment, or publication calendar shall authorize the Corporation to exceed its lawful purposes, weaken its nonprofit character, compromise public-benefit mission, collapse GCRI / GRF / GRA separation, confuse public authority roles, conduct regulated execution, create finance-readiness, certify, approve procurement, recognize standing, prefer providers, grant sponsor control, misuse data or AI, weaken cybersecurity, expose protected knowledge, ignore safeguards, or evade correctionability.
Section 117. Legal, Tax, Compliance, and Regulatory-Perimeter Oversight
117.1 Legal Compliance Oversight. The Board shall oversee the Corporation’s legal compliance architecture and shall ensure that the Corporation, its directors, officers, committees, councils, working groups, employees, contractors, fellows, advisors, volunteers, contributors, participants, supporters, sponsors, donors, funders, providers, hosts, public authority participants, university participants, laboratory participants, community participants, repository users, controlled-room participants, and Nexus-interface actors acting within or through the Corporation operate only within lawful authority, recorded delegation, approved scope, and applicable legal requirements.
Legal compliance oversight shall include, without limitation:
a) corporate existence, good standing, governance, filings, registered agent, registered office, principal office, minute books, resolutions, director records, officer records, member records where applicable, committee records, and official registers;
b) federal, state, territorial, District of Columbia, Tribal-interface, local, and cross-border legal review where applicable;
c) nonprofit, non-stock or non-share, non-distribution, tax-exempt or tax-exempt-compatible, public-benefit, charitable solicitation, grant, donation, sponsorship, restricted fund, and public support compliance;
d) contracts, MoUs, interface agreements, sponsorship agreements, donor agreements, grant agreements, public authority instruments, university agreements, laboratory agreements, host agreements, provider agreements, vendor agreements, contributor agreements, data agreements, software agreements, licensing instruments, repository terms, controlled-room terms, and Nexus interface instruments;
e) data governance, privacy, AI governance, cybersecurity, research ethics, public-safe publication, intellectual property, open-source, export-control, sanctions, competition, civil rights, accessibility, employment, contractor, volunteer, fellow, advisor, workplace, public authority, procurement-integrity, lobbying, political activity, government ethics, and professional-boundary compliance;
f) legal review of regulated-perimeter risks involving securities, investment advice, broker-dealer activity, finder activity, banking, lending, insurance, underwriting, rating, public finance, public procurement, certification, accreditation, recognition, public authority decisions, public warnings, emergency command, and enterprise execution;
g) preservation of GCRI US legal separateness from GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, qualified enterprise providers, sponsors, hosts, funders, public authorities, universities, laboratories, communities, and enterprise-stack actors; and
h) correction, withdrawal, retraction, takedown, quarantine, legal hold, privilege, controlled notice, public-safe notice, and remediation where legal error, ambiguity, overclaim, breach, or risk is identified.
The Board shall ensure that legal compliance is not treated as a box-checking function. Legal compliance shall be a continuous governance obligation, a condition of institutional legitimacy, a protection against role inflation, and a mechanism for preserving the Corporation’s public-benefit purpose, non-execution perimeter, public authority boundary, finance boundary, certification boundary, procurement-neutrality boundary, provider-neutrality boundary, sponsor non-control rule, data / AI / cyber controls, safeguards, validity-by-record, and correctionability.
117.2 State Nonprofit Corporate Compliance Oversight. The Board shall oversee compliance with the nonprofit corporation law of the Corporation’s state of incorporation or organization and any other state nonprofit corporate law applicable to the Corporation’s operations, qualifications, registrations, programs, public representations, property, contracts, employees, public authority interfaces, charitable solicitation, fundraising, or activities.
State nonprofit corporate compliance oversight shall include, without limitation:
a) maintenance of corporate existence and good standing;
b) compliance with the Articles or Certificate;
c) compliance with this Bylaw;
d) compliance with director duties, officer duties, member rights where applicable, notice rules, quorum rules, voting rules, written consent rules, meeting rules, recordkeeping rules, inspection rights, indemnification rules, conflict rules, merger rules, dissolution rules, asset disposition rules, and amendment rules;
e) annual reports, franchise or entity taxes where applicable, registered agent records, registered office records, principal office records, assumed name filings where applicable, and foreign qualification records;
f) governance of state-specific, territorial-specific, public authority-specific, host-specific, program-specific, or Nexus-interface-specific instruments so that no local instrument silently amends the Bylaw or fragments corporate governance;
g) oversight of director and officer authority so that state law rights, duties, limits, and approvals are respected;
h) review of related-party transactions, conflicts, private benefit, restricted assets, charitable trust constraints where applicable, and dissolution or asset-distribution constraints; and
i) preservation of legal continuity, records integrity, repository accuracy, notice discipline, and correction pathways.
No state filing, registration, assumed name, license, qualification, public authority reference, state program description, local interface, or jurisdictional schedule shall be treated as authority to expand the Corporation’s purposes, create public authority status, create finance-readiness authority, create certification authority, create procurement authority, create recognition authority, prefer providers, grant sponsor control, or conduct enterprise execution.
117.3 Federal Tax Compliance Oversight. The Board shall oversee federal tax compliance and shall ensure that the Corporation’s purposes, activities, revenues, expenses, support arrangements, compensation, reimbursements, transactions, public statements, receipts, restricted funds, sponsorships, subscriptions, fees, cost recovery, grants, donations, in-kind support, public authority learning activities, technical assets, publications, software releases, controlled rooms, academy programs, fellowships, and Nexus interface activities remain compatible with the Corporation’s actual and recorded federal tax status.
Federal tax compliance oversight shall include, without limitation:
a) federal tax classification;
b) tax-exempt application, recognition, maintenance, revocation, or change where applicable;
c) Section 501(c)(3), Section 501(c)(4), Section 501(c)(6), supporting organization, fiscal sponsorship, sponsored project, public charity, private foundation, or other status only where lawfully adopted and recorded;
d) no private inurement;
e) no impermissible private benefit;
f) excess benefit transaction review where applicable;
g) unrelated business income review where applicable;
h) lobbying and political activity controls where applicable;
i) donor receipt and contribution acknowledgment controls;
j) sponsorship revenue classification;
k) subscription, fee, academy, training, publication, controlled-room, repository, benchmarking, fellowship, challenge, cost-recovery, and technical-access revenue classification;
l) restricted fund and grant compliance;
m) compensation reasonableness and reimbursement controls;
n) related-party transaction review;
o) tax filings, extensions, information returns, public inspection requirements where applicable, and record retention; and
p) tax consequences of cross-border, state, territorial, public authority, host, provider, sponsor, donor, university, laboratory, consortium, national company, Project SPV, or Nexus interface arrangements.
No director, officer, fundraiser, grant writer, sponsor, donor, funder, provider, host, public authority participant, public-facing material, website, repository notice, receipt, acknowledgment, or AI-generated communication shall state or imply a tax status, deductibility status, charitable status, fiscal sponsorship status, public charity status, or tax benefit that is not supported by competent records.
117.4 State Tax, Franchise Tax, Charitable Solicitation, and Foreign Qualification Oversight. The Board shall oversee state tax, local tax, franchise tax, charitable solicitation, fundraising registration, exemption registration, foreign qualification, business registration, assumed-name registration, sales and use tax, employment tax, payroll tax, property tax, and other state or local compliance obligations where applicable to the Corporation’s operations.
Such oversight shall include, without limitation:
a) state and territorial qualification to do business where required;
b) charitable solicitation registration and renewal where required;
c) fundraising registration, professional fundraiser review, commercial co-venturer review, and campaign-specific review where applicable;
d) state income, franchise, sales, use, gross receipts, property, employment, payroll, and local tax analysis where applicable;
e) registration consequences of remote operations, controlled rooms, public authority rooms, events, trainings, academy programs, subscriptions, fees, cost recovery, grants, sponsorships, donations, in-kind contributions, technical access, repository access, host-site activities, public-safe publications, and state-specific programs;
f) state and territorial treatment of donor acknowledgments, sponsorship benefits, program fees, subscriptions, publications, software, datasets, dashboards, technical baselines, and public-good assets;
g) review of all-states-and-territories posture, District of Columbia posture, Puerto Rico posture, Guam posture, U.S. Virgin Islands posture, American Samoa posture, Northern Mariana Islands posture, Tribal-interface posture, and local-interface posture;
h) correction of improper public statements, donor receipts, solicitation materials, tax descriptions, state references, registration claims, public authority references, or localization claims; and
i) records of filings, confirmations, renewals, exemptions, notices, deadlines, responsible owners, and compliance status.
No fundraising campaign, public support campaign, grant campaign, sponsorship campaign, academy campaign, challenge campaign, public authority learning activity, host-site program, Nexus interface, state-specific event, or public-safe publication shall proceed in a jurisdiction where required registration, filing, legal review, or limitation language has been omitted and the omission creates material legal risk.
117.5 Privacy Compliance Oversight. The Board shall oversee privacy compliance and shall ensure that the Corporation’s collection, receipt, access, storage, processing, analysis, sharing, publication, retention, deletion, sealing, archival, and disposal of personal information and rights-bearing data are lawful, proportionate, purpose-limited, secure, public-safe, and correctionable.
Privacy compliance oversight shall include, without limitation:
a) privacy law mapping across federal, state, territorial, District of Columbia, Tribal-interface, local, cross-border, and sector-specific contexts where applicable;
b) privacy classification of personal information, sensitive personal information, children’s data, health-sensitive data, public authority data, community-protected data, Indigenous data, local and territorial knowledge, cyber-sensitive data, infrastructure-sensitive data, location data, geospatial data, biometric data, audio, video, image, telemetry, device, and digital interaction data where applicable;
c) lawful basis, consent, notice, limitation, minimization, purpose specification, access control, role-based access, logging, retention, deletion, de-identification, pseudonymization, aggregation, redaction, and secure disposal;
d) privacy-by-design review for dashboards, maps, datasets, APIs, SDKs, repositories, software, observability methods, AI systems, digital twins, sensor systems, data rooms, controlled rooms, clean rooms, evidence rooms, no-download rooms, and public authority rooms;
e) third-party processor, vendor, cloud, AI provider, cybersecurity provider, university, laboratory, host, sponsor, donor, funder, provider, public authority, and Nexus interface privacy controls;
f) cross-border transfer review, sovereign compute review, data residency review, transfer agreement review, and access restriction where applicable;
g) privacy incident review, breach response, notification discipline, legal hold, privilege, public-safe communication, correction, and remediation; and
h) privacy records sufficient to demonstrate lawful handling, limitation, correction, deletion, and accountability.
No public-benefit purpose, research interest, technical interest, public authority interest, sponsor request, provider request, host request, donor condition, publication deadline, repository milestone, dashboard launch, AI use, proof receipt, or Nexus interface shall justify privacy overcollection, unlawful processing, unsafe publication, uncontrolled disclosure, or failure to correct.
117.6 AI Governance Compliance Oversight. The Board shall oversee AI governance compliance and shall ensure that AI systems, model outputs, agentic AI tools, automated scores, inference systems, decision-support systems, evaluation tools, benchmark systems, retrieval systems, embedding systems, digital twins, dashboards, synthetic data systems, autonomous workflows, and AI-assisted publication or governance tools are used only within approved scope, lawful authority, human-review requirements, data restrictions, public-safe limitations, cybersecurity controls, and records discipline.
AI governance compliance oversight shall include, without limitation:
a) AI system classification;
b) model register requirements;
c) dataset card, model card, system card, benchmark card, and evaluation harness requirements;
d) inference record requirements;
e) compute workload record requirements;
f) agentic AI approval, monitoring, and restriction;
g) human review for material outputs;
h) prohibited AI uses;
i) restricted AI uses;
j) AI use in research, evidence review, observability, ontology, public authority learning, public-safe publication, software development, controlled rooms, data rooms, clean rooms, public authority rooms, legal review support, finance-boundary review support, and safeguards review;
k) controls against uploading confidential, privileged, public authority-sensitive, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, personal, health-sensitive, community-protected, Tribal, Indigenous, local, territorial, cultural, environmental, or protected knowledge materials into unapproved AI systems;
l) AI bias, discrimination, civil rights, accessibility, and public-safety review where applicable;
m) AI hallucination, model error, source confusion, provenance weakness, false confidence, synthetic evidence, deepfake, spoofing, adversarial input, prompt-injection, data leakage, and model misuse controls;
n) AI incident response, correction, supersession, withdrawal, public clarification, takedown, and archive; and
o) AI governance records.
No AI output, model output, agentic output, automated score, dashboard output, digital twin output, inference output, benchmark output, synthetic output, proof receipt, ledger entry, AI-RAN signal, O-RAN signal, DePIN signal, sensor signal, or compute output shall be treated as institutional authority, technical truth, public warning, emergency command, public authority decision, recognition, finance-readiness determination, insurance-readiness determination, certification, procurement approval, rating, provider approval, or operational authorization without competent human review, lawful authority, and record support.
117.7 Cybersecurity Compliance Oversight. The Board shall oversee cybersecurity compliance and shall ensure that the Corporation maintains cybersecurity governance, secure development, secure operations, access control, incident response, business continuity, disaster recovery, and technical asset protection appropriate to its public-benefit mission, data sensitivity, public authority interfaces, controlled rooms, repositories, public-good software, technical baselines, and Nexus-compatible role.
Cybersecurity compliance oversight shall include, without limitation:
a) cybersecurity policies, standards, controls, procedures, and review cycles;
b) identity, authentication, authorization, role-based access, privileged access, key management, credential management, token management, secret management, logging, monitoring, alerting, and access review;
c) repository security, branch protection, code review, dependency review, license review, vulnerability scanning, SBOM generation, artifact signing, provenance, build integrity, release integrity, rollback, and secure deprecation;
d) cloud security, endpoint security, network security, application security, data-room security, controlled-room security, clean-room security, evidence-room security, no-download-room security, public authority room security, and board-system security;
e) protection of cyber-sensitive, infrastructure-sensitive, public authority-sensitive, personal, health-sensitive, community-protected, Tribal, Indigenous, protected knowledge, and controlled-technology materials;
f) vulnerability disclosure, incident response, breach response, cyber event triage, containment, eradication, recovery, notification, law enforcement interface, public authority notice, public-safe communication, and post-incident review;
g) business continuity, backup, disaster recovery, continuity of operations, recovery time objectives, recovery point objectives, successor administrator plans, data portability, exit assistance, suspension, wind-down, and orderly transfer;
h) vendor, contractor, AI provider, cloud provider, repository provider, cybersecurity provider, data processor, host, sponsor, donor, public authority, university, laboratory, provider, and Nexus interface cyber controls; and
i) cybersecurity records, incident records, access records, vulnerability records, release records, repository records, and correction records.
No technical urgency, publication deadline, event deadline, grant deadline, public authority request, sponsor request, provider request, repository milestone, or operational convenience shall justify bypassing cybersecurity controls where bypass would create material risk to the Corporation, public-benefit mission, protected persons, protected knowledge, public authority interfaces, data integrity, repository integrity, or public trust.
117.8 Research Ethics Compliance Oversight. The Board shall oversee research ethics compliance and shall ensure that the Corporation’s research, public-good R&D, evidence work, observability work, methods work, AI work, public authority learning, community engagement, data collection, technical testing, controlled-room review, publications, datasets, dashboards, maps, and software releases are conducted with integrity, lawful authority, appropriate review, participant protections, safeguards, and correction pathways.
Research ethics compliance oversight shall include, without limitation:
a) research integrity policies;
b) research ethics review pathways;
c) human-subjects review where applicable;
d) IRB or equivalent review where applicable;
e) health-sensitive, youth, vulnerable population, disaster-exposed, climate-exposed, infrastructure-exposed, remote community, and high-risk participant review;
f) community review where appropriate;
g) Tribal and Indigenous protocol review where applicable;
h) Indigenous data and protected knowledge review;
i) local, territorial, cultural, environmental, and community-protected knowledge review;
j) informed consent, consent, non-consent, withdrawal, restriction, attribution, complaint, correction, and remedy pathways where applicable;
k) privacy, confidentiality, data minimization, de-identification, pseudonymization, aggregation, redaction, and public-safe presentation;
l) research conflict disclosure, sponsor disclosure, funder disclosure, provider disclosure, host disclosure, public authority involvement disclosure, and publication independence;
m) peer review, red-team review, model review, evidence challenge, reproducibility, replication, and publication integrity;
n) research misconduct intake, review, correction, retraction, withdrawal, takedown, archive, and notification; and
o) research ethics records.
No research, evidence, observability, AI, dashboard, map, public authority learning, host-site, sponsor-supported, provider-supported, or Nexus-interface activity shall proceed where ethical review is required and absent, where consent or safeguards are materially defective, or where protected knowledge, civil rights, accessibility, community safety, or public-safe publication risks cannot be lawfully mitigated.
117.9 Employment, Contractor, Volunteer, Fellow, Advisor, and Workplace Compliance Oversight. The Board shall oversee employment, contractor, volunteer, fellow, advisor, seconded personnel, workplace, classification, compensation, benefits, reimbursement, occupational safety, anti-harassment, non-discrimination, accessibility, whistleblowing, non-retaliation, confidentiality, IP, data, AI, cyber, and offboarding compliance.
Such oversight shall include, without limitation:
a) employee classification;
b) contractor classification;
c) volunteer and unpaid role classification;
d) fellow, intern, visiting researcher, advisor, consultant, seconded personnel, and contributor classification;
e) offer letters, employment agreements, contractor agreements, fellowship terms, advisor terms, volunteer terms, contributor terms, secondment terms, confidentiality agreements, IP agreements, data access terms, AI-use acknowledgments, cybersecurity acknowledgments, and public-safe claims acknowledgments;
f) wage, hour, payroll, tax, benefits, leave, workplace safety, insurance, accessibility, accommodation, anti-harassment, anti-discrimination, civil rights, whistleblower, non-retaliation, grievance, and remedy compliance;
g) conflicts, outside activities, related-party transactions, public authority relationships, sponsor relationships, provider relationships, donor relationships, funder relationships, host relationships, university relationships, laboratory relationships, national company relationships, Project SPV relationships, and enterprise relationships;
h) onboarding, training, supervision, performance review, corrective action, suspension, termination, resignation, offboarding, access revocation, return or deletion of materials, legal hold, and record retention; and
i) employment and workforce compliance records.
No title, fellowship, advisory role, contributor role, technical role, public authority contact role, repository access, controlled-room access, public platform role, or leadership proximity shall create authority to bind the Corporation unless the person is lawfully appointed, delegated, and recorded.
117.10 Accessibility and Civil Rights Compliance Oversight. The Board shall oversee accessibility, civil rights, non-discrimination, inclusive participation, language access where adopted, disability accommodation, public-safe communication, community safeguards, protected participation, grievance, remedy, and non-retaliation compliance.
Accessibility and civil rights compliance oversight shall include, without limitation:
a) compliance with applicable federal, state, territorial, District of Columbia, local, public authority, grant, contract, and program-specific civil rights and accessibility obligations;
b) accessibility of governance notices, participation materials, websites, public-safe publications, training materials, Academy materials, controlled-room materials where feasible, public authority learning materials, public summaries, dashboards, maps, software documentation, and public-good technical assets;
c) accessible meeting, virtual meeting, hybrid meeting, controlled-room, public authority room, academy, fellowship, challenge, lab, and public engagement practices where applicable;
d) non-discrimination and anti-harassment controls;
e) protections for vulnerable, remote, underserved, disaster-exposed, climate-exposed, health-exposed, infrastructure-exposed, and historically burdened communities;
f) review of public-safe maps, dashboards, datasets, geospatial outputs, AI outputs, automated scores, and observability outputs for disparate impact, stigmatizing presentation, overexposure, or public-safety harm;
g) grievance, remedy, correction, non-retaliation, and protected participation pathways; and
h) accessibility and civil rights records.
No technical design, publication format, event format, controlled-room format, data-room format, software release, dashboard, map, AI system, public authority learning product, or Nexus interface shall be approved where avoidable accessibility exclusion, civil rights risk, discriminatory impact, unsafe public presentation, or unremedied participation barrier materially undermines public-benefit purpose.
117.11 Lobbying, Political Activity, Government Ethics, Gifts, Grant, and Procurement Integrity Oversight Where Applicable. The Board shall oversee lobbying, political activity, campaign intervention, government ethics, gifts, hospitality, conflicts, public authority interaction, grant compliance, procurement integrity, and public-sector engagement compliance where applicable.
Such oversight shall include, without limitation:
a) classification of lobbying activity where applicable;
b) limits on lobbying under the Corporation’s actual tax status;
c) prohibition or control of political campaign intervention where applicable;
d) registration, reporting, and expenditure tracking where required;
e) government ethics, gift, travel, hospitality, revolving-door, conflict, and appearance-of-impropriety controls;
f) public authority participant capacity classification;
g) public procurement integrity controls;
h) grant compliance, federal award compliance, state grant compliance, public authority funding compliance, and subaward compliance where applicable;
i) public authority meeting records, agenda controls, minutes controls, no-official-adoption language, and public-safe notices;
j) controls against using public authority learning, controlled rooms, data rooms, evidence rooms, dashboards, maps, reports, proof receipts, technical baselines, or publications to influence procurement, funding, grants, regulation, enforcement, public finance, or public authority decisions outside lawful channels; and
k) lobbying, political activity, government ethics, gifts, grant, and procurement integrity records.
The Corporation shall not use its public-benefit mission, technical credibility, public authority learning role, Nexus interface, public-safe publication, or controlled-room access to create improper influence, pay-to-play arrangements, procurement advantage, funding advantage, public authority endorsement, public finance approval, or regulatory advantage.
117.12 Sanctions and Export-Control Oversight. The Board shall oversee sanctions and export-control compliance and shall ensure that the Corporation’s activities, relationships, transactions, technical assets, software, datasets, models, controlled rooms, public authority rooms, evidence rooms, data rooms, repositories, publications, cross-border interfaces, sponsors, donors, funders, providers, hosts, contractors, contributors, fellows, advisors, universities, laboratories, public authorities, and Nexus interfaces are reviewed for applicable sanctions, export-control, restricted-party, embargo, controlled-technology, and national security sensitivity risks.
Sanctions and export-control oversight shall include, without limitation:
a) sanctions screening of persons, entities, counterparties, beneficial owners, controllers, funders, sponsors, donors, providers, hosts, contractors, contributors, and relevant participants where appropriate;
b) export-control classification review for software, datasets, models, technical baselines, cybersecurity materials, encryption materials, AI systems, AI-RAN materials, O-RAN materials, DePIN materials, DLT materials, sensor systems, drones, robotics, geospatial materials, Earth observation materials, digital twins, dual-use technologies, controlled technology, and technical assistance where applicable;
c) review of foreign nationals, cross-border access, deemed export risk, controlled-room access, repository access, no-download-room access, public authority room access, and technical support;
d) review of sanctioned jurisdictions, embargoed regions, restricted entities, restricted sectors, government end users, military end users, dual-use end users, prohibited end uses, and diversion risks where applicable;
e) restrictions, refusals, holds, quarantines, access denials, license determinations, external counsel review, competent authority filings, and termination where required;
f) training for relevant directors, officers, staff, contributors, maintainers, controlled-room administrators, public authority room administrators, and technical asset custodians; and
g) sanctions and export-control records.
No public-good objective, open-source posture, technical collaboration, research opportunity, public authority request, donor condition, sponsor request, provider request, host request, or Nexus interface shall override sanctions, export-control, controlled-technology, or national security restrictions.
117.13 Controlled Technology and National Security Sensitivity Oversight. The Board shall oversee controlled technology, defense / dual-use, critical infrastructure, national security sensitivity, foreign access, foreign influence, foreign investment sensitivity, cyber sensitivity, infrastructure sensitivity, CFIUS-relevant sensitivity where applicable, and related risk review.
Controlled technology and national security sensitivity oversight shall include, without limitation:
a) classification of controlled technologies and sensitive technical assets;
b) review of AI, AI-RAN, O-RAN, DePIN, DLT, blockchain, Web3, quantum-relevant systems, sovereign compute, HPC, cyber tools, robotics, drones, sensors, geospatial systems, Earth observation, digital twins, biosecurity tools, telecom systems, semiconductor-related materials, advanced manufacturing methods, critical infrastructure telemetry, and other exponential technologies;
c) review of controlled technical data, technical assistance, source code, models, datasets, benchmarks, evaluation harnesses, vulnerability information, threat intelligence, exploit information, cryptographic materials, keys, credentials, and security architecture;
d) access restrictions for controlled rooms, data rooms, evidence rooms, no-download rooms, repositories, public authority rooms, and secure systems;
e) review of foreign participation, cross-border transfers, foreign sponsorship, foreign funding, foreign hosting, foreign provider participation, foreign public authority participation, foreign university or laboratory participation, and foreign-controlled enterprise actors where applicable;
f) protection of public authority-sensitive, cyber-sensitive, infrastructure-sensitive, geospatial-sensitive, protected knowledge, and community-sensitive materials;
g) hold, quarantine, technical isolation, publication freeze, repository restriction, external counsel review, government filing, competent authority notice, refusal, or termination where required; and
h) controlled technology and national security sensitivity records.
The Corporation shall not publish, release, export, transfer, provide access to, or facilitate use of controlled or sensitive technical materials where doing so would violate law, create unacceptable public safety risk, undermine public authority trust, expose protected knowledge, enable misuse, or compromise the Corporation’s public-benefit mission.
117.14 Competition and Antitrust Oversight. The Board shall oversee competition and antitrust compliance and shall ensure that the Corporation’s meetings, committees, councils, forums, working groups, panels, labs, benchmarking, indices, datasets, standards-support activities, technical comparisons, public authority learning, provider participation, sponsor participation, enterprise participation, public-good software, and Nexus interfaces do not become vehicles for unlawful coordination, collusion, exclusion, market allocation, price signaling, bid manipulation, wage coordination, procurement steering, boycott, or competitively sensitive information misuse.
Competition and antitrust oversight shall include, without limitation:
a) do-not-discuss rules;
b) agenda controls;
c) minutes controls;
d) chair and stop-meeting authority;
e) clean-team and clean-room structures;
f) aggregation, de-identification, delay, and independent administration of competitively sensitive information;
g) restrictions on discussions of prices, margins, costs, wages, bids, customers, suppliers, markets, territories, capacity, output, product plans, procurement strategies, competitive strategy, exclusionary conduct, boycotts, or provider selection;
h) review of benchmarking subscriptions, market baseline libraries, provider comparisons, technical comparisons, indices, scoring methods, public dashboards, public reports, procurement-adjacent outputs, and public authority materials;
i) review of sponsor, provider, host, enterprise, national company, Project SPV, investor, insurer, lender, public finance actor, and capital-reader participation in shared rooms; and
j) competition records, incident records, corrective actions, and training records.
No public-good mission, standards-support activity, interoperability goal, public authority learning session, controlled room, data room, benchmarking exercise, dashboard, map, evidence pack, technical baseline, or Nexus interface shall be used to reduce competition, coordinate market behavior, allocate opportunities, exclude competitors, steer procurement, or prefer providers.
117.15 Professional Boundary Oversight. The Board shall oversee professional boundary compliance and shall ensure that the Corporation does not hold itself out as providing legal advice, engineering opinions, medical advice, clinical advice, public health orders, financial advice, investment advice, insurance advice, rating opinions, accounting advice, tax advice, procurement advice, regulatory approvals, compliance certifications, licensed professional services, emergency instructions, or other regulated professional services unless separately and lawfully authorized, competent, insured where required, and recorded.
Professional boundary oversight shall include, without limitation:
a) legal advice boundary;
b) engineering advice boundary;
c) medical, clinical, public health, and safety advice boundary;
d) financial, investment, banking, lending, insurance, underwriting, rating, accounting, tax, and public finance boundary;
e) procurement, certification, accreditation, and compliance approval boundary;
f) emergency command and public warning boundary;
g) public authority decision boundary;
h) environmental, infrastructure, utility, telecom, cyber, data, AI, geospatial, Earth observation, biosecurity, and technical professional boundary where applicable;
i) required limitation language, non-reliance language, controlled vocabulary, public-safe notices, and review pathways; and
j) correction, withdrawal, retraction, takedown, clarification, and referral where professional-boundary confusion occurs.
The Corporation may produce research, evidence, methods, educational materials, technical baselines, public-good software, public-safe reports, dashboards, maps, training, controlled-room materials, public authority learning materials, and Nexus-interface inputs, but such outputs shall not be represented as professional advice, regulated opinions, final determinations, operational instructions, or reliance instruments unless a competent licensed or authorized body separately provides such service under lawful conditions.
117.16 Securities, Investment Adviser, Broker-Dealer, Finder, Insurance, Banking, Lending, Rating, Public Finance, Procurement, Certification, and Public Authority Regulatory-Perimeter Oversight. The Board shall oversee the Corporation’s regulatory-perimeter discipline and shall ensure that no activity, output, meeting, room, dataset, dashboard, map, proof receipt, evidence pack, technical baseline, public-good software, public authority learning material, Nexus interface, sponsor arrangement, provider arrangement, donor arrangement, funder arrangement, host arrangement, grant arrangement, or public statement causes the Corporation to conduct or appear to conduct regulated execution.
Regulatory-perimeter oversight shall include, without limitation:
a) securities offering, securities distribution, capital placement, solicitation, underwriting, broker-dealer, finder, and investment adviser boundaries;
b) investment advice, investment recommendation, suitability, transaction recommendation, portfolio management, asset management, and capital recommendation boundaries;
c) banking, deposit-taking, payment intermediation, custody, clearing, settlement, escrow, treasury execution, and third-party fund control boundaries;
d) lending, credit origination, credit brokerage, credit approval, guarantee, revenue guarantee, performance guarantee, and debt structuring boundaries;
e) insurance, reinsurance, underwriting, placement, pricing, binding, claims handling, insurance approval, and insurability determination boundaries;
f) rating, credit opinion, investment grade opinion, resilience rating, insurance rating, bankability rating, financeability determination, and automated score boundary;
g) public finance approval, tax credit approval, public guarantee, public credit, budget allocation, appropriation, sovereign finance, MDB / DFI approval, and grant approval boundaries;
h) procurement approval, public contract award, vendor selection, provider qualification for public authorities, procurement preference, and procurement recommendation boundaries;
i) certification, accreditation, conformance approval, compliance approval, legal safe harbor, standards approval, recognition, maturity, standing, Docket approval, Grid guarantee, and Nexus-compatible status boundaries;
j) public authority decision, regulatory action, enforcement, permit, public warning, emergency command, public health order, evacuation instruction, dispatch, incident management, and operational control boundaries; and
k) records, limitation language, holds, quarantines, re-scoping actions, referrals, externalization, termination, and public-safe corrections.
The Board shall ensure that GCRI US remains an evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, verifiable compute and intelligence methods, public authority learning, and safeguards institution and does not become a regulated financial, insurance, procurement, certification, public authority, emergency, or enterprise execution actor by design, implication, practice, technology, interface, funding, or public statement.
117.17 Perimeter Hold, Quarantine, Re-Scope, Referral, or Termination Authority. The Board, and any officer or committee expressly authorized within lawful limits, may require an immediate hold, stop, quarantine, access restriction, publication freeze, implementation freeze, technical isolation, controlled-room lockdown, legal review, compliance review, counsel review, safeguards review, public-safe review, or Board review where legal, tax, compliance, regulatory-perimeter, public authority, finance, procurement, certification, recognition, provider-neutrality, sponsor-control, data / AI / cyber, privacy, research ethics, civil rights, accessibility, protected knowledge, export-control, sanctions, competition, or professional-boundary risk exists.
The Corporation shall hold, quarantine, re-scope, refer, externalize, terminate, correct, or withdraw an activity where:
a) the activity may exceed the Corporation’s lawful powers;
b) the activity may conflict with the Articles or Certificate, this Bylaw, Board resolution, policy, delegation, budget, or records requirement;
c) the activity may create public authority confusion;
d) the activity may create finance, securities, investment adviser, broker-dealer, finder, insurance, banking, lending, rating, public finance, procurement, certification, recognition, public warning, emergency command, or enterprise execution risk;
e) the activity may create sponsor control, donor control, funder control, provider preference, host control, private benefit, private inurement, or anti-capture risk;
f) the activity may misuse data, AI, cyber systems, repositories, public-good software, technical baselines, controlled technology, or protected knowledge;
g) the activity may violate privacy, research ethics, civil rights, accessibility, community safeguards, Tribal or Indigenous protocol, protected participation, non-retaliation, or do-no-harm requirements;
h) the activity may violate sanctions, export-control, controlled-technology, national security sensitivity, competition, antitrust, or professional-boundary requirements;
i) the activity may rely on defective evidence, unsupported methods, uncontrolled vocabulary, stale records, false confidence, unverifiable claims, or unreviewed automated outputs; or
j) the activity may require correction, supersession, withdrawal, retraction, takedown, archive, public-safe notice, controlled notice, or legal notice.
A hold or quarantine shall be recorded, classified, assigned to a responsible owner, reviewed within a reasonable period, and resolved through lawful approval, restriction, redesign, correction, external referral, termination, or Board action. No person shall bypass a hold or quarantine by using an alternate channel, unofficial copy, repository fork, private message, AI system, public statement, sponsor communication, provider communication, public authority communication, or Nexus interface.
117.18 Compliance and Regulatory-Perimeter Records. The Corporation shall maintain Compliance and Regulatory-Perimeter Records sufficient to demonstrate that legal, tax, compliance, and regulatory-perimeter oversight has been exercised lawfully, diligently, independently, and consistently with this Bylaw.
Compliance and Regulatory-Perimeter Records shall include, as applicable:
a) legal compliance records;
b) state nonprofit corporate compliance records;
c) federal tax compliance records;
d) state tax, franchise tax, charitable solicitation, foreign qualification, business registration, assumed-name, sales tax, payroll tax, and local tax records;
e) privacy compliance records;
f) AI governance compliance records;
g) cybersecurity compliance records;
h) research ethics compliance records;
i) employment, contractor, volunteer, fellow, advisor, workplace, compensation, reimbursement, and classification records;
j) accessibility and civil rights compliance records;
k) lobbying, political activity, government ethics, gifts, hospitality, grant compliance, public authority interaction, and procurement integrity records;
l) sanctions, export-control, controlled-technology, national security sensitivity, CFIUS-relevant sensitivity where applicable, restricted-party, embargo, dual-use, and foreign-access review records;
m) competition, antitrust, clean-room, clean-team, benchmarking, data-sharing, standards-support, and meeting-discipline records;
n) professional-boundary records;
o) securities, investment adviser, broker-dealer, finder, banking, lending, insurance, underwriting, rating, public finance, procurement, certification, recognition, public authority, public warning, emergency command, and enterprise execution boundary records;
p) public authority capacity records, official-capacity records, observer records, regulator-listening records, public finance reader records, emergency-management participant records, public infrastructure operator records, public authority data contribution records, public authority reference records, and public authority room records;
q) data access records, AI-use records, model register records, inference record records, compute workload records, repository access records, software release records, SBOM records, vulnerability records, incident records, breach records, disaster recovery records, business continuity records, and secure disposal records;
r) research integrity records, evidence records, methods records, observability records, ontology records, technical truth records, publication review records, peer review records, red-team records, model review records, challenge records, correction records, supersession records, withdrawal records, retraction records, takedown records, and archive records;
s) community safeguard records, Tribal and Indigenous protocol records, Indigenous data records, protected knowledge records, local and territorial knowledge records, civil-rights records, accessibility records, public-safe mapping records, grievance records, remedy records, protected participation records, non-retaliation records, and stop-the-line records;
t) conflict records, recusal records, related-party records, private benefit records, inurement records, sponsor non-control records, donor non-control records, funder non-control records, provider-neutrality records, host non-control records, support concentration records, and anti-capture records;
u) hold records, stop records, quarantine records, access restriction records, publication freeze records, implementation freeze records, technical isolation records, controlled-room lockdown records, legal review records, counsel review records, compliance review records, safeguards review records, public-safe review records, Board review records, referral records, externalization records, termination records, and corrective action records;
v) GCRI Canada interface records, GRF interface records, GRA interface records, Nexus Standards interface records, Nexus Network interface records, Nexus Observatory interface records, Nexus Universe interface records, Nexus Rails interface records, Nexus Grid interface records, Nexus Academy interface records, Nexus Competence Cell interface records, consortium interface records, national company interface records, Project SPV interface records, provider interface records, sponsor interface records, host interface records, public authority interface records, university interface records, laboratory interface records, community interface records, and enterprise-stack interface records; and
w) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that compliance is constitutional infrastructure for the Corporation. Legal, tax, compliance, and regulatory-perimeter oversight shall preserve the Corporation’s public-benefit mission, nonprofit character, tax-exempt or tax-exempt-compatible posture, United States legal separateness, all-states-and-territories discipline, North America anchor boundary, non-execution perimeter, GCRI / GRF / GRA role separation, Nexus role separation, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, research integrity, safeguards, validity-by-record, and correctionability. No program urgency, funding urgency, sponsor request, provider request, public authority request, technical convenience, publication deadline, AI output, dashboard signal, proof receipt, ledger entry, committee recommendation, officer judgment, external partner preference, or Nexus interface shall override legal compliance, tax discipline, regulated-perimeter discipline, or the duty to stop, hold, quarantine, re-scope, refer, terminate, correct, or withdraw where required.
Section 118. Nexus Alignment and Legal Separateness Oversight
118.1 Nexus Alignment Oversight. The Board shall oversee the Corporation’s alignment with the Nexus constitutional, institutional, technical, public-good, interoperability, evidence, methods, observability, ontology, public-safe reporting, standards-support, finance-boundary, safeguards, and correction architecture, solely to the extent such alignment is lawful, consistent with the Articles or Certificate, consistent with this Bylaw, consistent with the Corporation’s United States nonprofit and public-benefit character, and compatible with the Corporation’s non-executing role.
Nexus alignment oversight shall ensure that the Corporation may support, contribute to, interoperate with, learn from, and help maintain the public-good stack of Nexus while preserving the Corporation’s separate legal personality, separate treasury, separate governance, separate Board authority, separate records, separate risk posture, separate tax posture, separate compliance obligations, separate liabilities, and separate institutional duties.
The Board shall ensure that Nexus alignment is treated as a disciplined constitutional interface and not as merger, agency, partnership, joint venture, alter ego status, shared treasury, shared liability, public authority delegation, finance-readiness delegation, certification delegation, procurement delegation, standards monopoly, recognition authority, protocol authority, sponsor control, provider preference, or enterprise execution.
Nexus alignment oversight shall include, without limitation:
a) review of Nexus constitutional instruments, public-good stack instruments, doctrine instruments, protocol instruments, standards-support instruments, observatory instruments, grid instruments, docket instruments, academy instruments, risk-management instruments, rails instruments, competence-cell instruments, consortium instruments, national company instruments, Project SPV instruments, provider instruments, sponsor instruments, host instruments, and public authority interface instruments that affect the Corporation;
b) review of the Corporation’s role within the Nexus public-good stack as evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, verifiable compute and intelligence methods, public authority learning, and safeguards steward;
c) review of interfaces with GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, qualified enterprise providers, sponsors, hosts, funders, public authorities, universities, laboratories, communities, media, and enterprise-stack actors;
d) review of role-separation risks, public authority confusion risks, finance-boundary risks, certification-boundary risks, procurement-neutrality risks, provider-neutrality risks, sponsor non-control risks, data / AI / cyber risks, safeguards risks, protected knowledge risks, competition risks, tax risks, and legal-separateness risks;
e) approval, correction, limitation, withdrawal, supersession, re-scoping, quarantine, or termination of Nexus-facing instruments where necessary to preserve the Corporation’s lawful role; and
f) maintenance of compatibility notes, divergence logs, equivalence notes, interface records, authority records, limitation language, public-safe notices, correction records, and repository records.
No Nexus alignment statement, public architecture diagram, role map, whitepaper, operating model, consortium charter, protocol reference, proof receipt, ledger entry, public-safe report, dashboard, technical baseline, software repository, public authority learning session, sponsor material, provider material, or public communication shall be treated as authority to override the Articles or Certificate, this Bylaw, Board reserved matters, nonprofit law, tax law, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, or correctionability.
118.2 Nexus Constitutional Framework Alignment. The Board shall oversee the Corporation’s alignment with the Nexus Constitutional Framework as an external mission-alignment, role-separation, public-good stack, interoperability, and institutional coherence instrument, only to the extent consistent with applicable law, the Articles or Certificate, this Bylaw, Board resolutions, and the Corporation’s United States legal obligations.
The Board shall ensure that any reference to the Nexus Constitutional Framework:
a) supports public-good mission alignment;
b) supports role clarity among GCRI US, GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, providers, sponsors, hosts, funders, public authorities, universities, laboratories, communities, and enterprise actors;
c) reinforces one rail / two stacks discipline;
d) preserves the separation of evidence, recognition, maturity records, claims discipline, finance-readiness, capital-readability, standards support, protocol authority, public authority learning, and enterprise execution;
e) supports public-safe claims, controlled vocabulary, records discipline, repository discipline, gazette discipline where applicable, and correctionability; and
f) prevents institutional drift into authority-inflating, execution-facing, sponsor-controlled, provider-preferential, public authority-confusing, finance-overclaiming, certification-overclaiming, procurement-overclaiming, or recognition-overclaiming functions.
The Nexus Constitutional Framework shall not supersede the Corporation’s Articles or Certificate, this Bylaw, Board reserved powers, member approval requirements where applicable, United States nonprofit corporate obligations, federal tax obligations, state law obligations, or applicable public authority, data, AI, cyber, privacy, civil rights, accessibility, sanctions, export-control, competition, or professional-boundary rules.
Where a Nexus constitutional concept is inconsistent with United States law or the Corporation’s governing instruments, the Board shall apply the lawful, narrower, more protective, and less authority-inflating interpretation and shall record any divergence, compatibility limitation, correction, or required amendment.
118.3 Public-Good Stack Framework Alignment. The Board shall oversee alignment with the Public-Good Stack Framework Charter and any related public-good stack instruments as public-benefit, non-executing, role-separated, interoperability, learning, evidence, safeguards, and public-safe communication instruments.
The Board shall ensure that the Corporation’s public-good stack role remains limited to lawful public-benefit functions, including:
a) evidence stewardship;
b) methods stewardship;
c) observability methods;
d) ontology and semantic interoperability;
e) technical truth methods;
f) public-good R&D;
g) public-good software;
h) open technical baseline stewardship;
i) verifiable compute and verifiable intelligence methods;
j) Nexus Truth Engine methods;
k) Nexus Observatory methods;
l) public authority learning support;
m) public-safe reporting support;
n) controlled-room, evidence-room, data-room, clean-room, public authority room, and no-download-room methods support;
o) community safeguards, Tribal and Indigenous protocol respect, protected knowledge safeguards, civil rights, accessibility, grievance, remedy, protected participation, non-retaliation, and do-no-harm support; and
p) correctionability and validity-by-record support.
The Board shall ensure that public-good stack alignment does not authorize the Corporation to become a public authority, regulator, emergency command body, public warning authority, finance-readiness authority, recognition body, certification body, procurement authority, provider approval body, sponsor-controlled platform, asset owner, infrastructure operator, national company, Project SPV, fund, lender, insurer, broker, dealer, investment adviser, rating agency, or enterprise execution vehicle.
Public-good stack instruments may guide the Corporation’s mission alignment and interoperability, but shall not create binding corporate authority unless lawfully adopted, versioned, recorded, and made subordinate to the Articles or Certificate and this Bylaw.
118.4 One Rail / Two Stacks Alignment. The Board shall oversee alignment with the One Rail / Two Stacks doctrine and shall ensure that the Corporation preserves the distinction between the common Nexus rail, the public-good stack, and the enterprise stack.
The Board shall ensure that the Corporation’s public-good work may support the common rail through evidence, methods, observability, ontology, technical baselines, public-good software, learning, safeguards, and correction, but shall not collapse into the enterprise stack.
For purposes of this Section:
a) the common rail shall mean the shared institutional, technical, evidentiary, semantic, and interoperability pathway through which Nexus-compatible records, methods, proofs, claims, maturity evidence, finance-readiness inputs, public authority learning materials, and enterprise interfaces may be organized and routed;
b) the public-good stack shall mean the non-executing public-benefit layer of evidence, methods, observability, ontology, technical truth, public-safe reporting, standards support, public authority learning, safeguards, and correction;
c) the enterprise stack shall mean the separately constituted layer of national companies, state or regional operating companies, Project SPVs, qualified enterprise providers, investors, insurers, lenders, underwriters, banks, public finance actors, operators, integrators, vendors, sponsors, hosts, asset owners, deployment companies, and execution actors; and
d) the Corporation’s role shall remain within the public-good stack unless a separate lawful instrument creates a permitted non-executing interface within recorded limits.
The Board shall ensure that no Corporation output converts public-good evidence into enterprise authorization, converts public-good software into commercial endorsement, converts technical baseline support into procurement mandate, converts evidence packs into finance-readiness determinations, converts public authority learning into public authority action, converts provider participation into provider preference, or converts sponsor support into sponsor control.
118.5 Non-Execution Doctrine Alignment. The Board shall oversee alignment with the Non-Execution Doctrine and shall ensure that every Nexus-facing function of the Corporation preserves the bright-line distinction between public-good stewardship and regulated or enterprise execution.
Non-execution alignment shall require the Corporation to avoid, refuse, hold, quarantine, re-scope, externalize, refer, or terminate any activity that would cause the Corporation to act or appear to act as:
a) emergency command body;
b) official public warning authority;
c) public health order authority;
d) dispatch or incident management body;
e) regulator or enforcement body;
f) public authority decision-maker;
g) procurement authority;
h) certification or accreditation body;
i) recognition or maturity-standing body;
j) finance-readiness authority;
k) capital-placement actor;
l) broker, dealer, finder, underwriter, investment adviser, lender, bank, insurer, reinsurer, rating agency, public finance approver, or guarantor;
m) enterprise delivery company;
n) national company;
o) Project SPV;
p) qualified enterprise provider;
q) infrastructure operator;
r) asset owner; or
s) sponsor-controlled or provider-controlled vehicle.
The Board shall ensure that non-execution controls apply equally to human decisions, Board actions, officer actions, committee recommendations, controlled-room outputs, data-room outputs, dashboards, maps, digital twins, AI systems, AI agents, model outputs, inference records, compute outputs, AI-RAN signals, O-RAN signals, DePIN records, DLT records, blockchain entries, proof receipts, public-safe reports, software releases, technical baselines, public authority learning materials, and Nexus interface records.
No execution-facing function shall be justified by public-good purpose, technical urgency, public authority interest, sponsor request, provider request, donor condition, funder request, grant opportunity, national company need, Project SPV need, event deadline, publication schedule, repository milestone, or Nexus alignment.
118.6 Validity-by-Record Doctrine Alignment. The Board shall oversee alignment with the Validity-by-Record Doctrine and shall ensure that institutional validity arises only from competent authority, lawful process, recorded action, proper versioning, repository discipline, controlled vocabulary, access classification, public-safe limitation, and correction pathways.
Validity-by-record alignment shall require that material institutional acts identify, as applicable:
a) responsible body;
b) responsible officer;
c) authority source;
d) decision record;
e) approval record;
f) version;
g) effective date;
h) review date;
i) custodian;
j) repository location;
k) access class;
l) publication class;
m) limitation language;
n) reliance boundary;
o) supersession status;
p) correction pathway;
q) archive status; and
r) metadata sufficient to establish provenance and institutional meaning.
No oral statement, meeting comment, slide, draft, AI summary, unofficial extract, public explainer, website update, repository fork, informal email, chat message, public authority conversation, sponsor statement, provider statement, media quote, proof receipt, ledger entry, dashboard state, model output, automated score, or uncontrolled copy shall create institutional validity unless supported by a competent record.
The Board shall ensure that all Nexus-facing outputs, GRF-facing inputs, GRA-facing inputs, Nexus Standards support, Nexus Observatory support, Nexus Grid support, Nexus Docket support, public authority learning materials, controlled-room outputs, public-safe publications, technical baselines, public-good software, and public claims are governed by validity-by-record discipline.
118.7 Correctionability Doctrine Alignment. The Board shall oversee alignment with the Correctionability Doctrine and shall ensure that every material institutional output, governance act, public-safe publication, evidence artifact, method, observability output, ontology item, technical baseline, software release, dashboard, map, dataset, model output, proof receipt, public authority learning material, controlled-room output, Nexus interface, GRF-facing input, GRA-facing input, and public claim is capable of correction, supersession, withdrawal, retraction, takedown, archival, or public clarification where required.
Correctionability alignment shall include, without limitation:
a) correction triggers;
b) challenge pathways;
c) error intake;
d) evidence dispute review;
e) source-lineage review;
f) provenance review;
g) confidence and uncertainty review;
h) public-safe publication review;
i) safeguards review;
j) data / AI / cyber review;
k) legal and regulatory-perimeter review;
l) public authority boundary review;
m) finance-boundary review;
n) certification-boundary review;
o) procurement-neutrality review;
p) provider-neutrality review;
q) sponsor non-control review;
r) controlled vocabulary review;
s) correction authority;
t) correction notice;
u) supersession chain;
v) withdrawal, retraction, takedown, and archive records; and
w) post-correction review.
No person shall resist a required correction because of reputational concern, sponsor preference, provider preference, donor preference, funder preference, public authority preference, publication history, event commitment, technical inconvenience, litigation concern, fundraising concern, finance-readiness concern, recognition concern, or Nexus interface concern.
The Board shall ensure that correctionability is not treated as institutional weakness. Correctionability is an affirmative duty of public-good stewardship, technical truth, public trust, safeguards protection, legal compliance, and Nexus compatibility.
118.8 Verifiable Compute and Verifiable Intelligence Doctrine Alignment. The Board shall oversee alignment with the Verifiable Compute and Verifiable Intelligence Doctrine and shall ensure that compute, AI, model, inference, benchmark, agentic, dataset, dashboard, digital twin, automation, evaluation, and proof systems used or supported by the Corporation are record-supported, reviewable, bounded, secure, public-safe, and correctionable.
Verifiable compute and verifiable intelligence alignment shall include, as applicable:
a) model registers;
b) dataset cards;
c) model cards;
d) system cards;
e) benchmark cards;
f) evaluation harnesses;
g) inference records;
h) compute workload records;
i) compute-to-data controls;
j) secure enclave controls;
k) confidential computing controls;
l) sovereign compute considerations;
m) data residency and cross-border transfer controls;
n) human review for material outputs;
o) AI-use approvals;
p) agentic AI controls;
q) prompt, retrieval, embedding, fine-tuning, training, and model-improvement restrictions;
r) audit logs;
s) proof receipts;
t) reproducibility records;
u) security records;
v) correction records; and
w) public-safe output limitation language.
No model, compute environment, inference output, agentic workflow, automated score, digital twin, proof receipt, DePIN record, DLT entry, blockchain entry, dashboard signal, AI-RAN signal, O-RAN signal, cyber telemetry output, geospatial layer, sensor signal, or verifiable intelligence artifact shall be treated as final authority, technical truth, public warning, emergency command, public authority decision, finance-readiness determination, insurance-readiness determination, rating, certification, procurement approval, recognition, provider approval, or operational authorization without lawful human authorization and competent record support.
118.9 GCRI Canada Interface Oversight. The Board shall oversee the Corporation’s interface with GCRI Canada and shall ensure that coordination with GCRI Canada preserves separate legal personality, separate jurisdictional obligations, separate governance authority, separate treasury, separate records, separate tax status, separate risk posture, separate liabilities, separate employment relationships, separate contracts, separate public representations, and separate compliance duties.
GCRI Canada interface oversight shall include, without limitation:
a) shared mission alignment without legal fusion;
b) shared doctrine without shared liability;
c) shared ontology without shared treasury;
d) shared methods without automatic agency;
e) shared technical baselines without automatic mutual authority;
f) shared projects only where separately and lawfully constituted;
g) dual-role person controls;
h) cross-border data, AI, cyber, privacy, research, public authority, export-control, sanctions, protected knowledge, and public-safe publication review;
i) North America evidence architecture coordination;
j) observability and ontology alignment;
k) public-good software and technical baseline coordination;
l) compatibility notes;
m) divergence logs;
n) equivalence notes;
o) public description discipline; and
p) interface records.
No GCRI Canada director, officer, employee, contractor, advisor, fellow, volunteer, contributor, sponsor, donor, provider, host, public authority participant, or partner shall have authority to bind the Corporation unless separately authorized by the Corporation through lawful delegation and record. No Corporation director, officer, employee, contractor, advisor, fellow, volunteer, contributor, sponsor, donor, provider, host, public authority participant, or partner shall have authority to bind GCRI Canada unless separately authorized by GCRI Canada through lawful delegation and record.
118.10 GRF Interface Oversight. The Board shall oversee the Corporation’s interface with The Global Risks Forum (GRF) and shall ensure that any GRF-facing support preserves GRF’s separate role as public-good registry, recognition, maturity-records, standing, claims-discipline, stakeholder-formation, public-safe reporting, and public-facing legitimacy steward, while preserving GCRI US as evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, public authority learning, and safeguards steward.
GRF interface oversight shall include, without limitation:
a) evidence support to GRF;
b) methods support to GRF;
c) observability support to GRF;
d) ontology and controlled vocabulary support to GRF;
e) public-good technical baseline support to GRF;
f) correction signals to GRF;
g) GRF-facing input records;
h) public-safe claims discipline;
i) maturity-record interface discipline;
j) recognition-boundary discipline;
k) standing-boundary discipline;
l) public-facing legitimacy boundary discipline;
m) Docket and Grid input routing discipline where applicable;
n) no-recognition language where required; and
o) correction, supersession, withdrawal, retraction, takedown, archive, and public clarification pathways.
The Board shall ensure that GCRI US does not issue, imply, sell, guarantee, or control GRF recognition, standing, maturity status, public-facing legitimacy, registry status, stakeholder-formation outcome, claims approval, or public legitimacy determination. Evidence support, methods support, technical baseline support, observability support, or correction signals from GCRI US shall not be represented as GRF recognition unless GRF separately and lawfully issues and records such recognition within its own authority.
118.11 GRA Interface Oversight. The Board shall oversee the Corporation’s interface with The Global Risks Alliance (GRA) and shall ensure that any GRA-facing support preserves GRA’s separate role as finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, capital-reader room, and regulated-perimeter discipline steward, while preserving the Corporation’s non-executing evidence, methods, observability, ontology, public-good technical baseline, and public authority learning role.
GRA interface oversight shall include, without limitation:
a) technical evidence inputs to GRA;
b) methods inputs to GRA;
c) observability inputs to GRA;
d) ontology and controlled vocabulary support to GRA;
e) public-good technical baseline inputs to GRA;
f) proof-pack technical input support;
g) insurance-readiness evidence input support without insurance approval;
h) capital-reader technical literacy support without solicitation;
i) correction signals to GRA;
j) finance-boundary review;
k) securities-boundary review;
l) investment-adviser and broker-dealer boundary review;
m) banking and lending boundary review;
n) insurance and underwriting boundary review;
o) rating-boundary review;
p) public-finance boundary review;
q) no-investment-advice language;
r) no-solicitation language;
s) no-finance-readiness-determination language; and
t) GRA interface records.
The Board shall ensure that GCRI US does not issue, imply, sell, guarantee, or control finance-readiness, capital-readability, insurance-readiness, proof-pack approval, bankability, investability, creditworthiness, public finance approval, tax credit approval, public guarantee, investment suitability, rating, underwriting result, lending result, insurance result, or capital allocation. Any GRA-facing technical input shall remain evidence or methods support unless GRA or another competent actor separately and lawfully makes and records a determination within its own authority.
118.12 Nexus Standards and Protocol Authority Interface Oversight. The Board shall oversee the Corporation’s interface with Nexus Standards and any protocol authority that is separately and lawfully constituted, and shall ensure that the Corporation’s technical support, evidence support, ontology support, schema support, interoperability support, software support, and open technical baseline support do not become standards authority, protocol authority, certification authority, accreditation authority, procurement authority, or conformance approval by implication.
Nexus Standards and protocol authority interface oversight shall include, without limitation:
a) standards-support role classification;
b) protocol-support role classification;
c) technical baseline contribution review;
d) schema and ontology contribution review;
e) evidence requirements support;
f) interoperability profile support;
g) API, SDK, data dictionary, metadata, dashboard, benchmark, test harness, and reference architecture support;
h) public-good software support;
i) proof receipt, role key, ledger, smart license, smart contract, and protocol-logic support only where authorized and non-executing;
j) conformance claim review;
k) Nexus-compatible claim review;
l) certification-boundary review;
m) procurement-boundary review;
n) public authority boundary review;
o) provider-neutrality review;
p) sponsor non-control review; and
q) standards and protocol interface records.
No technical centrality, repository control, reference implementation, schema authorship, ontology authorship, test harness, benchmark, API, SDK, software release, dashboard, proof receipt, ledger entry, role key, protocol profile, or technical baseline shall be treated as authority for the Corporation to certify, accredit, approve conformance, mandate procurement, select providers, bind public authorities, determine Nexus-compatible status, or control protocol authority unless a separate lawful authority is created and recorded.
118.13 Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, and Nexus Competence Cell Interface Oversight. The Board shall oversee the Corporation’s interfaces with Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, and related Nexus public-good infrastructure functions, and shall ensure that each interface is lawful, role-separated, public-safe, record-supported, and correctionable.
Such oversight shall include, without limitation:
a) Nexus Network interface review as the common public-good rail;
b) Nexus Observatory interface review for observability methods, nodes, hubs, clusters, hotspots, regional clusters, national dense Nexus cores, sensor methods, AI-RAN methods, O-RAN methods, DePIN methods, DLT and blockchain reference methods, digital twin methods, cyber telemetry methods, geospatial methods, Earth observation methods, degraded-mode awareness, resilience indicators, dashboards, and maps;
c) Nexus Universe interface review for annual global operating arena, controlled build, live operation, benchmarking, public-safe publication, learning, and ecosystem coordination;
d) Nexus Risk Management interface review for risk registers, issue registers, control registers, incident registers, systemic risk taxonomies, escalation pathways, safeguards, and correction discipline;
e) Nexus Rails interface review for routing, records, role keys, proof receipts, evidence flow, docket routing, grid routing, and interface discipline;
f) Nexus Grid interface review for maturity records, evidence support, stakeholder records, routeability, readiness support, and public-safe claims discipline without GCRI US recognition authority;
g) Nexus Academy interface review for training, literacy, capability formation, fellowships, competence records, and public authority learning without professional certification by default;
h) Nexus Competence Cell interface review for evidence, methods, observability, ontology, data governance, AI governance, cybersecurity, public-good software, public authority learning, safeguards, and localization capacity without certification by default;
i) data / AI / cyber, privacy, public authority, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, sponsor non-control, safeguards, and protected knowledge review for each interface; and
j) interface records, compatibility notes, divergence logs, correction records, and public-safe notices.
The Board shall ensure that no Nexus Network, Observatory, Universe, Risk Management, Rails, Grid, Academy, or Competence Cell interface creates hidden governance, uncontrolled delegation, public authority meaning, finance-readiness meaning, certification meaning, procurement meaning, recognition meaning, provider preference, sponsor control, or enterprise execution by the Corporation.
118.14 National, Regional, State, Territorial, Tribal, Local, and North America Consortium Interface Oversight. The Board shall oversee the Corporation’s interface with Global Nexus Consortium, Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, state Nexus interfaces, territorial Nexus interfaces, Tribal and Indigenous Nexus interfaces, local Nexus interfaces, metropolitan Nexus interfaces, sectoral Nexus interfaces, North America Nexus interfaces, and related public-good consortium structures.
Such oversight shall ensure that consortium relationships:
a) support public-good evidence, methods, observability, ontology, public authority learning, safeguards, technical literacy, public-good software, and open technical baselines;
b) respect national, regional, state, territorial, Tribal, Indigenous, local, community, sectoral, and cross-border legal contexts;
c) preserve the Corporation’s United States seat discipline;
d) preserve all-states-and-territories localization without fragmentation;
e) preserve North America anchor role within bounded public-good authority;
f) preserve public authority capacity classification;
g) preserve controlled vocabulary;
h) preserve public-safe claims;
i) preserve competition and antitrust discipline;
j) preserve data / AI / cyber, privacy, civil rights, accessibility, community safeguards, Tribal and Indigenous protocol, protected knowledge, and do-no-harm controls;
k) preserve no-agency, no-partnership, no-merger, no-shared-treasury, no-shared-liability, and no-enterprise-execution rules; and
l) maintain compatibility notes, divergence logs, equivalence notes, localization records, interface records, and correction paths.
No consortium relationship shall create authority for a consortium to bind GCRI US, or for GCRI US to bind a consortium, unless a lawful written instrument expressly authorizes the act within recorded limits. No consortium participation shall imply public authority adoption, procurement approval, finance-readiness, certification, recognition, provider preference, sponsor entitlement, or enterprise execution.
118.15 National Companies, State Operating Companies, Regional Companies, Project SPVs, Providers, Sponsors, Hosts, and Enterprise Actors Interface Oversight. The Board shall oversee the Corporation’s interface with national consortium companies, state operating companies, regional companies, sectoral operating companies, Project SPVs, qualified enterprise providers, sponsors, hosts, vendors, contractors, cloud providers, AI providers, data processors, integrators, operators, asset owners, investors, insurers, lenders, underwriters, banks, public finance actors, capital readers, and other enterprise-stack actors.
Enterprise-stack interface oversight shall ensure that:
a) the Corporation does not become an enterprise execution vehicle;
b) the Corporation does not own, operate, control, manage, finance, underwrite, insure, guarantee, rate, procure, certify, recognize, or approve enterprise deployments unless separately and lawfully authorized within non-execution limits;
c) enterprise actors do not control the Corporation’s governance, evidence, methods, observability, ontology, publications, technical baselines, software, repositories, public authority learning, controlled rooms, data rooms, public claims, or Nexus interfaces;
d) provider participation does not become provider preference;
e) sponsor support does not become sponsor control;
f) host participation does not become host control;
g) investor, insurer, lender, underwriter, bank, public finance actor, or capital-reader participation does not become finance execution by the Corporation;
h) Project SPV or national company participation does not create shared treasury, shared liability, partnership, agency, alter ego status, single employer status, joint employer status, or common enterprise status;
i) data, AI, cyber, privacy, export-control, sanctions, controlled-technology, competition, public authority, finance-boundary, certification-boundary, procurement-boundary, safeguards, protected knowledge, and professional-boundary controls are maintained; and
j) interface records, conflict records, related-party records, support records, access records, public claim records, correction records, and closeout records are maintained.
No enterprise actor shall use Corporation participation, support, publication, technical baseline, evidence input, controlled-room access, proof receipt, dashboard, map, software release, training, Academy participation, Nexus interface, public authority learning session, or public-safe report to claim certification, recognition, finance-readiness, insurance-readiness, bankability, investability, procurement advantage, public authority endorsement, provider preference, sponsor entitlement, or operational approval without competent authority and record.
118.16 No Merger by Coordination. Coordination with GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, providers, sponsors, hosts, funders, public authorities, universities, laboratories, communities, or enterprise actors shall not create merger, consolidation, alter ego status, branch status, division status, parent-subsidiary status, common enterprise status, common treasury, common governance, single employer status, joint employer status, shared liability, or legal fusion.
The Corporation may coordinate through lawful instruments, including MoUs, interface agreements, data agreements, research agreements, contribution agreements, public authority learning agreements, university agreements, laboratory agreements, sponsorship agreements, donor agreements, host agreements, provider agreements, repository terms, controlled-room terms, public-good software licenses, and Nexus interface protocols, provided that each instrument preserves legal separateness and does not override this Bylaw.
Coordination may include shared mission language, shared doctrine, shared ontology, shared methods, shared technical baselines, shared public-good software, shared public-safe publications, shared events, shared rooms, shared evidence workflows, shared repositories, shared dashboards, shared training, shared Academy materials, shared competence-cell materials, shared public authority learning, shared public-good support, and shared Nexus interfaces, but such sharing shall not create merger unless an express lawful merger, consolidation, or equivalent transaction is approved in accordance with applicable law, the Articles or Certificate, this Bylaw, and all required Board or member approvals.
Any public statement describing coordination shall use controlled vocabulary and shall avoid implying legal fusion, common control, common treasury, shared liability, public authority delegation, finance-readiness delegation, certification authority, procurement authority, recognition authority, provider preference, sponsor control, or enterprise execution.
118.17 No Agency by Coordination. No coordination, shared project, shared room, shared council, shared committee, shared working group, shared public authority session, shared publication, shared repository, shared software, shared dataset, shared dashboard, shared event, shared public statement, shared sponsor, shared provider, shared host, shared funder, shared donor, shared advisor, shared fellow, shared director, shared officer, shared contractor, shared employee, shared contributor, shared role key, shared proof receipt, shared ledger entry, shared mark, or shared Nexus interface shall create agency unless expressly created by a lawful written instrument approved by competent authority and recorded.
No person affiliated with another Nexus entity, consortium, national company, Project SPV, provider, sponsor, host, public authority, university, laboratory, funder, donor, or enterprise actor shall have authority to act as agent of the Corporation by reason of participation, title, expertise, authorship, public prominence, technical centrality, system access, public authority contact, funding relationship, provider relationship, sponsor relationship, or leadership proximity.
No person affiliated with the Corporation shall have authority to act as agent of any external body by reason of Corporation title, Board service, officer service, committee service, authorship, technical centrality, public authority contact, repository access, controlled-room access, public statement, or Nexus interface unless the external body separately and lawfully authorizes that person.
The Board shall require agency-risk review where public-facing materials, event materials, public authority materials, investor materials, sponsor materials, provider materials, grant materials, procurement-adjacent materials, media materials, or Nexus interface materials could create apparent authority.
118.18 No Shared Treasury by Coordination. The Corporation shall maintain separate treasury, bank accounts, books, accounting records, restricted fund records, unrestricted fund records, grant records, donation records, sponsorship records, in-kind contribution records, accounts payable, accounts receivable, payroll records, tax records, audit records, insurance records, reserves, financial controls, spending authorities, signing authorities, and budget approvals.
No coordination with GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, consortiums, national companies, Project SPVs, providers, sponsors, hosts, funders, public authorities, universities, laboratories, communities, or enterprise actors shall create common treasury, pooled funds, shared assets, common debt, common liability, implied guarantee, revenue guarantee, performance guarantee, public finance obligation, insurance obligation, lending obligation, capital commitment, or financial intermediation unless separately and lawfully authorized and recorded within the Corporation’s permitted nonprofit powers and non-execution limits.
The Corporation may receive grants, donations, sponsorships, fees, subscriptions, cost recovery, in-kind contributions, restricted funds, public-good support, and lawful reimbursements, and may enter into cost-sharing or reimbursement arrangements where lawful, but each such arrangement shall preserve:
a) public-benefit purpose;
b) no private inurement;
c) no impermissible private benefit;
d) restricted fund discipline;
e) donor, sponsor, funder, provider, and host non-control;
f) no finance execution;
g) no securities solicitation;
h) no investment advice;
i) no banking, lending, insurance, underwriting, rating, or public finance execution;
j) no procurement advantage;
k) no certification or recognition purchase;
l) no public authority access purchase;
m) records sufficient to trace funds, restrictions, expenditures, approvals, acknowledgments, and closeout; and
n) correction, refusal, return, restriction, termination, or reclassification where required.
118.19 No Shared Liability by Coordination. The Corporation shall not assume, guarantee, indemnify, insure, underwrite, backstop, support, or become liable for obligations of GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, providers, sponsors, hosts, funders, public authorities, universities, laboratories, communities, enterprise actors, or any other external person, except to the extent expressly authorized by lawful written instrument, approved by competent authority, consistent with this Bylaw, and recorded.
Shared mission, shared doctrine, shared ontology, shared methods, shared public-good software, shared technical baselines, shared public authority learning, shared events, shared rooms, shared evidence packs, shared dashboards, shared publications, shared repositories, shared marks, shared public statements, shared personnel, shared advisors, shared sponsors, shared providers, shared hosts, shared public authority contacts, shared proof receipts, shared role keys, shared ledger entries, shared Nexus interfaces, or common public descriptions shall not create shared liability.
The Board shall ensure that all material coordination instruments include appropriate limitation language addressing:
a) separate legal personality;
b) no agency;
c) no partnership;
d) no joint venture;
e) no merger;
f) no shared treasury;
g) no shared liability;
h) no authority to bind;
i) no public authority delegation;
j) no finance-readiness delegation;
k) no certification or procurement approval;
l) no recognition authority by GCRI US;
m) no provider preference;
n) no sponsor control;
o) data / AI / cyber responsibilities;
p) safeguards responsibilities;
q) public-safe claims;
r) records;
s) correction; and
t) termination or withdrawal.
Where liability ambiguity cannot be resolved through lawful limitation, role clarification, insurance, indemnity, risk allocation, re-scoping, or Board approval, the Corporation shall refuse, hold, quarantine, externalize, or terminate the relationship or activity.
118.20 No Substitution of Functions. The Corporation shall not substitute for the functions of GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, qualified enterprise providers, sponsors, hosts, funders, public authorities, universities, laboratories, communities, or enterprise actors.
The Corporation shall not:
a) perform GRF recognition, standing, maturity-records, registry, claims-discipline, stakeholder-formation, public-facing legitimacy, or public-safe reporting authority functions unless separately and lawfully authorized by GRF within a role that remains consistent with GCRI US law and this Bylaw;
b) perform GRA finance-readiness, capital-readability, proof-pack approval, insurance-readiness, diligence-translation, capital-reader room, RNFD, NFD, UNFSD, or regulated-perimeter determination functions;
c) perform Nexus Standards or protocol authority functions unless separately and lawfully designated and recorded;
d) perform public authority decisions, public warnings, emergency command, regulatory approvals, procurement approvals, funding approvals, public finance approvals, sovereign commitments, permits, enforcement, or official governmental functions;
e) perform enterprise execution functions of national companies, state operating companies, regional companies, sectoral operating companies, Project SPVs, providers, operators, integrators, asset owners, vendors, funds, lenders, insurers, underwriters, banks, public finance actors, or capital-market actors;
f) perform university, laboratory, IRB, peer-review, academic credentialing, professional licensing, or certification functions by default;
g) perform community consent, Tribal consent, Indigenous governance, or protected knowledge authorization functions for communities unless the competent community, Tribal, Indigenous, or knowledge-governance authority separately and lawfully provides such authority; or
h) perform media editorial, public advocacy, campaign, lobbying, political, or public authority communications functions beyond the Corporation’s lawful public-benefit and public-safe communication role.
The Corporation may provide evidence, methods, learning, technical baselines, public-good software, public-safe reports, controlled-room support, data-room support, research support, observability methods, ontology support, correction signals, and technical inputs to other bodies, but such support shall not substitute for the competent body’s own decision, authority, duty, or record.
118.21 Compatibility Notes, Divergence Logs, Interface Records, and Correction Paths. The Corporation shall maintain Nexus Alignment and Legal Separateness Records sufficient to demonstrate that Nexus alignment and external interfaces have been reviewed, approved, implemented, monitored, corrected, limited, superseded, withdrawn, terminated, or archived in conformity with this Bylaw.
Such records shall include, as applicable:
a) Nexus alignment records;
b) Nexus Constitutional Framework compatibility notes;
c) Public-Good Stack Framework compatibility notes;
d) One Rail / Two Stacks compatibility notes;
e) Non-Execution Doctrine compatibility notes;
f) Validity-by-Record Doctrine compatibility notes;
g) Correctionability Doctrine compatibility notes;
h) Verifiable Compute and Verifiable Intelligence Doctrine compatibility notes;
i) GCRI Canada interface records;
j) GRF interface records;
k) GRA interface records;
l) Nexus Standards and protocol authority interface records;
m) Nexus Network interface records;
n) Nexus Observatory interface records;
o) Nexus Universe interface records;
p) Nexus Risk Management interface records;
q) Nexus Rails interface records;
r) Nexus Grid interface records;
s) Nexus Academy interface records;
t) Nexus Competence Cell interface records;
u) Global Nexus Consortium, Regional Nexus Consortium, National Nexus Consortium, National Working Group, state, territorial, Tribal, local, sectoral, and North America interface records;
v) national company, state operating company, regional company, Project SPV, provider, sponsor, host, donor, funder, public authority, university, laboratory, community, media, and enterprise-stack interface records;
w) compatibility notes;
x) divergence logs;
y) equivalence notes;
z) role-separation records;
aa) authority records;
bb) public-safe limitation records;
cc) controlled vocabulary records;
dd) public authority capacity records;
ee) finance-boundary records;
ff) certification-boundary records;
gg) procurement-neutrality records;
hh) provider-neutrality records;
ii) sponsor non-control records;
jj) data / AI / cyber records;
kk) privacy records;
ll) safeguards records;
mm) protected knowledge records;
nn) conflict and recusal records;
oo) competition records;
pp) sanctions, export-control, and controlled-technology records;
qq) hold, quarantine, re-scope, externalization, referral, termination, correction, supersession, withdrawal, retraction, takedown, archive, and public clarification records; and
rr) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that Nexus alignment strengthens the Corporation only when it is lawful, recorded, role-separated, public-safe, non-executing, and correctionable. The Corporation may help build the public-good architecture, common rail, evidence layer, methods layer, observability layer, ontology layer, public-good software layer, technical baseline layer, public authority learning layer, and safeguards layer of Nexus, but it shall not collapse into GRF, GRA, Nexus Standards, public authority, national company, Project SPV, provider, sponsor, host, funder, or enterprise execution functions. Nexus alignment shall be proven by records, constrained by law, bounded by public-benefit purpose, protected by legal separateness, disciplined by controlled vocabulary, safeguarded by data / AI / cyber and community protections, and correctable whenever evidence, law, risk, public safety, public authority meaning, finance meaning, certification meaning, procurement meaning, recognition meaning, provider meaning, sponsor meaning, or institutional meaning requires correction.
Section 119. Oversight of Non-Execution, Public Authority Boundaries, Finance Boundaries, Procurement Neutrality, Certification Boundaries, and Provider Neutrality
119.1 Non-Execution Oversight. The Board shall oversee the Corporation’s non-execution perimeter and shall ensure that the Corporation remains a United States nonprofit, public-benefit, non-distributing, non-executing evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, public authority learning, verifiable compute and intelligence methods, and safeguards institution.
Non-execution oversight shall apply to every activity, instrument, program, platform, publication, room, dataset, dashboard, map, software release, technical baseline, proof receipt, repository, public authority learning session, controlled-room output, GCRI Canada interface, The Global Risks Forum (GRF) interface, The Global Risks Alliance (GRA) interface, Nexus Standards interface, Nexus Network interface, Nexus Observatory interface, Nexus Universe interface, Nexus Grid interface, Nexus Rails interface, Nexus Academy interface, Nexus Competence Cell interface, consortium interface, national company interface, Project SPV interface, provider interface, sponsor interface, host interface, funder interface, donor interface, public authority interface, university interface, laboratory interface, community interface, and enterprise-stack interface.
The Board shall ensure that the Corporation does not conduct, authorize, imply, sell, guarantee, intermediate, broker, underwrite, approve, certify, recognize, finance, operate, command, dispatch, procure, regulate, enforce, or execute activities reserved to public authorities, licensed professionals, regulated financial actors, insurers, lenders, rating agencies, procurement bodies, certification bodies, GRF, GRA, Nexus Standards, national companies, Project SPVs, qualified enterprise providers, asset owners, operators, sponsors, hosts, or other competent actors.
Non-execution oversight shall include, without limitation:
a) review of all proposed activities for execution-facing risk;
b) review of public authority interfaces for public authority substitution risk;
c) review of capital-facing interfaces for finance-readiness, solicitation, brokerage, investment advice, insurance, lending, rating, underwriting, or public finance risk;
d) review of provider, sponsor, donor, funder, host, national company, Project SPV, and enterprise-stack interfaces for control, preference, procurement, endorsement, or execution risk;
e) review of dashboards, maps, models, digital twins, AI agents, automated scores, proof receipts, DLT records, blockchain entries, AI-RAN signals, O-RAN signals, DePIN records, sensor signals, cyber telemetry, geospatial outputs, Earth observation outputs, observability records, and Truth Engine outputs for authority-inflation risk;
f) review of public materials, grant materials, sponsor materials, investor-adjacent materials, public authority materials, websites, media materials, social media, repositories, technical documentation, Gitbook pages, presentations, whitepapers, policy materials, and training materials for non-execution language;
g) adoption and enforcement of controlled vocabulary, public-safe notices, non-reliance language, boundary notices, approval thresholds, escalation pathways, and correction protocols; and
h) maintenance of non-execution records sufficient to demonstrate that the Corporation’s public-good role has not been converted into prohibited execution by design, practice, implication, funding pressure, technical integration, or public communication.
No program urgency, public authority request, sponsor request, provider request, donor condition, grant deadline, publication deadline, event deadline, technical milestone, repository milestone, controlled-room pressure, capital-reader interest, national company need, Project SPV need, or Nexus interface need shall justify departure from the non-execution perimeter.
119.2 Emergency Command Boundary Oversight. The Board shall oversee the emergency command boundary and shall ensure that the Corporation does not act as an emergency command body, incident command body, dispatch authority, evacuation authority, resource allocation authority, emergency operations center, public safety agency, public health order authority, infrastructure command authority, utility command authority, cyber incident command authority, or operational public warning authority.
Emergency command boundary oversight shall include review of:
a) public authority learning sessions;
b) tabletop exercises;
c) simulations;
d) after-action learning sessions;
e) observability dashboards;
f) public-safe maps;
g) AI-RAN, O-RAN, DePIN, DLT, blockchain, sensor, geospatial, Earth observation, cyber telemetry, digital twin, and Truth Engine outputs;
h) controlled rooms, public authority rooms, emergency-management rooms, evidence rooms, data rooms, and no-download rooms;
i) public authority communications;
j) media communications;
k) public-facing risk reports; and
l) crisis-related publications.
The Corporation may support learning, evidence review, methods development, public-safe reporting, technical literacy, scenario analysis, and after-action learning for public authorities and public-interest actors, but such support shall not be represented as command, dispatch, official warning, evacuation instruction, emergency management direction, public health order, operational instruction, safety directive, or incident control.
Where emergency command confusion arises, the Corporation shall immediately classify the issue, restrict the output, issue limitation language where appropriate, notify competent internal authority, escalate to counsel or compliance where required, and hold, quarantine, correct, withdraw, or re-scope the activity.
119.3 Public Warning Boundary Oversight. The Board shall oversee the public warning boundary and shall ensure that the Corporation does not issue official public warnings, emergency alerts, evacuation notices, shelter-in-place notices, public health orders, infrastructure shutoff notices, cyber emergency directives, hazard warnings, safety commands, or other public authority warnings unless separately and lawfully authorized by a competent public authority and recorded within narrow limits.
The Corporation may publish public-safe reports, educational materials, observability summaries, research outputs, methods notes, whitepapers, technical baselines, public-good software documentation, dashboards, maps, and learning materials, provided that such outputs are framed as public-good, research, evidence, methods, learning, or public-safe communication artifacts and not as official warnings or operational instructions.
Public warning boundary oversight shall require:
a) public-safe classification before publication of risk-facing outputs;
b) limitation language for dashboards, maps, datasets, models, reports, simulations, and observability products;
c) review of titles, labels, colors, scores, alerts, badges, symbols, push notifications, automated messages, emails, API responses, interface language, and public-facing graphics that could be mistaken for official warning systems;
d) human review of material public-facing risk outputs;
e) public authority boundary review where outputs involve hazards, emergencies, health, safety, infrastructure, public security, cyber incidents, or community exposure;
f) safeguards review where outputs may stigmatize, expose, burden, or endanger communities;
g) correction, supersession, withdrawal, takedown, or public clarification where warning confusion occurs; and
h) records of public-safe publication review.
No dashboard alert, AI-generated warning, automated threshold, sensor signal, proof receipt, confidence score, risk category, map color, digital twin output, public authority room output, or Observatory output shall be treated as an official public warning unless a competent public authority separately issues the warning under lawful authority.
119.4 Public Authority Decision Boundary Oversight. The Board shall oversee the public authority decision boundary and shall ensure that the Corporation does not make, substitute for, direct, approve, veto, certify, or control public authority decisions.
Public authority decision boundary oversight shall apply to federal, state, territorial, District of Columbia, Tribal, Indigenous government, local, county, municipal, metropolitan, port, utility, public health, emergency management, public safety, public works, water, energy, food, telecom, cyber, infrastructure, environmental, procurement, public finance, grant, regulatory, permitting, enforcement, inspection, emergency, and public records contexts.
The Corporation may support public authority learning, technical literacy, evidence literacy, public-safe reporting literacy, simulation, scenario analysis, tabletop learning, after-action learning, observability methods, data governance methods, AI governance methods, cyber methods, public-safe publication methods, and controlled-room review, but shall not convert those functions into public authority action.
The Board shall require that public authority interactions be classified, as applicable, as:
a) official capacity participation;
b) observer participation;
c) regulator-listening participation;
d) public finance reader participation;
e) emergency-management participant participation;
f) public infrastructure operator participation;
g) technical learning participation;
h) data contribution participation;
i) public authority room participation;
j) controlled-room participation;
k) advisory or consultative participation; or
l) other approved capacity.
No public authority participation in a Corporation meeting, committee, council, room, forum, dashboard, repository, publication, technical baseline, Nexus interface, or public-safe report shall be represented as official adoption, public approval, public funding commitment, procurement approval, regulatory approval, public finance approval, emergency command, public warning, sovereign obligation, public-private partnership, or governmental decision unless the competent public authority separately issues and records such act through lawful processes.
119.5 Regulatory Boundary Oversight. The Board shall oversee regulatory boundary discipline and shall ensure that the Corporation does not act as a regulator, enforcement agency, inspection authority, permitting authority, adjudicator, compliance approval body, legal safe-harbor issuer, public authority substitute, or quasi-regulatory body.
Regulatory boundary oversight shall include review of any output or activity that could be understood as:
a) approving compliance with law;
b) determining regulatory status;
c) issuing permits or licenses;
d) confirming legal conformity;
e) creating regulatory safe harbor;
f) ranking legal compliance;
g) directing regulated entities;
h) replacing public authority inspection;
i) resolving legal disputes;
j) enforcing standards as law;
k) instructing public authorities to act; or
l) instructing private actors to implement legally required controls.
The Corporation may develop methods, evidence frameworks, technical baselines, public-good software, controlled vocabulary, public-safe notices, open technical references, and learning materials that support regulatory literacy and public authority learning, but such materials shall not be represented as legal compliance approval, regulator endorsement, permit approval, enforcement guidance, or official regulatory interpretation.
Where regulatory boundary ambiguity exists, the matter shall be held, escalated, reviewed by counsel or compliance where appropriate, and corrected before publication or implementation.
119.6 Procurement Neutrality Oversight. The Board shall oversee procurement neutrality and shall ensure that the Corporation does not act as a procurement authority, procurement advisor, vendor selection body, bid evaluator, public contract award body, purchasing agent, procurement-preference body, prequalification authority, or public authority procurement substitute.
Procurement neutrality oversight shall apply to all Corporation relationships with providers, vendors, contractors, sponsors, hosts, public authorities, national companies, Project SPVs, consortiums, universities, laboratories, and enterprise actors.
The Board shall ensure that no Corporation output, participation status, technical baseline, software release, public-good asset, evidence pack, proof receipt, dashboard, map, public-safe report, controlled-room participation, Academy participation, public authority learning session, provider listing, sponsor acknowledgment, host participation, repository contribution, or Nexus interface is represented as:
a) public procurement approval;
b) vendor qualification;
c) preferred provider status;
d) required provider status;
e) public authority procurement recommendation;
f) bid advantage;
g) prequalification for a public contract;
h) compliance approval for procurement;
i) technology mandate;
j) exclusive route to Nexus-compatible participation;
k) public infrastructure deployment approval; or
l) government purchasing decision.
The Corporation may provide general educational materials, public-good technical baselines, interoperability references, public-safe evidence, methods, and open technical assets, provided that such materials do not direct procurement toward any specific provider, sponsor, vendor, platform, product, project, or enterprise actor.
Where procurement neutrality risk exists, the Corporation shall use controlled vocabulary, provider-neutral presentation, objective criteria where lawful, public-safe limitation language, competition-law review, conflict review, and correction pathways.
119.7 Certification and Accreditation Boundary Oversight. The Board shall oversee certification and accreditation boundary discipline and shall ensure that the Corporation does not act as a certification body, accreditation body, conformance approval body, compliance approval body, professional credentialing body, standards approval body, maturity approval body, Nexus-compatible approval body, or legal safe-harbor issuer unless separately and lawfully authorized, insured where required, competent, and recorded.
Certification and accreditation boundary oversight shall apply to:
a) persons;
b) directors, officers, staff, fellows, advisors, contributors, maintainers, volunteers, participants, public authority participants, and controlled-room participants;
c) providers, vendors, sponsors, donors, funders, hosts, universities, laboratories, communities, and enterprise actors;
d) national companies, state operating companies, regional companies, sectoral companies, and Project SPVs;
e) nodes, hubs, clusters, hotspots, regional clusters, national dense Nexus cores, observability environments, data rooms, controlled rooms, clean rooms, evidence rooms, public authority rooms, and no-download rooms;
f) datasets, models, systems, benchmarks, evaluation harnesses, technical profiles, software, APIs, SDKs, dashboards, maps, digital twins, sensor systems, AI-RAN systems, O-RAN systems, DePIN systems, DLT systems, blockchain systems, cyber systems, geospatial systems, Earth observation systems, and technical assets; and
g) programs, courses, Academy activities, fellowships, labs, challenges, capability formation programs, competence records, and learning records.
The Corporation may issue attendance records, completion records, participation records, contribution records, evidence records, method records, training records, competence records, repository records, proof receipts, or public-safe summaries where authorized, but such records shall not be described as certification, accreditation, professional credential, legal compliance approval, procurement approval, finance-readiness, insurance-readiness, recognition, maturity standing, or Nexus-compatible status unless the competent authority and governing record expressly authorize such meaning.
119.8 Securities Boundary Oversight. The Board shall oversee the securities boundary and shall ensure that the Corporation does not conduct securities offerings, securities distributions, securities solicitation, capital placement, underwriting, brokerage, dealer activity, finder activity, investment promotion, token offering, security-token offering, investment crowdfunding, pooled investment vehicle activity, private placement activity, or transaction facilitation.
Securities boundary oversight shall apply to:
a) grant materials;
b) donor materials;
c) sponsorship materials;
d) public-good support materials;
e) national company materials;
f) Project SPV materials;
g) Nexus financing materials;
h) GRA-facing technical inputs;
i) capital-reader rooms;
j) investor-adjacent rooms;
k) proof packs;
l) dashboards;
m) public-safe reports;
n) evidence packs;
o) technical baselines;
p) public statements;
q) website materials;
r) presentations;
s) event materials;
t) social media;
u) whitepapers; and
v) AI-generated summaries.
The Board shall ensure that the Corporation does not receive transaction-based compensation, success fees, placement fees, finder fees, underwriting fees, brokerage fees, carried interest, investment management fees, or similar compensation in connection with securities or investment transactions.
The Corporation may provide public-good evidence, methods, technical baselines, public authority learning, and GRA-facing technical inputs, provided that such support is not represented as investment solicitation, securities recommendation, capital placement, transaction facilitation, or investment advice.
119.9 Investment Adviser and Broker-Dealer Boundary Oversight. The Board shall oversee the investment adviser, broker-dealer, finder, and capital-placement boundary and shall ensure that the Corporation does not provide investment advice, transaction recommendations, suitability determinations, portfolio advice, asset management, capital allocation recommendations, investor matching, capital placement, brokerage, deal execution, securities distribution, or finder services.
Investment adviser and broker-dealer boundary oversight shall require review of:
a) capital-reader rooms;
b) GRA interface materials;
c) proof-pack materials;
d) RNFD, NFD, and UNFSD-facing materials;
e) project evidence materials;
f) national company and Project SPV materials;
g) investor-adjacent presentations;
h) public finance reader sessions;
i) insurance-reader sessions;
j) lender-reader sessions;
k) sponsor materials;
l) donor and funder materials;
m) dashboards and risk summaries;
n) public-safe reports;
o) AI-generated summaries; and
p) public statements.
The Corporation shall not recommend that any person buy, sell, hold, finance, insure, lend to, guarantee, underwrite, invest in, sponsor, fund, or enter into any transaction involving any company, Project SPV, technology, asset, instrument, project, provider, or deployment.
Any technical, evidence, methods, observability, or public-good input provided to GRA, capital readers, public finance readers, lenders, insurers, underwriters, investors, or other capital-facing actors shall be framed as non-investment, non-solicitation, non-transactional, non-reliance, and technical support only.
119.10 Banking and Lending Boundary Oversight. The Board shall oversee the banking and lending boundary and shall ensure that the Corporation does not act as a bank, deposit-taking institution, lender, loan originator, credit broker, credit underwriter, loan servicer, payment intermediary, escrow agent, custodian, clearing entity, settlement entity, treasury manager for third parties, guarantor, revenue guarantor, performance guarantor, or credit approval body.
Banking and lending boundary oversight shall apply to:
a) public-good support funds;
b) grants;
c) donations;
d) sponsorships;
e) subscriptions;
f) fees;
g) cost recovery;
h) restricted funds;
i) in-kind support;
j) fellowships;
k) awards;
l) scholarships;
m) challenge prizes;
n) reimbursement arrangements;
o) fiscal sponsorship or sponsored project structures where applicable;
p) national company interfaces;
q) Project SPV interfaces;
r) GRA interfaces;
s) public finance reader interfaces; and
t) capital-reader interfaces.
The Corporation may maintain its own bank accounts, receive lawful support, pay lawful expenses, reimburse lawful costs, and manage its own funds subject to Board-approved controls, but shall not hold or control third-party funds for transaction execution, capital placement, lending, escrow, insurance, underwriting, securities settlement, or enterprise delivery.
No Corporation evidence record, proof receipt, dashboard, technical baseline, public authority learning material, GRA-facing input, or Nexus interface shall be represented as credit approval, lending approval, bankability determination, debt service assurance, guarantee, revenue guarantee, performance guarantee, or repayment assurance.
119.11 Insurance and Underwriting Boundary Oversight. The Board shall oversee the insurance and underwriting boundary and shall ensure that the Corporation does not act as an insurer, reinsurer, insurance broker, insurance agent, underwriter, managing general agent, claims handler, claims adjuster, pricing authority, coverage approver, risk-bearing intermediary, insurance placement body, insurance-readiness authority, or insurability decision-maker.
Insurance and underwriting boundary oversight shall apply to:
a) GRA-facing evidence inputs;
b) insurance-reader rooms;
c) proof packs;
d) public-safe reports;
e) observability outputs;
f) risk taxonomies;
g) resilience indicators;
h) dashboards;
i) maps;
j) digital twins;
k) technical baselines;
l) AI outputs;
m) risk models;
n) sensor signals;
o) cyber telemetry;
p) infrastructure evidence;
q) climate, nature, energy, water, food, health, disaster, telecom, supply chain, and public safety evidence; and
r) public authority learning materials.
The Corporation may support insurance literacy, technical evidence, methods, observability, loss-prevention learning, resilience evidence, and public-good baselines, but shall not determine coverage, pricing, underwriting, binding, claims, insurability, insurance-readiness, risk transfer, or insurance eligibility.
Any insurance-facing output shall include limitation language where appropriate and shall be reviewed for finance-boundary, professional-boundary, public authority, data / AI / cyber, safeguards, and public-safe publication risks.
119.12 Rating Boundary Oversight. The Board shall oversee the rating boundary and shall ensure that the Corporation does not issue credit ratings, investment grade opinions, bankability ratings, resilience ratings, insurance ratings, procurement ratings, provider ratings, project ratings, security ratings, public finance ratings, sovereign ratings, risk ratings, or financeability determinations unless separately and lawfully authorized and recorded.
Rating boundary oversight shall apply to:
a) scores;
b) maturity classes;
c) readiness classes;
d) confidence classes;
e) uncertainty classes;
f) risk tiers;
g) dashboards;
h) maps;
i) indexes;
j) benchmarks;
k) proof receipts;
l) public-safe reports;
m) evidence packs;
n) Grid-support materials;
o) Docket-support materials;
p) GRF-facing inputs;
q) GRA-facing inputs;
r) public authority learning outputs;
s) automated scores; and
t) AI-generated classifications.
The Corporation may develop evidence classifications, confidence notes, uncertainty notes, technical profiles, method outputs, maturity inputs, readiness inputs, and public-good learning materials, but shall not represent them as ratings, investment opinions, credit opinions, insurance opinions, public finance opinions, procurement scores, or official determinations.
Where a score, class, signal, dashboard, benchmark, or index could be misunderstood as a rating, the Board shall require controlled vocabulary, limitation language, review, correction pathways, and, where necessary, withdrawal or redesign.
119.13 Public Finance Boundary Oversight. The Board shall oversee the public finance boundary and shall ensure that the Corporation does not approve, allocate, underwrite, guarantee, rate, commit, certify, recommend, administer, broker, or execute public finance, sovereign finance, municipal finance, development finance, MDB / DFI finance, tax credits, public guarantees, appropriations, grants, subsidies, budget allocations, public credit, concessional finance, blended finance, or public-private partnership finance.
Public finance boundary oversight shall apply to:
a) public finance reader rooms;
b) public authority learning sessions;
c) GRA interfaces;
d) RNFD, NFD, and UNFSD interfaces;
e) national company interfaces;
f) Project SPV interfaces;
g) public authority materials;
h) grant materials;
i) public infrastructure materials;
j) resilience infrastructure materials;
k) climate, nature, energy, water, food, health, telecom, cyber, disaster, and public safety infrastructure materials;
l) evidence packs;
m) proof packs;
n) dashboards;
o) public-safe reports; and
p) public statements.
The Corporation may provide evidence, methods, technical literacy, public-good software, open technical baselines, public authority learning, and non-executing technical inputs relevant to public finance literacy or diligence translation, but shall not determine eligibility, approve funding, direct appropriations, recommend public finance transactions, bind public authorities, or create reliance for capital allocation.
119.14 Capital-Reader Boundary Oversight. The Board shall oversee the capital-reader boundary and shall ensure that any capital-reader, investor-reader, insurer-reader, lender-reader, underwriter-reader, bank-reader, public finance reader, donor-reader, sponsor-reader, or funder-reader interface remains informational, educational, evidence-based, non-solicitation, non-transactional, non-reliance, and non-executing.
Capital-reader boundary oversight shall include:
a) room design review;
b) participant classification;
c) agenda controls;
d) presentation review;
e) evidence pack limitation review;
f) proof pack limitation review;
g) public-safe notice review;
h) no-investment-advice language;
i) no-solicitation language;
j) no-brokerage language;
k) no-finder language;
l) no-underwriting language;
m) no-lending language;
n) no-insurance-placement language;
o) no-rating language;
p) no-public-finance-approval language;
q) no-transaction-facilitation language;
r) competition-law controls;
s) conflict controls; and
t) records of attendance, capacity, materials, limitations, and corrections.
The Corporation shall not organize a capital-reader interface in a manner that matches investors with issuers, promotes investment, negotiates terms, circulates offering materials, screens investors for securities transactions, recommends transactions, or otherwise causes the Corporation to act as an intermediary.
119.15 Finance-Readiness Boundary Oversight. The Board shall oversee the finance-readiness boundary and shall ensure that the Corporation does not issue, imply, guarantee, sell, approve, certify, or control finance-readiness, capital-readability, bankability, investability, insurance-readiness, creditworthiness, public-finance readiness, underwriting readiness, or transaction readiness.
Finance-readiness boundary oversight shall preserve GRA’s separate role as finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, capital-reader room, and regulated-perimeter discipline steward, while preserving the Corporation’s separate role as evidence, methods, observability, ontology, technical baseline, public-good software, public authority learning, and safeguards steward.
The Corporation may provide technical evidence inputs, methods inputs, observability inputs, ontology inputs, public-good technical baseline inputs, correction signals, and public-safe learning materials to GRA, but such inputs shall not be represented as finance-readiness determinations.
No evidence pack, technical baseline, proof receipt, dashboard, map, AI output, maturity input, Grid input, Docket input, public authority learning output, controlled-room output, public-safe report, or Nexus interface produced by the Corporation shall be described as finance-ready, bankable, investable, insurable, creditworthy, de-risked for investment, transaction-ready, capital-approved, lender-approved, insurer-approved, or public-finance-approved unless a competent authority separately and lawfully makes and records such determination outside the Corporation’s authority.
119.16 Provider Neutrality Oversight. The Board shall oversee provider neutrality and shall ensure that the Corporation does not prefer, endorse, select, approve, certify, mandate, rank, promote, exclude, or disadvantage providers, vendors, contractors, integrators, operators, cloud providers, AI providers, cybersecurity providers, telecom providers, AI-RAN providers, O-RAN providers, DePIN providers, DLT providers, sensor providers, geospatial providers, Earth observation providers, software providers, data processors, host institutions, sponsors, or enterprise actors except through lawful internal procurement, lawful contracting, or objective participation controls that do not create public-facing provider preference.
Provider neutrality oversight shall include review of:
a) provider participation;
b) provider listings;
c) provider acknowledgments;
d) sponsor acknowledgments;
e) host acknowledgments;
f) technical contribution records;
g) public-good software repositories;
h) technical baseline references;
i) interoperability profiles;
j) controlled-room participation;
k) public authority learning participation;
l) training participation;
m) Academy participation;
n) challenge participation;
o) benchmarking participation;
p) public-safe reports;
q) websites;
r) presentations;
s) media statements; and
t) Nexus interface materials.
The Corporation may identify factual roles, contributions, sponsorships, donations, in-kind support, technical contributions, host support, or participation status where accurate, recorded, public-safe, and not misleading. Such identification shall not imply preferred provider status, procurement advantage, certification, recognition, Nexus-compatible approval, public authority endorsement, or operational approval.
Where provider neutrality risk exists, the Board shall require neutral language, objective classification, conflict review, competition review, sponsor non-control review, public authority boundary review, public-safe limitation language, and correction pathways.
119.17 Sponsor Non-Control Oversight. The Board shall oversee sponsor non-control and shall ensure that sponsors, donors, funders, supporters, contributors, hosts, providers, vendors, enterprise actors, investors, insurers, lenders, national companies, Project SPVs, public authorities, universities, laboratories, or other external actors do not control the Corporation’s governance, evidence, methods, research conclusions, public-safe publications, technical baselines, software releases, repositories, dashboards, maps, controlled rooms, data rooms, public authority learning, Nexus interfaces, Board decisions, officer decisions, committee recommendations, staffing, public claims, or correction decisions.
Sponsor non-control oversight shall apply to:
a) sponsorship agreements;
b) donor agreements;
c) grant agreements;
d) restricted fund instruments;
e) in-kind contribution arrangements;
f) host agreements;
g) provider agreements;
h) university agreements;
i) laboratory agreements;
j) public authority instruments;
k) national company and Project SPV interfaces;
l) public-good support campaigns;
m) branded programs;
n) named fellowships;
o) named rooms;
p) named publications;
q) named technical assets;
r) event sponsorships;
s) public acknowledgments; and
t) public-safe financial summaries.
No sponsor, donor, funder, host, provider, or enterprise actor shall receive governance control, research outcome control, publication veto, data access privilege, public authority access purchase, recognition purchase, finance-readiness purchase, certification purchase, procurement advantage, provider preference, public warning influence, emergency command influence, or correction veto by reason of support.
The Board shall require refusal, return, restriction, restructuring, disclosure, ring-fencing, diversification, termination, or corrective action where support creates undue influence, private benefit, inurement, capture, public authority confusion, finance-boundary risk, procurement risk, certification risk, recognition risk, or public trust risk.
119.18 Donor and Funder Non-Control Oversight. The Board shall oversee donor and funder non-control and shall ensure that donations, grants, restricted funds, unrestricted funds, program support, fellowships, scholarships, awards, challenge prizes, subscriptions, fees, cost recovery, public-good infrastructure support, and in-kind contributions do not convert into control over the Corporation’s mission, governance, research, evidence, methods, publications, technical baselines, software, data, AI, cyber systems, safeguards, public authority interfaces, Nexus interfaces, or corrections.
Donor and funder non-control oversight shall require:
a) gift acceptance review;
b) grant acceptance review;
c) restricted fund review;
d) charitable solicitation review where applicable;
e) tax review;
f) private benefit and inurement review;
g) conflict and related-party review;
h) sanctions and export-control review;
i) controlled-technology review;
j) public authority boundary review;
k) finance-boundary review;
l) procurement-neutrality review;
m) certification and recognition boundary review;
n) data / AI / cyber / privacy review;
o) safeguards and protected knowledge review;
p) public acknowledgment review;
q) reporting obligation review;
r) refusal, return, restriction, termination, or closeout review; and
s) donor and funder records.
The Corporation may honor lawful donor intent and restricted fund purposes where compatible with law, the Articles or Certificate, this Bylaw, public-benefit purpose, tax status, nonprofit character, and non-execution controls, but donor or funder intent shall not override institutional independence, public-good stewardship, records discipline, correctionability, safeguards, or lawful Board authority.
119.19 Public Authority Participation Boundary Oversight. The Board shall oversee public authority participation boundary discipline and shall ensure that participation by federal, state, territorial, District of Columbia, Tribal, Indigenous government, local, county, municipal, metropolitan, utility, port, public health, emergency management, public safety, public works, water, energy, food, telecom, cyber, infrastructure, environmental, public finance, procurement, or regulatory actors is properly classified, recorded, limited, and public-safe.
Public authority participation boundary oversight shall include:
a) capacity classification;
b) official-capacity records;
c) observer records;
d) regulator-listening records;
e) public finance reader records;
f) emergency-management participant records;
g) public infrastructure operator records;
h) simulation participant records;
i) public authority data contribution records;
j) public authority reference records;
k) public authority room records;
l) controlled-room records;
m) public-safe notice records;
n) no-official-adoption language;
o) no-public-warning language;
p) no-emergency-command language;
q) no-procurement-approval language;
r) no-public-finance-approval language;
s) no-regulatory-approval language;
t) no-sovereign-obligation language; and
u) correction records.
No public authority participant shall be given special control over the Corporation’s governance, evidence, methods, publications, technical baselines, software, public claims, provider presentation, sponsor presentation, finance-facing materials, or Nexus interface unless lawful, recorded, and consistent with the Corporation’s public-benefit and non-execution role.
119.20 Automated Output Boundary Oversight. The Board shall oversee automated output boundary discipline and shall ensure that AI systems, model outputs, inference outputs, agentic workflows, dashboards, maps, digital twins, proof receipts, DLT records, blockchain entries, smart contracts, role keys, DePIN records, AI-RAN signals, O-RAN signals, sensor signals, cyber telemetry, geospatial layers, Earth observation outputs, benchmark scores, evaluation harness outputs, confidence scores, uncertainty scores, and automated classifications do not create authority by automation.
Automated output boundary oversight shall require, as applicable:
a) model register entries;
b) dataset cards;
c) model cards;
d) system cards;
e) benchmark cards;
f) evaluation harness records;
g) inference records;
h) compute workload records;
i) human review;
j) audit logs;
k) provenance records;
l) source-lineage records;
m) confidence and uncertainty notes;
n) limitation language;
o) access classification;
p) publication classification;
q) public-safe review;
r) data / AI / cyber review;
s) privacy review;
t) safeguards review;
u) public authority boundary review;
v) finance-boundary review;
w) certification-boundary review;
x) procurement-neutrality review;
y) provider-neutrality review;
z) sponsor non-control review; and
aa) correction pathways.
No automated output shall be treated as technical truth, public warning, emergency command, public authority decision, recognition, finance-readiness, insurance-readiness, investment suitability, rating, certification, procurement approval, provider approval, operational approval, or binding governance decision without competent human review, lawful authority, and record support.
119.21 Boundary Incident Review. The Board shall ensure that any suspected or actual breach, near miss, ambiguity, overclaim, misuse, misstatement, unauthorized representation, uncontrolled output, defective limitation, improper public authority reference, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider-preference claim, sponsor-control claim, automated-output overclaim, emergency-command implication, public-warning implication, or execution-facing act is treated as a boundary incident.
Boundary incident review shall include, as applicable:
a) intake;
b) classification;
c) immediate hold;
d) stop order;
e) quarantine;
f) access restriction;
g) publication freeze;
h) implementation freeze;
i) technical isolation;
j) controlled-room lockdown;
k) public authority notice review;
l) sponsor, donor, funder, provider, host, or participant notice review;
m) legal review;
n) compliance review;
o) counsel review;
p) data / AI / cyber review;
q) safeguards review;
r) public-safe review;
s) Board or committee review;
t) correction;
u) supersession;
v) withdrawal;
w) retraction;
x) takedown;
y) archive;
z) referral; and
aa) post-incident review.
A boundary incident shall not be minimized because no harm has yet occurred. Near misses, misleading drafts, incorrect labels, automated outputs, public-facing ambiguity, investor-adjacent ambiguity, public authority ambiguity, sponsor-influenced ambiguity, provider-influenced ambiguity, or uncontrolled terminology may be sufficient to require correction.
No person shall bypass a hold, quarantine, publication freeze, access restriction, or corrective action by using an unofficial copy, derivative material, AI summary, repository fork, private message, oral statement, slide deck, public authority communication, sponsor communication, provider communication, media communication, or Nexus interface.
119.22 Boundary Oversight Records. The Corporation shall maintain Boundary Oversight Records sufficient to demonstrate that non-execution, public authority, finance, procurement, certification, provider-neutrality, sponsor non-control, donor non-control, funder non-control, public-warning, emergency-command, automated-output, and regulated-perimeter boundaries have been actively overseen, classified, enforced, corrected, and preserved.
Boundary Oversight Records shall include, as applicable:
a) non-execution records;
b) emergency command boundary records;
c) public warning boundary records;
d) public authority decision boundary records;
e) regulatory boundary records;
f) procurement-neutrality records;
g) certification and accreditation boundary records;
h) securities boundary records;
i) investment adviser, broker-dealer, finder, and capital-placement boundary records;
j) banking and lending boundary records;
k) insurance and underwriting boundary records;
l) rating boundary records;
m) public finance boundary records;
n) capital-reader boundary records;
o) finance-readiness boundary records;
p) provider-neutrality records;
q) sponsor non-control records;
r) donor and funder non-control records;
s) public authority participation capacity records;
t) automated output boundary records;
u) public-safe notice records;
v) controlled vocabulary records;
w) public claims review records;
x) limitation language records;
y) conflict and recusal records;
z) support acceptance records;
aa) provider participation records;
bb) public authority room records;
cc) capital-reader room records;
dd) controlled-room records;
ee) data-room records;
ff) evidence-room records;
gg) clean-room records;
hh) no-download-room records;
ii) AI, model, inference, compute workload, dashboard, map, digital twin, proof receipt, DLT, blockchain, DePIN, AI-RAN, O-RAN, sensor, cyber telemetry, geospatial, and Earth observation output review records;
jj) hold, stop, quarantine, access restriction, publication freeze, implementation freeze, technical isolation, controlled-room lockdown, re-scope, externalization, referral, termination, correction, supersession, withdrawal, retraction, takedown, archive, and public clarification records;
kk) legal review records;
ll) compliance review records;
mm) counsel review records;
nn) Board review records;
oo) committee review records;
pp) post-incident review records;
qq) training records;
rr) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata; and
ss) any other record necessary to demonstrate that the Corporation did not cross, authorize, imply, or fail to correct a prohibited boundary.
The governing rule of this Section is that the Corporation’s legitimacy depends on maintaining strict, visible, recorded, and correctionable boundaries. The Corporation may convene, research, observe, analyze, build public-good software, steward methods, support technical baselines, support public authority learning, support GRF-facing inputs, support GRA-facing inputs, support Nexus interoperability, and publish public-safe outputs, but it shall not execute. It shall not command emergencies, issue official warnings, make public authority decisions, regulate, procure, certify, accredit, recognize, rate, approve finance, solicit securities, advise investments, broker capital, lend, insure, underwrite, guarantee, prefer providers, allow sponsor control, or convert automated outputs into authority. Boundary discipline shall be proactive, not reactive; record-based, not informal; public-safe, not promotional; role-separated, not collapsed; and correctionable wherever law, evidence, public trust, safeguards, or institutional meaning requires correction.
Section 120. Oversight of Research, Evidence, Methods, Technical Truth, and Public-Good Technical Assets
120.1 Research Oversight. The Board shall oversee the Corporation’s research function and shall ensure that all research conducted, sponsored, supported, hosted, published, contributed to, or relied upon by the Corporation advances the Corporation’s lawful nonprofit, public-benefit, tax-exempt-compatible, evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, verifiable compute and intelligence, public authority learning, public-safe reporting, and safeguards purposes.
Research oversight shall apply to all research activities involving, without limitation:
a) systemic risk, resilience infrastructure, public safety support, public health support, climate, nature, biodiversity, energy, water, food, health, disaster, telecom, cyber, supply chain, ports, borders, public trust, infrastructure, and mission-critical systems;
b) AI, AI-RAN, O-RAN, DePIN, DLT, blockchain, Web3, quantum-relevant systems, sovereign compute, high-performance computing, cyber-physical systems, robotics, drones, sensors, geospatial systems, Earth observation, digital twins, biosecurity, advanced manufacturing, semiconductors, and other exponential technologies;
c) public authority learning, public authority capacity classification, regulator-listening rooms, public finance reader rooms, emergency-management learning, public infrastructure operator learning, scenario sessions, simulations, tabletop exercises, after-action learning, and controlled public authority interfaces;
d) community safeguards, Tribal and Indigenous protocol respect, Indigenous data safeguards, protected knowledge, local and territorial knowledge, public-safe mapping, civil rights, accessibility, grievance, remedy, protected participation, non-retaliation, and do-no-harm review;
e) public-good software, open technical baselines, reference architectures, schemas, APIs, SDKs, dashboards, maps, datasets, benchmarks, test harnesses, evaluation sets, gold vectors, negative tests, evidence packs, proof receipts, and technical profiles; and
f) GRF-facing inputs, GRA-facing technical inputs, Nexus Docket support, Nexus Grid support, Nexus Standards support, Nexus Observatory support, Nexus Truth Engine methods, Nexus Network interfaces, Nexus Universe materials, Nexus Academy materials, and Nexus Competence Cell materials.
The Board shall ensure that research is designed, conducted, reviewed, published, corrected, restricted, withdrawn, or archived in a manner consistent with applicable law, research ethics, data protection, privacy, AI governance, cybersecurity, human-subjects protections where applicable, community safeguards, protected knowledge controls, export-control and sanctions compliance, competition law, professional-boundary discipline, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, validity-by-record, and correctionability.
No research activity shall be treated as lawful or mission-compatible merely because it is innovative, technically valuable, sponsor-supported, provider-supported, public authority-relevant, capital-reader-relevant, Nexus-relevant, or publicly beneficial in aspiration. Research shall remain bounded by law, the Articles or Certificate, this Bylaw, Board policy, approved methodology, records discipline, public-safe limitation, and correction pathways.
120.2 Research Integrity Oversight. The Board shall oversee research integrity and shall ensure that the Corporation maintains institutional controls for honesty, accuracy, transparency, reproducibility, methodological discipline, conflict disclosure, source integrity, authorship integrity, attribution, review, correction, and public-safe communication.
Research integrity oversight shall include, without limitation:
a) adoption and enforcement of research integrity policies;
b) review of research agenda integrity;
c) review of research design integrity;
d) source-lineage and provenance review;
e) data integrity review;
f) model, algorithm, benchmark, and evaluation integrity review;
g) authorship, contribution, acknowledgment, and attribution controls;
h) sponsor, donor, funder, provider, host, employer, public authority, university, laboratory, national company, Project SPV, and enterprise actor conflict review;
i) plagiarism, fabrication, falsification, manipulation, suppression, selective reporting, undisclosed AI-use, undisclosed sponsor influence, and publication-bias review;
j) peer review, technical review, red-team review, model review, and public-safe review where appropriate;
k) correction, supersession, withdrawal, retraction, takedown, archive, and public clarification pathways; and
l) research integrity records sufficient to demonstrate lawful and defensible stewardship.
The Board shall ensure that no sponsor, donor, funder, provider, host, public authority participant, capital reader, investor, insurer, lender, underwriter, national company, Project SPV, university, laboratory, media actor, or enterprise actor may purchase, direct, suppress, veto, distort, delay, mislabel, or overstate a research conclusion.
Research integrity shall apply equally to formal reports, technical notes, whitepapers, public-safe summaries, dashboards, maps, datasets, software documentation, AI-generated outputs, benchmark results, public authority learning materials, controlled-room materials, evidence packs, proof receipts, repository artifacts, Nexus interface materials, GRF-facing inputs, and GRA-facing inputs.
120.3 Research Ethics Oversight. The Board shall oversee research ethics and shall ensure that research involving persons, communities, rights-bearing data, sensitive information, public authority information, protected knowledge, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, Indigenous knowledge, local or territorial knowledge, or vulnerable populations is reviewed through appropriate ethical, legal, safeguards, and public-safe pathways.
Research ethics oversight shall include, as applicable:
a) human-subjects review;
b) institutional review board or equivalent review;
c) informed consent review;
d) waiver, alteration, or documentation-of-consent review where lawful;
e) youth, vulnerable population, health-sensitive, disability, accessibility, civil rights, and non-discrimination review;
f) Tribal, Indigenous, community, local, territorial, cultural, environmental, and protected knowledge review;
g) public authority data review;
h) data minimization, purpose limitation, de-identification, pseudonymization, aggregation, redaction, retention, access, and deletion review;
i) AI-use, model-use, automated inference, data enrichment, embedding, retrieval, fine-tuning, training, and model-improvement review;
j) cybersecurity, access-control, repository, credential, key, token, and secure-compute review;
k) public-safe mapping, geospatial exposure, infrastructure exposure, community exposure, and do-no-harm review;
l) grievance, remedy, withdrawal, correction, non-retaliation, and protected participation pathways; and
m) research ethics records.
The Board shall ensure that research ethics is not reduced to legal compliance alone. Research ethics shall preserve dignity, autonomy, safety, public trust, community integrity, Indigenous and Tribal protocol respect, accessibility, civil rights, protected knowledge, privacy, confidentiality, and public-good legitimacy.
No research may proceed, be published, or be externally used where required ethical review has been omitted, materially defective, unresolved, or superseded by new risk information, unless the Board or delegated authority lawfully determines and records an emergency, protective, or corrective pathway consistent with this Bylaw.
120.4 Evidence Doctrine Oversight. The Board shall oversee the Corporation’s Evidence Doctrine and shall ensure that evidence is treated as recorded, sourced, classified, bounded, reviewable, challengeable, and correctionable institutional material.
Evidence Doctrine oversight shall require that evidence artifacts identify, as applicable:
a) source;
b) source type;
c) source authority;
d) source date;
e) collection method;
f) custody;
g) provenance;
h) transformation history;
i) data lineage;
j) model involvement;
k) human review;
l) confidence level;
m) uncertainty level;
n) limitations;
o) exclusions;
p) access class;
q) publication class;
r) safeguards class;
s) public authority boundary;
t) finance boundary;
u) certification boundary;
v) procurement boundary;
w) provider-neutrality boundary;
x) sponsor non-control boundary;
y) correction pathway; and
z) supersession or archive status.
The Board shall ensure that evidence is not inflated into recognition, standing, maturity status, finance-readiness, insurance-readiness, bankability, investment suitability, public finance approval, certification, procurement approval, public authority decision, public warning, emergency command, provider approval, sponsor entitlement, or operational authorization.
Evidence may support GRF, GRA, Nexus Standards, Nexus Observatory, Nexus Grid, Nexus Docket, Nexus Academy, Nexus Competence Cells, public authority learning, technical baselines, public-safe publications, and public-good software only within the authority, limitation language, controlled vocabulary, and record discipline applicable to the relevant interface.
120.5 Evidence Quality Oversight. The Board shall oversee evidence quality and shall ensure that evidence used by the Corporation meets appropriate standards of relevance, reliability, traceability, timeliness, completeness, proportionality, contextual accuracy, methodological fitness, public-safe presentation, and correctionability.
Evidence quality oversight shall include review of:
a) source reliability;
b) corroboration;
c) contradiction;
d) stale evidence;
e) incomplete evidence;
f) disputed evidence;
g) biased evidence;
h) synthetic evidence;
i) AI-generated or AI-mediated evidence;
j) sensor-derived evidence;
k) cyber telemetry evidence;
l) geospatial evidence;
m) Earth observation evidence;
n) digital twin evidence;
o) AI-RAN and O-RAN signal evidence;
p) DePIN, DLT, blockchain, and ledger evidence;
q) public authority evidence;
r) community evidence;
s) protected knowledge evidence;
t) sponsor or provider-originated evidence;
u) public claims evidence; and
v) correction history.
Evidence quality controls shall prevent the Corporation from relying on evidence that is materially unsupported, misleading, untraceable, unlawfully obtained, ethically defective, improperly transformed, insufficiently reviewed, unsafe for public use, or inconsistent with the Corporation’s public-benefit role.
Where evidence quality is uncertain, the Board shall require limitation language, uncertainty classification, restricted use, additional review, controlled-room handling, public-safe redaction, withholding, correction, supersession, withdrawal, or archive.
120.6 Source Lineage and Provenance Oversight. The Board shall oversee source lineage and provenance discipline and shall ensure that material evidence, data, software, models, benchmarks, dashboards, maps, public-good technical assets, and public-safe reports maintain records sufficient to identify origin, custody, transformation, review, approval, publication, correction, and supersession.
Source lineage and provenance oversight shall apply to:
a) datasets;
b) documents;
c) public authority records;
d) community submissions;
e) Indigenous or protected knowledge materials;
f) sensor data;
g) AI-RAN and O-RAN signals;
h) DePIN records;
i) DLT and blockchain records;
j) cyber telemetry;
k) geospatial layers;
l) Earth observation imagery and derived products;
m) digital twin assumptions;
n) model outputs;
o) inference outputs;
p) benchmark outputs;
q) software dependencies;
r) software bills of materials;
s) repository commits;
t) proof receipts;
u) controlled-room exhibits;
v) public-safe publications; and
w) GRF-facing, GRA-facing, Nexus-facing, public authority-facing, and enterprise-interface materials.
The Board shall ensure that no material artifact is treated as authoritative merely because it appears in a repository, dashboard, ledger, proof receipt, data room, controlled room, publication, public authority room, or Nexus interface. Authority shall arise only from competent process and record.
Where provenance is incomplete, disputed, compromised, sensitive, protected, or unsafe for publication, the Board shall require restriction, redaction, confidence limitation, additional review, quarantine, correction, withdrawal, or exclusion.
120.7 Confidence and Uncertainty Oversight. The Board shall oversee confidence and uncertainty discipline and shall ensure that material evidence outputs, methods outputs, observability outputs, technical truth outputs, dashboards, maps, model outputs, automated scores, proof receipts, public-safe reports, and Nexus-facing materials do not overstate certainty.
Confidence and uncertainty oversight shall include, as applicable:
a) confidence classification;
b) uncertainty classification;
c) assumptions disclosure;
d) limitations disclosure;
e) missing evidence identification;
f) contested evidence identification;
g) method sensitivity review;
h) model sensitivity review;
i) geospatial and temporal uncertainty review;
j) sensor reliability review;
k) cyber telemetry reliability review;
l) AI-output reliability review;
m) digital twin assumption review;
n) source diversity review;
o) corroboration review;
p) contradiction review;
q) human review;
r) public-safe limitation language; and
s) correction pathways.
No confidence score, uncertainty note, benchmark value, automated score, dashboard signal, map layer, risk category, maturity input, readiness input, proof receipt, or public-safe classification shall be represented as rating, certification, recognition, finance-readiness, insurance-readiness, procurement approval, public authority decision, emergency command, official public warning, or operational instruction.
The Board shall require that uncertainty be preserved where uncertainty exists. Public-good trust is not served by false precision, hidden assumptions, promotional certainty, sponsor-driven certainty, provider-driven certainty, or authority-inflating language.
120.8 Methods Stewardship Oversight. The Board shall oversee the Corporation’s methods stewardship function and shall ensure that methods are developed, adopted, versioned, tested, reviewed, bounded, published, restricted, corrected, superseded, withdrawn, retired, or archived through competent records.
Methods stewardship oversight shall apply to:
a) evidence methods;
b) research methods;
c) validation methods;
d) verification methods;
e) confidence methods;
f) uncertainty methods;
g) source-comparison methods;
h) corroboration methods;
i) contradiction methods;
j) failed-signal methods;
k) spoof-indicator methods;
l) sensor-fusion methods;
m) AI-output review methods;
n) model-evaluation methods;
o) AI-RAN and O-RAN signal interpretation methods;
p) DePIN, DLT, blockchain, and ledger validation methods;
q) digital twin assumption-review methods;
r) geospatial methods;
s) Earth observation methods;
t) cyber evidence methods;
u) public-safe publication methods;
v) community safeguards methods;
w) public authority learning methods;
x) correction methods; and
y) Nexus Truth Engine and Nexus Observatory methods.
Each material method shall identify, as applicable, its purpose, scope, excluded scope, assumptions, dependencies, validation history, limitations, intended users, prohibited uses, access class, publication class, public-safe status, custodian, version, effective date, review date, supersession status, correction pathway, and repository location.
No method shall be represented as law, regulation, public authority approval, finance-readiness approval, insurance-readiness approval, certification, accreditation, procurement mandate, recognition, rating, provider approval, sponsor entitlement, or enterprise execution authority.
120.9 Observability Methods Oversight. The Board shall oversee observability methods and shall ensure that the Corporation’s support for Nexus Observatory, observability nodes, hubs, clusters, hotspots, regional clusters, national dense Nexus cores, state interfaces, territorial interfaces, Tribal and Indigenous interfaces, local interfaces, sectoral interfaces, public authority interfaces, and North America interfaces remains evidence-based, methods-driven, public-safe, non-executing, and correctionable.
Observability methods oversight shall include review of:
a) sensor methods;
b) edge compute methods;
c) AI-RAN methods;
d) O-RAN methods;
e) DePIN methods;
f) DLT and blockchain reference methods;
g) digital twin methods;
h) cyber telemetry methods;
i) geospatial methods;
j) Earth observation methods;
k) dashboard methods;
l) map methods;
m) resilience indicator methods;
n) degraded-mode awareness methods;
o) public-safe observability outputs;
p) observability data governance;
q) observability privacy controls;
r) observability cyber controls;
s) observability AI controls;
t) observability safeguards; and
u) observability correction pathways.
The Board shall ensure that observability outputs do not become public warnings, emergency commands, operational instructions, public authority decisions, procurement approvals, finance-readiness determinations, certification, recognition, provider approval, or sponsor-controlled outputs.
Where observability outputs may affect public safety, infrastructure, cyber operations, public authority action, community exposure, protected knowledge, capital interpretation, provider standing, or public trust, the Board shall require heightened review, limitation language, access classification, public-safe publication controls, and correction readiness.
120.10 Ontology and Controlled Vocabulary Oversight. The Board shall oversee ontology and controlled vocabulary discipline and shall ensure that institutional meaning is governed, versioned, record-supported, and resistant to silent meaning shifts.
Ontology and controlled vocabulary oversight shall include, without limitation:
a) definitions schedules;
b) controlled vocabulary registers;
c) semantic registers;
d) taxonomies;
e) schemas;
f) data dictionaries;
g) metadata dictionaries;
h) risk categories;
i) evidence classifications;
j) maturity concepts;
k) readiness concepts;
l) public authority capacity terms;
m) finance-boundary terms;
n) certification-boundary terms;
o) procurement-boundary terms;
p) recognition-boundary terms;
q) Nexus-compatible claim terms;
r) public-safe notice language;
s) non-reliance language;
t) prohibited terms;
u) restricted terms;
v) deprecated terms; and
w) translation and accessibility terminology.
The Board shall ensure that controlled vocabulary applies to Board materials, committee materials, officer materials, public materials, websites, public-safe reports, dashboards, maps, datasets, software documentation, technical baselines, repositories, grant materials, sponsorship materials, public authority materials, Academy materials, Nexus materials, GRF-facing inputs, and GRA-facing inputs.
No person may use uncontrolled language to convert evidence into recognition, readiness input into finance-readiness, technical baseline into certification, participation into endorsement, public authority learning into public authority action, provider participation into provider preference, sponsor support into sponsor control, or automated output into authority.
120.11 Nexus Truth Engine Methods Oversight. The Board shall oversee Nexus Truth Engine methods and shall ensure that any Truth Engine-related methods used, supported, published, referenced, or integrated by the Corporation remain confidence, corroboration, contradiction, source-comparison, failed-signal, spoof-indicator, evidence-challenge, and correction methods, not final truth, public authority decision, public warning, emergency command, certification, recognition, finance-readiness, rating, procurement approval, or operational authorization.
Truth Engine methods oversight shall include:
a) source-comparison logic;
b) corroboration logic;
c) contradiction handling;
d) failed-signal handling;
e) spoof-indicator handling;
f) confidence classification;
g) uncertainty classification;
h) automated score limitation;
i) model-output review;
j) human-review requirements;
k) evidence challenge pathways;
l) correction triggers;
m) auditability;
n) reproducibility;
o) public-safe presentation;
p) access and publication classification;
q) data / AI / cyber controls;
r) safeguards review; and
s) record support.
The Board shall ensure that Truth Engine outputs are treated as methods-supported evidence artifacts or decision-support materials only within approved limits. No Truth Engine output shall override competent human judgment, Board authority, public authority authority, GRF authority, GRA authority, Nexus Standards authority, or lawful records.
Where Truth Engine methods are used in public-facing or public authority-facing settings, the Board shall require limitation language, public-safe review, uncertainty disclosure, correction readiness, and prevention of authority-inflating presentation.
120.12 Verifiable Compute and Verifiable Intelligence Oversight. The Board shall oversee verifiable compute and verifiable intelligence methods and shall ensure that compute, model, inference, benchmark, evaluation, agentic, dataset, dashboard, automation, proof, and AI-mediated systems used or supported by the Corporation are record-supported, secure, bounded, reviewable, explainable where appropriate, auditable, public-safe, and correctionable.
Verifiable compute and verifiable intelligence oversight shall include, as applicable:
a) model registers;
b) dataset cards;
c) model cards;
d) system cards;
e) benchmark cards;
f) evaluation harness records;
g) inference records;
h) compute workload records;
i) prompt, retrieval, embedding, fine-tuning, training, and model-improvement restrictions;
j) secure compute controls;
k) compute-to-data controls;
l) confidential computing controls;
m) secure enclave controls;
n) sovereign compute considerations;
o) access controls;
p) identity controls;
q) logging and monitoring;
r) human review;
s) audit trails;
t) proof receipts;
u) correction records; and
v) incident response pathways.
No model, inference, benchmark, automated score, agentic workflow, compute output, dashboard output, digital twin output, proof receipt, DLT entry, blockchain entry, AI-RAN signal, O-RAN signal, DePIN record, sensor signal, cyber telemetry output, or geospatial layer shall be treated as authority unless supported by competent human review, lawful delegation, and a proper institutional record.
The Board shall ensure that AI systems do not silently alter institutional meaning, bypass review, create unauthorized public claims, expose protected knowledge, weaken public authority boundaries, create finance overclaims, create certification overclaims, create procurement overclaims, or substitute for correctionable institutional judgment.
120.13 Public-Good Software Oversight. The Board shall oversee public-good software and shall ensure that software developed, maintained, funded, hosted, contributed to, released, forked, adopted, referenced, or relied upon by the Corporation advances lawful public-benefit purposes and preserves secure development, licensing discipline, provenance, public-safe use, anti-enclosure, interoperability, correctionability, and non-execution.
Public-good software oversight shall apply to:
a) source code;
b) APIs;
c) SDKs;
d) schemas;
e) data dictionaries;
f) dashboards;
g) maps;
h) data tools;
i) AI tools;
j) model evaluation tools;
k) benchmark libraries;
l) test harnesses;
m) gold vectors;
n) negative tests;
o) public authority learning tools;
p) observability tools;
q) Truth Engine tools;
r) proof receipt tools;
s) repository tools;
t) access-control tools;
u) controlled-room tools;
v) public-safe publication tools; and
w) Nexus interoperability tools.
Public-good software oversight shall require, as applicable, licensing review, contributor review, IP chain-of-title review, dependency review, SBOM review, vulnerability review, secret scanning, secure release, artifact signing, provenance records, rollback plans, security notices, public-safe documentation, prohibited-use notices, and correction pathways.
No public-good software release shall be represented as certification, procurement approval, provider approval, public authority adoption, finance-readiness, insurance-readiness, recognition, operational approval, emergency command, or public warning. Software may be public-good infrastructure, but it shall not create prohibited authority by code, interface, configuration, automation, or public description.
120.14 Open Technical Baseline Oversight. The Board shall oversee open technical baselines and shall ensure that baselines adopted, developed, referenced, published, or supported by the Corporation are properly scoped, versioned, bounded, public-safe, interoperable, inclusive, anti-capture, correctionable, and subordinate to law and competent authority.
Open technical baseline oversight shall include review of:
a) reference architectures;
b) interoperability profiles;
c) technical profiles;
d) schemas;
e) APIs;
f) SDKs;
g) metadata structures;
h) evidence requirements;
i) validation requirements;
j) verification requirements;
k) public-safe publication requirements;
l) data governance requirements;
m) AI governance requirements;
n) cybersecurity requirements;
o) privacy requirements;
p) secure compute requirements;
q) observability requirements;
r) proof receipt requirements;
s) dashboard requirements;
t) repository requirements;
u) public authority learning requirements;
v) safeguards requirements; and
w) correction requirements.
The Board shall ensure that open technical baselines do not become standards authority, protocol authority, certification authority, procurement mandate, provider preference, public authority decision, finance-readiness determination, recognition, or enterprise execution control by implication.
Where a baseline is used by GRF, GRA, Nexus Standards, Nexus Network, public authorities, consortiums, national companies, Project SPVs, providers, sponsors, hosts, universities, laboratories, or communities, the Corporation shall preserve limitation language, role separation, public-safe claims discipline, interface records, and correction paths.
120.15 Secure Release and Repository Oversight. The Board shall oversee secure release and repository discipline and shall ensure that the Corporation’s repositories, software releases, technical baselines, datasets, models, documentation, public-safe reports, dashboards, maps, benchmark artifacts, proof receipts, and technical profiles are managed through secure, controlled, versioned, reviewable, and correctionable systems.
Secure release and repository oversight shall include, as applicable:
a) repository ownership records;
b) custodian records;
c) access controls;
d) maintainer records;
e) contributor records;
f) branch protection;
g) commit integrity;
h) code review;
i) dependency review;
j) license review;
k) secret scanning;
l) vulnerability scanning;
m) SBOM generation;
n) artifact signing;
o) provenance records;
p) release approval;
q) rollback controls;
r) issue tracking;
s) security advisory handling;
t) takedown handling;
u) archive controls;
v) fork and compatibility claim review; and
w) public-safe documentation.
No repository permission, maintainer role, commit right, merge right, admin right, release right, package publication, dashboard deployment, API deployment, proof receipt issuance, ledger entry, role key, or software configuration shall create governance authority unless separately authorized by this Bylaw, Board resolution, delegation, policy, or competent record.
Where repository compromise, credential exposure, dependency compromise, model compromise, dataset compromise, public-safe publication error, protected knowledge exposure, or unauthorized release occurs, the matter shall be treated as an incident and escalated under the applicable data / AI / cyber, public-safe, safeguards, legal, and correction pathways.
120.16 Public-Safe Publication Oversight. The Board shall oversee public-safe publication and shall ensure that public outputs are reviewed for accuracy, evidence support, controlled vocabulary, public authority boundary, finance boundary, certification boundary, procurement neutrality, provider neutrality, sponsor non-control, safeguards, privacy, AI, cybersecurity, protected knowledge, accessibility, civil rights, non-reliance, and correctionability.
Public-safe publication oversight shall apply to:
a) reports;
b) whitepapers;
c) public dashboards;
d) public maps;
e) datasets;
f) software documentation;
g) technical baselines;
h) public-good software releases;
i) public authority learning materials;
j) Academy materials;
k) Nexus Universe materials;
l) public-safe summaries;
m) website materials;
n) media statements;
o) social media;
p) grant materials;
q) donor and sponsorship materials;
r) provider and host acknowledgments;
s) GRF-facing and GRA-facing summaries where public;
t) proof receipts where public; and
u) repository notices.
Public-safe publication review shall ensure that outputs do not expose protected knowledge, increase harm to vulnerable communities, reveal sensitive infrastructure details, create public warning confusion, imply public authority action, invite unlawful reliance, signal finance-readiness, imply certification, imply procurement approval, imply provider preference, create sponsor control, or overstate technical certainty.
Where publication risk cannot be cured through limitation language, redaction, aggregation, access restriction, public-safe framing, correction pathways, or re-scoping, the publication shall be held, restricted, withdrawn, quarantined, or abandoned.
120.17 Technical Asset Anti-Enclosure Oversight. The Board shall oversee anti-enclosure discipline for public-good technical assets and shall ensure that public-good software, open technical baselines, schemas, APIs, SDKs, dashboards, datasets, methods, ontologies, test harnesses, benchmark libraries, reference architectures, public-safe tools, and other technical assets stewarded by the Corporation are not captured, privatized, enclosed, misappropriated, monopolized, sponsor-controlled, provider-controlled, or converted into exclusive enterprise advantage contrary to the Corporation’s public-benefit purpose.
Technical asset anti-enclosure oversight shall include review of:
a) licensing models;
b) contributor terms;
c) assignment or license-back structures;
d) public-good license conditions;
e) restricted-use conditions;
f) patent and defensive publication strategy;
g) standards-essential claims;
h) repository governance;
i) fork governance;
j) compatibility claim governance;
k) sponsor and provider influence;
l) public authority dependence;
m) national company and Project SPV interfaces;
n) commercial reuse boundaries;
o) export-control and sanctions constraints;
p) controlled technology restrictions;
q) protected knowledge restrictions;
r) data rights and privacy restrictions; and
s) correction, takedown, deprecation, retirement, and archive pathways.
The Board shall ensure that anti-enclosure does not mean uncontrolled release. Public-good technical assets may be restricted, delayed, redacted, access-controlled, dual-licensed, withheld, or segmented where required by law, cybersecurity, privacy, protected knowledge, public safety, export-control, sanctions, controlled technology, public authority confidentiality, or community safeguards.
No sponsor, provider, host, donor, funder, investor, insurer, lender, national company, Project SPV, public authority, university, laboratory, or enterprise actor shall obtain exclusive control over a public-good technical asset unless the Board determines, records, and lawfully limits the arrangement in a manner consistent with public-benefit purpose, nonprofit character, anti-capture controls, and this Bylaw.
120.18 Research, Evidence, Methods, and Technical Asset Oversight Records. The Corporation shall maintain Research, Evidence, Methods, and Technical Asset Oversight Records sufficient to demonstrate that research, evidence, methods, technical truth, public-good software, open technical baselines, public-safe publications, and technical assets have been governed lawfully, ethically, securely, independently, publicly safely, and correctionably.
Such records shall include, as applicable:
a) research agenda records;
b) research approval records;
c) research ethics records;
d) human-subjects or equivalent review records;
e) community review records;
f) Tribal and Indigenous protocol records;
g) protected knowledge review records;
h) evidence intake records;
i) source-lineage records;
j) provenance records;
k) custody records;
l) data-to-evidence transformation records;
m) confidence records;
n) uncertainty records;
o) disputed evidence records;
p) correction records;
q) method register records;
r) method version records;
s) validation records;
t) verification records;
u) observability method records;
v) ontology and controlled vocabulary records;
w) Truth Engine method records;
x) verifiable compute records;
y) model register records;
z) dataset card, model card, system card, benchmark card, and evaluation harness records;
aa) inference records;
bb) compute workload records;
cc) public-good software records;
dd) technical asset register records;
ee) repository records;
ff) release records;
gg) SBOM records;
hh) vulnerability records;
ii) license records;
jj) IP chain-of-title records;
kk) contributor records;
ll) secure release records;
mm) public-safe publication records;
nn) dashboard and map review records;
oo) proof receipt records;
pp) GRF-facing input records;
qq) GRA-facing technical input records;
rr) Nexus Docket and Grid support records;
ss) Nexus Observatory support records;
tt) Nexus Standards support records;
uu) public authority learning records;
vv) data / AI / cyber review records;
ww) privacy review records;
xx) civil rights and accessibility review records;
yy) safeguards records;
zz) sponsor non-control records;
aaa) provider-neutrality records;
bbb) conflict and recusal records;
ccc) legal, compliance, sanctions, export-control, controlled-technology, competition, and professional-boundary review records;
ddd) hold, quarantine, restriction, re-scope, correction, supersession, withdrawal, retraction, takedown, deprecation, retirement, archive, and public clarification records; and
eee) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that the Corporation’s research, evidence, methods, technical truth, software, baselines, and technical assets are public-good instruments only when they remain lawful, ethical, independent, secure, transparent, bounded, public-safe, anti-capture, validity-by-record compliant, and correctionable. The Corporation may build, steward, publish, and support technical systems of high public value, but those systems shall not become hidden authority, unreviewed truth, automated governance, public warning, emergency command, finance-readiness, certification, procurement approval, recognition, provider preference, sponsor control, or enterprise execution.
Section 121. Oversight of Data, AI, Cybersecurity, Privacy, Civil Rights, Accessibility, Community Safeguards, and Protected Knowledge
121.1 Data Governance Oversight. The Board shall oversee the Corporation’s data governance function and shall ensure that all data collected, received, generated, derived, transformed, modeled, stored, accessed, analyzed, shared, published, licensed, deleted, archived, or otherwise processed by or for the Corporation is governed in a manner consistent with applicable law, the Articles or Certificate, this Bylaw, Board-approved policies, nonprofit and public-benefit purposes, tax-exempt or tax-exempt-compatible obligations, public-safe publication discipline, data minimization, purpose limitation, role separation, non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, validity-by-record, correctionability, and the Corporation’s public-good technical institution character.
Data governance oversight shall apply to all data systems, records, repositories, dashboards, maps, models, technical baselines, software tools, controlled rooms, clean rooms, evidence rooms, data rooms, no-download rooms, public authority rooms, AI systems, inference records, compute workload records, observability environments, Nexus Observatory interfaces, Nexus Truth Engine methods, Nexus Docket support, Nexus Grid support, GRF-facing inputs, GRA-facing technical inputs, public authority learning materials, public-safe publications, and public-good software assets.
The Board shall ensure that data governance controls address, without limitation:
a) lawful basis, authority, source, provenance, consent where required, collection purpose, use purpose, data minimization, accuracy, retention, deletion, archival, access class, publication class, safeguards class, and correction pathway;
b) personal information, rights-bearing data, health-sensitive data, public authority data, cyber-sensitive data, infrastructure-sensitive data, community-protected data, Tribal and Indigenous data, local and territorial knowledge, cultural and environmental knowledge, protected knowledge, confidential business information, and controlled technical information;
c) data intake, data contribution, data licensing, data sharing, data enrichment, data linkage, data fusion, data cleaning, data transformation, data labeling, data annotation, data storage, data transfer, data publication, and data destruction;
d) data used for AI training, fine-tuning, retrieval, embedding, evaluation, benchmarking, inference, agentic workflows, digital twins, dashboards, maps, proof receipts, sensor fusion, AI-RAN signal interpretation, O-RAN signal interpretation, DePIN validation, DLT validation, blockchain reference analysis, cyber telemetry, geospatial analysis, and Earth observation analysis;
e) public authority data contribution, public authority reference, public records sensitivity, FOIA or state public-records sensitivity where applicable, public-sector confidentiality, public-safety sensitivity, emergency-management sensitivity, regulatory sensitivity, procurement sensitivity, and public finance reader sensitivity;
f) sponsor, donor, funder, provider, host, university, laboratory, community, Indigenous, public authority, national company, Project SPV, and enterprise actor data contributions; and
g) records sufficient to demonstrate that data has not been used to create unauthorized public authority action, public warning, emergency command, recognition, finance-readiness, insurance-readiness, certification, procurement approval, provider preference, sponsor control, rating, investment recommendation, operational instruction, or enterprise execution.
No data holding, data access, data room, public authority contribution, dashboard, map, model, signal, ledger entry, proof receipt, evidence pack, technical baseline, repository, or public-safe output shall create institutional authority beyond the lawful authority recorded for that data and its approved use.
121.2 Privacy Oversight. The Board shall oversee privacy and shall ensure that the Corporation protects personal information, rights-bearing data, identifiable data, pseudonymous data, inferred personal data, sensitive data, and privacy-relevant metadata in accordance with applicable law, ethical duties, public-benefit purpose, data minimization, safeguards, and public trust.
Privacy oversight shall include, as applicable:
a) privacy impact review;
b) data protection impact review;
c) lawful collection review;
d) consent and notice review;
e) data minimization review;
f) purpose limitation review;
g) use limitation review;
h) de-identification review;
i) pseudonymization review;
j) aggregation review;
k) redaction review;
l) re-identification risk review;
m) retention and deletion review;
n) access-control review;
o) cross-border transfer review;
p) vendor, processor, subprocessor, cloud, AI, repository, and compute environment review;
q) incident, breach, and notification review;
r) public-safe publication review; and
s) privacy records.
Privacy oversight shall apply to participants, members where applicable, directors, officers, employees, contractors, fellows, advisors, volunteers, contributors, public authority participants, community participants, Tribal and Indigenous participants, students, research participants, controlled-room participants, data subjects, complainants, whistleblowers, donors, sponsors, funders, hosts, providers, and other persons whose information is processed by or for the Corporation.
The Board shall ensure that privacy is not waived by participation, public-good purpose, technical contribution, public authority relevance, sponsor support, repository access, dashboard use, public-safe reporting, or Nexus interface. Privacy shall be preserved unless a lawful, recorded, proportionate, and safeguarded basis authorizes a different treatment.
121.3 Rights-Bearing Data Oversight. The Board shall oversee rights-bearing data and shall ensure that data capable of affecting persons, communities, public benefits, rights, services, reputation, safety, exposure, access, opportunity, mobility, public authority treatment, or economic position is treated with heightened care.
Rights-bearing data oversight shall apply to data concerning, without limitation:
a) identity, residence, location, employment, education, income, benefits, health, disability, age, family status, immigration-sensitive context, language, accessibility needs, civil rights characteristics, community affiliation, Tribal or Indigenous affiliation where provided or inferred, and participation in protected or sensitive activities;
b) community exposure, environmental exposure, climate exposure, disaster exposure, infrastructure exposure, public health exposure, cyber exposure, surveillance exposure, telecom exposure, energy insecurity, water insecurity, food insecurity, mobility constraints, public safety context, and service vulnerability;
c) public authority interactions, public authority services, emergency management participation, public health participation, public safety participation, infrastructure operations, regulatory matters, public finance reader contexts, procurement contexts, grant contexts, and public records contexts;
d) AI-generated classifications, risk scores, maturity inputs, readiness inputs, confidence scores, uncertainty notes, automated labels, geospatial layers, dashboards, maps, digital twins, sensor signals, cyber telemetry, observability records, and proof receipts; and
e) complaints, grievances, remedy requests, non-consent, withdrawal requests, correction requests, whistleblowing, dissent, protected participation, and retaliation concerns.
The Board shall require heightened review before rights-bearing data is used for public-facing outputs, dashboards, maps, automated scoring, AI inference, controlled-room materials, public authority learning, GRF-facing inputs, GRA-facing technical inputs, Nexus Docket support, Nexus Grid support, public-safe reports, or technical baselines.
No rights-bearing data shall be used in a manner that produces discrimination, retaliation, exclusion, stigmatization, surveillance harm, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, provider preference, sponsor control, community exposure, or protected knowledge extraction.
121.4 Public Authority Data Oversight. The Board shall oversee public authority data and shall ensure that data received from, generated with, referenced by, or relevant to federal, state, territorial, District of Columbia, Tribal, Indigenous government, local, county, municipal, metropolitan, port, utility, public health, emergency management, public safety, public works, water, energy, food, telecom, cyber, infrastructure, environmental, public finance, procurement, regulatory, or other public authority actors is handled with lawful capacity classification, public authority boundary discipline, confidentiality, public-safe limitation, and record support.
Public authority data oversight shall include review of:
a) source authority;
b) official-capacity status;
c) observer status;
d) regulator-listening status;
e) public finance reader status;
f) emergency-management participant status;
g) public infrastructure operator status;
h) public authority data contribution status;
i) public authority reference status;
j) public records sensitivity;
k) open-records, FOIA, sunshine, open-meetings, procurement, grant, ethics, lobbying, political activity, and public confidentiality constraints where applicable;
l) emergency-management, public health, public safety, infrastructure, cyber, and public security sensitivity;
m) data sharing instrument;
n) use limitation;
o) publication limitation;
p) retention and deletion requirements;
q) re-use restrictions;
r) cross-border restrictions; and
s) correction and notice pathways.
The Board shall ensure that public authority data does not convert the Corporation into a public authority, public records custodian for governmental purposes except where lawfully applicable, emergency command body, public warning authority, regulator, procurement authority, public finance authority, or official decision-maker.
Public authority data may support learning, evidence review, methods development, public-safe reporting literacy, observability methods, technical baselines, and public-good software only within recorded limits. No public authority data contribution shall imply official adoption, sovereign approval, public funding commitment, procurement approval, regulatory approval, emergency command, public warning, public-private partnership, or public authority decision.
121.5 Health-Sensitive Data Oversight. The Board shall oversee health-sensitive data and shall ensure that health-related, public health-related, epidemiological, biomedical, behavioral, disability-related, mental health-related, environmental health-related, occupational health-related, emergency health-related, biosecurity-related, and other health-sensitive data is handled under heightened legal, ethical, privacy, security, public-safe, and safeguards controls.
Health-sensitive data oversight shall include, as applicable:
a) health privacy law review;
b) human-subjects or equivalent research ethics review;
c) public health authority interface review;
d) public health emergency boundary review;
e) consent, waiver, authorization, or public-health basis review where applicable;
f) de-identification, aggregation, redaction, and re-identification risk review;
g) youth, vulnerable population, disability, civil rights, accessibility, and non-discrimination review;
h) community and protected knowledge review;
i) biosecurity, dual-use, public safety, and controlled technology review;
j) AI-use and model-output review;
k) public-safe mapping review;
l) publication review;
m) incident and breach review; and
n) health-sensitive data records.
No health-sensitive data output shall be represented as medical advice, clinical diagnosis, public health order, public warning, emergency command, treatment recommendation, regulatory approval, insurance-readiness determination, underwriting basis, rating, public authority decision, or professional opinion unless separately and lawfully authorized by competent professionals or public authorities outside the Corporation’s non-executing role.
Where health-sensitive data may expose persons, communities, facilities, infrastructure, protected knowledge, public health response capacity, or vulnerable populations, the Corporation shall restrict, aggregate, redact, quarantine, withhold, or re-scope the output unless publication is lawful, proportionate, public-safe, and recorded.
121.6 Cyber-Sensitive and Infrastructure-Sensitive Data Oversight. The Board shall oversee cyber-sensitive and infrastructure-sensitive data and shall ensure that information capable of exposing vulnerabilities, attack paths, system weaknesses, credentials, keys, tokens, configurations, operational dependencies, facility details, network topology, cyber telemetry, infrastructure status, or mission-critical system risk is handled under heightened controls.
Cyber-sensitive and infrastructure-sensitive data oversight shall apply to, without limitation:
a) cybersecurity incidents;
b) vulnerability reports;
c) penetration test materials;
d) threat intelligence;
e) malware indicators;
f) exploit information;
g) credentials, keys, tokens, secrets, certificates, and identity data;
h) system architecture diagrams;
i) network topology;
j) cloud and compute configurations;
k) repository security information;
l) AI system security information;
m) model security information;
n) data room security information;
o) controlled-room security information;
p) public authority cyber information;
q) telecom, energy, water, food, port, transport, health, emergency management, public safety, public works, utility, and other critical infrastructure information;
r) AI-RAN, O-RAN, DePIN, DLT, blockchain, sensor, edge compute, geospatial, Earth observation, digital twin, and observability system security information; and
s) degraded-mode awareness information.
The Board shall ensure that such data is classified, access-controlled, need-to-know limited, logged, encrypted where appropriate, retained only as necessary, restricted from unapproved AI use, restricted from public release unless public-safe, and subject to incident response and correction pathways.
No cyber-sensitive or infrastructure-sensitive data shall be published, shared, placed in a public repository, included in a public dashboard, exposed through an API, inserted into an AI system, or referenced in public-safe materials where doing so would materially increase risk of cyber harm, infrastructure harm, public safety harm, community harm, public authority confusion, or malicious misuse.
121.7 AI Governance Oversight. The Board shall oversee AI governance and shall ensure that AI systems, AI-assisted workflows, model outputs, inference outputs, agentic systems, automated classifications, retrieval systems, embedding systems, evaluation systems, benchmark systems, data labeling tools, public-safe drafting tools, dashboards, digital twins, and AI-enabled observability systems used by or for the Corporation are governed, documented, secure, bounded, auditable, human-reviewable, public-safe, and correctionable.
AI governance oversight shall include, as applicable:
a) AI system intake review;
b) model register review;
c) dataset review;
d) training, fine-tuning, retrieval, embedding, prompt, inference, and model-improvement controls;
e) evaluation and benchmark review;
f) bias, discrimination, accessibility, civil rights, and disparate impact review;
g) privacy and data protection review;
h) cybersecurity and model security review;
i) protected knowledge and community safeguards review;
j) public authority boundary review;
k) finance, certification, procurement, recognition, rating, and professional-boundary review;
l) agentic AI control review;
m) human review requirements;
n) audit logging;
o) output limitation language;
p) incident response; and
q) AI correction records.
The Board shall ensure that AI systems are not used to bypass Board authority, officer delegation, legal review, research ethics review, safeguards review, public authority review, finance-boundary review, publication review, controlled vocabulary, repository discipline, or correction pathways.
No AI output shall be treated as official institutional truth, final evidence, legal advice, professional advice, public authority decision, emergency command, public warning, recognition, finance-readiness, insurance-readiness, certification, procurement approval, rating, provider approval, sponsor entitlement, or operational instruction without competent human review, lawful authority, and record support.
121.8 Model Register Oversight. The Board shall oversee the model register and shall ensure that material AI models, statistical models, simulation models, digital twin models, risk models, classification models, benchmark models, inference models, retrieval models, agentic models, foundation models, fine-tuned models, third-party models, open-source models, proprietary models, and internally developed models used by or for the Corporation are recorded where required.
The model register shall identify, as applicable:
a) model name;
b) model owner or provider;
c) model version;
d) model type;
e) intended use;
f) prohibited use;
g) deployment environment;
h) access class;
i) publication class;
j) data inputs;
k) training or fine-tuning status;
l) retrieval or embedding systems;
m) model card or equivalent documentation;
n) evaluation results;
o) benchmark results;
p) known limitations;
q) bias and civil rights review;
r) privacy review;
s) cybersecurity review;
t) safeguards review;
u) public authority boundary review;
v) finance, certification, procurement, rating, recognition, and professional-boundary review;
w) human review requirements;
x) incident history;
y) correction history; and
z) retirement, suspension, or archive status.
No unregistered model shall be used for material outputs requiring registration under policy. No model register entry shall imply certification, public authority approval, procurement approval, finance-readiness, insurance-readiness, recognition, rating, provider approval, or operational authorization.
121.9 Inference Record Oversight. The Board shall oversee inference record discipline and shall ensure that material AI outputs, model outputs, automated classifications, agentic actions, public-safe summaries, research outputs, evidence transformations, dashboard outputs, map outputs, digital twin outputs, proof receipt outputs, and Nexus-facing outputs are supported by inference records where required.
Inference records shall identify, as applicable:
a) model or system used;
b) model version;
c) user or process initiating the inference;
d) time and date;
e) input class;
f) data source class;
g) prompt, query, instruction, or workflow class where recordable without exposing protected information;
h) retrieval source class;
i) output class;
j) human reviewer;
k) review status;
l) confidence and uncertainty notes;
m) limitations;
n) public-safe status;
o) access class;
p) publication class;
q) correction pathway;
r) incident flag;
s) legal hold status; and
t) retention or deletion status.
Inference records shall be maintained with due regard to confidentiality, privilege, privacy, cybersecurity, protected knowledge, and public-safe handling. The Corporation shall not preserve prompts, inputs, outputs, or logs in a manner that unnecessarily increases exposure of personal information, protected knowledge, cyber-sensitive data, infrastructure-sensitive data, or public authority confidential material.
No inference record shall itself create authority. An inference record evidences that an inference occurred and may support review, audit, correction, reproducibility, or accountability; it shall not convert an AI output into a Board decision, officer approval, public authority decision, recognition, finance-readiness, certification, procurement approval, rating, or public warning.
121.10 Agentic AI Oversight. The Board shall oversee agentic AI and shall ensure that any AI system capable of taking actions, calling tools, modifying repositories, sending communications, creating records, updating dashboards, triggering workflows, accessing controlled materials, generating public outputs, or interacting with external systems is governed by explicit authority, bounded scope, human supervision, audit logs, access controls, and stop mechanisms.
Agentic AI oversight shall require, as applicable:
a) approved use case;
b) responsible owner;
c) delegated authority mapping;
d) prohibited action list;
e) access limitation;
f) tool-use limitation;
g) repository limitation;
h) data-room limitation;
i) controlled-room limitation;
j) public communication limitation;
k) public authority communication limitation;
l) finance-adjacent communication limitation;
m) sponsor, donor, funder, provider, host, or enterprise communication limitation;
n) human-in-the-loop or human-on-the-loop controls;
o) pre-action approval requirements;
p) post-action review requirements;
q) emergency stop;
r) audit logging;
s) incident response; and
t) correction and rollback pathways.
No agentic AI system shall be permitted to approve Board reserved matters, execute contracts, bind the Corporation, approve spending outside authority, issue public warnings, communicate official public authority instructions, make finance-readiness determinations, issue certifications, approve procurement, determine recognition, select providers, release controlled data, publish public-safe reports, alter official records, or override human review unless a specific lawful delegation and record expressly authorize the action within the non-execution perimeter.
The Board shall ensure that agentic convenience never becomes hidden governance.
121.11 Cybersecurity Oversight. The Board shall oversee cybersecurity and shall ensure that the Corporation maintains reasonable and appropriate administrative, technical, physical, organizational, and governance controls to protect systems, repositories, data, models, software, keys, credentials, records, communications, controlled rooms, public authority materials, protected knowledge, and public-good technical assets.
Cybersecurity oversight shall include, without limitation:
a) cybersecurity policy review;
b) risk assessment;
c) asset inventory;
d) identity and access management;
e) privileged access management;
f) multi-factor authentication where appropriate;
g) encryption where appropriate;
h) logging and monitoring;
i) vulnerability management;
j) secure development lifecycle;
k) dependency and supply-chain security;
l) SBOM discipline;
m) repository protection;
n) key, credential, token, certificate, and secret management;
o) endpoint and cloud security;
p) backup and recovery;
q) incident response;
r) breach response;
s) disaster recovery;
t) business continuity;
u) vendor and processor security;
v) security awareness training;
w) penetration testing or independent review where appropriate;
x) public authority cyber sensitivity review; and
y) cybersecurity records.
The Board shall ensure that cybersecurity controls apply to public-good software, open technical baselines, repositories, dashboards, maps, APIs, SDKs, datasets, AI systems, controlled rooms, no-download rooms, data rooms, evidence rooms, clean rooms, public authority rooms, Nexus interfaces, GRF-facing inputs, GRA-facing technical inputs, and all material digital surfaces of the Corporation.
No urgency, event deadline, grant deadline, sponsor request, provider request, publication deadline, technical milestone, public authority request, repository deadline, or Nexus interface request shall justify bypassing material cybersecurity controls.
121.12 Secure Development and Release Oversight. The Board shall oversee secure development and release and shall ensure that software, datasets, models, dashboards, maps, APIs, SDKs, schemas, technical baselines, documentation, public-safe reports, benchmark assets, proof receipts, and other technical artifacts are developed, reviewed, approved, released, corrected, deprecated, or retired under controlled procedures.
Secure development and release oversight shall include, as applicable:
a) secure design review;
b) threat modeling;
c) data protection review;
d) AI governance review;
e) privacy review;
f) public authority boundary review;
g) finance-boundary review;
h) certification and procurement boundary review;
i) safeguards review;
j) license review;
k) contributor review;
l) code review;
m) dependency review;
n) SBOM generation;
o) secret scanning;
p) vulnerability scanning;
q) artifact signing;
r) provenance records;
s) release notes;
t) public-safe limitation language;
u) rollback plans;
v) versioning;
w) deprecation;
x) takedown;
y) archive; and
z) correction records.
The Board shall ensure that technical releases are not represented as certification, conformance approval, procurement approval, provider approval, public authority adoption, finance-readiness, insurance-readiness, recognition, rating, operational instruction, public warning, or emergency command.
Where a release creates unacceptable legal, cybersecurity, privacy, protected knowledge, safeguards, public authority, finance-boundary, certification-boundary, procurement, sponsor-control, provider-neutrality, or public-safe risk, the release shall be held, restricted, modified, withdrawn, quarantined, deprecated, or abandoned.
121.13 Business Continuity and Disaster Recovery Oversight. The Board shall oversee business continuity and disaster recovery and shall ensure that the Corporation maintains reasonable continuity plans for governance, records, repositories, data, AI systems, cybersecurity, public authority learning, controlled rooms, public-safe publications, financial administration, legal compliance, safeguards, and Nexus interfaces.
Business continuity and disaster recovery oversight shall address, as applicable:
a) continuity of Board functions;
b) continuity of officer functions;
c) continuity of committee functions;
d) continuity of secretariat functions;
e) continuity of records and registers;
f) continuity of repositories;
g) continuity of data rooms and controlled rooms;
h) continuity of evidence and method records;
i) continuity of model registers and inference records;
j) continuity of cybersecurity monitoring;
k) continuity of public-safe publication controls;
l) continuity of incident response;
m) continuity of public authority interface controls;
n) continuity of grant, donation, sponsorship, fee, and restricted fund administration;
o) continuity of safeguards and grievance pathways;
p) backup and recovery;
q) recovery time objectives;
r) recovery point objectives;
s) successor administrator arrangements where needed;
t) key-person risk;
u) vendor and cloud continuity;
v) communications continuity;
w) emergency delegation; and
x) continuity records.
Continuity measures shall not authorize prohibited functions. No business continuity or disaster recovery plan shall convert the Corporation into an emergency command body, public warning authority, public authority substitute, finance executor, procurement authority, certification body, provider, operator, national company, Project SPV, or enterprise execution vehicle.
121.14 Civil Rights and Non-Discrimination Oversight. The Board shall oversee civil rights and non-discrimination and shall ensure that the Corporation’s governance, programs, participation structures, research, publications, datasets, AI systems, dashboards, maps, public authority learning, controlled rooms, technical baselines, public-good software, employment practices, contractor practices, volunteer practices, fellowships, Academy activities, public-safe reports, and Nexus interfaces respect applicable civil rights, non-discrimination, accessibility, and equal participation principles.
Civil rights and non-discrimination oversight shall include review of:
a) discriminatory eligibility rules;
b) discriminatory access barriers;
c) discriminatory data use;
d) discriminatory AI outputs;
e) disparate impact risks;
f) exclusionary design;
g) language access concerns;
h) disability access concerns;
i) geographic exclusion;
j) state, territorial, Tribal, local, remote, rural, border, island, Arctic, and underserved community access concerns;
k) public-safe mapping harms;
l) stigmatizing classifications;
m) retaliation;
n) harassment;
o) viewpoint suppression inconsistent with lawful public-benefit governance;
p) protected participation interference;
q) grievance handling; and
r) remedy pathways.
The Board shall ensure that civil rights review applies not only to formal employment or participation decisions, but also to technical systems, public maps, dashboards, AI classifications, evidence categories, maturity inputs, readiness inputs, observability outputs, publication language, public authority learning materials, and public-facing claims.
No public-good purpose shall justify discriminatory design, inaccessible process, retaliation, unsafe exposure, or community harm.
121.15 Accessibility Oversight. The Board shall oversee accessibility and shall ensure that the Corporation’s governance instruments, notices, meetings, participation pathways, public materials, publications, dashboards, maps, websites, repositories, Academy materials, public authority learning materials, controlled-room processes where feasible, grievance pathways, and public-safe outputs are designed and implemented with reasonable accessibility appropriate to their purpose, audience, risk, and legal requirements.
Accessibility oversight shall include, as applicable:
a) accessible governance documents;
b) accessible notices;
c) accessible meeting practices;
d) accessible electronic participation;
e) accessible websites and digital surfaces;
f) accessible reports and publications;
g) accessible dashboards and visualizations;
h) accessible maps with appropriate alternatives;
i) accessible training and Academy materials;
j) accessible forms and intake processes;
k) accessible grievance and remedy pathways;
l) language access review;
m) plain-language summaries where approved;
n) assistive technology compatibility review;
o) captioning, transcripts, alternative text, and document structure review where appropriate;
p) accommodation processes; and
q) accessibility records.
Accessibility summaries, translations, plain-language versions, alternative formats, and explanatory materials shall not replace the authoritative legal text unless expressly adopted as authoritative under this Bylaw and applicable law. No accessibility aid may soften non-execution boundaries, overstate authority, create public reliance, imply certification, imply finance-readiness, imply public authority action, or omit material limitation language.
121.16 Tribal, Indigenous, Local, Territorial, Cultural, Environmental, Community-Protected, and Protected Knowledge Oversight. The Board shall oversee Tribal, Indigenous, local, territorial, cultural, environmental, community-protected, and protected knowledge and shall ensure that such knowledge is not extracted, exposed, appropriated, commercialized, modeled, mapped, published, translated, embedded, trained on, licensed, or converted into technical assets without lawful authority, ethical review, safeguards, and appropriate respect for applicable protocols.
Protected knowledge oversight shall apply to:
a) Tribal knowledge;
b) Indigenous knowledge;
c) Indigenous data;
d) local knowledge;
e) territorial knowledge;
f) cultural knowledge;
g) sacred knowledge;
h) environmental knowledge;
i) biodiversity knowledge;
j) community safety knowledge;
k) place-based knowledge;
l) disaster memory;
m) public health community knowledge;
n) infrastructure vulnerability knowledge;
o) community geospatial knowledge;
p) oral histories where used;
q) community submissions;
r) protected maps;
s) protected datasets;
t) protected images or observations;
u) AI embeddings of protected knowledge;
v) model outputs derived from protected knowledge; and
w) technical baselines or software features derived from protected knowledge.
The Board shall require appropriate review of consent, non-consent, attribution, anonymity, withdrawal, restriction, redaction, aggregation, localization, public-safe mapping, intellectual property, data rights, benefit-sharing where appropriate, governance protocol, and correction pathways.
No protected knowledge shall be treated as free technical input merely because it is useful to evidence, observability, AI, dashboards, public authority learning, resilience infrastructure, climate, nature, disaster, biosecurity, geospatial, Earth observation, digital twin, Nexus Observatory, Nexus Grid, Nexus Docket, GRF-facing, or GRA-facing work.
Where protected knowledge risk cannot be cured, the Corporation shall hold, restrict, quarantine, withdraw, delete where lawful, seal, re-scope, refer, or abandon the activity.
121.17 Public-Safe Mapping Oversight. The Board shall oversee public-safe mapping and shall ensure that maps, geospatial layers, dashboards, location datasets, remote sensing products, Earth observation outputs, digital twins, sensor outputs, infrastructure maps, community exposure maps, risk maps, public health maps, climate maps, disaster maps, biodiversity maps, cyber-physical maps, AI-RAN maps, O-RAN maps, DePIN maps, and Nexus Observatory maps are reviewed for harm risk before public or controlled release.
Public-safe mapping oversight shall include review of:
a) location precision;
b) re-identification risk;
c) community exposure;
d) household exposure;
e) facility exposure;
f) infrastructure exposure;
g) critical asset exposure;
h) protected site exposure;
i) sacred site exposure;
j) sensitive biodiversity exposure;
k) public safety exposure;
l) cyber and physical security exposure;
m) law enforcement or surveillance misuse risk;
n) public authority confusion risk;
o) public warning confusion risk;
p) emergency command confusion risk;
q) finance, insurance, lending, rating, public finance, procurement, certification, recognition, and provider-standing misinterpretation risk;
r) sponsor or provider misuse risk;
s) stigmatizing or discriminatory presentation risk;
t) color, symbol, label, score, alert, and legend interpretation risk;
u) access class;
v) publication class; and
w) correction pathway.
The Board shall require aggregation, generalization, fuzzing, redaction, delay, access restriction, controlled-room handling, no-download handling, limitation language, or withholding where public-safe mapping risk requires it.
No map, dashboard, geospatial layer, observability product, digital twin, or public-safe visualization shall be represented as an official public warning, evacuation notice, emergency command, public authority decision, regulatory determination, finance-readiness determination, insurance-readiness determination, certification, procurement approval, recognition, provider rating, or operational instruction.
121.18 Grievance, Remedy, Protected Participation, Whistleblowing, and Non-Retaliation Oversight. The Board shall oversee grievance, remedy, protected participation, whistleblowing, dissent protection, confidential reporting, and non-retaliation systems and shall ensure that persons and communities may raise concerns regarding law, ethics, research integrity, data misuse, AI misuse, cyber risk, privacy, civil rights, accessibility, protected knowledge, public-safe mapping, sponsor control, provider preference, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, retaliation, harassment, or other misconduct.
Such oversight shall include, as applicable:
a) grievance intake;
b) confidential reporting;
c) anonymous reporting where lawful and feasible;
d) whistleblower protection;
e) protected participation classification;
f) retaliation prohibition;
g) retaliation response;
h) harassment response;
i) conflict-sensitive routing;
j) independent review where required;
k) safeguards review;
l) community review where appropriate;
m) Tribal or Indigenous protocol review where appropriate;
n) interim protection;
o) access restriction;
p) correction;
q) remedy;
r) appeal or reconsideration where approved;
s) closure records; and
t) follow-up review.
The Corporation shall not condition participation, access, funding, publication, technical contribution, public authority learning, controlled-room access, Academy access, fellowship status, contributor status, membership where applicable, support, or public acknowledgment on waiver of good-faith grievance, correction, protected participation, or lawful whistleblowing rights.
No person shall retaliate against a participant, member, director, officer, employee, contractor, fellow, advisor, volunteer, contributor, public authority participant, community participant, Tribal or Indigenous participant, donor, sponsor, host, provider, or other actor for good-faith reporting, dissent, refusal to participate in misconduct, request for correction, request for withdrawal, assertion of safeguards, or protected knowledge concern.
121.19 Stop-the-Line Oversight. The Board shall oversee stop-the-line authority and shall ensure that the Corporation maintains a clear mechanism to pause, hold, quarantine, restrict, freeze, withdraw, re-scope, or escalate activities where serious risk arises.
Stop-the-line authority may be triggered by, without limitation:
a) suspected legal violation;
b) suspected fiduciary breach;
c) suspected tax or nonprofit compliance concern;
d) suspected private inurement or impermissible private benefit;
e) public authority confusion;
f) public warning confusion;
g) emergency command confusion;
h) finance, securities, investment adviser, broker-dealer, finder, banking, lending, insurance, underwriting, rating, public finance, procurement, certification, recognition, or provider-preference boundary risk;
i) sponsor, donor, funder, provider, host, investor, national company, Project SPV, or enterprise capture risk;
j) data breach;
k) privacy concern;
l) AI incident;
m) agentic AI concern;
n) cybersecurity incident;
o) repository compromise;
p) model, dataset, dashboard, map, proof receipt, or technical asset compromise;
q) research ethics concern;
r) evidence integrity concern;
s) protected knowledge concern;
t) civil rights concern;
u) accessibility concern;
v) community harm concern;
w) retaliation concern;
x) public-safe publication concern; and
y) uncontrolled public claim.
Stop-the-line action may be taken by the Board, a committee, an officer, counsel, compliance function, safeguards function, cybersecurity function, data / AI governance function, public-safe publication function, or other person authorized by policy, delegation, or emergency procedure.
A stop-the-line action shall be recorded, reviewed, time-classified, assigned to a responsible owner, escalated where required, and resolved through hold, quarantine, correction, supersession, withdrawal, retraction, takedown, restriction, redesign, externalization, referral, termination, or documented release from hold.
No person shall bypass a stop-the-line action through informal communication, public statement, repository fork, AI summary, slide deck, uncontrolled copy, public authority communication, sponsor communication, provider communication, capital-reader communication, media communication, or Nexus interface.
121.20 Safeguards Oversight Records. The Corporation shall maintain Safeguards Oversight Records sufficient to demonstrate that data governance, privacy, rights-bearing data, public authority data, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, AI governance, model registers, inference records, agentic AI, cybersecurity, secure development, release controls, business continuity, disaster recovery, civil rights, accessibility, protected knowledge, public-safe mapping, grievance, remedy, whistleblowing, non-retaliation, and stop-the-line systems have been overseen, classified, enforced, corrected, and preserved.
Safeguards Oversight Records shall include, as applicable:
a) data governance records;
b) privacy records;
c) data protection impact records;
d) rights-bearing data records;
e) public authority data records;
f) health-sensitive data records;
g) cyber-sensitive data records;
h) infrastructure-sensitive data records;
i) community-protected data records;
j) Tribal and Indigenous data records;
k) protected knowledge records;
l) data intake records;
m) data contribution records;
n) data licensing records;
o) data sharing records;
p) data transfer records;
q) data access records;
r) data retention records;
s) deletion and secure disposal records;
t) AI governance records;
u) model register records;
v) dataset card records;
w) model card records;
x) system card records;
y) benchmark card records;
z) evaluation harness records;
aa) inference records;
bb) compute workload records;
cc) agentic AI approval and audit records;
dd) prompt, retrieval, embedding, fine-tuning, training, and model-improvement restriction records;
ee) cybersecurity records;
ff) identity and access records;
gg) credential, key, token, certificate, and secret management records;
hh) vulnerability records;
ii) SBOM records;
jj) secure release records;
kk) repository security records;
ll) incident response records;
mm) breach response records;
nn) backup, disaster recovery, and business continuity records;
oo) civil rights review records;
pp) accessibility records;
qq) accommodation records;
rr) public-safe mapping records;
ss) geospatial review records;
tt) community safeguard records;
uu) Tribal and Indigenous protocol records;
vv) local, territorial, cultural, environmental, and protected knowledge records;
ww) consent, non-consent, attribution, withdrawal, restriction, grievance, remedy, correction, and non-retaliation records;
xx) whistleblowing and confidential reporting records;
yy) stop-the-line records;
zz) holds, quarantines, restrictions, access freezes, publication freezes, implementation freezes, technical isolations, controlled-room lockdowns, corrections, supersessions, withdrawals, retractions, takedowns, deletions, archives, referrals, and terminations;
aaa) Board, committee, officer, counsel, compliance, data / AI / cyber, privacy, safeguards, public authority, public-safe publication, and legal review records;
bbb) conflict and recusal records;
ccc) sponsor non-control records;
ddd) provider-neutrality records;
eee) public authority boundary records;
fff) finance-boundary records;
ggg) certification and procurement boundary records;
hhh) correctionability records; and
iii) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that data, AI, cybersecurity, privacy, civil rights, accessibility, community safeguards, and protected knowledge are not peripheral compliance matters. They are constitutional controls within the Corporation’s public-good role. The Corporation may steward evidence, methods, observability, ontology, technical truth, public-good software, open technical baselines, public authority learning, and Nexus-compatible technical systems only where those activities preserve dignity, legality, security, privacy, non-discrimination, accessibility, community safety, protected knowledge, public trust, validity-by-record, and correctionability. No data system, AI system, cyber system, dashboard, map, model, proof receipt, technical asset, public authority room, controlled room, repository, or Nexus interface may be used to weaken those controls.
Section 122. Board Meeting Security, Confidentiality, Privilege, and Information Governance
122.1 Board Confidentiality Duty. Each Director shall owe a continuing duty of confidentiality with respect to Board materials, Board deliberations, Board minutes before approval, draft resolutions, executive-session materials, in camera materials, legal materials, privileged communications, work product, financial materials, personnel materials, risk materials, incident materials, investigation materials, committee reports, officer reports, controlled-room materials, public authority materials, data / AI / cyber materials, protected knowledge, sponsor and provider information, research materials, unpublished technical assets, repository materials, and any other information designated or reasonably understood to be confidential.
The confidentiality duty shall apply before, during, and after service as a Director and shall extend to all forms of information, including oral communications, written materials, electronic records, messages, repositories, datasets, dashboards, maps, recordings, transcripts, models, AI outputs, inference records, compute records, proof receipts, privileged memoranda, legal opinions, committee papers, public authority notes, controlled-room exhibits, no-download-room materials, and Board portal materials.
A Director shall not disclose, copy, forward, publish, summarize, upload, train, embed, translate, reproduce, screenshot, record, scrape, export, transmit, or otherwise use confidential Board information except as authorized by law, the Articles or Certificate, this Bylaw, Board resolution, applicable policy, delegated authority, legal process, counsel instruction, or a competent record.
The confidentiality duty shall not be used to suppress lawful whistleblowing, protected participation, correction requests, legal reporting, regulatory reporting, conflict disclosure, counsel communications, safeguards escalation, non-retaliation claims, civil-rights claims, protected knowledge concerns, or other protected reporting pathways recognized by law or this Bylaw.
122.2 Attorney-Client Privilege Protection. The Board shall protect attorney-client privilege for communications with counsel, legal advice, legal strategy, legal risk assessments, regulatory-perimeter analysis, tax advice, nonprofit compliance advice, governance advice, public authority boundary advice, finance-boundary advice, procurement-boundary advice, certification-boundary advice, data / AI / cyber advice, privacy advice, sanctions advice, export-control advice, competition advice, employment advice, research ethics advice, safeguards advice, and litigation or investigation advice.
Privileged materials shall be marked, circulated, stored, discussed, and retained in a manner appropriate to preserve privilege. Access shall be limited to persons whose role, authority, and need to know are recorded or reasonably established.
No Director, officer, committee member, advisor, staff member, contractor, fellow, volunteer, contributor, sponsor, provider, host, public authority participant, university participant, laboratory participant, community participant, or enterprise actor shall waive privilege, disclose privileged materials, or communicate privileged advice outside the approved privileged circle unless authorized by the Board, counsel, or other competent authority.
Where privilege status is uncertain, the material shall be treated as privileged pending counsel review. No public-good urgency, public authority request, sponsor request, provider request, publication deadline, fundraising need, technical milestone, media inquiry, grant deadline, or Nexus interface need shall justify unauthorized privilege waiver.
122.3 Work Product Protection. The Board shall protect attorney work product, investigation materials, litigation-prepared materials, regulatory-prepared materials, enforcement-response materials, risk-review materials, incident-response materials, breach-response materials, cyber-forensic materials, internal review materials, draft legal analyses, witness notes, counsel-directed technical analyses, counsel-directed data reviews, and counsel-directed AI or cyber reviews.
Work product materials shall be stored, accessed, circulated, and discussed under controlled conditions. The Board may direct that work product be segregated from ordinary business records, placed in a legal hold environment, assigned a restricted access class, or handled only through counsel-approved channels.
No work product shall be converted into ordinary public-facing material, Board summary, committee report, dashboard, AI summary, public-safe report, public authority briefing, sponsor update, provider update, donor report, repository entry, proof receipt, technical baseline, or Nexus-facing material unless counsel has approved the use and the record preserves necessary limitation language.
122.4 Public Authority Confidentiality. The Board shall protect information received from, generated with, or relating to public authorities where confidentiality, public-records sensitivity, procurement sensitivity, emergency-management sensitivity, public health sensitivity, public safety sensitivity, infrastructure sensitivity, regulatory sensitivity, public finance sensitivity, law-enforcement sensitivity, national security sensitivity, Tribal or Indigenous governance sensitivity, or other lawful public authority restriction applies.
Public authority confidentiality shall apply to federal, state, territorial, District of Columbia, Tribal, Indigenous government, local, county, municipal, metropolitan, port, utility, public health, emergency management, public safety, public works, water, energy, food, telecom, cyber, infrastructure, environmental, public finance, procurement, regulatory, and other public authority contexts.
The Board shall ensure that public authority materials are capacity-classified and that the record identifies, as applicable:
a) the public authority source;
b) official-capacity status;
c) observer status;
d) regulator-listening status;
e) public finance reader status;
f) emergency-management participant status;
g) public infrastructure operator status;
h) public authority data contribution status;
i) public authority reference status;
j) applicable confidentiality constraints;
k) public records or open-records sensitivity;
l) public-safe publication limits;
m) use limits;
n) access class;
o) retention class;
p) correction pathway; and
q) any required notice or return obligation.
No public authority material shall be disclosed, published, included in a public dashboard, placed in a repository, inserted into a public-safe report, uploaded into an AI system, shared with sponsors, shared with providers, shared with capital readers, or used in public claims unless the disclosure is lawful, authorized, public-safe, and recorded.
122.5 Cyber-Sensitive Confidentiality. The Board shall protect cyber-sensitive information, including security architecture, threat intelligence, vulnerability reports, incident materials, penetration-test results, exploit details, malware indicators, credentials, keys, tokens, secrets, certificates, identity controls, repository security materials, cloud configurations, model-security materials, API security materials, dashboard security materials, access-control records, logging records, forensic materials, and cyber response plans.
Cyber-sensitive materials shall be classified, access-controlled, encrypted where appropriate, logged, monitored, segregated where necessary, restricted from unapproved AI systems, and handled under cybersecurity policy.
The Board shall ensure that cyber-sensitive information is not disclosed in a way that increases the likelihood of unauthorized access, exploitation, system compromise, infrastructure harm, public authority harm, community harm, protected knowledge exposure, repository compromise, model compromise, public-safe publication error, or malicious misuse.
Where cyber-sensitive information is needed for Board oversight, committee oversight, counsel review, public authority learning, technical review, or incident response, the Corporation shall use restricted circulation, clean-room, controlled-room, no-download-room, redaction, aggregation, delayed disclosure, or other protective methods appropriate to the risk.
122.6 Infrastructure-Sensitive Confidentiality. The Board shall protect infrastructure-sensitive information, including information concerning critical infrastructure, public infrastructure, private infrastructure, telecommunications, energy, water, food, ports, transport, public health, emergency management, public safety, public works, utility systems, cyber-physical systems, AI-RAN systems, O-RAN systems, DePIN systems, DLT or blockchain infrastructure, sensor systems, edge compute, sovereign compute, digital twins, geospatial layers, Earth observation products, facility details, operational dependencies, degraded-mode conditions, and resilience vulnerabilities.
Infrastructure-sensitive materials shall be reviewed for public-safety, cyber, physical-security, public authority, community, protected knowledge, public-safe mapping, and operational misuse risk before disclosure.
No infrastructure-sensitive material shall be published, mapped, visualized, released through an API, placed in a public repository, summarized in public materials, included in a public-safe report, uploaded into an unapproved AI system, or shared with unauthorized persons where disclosure would materially increase harm risk.
The Board may require aggregation, redaction, fuzzing, delay, controlled-room access, no-download access, public-safe limitation language, or withholding where infrastructure sensitivity requires it.
122.7 Finance-Sensitive Confidentiality. The Board shall protect finance-sensitive information, including budgets, forecasts, financial statements before approval, cash-flow materials, restricted fund materials, grant materials, donor materials, sponsorship materials, fee schedules before approval, compensation materials, insurance materials, audit materials, risk reserves, financing-interface materials, GRA-facing technical inputs, capital-reader-room materials, public finance reader materials, proof-pack materials, diligence-translation materials, and regulated-perimeter analyses.
Finance-sensitive confidentiality shall preserve the Corporation’s nonprofit character, public-benefit purpose, anti-capture controls, sponsor non-control, provider neutrality, private benefit controls, finance-boundary discipline, securities-boundary discipline, investment-advice boundary discipline, insurance-boundary discipline, lending-boundary discipline, rating-boundary discipline, public finance boundary discipline, and procurement neutrality.
No finance-sensitive material shall be used or disclosed in a manner that implies securities offering, capital placement, investment recommendation, brokerage, finder activity, lending, underwriting, insurance placement, rating, public finance approval, finance-readiness determination, bankability determination, capital-readability determination, public procurement advantage, sponsor entitlement, donor control, provider preference, or enterprise execution by the Corporation.
122.8 Commercially Sensitive Confidentiality. The Board shall protect commercially sensitive information received from or relating to providers, vendors, contractors, sponsors, donors, funders, hosts, universities, laboratories, public authorities, national companies, Project SPVs, enterprise actors, technology developers, data contributors, software contributors, infrastructure operators, capital readers, insurers, lenders, and other third parties.
Commercially sensitive information may include trade secrets, business plans, product information, pricing information, cost information, bid information, customer information, supplier information, roadmaps, technical architectures, proprietary datasets, model information, cybersecurity information, intellectual property, licensing terms, investment-sensitive information, insurance-sensitive information, procurement-sensitive information, and commercially confidential submissions.
The Board shall ensure that commercially sensitive information is not used to create unfair advantage, collusion, market allocation, boycott, procurement steering, provider preference, sponsor control, investment signaling, private benefit, or improper public authority influence.
Where commercially sensitive information is reviewed in Board or committee settings, competition-law discipline, clean-team methods, clean-room methods, aggregation, de-identification, delayed disclosure, access restriction, recusal, and counsel review shall be used where appropriate.
122.9 Personal Information and Rights-Bearing Data Confidentiality. The Board shall protect personal information and rights-bearing data concerning directors, officers, employees, contractors, fellows, advisors, volunteers, contributors, members where applicable, supporters, subscribers, donors, sponsors, public authority participants, research participants, community participants, Tribal or Indigenous participants, students, complainants, whistleblowers, protected participants, controlled-room participants, and other persons.
Personal information and rights-bearing data shall be handled under privacy, data protection, confidentiality, civil rights, accessibility, research ethics, safeguards, and public-safe publication controls.
The Board shall require heightened care for sensitive personal information, health-related information, disability-related information, youth information, vulnerable-population information, geolocation information, employment information, identity information, immigration-sensitive context, protected participation information, grievance information, whistleblower information, retaliation concerns, and information that could affect public authority treatment, safety, reputation, services, access, opportunity, or rights.
No personal information or rights-bearing data shall be disclosed, published, mapped, modeled, uploaded into unapproved AI systems, used in public-facing materials, or shared outside authorized channels unless lawful, necessary, proportionate, public-safe, and recorded.
122.10 Tribal, Indigenous, Community-Protected, Local, Territorial, Cultural, Environmental, and Protected Knowledge Confidentiality. The Board shall protect Tribal, Indigenous, community-protected, local, territorial, cultural, environmental, and protected knowledge with heightened respect for lawful authority, consent, non-consent, attribution, anonymity, withdrawal, restriction, protocol, public-safe mapping, and do-no-harm obligations.
Protected knowledge confidentiality shall apply to knowledge, data, maps, oral histories, observations, images, documents, cultural information, environmental information, biodiversity information, sacred site information, community safety information, place-based knowledge, disaster memory, infrastructure vulnerability knowledge, health-sensitive community knowledge, protected datasets, protected geospatial layers, model embeddings, AI outputs, and technical artifacts derived from such knowledge.
The Board shall ensure that protected knowledge is not treated as ordinary data, free public-good input, open technical baseline material, public-good software material, AI training material, sponsor asset, provider asset, donor asset, publication asset, dashboard asset, or public authority learning asset without lawful and ethical review.
No protected knowledge shall be disclosed, extracted, modeled, mapped, trained on, embedded, licensed, commercialized, transferred, published, or operationalized contrary to applicable law, protocol, consent, non-consent, restriction, safeguard, or public-safe determination.
122.11 Controlled-Room Materials. The Board shall protect controlled-room materials and shall ensure that materials designated for controlled-room handling are accessed, reviewed, discussed, copied, summarized, exported, retained, corrected, returned, deleted, or archived only under approved controlled-room rules.
Controlled-room materials may include legal materials, evidence materials, public authority materials, data materials, AI materials, cyber materials, infrastructure materials, health-sensitive materials, protected knowledge, finance-sensitive materials, commercially sensitive materials, sponsor materials, provider materials, research materials, software materials, model materials, repository materials, proof receipts, dashboard materials, map materials, and Nexus interface materials.
Controlled-room handling shall include, as applicable:
a) admission approval;
b) identity verification;
c) capacity classification;
d) conflict review;
e) confidentiality acknowledgment;
f) no-download rule;
g) logging;
h) monitoring;
i) exhibit control;
j) chain-of-custody;
k) redaction controls;
l) AI-use restrictions;
m) competition controls;
n) public authority boundary controls;
o) finance-boundary controls;
p) safeguards controls;
q) access revocation;
r) closeout; and
s) return, deletion, sealing, or archive.
No Director shall remove controlled-room materials from the controlled environment unless expressly authorized by the applicable room protocol or competent record.
122.12 Data Room Materials. The Board shall protect data room materials and shall ensure that any data room established for governance, evidence, research, public authority learning, grants, sponsorship, controlled technical review, GRA-facing technical input, GRF-facing input, Nexus Docket support, Nexus Grid support, repository review, audit, legal review, or diligence-translation purposes is operated under recorded access, confidentiality, use, retention, and limitation rules.
Data room materials shall not be used as a basis for investment advice, securities solicitation, public finance approval, underwriting, insurance placement, lending approval, rating, procurement approval, certification, recognition, provider preference, public authority decision, or operational instruction by the Corporation.
A data room may support review, learning, diligence translation, evidence inspection, technical literacy, public-safe classification, or controlled collaboration only within the Corporation’s lawful non-executing role. Access to a data room shall not imply endorsement, approval, certification, finance-readiness, insurance-readiness, recognition, public authority adoption, procurement advantage, or provider status.
122.13 Research Confidentiality. The Board shall protect research confidentiality, including unpublished research, draft reports, research protocols, research participant information, human-subjects materials, ethics review materials, peer review materials, model review materials, red-team materials, preliminary findings, disputed findings, sensitive data, protected knowledge, sponsor disclosures, contributor disclosures, conflict disclosures, and correction records.
Research confidentiality shall preserve research integrity, academic independence, participant protection, privacy, safeguards, protected knowledge, publication integrity, public-safe reporting, and correctionability.
No Director shall disclose preliminary, draft, disputed, superseded, withdrawn, restricted, retracted, or unpublished research in a manner that implies finality, recognition, finance-readiness, certification, procurement approval, public authority decision, public warning, emergency command, provider status, sponsor entitlement, rating, investment suitability, or operational guidance.
Research confidentiality shall not be used to suppress necessary correction, lawful reporting, research misconduct review, ethics review, participant protection, protected knowledge restriction, public-safe withdrawal, or required legal disclosure.
122.14 Sponsor, Donor, Funder, Provider, Host, Partner, and Third-Party Confidentiality. The Board shall protect confidential information received from sponsors, donors, funders, providers, hosts, partners, vendors, contractors, universities, laboratories, public authorities, communities, Indigenous knowledge holders, civil society actors, media actors, national companies, Project SPVs, and other third parties, subject to law, this Bylaw, public-benefit purpose, anti-capture controls, public-safe obligations, and correctionability.
Third-party confidentiality shall not be used to conceal private inurement, impermissible private benefit, sponsor control, provider preference, donor control, funder control, host control, procurement steering, research manipulation, data misuse, AI misuse, cyber misconduct, protected knowledge extraction, public authority confusion, finance overclaim, certification overclaim, recognition overclaim, public warning overclaim, or other misconduct.
Where a confidentiality obligation conflicts with legal reporting, fiduciary duty, public-benefit purpose, safeguards, whistleblower protection, protected participation, correctionability, or required public-safe clarification, the matter shall be escalated to counsel, the Board, or other competent authority for lawful resolution.
122.15 Board System Security. The Board shall use secure systems for Board communications, Board materials, Board portals, electronic meetings, electronic consents, signatures, repositories, controlled-room access, data-room access, legal materials, financial materials, public authority materials, protected knowledge, and other governance-significant information.
Board system security shall include, as appropriate:
a) approved systems;
b) identity verification;
c) multi-factor authentication;
d) access control;
e) role-based permissions;
f) encryption;
g) logging;
h) monitoring;
i) secure file sharing;
j) device security;
k) endpoint controls;
l) secure deletion;
m) backup;
n) incident response;
o) access revocation;
p) administrator controls;
q) retention controls;
r) legal hold controls; and
s) periodic review.
Directors shall not use personal email, unmanaged messaging systems, personal cloud storage, unauthorized AI systems, shadow IT, public links, uncontrolled drives, personal repositories, unsecured devices, consumer file-transfer tools, or unapproved transcription tools for confidential Board materials unless permitted by policy or emergency procedure and appropriately recorded.
122.16 No Unapproved AI Uploads of Board Materials. No Director, officer, committee member, advisor, staff member, contractor, fellow, volunteer, contributor, or other person shall upload, paste, transmit, summarize, train, fine-tune, embed, index, retrieve against, or otherwise process Board materials through any AI system, model, agent, chatbot, transcription tool, summarization tool, coding tool, analysis tool, search tool, or automated workflow unless the system and use case have been approved under the Corporation’s data, AI, cyber, privacy, confidentiality, privilege, protected knowledge, and public-safe controls.
The prohibition on unapproved AI uploads shall apply to, without limitation:
a) privileged materials;
b) work product;
c) draft minutes;
d) Board resolutions;
e) confidential Board packs;
f) financial materials;
g) compensation materials;
h) personnel materials;
i) public authority materials;
j) cyber-sensitive materials;
k) infrastructure-sensitive materials;
l) health-sensitive materials;
m) personal information;
n) rights-bearing data;
o) Tribal, Indigenous, community-protected, local, territorial, cultural, environmental, or protected knowledge;
p) sponsor, donor, funder, provider, host, partner, and third-party confidential materials;
q) research materials;
r) unpublished reports;
s) repository secrets;
t) keys, tokens, credentials, or certificates;
u) incident materials;
v) investigation materials; and
w) legal or regulatory materials.
Approved AI use shall be documented by system, purpose, data class, access class, retention treatment, human reviewer, output limitation, record requirement, and correction pathway. AI-generated summaries of Board materials shall not be treated as official minutes, official resolutions, official legal advice, official findings, public-safe publications, or authoritative records unless reviewed, approved, and recorded through competent process.
122.17 No Shadow IT for Board Materials. No Director, officer, committee member, advisor, staff member, contractor, fellow, volunteer, contributor, or other person shall create, use, or maintain shadow IT for Board materials, including unauthorized drives, unauthorized folders, private repositories, personal note systems, unmanaged devices, unapproved messaging channels, unmanaged project tools, unauthorized automation, uncontrolled backups, personal AI workspaces, public links, or unapproved collaboration platforms.
Shadow IT restrictions shall apply to all Board and committee information governance matters, including confidential materials, privileged materials, work product, legal materials, financial materials, public authority materials, cyber-sensitive materials, infrastructure-sensitive materials, personal information, rights-bearing data, research materials, protected knowledge, controlled-room materials, data room materials, and Nexus interface materials.
Where shadow IT is discovered, the Corporation shall take appropriate action, including access revocation, preservation, forensic review, deletion, migration, quarantine, legal hold, incident response, privilege review, privacy review, cybersecurity review, correction, training, disciplinary action, or legal response.
No convenience, urgency, travel condition, public authority request, sponsor request, provider request, committee need, publication deadline, grant deadline, technical milestone, or Board preference shall justify unapproved shadow IT for Board materials.
122.18 Confidentiality Breach Response. The Board shall ensure that any suspected or actual confidentiality breach involving Board materials is promptly identified, contained, assessed, escalated, corrected, and recorded.
A confidentiality breach may include, without limitation:
a) unauthorized disclosure;
b) unauthorized forwarding;
c) unauthorized public posting;
d) unauthorized repository upload;
e) unauthorized AI upload;
f) unauthorized transcription;
g) unauthorized recording;
h) unauthorized screen capture;
i) unauthorized download;
j) unauthorized data export;
k) lost or stolen device;
l) misdirected email;
m) public link exposure;
n) access by unauthorized person;
o) privilege waiver risk;
p) work product exposure;
q) public authority material exposure;
r) cyber-sensitive exposure;
s) infrastructure-sensitive exposure;
t) personal information exposure;
u) protected knowledge exposure;
v) sponsor or provider confidential information exposure; or
w) uncontrolled public claim based on confidential material.
Breach response shall include, as appropriate:
a) immediate containment;
b) access suspension;
c) link revocation;
d) credential reset;
e) takedown request;
f) repository removal;
g) AI-system remediation request where available;
h) legal review;
i) privilege review;
j) privacy review;
k) cyber review;
l) safeguards review;
m) public authority notice review;
n) third-party notice review;
o) public-safe correction review;
p) disciplinary review;
q) law enforcement or regulator referral where required or appropriate;
r) correction, withdrawal, retraction, supersession, or public clarification; and
s) root-cause review.
No breach response shall itself disclose additional confidential material except as lawful, necessary, proportionate, and recorded.
122.19 Board Confidentiality and Information Governance Records. The Corporation shall maintain Board Confidentiality and Information Governance Records sufficient to demonstrate that Board materials, Board systems, confidential information, privileged materials, work product, public authority materials, cyber-sensitive materials, infrastructure-sensitive materials, finance-sensitive materials, commercially sensitive materials, personal information, rights-bearing data, protected knowledge, controlled-room materials, data room materials, research materials, third-party confidential information, AI-use restrictions, shadow IT restrictions, and breach responses have been classified, protected, reviewed, corrected, and preserved.
Such records shall include, as applicable:
a) Board confidentiality acknowledgments;
b) Director onboarding acknowledgments;
c) officer and committee confidentiality acknowledgments;
d) privileged material logs;
e) work product logs;
f) legal hold records;
g) Board portal access records;
h) identity and access records;
i) device and system access records;
j) meeting security records;
k) electronic consent security records;
l) controlled-room access records;
m) no-download-room access records;
n) data room access records;
o) public authority material classifications;
p) cyber-sensitive material classifications;
q) infrastructure-sensitive material classifications;
r) finance-sensitive material classifications;
s) commercially sensitive material classifications;
t) personal information and rights-bearing data classifications;
u) protected knowledge classifications;
v) AI-use approvals and restrictions;
w) AI-output review records;
x) shadow IT discovery and remediation records;
y) breach reports;
z) incident response records;
aa) privilege review records;
bb) privacy review records;
cc) cyber review records;
dd) safeguards review records;
ee) public authority notice records;
ff) third-party notice records;
gg) takedown, withdrawal, retraction, correction, supersession, restriction, quarantine, deletion, sealing, archive, and legal hold records;
hh) training records;
ii) access revocation records;
jj) disciplinary records where applicable;
kk) counsel review records;
ll) Board review records; and
mm) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that Board confidentiality and information governance are fiduciary controls, legal controls, public trust controls, public authority boundary controls, data / AI / cyber controls, safeguards controls, and Nexus role-separation controls. The Board may deliberate, review, supervise, and correct only if its information environment is secure, bounded, privilege-preserving, access-controlled, public-safe, and correctionable. No Director, officer, committee, council, advisor, participant, sponsor, provider, host, public authority participant, technical contributor, AI system, repository, dashboard, data room, controlled room, or external platform may convert Board information into unauthorized public meaning, public authority action, finance-readiness, certification, procurement approval, recognition, provider preference, sponsor control, public warning, emergency command, or enterprise execution.
Section 123. Emergency Board Decisions, Break-Glass Governance, Ratification, and Sunset
123.1 Emergency Decision Purpose. The Board may establish emergency decision procedures to preserve the lawful existence, fiduciary governance, public-benefit purpose, nonprofit character, tax-exempt or tax-exempt-compatible posture, records integrity, data / AI / cyber security, public authority boundary discipline, finance-boundary discipline, certification and procurement boundary discipline, community safeguards, protected knowledge, public-safe publication discipline, Nexus role separation, continuity, and correctionability of the Corporation when ordinary Board process cannot reasonably be completed before material harm may occur.
Emergency decision procedures shall be interpreted narrowly. They are protective governance mechanisms, not alternative governance channels, expedited execution rights, informal officer powers, sponsor-response mechanisms, provider-response mechanisms, public authority command mechanisms, capital-market response mechanisms, emergency-management authority, or exceptions to the Corporation’s non-execution character.
Emergency Board action may be used only to prevent, contain, pause, restrict, quarantine, correct, preserve, authorize narrowly bounded continuity, seek legal review, protect privileged or confidential information, secure systems, preserve records, comply with urgent legal requirements, avoid public harm, protect public-good assets, protect vulnerable persons or communities, or preserve lawful institutional capacity. Emergency Board action shall not be used to create new mission, expand corporate purposes, authorize prohibited functions, bypass member approval where required, ignore applicable law, weaken safeguards, or convert temporary urgency into permanent authority.
123.2 Emergency Decision Triggers. Emergency decision procedures may be activated where the Chair, Vice-Chair, President, Executive Director or Chief Executive Officer where approved, Secretary, Chief Legal, Compliance, and Risk Officer where approved, Chief Data, AI, and Cyber Officer where approved, a committee chair within scope, or any other person authorized by Board policy determines in good faith that delay may materially impair the Corporation or its public-benefit duties.
Emergency triggers may include, without limitation:
a) imminent legal deadline;
b) regulatory-perimeter risk;
c) cybersecurity incident;
d) data breach;
e) AI incident;
f) repository compromise;
g) credential, key, token, secret, certificate, or identity-control compromise;
h) public authority confusion;
i) public-safe publication error;
j) uncontrolled public claim;
k) public warning or emergency command overclaim;
l) finance, securities, insurance, lending, rating, public finance, procurement, certification, recognition, provider-preference, or sponsor-control overclaim;
m) protected knowledge exposure;
n) civil rights, accessibility, retaliation, whistleblower, grievance, or safeguards emergency;
o) research integrity emergency;
p) evidence integrity emergency;
q) controlled-room or data-room compromise;
r) public authority material exposure;
s) grant, restricted fund, donation, sponsorship, or support emergency affecting legal obligations;
t) director, officer, committee, repository, or system continuity failure;
u) urgent state, territorial, Tribal, local, federal, North America, or cross-border compliance conflict;
v) urgent need to preserve privilege, work product, legal hold, or evidence custody;
w) urgent need to hold, quarantine, withdraw, retract, takedown, restrict, suspend, revoke access, correct, or supersede a record, publication, technical asset, AI output, dashboard, map, software release, proof receipt, public claim, or Nexus-facing material; and
x) any other circumstance that presents comparable risk to the Corporation’s lawful governance, public-benefit purpose, public trust, safeguards, public-safe operation, or legal separateness.
No emergency trigger shall be interpreted to authorize conduct that the Corporation is prohibited from undertaking under this Bylaw.
123.3 Cybersecurity Incident Trigger. A cybersecurity incident may trigger emergency Board procedures where there is suspected or actual compromise of systems, repositories, cloud environments, Board portals, controlled rooms, data rooms, AI systems, model systems, dashboards, maps, APIs, SDKs, software releases, technical baselines, data assets, public-good software, credentials, keys, tokens, secrets, certificates, devices, communications systems, logging systems, backup systems, or identity systems.
Cybersecurity-triggered emergency action may include, without limitation:
a) access suspension;
b) credential reset;
c) key rotation;
d) repository freeze;
e) software release freeze;
f) dashboard or API shutdown;
g) data-room lockdown;
h) controlled-room lockdown;
i) forensic preservation;
j) incident-response activation;
k) legal hold;
l) counsel notification;
m) insurer notification where appropriate;
n) public authority notice review where required;
o) user, participant, sponsor, provider, donor, funder, host, public authority, or affected-person notice review where required;
p) takedown or withdrawal of compromised artifacts;
q) restriction of affected datasets, models, dashboards, maps, proof receipts, or public-safe publications;
r) public-safe correction; and
s) Board ratification of emergency measures.
Cybersecurity emergency action shall be bounded by law, privacy duties, public authority confidentiality, protected knowledge safeguards, privilege, incident-response discipline, and correctionability. It shall not be used to conceal cyber risk, avoid required notice, suppress lawful reporting, or continue compromised operations for convenience.
123.4 Data Breach Trigger. A data breach, suspected data breach, unauthorized disclosure, unauthorized access, unauthorized transfer, unauthorized AI upload, unauthorized repository publication, data-room exposure, public-link exposure, uncontrolled download, loss of device, misdirected communication, re-identification event, protected knowledge exposure, or other material data incident may trigger emergency Board procedures.
Data-breach emergency action may include, as applicable:
a) containment;
b) access revocation;
c) link revocation;
d) deletion request;
e) takedown request;
f) data-room or controlled-room freeze;
g) AI-system remediation request where feasible;
h) forensic preservation;
i) privacy review;
j) cyber review;
k) safeguards review;
l) public authority review;
m) protected knowledge review;
n) legal review;
o) notification analysis;
p) breach notice where legally required;
q) public-safe correction;
r) withdrawal, retraction, restriction, or supersession of affected materials; and
s) remedial governance measures.
The Board shall ensure that data-breach emergency response addresses personal information, rights-bearing data, public authority data, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, community-protected data, Tribal and Indigenous data, local and territorial knowledge, cultural and environmental knowledge, and protected knowledge according to their risk class.
No data breach response shall create further unauthorized disclosure, public authority confusion, public warning confusion, finance overclaim, certification overclaim, procurement overclaim, provider preference, sponsor control, retaliation, or protected knowledge harm.
123.5 AI Incident Trigger. An AI incident may trigger emergency Board procedures where an AI system, model, inference process, agentic workflow, automated classification, retrieval system, embedding system, fine-tuned system, benchmark system, evaluation system, dashboard, digital twin, public-safe drafting tool, coding tool, summarization tool, translation tool, observability tool, or AI-enabled technical asset produces or contributes to material risk.
AI incident triggers may include, without limitation:
a) unauthorized use of confidential Board materials;
b) unauthorized use of privileged materials;
c) unauthorized use of personal information;
d) unauthorized use of public authority materials;
e) unauthorized use of protected knowledge;
f) unauthorized model training, fine-tuning, embedding, retrieval indexing, or model-improvement use;
g) false, misleading, discriminatory, unsafe, or authority-inflating output;
h) hallucinated public authority reference;
i) hallucinated legal, finance, certification, procurement, recognition, or public warning meaning;
j) agentic AI action outside delegated authority;
k) unauthorized communication;
l) unauthorized repository modification;
m) unauthorized publication;
n) automated score overclaim;
o) model leakage;
p) prompt injection or tool misuse;
q) benchmark manipulation;
r) public-safe publication error caused by AI output;
s) inference record failure; and
t) inability to preserve adequate human review or correction.
AI emergency action may include immediate system suspension, model withdrawal, workflow freeze, output quarantine, access restriction, inference-record preservation, human review, correction, public clarification, takedown, retraining prohibition, vendor escalation, repository rollback, and Board ratification.
No AI incident response shall treat an AI output as final authority. Human review, lawful authority, record support, limitation language, and correctionability shall control.
123.6 Public Authority Confusion Trigger. Public authority confusion may trigger emergency Board procedures where a communication, publication, meeting, dashboard, map, public-safe report, public authority room, regulator-listening room, public finance reader room, emergency-management learning session, public infrastructure operator interface, simulation, tabletop exercise, after-action activity, technical baseline, proof receipt, AI output, repository entry, sponsor statement, provider statement, media statement, website material, grant material, or Nexus-facing material may be understood to imply public authority status, official action, delegation, endorsement, public warning, emergency command, procurement approval, public finance approval, regulatory approval, funding commitment, sovereign obligation, public-private partnership, or governmental decision.
Emergency action may include:
a) immediate hold;
b) public or controlled clarification;
c) correction of capacity classification;
d) withdrawal or retraction of public authority references;
e) suspension of affected meeting, room, dashboard, publication, or program;
f) public-safe notice insertion;
g) communication with affected public authority where lawful and appropriate;
h) counsel review;
i) public records, open meetings, procurement, government ethics, lobbying, grant, and public-sector data review where applicable;
j) participant notice; and
k) correction, supersession, or archive.
No emergency procedure shall authorize the Corporation to assume a public authority function, issue official public warnings, direct emergency response, make governmental decisions, approve procurement, regulate, enforce law, or bind a public authority.
123.7 Public-Safe Publication Error Trigger. A public-safe publication error may trigger emergency Board procedures where a published or pending public output may be materially inaccurate, unsupported, misleading, unsafe, overbroad, stale, disputed, improperly sourced, improperly classified, improperly mapped, improperly scored, improperly generated by AI, improperly translated, accessibility-defective in a material way, privacy-defective, cyber-risky, infrastructure-risky, protected-knowledge-exposing, public authority-confusing, finance-overclaiming, certification-overclaiming, procurement-overclaiming, recognition-overclaiming, provider-preferencing, sponsor-controlled, or inconsistent with controlled vocabulary.
Public-safe publication emergency action may include:
a) publication freeze;
b) takedown;
c) access restriction;
d) public correction;
e) controlled correction;
f) retraction;
g) supersession;
h) withdrawal;
i) limitation-language insertion;
j) map aggregation or redaction;
k) dashboard shutdown;
l) dataset restriction;
m) software documentation correction;
n) proof receipt correction;
o) source-lineage review;
p) evidence quality review;
q) methods review;
r) AI review;
s) safeguards review; and
t) archive.
The Board shall ensure that public-safe publication response preserves the distinction between evidence, method, observability output, technical baseline, public-good software, GRF-facing input, GRA-facing input, Nexus-facing support, and public authority action. No publication error shall be cured by silence where public correction is required by law, public-safe duty, record integrity, or correctionability.
123.8 Finance, Securities, Insurance, Lending, Rating, Public Finance, Procurement, Certification, Recognition, Provider-Preference, or Public Warning Overclaim Trigger. Any actual or suspected overclaim relating to finance-readiness, capital-readability, investment suitability, insurance-readiness, underwriting suitability, lending suitability, bankability, rating, public finance approval, grant approval, tax credit approval, procurement approval, certification, accreditation, conformance, recognition, maturity, standing, Docket status, Grid status, Nexus-compatible status, provider preference, sponsor entitlement, public warning, emergency command, or public authority decision may trigger emergency Board procedures.
Emergency action may include:
a) immediate withdrawal of the overclaim;
b) suspension of affected communication;
c) correction of public materials;
d) correction of controlled-room materials;
e) correction of sponsor, donor, provider, host, public authority, capital-reader, or media materials;
f) restriction of dashboard, map, proof receipt, evidence pack, technical baseline, public-good software documentation, or public-safe report;
g) notice to affected persons where necessary;
h) counsel review;
i) compliance review;
j) GRF interface review where recognition or public legitimacy is implicated;
k) GRA interface review where finance-readiness or capital-readability is implicated;
l) Nexus Standards interface review where conformance or protocol authority is implicated;
m) public-safe clarification; and
n) disciplinary or contractual response where appropriate.
The Board shall preserve the Corporation’s non-executing role. No emergency response may validate an overclaim by restating it in softer form unless a competent authority has lawfully created the underlying status and the Corporation has authority to reference it.
123.9 Sponsor, Provider, Donor, Funder, Host, or Capture Trigger. Sponsor, provider, donor, funder, host, or capture risk may trigger emergency Board procedures where any person or institution attempts to control, purchase, suppress, veto, distort, delay, influence, condition, privatize, enclose, or overstate the Corporation’s evidence, research, methods, technical baseline, public-good software, public authority access, publication, controlled-room access, Nexus interface, GRF-facing input, GRA-facing input, public-safe claim, Board decision, officer action, committee recommendation, or public description.
Capture triggers may include, without limitation:
a) support-for-outcome demand;
b) support-for-recognition demand;
c) support-for-finance-readiness demand;
d) support-for-certification demand;
e) support-for-procurement demand;
f) support-for-public-authority-access demand;
g) sponsor veto demand;
h) provider preference demand;
i) donor or funder editorial control demand;
j) host control demand;
k) enterprise actor control demand;
l) paid public claim demand;
m) influence concentration;
n) related-party pressure;
o) sponsored-seat pressure;
p) data-access pressure;
q) repository-control pressure;
r) public authority interface pressure;
s) publication suppression pressure; and
t) technical asset enclosure pressure.
Emergency action may include refusal, suspension, restriction, ring-fencing, recusal, access revocation, return of support, termination of support, termination of participation, public or controlled clarification, contract enforcement, legal review, committee review, and Board ratification.
No financial dependency, public profile, sponsor importance, provider importance, host importance, grant deadline, event deadline, technical dependency, or public authority relationship shall justify capture.
123.10 Protected Knowledge, Community Harm, Civil Rights, Accessibility, or Safeguards Trigger. Protected knowledge, community harm, civil rights, accessibility, or safeguards risk may trigger emergency Board procedures where an activity, record, publication, dashboard, map, dataset, AI system, model, inference, observability output, controlled room, public authority interface, sponsor interface, provider interface, public-safe report, technical baseline, public-good software release, Academy activity, research activity, or Nexus-facing material may create harm to persons, communities, Tribal or Indigenous rights, protected knowledge, vulnerable groups, accessibility, civil rights, dignity, safety, or protected participation.
Emergency action may include:
a) stop-the-line activation;
b) publication freeze;
c) map withdrawal;
d) dataset restriction;
e) model-use suspension;
f) AI-output quarantine;
g) dashboard shutdown;
h) controlled-room restriction;
i) public authority interface pause;
j) community or Tribal protocol review;
k) protected knowledge review;
l) civil rights review;
m) accessibility remediation;
n) grievance intake;
o) non-retaliation protection;
p) remedy planning;
q) public-safe correction;
r) deletion, sealing, or restriction where lawful; and
s) Board review.
The Board shall not require a community, complainant, whistleblower, Indigenous knowledge holder, protected participant, or affected person to prove final harm before the Corporation takes protective interim action where credible risk exists.
No emergency action shall extract additional protected knowledge, expose complainants, retaliate, stigmatize communities, or convert safeguards review into public relations management.
123.11 Legal Deadline or Regulatory Perimeter Trigger. A legal deadline or regulatory-perimeter trigger may arise where delay could cause missed filings, loss of good standing, tax compliance failure, charitable solicitation violation, grant noncompliance, public records or public authority breach, privacy breach, cyber notice failure, employment compliance failure, sanctions or export-control breach, litigation prejudice, regulatory response failure, investigation prejudice, contract default, restricted fund breach, insurance notice failure, or other material legal harm.
Regulatory-perimeter triggers may also arise where an activity may be perceived as securities activity, investment advice, broker-dealer activity, finder activity, insurance activity, underwriting, banking, lending, rating, public finance approval, procurement approval, certification, accreditation, regulatory approval, public authority action, public warning, emergency command, professional advice, or enterprise execution.
Emergency action may include:
a) counsel engagement;
b) compliance review;
c) privilege preservation;
d) legal hold;
e) filing authorization within delegated authority;
f) notice authorization where required;
g) activity suspension;
h) communication hold;
i) publication hold;
j) contract hold;
k) public-safe clarification;
l) externalization to licensed or competent actors;
m) referral to public authorities where appropriate;
n) termination or abandonment of activity; and
o) ratification or corrective action.
No regulatory-perimeter ambiguity shall be resolved by informal comfort, market custom, sponsor expectation, provider expectation, public authority encouragement, technical centrality, AI summary, or operational convenience. The more restrictive lawful interpretation shall apply pending competent review.
123.12 Repository, Software Release, Key, Token, Credential, Technical Asset, or Controlled Technology Compromise Trigger. A repository, software release, key, token, credential, technical asset, or controlled technology compromise may trigger emergency Board procedures where the Corporation’s public-good software, open technical baseline, code, dependency, package, dataset, model, dashboard, API, SDK, schema, benchmark, test harness, evaluation set, proof receipt, role key, smart-license logic, ledger interface, repository permission, release artifact, software bill of materials, signing process, technical profile, controlled technology, or technical asset may be compromised, misused, exposed, corrupted, weaponized, enclosed, or inaccurately represented.
Emergency action may include:
a) repository freeze;
b) maintainer access suspension;
c) credential reset;
d) key rotation;
e) package withdrawal;
f) release revocation;
g) vulnerability advisory;
h) artifact signing review;
i) SBOM review;
j) dependency rollback;
k) source provenance review;
l) contributor review;
m) license review;
n) export-control review;
o) sanctions review;
p) controlled-technology review;
q) public-safe technical notice;
r) takedown;
s) deprecation;
t) archive;
u) correction; and
v) Board ratification.
No repository permission, maintainer status, release artifact, ledger entry, proof receipt, role key, package publication, dashboard deployment, or technical asset configuration shall create governance authority beyond the competent record.
123.13 Emergency Decision Authority. Emergency Board decision authority shall be exercised by the Board where a quorum can reasonably be assembled in time. Where a full Board quorum cannot reasonably be assembled before material harm may occur, emergency authority may be exercised only by the Executive Committee if lawfully created and delegated, by the Chair acting with at least one other Director where permitted by law and policy, by a designated emergency governance group approved by the Board, or by officers only within emergency officer authority expressly granted under this Bylaw, Board resolution, or policy.
Emergency decision authority shall be limited to protective, interim, risk-containment, continuity, compliance, correction, restriction, and preservation measures. Emergency authority shall not be presumed from seniority, title, authorship, technical access, repository access, public authority relationship, sponsor relationship, provider relationship, media visibility, founder status, committee chair status, or operational proximity.
Every emergency decision shall identify:
a) emergency trigger;
b) decision-maker;
c) authority basis;
d) time of decision;
e) facts known;
f) risks identified;
g) action taken;
h) scope;
i) duration;
j) affected records, systems, persons, rooms, materials, or outputs;
k) legal, cyber, privacy, safeguards, public authority, finance-boundary, certification-boundary, procurement-boundary, recognition-boundary, provider-neutrality, or sponsor non-control implications;
l) notice required;
m) ratification pathway;
n) sunset date or review time; and
o) correction pathway.
123.14 Break-Glass Authority. Break-glass authority may be used only where immediate action is necessary to prevent or contain serious legal, cyber, privacy, data, AI, protected knowledge, public authority, public-safe, governance, financial-control, records-integrity, or institutional-continuity harm and ordinary authorization cannot reasonably be obtained in time.
Break-glass measures may include, without limitation:
a) temporary access suspension;
b) temporary credential reset;
c) temporary key rotation;
d) repository freeze;
e) software release hold;
f) dashboard shutdown;
g) API shutdown;
h) data-room lockdown;
i) controlled-room lockdown;
j) public statement hold;
k) publication freeze;
l) takedown request;
m) legal hold;
n) privilege-preservation measure;
o) evidence-preservation measure;
p) public-safe correction hold;
q) temporary delegation for continuity;
r) temporary external expert engagement;
s) emergency counsel engagement; and
t) emergency incident-response engagement.
Break-glass authority shall be narrowly tailored, documented promptly, reported to the Board, and reviewed for ratification, modification, continuation, correction, or termination. It shall not become a standing delegation by repetition, custom, technical convenience, or failure to review.
123.15 Limits on Break-Glass Authority. Break-glass authority shall not be used to amend the Articles or Certificate, amend this Bylaw, change the Corporation’s legal name, alter mission lock, alter nonprofit character, alter non-distribution requirements, dissolve the Corporation, merge the Corporation, sell substantially all assets, transfer public-good assets outside approved controls, approve a material support arrangement inconsistent with anti-capture controls, approve a conflicted transaction without required review, waive Board reserved matters, waive member approval where required, create new membership rights, create new public authority status, create finance-readiness authority, create certification authority, create procurement authority, create recognition authority, create standards authority, create protocol authority, approve enterprise execution, or authorize any prohibited function.
Break-glass authority shall not authorize:
a) securities offering;
b) investment advice;
c) brokerage or finder activity;
d) lending or credit approval;
e) insurance placement or underwriting;
f) rating;
g) public finance approval;
h) procurement approval;
i) certification;
j) recognition;
k) public warning;
l) emergency command;
m) public authority decision;
n) provider selection for public authorities;
o) sponsor control;
p) donor control;
q) funder control;
r) protected knowledge extraction;
s) unlawful data processing;
t) unauthorized AI training;
u) waiver of privilege without competent review; or
v) unlawful disclosure of confidential materials.
Any purported break-glass action outside lawful scope shall be void, voidable, suspended, non-operative, or subject to immediate correction to the fullest extent permitted by law.
123.16 No Emergency Exercise of Prohibited Functions. No emergency, crisis, disruption, incident, public authority request, sponsor request, provider request, public pressure, media inquiry, grant deadline, capital-reader request, cybersecurity event, data breach, AI incident, public-safe publication error, protected knowledge risk, or operational urgency shall authorize the Corporation to exercise a prohibited function.
The Corporation shall not, through emergency action:
a) command emergency response;
b) issue official public warnings;
c) direct evacuations;
d) make public health orders;
e) regulate;
f) enforce law;
g) approve procurement;
h) certify;
i) accredit;
j) recognize;
k) determine finance-readiness;
l) determine insurance-readiness;
m) rate;
n) approve public finance;
o) solicit securities;
p) place capital;
q) provide investment advice;
r) broker transactions;
s) lend;
t) underwrite;
u) bind insurance;
v) control enterprise execution;
w) select providers for public authorities;
x) override public authority decision-making; or
y) convert AI, dashboards, proof receipts, ledgers, sensors, AI-RAN signals, O-RAN signals, DePIN records, digital twins, or maps into final authority.
Emergency action shall remain protective, non-executing, record-supported, public-safe, and correctionable.
123.17 Time-Boxed Emergency Measures. Emergency measures shall be time-boxed. Each emergency action shall include a stated duration, review time, sunset time, ratification deadline, or condition for termination, unless the emergency action is completed immediately by its nature.
Time-boxing shall apply to:
a) access suspensions;
b) repository freezes;
c) room lockdowns;
d) publication freezes;
e) dashboard shutdowns;
f) API shutdowns;
g) software release holds;
h) AI system suspensions;
i) data restrictions;
j) public statement holds;
k) temporary delegations;
l) emergency consultant engagements;
m) legal holds subject to counsel preservation requirements;
n) interim restrictions on participants;
o) interim conflict restrictions;
p) support acceptance holds; and
q) other emergency controls.
No emergency measure shall continue indefinitely by neglect. Continuation beyond the initial emergency period shall require review, renewal, modification, or ratification by the Board or other competent authority within the lawful scope of authority.
123.18 Notice to Board. Any emergency decision, break-glass action, or emergency officer action affecting the Board’s oversight responsibilities shall be reported to the Board promptly and in any event within the period required by policy, law, Board resolution, or the emergency action record.
Notice to the Board shall include, as available:
a) nature of emergency;
b) trigger;
c) persons taking action;
d) authority relied upon;
e) affected systems, records, persons, rooms, publications, contracts, grants, support arrangements, public authority interfaces, Nexus interfaces, repositories, or technical assets;
f) immediate actions taken;
g) actions proposed;
h) legal review status;
i) cyber review status;
j) privacy review status;
k) data / AI review status;
l) safeguards review status;
m) finance-boundary review status;
n) certification and procurement boundary review status;
o) public authority review status;
p) sponsor, provider, donor, funder, host, or capture review status;
q) notice obligations;
r) correction obligations;
s) ratification need; and
t) sunset or next review point.
Notice may be restricted to a confidential or privileged Board channel where necessary to preserve privilege, protect cybersecurity, protect public authority confidentiality, protect personal information, protect protected knowledge, or avoid further harm.
123.19 Ratification. Emergency decisions and break-glass actions shall be submitted for ratification, modification, continuation, limitation, correction, or rejection by the Board or other competent authority as soon as reasonably practicable.
Ratification shall require review of:
a) authority;
b) factual basis;
c) necessity;
d) proportionality;
e) scope;
f) duration;
g) legal compliance;
h) tax and nonprofit compatibility where relevant;
i) public-benefit compatibility;
j) non-execution compatibility;
k) public authority boundary compatibility;
l) finance-boundary compatibility;
m) certification and procurement boundary compatibility;
n) data / AI / cyber compliance;
o) privacy compliance;
p) research integrity;
q) safeguards and protected knowledge;
r) conflicts and recusals;
s) sponsor and provider non-control;
t) records adequacy;
u) correction requirements; and
v) lessons learned.
Ratification shall not cure an unlawful act to the extent it cannot lawfully be cured. Where an emergency act exceeded authority, the Board shall determine whether the act is void, voidable, non-operative, subject to correction, subject to public or controlled clarification, subject to disciplinary response, subject to contract remedy, or subject to legal referral.
123.20 Sunset. Emergency measures shall sunset automatically at the time, date, event, or condition specified in the emergency action record unless extended by competent authority within lawful limits.
Sunset review shall determine whether the emergency measure should be:
a) terminated;
b) continued for a defined period;
c) narrowed;
d) expanded only where lawful and necessary;
e) converted into an ordinary Board-approved action;
f) referred to committee;
g) referred to counsel;
h) referred to compliance;
i) referred to data / AI / cyber review;
j) referred to safeguards review;
k) corrected;
l) superseded;
m) withdrawn;
n) archived;
o) publicly clarified; or
p) documented as closed.
No emergency practice shall become a policy, procedure, delegation, standard, protocol, technical baseline, public-safe notice, public authority interface, finance-boundary practice, data / AI / cyber practice, or Nexus interface practice unless separately adopted through ordinary competent process.
123.21 Post-Emergency Review. After any material emergency decision, the Board shall conduct or require a post-emergency review appropriate to the severity, complexity, and risk of the event.
Post-emergency review shall address, as applicable:
a) root cause;
b) trigger adequacy;
c) response speed;
d) authority adequacy;
e) decision quality;
f) records adequacy;
g) legal compliance;
h) privilege protection;
i) cyber response;
j) data response;
k) AI response;
l) privacy response;
m) public authority interface response;
n) finance-boundary response;
o) certification and procurement boundary response;
p) sponsor, donor, funder, provider, host, and capture response;
q) protected knowledge and safeguards response;
r) civil rights and accessibility response;
s) communication quality;
t) public-safe correction quality;
u) technical remediation;
v) continuity implications;
w) training needs;
x) policy amendments;
y) system improvements; and
z) recurrence prevention.
Post-emergency review shall not be used to assign blame where a learning, correction, or systems-improvement response is appropriate, but it shall not prevent accountability where misconduct, negligence, authority overreach, retaliation, concealment, or intentional violation occurred.
123.22 Correction and Notice Where Required. Where an emergency event or emergency action affects public materials, controlled materials, Board records, committee records, public authority materials, participant rights, donor or sponsor records, provider materials, research materials, datasets, dashboards, maps, software releases, technical baselines, AI outputs, proof receipts, Nexus-facing materials, GRF-facing inputs, GRA-facing inputs, or public-safe claims, the Corporation shall determine whether correction, notice, supersession, withdrawal, retraction, takedown, restriction, archive, or public clarification is required.
Correction and notice review shall consider:
a) applicable law;
b) contractual obligations;
c) public authority obligations;
d) privacy obligations;
e) cybersecurity obligations;
f) protected knowledge obligations;
g) research integrity obligations;
h) civil rights and accessibility obligations;
i) public-safe publication obligations;
j) reliance risk;
k) authority-inflation risk;
l) public trust;
m) harm prevention;
n) recurrence prevention;
o) controlled vocabulary;
p) limitation language;
q) correctionability; and
r) validity-by-record.
Notice may be public, controlled, internal, privileged, participant-specific, public-authority-specific, donor-specific, sponsor-specific, provider-specific, community-specific, Tribal-interface-specific, cross-border-specific, repository-specific, or no-download-room-specific, as the risk and law require.
No correction or notice shall create new overclaims, disclose protected information unnecessarily, waive privilege without competent approval, expose protected knowledge, cause retaliation, or imply that the Corporation has authority it does not possess.
123.23 Emergency Decision Records. The Corporation shall maintain Emergency Decision Records sufficient to demonstrate that emergency decisions, break-glass actions, emergency officer actions, emergency committee actions, emergency access restrictions, emergency publication controls, emergency data / AI / cyber controls, emergency public authority controls, emergency safeguards controls, emergency finance-boundary controls, emergency repository controls, emergency technical asset controls, and emergency correction actions were authorized, bounded, reviewed, ratified, sunset, corrected, and preserved.
Emergency Decision Records shall include, as applicable:
a) trigger record;
b) incident record;
c) emergency decision record;
d) break-glass activation record;
e) authority basis;
f) decision-maker identity;
g) time and date;
h) facts known at time of action;
i) risk classification;
j) affected systems;
k) affected records;
l) affected persons;
m) affected rooms;
n) affected publications;
o) affected public authority interfaces;
p) affected Nexus interfaces;
q) affected GRF-facing or GRA-facing inputs;
r) affected repositories;
s) affected datasets, models, dashboards, maps, proof receipts, software releases, technical baselines, or public-good technical assets;
t) actions taken;
u) access restrictions;
v) holds, quarantines, freezes, lockdowns, takedowns, withdrawals, retractions, corrections, supersessions, deletions, sealings, archives, or referrals;
w) legal review records;
x) privilege review records;
y) privacy review records;
z) cybersecurity review records;
aa) data governance review records;
bb) AI governance review records;
cc) public authority review records;
dd) finance-boundary review records;
ee) certification and procurement boundary review records;
ff) sponsor, donor, funder, provider, host, or capture review records;
gg) safeguards and protected knowledge review records;
hh) civil rights and accessibility review records;
ii) notice records;
jj) Board notice records;
kk) ratification records;
ll) sunset records;
mm) post-emergency review records;
nn) corrective action records;
oo) training and recurrence-prevention records;
pp) insurance, legal, regulatory, public authority, funder, law enforcement, or third-party referral records where applicable;
qq) responsible owner;
rr) custodian;
ss) repository location;
tt) access class;
uu) publication class;
vv) retention class;
ww) legal hold status;
xx) deletion status;
yy) archive status; and
zz) metadata.
The governing rule of this Section is that emergency governance is a temporary protective discipline, not a substitute constitution. Emergency procedures may preserve the Corporation, protect people, secure systems, protect records, maintain public-safe integrity, and prevent role confusion; they may not authorize mission drift, execution, public authority substitution, finance-readiness, certification, procurement approval, recognition, provider preference, sponsor control, emergency command, public warning, uncontrolled AI authority, or unrecorded governance. Every emergency action shall be lawful, bounded, time-limited, reviewable, recorded, ratified where required, sunset, corrected where needed, and integrated into the Corporation’s validity-by-record and correctionability disciplines.
Section 124. Board Minutes, Resolutions, Records, Action Items, and Record Integrity
124.1 Minute Requirement. The Corporation shall keep minutes of all meetings of the Board, including regular meetings, special meetings, annual meetings, emergency meetings, executive sessions, in camera sessions, controlled-room Board sessions, confidential sessions, public or stakeholder sessions where approved, state, territorial, Tribal, public authority, or North America interface sessions where approved, and any other meeting at which Board deliberation, fiduciary oversight, governance direction, reserved matter review, officer reporting, committee reporting, emergency action, ratification, correction, or other governance-significant activity occurs.
Minutes shall be sufficient to evidence that the Board acted with lawful authority, adequate information, fiduciary care, mission fidelity, nonprofit and public-benefit discipline, tax-exempt or tax-exempt-compatible awareness, conflict management, records discipline, role separation, non-execution, public authority boundary control, finance-boundary control, certification and procurement boundary control, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, and correctionability.
Minutes shall not be drafted as transcripts unless the Board expressly authorizes transcription and the confidentiality, privilege, privacy, public authority, cyber, infrastructure, finance, commercial, personal, protected knowledge, and legal risks of transcription have been reviewed. Minutes shall be accurate, neutral, complete as to formal action, proportionate as to deliberation, and disciplined as to confidential or privileged matters.
Minutes shall record the act of governance. They shall not inflate Board discussion into public authority action, finance-readiness determination, certification, procurement approval, recognition, provider preference, sponsor control, public warning, emergency command, professional advice, legal advice to third parties, or enterprise execution.
124.2 Resolution Requirement. Board resolutions shall be used to evidence formal Board action, including approval, adoption, amendment, repeal, restatement, suspension, withdrawal, ratification, delegation, appointment, removal, authorization, restriction, correction, supersession, dissolution, or other governance-significant acts.
A resolution shall identify, as applicable:
a) the matter approved or rejected;
b) the authority under which the Board acted;
c) the effective date;
d) any conditions precedent;
e) any transition rule;
f) any sunset date;
g) any delegated authority;
h) any budget, contract, publication, data, AI, cyber, public authority, finance-boundary, certification-boundary, procurement-boundary, safeguards, or Nexus-interface limitation;
i) any required notice;
j) any required filing;
k) any required repository, register, or gazette entry;
l) any required correction, supersession, withdrawal, retraction, takedown, or archive;
m) any conflict, abstention, or recusal;
n) any committee recommendation relied upon;
o) any officer report relied upon;
p) any counsel or compliance review relied upon;
q) any public-safe limitation language; and
r) any responsible owner.
Resolutions may be included in minutes, attached to minutes, entered in a Board resolution register, executed as written consents where lawful, or recorded in another official Board record approved by the Corporation. No slide, informal note, AI summary, email exchange, chat message, draft, working copy, public statement, repository issue, ledger entry, proof receipt, dashboard entry, or public announcement shall substitute for a Board resolution where a resolution is required.
124.3 Attendance Record. The minutes or meeting record shall identify Directors present, Directors absent, officers present, counsel present, staff present, committee representatives present, invited guests present, public authority participants present, advisors present, observers present, and any other persons admitted to the meeting or any portion of the meeting.
The attendance record shall identify, as applicable:
a) whether each Director participated in person, virtually, by teleconference, or by another lawful electronic means;
b) whether identity verification was completed where required;
c) whether any person attended only for a portion of the meeting;
d) whether any person was excluded from executive session, in camera session, privileged session, conflict session, controlled-room session, or other restricted portion;
e) whether any public authority participant attended in official capacity, observer capacity, regulator-listening capacity, public finance reader capacity, emergency-management participant capacity, public infrastructure operator capacity, simulation participant capacity, or another classified capacity;
f) whether any sponsor, donor, funder, provider, host, contractor, university, laboratory, community, Tribal, Indigenous, media, civil society, enterprise, national company, Project SPV, or Nexus-interface participant attended; and
g) whether any confidentiality, conflict, competition, data / AI / cyber, public authority boundary, finance-boundary, safeguards, or controlled-room acknowledgment was required.
Attendance shall not create voting rights, fiduciary authority, officer authority, representative authority, public authority endorsement, procurement status, provider status, sponsor entitlement, recognition, finance-readiness, certification, or Nexus-compatible status unless separately and lawfully recorded.
124.4 Quorum Record. The minutes shall record whether quorum was present at the commencement of the meeting and, where relevant, whether quorum remained present for each vote, reserved matter, conflict-sensitive matter, executive session, emergency action, or other decision requiring a quorum.
The quorum record shall reflect any effect of:
a) Director absence;
b) Director departure;
c) Director recusal;
d) loss of eligibility;
e) suspension of voting rights where lawful;
f) vacancy;
g) electronic participation failure;
h) identity verification failure;
i) conflict restriction;
j) emergency procedure; and
k) higher quorum requirement for reserved matters.
If quorum is lost, the minutes shall identify the time or point at which quorum was lost, the actions taken before loss of quorum, any matters deferred, any emergency or continuity authority relied upon, and any subsequent ratification required. No action requiring quorum shall be treated as valid merely because minutes were later drafted unless the action was lawfully taken or lawfully ratified.
124.5 Notice Record. The minutes or meeting record shall identify the notice given for the meeting, including the date of notice, method of notice, recipients, meeting date, meeting time, location or electronic access method, agenda reference, and any special meeting, emergency meeting, reserved matter, or action-specific notice requirement.
The notice record shall also identify, as applicable:
a) waiver of notice;
b) deemed waiver by attendance where permitted by law;
c) objection to notice;
d) special notice required by law, Articles or Certificate, this Bylaw, member rights where applicable, Board policy, committee charter, grant agreement, restricted fund requirement, public authority interface, controlled-room rule, or emergency procedure;
e) late-added agenda items;
f) supplemental materials;
g) confidentiality classification of notice;
h) public-safe notice where applicable;
i) state, territorial, Tribal, District of Columbia, local, North America, or cross-border notice considerations; and
j) any defect, correction, cure, ratification, or deferral.
No defective notice shall be cured by convenience, custom, operational urgency, sponsor request, provider request, public authority request, grant deadline, media pressure, or technical deadline unless cure is lawful and recorded.
124.6 Materials Reviewed Record. The minutes or meeting record shall identify material categories reviewed by the Board, without unnecessarily disclosing privileged, confidential, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, personal, health-sensitive, public authority, community-protected, Tribal, Indigenous, local, territorial, cultural, environmental, or protected knowledge content.
Materials reviewed may include, without limitation:
a) agenda materials;
b) officer reports;
c) committee reports;
d) financial statements;
e) budgets;
f) audit, review, or internal control materials;
g) legal memoranda;
h) counsel briefings;
i) compliance reports;
j) tax and nonprofit status materials;
k) risk registers;
l) incident reports;
m) evidence reports;
n) methods reports;
o) research reports;
p) public-safe publication materials;
q) data governance materials;
r) AI governance materials;
s) cybersecurity materials;
t) model register materials;
u) inference record materials;
v) repository and software release materials;
w) public authority interface materials;
x) GRF-facing input materials;
y) GRA-facing technical input materials;
z) Nexus interface materials;
aa) sponsor, donor, funder, provider, host, grant, and support materials;
bb) safeguards and protected knowledge materials;
cc) civil rights and accessibility materials;
dd) controlled-room and data-room materials; and
ee) emergency action materials.
The record shall distinguish between materials reviewed for information, materials reviewed for deliberation, materials reviewed for approval, materials subject to privilege, materials subject to restricted access, and materials incorporated into the formal record. No material shall be deemed approved merely because it was circulated or reviewed unless the Board action record expressly approves it.
124.7 Decision Record. The minutes shall record each decision of the Board with sufficient specificity to identify the decision made, the authority relied upon, the scope of approval, the limitations imposed, and the action required.
A decision record shall identify, as applicable:
a) the motion or resolution;
b) the proposer and seconder where recorded or required;
c) the matter decided;
d) the decision outcome;
e) the approval threshold;
f) the vote result;
g) abstentions;
h) recusals;
i) dissent or minority note where permitted;
j) conditions;
k) implementation steps;
l) delegated owner;
m) deadline;
n) required records;
o) required notice;
p) required filing;
q) required repository, register, or gazette entry;
r) required counsel, compliance, data / AI / cyber, public authority, finance-boundary, certification-boundary, procurement-boundary, safeguards, or public-safe publication review;
s) limitation language;
t) correction pathway; and
u) sunset or review date where applicable.
A decision record shall be construed narrowly to the matter actually approved. No general discussion, informal consensus, non-binding sense of the Board, officer update, committee recommendation, strategic discussion, technical note, AI-generated summary, dashboard view, or public statement shall be treated as a Board decision unless recorded as such.
124.8 Vote Record. The minutes shall record the vote taken on each matter requiring Board approval. The vote record shall identify whether the matter was approved, rejected, deferred, tabled, withdrawn, referred, remanded, held, quarantined, or otherwise disposed of.
The vote record shall identify, as applicable:
a) number of votes in favor;
b) number of votes against;
c) abstentions;
d) recusals;
e) non-voting attendees;
f) Directors absent;
g) Directors present but not voting;
h) voting threshold;
i) whether the threshold was met;
j) whether a higher threshold applied;
k) whether member approval is also required;
l) whether written consent was used;
m) whether electronic voting was used where lawful;
n) whether identity verification was completed; and
o) any legal, procedural, or conflict limitation affecting the vote.
The Board may record named votes where required by law, Articles or Certificate, this Bylaw, policy, conflict procedure, public authority interface, restricted fund obligation, committee charter, or Board direction. Where named votes are not required, the Board may record aggregate votes unless a Director requests that the Director’s dissent, abstention, or recusal be recorded.
124.9 Abstention Record. The minutes shall record abstentions on Board action where relevant to quorum, voting threshold, conflict analysis, fiduciary record, or legal effect.
An abstention record shall identify, as applicable:
a) the Director abstaining;
b) the matter on which the Director abstained;
c) whether the abstention was voluntary;
d) whether the abstention was related to uncertainty, lack of information, conflict concern, independence concern, legal concern, public authority boundary concern, finance-boundary concern, certification or procurement boundary concern, data / AI / cyber concern, safeguards concern, protected knowledge concern, or another stated reason;
e) whether the abstaining Director remained present;
f) whether the abstention affected quorum;
g) whether the abstention affected the vote threshold; and
h) whether further review or follow-up was requested.
An abstention shall not substitute for a mandatory recusal where recusal is required. Where the reason for abstention indicates a potential conflict, role confusion, legal ambiguity, public authority concern, finance-boundary concern, certification or procurement concern, or safeguards concern, the matter shall be reviewed under the applicable conflict, boundary, or escalation procedure.
124.10 Conflict Disclosure Record. The minutes shall record any conflict disclosure, related-party disclosure, dual-role disclosure, independence concern, sponsor relationship, donor relationship, funder relationship, provider relationship, host relationship, contractor relationship, public authority relationship, investor relationship, insurer relationship, lender relationship, national company relationship, Project SPV relationship, university or laboratory relationship, community relationship, Tribal or Indigenous interface relationship, or other interest disclosed in connection with a Board matter.
The conflict disclosure record shall identify, as applicable:
a) the person making the disclosure;
b) the nature of the disclosed interest;
c) the matter affected;
d) whether the disclosure was annual, event-based, meeting-specific, or updated;
e) whether counsel or compliance review occurred;
f) whether the Board determined the matter to be a conflict, potential conflict, appearance concern, independence concern, related-party transaction, or manageable relationship;
g) any recusal imposed;
h) any access restriction imposed;
i) any voting restriction imposed;
j) any mitigation required;
k) any independent review required;
l) any comparability, reasonableness, tax, nonprofit, or private benefit review required;
m) any sponsor non-control, provider-neutrality, public authority boundary, finance-boundary, certification-boundary, procurement-boundary, data / AI / cyber, safeguards, or competition review required; and
n) any corrective action required.
Conflict disclosure records shall be maintained with confidentiality appropriate to the matter. They shall not be used for retaliation, exclusion, stigmatization, or public mischaracterization, but shall be sufficient to demonstrate fiduciary and procedural integrity.
124.11 Recusal Record. The minutes shall record any recusal required or voluntarily undertaken by a Director or other participant in connection with a Board matter.
The recusal record shall identify, as applicable:
a) the person recused;
b) the matter;
c) the basis for recusal;
d) whether the person was recused from deliberation;
e) whether the person was recused from voting;
f) whether the person was recused from access to materials;
g) whether the person left the meeting or restricted session;
h) whether the recusal affected quorum;
i) whether the recusal affected the vote threshold;
j) whether the remaining disinterested Directors reviewed and approved the matter;
k) whether counsel, compliance, tax, nonprofit, competition, public authority, finance-boundary, certification-boundary, procurement-boundary, data / AI / cyber, safeguards, or protected knowledge review was required; and
l) when access or participation may resume.
A recused person shall not influence the decision through side-channel communication, informal pressure, sponsor communication, provider communication, public authority communication, staff instruction, AI-generated material, repository activity, media activity, or Nexus-interface activity. Recusal shall be meaningful, recorded, and enforceable.
124.12 Dissent or Minority Note Where Permitted. A Director may request that the minutes record the Director’s dissent, objection, minority view, abstention explanation, or requested limitation where permitted by law, the Articles or Certificate, this Bylaw, Board policy, and confidentiality requirements.
A dissent or minority note may address, without limitation:
a) legal authority;
b) fiduciary concern;
c) public-benefit concern;
d) tax or nonprofit concern;
e) private benefit or inurement concern;
f) non-execution concern;
g) public authority boundary concern;
h) finance-boundary concern;
i) certification or procurement boundary concern;
j) provider neutrality;
k) sponsor non-control;
l) data / AI / cyber concern;
m) privacy concern;
n) research integrity concern;
o) evidence or methods concern;
p) public-safe publication concern;
q) civil rights concern;
r) accessibility concern;
s) protected knowledge concern;
t) community safeguard concern;
u) competition concern;
v) sanctions or export-control concern;
w) record adequacy; or
x) correctionability.
The Board may require that dissent or minority notes be concise, factual, non-defamatory, non-retaliatory, privilege-preserving, confidentiality-preserving, and public-safe. A dissent or minority note shall not authorize disclosure of confidential, privileged, protected, or restricted information outside approved channels.
124.13 Action Item Record. The minutes or an official Board action tracker shall record action items arising from Board meetings, Board decisions, emergency actions, ratifications, corrections, committee reports, officer reports, audits, reviews, incidents, legal matters, public authority matters, data / AI / cyber matters, safeguards matters, support arrangements, Nexus interfaces, or other governance-significant matters.
Action item records shall identify, as applicable:
a) action item title;
b) action required;
c) responsible owner;
d) supporting owner;
e) approving authority;
f) deadline;
g) priority;
h) status;
i) dependencies;
j) required budget authority;
k) required contract authority;
l) required legal review;
m) required compliance review;
n) required data / AI / cyber review;
o) required privacy review;
p) required public authority review;
q) required finance-boundary review;
r) required certification or procurement boundary review;
s) required safeguards or protected knowledge review;
t) required public-safe publication review;
u) required repository, register, or gazette update;
v) completion evidence;
w) escalation trigger; and
x) closure record.
Action items shall not create authority beyond the Board decision or delegation from which they arise. An action item is an implementation control, not a standalone authorization.
124.14 Responsible Owner and Deadline Record. Each Board-approved action requiring implementation shall be assigned to a responsible owner unless the action is self-executing. The responsible owner may be a Director, officer, committee, secretariat function, counsel, compliance function, data / AI / cyber function, safeguards function, repository custodian, records custodian, public-safe publication custodian, or other authorized person or body.
The responsible owner record shall identify, as applicable:
a) owner name or office;
b) delegated authority;
c) reporting line;
d) required collaboration;
e) decision limits;
f) budget limits;
g) contract limits;
h) publication limits;
i) data access limits;
j) AI-use limits;
k) public authority communication limits;
l) finance-boundary limits;
m) certification and procurement boundary limits;
n) sponsor and provider interface limits;
o) safeguards limits;
p) completion date;
q) interim reporting date;
r) escalation date; and
s) closure evidence.
Deadlines shall be realistic, risk-aware, and compatible with lawful process. No deadline shall justify bypassing required legal review, Board approval, member approval where required, tax review, conflict review, counsel review, public authority review, data / AI / cyber review, safeguards review, public-safe publication review, or correction pathway.
124.15 Follow-Up Record. The Board shall maintain follow-up records sufficient to show whether Board decisions, resolutions, action items, emergency actions, ratifications, corrections, delegated approvals, committee recommendations, officer reports, audit items, risk items, incident items, legal items, public authority items, data / AI / cyber items, safeguards items, and Nexus-interface items have been completed, deferred, escalated, modified, superseded, withdrawn, or closed.
Follow-up records shall identify, as applicable:
a) status;
b) completion evidence;
c) partial completion;
d) overdue status;
e) extension approval;
f) deferral approval;
g) escalation;
h) Board reconsideration;
i) committee referral;
j) officer referral;
k) counsel referral;
l) compliance referral;
m) public authority review;
n) finance-boundary review;
o) data / AI / cyber review;
p) safeguards review;
q) correction record;
r) supersession record;
s) withdrawal record;
t) archive record; and
u) lessons learned.
A matter shall not be deemed closed merely because it was discussed. Closure shall require completion evidence, competent determination, or recorded deferral, withdrawal, supersession, or archive.
124.16 Correction, Supersession, Withdrawal, or Ratification Record. Where a Board record, resolution, minute, action item, delegation, approval, publication authorization, emergency action, committee report, officer report, public authority reference, technical asset authorization, data / AI / cyber authorization, safeguards determination, or Nexus-interface record is inaccurate, incomplete, unauthorized, ambiguous, stale, superseded, overclaiming, public authority-confusing, finance-overclaiming, certification-overclaiming, procurement-overclaiming, recognition-overclaiming, provider-preferencing, sponsor-controlled, unsafe, or otherwise defective, the Corporation shall create a correction, supersession, withdrawal, or ratification record.
The record shall identify:
a) the original record;
b) the defect or issue;
c) discovery date;
d) person identifying the issue;
e) authority for correction or ratification;
f) review conducted;
g) corrected text or corrected action;
h) superseding record;
i) withdrawn record;
j) retracted record;
k) affected registers;
l) affected repositories;
m) affected gazette or notice entries;
n) affected public materials;
o) affected controlled materials;
p) affected public authority, sponsor, provider, donor, funder, host, participant, GRF, GRA, Nexus, or enterprise interfaces;
q) notice required;
r) limitation language required;
s) legal hold status;
t) archive treatment; and
u) recurrence-prevention action.
Corrections shall preserve historical traceability. No correction shall silently replace the record of what occurred. Superseded, withdrawn, or corrected records shall be marked accordingly and retained or disposed of according to law, policy, legal hold, and retention requirements.
124.17 Secure Storage. Board minutes, resolutions, written consents, action trackers, records, materials, committee reports, officer reports, privileged materials, confidential materials, public authority materials, cyber-sensitive materials, infrastructure-sensitive materials, finance-sensitive materials, commercially sensitive materials, personal information, rights-bearing data, protected knowledge, controlled-room materials, and related Board records shall be stored in secure systems approved for their access class and retention class.
Secure storage shall include, as appropriate:
a) approved repository;
b) role-based access control;
c) identity verification;
d) multi-factor authentication;
e) encryption;
f) logging;
g) audit trail;
h) backup;
i) retention controls;
j) legal hold controls;
k) version control;
l) integrity controls;
m) access review;
n) export restriction;
o) no-download restriction where required;
p) AI-use restriction;
q) deletion control;
r) archival control; and
s) disaster recovery.
Directors, officers, committee members, staff, contractors, advisors, fellows, volunteers, contributors, sponsors, providers, hosts, public authority participants, or other persons shall not store Board records in unauthorized personal drives, private repositories, personal email accounts, unmanaged messaging systems, unapproved AI workspaces, public links, uncontrolled folders, or shadow IT.
124.18 Retention. Board records shall be retained in accordance with applicable law, the Articles or Certificate, this Bylaw, Board-approved retention policy, legal hold requirements, tax and nonprofit requirements, grant requirements, audit requirements, public authority interface requirements, contractual requirements, privacy requirements, cybersecurity requirements, research integrity requirements, protected knowledge requirements, and public-safe publication requirements.
Retention rules shall classify Board records by type and risk, including:
a) minutes;
b) resolutions;
c) written consents;
d) Board materials;
e) privileged materials;
f) legal hold materials;
g) financial materials;
h) tax records;
i) corporate filings;
j) director and officer records;
k) member records where applicable;
l) committee records;
m) conflict and recusal records;
n) compensation records;
o) grant, donation, sponsorship, restricted fund, and support records;
p) public authority records;
q) data / AI / cyber records;
r) incident records;
s) research records;
t) technical asset records;
u) public-safe publication records;
v) safeguards and protected knowledge records;
w) emergency action records;
x) correction records; and
y) archive records.
No Board record subject to legal hold, investigation, audit, public authority obligation, protected knowledge restriction, incident response, correction review, or regulatory-perimeter review shall be destroyed, deleted, altered, overwritten, or anonymized in a manner inconsistent with applicable requirements.
124.19 Board Record Access and Confidentiality. Access to Board records shall be granted only to persons with lawful authority, role-based need, Board authorization, officer delegation, counsel authorization, policy authorization, or other competent record. Access shall be limited by confidentiality class, privilege status, public authority sensitivity, data class, AI-use class, cyber sensitivity, infrastructure sensitivity, finance sensitivity, commercial sensitivity, personal information sensitivity, rights-bearing data sensitivity, protected knowledge sensitivity, safeguards sensitivity, and public-safe publication status.
Board record access may be granted to:
a) Directors;
b) officers;
c) counsel;
d) auditors or reviewers;
e) compliance personnel;
f) records custodians;
g) committee members within scope;
h) secretariat personnel within scope;
i) insurers where appropriate and lawful;
j) public authorities where legally required or authorized;
k) funders or grantors where contractually required and lawful;
l) investigators where authorized;
m) courts or regulators where required; and
n) other persons approved by competent authority.
Access shall not be granted merely because a person is a sponsor, donor, funder, provider, host, public authority participant, advisor, fellow, contributor, contractor, media participant, community participant, public figure, capital reader, national company, Project SPV, Nexus participant, or partner. Access shall not imply governance rights, public authority endorsement, finance-readiness, certification, procurement status, recognition, provider status, sponsor control, or public reliance.
124.20 Board Record Integrity, Audit Trail, and Tamper-Evidence. The Corporation shall maintain Board record integrity through procedures designed to preserve authenticity, completeness, accuracy, traceability, version history, approval status, access history, custody, retention, and correction history.
Record integrity controls may include:
a) official repository designation;
b) custodian assignment;
c) version identifiers;
d) approval status labels;
e) draft labels;
f) adopted labels;
g) superseded labels;
h) withdrawn labels;
i) archived labels;
j) hash, checksum, or tamper-evident reference where used;
k) electronic signature control;
l) metadata control;
m) audit logs;
n) access logs;
o) change logs;
p) legal hold flags;
q) correction flags;
r) privilege flags;
s) confidentiality flags;
t) public-safe flags;
u) AI-generated-material flags;
v) source-lineage references;
w) repository references;
x) backup and restoration records; and
y) deletion or secure disposal records.
No person shall alter, backdate, erase, overwrite, forge, fabricate, conceal, mislabel, unofficially replace, or selectively excerpt Board records in a manner that undermines record integrity. Drafts, AI summaries, working notes, redlines, slides, public explainers, unofficial extracts, translations, repository forks, and derivative communications shall not be treated as official Board records unless adopted, certified, or incorporated through competent process.
124.21 Board Records. The Corporation shall maintain Board Records sufficient to demonstrate lawful governance, fiduciary diligence, public-benefit discipline, nonprofit integrity, tax-exempt or tax-exempt-compatible compliance, mission lock, non-execution, role separation, public authority boundary discipline, finance-boundary discipline, certification and procurement boundary discipline, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, and correctionability.
Board Records shall include, as applicable:
a) meeting notices;
b) waivers of notice;
c) agendas;
d) Board materials;
e) attendance records;
f) quorum records;
g) minutes;
h) draft minutes;
i) approved minutes;
j) resolutions;
k) written consents;
l) vote records;
m) abstention records;
n) conflict disclosure records;
o) recusal records;
p) dissent or minority notes;
q) action item records;
r) responsible owner records;
s) deadline records;
t) follow-up records;
u) ratification records;
v) correction records;
w) supersession records;
x) withdrawal records;
y) retraction and takedown records;
z) archive records;
aa) Board register records;
bb) director register records;
cc) officer interface records;
dd) committee report records;
ee) officer report records;
ff) reserved matter records;
gg) delegation records;
hh) authority matrix records;
ii) policy approval records;
jj) budget approval records;
kk) financial oversight records;
ll) audit or review records;
mm) tax and nonprofit compliance records;
nn) grant, donation, sponsorship, restricted fund, and support records;
oo) public authority interface records;
pp) finance-boundary records;
qq) certification and procurement boundary records;
rr) provider-neutrality records;
ss) sponsor non-control records;
tt) data governance records;
uu) AI governance records;
vv) cybersecurity records;
ww) privacy records;
xx) model, inference, and compute workload oversight records;
yy) research, evidence, methods, observability, ontology, and technical truth oversight records;
zz) public-good software, technical baseline, repository, and secure-release oversight records;
aaa) public-safe publication records;
bbb) civil rights and accessibility records;
ccc) community safeguards records;
ddd) Tribal, Indigenous, local, territorial, cultural, environmental, and protected knowledge records;
eee) grievance, remedy, protected participation, whistleblowing, and non-retaliation records;
fff) emergency decision records;
ggg) break-glass records;
hhh) post-emergency review records;
iii) Board evaluation records;
jjj) Board training records;
kkk) Board succession records;
lll) indemnification, advancement, insurance, and liability protection records;
mmm) legal hold records;
nnn) access logs;
ooo) audit trails;
ppp) secure storage records;
qqq) retention and disposal records;
rrr) repository and gazette records; and
sss) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that Board records are not administrative residue. They are the legal memory, fiduciary proof, institutional boundary, correction pathway, and validity architecture of the Corporation. The Corporation shall govern by competent record, not by informal recollection, slide narrative, public statement, AI summary, repository artifact, dashboard state, proof receipt, ledger entry, or operational habit. Every material Board act shall be recorded, bounded, reviewable, secure, traceable, and correctionable, and no Board record shall be used to create authority beyond the lawful action it actually evidences.
Section 125. Board Evaluation, Training, Succession, Refreshment, and Fiduciary Development
125.1 Board Evaluation Purpose. The Board shall maintain a disciplined process for evaluating its own performance, composition, independence, fiduciary effectiveness, strategic judgment, legal compliance, public-benefit stewardship, nonprofit discipline, risk oversight, records discipline, public authority boundary control, finance-boundary control, certification and procurement boundary control, provider neutrality, sponsor non-control, data / AI / cyber oversight, safeguards oversight, Nexus alignment, and correctionability.
Board evaluation shall not be treated as a ceremonial governance exercise. It shall be a substantive mechanism for preserving the Corporation’s lawful nonprofit character, public-good technical institution role, United States and North America anchor discipline, non-execution perimeter, public trust, and capacity to govern exponential and mission-critical technologies with maturity.
The Board evaluation process may assess, without limitation: a) whether the Board is exercising fiduciary duties with care, loyalty, obedience to mission, independence, informed judgment, and appropriate challenge; b) whether Board composition includes the governance, legal, nonprofit, public-benefit, technical, data, AI, cyber, public authority, finance-boundary, safeguards, research, evidence, observability, ontology, public-good software, community, and Nexus interface competence needed for the Corporation’s role; c) whether Board deliberations are sufficiently prepared, documented, confidential, conflict-managed, public-safe, and boundary-aware; d) whether Board decisions are implemented through responsible owners, action items, records, deadlines, follow-up, correction, and review; e) whether Board materials, minutes, resolutions, consents, emergency decisions, committee reports, officer reports, and Nexus interface records demonstrate validity-by-record; and f) whether the Board has resisted mission drift, sponsor control, provider preference, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, public warning confusion, emergency command confusion, and enterprise execution pressure.
The Board shall determine the timing, format, confidentiality class, and responsible owner for Board evaluation, provided that evaluation shall occur at intervals sufficient to maintain institutional seriousness and shall be recorded in accordance with this Bylaw.
125.2 Individual Director Evaluation. The Board may establish processes for evaluating individual Director performance, participation, preparedness, independence, confidentiality compliance, conflict disclosure, committee contribution, fiduciary conduct, attendance, judgment, institutional discipline, and adherence to this Bylaw.
Individual Director evaluation may consider whether a Director: a) attends and prepares for Board and committee meetings; b) reviews materials with appropriate care and confidentiality; c) discloses conflicts, dual roles, related-party matters, sponsor relationships, provider relationships, public authority relationships, financial relationships, and other relevant interests; d) respects recusal, access restriction, controlled-room, data-room, privilege, confidentiality, and information governance rules; e) contributes constructively to strategy, risk, legal compliance, technical governance, public-good stewardship, community safeguards, and correctionability; f) avoids unauthorized public statements, authority inflation, external representation, sponsor-driven conduct, provider-driven conduct, public authority confusion, and side-channel influence; and g) participates in required training and continuing fiduciary development.
Individual Director evaluation shall be conducted with fairness, confidentiality, non-retaliation, and respect for dissent. A Director shall not be penalized for good-faith disagreement, minority view, lawful whistleblowing, protected participation, conflict disclosure, safeguards escalation, public-safe correction request, or insistence on legal review.
Where evaluation identifies material concern, the Board may require mentoring, training, role adjustment, committee reassignment, access restriction, conflict mitigation, recusal reinforcement, corrective action, non-renewal, resignation request, removal where lawful, or other action consistent with this Bylaw and applicable law.
125.3 Chair, Officer, Committee Chair, and Governance Leadership Evaluation. The Board shall evaluate, or cause the appropriate body to evaluate, the performance of the Chair, Vice-Chair, committee chairs, Board officers, and other governance leadership roles to ensure that leadership powers are exercised within lawful authority, with procedural fairness, records discipline, mission fidelity, and respect for Board collective authority.
Leadership evaluation shall assess whether governance leaders: a) preserve Board process, quorum, notice, agenda discipline, voting discipline, conflict discipline, and minute integrity; b) support informed deliberation without suppressing dissent or over-directing outcomes; c) protect privilege, confidentiality, controlled-room boundaries, data-room boundaries, public authority boundaries, and cyber-sensitive materials; d) escalate legal, tax, compliance, regulatory-perimeter, public authority, finance-boundary, certification-boundary, procurement-boundary, data / AI / cyber, safeguards, competition, protected knowledge, and professional-boundary issues when required; e) prevent sponsor, provider, donor, funder, host, public authority, national company, Project SPV, or enterprise-stack pressure from controlling Board process; f) preserve the distinction between Board governance, officer implementation, committee recommendation, public authority participation, Nexus interface support, and enterprise execution; and g) ensure that emergency and break-glass powers are used only as protective, time-boxed, record-supported, ratifiable, and sunset-bound measures.
No governance leadership role shall become personal control of the Corporation, founder control, sponsor control, provider control, public authority control, technical-team control, donor control, or informal executive authority beyond the Board’s lawful structure.
125.4 Board Skills Matrix. The Board shall maintain or approve a Board skills, competence, and composition matrix to identify the capabilities needed for effective oversight of the Corporation’s mission, legal obligations, public-good technical function, and Nexus interfaces.
The skills matrix may include competence in: a) nonprofit governance, fiduciary duties, United States corporate law, tax-exempt or tax-exempt-compatible governance, public-benefit law, charitable solicitation, fundraising controls, restricted funds, and private benefit controls; b) legal compliance, regulatory-perimeter discipline, public authority boundary discipline, finance-boundary discipline, procurement neutrality, certification boundaries, recognition boundaries, professional boundaries, sanctions, export-control, competition, privacy, data protection, civil rights, accessibility, employment, and government ethics; c) research integrity, evidence doctrine, methods stewardship, observability methods, ontology, technical truth, public-safe publication, verifiable compute, verifiable intelligence, public-good software, open technical baselines, repository governance, secure release, and correctionability; d) data governance, AI governance, cybersecurity, secure compute, sovereign compute, model registers, inference records, compute workload records, incident response, business continuity, and disaster recovery; e) public authority learning, emergency-management learning, regulator-listening rooms, public finance reader rooms, public infrastructure operator interfaces, controlled rooms, clean rooms, evidence rooms, data rooms, public authority rooms, and no-download rooms; f) community safeguards, Tribal and Indigenous protocol respect, protected knowledge, public-safe mapping, civil rights, accessibility, grievance, remedy, protected participation, non-retaliation, and do-no-harm review; and g) Nexus architecture, GCRI Canada coordination, The Global Risks Forum (GRF) interface discipline, The Global Risks Alliance (GRA) interface discipline, Nexus Standards, Nexus Observatory, Nexus Network, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, providers, sponsors, hosts, and enterprise-stack separation.
The skills matrix shall guide recruitment, nomination, appointment, training, committee assignments, succession planning, external advisor use, and Board development. It shall not be used to create protected seats, sponsor seats, provider seats, public authority seats, investor seats, or entitlement to Board service unless lawfully established in the Articles or Certificate, this Bylaw, or a competent record.
125.5 Director Training and Onboarding. Each Director shall receive onboarding appropriate to the Corporation’s legal status, public-benefit mission, nonprofit character, governance architecture, fiduciary duties, records discipline, confidentiality obligations, conflict rules, non-execution perimeter, public authority boundaries, finance boundaries, certification and procurement boundaries, data / AI / cyber controls, safeguards, and Nexus role separation.
Director onboarding shall include, as appropriate: a) the Articles or Certificate, this Bylaw, Board charter or governance policy, committee charters, authority matrix, delegation matrix, conflict policy, confidentiality policy, records policy, and public-safe notice discipline; b) the Corporation’s public-good technical institution role as evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, verifiable compute and intelligence methods, public authority learning, and safeguards steward; c) the distinction among GCRI US, GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, providers, sponsors, hosts, public authorities, universities, laboratories, communities, and enterprise actors; d) the Non-Execution Doctrine, Validity-by-Record Doctrine, Correctionability Doctrine, One Rail / Two Stacks Doctrine, Verifiable Compute and Verifiable Intelligence Doctrine, and Public-Good Stack Framework discipline; e) legal, tax, compliance, privacy, AI, cybersecurity, sanctions, export-control, competition, lobbying, government ethics, public authority, professional-boundary, and research ethics controls; and f) emergency governance, break-glass limits, stop-the-line authority, public-safe publication, protected knowledge handling, grievance and remedy, non-retaliation, and correction pathways.
A Director shall not be granted access to highly restricted Board materials, controlled-room materials, public authority materials, cyber-sensitive materials, infrastructure-sensitive materials, protected knowledge, finance-sensitive materials, privileged materials, or data-room materials until required acknowledgments, training, identity verification, confidentiality commitments, and access classifications have been completed where required.
125.6 Continuing Fiduciary Development. The Board shall provide, require, or approve continuing fiduciary development for Directors at intervals appropriate to the Corporation’s maturity, risk profile, technical scope, public authority interfaces, Nexus interfaces, legal obligations, and public-benefit mission.
Continuing fiduciary development may address: a) fiduciary duties, nonprofit law, tax compliance, charitable solicitation, private benefit, inurement, restricted funds, sponsorship, grants, donor relations, and anti-capture; b) public authority engagement, public records sensitivity, procurement integrity, lobbying, government ethics, public finance reader discipline, regulator-listening discipline, emergency-management learning boundaries, and no-public-authority-substitution rules; c) securities, investment adviser, broker-dealer, finder, banking, lending, insurance, underwriting, rating, public finance, procurement, certification, recognition, professional-boundary, and enterprise execution boundaries; d) data governance, privacy, AI governance, cybersecurity, model governance, inference records, agentic AI, secure release, repository security, SBOM, vulnerability management, incident response, and disaster recovery; e) research integrity, evidence quality, methods stewardship, observability, ontology, technical truth, public-safe publication, Nexus Truth Engine methods, Nexus Observatory methods, proof receipts, Docket support, Grid support, GRF-facing inputs, and GRA-facing technical inputs; and f) Tribal and Indigenous protocol respect, Indigenous data safeguards, protected knowledge, public-safe mapping, civil rights, accessibility, grievance, remedy, protected participation, non-retaliation, and stop-the-line escalation.
The Board may require targeted training for Directors serving on committees, entering controlled rooms, reviewing public authority materials, approving public-safe publications, reviewing finance-adjacent materials, reviewing AI systems, reviewing cyber incidents, reviewing protected knowledge, or supervising Nexus interfaces.
125.7 Succession Planning. The Board shall oversee succession planning for Directors, the Chair, Vice-Chair, committee chairs, officers, critical governance roles, records custodians, repository custodians, data / AI / cyber oversight roles, safeguards oversight roles, public-safe publication roles, and other roles necessary for continuity of governance.
Succession planning shall address, as applicable: a) expected vacancies, term limits, resignations, removals, incapacity, emergency vacancies, loss of eligibility, conflict-driven limitations, recusal-heavy directors, and committee continuity; b) continuity of fiduciary knowledge, institutional memory, legal knowledge, technical knowledge, public authority relationships, Nexus interface discipline, records discipline, and safeguards knowledge; c) leadership development, committee pipeline, chair succession, officer succession, emergency governance coverage, and acting-role designation; d) avoidance of founder dependency, sponsor dependency, provider dependency, donor dependency, public authority dependency, technical-team dependency, single-expert dependency, and institutional key-person risk; e) preservation of diversity of competence, geography, sectoral knowledge, public-benefit orientation, technical literacy, legal discipline, community safeguards capacity, and independence; and f) records sufficient to demonstrate that succession was managed through lawful, independent, mission-aligned, anti-capture, and non-retaliatory processes.
Succession planning shall not create an entitlement to office. No Director, officer, founder, sponsor, provider, donor, funder, host, public authority participant, university, laboratory, national company, Project SPV, consortium, or enterprise actor shall possess succession rights unless expressly provided by law, the Articles or Certificate, this Bylaw, or a competent record.
125.8 Board Refreshment and Composition Discipline. The Board shall maintain processes to support periodic refreshment, renewal, and composition discipline, while preserving continuity, institutional memory, mission lock, legal discipline, technical competence, public-good stewardship, and independence.
Board refreshment may include: a) recruitment of new Directors with needed competence; b) renewal or non-renewal of Directors according to term and performance criteria; c) transition planning for outgoing Directors; d) committee rotation where appropriate; e) leadership rotation where appropriate; f) advisory support where Board competence gaps exist but Board membership is not appropriate; g) removal or non-renewal where independence, conduct, attendance, confidentiality, conflict, competence, mission alignment, or fiduciary concerns warrant lawful action; and h) succession records, recruitment records, nomination records, evaluation records, and transition records.
Refreshment shall not be used to remove Directors for good-faith dissent, protected participation, lawful whistleblowing, safeguards escalation, conflict disclosure, insistence on public-safe correction, request for legal review, or refusal to support overclaim. Refreshment shall not be manipulated to create sponsor control, provider control, founder control, donor control, funder control, public authority control, investor control, national company control, Project SPV control, or enterprise-stack control.
125.9 Independence and Capture Review in Board Composition. The Board shall periodically review whether its composition, leadership, committee assignments, funding relationships, external affiliations, sponsor relationships, provider relationships, public authority relationships, national company relationships, Project SPV relationships, university relationships, laboratory relationships, donor relationships, funder relationships, host relationships, investor relationships, insurer relationships, lender relationships, and enterprise-stack relationships preserve independence and resist capture.
The review shall consider: a) whether any person or group can control or unduly influence Board decisions; b) whether support arrangements, funding concentration, technical dependency, repository dependency, data dependency, public authority dependency, sponsor dependency, provider dependency, or host dependency creates structural risk; c) whether Directors’ outside roles create unmanaged dual-role, conflict, recusal, confidentiality, competition, public authority, finance-boundary, certification-boundary, procurement-boundary, or recognition-boundary risk; d) whether Board composition overrepresents or underrepresents material competence, stakeholder, technical, legal, safeguards, or public-good perspectives needed for the Corporation’s role; and e) whether any Board practice creates appearance of pay-to-play, access-for-money, recognition purchase, finance-readiness purchase, certification purchase, procurement advantage, provider preference, or sponsor entitlement.
Where capture risk exists, the Board shall adopt mitigation, including disclosure, recusal, access restriction, independent review, committee restructuring, support diversification, role limitation, leadership change, recruitment, non-renewal, resignation request, removal where lawful, refusal or return of support, or public-safe clarification.
125.10 Committee and Council Competence Review. The Board shall ensure that Board committees, advisory councils, scientific panels, expert panels, public authority forums, working groups, Nexus interface groups, and other governance-support bodies have appropriate competence, independence, mandate clarity, records discipline, conflict controls, confidentiality controls, and boundary awareness.
Committee and council competence review shall consider whether the body has: a) a clear charter, scope, authority, limitation, reporting line, and sunset or review cycle; b) appropriate subject-matter competence for its mandate; c) appropriate legal, compliance, data / AI / cyber, public authority, finance-boundary, safeguards, and public-safe publication support where relevant; d) appropriate conflict, recusal, competition, sponsor non-control, provider-neutrality, confidentiality, and controlled-room rules; e) appropriate records, minutes, decisions, recommendations, dissent records, action items, and correction pathways; and f) no authority inflation beyond recommendation, review, advice, oversight support, or delegated authority lawfully granted.
No committee, council, panel, forum, working group, expert body, technical team, or Nexus interface body shall substitute for the Board unless the Board has lawfully delegated a matter within permissible limits and the delegation is recorded.
125.11 External Advisor and Expert Use. The Board may use external advisors, counsel, auditors, technical experts, scientific experts, public authority experts, safeguards experts, AI experts, cybersecurity experts, privacy experts, research ethics experts, competition experts, finance-boundary experts, insurance-boundary experts, procurement-boundary experts, community advisors, Tribal or Indigenous protocol advisors, and other specialists to support Board understanding and fiduciary judgment.
External advisor use shall be governed by: a) clear scope of engagement; b) independence and conflict review; c) confidentiality and privilege treatment where applicable; d) data / AI / cyber, privacy, public authority, protected knowledge, and controlled-room restrictions; e) competition and antitrust discipline; f) sponsor, provider, donor, funder, host, national company, Project SPV, and enterprise-stack relationship review; g) deliverable classification, reliance limitation, and public-safe treatment; and h) records of appointment, advice received, limitations, conflicts, fees, and closeout.
Advice from an external advisor shall inform Board judgment but shall not replace Board responsibility. No advisor shall be treated as a Director, officer, public authority decision-maker, certifier, recognizer, finance-readiness authority, procurement authority, provider selector, sponsor representative, or enterprise execution actor by reason of advice.
125.12 Board Culture and Fiduciary Conduct. The Board shall cultivate a governance culture of seriousness, preparation, independence, lawful candor, constructive challenge, records discipline, public-benefit loyalty, technical humility, safeguards awareness, and willingness to correct.
Board culture shall support: a) informed deliberation without domination; b) dissent without retaliation; c) urgency without perimeter breach; d) technical ambition without authority inflation; e) public authority engagement without public authority substitution; f) capital literacy without investment advice or finance execution; g) public-safe communication without public warning or emergency command; h) open technical stewardship without uncontrolled release or enclosure; i) sponsor and provider participation without control or preference; and j) correction without concealment.
No Board culture, leadership style, founder influence, sponsor influence, provider influence, public authority influence, technical prestige, academic prestige, donor relationship, funding need, media pressure, or operational habit shall supersede the Articles or Certificate, this Bylaw, fiduciary duties, legal compliance, non-execution, validity-by-record, or correctionability.
125.13 Evaluation, Training, Succession, and Fiduciary Development Records. The Corporation shall maintain Evaluation, Training, Succession, and Fiduciary Development Records sufficient to demonstrate that Board performance, Director performance, leadership performance, Board composition, competence, independence, training, succession, refreshment, committee competence, external advisor use, and fiduciary culture have been reviewed, improved, corrected, and preserved.
Such records shall include, as applicable: a) Board evaluation records; b) individual Director evaluation records; c) Chair, Vice-Chair, committee chair, and governance leadership evaluation records; d) skills matrix records; e) competence gap records; f) recruitment records; g) nomination records; h) appointment records; i) reappointment records; j) non-renewal records; k) resignation records; l) removal records where applicable; m) onboarding records; n) training records; o) continuing fiduciary development records; p) committee competence records; q) council competence records; r) succession plans; s) emergency succession records; t) leadership transition records; u) independence and capture review records; v) conflict and recusal records; w) external advisor engagement records; x) confidentiality acknowledgments; y) controlled-room access training records; z) data / AI / cyber training records; aa) public authority boundary training records; bb) finance-boundary, certification-boundary, procurement-neutrality, recognition-boundary, provider-neutrality, and sponsor non-control training records; cc) safeguards, protected knowledge, civil rights, accessibility, grievance, remedy, protected participation, and non-retaliation training records; dd) corrective action records; ee) mentoring, role adjustment, committee reassignment, access restriction, or training requirement records; ff) Board culture review records; gg) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that Board capacity is itself a public-good control. The Corporation cannot preserve its mission, legal status, evidence integrity, technical credibility, public authority boundaries, finance boundaries, safeguards, Nexus role separation, and correctionability unless the Board remains competent, independent, trained, refreshed, and record-disciplined. Board evaluation, training, succession, and fiduciary development shall therefore be treated as continuing governance duties, not optional institutional housekeeping.
Section 126. Board Continuity, Succession, Continuity Packs, and Emergency Succession
126.1 Board Continuity Purpose. The Board shall maintain continuity arrangements sufficient to preserve lawful governance, fiduciary oversight, public-benefit purpose, nonprofit character, tax-exempt or tax-exempt-compatible discipline, mission lock, non-execution, records integrity, public authority boundary discipline, finance-boundary discipline, certification and procurement boundary discipline, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, Nexus role separation, and correctionability during ordinary transition, planned succession, vacancy, incapacity, resignation, removal, emergency disruption, system failure, leadership transition, or other continuity event.
Board continuity shall not be treated as a personnel preference or internal convenience. It is a governance control necessary to ensure that the Corporation remains capable of acting through competent authority, lawful records, informed fiduciary judgment, secure access, and role-separated decision-making even when individual Directors, officers, committee chairs, custodians, advisors, or technical stewards are unavailable.
The Board continuity system shall preserve: a) lawful Board authority and quorum capability; b) continuity of reserved-matter oversight; c) continuity of Board records, minutes, resolutions, written consents, registers, and official repositories; d) continuity of legal, tax, compliance, data / AI / cyber, public authority, finance-boundary, certification-boundary, procurement-boundary, safeguards, and protected knowledge oversight; e) continuity of GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortium, national company, Project SPV, provider, sponsor, host, public authority, university, laboratory, community, and enterprise-stack interface discipline; and f) continuity of correction, withdrawal, supersession, retraction, takedown, quarantine, legal hold, public-safe notice, and emergency governance pathways.
No continuity arrangement shall create founder control, sponsor control, provider control, donor control, public authority control, officer control, committee control, advisor control, technical-team control, emergency-control habit, or informal governance outside the Board’s lawful authority.
126.2 Director Succession Planning. The Board shall maintain Director succession planning appropriate to the Corporation’s size, legal status, public-benefit mission, risk profile, technical scope, public authority interfaces, Nexus interfaces, and governance maturity.
Director succession planning shall address expected and unexpected changes in Board composition, including: a) end of term; b) resignation; c) removal; d) death; e) incapacity; f) loss of eligibility; g) persistent non-attendance; h) conflict-driven inability to serve effectively; i) confidentiality or conduct concern; j) material change in independence; k) legal disqualification; l) emergency vacancy; and m) expansion or rebalancing of Board competence.
The Board shall use succession planning to preserve competence, independence, fiduciary seriousness, continuity of institutional memory, and coverage of material oversight domains. Those domains include nonprofit governance, tax status, public-benefit law, data governance, AI governance, cybersecurity, privacy, public authority learning, finance-boundary discipline, research integrity, evidence methods, observability, ontology, public-good software, open technical baselines, safeguards, protected knowledge, civil rights, accessibility, competition, sanctions, export-control, and Nexus role separation.
Director succession planning shall not create entitlement to Board service. No founder, donor, sponsor, provider, host, funder, public authority participant, national company, Project SPV, investor, insurer, lender, university, laboratory, community, committee, council, technical team, or external actor shall possess a right to nominate, appoint, renew, veto, or replace a Director unless that right is expressly created by applicable law, the Articles or Certificate, this Bylaw, or a competent Board-approved record.
126.3 Officer Succession Interface. The Board shall oversee the interface between Board continuity and officer succession, recognizing that officer continuity may be necessary for legal filings, financial administration, records custody, repository control, public authority interfaces, controlled rooms, data / AI / cyber systems, public-safe publication, safeguards, and emergency response.
Officer succession interface planning shall ensure that, for each material officer role, the Board understands: a) the office’s lawful authority; b) the office’s delegation limits; c) the office’s records and systems access; d) the office’s key dependencies; e) the office’s critical deadlines; f) the office’s backup or acting-role pathway; g) the office’s conflict and confidentiality constraints; h) the office’s emergency authority, if any; and i) the process for Board review, appointment, ratification, continuation, limitation, or termination of acting service.
The Board shall not allow officer succession arrangements to convert officer implementation authority into Board governance authority. An acting officer, interim officer, emergency officer, delegated officer, consultant, contractor, advisor, founder, or technical steward shall not exercise Board reserved matters unless separately and lawfully authorized by the Board and applicable law.
Where officer succession affects legal compliance, financial controls, tax status, registered agent or filing obligations, bank access, public authority interfaces, data / AI / cyber systems, protected knowledge, controlled rooms, repositories, or Nexus interfaces, the Board shall require heightened records, access-control, and conflict review.
126.4 Committee Leadership Succession. The Board shall ensure that each standing committee, special committee, Board committee, advisory committee, council-interface committee, risk committee, audit or finance committee where established, governance committee, data / AI / cyber committee, safeguards committee, public-safe publication committee, research or technical committee, or other Board-created body has appropriate leadership continuity.
Committee leadership succession shall address: a) chair succession; b) vice-chair or deputy-chair function where established; c) acting chair authority; d) committee quorum continuity; e) continuity of committee records; f) continuity of restricted-material access; g) continuity of committee reporting to the Board; h) conflict-driven recusal of committee leadership; i) emergency committee action; and j) sunset, renewal, or reconstitution of committee leadership.
A committee leadership transition shall not expand the committee’s mandate, alter its charter, convert recommendation authority into decision authority, waive Board reserved matters, or alter public authority, finance, certification, procurement, provider-neutrality, sponsor non-control, data / AI / cyber, safeguards, or Nexus boundary controls.
Where a committee’s work involves privileged materials, public authority materials, cyber-sensitive materials, infrastructure-sensitive materials, finance-sensitive materials, personal information, rights-bearing data, protected knowledge, controlled-room materials, data-room materials, or public-safe publication review, committee leadership succession shall include secure handover and access revalidation.
126.5 Chair Succession. The Board shall maintain a Chair succession procedure to preserve lawful Board convening authority, meeting continuity, agenda continuity, emergency decision routing, public-facing governance stability, and continuity of fiduciary leadership.
Chair succession planning shall identify: a) the ordinary process for Chair appointment or election; b) the term or review cycle applicable to the Chair; c) the role of the Vice-Chair where one exists; d) the process for acting Chair designation; e) the process for Chair resignation, removal, incapacity, conflict restriction, or temporary unavailability; f) limitations on Chair authority; g) Board reserved matters that remain with the full Board; and h) records required to evidence any Chair transition.
The Chair shall not possess personal ownership of the Corporation’s mission, Board agenda, public authority relationships, sponsor relationships, provider relationships, Nexus interfaces, technical architecture, public-safe publications, records, repositories, or emergency powers. Chair succession shall therefore be structured to prevent personal dependency, founder dependency, sponsor dependency, provider dependency, public authority dependency, or technical-team dependency.
No Chair transition shall be used to suppress dissent, avoid conflict review, bypass Board evaluation, evade accountability, accelerate sponsor or provider influence, soften non-execution boundaries, or create informal executive control.
126.6 Emergency Chair Succession. Where the Chair is unavailable, incapacitated, conflicted, recused, suspended, deceased, removed, unreachable, or unable to act during an urgent matter, the Board may activate emergency Chair succession in accordance with applicable law, the Articles or Certificate, this Bylaw, Board policy, or a competent emergency governance record.
Emergency Chair succession may route temporary presiding authority to: a) the Vice-Chair; b) another Director designated by Board resolution; c) a committee chair within limited scope; d) the most senior eligible independent Director under an approved succession rule; or e) another person permitted by law and expressly authorized by the Board for limited procedural purposes.
Emergency Chair authority shall be limited to convening, presiding, routing, protecting records, preserving privilege, activating emergency Board procedures, ensuring notice, maintaining meeting order, and facilitating lawful Board action. Emergency Chair authority shall not include unilateral power to amend the Articles or Certificate, amend this Bylaw, alter mission lock, approve prohibited functions, waive reserved matters, approve conflicted transactions, issue public warnings, command emergencies, approve finance-readiness, issue certification, approve procurement, recognize status, select providers for public authorities, or bind the Corporation outside recorded authority.
Emergency Chair succession shall be recorded promptly and shall identify the trigger, authority, temporary role-holder, duration, affected matters, limitations, Board notice, ratification pathway, and sunset.
126.7 Emergency Board Continuity. The Board may maintain emergency continuity procedures to preserve governance where a disruption materially affects the Board’s ability to meet, deliberate, vote, access records, receive notice, preserve quorum, protect systems, maintain legal compliance, respond to incidents, or exercise fiduciary oversight.
Emergency Board continuity may be activated for: a) cyber incident; b) data breach; c) AI incident; d) repository compromise; e) public authority confusion; f) legal deadline; g) public-safe publication emergency; h) protected knowledge or safeguards emergency; i) physical disaster; j) communications outage; k) Board portal failure; l) records-system failure; m) loss of quorum due to emergency; n) simultaneous vacancy or incapacity; o) litigation or investigation emergency; p) public authority or regulatory notice requirement; or q) any comparable event affecting lawful governance continuity.
Emergency Board continuity procedures may permit alternative meeting methods, secure emergency notice, temporary access controls, emergency written consents where lawful, temporary repository access, emergency counsel engagement, records preservation, continuity of bank and filing authority, temporary committee routing, and emergency ratification procedures.
Emergency continuity shall remain protective and procedural. It shall not create a new governance constitution, expand corporate purposes, authorize execution, waive non-execution, bypass required approvals, weaken safeguards, or permit indefinite emergency governance.
126.8 Continuity Packs. The Corporation shall maintain Board Continuity Packs for material Board, officer, committee, records, repository, legal, financial, data / AI / cyber, public authority, safeguards, public-safe publication, and Nexus interface functions where continuity of knowledge, authority, access, or records is necessary.
A Continuity Pack may include: a) role description; b) authority source; c) delegation limits; d) current responsible owner; e) alternate responsible owner; f) key records; g) key registers; h) key repositories; i) key deadlines; j) critical contacts; k) access requirements; l) emergency procedures; m) unresolved action items; n) open legal, compliance, finance, data / AI / cyber, public authority, safeguards, public-safe publication, or Nexus issues; o) correction, supersession, withdrawal, retraction, takedown, quarantine, legal hold, or incident status; and p) handover checklist.
Continuity Packs shall be classified according to content sensitivity. A Continuity Pack may contain privileged, confidential, cyber-sensitive, infrastructure-sensitive, finance-sensitive, personal, rights-bearing, public authority-sensitive, sponsor-sensitive, provider-sensitive, research-sensitive, protected knowledge, or controlled-room materials. Access shall be limited accordingly.
No Continuity Pack shall be treated as an independent delegation of authority. It is an information-governance and continuity instrument only unless a competent record expressly grants authority.
126.9 Board Knowledge Transfer. The Board shall ensure that knowledge transfer occurs when Directors, officers, committee chairs, records custodians, repository custodians, data / AI / cyber custodians, public authority interface leads, safeguards leads, public-safe publication leads, technical stewards, or Nexus interface leads transition into or out of material roles.
Knowledge transfer shall preserve: a) institutional history; b) current risks; c) unresolved decisions; d) legal commitments; e) restricted fund obligations; f) public authority interface status; g) sponsor, donor, funder, provider, host, and enterprise-stack limitations; h) data / AI / cyber posture; i) public-safe publication status; j) safeguards and protected knowledge context; k) research and evidence limitations; l) repository and technical asset status; m) GRF-facing and GRA-facing input status; n) Nexus interface status; and o) correction and incident history.
Knowledge transfer shall be structured, recorded, confidentiality-preserving, privilege-preserving, and public-safe. It shall not be conducted through informal oral-only handover where material governance, legal, technical, financial, public authority, data / AI / cyber, safeguards, or Nexus risk would be lost.
Departing persons shall not retain Board materials, confidential information, privileged materials, protected knowledge, keys, credentials, tokens, repository access, controlled-room access, data-room access, Board portal access, or public authority materials except where lawful and expressly authorized.
126.10 Key Records Access Continuity. The Board shall ensure continuity of access to key records necessary for lawful governance, compliance, fiduciary oversight, emergency response, audit, legal defense, public-safe correction, and institutional memory.
Key records access continuity shall include, as applicable: a) Articles or Certificate; b) Bylaw and amendments; c) Board minutes and resolutions; d) written consents; e) director and officer registers; f) member records where applicable; g) committee records; h) authority and delegation matrices; i) policy and protocol registers; j) financial records; k) tax records; l) grant, donation, sponsorship, restricted fund, and support records; m) legal and privileged records; n) public authority interface records; o) data / AI / cyber records; p) research, evidence, methods, observability, ontology, and technical asset records; q) public-safe publication and correction records; r) safeguards and protected knowledge records; s) repository and software release records; t) emergency decision and break-glass records; and u) Nexus interface records.
Access continuity shall be achieved through secure custodianship, alternate custodians, role-based permissions, emergency access procedures, access logs, legal hold controls, backup and recovery, identity controls, and periodic access review.
No single person, device, password, cloud account, vendor, repository administrator, founder, officer, Director, contractor, sponsor, provider, public authority participant, or technical steward shall be the sole practical gatekeeper for records necessary to the Corporation’s legal continuity.
126.11 Legal, Financial, Data / AI / Cyber, Public Authority, Safeguards, and Nexus Interface Continuity. The Board shall ensure continuity of the Corporation’s most consequential oversight domains. Continuity in those domains shall be planned, documented, and periodically reviewed because failure in any one of them may impair lawful existence, public trust, tax status, public authority relationships, data integrity, cybersecurity, community protection, or Nexus compatibility.
Continuity planning shall address: a) legal continuity, including counsel contact, registered agent matters, filings, litigation, investigations, legal holds, contract deadlines, charitable solicitation status where applicable, and state or territorial qualification matters; b) financial continuity, including bank access, financial controls, spending authority, payroll, accounts payable, restricted funds, grant compliance, audit or review requirements, insurance, reserves, and fraud controls; c) data / AI / cyber continuity, including system access, incident response, model registers, inference records, compute workload records, repository security, credential management, backup, disaster recovery, vendor access, and secure release controls; d) public authority continuity, including capacity classification, public authority room controls, emergency-management learning boundaries, regulator-listening records, public finance reader records, public authority data contribution records, and no-official-adoption language; e) safeguards continuity, including protected knowledge restrictions, civil rights matters, accessibility commitments, public-safe mapping controls, grievance and remedy pathways, protected participation, whistleblower protections, non-retaliation, and stop-the-line pathways; and f) Nexus interface continuity, including GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, providers, sponsors, hosts, public authorities, universities, laboratories, communities, and enterprise-stack actors.
Continuity in any domain shall preserve role separation. No continuity measure shall transform the Corporation into a public authority, finance actor, certification body, procurement actor, provider, operator, national company, Project SPV, sponsor-controlled vehicle, or enterprise execution body.
126.12 Repository and Register Continuity. The Board shall ensure continuity of official repositories, registers, gazette or notice streams, technical repositories, software repositories, evidence registers, method registers, model registers, inference records, compute workload records, proof receipt records, public-safe publication registers, correction registers, controlled vocabulary registers, delegation registers, policy registers, protocol registers, risk registers, incident registers, and Nexus interface registers.
Repository and register continuity shall require: a) designated custodian; b) alternate custodian; c) access class; d) publication class; e) retention class; f) backup and recovery procedure; g) access review; h) administrator succession; i) credential and key continuity; j) versioning; k) audit trail; l) correction pathway; m) legal hold treatment; and n) archive procedure.
The Board shall prohibit repository or register arrangements that make institutional validity dependent on personal accounts, uncontrolled forks, unmanaged drives, vendor lock-in without exit controls, unrecorded administrators, undocumented credentials, sponsor-controlled infrastructure, provider-controlled infrastructure without safeguards, or public authority-controlled infrastructure inconsistent with legal separateness.
Where a repository or register continuity risk is identified, the Corporation shall mitigate through migration, backup, administrator rotation, credential reset, custodian designation, documentation, access restriction, vendor review, legal review, cybersecurity review, or Board action.
126.13 Crisis Governance Continuity. The Board shall maintain crisis governance continuity procedures for circumstances in which ordinary governance systems are materially impaired but the Corporation must still preserve lawful existence, fiduciary oversight, records integrity, public-safe discipline, and safeguards.
Crisis governance continuity may include: a) emergency Board meeting protocol; b) emergency notice protocol; c) secure alternate communications; d) emergency quorum assessment; e) emergency written consent process where lawful; f) emergency chair succession; g) emergency counsel engagement; h) emergency financial authority within limits; i) emergency repository access; j) emergency public-safe publication hold; k) emergency cyber incident response; l) emergency data breach response; m) emergency public authority boundary correction; n) emergency protected knowledge hold; o) emergency conflict and recusal review; p) emergency Board ratification process; and q) post-crisis review.
Crisis governance shall be governed by the most restrictive lawful interpretation where authority, safety, public reliance, public authority meaning, finance meaning, certification meaning, procurement meaning, recognition meaning, data / AI / cyber risk, or protected knowledge risk is unclear.
Crisis governance shall not authorize the Corporation to issue official public warnings, command emergencies, regulate, approve procurement, approve public finance, solicit securities, advise investments, lend, insure, underwrite, rate, certify, recognize, select providers for public authorities, or execute enterprise projects.
126.14 Board Vacancy Contingency. The Board shall maintain vacancy contingency procedures to preserve lawful governance where one or more Director vacancies occur.
Vacancy contingency planning shall address: a) remaining Director authority under applicable law and governing instruments; b) quorum effects; c) committee composition effects; d) conflict and recusal effects; e) reserved matter effects; f) urgent appointment or election procedures; g) member approval requirements where applicable; h) temporary committee reassignments; i) public authority interface effects; j) bank, filing, records, repository, and signature authority effects; k) legal, tax, compliance, data / AI / cyber, safeguards, and Nexus oversight effects; and l) public description and notice requirements where applicable.
Where vacancies materially impair Board independence, competence, quorum, committee function, conflict management, legal compliance, financial control, public authority boundary control, data / AI / cyber oversight, safeguards, or Nexus interface oversight, the Board shall prioritize lawful replacement, temporary mitigation, delegation review, committee restructuring, external advisor support, or emergency governance measures.
No vacancy shall be used to concentrate power in a remaining Director, founder, officer, sponsor, provider, donor, funder, public authority participant, national company, Project SPV, technical team, or external actor beyond lawful authority.
126.15 Minimum Governance Operations During Disruption. During disruption, the Corporation shall preserve minimum governance operations necessary to protect legal existence, public-benefit purpose, nonprofit character, records, finances, data / AI / cyber systems, public authority boundaries, safeguards, public-safe publications, and Nexus interfaces.
Minimum governance operations shall include, as applicable: a) ability to convene the Board or lawful emergency governance body; b) ability to verify Directors and authority; c) ability to preserve quorum or determine lawful alternatives; d) ability to access Articles or Certificate, Bylaw, minutes, resolutions, registers, policies, and delegations; e) ability to preserve bank, payroll, vendor, insurance, tax, filing, and registered agent continuity; f) ability to hold or restrict public-facing claims, publications, dashboards, maps, repositories, software releases, proof receipts, and public authority materials; g) ability to activate cyber, privacy, data breach, AI incident, protected knowledge, and safeguards response; h) ability to preserve privilege, legal hold, and evidence custody; i) ability to communicate securely with Directors, counsel, key officers, custodians, and required public authorities where lawful; and j) ability to record emergency actions, ratification, sunset, correction, and post-disruption review.
Minimum governance operations shall not be expanded into ordinary governance by default. Once disruption has passed or competent Board process can resume, emergency continuity measures shall be reviewed, ratified where required, narrowed, terminated, corrected, or converted into ordinary Board-approved measures.
No disruption shall justify unrecorded governance, uncontrolled public communication, unauthorized AI use, shadow IT, uncontrolled repository action, sponsor-directed action, provider-directed action, public authority substitution, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, or role collapse.
126.16 Continuity, Succession, and Emergency Succession Records. The Corporation shall maintain Continuity, Succession, and Emergency Succession Records sufficient to demonstrate that Board continuity, Director succession, officer succession interface, committee leadership succession, Chair succession, emergency Chair succession, emergency Board continuity, Continuity Packs, Board knowledge transfer, key records access continuity, legal continuity, financial continuity, data / AI / cyber continuity, public authority continuity, safeguards continuity, Nexus interface continuity, repository continuity, register continuity, crisis governance continuity, Board vacancy contingency, and minimum governance operations have been planned, reviewed, activated, corrected, and preserved.
Such records shall include, as applicable: a) Board continuity plans; b) Director succession plans; c) Board skills and competence matrices; d) vacancy contingency plans; e) Chair succession records; f) emergency Chair succession records; g) officer succession interface records; h) committee leadership succession records; i) Continuity Packs; j) handover records; k) knowledge-transfer records; l) access continuity records; m) repository custodian and alternate custodian records; n) register custodian and alternate custodian records; o) credential, key, token, certificate, and administrator succession records; p) legal continuity records; q) financial continuity records; r) data / AI / cyber continuity records; s) public authority interface continuity records; t) safeguards and protected knowledge continuity records; u) public-safe publication continuity records; v) Nexus interface continuity records; w) emergency Board continuity activation records; x) crisis governance records; y) minimum governance operations records; z) Board vacancy records; aa) emergency meeting and emergency notice records; bb) emergency written consent records where lawful; cc) ratification records; dd) sunset records; ee) post-disruption review records; ff) correction, supersession, withdrawal, retraction, takedown, quarantine, legal hold, archive, and public clarification records; gg) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that continuity shall preserve lawful governance, not replace it. The Corporation shall be resilient enough to survive transition, vacancy, disruption, cyber incident, data incident, AI incident, public authority confusion, protected knowledge risk, repository failure, leadership change, or crisis without abandoning its public-benefit purpose, nonprofit character, non-execution perimeter, records discipline, public authority boundaries, finance boundaries, certification and procurement boundaries, provider neutrality, sponsor non-control, safeguards, Nexus role separation, validity-by-record, or correctionability. Continuity is lawful institutional memory under pressure; it is not emergency power without limits.
Section 127. Compensation, Reimbursement, and No Improper Benefit for Directors
127.1 Director Compensation Principle. The Corporation shall treat Director compensation, if any, as a controlled governance matter subject to applicable law, the Articles or Certificate, this Bylaw, Board-approved policy, tax-exempt or tax-exempt-compatible requirements, nonprofit character, public-benefit purpose, private inurement prohibitions, excess benefit restrictions, conflict controls, reasonableness review, records discipline, and public trust.
Director service shall be presumed to be fiduciary, mission-locked, independent, public-benefit service and not a route to private extraction, compensation arbitrage, sponsor reward, provider influence, public authority access, finance-adjacent advantage, recognition leverage, certification leverage, procurement advantage, or enterprise-stack benefit.
No compensation, stipend, honorarium, fee, allowance, benefit, reimbursement, travel support, event support, training support, fellowship-style support, or other value transferred to or for the benefit of a Director shall be structured, approved, paid, reimbursed, characterized, or recorded in a manner that weakens the Corporation’s nonprofit character, public-benefit purpose, independence, Board judgment, tax posture, anti-capture controls, provider neutrality, sponsor non-control, or fiduciary integrity.
The Board shall interpret Director compensation and reimbursement rules in favor of legality, moderation, independence, transparency to the extent appropriate, public-benefit necessity, and record-supported reasonableness. Where doubt exists, the matter shall be escalated for conflict, tax, nonprofit, counsel, audit, or Board review before payment or commitment.
127.2 Uncompensated Director Service Unless Compensation Is Lawfully Approved. Directors shall serve without compensation unless compensation is expressly permitted by applicable law, not prohibited by the Articles or Certificate, consistent with this Bylaw, compatible with the Corporation’s tax-exempt or tax-exempt-compatible status, and approved through a competent, independent, recorded process.
Uncompensated service shall not prevent the Corporation from reimbursing reasonable and properly documented expenses incurred in furtherance of authorized Board service, provided such reimbursement complies with this Section.
The absence of Director compensation shall not reduce the fiduciary duties of Directors. A Director serving without compensation remains subject to the duties of care, loyalty, obedience to mission where applicable, good faith, confidentiality, conflict disclosure, recusal, records discipline, non-execution, public authority boundary discipline, finance-boundary discipline, data / AI / cyber controls, safeguards, validity-by-record, and correctionability.
No person shall represent that uncompensated Director service creates ownership rights, founder rights, special influence, permanent office, superior moral claim to control, entitlement to future compensation, reimbursement without documentation, sponsor-directed role, provider-directed role, public authority role, enterprise role, or exemption from conflict and confidentiality rules.
127.3 Compensation Where Permitted by Law and Governing Instruments. The Corporation may provide compensation to Directors only where the Board determines, through lawful and independent process, that compensation is permitted, reasonable, necessary or appropriate for the Corporation’s public-benefit purposes, and compatible with nonprofit and tax requirements.
Director compensation may be considered only for defined service categories, such as: a) Board service where permitted by law and approved by competent record; b) extraordinary Board service requiring substantial time beyond ordinary fiduciary expectations; c) committee chair service where permitted and justified by workload, risk, and institutional need; d) specialized governance service requiring documented expertise, provided that the service does not compromise independence or create impermissible private benefit; e) transitional governance service during formation, emergency, restructuring, audit, investigation, or continuity periods where lawful and independently approved; and f) other service expressly authorized by the Articles or Certificate, this Bylaw, Board policy, or competent record.
Director compensation shall not be approved merely because the Corporation has funds, because other institutions compensate directors, because a Director has stature, because a Director is a founder, because a sponsor or donor expects it, because a provider requests it, because a public authority values the Director’s role, or because compensation may increase access to particular networks.
Any compensated Director service shall be scoped, time-bound where appropriate, reviewed, recorded, and separable from any conflicted transaction, related-party arrangement, sponsor relationship, provider relationship, public authority relationship, finance-adjacent activity, certification-adjacent activity, procurement-adjacent activity, or enterprise-stack activity.
127.4 Reasonableness Review. Any Director compensation shall be subject to reasonableness review before approval and at intervals appropriate to the amount, duration, role, risk, and tax posture of the Corporation.
Reasonableness review shall consider: a) the nature and scope of the service; b) the time commitment required; c) the skill, expertise, independence, and fiduciary burden involved; d) comparable compensation where reliable comparability information is available; e) the Corporation’s size, resources, budget, public-benefit mission, and nonprofit character; f) the Corporation’s tax status or intended tax status; g) the effect on public trust, donor trust, sponsor non-control, provider neutrality, and anti-capture posture; h) whether the compensation could create private inurement, impermissible private benefit, excess benefit, related-party concern, or appearance of pay-to-play; i) whether the compensation could impair independence, recusal obligations, committee eligibility, or Board credibility; and j) whether unpaid service, reimbursement only, temporary stipend, capped compensation, external funding with firewall controls, or another narrower arrangement would satisfy the institutional need.
Reasonableness shall be judged by the substance of the arrangement, not merely by labels used in a contract, invoice, budget line, grant schedule, honorarium description, reimbursement form, or Board resolution.
No compensation shall be deemed reasonable solely because the recipient agrees to it, because it is below market for commercial consulting, because a sponsor funds it, because it appears in an approved budget, or because the Director is performing mission-critical work.
127.5 Independent Approval. Director compensation shall be approved only by disinterested Directors or another competent independent approval mechanism permitted by law and governing instruments. A Director whose compensation, reimbursement beyond ordinary expenses, benefit, contract, consulting arrangement, employment arrangement, fellowship arrangement, honorarium, related-party transaction, or other personal economic interest is under consideration shall disclose the interest and shall not participate in deliberation, recommendation, approval, vote, pressure, side-channel influence, or access to restricted materials except as permitted for factual information and recorded by the Board.
Independent approval shall require: a) prior disclosure of the proposed compensation or benefit; b) identification of the Director receiving compensation or benefit; c) identification of the service, role, term, amount, basis, and payment mechanism; d) conflict and recusal determination; e) reasonableness review; f) tax, nonprofit, private benefit, and inurement review where appropriate; g) budget authority review; h) documentation of alternatives considered where appropriate; i) approval by disinterested Directors or other lawful independent authority; j) recording of vote, abstentions, recusals, and limitations; and k) retention of the approval record.
No Director shall approve, recommend, condition, route, or influence the Director’s own compensation except through permitted factual disclosure. No officer, staff member, sponsor, donor, provider, public authority participant, funder, host, national company, Project SPV, investor, insurer, lender, contractor, or advisor shall be used to bypass independent Board approval.
127.6 Conflict Review. Director compensation and reimbursement shall be reviewed for conflicts of interest, related-party concerns, dual-role concerns, independence concerns, sponsor-linked concerns, provider-linked concerns, donor-linked concerns, public authority-linked concerns, enterprise-linked concerns, and appearance concerns.
Conflict review shall apply where compensation or reimbursement is connected to: a) employment, consulting, contractor, advisory, fellowship, speaker, teaching, research, or professional services arrangements; b) sponsor, donor, funder, provider, host, university, laboratory, public authority, national company, Project SPV, investor, insurer, lender, or enterprise-stack relationships; c) grants, restricted funds, sponsorships, gifts, event support, travel support, hospitality, or in-kind support; d) technical asset development, repository stewardship, software release, research output, public-safe publication, evidence pack, method review, observability output, ontology change, benchmark, model review, or public-good technical baseline; e) public authority learning, regulator-listening rooms, public finance reader rooms, emergency-management learning rooms, controlled rooms, clean rooms, evidence rooms, data rooms, or no-download rooms; f) GRF-facing inputs, GRA-facing technical inputs, Nexus Standards support, Nexus Docket support, Nexus Grid support, Nexus Observatory support, Nexus Universe support, or Nexus interface work; or g) any matter involving potential finance, certification, procurement, recognition, provider preference, sponsor control, or public authority meaning.
Where conflict risk cannot be adequately mitigated, the compensation, reimbursement, or benefit shall be refused, narrowed, deferred, restructured, independently reviewed, or terminated.
127.7 Tax-Exempt and Private Benefit Review. Director compensation shall be reviewed for compatibility with the Corporation’s tax-exempt or tax-exempt-compatible status, nonprofit character, public-benefit purpose, and restrictions against private inurement, excess benefit, and impermissible private benefit.
Tax-exempt and private benefit review shall consider: a) whether the compensation is for actual services necessary or appropriate to the Corporation’s purposes; b) whether the amount is reasonable; c) whether approval is independent; d) whether the arrangement is documented in advance; e) whether the arrangement creates more than incidental private benefit; f) whether the arrangement confers a special advantage unavailable on lawful, mission-consistent terms; g) whether the arrangement is connected to a restricted fund, grant, sponsorship, or donor condition; h) whether the arrangement could influence research, evidence, methods, publications, technical baselines, public authority access, provider treatment, or Nexus interface outputs; i) whether the arrangement requires disclosure on tax, solicitation, grant, audit, financial statement, conflict, or public records; and j) whether the arrangement should be prohibited, capped, disclosed, independently reviewed, or modified.
No compensation arrangement shall be approved if it would constitute private inurement, impermissible private benefit, an excess benefit transaction where applicable, misuse of restricted funds, improper sponsor benefit, disguised distribution, or unlawful diversion of public-benefit assets.
127.8 Reimbursement of Reasonable Expenses. The Corporation may reimburse Directors for reasonable, necessary, properly documented, and authorized expenses incurred in the performance of Board duties or other authorized service to the Corporation.
Reimbursable expenses may include: a) travel reasonably required for Board meetings, committee meetings, public authority learning sessions, controlled-room sessions, Nexus interface sessions, trainings, field visits, research oversight, or institutional events; b) lodging reasonably required for authorized service; c) meals and incidental expenses within approved limits; d) accessibility-related expenses necessary for participation; e) approved technology, communications, security, or identity-verification costs necessary for Board service; f) approved training or fiduciary development expenses; g) approved safety, safeguarding, or protected participation expenses where necessary; h) approved costs associated with public-safe, data / AI / cyber, legal, compliance, or controlled-room obligations; and i) other expenses expressly approved by policy, budget, or competent record.
Reimbursement shall not be used to provide disguised compensation, luxury benefit, personal travel, family travel, companion travel, vacation expense, political contribution, lobbying expense outside approved policy, sponsor hospitality, provider benefit, public authority entertainment, personal equipment unrelated to service, or any private benefit inconsistent with the Corporation’s purposes.
127.9 Expense Documentation. A Director seeking reimbursement shall provide documentation sufficient to establish the nature, amount, date, purpose, authorization, and public-benefit connection of the expense.
Expense documentation shall include, as applicable: a) receipt or invoice; b) date incurred; c) business or governance purpose; d) meeting, event, program, committee, controlled-room, public authority, Nexus interface, or Board matter supported; e) travel itinerary where applicable; f) funding source where relevant; g) cost center, grant, restricted fund, or budget line where relevant; h) certification that the expense is not reimbursed by another source unless disclosed; i) certification that the expense does not involve prohibited personal benefit, sponsor benefit, provider benefit, public authority entertainment, or improper hospitality; and j) approval by an authorized person not conflicted in the expense.
Where documentation is incomplete, the Corporation may deny reimbursement, require supplementation, reclassify the expense, cap payment, seek repayment, or escalate for review. Repeated documentation failures may trigger training, audit, access restriction, expense privilege restriction, or other corrective action.
127.10 Travel and Event Reimbursement. Travel and event reimbursement for Directors shall be governed by reasonableness, necessity, public-benefit purpose, budget authority, conflict controls, and public-trust discipline.
Travel and event reimbursement shall be subject to: a) prior approval where required by policy or risk class; b) reasonable class of travel and lodging standards; c) limits on upgrades, premium services, hospitality, entertainment, and incidental expenses; d) disclosure of sponsor, donor, provider, host, public authority, or third-party payment; e) refusal of travel support that creates control, influence, preferential access, public authority confusion, procurement advantage, provider preference, finance overclaim, certification overclaim, recognition overclaim, or private benefit concern; f) restrictions on companion, family, personal, campaign, political, lobbying, vacation, or unrelated travel; g) accessibility accommodations where needed for lawful and meaningful participation; h) security or safeguarding accommodations where justified by risk; i) public authority ethics and gift-rule review where public authority participants or officials are involved; and j) records sufficient to support audit, tax, grant, donor, and Board review.
No Director shall accept travel, hospitality, entertainment, honoraria, gifts, or other benefits from sponsors, providers, vendors, public authorities, donors, funders, hosts, national companies, Project SPVs, capital actors, or enterprise-stack actors in connection with Corporation duties unless the benefit is permitted by law, policy, conflict rules, tax rules, gift rules, sponsor non-control rules, provider-neutrality rules, and public authority boundary rules, and is recorded where required.
127.11 No Excess Benefit. The Corporation shall prohibit any excess benefit, unreasonable compensation, disguised distribution, improper enrichment, private inurement, or other transaction in which a Director receives value beyond what is lawful, reasonable, documented, and consistent with the Corporation’s nonprofit and public-benefit purposes.
An excess benefit concern may arise from: a) compensation above reasonable value; b) reimbursement of personal or undocumented expenses; c) payment for services not actually rendered; d) duplicate payment; e) inflated consulting, speaking, teaching, research, advisory, or technical fees; f) sponsor-funded benefits tied to influence; g) provider-funded benefits tied to access or preference; h) use of Corporation assets for personal purposes; i) free or discounted access to controlled assets outside policy; j) travel, hospitality, event, or entertainment benefits beyond approved standards; k) restricted fund misuse; l) related-party arrangements without independent approval; or m) compensation tied to prohibited outcomes.
Where an excess benefit concern is identified, the Corporation shall hold payment where possible, investigate, obtain independent review where appropriate, correct the record, seek repayment where lawful, impose mitigation, disclose where required, and take corrective action necessary to protect nonprofit integrity, tax status, and public trust.
127.12 No Private Inurement. No part of the Corporation’s net earnings, assets, revenue, grants, donations, sponsorships, restricted funds, unrestricted funds, technical assets, public-good software, data resources, repositories, controlled-room access, public authority access, Nexus interface access, or institutional opportunities shall inure to the private benefit of any Director.
Private inurement is prohibited whether structured as: a) salary; b) fee; c) consulting payment; d) honorarium; e) bonus; f) reimbursement; g) loan; h) guarantee; i) advance; j) gift; k) discounted asset transfer; l) license preference; m) repository or data access; n) provider preference; o) sponsor benefit; p) grant pass-through; q) travel or hospitality; r) public authority access; s) recognition influence; t) finance-readiness influence; or u) any other direct or indirect benefit.
The Corporation may pay reasonable compensation and reimburse reasonable expenses where lawful, properly approved, documented, and mission-consistent. Such permitted payments shall not be characterized as distributions, dividends, profit shares, ownership returns, founder returns, success fees, transaction fees, placement fees, capital-raising compensation, procurement success fees, certification fees, recognition fees, finance-readiness fees, or public authority access fees.
127.13 No Compensation Tied to Sponsorship, Fundraising Outcome, Provider Selection, Finance-Readiness, Certification, Recognition, Public Authority Access, or Procurement Outcome. No Director compensation, bonus, commission, success fee, incentive, stipend, reimbursement, honorarium, consulting fee, advisory fee, travel benefit, benefit package, or other value shall be tied to a prohibited or boundary-sensitive outcome.
The Corporation shall prohibit Director compensation tied to: a) securing sponsorship, donation, grant, restricted fund, public-good support, or in-kind contribution in a manner inconsistent with tax, nonprofit, fundraising, or anti-capture rules; b) sponsor retention, sponsor satisfaction, sponsor visibility, sponsor influence, or sponsor benefit beyond approved acknowledgment; c) provider selection, provider preference, vendor selection, vendor access, procurement pathway, public authority introduction, or enterprise-stack participation; d) recognition, maturity, standing, public-facing legitimacy, Docket status, Grid status, or Nexus-compatible claim; e) finance-readiness, insurance-readiness, bankability, capital-readability, investor-literacy output, proof pack status, rating, public finance status, tax credit status, loan readiness, or investment suitability; f) certification, accreditation, conformance approval, standards approval, compliance approval, or technical approval; g) public authority access, public authority attendance, public authority data contribution, public authority adoption, public authority funding, public authority procurement, public authority endorsement, public warning, emergency command, or regulator action; h) research findings, evidence conclusions, methods outcomes, benchmark scores, model review results, public-safe publication conclusions, technical baseline results, dashboard outputs, or Truth Engine outputs; or i) any transaction, approval, claim, or status that the Corporation is prohibited from performing.
Fundraising-related compensation for officers, staff, contractors, or third parties, if any, shall be governed by separate law, policy, tax review, charitable solicitation review where applicable, conflict controls, and Board-approved boundaries. No such arrangement shall be routed through Director compensation to evade controls.
127.14 Compensation Disclosure Where Required. The Corporation shall disclose Director compensation, reimbursement, related-party transactions, excess benefit corrections, or other benefits where required by law, tax filings, state filings, charitable solicitation filings where applicable, grant agreements, audit or review standards, conflict policies, Board policy, donor restrictions, public authority agreements, or other lawful obligations.
Disclosure may be public, controlled, internal, regulator-facing, funder-facing, auditor-facing, counsel-facing, or Board-facing depending on the applicable requirement and classification.
Disclosure shall be accurate, complete, proportionate, and public-safe. It shall not disclose personal information, privileged information, protected knowledge, security-sensitive information, or confidential third-party information beyond what is required or lawfully approved.
Where public disclosure is required, the Corporation shall ensure that disclosure does not imply endorsement, certification, public authority approval, finance-readiness, procurement approval, recognition, provider status, sponsor control, or other public meaning beyond the disclosed fact.
Failure to disclose compensation or benefits where required shall be treated as a governance and compliance concern subject to correction, amended filings, repayment review, conflict review, Board review, and disciplinary or legal action where appropriate.
127.15 Director Compensation and Reimbursement Records. The Corporation shall maintain Director Compensation and Reimbursement Records sufficient to demonstrate lawful approval, reasonableness, independence, tax compatibility, nonprofit integrity, public-benefit alignment, conflict management, payment accuracy, reimbursement integrity, disclosure compliance, and correctionability.
Director Compensation and Reimbursement Records shall include, as applicable: a) compensation policy; b) reimbursement policy; c) travel policy; d) fee schedule; e) Board approval records; f) independent approval records; g) disinterested Director vote records; h) conflict disclosures; i) recusal records; j) reasonableness review records; k) comparability data where used; l) tax and nonprofit review records; m) private benefit and inurement review records; n) excess benefit review records; o) budget authorization records; p) grant, restricted fund, sponsorship, or donor restriction records where relevant; q) compensation agreements; r) consulting, advisory, speaker, teaching, research, or special service agreements involving Directors; s) invoices; t) receipts; u) reimbursement requests; v) expense approvals; w) travel authorizations; x) event support records; y) accessibility accommodation expense records where applicable; z) sponsor, donor, funder, provider, host, public authority, or third-party support disclosures; aa) payment records; bb) repayment records; cc) disclosure records; dd) audit or review records; ee) amended or corrected records; ff) refusal, hold, denial, reduction, repayment, or corrective action records; gg) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that Director compensation and reimbursement shall never become a channel for private extraction, capture, influence purchase, public authority access, provider preference, sponsor control, finance-adjacent reward, certification leverage, recognition leverage, procurement advantage, or enterprise execution benefit. Director compensation, where permitted, shall be lawful, reasonable, independent, recorded, mission-consistent, and correctionable. Director reimbursement shall restore reasonable costs of service, not create hidden benefit. Every payment to or for a Director shall preserve fiduciary independence, public-benefit trust, nonprofit integrity, role separation, non-execution, and validity-by-record.
Section 128. Indemnification, Advancement of Expenses, Insurance, and Liability Protection
128.1 Indemnification Purpose. The Corporation may indemnify eligible persons to the fullest extent permitted by applicable law, the Articles or Certificate, this Bylaw, Board-approved policy, and any lawful indemnification agreement, in order to protect good-faith service to the Corporation, preserve independent fiduciary judgment, support qualified participation in governance and mission-critical oversight, and ensure that Directors, officers, committee members, employees, volunteers, fellows, advisors, and authorized representatives are not deterred from lawful service by reasonable exposure arising from authorized duties.
Indemnification shall be a protection for lawful, good-faith, mission-aligned service. It shall not be a shield for private inurement, improper personal benefit, bad faith, fraud, knowing violation of law, willful misconduct, unauthorized execution, public authority overclaim, finance overclaim, certification overclaim, procurement overclaim, provider preference, sponsor control, retaliation, protected knowledge breach, data misuse, AI misuse, cyber misconduct, research misconduct, or deliberate disregard of this Bylaw.
The purposes of indemnification under this Section are to: a) preserve competent governance of a United States nonprofit, public-benefit, non-executing technical institution; b) support fiduciary oversight of evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, public authority learning, data / AI / cyber controls, community safeguards, and Nexus interfaces; c) protect lawful participation in Board, officer, committee, council, controlled-room, public authority learning, research, safeguards, and public-safe publication functions; d) preserve role separation among GCRI US, GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, Nexus Network, consortiums, national companies, Project SPVs, providers, sponsors, hosts, and public authorities; and e) ensure that liability protection remains consistent with non-execution, public authority boundaries, finance boundaries, certification and procurement boundaries, provider neutrality, sponsor non-control, validity-by-record, and correctionability.
Indemnification shall be interpreted as an institutional protection, not as a waiver of duty. No person shall rely on indemnification to justify conduct outside authority, outside role, outside record, outside law, or outside the Corporation’s public-benefit purposes.
128.2 Indemnification to the Fullest Extent Permitted by Law. Subject to applicable law, the Articles or Certificate, this Bylaw, and any lawful conditions or exclusions, the Corporation may indemnify an eligible person against expenses, judgments, fines, penalties, settlements, and other amounts actually and reasonably incurred in connection with a proceeding, claim, action, investigation, inquiry, demand, arbitration, mediation, regulatory matter, internal review, external review, or other covered matter arising by reason of the person’s service to the Corporation or authorized service at the Corporation’s request.
Indemnification may apply where the person served, or is alleged to have served, as: a) Director; b) officer; c) committee member; d) council member acting within approved advisory role; e) employee; f) volunteer; g) fellow; h) advisor; i) authorized representative; j) agent within recorded delegation; k) repository, register, or records custodian; l) public authority learning facilitator; m) controlled-room participant acting under authorized role; n) research, evidence, methods, data / AI / cyber, safeguards, public-safe publication, or technical asset steward; or o) another person expressly approved by the Board or authorized under policy.
Indemnification shall be available only to the extent lawful and only for matters arising from authorized service, not from personal ventures, unauthorized representation, enterprise execution, sponsor-directed activity, provider-directed activity, public authority substitution, finance execution, certification activity, procurement activity, recognition activity, professional advice outside authorization, or conduct outside the Corporation’s role.
Where governing law provides mandatory indemnification for a successful defense or other protected circumstance, the Corporation shall comply with such law. Where governing law permits but does not require indemnification, the Board may authorize indemnification only after required review and recorded determination.
128.3 Eligible Directors. Each Director may be eligible for indemnification for acts or omissions undertaken in good faith within the scope of Director service, including participation in Board meetings, committee service, written consents, emergency governance, reserved matter review, fiduciary oversight, strategic oversight, legal and compliance oversight, records review, public-safe publication review, data / AI / cyber oversight, safeguards oversight, Nexus interface oversight, and other authorized Board functions.
Director indemnification may cover lawful service connected to: a) fiduciary deliberation and decision-making; b) review of budgets, grants, donations, sponsorships, restricted funds, contracts, support arrangements, and financial controls; c) oversight of evidence, methods, observability, ontology, research integrity, technical truth, public-good software, repositories, open technical baselines, model registers, inference records, compute workload records, and secure release; d) oversight of public authority learning, public authority capacity classification, regulator-listening rooms, public finance reader rooms, emergency-management learning rooms, and public-safe reporting; e) oversight of civil rights, accessibility, community safeguards, Tribal and Indigenous protocols, protected knowledge, grievance, remedy, protected participation, whistleblowing, and non-retaliation; f) oversight of non-execution, finance-boundary, certification-boundary, procurement-boundary, recognition-boundary, provider-neutrality, sponsor non-control, and public authority boundary systems; and g) oversight of correction, supersession, withdrawal, retraction, takedown, quarantine, legal hold, incident response, and emergency measures.
Director indemnification shall not protect a Director from consequences of bad faith, self-dealing, private inurement, knowingly unlawful conduct, improper personal benefit, intentional misconduct, unmanaged conflict, failure to recuse where required, retaliation, misuse of confidential information, or knowing support for prohibited functions.
128.4 Eligible Officers. Each officer may be eligible for indemnification for acts or omissions undertaken in good faith within the officer’s lawful office, delegated authority, Board-approved strategy, Board-approved budget, authority matrix, policy framework, and records requirements.
Officer indemnification may cover authorized service connected to: a) implementation of Board-approved decisions; b) corporate administration, filings, notices, minute books, registers, repositories, gazette or notice streams, and record custody; c) financial administration, budgeting, accounting, restricted fund tracking, tax filings, grants, donations, sponsorships, subscriptions, fees, reimbursements, procurement process, and internal controls; d) evidence, methods, research, observability, ontology, public-good software, technical baselines, data governance, AI governance, cybersecurity, privacy, safeguards, and public-safe publication operations; e) public authority learning, controlled rooms, clean rooms, evidence rooms, data rooms, no-download rooms, and capacity-classified public authority interfaces; f) legal, compliance, sanctions, export-control, competition, professional-boundary, public authority, finance-boundary, certification-boundary, procurement-boundary, and regulatory-perimeter escalation; and g) correction, incident response, emergency hold, quarantine, re-scope, withdrawal, takedown, or post-incident review.
Officer indemnification shall not apply to conduct outside delegated authority, self-approved compensation, misuse of funds, unauthorized contracting, unauthorized public statements, unauthorized public authority representation, finance execution, certification, procurement approval, provider preference, sponsor control, recognition, emergency command, or knowing failure to escalate material risk.
128.5 Eligible Committee Members, Employees, Volunteers, Fellows, Advisors, and Representatives Where Approved and Lawful. The Corporation may indemnify committee members, advisory body members, employees, volunteers, fellows, advisors, consultants, representatives, custodians, contributors, maintainers, and other persons serving the Corporation or serving at the Corporation’s request where such indemnification is lawful, authorized, documented, and consistent with the person’s role.
Eligibility may apply to persons serving in: a) Board committees, standing committees, special committees, advisory councils, Helix Councils, scientific panels, technical panels, peer-review panels, model-review panels, red-team panels, public authority forums, safeguards forums, and working groups; b) research, evidence, methods, observability, ontology, data / AI / cyber, public-good software, open technical baseline, repository, secure release, public-safe publication, and correction roles; c) public authority learning, simulation, tabletop, after-action learning, regulator-listening, public finance reader, emergency-management participant, and controlled-room support roles; d) community safeguards, Tribal and Indigenous protocol, civil rights, accessibility, protected knowledge, grievance, remedy, protected participation, non-retaliation, and do-no-harm roles; e) official representation roles approved by the Board or authorized officer; and f) other roles approved by competent record.
No person shall become eligible for indemnification merely by attending a meeting, donating funds, sponsoring a program, providing services, hosting an event, contributing code, joining a mailing list, accessing a repository, entering a controlled room, serving as public authority participant, serving as provider, serving as sponsor, serving as media participant, or using the Corporation’s materials unless eligibility is established by law, policy, contract, Board action, or other competent record.
Indemnification for non-Directors and non-officers may be narrower than indemnification for Directors and officers. The Corporation may require written terms, role scope, confidentiality obligations, conflict disclosure, training, insurance review, and access controls as conditions of eligibility.
128.6 Conditions for Indemnification. Indemnification shall be conditioned on a determination that the person seeking indemnification acted in a manner that satisfies the standards required by law and governing instruments.
The Corporation may require findings that the person: a) acted in good faith; b) acted within or reasonably believed the person acted within authorized role and scope; c) acted in a manner the person reasonably believed to be in, or not opposed to, the best interests and public-benefit purposes of the Corporation; d) complied with applicable law, the Articles or Certificate, this Bylaw, Board resolutions, policies, delegations, authority matrices, confidentiality rules, conflict rules, and records requirements; e) did not obtain improper personal benefit; f) did not engage in private inurement or impermissible private benefit; g) did not knowingly violate law; h) did not engage in fraud, willful misconduct, bad faith, or intentional wrongdoing; i) preserved non-execution and role separation; j) preserved public authority, finance, certification, procurement, provider-neutrality, sponsor non-control, and recognition boundaries; k) complied with data / AI / cyber, privacy, research integrity, public-safe publication, civil rights, accessibility, community safeguards, Tribal and Indigenous protocol, and protected knowledge controls; and l) cooperated with the Corporation’s review, defense, investigation, correction, legal hold, insurance, and records processes.
A person seeking indemnification shall provide timely notice, reasonable cooperation, truthful information, preservation of relevant records, conflict disclosure, and any undertaking required by law or policy. Failure to cooperate may justify denial, suspension, limitation, or recovery of indemnification to the extent lawful.
128.7 Good Faith Requirement. Good faith is a foundational condition of indemnification. A person acts in good faith only where the person acts honestly, with a lawful purpose, within reasonable understanding of the person’s role, and without intent to deceive, misappropriate, retaliate, conceal, overclaim, or obtain improper benefit.
Good faith may be supported by evidence that the person: a) relied on competent records, Board resolutions, policies, delegations, counsel advice, committee reports, officer reports, public-safe notices, or approved procedures; b) disclosed conflicts and recused where required; c) escalated legal, compliance, data / AI / cyber, public authority, finance-boundary, safeguards, research integrity, or public-safe publication concerns; d) preserved records and did not alter or conceal material facts; e) used controlled vocabulary and approved limitation language; f) avoided unauthorized public claims; g) complied with controlled-room, data-room, repository, AI-use, and confidentiality rules; and h) supported correction once an error or boundary concern was identified.
Good faith shall not be found merely because a person subjectively believed the person was helping the Corporation if the person knowingly exceeded authority, ignored mandatory controls, misused institutional identity, suppressed contrary evidence, bypassed recusal, concealed conflicts, violated law, or created prohibited authority.
128.8 Lawful Conduct Requirement. Indemnification shall not protect conduct that applicable law prohibits from being indemnified. Where law requires a particular standard for indemnification, such standard shall control.
The lawful conduct requirement shall be applied to: a) corporate law standards; b) nonprofit law standards; c) tax-exempt or tax-exempt-compatible restrictions; d) charitable solicitation rules where applicable; e) private inurement and excess benefit restrictions; f) fiduciary duty standards; g) conflict and related-party transaction requirements; h) employment, contractor, volunteer, fellow, advisor, workplace, civil rights, accessibility, and safety laws; i) privacy, data protection, cybersecurity, AI, research, health-sensitive data, public sector data, and children’s data requirements where applicable; j) sanctions, export-control, controlled technology, national security, and dual-use requirements; k) competition and antitrust requirements; l) lobbying, political activity, government ethics, gifts, grant, and procurement integrity requirements where applicable; m) securities, investment adviser, broker-dealer, finder, banking, lending, insurance, underwriting, rating, public finance, procurement, certification, and public authority regulatory-perimeter requirements; and n) any other law applicable to the matter.
Where legality is uncertain, the Corporation may hold indemnification, advance only where lawful with undertaking, seek counsel review, preserve privilege, notify insurers, segregate issues, and make a final determination after adequate review.
128.9 Best-Interest Requirement Where Applicable. Where required by law or governing instruments, indemnification shall be conditioned on a determination that the person acted in a manner reasonably believed to be in, or not opposed to, the best interests of the Corporation.
For purposes of this Bylaw, the best interests of the Corporation include preservation of: a) lawful nonprofit existence; b) public-benefit purpose; c) tax-exempt or tax-exempt-compatible posture; d) non-distribution and no-private-inurement discipline; e) mission lock; f) non-execution; g) GCRI / GRF / GRA role separation; h) public-good stack and enterprise stack separation; i) evidence integrity, methods integrity, observability integrity, ontology integrity, technical truth integrity, and public-good software integrity; j) public authority boundary discipline; k) finance, securities, investment adviser, broker-dealer, insurance, lending, rating, public finance, procurement, certification, recognition, and professional-boundary discipline; l) provider neutrality and sponsor non-control; m) data / AI / cyber, privacy, research integrity, civil rights, accessibility, community safeguards, Tribal and Indigenous protocol, protected knowledge, and public-safe publication controls; n) validity-by-record; and o) correctionability.
A person shall not be treated as acting in the Corporation’s best interests where the person knowingly prioritizes private benefit, sponsor demands, provider preference, personal reputation, political advantage, public authority pressure, funding pressure, media pressure, technical convenience, operational speed, or enterprise-stack benefit over law, mission, safeguards, and records.
128.10 Exclusions for Bad Faith, Fraud, Willful Misconduct, Knowing Violation of Law, Improper Personal Benefit, Private Inurement, Gross Misconduct Where Applicable, or Other Excluded Conduct. The Corporation shall not indemnify any person for conduct that applicable law, the Articles or Certificate, this Bylaw, Board policy, insurance terms, or competent determination excludes from indemnification.
Excluded conduct includes, to the extent applicable: a) bad faith; b) fraud; c) willful misconduct; d) knowing violation of law; e) intentional misrepresentation; f) concealment or destruction of records; g) improper personal benefit; h) private inurement; i) impermissible private benefit; j) excess benefit transaction where applicable; k) unlawful distribution of assets; l) self-dealing not lawfully approved; m) retaliation, harassment, discrimination, or civil rights violation; n) protected knowledge breach or exploitation; o) data misuse, AI misuse, cyber misconduct, credential misuse, repository compromise, or unauthorized AI upload; p) research misconduct, evidence fabrication, data falsification, plagiarism, or suppression of correction; q) sanctions, export-control, controlled technology, competition, procurement integrity, or government ethics violation; r) unauthorized public authority representation, public warning, emergency command, regulatory action, certification, procurement approval, recognition, finance-readiness determination, rating, investment advice, brokerage, lending, insurance, underwriting, public finance approval, provider selection, or enterprise execution; and s) other conduct excluded by law or Board-approved policy.
Where a proceeding includes both covered and excluded conduct, the Corporation may allocate expenses, limit indemnification, advance subject to undertaking, seek repayment, or deny indemnification for excluded portions to the extent lawful.
128.11 Advancement of Expenses Where Permitted. The Corporation may advance reasonable expenses incurred by an eligible person in defending or responding to a proceeding or covered matter before final disposition, where permitted by law and authorized by the Board or other competent authority.
Advancement may include reasonable attorneys’ fees, investigation costs, expert costs, filing costs, hearing costs, mediation costs, arbitration costs, and other defense costs actually and reasonably incurred.
Advancement shall be subject to: a) written request; b) description of the matter; c) evidence of eligibility; d) confirmation of service role; e) conflict review; f) insurance notice review; g) Board or delegated approval where required; h) undertaking to repay where required by law or policy; i) cooperation obligation; j) records preservation obligation; k) privilege and confidentiality controls; and l) right of the Corporation to suspend, limit, or terminate advancement where standards are not met.
Advancement shall not be treated as a determination that indemnification is ultimately required. Advancement is provisional protection, subject to final determination, repayment obligations, exclusions, allocation, insurance recovery, and correction.
128.12 Repayment Undertaking Where Required. Where required by law, the Articles or Certificate, this Bylaw, Board policy, indemnification agreement, or Board determination, a person receiving advancement shall provide a written undertaking to repay amounts advanced if it is ultimately determined that the person is not entitled to indemnification.
The repayment undertaking may require: a) identification of the person receiving advancement; b) identification of the matter; c) acknowledgment that advancement is provisional; d) obligation to repay non-indemnifiable amounts; e) obligation to cooperate with the Corporation and insurers; f) obligation to preserve records and evidence; g) obligation to disclose conflicts and material developments; h) obligation to submit invoices and billing records for reasonableness review; i) obligation to respect privilege, confidentiality, public authority sensitivity, cyber sensitivity, protected knowledge, and public-safe communication restrictions; j) agreement to allocation where covered and excluded matters are mixed; and k) agreement to offset insurance proceeds, settlements, or third-party recoveries where appropriate.
Failure to provide a required undertaking may justify refusal of advancement. Failure to repay when repayment is required may result in legal action, offset, indemnification denial, removal, suspension, access restriction, referral, or other lawful remedy.
128.13 Board Approval and Conflict Controls. Indemnification and advancement determinations shall be made by the Board, disinterested Directors, a committee of disinterested Directors, independent counsel, members where required, a court, or another mechanism permitted by law and governing instruments.
A person seeking indemnification or advancement shall not participate in the determination except to provide factual information, respond to questions, preserve rights, and cooperate with review. Any Director, officer, committee member, advisor, employee, or other person with a material conflict shall disclose the conflict and recuse from deliberation and approval.
Board approval and conflict controls shall include, as applicable: a) identification of claimant; b) role and authority of claimant; c) matter giving rise to request; d) proceeding or claim status; e) applicable indemnification standard; f) counsel review; g) insurance review; h) conflict and recusal record; i) covered and excluded conduct analysis; j) reasonableness review of expenses; k) undertaking review; l) allocation of covered and uncovered costs; m) vote or approval record; n) limitation, condition, or denial record; o) notice to claimant; and p) repository, register, retention, and legal hold entry.
No indemnification or advancement shall be approved through informal consensus, officer comfort, sponsor pressure, provider pressure, public authority pressure, founder preference, insurance assumption, reimbursement habit, or operational convenience.
128.14 Directors’ and Officers’ Insurance. The Corporation may purchase and maintain directors’ and officers’ liability insurance to protect the Corporation and eligible persons against covered claims, expenses, liabilities, and risks arising from lawful service to the Corporation.
Directors’ and officers’ insurance may cover, subject to policy terms: a) Directors; b) officers; c) committee members where covered; d) employees and volunteers where covered; e) fellows, advisors, or representatives where approved and covered; f) employment practices claims where included; g) fiduciary and governance claims where included; h) regulatory, investigation, or inquiry costs where included; i) nonprofit management liability risks; j) cyber, privacy, data, AI, technology, media, publication, or professional risks where included or separately insured; and k) other risks approved by the Board.
The Corporation shall periodically review insurance adequacy in light of its United States and North America anchor role, all-states-and-territories posture, public authority interfaces, data / AI / cyber posture, research and publication activities, controlled rooms, public-good software, technical repositories, safeguards obligations, funding relationships, Nexus interfaces, and non-execution boundaries.
Insurance shall not be used to justify prohibited activity, weaken controls, replace fiduciary judgment, avoid compliance, or imply that an activity is lawful merely because a policy may respond.
128.15 General Liability, Professional Liability, Cyber, Employment Practices, Fiduciary, Crime, Event, Property, Research, Lab, Travel, and Other Insurance. The Corporation may purchase and maintain additional insurance appropriate to its lawful activities, risk profile, assets, programs, people, systems, public-benefit mission, and Nexus interfaces.
Insurance may include: a) general liability; b) professional liability or errors and omissions where appropriate; c) cyber liability, privacy, data breach, AI incident, technology errors, and network security coverage; d) employment practices liability; e) fiduciary liability where applicable; f) crime, fraud, fidelity, and funds-transfer coverage; g) event liability; h) property, equipment, and facility coverage; i) travel, accident, and participant coverage; j) research, lab, fieldwork, controlled-room, simulation, tabletop, or public authority learning coverage; k) media, publication, intellectual property, defamation, or content liability where appropriate; l) volunteer, fellow, advisor, and participant coverage where appropriate; m) international, cross-border, state, territorial, Tribal-interface, and North America activity coverage where appropriate; and n) other coverage approved by the Board or authorized officer.
Insurance procurement shall be subject to Board oversight or delegated approval, budget authority, procurement controls, conflict review, broker and adviser boundary review, coverage review, exclusion review, claims-handling protocol, renewal review, and records discipline.
The Corporation shall not characterize insurance purchase as certification of compliance, elimination of risk, public authority approval, finance-readiness, insurance-readiness determination, rating, procurement approval, or permission to operate beyond lawful authority.
128.16 Insurance Not as Waiver of Duties. Insurance shall not waive or reduce any duty under law, the Articles or Certificate, this Bylaw, fiduciary principles, Board policy, officer delegation, committee charter, participation terms, confidentiality agreement, data / AI / cyber rule, safeguards rule, public-safe publication rule, conflict rule, or controlled-room rule.
The existence of insurance shall not: a) authorize prohibited functions; b) excuse lack of Board approval; c) excuse lack of member approval where required; d) cure private inurement; e) cure excess benefit; f) cure conflict or recusal failure; g) cure unauthorized public authority representation; h) cure finance, securities, investment adviser, broker-dealer, finder, banking, lending, insurance, underwriting, rating, public finance, procurement, certification, recognition, or professional-boundary breach; i) cure data misuse, AI misuse, cyber misconduct, privacy breach, research misconduct, protected knowledge breach, public-safe publication failure, or civil rights violation; j) cure sponsor control, provider preference, or enterprise execution; k) replace records, legal hold, correction, or incident response; or l) imply that the Corporation has accepted a risk that it is legally or missionally required to avoid.
Every insured activity must still satisfy law, mission, authority, boundary, records, and correction requirements.
128.17 Liability Limitations to Extent Permitted by Law. To the fullest extent permitted by applicable law and the Articles or Certificate, the personal liability of Directors, officers, and other eligible persons may be limited for actions taken in good faith within authorized service to the Corporation.
Any liability limitation shall be construed narrowly and lawfully. It shall not eliminate liability where elimination is prohibited by law, including for bad faith, intentional misconduct, knowing violation of law, improper personal benefit, private inurement, unlawful distribution, fraud, willful misconduct, or other non-exculpable conduct.
Liability limitation shall not create: a) immunity from fiduciary duty; b) immunity from compliance duties; c) immunity from records duties; d) immunity from conflict and recusal duties; e) immunity from confidentiality duties; f) immunity from data / AI / cyber, privacy, research integrity, public-safe publication, safeguards, civil rights, accessibility, protected knowledge, or non-retaliation duties; g) immunity from public authority, finance, certification, procurement, recognition, provider-neutrality, or sponsor non-control boundaries; h) immunity from lawful investigation, correction, repayment, removal, suspension, access restriction, legal hold, disclosure, or referral; or i) authority to perform prohibited functions.
The Corporation may include liability limitation language in policies, agreements, notices, participation terms, publications, controlled-room materials, insurance documents, and governance instruments, provided such language is lawful, accurate, public-safe, and consistent with this Bylaw.
128.18 Indemnification, Advancement, Insurance, and Liability Records. The Corporation shall maintain Indemnification, Advancement, Insurance, and Liability Records sufficient to demonstrate lawful eligibility, approval, reasonableness, conflict management, insurance coordination, payment integrity, repayment treatment, legal compliance, nonprofit integrity, public-benefit alignment, and correctionability.
Such records shall include, as applicable: a) indemnification policy; b) advancement policy; c) insurance policy register; d) liability limitation policy; e) indemnification agreements; f) advancement requests; g) indemnification requests; h) claimant role and authority records; i) proceeding, claim, inquiry, investigation, or matter records; j) notice to the Corporation; k) notice to insurers; l) coverage analysis; m) reservation of rights records; n) counsel engagement records; o) conflict disclosures; p) recusal records; q) Board, committee, independent counsel, court, member, or other approval records; r) eligibility determinations; s) good-faith determinations; t) lawful conduct determinations; u) best-interest determinations where applicable; v) excluded conduct analysis; w) allocation records for covered and uncovered matters; x) expense invoices; y) reasonableness review records; z) advancement payment records; aa) repayment undertakings; bb) repayment records; cc) indemnification payment records; dd) insurance proceeds records; ee) settlement approval records; ff) judgment, fine, penalty, or award records; gg) denial, limitation, suspension, or termination records; hh) correction, supersession, withdrawal, retraction, takedown, quarantine, legal hold, or public-safe clarification records where related; ii) insurance procurement records; jj) insurance renewal records; kk) broker, adviser, consultant, and carrier conflict records; ll) policy exclusion and coverage gap records; mm) claims-handling records; nn) incident and post-incident review records; oo) disclosure records where required; pp) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that indemnification, advancement, insurance, and liability protection exist to protect lawful service, not unlawful conduct. The Corporation may protect eligible persons who act in good faith, within authority, for public-benefit purposes, and in accordance with law and this Bylaw; it shall not convert protection into impunity, private benefit, role collapse, sponsor control, provider preference, public authority substitution, finance execution, certification, procurement approval, recognition, public warning, emergency command, or enterprise execution. Every protection shall be lawful, recorded, bounded, reviewable, conflict-managed, insurance-aware, and correctionable.
Section 129. Board Records, Registers, and Public-Safe Transparency
129.1 Board Register. The Corporation shall maintain a Board Register as an authoritative governance record identifying the existence, composition, authority, status, and continuity of the Board. The Board Register shall be maintained under the custody of the Secretary or other duly designated records custodian and shall be subject to this Bylaw, applicable law, the Articles or Certificate, records policies, confidentiality classifications, repository discipline, retention rules, legal hold requirements, and correctionability.
The Board Register shall record, as applicable:
a) the current legal name of the Corporation, the governing state law, the Articles or Certificate reference, the Bylaw version, the operative Board authority source, and the current Board governance status;
b) the number of authorized Directors, the number of seated Directors, the number of vacancies, any minimum or maximum number of Directors, any class or staggered-term structure where adopted, and any member-approval requirements where applicable;
c) the names, terms, offices, committee assignments, leadership roles, independence classifications, conflict status, training status, and access classifications of Directors;
d) the date of appointment, election, renewal, resignation, removal, expiration, vacancy, suspension of access, or other status change for each Director;
e) the Board’s reserved matter structure, delegation interface, emergency governance interface, continuity interface, committee interface, officer interface, and Nexus interface oversight role; and
f) the repository location, custodian, review date, retention class, access class, publication class, archive status, legal hold status, correction history, and metadata for Board records.
The Board Register shall be treated as a governance-validity instrument. It shall evidence Board composition and governance status for internal corporate purposes, but it shall not by itself create authority inconsistent with applicable law, the Articles or Certificate, this Bylaw, member approval requirements where applicable, or a competent Board record.
No informal list, slide, website page, grant schedule, sponsor-facing document, public authority deck, meeting attendee list, AI summary, spreadsheet, repository readme, public explainer, or external directory shall substitute for the Board Register unless adopted, reconciled, versioned, and recorded as an official register or public-safe extract.
129.2 Director Register. The Corporation shall maintain a Director Register identifying each Director who is or has been duly elected, appointed, seated, renewed, resigned, removed, suspended, disqualified, deceased, incapacitated, or otherwise recorded in relation to Board service.
The Director Register shall include, as applicable:
a) legal name, preferred professional name where appropriate, contact information, state or jurisdictional location where relevant, institutional affiliation where disclosed, and capacity in which the person serves;
b) appointment or election authority, appointing or electing body, resolution or consent reference, effective date, term commencement, term expiration, renewal eligibility, class or seat designation where applicable, and holdover status where permitted;
c) consent to serve, fiduciary acknowledgments, confidentiality acknowledgments, conflict disclosures, independence review, fit-and-proper review, sanctions or export-control screening where applicable, data / AI / cyber access eligibility, controlled-room eligibility, and safeguards eligibility;
d) offices held, committee memberships, committee chair roles, Board leadership roles, public authority interface restrictions, finance-boundary restrictions, certification-boundary restrictions, procurement-neutrality restrictions, provider-neutrality restrictions, sponsor non-control restrictions, and recusal patterns;
e) resignation, removal, vacancy, suspension, access restriction, non-renewal, disqualification, death, incapacity, or other end-of-service records; and
f) transition, handover, access revocation, records return, credential revocation, confidentiality survival, conflict survival, legal hold, and post-service restriction records.
The Director Register shall be maintained with strict accuracy because Director identity, term, authority, eligibility, and access status are foundational to lawful Board action, quorum, voting, written consents, committee authority, emergency governance, and validity-by-record.
A person shall not be treated as a Director merely because the person is a founder, incorporator, officer, advisor, fellow, sponsor representative, donor representative, provider representative, public authority participant, technical lead, committee member, community representative, university participant, laboratory participant, Nexus interface participant, or named public supporter unless the person has been lawfully elected or appointed and entered in the Director Register by competent record.
129.3 Officer Interface Register. The Corporation shall maintain an Officer Interface Register to preserve the relationship between Board governance authority and officer implementation authority. The Officer Interface Register shall identify officers, officer roles, appointment authority, delegated authority, reporting duties, authority limits, records duties, compensation status where applicable, and Board oversight pathways.
The Officer Interface Register shall include, as applicable:
a) the name, title, office, appointment date, appointment authority, term or at-will status, reporting line, authority source, delegation reference, and authority matrix reference for each officer;
b) statutory officer status, non-statutory officer status, executive leadership status, management status, secretariat status, technical leadership status, or advisory status, as applicable;
c) signature authority, banking authority, spending authority, contracting authority, hiring authority, publication authority, data access authority, AI-use authority, repository authority, controlled-room authority, public authority reference authority, correction authority, and emergency authority;
d) officer conflicts, recusals, related-party restrictions, compensation review, reimbursement controls, data / AI / cyber access class, public authority capacity restrictions, finance-boundary restrictions, certification-boundary restrictions, procurement-boundary restrictions, provider-neutrality restrictions, and sponsor non-control restrictions;
e) Board reporting schedule, committee reporting duties, escalation duties, incident duties, correction duties, and records certification duties; and
f) resignation, removal, suspension, vacancy, acting officer status, interim delegation, succession, handover, access revocation, and closeout records.
The Officer Interface Register shall prevent silent authority inflation by ensuring that officers act only within recorded appointment, delegation, budget authority, policy authority, and Board-approved scope. No officer shall acquire additional authority by seniority, title, technical centrality, public prominence, donor relationship, sponsor relationship, provider relationship, public authority contact, repository access, AI system access, or Nexus interface role.
129.4 Board Resolution Register. The Corporation shall maintain a Board Resolution Register containing adopted resolutions, written consents, reserved matter approvals, emergency ratifications, committee creations, officer appointments, delegations, policy approvals, budget approvals, major transaction approvals, public authority interface approvals, records approvals, correction approvals, and other governance acts of the Board.
The Board Resolution Register shall identify, for each resolution or written consent:
a) resolution number or unique identifier;
b) date of meeting or consent;
c) meeting type, notice status, waiver status, quorum status, and voting standard;
d) text of the resolution or action approved;
e) materials reviewed or incorporated by reference;
f) Directors present, absent, voting, abstaining, recused, or dissenting where recorded;
g) conflicts disclosed and recusals applied;
h) authority source, including applicable law, Articles or Certificate, Bylaw provision, policy, delegation, or reserved matter classification;
i) effective date, conditions, sunset, review date, responsible owner, implementation requirements, and reporting requirements;
j) related registers, policies, contracts, filings, notices, repository entries, gazette entries, public-safe summaries, or correction records; and
k) repository location, access class, publication class, retention class, legal hold status, archive status, and metadata.
No Board resolution shall be silently altered after adoption. Corrections to clerical errors, metadata errors, formatting errors, or non-substantive defects shall be recorded. Material correction, amendment, rescission, ratification, supersession, or restatement shall require competent Board action or other lawful authority.
Where a resolution relates to public authority interfaces, finance-adjacent matters, certification-adjacent matters, procurement-adjacent matters, recognition-adjacent matters, controlled technology, protected knowledge, data / AI / cyber systems, public-safe publication, sponsorship, restricted funds, provider participation, or Nexus interfaces, the Resolution Register shall include boundary language sufficient to prevent overclaim, reliance error, and authority confusion.
129.5 Reserved Matters Register. The Corporation shall maintain a Reserved Matters Register identifying matters that require Board approval, member approval where applicable, higher voting thresholds, legal review, tax review, counsel review, public-safe review, safeguards review, data / AI / cyber review, public authority boundary review, finance-boundary review, certification-boundary review, procurement-neutrality review, provider-neutrality review, or sponsor non-control review.
The Reserved Matters Register shall classify reserved matters by subject, approval authority, threshold, review pathway, records requirement, and implementation limitation. It may include, without limitation:
a) amendments to the Articles or Certificate, this Bylaw, mission lock, nonprofit character, public-benefit purpose, tax status, non-execution boundary, all-states-and-territories posture, North America anchor role, or Nexus role-separation architecture;
b) annual strategy, annual plan, annual budget, material budget amendments, major grants, major donations, major sponsorships, restricted funds, support arrangements, major contracts, debt, leases, asset transfers, intellectual property transfers, repository transfers, and technical asset dispositions;
c) officer appointments, officer removals, Board committee creation, committee dissolution, major policy adoption, public authority protocols, data / AI / cyber policies, safeguards policies, public-safe publication policies, sponsorship policies, sanctions policies, export-control policies, competition policies, controlled-technology policies, and records policies;
d) public authority interfaces, regulator-listening arrangements, public finance reader arrangements, emergency-management learning arrangements, controlled rooms, data rooms, clean rooms, evidence rooms, public authority rooms, and no-download rooms;
e) litigation, investigations, regulatory engagement, settlements, enforcement matters, public corrections, takedowns, retractions, withdrawals, legal holds, incidents, and crisis governance matters; and
f) dissolution, merger, consolidation, conversion, sale of substantially all assets, wind-up, public-good asset distribution, or any other structural act requiring heightened authority.
A Reserved Matters Register shall not reduce the Board’s obligations under law, the Articles or Certificate, this Bylaw, or fiduciary duties. If a matter is not listed but is material to mission, law, tax status, public-benefit purpose, non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, public-safe publication, Nexus role separation, validity-by-record, or correctionability, the matter shall be treated as reserved pending Board review.
129.6 Conflict and Recusal Register. The Corporation shall maintain a Conflict and Recusal Register for Directors, officers, committee members, advisors, fellows, employees, contractors, volunteers, contributors, public authority participants, sponsors, providers, donors, funders, hosts, and other persons whose interests, affiliations, duties, or relationships may affect governance, access, deliberation, recommendation, approval, publication, technical work, public authority interface, finance-adjacent output, safeguards review, or Nexus interface activity.
The Conflict and Recusal Register shall include, as applicable:
a) annual conflict disclosures;
b) event-based conflict disclosures;
c) related-party disclosures;
d) financial, institutional, professional, academic, public authority, sponsor, provider, donor, funder, host, investor, insurer, lender, bank, public finance actor, national company, Project SPV, enterprise-stack, university, laboratory, community, media, political, campaign, lobbying, government ethics, research, data / AI / cyber, protected knowledge, or personal conflicts;
e) recusal determinations;
f) access restrictions;
g) deliberation restrictions;
h) voting restrictions;
i) committee eligibility restrictions;
j) publication restrictions;
k) controlled-room restrictions;
l) mitigation measures;
m) independent review records;
n) conflict waiver or management records where lawful;
o) unresolved conflict records; and
p) violation, correction, removal, suspension, or public-safe clarification records.
The Register shall distinguish between disclosed and managed conflicts, unmanaged conflicts, prohibited conflicts, apparent conflicts, structural capture risks, and conflicts that require recusal, restriction, refusal, resignation, removal, or termination of relationship.
A conflict disclosure shall not cure a conflict unless the competent authority reviews, manages, records, and limits the conflict as required. A recusal shall be effective only if it includes exclusion from deliberation, recommendation, vote, approval, access, or influence to the extent required by law, policy, or the Board.
129.7 Board Training Register. The Corporation shall maintain a Board Training Register to record onboarding, fiduciary development, continuing governance education, technical literacy, legal compliance training, data / AI / cyber training, public authority boundary training, finance-boundary training, safeguards training, public-safe publication training, competition training, sanctions training, export-control training, controlled-technology training, and Nexus role-separation training completed or required for Directors.
The Board Training Register shall include, as applicable:
a) onboarding completion;
b) fiduciary duty training;
c) United States nonprofit governance training;
d) tax-exempt or tax-exempt-compatible training;
e) public-benefit and mission-lock training;
f) non-execution training;
g) GCRI / GRF / GRA role-separation training;
h) public-good stack and enterprise stack separation training;
i) public authority boundary training;
j) finance, securities, investment adviser, broker-dealer, finder, banking, lending, insurance, underwriting, rating, public finance, procurement, certification, recognition, provider-neutrality, and sponsor non-control boundary training;
k) data governance, privacy, AI governance, cybersecurity, secure compute, repository security, incident response, business continuity, and disaster recovery training;
l) research integrity, evidence doctrine, methods stewardship, observability, ontology, public-safe publication, technical truth, public-good software, open technical baseline, and correctionability training;
m) civil rights, accessibility, Tribal and Indigenous protocol, protected knowledge, public-safe mapping, community safeguards, grievance, remedy, protected participation, whistleblowing, and non-retaliation training;
n) competition, antitrust, sanctions, export-control, controlled technology, national security sensitivity, professional-boundary, lobbying, political activity, government ethics, gifts, grant, and procurement integrity training where applicable; and
o) date, provider, format, materials, certification of understanding, required renewal date, incomplete training, corrective training, and access consequence records.
A Director may be restricted from accessing sensitive materials, controlled rooms, public authority materials, cyber-sensitive materials, finance-sensitive materials, protected knowledge, technical repositories, public-safe publication approval processes, or other high-risk functions until required training and acknowledgments have been completed.
129.8 Board Evaluation Register. The Corporation shall maintain a Board Evaluation Register recording Board self-assessments, Director performance reviews, Board skills matrix reviews, independence reviews, conflict reviews, attendance reviews, committee performance reviews, leadership reviews, succession reviews, refreshment reviews, Board culture reviews, external advisor reviews, and corrective actions arising from Board evaluation.
The Board Evaluation Register shall include, as applicable:
a) evaluation cycle, methodology, responsible owner, confidentiality class, reviewer, and materials considered;
b) Board-level findings on fiduciary performance, mission stewardship, legal compliance, records discipline, strategic oversight, risk oversight, technical oversight, public authority boundary control, finance-boundary control, safeguards oversight, data / AI / cyber oversight, Nexus alignment, and correctionability;
c) individual Director findings where approved, including attendance, preparation, contribution, independence, confidentiality, conflicts, training, committee contribution, and role suitability;
d) skills matrix gaps, recruitment needs, committee restructuring needs, leadership succession needs, training needs, continuity needs, and external advisor needs;
e) anti-capture findings, sponsor influence concerns, provider influence concerns, donor concentration concerns, public authority dependency concerns, technical-team dependency concerns, founder dependency concerns, and enterprise-stack influence concerns;
f) corrective action, mentoring, additional training, access restriction, committee reassignment, leadership transition, recruitment, non-renewal, resignation request, removal where lawful, or other governance response; and
g) follow-up, completion, supersession, archive, and retention records.
Evaluation records shall be protected according to their sensitivity. They may be confidential, privileged, personnel-sensitive, governance-sensitive, or legally restricted. Public-safe summaries may be prepared only where approved and only in a manner that does not disclose protected information, chill dissent, expose confidential deliberation, or distort governance meaning.
129.9 Board Delegation Register. The Corporation shall maintain a Board Delegation Register identifying every delegation of authority from the Board to officers, committees, employees, contractors, advisors, custodians, working groups, controlled-room leads, public authority interface leads, repository administrators, technical release leads, or other authorized persons.
The Board Delegation Register shall include, as applicable:
a) delegating authority;
b) recipient of delegation;
c) legal and Bylaw authority for delegation;
d) scope of authority;
e) excluded matters;
f) budget limit;
g) contract limit;
h) signature limit;
i) publication limit;
j) data access limit;
k) AI-use limit;
l) repository access limit;
m) controlled-room admission limit;
n) public authority reference limit;
o) finance-boundary limit;
p) certification and procurement boundary limit;
q) safeguards limit;
r) effective date, expiration date, review date, revocability, conditions, reporting duties, and records duties; and
s) suspension, amendment, revocation, ratification, correction, or supersession records.
The Delegation Register shall identify Board reserved matters that may not be delegated, prohibited functions that may not be delegated, and emergency authority that may be used only under defined triggers, time limits, notice, ratification, and sunset controls.
No delegation shall be implied from prior practice, title, role, urgency, seniority, founder status, technical necessity, sponsor request, provider request, public authority request, repository access, data-room access, AI-system access, or committee membership. Delegations shall be recorded, bounded, reviewable, revocable, and correctionable.
129.10 Board Policy Register. The Corporation shall maintain a Board Policy Register identifying all Board-approved policies, schedules, protocols, matrices, forms, registers, controlled vocabularies, public-safe notice libraries, operating procedures, committee charters, program charters, authority matrices, risk matrices, data / AI / cyber instruments, safeguards instruments, public authority instruments, and Nexus interface instruments adopted or approved by the Board.
The Board Policy Register shall include, as applicable:
a) title, short title, instrument class, version, status, adopting authority, approval record, effective date, review date, custodian, repository location, access class, publication class, retention class, archive status, and metadata;
b) policy scope, affected roles, affected records, affected systems, affected interfaces, affected public materials, affected repositories, and affected controlled rooms;
c) higher-order authority, Bylaw cross-reference, supersession history, amendment history, withdrawal history, archive history, transition rules, savings rules, and implementation rules;
d) training requirements, notices, public-safe summaries, controlled vocabulary implications, limitation language, non-reliance language, and public-safe publication implications;
e) legal, tax, nonprofit, data / AI / cyber, public authority, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, sponsor non-control, competition, sanctions, export-control, controlled-technology, safeguards, civil rights, accessibility, protected knowledge, and research integrity review records; and
f) correction, challenge, escalation, review, sunset, and renewal pathways.
No policy or implementing instrument shall be treated as current Board authority unless entered in the Board Policy Register or otherwise recorded in an official repository with competent approval. Superseded, withdrawn, draft, archived, public-summary, translated, redlined, AI-generated, or unofficial copies shall not be treated as operative authority.
129.11 Board Risk Register Interface. The Board shall maintain an interface with the Corporation’s risk register sufficient to enable Board oversight of strategic, legal, tax, nonprofit, financial, operational, data / AI / cyber, research, evidence, technical, public authority, finance-boundary, certification-boundary, procurement-boundary, provider-neutrality, sponsor non-control, safeguards, community, protected knowledge, reputational, continuity, and Nexus interface risks.
The Board Risk Register Interface shall ensure that the Board receives, reviews, and records material risk information, including:
a) risk category, description, owner, likelihood, impact, severity, control status, mitigation, residual risk, escalation status, and review date;
b) mission-lock risk, non-execution risk, public authority confusion risk, finance overclaim risk, certification overclaim risk, procurement overclaim risk, recognition overclaim risk, provider-preference risk, sponsor-control risk, and private-benefit risk;
c) data breach risk, AI incident risk, cyber incident risk, repository compromise risk, controlled-technology risk, export-control risk, sanctions risk, competition risk, privacy risk, public-safe publication risk, and technical asset risk;
d) community harm risk, civil rights risk, accessibility risk, Indigenous protocol risk, protected knowledge risk, public-safe mapping risk, grievance risk, retaliation risk, and do-no-harm risk;
e) legal, regulatory, investigation, litigation, audit, tax, grant, funding, public authority, cross-border, state, territorial, Tribal-interface, and North America interface risk; and
f) assigned response, Board action, committee action, officer action, hold, quarantine, re-scope, externalize, refer, terminate, correct, supersede, withdraw, retract, takedown, disclose, or monitor decision.
The Board Risk Register Interface shall not convert risk classification into a rating, certification, finance-readiness determination, insurance-readiness determination, procurement approval, recognition, public warning, emergency command, public authority decision, provider approval, or sponsor entitlement.
129.12 Board Incident Register Interface. The Board shall maintain an interface with the Corporation’s incident register sufficient to ensure that material incidents are escalated, reviewed, recorded, corrected, and closed under Board oversight where required.
The Board Incident Register Interface shall include, as applicable:
a) incident identifier, date, source, reporter, responsible owner, category, severity, affected persons, affected systems, affected records, affected repositories, affected rooms, affected public materials, affected public authority interfaces, affected Nexus interfaces, and affected safeguards;
b) incident categories, including governance incident, fiduciary incident, conflict incident, confidentiality incident, records incident, public-safe publication incident, data incident, privacy incident, AI incident, cybersecurity incident, repository incident, controlled-technology incident, research integrity incident, evidence incident, method incident, technical asset incident, public authority boundary incident, finance-boundary incident, certification-boundary incident, procurement-boundary incident, provider-neutrality incident, sponsor non-control incident, safeguards incident, protected knowledge incident, civil rights incident, accessibility incident, retaliation incident, and competition incident;
c) immediate measures, hold, stop, quarantine, access restriction, publication freeze, implementation freeze, technical isolation, controlled-room lockdown, legal hold, notice, insurance notice, counsel notice, public authority notice where required, funder notice where required, and public-safe notice where approved;
d) investigation, root-cause analysis, corrective action, disciplinary action, contractual remedy, security remediation, correction, supersession, withdrawal, retraction, takedown, archive, public clarification, and lessons-learned records; and
e) Board review, committee review, officer review, counsel review, compliance review, safeguards review, data / AI / cyber review, insurance review, and closure record.
No incident shall be hidden, minimized, reclassified, delayed, or closed merely to preserve reputation, satisfy a sponsor, protect a provider, avoid public authority discomfort, avoid funder concern, maintain publication timelines, preserve technical momentum, or avoid correction.
129.13 Board Correction Register Interface. The Board shall maintain an interface with the Corporation’s correction register sufficient to ensure that material errors, omissions, overclaims, boundary breaches, public-safe publication concerns, evidence defects, method defects, data defects, AI defects, cyber defects, safeguards concerns, public authority confusion, finance overclaims, certification overclaims, procurement overclaims, recognition overclaims, provider-preference claims, sponsor-control claims, and Nexus interface errors are corrected under appropriate authority.
The Board Correction Register Interface shall include, as applicable:
a) correction identifier, affected record, affected publication, affected dashboard, affected map, affected software release, affected repository, affected proof receipt, affected public authority material, affected controlled room, affected policy, affected technical baseline, affected Board record, affected committee record, or affected Nexus interface record;
b) correction type, including clarification, limitation, erratum, metadata correction, version correction, controlled vocabulary correction, boundary correction, public-safe notice addition, supersession, withdrawal, retraction, takedown, quarantine, archive, legal hold, public correction, controlled correction, or internal correction;
c) error source, reporter, challenge, review body, responsible owner, authority, effective date, correction text, affected parties, notice class, access class, publication class, and retention class;
d) legal, tax, nonprofit, data / AI / cyber, public authority, finance-boundary, certification-boundary, procurement-boundary, recognition-boundary, provider-neutrality, sponsor non-control, safeguards, protected knowledge, research integrity, competition, sanctions, export-control, and counsel review where required; and
e) Board review, committee review, officer review, ratification, implementation, follow-up, closure, supersession, and archive records.
Correction shall be treated as an institutional duty, not an admission to be avoided. The Board shall preserve a culture in which errors can be reported, tested, corrected, limited, withdrawn, superseded, retracted, or archived without retaliation and without concealment.
129.14 Board Public-Safe Transparency. The Board may authorize public-safe transparency regarding Board governance, mission, purposes, policies, committees, leadership, public-benefit orientation, non-execution boundaries, public authority boundaries, finance boundaries, data / AI / cyber controls, safeguards, public-good software, technical baselines, public-safe publications, and Nexus role separation, provided that such transparency is accurate, lawful, records-supported, non-misleading, and consistent with confidentiality, privilege, privacy, security, protected knowledge, public authority, competition, tax, grant, and legal limitations.
Board public-safe transparency may include:
a) public-safe governance summaries;
b) public-safe descriptions of Board composition and governance structure;
c) public-safe summaries of mission, nonprofit character, public-benefit purpose, non-execution role, public authority boundary, finance boundary, certification and procurement boundary, provider neutrality, sponsor non-control, and Nexus role separation;
d) public-safe summaries of adopted policies, controlled vocabularies, public-safe notice libraries, records discipline, correctionability, and validity-by-record;
e) public-safe annual governance, compliance, risk, safeguards, or impact summaries where approved;
f) public-safe summaries of committee architecture, advisory bodies, public authority learning interfaces, controlled rooms, research integrity systems, data / AI / cyber governance systems, and public-good technical asset stewardship; and
g) public-safe correction, supersession, withdrawal, retraction, takedown, archive, or clarification notices where required or approved.
Public-safe transparency shall not disclose privileged information, confidential Board deliberations, protected knowledge, personal information, rights-bearing data, cyber-sensitive details, infrastructure-sensitive details, security controls, legal strategy, investigation details, public authority confidential materials, trade secrets, sponsor confidential information, provider confidential information, donor confidential information, research confidential information, or information that would create harm or unlawful reliance.
Transparency shall not be used to market recognition, finance-readiness, certification, procurement advantage, public authority endorsement, provider preference, sponsor control, investment suitability, rating, emergency command, public warning, or enterprise execution.
129.15 Public-Safe Governance Summaries Where Approved. The Corporation may prepare public-safe governance summaries explaining the Board’s role, governance framework, reserved matters, committees, officers, records discipline, public-benefit purpose, non-execution posture, public authority boundary, finance boundary, data / AI / cyber controls, safeguards, correctionability, and Nexus alignment.
A public-safe governance summary shall be:
a) approved by the Board or authorized officer within delegation;
b) based on current operative records;
c) versioned, dated, and repository-referenced;
d) written in controlled vocabulary;
e) accompanied by appropriate limitation and non-reliance language;
f) reviewed for public authority overclaim, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider preference, sponsor control, and enterprise execution implications;
g) reviewed for confidentiality, privilege, privacy, data / AI / cyber, protected knowledge, public-safe mapping, civil rights, accessibility, competition, sanctions, export-control, and public authority constraints where relevant; and
h) corrected, superseded, withdrawn, or archived when no longer accurate.
A public-safe governance summary is explanatory only. It shall not amend the Articles or Certificate, this Bylaw, Board resolutions, registers, policies, delegations, committee charters, officer authority, public authority capacity records, or Nexus interface instruments. Where a summary conflicts with an operative record, the operative record controls and the summary shall be corrected.
129.16 Confidentiality, Privilege, Privacy, Public Authority, Cybersecurity, Protected Knowledge, and Legal Limits on Transparency. The Board shall preserve transparency only within lawful and safe limits. The Corporation shall not disclose information where disclosure would violate law, fiduciary duty, privilege, confidentiality, contract, data protection obligations, privacy rights, research ethics, public authority obligations, cybersecurity duties, protected knowledge safeguards, civil rights obligations, accessibility obligations, competition obligations, sanctions obligations, export-control obligations, court orders, legal holds, investigation protocols, grant terms, donor restrictions, sponsor restrictions, provider restrictions, or other binding obligations.
Transparency limits shall apply to:
a) attorney-client privileged materials and attorney work product;
b) Board executive-session materials and confidential deliberations;
c) personal information, rights-bearing data, health-sensitive data, youth data, public sector data, public authority data, and protected participant data;
d) cyber-sensitive, infrastructure-sensitive, controlled-technology, national security-sensitive, repository-sensitive, key, token, credential, incident, vulnerability, or secure-release materials;
e) Tribal, Indigenous, local, territorial, cultural, environmental, community-protected, and protected knowledge;
f) public authority confidential materials, regulator-listening materials, public finance reader materials, emergency-management learning materials, and controlled-room materials;
g) sponsor, donor, funder, provider, host, contractor, university, laboratory, or partner confidential information;
h) internal investigations, misconduct reviews, disciplinary records, employment matters, contractor matters, volunteer matters, fellow matters, advisor matters, grievance matters, remedy matters, whistleblower matters, retaliation matters, and litigation materials; and
i) any information whose publication would create public reliance error, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider preference, sponsor control, market distortion, security harm, community harm, or legal exposure.
Where transparency and protection conflict, the Corporation shall apply the most protective lawful posture pending review. The Board may authorize controlled notice, delayed notice, redacted notice, aggregate notice, public-safe summary, counsel-facing disclosure, regulator-facing disclosure, funder-facing disclosure, affected-person notice, or no disclosure where lawful and justified.
129.17 Board Records Retention. The Corporation shall retain Board records in accordance with applicable law, the Articles or Certificate, this Bylaw, Board-approved records policy, tax requirements, nonprofit requirements, corporate requirements, charitable solicitation requirements, grant requirements, contract requirements, audit requirements, legal hold obligations, insurance requirements, data / AI / cyber obligations, public authority obligations, safeguards obligations, and Nexus interface requirements.
Board records retention shall apply to:
a) Articles or Certificate, Bylaw, amendments, restatements, adoption records, and repository records;
b) Board minutes, resolutions, written consents, notices, waivers, agendas, materials, attendance records, quorum records, vote records, abstention records, recusal records, dissent records where permitted, and action-item records;
c) Director registers, officer interface registers, committee registers, delegation registers, authority matrices, reserved matter registers, policy registers, conflict registers, risk register interfaces, incident register interfaces, correction register interfaces, and public-safe transparency records;
d) Board evaluation, training, succession, continuity, compensation, reimbursement, indemnification, insurance, and liability records;
e) public authority interface records, finance-boundary records, certification-boundary records, procurement-boundary records, provider-neutrality records, sponsor non-control records, data / AI / cyber records, safeguards records, protected knowledge records, public-safe publication records, evidence records, method records, technical asset records, repository records, and Nexus interface records;
f) legal, tax, audit, grant, donation, sponsorship, restricted fund, charitable solicitation, state qualification, foreign qualification, employment, contractor, volunteer, fellow, advisor, insurance, litigation, investigation, regulatory, and compliance records; and
g) correction, supersession, withdrawal, retraction, takedown, quarantine, legal hold, archive, secure disposal, deletion, sealing, and destruction records.
Retention periods may differ by record class. Permanent records shall be preserved permanently unless lawful destruction is required. Records subject to legal hold, investigation hold, audit hold, public authority hold, insurance hold, grievance hold, protected knowledge hold, data incident hold, cyber incident hold, AI incident hold, or litigation hold shall not be destroyed until the hold is lawfully released.
129.18 Board Records Access, Sealing, Deletion, Archival, and Secure Disposal. The Corporation shall govern access, sealing, deletion, archival, and secure disposal of Board records through controlled procedures consistent with law, fiduciary duties, privilege, confidentiality, privacy, data / AI / cyber controls, public authority obligations, protected knowledge safeguards, records retention, legal holds, correctionability, and validity-by-record.
Board records access shall be role-based, need-to-know, least-privilege, auditable, and revocable. Access may be granted to Directors, officers, committee members, counsel, auditors, insurers, regulators, public authorities, funders, employees, contractors, advisors, repository custodians, records custodians, or other persons only where lawful, authorized, and recorded.
Sealing may be used where records contain sensitive deliberations, privileged material, personal information, protected knowledge, cyber-sensitive information, infrastructure-sensitive information, public authority confidential material, investigation material, grievance material, whistleblower material, or other restricted content. Sealed records shall remain preserved, indexed, and retrievable by authorized persons under approved conditions.
Deletion or secure disposal may occur only where permitted by law, retention rules, legal hold status, audit obligations, investigation obligations, grant obligations, contract obligations, data protection requirements, public authority obligations, and Board policy. Secure disposal shall include appropriate destruction, deletion, cryptographic erasure, credential revocation, access revocation, repository pruning, archive sealing, or other secure process suitable to the record type.
Archival shall preserve historical traceability. Superseded, withdrawn, corrected, retracted, or archived records shall not be treated as current authority, but they shall remain traceable where necessary to show governance history, validity chain, correction history, public-safe limitation, legal compliance, and institutional memory.
The governing rule of this Section is that Board records are the legal memory of the Corporation. They prove authority, preserve fiduciary seriousness, prevent silent drift, discipline public claims, protect legal separateness, support public-safe transparency, enable correction, and demonstrate that GCRI US remains a United States nonprofit, public-benefit, non-executing technical institution within the Nexus public-good stack. Board records shall therefore be accurate, complete, versioned, secure, confidential where required, transparent where safe, retained where necessary, corrected where defective, and never inflated into authority beyond the competent record.
Section 130. Board Enforcement of Article IV
130.1 Article IV Enforcement Purpose. The Board shall enforce this Article IV to preserve the lawful governance, fiduciary integrity, public-benefit mission, nonprofit character, tax-exempt or tax-exempt-compatible posture, United States legal separateness, all-states-and-territories operating discipline, North America anchor boundaries, non-execution perimeter, public authority boundary, finance boundary, procurement-neutrality boundary, certification boundary, provider-neutrality boundary, sponsor non-control rule, data / AI / cyber controls, research integrity, community safeguards, protected knowledge controls, validity-by-record, correctionability, and Nexus role separation of the Corporation.
Article IV enforcement is not punitive by default. It is a governance-protection function designed to ensure that Board authority is exercised only through lawful, recorded, fiduciary, conflict-managed, public-safe, mission-consistent, and correctionable processes. Enforcement may be preventive, corrective, remedial, disciplinary, protective, restorative, public-safe, confidential, legal, or structural, depending on the risk, harm, intent, recurrence, legal requirement, and governance significance of the matter.
The Board shall apply Article IV enforcement to any act, omission, record defect, authority overreach, conflict failure, confidentiality breach, boundary breach, public claim defect, data / AI / cyber incident, safeguards failure, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider-preference claim, sponsor-control concern, or failure of fiduciary conduct that materially affects or may materially affect Board governance.
Enforcement shall be conducted with fairness, independence, proportionality, confidentiality where required, public-safe transparency where appropriate, anti-retaliation protection, legal compliance, records discipline, and correctionability. No enforcement matter shall be ignored, softened, delayed, privatized, politicized, redirected, or suppressed merely to protect a Director, founder, officer, sponsor, provider, donor, funder, host, public authority relationship, enterprise actor, technical program, publication, repository, event, or institutional reputation.
130.2 Director Duty Violation Review. The Board shall review any alleged or suspected violation by a Director of fiduciary duty, legal duty, Bylaw duty, confidentiality duty, conflict duty, recusal duty, records duty, public-benefit duty, non-execution duty, public authority boundary duty, finance-boundary duty, safeguards duty, data / AI / cyber duty, or correction duty.
Director duty violation review may be triggered by:
a) failure to act in good faith, with care, loyalty, diligence, prudence, independence, or obedience to mission and law where applicable;
b) failure to prepare for or participate in Board work where the failure materially affects governance continuity, quorum, oversight, or reserved matter review;
c) failure to disclose a conflict, related-party interest, dual-role concern, sponsor relationship, provider relationship, donor relationship, funder relationship, public authority relationship, enterprise-stack relationship, financial interest, or institutional affiliation relevant to Board duties;
d) failure to recuse from deliberation, recommendation, vote, access, pressure, side-channel influence, or approval where recusal is required;
e) misuse of confidential information, privileged materials, Board materials, public authority materials, protected knowledge, data, AI outputs, cyber-sensitive information, technical assets, evidence, methods, publications, proof receipts, repositories, or controlled-room access;
f) misuse of the Corporation’s name, marks, seal, reports, datasets, software, technical baselines, Board title, officer interface, public authority interface, Nexus interface, GRF-facing input, GRA-facing input, or public-safe claims;
g) action inconsistent with nonprofit character, public-benefit purpose, non-distribution, no-private-inurement, no-impermissible-private-benefit, tax-exempt or tax-exempt-compatible obligations, or public trust;
h) conduct that creates or risks public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider preference, sponsor control, public warning confusion, emergency command confusion, or enterprise execution;
i) retaliation, harassment, discrimination, intimidation, suppression of dissent, suppression of correction, interference with protected participation, or breach of grievance, remedy, whistleblowing, or non-retaliation safeguards; or
j) knowing disregard of law, the Articles or Certificate, this Bylaw, Board resolutions, policies, delegations, records requirements, safeguards, controlled vocabulary, public-safe notices, or competent legal or compliance escalation.
A Director duty violation review shall identify the alleged duty, facts, affected records, affected persons, affected governance actions, affected systems, affected public materials, affected public authority interfaces, affected Nexus interfaces, conflicts, evidence, privilege status, confidentiality status, legal hold needs, interim controls, and corrective pathway.
130.3 Governance Process Violation Review. The Board shall review any governance process violation that may impair lawful Board action, institutional validity, fiduciary record, quorum, voting, notice, meeting process, written consent, committee process, reserved matter treatment, delegation, ratification, emergency governance, or continuity of Board authority.
Governance process violation review may apply to:
a) defective notice, waiver, agenda, Board materials circulation, identity verification, quorum calculation, voting standard, written consent, electronic participation, abstention record, recusal record, or meeting record;
b) failure to identify a reserved matter, apply a higher approval threshold, obtain member approval where required, obtain legal review where required, obtain tax review where required, or obtain Board approval before implementation;
c) improper use of emergency Board decision-making, break-glass authority, ratification, sunset, or post-emergency review;
d) failure to record a Board decision, resolution, dissent where permitted, action item, responsible owner, deadline, follow-up, or correction;
e) informal adoption by email, chat, slide, memo, AI summary, public statement, working group practice, sponsor request, provider request, public authority request, technical release, dashboard launch, repository merge, proof receipt, ledger entry, or operational custom without competent Board action;
f) bypassing committees, officers, counsel, compliance, safeguards review, data / AI / cyber review, public authority boundary review, finance-boundary review, certification-boundary review, procurement-neutrality review, provider-neutrality review, or sponsor non-control review where required; or
g) silent amendment, operational drift, state-by-state drift, territorial drift, Tribal-interface drift, program drift, funding-agreement drift, sponsor-specific drift, provider-specific drift, public authority-specific drift, or Nexus interface drift inconsistent with this Bylaw.
Where a governance process violation is identified, the Board may hold implementation, require ratification, void or treat as non-operative an unauthorized act to the fullest extent lawful, correct the record, re-open deliberation, re-run notice, re-take a vote, obtain member approval where required, obtain legal review, reclassify the matter, impose interim restrictions, or take other corrective action necessary to restore governance validity.
130.4 Reserved Matter Violation Review. The Board shall review any act, commitment, approval, public statement, contract, policy, technical release, public authority interface, finance-adjacent activity, certification-adjacent activity, procurement-adjacent activity, sponsorship arrangement, provider arrangement, Nexus interface, controlled-room activation, repository transfer, public-safe publication, or structural decision that may have been undertaken without required Board approval as a reserved matter.
Reserved matter violation review shall consider whether the matter involved:
a) amendment, restatement, repeal, replacement, interpretation, or practical alteration of the Articles or Certificate, this Bylaw, mission lock, public-benefit purpose, nonprofit character, tax posture, non-execution boundary, all-states-and-territories posture, North America anchor role, or Nexus role-separation architecture;
b) major grants, donations, sponsorships, restricted funds, in-kind contributions, support arrangements, annual budget, material budget amendments, major contracts, debt, credit facilities, leases, intellectual property transfers, repository transfers, technical asset dispositions, or long-term obligations;
c) creation, suspension, dissolution, or material alteration of major committees, councils, controlled rooms, public authority rooms, data rooms, evidence rooms, public authority interfaces, Nexus interfaces, programs, platforms, public-good software systems, or technical baselines;
d) public authority protocols, regulator-listening arrangements, public finance reader arrangements, emergency-management learning arrangements, public authority data contributions, public authority references, public-safe dashboards, public-safe maps, or public-safe reports;
e) data, AI, cyber, privacy, research integrity, public-safe publication, safeguards, sanctions, export-control, competition, controlled-technology, sponsorship, provider-neutrality, sponsor non-control, finance-boundary, certification-boundary, procurement-neutrality, or recognition-boundary policies; or
f) litigation, investigation, regulatory engagement, settlement, enforcement matter, dissolution, merger, consolidation, conversion, sale of substantially all assets, wind-up, or public-good asset distribution.
An unauthorized reserved matter act shall not be cured merely by subsequent operational implementation, sponsor reliance, provider reliance, public authority awareness, publication, media reference, technical integration, repository merge, dashboard launch, proof receipt, ledger entry, expenditure, or elapsed time. The Board may ratify only where lawful, informed, independent, conflict-managed, recorded, and consistent with this Bylaw.
130.5 Conflict or Recusal Violation Review. The Board shall review any failure to disclose, update, manage, mitigate, record, or recuse from a conflict of interest, related-party transaction, dual-role concern, independence concern, sponsor influence concern, provider influence concern, donor or funder influence concern, host influence concern, public authority relationship, enterprise-stack relationship, financial interest, research interest, data / AI / cyber interest, technical asset interest, or personal relationship affecting Board governance.
Conflict or recusal violation review shall include, as applicable:
a) identification of the conflicted person, affected matter, relationship, interest, benefit, affiliation, role, funding source, employer, sponsor, provider, donor, funder, host, public authority, investor, insurer, lender, national company, Project SPV, university, laboratory, community, media, or enterprise connection;
b) review of whether the conflict was disclosed in advance, disclosed during deliberation, discovered after the fact, concealed, misunderstood, minimized, or left unmanaged;
c) review of whether recusal should have applied to deliberation, recommendation, vote, approval, access to materials, committee participation, controlled-room access, public authority interface, public statement, technical release, publication, contract, compensation, reimbursement, or investigation;
d) review of whether the conflicted person influenced the matter through side channels, staff pressure, sponsor pressure, provider pressure, public authority pressure, technical pressure, public messaging, draft control, agenda control, or access to confidential materials;
e) review of whether independent approval, disinterested Director approval, counsel review, tax review, nonprofit review, private benefit review, public-safe review, or safeguards review was required; and
f) review of the validity, voidability, ratification possibility, correction need, disclosure need, access restriction, committee restriction, vote exclusion, resignation, removal, repayment, contract remedy, or other response.
A conflict disclosure shall not itself validate a conflicted act. The Board shall determine whether the conflict was adequately managed, whether the record is sufficient, whether any Board action remains valid, and whether correction, ratification, withdrawal, re-vote, recusal expansion, or remedial action is required.
130.6 Confidentiality Violation Review. The Board shall review any alleged or suspected breach of confidentiality, privilege, Board material security, controlled-room restrictions, data-room restrictions, evidence-room restrictions, clean-room restrictions, no-download rules, public authority confidentiality, cyber-sensitive confidentiality, infrastructure-sensitive confidentiality, finance-sensitive confidentiality, commercially sensitive confidentiality, research confidentiality, sponsor confidentiality, provider confidentiality, donor confidentiality, personnel confidentiality, protected knowledge safeguards, or personal information protections.
Confidentiality violation review may be triggered by:
a) unauthorized disclosure, copying, download, recording, screenshot, forwarding, publication, transcription, upload, AI processing, repository posting, chat posting, social media posting, public statement, press disclosure, or external sharing;
b) use of unapproved AI systems, shadow IT, personal accounts, unapproved storage, unapproved collaboration tools, unapproved devices, unapproved transcription tools, or unapproved analytics tools for Board materials;
c) disclosure of attorney-client privileged material, work product, legal strategy, investigation material, litigation material, settlement material, insurance material, regulatory material, or counsel communications;
d) disclosure of public authority confidential materials, emergency-management learning materials, regulator-listening materials, public finance reader materials, public authority data, or public authority reference material;
e) disclosure of cyber-sensitive, infrastructure-sensitive, key, token, credential, repository, vulnerability, incident, secure-release, SBOM, controlled-technology, national security-sensitive, sanctions-sensitive, or export-control-sensitive information;
f) disclosure of Tribal, Indigenous, local, territorial, cultural, environmental, community-protected, health-sensitive, youth, vulnerable population, or protected knowledge information;
g) disclosure to sponsors, providers, donors, funders, hosts, public authorities, media, enterprise actors, investors, insurers, lenders, national companies, Project SPVs, or other external persons without authority; or
h) failure to report a confidentiality breach, suspected compromise, unauthorized access, lost device, exposed credential, or improper disclosure.
The Board may require immediate containment, access revocation, credential reset, legal hold, forensic review, counsel review, insurance notice, affected-person notice, public authority notice where required, funder notice where required, public-safe clarification where approved, deletion certification, return of materials, sealing of records, disciplinary action, contractual remedy, or legal referral.
130.7 Board Record Violation Review. The Board shall review any deficiency, alteration, omission, falsification, destruction, non-retention, unauthorized deletion, unauthorized sealing, unauthorized public release, unauthorized withholding, improper archive, metadata defect, version defect, signature defect, repository defect, register defect, gazette defect, legal hold breach, or correction failure affecting Board records.
Board record violation review shall apply to:
a) minutes, resolutions, written consents, notices, waivers, agendas, materials, attendance records, quorum records, vote records, abstention records, recusal records, dissent records where permitted, action-item records, and follow-up records;
b) Board Register, Director Register, Officer Interface Register, Board Resolution Register, Reserved Matters Register, Conflict and Recusal Register, Board Training Register, Board Evaluation Register, Board Delegation Register, Board Policy Register, risk register interface, incident register interface, and correction register interface;
c) director qualification records, independence records, training records, evaluation records, succession records, continuity records, compensation records, reimbursement records, indemnification records, insurance records, liability records, enforcement records, and legal hold records;
d) public authority records, finance-boundary records, certification-boundary records, procurement-neutrality records, provider-neutrality records, sponsor non-control records, data / AI / cyber records, safeguards records, protected knowledge records, evidence records, methods records, public-safe publication records, technical asset records, repository records, and Nexus interface records; and
e) records required for corporate law, federal tax, state tax, nonprofit compliance, charitable solicitation, grant compliance, restricted funds, audit, insurance, investigations, litigation, employment, contractor, volunteer, fellow, advisor, public authority, or cross-border obligations.
Where a Board record violation is found, the Board may require reconstruction, certification, correction, supplemental minutes, ratification, legal hold, audit trail review, metadata correction, repository restoration, access review, sealing, secure disposal, disclosure where required, training, discipline, or independent review.
No person shall alter Board records to improve optics, hide dissent, avoid conflict disclosure, obscure recusal, soften a boundary breach, satisfy a sponsor, protect a provider, preserve a public authority relationship, avoid funder concern, conceal error, prevent correction, or create authority that was not lawfully granted.
130.8 Public Authority, Finance, Certification, Procurement, Recognition, Provider-Preference, Sponsor-Control, or Public Warning Boundary Violation Review. The Board shall review any act, omission, communication, output, publication, dashboard, map, proof receipt, technical baseline, evidence pack, controlled-room activity, public authority room activity, public statement, funding material, sponsor material, provider material, grant material, bid material, investor-facing material, public finance reader material, GRA-facing input, GRF-facing input, Nexus interface material, or Board action that may violate or create confusion around boundary disciplines.
Boundary violation review shall include, as applicable:
a) public authority boundary review, including alleged public authority delegation, official adoption, regulator action, permit, compliance approval, public warning, emergency command, public health order, public safety instruction, procurement approval, funding approval, sovereign obligation, public-private partnership, public finance approval, or governmental decision;
b) finance boundary review, including alleged securities offering, securities solicitation, investment advice, broker-dealer activity, finder activity, capital placement, banking, lending, credit approval, guarantee, insurance placement, underwriting, claims handling, rating, credit opinion, investment grade opinion, bankability determination, finance-readiness determination, insurance-readiness determination, public finance approval, tax credit approval, MDB / DFI approval, or capital recommendation;
c) certification and procurement boundary review, including alleged certification, accreditation, conformance approval, compliance approval, vendor selection, procurement preference, procurement approval, qualified provider approval, standards approval, technical approval, or procurement recommendation;
d) recognition boundary review, including alleged GRF recognition, standing, maturity, legitimacy determination, Docket approval, Grid guarantee, Nexus-compatible status, badge, ranking, maturity tier, or public-facing status claim;
e) provider-neutrality review, including alleged preferred provider status, required provider status, vendor endorsement, commercial promotion, provider ranking, provider capture, provider veto, provider steering, or provider advantage;
f) sponsor non-control review, including alleged sponsor control, donor control, funder control, host control, outcome purchase, publication veto, research finding purchase, public authority access purchase, finance-readiness purchase, recognition purchase, certification purchase, procurement advantage purchase, or influence through restricted support; and
g) public warning and emergency command review, including alleged public safety command, evacuation instruction, dispatch, operational direction, infrastructure-control instruction, incident command, or emergency management substitution.
Where a boundary violation or credible boundary risk is identified, the Board shall apply hold, stop, quarantine, re-scope, correction, limitation language, withdrawal, retraction, takedown, access restriction, externalization, referral to competent authority, contract remedy, training, disciplinary action, or legal review as appropriate. No boundary violation shall be cured by disclaimer alone where the substance of the act remains unauthorized or unlawful.
130.9 Data / AI / Cyber / Privacy, Research Integrity, Civil Rights, Accessibility, Community Safeguards, Tribal / Indigenous, Protected Knowledge, or Public-Safe Publication Violation Review. The Board shall review any alleged or suspected violation involving data governance, privacy, AI governance, cybersecurity, secure compute, repository security, research integrity, evidence integrity, methods integrity, public-good software, technical baselines, public-safe publication, civil rights, accessibility, community safeguards, Tribal or Indigenous protocols, Indigenous data safeguards, local or territorial knowledge, protected knowledge, public-safe mapping, grievance, remedy, protected participation, whistleblowing, non-retaliation, or do-no-harm obligations.
Review under this subsection may apply to:
a) unauthorized data collection, access, use, transfer, linkage, retention, deletion, publication, scraping, enrichment, model training, embedding, fine-tuning, retrieval, inference, disclosure, dashboarding, mapping, or cross-border transfer;
b) unauthorized AI use, model output reliance, agentic AI action, unapproved AI upload, missing model register, missing inference record, missing compute workload record, missing human review, hallucinated authority, automated score overclaim, or AI-generated public claim defect;
c) cybersecurity incident, credential compromise, key compromise, token exposure, repository compromise, vulnerability mishandling, SBOM defect, secure-release failure, supply-chain compromise, unauthorized code merge, or controlled-technology exposure;
d) research misconduct, evidence fabrication, source-lineage failure, provenance defect, method misuse, confidence overstatement, uncertainty suppression, reproducibility failure, peer-review manipulation, publication suppression, correction suppression, or retraction failure;
e) civil rights violation, discrimination, accessibility failure, exclusionary participation practice, retaliation, harassment, intimidation, grievance mishandling, remedy failure, or protected participation failure;
f) breach of Tribal, Indigenous, local, territorial, cultural, environmental, community-protected, health-sensitive, youth, vulnerable population, or protected knowledge safeguards;
g) public-safe mapping failure, unsafe public disclosure, security-sensitive location disclosure, community harm, doxxing, stigmatization, extractive data use, or public-safe notice failure; and
h) publication, dashboard, map, dataset, software, benchmark, technical baseline, whitepaper, public report, public authority material, GRF-facing input, GRA-facing input, proof receipt, or Nexus interface output that is inaccurate, unsafe, unsupported, overclaimed, stale, disputed, or not correctionable.
The Board may require immediate containment, public-safe review, safeguards review, data protection review, AI review, cyber review, research integrity review, community review, Tribal or Indigenous protocol review, legal review, access restriction, publication freeze, dataset freeze, model freeze, repository freeze, takedown, correction, withdrawal, retraction, notification, independent review, disciplinary action, or structural redesign.
130.10 Corrective Action. The Board may require corrective action where a violation, defect, risk, boundary breach, process failure, record defect, overclaim, safeguards failure, data / AI / cyber incident, research integrity concern, conflict concern, or governance deficiency is identified.
Corrective action may include:
a) instruction, clarification, warning, training, corrective training, supervision, mentoring, recusal expansion, access restriction, committee reassignment, delegation restriction, or authority suspension;
b) correction of minutes, resolutions, registers, policies, public statements, publications, dashboards, maps, datasets, software, technical baselines, proof receipts, public-safe notices, controlled vocabulary entries, metadata, repository entries, gazette entries, or Nexus interface records;
c) ratification where lawful, re-approval, re-vote, re-notice, reclassification as a reserved matter, legal review, tax review, nonprofit review, audit review, counsel review, public-safe review, safeguards review, data / AI / cyber review, finance-boundary review, certification-boundary review, procurement-neutrality review, provider-neutrality review, or sponsor non-control review;
d) hold, stop, quarantine, re-scope, restriction, suspension, withdrawal, retraction, takedown, archive, legal hold, incident response, business continuity measure, disaster recovery measure, or secure disposal;
e) repayment, reimbursement denial, compensation adjustment, contract amendment, contract termination, support refusal, support return, support restriction, sponsor benefit withdrawal, provider participation restriction, public acknowledgment correction, or related-party remedy;
f) resignation request, removal proceeding, committee removal, officer removal, access revocation, credential revocation, repository revocation, controlled-room exclusion, participation suspension, or termination where lawful; and
g) public-safe clarification, controlled notice, affected-person notice, public authority notice, regulator notice, funder notice, insurer notice, law enforcement referral, or other external notice where required or appropriate.
Corrective action shall be proportionate to the seriousness, recurrence, intent, harm, legal exposure, public reliance risk, safeguards impact, institutional impact, and feasibility of remediation. Corrective action shall not be delayed merely because correction is inconvenient, embarrassing, expensive, reputationally difficult, or adverse to a sponsor, provider, public authority relationship, funding relationship, publication timeline, or technical release plan.
130.11 Suspension or Restriction of Access. The Board may suspend or restrict access of a Director, officer, committee member, advisor, fellow, employee, contractor, volunteer, participant, contributor, maintainer, sponsor representative, provider representative, public authority participant, or other person to Board materials, committee materials, repositories, systems, data rooms, controlled rooms, clean rooms, evidence rooms, no-download rooms, public authority rooms, technical assets, records, keys, credentials, public authority materials, finance-sensitive materials, cyber-sensitive materials, protected knowledge, or other Corporation resources where necessary to protect the Corporation.
Suspension or restriction may be imposed where there is credible concern regarding:
a) conflict, recusal breach, unauthorized access, unauthorized disclosure, confidentiality breach, privilege breach, records breach, data misuse, AI misuse, cyber misconduct, credential compromise, repository compromise, or controlled-room breach;
b) public authority overclaim, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider-preference claim, sponsor-control concern, public warning confusion, emergency command confusion, or enterprise execution risk;
c) harassment, retaliation, discrimination, civil rights violation, accessibility violation, protected knowledge breach, safeguards violation, community harm, public-safe mapping concern, grievance interference, or protected participation concern;
d) sanctions, export-control, controlled-technology, national security, competition, procurement integrity, government ethics, grant compliance, research integrity, or professional-boundary concern;
e) resignation, removal, end of term, suspension, investigation, legal hold, termination, offboarding, or change in role; or
f) any other circumstance where continued access creates unacceptable legal, governance, fiduciary, data / AI / cyber, safeguards, public authority, finance, reputation, or mission risk.
Access suspension may be temporary, conditional, partial, emergency, role-specific, system-specific, record-specific, room-specific, or permanent where lawful. Suspension shall be recorded with basis, scope, duration, authority, notice, review date, conditions, appeal or response pathway where available, and closeout treatment.
130.12 Removal Where Permitted. The Board may initiate, recommend, or take removal action where permitted by applicable law, the Articles or Certificate, this Bylaw, member approval requirements where applicable, Board policy, committee charter, agreement, or other competent authority.
Removal may apply to a Director, officer, committee member, committee chair, council member, advisory body member, panelist, working group participant, custodian, representative, or other appointed person. Grounds may include:
a) legal ineligibility, loss of qualification, failure to consent, incapacity, resignation, expiration of term, persistent non-attendance, or inability to perform duties;
b) breach of fiduciary duty, duty of care, duty of loyalty, duty of good faith, duty of obedience to mission where applicable, confidentiality duty, conflict duty, recusal duty, records duty, or training duty;
c) misconduct, fraud, corruption, private inurement, excess benefit, impermissible private benefit, unmanaged related-party transaction, self-dealing, retaliation, harassment, discrimination, civil rights violation, or serious integrity concern;
d) public authority overclaim, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider-preference overclaim, sponsor-control conduct, public warning overclaim, emergency command overclaim, or enterprise execution conduct;
e) data misuse, AI misuse, cyber misconduct, repository compromise, credential misuse, protected knowledge breach, research misconduct, publication misconduct, evidence manipulation, correction suppression, or public-safe publication failure;
f) sanctions, export-control, controlled-technology, competition, procurement integrity, government ethics, grant compliance, lobbying, political activity, professional-boundary, or legal compliance violation; or
g) conduct materially inconsistent with the Corporation’s public-benefit purpose, nonprofit character, non-execution perimeter, Nexus role separation, data / AI / cyber controls, safeguards, validity-by-record, or correctionability.
Removal shall be conducted in a manner consistent with applicable law, fairness, confidentiality, conflict controls, recusal, notice and response where required or appropriate, emergency restrictions where needed, records discipline, and legal review where material. Removal shall not prevent additional corrective action, repayment, access revocation, contract remedy, public-safe correction, regulatory notice, funder notice, insurer notice, or legal referral where required or appropriate.
130.13 Public or Controlled Correction Where Required. Where an Article IV violation results in a public error, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider-preference claim, sponsor-control claim, public warning confusion, emergency command confusion, unsafe publication, incorrect Board record, misleading governance summary, defective public statement, defective dashboard, defective map, defective dataset, defective software release, defective technical baseline, defective proof receipt, defective GRF-facing input, defective GRA-facing input, or defective Nexus interface output, the Board shall require correction in a public or controlled manner appropriate to the risk.
Correction may include:
a) public clarification, erratum, limitation notice, non-reliance notice, public-safe notice, amended governance summary, corrected Board statement, corrected website entry, corrected repository notice, corrected gazette entry, or corrected public material;
b) controlled notice to Directors, officers, committee members, public authority participants, funders, sponsors, providers, hosts, affected communities, affected participants, auditors, insurers, counsel, regulators, public authorities, GRF, GRA, Nexus entities, or other affected persons;
c) withdrawal, supersession, retraction, takedown, quarantine, archive, version correction, metadata correction, controlled vocabulary correction, proof receipt correction, dashboard correction, map correction, dataset correction, software correction, technical baseline correction, or repository correction;
d) corrected limitation language for no public authority action, no public warning, no emergency command, no finance-readiness, no investment advice, no securities solicitation, no insurance approval, no rating, no procurement approval, no certification, no recognition, no provider preference, no sponsor control, no professional advice, and no operational instruction; and
e) correction of records sufficient to preserve validity-by-record and prevent later reliance on superseded or defective materials.
Correction shall be timely, accurate, proportionate, traceable, public-safe, legally reviewed where needed, and preserved in the correction register. No person shall suppress correction to avoid embarrassment, preserve funding, protect a sponsor, protect a provider, protect a public authority relationship, protect a publication, protect a technical release, protect a Board member, or avoid reputational cost.
130.14 Legal, Regulatory, Funder, Public Authority, or Law Enforcement Referral Where Required or Appropriate. The Board may refer a matter to counsel, auditors, insurers, regulators, public authorities, funders, grantors, law enforcement, courts, professional bodies, ethics bodies, public authority oversight bodies, data protection authorities, cybersecurity authorities, sanctions authorities, export-control authorities, competition authorities, charitable solicitation authorities, tax authorities, or other competent bodies where referral is required by law, contract, grant, insurance, fiduciary duty, public authority obligation, safeguarding duty, or Board determination.
Referral may be required or appropriate where the matter involves:
a) fraud, theft, embezzlement, bribery, corruption, misuse of restricted funds, private inurement, excess benefit, impermissible private benefit, false filing, false statement, or financial misconduct;
b) data breach, privacy breach, cyber incident, credential compromise, controlled-technology exposure, sanctions issue, export-control issue, national security sensitivity, or material cybersecurity risk;
c) harassment, retaliation, discrimination, civil rights violation, protected knowledge breach, community harm, vulnerable participant harm, youth harm, protected participation interference, or safeguarding failure;
d) research misconduct, evidence fabrication, falsification, plagiarism, public-safe publication misconduct, grant misconduct, public authority misrepresentation, or suppression of correction;
e) securities, investment adviser, broker-dealer, finder, banking, lending, insurance, underwriting, rating, public finance, procurement, certification, professional-boundary, lobbying, political activity, government ethics, gifts, grant compliance, or competition concern;
f) public warning overclaim, emergency command overclaim, public authority impersonation, public authority delegation overclaim, procurement approval overclaim, certification overclaim, recognition overclaim, finance-readiness overclaim, or official adoption overclaim; or
g) any matter where external legal authority, public authority, funder, insurer, regulator, or law enforcement must be notified or may need to act.
Referral shall be coordinated through counsel or an authorized compliance function where appropriate. Referral shall preserve privilege where lawful, protect confidentiality, protect affected persons, protect whistleblowers, protect protected knowledge, protect cyber-sensitive information, avoid public reliance errors, and maintain accurate records. A referral shall not be characterized as a finding unless a competent authority has made a finding.
130.15 Enforcement Records. The Corporation shall maintain Article IV Enforcement Records sufficient to demonstrate that Board enforcement matters have been identified, reviewed, escalated, decided, corrected, restricted, referred, closed, and archived in accordance with law, the Articles or Certificate, this Bylaw, fiduciary duties, confidentiality, privilege, public-safe publication, safeguards, data / AI / cyber controls, validity-by-record, and correctionability.
Article IV Enforcement Records shall include, as applicable:
a) intake records, complaint records, self-report records, whistleblower records, grievance records, incident records, challenge records, audit findings, counsel referrals, committee referrals, officer referrals, public authority referrals, funder referrals, sponsor referrals, provider referrals, participant referrals, and external notices;
b) alleged violation description, affected Article IV provision, affected duty, affected person, affected record, affected system, affected publication, affected repository, affected committee, affected public authority interface, affected finance-boundary matter, affected certification-boundary matter, affected procurement-boundary matter, affected safeguards matter, affected data / AI / cyber matter, and affected Nexus interface;
c) conflict checks, recusal records, independence review, investigator or reviewer appointment, counsel review, privilege treatment, confidentiality classification, access controls, legal hold, evidence preservation, record preservation, and interim measures;
d) factual findings, evidence considered, witness information, documentary support, technical logs, repository logs, AI logs, data access logs, meeting records, public materials, controlled-room records, metadata, audit trail, and chain-of-custody records;
e) Board review, committee review, officer review, counsel review, compliance review, tax review, nonprofit review, data / AI / cyber review, public authority review, finance-boundary review, certification-boundary review, procurement-neutrality review, provider-neutrality review, sponsor non-control review, safeguards review, and public-safe publication review;
f) determination records, no-action records, warning records, training records, corrective action records, access restriction records, delegation suspension records, recusal expansion records, compensation or reimbursement hold records, repayment records, ratification records, voiding or non-operative treatment records, withdrawal records, retraction records, takedown records, archive records, legal referral records, regulatory referral records, funder notice records, public authority notice records, insurer notice records, and law enforcement referral records;
g) public or controlled correction records, limitation notice records, non-reliance notice records, public-safe clarification records, affected-person notice records, public authority notice records, GRF-facing correction records, GRA-facing correction records, Nexus interface correction records, and repository correction records;
h) disciplinary records, removal records, resignation records, settlement records, contract remedy records, support refusal or return records, provider restriction records, sponsor restriction records, donor restriction records, host restriction records, participation termination records, and access closeout records;
i) appeal, reconsideration, response, minority view, dissent where permitted, Board ratification, review, closure, monitoring, recurrence-prevention, training, policy amendment, procedure amendment, register amendment, controlled vocabulary amendment, and recurrence audit records; and
j) responsible owner, custodian, authority, version, effective date, review date, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, and metadata.
The governing rule of this Section is that Article IV enforcement is a fiduciary system for protecting the Corporation’s Board from drift, capture, informality, authority inflation, record failure, and public reliance error. The Board shall enforce its own governance standards with the same seriousness with which it oversees evidence, methods, observability, public-good software, data, AI, cyber, public authority learning, safeguards, and Nexus interfaces. Enforcement shall be lawful, fair, independent, recorded, public-safe, proportionate, protective of correction, and never converted into concealment, retaliation, sponsor accommodation, provider accommodation, public authority substitution, finance execution, certification, procurement approval, recognition, or enterprise execution.
Last updated
Was this helpful?