ARTICLE V. OFFICERS
Section 131. Officer Architecture and Executive Leadership System
131.1 Officer Architecture Purpose. The Corporation shall maintain an officer architecture and executive leadership system sufficient to implement Board-approved strategy, administer lawful operations, preserve corporate records, manage public-benefit programs, steward 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, public-safe publication, and Nexus interfaces, and protect the Corporation’s United States nonprofit, public-benefit, non-executing, tax-exempt-compatible, all-states-and-territories, and North America anchor character.
The officer architecture shall be designed to ensure that executive authority is:
a) derived from law, the Articles or Certificate, this Bylaw, Board resolutions, Board-approved policies, Board-approved budgets, and recorded delegations;
b) exercised for public-benefit purposes and not for private inurement, impermissible private benefit, sponsor control, provider preference, public authority substitution, finance execution, certification, procurement approval, recognition, public warning, emergency command, or enterprise execution;
c) bounded by role, office, delegation, authority matrix, expenditure authority, contract authority, publication authority, data access authority, AI-use authority, controlled-room authority, public authority interface authority, and records obligations;
d) subject to Board oversight, legal compliance, tax-exempt or tax-exempt-compatible discipline, nonprofit controls, conflict controls, related-party controls, data / AI / cyber controls, community safeguards, public-safe publication controls, validity-by-record, and correctionability; and
e) structured to preserve clear separation among Board governance, officer execution of approved internal administration, committee recommendations, advisory participation, technical contribution, public authority learning, sponsor support, provider participation, GRF recognition functions, GRA finance-readiness functions, Nexus Standards functions, and enterprise-stack execution.
The officer architecture shall be read as an internal governance system. It shall not create apparent authority, public authority delegation, finance-readiness authority, certification authority, procurement authority, recognition authority, provider approval authority, sponsor entitlement, professional advice authority, or operational control over third-party systems.
131.2 Officers as Delegated Institutional Actors. Officers are delegated institutional actors of the Corporation. They are not sovereign organs, independent fiduciary bodies, public authorities, regulators, standards monopolies, certification bodies, procurement bodies, finance-readiness authorities, fund managers, brokers, dealers, investment advisers, lenders, insurers, rating agencies, emergency command bodies, national companies, Project SPVs, qualified enterprise providers, infrastructure operators, or enterprise execution vehicles.
Each officer shall serve within the office, title, scope, term, delegation, reporting line, authority matrix, budget, policy framework, and records obligations approved by the Board or other competent authority. Officer authority shall be personal to the office and role recorded, not to public prominence, technical expertise, founder status, donor relationship, sponsor relationship, provider relationship, public authority contact, repository access, AI-system access, controlled-room access, Nexus familiarity, or prior practice.
An officer may coordinate, administer, recommend, escalate, implement, and manage matters within delegated scope. An officer shall not convert delegated operational authority into Board authority, member authority where applicable, public authority authority, GRF authority, GRA authority, Nexus Standards authority, enterprise-stack authority, or external reliance authority.
Officer action shall be valid only where supported by a competent record. Where an officer acts without authority, exceeds delegation, or creates ambiguity as to authority, the act shall be subject to hold, review, ratification where lawful, correction, restriction, withdrawal, retraction, takedown, referral, or treatment as void, voidable, suspended, or non-operative to the fullest extent lawful.
131.3 Officers Subject to Board Authority. All officers shall be subject to the Board’s ultimate governance authority, reserved powers, fiduciary oversight, policy direction, budget approval, compliance oversight, risk oversight, records oversight, and enforcement authority. The Board may appoint, remove, suspend, limit, delegate to, revoke delegation from, require reports from, require training of, review, evaluate, investigate, discipline, or replace officers as permitted by law, the Articles or Certificate, this Bylaw, Board-approved policies, and applicable agreements.
Officers shall implement Board-approved strategy and policy; they shall not independently determine the Corporation’s mission, amend this Bylaw, alter the Articles or Certificate, change legal identity, change tax posture, change nonprofit character, change public-benefit purpose, change non-execution boundary, change North America anchor status, create a new regulated function, bind a Board reserved matter, waive safeguards, or alter Nexus role separation unless competent Board approval and all required legal approvals have been obtained.
Board authority over officers includes authority to require:
a) regular and special reports;
b) financial, operational, programmatic, technical, legal, tax, compliance, data / AI / cyber, safeguards, risk, incident, and correction reporting;
c) access to books, registers, records, repositories, dashboards, systems, rooms, policies, protocols, contracts, grants, support arrangements, and officer decisions;
d) escalation of material risks, conflicts, incidents, overclaims, boundary concerns, legal ambiguities, public authority issues, finance-boundary issues, certification-boundary issues, procurement-neutrality issues, provider-neutrality issues, sponsor non-control issues, and safeguards concerns;
e) correction, supersession, withdrawal, retraction, takedown, quarantine, legal hold, access restriction, delegation suspension, or public-safe clarification where needed; and
f) officer cooperation with counsel, auditors, insurers, committees, investigations, public authority notices where required, funder notices where required, and lawful external review.
No officer shall resist Board oversight on the basis of technical centrality, operational urgency, confidentiality controlled by the officer, sponsor relationship, provider relationship, public authority relationship, funding deadline, publication deadline, repository deadline, or personal control over systems or records.
131.4 Officers Subject to Law, Articles, Bylaw, Board Resolutions, Policies, Delegation Matrix, Budget, and Records Requirements. Each officer shall act subject to applicable United States federal law, governing state nonprofit corporation law, territorial, District of Columbia, Tribal-interface, local, cross-border, and foreign laws where applicable, the Articles or Certificate, this Bylaw, Board resolutions, Board-approved policies, committee charters where relevant, officer delegations, authority matrices, Board-approved budgets, approved contracts, records policies, data / AI / cyber policies, public authority boundary policies, finance-boundary policies, safeguards policies, public-safe publication policies, and any applicable legal, tax, grant, insurance, or funder obligations.
An officer shall not use a lower-order instrument to override a higher-order instrument. No operating procedure, management instruction, dashboard workflow, repository rule, technical profile, AI output, proof receipt, ledger entry, form, checklist, template, public statement, grant document, sponsor acknowledgment, provider agreement, public authority MoU, controlled-room rule, or operational custom may authorize an officer to act contrary to law, the Articles or Certificate, this Bylaw, Board reserved matters, Board-approved policy, or mandatory safeguards.
Each officer shall maintain records sufficient to demonstrate:
a) authority for the action taken;
b) compliance with the approved budget, delegation, and authority matrix;
c) conflict disclosure and recusal compliance;
d) legal, tax, nonprofit, public authority, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, sponsor non-control, competition, sanctions, export-control, controlled-technology, data / AI / cyber, privacy, research integrity, safeguards, and public-safe publication review where required;
e) identity of approver, custodian, responsible owner, version, effective date, review date, repository location, access class, publication class, retention class, and archive status; and
f) correction, supersession, withdrawal, retraction, takedown, legal hold, or incident response pathway where relevant.
Where an officer is uncertain whether authority exists, whether a matter is reserved, whether a boundary is implicated, or whether legal ambiguity exists, the officer shall escalate before acting unless emergency controls permit temporary protective action.
131.5 Executive Leadership System. The Corporation may maintain an executive leadership system composed of officers, senior management, secretariat leads, technical leads, public authority learning leads, safeguards leads, data / AI / cyber leads, research leads, program leads, and other persons approved by the Board or authorized within delegation. The executive leadership system shall support integrated implementation of Board-approved mission while preserving legal separateness, role clarity, anti-capture controls, records discipline, and non-execution.
The executive leadership system may coordinate:
a) strategy implementation, annual planning, program execution, budget administration, risk escalation, and Board reporting;
b) evidence, methods, observability, ontology, technical truth, research, publication, public-good software, technical baseline, repository, secure release, and correction functions;
c) data governance, privacy, AI governance, cybersecurity, secure compute, model registers, inference records, compute workload records, access controls, incident response, business continuity, and disaster recovery;
d) public authority learning, public authority capacity classification, regulator-listening participation, public finance reader participation, emergency-management participant participation, public infrastructure operator participation, public-safe reporting, controlled rooms, clean rooms, evidence rooms, data rooms, public authority rooms, and no-download rooms;
e) 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, and non-retaliation;
f) grants, donations, sponsorships, subscriptions, fees, cost recovery, in-kind support, donor acknowledgments, sponsor acknowledgments, anti-capture controls, restricted funds, and public-good support administration; and
g) 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, providers, sponsors, hosts, universities, laboratories, communities, and public authorities.
The executive leadership system shall not function as a shadow board. It shall not approve Board reserved matters, alter legal identity, change mission, create public authority meaning, create finance-readiness meaning, create certification meaning, create procurement meaning, create recognition meaning, select providers for public authorities, control enterprise execution, or bind the Corporation beyond recorded authority.
131.6 Statutory Officers Where Required by Governing Law. The Corporation shall maintain such statutory officers as are required by governing state nonprofit corporation law, the Articles or Certificate, this Bylaw, or Board resolution. Statutory officers may include, where applicable, a President, Secretary, Treasurer, Chair, Vice-Chair, or such other offices as law or the Board may require or permit.
Each statutory officer shall be appointed, elected, confirmed, or recorded in accordance with applicable law and governing instruments. The Corporation shall preserve records showing the statutory basis, appointment authority, term, consent, eligibility, duties, delegation, resignation, removal, vacancy, acting status, and succession of each statutory officer.
Statutory officer status shall not expand authority beyond the office, law, Bylaw, Board resolution, delegation, budget, and authority matrix. A statutory officer shall not exercise a prohibited function merely because the office is required by law or recognized in corporate records.
Where a statutory office is vacant, impaired, contested, or unclear, the Board shall take lawful steps to appoint, designate, clarify, ratify, or replace the officer and preserve continuity of corporate filings, minute books, registers, bank authority, tax filings, notices, repository controls, legal holds, and Board support.
131.7 Non-Statutory Executive Officers Where Approved. The Board may create non-statutory executive officer positions to support the Corporation’s public-benefit technical mission, provided that each position is lawful, purpose-aligned, funded or supportable, appropriately bounded, recorded, and subject to Board oversight.
Non-statutory executive officer positions may include, without limitation, 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, Chief Operating Officer, Chief Development, Grants, and Public-Good Support Officer, or other offices approved by the Board.
A Board resolution creating a non-statutory executive office shall identify:
a) title and short title;
b) purpose and scope;
c) reporting line;
d) appointing authority;
e) authority limits;
f) budget and spending limits where applicable;
g) contracting and signature limits where applicable;
h) publication, public statement, repository, data access, AI-use, controlled-room, and public authority interface limits where applicable;
i) conflict, independence, confidentiality, safeguards, and records obligations;
j) prohibited functions and boundary limitations;
k) review cycle, sunset, amendment, or dissolution provisions; and
l) register entry, repository location, and effective date.
No non-statutory title shall be used to imply legal authority not granted. Titles such as “Chief,” “Director,” “Lead,” “Head,” “Principal,” “Architect,” “Steward,” “Custodian,” or “Officer” shall be controlled by the Corporation’s official records and public-safe naming protocols.
131.8 Management Roles Distinguished From Officers. Management roles may be created to administer programs, functions, teams, repositories, rooms, data assets, technical assets, publications, grants, support relationships, communications, operations, or other activities. A management role shall not be treated as an officer role unless the Board or competent authority expressly designates it as an officer role and records the designation.
Managers may supervise people, processes, budgets, deliverables, or systems within delegated scope. They shall not acquire corporate authority merely by managing a function, leading a team, holding a title, controlling a repository, controlling a dashboard, coordinating a public authority room, drafting a report, administering a grant, coordinating a sponsor, managing a provider interface, or operating a technical system.
A management role shall be subject to:
a) written role description or delegation;
b) reporting line;
c) authority matrix;
d) budget controls;
e) contracting and procurement limits;
f) data / AI / cyber access controls;
g) public authority interface controls;
h) finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, sponsor non-control, and recognition-boundary controls;
i) confidentiality, conflict, safeguards, and public-safe publication controls; and
j) records, review, suspension, revocation, and offboarding requirements.
Where a management role uses a title that could be confused with officer authority, the Corporation shall clarify the role in records and public-safe materials. No management convenience shall create apparent authority.
131.9 Secretariat Roles Distinguished From Officers. Secretariat roles support Board administration, officer administration, committee administration, records management, meeting logistics, notices, agenda coordination, document control, register updates, repository maintenance, gazette or notice-stream administration, case identifiers, forms-first intake, routing, minute preparation, action-item tracking, and governance support.
Secretariat personnel may be employees, contractors, volunteers, fellows, officers, or other authorized persons, but secretariat status alone does not create officer authority, Board authority, committee authority, fiduciary authority, public authority authority, publication authority, finance authority, certification authority, procurement authority, recognition authority, provider approval authority, sponsor negotiation authority, or external representation authority.
Secretariat roles shall be designed to protect:
a) accuracy of records;
b) completeness of notices and agendas;
c) version control;
d) repository discipline;
e) confidentiality and privilege;
f) access control;
g) legal hold and retention;
h) public-safe notice discipline;
i) controlled vocabulary use;
j) traceability of decisions, delegations, approvals, corrections, and supersessions; and
k) separation between administrative support and substantive authority.
A secretariat record, routing note, intake label, meeting summary, AI summary, transcript, action-item list, draft minutes, or repository entry shall not become operative authority unless adopted, approved, certified, or otherwise made operative by competent record.
131.10 Technical Leadership Roles Distinguished From Corporate Authority. Technical leadership roles may be created to support public-good software, open technical baselines, repositories, schemas, APIs, SDKs, dashboards, data tools, reference architectures, test harnesses, gold vectors, negative tests, benchmark libraries, observability methods, Nexus Truth Engine methods, verifiable compute methods, secure release, SBOM, model registers, inference records, compute workload records, cyber controls, AI-RAN, O-RAN, DePIN, DLT, digital twins, sensors, geospatial systems, Earth observation, and other technical assets.
Technical leadership shall not be treated as corporate authority unless expressly delegated and recorded. A technical lead, maintainer, architect, data steward, model steward, repository administrator, release manager, cybersecurity lead, AI lead, dashboard lead, observability lead, or protocol contributor shall not acquire authority to bind the Corporation merely by technical expertise, authorship, merge rights, administrator access, public recognition, commit history, system control, publication authorship, standards familiarity, public authority interaction, or technical indispensability.
Technical leaders shall not:
a) amend this Bylaw, Board policy, controlled vocabulary, public-safe notice library, public authority capacity classification, finance-boundary classification, certification-boundary classification, procurement-neutrality classification, provider-neutrality classification, sponsor non-control classification, or Nexus role-separation rule through technical design;
b) represent a technical baseline, repository, model, dataset, benchmark, dashboard, proof receipt, ledger entry, AI output, observability signal, DePIN signal, AI-RAN signal, O-RAN signal, sensor signal, or digital twin output as certification, procurement approval, recognition, finance-readiness, public authority action, public warning, emergency command, or operational authorization;
c) release technical assets without required legal, IP, licensing, data, AI, cyber, privacy, export-control, sanctions, controlled-technology, competition, safeguards, public-safe publication, and authority review; or
d) create provider preference, sponsor entitlement, enterprise-stack advantage, public authority reliance, or regulated execution through technical integration.
Technical leadership shall be records-supported, reviewable, secure, correctionable, and subordinate to law, the Articles or Certificate, this Bylaw, Board authority, officer delegation, and public-safe controls.
131.11 Public Authority Interface Roles Distinguished From Public Authority Power. The Corporation may designate officers, staff, advisors, facilitators, or other authorized persons to support public authority learning, regulator-listening participation, public finance reader participation, emergency-management participant participation, public infrastructure operator participation, official-capacity classification, observer classification, public authority data contribution intake, public authority reference review, controlled-room operation, public authority room operation, simulation, tabletop, scenario, after-action learning, and public-safe reporting.
A public authority interface role is not public authority power. No officer, employee, advisor, facilitator, room lead, public authority liaison, public finance reader coordinator, regulator-listening coordinator, emergency-management learning coordinator, or public infrastructure operator interface lead shall represent that the Corporation has authority to make, approve, issue, direct, adopt, enforce, certify, procure, fund, command, warn, regulate, or substitute for any public authority decision.
Public authority interface roles shall be subject to:
a) capacity classification;
b) approved public authority participation terms;
c) official-capacity, observer, regulator-listening, public finance reader, emergency-management participant, or public infrastructure operator status records where relevant;
d) public authority data contribution controls;
e) public authority reference review;
f) confidentiality, public records, open meetings, public procurement, government ethics, gifts, lobbying, grant, FOIA, state sunshine, privacy, cyber, security, and public authority legal review where applicable;
g) non-reliance and limitation language;
h) prohibition on public warning, emergency command, regulatory approval, public finance approval, procurement approval, certification, recognition, or sovereign obligation claims; and
i) public-safe correction and takedown pathways.
Public authority interface personnel shall escalate any ambiguity suggesting public authority delegation, official adoption, public warning, emergency command, procurement approval, funding approval, regulatory approval, public finance approval, sovereign obligation, public-private partnership, or public authority reliance.
131.12 Nexus Interface Roles Distinguished From Nexus System Control. The Corporation may designate officers, leads, custodians, representatives, or technical contributors to support 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, Global Nexus Consortium, Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, National Consortium Companies, Project SPVs, providers, sponsors, hosts, universities, laboratories, communities, and public authorities.
A Nexus interface role shall not be treated as control of Nexus as a whole. Nexus coordination does not create merger, partnership, agency, shared treasury, shared liability, common employer, joint employer, public authority delegation, finance-readiness authority, recognition authority, standards authority, protocol authority, procurement authority, certification authority, provider approval authority, sponsor entitlement, enterprise execution authority, or operational control unless a separate lawful instrument expressly creates and records such relationship.
Nexus interface personnel shall preserve:
a) GCRI US as evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, and open technical baseline steward;
b) 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;
c) 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;
d) Nexus Standards and protocol authority functions only where separately and lawfully constituted;
e) consortium, national company, Project SPV, provider, sponsor, host, and enterprise-stack separateness; and
f) public-good stack and enterprise stack separation.
Nexus interface roles shall be documented through compatibility notes, divergence logs, interface records, authority matrices, controlled vocabulary, public-safe notices, and correction pathways. No officer shall use Nexus terminology to inflate GCRI US authority or collapse roles across the Nexus ecosystem.
131.13 Officer Authority by Appointment and Delegation Only. Officer authority shall arise only from lawful appointment, election, confirmation, Board resolution, written delegation, authority matrix, policy, contract, or other competent record. No person shall be treated as an officer, acting officer, authorized representative, signatory, spokesperson, custodian, public authority interface lead, finance-boundary lead, technical release authority, controlled-room admission authority, or Nexus interface representative unless the person’s role and authority are recorded.
Officer authority shall not arise by implication from:
a) founder status;
b) seniority;
c) public title;
d) social prominence;
e) authorship;
f) technical centrality;
g) repository administration;
h) data access;
i) AI-system access;
j) controlled-room access;
k) committee participation;
l) council participation;
m) advisory status;
n) fellowship status;
o) donor, sponsor, provider, host, university, laboratory, public authority, or community relationship;
p) prior course of dealing;
q) public presentation;
r) media appearance;
s) fundraising activity;
t) grant drafting;
u) Nexus interface participation; or
v) operational necessity.
Any person purporting to act as an officer without appointment or delegation shall be subject to correction, access restriction, public clarification, contract action, removal, suspension, legal response, or other lawful remedy. Any third-party reliance created by unauthorized officer representation shall be limited to the fullest extent lawful and corrected through public-safe or controlled notice where needed.
131.14 No Officer Authority by Title Alone Outside Recorded Scope. Officer titles shall be interpreted narrowly and by record. A title shall not expand authority beyond the office description, Board resolution, delegation matrix, authority matrix, policy, budget, contract, and applicable law.
No officer title, including “President,” “Executive Director,” “Chief Executive Officer,” “Secretary,” “Treasurer,” “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,” “Chief Operating Officer,” “Chief Development, Grants, and Public-Good Support Officer,” “Director,” “Head,” “Lead,” “Steward,” “Custodian,” or similar title, shall be used to imply that the officer may:
a) approve Board reserved matters;
b) amend governing documents;
c) bind the Corporation outside delegation;
d) create debt, guarantees, restricted fund obligations, major contracts, intellectual property transfers, repository transfers, or technical asset dispositions outside approval;
e) issue public authority decisions, public warnings, emergency commands, regulatory approvals, public finance approvals, procurement approvals, certifications, recognitions, ratings, finance-readiness determinations, insurance-readiness determinations, provider approvals, sponsor entitlements, or operational authorizations;
f) waive data / AI / cyber controls, safeguards, protected knowledge controls, public-safe publication controls, controlled-room rules, or records obligations;
g) represent GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, consortiums, national companies, Project SPVs, providers, sponsors, hosts, public authorities, funders, universities, laboratories, or communities without express written authority; or
h) act as an enterprise-stack executor.
Where title meaning is unclear, the narrower and more protective interpretation shall apply pending Board or counsel review. Public materials using officer titles shall include limitation language where necessary to prevent apparent authority, public reliance, or role confusion.
131.15 Officer Architecture Records. The Corporation shall maintain Officer Architecture Records sufficient to demonstrate the lawful creation, appointment, delegation, limitation, supervision, review, correction, suspension, removal, succession, and closure of officer and executive leadership roles.
Officer Architecture Records shall include, as applicable:
a) officer register, statutory officer records, non-statutory officer records, executive leadership records, management role records, secretariat role records, technical leadership records, public authority interface role records, Nexus interface role records, acting officer records, interim officer records, and succession records;
b) Board resolutions creating offices, appointing officers, approving role descriptions, approving delegations, approving authority matrices, approving reporting lines, approving compensation, approving budget authority, approving signatory authority, and approving public representation authority;
c) eligibility records, consent records, fit-and-proper records, integrity records, independence records, conflict records, sanctions records, export-control records, controlled-technology records, public authority boundary records, finance-boundary records, certification-boundary records, procurement-neutrality records, provider-neutrality records, sponsor non-control records, data / AI / cyber records, privacy records, research integrity records, civil rights records, accessibility records, safeguards records, protected knowledge records, and public-safe publication records;
d) delegation records, authority matrix records, spending authority records, banking authority records, contracting authority records, signature authority records, grant authority records, donation authority records, sponsorship authority records, publication authority records, public statement authority records, public authority reference authority records, data access authority records, AI-use authority records, model approval authority records, repository authority records, software release authority records, controlled-room authority records, incident response authority records, correction authority records, and emergency authority records;
e) reporting records, Board report records, committee report records, risk escalation records, incident escalation records, correction escalation records, legal escalation records, public authority escalation records, finance-boundary escalation records, safeguards escalation records, data / AI / cyber escalation records, and Nexus interface records;
f) title-use records, public description records, officer biography records, website records, grant records, sponsorship records, donor records, provider records, public authority records, media records, repository records, publication records, and correction records relating to officer authority;
g) resignation records, removal records, suspension records, access restriction records, delegation revocation records, acting officer appointment records, vacancy records, handover records, credential revocation records, records return records, records deletion or sealing records, confidentiality survival records, conflict survival records, legal hold records, and post-service restriction records; and
h) 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 officer architecture exists to make the Corporation operationally capable without making it authority-inflating, execution-facing, sponsor-controlled, provider-preferential, public-authority-confusing, finance-executing, certification-granting, procurement-directing, recognition-issuing, or enterprise-operating. Officers shall therefore be lawful, appointed, delegated, bounded, trained, supervised, recorded, reviewable, removable, and correctionable.
Section 132. Officers of GCRI US
132.1 Required Officers. The Corporation shall have such officers as are required by applicable United States federal law, governing state nonprofit corporation law, the Articles or Certificate, this Bylaw, Board resolution, or other competent governing record. Required officers shall be maintained to ensure lawful corporate existence, fiduciary administration, governance continuity, financial stewardship, record custody, notice discipline, tax and nonprofit compliance, public-benefit accountability, and implementation of Board-approved purposes.
Required officers may include, as applicable, a Chair of the Board, Vice-Chair of the Board, President, Secretary, Treasurer, Chief Financial Officer, Executive Director, Chief Executive Officer, or such other statutory or functional officers as the Board determines to be necessary or appropriate. The Board may assign duties among officers in a manner consistent with law, the Articles or Certificate, this Bylaw, nonprofit character, public-benefit purpose, tax-exempt or tax-exempt-compatible discipline, segregation of duties, internal controls, non-execution, role separation, data / AI / cyber controls, safeguards, validity-by-record, and correctionability.
No office shall be treated as required merely because a title appears in a proposal, website, slide, public statement, draft charter, grant material, sponsor material, provider material, public authority communication, repository entry, AI summary, staffing plan, or Nexus interface document unless the office is required by law or has been created by competent Board or governing record.
132.2 Chair of the Board. The Corporation may have a Chair of the Board, who shall serve as the principal Board leadership officer unless another lawful governance structure is adopted by the Board. The Chair shall support the Board’s exercise of fiduciary governance, reserved powers, mission-lock protection, Board meeting discipline, director engagement, Board continuity, Board evaluation, officer interface discipline, committee coordination, and escalation of governance-significant matters.
The Chair may, within recorded authority:
a) preside at meetings of the Board;
b) support agenda-setting with the Secretary, President, Executive Director, Chief Executive Officer, committee chairs, and other authorized officers;
c) ensure that Board materials identify material legal, fiduciary, public-benefit, nonprofit, tax, public authority, finance, certification, procurement, provider-neutrality, sponsor non-control, data / AI / cyber, safeguards, research integrity, public-safe publication, and Nexus interface considerations;
d) call or support the calling of special or emergency meetings where permitted;
e) support Board review of officer performance, succession, committee structure, and governance maturity;
f) ensure that Directors receive sufficient information to exercise informed judgment; and
g) support correction, ratification, suspension, hold, quarantine, legal review, or escalation where Board action or governance protection is required.
The Chair shall not have unilateral authority to amend this Bylaw, approve reserved matters, bind the Corporation outside delegation, override Board decisions, suppress Director access to material governance information, waive conflicts, approve prohibited functions, create public authority meaning, create finance-readiness meaning, certify, procure, recognize, select providers, confer sponsor control, or direct enterprise execution unless a separate lawful record expressly grants authority within permitted limits.
132.3 Vice-Chair of the Board. The Corporation may have one or more Vice-Chairs of the Board, appointed or elected as provided by law, the Articles or Certificate, this Bylaw, or Board resolution. A Vice-Chair shall support the Chair, assist with Board continuity, perform duties assigned by the Board or Chair within lawful authority, and act in the place of the Chair when the Chair is absent, unavailable, conflicted, recused, incapacitated, or otherwise unable to act, to the extent authorized by governing record.
A Vice-Chair may support:
a) Board meeting preparation and governance follow-up;
b) committee and council coordination;
c) Director onboarding, training, succession, and evaluation;
d) conflict and recusal discipline;
e) emergency Board convening and continuity;
f) interface with officers, counsel, auditors, committees, public-safe publication controls, and safeguards functions; and
g) preservation of the Board’s non-execution, public authority boundary, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, sponsor non-control, and Nexus role-separation duties.
A Vice-Chair shall not have independent executive authority by title alone. Acting as Chair shall not expand the Vice-Chair’s authority beyond the Chair’s lawful authority, the Board’s delegation, applicable law, the Articles or Certificate, this Bylaw, and recorded limits.
132.4 President. The Corporation may have a President who serves as a principal institutional officer responsible for implementing Board-approved strategy, supporting public-benefit mission execution within the Corporation’s non-execution perimeter, coordinating senior officers and executive leadership where delegated, representing the Corporation where authorized, and reporting to the Board.
The President may be authorized to:
a) support the Corporation’s United States nonprofit, all-states-and-territories, and North America anchor posture;
b) coordinate evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, public authority learning, and safeguards programs within Board-approved scope;
c) supervise or coordinate officers, employees, contractors, fellows, advisors, volunteers, contributors, and program leads where delegated;
d) support relationships with GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, Nexus Network, consortiums, public authorities, universities, laboratories, communities, sponsors, donors, funders, hosts, and providers within recorded authority;
e) support fundraising, grant development, donation acceptance, sponsorship administration, fee programs, subscriptions, and public-good support within anti-capture controls;
f) ensure escalation of material risks, incidents, boundary concerns, and corrections; and
g) provide regular reports to the Board and relevant committees.
The President shall not approve Board reserved matters, exercise public authority, issue public warnings, direct emergency command, determine finance-readiness, provide investment advice, solicit securities, certify, accredit, approve procurement, recognize maturity or standing, approve providers, sell sponsor influence, or execute enterprise-stack functions. Presidential authority shall be bounded by Board-approved strategy, budget, delegation, authority matrix, conflict controls, records requirements, and this Bylaw.
132.5 Executive Director or Chief Executive Officer Where Approved. The Corporation may have an Executive Director or Chief Executive Officer where the Board determines that such office is necessary or appropriate for operational management. The office may be created as a principal management office, principal executive office, or combined operational leadership office, subject to law, the Articles or Certificate, this Bylaw, Board resolution, employment or services agreement, authority matrix, budget, and records requirements.
The Executive Director or Chief Executive Officer may be responsible for:
a) day-to-day administration of Board-approved operations;
b) implementation of Board-approved plans, budgets, policies, programs, and controls;
c) supervision of staff, contractors, fellows, advisors, volunteers, contributors, and operational teams where delegated;
d) execution of contracts, expenditures, filings, hiring, procurement, publications, repository actions, access decisions, and operational decisions only within delegated authority;
e) maintenance of internal controls, risk escalation, compliance implementation, incident response, and correction processes;
f) support for data / AI / cyber, privacy, research integrity, safeguards, public-safe publication, and public authority learning controls; and
g) regular reporting to the Board, Chair, President, committees, or other competent authority as required.
The Executive Director or Chief Executive Officer shall not become a substitute Board. No operational convenience, urgency, technical dependency, funding pressure, sponsor request, provider request, public authority request, publication deadline, repository deadline, or event deadline shall justify action outside recorded authority or contrary to the Bylaw.
132.6 Secretary. The Corporation shall have a Secretary where required by law or Board determination. The Secretary shall serve as the principal corporate records officer unless another custodian is lawfully designated for specific records. The Secretary shall support validity-by-record, notice discipline, minute discipline, repository discipline, Board resolution discipline, register discipline, version control, certification of records, legal hold coordination, retention, archival, and governance authenticity.
The Secretary’s duties may include:
a) preparing or supervising notices, agendas, minutes, resolutions, written consents, certifications, and meeting records;
b) maintaining the minute book, Board Register, Director Register, Officer Register, Board Resolution Register, Bylaw Register, member register where applicable, committee register, delegation register, policy register, and other governance registers;
c) ensuring that adopted instruments are versioned, deposited, indexed, dated, marked for status, assigned custodians, and linked to approval records;
d) supporting repository, gazette, and notice-stream administration;
e) maintaining records of notice, waiver, quorum, voting, abstention, recusal, dissent where permitted, action items, responsible owners, follow-up, correction, supersession, withdrawal, retraction, and archive;
f) coordinating records access, sealing, retention, legal hold, and secure disposal consistent with law and policy; and
g) certifying records when authorized.
The Secretary’s custody of records shall not create authority to alter substantive decisions, approve matters, validate unauthorized acts, create public authority meaning, create finance-readiness meaning, certify, procure, recognize, or bind the Corporation beyond recorded authority. The Secretary shall escalate any apparent record defect, authority defect, notice defect, quorum defect, voting defect, conflict defect, or version-control defect.
132.7 Treasurer or Chief Financial Officer. The Corporation shall have a Treasurer or Chief Financial Officer where required by law, Board resolution, internal control design, or financial administration needs. The Treasurer or Chief Financial Officer shall support lawful financial stewardship, budget discipline, internal controls, accounting, treasury oversight, restricted fund tracking, financial reporting, tax compliance, audit or review readiness, fraud prevention, private-benefit control, and public-benefit use of assets.
The Treasurer or Chief Financial Officer may be responsible for:
a) supporting preparation, monitoring, and reporting of annual budgets and material budget amendments;
b) maintaining or supervising books, accounts, ledgers, reconciliations, financial statements, payroll records, grant records, donation records, sponsorship records, in-kind contribution records, subscription records, fee records, restricted fund records, and expense records;
c) administering banking, payment, signing, reimbursement, procurement, contracting, and expenditure controls within authority;
d) supporting tax filings, state filings, charitable solicitation filings, grant reporting, audit engagement, insurance review, and financial compliance;
e) monitoring private inurement, impermissible private benefit, excess benefit, related-party transactions, donor restrictions, sponsor restrictions, restricted funds, and support concentration risks; and
f) escalating fraud, misuse, unauthorized expenditure, budget variance, restricted fund concern, grant compliance concern, tax risk, financial control weakness, or capture risk.
The Treasurer or Chief Financial Officer shall not conduct banking, lending, credit approval, securities activity, investment advice, brokerage, finder activity, insurance placement, underwriting, rating, public finance approval, capital placement, escrow, third-party custody, or enterprise finance execution unless a separate lawful structure expressly authorizes such function and the Corporation is permitted to engage in it. The Treasurer or Chief Financial Officer shall not use funds outside Board-approved public-benefit purposes or recorded authority.
132.8 Chief Evidence Officer. The Corporation may have a Chief Evidence Officer responsible for supporting evidence doctrine, evidence quality, evidence intake, source lineage, provenance, custody, confidence, uncertainty, evidentiary classification, evidence challenge, proof receipt support, public-safe evidence outputs, and correction of evidence records within delegated scope.
The Chief Evidence Officer may support evidence relating to systemic risk, resilience infrastructure, AI, AI-RAN, O-RAN, DePIN, DLT, blockchain, Web3, quantum-relevant systems, sovereign compute, HPC, cyber, robotics, drones, sensors, geospatial systems, Earth observation, digital twins, biosecurity, climate, nature, energy, water, food, health, disaster, telecom, supply chains, public trust, advanced manufacturing, semiconductors, and other exponential or mission-critical technologies.
The Chief Evidence Officer may provide technical evidence support to Board committees, public authority learning rooms, controlled rooms, Nexus Docket support, Nexus Grid support, GRF-facing inputs, and GRA-facing technical inputs. Such support shall not constitute recognition, standing, maturity determination, finance-readiness determination, insurance-readiness determination, rating, certification, procurement approval, public authority decision, public warning, emergency command, or operational instruction.
132.9 Chief Research Officer. The Corporation may have a Chief Research Officer responsible for supporting public-benefit research, research integrity, research ethics, scientific and technical research agendas, educational outputs, peer review, publication integrity, reproducibility, replication, research records, research correction, and research collaboration within delegated scope.
The Chief Research Officer may coordinate research involving universities, laboratories, fellows, students, visiting researchers, communities, public authorities, technical contributors, providers, sponsors, donors, funders, and Nexus interfaces, provided that research independence, conflict disclosure, sponsor disclosure, publication integrity, data / AI / cyber controls, civil rights, accessibility, Tribal and Indigenous protocols, protected knowledge, and public-safe publication requirements are preserved.
The Chief Research Officer shall ensure that research outputs are appropriately classified, limited, and corrected. Research outputs shall not be represented as professional advice, public authority approval, public warning, emergency command, certification, procurement approval, recognition, finance-readiness, insurance-readiness, rating, provider endorsement, or enterprise execution direction.
132.10 Chief Methods Officer. The Corporation may have a Chief Methods Officer responsible for supporting methods stewardship, method design, method versioning, validation methods, verification methods, confidence methods, uncertainty methods, source-comparison methods, corroboration methods, sensor-fusion methods, AI-output review methods, digital twin assumption review methods, DePIN and DLT validation methods, AI-RAN and O-RAN signal interpretation methods, geospatial evidence methods, cyber evidence methods, observability methods, Nexus Truth Engine methods, and correction methods.
The Chief Methods Officer may maintain or support method registers, method profiles, validation protocols, uncertainty notes, public-safe method summaries, controlled-room methods, and technical baselines. Each method shall identify scope, excluded scope, assumptions, confidence limits, validation requirements, public-safe limitations, review cycle, correction pathway, and relationship to relevant evidence, data, AI, cyber, safeguards, and public authority boundaries.
A method shall not become certification, legal compliance approval, procurement mandate, public authority decision, finance-readiness determination, insurance-readiness determination, rating, recognition, public warning, emergency command, or operational authority merely because it is adopted, stewarded, or used by the Corporation.
132.11 Chief Technology Officer. The Corporation may have a Chief Technology Officer responsible for supporting technical architecture, public-good software, open technical baselines, repositories, schemas, APIs, SDKs, dashboards, data tools, reference architectures, test harnesses, gold vectors, negative tests, benchmark libraries, observability technical environments, Truth Engine technical environments, verifiable compute support, secure release, interoperability, and technical incident escalation within delegated scope.
The Chief Technology Officer may coordinate technical teams, maintainers, contributors, vendors, cloud providers, AI providers, data processors, cybersecurity resources, public-good software releases, and technical asset governance, subject to IP, licensing, data, AI, cyber, privacy, sanctions, export-control, controlled-technology, competition, safeguards, public-safe publication, and Board-approved authority controls.
The Chief Technology Officer shall not treat technical centrality as governance authority. No repository merge, software release, API integration, dashboard launch, model output, proof receipt, ledger entry, role key, smart license, standard profile, technical baseline, signal feed, digital twin, AI-RAN signal, DePIN record, or sensor signal shall be represented as certification, procurement approval, provider preference, public authority decision, public warning, emergency command, recognition, finance-readiness, or enterprise authorization unless a competent body lawfully records that meaning.
132.12 Chief Data, AI, and Cyber Officer. The Corporation may have a Chief Data, AI, and Cyber Officer responsible for supporting data governance, privacy, AI governance, cybersecurity, secure compute, model registers, inference records, compute workload records, agentic AI controls, identity and access controls, logging, monitoring, vulnerability management, incident response, backup, business continuity, disaster recovery, repository security, and secure development within delegated scope.
The Chief Data, AI, and Cyber Officer shall support controls for rights-bearing data, public authority data, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, community-protected data, Tribal and Indigenous data, protected knowledge, controlled technology, cross-border transfers, sovereign data zones, and other sensitive systems. This office may require access restriction, model freeze, dataset freeze, repository freeze, publication hold, controlled-room restriction, credential reset, forensic review, incident escalation, legal hold, or correction where a material data / AI / cyber risk exists.
The Chief Data, AI, and Cyber Officer shall preserve the rule that AI, compute, cyber tools, dashboards, digital twins, DePIN records, DLT records, blockchain entries, model outputs, automated scores, inference logs, observability signals, sensor signals, or AI-RAN / O-RAN signals are not institutional authority without human authorization, competent record, lawful scope, limitation language, and correction pathway.
132.13 Chief Public-Good Software and Technical Assets Officer. The Corporation may have a Chief Public-Good Software and Technical Assets Officer responsible for supporting public-good software stewardship, open technical baseline stewardship, technical asset registers, contributor governance, open-source and public-good licensing, restricted licensing where needed, IP chain-of-title, contributor license agreements, secure release, SBOM, signing, provenance, dependency review, vulnerability review, rollback, repository discipline, fork review, compatibility claim review, anti-enclosure controls, and technical asset archival within delegated scope.
This office may support public-good assets such as software tools, schemas, APIs, SDKs, dashboards, data tools, reference architectures, evidence tools, observability tools, verifiable compute tools, benchmark assets, method libraries, controlled vocabularies, public-safe templates, and technical profiles.
Public-good software and technical assets shall be stewarded for public-benefit purposes and may be open, restricted, controlled, internal, public-safe, deprecated, withdrawn, retired, or archived depending on legal, security, privacy, protected knowledge, public-safe publication, and mission requirements. No public-good asset shall be represented as certification, procurement approval, provider preference, public authority decision, finance-readiness, recognition, public warning, emergency command, or operational authorization by default.
132.14 Chief Public Authority Learning Officer. The Corporation may have a Chief Public Authority Learning Officer responsible for supporting lawful public authority learning, federal, state, territorial, District of Columbia, Tribal, Indigenous government, local, county, municipal, metropolitan, utility, port, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, and infrastructure interfaces within delegated scope.
The Chief Public Authority Learning Officer may support public authority capacity classification, official-capacity records, observer records, regulator-listening records, public finance reader records, emergency-management participant records, public infrastructure operator records, public authority data contribution intake, public authority reference review, simulations, tabletops, scenario sessions, after-action learning, public authority rooms, and controlled rooms.
This office shall preserve the bright-line rule that public authority participation does not create public authority delegation, official adoption, sovereign obligation, public-private partnership, procurement approval, funding approval, regulatory approval, public finance approval, public warning, emergency command, or public authority decision. Where public authority confusion arises, the Chief Public Authority Learning Officer shall escalate for hold, correction, limitation, clarification, counsel review, or externalization to the competent authority.
132.15 Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer. The Corporation may have a Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer responsible for supporting community safeguards, civil rights, non-discrimination, accessibility, Tribal and Indigenous protocol respect, Indigenous data safeguards, protected knowledge, local and territorial knowledge, public-safe mapping, vulnerable and remote community safeguards, consent and non-consent pathways, attribution, withdrawal, restriction, correction, grievance, remedy, protected participation, whistleblowing, non-retaliation, and do-no-harm review within delegated scope.
This office may exercise or support safeguards stop-the-line authority where authorized, including recommending or initiating holds, publication freezes, mapping restrictions, dataset restrictions, access restrictions, controlled-room restrictions, repository restrictions, community review, Tribal or Indigenous protocol review, legal review, correction, withdrawal, retraction, takedown, or public-safe limitation where safeguards concerns arise.
No program, sponsor, provider, donor, funder, host, public authority participant, researcher, technical team, media participant, or officer may extract, disclose, commercialize, instrumentalize, or overclaim protected knowledge for convenience, reputation, funding, speed, technical completeness, publication, recognition, finance-readiness, procurement, certification, or enterprise-stack advantage. Safeguards duties shall be substantive controls, not cosmetic consultation.
132.16 Chief Legal, Compliance, and Risk Officer Where Approved. The Corporation may have a Chief Legal, Compliance, and Risk Officer where approved by the Board. This office shall support legal compliance, corporate compliance, federal tax and state nonprofit compliance, charitable solicitation and foreign qualification compliance, privacy compliance, AI governance compliance, cybersecurity compliance, research ethics compliance, employment and workplace compliance, accessibility and civil rights compliance, grant compliance, lobbying and political activity controls, government ethics, gifts, procurement integrity, sanctions, export-control, controlled technology, competition, professional-boundary review, regulatory-perimeter escalation, risk registers, issue registers, control registers, incident registers, investigations, enforcement, appeals, corrective action, and counsel coordination.
The Chief Legal, Compliance, and Risk Officer may be a licensed attorney, non-lawyer compliance officer, risk officer, or combined role, as approved and lawful. Where the person is not admitted or authorized to practice law in the relevant jurisdiction, the role shall not be represented as giving legal advice, legal opinions, attorney-client privileged advice, or legal representation unless authorized by law and coordinated with counsel.
This office shall have escalation responsibility for matters involving public authority overclaim, finance overclaim, securities, investment adviser, broker-dealer, finder, insurance, banking, lending, rating, public finance, procurement, certification, recognition, provider preference, sponsor control, data / AI / cyber incident, protected knowledge breach, sanctions, export-control, controlled technology, competition, professional boundary, tax, nonprofit, or public-benefit risk.
132.17 Chief Operating Officer Where Approved. The Corporation may have a Chief Operating Officer responsible for supporting operational management, program operations, people operations, vendor and contractor operations, facilities, tools, systems, administrative controls, procurement process, contracting process, records operations, business continuity, operational resilience, delegation matrix implementation, and internal process discipline within delegated scope.
The Chief Operating Officer may coordinate daily operations across functions, provided that operational efficiency does not override law, the Articles or Certificate, this Bylaw, Board approvals, budget authority, public-benefit purpose, non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, research integrity, public-safe publication, or records discipline.
The Chief Operating Officer shall escalate material operational risk, staffing risk, vendor risk, contractor risk, facility risk, system risk, continuity risk, procurement risk, records risk, access risk, or implementation drift. No operational custom shall amend the Bylaw or create hidden authority.
132.18 Chief Development, Grants, and Public-Good Support Officer Where Approved. The Corporation may have a Chief Development, Grants, and Public-Good Support Officer responsible for supporting fundraising strategy, grant development, donation development, sponsorship development, public-good support development, in-kind contribution coordination, subscription and fee program coordination where delegated, support acceptance intake, donor records, funder records, sponsor records, supporter records, public acknowledgment controls, restricted fund coordination, and anti-capture controls.
This office shall ensure that support arrangements are screened for legality, tax treatment, nonprofit compatibility, private benefit, inurement, conflicts, related parties, sanctions, export-control, controlled technology, public authority boundary, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, sponsor non-control, data / AI / cyber, safeguards, protected knowledge, research independence, and public-safe claim risks.
No development, grant, donation, sponsorship, fee, subscription, in-kind support, or public-good support activity shall be used to sell or imply control, outcome purchase, publication veto, public authority access, recognition, finance-readiness, insurance-readiness, certification, procurement advantage, provider preference, standards outcome, Docket outcome, Grid outcome, Nexus-compatible status, or enterprise execution opportunity. Fundraising shall remain public-benefit support, not regulated capital solicitation or pay-to-play influence.
132.19 Additional Officers Authorized by Board Resolution. The Board may create additional officer positions where necessary or appropriate to advance the Corporation’s lawful public-benefit purposes and institutional maturity. Additional officers may be functional, regional, programmatic, technical, compliance, safeguards, educational, administrative, repository, public authority learning, or Nexus-interface officers, provided that each is created by competent record.
A Board resolution creating an additional officer position shall specify:
a) title and approved short title;
b) purpose and public-benefit justification;
c) statutory or non-statutory status;
d) appointment authority;
e) reporting line;
f) duties;
g) authority limits;
h) budget, signature, contracting, publication, public statement, data access, AI-use, repository, controlled-room, public authority interface, and correction authority where applicable;
i) prohibited functions;
j) conflict, independence, confidentiality, data / AI / cyber, safeguards, public-safe publication, and records requirements;
k) review cycle, sunset, amendment, and dissolution rules; and
l) register entry and repository location.
No additional officer position shall be created in a manner that fragments responsibility, weakens internal controls, duplicates authority without clarity, creates sponsor or provider control, creates public authority confusion, creates finance-boundary risk, creates certification or procurement overclaim, or collapses GCRI US into another Nexus or enterprise-stack role.
132.20 Combination of Offices Where Permitted by Law and Not Inconsistent With Controls. One person may hold more than one office only where permitted by applicable law, the Articles or Certificate, this Bylaw, Board resolution, internal control requirements, tax-exempt or tax-exempt-compatible discipline, conflict controls, segregation-of-duties requirements, financial controls, records requirements, and public-benefit governance standards.
The Board may approve combined offices where the combination promotes continuity, efficiency, startup practicality, cost control, or mission delivery without weakening governance. A combination of offices shall be reviewed for:
a) statutory compatibility;
b) conflict of interest;
c) concentration of authority;
d) financial control risk;
e) records integrity risk;
f) public authority boundary risk;
g) finance-boundary risk;
h) certification and procurement boundary risk;
i) provider-neutrality and sponsor non-control risk;
j) data / AI / cyber access concentration;
k) safeguards and protected knowledge risk;
l) succession risk;
m) emergency governance risk; and
n) anti-capture risk.
The Board may require compensating controls, including countersignature, independent review, committee oversight, spending limits, access restrictions, separate records custodianship, enhanced reporting, periodic review, recusal rules, or separation of offices. No combined office shall allow self-approval of compensation, reimbursement, related-party transactions, conflicts, public-safe claims, financial controls, record corrections, access grants, or material outputs.
132.21 Separation of Offices Where Needed for Segregation of Duties. The Board shall separate offices, duties, approvals, custody, access, review, and reporting lines where separation is necessary to preserve internal controls, fiduciary discipline, records integrity, financial integrity, data / AI / cyber security, conflict management, safeguards, public authority boundary discipline, finance-boundary discipline, certification-boundary discipline, procurement neutrality, provider neutrality, sponsor non-control, or public trust.
Separation may be required between:
a) approval and payment;
b) custody and reconciliation;
c) grant development and restricted fund compliance;
d) sponsorship development and anti-capture review;
e) provider relationship management and provider-neutrality review;
f) public authority interface management and public authority capacity classification;
g) data access administration and privacy review;
h) AI system administration and model output approval;
i) repository administration and secure release approval;
j) software development and vulnerability review;
k) publication drafting and public-safe publication approval;
l) evidence creation and evidence validation;
m) research sponsorship and research integrity review;
n) safeguards review and program delivery;
o) conflict disclosure and conflict adjudication; and
p) officer compensation proposal and officer compensation approval.
Where personnel constraints require temporary overlap, the Board or authorized officer shall record compensating controls and review them periodically. The Corporation shall not allow convenience, speed, founder dependence, technical dependence, sponsor dependence, provider dependence, or funding pressure to justify unsafe concentration of authority.
132.22 Officer Register. The Corporation shall maintain an Officer Register as an authoritative record of all officers, acting officers, interim officers, statutory officers, non-statutory officers, principal officers, delegated officers, former officers, suspended officers, removed officers, resigned officers, and vacant offices.
The Officer Register shall include, as applicable:
a) officer name, title, office class, statutory or non-statutory status, appointment authority, appointment date, effective date, term, renewal status, reporting line, and role description;
b) Board resolution, written consent, employment agreement, services agreement, delegation, authority matrix, budget authority, signature authority, banking authority, contracting authority, publication authority, public statement authority, public authority reference authority, data access authority, AI-use authority, model approval authority, repository authority, software release authority, controlled-room authority, incident response authority, correction authority, and emergency authority;
c) eligibility, fit-and-proper review, integrity review, conflict disclosure, independence review, sanctions screening, export-control screening, controlled-technology review, public authority boundary review, finance-boundary review, certification-boundary review, procurement-neutrality review, provider-neutrality review, sponsor non-control review, data / AI / cyber review, privacy review, research integrity review, safeguards review, civil rights review, accessibility review, and protected knowledge review;
d) compensation status, reimbursement status, benefits status, related-party status, recusal requirements, access restrictions, training requirements, certification of understanding, performance evaluation, corrective training, and accountability records;
e) resignation, suspension, removal, vacancy, acting appointment, interim appointment, succession, handover, access revocation, credential revocation, record return, record sealing, deletion, archive, confidentiality survival, conflict survival, legal hold, and post-service restriction records; and
f) custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The Officer Register shall control over informal titles, biographies, email signatures, websites, decks, proposals, grant submissions, sponsor materials, provider materials, public authority materials, repository labels, organizational charts, AI summaries, and public descriptions. Where a public description conflicts with the Officer Register, the Register shall control and the public description shall be corrected.
The governing rule of this Section is that officers exist to make GCRI US capable, accountable, and operational within its lawful public-benefit mission. Officer roles shall therefore be explicit, bounded, recorded, trained, supervised, conflict-managed, removable, and correctionable. No officer title shall be allowed to become a hidden amendment to the Bylaw, a substitute Board, a public authority, a finance-readiness authority, a certification body, a procurement body, a recognition body, a provider-selection body, a sponsor-control mechanism, or an enterprise execution office.
Section 133. Appointment, Term, Eligibility, Screening, Consent, and Good Standing of Officers
133.1 Appointment Authority. Officers shall be appointed, elected, confirmed, designated, renewed, suspended, removed, replaced, or continued only by the authority permitted under applicable law, the Articles or Certificate, this Bylaw, Board resolution, Board-approved policy, written delegation, employment or services agreement, or other competent governing record.
The Board shall retain authority over principal officers and any officer whose role materially affects corporate governance, financial authority, public-benefit mission, tax-exempt or tax-exempt-compatible status, legal compliance, records custody, public authority interface, data / AI / cyber controls, safeguards, public-safe publication, research integrity, public-good software, technical baselines, Nexus interfaces, sponsor relationships, provider relationships, or Board reserved matters.
Appointment authority shall be exercised in a manner that preserves:
a) United States nonprofit corporate discipline;
b) public-benefit purpose;
c) tax-exempt or tax-exempt-compatible posture;
d) non-execution;
e) GCRI / GRF / GRA role separation;
f) public-good stack and enterprise stack separation;
g) public authority boundary discipline;
h) finance, securities, insurance, lending, rating, public finance, procurement, certification, recognition, and professional-boundary discipline;
i) data / AI / cyber / privacy controls;
j) civil rights, accessibility, Tribal and Indigenous protocol respect, community safeguards, protected knowledge, and public-safe mapping controls;
k) provider neutrality and sponsor non-control;
l) validity-by-record; and
m) correctionability.
No officer shall be appointed by implication, course of dealing, title use, public statement, website entry, proposal, grant application, fundraising deck, sponsor request, provider request, public authority communication, repository access, controlled-room access, AI-system access, technical authorship, committee participation, advisory status, or Nexus interface participation alone.
133.2 Board Appointment of Principal Officers. Principal officers shall be appointed by the Board unless applicable law, the Articles or Certificate, this Bylaw, or a recorded Board delegation lawfully provides otherwise. Principal officers may include, as applicable, the President, Executive Director, Chief Executive Officer, Secretary, Treasurer, Chief Financial Officer, Chief Legal, Compliance, and Risk Officer, Chief Data, AI, and Cyber Officer, Chief Evidence Officer, Chief Research Officer, Chief Methods Officer, Chief Technology Officer, Chief Public-Good Software and Technical Assets Officer, Chief Public Authority Learning Officer, Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer, Chief Operating Officer, Chief Development, Grants, and Public-Good Support Officer, and any other officer designated by the Board as principal.
A Board appointment of a principal officer shall be made by resolution, written consent, or other lawful Board action and shall identify, as applicable:
a) officer name;
b) title;
c) office class;
d) statutory or non-statutory status;
e) appointment date;
f) effective date;
g) term or at-will status;
h) reporting line;
i) role description;
j) delegated authority;
k) authority limitations;
l) compensation or unpaid status;
m) required acknowledgments;
n) required training;
o) conflict, independence, confidentiality, safeguards, data / AI / cyber, public-safe publication, and records obligations;
p) any required countersignature, committee review, counsel review, or approval threshold; and
q) Officer Register entry requirements.
A Board appointment shall not authorize the officer to approve Board reserved matters unless the Board expressly and lawfully delegates a specific matter and such delegation is permitted by law and this Bylaw. No appointment shall authorize a prohibited function.
133.3 Delegated Appointment of Non-Principal Officers Where Authorized. The Board may authorize the appointment of non-principal officers by the President, Executive Director, Chief Executive Officer, Secretary, Treasurer, Chief Operating Officer, Chief Legal, Compliance, and Risk Officer, or other designated officer, provided that the delegation is lawful, written, bounded, recorded, reviewable, and consistent with this Bylaw.
Delegated appointment authority may be used for operational, technical, administrative, programmatic, repository, data, AI, cyber, safeguards, public authority learning, academy, research, fellowship, development, or regional-interface officer roles where the role does not materially affect Board reserved matters, legal status, tax status, public-benefit purpose, mission lock, non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, recognition boundaries, provider neutrality, sponsor non-control, or enterprise-stack separation.
A delegated appointment shall be invalid, voidable, suspended, or non-operative to the fullest extent lawful where it:
a) exceeds the delegation;
b) creates a principal officer role without Board approval;
c) grants budget, contracting, signature, publication, data access, AI-use, repository, controlled-room, public authority interface, correction, or emergency authority outside the authority matrix;
d) creates public authority confusion;
e) creates finance, certification, procurement, recognition, provider-preference, or sponsor-control risk;
f) creates unsafe concentration of access or control;
g) bypasses screening, conflict review, or safeguards review; or
h) creates an appearance that an officer may bind the Corporation beyond recorded authority.
Each delegated appointment shall be reported to the Board or relevant committee where required, entered in the Officer Register, and reviewed periodically for authority, need, performance, risk, and continuing good standing.
133.4 Officer Eligibility. A person shall be eligible to serve as an officer only if the person satisfies applicable law, the Articles or Certificate, this Bylaw, Board-approved policies, role description, screening requirements, consent requirements, conflict requirements, confidentiality requirements, data / AI / cyber requirements, safeguards requirements, and any qualification specific to the office.
Eligibility shall be assessed before appointment and periodically thereafter. Eligibility may depend on:
a) legal capacity;
b) identity verification;
c) ability to perform the duties of the office;
d) integrity and fit-and-proper status;
e) absence of disqualifying misconduct;
f) ability to comply with fiduciary-adjacent duties where applicable;
g) ability to maintain confidentiality;
h) ability to disclose and manage conflicts;
i) capacity to comply with public-benefit purpose and nonprofit controls;
j) understanding of non-execution and role separation;
k) competence relevant to the office;
l) ability to follow data / AI / cyber / privacy controls;
m) ability to respect civil rights, accessibility, community safeguards, Tribal and Indigenous protocols, and protected knowledge; and
n) willingness to support validity-by-record and correctionability.
Eligibility shall not be presumed from reputation, academic title, public office, former public office, donor relationship, sponsor relationship, provider relationship, technical skill, founder relationship, media profile, public authority contact, Nexus familiarity, or prior informal role.
133.5 Legal Eligibility. Each officer shall satisfy all legal eligibility requirements applicable to the office. Legal eligibility may include, where applicable, age, capacity, residency, employment authorization, corporate law eligibility, licensing or professional-boundary status, sanctions status, export-control status, government ethics restrictions, public authority restrictions, nonprofit restrictions, charitable restrictions, tax restrictions, grant restrictions, procurement restrictions, conflict restrictions, and any statutory rule governing officers of the Corporation.
The Corporation shall not appoint or continue an officer where legal eligibility is absent, uncertain without review, materially impaired, or dependent on an unlawful waiver. Where eligibility is uncertain, the Corporation may condition appointment upon counsel review, compliance review, additional disclosure, limitation of authority, access restriction, role narrowing, external authorization, or Board determination.
Legal eligibility shall be recorded. A person who becomes legally ineligible after appointment shall promptly disclose the condition and shall be subject to suspension, restriction, removal, resignation, reassignment, or other lawful action.
133.6 Fit-and-Proper Review. The Corporation may require fit-and-proper review before appointing or continuing an officer. Fit-and-proper review shall be proportionate to the office, authority, access, fiduciary significance, public-facing role, financial authority, data / AI / cyber access, public authority interface, safeguards exposure, technical asset control, sponsor interface, provider interface, and Nexus interface.
Fit-and-proper review may consider:
a) honesty, integrity, reputation, and reliability;
b) professional competence and judgment;
c) prior governance conduct;
d) prior nonprofit, research, public authority, academic, enterprise, technical, financial, or public-interest conduct;
e) history of fraud, corruption, harassment, retaliation, discrimination, abuse, exploitation, cyber misconduct, data misuse, research misconduct, protected knowledge breach, or public authority misrepresentation;
f) sanctions, export-control, controlled-technology, national security, procurement integrity, competition, or grant compliance concerns;
g) ability to respect boundaries between public-good stewardship and enterprise execution;
h) ability to preserve sponsor non-control and provider neutrality;
i) ability to operate under records discipline; and
j) willingness to correct errors.
Fit-and-proper review shall not be used to exclude persons on discriminatory, retaliatory, political, factional, sponsor-preference, provider-preference, donor-preference, or viewpoint-discriminatory grounds inconsistent with law, civil rights, public-benefit purpose, or the Corporation’s safeguards.
133.7 Integrity Review. The Corporation may conduct integrity review for officers whose roles involve governance, finance, records, public authority interface, public-safe publication, research, evidence, methods, data, AI, cybersecurity, repositories, controlled rooms, protected knowledge, sponsor relationships, provider relationships, grants, donations, or Nexus interfaces.
Integrity review may include review of:
a) accuracy of disclosures;
b) prior misconduct findings where relevant and lawfully considered;
c) material legal proceedings;
d) professional discipline;
e) research misconduct;
f) publication misconduct;
g) cybersecurity or data misuse history;
h) public authority misrepresentation;
i) fraud, bribery, corruption, money laundering, sanctions, export-control, procurement integrity, or grant integrity issues;
j) harassment, retaliation, discrimination, civil rights violations, safeguarding concerns, or protected-participation interference; and
k) misuse of institutional names, public claims, reports, datasets, software, marks, proof receipts, badges, technical baselines, or Nexus-compatible claims.
Integrity review shall be documented and access-limited. Allegations shall be handled fairly and proportionately. The Corporation may require additional controls, conditional appointment, restricted authority, denial of appointment, suspension, or removal where integrity risk is material and not capable of adequate mitigation.
133.8 Conflict Review. Before appointment and periodically thereafter, each officer shall disclose conflicts of interest, related-party interests, dual roles, financial interests, institutional affiliations, sponsor relationships, donor or funder relationships, provider relationships, host relationships, public authority relationships, investor, insurer, lender, underwriter, bank, public finance, capital-reader, national company, Project SPV, university, laboratory, community, media, civil society, or enterprise actor relationships relevant to the office.
Conflict review shall determine whether:
a) the conflict is disqualifying;
b) the conflict can be managed by disclosure;
c) recusal is required;
d) access restrictions are required;
e) signature, spending, contracting, publication, public statement, public authority reference, data access, AI-use, repository, controlled-room, software release, correction, or emergency authority must be restricted;
f) independent review is required;
g) Board or committee approval is required;
h) related-party transaction procedures are required;
i) compensation review is required;
j) sponsor non-control or provider-neutrality risk exists; or
k) the appointment should be denied, deferred, narrowed, conditioned, suspended, or terminated.
Conflict review shall be recorded in the appropriate conflict records and Officer Register. Disclosure of a conflict shall not itself cure the conflict or validate action taken in breach of recusal or authority limits.
133.9 Independence Review. The Corporation may require independence review for officers whose roles materially affect Board reporting, finance, audit, internal controls, evidence, methods, research, public-safe publication, data / AI / cyber controls, safeguards, public authority interface, sponsor interface, provider interface, or Nexus interface.
Independence review shall consider whether the officer can exercise judgment without undue influence from:
a) sponsors;
b) donors or funders;
c) providers, vendors, contractors, or hosts;
d) public authorities;
e) national companies, state operating companies, regional companies, or Project SPVs;
f) investors, insurers, lenders, underwriters, banks, public finance actors, or capital readers;
g) universities, laboratories, research sponsors, or publication stakeholders;
h) political, partisan, campaign, lobbying, government ethics, or procurement relationships;
i) personal relationships; or
j) any person seeking recognition, finance-readiness, certification, procurement advantage, public authority access, technical approval, provider preference, or public-safe claim advantage.
Independence review may result in recusal, authority limitation, access limitation, supervision, dual-control requirements, committee oversight, public description limitation, or non-appointment. Independence is role-specific and shall be reviewed when facts change.
133.10 Sanctions and Export-Control Screening Where Applicable. The Corporation shall conduct sanctions, export-control, controlled-technology, restricted-party, and national security sensitivity screening where the officer’s role involves cross-border activity, controlled technology, AI systems, cybersecurity, infrastructure-sensitive data, sovereign compute, secure compute, DLT, blockchain, DePIN, AI-RAN, O-RAN, geospatial systems, Earth observation, sensors, digital twins, public authority data, public authority interfaces, protected knowledge, technical releases, repositories, procurement-sensitive information, grants, donations, sponsorships, or international collaboration.
Screening may include review of:
a) restricted-party lists;
b) sanctions exposure;
c) export-control classification;
d) controlled technology access;
e) dual-use or defense-sensitive implications;
f) country, territory, entity, institution, employer, sponsor, provider, funder, or beneficiary risk;
g) cybersecurity and infrastructure sensitivity;
h) data localization or cross-border transfer restrictions; and
i) restrictions imposed by grant, contract, public authority, funder, insurer, repository, or controlled-room rules.
An officer shall not be granted access to restricted data, controlled technology, export-controlled materials, cyber-sensitive systems, protected knowledge, public authority materials, or technical repositories until required screening is complete or an authorized interim restriction is recorded.
133.11 Controlled Technology Screening Where Applicable. Where an officer may access, develop, review, release, transmit, or supervise controlled technology, controlled technical data, dual-use systems, cybersecurity tools, encryption-sensitive systems, AI models, secure compute systems, AI-RAN / O-RAN interfaces, DePIN systems, DLT systems, sensor networks, geospatial systems, Earth observation systems, digital twins, critical infrastructure models, or other sensitive technical assets, the Corporation shall conduct controlled technology screening appropriate to the role.
Controlled technology screening shall consider whether:
a) access is lawful;
b) access is necessary;
c) access can be limited;
d) jurisdictional restrictions apply;
e) export-control rules apply;
f) sanctions rules apply;
g) public authority restrictions apply;
h) grant or contract restrictions apply;
i) cyber-sensitive handling rules apply;
j) repository access controls are sufficient;
k) AI-use restrictions are required;
l) secure-room or no-download rules are required; and
m) technical release authority must be withheld or dual-controlled.
The Corporation may deny, delay, condition, restrict, monitor, revoke, or compartmentalize access where controlled technology risk cannot be safely managed.
133.12 Public Authority Boundary Screening Where Applicable. Where an officer may interact with federal, state, territorial, District of Columbia, Tribal, Indigenous government, local, municipal, county, metropolitan, utility, port, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, infrastructure, regulatory, procurement, grant, public finance, or public infrastructure operator bodies, the Corporation shall conduct public authority boundary screening.
Public authority boundary screening shall determine whether the officer understands and can comply with:
a) no public authority delegation;
b) no public warning;
c) no emergency command;
d) no regulator substitution;
e) no procurement approval;
f) no funding approval;
g) no public finance approval;
h) no official adoption by participation;
i) no sovereign obligation;
j) no public-private partnership claim without competent instrument;
k) public authority capacity classification;
l) official-capacity, observer, regulator-listening, public finance reader, emergency-management participant, and public infrastructure operator classifications;
m) public records, open meetings, public procurement, government ethics, gifts, lobbying, grant, privacy, cyber, security, and public authority confidentiality considerations; and
n) public authority reference controls.
An officer who cannot maintain public authority boundary discipline shall not be appointed to a public authority interface role or shall be restricted, supervised, trained, or removed from that function.
133.13 Finance, Securities, Insurance, Lending, Rating, Public Finance, Procurement, Certification, and Professional Boundary Screening Where Applicable. Where an officer may interact with finance-adjacent, capital-reader, insurance, lending, public finance, procurement, certification, professional advisory, GRA-facing, GRF-facing, Docket, Grid, sponsor, provider, national company, Project SPV, investor, insurer, lender, bank, underwriter, rating, diligence, or public authority funding materials, the Corporation shall conduct regulated-boundary screening.
Such screening shall assess whether the officer understands and can comply with the Corporation’s prohibitions on:
a) securities offerings or solicitations;
b) broker-dealer, finder, capital placement, underwriting, or investment adviser activity;
c) banking, deposit-taking, lending, credit approval, guarantee, or escrow activity;
d) insurance placement, binding, underwriting, pricing, claims handling, or insurance approval;
e) rating, credit opinion, bankability, insurability, investment grade, resilience rating, or financeability determination;
f) public finance approval, tax credit approval, appropriation, grant approval, MDB / DFI approval, sovereign finance approval, public guarantee, or budget allocation;
g) procurement approval, vendor selection, procurement preference, or bid steering;
h) certification, accreditation, legal compliance approval, conformance approval, or regulated credentialing;
i) professional legal, engineering, medical, clinical, public health, financial, insurance, securities, tax, or other professional advice unless separately and lawfully authorized; and
j) recognition, standing, maturity, Docket approval, Grid guarantee, or Nexus-compatible public status unless the competent body and record authorize it.
Where screening identifies material regulated-boundary risk, the Corporation may deny appointment, restrict authority, require counsel review, impose public-safe notices, prohibit external communication, require supervision, or route the function to a competent licensed or authorized actor.
133.14 Data / AI / Cyber / Privacy Eligibility Review. Where an officer may access or supervise data, AI systems, models, compute, repositories, cyber systems, controlled rooms, datasets, dashboards, technical baselines, public authority data, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, rights-bearing data, Tribal or Indigenous data, protected knowledge, or cross-border data flows, the Corporation shall conduct data / AI / cyber / privacy eligibility review.
The review shall assess the officer’s ability and willingness to comply with:
a) data minimization;
b) purpose limitation;
c) access controls;
d) confidentiality;
e) logging;
f) identity controls;
g) credential and key management;
h) AI-use restrictions;
i) model register requirements;
j) inference record requirements;
k) compute workload record requirements;
l) no unapproved AI uploads;
m) no shadow IT;
n) secure development rules;
o) repository security;
p) incident reporting;
q) cross-border transfer controls;
r) public-safe publication controls;
s) deletion, retention, sealing, and archive rules; and
t) correction requirements.
No officer shall receive sensitive access unless the access is necessary, proportionate, approved, logged, revocable, and subject to records discipline.
133.15 Research Integrity Eligibility Review. Where an officer may direct, supervise, review, publish, fundraise for, support, or communicate research, evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, technical baselines, peer review, model review, red-team review, benchmarks, public-safe reports, or technical outputs, the Corporation shall conduct research integrity eligibility review.
Research integrity eligibility review shall assess the officer’s capacity to preserve:
a) research independence;
b) evidence integrity;
c) method discipline;
d) reproducibility;
e) transparency appropriate to classification;
f) source lineage;
g) provenance;
h) confidence and uncertainty disclosure;
i) sponsor and funder disclosure;
j) conflict disclosure;
k) peer review where applicable;
l) public-safe publication;
m) correction, supersession, withdrawal, retraction, and archive discipline; and
n) separation between evidence support, GRF recognition functions, GRA finance-readiness functions, public authority decisions, certification, procurement, and enterprise execution.
An officer with a material unresolved research integrity concern may be denied appointment, restricted from research authority, required to undergo corrective training, subjected to supervision, or removed from research-related functions.
133.16 Civil Rights, Accessibility, Community Safeguards, Tribal / Indigenous, and Protected Knowledge Eligibility Review. Where an officer may interact with communities, Tribal or Indigenous governments, Indigenous knowledge holders, local or territorial knowledge holders, vulnerable or remote communities, youth, health-sensitive populations, disaster-exposed communities, climate-exposed communities, infrastructure-exposed communities, civil society, media, public-interest participants, or protected knowledge systems, the Corporation shall conduct safeguards eligibility review.
Safeguards eligibility review shall assess the officer’s capacity to comply with:
a) civil rights and non-discrimination requirements;
b) accessibility requirements;
c) inclusive participation obligations;
d) Tribal sovereignty respect;
e) Indigenous governance respect;
f) Indigenous data safeguards;
g) protected knowledge safeguards;
h) local and territorial knowledge protections;
i) consent, non-consent, attribution, withdrawal, restriction, correction, and remedy pathways where applicable;
j) public-safe mapping restrictions;
k) do-no-harm review;
l) grievance and remedy systems;
m) protected participation and non-retaliation; and
n) safeguards stop-the-line processes.
No officer shall be appointed or continued in a safeguards-sensitive role where the person’s conduct, conflict, incentives, training, or role design creates unacceptable risk of extraction, discrimination, retaliation, exclusion, unsafe disclosure, protected knowledge misuse, or community harm.
133.17 Officer Consent. No person shall serve as an officer unless the person has consented to serve in a manner recorded by the Corporation. Consent may be provided by signed instrument, electronic acknowledgment, written acceptance, employment agreement, services agreement, Board minutes, or other reliable record.
Officer consent shall confirm, as applicable, that the person:
a) accepts the office;
b) understands the role description;
c) accepts the authority limits;
d) agrees to comply with law, the Articles or Certificate, this Bylaw, Board resolutions, policies, delegations, authority matrices, and records requirements;
e) agrees to disclose conflicts;
f) agrees to maintain confidentiality;
g) agrees to comply with data / AI / cyber / privacy controls;
h) agrees to comply with safeguards, civil rights, accessibility, Tribal and Indigenous protocol, protected knowledge, and public-safe publication controls;
i) agrees to avoid public authority, finance, certification, procurement, recognition, provider-preference, sponsor-control, public warning, emergency command, and enterprise execution overclaims;
j) agrees to complete required training;
k) agrees to support correctionability; and
l) agrees to return, delete, transfer, seal, or preserve records and materials upon resignation, removal, suspension, role change, legal hold, or closeout as required.
A person who acts without consent shall not be treated as a valid officer unless and until lawful appointment and consent are properly recorded and any prior acts are reviewed.
133.18 Officer Acknowledgment of Duties. Each officer shall acknowledge the duties applicable to the office. The acknowledgment shall be tailored to the role and may include general officer duties, fiduciary-adjacent duties where applicable, confidentiality duties, conflict duties, recusal duties, reporting duties, escalation duties, records duties, data / AI / cyber duties, research integrity duties, public authority boundary duties, finance-boundary duties, certification-boundary duties, procurement-neutrality duties, provider-neutrality duties, sponsor non-control duties, safeguards duties, public-safe publication duties, and correction duties.
The acknowledgment shall expressly state that officer authority is bounded by record and shall not include authority to:
a) amend governing documents;
b) approve Board reserved matters;
c) bind the Corporation outside delegation;
d) create public authority meaning;
e) issue public warnings or emergency commands;
f) conduct regulated finance, securities, insurance, lending, banking, rating, public finance, brokerage, finder, underwriting, or investment adviser functions;
g) certify, accredit, approve procurement, recognize maturity or standing, or approve Nexus-compatible status unless separately and lawfully authorized;
h) prefer providers or confer sponsor control;
i) release data, AI outputs, protected knowledge, public authority materials, or technical assets outside controls; or
j) execute enterprise-stack functions.
Failure to provide required acknowledgment may delay appointment, restrict authority, suspend access, or prevent service.
133.19 Officer Term. An officer shall serve for the term, at-will period, project period, fiscal period, calendar period, employment period, contract period, acting period, interim period, or continuing period specified by law, the Articles or Certificate, this Bylaw, Board resolution, appointment record, employment agreement, services agreement, or other competent record.
If no term is specified, the officer shall serve until resignation, removal, replacement, expiration of employment or services arrangement, expiration of delegation, dissolution of office, loss of eligibility, or other lawful end of service, subject to the Board’s authority and applicable law.
Officer terms may be structured to support continuity, review, accountability, succession, periodic renewal, mission alignment, anti-capture controls, and risk management. An officer’s continuation in service shall not be used to create permanent tenure, founder entitlement, sponsor entitlement, provider entitlement, public authority entitlement, or authority beyond the recorded office.
133.20 Renewal. Officer renewal shall be subject to continuing eligibility, performance, good standing, need for the office, mission alignment, budget availability, legal compliance, conflict review, independence review, compensation review where applicable, authority review, access review, training status, records status, and risk review.
Before renewal, the Corporation may review:
a) performance against role description;
b) compliance with authority limits;
c) conflict disclosure and recusal history;
d) reporting quality;
e) records quality;
f) financial stewardship where applicable;
g) data / AI / cyber compliance;
h) research integrity compliance;
i) safeguards compliance;
j) public authority boundary compliance;
k) finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control compliance;
l) public-safe claims discipline;
m) correction responsiveness;
n) staff, contractor, contributor, and participant management where applicable; and
o) any incident, complaint, investigation, or corrective action.
Renewal may be approved, denied, deferred, conditioned, shortened, re-scoped, compensated differently, subjected to additional controls, or replaced. Renewal shall be recorded.
133.21 Good Standing. An officer shall remain in good standing only while the officer satisfies eligibility requirements, performs duties, complies with law and governing instruments, remains within authority, maintains required training, maintains required disclosures, preserves confidentiality, follows records discipline, escalates material risks, avoids prohibited functions, supports correctionability, and complies with all role-specific obligations.
Good standing may be impaired by:
a) loss of legal eligibility;
b) failure to disclose conflicts;
c) breach of recusal;
d) unmanaged related-party interest;
e) unauthorized act;
f) public authority overclaim;
g) finance, securities, insurance, lending, rating, public finance, procurement, certification, recognition, provider-preference, or sponsor-control overclaim;
h) data misuse, AI misuse, cyber misconduct, credential misuse, repository misuse, or controlled-room breach;
i) research misconduct, evidence manipulation, method misuse, publication suppression, or correction suppression;
j) breach of civil rights, accessibility, community safeguards, Tribal or Indigenous protocols, protected knowledge, public-safe mapping, grievance, remedy, protected participation, or non-retaliation obligations;
k) misuse of name, marks, titles, reports, datasets, software, technical baselines, proof receipts, badges, logos, or public-good assets;
l) breach of confidentiality or privilege;
m) persistent failure to perform duties;
n) failure to complete required training;
o) retaliation, harassment, discrimination, intimidation, or suppression of dissent; or
p) conduct materially inconsistent with public-benefit purpose, nonprofit character, non-execution, role separation, validity-by-record, or correctionability.
Loss or impairment of good standing may result in warning, corrective training, supervision, recusal expansion, access restriction, delegation suspension, compensation review, suspension, removal, contract remedy, public or controlled correction, legal referral, or other lawful action.
133.22 Officer Appointment and Eligibility Records. The Corporation shall maintain Officer Appointment and Eligibility Records sufficient to demonstrate that each officer has been appointed, screened, consented, acknowledged, trained, delegated, renewed, restricted, suspended, removed, or closed out only within lawful authority and consistent with this Bylaw.
Officer Appointment and Eligibility Records shall include, as applicable:
a) office creation record;
b) appointment authority record;
c) Board resolution or delegated appointment record;
d) role description;
e) reporting line;
f) term record;
g) consent to serve;
h) duty acknowledgment;
i) eligibility review;
j) legal eligibility record;
k) fit-and-proper review;
l) integrity review;
m) conflict disclosure and review;
n) independence review;
o) sanctions screening;
p) export-control screening;
q) controlled-technology screening;
r) public authority boundary screening;
s) finance, securities, insurance, lending, rating, public finance, procurement, certification, recognition, provider-neutrality, and sponsor non-control boundary screening;
t) data / AI / cyber / privacy eligibility review;
u) research integrity eligibility review;
v) civil rights, accessibility, community safeguards, Tribal / Indigenous, and protected knowledge eligibility review;
w) compensation, reimbursement, benefits, and related-party review where applicable;
x) training and certification of understanding;
y) authority matrix entry;
z) access records;
aa) good standing reviews;
bb) renewal records;
cc) resignation, suspension, removal, vacancy, acting appointment, interim appointment, succession, handover, access revocation, credential revocation, records return, records deletion or sealing, legal hold, archive, and closeout records; and
dd) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that no officer may enter, hold, expand, renew, or continue office on trust, title, relationship, urgency, technical indispensability, public visibility, sponsor preference, provider preference, public authority familiarity, or informal practice alone. Officer service shall be lawful, consented, screened, acknowledged, bounded, recorded, reviewable, trainable, removable, and correctionable.
Section 134. General Duties of All Officers
134.1 Duty to Act Within Authority. Each officer shall act only within the authority granted by applicable law, the Articles or Certificate, this Bylaw, Board resolution, Board-approved policy, approved budget, written delegation, authority matrix, employment or services agreement, committee charter where applicable, and other competent governing record.
An officer shall not assume, imply, exercise, delegate, enlarge, transfer, sublicense, externalize, or represent authority not expressly granted. Officer authority shall be interpreted narrowly where doubt exists and shall be subject to the more protective reading pending review.
No officer shall rely on title, seniority, founder relationship, public visibility, technical centrality, authorship, committee participation, advisory role, sponsor relationship, provider relationship, public authority relationship, repository access, data access, AI-system access, controlled-room access, Nexus interface participation, prior practice, urgency, or operational convenience as authority to bind the Corporation.
Any officer action outside authority shall be subject to hold, restriction, correction, ratification where lawful, withdrawal, retraction, takedown, suspension, removal, contractual remedy, legal review, or treatment as void, voidable, suspended, or non-operative to the fullest extent lawful.
134.2 Duty to Act in Good Faith. Each officer shall act in good faith, with honesty, care, diligence, loyalty to the Corporation’s lawful public-benefit purposes, respect for Board authority, and fidelity to the Corporation’s United States nonprofit, public-benefit, non-executing, evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, public authority learning, and Nexus-compatible stewardship role.
Good faith requires an officer to:
a) act for the Corporation’s public-benefit purposes and not for personal advantage, private inurement, impermissible private benefit, sponsor control, provider preference, public authority confusion, finance execution, certification, procurement, recognition, or enterprise-stack advantage;
b) disclose material facts, conflicts, risks, errors, incidents, limitations, assumptions, dependencies, and uncertainties known to the officer and relevant to the officer’s function;
c) avoid misleading public statements, incomplete internal records, selective disclosures, hidden side arrangements, undisclosed sponsor or provider influence, and authority-inflating descriptions;
d) follow applicable review, approval, notice, repository, register, publication, data, AI, cyber, safeguards, legal, compliance, and correction processes; and
e) cooperate with Board oversight, committee review, counsel review, audit or financial review, compliance review, safeguards review, incident response, and corrective action.
No officer shall claim good faith where the officer knowingly bypasses authority, conceals risk, suppresses correction, misuses records, ignores boundary controls, permits sponsor or provider capture, or allows public authority, finance, certification, procurement, recognition, or public warning confusion to persist.
134.3 Duty to Advance Public-Benefit Purpose. Each officer shall exercise authority in furtherance of the Corporation’s lawful public-benefit purposes. Those purposes include research, education, evidence integrity, methods stewardship, observability, ontology, semantic interoperability, technical truth, public-good R&D, public-good software, open technical baselines, public authority learning, community safeguards, public-safe publication, data / AI / cyber governance, and responsible Nexus public-good stack compatibility.
An officer shall not treat institutional scale, revenue, sponsorship, public attention, technical adoption, repository usage, public authority participation, provider engagement, grant opportunity, media opportunity, or Nexus visibility as superior to public-benefit purpose. Public-benefit purpose shall control over convenience, speed, commercial pressure, sponsor preference, provider preference, publicity, political advantage, public authority pressure, capital-reader interest, or enterprise-stack opportunity.
Each officer shall preserve public-benefit discipline by ensuring that the officer’s actions are:
a) purpose-aligned;
b) legally authorized;
c) record-supported;
d) non-executing;
e) public-safe where externally communicated;
f) compatible with safeguards;
g) compatible with data / AI / cyber controls;
h) free from impermissible private benefit; and
i) correctionable.
134.4 Duty to Preserve Nonprofit Character. Each officer shall preserve the Corporation’s nonprofit, non-share, non-stock where applicable, non-distributing, public-benefit character. No officer shall manage the Corporation as a profit-distributing enterprise, private benefit vehicle, sponsor-controlled platform, provider-controlled channel, investment product, commercial delivery company, national company, Project SPV, fund, broker, lender, insurer, rating agency, procurement body, certification body, public authority, emergency command body, or enterprise execution vehicle.
Officers shall ensure that revenues, grants, donations, sponsorships, subscriptions, fees, cost recoveries, in-kind contributions, intellectual property, software assets, data assets, repositories, technical baselines, publications, and public-good assets are used only for lawful purposes consistent with the Corporation’s governing instruments.
An officer shall escalate any proposed activity, agreement, benefit, pricing structure, sponsorship package, provider interface, grant condition, restricted fund, licensing arrangement, service offering, or public claim that may create nonprofit-status risk, unrelated business risk, private benefit risk, inurement risk, tax risk, charitable solicitation risk, or mission drift.
134.5 Duty to Prevent Private Inurement and Impermissible Private Benefit. Each officer shall avoid, prevent, disclose, and escalate private inurement, excess benefit, impermissible private benefit, self-dealing, improper related-party advantage, disguised compensation, sponsor control, donor control, funder control, provider preference, host control, public authority access sale, research finding purchase, publication suppression right, recognition purchase, finance-readiness purchase, certification purchase, procurement advantage, or enterprise-stack advantage.
Officers shall not use the Corporation’s funds, records, data, AI systems, repositories, rooms, publications, public-good software, technical baselines, marks, staff, fellows, volunteers, public authority interfaces, Nexus interfaces, or public trust to benefit themselves or another private person except through lawful, fair, reasonable, documented, purpose-aligned, and approved arrangements.
Private benefit review shall be required where an officer action involves:
a) compensation, reimbursement, benefits, consulting, contractor, fellowship, stipend, scholarship, award, travel, or event support;
b) related-party transaction;
c) grant, donation, sponsorship, restricted fund, or in-kind contribution;
d) provider, vendor, contractor, host, sponsor, donor, or funder arrangement;
e) intellectual property, licensing, repository, software, data, technical asset, or publication benefit;
f) public authority interface, controlled-room access, data-room access, or public-safe publication access; or
g) any arrangement that may confer special visibility, access, influence, preference, recognition, or commercial advantage.
No officer shall approve a transaction from which the officer or a related party may benefit unless all conflict, recusal, independent review, approval, reasonableness, tax, records, and disclosure requirements are satisfied.
134.6 Duty to Preserve Tax-Exempt or Tax-Exempt-Compatible Status. Each officer shall act in a manner compatible with the Corporation’s current or intended federal tax classification, state tax posture, charitable solicitation posture, nonprofit status, public-benefit purpose, and any tax-exempt or tax-exempt-compatible commitments adopted by the Board.
Officers shall not represent that the Corporation is recognized as a charity, exempt organization, supporting organization, fiscal sponsor, sponsored project, Section 501(c)(3) organization, Section 501(c)(4) organization, Section 501(c)(6) organization, public charity, private foundation, or other tax-status category unless that status has been lawfully obtained or adopted and recorded.
Officers shall preserve tax discipline by ensuring appropriate review of:
a) donations, grants, sponsorships, subscriptions, fees, cost recovery, program revenue, licensing revenue, data access fees, academy fees, fellowship support, challenge prizes, and public-good support;
b) donor acknowledgments, sponsorship benefits, restricted funds, donor-advised or funder-directed restrictions, naming benefits, public acknowledgments, and in-kind contributions;
c) lobbying, political activity, public authority engagement, government ethics, gifts, procurement integrity, and grant compliance where applicable;
d) private benefit, inurement, excess benefit, unrelated business income, charitable solicitation, sales tax, state tax, and cross-border tax implications; and
e) public representations of tax status.
Where a tax-status risk exists, the officer shall hold, restrict, re-scope, refer for review, or decline the activity pending competent review.
134.7 Duty to Preserve Non-Execution. Each officer shall preserve the Corporation’s bright-line non-execution character. The Corporation’s role is to steward evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, public authority learning, and public-safe technical support; it is not to execute regulated, commercial, sovereign, emergency, finance, procurement, certification, recognition, or enterprise-stack functions.
No officer shall cause or permit the Corporation to act as:
a) emergency command body, incident command body, dispatcher, evacuation authority, public warning authority, public health order issuer, public safety agency, or infrastructure operator;
b) regulator, permit issuer, compliance approver, procurement body, vendor selector, certification body, accreditation body, recognition body, maturity body, public authority decision-maker, or legal compliance authority;
c) securities issuer, broker, dealer, finder, investment adviser, capital placer, underwriter, asset manager, bank, lender, insurer, insurance intermediary, rating agency, public finance approver, guarantor, escrow agent, or fiduciary for third-party capital;
d) national company, state operating company, regional company, Project SPV, qualified enterprise provider, asset owner, deployment company, commercial operator, managed service provider, or enterprise delivery vehicle; or
e) standards monopoly or protocol authority unless a separate lawful instrument expressly creates and records such authority within lawful limits.
Officers shall ensure that dashboards, proof receipts, AI outputs, digital twins, DePIN records, DLT or blockchain entries, AI-RAN signals, O-RAN signals, sensor outputs, observability signals, controlled-room outputs, public-safe reports, and technical baselines are not treated as execution authority.
134.8 Duty to Preserve GCRI / GRF / GRA Role Separation. Each officer shall preserve the separation among the GCRI function, The Global Risks Forum (GRF), and The Global Risks Alliance (GRA). Officers shall maintain GCRI US as a United States and North America evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, and open technical baseline steward.
Officers shall not represent that GCRI US performs or controls:
a) The Global Risks Forum (GRF) functions, including public-good registry, recognition, maturity-records, standing, claims-discipline, stakeholder-formation, public-safe reporting, or public-facing legitimacy determinations;
b) The Global Risks Alliance (GRA) functions, including finance-readiness, capital-readability, proof-pack stewardship, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, capital-reader rooms, or regulated-perimeter discipline determinations; or
c) Nexus Standards or protocol authority functions unless separately and lawfully constituted and recorded.
GCRI US may provide evidence, methods, technical baselines, correction signals, observability inputs, ontology support, and technical records to GRF, GRA, Nexus Standards, and Nexus interfaces where authorized. Such support shall remain support and shall not become recognition, finance-readiness, certification, procurement approval, standards adoption, or enterprise execution.
134.9 Duty to Preserve Public-Good Stack and Enterprise Stack Separation. Each officer shall preserve the separation between the Nexus public-good stack and the enterprise stack. Public-good stack functions include evidence, methods, observability, ontology, records, public-safe reporting, controlled vocabulary, learning, safeguards, public-good software, open technical baselines, standards support, public authority learning, and correctionability. Enterprise stack functions include commercial deployment, project ownership, provider delivery, capital execution, infrastructure operation, asset ownership, procurement delivery, national company operations, and Project SPV execution.
Officers shall not collapse these stacks by:
a) using public-good records to select, prefer, certify, or endorse enterprise providers;
b) using technical baselines to create procurement mandates or commercial exclusivity;
c) using public authority rooms to channel business opportunities to providers;
d) using sponsor support to influence evidence, methods, publications, standards support, recognition inputs, or finance-readiness inputs;
e) using GCRI US outputs as investment, insurance, lending, procurement, rating, or certification tools;
f) allowing national companies, Project SPVs, providers, sponsors, hosts, investors, insurers, lenders, or enterprise actors to control public-good records, claims, or outputs; or
g) treating GCRI US participation as enterprise authorization.
Where public-good and enterprise-stack actors must interface, officers shall use written terms, controlled vocabulary, public-safe notices, authority matrices, conflict controls, provider-neutrality controls, sponsor non-control controls, records discipline, and correction pathways.
134.10 Duty to Preserve United States Legal Separateness. Each officer shall preserve the Corporation’s separate United States legal personality. The Corporation shall be administered as a distinct legal entity with its own governance, records, funds, contracts, officers, authorities, liabilities, repositories, filings, tax records, insurance, and public representations.
Officers shall not create confusion between GCRI US and any founder, director, officer, employee, contractor, member, donor, sponsor, provider, host, public authority, university, laboratory, community, GCRI Canada, other GCRI entity, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, Nexus Network, consortium, national company, Project SPV, or enterprise actor.
United States legal separateness shall be preserved through:
a) correct legal name use;
b) separate contracting;
c) separate bank accounts and accounting;
d) separate Board and officer records;
e) separate minute books and registers;
f) separate tax and state filings;
g) separate insurance records;
h) separate repository and data access controls where required;
i) separate public descriptions;
j) separate authority matrices; and
k) correction of misleading statements.
No officer shall permit shared mission, shared personnel, shared data, shared records, shared software, shared public events, shared publications, shared repositories, shared councils, shared funders, or shared Nexus interfaces to create legal fusion, alter ego status, common treasury, agency, partnership, joint venture, joint employer, single employer, or shared liability unless a separate lawful instrument expressly creates and records the relationship.
134.11 Duty to Preserve Separateness From GCRI Canada and Other GCRI Entities. Each officer shall preserve separateness between GCRI US, GCRI Canada, and any other national, regional, or global GCRI entity. Coordination, compatibility, shared doctrine, shared ontology, shared methods, shared technical baselines, shared public-good software, shared public-safe reports, cross-border evidence architecture, North America alignment, or shared Nexus interface shall not create merger, branch status, parent-subsidiary status, alter ego status, agency, partnership, joint venture, common treasury, shared liability, single employer, or automatic mutual authority.
Officers shall ensure that cross-border coordination with GCRI Canada or other GCRI entities is governed by appropriate records, which may include:
a) MoUs;
b) interface agreements;
c) compatibility notes;
d) divergence logs;
e) cross-border data transfer records;
f) public authority capacity records;
g) IP and licensing records;
h) shared publication records;
i) repository access records;
j) public-safe description controls; and
k) correction pathways.
An officer acting in a dual role shall identify the capacity in which the officer is acting, avoid using one role to bind another entity, disclose conflicts, observe recusal requirements, and preserve records sufficient to prevent role confusion.
134.12 Duty to Preserve Public Authority Boundaries. Each officer shall preserve the Corporation’s public authority boundary. The Corporation may support public authority learning, evidence literacy, technical literacy, public-safe reporting literacy, observability methods, scenario sessions, simulations, tabletops, after-action learning, public authority rooms, regulator-listening participation, public finance reader participation, emergency-management participant participation, and public infrastructure operator participation. It shall not act as a public authority unless lawfully constituted as such by competent law and recorded authority.
Officers shall not represent that the Corporation may:
a) make public authority decisions;
b) issue regulations, permits, approvals, compliance findings, or enforcement actions;
c) issue public warnings, emergency commands, evacuation instructions, public health orders, dispatches, incident commands, or safety commands;
d) approve procurement, public funding, public finance, grants, tax credits, appropriations, or sovereign obligations;
e) bind public authorities through participation;
f) create official adoption through attendance, data contribution, public authority room participation, or dashboard access;
g) act as a public-private partnership unless a competent instrument creates and records such relationship; or
h) substitute for a regulator, public safety agency, emergency-management agency, public health authority, utility regulator, procurement body, public finance body, or infrastructure operator.
Officers shall use capacity classifications, public-safe notices, official-capacity records, observer records, regulator-listening records, public finance reader records, emergency-management participant records, public authority reference review, and correction pathways to prevent public authority confusion.
134.13 Duty to Preserve Finance, Securities, Insurance, Lending, Rating, Public Finance, Procurement, Certification, and Professional Boundaries. Each officer shall preserve all regulated and professional boundaries applicable to the Corporation. No officer shall permit the Corporation to provide or imply securities offerings, securities solicitation, broker-dealer activity, finder activity, capital placement, underwriting, investment advice, investment suitability, portfolio management, banking, lending, credit approval, credit brokerage, guarantee, insurance placement, insurance underwriting, insurance pricing, claims handling, rating, credit opinion, bankability determination, insurability determination, resilience rating, public finance approval, tax credit approval, sovereign finance approval, procurement approval, vendor selection, certification, accreditation, professional advice, or legal compliance approval unless separately and lawfully authorized and recorded.
Officers may support evidence, methods, technical baselines, public-good learning, proof-pack inputs, public authority literacy, GRA-facing technical inputs, GRF-facing evidence inputs, Docket support, Grid support, and capital-reader literacy only within non-execution boundaries and with limitation language.
Where finance-adjacent, insurance-adjacent, procurement-adjacent, certification-adjacent, recognition-adjacent, or professional-boundary risk arises, the officer shall:
a) stop or hold the activity where needed;
b) escalate to the appropriate officer, committee, counsel, compliance function, or Board;
c) re-scope language and function;
d) add or revise public-safe notices;
e) restrict access;
f) externalize to a competent licensed or authorized actor where appropriate;
g) correct misleading records or statements; and
h) preserve records of review.
134.14 Duty to Preserve Provider Neutrality and Sponsor Non-Control. Each officer shall preserve provider neutrality and sponsor non-control. The Corporation may receive lawful support, sponsorship, donations, grants, in-kind contributions, technical contributions, provider participation, host support, and enterprise actor participation only where such participation does not control, distort, suppress, purchase, or predetermine the Corporation’s governance, evidence, methods, research, publications, technical baselines, public-safe claims, public authority learning, GRF-facing inputs, GRA-facing inputs, Nexus interface records, or corrections.
Officers shall not grant, imply, or permit:
a) preferred provider status;
b) required provider status;
c) procurement advantage;
d) certification advantage;
e) recognition advantage;
f) finance-readiness advantage;
g) public authority access purchase;
h) publication veto;
i) research finding purchase;
j) standards outcome purchase;
k) Docket or Grid outcome purchase;
l) Nexus-compatible status purchase;
m) data access advantage outside lawful controls;
n) public-good software influence inconsistent with governance; or
o) sponsor naming or benefit rights that create control.
All sponsor, donor, funder, provider, host, contractor, vendor, and enterprise relationships shall be reviewed, documented, bounded, disclosed where appropriate, and correctionable.
134.15 Duty to Preserve Data / AI / Cyber / Privacy Controls. Each officer shall comply with and preserve data governance, AI governance, cybersecurity, privacy, secure compute, identity, access, logging, monitoring, model register, inference record, compute workload record, repository, secure release, incident response, business continuity, disaster recovery, and public-safe data publication controls.
Officers shall not:
a) access data without authorization;
b) disclose data without authority;
c) upload controlled, confidential, personal, public authority, cyber-sensitive, infrastructure-sensitive, health-sensitive, community-protected, Tribal, Indigenous, local, territorial, or protected knowledge materials to unapproved systems;
d) use unapproved AI systems for controlled materials;
e) bypass model registers, inference records, or compute workload records where required;
f) use agentic AI without controls;
g) release datasets, dashboards, maps, code, models, benchmarks, evaluation sets, APIs, SDKs, or technical baselines without required review;
h) ignore vulnerabilities, incidents, credential compromise, key compromise, repository compromise, or data breach indicators;
i) use shadow IT or side-channel storage for official records; or
j) treat AI outputs, automated scores, dashboards, proof receipts, digital twins, DePIN records, ledger entries, sensor signals, AI-RAN signals, or O-RAN signals as institutional authority without human review and competent record.
Officers shall escalate data / AI / cyber / privacy risks promptly and support containment, legal hold, forensic review, access revocation, publication freeze, correction, notification where required, and secure disposal where appropriate.
134.16 Duty to Preserve Research Integrity, Evidence Integrity, Methods Integrity, and Technical Truth Integrity. Each officer shall preserve research integrity, evidence integrity, methods integrity, observability integrity, ontology integrity, technical truth integrity, verifiable compute integrity, public-good software integrity, open technical baseline integrity, and public-safe publication integrity.
Officers shall ensure that institutional outputs are supported by appropriate records, including where relevant:
a) source lineage;
b) provenance;
c) custody;
d) method version;
e) confidence statement;
f) uncertainty note;
g) assumptions;
h) limitations;
i) validation or verification status;
j) peer review or technical review status;
k) conflict and sponsor disclosure;
l) public-safe classification;
m) correction pathway;
n) supersession status; and
o) archive status.
No officer shall manipulate, suppress, exaggerate, cherry-pick, fabricate, backdate, misclassify, or overstate evidence, methods, observability signals, public-good software, benchmarks, model outputs, technical baselines, reports, proof receipts, Docket support, Grid support, GRF-facing inputs, GRA-facing inputs, or Nexus interface records.
Technical truth shall be understood as disciplined, record-supported, uncertainty-aware, public-safe, and correctionable technical integrity, not as oracle status, public authority decision, public warning, recognition, finance-readiness, certification, procurement approval, rating, or operational command.
134.17 Duty to Preserve Civil Rights, Accessibility, Community Safeguards, Tribal / Indigenous Protocols, and Protected Knowledge. Each officer shall respect and preserve civil rights, non-discrimination, accessibility, inclusive participation, Tribal sovereignty respect, Indigenous governance respect, Indigenous data safeguards, protected knowledge safeguards, local and territorial knowledge safeguards, public-safe mapping, vulnerable and remote community safeguards, consent and non-consent pathways, attribution, withdrawal, restriction, correction, grievance, remedy, protected participation, whistleblowing, dissent protection, and non-retaliation.
Officers shall not extract, disclose, commercialize, map, publish, train AI systems on, translate, repackage, benchmark, tokenize, index, dashboard, or otherwise use community-protected, Indigenous, local, territorial, cultural, environmental, or protected knowledge in a manner inconsistent with law, consent, non-consent, protocol, safeguards, public-safe classification, or recorded authority.
Where safeguards risk arises, officers shall support:
a) pause or stop-the-line action;
b) publication hold;
c) access restriction;
d) map blurring, aggregation, redaction, or withdrawal;
e) community, Tribal, Indigenous, local, territorial, accessibility, civil rights, or protected knowledge review;
f) grievance and remedy handling;
g) public-safe correction;
h) non-retaliation protections; and
i) Board or committee escalation where material.
Safeguards shall be substantive conditions of officer authority and not optional consultation.
134.18 Duty to Maintain Records. Each officer shall maintain complete, accurate, timely, accessible, secure, versioned, retention-compliant, and correctionable records of the officer’s actions, approvals, refusals, delegations, conflicts, recusals, reports, expenditures, contracts, publications, data access, AI use, public authority references, repository actions, controlled-room actions, incidents, escalations, corrections, supersessions, withdrawals, retractions, takedowns, and closeouts.
Officer records shall identify, as applicable:
a) authority relied upon;
b) decision made;
c) date and time;
d) responsible owner;
e) approver;
f) consulted persons;
g) conflicts and recusals;
h) materials reviewed;
i) budget or contract authority;
j) data / AI / cyber classification;
k) public authority capacity classification;
l) finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control boundary review;
m) safeguards review;
n) public-safe notice language;
o) repository location;
p) access class;
q) publication class;
r) retention class;
s) legal hold status; and
t) correction pathway.
No officer shall maintain shadow records, private archives, unapproved repositories, unofficial AI transcripts, unapproved side-channel storage, or unrecorded decision paths for official corporate matters.
134.19 Duty to Escalate Risks, Conflicts, Incidents, and Boundary Concerns. Each officer shall promptly escalate material risks, conflicts, incidents, uncertainties, control weaknesses, authority defects, record defects, legal ambiguities, public authority concerns, finance-boundary concerns, certification-boundary concerns, procurement concerns, recognition concerns, provider-neutrality concerns, sponsor non-control concerns, data / AI / cyber incidents, privacy incidents, research integrity concerns, public-safe publication errors, safeguards concerns, protected knowledge issues, civil rights or accessibility concerns, competition issues, sanctions issues, export-control issues, controlled-technology issues, and Nexus role-separation concerns.
Escalation shall be made to the appropriate authority, which may include:
a) Board;
b) Chair;
c) President;
d) Executive Director or Chief Executive Officer;
e) Secretary;
f) Treasurer or Chief Financial Officer;
g) Chief Legal, Compliance, and Risk Officer;
h) Chief Data, AI, and Cyber Officer;
i) Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer;
j) relevant committee;
k) counsel;
l) compliance function;
m) auditor or financial reviewer where appropriate;
n) public authority where notice is legally required; or
o) funder, insurer, grantor, or other body where legally or contractually required.
Escalation shall not be delayed because the matter is reputationally inconvenient, sponsor-sensitive, provider-sensitive, technically complex, politically sensitive, funder-sensitive, public authority-sensitive, or likely to require correction.
134.20 Duty to Support Correctionability. Each officer shall support correctionability as a continuous duty. Correctionability requires that institutional records, publications, datasets, software, dashboards, maps, technical baselines, evidence packs, proof receipts, method notes, public authority learning materials, public-safe reports, GRF-facing inputs, GRA-facing inputs, Nexus interface records, and public claims remain open to challenge, review, correction, supersession, withdrawal, retraction, takedown, clarification, archive, and public-safe notice where appropriate.
No officer shall suppress, punish, ignore, delay, conceal, or minimize a correction request, evidence challenge, method challenge, safeguards complaint, public authority confusion report, finance overclaim report, certification overclaim report, procurement overclaim report, recognition overclaim report, data / AI / cyber incident report, protected knowledge concern, or public-safe publication error.
Officers shall support correction by:
a) preserving source records;
b) maintaining version control;
c) marking draft, provisional, superseded, withdrawn, retracted, archived, disputed, stale, restricted, or corrected status;
d) notifying affected persons or bodies where required;
e) issuing public or controlled corrections where appropriate;
f) updating registers, repositories, dashboards, datasets, models, software, and publications;
g) recording the basis and authority for correction;
h) preventing continued reliance on superseded materials; and
i) learning from errors through policy, method, training, technical, or governance improvement.
Correction shall not be treated as reputational failure; it shall be treated as an institutional safeguard.
134.21 Officer Duty Records. The Corporation shall maintain Officer Duty Records sufficient to demonstrate that officers have understood, accepted, performed, breached, corrected, or been held accountable for their duties.
Officer Duty Records shall include, as applicable:
a) duty acknowledgments;
b) role descriptions;
c) appointment records;
d) authority matrix entries;
e) training records;
f) certifications of understanding;
g) conflict disclosures;
h) recusal records;
i) confidentiality acknowledgments;
j) data / AI / cyber access records;
k) public authority boundary acknowledgments;
l) finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control boundary acknowledgments;
m) safeguards acknowledgments;
n) public-safe publication acknowledgments;
o) reports to the Board or committees;
p) risk escalations;
q) incident reports;
r) correction records;
s) performance evaluations;
t) corrective training;
u) delegation restrictions;
v) access restrictions;
w) warnings;
x) suspensions;
y) removals;
z) resignation and closeout records; and
aa) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that every officer is a bounded steward of delegated institutional responsibility. Officer duties are not ceremonial, title-based, sponsor-facing, provider-facing, public-authority-facing, finance-facing, or convenience-based. They are enforceable public-benefit obligations designed to preserve lawful authority, nonprofit character, non-execution, role separation, records discipline, public-safe operation, technical integrity, safeguards, and correctionability.
Section 135. Chair of the Board
135.1 Chair Role. The Chair of the Board shall serve as the principal governance leadership officer of the Board, subject at all times to applicable law, the Articles or Certificate, this Bylaw, Board resolutions, Board-approved policies, the authority matrix, conflict controls, records requirements, and any limitations imposed by the Board. The Chair’s office exists to strengthen fiduciary governance, Board discipline, continuity, agenda integrity, director engagement, mission-lock protection, public-benefit stewardship, and lawful oversight of the Corporation’s non-executing public-good technical institution role.
The Chair shall not be treated as the owner, controller, executive substitute, founder-proxy, sponsor-facing authority, provider-facing authority, public authority, finance-readiness authority, certification authority, recognition authority, standards authority, procurement authority, emergency command authority, or enterprise execution authority of the Corporation. The Chair’s authority is governance authority only, except to the extent that the Board expressly and lawfully delegates additional authority by competent record.
The Chair shall preserve the distinction between:
a) Board governance and executive management;
b) fiduciary oversight and operational implementation;
c) public-good stewardship and enterprise execution;
d) evidence and recognition;
e) technical inputs and finance-readiness determinations;
f) public authority learning and public authority action;
g) technical baselines and certification or procurement authority; and
h) leadership facilitation and unilateral institutional control.
135.2 Board Leadership. The Chair shall provide leadership to the Board as a collective governing body. The Chair shall support the Board in exercising informed, careful, independent, public-benefit-oriented, conflict-managed, record-supported, and correctionable judgment.
The Chair’s Board leadership responsibilities may include:
a) promoting effective Director participation;
b) ensuring that Directors receive appropriate information before decisions;
c) supporting a culture of disciplined inquiry, dissent protection, independent judgment, and fiduciary seriousness;
d) ensuring that Board deliberations address material legal, tax, nonprofit, public-benefit, financial, operational, public authority, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, sponsor non-control, data / AI / cyber, safeguards, research integrity, and Nexus interface issues;
e) ensuring that Board decisions are properly noticed, deliberated, approved, recorded, implemented, monitored, and corrected where needed;
f) supporting alignment between Board committees, officers, councils, and advisory bodies; and
g) preserving the Board’s role as the highest internal governing authority subject to law, the Articles or Certificate, this Bylaw, and member approval where required.
The Chair shall not use Board leadership to dominate the Board, suppress dissent, prevent lawful access to information, exclude Directors from material deliberations, steer decisions for private advantage, or convert facilitative leadership into personal authority.
135.3 Governance Agenda Leadership. The Chair shall support the preparation of Board agendas in coordination with the Secretary, President, Executive Director or Chief Executive Officer where appointed, relevant officers, committee chairs, counsel, compliance function, and other authorized persons. The Chair shall ensure that agenda-setting remains a governance function and not a mechanism for suppressing oversight, avoiding difficult matters, privileging sponsors or providers, delaying corrections, or concealing boundary issues.
Board agendas should identify, as applicable:
a) items requiring Board decision;
b) reserved matters;
c) consent items;
d) informational items;
e) risk items;
f) compliance items;
g) financial and budget items;
h) public authority interface items;
i) finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control boundary items;
j) data / AI / cyber / privacy items;
k) safeguards, civil rights, accessibility, Tribal / Indigenous, protected knowledge, and public-safe publication items;
l) Nexus, GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, and enterprise-stack interface items;
m) correction, supersession, withdrawal, retraction, takedown, and archive items; and
n) executive session or privileged items.
The Chair shall ensure that urgent matters are not omitted merely because they are inconvenient, reputationally sensitive, sponsor-sensitive, provider-sensitive, public authority-sensitive, technically complex, legally ambiguous, or financially significant.
135.4 Fiduciary Discipline. The Chair shall support fiduciary discipline by helping the Board act with care, loyalty, obedience to mission and law where applicable, prudence, diligence, good faith, independence, and public-benefit accountability. The Chair shall ensure that the Board has a reasonable opportunity to understand the facts, alternatives, risks, constraints, authority limits, conflicts, and records needed for decision-making.
The Chair shall support fiduciary discipline by ensuring that Board processes include:
a) adequate notice and materials;
b) meaningful deliberation;
c) conflict disclosure and recusal;
d) independent review where required;
e) counsel, tax, compliance, financial, technical, safeguards, or public authority review where appropriate;
f) risk and boundary notes for material decisions;
g) clear voting records;
h) action items and responsible owners;
i) follow-up reporting; and
j) correction pathways.
No Chair action, agenda structure, time pressure, committee report, officer recommendation, sponsor request, provider request, public authority request, or technical urgency shall excuse the Board from exercising fiduciary judgment.
135.5 Mission-Lock Protection. The Chair shall support the Board’s duty to protect the Corporation’s mission lock. The Corporation’s mission lock requires preservation of its lawful 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, verifiable compute, public authority learning, community safeguards, validity-by-record, and correctionability purposes.
The Chair shall cause mission-lock concerns to be brought to the Board where a matter may involve:
a) expansion beyond the Articles or Certificate;
b) drift into enterprise execution;
c) drift into GRF recognition functions;
d) drift into GRA finance-readiness functions;
e) drift into Nexus Standards or protocol authority without lawful designation;
f) public authority confusion;
g) regulated finance, securities, insurance, lending, rating, public finance, procurement, certification, or professional-boundary risk;
h) sponsor, donor, funder, provider, host, or enterprise actor capture;
i) private inurement or impermissible private benefit;
j) misuse of public-good software, technical baselines, proof receipts, dashboards, AI outputs, or Nexus-compatible claims; or
k) weakening of data / AI / cyber controls, research integrity, public-safe publication, civil rights, accessibility, Tribal / Indigenous protocols, community safeguards, or protected knowledge safeguards.
The Chair shall not allow mission language to be used as a general license for prohibited functions.
135.6 Public-Benefit Purpose Protection. The Chair shall support protection of the Corporation’s public-benefit purpose in Board deliberations, officer oversight, committee coordination, external relationships, and public descriptions. The Chair shall ensure that the Board considers whether material actions advance the Corporation’s public-benefit purposes and whether the proposed action is lawful, proportionate, record-supported, public-safe, non-executing, and compatible with safeguards.
The Chair shall treat public benefit as a substantive governance condition, not a branding statement. Public-benefit purpose shall be tested against:
a) lawful authority;
b) nonprofit compatibility;
c) tax-exempt or tax-exempt-compatible discipline;
d) public-good value;
e) evidence and research integrity;
f) community and civil rights impact;
g) accessibility;
h) Tribal and Indigenous protocol respect;
i) protected knowledge risk;
j) public authority boundary integrity;
k) finance, certification, procurement, recognition, and enterprise boundary integrity;
l) provider neutrality and sponsor non-control; and
m) correctionability.
Where a public-benefit concern is material, the Chair shall ensure escalation to the Board, an appropriate committee, counsel, compliance function, safeguards function, or other competent reviewer.
135.7 Non-Execution Protection. The Chair shall support the Board’s duty to preserve the Corporation’s non-execution perimeter. The Chair shall ensure that Board agendas, minutes, resolutions, public statements, officer delegations, committee charters, program approvals, sponsorship materials, provider materials, public authority interfaces, technical baselines, public-good software releases, dashboards, proof receipts, and Nexus interface records do not convert the Corporation into an executing body.
The Chair shall ensure Board attention to any proposal that could be understood as:
a) emergency command;
b) public warning;
c) public authority decision;
d) regulatory approval;
e) procurement approval;
f) certification or accreditation;
g) recognition, standing, maturity, Docket approval, Grid guarantee, or Nexus-compatible public status determination;
h) finance-readiness, insurance-readiness, bankability, capital-readability, investment suitability, rating, or public finance approval;
i) provider selection or preferred provider status;
j) sponsor control or outcome purchase;
k) national company, Project SPV, asset owner, operator, managed service provider, or enterprise delivery role; or
l) execution by AI system, dashboard, digital twin, DLT record, DePIN signal, AI-RAN signal, sensor signal, proof receipt, data room, controlled room, or workflow integration.
Where non-execution risk exists, the Chair shall cause the matter to be held, re-scoped, clarified, routed for review, or escalated.
135.8 Role-Separation Protection. The Chair shall support protection of the Corporation’s role separation 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 providers, sponsors, hosts, funders, public authorities, universities, laboratories, communities, and enterprise-stack actors.
The Chair shall ensure that Board materials and public descriptions distinguish:
a) GCRI US as evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, and open technical baseline steward;
b) 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;
c) The Global Risks Alliance (GRA) as finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, and regulated-perimeter discipline steward;
d) Nexus Standards and protocol authority functions as separate unless lawfully conferred;
e) public authorities as sovereign or governmental actors acting only through their own lawful authority; and
f) enterprise-stack actors as separate execution, provider, finance, ownership, delivery, or operational actors.
The Chair shall require correction where role separation is blurred in minutes, contracts, MoUs, websites, proposals, grant submissions, sponsor decks, provider materials, public authority materials, repository entries, dashboards, AI summaries, or public statements.
135.9 Board Meeting Leadership. The Chair shall preside at Board meetings unless absent, unavailable, conflicted, recused, incapacitated, or otherwise unable to act, in which case the Vice-Chair or another person authorized by law, the Articles or Certificate, this Bylaw, or Board record may preside.
In leading Board meetings, the Chair shall support:
a) quorum confirmation;
b) notice confirmation;
c) agenda discipline;
d) conflict disclosure;
e) recusal implementation;
f) orderly deliberation;
g) inclusion of relevant Director questions and minority views;
h) protection of privileged, confidential, cyber-sensitive, infrastructure-sensitive, public authority, finance-sensitive, personal, community-protected, Tribal, Indigenous, local, territorial, and protected knowledge materials;
i) competition and antitrust discipline;
j) public authority boundary discipline;
k) finance, certification, procurement, recognition, provider-neutrality, sponsor non-control, and public warning boundary discipline;
l) clear voting and action-item records; and
m) meeting closeout with responsible owners and follow-up requirements.
The Chair may interrupt, pause, recess, restrict, or refer a meeting discussion where it threatens confidentiality, privilege, public authority boundaries, regulated finance boundaries, competition law, safeguards, protected knowledge, data / AI / cyber controls, or lawful governance discipline.
135.10 Board Evaluation Leadership. The Chair shall support Board evaluation, Director development, committee evaluation, governance maturity review, succession planning, skills-matrix review, independence review, conflict review, and training completion. The Chair may coordinate with the Governance, Nominating, Ethics, and Board Renewal Committee or equivalent body where established.
Board evaluation leadership may include:
a) annual Board self-assessment;
b) Director attendance review;
c) Director preparation and participation review;
d) skills and competency gap review;
e) independence and anti-capture review;
f) conflict and recusal process review;
g) committee performance review;
h) Board materials and meeting quality review;
i) fiduciary training review;
j) Nexus role-separation training review;
k) non-execution and public authority boundary training review;
l) finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control training review;
m) data / AI / cyber, research integrity, safeguards, civil rights, accessibility, Tribal / Indigenous, and protected knowledge training review; and
n) corrective governance improvement.
The Chair shall not use evaluation to punish lawful dissent, suppress minority views, entrench personal control, favor sponsors or providers, or exclude Directors for improper reasons.
135.11 Director Engagement and Succession Support. The Chair shall support Director engagement and Board succession. The Chair shall encourage Directors to participate meaningfully, review materials, disclose conflicts, attend meetings, complete required training, support correctionability, and preserve confidentiality and records discipline.
Director engagement and succession support may include:
a) onboarding support;
b) continuing education support;
c) pairing Directors with relevant committees where appropriate;
d) encouraging Directors to raise governance-significant matters;
e) supporting orderly transition of committee leadership;
f) supporting Chair and Vice-Chair succession planning;
g) supporting emergency Board continuity plans;
h) identifying skills, geographic, state, territorial, Tribal, public authority, technical, safeguards, finance-boundary, and public-interest perspective gaps;
i) supporting recruitment processes consistent with independence and anti-capture controls; and
j) ensuring handover of knowledge, records, duties, and access controls at the end of service.
No Director engagement or succession practice shall create founder entitlement, sponsor entitlement, provider entitlement, public authority entitlement, donor entitlement, funder entitlement, or factional control of Board composition.
135.12 Emergency Board Convening Authority. The Chair may convene, support the convening of, or request the convening of an emergency Board meeting where permitted by law, the Articles or Certificate, this Bylaw, Board policy, or Board resolution. Emergency Board convening authority shall be used to protect lawful governance and public-benefit mission where delay could materially harm the Corporation, its records, public trust, legal status, assets, systems, public-safe outputs, participants, communities, protected knowledge, or Nexus role separation.
Emergency Board convening may be appropriate for:
a) cybersecurity incident;
b) data breach;
c) AI incident;
d) public-safe publication error;
e) public authority confusion;
f) emergency command or public warning overclaim;
g) finance, securities, insurance, lending, rating, public finance, procurement, certification, recognition, provider-preference, or sponsor-control overclaim;
h) protected knowledge breach;
i) civil rights, accessibility, community harm, Tribal or Indigenous protocol breach, or safeguards concern;
j) material legal deadline;
k) regulatory-perimeter uncertainty;
l) repository, software release, key, token, credential, technical asset, controlled technology, or infrastructure compromise;
m) officer incapacity, vacancy, misconduct, or boundary breach;
n) material sponsor, provider, donor, funder, host, or enterprise capture risk; or
o) other material risk requiring Board attention.
Emergency convening shall not authorize the Chair to exercise prohibited functions, bypass mandatory approvals, or permanently alter governance arrangements without proper Board action.
135.13 Interface With President, Executive Director, or Chief Executive Officer. The Chair shall serve as a governance interface with the President, Executive Director, Chief Executive Officer, or other principal executive officer where appointed. This interface shall support Board oversight, officer accountability, strategy implementation reporting, escalation, and alignment with Board-approved purposes and controls.
The Chair may request reports, status updates, risk escalations, Board materials, compliance summaries, budget updates, incident updates, correction updates, public authority interface summaries, sponsor and provider relationship summaries, Nexus interface summaries, and other information needed for Board governance.
The Chair shall not use the interface with executive leadership to:
a) micromanage daily operations without delegation;
b) issue unilateral executive instructions outside authority;
c) bypass the Board;
d) privately approve reserved matters;
e) suppress officer escalation to the Board;
f) direct evidence, methods, research conclusions, public-safe publication outcomes, public authority references, finance-boundary outputs, certification-boundary outputs, or provider outcomes for improper purposes;
g) create hidden governance outside minutes and records; or
h) substitute personal authority for Board-approved strategy, budget, policy, and delegation.
The President, Executive Director, Chief Executive Officer, and other officers shall remain accountable to the Board according to the governing records.
135.14 Interface With Secretary. The Chair shall coordinate with the Secretary to support meeting notices, agendas, minutes, resolutions, written consents, Board records, action items, Board registers, governance calendars, repository entries, gazette or notice-stream entries, version control, and Board record integrity.
The Chair shall support the Secretary in ensuring that Board records accurately reflect:
a) meeting type;
b) notice;
c) attendance;
d) quorum;
e) materials reviewed;
f) conflicts disclosed;
g) recusals;
h) decisions;
i) votes;
j) abstentions;
k) dissent or minority notes where permitted;
l) action items;
m) responsible owners;
n) deadlines;
o) follow-up obligations;
p) corrections, supersessions, withdrawals, ratifications, or reservations; and
q) access, confidentiality, privilege, and publication classifications.
The Chair shall not direct the Secretary to alter, omit, backdate, misclassify, conceal, or distort Board records. Where the Chair disagrees with a record, the correction or clarification process shall be used.
135.15 Interface With Committee Chairs. The Chair may coordinate with committee chairs, council chairs, working group leads, panel chairs, and advisory body leads to support Board workflow, reporting, escalation, and committee effectiveness. Such coordination shall preserve each body’s charter, scope, records, confidentiality rules, conflict rules, and authority limits.
The Chair may request that committee chairs provide:
a) reports;
b) recommendations;
c) risk notes;
d) boundary notes;
e) conflict and recusal summaries;
f) minority views;
g) public authority boundary analysis;
h) finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control analysis;
i) data / AI / cyber notes;
j) safeguards and protected knowledge notes;
k) implementation status;
l) corrective action status; and
m) matters requiring Board review.
The Chair shall not use committee coordination to predetermine committee findings, suppress dissent, bypass the Board, inflate advisory views into approvals, convert technical review into certification, convert evidence review into recognition, convert finance-boundary support into finance-readiness, or convert public authority learning into public authority action.
135.16 No Sole Executive Authority Unless Separately Delegated. The Chair shall not have sole executive authority by virtue of being Chair. The Chair may not bind the Corporation, approve expenditures, sign contracts, hire or remove staff, approve grants, accept donations, accept sponsorships, approve publications, approve data access, approve AI use, approve software releases, approve controlled-room admissions, make public authority commitments, make public statements, or direct programs unless such authority is separately granted by law, the Articles or Certificate, this Bylaw, Board resolution, Board-approved delegation, authority matrix, or other competent record.
Any separate delegation to the Chair shall be:
a) written or otherwise recorded;
b) specific;
c) limited in scope;
d) limited in duration where appropriate;
e) subject to budget where applicable;
f) subject to conflict and recusal rules;
g) subject to records requirements;
h) subject to public authority, finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control boundaries;
i) subject to data / AI / cyber and safeguards controls; and
j) revocable.
The Chair shall not rely on custom, urgency, relationship, seniority, public expectation, funder expectation, sponsor expectation, provider expectation, public authority expectation, technical expectation, or founder expectation to exercise executive authority outside delegation.
135.17 No Authority to Override Board Reserved Matters. The Chair shall have no authority to override, approve, amend, waive, defer, ratify, conceal, or implement Board reserved matters except through lawful Board action or other competent authority expressly permitted by law and the governing instruments.
Without limiting the foregoing, the Chair shall not unilaterally approve:
a) amendment, restatement, repeal, or replacement of the Bylaw;
b) amendment of the Articles or Certificate;
c) change of legal name, state of incorporation, corporate form, registered office, registered agent, or principal governance seat where material;
d) tax-exempt status application, change, revocation, or structural shift;
e) mission-lock, public-benefit, nonprofit, non-distribution, or non-execution boundary change;
f) annual strategy, annual plan, annual budget, or material budget amendment;
g) major grants, donations, sponsorships, restricted funds, public-good support arrangements, or in-kind contributions;
h) major contracts, debt, leases, credit facilities, asset transfers, IP transfers, repository transfers, or technical asset dispositions;
i) appointment or removal of key officers where Board approval is required;
j) creation or dissolution of major committees, councils, programs, controlled rooms, or Nexus interfaces;
k) major policies or protocols affecting public authority, data / AI / cyber, privacy, research integrity, publication, safeguards, sponsorship, sanctions, export-control, competition, controlled technology, finance boundaries, certification boundaries, procurement boundaries, recognition boundaries, or provider neutrality;
l) litigation, investigation, settlement, regulatory engagement, or enforcement matter of material significance; or
m) dissolution, merger, consolidation, conversion, sale of substantially all assets, wind-up, or public-good asset distribution.
Any attempted Chair action inconsistent with this Section shall be subject to correction, non-recognition, Board review, and any other lawful remedy.
135.18 Chair Records. The Corporation shall maintain Chair Records sufficient to demonstrate the Chair’s appointment, term, eligibility, duties, authority, delegations, actions, recusals, reports, meeting leadership, emergency convening, Board coordination, committee interface, executive interface, corrections, and closeout.
Chair Records shall include, as applicable:
a) Chair appointment or election record;
b) term and renewal record;
c) eligibility and consent record;
d) duty acknowledgment;
e) authority matrix entry;
f) separate delegation records, if any;
g) Board meeting agendas supported by the Chair;
h) meeting leadership records;
i) emergency convening records;
j) Board evaluation and succession records supported by the Chair;
k) Director engagement records where appropriate;
l) committee interface records;
m) President, Executive Director, Chief Executive Officer, Secretary, Treasurer, counsel, compliance, safeguards, and officer interface records where governance-significant;
n) conflicts, recusals, abstentions, access restrictions, and independence review records;
o) public authority boundary, finance-boundary, certification-boundary, procurement-neutrality, recognition-boundary, provider-neutrality, sponsor non-control, data / AI / cyber, safeguards, and protected knowledge escalation records;
p) corrections, clarifications, supersessions, withdrawals, ratifications, or public-safe notices involving Chair action;
q) handover and closeout records; and
r) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that the Chair exists to make the Board more disciplined, informed, independent, public-benefit-oriented, and correctionable. The Chair shall lead governance but shall not become the Corporation’s unilateral executive, public authority, finance-readiness authority, recognition authority, certification authority, procurement authority, sponsor channel, provider channel, technical oracle, or enterprise execution point.
Section 136. Vice-Chair of the Board
136.1 Vice-Chair Role. The Vice-Chair of the Board shall serve as the secondary governance leadership officer of the Board and as the principal continuity support to the Chair, subject at all times to applicable law, the Articles or Certificate, this Bylaw, Board resolutions, Board-approved policies, the authority matrix, conflict controls, records requirements, and any limitations imposed by the Board.
The Vice-Chair’s office exists to preserve Board continuity, governance resilience, fiduciary discipline, meeting readiness, director engagement, succession support, emergency preparedness, and orderly Board function when the Chair is absent, unavailable, conflicted, recused, incapacitated, or otherwise unable to act.
The Vice-Chair shall not be treated as:
a) co-executive of the Corporation;
b) substitute President, Executive Director, Chief Executive Officer, Secretary, Treasurer, or Chief Financial Officer;
c) independent source of management authority;
d) public authority representative;
e) finance-readiness, certification, recognition, procurement, public warning, emergency command, provider-selection, sponsor-control, or enterprise execution authority;
f) owner or controller of Board process; or
g) holder of any authority not expressly granted by law, the Articles or Certificate, this Bylaw, Board resolution, Board-approved delegation, authority matrix, or other competent record.
The Vice-Chair shall support the Chair and Board while preserving the distinction between governance leadership, executive management, technical leadership, public authority learning, finance-boundary support, GRF-facing inputs, GRA-facing inputs, Nexus interface support, and enterprise execution.
136.2 Support to Chair. The Vice-Chair shall support the Chair in carrying out the Chair’s governance functions, including Board leadership, agenda discipline, meeting preparation, director engagement, committee coordination, fiduciary development, succession planning, emergency convening readiness, and protection of mission lock, public-benefit purpose, nonprofit character, non-execution, role separation, records discipline, validity-by-record, and correctionability.
Support to the Chair may include:
a) assisting with Board calendar planning;
b) reviewing draft agendas and governance-significant materials;
c) helping ensure that reserved matters are properly identified;
d) supporting timely circulation of Board materials in coordination with the Secretary;
e) helping identify conflicts, recusals, confidentiality classifications, public authority boundary issues, finance-boundary issues, certification-boundary issues, procurement-neutrality issues, provider-neutrality issues, sponsor non-control issues, data / AI / cyber issues, safeguards issues, and Nexus interface issues requiring Board attention;
f) supporting orderly follow-up on Board action items;
g) helping ensure committee reports are routed to the Board where required; and
h) assisting with Board continuity and handover processes.
The Vice-Chair shall not use support to the Chair to create informal dual control, shadow governance, private pre-clearance of Board matters, suppression of Director concerns, unilateral agenda control, or a parallel channel for sponsor, provider, public authority, funder, donor, or enterprise actor influence.
136.3 Acting Chair Function Where Chair Is Unavailable. Where the Chair is absent, unavailable, conflicted, recused, incapacitated, suspended, removed, resigned, or otherwise unable to act, the Vice-Chair may act as Chair only to the extent permitted by applicable law, the Articles or Certificate, this Bylaw, Board resolution, Board-approved policy, succession plan, meeting rule, or other competent record.
When acting as Chair, the Vice-Chair shall have only the authority necessary to perform the Chair’s governance functions for the relevant period, matter, meeting, proceeding, or emergency. Acting Chair status shall not expand the Vice-Chair’s authority beyond the Chair’s lawful authority and shall not create executive management authority unless separately and lawfully delegated.
Acting Chair authority may include, where authorized:
a) presiding at Board meetings;
b) confirming quorum with the Secretary;
c) supporting agenda discipline;
d) managing conflict and recusal processes;
e) maintaining orderly deliberation;
f) pausing or recessing a meeting for confidentiality, privilege, public authority boundary, finance-boundary, safeguards, competition, data / AI / cyber, or legal reasons;
g) coordinating emergency Board convening;
h) ensuring Board decisions are properly recorded; and
i) supporting follow-up on Board actions.
Acting Chair authority shall end when the Chair resumes service, the conflict or recusal concludes, the Board appoints another acting presiding officer, the Board elects or appoints a new Chair, or the applicable acting period expires.
136.4 Delegated Governance Duties. The Board or Chair may assign governance-support duties to the Vice-Chair, provided that such duties are lawful, recorded where material, within the Board’s authority, consistent with this Bylaw, and not inconsistent with the Chair’s office, officer authority, committee charters, or Board reserved matters.
Delegated governance duties may include:
a) supporting Board evaluation;
b) supporting director onboarding;
c) supporting Board training;
d) supporting committee chair coordination;
e) monitoring completion of Board action items;
f) supporting succession planning;
g) supporting governance calendar discipline;
h) reviewing governance process improvements;
i) supporting mission-lock and role-separation review;
j) supporting emergency governance readiness;
k) supporting Board-controlled public-safe governance summaries where approved; and
l) supporting cross-committee coordination.
Delegated governance duties shall not include authority to bind the Corporation, approve reserved matters, approve contracts, approve expenditures, approve publications, approve data access, approve AI use, approve software releases, approve controlled-room access, accept grants or sponsorships, hire or remove officers or staff, or make external commitments unless separately and lawfully delegated by competent record.
136.5 Board Continuity Duties. The Vice-Chair shall support Board continuity by helping ensure that Board governance can continue during Chair absence, leadership transition, Director turnover, officer transition, cyber incident, data incident, public-safe publication incident, public authority confusion, regulatory-perimeter uncertainty, repository compromise, sponsor or provider capture concern, safeguards issue, protected knowledge issue, legal deadline, or other governance disruption.
Board continuity support may include:
a) maintaining familiarity with current Board agenda, action items, reserved matters, committee reports, and material risk registers;
b) supporting Chair succession and emergency Chair succession planning;
c) supporting continuity packs and governance handover materials;
d) helping ensure that key Board records, registers, delegations, authority matrices, and repository locations are known and accessible to authorized persons;
e) supporting minimum governance operations during disruption;
f) helping identify urgent matters requiring Board attention;
g) supporting emergency meeting readiness;
h) supporting lawful temporary presiding arrangements; and
i) ensuring that continuity measures remain bounded, time-limited, recorded, and subject to Board review.
Continuity duties shall not be used to create permanent office succession, personal entitlement, founder entitlement, factional control, sponsor entitlement, provider entitlement, public authority entitlement, or informal governance outside the Bylaw.
136.6 Committee and Council Interface Support. The Vice-Chair may support the Chair in maintaining effective interfaces with Board committees, standing committees, special committees, leadership councils, Helix councils, advisory councils, public authority forums, scientific and technical advisory bodies, working groups, expert panels, peer review panels, model review panels, Nexus Competence Cells, program steering groups, and controlled-room review groups.
Committee and council interface support may include:
a) confirming that bodies operate within charter;
b) encouraging timely reporting;
c) identifying matters requiring Board escalation;
d) supporting alignment across committees without collapsing their distinct mandates;
e) ensuring that recommendations include risk, boundary, conflict, recusal, public authority, finance, certification, procurement, recognition, provider-neutrality, sponsor non-control, data / AI / cyber, safeguards, and protected knowledge notes where relevant;
f) ensuring that committee records are routed to the Secretary or appropriate custodian;
g) supporting periodic review, renewal, sunset, redesign, or dissolution processes; and
h) helping prevent advisory outputs from being represented as approvals.
The Vice-Chair shall not convert committee recommendations into Board decisions, advisory advice into institutional authority, technical review into certification, evidence review into recognition, public authority feedback into public authority adoption, capital-reader literacy into finance-readiness, or working-group work product into binding standards unless the competent authority and record expressly authorize the result.
136.7 Succession Support. The Vice-Chair shall support Board succession planning, Chair succession planning, committee leadership succession, emergency governance succession, and leadership continuity in coordination with the Chair, Governance, Nominating, Ethics, and Board Renewal Committee where established, Secretary, and Board.
Succession support may include:
a) identifying Board skills and perspective needs;
b) supporting Director recruitment processes;
c) supporting independence and anti-capture review;
d) supporting continuity planning for Chair, Vice-Chair, committee chairs, and key Board functions;
e) helping prepare transition materials;
f) supporting orderly transfer of Board knowledge;
g) supporting records and access closeout for outgoing Directors;
h) supporting onboarding for incoming Directors;
i) identifying risks from concentration of authority, knowledge, access, relationships, or technical dependency; and
j) ensuring that succession processes protect mission lock, public-benefit purpose, role separation, non-execution, provider neutrality, sponsor non-control, safeguards, validity-by-record, and correctionability.
Succession support shall not be used to preselect successors without lawful process, entrench existing leadership, exclude qualified candidates for improper reasons, reward sponsor or provider preferences, or create hereditary, founder-based, factional, donor-based, funder-based, public authority-based, or enterprise-based control of governance.
136.8 Emergency Governance Support. The Vice-Chair shall support emergency governance readiness and response where Board-level action may be required. The Vice-Chair may assist the Chair, Secretary, officers, committees, counsel, compliance function, safeguards function, data / AI / cyber function, and other authorized persons in ensuring that emergency governance processes are lawful, timely, record-supported, time-limited, and subject to Board review.
Emergency governance support may be appropriate in connection with:
a) cyber incidents;
b) data breaches;
c) AI incidents;
d) public-safe publication errors;
e) public authority confusion;
f) emergency command or public warning overclaims;
g) finance, securities, insurance, lending, rating, public finance, procurement, certification, recognition, provider-preference, or sponsor-control overclaims;
h) protected knowledge breach;
i) community harm, civil rights concern, accessibility concern, Tribal or Indigenous protocol issue, or safeguards concern;
j) legal deadline or regulatory-perimeter ambiguity;
k) repository, software release, key, token, credential, technical asset, controlled technology, or infrastructure compromise;
l) Chair incapacity or recusal;
m) officer incapacity, vacancy, misconduct, or delegation defect; and
n) other material risks requiring Board-level attention.
Emergency governance support shall not authorize the Vice-Chair to exercise prohibited functions, issue public warnings, direct emergency operations, approve finance-readiness, approve certification, approve procurement, bind public authorities, approve provider selection, accept sponsor control, or execute enterprise-stack activity.
136.9 Limits on Vice-Chair Authority. The Vice-Chair shall have no authority except as expressly provided by applicable law, the Articles or Certificate, this Bylaw, Board resolution, Board-approved policy, Board-approved delegation, authority matrix, meeting rule, succession plan, or other competent record.
The Vice-Chair shall not, by virtue of office alone:
a) bind the Corporation;
b) sign contracts;
c) approve expenditures;
d) approve grants, donations, sponsorships, restricted funds, or in-kind contributions;
e) hire, discipline, remove, or supervise officers, staff, contractors, fellows, advisors, volunteers, contributors, or maintainers;
f) approve public statements;
g) approve public-safe publications;
h) approve data access;
i) approve AI use;
j) approve model, dataset, benchmark, dashboard, software, API, SDK, repository, or technical baseline releases;
k) approve controlled-room, clean-room, data-room, evidence-room, public authority room, or no-download-room access;
l) approve public authority references;
m) approve finance-readiness, insurance-readiness, capital-readability, bankability, rating, or public finance determinations;
n) approve certification, accreditation, procurement, recognition, standing, maturity, Docket approval, Grid guarantee, or Nexus-compatible public status;
o) select, prefer, endorse, or require providers;
p) confer sponsor, donor, funder, host, or enterprise control; or
q) exercise emergency command, public warning, regulator, public authority, or enterprise execution functions.
Any Vice-Chair action outside lawful authority shall be subject to hold, correction, non-recognition, Board review, ratification where lawful, withdrawal, retraction, access restriction, removal, or other lawful remedy.
136.10 No Independent Executive Authority Unless Delegated. The Vice-Chair shall not possess independent executive authority unless the Board has expressly delegated such authority by competent record and the delegation is lawful, specific, bounded, recorded, revocable, and consistent with this Bylaw.
Any executive or operational delegation to the Vice-Chair shall identify:
a) scope;
b) purpose;
c) duration;
d) budget limit where applicable;
e) contracting or signature limit where applicable;
f) reporting line;
g) required approvals;
h) conflict and recusal rules;
i) records requirements;
j) confidentiality and privilege requirements;
k) public authority boundary controls;
l) finance, certification, procurement, recognition, provider-neutrality, sponsor non-control, and public warning boundary controls;
m) data / AI / cyber / privacy controls;
n) safeguards, civil rights, accessibility, Tribal / Indigenous, local, territorial, and protected knowledge controls;
o) correction pathway; and
p) termination or sunset rule.
No delegation shall permit the Vice-Chair to override Board reserved matters, weaken the Corporation’s public-benefit purpose, alter nonprofit or tax status, collapse GCRI / GRF / GRA role separation, create public authority meaning, create regulated finance meaning, create certification or procurement meaning, confer recognition, prefer providers, accept sponsor control, or conduct enterprise execution.
136.11 Vice-Chair Records. The Corporation shall maintain Vice-Chair Records sufficient to demonstrate the Vice-Chair’s appointment, term, eligibility, duties, authority, delegations, acting Chair status, Board continuity support, committee interface support, emergency governance support, conflicts, recusals, reports, actions, corrections, and closeout.
Vice-Chair Records shall include, as applicable:
a) Vice-Chair appointment or election record;
b) term and renewal record;
c) eligibility and consent record;
d) duty acknowledgment;
e) authority matrix entry;
f) acting Chair records;
g) separate delegation records, if any;
h) Board continuity support records;
i) Chair support records where governance-significant;
j) emergency governance support records;
k) Board evaluation and succession support records;
l) committee, council, working group, panel, and advisory body interface records;
m) conflicts, recusals, abstentions, independence reviews, and access restrictions;
n) public authority boundary, finance-boundary, certification-boundary, procurement-neutrality, recognition-boundary, provider-neutrality, sponsor non-control, data / AI / cyber, safeguards, and protected knowledge escalation records;
o) corrections, clarifications, supersessions, withdrawals, ratifications, or public-safe notices involving Vice-Chair action;
p) handover and closeout records; and
q) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that the Vice-Chair is a continuity and governance-support office, not an independent executive office. The Vice-Chair strengthens Board resilience, Chair succession, committee interface discipline, emergency readiness, and governance quality, but may not become a shadow Chair, shadow executive, public authority, finance-readiness authority, recognition authority, certification authority, procurement authority, provider channel, sponsor channel, or enterprise execution point.
Section 137. President
137.1 President Role. The President shall serve as a principal institutional officer of the Corporation, subject at all times to applicable law, the Articles or Certificate, this Bylaw, Board resolutions, Board-approved policies, Board-approved strategy, Board-approved budget, the delegation matrix, the authority matrix, officer duty records, conflict controls, public-safe claim controls, records requirements, and any limitations imposed by the Board.
The President’s role is to provide institutional leadership, coordination, representation, and execution of Board-approved nonprofit, public-benefit, non-executing institutional strategy within lawful authority. The President may support the Corporation’s evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, public authority learning, all-states-and-territories posture, North America anchor role, and Nexus public-good stack compatibility functions, provided that all such activity remains 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.
The President shall not be treated, by title alone, as:
a) owner, controller, or unilateral governor of the Corporation;
b) substitute Board;
c) person authorized to approve Board reserved matters;
d) public authority, regulator, public warning authority, emergency command authority, procurement authority, public finance authority, certification authority, recognition authority, finance-readiness authority, standards authority, or protocol authority;
e) broker, finder, investment adviser, lender, insurer, underwriter, rating actor, bank, fund, asset manager, capital-placement actor, or public finance intermediary;
f) provider, national company, Project SPV, asset owner, deployment company, infrastructure operator, managed service provider, or enterprise execution actor; or
g) person authorized to bind 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, funders, universities, laboratories, communities, or enterprise-stack actors.
137.2 Institutional Leadership Within Board-Approved Strategy. The President may provide institutional leadership for the Corporation within Board-approved strategy, Board-approved plans, Board-approved budgets, Board-approved policies, and lawful delegations. Institutional leadership may include coordinating officers, supporting implementation of institutional priorities, representing the Corporation where authorized, advancing mission-aligned partnerships, supporting public-good programs, strengthening records discipline, and ensuring that institutional work remains aligned with this Bylaw.
Institutional leadership shall be exercised to advance:
a) public-benefit purpose;
b) nonprofit and non-distribution character;
c) evidence integrity;
d) methods integrity;
e) observability and ontology stewardship;
f) technical truth discipline;
g) public-good R&D;
h) public-good software and open technical baselines;
i) public authority learning without public authority substitution;
j) community safeguards, civil rights, accessibility, Tribal and Indigenous protocol respect, local and territorial knowledge protection, and protected knowledge safeguards;
k) lawful United States all-states-and-territories posture;
l) bounded North America anchor role;
m) Nexus role separation; and
n) correctionable governance.
The President shall not use institutional leadership to create informal governance, bypass the Board, suppress officer escalation, alter Board-approved strategy, weaken controls, privilege sponsors or providers, steer public authority relationships, inflate public claims, collapse GCRI / GRF / GRA role separation, or convert public-good support into enterprise execution.
137.3 Public-Benefit Mission Execution Within Non-Execution Boundary. The President may support execution of the Corporation’s public-benefit mission only within the Corporation’s non-executing role. For purposes of this Section, mission execution means internal institutional implementation of lawful nonprofit, public-benefit, evidence, methods, observability, ontology, public-good R&D, public-good software, open technical baseline, public authority learning, safeguards, and correction functions; it does not mean regulated, sovereign, commercial, procurement, certification, finance, recognition, emergency, operational, or enterprise execution.
The President shall ensure that mission implementation does not become:
a) emergency command, public warning, public health order, incident command, dispatch, evacuation instruction, safety command, or infrastructure operation;
b) public authority decision, regulation, enforcement, permit, public finance approval, funding approval, procurement approval, or sovereign obligation;
c) securities offering, securities solicitation, brokerage, finder activity, capital placement, investment advice, lending, banking, insurance placement, underwriting, rating, guarantee, or public finance execution;
d) certification, accreditation, recognition, maturity determination, standing determination, Nexus-compatible public status, Docket approval, Grid guarantee, finance-readiness determination, insurance-readiness determination, or provider approval;
e) provider selection, preferred-provider designation, sponsor-control mechanism, donor-control mechanism, funder-control mechanism, host-control mechanism, or enterprise-stack advantage; or
f) operational control of a national company, state operating company, regional company, Project SPV, provider, host, deployment, infrastructure asset, data room, observability network, AI-RAN system, DePIN system, DLT system, digital twin, dashboard, software release, or technical asset beyond lawful non-executing stewardship.
Where a mission activity approaches a prohibited or regulated perimeter, the President shall hold, pause, re-scope, escalate, externalize, refer, restrict, quarantine, or terminate the activity as required.
137.4 Board Reporting. The President shall report to the Board in the manner, frequency, format, and scope required by this Bylaw, Board resolution, Board-approved policy, committee request, Chair request within governance authority, or other competent record. Board reporting shall be accurate, complete, timely, risk-aware, public-safe where applicable, and record-supported.
President reports may include:
a) implementation of Board-approved strategy and annual plans;
b) mission and public-benefit progress;
c) evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, and open technical baseline activity;
d) public authority learning activity and capacity-classification issues;
e) data / AI / cyber / privacy status;
f) research integrity, public-safe publication, and correction status;
g) safeguards, civil rights, accessibility, Tribal / Indigenous, local, territorial, and protected knowledge matters;
h) budget, fundraising, grant, donation, sponsorship, support, and restricted-fund matters within the President’s knowledge or delegated scope;
i) officer and program performance where delegated;
j) risks, incidents, conflicts, recusals, boundary concerns, and control weaknesses;
k) GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, consortium, national company, Project SPV, provider, sponsor, host, public authority, university, laboratory, community, and enterprise-stack interface matters; and
l) matters requiring Board approval, Board notice, Board ratification, Board correction, or Board reserved-matter review.
The President shall not omit material risks, unfavorable facts, boundary breaches, sponsor or provider pressures, public authority confusion, finance overclaims, certification overclaims, procurement overclaims, recognition overclaims, data / AI / cyber incidents, safeguards concerns, protected knowledge issues, or correction needs.
137.5 Management Oversight Where Delegated. The President may exercise management oversight only where such authority is delegated by the Board, this Bylaw, an employment or services agreement, authority matrix, or other competent governing record. Management oversight may include supervision of officers, employees, contractors, consultants, fellows, advisors, volunteers, contributors, maintainers, programs, operations, or institutional functions, but only within the scope of the delegation.
Management oversight shall include a duty to preserve:
a) lawful authority and segregation of duties;
b) budget discipline;
c) contracting discipline;
d) records discipline;
e) confidentiality and privilege;
f) data / AI / cyber / privacy controls;
g) public authority boundary controls;
h) finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control controls;
i) research integrity and public-safe publication discipline;
j) civil rights, accessibility, community safeguards, Tribal and Indigenous protocol respect, and protected knowledge controls;
k) competition, sanctions, export-control, controlled technology, and professional-boundary compliance; and
l) correctionability.
The President shall not exercise management oversight to control Board deliberation, override officer statutory duties, suppress independent escalation by officers, interfere with counsel or compliance review, direct research conclusions for improper purposes, suppress corrections, bypass committee review, or create hidden authority.
137.6 Program Oversight Where Delegated. The President may oversee programs, platforms, labs, academy activities, fellowships, working groups, controlled rooms, public authority learning sessions, technical baselines, public-good software initiatives, observability methods, ontology projects, research programs, public-safe publication processes, or Nexus interface activities only where delegated and consistent with Board-approved strategy, budget, policies, and this Bylaw.
Program oversight shall ensure that each program has, as applicable:
a) lawful purpose;
b) approved scope;
c) responsible owner;
d) budget authority;
e) data / AI / cyber classification;
f) public authority capacity classification;
g) finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control boundary review;
h) safeguards review;
i) conflict and related-party review;
j) records custodian;
k) repository location;
l) access class;
m) publication class;
n) correction pathway; and
o) sunset, review, or closeout rule.
No program may be approved, continued, expanded, represented, or externally described by the President as creating public authority authority, finance-readiness, certification, recognition, procurement approval, provider preference, sponsor control, or enterprise execution unless a competent body and governing record lawfully authorize the status.
137.7 External Representation Where Authorized. The President may represent the Corporation externally only within lawful authority and recorded delegation. External representation may include public-benefit convening, public-safe communications, institutional introductions, public authority learning coordination, university and laboratory interfaces, sponsor and donor engagement, provider-neutral ecosystem engagement, community and safeguards engagement, GCRI Canada coordination, GRF and GRA interface support, and Nexus public-good stack coordination.
External representation shall be governed by:
a) legal name and name-use controls;
b) approved public description language;
c) controlled vocabulary;
d) public-safe notice language;
e) non-reliance language where appropriate;
f) authority matrix limits;
g) conflict disclosure and recusal requirements;
h) confidentiality and privilege controls;
i) data / AI / cyber restrictions;
j) safeguards and protected knowledge restrictions;
k) public authority capacity classifications;
l) finance, certification, procurement, recognition, provider-neutrality, sponsor non-control, and enterprise-stack boundary controls; and
m) correction requirements.
The President shall not use external representation to make unauthorized commitments, imply public authority endorsement, imply government adoption, solicit securities, provide investment advice, sell finance-readiness, confer recognition, certify products or providers, approve procurement, prefer providers, grant sponsors control, or bind affiliated or external institutions.
137.8 United States All-States-and-Territories Interface Oversight Where Delegated. The President may support oversight of the Corporation’s United States all-states-and-territories posture where delegated. Such oversight may include coordination across federal, state, District of Columbia, territorial, Tribal, local, municipal, county, metropolitan, port, utility, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, infrastructure, university, laboratory, community, provider, sponsor, host, and public-interest interfaces.
The President shall ensure that state and territorial activity is reviewed for:
a) corporate qualification or registration requirements;
b) charitable solicitation requirements;
c) state tax, franchise tax, sales tax, and fee classification issues;
d) employment, contractor, volunteer, workplace, and safety requirements;
e) privacy, AI, cyber, public sector data, health data, research, and children’s data rules;
f) public records, open meetings, procurement, lobbying, government ethics, gifts, grants, and public authority constraints where applicable;
g) public authority capacity classification;
h) Tribal and Indigenous protocol respect;
i) civil rights and accessibility requirements;
j) sanctions, export-control, controlled technology, and national security sensitivity where applicable; and
k) records, localization notes, compatibility notes, divergence logs, and correction pathways.
No United States state, territorial, District of Columbia, Tribal, local, regional, sectoral, host, sponsor, provider, public authority, or program interface shall be permitted to fracture the Corporation’s mission lock, legal identity, non-execution, controlled vocabulary, public authority boundary, finance boundary, data / AI / cyber controls, safeguards, validity-by-record, or correctionability.
137.9 North America Anchor Interface Oversight Where Delegated. The President may support the Corporation’s bounded North America anchor role where delegated. North America anchor interface oversight may include lawful coordination involving the United States, Canada, Mexico, Caribbean, Arctic, Great Lakes, Pacific, Atlantic, Gulf, border, Indigenous, regional, and cross-border evidence, methods, observability, ontology, technical baseline, public-good software, public authority learning, data / AI / cyber, and safeguards interfaces.
The President shall ensure that North America anchor activity is described as a bounded public-good evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, public authority learning, and safeguards support role, not as:
a) treaty authority;
b) intergovernmental authority;
c) regional regulator;
d) North America sovereign authority;
e) emergency command body;
f) public warning body;
g) public finance approver;
h) procurement body;
i) certification body;
j) recognition body;
k) finance-readiness body;
l) standards monopoly;
m) infrastructure operator;
n) enterprise delivery vehicle; or
o) authority to bind GCRI Canada or any other national or regional entity.
North America anchor interface records shall identify capacity, jurisdiction, participants, public authority status, cross-border data issues, localization needs, limitations, notices, compatibility notes, divergence logs, and correction pathways.
137.10 GCRI Canada Interface Support. The President may support coordination with GCRI Canada within lawful authority and recorded interface structures. Such coordination may include shared doctrine, compatible methods, ontology alignment, observability methods, public-good software, open technical baselines, public-safe publications, cross-border learning, North America risk evidence support, and correction signals.
The President shall preserve separate legal personality and shall ensure that coordination with GCRI Canada does not create:
a) merger;
b) branch status;
c) parent-subsidiary status;
d) alter ego status;
e) common treasury;
f) automatic mutual authority;
g) shared liability;
h) single employer or joint employer status;
i) agency;
j) partnership;
k) joint venture; or
l) authority for either entity to bind the other without express written instrument.
Where a person holds roles in both GCRI US and GCRI Canada, the President shall support dual-role controls, capacity identification, conflict disclosure, recusal, separate records, access controls, and public description discipline. Shared mission shall not substitute for legal authority.
137.11 GRF, GRA, Nexus Standards, Nexus Network, and Nexus Entity Interface Support. The President may support interfaces with 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 other Nexus-related actors only within the Corporation’s lawful role and recorded authority.
In such interfaces, the President shall maintain that:
a) GCRI US provides evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, and correction signals;
b) 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;
c) 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;
d) Nexus Standards and any protocol authority remain separate unless lawfully conferred and recorded;
e) public authorities act only through their own lawful authority;
f) national companies and Project SPVs remain enterprise-stack actors; and
g) providers, sponsors, hosts, funders, and enterprise actors do not control public-good outputs.
The President shall not represent GCRI US evidence support as GRF recognition, GRA finance-readiness, Nexus Standards adoption, public authority approval, certification, procurement approval, provider preference, sponsor entitlement, or enterprise execution.
137.12 Public Authority Interface Support Without Public Authority Delegation. The President may support public authority learning and public authority interface activities where authorized, including federal, state, territorial, District of Columbia, Tribal, Indigenous government, local, municipal, county, metropolitan, utility, port, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, infrastructure, public finance reader, regulator-listening, and public infrastructure operator interfaces.
The President shall ensure that public authority interface activity is governed by capacity classification, official-capacity records, observer records, regulator-listening records, public finance reader records, emergency-management participant records, public infrastructure operator records, controlled-room rules, public authority reference controls, confidentiality rules, public records considerations, government ethics considerations, lobbying and gifts controls where applicable, public procurement discipline, and public-safe notice language.
The President shall not state, imply, permit, or fail to correct an implication that the Corporation:
a) exercises delegated governmental power;
b) issues public warnings;
c) directs emergency response;
d) approves public procurement;
e) approves public funding;
f) approves public finance;
g) creates official adoption through participation;
h) creates sovereign obligations;
i) substitutes for a regulator or public authority;
j) makes legal compliance determinations; or
k) binds a public authority by meeting, data contribution, dashboard access, controlled-room participation, or public-safe report review.
137.13 Fundraising and Public-Good Support Support Within Controls. The President may support fundraising, grant development, donation development, sponsorship development, public-good infrastructure support, in-kind contribution coordination, subscription strategy, fee strategy, academy support, fellowship support, challenge support, and other lawful support activities where authorized and consistent with this Bylaw.
Fundraising and support activity shall remain subject to:
a) tax and nonprofit review;
b) charitable solicitation compliance where applicable;
c) support acceptance review;
d) conflict and related-party review;
e) sanctions and export-control review;
f) controlled technology and national security sensitivity review;
g) public authority boundary review;
h) finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control review;
i) data / AI / cyber review;
j) safeguards and protected knowledge review;
k) public acknowledgment controls;
l) private benefit and inurement review;
m) restricted fund controls;
n) records discipline; and
o) correction and termination pathways.
The President shall not offer, negotiate, imply, or permit support arrangements that confer control over governance, evidence, methods, publications, technical baselines, public authority access, GRF-facing inputs, GRA-facing inputs, Nexus interfaces, provider status, certification, recognition, finance-readiness, procurement advantage, public claims, or correction outcomes.
137.14 No Authority to Conduct Prohibited Functions. The President shall have no authority to conduct, approve, imply, facilitate, or permit prohibited functions. This limitation applies regardless of title, urgency, public interest, public authority request, sponsor request, provider request, donor request, funder request, technical need, reputational pressure, grant deadline, public safety concern, emergency context, market demand, Nexus interface expectation, or operational convenience.
The President shall not conduct or authorize:
a) emergency command, public warning, public health order, dispatch, evacuation instruction, safety command, or incident command;
b) public authority decision, regulation, enforcement, permit, public procurement approval, funding approval, public finance approval, sovereign obligation, or official adoption;
c) securities offering, solicitation, broker-dealer activity, finder activity, investment advice, capital placement, underwriting, lending, banking, insurance placement, insurance underwriting, rating, guarantee, or public finance execution;
d) certification, accreditation, recognition, standing, maturity determination, Docket approval, Grid guarantee, Nexus-compatible public status, finance-readiness, insurance-readiness, bankability, investability, or capital-readability determination;
e) provider selection, preferred provider designation, procurement steering, or commercial endorsement;
f) sponsor, donor, funder, host, provider, public authority, or enterprise control of public-good outputs;
g) execution of national company, state operating company, regional company, Project SPV, provider, asset owner, operator, or commercial delivery functions; or
h) use of AI outputs, dashboards, proof receipts, digital twins, DePIN records, DLT entries, AI-RAN signals, O-RAN signals, sensor signals, automated scores, model outputs, or technical baselines as authority without competent human review and governing record.
Any proposed action that may fall within this Section shall be held and escalated for competent review.
137.15 No Authority to Bind Reserved Matters Without Board Approval. The President shall not bind the Corporation with respect to Board reserved matters unless the Board has approved the matter through lawful action and the President is authorized to implement the approved action within recorded limits. Implementation authority shall not be treated as approval authority.
Without limiting the foregoing, the President shall not unilaterally approve:
a) amendment, restatement, repeal, or replacement 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 office, or principal governance seat where material;
d) tax-exempt status application, change, revocation, or structural shift;
e) charitable status, fiscal sponsorship, supporting organization, or other tax-structure decision;
f) mission-lock, public-benefit, nonprofit, non-distribution, or non-execution boundary change;
g) annual strategy, annual plan, annual budget, or material budget amendment;
h) major grant, donation, sponsorship, restricted fund, support arrangement, contract, debt, credit facility, lease, asset transfer, IP transfer, repository transfer, or technical asset disposition;
i) appointment or removal of key officers where Board approval is required;
j) creation or dissolution of major committees, councils, programs, controlled rooms, or Nexus interfaces;
k) adoption of major policies or protocols affecting public authority, data / AI / cyber, privacy, research integrity, publication, safeguards, sponsorship, sanctions, export-control, competition, controlled technology, finance boundaries, certification boundaries, procurement boundaries, recognition boundaries, provider neutrality, or sponsor non-control;
l) litigation, investigation, regulatory engagement, settlement, enforcement matter, dissolution, merger, consolidation, conversion, sale of substantially all assets, wind-up, or public-good asset distribution; or
m) any matter reserved to the Board by law, the Articles or Certificate, this Bylaw, Board resolution, member approval where required, or policy.
Any President action purporting to approve a reserved matter without authority shall be subject to hold, correction, non-recognition, Board review, ratification where lawful, withdrawal, retraction, or other lawful remedy.
137.16 President Records. The Corporation shall maintain President Records sufficient to demonstrate the President’s appointment, term, eligibility, authority, delegations, duties, reports, decisions, external representations, public authority interfaces, support activities, management oversight, program oversight, conflicts, recusals, incidents, corrections, restrictions, succession, and closeout.
President Records shall include, as applicable:
a) appointment or election record;
b) term and renewal record;
c) eligibility, consent, fit-and-proper, integrity, conflict, independence, sanctions, export-control, controlled-technology, data / AI / cyber, research integrity, public authority boundary, finance-boundary, safeguards, and protected knowledge screening records;
c) duty acknowledgment and certification of understanding;
d) role description;
e) reporting line;
f) authority matrix entry;
g) separate delegations;
h) Board reports;
i) committee reports involving the President;
j) decisions within delegated authority;
k) public statements and external representation approvals;
l) public authority capacity records;
m) all-states-and-territories interface records;
n) North America anchor interface records;
o) GCRI Canada interface records;
p) 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;
q) support, grant, donation, sponsorship, in-kind, subscription, fee, and public-good support records involving the President;
r) data / AI / cyber, research integrity, public-safe publication, safeguards, protected knowledge, competition, sanctions, export-control, controlled technology, public authority, finance, certification, procurement, recognition, provider-neutrality, sponsor non-control, and non-execution escalation records;
s) conflicts, recusals, abstentions, restrictions, corrective actions, access revocations, and closeout records; and
t) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that the President may lead, coordinate, represent, and implement within Board-approved and lawfully delegated authority, but may not become a substitute Board, public authority, finance-readiness authority, recognition authority, certification authority, procurement authority, sponsor channel, provider channel, technical oracle, or enterprise execution point. Presidential authority is bounded by record, review, delegation, public-benefit purpose, non-execution, role separation, safeguards, and correctionability.
Section 138. Executive Director or Chief Executive Officer
138.1 Executive Director or Chief Executive Officer Role Where Approved. The Executive Director or Chief Executive Officer, where such office is approved by the Board, shall serve as the principal operational executive of the Corporation, subject at all times to applicable law, the Articles or Certificate, this Bylaw, Board resolutions, Board-approved strategy, Board-approved budget, Board-approved policies, the delegation matrix, the authority matrix, employment or services agreement, conflict controls, records requirements, public-safe claim controls, and any limitations imposed by the Board.
The Executive Director or Chief Executive Officer shall be responsible for the day-to-day operational leadership of the Corporation only within delegated authority. The office exists to implement Board-approved strategy, manage operational systems, coordinate staff and contractor functions, support institutional continuity, and ensure that public-benefit work is performed with administrative seriousness, legal discipline, technical integrity, safeguards, and correctionability.
The Executive Director or Chief Executive Officer shall not, by title alone, be treated as:
a) a substitute Board;
b) a person authorized to approve Board reserved matters;
c) a public authority, regulator, public warning authority, emergency command authority, procurement authority, public finance authority, certification authority, recognition authority, finance-readiness authority, standards authority, or protocol authority;
d) a broker, finder, investment adviser, lender, insurer, underwriter, bank, fund, rating agency, capital-placement actor, asset manager, or public finance intermediary;
e) a national company, Project SPV, provider, asset owner, deployment company, infrastructure operator, managed service provider, commercial delivery actor, or enterprise execution vehicle;
f) a person authorized to bind 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, communities, or enterprise-stack actors; or
g) a person authorized to convert evidence, methods, observability, ontology, technical baselines, public-good software, proof receipts, AI outputs, dashboards, digital twins, AI-RAN signals, O-RAN signals, DePIN records, DLT entries, or controlled-room outputs into external authority without competent record.
138.2 Operational Management. The Executive Director or Chief Executive Officer may manage the Corporation’s daily operations within lawful authority and recorded delegation. Operational management may include staff coordination, contractor coordination, program administration, budget implementation, operational planning, internal workflow management, meeting preparation, records routing, administrative controls, vendor coordination, repository administration support, controlled-room administration support, and implementation of Board-approved institutional priorities.
Operational management shall be exercised to preserve:
a) public-benefit purpose;
b) nonprofit and non-distribution character;
c) non-execution;
d) legal separateness;
e) GCRI / GRF / GRA role separation;
f) public-good stack and enterprise stack separation;
g) public authority boundaries;
h) finance, securities, insurance, lending, rating, public finance, procurement, certification, recognition, provider-neutrality, and sponsor non-control boundaries;
i) data / AI / cyber / privacy controls;
j) research integrity, evidence integrity, methods integrity, and technical truth integrity;
k) civil rights, accessibility, community safeguards, Tribal and Indigenous protocol respect, local and territorial knowledge safeguards, and protected knowledge safeguards;
l) competition, sanctions, export-control, controlled technology, and professional-boundary compliance;
m) records discipline; and
n) correctionability.
Operational management shall not be used to create informal authority, bypass Board approval, suppress escalation, weaken controls, alter public meaning, create public reliance, privilege a sponsor or provider, or convert institutional support into regulated or enterprise execution.
138.3 Implementation of Board-Approved Strategy. The Executive Director or Chief Executive Officer shall implement Board-approved strategy within the limits of approved authority, approved budget, approved plans, and approved controls. Implementation shall be faithful to the Board’s recorded decisions and shall not substitute executive preference, donor preference, sponsor preference, provider preference, public authority pressure, technical urgency, market opportunity, or personal judgment for Board-approved strategy.
Implementation of Board-approved strategy may include:
a) preparing operational plans;
b) assigning responsible owners;
c) coordinating officer workstreams;
d) establishing implementation calendars;
e) tracking milestones;
f) identifying dependencies;
g) reporting implementation status;
h) escalating delay, risk, or control concerns;
i) documenting changes requiring approval;
j) maintaining implementation records; and
k) supporting correction, supersession, withdrawal, or redesign where the strategy no longer remains lawful, feasible, public-safe, or mission-aligned.
The Executive Director or Chief Executive Officer shall not materially change, expand, reframe, commercialize, externalize, localize, or represent Board-approved strategy in a manner that alters mission lock, public-benefit purpose, nonprofit character, 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, or correctionability.
138.4 Implementation of Board-Approved Budget. The Executive Director or Chief Executive Officer may implement the Board-approved budget within delegated authority and approved spending, procurement, contracting, grant, donation, sponsorship, restricted-fund, reimbursement, compensation, and internal-control rules. Budget implementation shall be purpose-aligned, reasonable, documented, reviewable, and subject to financial controls.
The Executive Director or Chief Executive Officer shall ensure that expenditures and commitments within operational authority are:
a) within approved budget category;
b) within signature and spending authority;
c) supported by adequate documentation;
d) consistent with public-benefit purpose;
e) free from private inurement and impermissible private benefit;
f) compliant with restricted fund, grant, donation, sponsorship, and in-kind contribution terms;
g) consistent with tax-exempt or tax-exempt-compatible discipline;
h) compliant with procurement and contracting procedures;
i) reviewed for conflicts and related-party issues where applicable;
j) reviewed for sanctions, export-control, controlled technology, and competition concerns where applicable; and
k) recorded in the accounting and corporate records.
No budget implementation authority shall permit the Executive Director or Chief Executive Officer to approve a material budget amendment, incur major debt, pledge assets, transfer intellectual property, transfer repositories, dispose of major technical assets, accept restricted funds outside authority, or enter major contracts unless approved by the Board or otherwise lawfully authorized by competent record.
138.5 Staff, Contractor, Fellow, Advisor, Volunteer, and Contributor Management Where Delegated. The Executive Director or Chief Executive Officer may manage staff, contractors, consultants, fellows, advisors, volunteers, seconded personnel, contributors, maintainers, and operational teams where delegated. Management authority shall be exercised through lawful roles, written terms where required, clear reporting lines, appropriate supervision, and records sufficient to demonstrate authority, duties, conflicts, confidentiality, data access, AI-use permissions, cyber access, repository access, intellectual property treatment, and closeout.
Personnel and contributor management shall include, as applicable:
a) onboarding;
b) role descriptions;
c) authority limitations;
d) confidentiality acknowledgments;
e) code-of-conduct acknowledgments;
f) conflict disclosures;
g) data / AI / cyber training;
h) public authority boundary training;
i) finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control training;
j) civil rights, accessibility, community safeguards, Tribal / Indigenous protocol, local and territorial knowledge, and protected knowledge training;
k) repository and controlled-room access controls;
l) performance and deliverable review;
m) incident and grievance handling;
n) correction and disciplinary action;
o) offboarding; and
p) access revocation, return, deletion, transfer, sealing, or archival of records and materials.
The Executive Director or Chief Executive Officer shall not use personnel management to retaliate against protected participation, suppress lawful dissent, punish correction requests, hide conflicts, bypass committee or Board reporting, coerce research findings, influence technical outputs for sponsors or providers, or weaken safeguards.
138.6 Program Management. The Executive Director or Chief Executive Officer may manage programs, platforms, labs, fellowships, academy activities, technical workstreams, evidence systems, observability projects, ontology projects, public-good software initiatives, open technical baseline work, public authority learning sessions, controlled rooms, clean rooms, evidence rooms, data rooms, no-download rooms, Nexus interface activities, and public-safe publication workflows where delegated and within approved strategy, budget, and policies.
Program management shall require each material program to have, as applicable:
a) written scope;
b) lawful purpose;
c) responsible owner;
d) budget authority;
e) implementation schedule;
f) authority matrix entry;
g) participant and access controls;
h) public authority capacity classification;
i) finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control review;
j) data / AI / cyber / privacy classification;
k) research integrity and publication review pathway;
l) safeguards and protected knowledge review pathway;
m) public-safe notice language;
n) repository or record location;
o) escalation pathway;
p) correction pathway; and
q) closeout, archive, or sunset rule.
The Executive Director or Chief Executive Officer shall not manage any program as a substitute public authority, finance-readiness system, certification system, recognition system, procurement system, public warning system, emergency command system, provider-selection channel, sponsor-controlled surface, or enterprise execution vehicle.
138.7 Policy Implementation. The Executive Director or Chief Executive Officer shall implement Board-approved policies and may implement officer-approved operational instruments within delegated authority. Policy implementation shall include communication, training, workflow design, register updates, repository placement, forms deployment, checklist use, monitoring, exception escalation, corrective action, and periodic review.
Policy implementation shall not be treated as authority to amend policy. Where a policy is unclear, incomplete, outdated, inconsistent with higher-order authority, unsafe in application, or exposed to legal, public authority, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, sponsor non-control, data / AI / cyber, safeguards, research integrity, or public-safe publication risk, the Executive Director or Chief Executive Officer shall escalate the matter to the responsible officer, committee, counsel, compliance function, or Board.
No operational interpretation, training slide, AI summary, staff instruction, dashboard rule, repository workflow, checklist, form, implementation memo, vendor setting, controlled-room practice, or program custom shall amend, supersede, weaken, or silently replace an adopted policy, the Articles or Certificate, this Bylaw, or Board reserved matter.
138.8 Internal Controls Implementation. The Executive Director or Chief Executive Officer shall support implementation of internal controls adopted by the Board, officers, committees, or policies. Internal controls shall be designed to prevent unauthorized acts, defective records, private benefit, misuse of funds, conflicts, data misuse, AI misuse, cyber incidents, public authority confusion, finance overclaims, certification overclaims, procurement overclaims, recognition overclaims, provider preference, sponsor control, research integrity failures, safeguards breaches, and uncorrected public claims.
Internal controls may include:
a) segregation of duties;
b) spending approvals;
c) signature controls;
d) contract review;
e) grant and restricted-fund controls;
f) donation and sponsorship acceptance controls;
g) bank and reconciliation controls;
h) procurement and vendor controls;
i) repository access controls;
j) data access controls;
k) AI-use controls;
l) model register and inference record controls;
m) cybersecurity controls;
n) publication controls;
o) public authority reference controls;
p) controlled-room controls;
q) conflict and recusal controls;
r) sanctions and export-control controls;
s) safeguards and protected knowledge controls; and
t) correction controls.
The Executive Director or Chief Executive Officer shall report control weaknesses, control failures, circumvention, suspected fraud, unauthorized access, shadow systems, or repeated exceptions to the appropriate authority.
138.9 Risk Escalation. The Executive Director or Chief Executive Officer shall promptly escalate material operational, legal, financial, tax, nonprofit, public-benefit, mission-lock, non-execution, public authority, finance, securities, insurance, lending, rating, public finance, procurement, certification, recognition, provider-neutrality, sponsor non-control, data / AI / cyber, privacy, research integrity, publication, safeguards, protected knowledge, civil rights, accessibility, competition, sanctions, export-control, controlled technology, professional-boundary, personnel, contractor, repository, technical asset, Nexus interface, and reputational risks.
Escalation shall be made to the appropriate person or body, which may include:
a) Chair;
b) President;
c) Board;
d) relevant Board committee;
e) Secretary;
f) Treasurer or Chief Financial Officer;
g) Chief Legal, Compliance, and Risk Officer;
h) Chief Data, AI, and Cyber Officer;
i) Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer;
j) Chief Evidence Officer;
k) Chief Research Officer;
l) Chief Methods Officer;
m) counsel;
n) compliance function;
o) auditor or financial reviewer;
p) insurer, funder, grantor, or public authority where notice is legally or contractually required; and
q) law enforcement or regulator where legally required or appropriate.
Risk escalation shall not be delayed because the risk is inconvenient, reputationally sensitive, sponsor-sensitive, provider-sensitive, public authority-sensitive, technically complex, legally ambiguous, politically sensitive, or likely to require correction.
138.10 Compliance Escalation. The Executive Director or Chief Executive Officer shall escalate compliance questions and suspected compliance failures involving applicable law, the Articles or Certificate, this Bylaw, Board resolutions, policies, tax-exempt or tax-exempt-compatible obligations, grant conditions, restricted fund terms, charitable solicitation rules, state qualification rules, employment rules, privacy rules, AI governance rules, cybersecurity rules, research ethics rules, civil rights and accessibility rules, lobbying or political activity rules, government ethics rules, public procurement integrity rules, sanctions, export controls, controlled technology, competition law, and professional boundaries.
Compliance escalation shall include, as applicable:
a) identification of the issue;
b) relevant facts;
c) affected persons, systems, jurisdictions, records, and outputs;
d) authority relied upon;
e) action already taken;
f) immediate risk controls;
g) recommended hold, quarantine, restriction, re-scope, externalization, referral, correction, or termination;
h) record preservation steps;
i) privilege or confidentiality handling; and
j) follow-up owner and deadline.
No Executive Director or Chief Executive Officer may treat informal operational comfort, sponsor assurance, provider assurance, public authority interest, technical feasibility, industry custom, AI output, dashboard signal, proof receipt, legal template, or prior practice as a substitute for competent compliance review.
138.11 Public-Safe Publication Oversight Where Delegated. The Executive Director or Chief Executive Officer may oversee public-safe publication workflows where delegated. Public-safe publication oversight may apply to reports, whitepapers, datasets, dashboards, maps, software documentation, technical baselines, proof receipts, public-good software releases, repository notices, public authority learning materials, grant materials, sponsorship acknowledgments, media materials, academy materials, and Nexus interface materials.
Public-safe publication oversight shall require, as applicable:
a) authority to publish;
b) publication class;
c) access class;
d) source-lineage and provenance review;
e) method version review;
f) confidence and uncertainty language;
g) data / AI / cyber / privacy review;
h) public authority boundary review;
i) finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control review;
j) civil rights, accessibility, community safeguards, Tribal / Indigenous, local, territorial, and protected knowledge review;
k) competition, sanctions, export-control, controlled technology, and professional-boundary review;
l) public-safe notices and limitation language;
m) correction, supersession, withdrawal, retraction, takedown, and archive pathways; and
n) repository and metadata records.
The Executive Director or Chief Executive Officer shall not permit publication of materials that create public warning confusion, public authority confusion, investment reliance, insurance reliance, procurement reliance, certification reliance, recognition reliance, provider preference, sponsor control, protected knowledge exposure, data breach risk, cyber risk, research integrity risk, or public harm.
138.12 Data / AI / Cyber / Privacy Control Implementation Where Delegated. The Executive Director or Chief Executive Officer may support implementation of data governance, AI governance, cybersecurity, privacy, secure compute, identity, access, logging, monitoring, repository, model register, inference record, compute workload record, secure release, incident response, business continuity, disaster recovery, and vendor security controls where delegated.
Data / AI / cyber / privacy implementation shall include, as applicable:
a) approved systems use;
b) access authorization;
c) least-privilege access;
d) identity verification;
e) credential, key, token, and secret controls;
f) logging and monitoring;
g) AI-use approvals;
h) model register entries;
i) inference record entries;
j) compute workload records;
k) dataset, model, system, and benchmark cards;
l) personal information, public authority data, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, community-protected data, Tribal / Indigenous data, local and territorial knowledge, and protected knowledge classification;
m) cross-border transfer review;
n) secure development and release controls;
o) vendor and processor review;
p) incident response; and
q) correction, deletion, sealing, archival, or secure disposal where required.
No Executive Director or Chief Executive Officer shall permit controlled materials to be uploaded to unapproved AI systems, stored in shadow systems, shared through unapproved channels, processed without authority, used for unauthorized training or model improvement, disclosed beyond access class, or relied upon as authority without human review and governing record.
138.13 Public Authority Interface Management Where Delegated. The Executive Director or Chief Executive Officer may manage public authority interfaces where delegated, including federal, state, District of Columbia, territorial, Tribal, Indigenous government, local, county, municipal, metropolitan, port, utility, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, infrastructure, public finance reader, regulator-listening, and public infrastructure operator interfaces.
Public authority interface management shall require:
a) capacity classification;
b) official-capacity or observer records where applicable;
c) public authority room, controlled-room, clean-room, evidence-room, data-room, or no-download-room controls where applicable;
d) public authority data contribution controls;
e) public authority reference controls;
f) confidentiality and public records review where applicable;
g) government ethics, gifts, lobbying, grant, procurement integrity, and open-meetings review where applicable;
h) public-safe notices;
i) limitation and non-reliance language;
j) records of questions, feedback, materials, and follow-up;
k) escalation of public authority confusion; and
l) correction or clarification where needed.
The Executive Director or Chief Executive Officer shall not manage public authority relationships in a manner that implies delegated governmental power, official adoption, public warning authority, emergency command, public finance approval, funding approval, procurement approval, regulatory approval, sovereign obligation, public-private partnership status, or substitution for a public authority.
138.14 Sponsor, Donor, Funder, Provider, Host, and Partner Relationship Management Within Anti-Capture Controls. The Executive Director or Chief Executive Officer may manage sponsor, donor, funder, provider, host, university, laboratory, public-benefit organization, community, civil society, media, public-interest, and partner relationships where delegated. Such management shall preserve anti-capture controls, provider neutrality, sponsor non-control, public-benefit purpose, research independence, public-safe publication integrity, and Nexus role separation.
Relationship management shall be conducted through written terms, approved public descriptions, conflict disclosures, benefit schedules, acknowledgment controls, data and IP terms, confidentiality terms, access controls, support acceptance records, and correction pathways where appropriate.
No relationship management activity shall permit:
a) control over governance;
b) control over Board, committee, officer, or staff decisions;
c) purchase of research findings;
d) publication veto or suppression right;
e) public authority access purchase;
f) provider preference;
g) procurement advantage;
h) recognition purchase;
i) finance-readiness purchase;
j) certification purchase;
k) Nexus-compatible status purchase;
l) Docket or Grid outcome purchase;
m) privileged data access outside controls;
n) misuse of GCRI US name, marks, public-good software, technical baselines, reports, proof receipts, dashboards, or public authority references; or
o) influence over corrections.
Where support or participation creates capture risk, the Executive Director or Chief Executive Officer shall escalate, restrict, ring-fence, diversify, refuse, return, terminate, or correct the relationship.
138.15 No Authority Over Board Reserved Matters Without Board Approval. The Executive Director or Chief Executive Officer shall have no authority over Board reserved matters except to prepare materials, provide recommendations, implement approved actions, or carry out a specific delegation recorded by the Board and lawful under the governing instruments. Operational responsibility shall not become approval authority.
The Executive Director or Chief Executive Officer shall not unilaterally approve:
a) amendment, restatement, repeal, or replacement 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 office, or governance seat where material;
d) tax-exempt status application, change, revocation, or structural shift;
e) charitable status, fiscal sponsorship, supporting organization, or other tax-structure decision;
f) mission-lock, public-benefit, nonprofit, non-distribution, or non-execution boundary change;
g) annual strategy, annual plan, annual budget, or material budget amendment;
h) major grant, donation, sponsorship, restricted fund, support arrangement, contract, debt, lease, credit facility, asset transfer, IP transfer, repository transfer, or technical asset disposition;
i) appointment or removal of key officers where Board approval is required;
j) creation or dissolution of major committees, councils, programs, controlled rooms, public authority rooms, Nexus interfaces, or cross-border institutional structures;
k) adoption of major policies or protocols affecting public authority, data / AI / cyber, privacy, research integrity, publication, safeguards, sponsorship, sanctions, export-control, competition, controlled technology, finance boundaries, certification boundaries, procurement boundaries, recognition boundaries, provider neutrality, or sponsor non-control;
l) litigation, investigation, regulatory engagement, settlement, enforcement matter of material significance, dissolution, merger, consolidation, conversion, sale of substantially all assets, wind-up, or public-good asset distribution; or
m) any other matter reserved by law, the Articles or Certificate, this Bylaw, Board resolution, member approval where required, or policy.
Any purported approval by the Executive Director or Chief Executive Officer of a reserved matter without authority shall be subject to hold, correction, non-recognition, Board review, ratification where lawful, withdrawal, retraction, or other lawful remedy.
138.16 No Authority to Conduct Regulated Execution, Public Authority Action, Finance Execution, Certification, Procurement Approval, Recognition, or Emergency Command. The Executive Director or Chief Executive Officer shall have no authority to conduct, approve, imply, facilitate, or permit any prohibited or regulated execution function. This limitation shall apply regardless of operational urgency, public interest, public authority request, sponsor request, provider request, donor request, funder request, host request, technical feasibility, market demand, grant deadline, emergency context, public safety concern, institutional opportunity, or Nexus interface expectation.
The Executive Director or Chief Executive Officer shall not conduct or authorize:
a) emergency command, incident command, dispatch, evacuation instruction, public health order, official public warning, public safety command, or infrastructure operation;
b) regulation, enforcement, permit issuance, legal compliance approval, public authority decision, public procurement approval, public funding approval, public finance approval, sovereign obligation, or official adoption;
c) securities offering, securities solicitation, brokerage, finder activity, investment advice, capital placement, underwriting, banking, lending, guarantee, insurance placement, insurance underwriting, rating, or public finance execution;
d) certification, accreditation, conformance approval, professional credentialing, recognition, maturity determination, standing determination, Docket approval, Grid guarantee, Nexus-compatible public status, finance-readiness determination, insurance-readiness determination, bankability determination, investability determination, or capital-readability determination;
e) provider selection, preferred-provider status, required-provider status, procurement steering, commercial endorsement, or enterprise-stack authorization;
f) sponsor, donor, funder, host, provider, public authority, investor, insurer, lender, national company, Project SPV, or enterprise control over public-good outputs; or
g) use of AI outputs, dashboards, digital twins, proof receipts, DePIN records, DLT entries, AI-RAN signals, O-RAN signals, sensor signals, automated scores, model outputs, controlled-room outputs, or technical baselines as authority without competent human review, limitation language, and governing record.
Any activity approaching this Section shall be stopped, held, quarantined, re-scoped, externalized, referred, terminated, or escalated to competent review.
138.17 Executive Director or Chief Executive Officer Records. The Corporation shall maintain Executive Director or Chief Executive Officer Records sufficient to demonstrate appointment, term, eligibility, authority, delegations, employment or services terms, management actions, Board reporting, budget implementation, program management, policy implementation, internal controls, public authority interfaces, support relationships, risks, incidents, escalations, corrections, conflicts, recusals, restrictions, succession, and closeout.
Executive Director or Chief Executive Officer Records shall include, as applicable:
a) appointment record;
b) term and renewal record;
c) employment, services, compensation, benefits, reimbursement, and expense records;
d) eligibility, consent, fit-and-proper, integrity, conflict, independence, sanctions, export-control, controlled-technology, data / AI / cyber, research integrity, public authority boundary, finance-boundary, safeguards, and protected knowledge screening records;
e) duty acknowledgment and certification of understanding;
f) role description;
g) reporting line;
h) authority matrix entry;
i) separate delegations;
j) Board reports and committee reports;
k) operational plans and implementation records;
l) budget implementation records;
m) spending, procurement, contracting, grant, donation, sponsorship, in-kind, subscription, fee, and cost-recovery records within delegated scope;
n) staff, contractor, consultant, fellow, advisor, volunteer, contributor, maintainer, and seconded personnel records within delegated scope;
o) program records, controlled-room records, repository records, publication records, and technical asset records within delegated scope;
p) data / AI / cyber / privacy control records;
q) public authority capacity and interface records;
r) sponsor, donor, funder, provider, host, university, laboratory, community, civil society, media, public-interest, and partner relationship records;
s) 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, and enterprise-stack interface records;
t) risk, compliance, incident, corrective action, correction, supersession, withdrawal, retraction, takedown, and archive records;
u) conflicts, recusals, access restrictions, delegation restrictions, disciplinary actions, suspension, resignation, removal, handover, access revocation, and closeout records; and
v) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that the Executive Director or Chief Executive Officer may manage operations and implement Board-approved strategy within recorded delegation, but may not become a substitute Board, public authority, finance-readiness authority, recognition authority, certification authority, procurement authority, sponsor channel, provider channel, standards authority, technical oracle, or enterprise execution point. Executive authority is operational, bounded, reviewable, record-supported, public-benefit-aligned, non-executing, and correctionable.
Section 145. Chief Data, AI, and Cyber Officer
145.1 Chief Data, AI, and Cyber Officer Role. The Chief Data, AI, and Cyber Officer, where such office is approved by the Board, shall serve as the principal data-governance, privacy-control, AI-governance, model-register, inference-record, compute-workload-record, agentic-AI-control, cybersecurity-program, identity-and-access, logging-and-monitoring, vulnerability-management, incident-response, backup, business-continuity, public-authority-data, health-sensitive-data, cyber-sensitive-data, infrastructure-sensitive-data, community-protected-data, Tribal / Indigenous data, protected-knowledge-data, cross-border-transfer, sovereign-data-zone, AI-incident, cyber-incident, and automated-output-boundary officer of the Corporation, subject at all times to applicable law, the Articles or Certificate, this Bylaw, Board resolutions, Board-approved policies, the delegation matrix, the authority matrix, approved budget, research integrity controls, evidence controls, methods controls, technical controls, privacy controls, data / AI / cyber controls, public authority boundary controls, finance-boundary controls, certification-boundary controls, procurement-neutrality controls, provider-neutrality controls, sponsor non-control controls, safeguards, protected knowledge restrictions, controlled vocabulary, validity-by-record, and correctionability.
The Chief Data, AI, and Cyber Officer’s office exists to preserve the lawful, secure, privacy-respecting, rights-respecting, auditable, accountable, human-reviewable, public-safe, and correctionable use of data, AI systems, compute systems, cyber systems, model outputs, inference outputs, datasets, dashboards, repositories, controlled rooms, public authority data interfaces, observability systems, Nexus Truth Engine support systems, verifiable compute systems, public-good software systems, and other technical environments used by or supported by the Corporation.
The Chief Data, AI, and Cyber Officer shall not, by title, technical expertise, security authority, model access, dataset access, dashboard access, system-administrator access, compute access, incident-response role, cyber role, AI governance role, or data custody alone, be treated as:
a) a substitute Board;
b) a person authorized to approve Board reserved matters;
c) a regulator, public authority, data protection authority, public warning authority, emergency command authority, procurement authority, public finance authority, certification authority, recognition authority, standards authority, protocol authority, finance-readiness authority, rating authority, insurance-readiness authority, capital-readability authority, or enterprise execution actor;
d) a person authorized to make final legal, regulatory, engineering, clinical, public health, public safety, cyber, telecom, financial, insurance, underwriting, lending, procurement, emergency-management, operational, certification, recognition, or finance-readiness determinations;
e) a person authorized to bind 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, communities, Indigenous knowledge holders, data subjects, funders, or enterprise-stack actors;
f) a person authorized to convert a dataset, model register, inference record, compute workload record, benchmark, dashboard, AI output, agentic AI action, cyber tool, data-room output, controlled-room output, public authority data contribution, proof receipt, ledger reference, digital twin, sensor signal, AI-RAN signal, O-RAN signal, DePIN record, or observability output into certification, recognition, finance-readiness, procurement approval, public authority action, public warning, emergency command, provider approval, sponsor entitlement, or enterprise execution authority; or
g) a person authorized to waive privacy, data protection, AI governance, cybersecurity, research ethics, evidence integrity, methods integrity, secure development, public authority boundary controls, finance-boundary controls, certification-boundary controls, procurement-neutrality controls, competition controls, sanctions controls, export-control requirements, controlled-technology restrictions, civil-rights controls, accessibility controls, Tribal or Indigenous protocol controls, protected knowledge controls, validity-by-record, or correctionability.
145.2 Data Governance Oversight Where Delegated. The Chief Data, AI, and Cyber Officer may oversee data governance where delegated. Data governance oversight shall ensure that data used, received, created, derived, transformed, stored, accessed, shared, published, archived, deleted, or otherwise processed by or for the Corporation is governed by lawful authority, public-benefit purpose, role separation, data minimization, security, privacy, provenance, access classification, public-safe publication, safeguards, retention, correction, and records discipline.
Data governance oversight may address:
a) data classification;
b) data ownership and custodianship;
c) data source authorization;
d) source lineage and provenance;
e) lawful basis or lawful authority where applicable;
f) consent, non-consent, withdrawal, restriction, and correction pathways where applicable;
g) data minimization;
h) purpose limitation;
i) access controls;
j) use limitations;
k) sharing limitations;
l) cross-border transfer controls;
m) public authority data controls;
n) rights-bearing data controls;
o) health-sensitive data controls;
p) cyber-sensitive and infrastructure-sensitive data controls;
q) community-protected, Tribal, Indigenous, local, territorial, cultural, environmental, and protected knowledge controls;
r) retention, deletion, sealing, archival, and secure disposal rules;
s) public-safe publication review; and
t) correction, supersession, withdrawal, takedown, and audit trail requirements.
No dataset shall be treated as usable merely because it is available, public, donated, sponsor-provided, provider-provided, public authority-provided, scraped, purchased, AI-generated, inferred, synthetic, anonymized by assertion, dashboard-ready, technically valuable, or useful for public-good purposes. Data shall be used only within its lawful authority, approved purpose, access class, publication class, safeguard class, record support, and correction pathway.
145.3 Privacy Controls Oversight Where Delegated. The Chief Data, AI, and Cyber Officer may oversee privacy controls where delegated. Privacy controls shall be proportionate to the sensitivity, identifiability, rights-bearing nature, source, jurisdiction, lawful basis, participant expectations, public authority context, cross-border context, publication risk, AI-use risk, cyber risk, and safeguard implications of the data or system.
Privacy controls may include:
a) privacy screening;
b) data protection review;
c) personal information classification;
d) sensitive personal information classification;
e) health data classification;
f) children’s, youth, or vulnerable population data classification;
g) public authority personal data review;
h) consent and notice review;
i) de-identification, pseudonymization, aggregation, masking, redaction, generalization, or synthetic data review;
j) re-identification risk review;
k) access restrictions;
l) no-download restrictions;
m) controlled-room restrictions;
n) data processing terms;
o) data sharing terms;
p) retention and deletion controls;
q) breach response integration;
r) public-safe publication review; and
s) correction and complaint pathways.
Privacy shall not be treated as satisfied by a generic notice, dataset label, model card, public-source assertion, technical anonymization claim, aggregation claim, security control, contractual disclaimer, sponsor assurance, provider assurance, or public authority presence where actual risk remains. Where privacy risk cannot be reduced to an acceptable lawful and public-safe level, the activity shall be held, restricted, redesigned, externalized, referred, terminated, withdrawn, or deleted as appropriate.
145.4 AI Governance Oversight Where Delegated. The Chief Data, AI, and Cyber Officer may oversee AI governance where delegated. AI governance shall apply to machine learning systems, foundation models, large language models, multimodal systems, retrieval-augmented systems, classification systems, scoring systems, forecasting systems, simulation systems, digital twin systems, agentic systems, automated workflows, AI-assisted research systems, AI-assisted publication systems, AI-assisted code systems, model evaluation systems, and any other AI-enabled system used by or for the Corporation.
AI governance oversight shall address, as applicable:
a) AI system identity;
b) model identity;
c) model version;
d) system purpose;
e) intended use;
f) prohibited use;
g) data sources;
h) training, fine-tuning, embedding, retrieval, and model-improvement restrictions;
i) prompt, query, retrieval, and inference logging where appropriate;
j) human-review requirements;
k) bias, fairness, discrimination, civil-rights, and accessibility risks;
l) hallucination, fabrication, and unsupported-output risks;
m) privacy, confidentiality, and protected knowledge risks;
n) cybersecurity and adversarial risks;
o) public authority confusion risks;
p) finance, certification, procurement, recognition, public warning, and professional-boundary overclaim risks;
q) validation, verification, evaluation, red-team, and benchmark requirements;
r) limitation language and public-safe notices; and
s) correction, override, rejection, deactivation, rollback, and archive pathways.
No AI system shall be used as a substitute for competent human judgment where material legal, public authority, finance, certification, procurement, safety, research ethics, protected knowledge, civil-rights, accessibility, or public-safe publication consequences may arise. AI systems may support evidence, research, methods, observability, ontology, technical truth, software, learning, and administrative work; they shall not become institutional authority merely because they are accurate in some settings, embedded in workflows, technically advanced, widely used, externally validated, or operationally convenient.
145.5 Model Register Oversight Where Delegated. The Chief Data, AI, and Cyber Officer may oversee the Model Register where delegated. The Model Register shall operate as a structured record of AI models, statistical models, simulation models, scoring models, classification models, retrieval systems, foundation models, digital twin models, benchmark models, evaluation models, and material model configurations used by or for the Corporation.
The Model Register may include, as applicable:
a) model identifier;
b) model name;
c) model provider or source;
d) model version;
e) model owner or custodian;
f) system in which the model is used;
g) intended use;
h) prohibited use;
i) access class;
j) publication class;
k) data source and training / fine-tuning / retrieval notes where known and permitted;
l) model card or equivalent documentation;
m) evaluation status;
n) validation and verification status;
o) red-team status;
p) bias, fairness, civil-rights, accessibility, privacy, cyber, public authority, finance, certification, procurement, recognition, and public-safe risk classification;
q) human-review requirements;
r) logging requirements;
s) incident history;
t) correction, override, restriction, deactivation, supersession, retirement, archive, retention, deletion, and legal hold status; and
u) affected evidence, methods, observability, public authority, GRF, GRA, Nexus, sponsor, provider, host, or enterprise-stack interfaces.
A Model Register entry shall evidence the recorded model status only. It shall not be represented as certification, approval, public authority adoption, finance-readiness, procurement approval, recognition, rating, provider approval, safety guarantee, legality finding, bias-free finding, or operational authorization.
145.6 Inference Records Oversight Where Delegated. The Chief Data, AI, and Cyber Officer may oversee inference records where delegated. Inference records shall be used to preserve traceability, accountability, reproducibility where appropriate, human review, public-safe publication, evidence integrity, and correctionability for material AI outputs.
Inference records may include, as applicable:
a) system identifier;
b) model identifier and version;
c) date and time;
d) user or process initiating the inference;
e) input class;
f) prompt, query, retrieval, or instruction record where appropriate and lawful;
g) retrieval-source record;
h) dataset or evidence references;
i) output record or output hash;
j) human reviewer;
k) review decision;
l) confidence or uncertainty notation where applicable;
m) limitation language;
n) public-safe status;
o) use decision;
p) correction, override, rejection, supersession, withdrawal, deletion, or archive status;
q) privacy and protected knowledge restrictions;
r) public authority boundary notation;
s) finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control notation; and
t) retention, access, legal hold, and metadata.
Inference records shall not be collected or retained in a manner that unlawfully captures personal information, protected knowledge, confidential information, privileged material, public authority restricted material, or cyber-sensitive information beyond authorized scope. Where inference recording conflicts with privacy, confidentiality, security, protected knowledge, or legal restrictions, the Corporation shall adopt a more protective record method, including redaction, hashing, summarized metadata, controlled-room-only review, restricted retention, or non-retention where lawful and appropriate.
145.7 Compute Workload Records Oversight Where Delegated. The Chief Data, AI, and Cyber Officer may oversee compute workload records where delegated. Compute workload records shall support verifiable compute, verifiable intelligence, auditability, cost control, data protection, security, environmental responsibility where adopted, sovereign compute controls, cross-border controls, public authority data controls, and correctionability.
Compute workload records may include, as applicable:
a) workload identifier;
b) workload purpose;
c) initiating person or process;
d) compute environment;
e) cloud, on-premises, sovereign, confidential, enclave, edge, or hybrid compute classification;
f) model, dataset, software, or system used;
g) data classification;
h) access class;
i) jurisdictional or sovereign data zone classification;
j) public authority data status;
k) cyber-sensitive or infrastructure-sensitive data status;
l) protected knowledge status;
m) workload date, duration, and resource class;
n) security configuration;
o) logging status;
p) output record or proof receipt;
q) human-review requirement;
r) incident or anomaly record;
s) correction, revocation, rollback, archive, retention, deletion, or legal hold status; and
t) cost, budget, or grant allocation reference where required.
A compute workload record shall not be treated as proof of correctness, legality, public authority adoption, finance-readiness, certification, procurement approval, recognition, rating, provider approval, or operational authorization. It is a record of compute activity and related controls, not a substantive approval of the output.
145.8 Agentic AI Controls Oversight Where Delegated. The Chief Data, AI, and Cyber Officer may oversee agentic AI controls where delegated. Agentic AI controls shall apply to any AI system capable of tool use, autonomous or semi-autonomous action, workflow execution, repository interaction, data access, external communication, public posting, code generation, code execution, transaction preparation, form completion, scheduling, notification, infrastructure interaction, or other material action beyond passive output generation.
Agentic AI controls shall include, as applicable:
a) approved use-case identification;
b) prohibited use-case identification;
c) tool access controls;
d) identity and credential restrictions;
e) human-in-the-loop requirements;
f) human-on-the-loop monitoring where appropriate;
g) step limits;
h) spending limits;
i) data access limits;
j) repository access limits;
k) publication limits;
l) public authority communication limits;
m) finance, procurement, certification, recognition, and provider-reference limits;
n) external communication approval;
o) audit logs;
p) sandboxing;
q) kill-switch or deactivation pathway;
r) incident escalation; and
s) correction, rollback, revocation, and archive controls.
No agentic AI system shall be permitted to approve Board reserved matters, enter into contracts, make public authority commitments, issue public statements, provide professional advice, conduct securities, investment, lending, insurance, rating, public finance, procurement, certification, or recognition activity, select providers, control emergency response, publish public warnings, release restricted data, expose protected knowledge, bypass human review, or exercise institutional authority without competent human authorization and record support.
145.9 Cybersecurity Program Oversight Where Delegated. The Chief Data, AI, and Cyber Officer may oversee the cybersecurity program where delegated. The cybersecurity program shall protect the Corporation’s systems, repositories, datasets, models, dashboards, controlled rooms, public authority rooms, data rooms, clean rooms, evidence rooms, no-download rooms, software releases, public-good technical assets, credentials, keys, tokens, communications, devices, vendors, cloud environments, and technical interfaces.
Cybersecurity program oversight may include:
a) cybersecurity governance;
b) risk assessment;
c) identity and access management;
d) multi-factor authentication;
e) privileged access management;
f) logging and monitoring;
g) vulnerability management;
h) patch management;
i) endpoint protection;
j) network security;
k) cloud security;
l) application security;
m) repository security;
n) supply-chain security;
o) incident response;
p) business continuity and disaster recovery;
q) backup and restoration;
r) vendor security review;
s) security awareness training; and
t) post-incident review and correction.
Cybersecurity controls shall be proportionate to the sensitivity of the Corporation’s work, including public authority interfaces, infrastructure-sensitive data, cyber-sensitive data, AI systems, protected knowledge, public-safe mapping, technical baselines, repositories, software releases, and controlled-room activities. Technical convenience, publication speed, sponsor pressure, provider pressure, event deadlines, grant timelines, or operational urgency shall not justify bypassing cybersecurity requirements.
145.10 Identity, Access, Logging, Monitoring, Vulnerability, Incident Response, Backup, and Business Continuity Controls. The Chief Data, AI, and Cyber Officer shall support identity, access, logging, monitoring, vulnerability, incident response, backup, and business continuity controls where delegated. Such controls shall ensure that systems and records remain protected, accountable, recoverable, and auditable.
The controls may include:
a) identity verification;
b) account provisioning;
c) role-based access control;
d) least-privilege access;
e) segregation of duties;
f) access review;
g) access revocation;
h) privileged access logging;
i) activity logging;
j) security monitoring;
k) anomaly detection;
l) vulnerability intake;
m) vulnerability prioritization;
n) remediation tracking;
o) incident triage;
p) incident containment;
q) backup scheduling;
r) restoration testing;
s) recovery-time and recovery-point objectives where adopted; and
t) continuity playbooks.
Access shall not be granted merely because a person is senior, technically important, a sponsor representative, a provider representative, a donor representative, a public authority participant, a university partner, a fellow, an advisor, a contractor, a maintainer, or a member of a council or working group. Access shall be authorized, recorded, limited, reviewed, revocable, and proportionate to need.
145.11 Public Authority Data Controls. The Chief Data, AI, and Cyber Officer shall support public authority data controls where delegated. Public authority data includes data received from, generated with, derived from, linked to, displayed for, or used in connection with federal, state, territorial, Tribal, local, public infrastructure, emergency-management, public health, public safety, public works, utility, port, telecom, cyber, energy, water, food, disaster, or other public authority contexts.
Public authority data controls shall address, as applicable:
a) public authority source;
b) participant capacity;
c) official-capacity status;
d) observer status;
e) regulator-listening status;
f) public finance reader status;
g) emergency-management participant status;
h) data contribution authority;
i) public records, FOIA, sunshine, open meetings, procurement, confidentiality, privacy, security, and retention implications;
j) public authority reference review;
k) public-safe publication limits;
l) official-use restrictions;
m) no-public-warning language;
n) no-emergency-command language;
o) no-procurement-approval language;
p) no-regulatory-approval language;
q) no-public-finance-approval language;
r) controlled-room restrictions;
s) correction and notice pathways; and
t) return, deletion, sealing, archive, or legal hold requirements.
No public authority data contribution, meeting attendance, dashboard access, controlled-room participation, public authority reference, data feed, evidence pack, simulation, tabletop, or after-action learning output shall be represented as public authority adoption, public authority decision, official warning, emergency command, procurement approval, funding approval, regulatory approval, sovereign obligation, public finance approval, or public-private partnership unless separately and lawfully authorized by competent public authority and recorded.
145.12 Health, Cyber, Infrastructure, Community-Protected, Tribal / Indigenous, and Protected Knowledge Data Controls. The Chief Data, AI, and Cyber Officer shall support enhanced controls for health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, community-protected data, Tribal or Indigenous data, local or territorial knowledge, cultural knowledge, environmental knowledge, and protected knowledge. Such data shall be treated as higher-risk unless a competent review determines otherwise.
Enhanced controls may include:
a) heightened intake review;
b) lawful authority review;
c) consent, non-consent, withdrawal, and restriction review;
d) community, Tribal, Indigenous, or protected knowledge review;
e) civil-rights and accessibility review;
f) public-safe mapping review;
g) data minimization;
h) controlled-room access;
i) no-download access;
j) encryption;
k) separation from general repositories;
l) restricted AI use;
m) restriction on training, fine-tuning, embedding, retrieval, or model improvement;
n) redaction, aggregation, masking, or synthetic substitution;
o) public-safe publication hold;
p) takedown and correction pathway;
q) grievance and remedy pathway;
r) deletion, sealing, return, or archive pathway; and
s) independent review where required.
Protected knowledge shall not be extracted, modeled, mapped, published, reused, commercialized, transferred, or exposed for sponsor convenience, provider convenience, donor convenience, public authority convenience, research convenience, dashboard completeness, technical curiosity, AI training, benchmarking, media value, or institutional reputation. Where protected knowledge rules conflict with technical completeness, protected knowledge controls shall prevail.
145.13 Cross-Border Transfer and Sovereign Data Zone Support. The Chief Data, AI, and Cyber Officer may support cross-border transfer and sovereign data zone controls where delegated. Cross-border transfer and sovereign data zone support shall apply to data, models, compute workloads, repositories, backups, logs, public authority data, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, Tribal or Indigenous data, protected knowledge, and technical systems that cross or may be accessed across jurisdictional boundaries.
Cross-border and sovereign data controls may address:
a) source jurisdiction;
b) destination jurisdiction;
c) access jurisdiction;
d) storage location;
e) compute location;
f) backup location;
g) support personnel location;
h) cloud provider location;
i) public authority restrictions;
j) data localization requirements;
k) cross-border transfer lawful basis;
l) contractual transfer controls;
m) encryption and key location;
n) sovereign compute requirements;
o) controlled-room localization;
p) GCRI Canada interface controls;
q) Mexico, Caribbean, Arctic, Indigenous, regional, and international interface controls;
r) conflict-of-law escalation;
s) compatibility notes and divergence logs; and
t) suspension, compartmentalization, separate instrument, re-routing, deletion, or localization where required.
No cross-border data, AI, cyber, compute, repository, or dashboard arrangement shall be treated as lawful merely because it is technically feasible, cloud-enabled, sponsor-requested, provider-supported, public authority-facing, publicly available, or aligned with North America anchor objectives. Cross-border arrangements shall be reviewed under the most protective lawful posture where ambiguity exists.
145.14 AI Incident and Cyber Incident Escalation. The Chief Data, AI, and Cyber Officer shall support escalation of AI incidents and cyber incidents within delegated authority and in coordination with the relevant officers, committees, counsel, compliance function, safeguards function, public authority interface function, technology function, Board, and external authorities where required by law or competent record.
AI incidents and cyber incidents may include:
a) unauthorized access;
b) data breach;
c) credential, key, token, or secret exposure;
d) model misuse;
e) agentic AI misuse;
f) hallucination causing material risk;
g) automated public authority overclaim;
h) automated finance, certification, procurement, recognition, provider-preference, or public warning overclaim;
i) biased, discriminatory, inaccessible, or rights-impairing model output;
j) privacy exposure;
k) protected knowledge exposure;
l) public-safe mapping exposure;
m) prompt injection;
n) model extraction;
o) data poisoning;
p) malware or malicious contribution;
q) repository compromise;
r) dashboard compromise;
s) public authority data misuse;
t) cyber-sensitive or infrastructure-sensitive data exposure;
u) AI-RAN, O-RAN, DePIN, DLT, blockchain, digital twin, sensor, geospatial, Earth observation, or observability-interface compromise; and
v) vendor, provider, cloud, or supply-chain compromise.
Incident escalation may require hold, access restriction, repository freeze, model freeze, inference freeze, compute freeze, dashboard freeze, controlled-room lockdown, key rotation, credential revocation, patching, rollback, takedown, public-safe notice, controlled notice, public authority notice where required, affected-person notice where required, donor or funder notice where required, GRF or GRA interface notice where appropriate, Board notice, legal review, forensic review, correction, supersession, withdrawal, archive, and post-incident review.
145.15 No AI, Compute, Cyber Tool, Dashboard, Digital Twin, DePIN, Ledger, or Signal as Authority. No AI system, model output, inference record, compute workload record, verifiable compute workflow, cyber tool, cybersecurity score, dashboard, digital twin, DePIN record, DLT record, blockchain or ledger entry, proof receipt, smart contract, role key, AI-RAN signal, O-RAN signal, sensor signal, geospatial output, Earth observation output, cyber telemetry, anomaly flag, automated risk class, confidence label, public authority data feed, or observability output used by or associated with the Corporation shall be represented or used as legal authority, regulatory approval, public authority decision, public authority adoption, public warning, emergency command, evacuation instruction, operational instruction, procurement approval, vendor selection, certification, accreditation, recognition, standing determination, maturity determination, Nexus-compatible public status, Docket approval, Grid guarantee, finance-readiness determination, insurance-readiness determination, capital-readability determination, bankability determination, investability determination, credit opinion, rating, investment recommendation, underwriting basis, lending basis, public finance approval, provider approval, sponsor entitlement, or enterprise execution authority.
This limitation applies regardless of whether the system or output is:
a) technically sophisticated;
b) validated for a limited use;
c) audited for a limited use;
d) generated in a secure environment;
e) recorded in a register;
f) supported by a proof receipt;
g) referenced by a ledger;
h) shown on a dashboard;
i) generated through sovereign compute;
j) used in a controlled room;
k) reviewed by a public authority participant;
l) supported by a sponsor, provider, funder, host, university, laboratory, or partner;
m) connected to Nexus Observatory, Nexus Truth Engine, Nexus Standards, Nexus Grid, Nexus Rails, Nexus Universe, or Nexus Academy activity; or
n) used to support GRF-facing or GRA-facing inputs.
Where an automated or technical output is likely to be misunderstood as authority, the Chief Data, AI, and Cyber Officer shall support limitation language, controlled vocabulary correction, non-reliance notices, access restriction, human review, publication hold, public-safe review, reclassification, re-scoping, referral to competent authority, withdrawal, correction, rollback, takedown, deactivation, or archive.
145.16 Chief Data, AI, and Cyber Officer Records. The Corporation shall maintain Chief Data, AI, and Cyber Officer Records sufficient to demonstrate the Chief Data, AI, and Cyber Officer’s appointment, term, eligibility, authority, delegations, data governance oversight, privacy control oversight, AI governance oversight, Model Register oversight, inference record oversight, compute workload record oversight, agentic AI controls, cybersecurity program oversight, identity and access controls, logging and monitoring controls, vulnerability management, incident response, backup, business continuity, public authority data controls, health-sensitive data controls, cyber-sensitive data controls, infrastructure-sensitive data controls, community-protected data controls, Tribal / Indigenous data controls, protected knowledge data controls, cross-border transfer controls, sovereign data zone support, AI incident escalation, cyber incident escalation, automated-output boundary controls, conflicts, recusals, restrictions, succession, and closeout.
Chief Data, AI, and Cyber Officer Records shall include, as applicable:
a) appointment or election record;
b) term and renewal record;
c) eligibility, consent, fit-and-proper, integrity, conflict, independence, sanctions, export-control, controlled-technology, data governance, AI governance, cybersecurity, privacy, research integrity, evidence integrity, methods integrity, public authority boundary, finance-boundary, certification-boundary, procurement-neutrality, recognition-boundary, provider-neutrality, sponsor non-control, safeguards, civil-rights, accessibility, Tribal and Indigenous protocol, and protected knowledge screening records;
d) duty acknowledgment and certification of understanding;
e) role description;
f) reporting line;
g) authority matrix entry;
h) separate delegations;
i) data classification records;
j) dataset register records;
k) data access records;
l) data sharing records;
m) privacy review records;
n) data protection review records;
o) consent, non-consent, withdrawal, restriction, complaint, correction, deletion, sealing, retention, archive, and legal hold records;
p) AI system records;
q) Model Register records;
r) model card, dataset card, system card, benchmark card, evaluation harness, red-team, validation, verification, bias, fairness, civil-rights, accessibility, public-safe, and human-review records;
s) inference records;
t) compute workload records;
u) verifiable compute, secure enclave, confidential computing, sovereign compute, compute-to-data, and proof-receipt records;
v) agentic AI control records;
w) cybersecurity governance records;
x) identity, access, logging, monitoring, vulnerability, patching, endpoint, network, cloud, application, repository, supply-chain, backup, disaster recovery, and business continuity records;
y) incident records, including AI incident, cyber incident, privacy incident, data breach, model incident, repository incident, dashboard incident, public authority data incident, protected knowledge incident, and public-safe mapping incident records;
z) public authority data, official-capacity, observer, regulator-listening, public finance reader, emergency-management participant, public infrastructure operator, public authority reference, controlled-room, data-room, clean-room, evidence-room, and no-download-room records;
aa) health-sensitive, cyber-sensitive, infrastructure-sensitive, community-protected, Tribal, Indigenous, local, territorial, cultural, environmental, protected knowledge, civil-rights, accessibility, and public-safe mapping data records;
bb) cross-border transfer, sovereign data zone, GCRI Canada interface, North America interface, foreign access, cloud location, backup location, support-personnel location, compatibility note, divergence log, and conflict-of-law escalation records;
cc) AI-RAN, O-RAN, DePIN, DLT, blockchain, digital twin, sensor, geospatial, Earth observation, cyber telemetry, observability, Truth Engine, dashboard, and automated-output boundary records;
dd) escalations involving public authority boundary, finance boundary, certification boundary, procurement neutrality, recognition boundary, provider neutrality, sponsor non-control, data / AI / cyber, safeguards, protected knowledge, civil rights, accessibility, competition, sanctions, export-control, controlled technology, public-safe publication, professional boundary, or legal risk;
ee) conflicts, recusals, access restrictions, delegation restrictions, resignation, removal, handover, access revocation, and closeout records; and
ff) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that the Chief Data, AI, and Cyber Officer safeguards data, AI, compute, cyber, privacy, and automated-output integrity, not external authority. Data, AI systems, model registers, inference records, compute workload records, cyber controls, dashboards, digital twins, proof receipts, ledgers, sensors, AI-RAN signals, O-RAN signals, DePIN records, DLT records, blockchain references, observability outputs, and automated scores may support evidence, methods, research, observability, ontology, technical truth, public-good software, public authority learning, safeguards, GRF-facing inputs, GRA-facing technical inputs, Nexus Docket support, Nexus Grid support, and public-safe publication, but they do not become certification, recognition, finance-readiness, procurement approval, public authority action, public warning, emergency command, rating, provider approval, sponsor entitlement, or enterprise execution by virtue of being generated, logged, secured, verified, computed, visualized, ledger-referenced, or technically credible. Data, AI, and cyber stewardship is lawful, secure, privacy-respecting, rights-respecting, bounded, record-supported, human-reviewable where material, public-safe, non-executing, role-separated, and correctionable.
Section 146. Chief Public-Good Software and Technical Assets Officer
146.1 Chief Public-Good Software and Technical Assets Officer Role. The Chief Public-Good Software and Technical Assets Officer, where such office is approved by the Board, shall serve as the principal public-good software, public-good technical asset, open technical baseline, technical asset register, contributor-governance, repository-stewardship, open-source-governance, public-good licensing, chain-of-title, secure-release, SBOM, signing, provenance, dependency, vulnerability, rollback, fork-review, compatibility-claim, Nexus-compatible-claim, anti-enclosure, commercial-use-boundary, takedown, correction, deprecation, retirement, and archive officer of the Corporation, subject at all times to applicable law, the Articles or Certificate, this Bylaw, Board resolutions, Board-approved policies, the delegation matrix, the authority matrix, approved budget, research integrity controls, evidence controls, methods controls, data / AI / cyber controls, privacy controls, secure-development controls, public authority boundary controls, finance-boundary controls, certification-boundary controls, procurement-neutrality controls, provider-neutrality controls, sponsor non-control controls, intellectual-property controls, safeguards, protected knowledge restrictions, controlled vocabulary, validity-by-record, and correctionability.
The Chief Public-Good Software and Technical Assets Officer’s office exists to preserve the lawful, secure, interoperable, maintainable, open-where-appropriate, restricted-where-necessary, public-benefit, public-safe, non-executing, auditable, versioned, anti-enclosure, and correctionable stewardship of public-good software and technical assets developed, received, adapted, maintained, released, licensed, contributed, forked, referenced, deprecated, retired, or archived by or for the Corporation.
The Chief Public-Good Software and Technical Assets Officer shall not, by title, authorship, maintainership, repository control, release responsibility, software expertise, technical centrality, open-source leadership, licensing authority, technical asset custody, or public-good stewardship alone, be treated as:
a) a substitute Board;
b) a person authorized to approve Board reserved matters;
c) a regulator, public authority, public warning authority, emergency command authority, procurement authority, public finance authority, certification authority, recognition authority, standards authority, protocol authority, finance-readiness authority, rating authority, insurance-readiness authority, capital-readability authority, or enterprise execution actor;
d) a person authorized to make final legal, intellectual-property, engineering, cybersecurity, public safety, public health, telecom, financial, insurance, underwriting, lending, procurement, emergency-management, operational, certification, recognition, or finance-readiness determinations;
e) a person authorized to bind 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, communities, Indigenous knowledge holders, contributors, maintainers, funders, or enterprise-stack actors;
f) a person authorized to convert a software release, technical asset, open technical baseline, reference implementation, repository, schema, API, SDK, dashboard, test harness, gold vector, negative test, benchmark asset, public-good license, proof receipt, role key, smart license, fork, compatibility note, Nexus-compatible claim, AI-RAN interface, O-RAN interface, DePIN artifact, DLT artifact, blockchain reference, digital twin asset, sensor artifact, cyber tool, geospatial tool, or observability asset into certification, recognition, finance-readiness, procurement approval, public authority action, public warning, emergency command, provider approval, sponsor entitlement, or enterprise execution authority; or
g) a person authorized to waive intellectual-property review, licensing controls, contributor controls, secure-release controls, repository controls, software supply-chain controls, data / AI / cyber controls, public authority boundary controls, finance-boundary controls, certification-boundary controls, procurement-neutrality controls, provider-neutrality controls, sponsor non-control controls, competition controls, sanctions controls, export-control requirements, controlled-technology restrictions, civil-rights controls, accessibility controls, Tribal or Indigenous protocol controls, protected knowledge controls, validity-by-record, or correctionability.
146.2 Public-Good Technical Asset Register Support. The Chief Public-Good Software and Technical Assets Officer may support, oversee, or coordinate the Public-Good Technical Asset Register where delegated. The Public-Good Technical Asset Register shall operate as a structured record of public-good software, open technical baselines, schemas, APIs, SDKs, dashboards, data tools, reference architectures, technical profiles, repositories, model-support artifacts, evaluation harnesses, benchmark libraries, test vectors, gold vectors, negative tests, documentation assets, public-good templates, controlled technical playbooks, digital twins, observability tools, AI-RAN or O-RAN interface artifacts, DePIN or DLT artifacts, blockchain reference artifacts, cyber tools, geospatial tools, sensor artifacts, proof-receipt artifacts, role-key artifacts, smart-license artifacts, and related technical assets.
The Public-Good Technical Asset Register may include, as applicable:
a) asset identifier;
b) asset title;
c) asset class;
d) asset purpose;
e) asset custodian;
f) responsible officer or maintainer;
g) repository location;
h) version;
i) status;
j) approval authority;
k) effective date;
l) review date;
m) license status;
n) IP provenance and chain-of-title status;
o) contributor history;
p) access class;
q) publication class;
r) intended use;
s) prohibited use;
t) data / AI / cyber / privacy classification;
u) public authority boundary classification;
v) finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control classifications;
w) safeguards and protected knowledge classification;
x) secure-release status;
y) vulnerability status;
z) correction, supersession, deprecation, withdrawal, takedown, retirement, archive, legal hold, retention, deletion, and metadata status; and
aa) affected Nexus, GRF, GRA, GCRI Canada, public authority, consortium, national company, Project SPV, provider, host, sponsor, contributor, maintainer, or enterprise-stack interface.
A Public-Good Technical Asset Register entry shall evidence the recorded asset status only. It shall not be represented as certification, recognition, standards-conformance approval, procurement approval, finance-readiness, insurance-readiness, public authority adoption, rating, provider approval, sponsor endorsement, legal compliance approval, operational approval, or Nexus-wide approval unless a competent body has separately and lawfully created such authority and the relevant record identifies the competent authority, scope, date, and limitation.
146.3 Public-Good Software Stewardship. The Chief Public-Good Software and Technical Assets Officer may support public-good software stewardship where delegated. Public-good software stewardship shall govern software developed, maintained, released, contributed, adapted, documented, forked, packaged, distributed, deprecated, retired, withdrawn, or archived by or for the Corporation in furtherance of its evidence, methods, observability, ontology, technical truth, public-good R&D, verifiable compute, public authority learning, public-safe publication, safeguards, open technical baseline, and Nexus-compatible public-good purposes.
Public-good software stewardship may address:
a) software purpose;
b) approved scope;
c) excluded scope;
d) user class;
e) access class;
f) publication class;
g) repository governance;
h) maintainer governance;
i) contribution workflow;
j) code review;
k) documentation;
l) license selection;
m) dependency review;
n) secure-development review;
o) SBOM generation;
p) artifact signing;
q) provenance record;
r) release notes;
s) vulnerability disclosure and remediation;
t) rollback, takedown, correction, deprecation, retirement, and archive pathways.
Public-good software shall be stewarded as a public-benefit technical asset and not as a certification scheme, procurement scheme, provider-selection scheme, regulated product approval, public authority system, public warning system, emergency command system, finance-readiness tool, insurance-readiness tool, rating tool, legal compliance tool, or enterprise execution platform. A release may support learning, interoperability, evidence discipline, and technical baselines; it shall not create external authority merely because it is useful, public, open, signed, widely adopted, referenced in a Nexus context, or supported by sponsors, providers, public authorities, universities, laboratories, or contributors.
146.4 Open Technical Baseline Stewardship. The Chief Public-Good Software and Technical Assets Officer may support open technical baseline stewardship where delegated. Open technical baselines may describe public-good reference architectures, interoperability patterns, schemas, APIs, SDKs, data dictionaries, observability patterns, secure-release patterns, AI governance patterns, cyber baselines, dashboard patterns, digital twin patterns, AI-RAN and O-RAN interface patterns, DePIN / DLT / blockchain reference patterns, edge-compute patterns, sovereign compute patterns, geospatial patterns, Earth observation patterns, sensor patterns, proof-receipt patterns, and related technical profiles.
Open technical baseline stewardship shall ensure that each material baseline identifies, as applicable:
a) title, short title, version, custodian, status, effective date, review date, supersession status, archive status, and repository location;
b) intended use, prohibited uses, audience, access class, publication class, and reliance limitations;
c) scope, excluded scope, assumptions, dependencies, interoperability boundaries, technical requirements, security requirements, privacy requirements, AI requirements, cyber requirements, data requirements, hardware requirements, software requirements, network requirements, and validation requirements;
d) evidence, methods, source-lineage, auditability, logging, provenance, correction, challenge, supersession, withdrawal, and retirement requirements;
e) public authority boundary, public warning boundary, emergency command boundary, finance boundary, procurement boundary, certification boundary, recognition boundary, provider-neutrality boundary, sponsor non-control boundary, and safeguards boundary; and
f) relationship to 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, universities, laboratories, communities, and enterprise-stack actors.
No open technical baseline shall be represented as law, regulation, public authority adoption, certification, accreditation, procurement requirement, provider approval, finance-readiness determination, insurance-readiness determination, rating, public warning, emergency command, operational authorization, or enterprise execution mandate unless a separate competent authority lawfully creates and records that status.
146.5 Contributor Governance Support. The Chief Public-Good Software and Technical Assets Officer may support contributor governance where delegated. Contributor governance shall apply to individuals and institutions contributing code, schemas, datasets, documentation, benchmarks, test vectors, evaluation harnesses, dashboards, user-interface materials, security reports, vulnerability reports, threat-intelligence materials, observability methods, AI-RAN interface materials, O-RAN interface materials, DePIN materials, DLT materials, blockchain reference materials, geospatial materials, sensor methods, digital twin materials, or related technical assets.
Contributor governance may include:
a) contributor eligibility review;
b) identity or institutional affiliation verification where appropriate;
c) sanctions, export-control, controlled-technology, and national security sensitivity review;
d) conflict disclosure;
e) sponsor, provider, employer, funder, public authority, university, laboratory, host, or enterprise affiliation disclosure;
f) contributor terms;
g) contributor license agreement or assignment instrument;
h) moral-rights treatment where applicable;
i) IP provenance review;
j) data rights review;
k) privacy and protected knowledge review;
l) secure-development review;
m) code-review and maintainer-review routing;
n) attribution and public reference controls;
o) confidentiality and controlled-room obligations;
p) competition and antitrust discipline;
q) rejection, quarantine, modification, acceptance, withdrawal, takedown, or correction pathways; and
r) contributor offboarding, access revocation, and record retention.
No contributor shall acquire governance authority, maintainer authority, public authority interface authority, certification authority, recognition authority, finance-readiness authority, procurement authority, provider approval authority, sponsor entitlement, or enterprise execution authority merely by making, funding, maintaining, reviewing, or promoting a contribution. Contribution acceptance shall not imply endorsement of a contributor, sponsor, provider, employer, product, jurisdiction, project, public authority, commercial offering, financing structure, or enterprise actor.
146.6 Open-Source and Public-Good Licensing Support. The Chief Public-Good Software and Technical Assets Officer may support open-source and public-good licensing where delegated and in coordination with legal, compliance, tax, intellectual-property, data, AI, cyber, safeguards, and Board review where required. Licensing shall be structured to advance the Corporation’s public-benefit purposes, public-good software mission, anti-enclosure discipline, interoperability aims, public-safe publication obligations, and correctionability while preserving lawful restrictions where openness would create unacceptable risk.
Licensing support may address:
a) open-source license selection;
b) public-good license selection;
c) permissive license review;
d) copyleft license review;
e) restricted license review;
f) non-public controlled license review;
g) data license review;
h) documentation license review;
i) model, benchmark, evaluation, and dataset terms;
j) patent, defensive publication, standards-essential, royalty, and non-assert considerations;
k) third-party license compatibility;
l) dependency license compatibility;
m) contributor license agreement review;
n) chain-of-title review;
o) attribution requirements;
p) trademark, mark, logo, badge, seal, and naming restrictions;
q) export-control, sanctions, controlled-technology, cybersecurity, privacy, and protected knowledge restrictions;
r) commercial use boundaries; and
s) termination, withdrawal, takedown, correction, and archive provisions.
Open-source status shall not be used to weaken data protection, privacy, cybersecurity, protected knowledge, public authority confidentiality, public-safe mapping, export-control, sanctions, controlled-technology, civil-rights, accessibility, or safeguards requirements. Public-good licensing shall not be represented as certification, public authority approval, procurement approval, provider approval, finance-readiness, recognition, rating, or operational authorization.
146.7 IP Chain-of-Title Support. The Chief Public-Good Software and Technical Assets Officer may support intellectual-property chain-of-title controls where delegated. Chain-of-title controls shall be used to establish, preserve, document, and correct the lawful rights, permissions, licenses, assignments, contributor grants, authorship records, ownership records, third-party restrictions, public-domain claims, open-license claims, database-rights implications, moral-rights implications, patent implications, trade secret implications, and public-good stewardship obligations applicable to technical assets.
IP chain-of-title support may include:
a) author and contributor identification;
b) institutional contributor identification;
c) employment or contractor ownership review;
d) university, laboratory, public authority, sponsor, provider, host, funder, or partner rights review;
e) assignment and license documentation;
f) contributor license agreement administration;
g) third-party dependency review;
h) dataset rights review;
i) model and benchmark rights review;
j) documentation and media rights review;
k) patent and defensive publication review;
l) trademark and naming review;
m) open-source license compatibility review;
n) restricted-material review;
o) provenance record maintenance;
p) unauthorized contribution review;
q) infringement-risk escalation;
r) correction, removal, replacement, quarantine, withdrawal, takedown, or archive; and
s) records of unresolved rights limitations.
No technical asset shall be released, relicensed, transferred, commercialized, integrated, contributed to a third-party repository, published as a baseline, used as a reference implementation, or held out as a public-good asset where chain-of-title is materially uncertain unless the uncertainty is recorded, limited, approved within lawful authority, and controlled through restriction, quarantine, disclaimer, or counsel-reviewed pathway.
146.8 Secure Release, SBOM, Signing, Provenance, Dependency, Vulnerability, Rollback, and Repository Discipline Support. The Chief Public-Good Software and Technical Assets Officer shall support secure release and repository discipline where delegated. Secure release discipline shall apply to software, packages, containers, schemas, APIs, SDKs, dashboards, data tools, technical baselines, documentation bundles, benchmark assets, model-support assets, test harnesses, proof-receipt tools, observability tools, AI-RAN / O-RAN interface artifacts, DePIN / DLT / blockchain reference artifacts, digital twin artifacts, cyber tools, geospatial tools, and related technical releases.
Secure release support may include:
a) release readiness review;
b) maintainer approval;
c) branch protection;
d) code review;
e) dependency review;
f) license review;
g) vulnerability scanning;
h) secret, token, key, and credential scanning;
i) SBOM generation;
j) artifact signing;
k) provenance attestation;
l) release notes;
m) public-safe documentation review;
n) version tagging;
o) rollback plan;
p) vulnerability disclosure pathway;
q) emergency patch process;
r) takedown pathway;
s) archive pathway; and
t) post-release correction review.
No release shall proceed merely because of sponsor deadlines, provider deadlines, public authority event timing, grant milestones, media pressure, demonstration needs, repository popularity, contributor expectation, competitive pressure, technical convenience, or operational urgency. Where secure release requirements are not satisfied, the release shall be held, restricted, re-scoped, quarantined, withdrawn, rolled back, or escalated.
146.9 Fork and Compatibility Claim Review Support. The Chief Public-Good Software and Technical Assets Officer may support fork and compatibility claim review where delegated. Fork and compatibility claim review shall apply to any third-party fork, internal fork, experimental fork, implementation, derivative work, adaptation, localization, integration, module, plug-in, extension, distribution, dashboard, deployment package, reference implementation, or related technical asset that uses, references, extends, or claims compatibility with the Corporation’s public-good software, technical assets, open technical baselines, schemas, APIs, SDKs, profiles, or repositories.
Fork and compatibility claim review may address:
a) fork identity;
b) fork owner;
c) repository location;
d) license compliance;
e) attribution compliance;
f) security posture;
g) divergence from upstream;
h) data / AI / cyber controls;
i) privacy controls;
j) public authority boundary controls;
k) finance, certification, procurement, recognition, provider-neutrality, and sponsor non-control limitations;
l) safeguards and protected knowledge implications;
m) public-safe language;
n) use of names, marks, logos, badges, seals, labels, and Nexus-compatible references;
o) version compatibility;
p) technical compatibility;
q) compatibility notes;
r) divergence logs;
s) correction, withdrawal, takedown, or disclaimer requirements; and
t) public or controlled clarification where needed.
No fork, derivative work, integration, reference implementation, compatibility statement, badge, label, repository note, proof receipt, role key, smart license, public statement, technical demonstration, or third-party publication shall be allowed to imply certification, recognition, finance-readiness, procurement approval, public authority adoption, provider preference, sponsor endorsement, GCRI US approval, GRF recognition, GRA determination, or Nexus-wide status unless separately and lawfully authorized by competent authority and recorded.
146.10 Nexus-Compatible Claim Boundary Support. The Chief Public-Good Software and Technical Assets Officer may support Nexus-compatible claim boundary review where delegated. Nexus-compatible claim boundary review shall ensure that references to Nexus compatibility, Nexus-aligned architecture, Nexus Observatory compatibility, Nexus Standards support, Nexus Grid support, Nexus Docket support, Nexus Rails support, Nexus Universe use, Nexus Academy use, Nexus Competence Cell use, GRF-facing input support, or GRA-facing technical input support are accurate, limited, recorded, public-safe, and not authority-inflating.
Nexus-compatible claim boundary support may include review of:
a) technical compatibility claims;
b) interoperability claims;
c) schema compatibility claims;
d) API compatibility claims;
e) dashboard compatibility claims;
f) proof-receipt compatibility claims;
g) technical baseline compatibility claims;
h) public-good software compatibility claims;
i) Nexus Observatory interface claims;
j) Nexus Standards support claims;
k) Nexus Docket or Grid support claims;
l) GRF-facing input support claims;
m) GRA-facing technical input support claims;
n) provider or host use claims;
o) sponsor acknowledgment claims;
p) public authority use or participation claims;
q) state, territorial, Tribal, local, North America, or cross-border interface claims;
r) limitation language;
s) controlled vocabulary; and
t) correction, withdrawal, takedown, or public clarification.
“Nexus-compatible,” “Nexus-aligned,” “Nexus-ready,” “Nexus-integrated,” “Docket-supporting,” “Grid-supporting,” “GRF-facing,” “GRA-facing,” or similar language shall not be used as a proxy for certification, recognition, finance-readiness, insurance-readiness, rating, procurement approval, public authority adoption, provider approval, sponsor entitlement, capital-readability determination, or enterprise execution authority. Any such claim shall be bounded by the specific technical scope, version, competent record, limitation, and responsible authority.
146.11 Anti-Enclosure Controls Support. The Chief Public-Good Software and Technical Assets Officer may support anti-enclosure controls where delegated. Anti-enclosure controls shall protect the Corporation’s public-good software, open technical baselines, public-good technical assets, schemas, APIs, SDKs, dashboards, reference architectures, documentation, test harnesses, benchmarks, public-good datasets where lawful, and other public-good technical assets from capture, privatization, exclusive control, sponsor lock-in, provider lock-in, patent ambush, restrictive relicensing, standards capture, data enclosure, interoperability foreclosure, or public-good mission drift.
Anti-enclosure controls may include:
a) license selection;
b) open repository governance;
c) public-good stewardship clauses;
d) non-exclusive licensing;
e) defensive publication;
f) patent and standards-essential-rights review;
g) trademark and name-use restrictions;
h) fork transparency;
i) compatibility notes;
j) public-good contribution terms;
k) sponsor non-control terms;
l) provider-neutrality terms;
m) anti-lock-in architecture;
n) portability requirements;
o) open schema publication where safe;
p) controlled openness where full openness creates harm;
q) public-safe publication review;
r) commercial-use boundary review;
s) corrective action for enclosure attempts; and
t) withdrawal, takedown, or public clarification where misuse occurs.
Anti-enclosure does not require unsafe openness. The Corporation may restrict, delay, redact, compartmentalize, license narrowly, or withhold technical assets where publication or unrestricted reuse would create unacceptable privacy, cyber, protected knowledge, public authority, infrastructure, export-control, sanctions, controlled-technology, civil-rights, accessibility, public-safe mapping, or community harm risk.
146.12 Commercial Use Boundary Support. The Chief Public-Good Software and Technical Assets Officer may support commercial use boundary review where delegated. Commercial use boundary review shall ensure that public-good software and technical assets are not used, marketed, packaged, sublicensed, embedded, white-labeled, resold, integrated, or referenced in a manner that misstates the Corporation’s role, creates public authority confusion, implies certification, implies recognition, implies finance-readiness, implies procurement approval, creates provider preference, creates sponsor entitlement, undermines anti-enclosure controls, violates license terms, or converts public-good stewardship into enterprise execution.
Commercial use boundary review may address:
a) permissible commercial use under applicable license;
b) prohibited commercial use;
c) attribution requirements;
d) name and mark restrictions;
e) public claim restrictions;
f) public authority reference restrictions;
g) provider neutrality;
h) sponsor non-control;
i) no-certification language;
j) no-recognition language;
k) no-finance-readiness language;
l) no-procurement-approval language;
m) no-public-warning or emergency-command language;
n) no-warranty, no-reliance, and limitation language;
o) sublicensing and redistribution controls;
p) hosted-service and software-as-a-service implications;
q) derivative work and fork obligations;
r) audit, notice, correction, takedown, or termination rights; and
s) legal escalation where misuse occurs.
Commercial use shall not be treated as improper merely because a public-good asset is useful to enterprise actors, providers, hosts, sponsors, national companies, Project SPVs, public authorities, universities, laboratories, or capital readers. The governing rule is that lawful use may occur within license, boundary, and public-safe controls, but no user may convert the Corporation’s public-good technical asset into a false endorsement, procurement advantage, certified product, finance-readiness signal, recognition status, public authority approval, or execution mandate.
146.13 Technical Asset Takedown, Correction, Deprecation, Retirement, and Archive Support. The Chief Public-Good Software and Technical Assets Officer shall support technical asset takedown, correction, deprecation, retirement, and archive where delegated. Such measures shall be available where a technical asset is inaccurate, unsafe, stale, vulnerable, insecure, unlawfully sourced, improperly licensed, chain-of-title defective, privacy-infringing, AI-governance-defective, cyber-risk-amplifying, public-authority-confusing, finance-overclaiming, certification-overclaiming, procurement-overclaiming, recognition-overclaiming, provider-preferential, sponsor-controlled, protected-knowledge-exposing, community-harming, inaccessible, discriminatory, contrary to public-safe publication, or inconsistent with this Bylaw.
Technical asset corrective measures may include:
a) issue notice;
b) security advisory;
c) repository hold;
d) access restriction;
e) release freeze;
f) version correction;
g) documentation correction;
h) license correction;
i) attribution correction;
j) dependency replacement;
k) key or credential rotation;
l) vulnerability patch;
m) rollback;
n) takedown;
o) quarantine;
p) deprecation;
q) supersession;
r) retirement;
s) archive; and
t) public or controlled clarification where required.
Corrective action shall identify affected users, affected repositories, affected releases, affected registers, affected dashboards, affected datasets, affected models, affected public authority materials, affected GRF-facing or GRA-facing inputs, affected Nexus Docket or Grid support materials, affected compatibility claims, notice requirements, transition rules, and archive status where applicable. No technical asset shall remain in current use merely because correction is inconvenient, reputationally sensitive, sponsor-sensitive, provider-sensitive, public authority-sensitive, technically difficult, or operationally disruptive.
146.14 No Public-Good Asset as Certification, Procurement Approval, Provider Preference, or Public Authority Decision. No public-good software, open technical baseline, technical profile, reference architecture, schema, API, SDK, dashboard, data tool, repository, model-support artifact, test harness, gold vector, negative test, benchmark asset, proof-receipt artifact, role-key artifact, smart-license artifact, digital twin, AI-RAN interface artifact, O-RAN interface artifact, DePIN artifact, DLT artifact, blockchain reference, cyber tool, geospatial tool, sensor artifact, observability tool, documentation asset, public-good license, or related technical asset of the Corporation, and no act of the Chief Public-Good Software and Technical Assets Officer, shall be represented or used as certification, accreditation, standards-conformance approval, procurement approval, vendor selection, preferred provider status, public authority decision, public authority adoption, public warning, emergency command, regulatory approval, legal compliance approval, finance-readiness determination, insurance-readiness determination, capital-readability determination, bankability determination, investability determination, credit opinion, rating, investment recommendation, underwriting basis, lending basis, public finance approval, recognition, standing determination, maturity determination, Docket approval, Grid guarantee, Nexus-compatible public status, sponsor entitlement, or enterprise execution authority.
This limitation applies regardless of whether the asset is:
a) open source;
b) public-good-branded;
c) widely adopted;
d) used by a provider;
e) used by a sponsor;
f) used by a host;
g) referenced by a public authority participant;
h) reviewed by an expert panel;
i) included in a repository;
j) included in a controlled room;
k) included in a public authority learning room;
l) supported by a proof receipt;
m) referenced by a ledger;
n) mapped to a technical baseline;
o) connected to Nexus Observatory, Nexus Standards, Nexus Network, Nexus Truth Engine, Nexus Grid, Nexus Rails, Nexus Universe, Nexus Academy, or Nexus Competence Cell activity;
p) used to support GRF-facing or GRA-facing inputs; or
q) validated, tested, signed, benchmarked, documented, or published.
Where a public-good asset is likely to be misunderstood as external authority, the Chief Public-Good Software and Technical Assets Officer shall support controlled vocabulary correction, limitation language, non-reliance notices, release notes, access restriction, publication hold, public-safe review, reclassification, re-scoping, referral to competent authority, withdrawal, correction, rollback, takedown, deprecation, retirement, or archive.
146.15 Chief Public-Good Software and Technical Assets Officer Records. The Corporation shall maintain Chief Public-Good Software and Technical Assets Officer Records sufficient to demonstrate the Chief Public-Good Software and Technical Assets Officer’s appointment, term, eligibility, authority, delegations, Public-Good Technical Asset Register support, public-good software stewardship, open technical baseline stewardship, contributor governance support, open-source and public-good licensing support, IP chain-of-title support, secure release support, SBOM support, signing support, provenance support, dependency review support, vulnerability review support, rollback support, repository discipline, fork and compatibility claim review support, Nexus-compatible claim boundary support, anti-enclosure controls support, commercial use boundary support, technical asset takedown, correction, deprecation, retirement, archive support, public-good asset boundary controls, conflicts, recusals, restrictions, succession, and closeout.
Chief Public-Good Software and Technical Assets Officer Records shall include, as applicable:
a) appointment or election record;
b) term and renewal record;
c) eligibility, consent, fit-and-proper, integrity, conflict, independence, sanctions, export-control, controlled-technology, data / AI / cyber, privacy, research integrity, evidence integrity, methods integrity, technical integrity, intellectual-property, public authority boundary, finance-boundary, certification-boundary, procurement-neutrality, recognition-boundary, provider-neutrality, sponsor non-control, safeguards, civil-rights, accessibility, Tribal and Indigenous protocol, and protected knowledge screening records;
d) duty acknowledgment and certification of understanding;
e) role description;
f) reporting line;
g) authority matrix entry;
h) separate delegations;
i) Public-Good Technical Asset Register records;
j) repository records;
k) software asset records;
l) open technical baseline records;
m) schema, API, SDK, dashboard, data tool, reference architecture, technical profile, test harness, gold vector, negative test, evaluation set, benchmark library, documentation, model-support, dataset-support, proof-receipt, role-key, smart-license, digital twin, AI-RAN, O-RAN, DePIN, DLT, blockchain, cyber, geospatial, Earth observation, sensor, and observability asset records;
n) contributor intake, eligibility, affiliation, conflict, sanctions, export-control, controlled-technology, data rights, privacy, protected knowledge, IP, contributor license, assignment, attribution, review, acceptance, rejection, quarantine, withdrawal, takedown, and offboarding records;
o) license selection, open-source review, public-good license review, restricted license review, third-party dependency license review, patent review, defensive publication review, trademark review, standards-essential-rights review, attribution, relicensing, sublicensing, commercial-use boundary, and public-claim records;
p) IP chain-of-title, authorship, ownership, assignment, contributor grant, third-party rights, dataset rights, model rights, documentation rights, unresolved rights limitation, infringement-risk, and legal escalation records;
q) secure release, code review, branch protection, maintainer approval, dependency review, SBOM, signing, provenance, vulnerability scanning, secret scanning, release note, rollback, patch, security advisory, post-release review, and secure archive records;
r) fork review, derivative work review, compatibility note, divergence log, Nexus-compatible claim, GRF-facing input support, GRA-facing technical input support, Nexus Docket-support, Nexus Grid-support, Nexus Standards-support, public authority learning, provider interface, sponsor interface, host interface, and enterprise-stack boundary records;
s) anti-enclosure, public-good stewardship, portability, interoperability, open schema, controlled openness, sponsor non-control, provider neutrality, capture-risk, public-safe publication, protected knowledge, and technical asset misuse records;
t) correction, supersession, withdrawal, takedown, deprecation, retirement, archive, legal hold, retention, deletion, and secure disposal records;
u) escalations involving public authority boundary, finance boundary, certification boundary, procurement neutrality, recognition boundary, provider neutrality, sponsor non-control, data / AI / cyber, safeguards, protected knowledge, civil rights, accessibility, competition, sanctions, export-control, controlled technology, public-safe publication, intellectual-property, professional boundary, or legal risk;
v) conflicts, recusals, access restrictions, delegation restrictions, resignation, removal, handover, access revocation, and closeout records; and
w) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that the Chief Public-Good Software and Technical Assets Officer safeguards public-good technical stewardship, not external authority. Public-good software, open technical baselines, repositories, schemas, APIs, SDKs, dashboards, data tools, reference architectures, technical profiles, test harnesses, gold vectors, negative tests, benchmark assets, proof receipts, role keys, smart licenses, observability tools, AI-RAN artifacts, O-RAN artifacts, DePIN artifacts, DLT artifacts, blockchain references, cyber tools, digital twins, geospatial tools, sensor artifacts, and documentation may support evidence, methods, research, observability, ontology, technical truth, public authority learning, safeguards, GRF-facing inputs, GRA-facing technical inputs, Nexus Docket support, Nexus Grid support, interoperability, and public-safe publication, but they do not become certification, recognition, finance-readiness, procurement approval, public authority action, public warning, emergency command, rating, provider approval, sponsor entitlement, or enterprise execution by virtue of being released, open, useful, signed, benchmarked, ledger-referenced, technically credible, or Nexus-compatible in a limited technical sense. Public-good software and technical asset stewardship is lawful, secure, bounded, anti-enclosure, record-supported, public-safe, non-executing, role-separated, reviewable, and correctionable.
Section 147. Chief Public Authority Learning Officer
147.1 Chief Public Authority Learning Officer Role. The Chief Public Authority Learning Officer, where such office is approved by the Board, shall serve as the principal public-authority-learning, government-interface, capacity-classification, regulator-listening, public-finance-reader, emergency-management-learning, public-infrastructure-operator-learning, public authority data-contribution, public authority reference, public authority room, simulation, tabletop, exercise, after-action-learning, federal-interface, state-interface, territorial-interface, District of Columbia-interface, Tribal and Indigenous government-interface, local-interface, public-safe-reporting, and official-capacity-boundary officer of the Corporation, subject at all times to applicable law, the Articles or Certificate, this Bylaw, Board resolutions, Board-approved policies, the delegation matrix, the authority matrix, approved budget, legal and compliance controls, tax-exempt or tax-exempt-compatible restrictions, public-benefit purpose, non-execution, GCRI / GRF / GRA role separation, public-good stack and enterprise stack separation, public authority boundary controls, finance-boundary controls, procurement-neutrality controls, certification-boundary controls, recognition-boundary controls, provider-neutrality controls, sponsor non-control controls, data / AI / cyber controls, privacy controls, research integrity controls, evidence controls, methods controls, community safeguards, protected knowledge restrictions, controlled vocabulary, validity-by-record, and correctionability.
The Chief Public Authority Learning Officer’s office exists to support lawful, bounded, non-executing, public-safe, evidence-grounded, technically literate, capacity-classified, record-supported, and correctionable learning interfaces between the Corporation and public authorities. The office may support public authority understanding of systemic risk evidence, observability methods, technical baselines, public-good software, Nexus Truth Engine methods, Nexus Observatory methods, verifiable compute, data / AI / cyber governance, public-safe reporting, community safeguards, and Nexus public-good stack compatibility, but it shall not convert the Corporation into a public authority, regulator, emergency command body, public warning authority, procurement body, public finance approver, certification body, recognition body, finance-readiness authority, standards authority, provider selector, or enterprise execution actor.
The Chief Public Authority Learning Officer shall not, by title, public authority relationship, convening role, meeting access, public official contact, public authority room responsibility, emergency-management literacy role, simulation role, tabletop role, public finance reader interface, regulator-listening interface, public infrastructure operator interface, or public-safe reporting role alone, be treated as:
a) a substitute Board;
b) a person authorized to approve Board reserved matters;
c) a regulator, public authority, public official, public warning authority, emergency command authority, procurement authority, public finance authority, grant approval authority, permitting authority, certification authority, recognition authority, finance-readiness authority, rating authority, insurance-readiness authority, capital-readability authority, standards authority, protocol authority, or enterprise execution actor;
d) a person authorized to make final legal, regulatory, procurement, public finance, public safety, public health, emergency-management, infrastructure, utility, telecom, cyber, environmental, engineering, finance, insurance, lending, underwriting, rating, certification, recognition, operational, or sovereign determinations;
e) a person authorized to bind the United States, any state, territory, the District of Columbia, Tribal Nation, Indigenous government, local government, municipal body, county body, metropolitan authority, port authority, utility, public health authority, public safety authority, emergency-management authority, public works authority, public infrastructure operator, public finance body, regulator, or other public authority;
f) a person authorized to bind GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Standards, consortiums, national companies, Project SPVs, providers, sponsors, hosts, universities, laboratories, communities, Indigenous knowledge holders, funders, or enterprise-stack actors; or
g) a person authorized to convert public authority attendance, public authority data contribution, public authority reference, public authority room access, regulator-listening participation, public finance reader participation, emergency-management participation, public infrastructure operator participation, simulation participation, tabletop participation, after-action-learning participation, dashboard access, evidence pack access, proof receipt, technical baseline, public-safe report, observability output, AI output, digital twin, DePIN signal, AI-RAN signal, O-RAN signal, sensor signal, or ledger reference into public authority adoption, official decision, public warning, emergency command, procurement approval, funding approval, regulatory approval, public finance approval, sovereign obligation, certification, recognition, finance-readiness, provider approval, sponsor entitlement, or enterprise execution authority.
147.2 Public Authority Learning Program Support. The Chief Public Authority Learning Officer may support public authority learning programs where delegated. Public authority learning programs shall be designed to improve evidence literacy, technical literacy, public-safe reporting literacy, risk-method literacy, data / AI / cyber literacy, observability literacy, systemic-risk literacy, resilience-infrastructure literacy, and Nexus public-good stack literacy among public authority participants without creating public authority delegation, public authority substitution, public warning authority, emergency command authority, procurement approval, regulatory approval, public finance approval, certification, recognition, or finance-readiness determination.
Public authority learning program support may include:
a) curriculum design;
b) learning objectives;
c) participant capacity classification;
d) public authority interface terms;
e) public authority room rules;
f) controlled-room rules;
g) public-safe notice language;
h) evidence and method explanations;
i) technical baseline explanations;
j) observability and dashboard literacy;
k) data / AI / cyber and privacy literacy;
l) verifiable compute and proof-receipt literacy;
m) public-safe mapping literacy;
n) community safeguard literacy;
o) Indigenous protocol and protected knowledge awareness;
p) simulation, tabletop, exercise, and after-action-learning design;
q) public authority reference review;
r) correction and supersession pathways; and
s) learning records.
Public authority learning programs shall not be marketed or represented as official public authority training unless a competent public authority has lawfully authorized such status by record. A learning program may be useful to public authorities without becoming a governmental function, regulated training requirement, procurement prerequisite, certification requirement, public finance condition, emergency-management protocol, public warning system, or official adoption of the Corporation’s materials.
147.3 Federal Public Authority Interface Support. The Chief Public Authority Learning Officer may support federal public authority interfaces where delegated and lawful. Federal public authority interface support may involve communications, learning sessions, evidence briefings, controlled-room participation, public authority rooms, data contribution discussions, public-safe publication review, simulation participation, tabletop participation, after-action learning, technical literacy sessions, grant-related learning interfaces, standards-support conversations, or other non-executing public-benefit interactions with federal departments, agencies, commissions, offices, laboratories, federally chartered entities, public infrastructure operators, emergency-management bodies, regulators, public health bodies, public safety bodies, and other federal public authority participants.
Federal public authority interface support shall identify and record, as applicable:
a) the public authority entity;
b) the participating office or unit;
c) participant names and roles where appropriate;
d) official-capacity, observer, regulator-listening, public finance reader, emergency-management participant, public infrastructure operator, technical participant, or other capacity classification;
e) lawful basis or authorizing context for participation where required;
f) meeting purpose;
g) materials shared;
h) data contributions or data restrictions;
i) confidentiality, public records, FOIA, procurement, ethics, gifts, grant, lobbying, national security, controlled-technology, sanctions, export-control, privacy, cyber, and public authority constraints where relevant;
j) public-safe notices;
k) non-reliance language;
l) correction pathways; and
m) public authority interface records.
No federal public authority interface shall be represented as federal approval, federal funding approval, federal procurement approval, federal regulatory approval, federal public finance approval, federal certification, federal endorsement, federal public warning, federal emergency command, federal adoption, federal partnership, federal obligation, or federal sponsorship unless separately and lawfully authorized by the competent federal authority and recorded in an appropriate instrument.
147.4 State Public Authority Interface Support. The Chief Public Authority Learning Officer may support state public authority interfaces where delegated and lawful. State public authority interface support shall account for the Corporation’s all-states-and-territories operating posture while preserving state-by-state legal compliance, public authority capacity classification, public records and sunshine-law sensitivity, procurement integrity, lobbying and government ethics controls, grant compliance, data / AI / cyber requirements, public-safe publication limits, and non-execution boundaries.
State public authority interface support may involve:
a) governors’ offices and executive offices;
b) state agencies;
c) state emergency-management bodies;
d) state public health and public safety bodies;
e) state utility, energy, water, food, telecom, cyber, transportation, infrastructure, environment, climate, disaster, insurance, finance, procurement, innovation, and technology bodies;
f) state universities and public laboratories where acting in a public capacity;
g) state regulators in regulator-listening capacity;
h) state public finance readers;
i) state infrastructure operators;
j) state legislative or policy-learning interfaces where lawful; and
k) state grant, research, education, and public-benefit interfaces.
No state public authority interface shall be represented as state adoption, state endorsement, state procurement approval, state funding approval, state public finance approval, state regulatory approval, state public warning, state emergency command, state certification, state recognition, state mandate, state partnership, state obligation, or state authorization of a provider, sponsor, project, national company, Project SPV, technical asset, dashboard, public-good software, technical baseline, or Nexus-compatible claim unless separately and lawfully authorized by the competent state authority and recorded.
147.5 Territorial Public Authority Interface Support. The Chief Public Authority Learning Officer may support territorial public authority interfaces where delegated and lawful, including interfaces involving Puerto Rico, Guam, the U.S. Virgin Islands, American Samoa, the Northern Mariana Islands, and other territorial or insular public authority contexts where relevant. Territorial interface support shall respect applicable federal, territorial, local, Indigenous, cultural, language, disaster, climate, infrastructure, public health, public safety, data, cyber, procurement, public finance, emergency-management, and public authority constraints.
Territorial public authority interface support shall be localized without fragmentation. Localization may include territory-specific notice language, language-access support, public-safe mapping controls, disaster-exposure context, infrastructure-sensitivity review, public authority capacity classification, data localization review, community safeguard review, Indigenous and local knowledge protection, and compatibility notes. No territorial localization shall weaken 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, or correctionability.
No territorial public authority participation, data contribution, controlled-room attendance, simulation participation, dashboard access, public-safe report, evidence briefing, or technical baseline review shall be represented as territorial public authority adoption, official warning, emergency command, procurement approval, funding approval, regulatory approval, public finance approval, sovereign obligation, certification, recognition, or execution authority unless separately and lawfully authorized and recorded.
147.6 District of Columbia Interface Support. The Chief Public Authority Learning Officer may support District of Columbia public authority interfaces where delegated and lawful. District of Columbia interface support may involve municipal, district-level, federal-adjacent, metropolitan, utility, emergency-management, public health, public safety, infrastructure, procurement, public finance, regulatory, university, laboratory, and public authority learning contexts.
District of Columbia interface support shall identify whether the relevant capacity is District governmental, federal, municipal, metropolitan, academic, public infrastructure operator, regulator-listening, public finance reader, emergency-management participant, observer, or another capacity. Where the same session involves federal and District participants, the Chief Public Authority Learning Officer shall support distinct capacity classification, public records and confidentiality review, public authority reference review, public-safe limitation language, and conflict-of-law escalation where necessary.
No District of Columbia interface shall be used to imply federal adoption, District adoption, procurement approval, funding approval, public finance approval, regulatory approval, public warning, emergency command, public-private partnership, certification, recognition, provider preference, sponsor entitlement, or enterprise execution authority without competent record.
147.7 Tribal and Indigenous Government Interface Support Where Lawfully and Respectfully Structured. The Chief Public Authority Learning Officer may support Tribal and Indigenous government interfaces where delegated, lawful, respectful, and consistent with applicable sovereignty, governance, cultural, data, knowledge, consultation, consent, confidentiality, public-safe mapping, protected knowledge, community safeguard, and non-extraction requirements. Such support shall be coordinated with the safeguards function and any relevant Tribal, Indigenous, local, territorial, cultural, environmental, protected knowledge, civil-rights, accessibility, or community review process.
Tribal and Indigenous government interface support shall respect:
a) Tribal sovereignty;
b) Indigenous governance protocols;
c) lawful authority and consent rules;
d) non-consent and withdrawal pathways where applicable;
e) protected knowledge restrictions;
f) Indigenous data safeguards;
g) local and territorial knowledge safeguards;
h) attribution rules;
i) no-download or controlled-room requirements;
j) public-safe mapping restrictions;
k) language, accessibility, cultural, and participation needs;
l) grievance and remedy pathways;
m) non-retaliation and protected participation;
n) correction and takedown pathways; and
o) records of capacity, authority, limitations, and safeguards.
No Tribal or Indigenous government interface shall be treated as consultation, consent, approval, authorization, endorsement, public authority adoption, sovereign obligation, data-sharing permission, knowledge-use permission, public mapping permission, procurement approval, funding approval, certification, recognition, finance-readiness, or project approval unless the competent Tribal or Indigenous authority has expressly and lawfully authorized such status and the governing record identifies the scope, limitations, and conditions.
147.8 Local, County, Municipal, Metropolitan, Utility, Port, Public Health, Emergency Management, Public Safety, Public Works, Telecom, Energy, Water, Food, Cyber, and Infrastructure Interface Support. The Chief Public Authority Learning Officer may support local and sectoral public authority interfaces where delegated and lawful. Such interfaces may involve local governments, counties, municipalities, metropolitan authorities, regional bodies, ports, utilities, public health agencies, emergency-management bodies, public safety agencies, public works departments, telecom-related public bodies, energy authorities, water authorities, food-system authorities, cyber offices, infrastructure operators, transportation bodies, resilience offices, climate offices, disaster-risk bodies, and related mission-critical systems.
Local and sectoral interface support may address:
a) participant capacity classification;
b) local legal authority;
c) public records and open meetings considerations;
d) procurement and grant integrity;
e) emergency-management boundaries;
f) public warning boundaries;
g) infrastructure-sensitive information controls;
h) cyber-sensitive information controls;
i) health-sensitive information controls;
j) data contribution controls;
k) public-safe dashboard and map limitations;
l) community safeguard implications;
m) provider-neutrality and sponsor non-control;
n) simulation, tabletop, exercise, and after-action-learning design; and
o) correction and notice pathways.
No local or sectoral interface shall authorize the Corporation to operate public infrastructure, direct public employees, issue public warnings, command emergency resources, dispatch services, make public health orders, select vendors, approve procurement, approve funding, approve public finance, regulate conduct, certify compliance, approve providers, recognize projects, or execute enterprise delivery unless separately and lawfully structured outside the prohibited functions and expressly approved within the limits of this Bylaw.
147.9 Capacity Classification Support. The Chief Public Authority Learning Officer shall support public authority capacity classification where delegated. Capacity classification shall be used to identify the legal, institutional, participation, access, reliance, confidentiality, public records, procurement, public finance, emergency-management, and public-safe meaning of public authority participation.
Public authority capacity classifications may include, without limitation:
a) official-capacity participant;
b) observer;
c) regulator-listening participant;
d) public finance reader;
e) emergency-management participant;
f) public infrastructure operator participant;
g) public health participant;
h) public safety participant;
i) technical participant;
j) public university or laboratory participant;
k) grant officer or grant reader;
l) procurement-sensitive participant;
m) data contributor;
n) controlled-room participant;
o) no-download-room participant;
p) simulation participant;
q) tabletop participant;
r) after-action-learning participant;
s) public-facing speaker where authorized; and
t) non-authorized attendee.
Capacity classification shall be recorded before or promptly after material participation. Where capacity is unclear, the Corporation shall apply the more restrictive classification, limit reliance, restrict public references, require clarification, hold publication where necessary, and escalate to counsel, compliance, the relevant officer, committee, or Board. No ambiguity in capacity shall be used to inflate authority.
147.10 Public Authority Data Contribution Support. The Chief Public Authority Learning Officer may support public authority data contribution processes where delegated and in coordination with data / AI / cyber, privacy, safeguards, legal, compliance, records, and technical officers where required. Public authority data contribution support shall ensure that data received from, generated with, derived from, linked to, displayed for, or used in connection with public authorities is handled only within lawful authority, approved purpose, access class, publication class, retention rule, security classification, public-safe limitation, and correction pathway.
Public authority data contribution support may address:
a) data source;
b) contributor authority;
c) data contribution terms;
d) public records implications;
e) confidentiality and privilege claims;
f) privacy and rights-bearing data;
g) health-sensitive data;
h) cyber-sensitive and infrastructure-sensitive data;
i) emergency-management data;
j) public safety data;
k) procurement-sensitive data;
l) public finance-sensitive data;
m) Tribal, Indigenous, local, territorial, community-protected, cultural, environmental, or protected knowledge data;
n) AI-use restrictions;
o) dashboard and map restrictions;
p) publication restrictions;
q) return, sealing, deletion, retention, archive, or legal hold requirements; and
r) correction, supersession, withdrawal, and takedown pathways.
No public authority data contribution shall be treated as permission to publish, train models, fine-tune models, embed data, reuse data, disclose data, map data, transfer data cross-border, provide data to sponsors or providers, create public authority statements, issue public warnings, approve projects, approve providers, support procurement, support public finance, or create official reliance unless the governing record expressly permits that use.
147.11 Public Authority Reference Review Support. The Chief Public Authority Learning Officer shall support public authority reference review where delegated. Public authority reference review shall apply before the Corporation uses the name, seal, logo, acronym, office, title, official capacity, quotation, attendance, data contribution, meeting reference, program participation, controlled-room participation, dashboard access, simulation participation, tabletop participation, after-action-learning participation, public-safe report reference, or other public authority-associated fact in public, controlled, fundraising, grant, sponsorship, technical, Nexus, GRF-facing, GRA-facing, repository, website, social media, slide, press, or public statement materials.
Public authority reference review shall determine, as applicable:
a) whether the reference is accurate;
b) whether the reference is authorized;
c) whether the participant acted in official capacity, observer capacity, regulator-listening capacity, public finance reader capacity, emergency-management participant capacity, public infrastructure operator capacity, personal capacity, academic capacity, or another capacity;
d) whether public records, procurement, grant, ethics, gifts, lobbying, political activity, confidentiality, privacy, cyber, public safety, national security, or public authority constraints apply;
e) whether the reference could imply endorsement, adoption, approval, funding, procurement, public finance, regulation, certification, recognition, public warning, emergency command, public-private partnership, provider preference, sponsor entitlement, or sovereign obligation;
f) whether limitation language is required;
g) whether controlled vocabulary applies;
h) whether public authority consent or clearance is required; and
i) whether correction, withdrawal, takedown, or clarification is required.
No public authority reference shall be used to create apparent authority, public authority endorsement, procurement advantage, funding advantage, finance-readiness signal, recognition signal, certification signal, provider preference, sponsor value, or public reliance beyond the competent record.
147.12 Regulator-Listening and Public Finance Reader Protocol Support. The Chief Public Authority Learning Officer may support regulator-listening and public finance reader protocols where delegated. Regulator-listening participation means a regulator or regulatory-adjacent public authority participant may listen, learn, ask questions, provide general context where lawful, and understand evidence or methods without being deemed to approve, adopt, certify, regulate, enforce, waive, or endorse any output. Public finance reader participation means a public finance, budget, grant, treasury, infrastructure finance, MDB / DFI-adjacent, bond, credit, resilience-finance, or capital-reader public participant may review evidence, methods, proof-pack inputs, or public-good technical materials for literacy or diligence translation without being deemed to approve financing, appropriations, grants, guarantees, tax credits, bonds, credit, public finance, insurance, procurement, or capital allocation.
Regulator-listening and public finance reader protocols shall include, as applicable:
a) capacity classification;
b) admission criteria;
c) conflicts and recusal screening;
d) competition and procurement integrity controls;
e) no-reliance and no-approval notices;
f) data access limits;
g) public authority reference restrictions;
h) confidentiality and public records controls;
i) meeting agenda controls;
j) minutes controls;
k) question-handling protocols;
l) prohibited-topic controls;
m) public-safe reporting limits;
n) finance-boundary controls;
o) correction pathways; and
p) records of attendance, materials, capacity, and limitations.
No regulator-listening or public finance reader participation shall create regulatory safe harbor, compliance approval, official guidance, procurement approval, public finance approval, funding approval, grant approval, budget allocation, appropriation, guarantee, credit opinion, rating, insurance approval, finance-readiness determination, recognition, certification, or public authority adoption.
147.13 Scenario, Simulation, Tabletop, Exercise, and After-Action Learning Support. The Chief Public Authority Learning Officer may support scenario, simulation, tabletop, exercise, and after-action learning where delegated. Such activities shall be structured as learning, evidence, methods, public-safe reporting, capacity-building, technical literacy, observability-literacy, data / AI / cyber literacy, resilience-literacy, and correctionability activities, not as emergency command, public warning, operational deployment, official incident management, dispatch, public health order, public safety command, procurement approval, provider selection, public finance approval, certification, recognition, or execution authority.
Scenario, simulation, tabletop, exercise, and after-action learning support may include:
a) scenario scope;
b) learning objectives;
c) participant capacity classification;
d) assumptions and limitations;
e) no-real-world-command notices;
f) no-public-warning notices;
g) public authority boundary notices;
h) finance, procurement, certification, recognition, provider-neutrality, and sponsor non-control notices;
i) data access and confidentiality controls;
j) cyber and infrastructure-sensitive controls;
k) public-safe mapping controls;
l) protected knowledge restrictions;
m) observation templates;
n) after-action learning methods;
o) corrective action logs;
p) public-safe summary review;
q) restricted annex controls;
r) correction and supersession pathways; and
s) records of materials, participants, outputs, limitations, and follow-up.
No scenario output, simulation output, tabletop finding, exercise observation, after-action note, dashboard, map, AI output, digital twin output, sensor signal, proof receipt, or public-safe summary shall be treated as a public warning, emergency command, operational instruction, public authority decision, procurement decision, finance-readiness determination, certification, recognition, rating, provider approval, sponsor entitlement, or enterprise execution authority.
147.14 No Public Authority Delegation, Public Warning, Emergency Command, Procurement Approval, Funding Approval, Regulatory Approval, Public Finance Approval, Sovereign Obligation, or Official Adoption by Participation. No act, omission, program, meeting, controlled room, public authority room, evidence room, data room, no-download room, simulation, tabletop, exercise, after-action-learning session, public-safe report, dashboard, map, technical baseline, public-good software release, evidence pack, method note, proof receipt, role key, smart license, AI output, digital twin output, sensor signal, AI-RAN signal, O-RAN signal, DePIN record, DLT record, blockchain or ledger reference, public authority data contribution, public authority reference, regulator-listening session, public finance reader session, or public authority attendance associated with the Corporation shall be represented or used as:
a) delegation of public authority;
b) public authority substitution;
c) public warning;
d) emergency command;
e) incident command;
f) dispatch;
g) evacuation instruction;
h) public health order;
i) public safety order;
j) operational instruction to a public authority or infrastructure operator;
k) procurement approval;
l) vendor selection;
m) provider preference;
n) funding approval;
o) grant approval;
p) regulatory approval;
q) compliance approval;
r) public finance approval;
s) sovereign obligation;
t) public-private partnership;
u) certification;
v) recognition;
w) finance-readiness, insurance-readiness, capital-readability, bankability, investability, rating, or credit opinion;
x) official adoption;
y) official endorsement; or
z) enterprise execution authority.
This limitation applies regardless of whether a public official attended, spoke, contributed data, reviewed materials, asked questions, joined a controlled room, joined a public authority room, participated in a simulation, reviewed a dashboard, received a report, used a technical asset, appeared in public materials, or participated repeatedly. Official public authority meaning requires competent public authority action, lawful authority, and a governing record outside mere participation.
147.15 Chief Public Authority Learning Officer Records. The Corporation shall maintain Chief Public Authority Learning Officer Records sufficient to demonstrate the Chief Public Authority Learning Officer’s appointment, term, eligibility, authority, delegations, public authority learning program support, federal interface support, state interface support, territorial interface support, District of Columbia interface support, Tribal and Indigenous government interface support, local and sectoral interface support, capacity classification support, public authority data contribution support, public authority reference review support, regulator-listening and public finance reader protocol support, scenario, simulation, tabletop, exercise, after-action-learning support, public authority boundary controls, conflicts, recusals, restrictions, succession, and closeout.
Chief Public Authority Learning Officer Records shall include, as applicable:
a) appointment or election record;
b) term and renewal record;
c) eligibility, consent, fit-and-proper, integrity, conflict, independence, sanctions, export-control, controlled-technology, public authority boundary, public finance boundary, procurement boundary, emergency-management boundary, public warning boundary, regulatory boundary, data / AI / cyber, privacy, research integrity, evidence integrity, methods integrity, finance-boundary, certification-boundary, recognition-boundary, provider-neutrality, sponsor non-control, safeguards, civil-rights, accessibility, Tribal and Indigenous protocol, and protected knowledge screening records;
d) duty acknowledgment and certification of understanding;
e) role description;
f) reporting line;
g) authority matrix entry;
h) separate delegations;
i) public authority learning program records;
j) curriculum, learning objective, attendance, capacity classification, materials, notices, and evaluation records;
k) federal public authority interface records;
l) state public authority interface records;
m) District of Columbia and territorial public authority interface records;
n) Tribal and Indigenous government interface records;
o) local, county, municipal, metropolitan, utility, port, public health, emergency-management, public safety, public works, telecom, energy, water, food, cyber, infrastructure, and public infrastructure operator interface records;
p) official-capacity, observer, regulator-listening, public finance reader, emergency-management participant, public infrastructure operator, technical participant, simulation participant, tabletop participant, after-action-learning participant, and public-facing speaker capacity records;
q) public authority data contribution records;
r) public authority reference review records;
s) public authority room, controlled-room, clean-room, evidence-room, data-room, and no-download-room records;
t) public records, FOIA, sunshine, open meetings, procurement, grant, lobbying, government ethics, gifts, confidentiality, privacy, cyber, public safety, national security, controlled-technology, sanctions, export-control, and public authority constraint records;
u) regulator-listening protocol records;
v) public finance reader protocol records;
w) scenario, simulation, tabletop, exercise, after-action-learning, observation, corrective action, public-safe summary, restricted annex, and learning record records;
x) public-safe notice, no-reliance, no-public-warning, no-emergency-command, no-procurement-approval, no-funding-approval, no-regulatory-approval, no-public-finance-approval, no-certification, no-recognition, no-finance-readiness, no-provider-preference, and no-sponsor-control language records;
y) escalations involving public authority boundary, emergency command, public warning, procurement, funding, regulatory approval, public finance, finance boundary, certification boundary, recognition boundary, provider neutrality, sponsor non-control, data / AI / cyber, safeguards, protected knowledge, civil rights, accessibility, competition, sanctions, export-control, controlled technology, public-safe publication, professional boundary, or legal risk;
z) conflicts, recusals, access restrictions, delegation restrictions, resignation, removal, handover, access revocation, and closeout records; and
aa) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that the Chief Public Authority Learning Officer safeguards public authority learning, not public authority power. Public authorities may learn from, observe, review, question, contribute to, or participate in the Corporation’s evidence, methods, observability, technical baseline, public-good software, public-safe reporting, simulation, tabletop, after-action-learning, controlled-room, and Nexus-compatible activities, but their participation does not create public authority delegation, official adoption, public warning, emergency command, procurement approval, funding approval, regulatory approval, public finance approval, sovereign obligation, public-private partnership, certification, recognition, finance-readiness, provider approval, sponsor entitlement, or enterprise execution authority. Public authority learning is capacity-classified, lawful, bounded, record-supported, public-safe, non-executing, role-separated, and correctionable.
Section 148. Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer
148.1 Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer Role. The Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer, where such office is approved by the Board, shall serve as the principal community-safeguards, civil-rights, accessibility, non-discrimination, protected-knowledge, Tribal and Indigenous protocol, Indigenous data safeguard, local-knowledge, territorial-knowledge, cultural-knowledge, environmental-knowledge, public-safe mapping, vulnerable-community, remote-community, disaster-exposed-community, climate-exposed-community, health-exposed-community, infrastructure-exposed-community, grievance, remedy, protected-participation, non-retaliation, do-no-harm, consent, non-consent, attribution, withdrawal, restriction, correction, takedown, and safeguards stop-the-line officer of the Corporation, subject at all times to applicable law, the Articles or Certificate, this Bylaw, Board resolutions, Board-approved policies, the delegation matrix, the authority matrix, approved budget, legal and compliance controls, tax-exempt or tax-exempt-compatible restrictions, public-benefit purpose, non-execution, GCRI / GRF / GRA role separation, public-good stack and enterprise stack separation, public authority boundary controls, finance-boundary controls, procurement-neutrality controls, certification-boundary controls, recognition-boundary controls, provider-neutrality controls, sponsor non-control controls, research integrity controls, evidence controls, methods controls, data / AI / cyber controls, privacy controls, public-safe publication controls, controlled vocabulary, validity-by-record, and correctionability.
The Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer’s office exists to ensure that the Corporation’s research, evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, public authority learning, controlled rooms, clean rooms, data rooms, evidence rooms, public-safe reports, dashboards, maps, datasets, model uses, AI outputs, digital twins, sensor systems, AI-RAN / O-RAN interfaces, DePIN interfaces, DLT / blockchain references, Nexus interfaces, GRF-facing inputs, GRA-facing technical inputs, Academy activities, fellowships, labs, programs, publications, and public materials are designed, reviewed, limited, corrected, and, where necessary, stopped in a manner that respects human dignity, civil rights, accessibility, community agency, Tribal sovereignty, Indigenous governance, protected knowledge, local context, public safety, public trust, and do-no-harm obligations.
The Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer shall not, by title, safeguard expertise, community relationship, Tribal or Indigenous interface role, civil-rights role, accessibility role, grievance role, public-safe mapping role, protected-knowledge review role, stop-the-line role, public authority contact, or participation in any committee, forum, controlled room, public authority room, research process, publication process, or Nexus interface alone, be treated as:
a) a substitute Board;
b) a person authorized to approve Board reserved matters;
c) a public authority, civil-rights enforcement agency, court, tribunal, regulator, emergency command authority, public warning authority, certification authority, recognition authority, procurement authority, public finance authority, finance-readiness authority, standards authority, protocol authority, or enterprise execution actor;
d) a person authorized to make final legal, human-rights, civil-rights, Indigenous-rights, Tribal-law, environmental-justice, public-health, public-safety, emergency-management, engineering, clinical, regulatory, finance, insurance, lending, procurement, certification, recognition, or operational determinations;
e) a person authorized to bind any Tribal Nation, Indigenous government, Indigenous knowledge holder, community, local organization, protected knowledge holder, public authority, university, laboratory, sponsor, provider, host, donor, funder, national company, Project SPV, GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Standards, or enterprise-stack actor; or
f) a person authorized to convert a safeguards review, civil-rights review, accessibility review, Tribal or Indigenous interface, protected-knowledge review, public-safe mapping review, grievance record, remedy record, stop-the-line action, community meeting, public authority meeting, controlled-room review, public-safe notice, dashboard limitation, evidence limitation, correction, takedown, or publication hold into public authority action, official legal finding, certification, recognition, finance-readiness, procurement approval, provider approval, sponsor entitlement, public warning, emergency command, or enterprise execution authority.
148.2 Community Safeguards Oversight Where Delegated. The Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer may oversee community safeguards where delegated. Community safeguards shall be used to identify, prevent, reduce, correct, and remediate risks that the Corporation’s activities could create or amplify for communities, including risks arising from data collection, public-safe reporting, mapping, dashboards, observability outputs, public authority learning, technical baselines, public-good software, AI systems, digital twins, sensors, DePIN records, DLT / blockchain references, cyber-sensitive information, infrastructure-sensitive information, climate and disaster-risk information, health-sensitive information, publication, media amplification, sponsor relationships, provider relationships, and public authority references.
Community safeguards oversight may address:
a) affected-community identification;
b) community context review;
c) vulnerability and exposure review;
d) remote-community access and harm review;
e) disaster, climate, health, infrastructure, cyber, environmental, food, water, energy, telecom, and public-safety exposure review;
f) civil-rights, accessibility, language, disability, age, gender, race, ethnicity, national origin, religion, socioeconomic, rural, geographic, and other rights-bearing impact review;
g) community participation design;
h) non-extractive engagement;
i) consent, non-consent, withdrawal, restriction, attribution, correction, and takedown pathways where applicable;
j) public-safe mapping controls;
k) protected knowledge controls;
l) grievance and remedy pathways;
m) non-retaliation protections;
n) publication limitation language;
o) sponsor, provider, donor, funder, host, public authority, and institutional convenience extraction-risk review; and
p) records, review cycles, corrective actions, and closeout.
Community safeguards shall be applied before institutional convenience, reputational interest, dashboard completeness, sponsor interest, provider interest, media value, technical curiosity, publication speed, public authority interest, or grant deadline. Where community harm cannot be reduced to an acceptable lawful and public-safe level, the relevant activity shall be held, restricted, re-scoped, compartmentalized, anonymized, aggregated, delayed, withdrawn, corrected, taken down, externalized, referred, or terminated.
148.3 Tribal and Indigenous Protocol Support. The Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer may support Tribal and Indigenous protocol review where delegated. Tribal and Indigenous protocol support shall respect Tribal sovereignty, Indigenous governance, Indigenous rights, Indigenous data sovereignty principles where applicable, protected knowledge, cultural protocols, local law, territorial context, community authority, consent and non-consent, traditional knowledge restrictions, sacred-site restrictions, public-safe mapping concerns, language access, accessibility, and appropriate relationship-building.
Tribal and Indigenous protocol support may include:
a) identification of Tribal, Indigenous, or Indigenous-affiliated interests;
b) determination of whether a Tribal Nation, Indigenous government, Indigenous organization, knowledge holder, community body, or other competent authority should be consulted or engaged;
c) review of lawful authority for engagement;
d) review of consent, non-consent, withdrawal, restriction, attribution, confidentiality, publication, and correction requirements;
e) review of Indigenous data safeguards;
f) review of cultural, environmental, land, water, biodiversity, climate, health, disaster, infrastructure, cyber, geospatial, and public-safe mapping sensitivities;
g) review of protected knowledge and local knowledge restrictions;
h) review of controlled-room, no-download, clean-room, or restricted-annex requirements;
i) review of language, accessibility, and participation needs;
j) review of grievance, remedy, non-retaliation, and takedown pathways;
k) coordination with public authority learning, data / AI / cyber, privacy, research integrity, evidence, methods, publication, and legal functions; and
l) maintenance of protocol records, compatibility notes, divergence logs, and correction records.
No Tribal or Indigenous engagement, attendance, data contribution, knowledge contribution, advisory comment, public authority interface, workshop participation, room participation, or silence shall be treated as consent, consultation completion, approval, endorsement, publication permission, mapping permission, data-sharing permission, AI-use permission, certification, recognition, finance-readiness, procurement approval, public authority adoption, or project approval unless the competent authority and governing record expressly authorize that meaning.
148.4 Indigenous Data and Indigenous Knowledge Safeguards Support. The Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer may support Indigenous data and Indigenous knowledge safeguards where delegated. Indigenous data and Indigenous knowledge safeguards shall apply to data, records, observations, maps, stories, oral histories, ecological knowledge, environmental knowledge, cultural knowledge, territorial knowledge, health knowledge, community knowledge, technical observations, sensor data, geospatial layers, Earth observation interpretations, digital twin inputs, AI training or retrieval materials, public-safe reports, dashboards, evidence packs, technical baselines, and public-good software outputs that concern or derive from Tribal, Indigenous, local, territorial, cultural, or protected knowledge contexts.
Indigenous data and Indigenous knowledge safeguard support may address:
a) knowledge provenance;
b) knowledge holder authority;
c) community authority;
d) data governance requirements;
e) consent, non-consent, withdrawal, and restriction pathways;
f) attribution, anonymity, masking, aggregation, redaction, localization, or non-publication requirements;
g) restrictions on AI training, fine-tuning, embedding, retrieval, model improvement, simulation, benchmarking, dashboarding, and automated inference;
h) restrictions on publication, mapping, geospatial display, public-safe reporting, media use, sponsor access, provider access, public authority access, and cross-border transfer;
i) controlled-room, no-download, clean-room, or restricted repository requirements;
j) grievance, remedy, correction, takedown, sealing, deletion, return, or archive requirements; and
k) continuing review where knowledge sensitivity changes over time.
Indigenous data and Indigenous knowledge shall not be extracted, modeled, mapped, published, commercialized, transferred, benchmarked, converted into technical assets, incorporated into public-good software, or exposed to sponsors, providers, donors, funders, hosts, public authorities, researchers, media, or enterprise actors merely because it is technically useful, publicly visible, already published elsewhere, obtainable online, included in a dataset, generated by sensors, inferred by AI, or relevant to systemic risk.
148.5 Local, Territorial, Cultural, Environmental, and Protected Knowledge Safeguards Support. The Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer may support safeguards for local, territorial, cultural, environmental, and protected knowledge where delegated. Protected knowledge may include non-public, sensitive, sacred, community-held, location-sensitive, ecologically sensitive, culturally sensitive, security-sensitive, health-sensitive, infrastructure-sensitive, cyber-sensitive, disaster-sensitive, or retaliation-sensitive information whose disclosure, misuse, extraction, miscontextualization, commercialization, mapping, or AI processing could cause harm.
Protected knowledge safeguards may address:
a) knowledge classification;
b) source and authority;
c) lawful basis for use;
d) public-safe publication class;
e) access class;
f) community review;
g) public authority review where relevant;
h) location obfuscation;
i) aggregation, generalization, masking, redaction, or non-disclosure;
j) controlled-room or no-download restrictions;
k) AI-use restrictions;
l) technical asset restrictions;
m) repository restrictions;
n) sponsor, provider, donor, funder, host, media, and enterprise access restrictions;
o) cross-border transfer restrictions;
p) correction, takedown, sealing, deletion, return, or archive requirements; and
q) grievance and remedy pathways.
Where protected knowledge restrictions conflict with publication completeness, evidence richness, dashboard precision, geospatial accuracy, technical baseline usefulness, AI-model performance, sponsor interest, provider interest, public authority curiosity, institutional reputation, or research ambition, the protected knowledge restriction shall control unless a competent and lawful record determines otherwise.
148.6 Civil Rights and Non-Discrimination Support. The Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer may support civil-rights and non-discrimination review where delegated. Civil-rights and non-discrimination support shall apply to the Corporation’s governance, participation, programs, research, evidence practices, data systems, AI systems, dashboards, maps, publications, public authority learning sessions, controlled rooms, Academy activities, fellowships, technical assets, software, public statements, and external interfaces.
Civil-rights and non-discrimination support may address:
a) equal access to participation where required or adopted;
b) non-discrimination in admission, participation, employment, contracting, fellowship, volunteer, advisory, public authority learning, and program access;
c) disability, race, color, national origin, ethnicity, religion, sex, gender, sexual orientation, age, veteran status, socioeconomic status, geographic location, language, immigration-related sensitivity, and other protected or rights-bearing considerations where applicable;
d) disparate impact and disparate treatment risk;
e) bias in datasets, models, dashboards, scores, maps, and automated outputs;
f) public-safe language and non-stigmatizing framing;
g) grievance and remedy pathways;
h) retaliation prevention;
i) accessibility integration;
j) public authority and grant-related civil-rights requirements where applicable; and
k) correction, withdrawal, takedown, or public clarification where civil-rights risk is identified.
No research, evidence, method, technical baseline, dashboard, public-safe map, AI output, public authority learning artifact, or Nexus-facing input shall be approved for use or publication where it materially misclassifies, stigmatizes, excludes, stereotypes, surveils, exposes, or burdens protected or vulnerable persons or communities without lawful authority, safeguards, limitation language, human review, and a correction pathway.
148.7 Accessibility Support. The Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer may support accessibility where delegated. Accessibility support shall seek to make the Corporation’s governance processes, participation pathways, notices, publications, public-safe reports, websites, digital surfaces, dashboards, maps, technical documentation, Academy materials, controlled-room procedures, public authority learning materials, and public-facing summaries accessible to persons with disabilities and to participants with language, technology, geography, connectivity, literacy, or other access barriers, subject to lawful limitations and controlled-material restrictions.
Accessibility support may include:
a) accessible document formats;
b) screen-reader compatibility;
c) captioning, transcripts, or equivalent accommodations;
d) plain-language summaries where approved and non-operative;
e) language-access support where approved;
f) meeting accommodation procedures;
g) accessible registration and participation forms;
h) accessible public-safe notices;
i) accessible dashboard and map design;
j) accessibility review for Academy and training materials;
k) accessibility review for public authority learning sessions;
l) accessible grievance and remedy pathways;
m) accessible correction notices; and
n) accessibility records and review cycles.
Accessibility shall not be used to justify disclosure of restricted data, protected knowledge, confidential material, privileged material, public authority restricted material, cyber-sensitive information, or infrastructure-sensitive information beyond authorized scope. Where access and restriction must be reconciled, the Corporation shall use controlled accessibility methods, redacted alternatives, summary materials, assisted access, controlled rooms, or other lawful protective measures.
148.8 Vulnerable, Remote, Disaster-Exposed, Climate-Exposed, Health-Exposed, Infrastructure-Exposed, and High-Risk Community Safeguards Support. The Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer may support enhanced safeguards for vulnerable, remote, disaster-exposed, climate-exposed, health-exposed, infrastructure-exposed, cyber-exposed, conflict-exposed, economically stressed, historically underserved, institutionally marginalized, or otherwise high-risk communities where delegated. Enhanced safeguards shall be proportionate to the potential harm that could arise from data exposure, mapping, public reporting, AI inference, public authority attention, sponsor or provider attention, media amplification, infrastructure disclosure, stigmatization, retaliation, exclusion, or misallocation of resources.
Enhanced safeguards may include:
a) pre-engagement risk review;
b) community context review;
c) local partner review;
d) public authority capacity review;
e) public-safe mapping review;
f) health, disaster, climate, infrastructure, cyber, food, water, energy, telecom, and public-safety sensitivity review;
g) language and accessibility planning;
h) restricted publication;
i) location obfuscation;
j) aggregation or generalization;
k) controlled-room access;
l) no-download access;
m) AI-use restriction;
n) sponsor and provider access restriction;
o) media reference restriction;
p) grievance and remedy readiness;
q) non-retaliation protections;
r) post-publication monitoring where appropriate; and
s) correction, withdrawal, takedown, or emergency limitation pathways.
The Corporation shall not treat high-risk communities as data sources, case studies, demonstration sites, dashboard content, investor-facing narratives, sponsor-facing narratives, provider-market opportunities, public authority showcases, or media assets without lawful authority, public-benefit justification, safeguards review, public-safe framing, and correctionability.
148.9 Public-Safe Mapping Review Support. The Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer shall support public-safe mapping review where delegated. Public-safe mapping review shall apply to maps, geospatial layers, Earth observation outputs, sensor maps, infrastructure maps, hazard maps, climate maps, health maps, biodiversity maps, cyber maps, public authority maps, digital twins, dashboards, observability outputs, AI-generated spatial outputs, public-safe reports, evidence packs, technical baselines, and public materials that display, infer, or enable location-based interpretation of people, communities, assets, infrastructure, hazards, vulnerabilities, protected knowledge, or sensitive systems.
Public-safe mapping review may address:
a) location sensitivity;
b) precision and scale;
c) re-identification risk;
d) community exposure risk;
e) infrastructure exposure risk;
f) cyber and security risk;
g) health and public safety risk;
h) protected knowledge risk;
i) Tribal, Indigenous, local, territorial, cultural, environmental, and sacred-site sensitivity;
j) public authority boundary implications;
k) emergency command and public warning confusion;
l) sponsor, provider, media, and enterprise misuse risk;
m) aggregation, generalization, masking, jittering, redaction, or non-publication;
n) limitation language;
o) controlled access;
p) correction and takedown; and
q) archive and supersession.
No map, dashboard, digital twin, geospatial product, Earth observation interpretation, sensor output, AI-generated spatial output, DePIN record, DLT / blockchain reference, or observability output shall be released merely because it is technically accurate. Public-safe mapping requires review of how the mapped information may be misunderstood, weaponized, commercialized, used for targeting, used for exclusion, used to distort public authority action, or used to create public reliance beyond lawful and recorded scope.
148.10 Consent, Non-Consent, Attribution, Withdrawal, Restriction, and Correction Pathway Support. The Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer may support consent, non-consent, attribution, withdrawal, restriction, and correction pathways where delegated. Such pathways shall be designed to protect persons, communities, Tribal and Indigenous authorities, knowledge holders, data subjects, research participants, contributors, hosts, public authority participants, and other affected parties whose information, knowledge, participation, identity, data, or context may be used by or associated with the Corporation.
Pathway support may include:
a) consent form review;
b) non-consent record review;
c) withdrawal procedure review;
d) restriction notice review;
e) attribution preference review;
f) anonymity or pseudonymity review;
g) correction request intake;
h) takedown request intake;
i) grievance routing;
j) remedy routing;
k) participant communication;
l) controlled-room limitation;
m) publication limitation;
n) dashboard limitation;
o) dataset limitation;
p) AI-use limitation;
q) repository limitation;
r) public authority reference limitation;
s) records update; and
t) supersession, sealing, deletion, archive, or legal hold coordination.
Consent shall not be presumed from attendance, silence, failure to object, prior participation, public availability, public authority presence, sponsor presence, provider presence, academic participation, community membership, data contribution by a third party, or technical availability of information. Where consent is required and cannot be obtained or cannot be safely relied upon, the Corporation shall not proceed with the relevant use unless another lawful and safeguards-reviewed basis is recorded.
148.11 Grievance and Remedy Support. The Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer may support grievance and remedy systems where delegated. Grievance and remedy systems shall provide structured pathways for concerns relating to community harm, civil-rights harm, accessibility barriers, protected knowledge exposure, Indigenous protocol breach, data misuse, AI misuse, public-safe mapping risk, publication harm, public authority confusion, retaliation, harassment, exclusion, misattribution, misclassification, stigmatization, or misuse of the Corporation’s name, materials, dashboards, datasets, software, technical baselines, or public statements.
Grievance and remedy support may include:
a) intake pathways;
b) anonymous or confidential reporting where lawful and appropriate;
c) anti-retaliation notice;
d) triage;
e) urgent hold or stop-the-line review;
f) conflict and independence review;
g) fact-gathering;
h) affected-person or affected-community communication;
i) protected knowledge handling;
j) privacy and cyber coordination;
k) public authority boundary coordination;
l) corrective action recommendation;
m) remedy recommendation;
n) correction, supersession, withdrawal, retraction, takedown, restriction, apology, clarification, access change, training, discipline, or termination pathway;
o) appeal or review pathway where adopted;
p) closure record; and
q) post-closure monitoring where appropriate.
A grievance process shall not be used to suppress lawful dissent, punish protected participation, avoid correction, shield sponsors or providers, shield public authority relationships, protect institutional reputation at the expense of affected persons or communities, or convert the Corporation into a court, regulator, public authority, law-enforcement body, or legal-adjudication forum.
148.12 Protected Participation and Non-Retaliation Support. The Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer shall support protected participation and non-retaliation controls where delegated. Protected participation includes good-faith raising of concerns, dissent, methodological challenge, evidence challenge, civil-rights concern, accessibility concern, protected knowledge concern, public-safe mapping concern, data / AI / cyber concern, research-integrity concern, conflict concern, public authority boundary concern, finance-boundary concern, procurement-boundary concern, certification-boundary concern, provider-neutrality concern, sponsor-control concern, or legal compliance concern.
Non-retaliation controls may include:
a) confidential reporting channels;
b) anti-retaliation notices;
c) access restriction for alleged retaliators where appropriate;
d) independent review;
e) conflict-free escalation;
f) protection of complainant identity where lawful and appropriate;
g) separation of roles;
h) prohibition on adverse participation consequences for good-faith reports;
i) prohibition on funding, sponsorship, provider, public authority, employment, fellowship, advisory, or repository retaliation;
j) documentation of responsive action;
k) correction of retaliatory records or statements;
l) remedy and restoration; and
m) disciplinary, contractual, access, or legal response where warranted.
No person shall be disadvantaged, excluded, threatened, disciplined, defamed, de-platformed, deprived of access, denied participation, denied payment lawfully owed, deprived of attribution, or subjected to adverse public reference because the person made a good-faith safeguards report, evidence challenge, protected knowledge objection, civil-rights complaint, accessibility complaint, public-safe mapping objection, conflict disclosure, or boundary escalation.
148.13 Safeguards Stop-the-Line Support. The Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer may exercise or support safeguards stop-the-line authority where delegated. Safeguards stop-the-line authority shall permit a temporary hold, restriction, quarantine, publication freeze, access freeze, dashboard freeze, map freeze, dataset freeze, model-use freeze, technical asset freeze, controlled-room limitation, public authority reference hold, sponsor reference hold, provider reference hold, or other protective action when an activity presents credible risk of serious community harm, civil-rights harm, accessibility failure, protected knowledge exposure, Indigenous protocol breach, public-safe mapping harm, data / AI / cyber harm, retaliation, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider preference, sponsor control, or other boundary breach.
Safeguards stop-the-line support shall include:
a) identification of the triggering concern;
b) immediate scope of hold or restriction;
c) affected materials, systems, rooms, records, outputs, participants, publications, dashboards, maps, datasets, models, repositories, or public statements;
d) notice to responsible officer, committee, counsel, compliance function, Chair, Executive Director or Chief Executive Officer, or Board as appropriate;
e) preservation of evidence and records;
f) protection against retaliation;
g) review pathway;
h) corrective action pathway;
i) decision to release, modify, restrict, withdraw, correct, take down, archive, refer, or terminate; and
j) closeout record.
Stop-the-line authority shall be protective, time-sensitive, record-supported, and reviewable. It shall not be used for personal disagreement, institutional politics, sponsor preference, provider preference, public authority pressure, avoidance of lawful transparency, suppression of dissent, or evasion of Board authority.
148.14 No Extraction of Protected Knowledge for Sponsor, Provider, Donor, Funder, Host, Public Authority, or Institutional Convenience. No protected knowledge, Indigenous knowledge, Tribal knowledge, local knowledge, territorial knowledge, cultural knowledge, environmental knowledge, community-held knowledge, vulnerability information, sensitive geospatial information, public-safe mapping information, cyber-sensitive information, infrastructure-sensitive information, health-sensitive information, disaster-sensitive information, or retaliation-sensitive information shall be collected, extracted, inferred, modeled, mapped, published, disclosed, transferred, licensed, commercialized, benchmarked, used for AI training or retrieval, incorporated into public-good software, converted into a technical baseline, or made available through a controlled room, data room, dashboard, map, digital twin, repository, public authority interface, sponsor interface, provider interface, donor report, funder report, media product, Nexus interface, GRF-facing input, or GRA-facing technical input for sponsor convenience, provider convenience, donor convenience, funder convenience, host convenience, public authority convenience, institutional convenience, research convenience, publication convenience, grant convenience, demonstration value, technical curiosity, market value, or reputational benefit.
The Corporation shall apply the following governing principles:
a) protected knowledge is not a raw material for institutional advantage;
b) public-good purpose does not eliminate the need for safeguards;
c) technical usefulness does not create permission;
d) public visibility does not eliminate sensitivity;
e) public authority interest does not create consent;
f) sponsor or provider support does not create access entitlement;
g) research ambition does not override community harm prevention;
h) AI capability does not justify extraction;
i) mapping precision does not justify exposure;
j) ledger, proof-receipt, or repository recordation does not cure misuse;
k) public-safe publication requires actual public-safe review; and
l) correctionability requires meaningful withdrawal, restriction, takedown, correction, sealing, deletion, or archive pathways where harm risk is identified.
Where a protected knowledge concern arises, the Corporation shall apply the more protective lawful interpretation pending review. The relevant activity shall be held, restricted, compartmentalized, re-scoped, aggregated, redacted, anonymized, localized, delayed, withdrawn, corrected, taken down, referred, or terminated as necessary to prevent or reduce harm.
148.15 Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer Records. The Corporation shall maintain Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer Records sufficient to demonstrate the Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer’s appointment, term, eligibility, authority, delegations, community safeguards oversight, Tribal and Indigenous protocol support, Indigenous data and Indigenous knowledge safeguards support, local, territorial, cultural, environmental, and protected knowledge safeguards support, civil-rights support, non-discrimination support, accessibility support, vulnerable-community safeguards, remote-community safeguards, disaster-exposed safeguards, climate-exposed safeguards, health-exposed safeguards, infrastructure-exposed safeguards, high-risk community safeguards, public-safe mapping review support, consent and non-consent pathway support, attribution pathway support, withdrawal pathway support, restriction pathway support, correction pathway support, grievance support, remedy support, protected participation support, non-retaliation support, safeguards stop-the-line support, protected knowledge non-extraction controls, conflicts, recusals, restrictions, succession, and closeout.
Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer Records shall include, as applicable:
a) appointment or election record;
b) term and renewal record;
c) eligibility, consent, fit-and-proper, integrity, conflict, independence, sanctions, export-control, controlled-technology, public authority boundary, finance-boundary, certification-boundary, procurement-neutrality, recognition-boundary, provider-neutrality, sponsor non-control, data / AI / cyber, privacy, research integrity, evidence integrity, methods integrity, civil-rights, accessibility, community safeguards, Tribal and Indigenous protocol, Indigenous data, Indigenous knowledge, protected knowledge, public-safe mapping, grievance, remedy, non-retaliation, and stop-the-line screening records;
d) duty acknowledgment and certification of understanding;
e) role description;
f) reporting line;
g) authority matrix entry;
h) separate delegations;
i) community safeguards review records;
j) Tribal and Indigenous protocol records;
k) Indigenous data safeguard records;
l) Indigenous knowledge safeguard records;
m) local, territorial, cultural, environmental, community-protected, and protected knowledge records;
n) civil-rights, non-discrimination, accessibility, disability-access, language-access, public-legibility, and inclusive-participation records;
o) vulnerable-community, remote-community, disaster-exposed, climate-exposed, health-exposed, infrastructure-exposed, cyber-exposed, environmental-justice, public-safety, and high-risk community review records;
p) public-safe mapping, geospatial, Earth observation, sensor, digital twin, dashboard, observability, AI-generated spatial output, infrastructure map, health map, cyber map, and location-sensitive output records;
q) consent, non-consent, withdrawal, restriction, attribution, anonymity, pseudonymity, correction, takedown, sealing, deletion, return, archive, and legal hold records;
r) grievance, remedy, confidential reporting, protected participation, whistleblowing, dissent protection, non-retaliation, investigation, corrective action, appeal, closure, and post-closure monitoring records;
s) safeguards stop-the-line, hold, quarantine, access restriction, publication freeze, dashboard freeze, map freeze, dataset freeze, model-use freeze, repository freeze, controlled-room limitation, correction, withdrawal, retraction, takedown, and release records;
t) protected knowledge non-extraction, sponsor access, provider access, donor access, funder access, host access, public authority access, media access, AI-use restriction, technical asset restriction, repository restriction, cross-border restriction, and public-safe publication limitation records;
u) public-safe notices, limitation language, no-reliance language, controlled vocabulary notes, compatibility notes, divergence logs, and correction notices;
v) escalations involving public authority boundary, finance boundary, certification boundary, procurement neutrality, recognition boundary, provider neutrality, sponsor non-control, data / AI / cyber, privacy, safeguards, protected knowledge, civil rights, accessibility, competition, sanctions, export-control, controlled technology, research integrity, public-safe publication, professional boundary, or legal risk;
w) conflicts, recusals, access restrictions, delegation restrictions, resignation, removal, handover, access revocation, and closeout records; and
x) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that the Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer safeguards persons, communities, rights, accessibility, protected knowledge, and public-safe participation, not external authority. Safeguards reviews, civil-rights reviews, accessibility reviews, Tribal or Indigenous protocol reviews, protected knowledge restrictions, public-safe mapping reviews, grievance records, remedy records, non-retaliation controls, and stop-the-line actions may hold, restrict, correct, withdraw, take down, or re-scope the Corporation’s activities, but they do not create certification, recognition, finance-readiness, procurement approval, public authority action, public warning, emergency command, rating, provider approval, sponsor entitlement, or enterprise execution authority. Safeguards stewardship is lawful, rights-respecting, accessible, non-extractive, public-safe, bounded, record-supported, non-executing, role-separated, reviewable, and correctionable.
Section 149. Chief Legal, Compliance, and Risk Officer
149.1 Chief Legal, Compliance, and Risk Officer Role Where Approved. The Chief Legal, Compliance, and Risk Officer, where such office is approved by the Board, shall serve as the principal legal-compliance, corporate-compliance, nonprofit-compliance, tax-compliance, charitable-solicitation, state-qualification, foreign-qualification, privacy-compliance, AI-governance-compliance, cybersecurity-compliance, research-ethics-compliance, employment-compliance, contractor-compliance, volunteer-compliance, civil-rights-compliance, accessibility-compliance, sanctions-compliance, export-control-compliance, controlled-technology, national-security-sensitivity, competition, antitrust, procurement-integrity, grant-compliance, lobbying, political-activity, government-ethics, gifts, professional-boundary, regulatory-perimeter, risk-register, issue-register, control-register, incident-register, investigation, enforcement, appeal, corrective-action, counsel-coordination, privilege-protection, legal-hold, compliance-training, and legal-risk escalation officer of the Corporation, subject at all times to applicable law, the Articles or Certificate, this Bylaw, Board resolutions, Board-approved policies, the delegation matrix, the authority matrix, approved budget, fiduciary oversight, public-benefit purpose, nonprofit and non-distribution character, tax-exempt or tax-exempt-compatible restrictions, non-execution, GCRI / GRF / GRA role separation, public-good stack and enterprise stack separation, public authority boundary controls, finance-boundary controls, certification-boundary controls, procurement-neutrality controls, provider-neutrality controls, sponsor non-control controls, data / AI / cyber controls, research integrity controls, safeguards, protected knowledge restrictions, controlled vocabulary, validity-by-record, and correctionability.
The Chief Legal, Compliance, and Risk Officer’s office exists to support lawful, bounded, risk-aware, record-supported, public-benefit, non-executing, role-separated, compliance-disciplined, privilege-protected, correctionable operation of the Corporation. The office may coordinate legal review, compliance review, counsel engagement, risk escalation, incident response, records integrity, regulatory-perimeter controls, public-safe limitation language, and corrective action; provided that the office shall not, by title, legal function, compliance function, risk function, counsel interface, register custody, incident review, investigation role, or approval workflow alone, be treated as a substitute Board, court, regulator, public authority, public warning authority, emergency command authority, certification body, procurement body, public finance authority, finance-readiness authority, standards authority, protocol authority, rating agency, insurer, lender, broker, dealer, investment adviser, or enterprise execution actor.
The Chief Legal, Compliance, and Risk Officer shall not, unless separately and lawfully authorized and qualified, be treated as:
a) a person authorized to provide legal advice to third parties;
b) a person authorized to practice law where not admitted or otherwise permitted by law;
c) a person authorized to issue binding legal opinions on behalf of the Corporation unless expressly delegated and, where required, acting through or under counsel;
d) a person authorized to bind public authorities, GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Standards, consortiums, national companies, Project SPVs, sponsors, donors, funders, providers, hosts, universities, laboratories, communities, Indigenous knowledge holders, capital readers, insurers, lenders, investors, or enterprise-stack actors;
e) a person authorized to waive Board approval, member approval where required, counsel review where required, tax review where required, public authority clearance where required, privacy review, AI review, cybersecurity review, research ethics review, safeguards review, protected knowledge review, sanctions review, export-control review, controlled-technology review, or competition review;
f) a person authorized to approve regulated execution, public authority action, public warning, emergency command, public finance approval, finance-readiness, insurance-readiness, certification, accreditation, procurement approval, recognition, standing, maturity determination, rating, provider preference, sponsor entitlement, or enterprise execution; or
g) a person authorized to convert legal review, compliance review, risk classification, counsel coordination, incident review, register entry, controlled vocabulary note, limitation language, public-safe notice, proof receipt, Docket-support record, Grid-support record, GRF-facing input, GRA-facing technical input, public authority room record, or Nexus-compatible interface record into external authority.
149.2 Legal Compliance Support. The Chief Legal, Compliance, and Risk Officer may support legal compliance across the Corporation where delegated. Legal compliance support shall include identifying, routing, monitoring, escalating, documenting, and supporting the resolution of legal questions affecting corporate governance, nonprofit operation, public-benefit purpose, tax status, fundraising, contracts, intellectual property, research, data, privacy, AI, cybersecurity, publications, public authority interfaces, state and territorial operations, Tribal and Indigenous interfaces, cross-border matters, grants, sponsorships, employment, contracting, controlled rooms, technical assets, public-good software, public-safe reporting, Nexus interfaces, GRF-facing inputs, GRA-facing technical inputs, and enterprise-stack boundaries.
Legal compliance support may include:
a) legal issue intake;
b) legal-risk classification;
c) legal review routing;
d) counsel engagement;
e) matter tracking;
f) legal hold coordination;
g) privilege marking and segregation;
h) document-control support;
i) regulatory-perimeter screening;
j) public-safe limitation language review;
k) legal approval pathway mapping;
l) legal-risk reporting to officers, committees, and the Board;
m) corrective action support; and
n) closeout and archive records.
Legal compliance support shall not be used to create informal legal clearance, operational comfort, silent exceptions, undocumented approvals, or practice-based amendments. Where a matter materially affects legal status, tax status, nonprofit character, mission lock, public-benefit purpose, public authority boundaries, finance boundaries, procurement neutrality, certification boundaries, recognition boundaries, data / AI / cyber controls, safeguards, protected knowledge, or Board reserved matters, the matter shall be escalated to the appropriate officer, committee, counsel, compliance function, or Board.
149.3 Corporate Compliance Support. The Chief Legal, Compliance, and Risk Officer may support corporate compliance where delegated. Corporate compliance support shall include monitoring and supporting compliance with the Corporation’s governing statute, Articles or Certificate, Bylaw, Board resolutions, officer delegations, committee charters, member approvals where applicable, records requirements, registered-agent requirements, registered-office requirements, annual-report requirements, state filing requirements, director and officer register requirements, minute-book requirements, authority matrix requirements, and repository or gazette requirements.
Corporate compliance support may address:
a) good standing;
b) registered agent and registered office records;
c) principal office and governance seat records;
d) corporate filings;
e) annual reports;
f) franchise tax filings where applicable;
g) Board and committee action validity;
h) director, officer, committee, and member records where applicable;
i) delegation records;
j) authority matrix records;
k) bylaws, policies, schedules, protocols, registers, forms, matrices, and operating-instrument records;
l) state and territorial qualification status;
m) charitable solicitation status where applicable; and
n) correction, restatement, ratification, or remedial filings where required.
No failure of administrative convenience shall justify operating outside corporate authority. Where a corporate compliance defect may affect the validity of an act, the authority of a person, the status of a record, the good standing of the Corporation, or the legality of state, territorial, Tribal, local, or cross-border operation, the matter shall be held, corrected, ratified where lawful, re-scoped, or escalated.
149.4 Federal Tax and State Nonprofit Compliance Support. The Chief Legal, Compliance, and Risk Officer may support federal tax and state nonprofit compliance where delegated and in coordination with the Treasurer or Chief Financial Officer, counsel, tax advisors, auditors, finance committee, and Board where required. Such support shall preserve the Corporation’s nonprofit, non-share or non-stock, non-distributing, public-benefit, tax-exempt or tax-exempt-compatible character and prevent private inurement, impermissible private benefit, excess benefit transactions, unrelated business risk, improper receipting, restricted-fund misuse, donor-control risk, sponsor-control risk, and public misrepresentation of tax status.
Federal tax and state nonprofit compliance support may include review of:
a) federal tax classification records;
b) IRS recognition or application records where applicable;
c) annual federal tax filings;
d) state nonprofit filings;
e) state and local tax filings;
f) unrelated business income risk;
g) donation receipting authority;
h) restricted fund treatment;
i) grant conditions;
j) sponsorship benefits;
k) subscription, fee, Academy, training, fellowship, challenge, lab, publication, data-room, controlled-room, and cost-recovery revenue classification;
l) compensation and reimbursement reasonableness;
m) related-party transactions;
n) private benefit and inurement risk;
o) lobbying and political activity boundaries where applicable; and
p) dissolution, asset dedication, and public-good asset distribution obligations.
No officer, committee, sponsor, donor, funder, provider, host, participant, public authority participant, university, laboratory, or Nexus interface actor may represent the Corporation’s tax status beyond the competent record. Where charitable status, tax-deductibility, public charity status, private foundation status, fiscal sponsorship, supporting organization status, Section 501(c)(3), Section 501(c)(4), Section 501(c)(6), or other tax classification is uncertain, pending, limited, suspended, revoked, or not obtained, public materials and transaction documents shall state only the recorded status.
149.5 Charitable Solicitation and Foreign Qualification Support. The Chief Legal, Compliance, and Risk Officer may support charitable solicitation, state qualification, territorial qualification, and foreign registration or qualification where delegated. Such support shall apply when the Corporation solicits donations, grants, sponsorships, subscriptions, public-good support, restricted funds, in-kind contributions, memberships, fees, or public-facing support in jurisdictions requiring registration, qualification, exemption, filing, notice, disclosure, tax review, public-benefit review, or other lawful compliance step.
Charitable solicitation and qualification support may include:
a) jurisdictional trigger review;
b) state charitable solicitation registration;
c) renewal and annual filing support;
d) charitable disclosure language review;
e) fundraiser, platform, campaign, event, digital-solicitation, and donor-communication review;
f) commercial co-venture review where applicable;
g) professional fundraiser or fundraising consultant review where applicable;
h) foreign qualification or certificate-of-authority review;
i) territorial registration review;
j) cross-border solicitation review;
k) public authority grant registration review;
l) tax and receipting coordination;
m) donor, sponsor, and funder public acknowledgment controls; and
n) solicitation records and correction records.
No solicitation shall proceed merely because it is mission-aligned, urgent, sponsor-supported, donor-requested, digitally easy, event-driven, grant-driven, or publicly beneficial if required registrations, disclosures, tax treatment, authority, or records are missing. Where uncertainty exists, the Corporation shall apply the more restrictive lawful posture pending review.
149.6 Privacy, AI, Cybersecurity, Research Ethics, Employment, Civil Rights, Accessibility, Grant, Lobbying, Political Activity, Government Ethics, Procurement Integrity, and Public Authority Compliance Support Where Applicable. The Chief Legal, Compliance, and Risk Officer may support cross-functional compliance for privacy, data protection, AI governance, cybersecurity, research ethics, employment, contractor, volunteer, fellow, advisor, workplace, civil-rights, accessibility, grant, lobbying, political activity, government ethics, gifts, procurement integrity, and public authority interaction requirements where delegated and in coordination with responsible officers, committees, counsel, compliance professionals, and subject-matter experts.
Such compliance support may include review of:
a) privacy notices, data-processing terms, data-sharing terms, retention rules, deletion rules, 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, and protected knowledge;
b) AI governance rules, model-register requirements, inference records, compute workload records, training-data restrictions, fine-tuning restrictions, embedding restrictions, retrieval restrictions, agentic AI controls, human-review thresholds, automated-output limitations, and AI incident pathways;
c) cybersecurity controls, access controls, identity controls, credential controls, key controls, vulnerability handling, incident response, disaster recovery, business continuity, secure development, secure release, SBOM, signing, provenance, and vendor security;
d) research ethics, human-subjects review, IRB or equivalent review, community review, Tribal and Indigenous protocol review, protected knowledge review, youth and vulnerable participant review, informed consent, withdrawal, and research misconduct pathways;
e) employment, contractor, volunteer, fellow, advisor, seconded-personnel, workplace, harassment, retaliation, classification, safety, and training compliance;
f) civil-rights, non-discrimination, accessibility, disability access, language access, public-legibility, and inclusive participation obligations;
g) grants, restricted funds, federal awards, state awards, public authority conditions, reporting obligations, procurement restrictions, cost allowability, audit rights, and public authority records requirements;
h) lobbying, political activity, campaign activity, grassroots communications, public policy education, government ethics, gifts, hospitality, conflicts, and public official interaction limits; and
i) procurement integrity, public records, FOIA, state sunshine, open meetings, confidentiality, public authority reference, public authority room, regulator-listening, public finance reader, emergency-management participant, and public infrastructure operator rules.
No compliance support under this Section shall permit the Corporation to conduct regulated activities, public authority functions, procurement functions, certification functions, recognition functions, finance-readiness functions, public warning functions, emergency command functions, or enterprise execution functions. Compliance review is a boundary discipline, not an authority generator.
149.7 Sanctions and Export-Control Compliance Support. The Chief Legal, Compliance, and Risk Officer may support sanctions and export-control compliance where delegated. Such support shall apply to persons, entities, jurisdictions, software, datasets, models, technical baselines, AI systems, compute systems, encryption, cyber tools, AI-RAN / O-RAN materials, DePIN materials, DLT / blockchain materials, dual-use technologies, controlled technology, public authority interfaces, cross-border data transfers, foreign participation, sponsorships, grants, donations, in-kind support, technical contributions, repository access, controlled rooms, no-download rooms, technical assistance, and publication activities where sanctions or export-control risk may arise.
Sanctions and export-control compliance support may include:
a) restricted-party screening;
b) jurisdictional screening;
c) beneficial ownership or control review where applicable;
d) export classification review;
e) controlled-technology review;
f) deemed-export review;
g) technical-assistance review;
h) encryption and cybersecurity tool review;
i) dual-use and national security sensitivity review;
j) license-exception or authorization review where applicable;
k) access restriction;
l) repository restriction;
m) controlled-room restriction;
n) publication restriction;
o) sanctions clause and export-control clause review;
p) escalation to counsel or external specialists; and
q) records, screening logs, holds, refusals, releases, and corrective actions.
No urgency, public-good purpose, humanitarian purpose, research purpose, open-source purpose, sponsor request, provider request, public authority request, academic request, technical convenience, or cross-border collaboration shall waive sanctions, export-control, controlled-technology, or national security sensitivity review where required. Where a sanctions or export-control risk cannot be resolved, the activity shall be refused, held, restricted, re-scoped, externalized, or terminated.
149.8 Controlled Technology and National Security Sensitivity Review Support. The Chief Legal, Compliance, and Risk Officer may support controlled-technology and national-security-sensitivity review where delegated. Controlled-technology review shall apply to technologies, data, software, models, compute workloads, test harnesses, benchmarks, cyber tools, security tooling, infrastructure information, telecommunications information, AI-RAN / O-RAN artifacts, DePIN infrastructure, DLT / blockchain infrastructure, digital twins, sensors, geospatial layers, Earth observation outputs, public-safe maps, critical infrastructure records, sovereign compute environments, confidential computing environments, and related mission-critical systems.
Controlled-technology and national-security-sensitivity review may include:
a) classification of sensitive technical information;
b) dual-use sensitivity review;
c) critical infrastructure sensitivity review;
d) cyber offense / defense boundary review;
e) telecom and network sensitivity review;
f) AI capability and model-risk sensitivity review;
g) geospatial and Earth observation sensitivity review;
h) sensor and observability sensitivity review;
i) public authority data sensitivity review;
j) foreign access sensitivity review;
k) cloud, compute, and vendor sensitivity review;
l) public release and open-source risk review;
m) controlled-room or no-download-room requirements;
n) data localization or sovereign compute considerations;
o) publication delay, redaction, aggregation, or restriction; and
p) escalation to counsel, security advisors, public authority contacts where lawful, or the Board where material.
Controlled-technology review shall not be used to exaggerate secrecy, suppress lawful public-interest reporting, create public authority status, or imply national security authorization. It is a protective legal and operational discipline to prevent unsafe disclosure, unlawful transfer, or misuse of sensitive technical materials.
149.9 Competition and Antitrust Compliance Support. The Chief Legal, Compliance, and Risk Officer may support competition and antitrust compliance where delegated. Competition and antitrust compliance support shall apply to Board meetings, committee meetings, Helix Councils, advisory forums, working groups, panels, research consortia, benchmarking activities, indices, datasets, shared repositories, standards-support activities, provider participation, sponsor participation, host participation, public authority rooms, controlled rooms, clean rooms, data rooms, labs, challenges, Academy activities, public statements, market baselines, and enterprise-stack interfaces.
Competition and antitrust compliance support may include:
a) agenda review;
b) do-not-discuss list maintenance;
c) meeting-chair and facilitator training;
d) competition-law notices;
e) clean-team design;
f) clean-room design;
g) aggregation, de-identification, delay, and independent administration controls;
h) competitively sensitive information classification;
i) data-sharing controls;
j) benchmarking controls;
k) provider, sponsor, host, and enterprise participant restrictions;
l) procurement-neutrality review;
m) minute review;
n) stop-meeting authority support;
o) incident escalation;
p) corrective action; and
q) competition records.
No meeting, working group, Helix Council, challenge, lab, data-sharing exercise, benchmark, technical comparison, provider interface, sponsor interface, public authority interface, or Nexus interface shall be used to discuss or coordinate prices, margins, costs, bids, wages, customers, suppliers, markets, territories, capacity, exclusion, boycotts, procurement steering, vendor selection, investment strategy, underwriting strategy, insurance pricing, lending terms, or other collusive or competitively sensitive conduct.
149.10 Professional Boundary Review Support. The Chief Legal, Compliance, and Risk Officer may support professional boundary review where delegated. Professional boundary review shall ensure that the Corporation’s reports, evidence outputs, public-safe publications, technical baselines, dashboards, maps, software, datasets, AI outputs, Academy materials, public authority learning sessions, simulations, tabletop exercises, controlled-room materials, GRF-facing inputs, GRA-facing technical inputs, and Nexus-compatible materials are not misrepresented as legal advice, engineering certification, clinical advice, medical advice, public health order, safety order, investment advice, insurance advice, lending advice, underwriting advice, rating opinion, accounting advice, tax advice, procurement advice, regulatory approval, or other professional advice unless separately and lawfully authorized by competent professionals, competent authority, and governing records.
Professional boundary review may address:
a) intended audience;
b) scope of output;
c) professional reliance risk;
d) limitation language;
e) non-reliance notices;
f) review by licensed professionals where required;
g) public authority boundary language;
h) finance-boundary language;
i) certification-boundary language;
j) procurement-neutrality language;
k) public warning and emergency command disclaimers;
l) no-investment-advice and no-securities-solicitation notices;
m) no-insurance, no-lending, no-rating, and no-public-finance-approval notices;
n) no-engineering-certification or no-professional-certification notices;
o) controlled vocabulary review; and
p) correction, withdrawal, takedown, or public clarification where needed.
Professional boundary review shall not prevent the Corporation from conducting lawful research, education, evidence analysis, methods development, technical literacy, public-good software development, or public authority learning. It shall ensure that such work is not inflated into regulated professional services or external reliance beyond lawful scope.
149.11 Regulatory-Perimeter Escalation Support. The Chief Legal, Compliance, and Risk Officer shall support regulatory-perimeter escalation where delegated. Regulatory-perimeter escalation shall be triggered whenever an activity, output, relationship, agreement, communication, dashboard, dataset, software release, public authority room, controlled room, capital-reader room, public statement, sponsorship, grant, donation, provider interface, public authority interface, Nexus interface, GRF-facing input, or GRA-facing technical input may reasonably implicate securities, investment adviser, broker-dealer, finder, insurance, banking, lending, underwriting, rating, public finance, procurement, certification, accreditation, public authority, public warning, emergency command, professional licensing, export-control, sanctions, controlled-technology, competition, privacy, AI, cyber, research ethics, civil-rights, accessibility, or protected knowledge boundaries.
Regulatory-perimeter escalation support shall include:
a) intake of perimeter concern;
b) immediate risk classification;
c) hold, stop, quarantine, or restriction recommendation where needed;
d) identification of affected materials, participants, systems, rooms, outputs, publications, dashboards, maps, datasets, repositories, technical assets, public statements, agreements, and records;
e) routing to counsel, compliance, responsible officer, committee, Chair, Executive Director or Chief Executive Officer, or Board where required;
f) privilege and confidentiality controls;
g) controlled or public notice where required;
h) remediation plan;
i) re-scoping, function separation, externalization, referral, abandonment, or termination recommendation; and
j) closeout, correction, supersession, withdrawal, archive, and metadata records.
No person may rely on informal comfort, silence, past practice, sponsor expectation, provider expectation, public authority interest, grant deadline, publication deadline, technical urgency, fundraising need, or market pressure as a substitute for regulatory-perimeter escalation where a material boundary risk exists.
149.12 Risk Register, Issue Register, Control Register, and Incident Register Support. The Chief Legal, Compliance, and Risk Officer may support the Corporation’s risk register, issue register, control register, and incident register where delegated. Such registers shall support structured identification, classification, ownership, monitoring, escalation, correction, and closure of legal, compliance, governance, tax, financial, operational, research, evidence, methods, data, AI, cyber, privacy, safeguards, public authority, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, sponsor non-control, competition, sanctions, export-control, controlled-technology, public-safe publication, reputational, continuity, and Nexus-interface risks.
Register support may include:
a) risk taxonomy;
b) issue classification;
c) control mapping;
d) incident classification;
e) severity level;
f) likelihood and impact assessment;
g) responsible owner;
h) affected function;
i) affected instrument;
j) affected jurisdiction;
k) affected public authority, community, technical asset, repository, room, publication, dataset, model, dashboard, map, sponsor, provider, host, or Nexus interface;
l) mitigation plan;
m) escalation pathway;
n) deadline;
o) review cycle;
p) evidence and record links;
q) closure criteria;
r) correction, supersession, withdrawal, takedown, or public clarification status; and
s) archive and retention metadata.
Registers are evidence and governance instruments. A register entry shall not, by itself, create certification, recognition, finance-readiness, public authority action, procurement approval, provider approval, sponsor entitlement, public warning, emergency command, rating, legal opinion, or enterprise execution authority.
149.13 Investigation, Enforcement, Appeal, and Corrective Action Support. The Chief Legal, Compliance, and Risk Officer may support investigations, enforcement processes, appeals, and corrective actions where delegated. Such support may apply to alleged breaches of law, Articles or Certificate, this Bylaw, Board resolutions, policies, codes, contracts, grant terms, sponsorship terms, data rules, AI rules, cyber rules, research integrity rules, safeguards, confidentiality, public-safe publication rules, controlled vocabulary, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, competition rules, sanctions, export-control, controlled-technology restrictions, or professional boundaries.
Investigation, enforcement, appeal, and corrective action support may include:
a) intake and triage;
b) conflict and independence review;
c) scope definition;
d) preservation of records;
e) legal hold coordination;
f) privilege and work-product controls;
g) confidentiality and non-retaliation controls;
h) interim access restriction;
i) fact gathering;
j) witness or participant communication;
k) public authority notification review where applicable;
l) sponsor, donor, funder, provider, host, university, laboratory, community, or affected-party notification review where applicable;
m) findings support;
n) corrective action plan;
o) appeal or review pathway where adopted;
p) remedy, discipline, contract action, access revocation, correction, withdrawal, takedown, retraction, public clarification, referral, or termination; and
q) closure and archive.
Investigations shall be fair, proportionate, record-supported, conflict-managed, confidentiality-protected where appropriate, and non-retaliatory. They shall not be used to suppress good-faith dissent, evidence challenges, safeguards concerns, civil-rights complaints, accessibility complaints, protected knowledge objections, public authority boundary concerns, finance-boundary concerns, or lawful whistleblowing.
149.14 Counsel Coordination. The Chief Legal, Compliance, and Risk Officer may coordinate with internal counsel, external counsel, special counsel, tax counsel, nonprofit counsel, employment counsel, intellectual-property counsel, privacy counsel, AI counsel, cybersecurity counsel, sanctions counsel, export-control counsel, competition counsel, government ethics counsel, public finance counsel, procurement counsel, litigation counsel, and other legal advisors where delegated and within budget or emergency authority.
Counsel coordination may include:
a) identifying the need for counsel;
b) preparing factual summaries;
c) preserving privilege;
d) coordinating document production;
e) tracking advice requests;
f) maintaining legal matter lists;
g) supporting Board and officer briefings;
h) coordinating counsel review of policies, contracts, publications, public authority materials, data rooms, controlled rooms, repositories, technical releases, grant instruments, sponsorship instruments, employment matters, investigations, disputes, and regulatory-perimeter matters;
i) tracking advice implementation;
j) maintaining legal budgets and engagement letters in coordination with finance where applicable; and
k) ensuring legal advice is recorded, protected, and implemented through competent action.
Counsel coordination shall not be confused with counsel authority unless the relevant person is properly authorized to act as counsel. Legal advice received by the Corporation shall be used for the Corporation’s lawful governance and compliance purposes and shall not be redistributed, quoted, summarized, or relied upon by third parties except as authorized by the Corporation, counsel, and applicable law.
149.15 Privilege Protection Support. The Chief Legal, Compliance, and Risk Officer shall support attorney-client privilege, work-product protection, common-interest or joint-defense protections where applicable, confidentiality, legal-hold integrity, investigation confidentiality, and sensitive compliance records where delegated. Privilege protection shall apply to legal advice, legal requests, counsel memoranda, litigation materials, regulatory matters, investigations, compliance escalations, legal-risk assessments, privileged Board materials, privileged committee materials, privileged officer materials, and privileged repository materials.
Privilege protection support may include:
a) privileged matter classification;
b) need-to-know access controls;
c) legal folder and repository controls;
d) controlled distribution;
e) privileged meeting designation;
f) minutes discipline;
g) document marking;
h) AI-use restrictions;
i) prohibition on uploading privileged materials to unapproved systems;
j) legal hold notices;
k) preservation instructions;
l) waiver-risk review;
m) common-interest agreement coordination where applicable;
n) inadvertent disclosure response;
o) clawback coordination where applicable; and
p) privilege log and record support.
Privilege shall not be used to conceal wrongdoing, suppress required correction, avoid lawful reporting, prevent Board oversight, block safeguards, or evade public-benefit obligations. Where law requires disclosure or notice, the Corporation shall coordinate with counsel to preserve privilege to the extent lawful while fulfilling legal obligations.
149.16 No Legal Opinion by Non-Lawyer Officer Unless Properly Authorized Under Law. No non-lawyer officer, employee, contractor, advisor, fellow, volunteer, contributor, committee member, working group participant, public authority participant, sponsor, provider, host, donor, funder, university participant, laboratory participant, community participant, or Nexus interface participant shall provide, issue, sign, circulate, publish, imply, or rely upon a legal opinion, tax opinion, regulatory opinion, public authority opinion, procurement opinion, securities opinion, insurance opinion, lending opinion, rating opinion, public finance opinion, export-control opinion, sanctions opinion, employment opinion, privacy opinion, AI compliance opinion, cybersecurity legal opinion, civil-rights legal opinion, Indigenous rights legal opinion, professional licensing opinion, or formal legal clearance on behalf of the Corporation unless the person is lawfully authorized, appropriately qualified, acting within scope, and the opinion is approved through the relevant legal and governance pathway.
Operational statements may identify recorded status, known facts, adopted policies, registered filings, approved notices, and limitation language, but shall not be converted into legal opinions. Where a public document, report, grant application, sponsorship material, contract, public authority material, repository notice, technical baseline, controlled-room material, dashboard, map, public-safe report, proof receipt, Docket-support material, Grid-support material, GRF-facing input, GRA-facing technical input, or Nexus-compatible material requires legal conclusion, counsel review shall be obtained where appropriate and the record shall identify the scope and limitation of the conclusion.
No legal review, compliance review, checklist, register entry, AI-generated summary, counsel note, meeting statement, public-safe notice, or officer email shall be represented as a formal legal opinion unless it is expressly designated as such by authorized counsel or competent authority and recorded accordingly.
149.17 Chief Legal, Compliance, and Risk Officer Records. The Corporation shall maintain Chief Legal, Compliance, and Risk Officer Records sufficient to demonstrate the Chief Legal, Compliance, and Risk Officer’s appointment, term, eligibility, authority, delegations, legal compliance support, corporate compliance support, federal tax and state nonprofit compliance support, charitable solicitation support, state qualification support, territorial qualification support, foreign qualification support, privacy compliance support, AI governance compliance support, cybersecurity compliance support, research ethics compliance support, employment compliance support, civil-rights compliance support, accessibility compliance support, grant compliance support, lobbying and political activity review support, government ethics support, gifts review support, procurement integrity support, public authority compliance support, sanctions compliance support, export-control compliance support, controlled-technology review support, national-security-sensitivity review support, competition and antitrust support, professional boundary review support, regulatory-perimeter escalation support, risk register support, issue register support, control register support, incident register support, investigation support, enforcement support, appeal support, corrective action support, counsel coordination, privilege protection support, legal-opinion boundary controls, conflicts, recusals, restrictions, succession, and closeout.
Chief Legal, Compliance, and Risk Officer Records shall include, as applicable:
a) appointment or election record;
b) term and renewal record;
c) eligibility, consent, fit-and-proper, integrity, conflict, independence, sanctions, export-control, controlled-technology, legal, compliance, risk, public authority boundary, finance-boundary, certification-boundary, procurement-neutrality, recognition-boundary, provider-neutrality, sponsor non-control, data / AI / cyber, privacy, research integrity, evidence integrity, methods integrity, civil-rights, accessibility, Tribal and Indigenous protocol, protected knowledge, competition, professional-boundary, and public-safe publication screening records;
d) duty acknowledgment and certification of understanding;
e) role description;
f) reporting line;
g) authority matrix entry;
h) separate delegations;
i) legal matter records;
j) compliance matter records;
k) corporate filing and good-standing records;
l) federal tax, state tax, nonprofit, charitable solicitation, state qualification, territorial qualification, foreign qualification, annual report, franchise tax, donation receipt, restricted fund, unrelated business income, private benefit, inurement, and excess benefit records;
m) privacy, AI governance, cybersecurity, research ethics, employment, contractor, volunteer, fellow, advisor, workplace, civil-rights, accessibility, grant, lobbying, political activity, government ethics, gifts, procurement integrity, public records, FOIA, open meetings, and public authority compliance records;
n) sanctions screening, export-control screening, restricted-party screening, beneficial ownership screening, controlled-technology, dual-use, deemed-export, technical-assistance, encryption, cyber tool, foreign access, publication restriction, and license or authorization records;
o) competition, antitrust, clean-team, clean-room, do-not-discuss, agenda review, minute review, stop-meeting, incident, training, and corrective action records;
p) professional boundary, no-legal-advice, no-engineering-opinion, no-clinical-advice, no-public-warning, no-emergency-command, no-investment-advice, no-insurance-advice, no-lending-advice, no-rating, no-public-finance-approval, no-procurement-approval, no-certification, no-recognition, and non-reliance records;
q) regulatory-perimeter intake, hold, stop, quarantine, restriction, publication freeze, implementation freeze, controlled-room lockdown, remediation, re-scoping, function separation, externalization, referral, termination, correction, and closeout records;
r) risk register, issue register, control register, incident register, severity, owner, mitigation, escalation, deadline, review, closure, correction, supersession, withdrawal, takedown, and archive records;
s) investigation, enforcement, appeal, grievance-interface, corrective action, discipline, contract action, access restriction, public or controlled correction, legal referral, regulatory referral, public authority referral, funder referral, law enforcement referral, and closure records;
t) counsel engagement letters, counsel instruction records, privileged request records, legal advice records, legal hold records, privilege logs, work-product records, common-interest records where applicable, waiver-risk records, inadvertent disclosure records, and privilege-protection records;
u) public-safe notice, limitation language, controlled vocabulary, legal disclaimer, non-reliance, correction, public clarification, and public statement review records;
v) escalations involving public authority boundary, finance boundary, certification boundary, procurement neutrality, recognition boundary, provider neutrality, sponsor non-control, data / AI / cyber, privacy, safeguards, protected knowledge, civil rights, accessibility, research integrity, public-safe publication, competition, sanctions, export-control, controlled technology, professional boundary, tax, nonprofit, corporate, or legal risk;
w) conflicts, recusals, access restrictions, delegation restrictions, resignation, removal, handover, access revocation, and closeout records; and
x) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that the Chief Legal, Compliance, and Risk Officer safeguards legality, compliance, risk discipline, regulatory-perimeter discipline, privilege, and correctionability, not external authority. Legal review, compliance review, risk classification, counsel coordination, register support, investigation support, corrective action, limitation language, and public-safe notice may protect the Corporation from unlawful, unsafe, authority-inflating, noncompliant, or role-collapsing conduct, but they do not create public authority action, legal advice to third parties, certification, recognition, finance-readiness, procurement approval, public warning, emergency command, rating, provider approval, sponsor entitlement, or enterprise execution authority. Legal, compliance, and risk stewardship is lawful, bounded, counsel-coordinated where required, record-supported, privilege-aware, non-executing, role-separated, public-safe, reviewable, and correctionable.
Section 150. Chief Operating Officer
150.1 Chief Operating Officer Role Where Approved. The Chief Operating Officer, where such office is approved by the Board, shall serve as the principal operations-management, program-operations, people-operations, vendor-operations, contractor-operations, facilities, tools, systems, administrative-controls, records-operations, business-continuity, operational-resilience, delegation-matrix implementation, internal-process discipline, procurement-process, contracting-process, operational-risk escalation, workflow, intake, routing, service-delivery, internal coordination, operational reporting, and closeout officer of the Corporation, subject at all times to applicable law, the Articles or Certificate, this Bylaw, Board resolutions, Board-approved policies, the delegation matrix, the authority matrix, approved budget, fiduciary oversight, public-benefit purpose, nonprofit and non-distribution character, tax-exempt or tax-exempt-compatible restrictions, non-execution, GCRI / GRF / GRA role separation, public-good stack and enterprise stack separation, public authority boundary controls, finance-boundary controls, certification-boundary controls, procurement-neutrality controls, provider-neutrality controls, sponsor non-control controls, data / AI / cyber controls, privacy controls, research integrity controls, evidence controls, methods controls, public-safe publication controls, safeguards, protected knowledge restrictions, controlled vocabulary, validity-by-record, and correctionability.
The Chief Operating Officer’s office exists to ensure that the Corporation’s lawful work is operationally serious, administratively reliable, records-supported, appropriately staffed or resourced, safely routed, timely executed within delegated authority, and continuously improved without weakening the Corporation’s constitutional boundaries. The office may coordinate internal operations, cross-functional workflows, program support, vendor administration, contractor administration, facilities, tools, systems, intake processes, records operations, continuity plans, operational dashboards, staff coordination, and implementation discipline; provided that no operational role shall convert the Corporation into an enterprise execution vehicle, public authority substitute, public warning body, emergency command body, procurement authority, certification body, recognition body, finance-readiness authority, regulated intermediary, provider selector, sponsor-controlled platform, or operational infrastructure operator.
The Chief Operating Officer shall not, by title, administrative centrality, operational urgency, access to staff, system administration, workflow ownership, budget implementation, vendor coordination, program coordination, public authority interface support, sponsor interface support, provider interface support, controlled-room administration, or crisis-management involvement alone, be treated as:
a) a substitute Board;
b) a person authorized to approve Board reserved matters;
c) a person authorized to amend this Bylaw, alter mission lock, alter non-execution, alter role separation, alter the public authority boundary, alter the finance boundary, alter certification or procurement boundaries, alter provider neutrality, alter sponsor non-control, alter data / AI / cyber controls, or alter safeguards;
d) a public authority, regulator, public warning authority, emergency command authority, procurement authority, public finance authority, certification authority, recognition authority, finance-readiness authority, rating authority, standards authority, protocol authority, infrastructure operator, asset owner, national company, Project SPV, qualified enterprise provider, or enterprise delivery actor;
e) a person authorized to bind GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Standards, consortiums, national companies, Project SPVs, sponsors, donors, funders, providers, hosts, public authorities, universities, laboratories, communities, Indigenous knowledge holders, capital readers, insurers, lenders, investors, or enterprise-stack actors without express lawful authority; or
f) a person authorized to convert operational implementation, workflow approval, vendor onboarding, contractor onboarding, program routing, room administration, dashboard launch support, publication routing, public authority logistics, sponsor logistics, provider logistics, repository administration, technical asset deployment, or continuity action into certification, recognition, finance-readiness, procurement approval, public authority action, public warning, emergency command, provider approval, sponsor entitlement, or enterprise execution.
150.2 Operations Management. The Chief Operating Officer may manage the day-to-day operations of the Corporation where delegated. Operations management shall include the coordination of people, processes, systems, tools, facilities, vendors, contractors, timelines, operating calendars, administrative controls, internal reporting, workflow performance, and operational follow-through necessary to implement Board-approved strategy, Board-approved budgets, officer-approved plans, approved policies, approved programs, approved controlled rooms, approved public authority learning activities, approved technical activities, approved publications, approved support relationships, and approved Nexus-compatible interfaces.
Operations management may include:
a) operational planning;
b) workstream coordination;
c) operating calendar maintenance;
d) meeting and milestone coordination;
e) intake and triage administration;
f) administrative routing;
g) staff, contractor, fellow, advisor, volunteer, and contributor coordination;
h) resource allocation within approved budgets;
i) operational dashboard preparation subject to confidentiality and public-safe limits;
j) task tracking and closeout;
k) implementation of internal controls;
l) operational issue escalation;
m) vendor and tool management;
n) facilities and event support;
o) continuity planning; and
p) maintenance of records demonstrating operational authority and completion.
Operations management shall be bounded by authority. No operational plan, workflow, dashboard, project management tool, meeting note, action list, implementation tracker, informal direction, standing practice, or urgency-based instruction shall create authority not granted by law, the Articles or Certificate, this Bylaw, Board resolution, policy, delegation, or competent record.
150.3 Program Operations Support. The Chief Operating Officer may support program operations where delegated. Program operations support may apply to evidence programs, methods programs, observability programs, ontology programs, technical truth programs, public-good R&D programs, public-good software programs, open technical baseline programs, Academy programs, fellowships, challenge programs, labs, controlled rooms, clean rooms, evidence rooms, data rooms, no-download rooms, public authority learning programs, public-safe publication workflows, Nexus Universe activities, Nexus Observatory support activities, Nexus Standards support activities, Nexus Grid support activities, Nexus Rails support activities, Nexus Competence Cell activities, GRF-facing inputs, and GRA-facing technical inputs.
Program operations support may include:
a) program launch readiness;
b) program workplan administration;
c) participant onboarding coordination;
d) eligibility and screening routing;
e) room logistics;
f) records setup;
g) timeline management;
h) agenda and materials coordination;
i) operational dependency tracking;
j) escalation of legal, finance, public authority, data / AI / cyber, safeguards, research-integrity, evidence, methods, or publication issues;
k) program closeout;
l) correction, supersession, withdrawal, archive, or takedown routing where needed; and
m) program records.
Program operations support shall not become program authority beyond delegation. The Chief Operating Officer may coordinate the execution of approved program processes but shall not approve research conclusions, evidence classifications, method validity, technical truth outputs, public-safe publication, public authority references, finance-boundary determinations, GRF recognition inputs, GRA finance-readiness inputs, Nexus-compatible claims, certification-adjacent claims, procurement-adjacent claims, or safeguards-sensitive outputs except within express delegation and required review pathways.
150.4 People Operations Support. The Chief Operating Officer may support people operations where delegated and in coordination with the President, Executive Director or Chief Executive Officer, Secretary, Treasurer or Chief Financial Officer, Chief Legal, Compliance, and Risk Officer, safeguards function, and responsible supervisors. People operations support may apply to employees, contractors, consultants, fellows, advisors, volunteers, seconded personnel, technical contributors, maintainers, interns, program participants, and other persons performing work for or with the Corporation.
People operations support may include:
a) onboarding coordination;
b) role description administration;
c) workplan coordination;
d) access request routing;
e) training coordination;
f) certification-of-understanding tracking;
g) confidentiality and conduct acknowledgment tracking;
h) conflict disclosure routing;
i) time, attendance, and deliverable coordination where applicable;
j) contractor and consultant administration;
k) volunteer and fellow administration;
l) performance support within delegated authority;
m) offboarding coordination;
n) access revocation coordination;
o) return, deletion, sealing, or transfer of materials; and
p) people operations records.
People operations support shall not override employment law, contractor classification rules, civil-rights obligations, accessibility obligations, anti-harassment obligations, non-retaliation obligations, wage and hour rules, grant conditions, immigration or work authorization rules where applicable, conflict controls, confidentiality restrictions, data / AI / cyber controls, protected knowledge restrictions, or Board and officer appointment requirements. No person shall be treated as an officer, fiduciary, authorized representative, public spokesperson, public authority liaison, repository maintainer, controlled-room participant, or Nexus interface actor unless the relevant appointment, delegation, access, and record requirements have been satisfied.
150.5 Vendor and Contractor Operations Support. The Chief Operating Officer may support vendor and contractor operations where delegated. Vendor and contractor operations support shall include administrative coordination of procurement processes, contracting workflows, onboarding, deliverable tracking, access coordination, invoice routing, performance monitoring, issue escalation, renewal tracking, closeout, and record maintenance, subject to applicable law, approved budget, authority matrix, procurement-neutrality controls, conflicts controls, related-party controls, data / AI / cyber controls, confidentiality, sanctions, export-control, controlled-technology review, safeguards, and private-benefit controls.
Vendor and contractor operations support may address:
a) vendor intake;
b) contractor intake;
c) scope-of-work administration;
d) competitive or comparative process support where required;
e) conflict and related-party routing;
f) sanctions and export-control routing;
g) data-processing and cybersecurity routing;
h) insurance and indemnity documentation routing where required;
i) confidentiality and IP documentation routing;
j) procurement-neutrality and provider-neutrality review;
k) deliverable tracking;
l) invoice and payment routing;
m) renewal, termination, or closeout administration; and
n) vendor and contractor records.
Vendor or contractor administration shall not create preferred provider status, Nexus-compatible status, certification, recognition, finance-readiness, procurement advantage, public authority endorsement, sponsor entitlement, or enterprise-stack standing. No vendor or contractor shall receive access to restricted data, controlled rooms, public authority materials, protected knowledge, model registers, inference records, compute workload records, technical assets, repositories, public-safe publication drafts, or confidential Board or officer materials beyond approved access class and documented need.
150.6 Facilities, Tools, Systems, and Administrative Controls. The Chief Operating Officer may support the Corporation’s facilities, tools, systems, and administrative controls where delegated. Such support may include physical office arrangements, remote-work systems, meeting systems, document-management systems, workflow tools, issue trackers, access-request tools, repository administration support, controlled-room platforms, no-download-room tooling, secure communication tools, calendaring systems, task-management systems, procurement systems, finance-administration systems, and other operational infrastructure necessary for lawful public-benefit administration.
Facilities, tools, systems, and administrative controls shall be selected, configured, and used in a manner consistent with:
a) data classification;
b) privacy requirements;
c) cybersecurity requirements;
d) access controls;
e) identity controls;
f) logging and audit trails;
g) retention and deletion requirements;
h) legal hold requirements;
i) privileged-material protections;
j) protected knowledge restrictions;
k) public authority confidentiality requirements;
l) export-control and controlled-technology restrictions;
m) accessibility requirements;
n) business continuity requirements; and
o) approved budget and procurement controls.
No operational tool, workflow platform, AI assistant, repository, dashboard, meeting platform, document store, communication channel, file-sharing tool, project management system, or uncontrolled side channel shall be used as a substitute for official records, official approvals, controlled repositories, secure access rules, legal hold, privilege protection, data / AI / cyber controls, public-safe review, or Board authority.
150.7 Records Operations Support. The Chief Operating Officer may support records operations where delegated and in coordination with the Secretary, Chief Legal, Compliance, and Risk Officer, Chief Data, AI, and Cyber Officer, Treasurer or Chief Financial Officer, and other responsible officers. Records operations support shall ensure that operational records are created, classified, routed, stored, retained, sealed, deleted, archived, and disposed of in accordance with applicable law, the Articles or Certificate, this Bylaw, Board-approved policies, retention schedules, access classes, publication classes, legal holds, and repository discipline.
Records operations support may include:
a) intake record creation;
b) case ID coordination;
c) register routing;
d) repository deposit support;
e) metadata completeness checks;
f) access class tagging;
g) publication class tagging;
h) retention class tagging;
i) version tracking;
j) supersession tracking;
k) correction routing;
l) archive routing;
m) secure disposal routing;
n) legal hold coordination; and
o) records-quality reports.
Records operations support shall preserve validity-by-record. A missing, incomplete, misclassified, unapproved, inaccessible, unofficial, corrupted, unversioned, unretained, or improperly altered record may not be cured by memory, reputation, title, seniority, technical centrality, repeated practice, sponsor expectation, provider expectation, public authority attendance, or informal operational consensus. Where record defects arise, the Chief Operating Officer shall support correction, ratification where lawful, reclassification, restriction, replacement, supersession, withdrawal, archive, or escalation.
150.8 Business Continuity and Operational Resilience Support. The Chief Operating Officer may support business continuity and operational resilience where delegated. Business continuity and operational resilience support shall seek to preserve minimum lawful governance operations, essential records, communication channels, access controls, incident routing, payroll or payment continuity, critical vendor coordination, public-safe notice capability, legal and compliance escalation, data / AI / cyber continuity, public authority interface continuity, safeguards continuity, repository continuity, controlled-room continuity, and Board and officer continuity during disruption.
Business continuity and operational resilience support may include:
a) continuity planning;
b) critical function identification;
c) dependency mapping;
d) backup and recovery coordination;
e) recovery time objective and recovery point objective support where adopted;
f) emergency contact lists;
g) alternate communication channels;
h) successor administrator planning;
i) key-person dependency reduction;
j) vendor continuity review;
k) facilities continuity;
l) remote-work continuity;
m) repository and register continuity;
n) incident tabletop coordination;
o) continuity pack maintenance;
p) post-disruption review; and
q) continuity records.
Business continuity shall not authorize prohibited functions. No disruption, emergency, outage, cyber incident, public authority request, sponsor request, provider request, publication deadline, grant deadline, event deadline, or operational crisis shall permit the Corporation to issue public warnings, command emergency response, approve procurement, approve financing, certify compliance, recognize standing, select providers for public authorities, waive safeguards, waive data / AI / cyber controls, or bypass Board reserved matters except to the limited extent expressly permitted by lawful emergency authority and subject to ratification, sunset, and correction.
150.9 Delegation Matrix Implementation Support. The Chief Operating Officer may support implementation of the delegation matrix where delegated. Delegation matrix implementation support shall include operationalizing recorded delegations, authority thresholds, signature rules, spending limits, contracting limits, publication limits, data access limits, AI-use limits, cybersecurity limits, public authority interface limits, finance-boundary limits, certification-boundary limits, procurement-neutrality limits, research and evidence limits, technical asset limits, repository limits, controlled-room limits, emergency limits, and escalation pathways.
Delegation matrix implementation support may include:
a) maintaining workflow alignment with delegations;
b) routing approvals to authorized persons;
c) preventing approval by unauthorized persons;
d) flagging threshold exceedances;
e) maintaining approval logs;
f) supporting authority matrix updates where approved;
g) coordinating training on authority limits;
h) identifying gaps between practice and delegation;
i) reporting unauthorized acts or attempted acts;
j) supporting access restrictions tied to delegation;
k) supporting revocation or suspension implementation; and
l) maintaining delegation implementation records.
The delegation matrix is not self-executing without records. No person shall obtain authority merely because a workflow tool permits a button to be pressed, a system role exists, an approval field is open, a person is senior, a person has access, a person authored a document, a person controls a repository, a person leads a program, or a person is operationally necessary. Where workflow configuration conflicts with the delegation matrix, the delegation matrix and higher-order governing instruments shall control.
150.10 Internal Process Discipline. The Chief Operating Officer may support internal process discipline where delegated. Internal process discipline shall ensure that recurring activities are performed through approved, documented, reviewable, and correctionable workflows rather than informal custom, undocumented discretion, side channels, uncontrolled spreadsheets, inconsistent state-by-state practices, sponsor-specific exceptions, provider-specific exceptions, public authority-specific shortcuts, or undocumented emergency practices.
Internal process discipline may apply to:
a) intake;
b) triage;
c) approval routing;
d) contracting;
e) procurement administration;
f) support acceptance;
g) participant onboarding;
h) controlled-room admission;
i) repository access;
j) data access;
k) AI-use authorization;
l) publication review;
m) public authority reference review;
n) technical release;
o) incident escalation;
p) correction, withdrawal, takedown, and archive;
q) offboarding; and
r) closeout.
Internal process discipline shall be designed to make the lawful path easier than the unlawful path. Where a workflow creates friction, the remedy shall be lawful improvement, not bypass. Where an approved process is outdated, incomplete, unsafe, or inconsistent with law, this Bylaw, Board-approved policies, data / AI / cyber controls, safeguards, or Nexus role separation, the process shall be corrected through the competent record rather than ignored.
150.11 Procurement and Contracting Process Support. The Chief Operating Officer may support procurement and contracting processes where delegated and within the authority matrix. Procurement and contracting process support shall include administrative coordination of need identification, scope development, vendor intake, contractor intake, comparative review where required, conflict review, budget confirmation, legal review routing, data / AI / cyber review routing, sanctions and export-control routing, insurance and indemnity review routing, signature routing, contract repository deposit, renewal tracking, performance tracking, closeout, and records.
Procurement and contracting process support may address:
a) purchase requests;
b) scope statements;
c) statements of work;
d) service agreements;
e) software subscriptions;
f) cloud and compute arrangements;
g) data-processing agreements;
h) confidentiality agreements;
i) contributor and contractor agreements;
j) facilities and event agreements;
k) equipment and tool purchases;
l) professional service engagements;
m) research collaboration agreements;
n) public authority interface agreements;
o) sponsor, donor, funder, host, and provider interface agreements; and
p) amendments, renewals, terminations, and closeout.
Procurement and contracting process support shall not be confused with public procurement authority. The Corporation may procure goods and services for its own lawful nonprofit operations, but it shall not procure on behalf of public authorities, select vendors for public authorities, create procurement preference, create provider preference, certify vendors, recognize vendors, approve finance-readiness, or use procurement processes to channel improper private benefit, sponsor control, provider control, public authority confusion, or enterprise-stack execution.
150.12 Operational Risk Escalation. The Chief Operating Officer shall support operational risk escalation where delegated. Operational risk escalation shall be triggered where an operational matter presents or may present material risk to legal compliance, corporate status, tax status, nonprofit character, public-benefit purpose, mission lock, non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, privacy, research integrity, evidence integrity, methods integrity, public-safe publication, safeguards, protected knowledge, civil rights, accessibility, competition, sanctions, export-control, controlled technology, business continuity, records integrity, or Nexus role separation.
Operational risk escalation may include:
a) immediate identification of the operational issue;
b) temporary hold, routing stop, access restriction, publication freeze, implementation freeze, vendor hold, contractor hold, room hold, repository hold, or release hold where authorized or urgently necessary pending review;
c) notice to the responsible officer;
d) notice to the Chief Legal, Compliance, and Risk Officer where legal or compliance risk exists;
e) notice to the Chief Data, AI, and Cyber Officer where data, AI, cyber, privacy, compute, model, or repository risk exists;
f) notice to the Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer where safeguards, civil-rights, accessibility, protected knowledge, or public-safe mapping risk exists;
g) notice to the Secretary where records or authority defects exist;
h) notice to the Treasurer or Chief Financial Officer where financial, payment, restricted fund, or private benefit risk exists;
i) notice to the President, Executive Director or Chief Executive Officer, Chair, committee, or Board where material;
j) preservation of relevant records;
k) corrective action tracking; and
l) closeout and archive.
No operational issue shall be suppressed because it is inconvenient, embarrassing, sponsor-sensitive, provider-sensitive, public authority-sensitive, grant-sensitive, publication-sensitive, or deadline-sensitive. Operational risk escalation is a duty of protection, not a discretionary courtesy.
150.13 No Operational Convenience Override of Bylaw, Policy, Records, Data / AI / Cyber, Public Authority, Finance, Safeguards, or Non-Execution Controls. No operational convenience, speed, administrative burden, staffing shortage, event deadline, grant deadline, publication deadline, public authority request, sponsor request, provider request, donor request, funder request, host request, media interest, technical urgency, system limitation, workflow design, software configuration, repository permission, dashboard schedule, controlled-room pressure, meeting pressure, budget pressure, or perceived institutional need shall override applicable law, the Articles or Certificate, this Bylaw, Board reserved matters, Board-approved policies, recorded delegations, authority matrix limits, records requirements, data / AI / cyber controls, privacy controls, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, competition controls, sanctions controls, export-control controls, controlled-technology controls, research integrity controls, safeguards, protected knowledge restrictions, public-safe publication requirements, validity-by-record, or correctionability.
The Corporation shall apply the following operational convenience rules:
a) where speed conflicts with authority, authority controls;
b) where workflow conflicts with records, records controls;
c) where access conflicts with data classification, data classification controls;
d) where publication conflicts with public-safe review, public-safe review controls;
e) where public authority interest conflicts with public authority boundary discipline, the boundary controls;
f) where sponsor or provider convenience conflicts with non-control, non-control controls;
g) where technical capability conflicts with safeguards, safeguards control;
h) where dashboard completeness conflicts with protected knowledge, protected knowledge controls;
i) where funding convenience conflicts with tax, nonprofit, private benefit, or anti-capture review, review controls;
j) where operational momentum conflicts with legal ambiguity, escalation controls;
k) where informal practice conflicts with this Bylaw, this Bylaw controls; and
l) where uncertainty exists, the more restrictive lawful posture shall apply pending review.
Any operational act taken in violation of this Section shall be subject to hold, restriction, correction, ratification where lawful, withdrawal, takedown, contract remedy, access revocation, disciplinary action, public or controlled clarification, or referral to the appropriate officer, committee, counsel, Board, public authority, funder, or law enforcement body where required or appropriate.
150.14 Chief Operating Officer Records. The Corporation shall maintain Chief Operating Officer Records sufficient to demonstrate the Chief Operating Officer’s appointment, term, eligibility, authority, delegations, operations management, program operations support, people operations support, vendor and contractor operations support, facilities administration, tool administration, system administration, administrative controls, records operations support, business continuity support, operational resilience support, delegation matrix implementation support, internal process discipline, procurement process support, contracting process support, operational risk escalation, operational convenience boundary controls, conflicts, recusals, restrictions, succession, and closeout.
Chief Operating Officer Records shall include, as applicable:
a) appointment or election record;
b) term and renewal record;
c) eligibility, consent, fit-and-proper, integrity, conflict, independence, sanctions, export-control, controlled-technology, public authority boundary, finance-boundary, certification-boundary, procurement-neutrality, recognition-boundary, provider-neutrality, sponsor non-control, data / AI / cyber, privacy, research integrity, evidence integrity, methods integrity, safeguards, civil-rights, accessibility, Tribal and Indigenous protocol, protected knowledge, competition, professional-boundary, and public-safe publication screening records;
d) duty acknowledgment and certification of understanding;
e) role description;
f) reporting line;
g) authority matrix entry;
h) separate delegations;
i) operational plans, calendars, dashboards, workplans, task logs, milestone records, action trackers, and closeout records;
j) program operations records, program launch records, participant onboarding routing records, controlled-room support records, public authority learning support records, technical activity support records, publication routing records, Nexus interface support records, GRF-facing input routing records, and GRA-facing technical input routing records;
k) people operations records, onboarding records, training coordination records, access request records, confidentiality acknowledgment records, conflict routing records, offboarding records, access revocation records, and return, deletion, sealing, or transfer records;
l) vendor and contractor records, intake records, scope records, procurement routing records, conflict review records, sanctions and export-control routing records, data / AI / cyber review routing records, contract routing records, deliverable records, invoice routing records, renewal records, termination records, and closeout records;
m) facilities, tools, systems, workflow, communication, meeting, repository-support, controlled-room platform, document-management, project-management, identity, access, logging, retention, legal hold, and administrative-control records;
n) records operations records, case ID records, metadata completeness records, access class records, publication class records, retention class records, version records, supersession records, correction routing records, archive routing records, and secure disposal records;
o) business continuity, operational resilience, dependency mapping, backup coordination, recovery objective, emergency contact, successor administrator, continuity pack, incident tabletop, disruption response, post-disruption review, and continuity records;
p) delegation matrix implementation records, authority routing records, approval logs, threshold-exceedance records, unauthorized-act reports, workflow configuration records, access restriction records, and delegation suspension or revocation implementation records;
q) internal process discipline records, workflow records, intake records, triage records, routing records, approval records, contracting records, support acceptance records, participant onboarding records, publication review records, public authority reference review routing records, repository access routing records, data access routing records, AI-use routing records, incident escalation records, correction records, withdrawal records, takedown records, archive records, and closeout records;
r) procurement and contracting process records, purchase request records, statement-of-work records, comparative review records where applicable, budget confirmation records, legal review routing records, insurance and indemnity routing records, signature routing records, repository deposit records, amendment records, renewal records, termination records, and closeout records;
s) operational risk escalation records, holds, stops, access restrictions, publication freezes, implementation freezes, vendor holds, contractor holds, room holds, repository holds, release holds, notices to officers or Board, corrective action records, closeout records, and archive records;
t) operational convenience override concerns, refused shortcuts, corrected workflows, public authority pressure records, sponsor pressure records, provider pressure records, grant deadline escalation records, event deadline escalation records, publication deadline escalation records, and legal ambiguity escalation records;
u) public-safe notice, limitation language, controlled vocabulary, non-reliance, correction, supersession, withdrawal, takedown, public clarification, and archive records associated with operations;
v) escalations involving public authority boundary, finance boundary, certification boundary, procurement neutrality, recognition boundary, provider neutrality, sponsor non-control, data / AI / cyber, privacy, safeguards, protected knowledge, civil rights, accessibility, research integrity, public-safe publication, competition, sanctions, export-control, controlled technology, professional boundary, tax, nonprofit, corporate, or operational risk;
w) conflicts, recusals, access restrictions, delegation restrictions, resignation, removal, handover, access revocation, and closeout records; and
x) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that the Chief Operating Officer makes the Corporation operationally reliable, not operationally unbounded. Operational management, program support, people operations, vendor administration, facilities, tools, systems, process discipline, continuity, procurement support, contracting support, and workflow implementation are lawful support functions subordinate to the Board, the Bylaw, recorded delegations, public-benefit purpose, non-execution, role separation, data / AI / cyber controls, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, safeguards, validity-by-record, and correctionability. Operations shall be disciplined, documented, reviewable, non-executing, public-safe, and correctionable; operational convenience shall never be a source of authority.
Section 151. Chief Development, Grants, and Public-Good Support Officer
151.1 Chief Development, Grants, and Public-Good Support Officer Role Where Approved. The Chief Development, Grants, and Public-Good Support Officer, where such office is approved by the Board, shall serve as the principal fundraising-strategy, grant-development, donation-development, sponsorship-development, public-good-support, in-kind-contribution, restricted-fund intake, unrestricted-support intake, subscription-support, fee-program coordination, supporter-stewardship, donor-records, funder-records, sponsor-records, public-acknowledgment, benefit-schedule, anti-capture, support-acceptance intake, support-refusal, support-return, support-restriction, support-termination, and support-closeout officer of the Corporation, subject at all times to applicable law, the Articles or Certificate, this Bylaw, Board resolutions, Board-approved policies, the delegation matrix, the authority matrix, approved budget, fiduciary oversight, public-benefit purpose, nonprofit and non-distribution character, tax-exempt or tax-exempt-compatible restrictions, charitable-solicitation requirements where applicable, grant conditions, restricted-fund rules, private-benefit controls, non-execution, GCRI / GRF / GRA role separation, public-good stack and enterprise stack separation, public authority boundary controls, finance-boundary controls, certification-boundary controls, procurement-neutrality controls, provider-neutrality controls, sponsor non-control controls, data / AI / cyber controls, privacy controls, research integrity controls, safeguards, protected knowledge restrictions, controlled vocabulary, validity-by-record, and correctionability.
The Chief Development, Grants, and Public-Good Support Officer’s office exists to help the Corporation lawfully obtain, steward, acknowledge, and report public-good support without selling authority, outcomes, access, influence, recognition, finance-readiness, certification, procurement advantage, provider status, public authority proximity, research conclusions, public-safe publication results, technical baselines, Docket support, Grid support, Nexus-compatible claims, or GCRI / GRF / GRA / Nexus meaning. Development is a support function; it is not a control function.
The Chief Development, Grants, and Public-Good Support Officer shall not, by title, fundraising role, donor relationship, sponsor relationship, funder relationship, grant responsibility, public-good support responsibility, event role, public-facing role, relationship ownership, or proximity to major support alone, be treated as:
a) a substitute Board;
b) a person authorized to approve Board reserved matters;
c) a person authorized to bind the Corporation outside recorded delegation;
d) a broker, dealer, finder, investment adviser, capital raiser for securities, lender, insurer, underwriter, rating agency, public finance arranger, placement agent, financial intermediary, public finance approver, procurement authority, certification authority, recognition authority, public authority, emergency command authority, public warning authority, provider selector, or enterprise execution actor;
e) a person authorized to promise public authority access, public authority action, public finance approval, public procurement advantage, certification, recognition, finance-readiness, insurance-readiness, Docket standing, Grid standing, maturity status, Nexus-compatible status, provider preference, sponsor influence, research outcome, publication outcome, public-safe report treatment, dashboard treatment, technical baseline inclusion, software feature inclusion, repository access, controlled-room access, or GRF / GRA / Nexus action; or
f) a person authorized to waive legal review, tax review, nonprofit review, charitable-solicitation review, restricted-fund review, conflict review, sanctions review, export-control review, controlled-technology review, competition review, data / AI / cyber review, privacy review, public authority boundary review, finance-boundary review, certification-boundary review, procurement-neutrality review, provider-neutrality review, sponsor non-control review, safeguards review, protected knowledge review, Board approval, or counsel review where required.
151.2 Fundraising Strategy Support. The Chief Development, Grants, and Public-Good Support Officer may support fundraising strategy where delegated. Fundraising strategy shall be designed to sustain the Corporation’s lawful nonprofit, public-benefit, evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, public authority learning, safeguards, and Nexus-compatible public-good purposes without creating private capture, donor capture, sponsor capture, funder capture, provider capture, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, or mission drift.
Fundraising strategy support may include:
a) identification of lawful support categories;
b) preparation of annual or multi-year support plans;
c) alignment of support opportunities with Board-approved strategy and budget;
d) coordination of unrestricted support, restricted support, grants, donations, sponsorships, subscriptions, fees, in-kind support, public-good infrastructure support, challenge support, fellowship support, Academy support, and program support;
e) review of donor, funder, sponsor, and supporter concentration risk;
f) development of public-safe support language;
g) review of benefits and acknowledgments;
h) coordination with finance, legal, compliance, tax, operations, safeguards, data / AI / cyber, research, publication, and program functions;
i) identification of support relationships requiring Board approval;
j) refusal, restriction, return, termination, or re-scoping recommendations where support would impair mission lock or independence; and
k) support strategy records.
Fundraising strategy shall not be based on selling proximity to public authorities, capital readers, sponsors, providers, national companies, Project SPVs, GRF recognition pathways, GRA finance-readiness pathways, Nexus Docket pathways, Nexus Grid pathways, Nexus-compatible claims, public-safe reporting, public authority learning rooms, controlled rooms, data rooms, public-good software, technical baselines, or observability outputs. Public-good support shall support the mission; it shall not purchase the mission.
151.3 Grant Development Support. The Chief Development, Grants, and Public-Good Support Officer may support grant development where delegated. Grant development support may include identifying grant opportunities, coordinating grant calendars, preparing nonbinding concept notes, supporting proposal drafting, coordinating budgets with the Treasurer or Chief Financial Officer, coordinating compliance review, obtaining program input, gathering supporting materials, preparing public-safe institutional descriptions, routing applications for approval, tracking submission deadlines, supporting award negotiation, and coordinating grant records.
Grant development support shall include review, where applicable, of:
a) eligibility;
b) charitable or nonprofit status representations;
c) public-benefit alignment;
d) restricted-fund implications;
e) cost-share or matching obligations;
f) reporting obligations;
g) audit rights;
h) public authority conditions;
i) lobbying, political activity, government ethics, gifts, procurement, public records, open meetings, or public-sector constraints;
j) data, AI, cyber, privacy, research ethics, publication, IP, and protected knowledge conditions;
k) sanctions, export-control, controlled-technology, and cross-border restrictions;
l) conflict, related-party, sponsor-control, provider-control, or private-benefit risks;
m) public authority boundary, finance-boundary, certification-boundary, procurement-neutrality, recognition-boundary, and provider-neutrality implications; and
n) Board, officer, counsel, tax, or compliance approval requirements.
No grant proposal, concept note, budget narrative, workplan, logic model, impact statement, public authority letter, support letter, sponsor letter, partner letter, or technical annex shall promise prohibited functions or imply that the Corporation will serve as a regulator, public authority, public warning body, emergency command body, procurement authority, certification body, recognition body, finance-readiness body, fund, broker, dealer, investment adviser, lender, insurer, rating agency, provider, operator, national company, Project SPV, or enterprise execution vehicle.
151.4 Donation Development Support. The Chief Development, Grants, and Public-Good Support Officer may support donation development where delegated. Donation development support may include donor identification, donor education, donor stewardship, preparation of donation materials, preparation of public-safe mission summaries, routing of donation acceptance review, coordination of donation agreements where required, coordination of receipting review where applicable, tracking of restrictions, and maintenance of donor records.
Donation development support shall preserve the distinction between gift, grant, sponsorship, fee, subscription, restricted fund, in-kind contribution, reimbursement, contract payment, and purchase of services. A payment shall not be called a donation merely because the donor prefers charitable language, public recognition, tax treatment, reputational benefit, or simplified paperwork.
Donation development support shall not promise or imply:
a) governance control;
b) Board seat or officer appointment;
c) committee, council, working group, or panel control;
d) research finding or publication outcome;
e) public authority access;
f) public authority adoption;
g) certification, recognition, maturity standing, Docket standing, Grid standing, or Nexus-compatible status;
h) finance-readiness, insurance-readiness, bankability, capital-readability, rating, investment suitability, or public finance approval;
i) provider preference, procurement advantage, vendor selection, or market preference;
j) privileged data access, protected knowledge access, controlled-room access, public authority room access, or repository access beyond approved access class; or
k) sponsor-equivalent benefits unless the support is treated and approved as sponsorship or another appropriate support class.
151.5 Sponsorship Development Support. The Chief Development, Grants, and Public-Good Support Officer may support sponsorship development where delegated. Sponsorship development support shall include identifying lawful sponsorship opportunities, preparing benefit schedules, coordinating sponsor intake, routing sponsor acceptance review, preparing sponsorship agreements, coordinating public acknowledgment language, monitoring sponsor benefits, preventing sponsor control, and supporting sponsor closeout.
Sponsorship benefits may include only lawful and approved benefits consistent with nonprofit character, tax-exempt or tax-exempt-compatible status, public-benefit purpose, anti-capture controls, provider neutrality, public authority boundary discipline, finance-boundary discipline, certification-boundary discipline, procurement-neutrality discipline, safeguards, public-safe publication, and controlled vocabulary. Benefits may include public acknowledgment, event recognition, limited logo placement, participation opportunities, educational access, controlled-room access where independently approved, sponsor briefings within approved limits, and public-good support recognition where lawful and recorded.
Sponsorship shall not include:
a) control over governance, strategy, research agenda, evidence conclusions, method conclusions, technical truth outputs, publication decisions, public-safe reports, dashboards, maps, software releases, technical baselines, controlled vocabulary, GRF-facing inputs, GRA-facing inputs, Docket support, Grid support, or Nexus-compatible claims;
b) approval, veto, suppression, delay, or modification rights over independent research, evidence, methods, publications, correction, withdrawal, takedown, or archive decisions;
c) guaranteed access to public authorities, regulators, public finance readers, emergency-management participants, capital readers, communities, Indigenous knowledge holders, protected knowledge, controlled rooms, no-download rooms, repositories, data rooms, or evidence rooms beyond approved access class;
d) preferred provider status, procurement advantage, certification advantage, recognition advantage, finance-readiness advantage, or market advantage;
e) rights to imply endorsement, public authority adoption, GRF recognition, GRA finance-readiness, Nexus Standards conformance, Nexus-compatible status, or public-good legitimacy; or
f) benefits that create private inurement, impermissible private benefit, unrelated business risk, charitable-solicitation noncompliance, advertising risk where not intended, competition risk, sanctions risk, export-control risk, or reputational capture.
151.6 Public-Good Support Development. The Chief Development, Grants, and Public-Good Support Officer may develop public-good support relationships where delegated. Public-good support may include unrestricted support, mission-restricted support, program support, research support, Academy support, fellowship support, technical baseline support, open-source support, repository support, controlled-room support, public authority learning support, safeguards support, accessibility support, community participation support, public-safe publication support, observability methods support, and Nexus-compatible public-good stack support.
Public-good support development shall be governed by the following principles:
a) support shall be mission-aligned;
b) support shall be lawful;
c) support shall not create control;
d) support shall not buy outcomes;
e) support shall not buy public authority proximity;
f) support shall not buy recognition, certification, procurement advantage, finance-readiness, or provider preference;
g) support shall not weaken evidence integrity, research integrity, methods integrity, safeguards, data / AI / cyber controls, or correctionability;
h) support shall be recorded, classified, and reviewed;
i) restricted support shall be tracked and used only for approved purposes; and
j) support that cannot satisfy the acceptance test shall be refused, returned, restricted, re-scoped, or terminated.
Public-good support language shall be disciplined. The Corporation may state that support enables lawful public-benefit work, but shall not state or imply that support validates a sponsor, certifies a provider, recognizes a project, makes a deployment finance-ready, approves procurement, creates public authority endorsement, or confers public-good legitimacy beyond the approved acknowledgment.
151.7 In-Kind Contribution Coordination. The Chief Development, Grants, and Public-Good Support Officer may coordinate in-kind contributions where delegated. In-kind contributions may include equipment, software licenses, cloud credits, compute credits, AI tools, cybersecurity tools, datasets, technical services, professional services, meeting space, event space, staff time, lab space, research support, translation support, accessibility support, communications support, travel support, or other non-cash support that advances the Corporation’s lawful purposes.
In-kind contribution coordination shall include review of:
a) valuation where required;
b) ownership and title;
c) license terms;
d) restrictions;
e) data rights;
f) IP rights;
g) cybersecurity risk;
h) AI-use risk;
i) privacy risk;
j) export-control, sanctions, controlled-technology, and national-security sensitivity;
k) conflicts and related-party risk;
l) sponsor or provider capture risk;
m) public authority boundary risk;
n) private-benefit or inurement risk;
o) tax and receipting implications;
p) operational dependency risk; and
q) return, deletion, discontinuation, or closeout requirements.
No in-kind contribution shall be accepted merely because it is valuable, scarce, technically advanced, or offered by a prominent sponsor, provider, cloud provider, AI provider, public authority, university, laboratory, funder, host, or enterprise actor. In-kind support shall not be used to create dependence that compromises neutrality, research independence, software independence, data governance, public authority boundary discipline, provider neutrality, sponsor non-control, or correctionability.
151.8 Subscription and Fee Program Coordination Where Delegated. The Chief Development, Grants, and Public-Good Support Officer may coordinate subscription and fee programs where delegated and in coordination with the Treasurer or Chief Financial Officer, Chief Legal, Compliance, and Risk Officer, relevant program officers, and the Board where required. Subscription and fee programs may include lawful supporter subscriptions, publication subscriptions, Academy fees, training fees, program fees, controlled-room fees, cost-recovery fees, fellowship-related fees, lab fees, challenge fees, technical access fees, repository support fees, or other fees approved in accordance with this Bylaw.
Subscription and fee program coordination shall ensure that each fee is classified, approved, recorded, and represented correctly. A fee shall not be mischaracterized as a donation where it is consideration for goods, services, access, training, publication, room participation, technical access, or other benefits. A subscription or fee shall not create governance rights, voting rights, fiduciary status, public authority access, public authority endorsement, certification, recognition, finance-readiness, procurement advantage, provider preference, Nexus-compatible status, or regulated credential unless separately and lawfully authorized by competent authority and record.
Subscription and fee program coordination may include:
a) fee schedule routing;
b) waiver and scholarship routing;
c) public-interest access routing;
d) refund and cancellation administration;
e) tax classification routing;
f) sales tax, unrelated business income, and state tax review where applicable;
g) access benefit classification;
h) public-safe claim review;
i) donor, sponsor, and fee-payer distinction review; and
j) subscription and fee records.
151.9 Support Acceptance Intake. The Chief Development, Grants, and Public-Good Support Officer may support acceptance intake for grants, donations, sponsorships, in-kind contributions, restricted funds, unrestricted support, subscriptions, fees, public-good infrastructure support, challenge support, fellowship support, and other support relationships where delegated. Support acceptance intake shall be a structured review process and shall not be treated as final approval unless the officer has express authority for the relevant support class and all required reviews are complete.
Support acceptance intake shall collect, as applicable:
a) identity of donor, funder, sponsor, supporter, provider, host, contributor, or other support source;
b) legal name and beneficial ownership or control information where applicable;
c) amount, form, timing, and restrictions;
d) proposed use;
e) proposed acknowledgment or benefits;
f) tax and receipting implications;
g) charitable-solicitation implications;
h) grant or contract conditions;
i) public authority involvement;
j) conflicts and related-party issues;
k) sanctions, export-control, controlled-technology, and national-security sensitivity;
l) data, AI, cyber, privacy, and repository implications;
m) research integrity, evidence integrity, methods integrity, and publication implications;
n) safeguards, protected knowledge, civil-rights, accessibility, and public-safe mapping implications;
o) public authority boundary, finance boundary, certification boundary, procurement-neutrality, recognition-boundary, provider-neutrality, and sponsor non-control implications; and
p) required approvals, restrictions, refusal, return, termination, or closeout steps.
Support acceptance intake shall be conservative where ambiguity exists. Support shall be held pending review where the source, purpose, restrictions, benefits, public description, legal classification, tax treatment, public authority implications, data implications, AI implications, cyber implications, safeguards implications, or boundary implications are uncertain.
151.10 Donor, Funder, Sponsor, and Supporter Records Support. The Chief Development, Grants, and Public-Good Support Officer may support donor, funder, sponsor, and supporter records where delegated. Such records shall be sufficient to demonstrate who provided support, what was provided, when it was provided, for what purpose it was accepted, what restrictions apply, what acknowledgments or benefits were approved, what reviews were performed, what conditions apply, how the support was used or restricted, and how the support was closed out.
Donor, funder, sponsor, and supporter records may include:
a) intake records;
b) screening records;
c) acceptance records;
d) refusal, restriction, return, or termination records;
e) donation agreements;
f) grant agreements;
g) sponsorship agreements;
h) in-kind contribution agreements;
i) restricted fund records;
j) public acknowledgment records;
k) benefit schedule records;
l) tax and receipting records;
m) charitable-solicitation records;
n) conflict and related-party records;
o) sanctions and export-control records;
p) data / AI / cyber review records;
q) public authority boundary records;
r) finance, certification, procurement, recognition, and provider-neutrality boundary records;
s) safeguards and protected knowledge review records;
t) reporting records;
u) closeout records; and
v) correction, supersession, withdrawal, public clarification, and archive records.
Records shall distinguish between support source, program participant, provider, vendor, contractor, public authority participant, capital reader, university, laboratory, host, and community participant. A person or entity may occupy more than one role only where each role is separately classified, reviewed, recorded, and bounded.
151.11 Public Acknowledgment Controls Support. The Chief Development, Grants, and Public-Good Support Officer may support public acknowledgment controls where delegated. Public acknowledgments may recognize lawful support, but shall not create endorsement, certification, recognition, finance-readiness, public authority approval, procurement advantage, provider preference, sponsor control, donor control, funder control, host control, commercial recommendation, technical approval, or public-good legitimacy beyond the fact of support.
Public acknowledgment controls shall apply to:
a) websites;
b) reports;
c) public-safe publications;
d) event materials;
e) Academy materials;
f) program materials;
g) repository notices;
h) software documentation;
i) technical baselines;
j) dashboards and maps;
k) controlled-room materials;
l) public authority learning materials;
m) grant reports;
n) sponsor pages;
o) press materials;
p) social media;
q) donor walls;
r) logos, marks, seals, and badges; and
s) public statements.
Acknowledgment language shall be approved, versioned, and limited. Sponsor, donor, funder, provider, host, or supporter logos shall be used only where authorized and shall be accompanied by limitation language where needed. No acknowledgment shall be placed in a manner that implies that the sponsor or supporter controls research, approves methods, endorses outputs, receives preferred treatment, receives public authority access, receives finance-readiness benefits, receives recognition benefits, receives procurement benefits, or receives certification benefits.
151.12 Anti-Capture Controls Support. The Chief Development, Grants, and Public-Good Support Officer shall support anti-capture controls where delegated. Anti-capture controls shall prevent any donor, funder, sponsor, provider, host, investor, insurer, lender, underwriter, bank, public finance actor, capital reader, public authority, national company, Project SPV, vendor, contractor, platform operator, cloud provider, AI provider, data provider, or enterprise actor from obtaining governance control, operational control, research control, evidence control, methods control, publication control, public authority access control, technical asset control, repository control, controlled-room control, data-room control, public-good software control, or Nexus-interface control through support.
Anti-capture controls may include:
a) concentration review;
b) source review;
c) beneficial ownership or control review where applicable;
d) conflict and related-party review;
e) influence cap review;
f) sponsor benefit limitation;
g) donor restriction review;
h) restricted fund limitation;
i) independent review of major support;
j) Board approval for material support;
k) separation of development staff from research conclusions and evidence determinations where required;
l) firewall between sponsor relationships and publication decisions;
m) firewall between provider support and provider-neutral processes;
n) firewall between capital actors and GRA-adjacent finance-readiness inputs;
o) firewall between public authorities and public authority boundary controls;
p) refusal, return, termination, or diversification of support where needed; and
q) anti-capture records.
A support relationship shall be presumptively unacceptable where it requires or materially pressures the Corporation to alter evidence, suppress adverse findings, delay correction, soften public-safe notices, privilege a sponsor or provider, steer public authorities, create procurement advantage, create finance-readiness signals, create recognition signals, provide protected knowledge access, weaken data / AI / cyber controls, weaken safeguards, or misrepresent the Corporation’s role.
151.13 No Securities Solicitation. The Chief Development, Grants, and Public-Good Support Officer shall not conduct, authorize, facilitate, coordinate, imply, or support any securities offering, securities sale, securities distribution, investment solicitation, capital placement, underwriting, brokerage, dealer activity, finder activity, investment adviser activity, investment recommendation, investor matching, investor introduction for compensation, suitability determination, transaction recommendation, portfolio recommendation, asset management service, public finance solicitation, fund formation, Project SPV financing solicitation, national company financing solicitation, token sale, digital asset offering, revenue participation sale, debt placement, equity placement, guarantee sale, or other regulated capital execution activity on behalf of the Corporation or any other person.
The following shall not be treated as permissible merely because they occur in a development context:
a) introducing investors to Project SPVs or national companies as a fundraising benefit;
b) describing a project as investable, bankable, finance-ready, insurance-ready, underwritable, rated, de-risked, or capital-ready without competent authority and approved limitation language;
c) packaging donor or sponsor materials as investment materials;
d) presenting public-good support opportunities as financial opportunities;
e) accepting compensation tied to investment, capital placement, financing, lending, underwriting, insurance, or public finance outcomes;
f) allowing sponsors, funders, or capital actors to use GCRI US materials as securities marketing materials;
g) implying that GCRI US evidence, technical baselines, proof receipts, Docket support, Grid support, GRF-facing inputs, or GRA-facing technical inputs constitute investment diligence or capital approval; or
h) using controlled rooms, public authority learning rooms, data rooms, public-safe reports, dashboards, maps, or technical baselines as transaction execution channels.
Where a support discussion appears to cross into regulated finance activity, the Chief Development, Grants, and Public-Good Support Officer shall stop, hold, re-scope, restrict, route to the Chief Legal, Compliance, and Risk Officer, and preserve records.
151.14 No Investment Advice. The Chief Development, Grants, and Public-Good Support Officer shall not provide investment advice, investment recommendations, securities analysis, suitability analysis, portfolio recommendations, transaction recommendations, asset allocation advice, risk-return recommendations, capital structure advice for investors, underwriting advice, lending advice, insurance placement advice, rating opinions, bankability determinations, investability determinations, financeability determinations, public finance opinions, tax-credit monetization advice, guarantee advice, or capital-reader determinations.
The officer may describe the Corporation’s lawful public-benefit work, approved public-good programs, approved support needs, approved grant opportunities, approved sponsorship opportunities, approved donation opportunities, approved Academy or program support opportunities, and approved public-safe outputs, provided that all descriptions remain within controlled vocabulary, non-reliance language, public-safe claim rules, finance-boundary rules, and approved authority.
No development communication shall state or imply that:
a) supporting the Corporation is an investment;
b) support will produce financial return;
c) support creates project priority;
d) support creates Docket or Grid advantage;
e) support improves finance-readiness;
f) support improves recognition, maturity, standing, certification, procurement, provider selection, or public authority treatment;
g) support creates access to investment opportunities;
h) support creates access to capital readers or public finance actors; or
i) GCRI US materials may be relied upon for investment, lending, insurance, underwriting, rating, public finance, or procurement decisions.
151.15 No Finance-Readiness Sale. The Chief Development, Grants, and Public-Good Support Officer shall not sell, promise, imply, package, discount, accelerate, sponsor, trade, grant, or condition finance-readiness, capital-readability, proof-pack readiness, insurance-readiness, underwriting-readiness, bankability, investability, project readiness, Docket status, Grid status, maturity status, risk rating, resilience rating, public finance approval, investor access, lender access, insurer access, public finance reader access, or GRA-facing treatment as a benefit of grant, donation, sponsorship, subscription, fee, in-kind support, public-good support, event support, Academy support, challenge support, controlled-room participation, technical contribution, or program participation.
Finance-adjacent language shall be subject to strict controls. A support relationship may fund lawful evidence, methods, education, technical literacy, public-good software, public authority learning, safeguards, and public-safe publication, but it shall not purchase the conclusion that any project, company, technology, deployment, jurisdiction, provider, host, sponsor, funder, national company, Project SPV, public authority, dataset, model, technical asset, or infrastructure system is finance-ready, insurance-ready, bankable, investable, underwritable, rated, de-risked, or capital-readable.
Where finance-readiness or capital-readability is relevant to the broader Nexus architecture, the Chief Development, Grants, and Public-Good Support Officer shall preserve GRA role separation and shall not represent GCRI US as performing GRA functions. Any GRA-facing technical input shall be evidence-bounded, method-bounded, record-supported, non-executing, non-soliciting, and subject to approved interface controls.
151.16 No Recognition, Certification, Procurement Advantage, Public Authority Access, or Outcome Purchase. The Chief Development, Grants, and Public-Good Support Officer shall not sell, promise, imply, package, discount, accelerate, sponsor, trade, grant, or condition recognition, certification, accreditation, compliance approval, procurement advantage, provider preference, public authority access, public authority endorsement, public authority adoption, public authority participation, official status, public warning status, emergency-management status, maturity status, standing, Nexus-compatible status, Docket status, Grid status, technical conformance, research outcome, evidence outcome, methods outcome, publication outcome, dashboard treatment, map treatment, technical baseline inclusion, software feature inclusion, controlled vocabulary treatment, public-safe report treatment, correction treatment, takedown treatment, or GRF-facing treatment as a benefit of support.
The following shall be prohibited:
a) support-for-recognition;
b) support-for-certification;
c) support-for-procurement;
d) support-for-public-authority-access;
e) support-for-provider-preference;
f) support-for-finance-readiness;
g) support-for-GRF-standing;
h) support-for-GRA-treatment;
i) support-for-Nexus-compatible-status;
j) support-for-publication-outcome;
k) support-for-research-finding;
l) support-for-dashboard-placement;
m) support-for-technical-baseline-inclusion;
n) support-for-controlled-room-access beyond approved independent access class; and
o) support-for-suppression, delay, dilution, or avoidance of correction.
Where any donor, sponsor, funder, supporter, provider, host, public authority, capital actor, enterprise actor, or related party requests such benefit, the request shall be recorded, escalated, refused unless lawfully re-scoped, and, where necessary, the support shall be declined, returned, restricted, terminated, or publicly clarified.
151.17 Chief Development, Grants, and Public-Good Support Officer Records. The Corporation shall maintain Chief Development, Grants, and Public-Good Support Officer Records sufficient to demonstrate the Chief Development, Grants, and Public-Good Support Officer’s appointment, term, eligibility, authority, delegations, fundraising strategy support, grant development support, donation development support, sponsorship development support, public-good support development, in-kind contribution coordination, subscription and fee program coordination, support acceptance intake, donor records support, funder records support, sponsor records support, supporter records support, public acknowledgment controls support, anti-capture controls support, securities-solicitation boundary compliance, investment-advice boundary compliance, finance-readiness sale prohibition compliance, recognition / certification / procurement / public authority access / outcome purchase prohibition compliance, conflicts, recusals, restrictions, succession, and closeout.
Chief Development, Grants, and Public-Good Support Officer Records shall include, as applicable:
a) appointment or election record;
b) term and renewal record;
c) eligibility, consent, fit-and-proper, integrity, conflict, independence, sanctions, export-control, controlled-technology, public authority boundary, finance-boundary, certification-boundary, procurement-neutrality, recognition-boundary, provider-neutrality, sponsor non-control, charitable-solicitation, grant-compliance, tax, nonprofit, private-benefit, data / AI / cyber, privacy, research integrity, evidence integrity, methods integrity, safeguards, civil-rights, accessibility, Tribal and Indigenous protocol, protected knowledge, competition, professional-boundary, and public-safe publication screening records;
d) duty acknowledgment and certification of understanding;
e) role description;
f) reporting line;
g) authority matrix entry;
h) separate delegations;
i) fundraising strategy records, support plans, development calendars, pipeline records, concentration-risk records, support-category records, support restriction records, and Board approval routing records;
j) grant opportunity records, concept notes, proposal drafts, budget coordination records, compliance routing records, submission records, award records, grant agreements, grant-condition records, reporting records, audit-right records, closeout records, and grant correction records;
k) donation records, donor intake records, donation agreements, gift restriction records, donor communications, donor acknowledgment records, receipting review records, tax classification records, refusal records, return records, and closeout records;
l) sponsorship records, sponsor intake records, sponsorship agreements, benefit schedules, logo-use records, acknowledgment records, sponsor non-control records, sponsor benefit review records, sponsor restriction records, sponsor refusal or termination records, and sponsor closeout records;
m) public-good support records, unrestricted support records, restricted support records, program support records, technical baseline support records, public-good software support records, Academy support records, fellowship support records, challenge support records, safeguards support records, accessibility support records, community support records, public-safe publication support records, and Nexus-compatible support records;
n) in-kind contribution records, valuation records, ownership records, license records, IP records, data-rights records, cybersecurity review records, AI-use review records, privacy review records, export-control records, sanctions records, controlled-technology records, dependency-risk records, return records, deletion records, discontinuation records, and closeout records;
o) subscription and fee program records, fee schedule routing records, waiver records, scholarship records, reduced-fee records, public-interest seat records, refund records, cancellation records, sales tax review records, unrelated business income review records, state tax review records, and access-benefit classification records;
p) support acceptance intake records, source identity records, beneficial ownership or control records where applicable, restriction records, proposed use records, proposed benefit records, tax review records, charitable-solicitation review records, public authority involvement records, conflict records, sanctions and export-control records, data / AI / cyber records, safeguards records, protected knowledge records, boundary review records, and approval records;
q) donor, funder, sponsor, supporter, provider, host, enterprise actor, university, laboratory, public authority, community, Tribal, Indigenous, civil society, media, and public-interest support classification records where applicable;
r) public acknowledgment records, approved language records, logo-use records, mark-use records, website records, report acknowledgment records, event acknowledgment records, repository notice records, public-safe limitation records, non-reliance records, controlled vocabulary records, and correction records;
s) anti-capture records, concentration review records, influence cap records, firewall records, independent review records, major support review records, refusal records, return records, restriction records, termination records, diversification records, and public clarification records;
t) securities-solicitation boundary records, stopped-discussion records, finance-boundary escalation records, no-investment-advice records, no-brokerage records, no-finder records, no-public-finance-approval records, no-rating records, no-finance-readiness sale records, and GRA role-separation records;
u) recognition, certification, procurement, public authority access, provider preference, GRF-facing, Docket, Grid, Nexus-compatible, publication outcome, research outcome, technical baseline inclusion, controlled-room access, and outcome-purchase refusal records;
v) public-safe notice, limitation language, support disclaimers, no-control disclaimers, non-endorsement language, correction, supersession, withdrawal, takedown, public clarification, and archive records associated with development activities;
w) escalations involving public authority boundary, finance boundary, certification boundary, procurement neutrality, recognition boundary, provider neutrality, sponsor non-control, data / AI / cyber, privacy, safeguards, protected knowledge, civil rights, accessibility, research integrity, public-safe publication, competition, sanctions, export-control, controlled technology, charitable solicitation, tax, nonprofit, private benefit, professional boundary, or development risk;
x) conflicts, recusals, access restrictions, delegation restrictions, resignation, removal, handover, access revocation, and closeout records; and
y) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that the Chief Development, Grants, and Public-Good Support Officer helps secure support for the Corporation’s public-benefit mission, not control over the mission. Grants, donations, sponsorships, in-kind contributions, subscriptions, fees, restricted funds, unrestricted support, public-good infrastructure support, acknowledgments, and development relationships may lawfully sustain evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, public authority learning, safeguards, and Nexus-compatible public-good work; they may not buy governance, authority, outcomes, access, recognition, finance-readiness, certification, procurement advantage, provider preference, public authority meaning, or enterprise execution. Development stewardship shall be lawful, support-without-control, anti-capture, tax-aware, record-supported, public-safe, non-executing, role-separated, reviewable, and correctionable.
Section 152. Secretariat and Central Bureau
152.1 Secretariat Purpose. The Corporation may maintain a Secretariat to serve as the administrative, records-coordination, intake-routing, meeting-support, notice-support, register-support, repository-support, version-control-support, case-management, workflow-coordination, document-control, controlled-room-administration-support, committee-support, council-support, officer-support, Board-support, public-safe notice-support, and institutional continuity support function of the Corporation, subject at all times to applicable law, the Articles or Certificate, this Bylaw, Board resolutions, Board-approved policies, the delegation matrix, the authority matrix, approved budget, fiduciary oversight, nonprofit and non-distribution character, public-benefit purpose, tax-exempt or tax-exempt-compatible restrictions, non-execution, GCRI / GRF / GRA role separation, public-good stack and enterprise stack separation, public authority boundary controls, finance-boundary controls, certification-boundary controls, procurement-neutrality controls, provider-neutrality controls, sponsor non-control controls, data / AI / cyber controls, privacy controls, research integrity controls, safeguards, protected knowledge restrictions, controlled vocabulary, validity-by-record, and correctionability.
The Secretariat exists to make the lawful governance and operational work of the Corporation procedurally reliable, traceable, accessible to authorized persons, reviewable, and correctionable. It may support the preparation, routing, tracking, filing, indexing, versioning, custody, notice, meeting administration, register administration, case ID assignment, forms-first intake, and repository deposit of institutional records. It shall not, by administrative centrality, custody of records, access to systems, preparation of agendas, receipt of intake materials, control of calendars, management of forms, maintenance of registers, or coordination of repository workflows, acquire substantive authority to decide matters reserved to the Board, officers, committees, counsel, public authorities, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, Nexus Network, or any competent body.
The Secretariat shall be a disciplined support function. It may organize authority; it may not create authority. It may route decisions; it may not substitute for decision-makers. It may preserve records; it may not convert defective records into valid authority except through lawful correction, ratification, supersession, or other competent action.
152.2 Central Bureau Purpose. The Corporation may maintain a Central Bureau, whether within the Secretariat or as a separately designated administrative unit, to serve as the central institutional coordination point for official intake, docketing, workflow routing, meeting logistics, register updates, case-numbering, controlled document circulation, notice administration, repository deposit, gazette or notice-stream coordination, records completeness checks, and institutional memory.
The Central Bureau may support:
a) Board, officer, committee, council, working group, panel, forum, and program administration;
b) evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, technical baseline, public authority learning, safeguards, and public-safe publication workflows;
c) intake and routing for grants, donations, sponsorships, in-kind contributions, subscriptions, fees, controlled-room participation, public authority participation, academic participation, community participation, technical contribution, provider participation, host participation, and other institutional interactions;
d) case-numbering, register entry, metadata classification, access classification, publication classification, retention classification, version classification, supersession classification, correction routing, and archive routing;
e) controlled-room, clean-room, evidence-room, data-room, public authority room, and no-download-room administrative support;
f) state, territorial, Tribal, local, North America, cross-border, 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, university, laboratory, community, and enterprise-stack interface routing; and
g) continuity support for essential records, official communication channels, meeting calendars, authority matrices, delegation logs, registers, repositories, and approved notice pathways.
The Central Bureau shall not be represented as a public authority bureau, regulatory office, finance-readiness office, certification office, procurement office, recognition office, emergency command office, public warning office, provider-selection office, investment office, insurance office, lending office, rating office, public finance office, or enterprise execution office.
152.3 Administrative Support to Board. The Secretariat may provide administrative support to the Board and its directors. Such support may include meeting scheduling, notice preparation, agenda preparation under authorized direction, board materials compilation, secure circulation, attendance tracking, quorum support, conflict disclosure collection, recusal notation, minute preparation support, resolution drafting support under authorized direction, action item tracking, follow-up tracking, register updates, repository deposit, and Board record retention.
Administrative support to the Board shall preserve the distinction between support and governance. The Secretariat may assist the Chair, Secretary, officers, committee chairs, counsel, and directors in preparing and maintaining Board processes, but shall not determine whether the Board has lawfully approved a matter except through the records authorized by the Secretary, Board, counsel, or competent officer. Where a Board record appears incomplete, inconsistent, defective, unofficial, unsigned, unapproved, unversioned, or misclassified, the Secretariat shall route the issue for correction rather than cure the defect by assumption.
Board support shall be subject to confidentiality, privilege, data / AI / cyber, public authority confidentiality, protected knowledge, sponsor confidentiality, provider confidentiality, personal information, rights-bearing data, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, and legal-hold controls. No Board material shall be uploaded to unapproved AI systems, stored in shadow systems, circulated through uncontrolled side channels, or converted into public-facing materials without approval.
152.4 Administrative Support to Officers. The Secretariat may provide administrative support to officers acting within recorded authority. Such support may include calendar coordination, meeting coordination, intake routing, document preparation support, delegation tracking, authority matrix lookup, workflow administration, record collection, signature routing, decision-log preparation, register updates, notice preparation, repository deposit, task tracking, and closeout support.
Administrative support to officers shall not enlarge officer authority. A Secretariat action taken for an officer shall be valid only if the underlying officer act is within lawful authority, delegation, budget, approval pathway, and record requirements. The Secretariat shall not treat officer title, urgency, seniority, recurring practice, system access, or informal instruction as sufficient authority where a delegation, Board approval, counsel review, public-safe review, data / AI / cyber review, safeguards review, finance-boundary review, certification-boundary review, public authority review, or other approval is required.
Where an officer request appears outside authority, incomplete, inconsistent with the Bylaw, inconsistent with Board-approved policy, inconsistent with public-benefit purpose, or likely to create public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider preference, sponsor control, data / AI / cyber risk, safeguards risk, protected knowledge risk, or public-safe publication risk, the Secretariat shall route the matter for escalation rather than process it as routine administration.
152.5 Administrative Support to Committees and Councils. The Secretariat may provide administrative support to Board committees, officer-created working groups, Leadership Councils, Helix Councils, advisory councils, scientific and technical advisory bodies, public authority forums, community and safeguards forums, peer review panels, model review panels, evidence review panels, red-team panels, technical working groups, drafting groups, standards-support groups, open-source maintainer groups, Nexus Competence Cells, program steering groups, controlled-room review groups, and other bodies created, chartered, delegated, or recorded under this Bylaw.
Such support may include:
a) charter repository support;
b) membership and appointment tracking;
c) conflict disclosure administration;
d) attendance tracking;
e) notice and agenda support;
f) secure materials circulation;
g) minutes and recommendation record support;
h) action item tracking;
i) minority view capture where permitted;
j) escalation routing;
k) recommendation routing to officers, committees, counsel, or Board;
l) sunset and periodic review tracking;
m) confidentiality acknowledgment tracking;
n) data / AI / cyber access tracking;
o) public authority capacity tracking;
p) competition-law meeting discipline support; and
q) committee and council records support.
Administrative support shall not convert any committee, council, forum, panel, working group, or advisory body into a substitute Board, public authority, regulator, finance-readiness authority, certification body, procurement body, recognition body, emergency command body, public warning authority, provider selector, sponsor-controlled forum, or enterprise execution body.
152.6 Case ID Administration. The Secretariat may administer case IDs, matter numbers, docket numbers, intake numbers, room IDs, register IDs, repository IDs, exhibit IDs, publication IDs, correction IDs, incident IDs, access request IDs, public authority interface IDs, grant IDs, sponsorship IDs, donation IDs, controlled-room IDs, technical contribution IDs, software release IDs, model register IDs, inference record IDs, compute workload IDs, proof receipt IDs, Docket-support IDs, Grid-support IDs, GRF-facing input IDs, GRA-facing technical input IDs, and other structured identifiers approved by the Corporation.
Case ID administration shall serve traceability, not substantive approval. Assignment of a case ID shall indicate only that a matter has been received, logged, indexed, routed, or classified for administrative handling. It shall not indicate that the matter is approved, valid, verified, validated, recognized, certified, finance-ready, procurement-ready, Nexus-compatible, public-authority-approved, Board-approved, legally cleared, public-safe, publication-ready, access-approved, or eligible for execution.
Each case ID system shall, as applicable, identify:
a) matter type;
b) intake source;
c) responsible owner;
d) custodian;
e) access class;
f) publication class;
g) confidentiality class;
h) data / AI / cyber class;
i) public authority capacity class;
j) finance-boundary class;
k) certification-boundary class;
l) safeguards class;
m) status;
n) routing history;
o) required reviews;
p) approval status;
q) correction history;
r) supersession status;
s) retention class; and
t) archive status.
No person may use the existence of a case ID, docket number, room ID, proof receipt number, register number, or repository number as a public claim of status unless the competent record expressly authorizes the claim.
152.7 Forms-First Intake Administration. The Secretariat may administer forms-first intake processes to ensure that institutional matters are received with sufficient information, disclosures, acknowledgments, classifications, routing instructions, and records to support lawful review. Forms-first intake may apply to membership, participation, public authority participation, controlled-room participation, research intake, evidence intake, technical contributions, software contributions, dataset contributions, AI-use requests, data-access requests, repository-access requests, public authority references, publication requests, correction requests, grant requests, donation requests, sponsorship requests, in-kind support requests, provider interfaces, host interfaces, community interfaces, Tribal and Indigenous interfaces, protected knowledge concerns, grievances, incidents, and other matters.
Forms-first intake may require:
a) identity and affiliation information;
b) capacity classification;
c) authority representation;
d) conflict disclosure;
e) related-party disclosure;
f) sponsor, donor, funder, provider, host, public authority, capital actor, university, laboratory, community, or enterprise relationship disclosure;
g) sanctions, export-control, controlled-technology, and jurisdictional screening information;
h) data, AI, cyber, privacy, and repository information;
i) research ethics, human-subjects, community, Tribal, Indigenous, and protected knowledge information;
j) public authority boundary information;
k) finance-boundary, procurement-boundary, certification-boundary, recognition-boundary, provider-neutrality, and sponsor non-control information;
l) confidentiality, conduct, non-retaliation, controlled vocabulary, public-safe claims, and correction acknowledgments; and
m) supporting materials and record links.
A form shall not substitute for judgment. Completion of an intake form shall not create admission, approval, authority, access, public-safe status, public authority capacity, finance-readiness, certification, recognition, procurement advantage, provider preference, sponsor entitlement, or publication status unless the form is approved by the competent authority and the record states the result.
152.8 Register Administration. The Secretariat may support register administration under the direction of the Secretary, relevant officer, committee, or custodian. Registers may include governance registers, officer registers, director registers, committee registers, delegation registers, authority matrix registers, policy registers, protocol registers, schedule registers, form registers, notice registers, repository registers, evidence registers, method registers, observability registers, ontology registers, technical asset registers, software asset registers, dataset registers, model registers, system registers, benchmark registers, access registers, correction registers, incident registers, risk registers, support registers, public authority capacity registers, participant registers, safeguards registers, controlled vocabulary registers, and other registers approved by the Corporation.
Register administration may include entry creation, metadata completion, status updates, access class tagging, publication class tagging, version tracking, supersession tracking, correction tracking, archive routing, review-date reminders, custodian routing, and completeness checks. Register administration shall be performed only within assigned authority and shall not alter substantive status without competent approval.
A register entry shall state only the recorded status that the competent authority has approved. No Secretariat staff member, contractor, volunteer, fellow, advisor, contributor, or administrator shall inflate a register entry into certification, recognition, finance-readiness, procurement approval, public authority adoption, provider approval, sponsor entitlement, legal clearance, tax clearance, public-safe approval, or enterprise execution authority.
152.9 Repository Administration. The Secretariat may support repository administration for official repositories, controlled repositories, public repositories, internal repositories, legal repositories, Board repositories, committee repositories, evidence repositories, methods repositories, observability repositories, ontology repositories, public-good software repositories, technical baseline repositories, dataset repositories, model repositories, secure-release repositories, public-safe publication repositories, grant repositories, sponsorship repositories, participant repositories, controlled-room repositories, and archive repositories.
Repository administration may include:
a) folder or collection setup;
b) access provisioning routing;
c) access revocation routing;
d) metadata tagging;
e) version deposit;
f) supersession marking;
g) draft / adopted / in force / superseded / withdrawn / archived status marking;
h) retention tagging;
i) legal hold tagging;
j) integrity checks;
k) duplicate detection;
l) repository migration support;
m) repository continuity support;
n) public / controlled / internal status differentiation; and
o) archive and secure disposal routing.
Repository placement shall not create authority. No draft, working copy, redline, AI summary, slide, translation, extract, fork, mirror, cached copy, public explainer, unofficial repository entry, or derivative communication shall be treated as operative unless it has been adopted, approved, versioned, deposited, and recorded through the competent pathway.
152.10 Gazette or Notice-Stream Administration. The Secretariat may support the Corporation’s gazette, notice stream, public-safe notice mechanism, internal notice mechanism, controlled notice mechanism, state-specific notice mechanism, territorial notice mechanism, Tribal-interface notice mechanism, cross-border notice mechanism, repository notice mechanism, correction notice mechanism, supersession notice mechanism, withdrawal notice mechanism, takedown notice mechanism, and archive notice mechanism where approved.
Gazette or notice-stream administration may include preparation, routing, formatting, version control, publication scheduling, distribution, access control, correction, supersession, and archive of notices concerning:
a) adoption, amendment, restatement, repeal, withdrawal, supersession, or archive of governing instruments;
b) Board actions, officer appointments, delegations, suspensions, revocations, committee creations, committee dissolutions, and policy changes where notice is approved or required;
c) public-safe publications, technical baselines, public-good software releases, dataset releases, dashboard launches, map publications, and correction notices;
d) public authority room notices, controlled-room notices, no-download-room notices, access notices, and closeout notices;
e) sponsor, donor, funder, supporter, provider, host, university, laboratory, community, Tribal, Indigenous, civil society, media, or public-interest participation notices where permitted;
f) public-safe limitation language, non-reliance notices, public authority boundary notices, finance-boundary notices, certification-boundary notices, procurement-neutrality notices, recognition-boundary notices, provider-neutrality notices, sponsor non-control notices, and correctionability notices; and
g) state, territorial, Tribal, local, North America, GCRI Canada, GRF, GRA, Nexus, consortium, national company, Project SPV, provider, host, sponsor, and enterprise-stack interface notices where approved.
A notice shall not cure an unauthorized act, missing approval, unlawful claim, defective record, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, data breach, AI misuse, cyber incident, safeguards breach, protected knowledge breach, private benefit concern, or competition violation unless the competent authority expressly determines that notice is an appropriate component of correction.
152.11 Calendar and Meeting Administration. The Secretariat may support institutional calendar and meeting administration. This support may apply to Board meetings, committee meetings, officer meetings, Leadership Council meetings, Helix Council meetings, advisory forum meetings, public authority learning sessions, controlled-room sessions, clean-room sessions, evidence-room sessions, data-room sessions, no-download-room sessions, public-safe publication reviews, research reviews, evidence reviews, method reviews, technical reviews, safeguards reviews, grant reviews, sponsorship reviews, public authority interface meetings, GCRI Canada interface meetings, GRF interface meetings, GRA interface meetings, Nexus interface meetings, consortium interface meetings, and program meetings.
Calendar and meeting administration shall include, as applicable:
a) scheduling;
b) participant verification;
c) capacity classification;
d) agenda routing;
e) secure materials circulation;
f) conflict disclosure collection;
g) confidentiality acknowledgment confirmation;
h) competition notice distribution;
i) public authority boundary notice distribution;
j) finance-boundary notice distribution;
k) controlled-room admission checks;
l) meeting link security;
m) recording restrictions;
n) attendance records;
o) minutes or meeting note routing;
p) action item tracking; and
q) follow-up and closeout.
Meeting logistics shall not create membership, authority, public authority status, official adoption, public finance status, certification status, recognition status, finance-readiness status, provider status, sponsor control, or enterprise execution status. Attendance shall mean attendance only unless a competent record states otherwise.
152.12 Docket Routing Administration. The Secretariat may support Docket routing administration for matters that are required or permitted to be logged, reviewed, classified, staged, routed, corrected, superseded, withdrawn, archived, or transmitted through a Docket-support process. Docket routing may include evidence dockets, method dockets, observability dockets, ontology dockets, technical baseline dockets, public-safe publication dockets, correction dockets, public authority learning dockets, controlled-room dockets, support acceptance dockets, technical contribution dockets, incident dockets, risk dockets, Nexus Docket-support records, Nexus Grid-support records, GRF-facing input routing, and GRA-facing technical input routing.
Docket routing administration may include:
a) intake logging;
b) matter classification;
c) completeness check;
d) assignment to responsible owner;
e) required review identification;
f) conflict and recusal notation;
g) access class assignment;
h) public-safe limitation flagging;
i) deadline tracking;
j) status tracking;
k) escalation routing;
l) decision record linkage;
m) correction and supersession linkage; and
n) closeout and archive.
Docket routing shall not be confused with Docket approval. The Secretariat shall not represent that a matter is approved, mature, recognized, finance-ready, certified, procurement-ready, Nexus-compatible, public authority endorsed, public-safe, or execution-ready merely because it has been routed, logged, indexed, assigned, or reviewed administratively. Any Docket or Grid meaning shall be limited to the competent authority and governing record.
152.13 Records Completeness Checks. The Secretariat may conduct records completeness checks to identify missing, incomplete, inconsistent, misclassified, unapproved, unsigned, undated, unversioned, unsuperseded, unarchived, improperly published, improperly restricted, improperly retained, improperly deleted, or otherwise defective records. Completeness checks may apply to governance records, Board records, officer records, committee records, member and participant records, public authority capacity records, grant records, donation records, sponsorship records, contract records, financial records, evidence records, method records, research records, data records, AI records, cyber records, repository records, technical asset records, software release records, controlled-room records, safeguards records, correction records, and interface records.
Records completeness checks may identify whether a record contains, as applicable:
a) title;
b) version;
c) status;
d) date;
e) authority;
f) approver;
g) custodian;
h) responsible owner;
i) access class;
j) publication class;
k) retention class;
l) required limitation language;
m) conflict or recusal status;
n) required review records;
o) decision record;
p) effective date;
q) review date;
r) supersession status;
s) correction history; and
t) archive status.
A completeness check shall not itself validate a defective act. Where a defect is identified, the Secretariat shall route the matter for correction, ratification where lawful, limitation, restriction, supersession, withdrawal, takedown, reclassification, legal review, Board review, officer review, committee review, or archive.
152.14 Version Control Support. The Secretariat may support version control for bylaws, Board resolutions, policies, protocols, schedules, forms, registers, matrices, checklists, technical profiles, controlled vocabularies, public-safe notice libraries, operating procedures, manuals, playbooks, templates, public-safe publications, datasets, software releases, technical baselines, repository artifacts, evidence packs, methods documents, ontology artifacts, proof receipts, Docket-support materials, Grid-support materials, GRF-facing inputs, GRA-facing technical inputs, and Nexus-compatible materials.
Version control support shall include, as applicable:
a) version numbering;
b) draft status marking;
c) adopted status marking;
d) in-force status marking;
e) superseded status marking;
f) withdrawn status marking;
g) archived status marking;
h) effective date tracking;
i) review date tracking;
j) changelog support;
k) redline support;
l) supersession chain support;
m) hash, integrity, or tamper-evident reference support where used;
n) repository deposit;
o) public or controlled notice routing; and
p) correction history.
No version control label shall be used to create substantive authority beyond the governing record. A document marked “final,” “approved,” “current,” “official,” “adopted,” “Nexus-compatible,” “verified,” “validated,” “recognized,” “finance-ready,” “certified,” or similar shall not have that status unless the competent authority has approved the status and the record supports the label.
152.15 Notice Support. The Secretariat may provide notice support for notices required or permitted under applicable law, the Articles or Certificate, this Bylaw, Board resolutions, policies, agreements, grant instruments, sponsorship instruments, public authority interface instruments, controlled-room terms, participant terms, contributor terms, repository rules, data rules, AI rules, cyber rules, safeguards rules, and correction procedures.
Notice support may include:
a) preparing notice drafts under authorized direction;
b) identifying recipients;
c) verifying addresses or electronic delivery details;
d) applying notice categories;
e) applying access classes;
f) applying publication classes;
g) coordinating translations or accessibility formats where approved;
h) routing notices for approval;
i) distributing notices;
j) logging delivery;
k) recording waiver where lawful;
l) tracking response deadlines;
m) issuing reminders;
n) correcting defective notices; and
o) archiving notice records.
Notice support shall not be treated as legal determination that notice is sufficient unless the competent authority or counsel has made that determination where required. Where notice affects Board action, member action, director rights, officer removal, participant suspension, public authority interface, legal compliance, contractual rights, grant rights, sponsorship rights, protected knowledge, data breach, cyber incident, public-safe correction, or other material matter, the Secretariat shall route the notice for appropriate review before issuance.
152.16 Controlled-Room Administration Support. The Secretariat may support administration of controlled rooms, clean rooms, evidence rooms, data rooms, public authority rooms, regulator-listening rooms, public finance reader rooms, emergency-management learning rooms, no-download rooms, confidential review rooms, legal rooms, safeguards rooms, protected knowledge rooms, model review rooms, red-team rooms, technical review rooms, and other restricted environments approved by the Corporation.
Controlled-room administration support may include:
a) room creation routing;
b) room purpose classification;
c) participant intake;
d) identity verification routing;
e) capacity classification routing;
f) conflict disclosure collection;
g) sanctions and export-control routing;
h) data / AI / cyber review routing;
i) privacy review routing;
j) competition-law notice routing;
k) public authority boundary notice routing;
l) finance-boundary notice routing;
m) safeguards and protected knowledge review routing;
n) access class assignment;
o) no-download controls;
p) exhibit numbering;
q) chain-of-custody support;
r) logging and attendance records;
s) access revocation routing;
t) closeout, return, deletion, sealing, archive, or secure disposal routing; and
u) room records.
Controlled-room administration shall not create substantive permission to access restricted materials. Access shall require competent authorization, need-to-know, capacity classification, screening, acknowledgment, and applicable review. Participation in any room shall not create endorsement, public authority adoption, certification, recognition, finance-readiness, procurement approval, provider approval, sponsor entitlement, public warning authority, emergency command authority, legal clearance, or enterprise execution authority.
152.17 No Secretariat Substantive Authority Except as Delegated. The Secretariat, Central Bureau, administrative staff, contractors, volunteers, fellows, advisors, coordinators, repository administrators, register administrators, case administrators, workflow administrators, meeting administrators, room administrators, and records support personnel shall have no substantive authority except as expressly delegated, documented, limited, and recorded.
No Secretariat or Central Bureau function may:
a) amend this Bylaw;
b) approve Board reserved matters;
c) appoint or remove directors or principal officers;
d) approve major policies, protocols, schedules, instruments, or public-safe outputs unless delegated;
e) approve budgets, material contracts, grants, donations, sponsorships, restricted funds, in-kind contributions, or major expenditures unless delegated;
f) approve research conclusions, evidence classifications, method validity, observability outputs, technical truth outputs, public-good software releases, technical baselines, public-safe publications, Docket-support status, Grid-support status, GRF-facing input status, or GRA-facing technical input status unless delegated;
g) approve public authority references, official-capacity classifications, public authority room admission, regulator-listening status, public finance reader status, emergency-management participant status, or public authority data contribution unless delegated;
h) approve data access, AI use, model use, repository access, controlled-room access, no-download-room access, software release, or technical asset release unless delegated;
i) approve certification, accreditation, recognition, finance-readiness, insurance-readiness, rating, procurement approval, provider preference, sponsor entitlement, public warning, emergency command, public finance approval, investment-related status, or enterprise execution; or
j) create external reliance through administrative labels, public language, notices, emails, calendars, forms, IDs, registers, repository entries, workflow statuses, minutes drafts, or meeting logistics.
Where Secretariat personnel are separately appointed as officers, committee members, authorized signatories, custodians, or decision-makers, they shall act only in that separately recorded capacity and only within the applicable authority, conflict, recusal, confidentiality, and records controls.
152.18 Secretariat and Central Bureau Records. The Corporation shall maintain Secretariat and Central Bureau Records sufficient to demonstrate the creation, purpose, authority, staffing, delegated responsibilities, administrative functions, case ID systems, forms-first intake systems, register administration, repository administration, gazette or notice-stream administration, calendar and meeting administration, Docket routing administration, records completeness checks, version control support, notice support, controlled-room administration support, substantive authority limits, escalations, corrections, access restrictions, continuity support, and closeout of the Secretariat and Central Bureau.
Secretariat and Central Bureau Records shall include, as applicable:
a) Board resolution, officer authorization, policy, operating procedure, or other competent record establishing the Secretariat or Central Bureau;
b) role descriptions, reporting lines, custodians, responsible owners, staffing records, contractor records, volunteer records, fellow records, advisor records, training records, confidentiality acknowledgments, conflict disclosures, sanctions and export-control screenings where applicable, data / AI / cyber acknowledgments, and safeguards acknowledgments;
c) case ID system records, matter numbering records, docket numbering records, room ID records, register ID records, repository ID records, proof receipt routing records, Docket-support routing records, Grid-support routing records, GRF-facing input routing records, and GRA-facing technical input routing records;
d) forms-first intake records, form libraries, intake classifications, required fields, intake completeness checks, routing rules, approval pathways, escalation pathways, and rejected or incomplete intake records;
e) register administration records, register update logs, custodian instructions, access class records, publication class records, retention class records, correction records, supersession records, withdrawal records, archive records, and register integrity records;
f) repository administration records, repository locations, access logs, permission changes, deposit logs, version logs, supersession logs, legal hold records, integrity records, migration records, continuity records, archive records, and secure disposal records;
g) gazette and notice-stream records, notice drafts, approval records, delivery logs, public notice records, controlled notice records, internal notice records, state-specific notice records, territorial notice records, Tribal-interface notice records, cross-border notice records, correction notice records, supersession notice records, withdrawal notice records, takedown notice records, and archive notice records;
h) calendar and meeting records, notices, agendas, materials circulation logs, participant lists, attendance records, capacity classifications, confidentiality acknowledgments, conflict disclosures, recusal records, competition notices, public authority boundary notices, finance-boundary notices, meeting minutes routing records, action item records, and closeout records;
i) Docket routing records, evidence docket records, method docket records, observability docket records, ontology docket records, technical baseline docket records, public-safe publication docket records, correction docket records, incident docket records, risk docket records, Nexus Docket-support records, Nexus Grid-support records, GRF-facing input routing records, and GRA-facing technical input routing records;
j) records completeness check records, defect logs, missing approval logs, missing signature logs, missing version logs, misclassification logs, incomplete metadata logs, correction routing logs, ratification routing logs where lawful, restriction logs, withdrawal logs, takedown logs, and archive routing logs;
k) version control records, version identifiers, changelogs, redlines, draft records, adopted records, in-force records, superseded records, withdrawn records, archived records, effective-date records, review-date records, hash or tamper-evident reference records where used, and correction history records;
l) notice support records, recipient lists, delivery method records, waiver records, response deadline records, reminder records, defective notice correction records, translation records, accessibility records, and notice archive records;
m) controlled-room administration records, room creation records, room purpose classifications, participant intake records, identity verification routing records, capacity classification records, conflict records, sanctions records, export-control records, data / AI / cyber records, privacy records, competition records, public authority boundary records, finance-boundary records, safeguards records, protected knowledge records, access records, no-download records, exhibit records, chain-of-custody records, attendance logs, access revocation records, return records, deletion records, sealing records, archive records, and closeout records;
n) escalation records involving unauthorized requests, authority defects, missing approvals, public authority boundary concerns, finance-boundary concerns, certification-boundary concerns, procurement-neutrality concerns, recognition-boundary concerns, provider-neutrality concerns, sponsor non-control concerns, data / AI / cyber concerns, privacy concerns, protected knowledge concerns, safeguards concerns, competition concerns, sanctions concerns, export-control concerns, controlled-technology concerns, public-safe publication concerns, and records integrity concerns;
o) correction, supersession, withdrawal, retraction, takedown, public clarification, controlled clarification, access restriction, suspension, revocation, archive, and secure disposal records associated with Secretariat or Central Bureau activity;
p) continuity records, backup administrator records, successor custodian records, repository continuity records, register continuity records, meeting continuity records, notice continuity records, legal hold continuity records, controlled-room continuity records, disaster recovery support records, and migration records;
q) audits, reviews, evaluations, training records, corrective action records, process redesign records, access review records, authority review records, and periodic review records;
r) conflicts, recusals, access restrictions, delegation restrictions, resignation, removal, handover, access revocation, and closeout records for Secretariat and Central Bureau personnel; and
s) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that the Secretariat and Central Bureau provide administrative seriousness, not substantive power. They may make the Corporation’s governance, records, notices, registers, repositories, controlled rooms, meetings, forms, dockets, workflows, and correction pathways reliable; they may not create authority, waive authority, cure defects by assumption, approve prohibited functions, create external reliance, or convert administrative status into public authority action, finance-readiness, certification, procurement approval, recognition, provider preference, sponsor entitlement, public warning, emergency command, legal clearance, or enterprise execution. Secretariat and Central Bureau administration shall be lawful, bounded, records-first, access-controlled, public-safe, non-executing, role-separated, reviewable, and correctionable.
Section 153. Delegation of Authority
153.1 Delegation Purpose. The Corporation may delegate limited authority to directors, officers, committees, council chairs, working group leads, custodians, employees, contractors, agents, representatives, repository administrators, controlled-room administrators, program leads, technical leads, or other persons only where such delegation is lawful, necessary or appropriate for the efficient conduct of the Corporation’s nonprofit, public-benefit, evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, public authority learning, safeguards, records, repository, controlled-room, publication, administrative, and Nexus-compatible public-good functions.
Delegation exists to make lawful authority usable, traceable, accountable, reviewable, and correctionable. It shall not be used to evade Board oversight, dilute fiduciary responsibility, obscure responsibility, create informal governance, accelerate prohibited functions, create apparent authority, shift reserved matters to unaccountable persons, weaken public authority boundaries, weaken finance boundaries, weaken certification or procurement boundaries, create provider preference, enable sponsor control, bypass data / AI / cyber controls, bypass safeguards, bypass legal review, or convert administrative convenience into substantive power.
Every delegation shall be interpreted narrowly and against authority inflation. A delegated person may act only within the scope, duration, budget, conditions, access class, publication class, review requirements, approval thresholds, escalation requirements, and record requirements stated in the delegation and applicable higher-order instruments. No delegation shall be valid merely because a person holds a title, leads a program, manages a repository, chairs a meeting, has system access, communicates with public authorities, coordinates sponsors, prepares a document, controls a workflow, signs an email, appears in public materials, or is operationally relied upon.
153.2 Board Delegation. The Board may delegate authority to officers, committees, directors, employees, contractors, agents, representatives, custodians, or other persons to the fullest extent permitted by applicable law, the Articles or Certificate, this Bylaw, Board resolutions, member approval requirements where applicable, fiduciary duties, public-benefit purpose, nonprofit and non-distribution character, tax-exempt or tax-exempt-compatible restrictions, and mandatory controls.
Board delegation may include authority to implement Board-approved strategy, administer Board-approved budgets, sign specified instruments, approve specified expenditures, manage specified programs, supervise specified staff or contractors, operate specified controlled rooms, administer specified repositories, approve specified publications, administer specified grants or sponsorships, maintain specified registers, execute specified contracts, implement specified policies, respond to specified incidents, issue specified notices, or perform specified governance-support functions.
A Board delegation shall not be presumed. It shall be evidenced by resolution, written consent, approved policy, authority matrix, delegation matrix, charter, officer appointment record, contract, employment instrument, or other competent Board record. Where a Board delegation affects material governance, mission lock, legal status, tax status, restricted funds, public authority interfaces, finance-boundary matters, data / AI / cyber systems, safeguards, protected knowledge, public-safe publications, technical assets, repositories, controlled rooms, Nexus interfaces, GCRI Canada interfaces, GRF interfaces, GRA interfaces, major support relationships, or Board reserved matters, the delegation shall identify the specific authority granted and the controls applicable to its use.
153.3 Officer Delegation. An officer may delegate operational authority only where the officer has authority to do so and only within the officer’s own lawful authority, Board-approved delegation, approved budget, applicable policy, authority matrix, delegation matrix, and records requirements. An officer may not delegate more authority than the officer possesses, may not delegate authority prohibited by law or this Bylaw, and may not delegate a matter reserved to the Board unless the Board has expressly and lawfully authorized such delegation.
Officer delegations may include limited authority for routine administration, intake handling, workflow routing, meeting coordination, procurement support, document preparation, repository administration, register updates, controlled-room administration, technical review support, program coordination, data-access routing, publication routing, participant onboarding, support intake, records maintenance, notice support, and other operational acts within approved controls.
Officer delegation shall be written, versioned, and recorded. Informal instructions, recurring practice, Slack messages, calendar invitations, task assignments, workflow assignments, project-management cards, repository permissions, system roles, AI-generated summaries, meeting notes, draft policies, or implied practice shall not create officer delegation unless they are incorporated into a competent record or otherwise recognized by an authorized delegation instrument.
153.4 Delegation Matrix. The Corporation shall maintain a Delegation Matrix or equivalent authority-control instrument that identifies who may act, for what purpose, within what limits, under what conditions, with what approvals, with what records, and subject to what escalation pathways. The Delegation Matrix shall be consistent with law, the Articles or Certificate, this Bylaw, Board resolutions, Board reserved matters, approved budget, committee charters, officer appointments, policies, conflict controls, data / AI / cyber controls, safeguards, public-safe publication controls, and Nexus role-separation rules.
The Delegation Matrix may classify authority by:
a) governance authority;
b) officer authority;
c) committee authority;
d) financial authority;
e) contracting authority;
f) signature authority;
g) procurement administration authority;
h) publication authority;
i) public authority reference authority;
j) data access authority;
k) AI-use authority;
l) model approval authority;
m) repository access authority;
n) software release authority;
o) controlled-room admission authority;
p) support acceptance authority;
q) incident response authority;
r) correction authority; and
s) emergency authority.
The Delegation Matrix shall be treated as an implementing instrument subordinate to law, the Articles or Certificate, this Bylaw, and Board reserved powers. Where the Delegation Matrix conflicts with a higher-order instrument, the higher-order instrument shall control. Where the Delegation Matrix is silent or ambiguous, no authority shall be implied where the matter is material, external-facing, regulated-perimeter-sensitive, public authority-sensitive, finance-adjacent, certification-adjacent, procurement-adjacent, provider-sensitive, sponsor-sensitive, data-sensitive, AI-sensitive, cyber-sensitive, safeguards-sensitive, protected-knowledge-sensitive, public-safe-publication-sensitive, or Nexus-interface-sensitive.
153.5 Written Delegation Requirement. Each delegation shall be in writing or in another durable, retrievable, controlled, and record-supported form approved by the Corporation. A delegation shall identify, as applicable, the delegating authority, delegate, role, scope, purpose, effective date, duration, expiration date, budget limit, contract limit, signature limit, publication limit, data-access limit, AI-use limit, cyber limit, repository limit, controlled-room limit, public authority interface limit, finance-boundary limit, certification-boundary limit, procurement-boundary limit, safeguards limit, required reviews, escalation requirements, reporting requirements, revocation rule, custodian, repository location, retention class, and correction pathway.
A written delegation may be contained in:
a) Board resolution;
b) written consent;
c) officer appointment record;
d) committee charter;
e) council charter;
f) working group mandate;
g) authority matrix;
h) delegation matrix;
i) employment or contractor instrument;
j) program charter;
k) controlled-room charter;
l) repository access instrument;
m) policy or operating procedure; or
n) other competent record approved by the Corporation.
A person asserting delegated authority bears the burden of identifying the record granting that authority. Where no record exists, the act shall be treated as unauthorized unless lawful ratification is available and approved by the competent authority.
153.6 Scope. Each delegation shall state its scope with sufficient specificity to prevent authority inflation. Scope may be defined by subject matter, function, program, department, budget, contract type, jurisdiction, state, territory, Tribal or Indigenous interface, public authority interface, North America interface, data class, AI class, cyber class, repository, room, publication type, technical asset, support class, participant class, time period, risk class, review threshold, or other limiting category.
A delegation shall not be interpreted to include adjacent powers merely because they are operationally convenient. Authority to prepare materials shall not include authority to approve them. Authority to route a contract shall not include authority to sign it. Authority to maintain a register shall not include authority to create substantive status. Authority to host a meeting shall not include authority to bind the Corporation. Authority to administer a controlled room shall not include authority to admit persons outside admission criteria. Authority to draft a technical baseline shall not include authority to certify conformance. Authority to communicate with a public authority shall not include authority to act as a public authority or accept public authority delegation. Authority to coordinate support shall not include authority to sell outcomes, recognition, finance-readiness, certification, procurement advantage, public authority access, or provider preference.
153.7 Duration. Each delegation shall state its duration, expiration, renewal pathway, and review cycle where applicable. A delegation may be continuing, annual, program-specific, project-specific, matter-specific, emergency, interim, acting, temporary, conditional, or one-time. A delegation shall expire according to its terms, upon revocation, upon termination of the delegate’s role, upon completion of the delegated matter, upon expiration of the underlying approval, upon dissolution of the relevant committee or program, upon expiration of the approved budget, upon termination of access rights, or upon any other event specified by the competent record.
No delegation shall continue indefinitely by silence where the delegation affects material legal, tax, financial, public authority, finance-boundary, certification-boundary, procurement-neutrality, data / AI / cyber, safeguards, protected knowledge, technical asset, repository, controlled-room, public-safe publication, support acceptance, or Nexus-interface matters unless the Board or competent authority has expressly approved a continuing delegation and periodic review.
A person whose delegation has expired shall immediately cease acting under that delegation and shall support handover, closeout, access revocation, records transfer, and correction of any public or internal materials that continue to imply authority.
153.8 Conditions. A delegation may be unconditional only where the matter is low-risk, routine, lawful, within approved budget, within approved policy, and not otherwise subject to required review. Delegations may be conditioned on prior approval, concurrent approval, post-action reporting, counsel review, compliance review, tax review, finance review, public authority review, data / AI / cyber review, safeguards review, research integrity review, publication review, conflict clearance, sanctions screening, export-control screening, controlled-technology review, competition review, Board ratification, or other controls.
Conditions may include:
a) spending thresholds;
b) contract forms;
c) approved counterparties;
d) prohibited counterparties;
e) public-safe language requirements;
f) non-reliance language requirements;
g) data classification rules;
h) AI-use restrictions;
i) cybersecurity requirements;
j) access-control requirements;
k) public authority capacity classifications;
l) finance-boundary notices;
m) certification-boundary notices;
n) procurement-neutrality notices;
o) sponsor non-control notices;
p) provider-neutrality notices;
q) safeguards requirements;
r) protected knowledge restrictions; and
s) correction and escalation obligations.
A conditional delegation shall be non-operative if its conditions are not satisfied, unless the competent authority lawfully waives, modifies, cures, or ratifies the defect by record.
153.9 Budget Limit. A delegation involving spending, procurement, contracting, reimbursement, grants, sponsorship benefits, restricted funds, subscriptions, fees, program costs, travel, events, software tools, cloud services, compute resources, data services, AI systems, cybersecurity services, consultants, contractors, fellows, awards, stipends, scholarships, or in-kind support shall state or incorporate a budget limit. The budget limit may be expressed by dollar amount, approved budget line, project budget, program budget, contract threshold, expense category, time period, vendor, fund, restricted purpose, or other recorded control.
No delegated person may split transactions, reclassify expenses, create artificial phases, use multiple vendors, use related parties, convert cash support to in-kind support, route through another actor, or use emergency language to avoid budget limits. Any expenditure outside the budget limit shall require prior approval or lawful ratification where permitted.
Budget authority shall not include authority to use funds for private inurement, impermissible private benefit, prohibited execution, public authority substitution, finance execution, certification, procurement approval, recognition, provider preference, sponsor control, political activity, unlawful lobbying, sanctions violations, export-control violations, controlled-technology violations, data misuse, AI misuse, cyber misuse, protected knowledge misuse, or activities inconsistent with public-benefit purpose.
153.10 Contract Limit. A delegation involving contracts shall state or incorporate contract limits, including permitted contract types, maximum value, term length, renewal authority, amendment authority, termination authority, required form, review requirements, signature authority, insurance requirements, indemnity requirements, IP requirements, confidentiality requirements, data-processing requirements, cybersecurity requirements, AI-use requirements, export-control requirements, sanctions requirements, public authority requirements, grant requirements, sponsorship requirements, provider-neutrality requirements, sponsor non-control requirements, and record requirements.
Contract authority may include authority to negotiate, prepare, route, recommend, approve, sign, amend, renew, terminate, or close out contracts only to the extent expressly stated. Authority to negotiate shall not include authority to sign. Authority to prepare shall not include authority to approve. Authority to approve business terms shall not include authority to waive legal terms. Authority to sign one contract shall not include authority to sign amendments, renewals, statements of work, purchase orders, data-processing addenda, IP assignments, public authority instruments, sponsorship instruments, or restricted fund instruments unless stated.
No contract delegation shall authorize the Corporation to become a public authority, regulator, public warning body, emergency command body, public procurement authority, certification body, recognition body, finance-readiness authority, broker, dealer, finder, investment adviser, lender, insurer, underwriter, rating agency, public finance approver, national company, Project SPV, provider, operator, or enterprise execution vehicle.
153.11 Publication Limit. A delegation involving publication shall state or incorporate publication limits, including permitted publication types, public-safe review requirements, evidence review requirements, methods review requirements, research integrity review requirements, data / AI / cyber review requirements, privacy review requirements, safeguards review requirements, public authority reference review requirements, finance-boundary review requirements, certification-boundary review requirements, procurement-neutrality review requirements, controlled vocabulary requirements, non-reliance language requirements, correction pathway, and approval authority.
Publication delegation may apply to public reports, whitepapers, technical baselines, datasets, dashboards, maps, software documentation, API documentation, repository notices, public-safe summaries, Academy materials, training materials, grant reports, sponsorship acknowledgments, public authority learning materials, controlled-room summaries, correction notices, supersession notices, withdrawal notices, takedown notices, and archive notices.
No publication delegation shall authorize public warnings, emergency commands, public authority decisions, finance-readiness determinations, insurance-readiness determinations, ratings, investment advice, securities solicitation, procurement recommendations, certification, accreditation, recognition, provider preference, sponsor endorsement, or professional advice unless a separate competent authority lawfully exists and the record expressly supports the status.
153.12 Data Access Limit. A delegation involving data access shall state or incorporate data-access limits, including data class, permitted users, permitted purpose, permitted environment, permitted retention, permitted export, permitted sharing, permitted analysis, permitted publication, data minimization, access logging, revocation triggers, privacy requirements, public authority confidentiality requirements, health-sensitive data requirements, cyber-sensitive data requirements, infrastructure-sensitive data requirements, community-protected data requirements, Tribal and Indigenous data requirements, protected knowledge restrictions, cross-border transfer restrictions, and deletion or archive requirements.
Data access delegation shall follow least privilege, need-to-know, purpose limitation, access logging, identity verification, and revocability. Access to a dataset, data room, dashboard, repository, model register, inference record, compute workload record, observability feed, public authority data contribution, protected knowledge record, or controlled material shall not create authority to use, disclose, publish, export, train on, fine-tune, embed, commercialize, combine, re-identify, sell, transfer, or rely on such material beyond the delegation.
Where data-access ambiguity exists, access shall be held, narrowed, suspended, or routed for review pending clarification. No urgency, public authority interest, sponsor interest, provider interest, research interest, publication deadline, technical convenience, or system configuration shall override data-access limits.
153.13 AI-Use Limit. A delegation involving AI use shall state or incorporate AI-use limits, including permitted AI systems, prohibited AI systems, approved use cases, prohibited use cases, input restrictions, output restrictions, human review requirements, model register requirements, inference record requirements, prompt and output logging where required, training and fine-tuning restrictions, embedding and retrieval restrictions, agentic AI restrictions, confidential information restrictions, public authority material restrictions, protected knowledge restrictions, personal information restrictions, cyber-sensitive restrictions, infrastructure-sensitive restrictions, public-safe publication requirements, and correction requirements.
AI-use delegation shall not authorize:
a) uploading restricted Board materials, privileged materials, public authority confidential materials, protected knowledge, personal information, health-sensitive information, cyber-sensitive information, infrastructure-sensitive information, sponsor confidential information, provider confidential information, or controlled-room materials into unapproved AI systems;
b) treating model output as institutional truth without human review and record support;
c) allowing agentic AI systems to make binding governance, finance, public authority, publication, access, contracting, employment, safeguarding, or technical release decisions without competent human authorization;
d) using AI outputs as public warnings, emergency commands, certification, recognition, finance-readiness, procurement approval, ratings, or public authority decisions;
e) using AI systems in a manner that violates privacy, IP, licensing, confidentiality, civil rights, accessibility, competition, sanctions, export-control, controlled-technology, or protected knowledge rules; or
f) bypassing human accountability through automation.
AI-use authority shall be reviewable, logged where required, limited to approved systems, and subject to immediate suspension where misuse, hallucination risk, model drift, data leakage, bias, security risk, public authority confusion, finance overclaim, certification overclaim, safeguards harm, or correction failure is identified.
153.14 Cybersecurity Limit. A delegation involving cybersecurity, identity, access, credentials, keys, tokens, secure release, repository permissions, cloud environments, compute environments, controlled rooms, dashboards, data rooms, monitoring systems, incident response, vulnerability handling, backup, disaster recovery, or business continuity shall state or incorporate cybersecurity limits. Such limits shall include role, system, environment, access level, credential authority, logging requirements, approval requirements, segregation of duties, emergency authority, incident escalation, revocation rule, and records requirements.
Cybersecurity delegation may authorize defined technical actions necessary to protect systems and records, including access suspension, credential rotation, key revocation, repository lock, release hold, network restriction, no-download lock, controlled-room lockdown, incident preservation, forensic preservation, backup restoration, vulnerability remediation, and communication of security notices, only within lawful authority and approved incident procedures.
Cybersecurity delegation shall not authorize concealment of incidents, destruction of evidence, alteration of records, unauthorized surveillance, unlawful access, public authority impersonation, retaliation against reporters, publication of sensitive vulnerabilities without review, or bypass of legal, privacy, civil rights, public authority, protected knowledge, export-control, sanctions, or controlled-technology requirements.
153.15 Public Authority Interface Limit. A delegation involving public authority interfaces shall state or incorporate public authority limits, including capacity classification, official-capacity rules, observer rules, regulator-listening rules, public finance reader rules, emergency-management participant rules, public infrastructure operator rules, public authority data contribution rules, public authority reference review, public records and open meetings considerations where applicable, lobbying and government ethics review where applicable, gift rules, procurement integrity rules, grant compliance rules, confidentiality requirements, and public-safe language requirements.
Public authority interface delegation may authorize scheduling, meeting support, learning support, technical literacy support, evidence presentation, methods explanation, controlled-room administration, data contribution routing, public-safe reporting support, scenario support, simulation support, tabletop support, after-action learning support, and capacity classification support. It shall not authorize GCRI US to act as a public authority, accept public authority delegation, issue public warnings, command emergency response, make regulatory decisions, approve permits, approve procurement, approve funding, approve public finance, bind a sovereign body, create public-private partnership obligations, or imply official adoption by participation.
Where a public authority requests or appears to expect action outside the Corporation’s boundary, the delegate shall stop, clarify capacity, apply limitation language, route to the responsible officer or counsel, and preserve records.
153.16 Finance Boundary Limit. A delegation involving finance-adjacent matters shall state or incorporate finance-boundary limits, including securities, investment adviser, broker-dealer, finder, banking, lending, guarantee, insurance, underwriting, rating, public finance, tax credit, capital-reader, finance-readiness, insurance-readiness, proof-pack, bankability, investability, capital-readability, and regulated-perimeter controls.
A finance-boundary delegation may authorize internal budgeting, treasury administration, grant administration, donation administration, sponsorship administration, restricted fund administration, cost-recovery administration, public-safe financial reporting, and GRA-facing technical evidence input routing where permitted. It shall not authorize securities offerings, investment solicitation, broker-dealer activity, finder activity, investment advice, capital placement, lending, credit approval, guarantees, insurance placement, underwriting, rating, public finance approval, tax-credit approval, capital-reader execution, Project SPV financing solicitation, national company financing solicitation, investor matching, or finance-readiness determination.
Where finance-adjacent language appears in a delegated activity, the delegate shall use controlled vocabulary, limitation language, non-reliance language, GRA role-separation language where applicable, and escalation to legal or compliance where ambiguity exists.
153.17 Certification and Procurement Boundary Limit. A delegation involving certification-adjacent, procurement-adjacent, recognition-adjacent, conformance-adjacent, maturity-adjacent, Docket-adjacent, Grid-adjacent, Nexus-compatible, provider-related, sponsor-related, public authority-related, or technical baseline-related matters shall state or incorporate certification and procurement boundary limits.
No delegation shall authorize the delegate to certify, accredit, recognize, approve compliance, approve procurement, select vendors for public authorities, confer provider preference, confer sponsor entitlement, determine maturity standing, determine GRF recognition, determine Nexus-compatible status, approve Docket standing, guarantee Grid standing, issue badges with status meaning, or treat a technical baseline, software release, proof receipt, dashboard, data room, controlled room, or ledger entry as conformance approval unless a separate competent body has been lawfully created and the delegation expressly identifies the authority.
Procurement support for the Corporation’s own operations shall remain distinct from public procurement. Provider participation shall remain distinct from provider preference. Technical compatibility shall remain distinct from certification. Evidence input shall remain distinct from recognition. Technical baseline stewardship shall remain distinct from protocol authority unless separately and lawfully designated.
153.18 Research and Evidence Limit. A delegation involving research, evidence, methods, observability, ontology, technical truth, public-good R&D, peer review, model review, evidence review, red-team review, public-safe publication, technical baseline drafting, or public-good software documentation shall state or incorporate research and evidence limits. These limits shall include research integrity review, ethics review, human-subjects review where applicable, community review where applicable, Tribal and Indigenous protocol review where applicable, protected knowledge review where applicable, conflict review, sponsor independence review, data / AI / cyber review, public-safe publication review, version control, correction pathway, and evidence classification rules.
Research and evidence delegation may authorize collection, preparation, analysis, review, drafting, recommendation, publication routing, correction routing, or archive support. It shall not authorize a delegate to inflate research outputs into professional advice, public authority decisions, public warnings, emergency commands, finance-readiness determinations, ratings, certifications, recognition, procurement recommendations, provider endorsements, sponsor validations, or operational instructions.
Where evidence is provisional, disputed, stale, uncertain, confidence-limited, method-limited, source-limited, privacy-limited, protected-knowledge-limited, or public-safe-limited, the delegate shall preserve those limitations and shall not remove or soften them for convenience, sponsor preference, provider preference, public authority preference, media interest, grant pressure, publication timing, or institutional reputation.
153.19 Technical Asset and Repository Limit. A delegation involving technical assets or repositories shall state or incorporate limits for software, schemas, APIs, SDKs, dashboards, data tools, reference architectures, test harnesses, gold vectors, negative tests, evaluation sets, benchmark libraries, datasets, model cards, system cards, benchmark cards, technical profiles, open technical baselines, proof receipts, role keys, smart licenses, ledger entries, observability tools, AI-RAN tools, O-RAN tools, DePIN tools, DLT or blockchain reference materials, digital twin tools, cyber tools, geospatial tools, Earth observation tools, sensor tools, compute tools, and public-good repositories.
Technical asset and repository delegation may authorize development, review, commit, merge, release, rollback, deprecation, vulnerability fix, documentation, repository administration, access routing, license application, SBOM generation, artifact signing, provenance recording, dependency review, secure release, fork review, compatibility review, and archive support, only within approved authority.
Technical asset delegation shall not authorize certification, procurement approval, provider preference, public authority adoption, finance-readiness, recognition, emergency command, public warning, legal compliance approval, or operational control. Repository permission shall not equal corporate authority. Merge rights shall not equal publication authority. Release rights shall not equal certification authority. A proof receipt shall not equal recognition, finance-readiness, certification, procurement approval, or public authority adoption unless expressly and lawfully authorized by competent record.
153.20 Emergency Limit. A delegation involving emergency authority, break-glass authority, incident response, urgent hold, publication freeze, access restriction, repository lock, controlled-room lockdown, key revocation, credential rotation, system isolation, evidence preservation, public-safe correction, or urgent legal compliance shall state or incorporate emergency limits. Emergency delegation shall be time-limited, purpose-limited, reviewable, recorded, subject to notice, subject to ratification where required, subject to sunset, and subject to post-event review.
Emergency authority may be used to preserve the Corporation, protect records, prevent harm, preserve privilege, prevent data loss, protect cyber systems, prevent public authority confusion, prevent finance overclaim, prevent certification overclaim, prevent procurement overclaim, prevent recognition overclaim, prevent protected knowledge harm, prevent civil-rights harm, stop unauthorized publication, suspend unsafe access, or preserve evidence pending review.
Emergency authority shall not be used to exercise prohibited functions. No emergency delegation shall authorize securities solicitation, investment advice, broker-dealer activity, finder activity, lending, insurance, underwriting, rating, public finance approval, public procurement approval, certification, recognition, public warning, emergency command, public authority action, provider selection for public authorities, sponsor control, enterprise execution, suppression of lawful complaint, retaliation, concealment of misconduct, destruction of records, or permanent alteration of governance without competent approval.
153.21 Revocability. Every delegation shall be revocable unless applicable law, a lawful contract, or the terms of a competent instrument require otherwise. The Board may revoke, suspend, narrow, condition, replace, or supersede any delegation within its authority. An officer may revoke, suspend, narrow, condition, replace, or supersede an officer-level delegation within the officer’s authority. Revocation may be immediate where necessary to protect the Corporation, records, public-benefit purpose, nonprofit character, tax status, public authority boundaries, finance boundaries, data / AI / cyber controls, safeguards, protected knowledge, public-safe publication, or Nexus role separation.
Revocation or suspension shall be considered where there is:
a) breach of law, Articles, Bylaw, policy, delegation, contract, or duty;
b) unmanaged conflict;
c) loss of eligibility;
d) misuse of authority;
e) public authority overclaim;
f) finance overclaim;
g) certification or procurement overclaim;
h) recognition or provider-preference overclaim;
i) sponsor or donor control risk;
j) data misuse;
k) AI misuse;
l) cyber incident;
m) protected knowledge breach;
n) research misconduct;
o) records defect;
p) confidentiality breach;
q) competition concern;
r) sanctions or export-control concern; or
s) any other material risk.
Upon revocation, the delegate shall cease acting, return or transfer records, support handover, surrender or lose access, correct public or internal references where needed, and cooperate with review, correction, archive, or investigation.
153.22 No Delegation of Reserved Matters Unless Lawfully and Expressly Authorized. No Board reserved matter shall be delegated unless applicable law, the Articles or Certificate, this Bylaw, and the Board expressly permit such delegation, and the delegation is recorded with sufficient specificity. Reserved matters include, without limitation, amendment of this Bylaw, amendment of the Articles or Certificate, changes to legal name or legal form, major changes to tax status, mission lock changes, non-execution changes, public-benefit purpose changes, major budgets, major contracts, major support arrangements, creation or dissolution of major committees or programs, major policies, material public authority protocols, material data / AI / cyber policies, material safeguards policies, litigation or settlement of material significance, dissolution, merger, conversion, sale of substantially all assets, and any other matter reserved by law, the Articles or Certificate, this Bylaw, Board resolution, member approval requirement, or policy.
A delegation touching a reserved matter shall be interpreted as authority to prepare, study, recommend, route, administer, or implement after approval only, unless the delegation expressly states lawful decision authority. No committee recommendation, officer approval, Secretariat record, counsel memo, public authority request, sponsor request, provider request, grant deadline, event deadline, technical urgency, repository status, AI summary, or workflow label shall substitute for required Board action.
153.23 No Delegation of Prohibited Functions. No delegation may authorize any person, office, committee, council, panel, working group, Secretariat, Central Bureau, program, controlled room, repository, technical asset, AI system, dashboard, proof receipt, ledger entry, or Nexus interface to perform a prohibited function. Prohibited functions include, without limitation, acting as a regulator, public authority, public warning body, emergency command body, public procurement authority, certification body, recognition body, finance-readiness authority, broker, dealer, finder, investment adviser, lender, insurer, underwriter, rating agency, public finance approver, fund, market operator, national company, Project SPV, provider, operator, deployment company, infrastructure owner, or enterprise execution vehicle, except where a separate legal entity or competent authority lawfully performs its own role outside GCRI US and without converting GCRI US into that actor.
No delegation may authorize:
a) securities offering, solicitation, brokerage, dealer activity, finder activity, investment advice, capital placement, lending, insurance placement, underwriting, rating, public finance approval, or guarantee;
b) public warning, evacuation instruction, incident command, emergency dispatch, public health order, or safety command;
c) regulation, enforcement, permit issuance, compliance approval, procurement award, vendor selection for public authorities, or governmental decision;
d) certification, accreditation, recognition, maturity standing, Docket approval, Grid guarantee, finance-readiness, insurance-readiness, bankability, investability, capital-readability, or Nexus-compatible status unless separately and lawfully authorized by competent authority;
e) sponsor control, donor control, funder control, host control, provider preference, outcome purchase, research finding purchase, publication veto, protected knowledge extraction, or private inurement;
f) unauthorized data access, AI use, cyber action, public authority data use, protected knowledge use, or public-safe publication; or
g) any act inconsistent with public-benefit purpose, nonprofit character, role separation, validity-by-record, or correctionability.
Any attempted delegation of a prohibited function shall be void, voidable, suspended, or non-operative to the fullest extent lawful and shall be escalated for correction, public or controlled clarification where needed, and enforcement.
153.24 Delegation Records. The Corporation shall maintain Delegation Records sufficient to demonstrate the source, scope, duration, conditions, limits, use, review, amendment, suspension, revocation, expiration, ratification, correction, supersession, archive, and enforcement of delegated authority. Delegation Records shall be maintained in the official repository or other approved controlled repository and shall be linked, where appropriate, to the officer register, director register, committee register, authority matrix, delegation matrix, policy register, contract register, budget records, public authority capacity records, data access records, AI-use records, cyber access records, publication records, controlled-room records, technical asset records, support records, correction records, and Board resolution register.
Delegation Records shall include, as applicable:
a) delegating authority;
b) delegate identity;
c) role and office;
d) appointment or engagement record;
e) scope of authority;
f) excluded authority;
g) effective date;
h) expiration date;
i) renewal or review cycle;
j) budget limit;
k) contract limit;
l) signature limit;
m) publication limit;
n) data-access limit;
o) AI-use limit;
p) cybersecurity limit;
q) public authority interface limit;
r) finance-boundary limit;
s) certification and procurement boundary limit;
t) research and evidence limit;
u) technical asset and repository limit;
v) emergency limit;
w) conditions and required reviews;
x) reporting obligations;
y) conflict disclosures;
z) recusals and access restrictions;
aa) actions taken under delegation;
bb) decisions made under delegation;
cc) contracts signed under delegation;
dd) expenditures approved under delegation;
ee) publications approved under delegation;
ff) data access approved under delegation;
gg) AI use approved under delegation;
hh) repository access approved under delegation;
ii) controlled-room access approved under delegation;
jj) incidents escalated under delegation;
kk) corrections made under delegation;
ll) challenges, defects, exceptions, refusals, holds, restrictions, suspensions, revocations, expirations, ratifications where lawful, supersessions, withdrawals, and archive records;
mm) training and certification of understanding;
nn) access revocation and handover records; and
oo) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that delegation is a controlled method for transmitting limited authority, not a method for creating unbounded power. Delegated authority shall be lawful, written, specific, narrow, time-bounded or reviewable, records-supported, revocable, public-safe where relevant, non-executing, role-separated, escalation-ready, and correctionable. No delegation shall override law, the Articles or Certificate, this Bylaw, Board reserved powers, public-benefit purpose, nonprofit character, tax-exempt or tax-exempt-compatible restrictions, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, protected knowledge restrictions, validity-by-record, or correctionability.
Section 154. Authority Matrix, Signature Authority, Spending Authority, Contracting Authority, Publication Authority, Data Access Authority, AI-Use Authority, and Controlled-Room Authority
154.1 Authority Matrix Purpose. The Corporation shall maintain an Authority Matrix, or one or more equivalent authority-control instruments, to classify, assign, limit, record, review, suspend, revoke, supersede, and audit institutional authority for governance, management, finance, contracting, signatures, publications, public statements, data access, AI use, model approval, repository access, software release, technical asset release, controlled-room admission, public authority references, incident response, corrections, support acceptance, and other authority-bearing acts of the Corporation.
The Authority Matrix exists to make institutional power visible, bounded, lawful, accountable, and correctionable. It shall identify who may act, in what capacity, for what purpose, under what legal source, within what threshold, subject to what conditions, with what required reviews, with what records, and with what escalation duties. It shall prevent title-based authority inflation, informal authority drift, program-specific overreach, sponsor-specific exceptions, provider-specific exceptions, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, public-safe publication defects, data / AI / cyber misuse, protected knowledge exposure, and unrecorded departures from the Corporation’s non-execution perimeter.
The Authority Matrix shall be subordinate to applicable law, the Articles or Certificate, this Bylaw, Board reserved powers, member approval rights where applicable, Board resolutions, fiduciary duties, public-benefit purpose, nonprofit and non-distribution character, tax-exempt or tax-exempt-compatible restrictions, approved budget, policies, delegations, public authority boundary controls, finance-boundary controls, certification-boundary controls, procurement-neutrality controls, provider-neutrality controls, sponsor non-control controls, data / AI / cyber controls, privacy controls, research integrity controls, community safeguards, protected knowledge restrictions, validity-by-record, and correctionability.
No person may rely on the Authority Matrix to exercise a prohibited function. No entry, role label, approval cell, workflow status, repository permission, dashboard permission, signature block, AI-system role, controlled-room role, case ID, proof receipt, public authority contact, sponsor relationship, provider relationship, technical centrality, or historical practice shall create authority beyond the lawful meaning of the controlling record.
154.2 Signature Authority. The Corporation shall establish signature authority for instruments that may bind, evidence, acknowledge, notice, certify, approve, submit, accept, amend, renew, terminate, supersede, withdraw, or otherwise affect the Corporation’s legal, governance, financial, operational, technical, public-facing, or Nexus-compatible position. Signature authority shall be conferred only by law, the Articles or Certificate, this Bylaw, Board resolution, officer appointment, delegation, authority matrix, contract instrument, policy, or other competent record.
Signature authority may apply to:
a) corporate filings, annual reports, state qualification filings, charitable solicitation filings, tax filings, grant filings, public authority filings, and other regulatory or administrative submissions;
b) contracts, amendments, statements of work, purchase orders, licenses, contributor agreements, employment agreements, contractor agreements, vendor agreements, data-processing agreements, confidentiality agreements, public authority MoUs, university agreements, laboratory agreements, host agreements, sponsorship agreements, donation agreements, grant agreements, in-kind contribution agreements, and restricted fund instruments;
c) Board certifications, Secretary certificates, officer certificates, repository certifications, adoption certificates, incumbency certificates, records certifications, and public-safe notices;
d) publications, public statements, correction notices, withdrawal notices, takedown notices, supersession notices, archive notices, repository notices, and gazette entries; and
e) controlled-room terms, access approvals, data access approvals, AI-use approvals, repository access approvals, software release approvals, technical asset release approvals, and incident-response notices where signature or recorded approval is required.
A signature shall be valid only if the signatory has authority for the specific instrument, capacity, subject matter, amount, term, jurisdiction, risk class, access class, publication class, and approval pathway. Signature authority shall not include authority to approve substance unless the signatory also has substantive approval authority. Signature by an authorized person shall not cure missing Board approval, missing member approval where required, missing legal review, missing tax review, missing data / AI / cyber review, missing safeguards review, missing conflict review, missing public authority review, missing finance-boundary review, missing certification-boundary review, or other required review.
Electronic signatures, digital signatures, repository approvals, workflow approvals, key-based approvals, smart-document approvals, and machine-readable approvals may be used where lawful and approved, provided that identity, authority, version, timestamp, integrity, access control, audit trail, and retention requirements are satisfied. No shared credential, generic account, unmanaged key, unsigned email, informal message, AI-generated approval, unchecked workflow state, or auto-filled signature block shall substitute for authorized signature.
154.3 Banking Authority. The Corporation shall establish banking authority for opening, maintaining, closing, accessing, administering, reconciling, approving, moving, safeguarding, and reporting funds held in bank accounts, payment accounts, investment accounts permitted by law and policy, merchant accounts, grant accounts, restricted fund accounts, reserve accounts, escrow-like accounts used only for the Corporation’s own lawful purposes where permitted, and other treasury or payment systems approved by the Board or competent authority.
Banking authority shall be structured to preserve segregation of duties, dual control where appropriate, reconciliation discipline, restricted fund tracking, fraud prevention, cyber resilience, donor and sponsor support-without-control, grant compliance, nonprofit character, tax-exempt or tax-exempt-compatible status, and public-benefit purpose. Banking authority may include authority to initiate payments, approve payments, release payments, reconcile accounts, view balances, administer user roles, approve wire transfers, approve ACH payments, approve card payments, approve refunds, accept grants or donations, deposit checks, manage merchant services, and maintain treasury records, only within approved limits.
No banking authority shall authorize:
a) use of funds for private inurement, impermissible private benefit, political or lobbying activity outside permitted limits, prohibited execution, unlawful purposes, or purposes inconsistent with restrictions;
b) third-party fund custody, payment intermediation, clearing, settlement, escrow, treasury execution for others, deposit-taking, money transmission, banking activity, lending activity, investment management, or capital execution;
c) movement of restricted funds outside their approved purpose;
d) support-for-control, support-for-outcome, support-for-recognition, support-for-finance-readiness, support-for-certification, support-for-procurement, support-for-public-authority-access, or support-for-provider-preference arrangements;
e) payments to sanctioned persons, restricted parties, prohibited jurisdictions, controlled-technology transactions, or unlawful counterparties; or
f) circumvention of budget limits, procurement controls, conflict controls, or approval thresholds.
Banking authority shall be reviewed periodically and immediately upon officer change, staff change, contractor change, suspected compromise, conflict, resignation, removal, suspension, role change, incident, or loss of good standing. Access shall be revoked promptly when authority ends.
154.4 Spending Authority. The Corporation shall establish spending authority for expenditures, reimbursements, procurement, subscriptions, software tools, cloud services, compute resources, AI tools, cybersecurity tools, professional services, contractor services, employment costs, fellowships, stipends, scholarships, awards, grants made by the Corporation where lawful, events, travel, facilities, insurance, taxes, filings, public-safe publications, technical assets, controlled rooms, repository systems, and other mission-related costs.
Spending authority shall be tied to approved budget, lawful purpose, fund availability, restricted fund limitations, Board approvals, officer delegations, procurement controls, conflict controls, sanctions controls, export-control controls, controlled-technology controls, cybersecurity controls, data / AI / privacy controls, safeguards controls, and records requirements. Spending authority may be classified by amount, budget line, fund, program, project, vendor, category, frequency, term, emergency status, and required approvals.
No person may split purchases, stage transactions, misclassify expenses, use personal accounts, route expenses through related parties, use sponsor or provider channels, accept undisclosed in-kind substitution, create off-book obligations, or use emergency language to avoid spending controls. Expense approval shall not be self-approved where conflict or self-benefit exists. Reimbursement shall require documentation, public-benefit purpose, reasonableness, and approval by a person other than the payee where required.
Spending authority shall not include authority to procure regulated financial services, execute investment transactions, lend, guarantee, insure, underwrite, rate, approve public finance, select providers for public authorities, certify vendors, recognize projects, confer finance-readiness, or operate enterprise delivery activities. All spending shall remain bounded by the Corporation’s public-benefit, nonprofit, non-executing, role-separated character.
154.5 Procurement Authority. The Corporation may establish procurement authority for its own internal purchases, vendor engagements, contractor engagements, technology subscriptions, professional services, equipment, facilities, software, cloud, compute, AI tools, cybersecurity services, data services, event services, travel services, accessibility services, translation services, publication services, and operational support. Procurement authority shall be internal administrative authority only and shall not be represented as public procurement authority, public vendor selection authority, public contract award authority, provider certification, provider recognition, provider preference, or public authority endorsement.
Procurement authority shall be exercised in a manner that promotes reasonableness, mission fit, conflict control, value, competition where appropriate, vendor neutrality, sponsor non-control, data protection, cybersecurity, privacy, AI governance, export-control compliance, sanctions compliance, controlled-technology discipline, accessibility, civil rights, and safeguards. Procurement authority may require quotes, comparative review, sole-source justification, conflict disclosure, related-party review, vendor diligence, security review, data-processing review, insurance review, IP review, tax review, and contract review.
No procurement authority shall authorize:
a) steering public authorities to vendors;
b) recommending vendors as certified, approved, preferred, finance-ready, Nexus-compatible, or public authority-ready;
c) allowing sponsors or providers to control vendor selection;
d) accepting vendor discounts, credits, or in-kind support that compromises neutrality or creates improper private benefit;
e) procuring tools or services that violate data / AI / cyber, protected knowledge, export-control, sanctions, or controlled-technology rules; or
f) treating internal procurement results as public standards, market rankings, public procurement recommendations, or provider legitimacy determinations.
Where a vendor, provider, sponsor, host, or enterprise actor also participates in research, controlled rooms, public authority learning, technical baselines, public-good software, Nexus interfaces, GRF-facing inputs, or GRA-facing technical inputs, the procurement authority shall require role classification, conflict management, public-safe claim controls, and provider-neutral records.
154.6 Contracting Authority. The Corporation shall establish contracting authority for agreements, amendments, renewals, extensions, terminations, statements of work, purchase orders, order forms, licenses, contributor instruments, data-processing agreements, confidentiality instruments, employment and contractor instruments, public authority MoUs, university agreements, laboratory agreements, host agreements, community interface agreements, Tribal or Indigenous protocol instruments where appropriate, sponsorship agreements, donation agreements, grant agreements, in-kind contribution agreements, restricted fund instruments, software licenses, repository terms, controlled-room terms, and other binding instruments.
Contracting authority shall identify who may negotiate, approve business terms, approve legal terms, sign, amend, renew, terminate, waive, enforce, or close out contracts. Authority to negotiate shall not include authority to approve. Authority to prepare shall not include authority to sign. Authority to sign shall not include authority to waive Board approval, counsel review, tax review, data / AI / cyber review, public authority review, finance-boundary review, safeguards review, conflict review, or other required control.
Contracts shall be reviewed for, as applicable:
a) lawful purpose;
b) authority and capacity;
c) budget and funding source;
d) restricted fund compliance;
e) private benefit and inurement;
f) IP, licensing, data rights, confidentiality, publication rights, attribution, and moral rights;
g) privacy, cybersecurity, AI use, data processing, model use, repository access, and secure development;
h) export-control, sanctions, controlled technology, national security sensitivity, and cross-border issues;
i) competition, antitrust, procurement integrity, gifts, government ethics, lobbying, and grant compliance;
j) public authority boundary, finance boundary, certification boundary, recognition boundary, procurement-neutrality, provider-neutrality, and sponsor non-control;
k) civil rights, accessibility, community safeguards, Tribal and Indigenous protocols, protected knowledge, public-safe mapping, grievance, remedy, non-retaliation, and do-no-harm controls; and
l) termination, suspension, audit, reporting, correction, supersession, withdrawal, takedown, archive, return, deletion, and dispute provisions.
No contract shall convert the Corporation into a regulator, public authority, public warning body, emergency command body, public procurement authority, certification body, recognition body, finance-readiness authority, broker, dealer, finder, investment adviser, lender, insurer, underwriter, rating agency, public finance approver, national company, Project SPV, provider, operator, asset owner, or enterprise execution vehicle.
154.7 Grant Agreement Authority. The Corporation shall establish grant agreement authority for the application, negotiation, acceptance, amendment, reporting, renewal, closeout, refusal, return, restriction, or termination of grants received by the Corporation and grants made by the Corporation where lawful and approved. Grant agreement authority shall be exercised only within applicable law, governing instruments, Board approvals, budget authority, tax-exempt or tax-exempt-compatible controls, restricted fund controls, public-benefit purpose, grant compliance obligations, and records requirements.
Grant agreement authority may include authority to approve proposal submission, approve budget narratives, approve institutional representations, accept grant awards, sign grant agreements, submit grant reports, approve drawdowns, approve cost-share records, approve restricted fund uses, approve grant modifications, and approve grant closeout, only where expressly delegated.
Grant agreements shall not promise or imply prohibited functions. No grant agreement shall require the Corporation to issue public warnings, command emergency response, act as public authority, regulate, certify, recognize, approve procurement, determine finance-readiness, provide investment advice, solicit capital, rate projects, select providers for public authorities, suppress adverse findings, alter evidence, waive correctionability, disclose protected knowledge improperly, weaken data / AI / cyber controls, or allow funder control of research conclusions or public-safe publication.
Where a grant includes public authority conditions, public records obligations, open meetings implications, lobbying restrictions, procurement restrictions, data-sharing requirements, publication requirements, IP requirements, human-subjects requirements, research ethics requirements, export-control requirements, cybersecurity requirements, or cross-border requirements, grant agreement authority shall require legal, compliance, finance, program, data / AI / cyber, safeguards, and Board review where appropriate.
154.8 Donation Agreement Authority. The Corporation shall establish donation agreement authority for the acceptance, documentation, restriction, acknowledgment, receipting review, amendment, return, refusal, termination, and closeout of donations. Donation agreement authority shall be exercised consistently with nonprofit character, public-benefit purpose, tax classification, charitable solicitation law where applicable, donor restriction rules, private benefit controls, anti-capture controls, sponsor non-control, public-safe acknowledgment rules, and records requirements.
Donation agreement authority may include authority to accept unrestricted gifts, restricted gifts, mission-restricted gifts, program support, challenge support, fellowship support, Academy support, technical baseline support, public-good software support, safeguards support, accessibility support, community participation support, or other lawful support, only within approved thresholds and acceptance criteria.
A donation shall not be accepted where it would require or materially pressure the Corporation to provide governance control, research control, publication control, public authority access, provider preference, recognition, certification, procurement advantage, finance-readiness, insurance-readiness, rating, investment access, controlled-room access beyond approved criteria, protected knowledge access, or outcome purchase. Donation language shall distinguish gifts from sponsorships, grants, fees, subscriptions, service payments, cost recovery, and contracts.
Donation agreement authority shall not authorize tax representations beyond lawful receipting authority and approved language. No donor shall be promised tax deductibility unless the Corporation’s tax status and applicable law support such statement and the record authorizes it.
154.9 Sponsorship Agreement Authority. The Corporation shall establish sponsorship agreement authority for the negotiation, acceptance, amendment, benefit scheduling, acknowledgment, monitoring, restriction, termination, refusal, return, and closeout of sponsorships. Sponsorship agreement authority shall be subject to Board approval where material, tax and nonprofit review, private benefit review, public acknowledgment controls, sponsor non-control rules, provider-neutrality rules, public authority boundary rules, finance-boundary rules, certification-boundary rules, procurement-neutrality rules, competition controls, safeguards controls, and public-safe claim requirements.
Sponsorship agreements may authorize only lawful, approved, and bounded benefits, such as public acknowledgment, limited logo use, event recognition, participation opportunities, approved learning access, approved briefings, and other support benefits that do not confer control or status. Each sponsorship agreement shall classify benefits, restrictions, acknowledgment language, logo use, sponsor role, non-control language, termination rights, public-safe limitations, and correction rights.
No sponsorship agreement shall provide:
a) governance control;
b) Board, committee, council, working group, panel, room, publication, research, evidence, methods, technical baseline, software release, or controlled vocabulary veto;
c) public authority access purchase;
d) provider preference;
e) procurement advantage;
f) certification, accreditation, recognition, maturity standing, Docket standing, Grid standing, or Nexus-compatible status;
g) finance-readiness, insurance-readiness, bankability, investability, rating, or capital-readability;
h) publication outcome, research finding, evidence conclusion, dashboard placement, map treatment, software feature inclusion, or technical baseline inclusion;
i) suppression, delay, softening, withdrawal, takedown avoidance, or correction avoidance; or
j) access to protected knowledge or controlled materials beyond approved independent criteria.
Sponsorship agreement authority shall include power to stop, restrict, re-scope, terminate, return, correct, or publicly clarify sponsorships where sponsor conduct or claims threaten the Corporation’s mission, independence, neutrality, tax status, public-safe claims discipline, or Nexus role separation.
154.10 In-Kind Contribution Agreement Authority. The Corporation shall establish in-kind contribution agreement authority for equipment, software licenses, cloud credits, compute credits, AI tools, cybersecurity tools, datasets, technical services, professional services, meeting space, event space, staff time, research support, accessibility support, translation support, communications support, travel support, facilities, lab access, or other non-cash support. Such authority shall be exercised only after review of ownership, valuation, title, license terms, restrictions, IP rights, data rights, cybersecurity, AI use, privacy, export control, sanctions, controlled technology, conflicts, private benefit, sponsor control, provider neutrality, operational dependency, return, deletion, discontinuation, and closeout.
In-kind contribution authority shall not permit the Corporation to accept support that creates hidden control, technical lock-in, provider preference, sponsor control, data capture, model training capture, protected knowledge exposure, cyber dependency, operational dependency, public authority confusion, procurement advantage, certification implication, recognition implication, finance-readiness implication, or improper private benefit.
Any in-kind contribution used in public-good software, technical baselines, observability methods, data rooms, controlled rooms, public authority learning, repositories, dashboards, AI systems, cyber systems, or public-safe publications shall be recorded with sufficient detail to disclose material dependencies, limitations, restrictions, contribution source, sponsor or provider role, licensing terms, security conditions, and correction or removal pathway.
No in-kind contribution shall be described as neutral, open, public-good, unrestricted, sovereign, independent, verified, validated, certified, or Nexus-compatible unless the record supports that language under controlled vocabulary and public-safe claim rules.
154.11 Employment and Contractor Engagement Authority. The Corporation shall establish authority for the hiring, appointment, engagement, classification, compensation, supervision, discipline, suspension, termination, offboarding, and records handling of employees, contractors, consultants, fellows, advisors, volunteers, seconded personnel, interns, technical contributors, repository maintainers, and other persons performing work for or with the Corporation.
Employment and contractor engagement authority shall include controls for role description, classification, compensation, benefits, tax withholding or reporting, employment eligibility, background or integrity review where appropriate, conflict disclosure, confidentiality, IP and work product, data / AI / cyber access, repository access, controlled-room access, public authority contact, protected knowledge, civil rights, accessibility, harassment, retaliation, workplace safety, sanctions, export-control, controlled technology, and offboarding.
No employment or contractor engagement shall create authority to bind the Corporation unless separately delegated. No person shall obtain fiduciary authority, officer authority, public authority interface authority, finance-adjacent authority, publication authority, data access authority, AI-use authority, repository release authority, controlled-room admission authority, or public statement authority merely by being hired, engaged, seconded, contracted, appointed as fellow, named as advisor, or given system access.
Contractor and consultant authority shall be especially bounded. Contractors may support work; they may not exercise reserved governance, approve public-safe outputs, certify technical assets, determine evidence status, recognize projects, determine finance-readiness, control public authority interfaces, or speak for the Corporation unless expressly authorized by record.
154.12 Publication Authority. The Corporation shall establish publication authority for public reports, public-safe reports, whitepapers, technical baselines, public-good software documentation, datasets, dashboards, maps, APIs, SDKs, schemas, benchmark materials, model cards, system cards, benchmark cards, evidence packs, methods documents, ontology artifacts, Academy materials, training materials, public authority learning materials, public statements, press materials, website materials, social media, grant reports, sponsor acknowledgments, correction notices, supersession notices, withdrawal notices, retraction notices, takedown notices, archive notices, repository notices, and gazette entries.
Publication authority shall require appropriate review for:
a) legal authority;
b) evidence integrity;
c) methods integrity;
d) research integrity;
e) source lineage;
f) confidence and uncertainty;
g) public-safe language;
h) controlled vocabulary;
i) non-reliance language;
j) public authority boundary;
k) finance boundary;
l) certification and procurement boundary;
m) provider-neutrality and sponsor non-control;
n) data protection, privacy, AI governance, cyber sensitivity, infrastructure sensitivity, health sensitivity, and cross-border restrictions;
o) civil rights, accessibility, community safeguards, Tribal and Indigenous protocol, protected knowledge, and public-safe mapping;
p) IP, licensing, attribution, confidentiality, and third-party rights; and
q) correction, supersession, withdrawal, takedown, and archive pathways.
Publication authority shall not authorize professional advice, legal advice, engineering opinion by default, clinical or medical advice by default, public warning, emergency command, public authority decision, regulatory approval, procurement recommendation, certification, recognition, finance-readiness determination, rating, investment advice, securities solicitation, provider preference, sponsor endorsement, or enterprise execution instruction.
No draft, internal memo, AI summary, slide, fundraiser deck, website mockup, social media post, repository issue, working paper, technical note, committee recommendation, public authority meeting note, or sponsor material shall be treated as authorized publication unless approved through the applicable publication authority pathway.
154.13 Public Authority Reference Authority. The Corporation shall establish public authority reference authority for any use of the name, logo, title, office, agency, department, ministry, commission, regulator, public corporation, public finance entity, emergency management body, public health authority, utility, port, Tribal government, Indigenous government, state authority, territorial authority, federal authority, local authority, or public official in Corporation materials, records, rooms, publications, websites, press statements, grant materials, sponsorship materials, controlled-room materials, public authority learning materials, or Nexus interface materials.
Public authority reference authority shall require review of capacity, consent where required, source, accuracy, context, public records constraints, open meetings constraints, confidentiality, public authority data rules, procurement integrity, gifts, government ethics, lobbying, grant compliance, public-safe language, and non-endorsement language. Public authority participation shall be classified, as applicable, as official-capacity, observer, regulator-listening, public finance reader, emergency-management participant, public infrastructure operator, simulation participant, technical listener, data contributor, or other approved capacity.
No public authority reference shall imply endorsement, adoption, funding approval, public procurement approval, regulatory approval, public finance approval, sovereign obligation, public-private partnership, emergency command, public warning, certification, recognition, provider preference, or official status unless the competent public authority has lawfully taken such action and the Corporation’s record accurately states it.
Where public authority reference risk exists, the Corporation shall hold publication, obtain clarification, revise language, apply limitation notices, restrict circulation, withdraw materials, or issue correction.
154.14 Data Access Authority. The Corporation shall establish data access authority for datasets, data rooms, evidence rooms, clean rooms, public authority rooms, no-download rooms, dashboards, maps, APIs, repositories, model registers, inference records, compute workload records, observability feeds, sensor feeds, AI-RAN signals, O-RAN signals, DePIN records, DLT or blockchain reference records, digital twin artifacts, cyber telemetry, geospatial data, Earth observation data, public authority data contributions, rights-bearing data, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, community-protected data, Tribal and Indigenous data, local and territorial knowledge, protected knowledge, and confidential third-party data.
Data access authority shall be based on least privilege, purpose limitation, need-to-know, approved role, access class, data class, retention class, sharing restrictions, export restrictions, publication restrictions, AI-use restrictions, security controls, logging, monitoring, revocation, and correction. Data access shall be granted only by persons authorized to approve the relevant data class and use case.
Data access authority shall not authorize:
a) access outside the approved purpose;
b) downloading where no-download controls apply;
c) copying, scraping, re-identifying, combining, transferring, publishing, training, fine-tuning, embedding, commercializing, or redistributing data without authority;
d) use of public authority data outside the approved public authority capacity;
e) use of protected knowledge outside applicable consent, protocol, restriction, or safeguard;
f) bypass of privacy, AI, cyber, research ethics, human-subjects, civil rights, accessibility, export-control, sanctions, or controlled-technology controls; or
g) conversion of data access into ownership, certification, recognition, finance-readiness, public authority status, provider preference, or operational control.
Data access shall be revoked or suspended promptly upon expiration, role change, conflict, misuse, breach, incident, investigation, public authority request, safeguard concern, protected knowledge concern, or loss of good standing.
154.15 AI-Use Authority. The Corporation shall establish AI-use authority for any use of AI systems, model systems, automated analysis tools, agentic AI, retrieval systems, embedding systems, synthetic data systems, evaluation harnesses, decision-support tools, inference systems, model registries, prompt systems, compute-to-data systems, confidential computing systems, secure enclaves, sovereign compute environments, dashboards using AI, public-safe publication tools, observability tools, Truth Engine components, and verifiable intelligence methods.
AI-use authority shall identify approved systems, approved purposes, prohibited systems, prohibited purposes, input restrictions, output restrictions, human review requirements, logging requirements, model register requirements, inference record requirements, compute workload record requirements, evaluation requirements, bias and civil-rights review, privacy requirements, cybersecurity requirements, protected knowledge restrictions, public authority material restrictions, publication restrictions, and correction requirements.
No AI-use authority shall allow AI systems to serve as final authority for governance, legal, finance, public authority, research integrity, evidence classification, publication, certification, recognition, finance-readiness, procurement, access, hiring, termination, discipline, grievance, safeguards, protected knowledge, public warning, emergency command, or enterprise execution decisions. AI outputs may support human review only where the record preserves the model, prompt, input class, output, review, limitation, and correction pathway required for material use.
The Corporation shall prohibit unapproved AI uploads of Board materials, privileged materials, controlled-room materials, public authority confidential materials, personal information, health-sensitive information, cyber-sensitive information, infrastructure-sensitive information, sponsor confidential information, provider confidential information, research participant information, or protected knowledge. Where an AI-use incident occurs, the Corporation shall hold, isolate, investigate, mitigate, notify where required, correct, revoke access, and preserve records.
154.16 Model Approval Authority. The Corporation shall establish model approval authority for models, AI systems, evaluation harnesses, benchmark systems, inference systems, automated scoring systems, retrieval systems, classifiers, ranking systems, simulation models, digital twin models, risk models, resilience models, observability models, Truth Engine models, language models, vision models, geospatial models, cyber models, sensor-fusion models, AI-RAN or O-RAN signal interpretation models, DePIN or DLT validation models, and other model-based technical assets used by or for the Corporation.
Model approval authority shall not mean regulatory approval, certification, public authority approval, procurement approval, finance-readiness, rating, recognition, or operational authorization. It shall mean only that the model has been approved for a specified internal or public-good use case, under specified assumptions, limitations, controls, access classes, publication classes, review requirements, and correction pathways.
A model approval record shall identify, as applicable:
a) model name, version, owner, custodian, source, license, and repository location;
b) intended use and prohibited uses;
c) training, fine-tuning, retrieval, embedding, input, output, and inference restrictions;
d) dataset cards, model cards, system cards, benchmark cards, evaluation results, limitations, known failure modes, bias review, civil-rights review, accessibility review, and safeguards review;
e) privacy, cybersecurity, protected knowledge, public authority, export-control, sanctions, controlled-technology, and cross-border controls;
f) human review requirements;
g) logging, monitoring, drift review, incident review, and retirement triggers; and
h) correction, supersession, withdrawal, rollback, takedown, archive, and public-safe notice pathways.
No model shall be deployed in a material public-facing, public authority-facing, finance-adjacent, certification-adjacent, safeguards-sensitive, protected-knowledge-sensitive, or rights-bearing context without approved model authority, human review, and records.
154.17 Repository Access Authority. The Corporation shall establish repository access authority for official repositories, controlled repositories, public repositories, internal repositories, legal repositories, Board repositories, evidence repositories, methods repositories, observability repositories, ontology repositories, public-good software repositories, technical baseline repositories, dataset repositories, model repositories, secure-release repositories, controlled-room repositories, grant repositories, sponsorship repositories, participant repositories, archive repositories, and any other record or technical repository.
Repository access authority shall classify access by role, purpose, repository, collection, branch, folder, dataset, system, environment, permission level, read access, write access, admin access, merge access, release access, issue access, secret access, key access, credential access, audit access, and archive access. Repository access shall follow least privilege, need-to-know, segregation of duties, logging, review, and revocation.
Repository access shall not be confused with substantive authority. Read access shall not create reliance rights. Write access shall not create approval authority. Merge access shall not create publication authority. Admin access shall not create governance authority. Release access shall not create certification authority. Issue management shall not create decision authority. Repository labels shall not create legal status unless supported by competent record.
Repository access shall be suspended or revoked upon role change, termination, conflict, misuse, cyber risk, data risk, protected knowledge risk, public authority risk, export-control risk, sanctions risk, controlled-technology risk, or loss of good standing. Repository access records shall preserve user identity, authority source, access level, changes, approvals, logs, revocations, incidents, and closeout.
154.18 Software Release Authority. The Corporation shall establish software release authority for public-good software, open technical baselines, APIs, SDKs, schemas, dashboards, data tools, reference architectures, test harnesses, evaluation harnesses, benchmark libraries, gold vectors, negative tests, model cards, system cards, benchmark cards, technical profiles, proof-receipt tools, observability tools, Truth Engine tools, verifiable compute tools, cyber tools, geospatial tools, AI-RAN or O-RAN reference tools, DePIN or DLT reference tools, digital twin tools, and related technical assets.
Software release authority shall require, as applicable, secure development review, code review, dependency review, license review, IP chain-of-title review, contributor license review, SBOM generation, vulnerability review, secret scanning, key management review, artifact signing, provenance recording, reproducible build review, rollback plan, documentation review, public-safe language review, data / AI / cyber review, export-control review, sanctions review, controlled-technology review, safeguards review, and Board or officer approval where material.
A software release shall not be represented as certification, procurement approval, provider approval, public authority adoption, finance-readiness, recognition, warranty, guarantee, operational instruction, public warning, emergency command, legal compliance approval, or professional advice. Open release shall not eliminate the need for limitation language, license compliance, security controls, export-control review, or protected knowledge review.
Software release authority shall include authority to hold, freeze, withdraw, deprecate, rollback, patch, quarantine, restrict, archive, or issue security notices for releases where vulnerability, misuse, data exposure, protected knowledge exposure, AI misuse, cyber risk, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, or public-safe publication concern arises.
154.19 Controlled-Room Admission Authority. The Corporation shall establish controlled-room admission authority for controlled rooms, clean rooms, evidence rooms, data rooms, public authority rooms, regulator-listening rooms, public finance reader rooms, emergency-management learning rooms, no-download rooms, confidential review rooms, legal rooms, safeguards rooms, protected knowledge rooms, model review rooms, red-team rooms, technical review rooms, and other restricted environments.
Controlled-room admission authority shall require, as applicable, identity verification, affiliation verification, role classification, public authority capacity classification, conflict disclosure, related-party review, sanctions screening, export-control screening, controlled-technology review, data / AI / cyber review, privacy review, competition notice, public authority boundary notice, finance-boundary notice, certification-boundary notice, procurement-neutrality notice, confidentiality acknowledgment, no-download acknowledgment, protected knowledge acknowledgment, civil-rights acknowledgment, accessibility accommodation, safeguards review, and approval by the competent room authority.
Admission to a controlled room shall not confer membership, governance authority, public authority status, official adoption, public finance status, certification, recognition, finance-readiness, provider preference, sponsor entitlement, public warning authority, emergency command authority, legal clearance, or enterprise execution authority. Room participation shall be capacity-specific, purpose-specific, time-limited or reviewable, logged, monitored where lawful, revocable, and subject to closeout.
Controlled-room admission authority shall include the power to deny, condition, restrict, suspend, remove, revoke access, seal materials, require return or deletion, quarantine exhibits, impose no-download restrictions, issue correction notices, and refer misconduct for enforcement. Admission records shall identify room purpose, admitted person, capacity, authority source, access class, materials access, restrictions, acknowledgments, attendance, exhibits, chain of custody, revocation, closeout, and archive status.
154.20 Incident Response Authority. The Corporation shall establish incident response authority for cybersecurity incidents, data incidents, AI incidents, repository incidents, controlled-room incidents, public-safe publication incidents, public authority confusion incidents, finance-boundary incidents, certification-boundary incidents, procurement-neutrality incidents, recognition-boundary incidents, provider-neutrality incidents, sponsor-control incidents, sanctions incidents, export-control incidents, controlled-technology incidents, research integrity incidents, evidence integrity incidents, protected knowledge incidents, civil-rights incidents, accessibility incidents, harassment incidents, retaliation incidents, competition incidents, fraud incidents, financial control incidents, and other matters requiring urgent containment, review, correction, notice, or escalation.
Incident response authority may include power to hold, stop, quarantine, isolate, restrict access, revoke credentials, rotate keys, freeze publication, freeze implementation, lock repositories, lock controlled rooms, preserve evidence, engage counsel, engage forensic support, notify officers, notify the Board, notify affected persons where required, notify public authorities where required, issue controlled notices, issue public-safe notices, withdraw materials, correct records, suspend delegations, suspend participants, terminate access, and initiate corrective action.
Incident response authority shall be time-limited where emergency in character, record-supported, reviewable, and subject to ratification where required. It shall not authorize concealment, retaliation, destruction of records, unlawful surveillance, unauthorized access, false public statements, suppression of protected complaints, waiver of legal rights outside authority, or exercise of prohibited functions.
Incident response authority shall preserve privilege where applicable, public-safe communication, protected knowledge safeguards, data minimization, confidentiality, evidence integrity, chain of custody, and correctionability.
154.21 Correction Authority. The Corporation shall establish correction authority for corrections, clarifications, supersessions, withdrawals, retractions, takedowns, public-safe notices, controlled notices, repository corrections, register corrections, publication corrections, dataset corrections, software corrections, model corrections, dashboard corrections, map corrections, proof receipt corrections, evidence corrections, methods corrections, ontology corrections, public authority reference corrections, donor or sponsor acknowledgment corrections, controlled-room corrections, and archival corrections.
Correction authority may include authority to identify defects, classify correction type, initiate correction review, hold further reliance, apply limitation language, issue errata, supersede instruments, withdraw publications, retract statements, take down materials, restrict access, correct register entries, correct repository labels, correct public claims, notify affected parties, notify public authorities where required, notify donors or sponsors where required, and preserve correction records.
Correction authority shall not be used to hide errors, erase accountability, suppress dissent, alter historical records without trace, remove adverse findings for sponsor or provider convenience, soften public authority boundary language, soften finance-boundary language, soften certification-boundary language, avoid public-safe notice, conceal protected knowledge misuse, conceal AI misuse, conceal cyber incidents, or avoid legal obligations.
Corrections shall preserve the validity-by-record doctrine. A corrected record shall identify what was corrected, why it was corrected, who authorized the correction, when the correction became effective, what prior version was superseded, whether public or controlled notice is required, what reliance limitations apply, and what archive record preserves historical traceability.
154.22 Authority Matrix Records. The Corporation shall maintain Authority Matrix Records sufficient to demonstrate the creation, approval, versioning, use, review, amendment, suspension, revocation, supersession, correction, and enforcement of signature authority, banking authority, spending authority, procurement authority, contracting authority, grant agreement authority, donation agreement authority, sponsorship agreement authority, in-kind contribution agreement authority, employment and contractor engagement authority, publication authority, public authority reference authority, data access authority, AI-use authority, model approval authority, repository access authority, software release authority, controlled-room admission authority, incident response authority, correction authority, and any other authority-bearing class.
Authority Matrix Records shall include, as applicable:
a) the Authority Matrix title, version, status, custodian, adopting authority, effective date, review date, repository location, access class, publication class, supersession status, and archive status;
b) Board approval records, officer approval records, committee recommendation records, counsel review records, compliance review records, finance review records, tax review records, data / AI / cyber review records, safeguards 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, and conflict review records;
c) role descriptions, authority classes, thresholds, conditions, exclusions, required approvals, required reviews, required notices, required records, escalation pathways, and revocation rules;
d) signature authority records, signatory lists, signature specimens where used, digital signature records, electronic signature settings, key or credential records where used, certification records, and signature revocation records;
e) banking authority records, account authority records, payment approval records, treasury access records, reconciliation records, restricted fund records, user-access records, fraud control records, cyber access records, and banking revocation records;
f) spending, procurement, contracting, grant, donation, sponsorship, in-kind contribution, employment, contractor, reimbursement, benefit, and expense authority records;
g) publication authority records, public statement authority records, public authority reference authority records, controlled vocabulary approval records, limitation language records, non-reliance records, correction notice records, withdrawal records, takedown records, and archive records;
h) data access records, AI-use records, model approval records, inference records, compute workload records, repository access records, software release records, technical asset release records, SBOM records, signing records, provenance records, vulnerability records, rollback records, and retirement records;
i) controlled-room admission records, participant capacity records, screening records, access records, exhibit records, chain-of-custody records, attendance records, no-download records, revocation records, closeout records, return records, deletion records, sealing records, and archive records;
j) incident response records, emergency authority records, break-glass records, hold records, quarantine records, access restriction records, publication freeze records, implementation freeze records, technical isolation records, notices, investigations, corrective actions, ratification records, sunset records, and post-incident review records;
k) correction authority records, correction requests, correction approvals, correction notices, errata, supersession records, withdrawal records, retraction records, takedown records, public clarification records, controlled clarification records, archive records, and correction history metadata;
l) exceptions requested, exceptions refused, exceptions approved where lawful, authority challenges, authority defects, unauthorized acts, ratifications where lawful, voided or non-operative acts, public or controlled corrections, enforcement actions, and lessons learned;
m) periodic review records, access review records, authority review records, threshold review records, segregation-of-duties review records, Board review records, officer certification records, training records, and corrective training records; and
n) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that authority must be known before it is used, recorded when it is granted, limited while it is held, reviewed while it is active, revoked when it ends, and corrected when it is misused. The Authority Matrix is not a convenience chart; it is a constitutional control surface for institutional seriousness. It may organize lawful authority, but it may not create prohibited authority. It may identify who may sign, spend, contract, publish, access data, use AI, approve models, release software, admit participants to controlled rooms, respond to incidents, or correct records; it may not convert GCRI US into a public authority, finance-readiness authority, certification body, procurement body, recognition body, provider selector, sponsor-controlled platform, public warning body, emergency command body, regulated financial actor, or enterprise execution vehicle. Every authority entry shall be lawful, bounded, records-supported, public-safe where relevant, non-executing, role-separated, reviewable, revocable, and correctionable.
Section 155. Officer Conflicts, Related-Party Transactions, Recusals, and Independence Restrictions
155.1 Officer Conflict Duty. Each officer of the Corporation shall owe a continuing duty to identify, disclose, update, manage, mitigate, avoid where required, and refrain from acting upon any conflict of interest, related-party interest, divided loyalty, institutional dependence, financial incentive, personal benefit, fiduciary conflict, professional conflict, public authority conflict, sponsor conflict, provider conflict, donor conflict, funder conflict, host conflict, research conflict, data / AI / cyber conflict, protected knowledge conflict, public-safe publication conflict, or Nexus role-separation conflict that may affect, appear to affect, or reasonably be perceived as affecting the officer’s judgment, independence, authority, recommendation, approval, access, custody, publication, contracting, expenditure, relationship management, public representation, technical release, controlled-room decision, or correction duty.
The conflict duty is not limited to actual impropriety. It applies to actual conflicts, potential conflicts, apparent conflicts, emerging conflicts, recurring conflicts, structural conflicts, institutional conflicts, indirect conflicts, family or household conflicts, affiliate conflicts, employer conflicts, funder conflicts, investor conflicts, board-service conflicts, advisory conflicts, consulting conflicts, public office conflicts, academic conflicts, contractor conflicts, and any other circumstance in which the officer’s judgment for the Corporation may be pulled away from the Corporation’s lawful nonprofit, public-benefit, public-good, non-executing, evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baseline, public authority learning, safeguards, validity-by-record, correctionability, and Nexus role-separated purposes.
An officer shall not decide for himself or herself whether a material conflict is immaterial. Where doubt exists, disclosure, recusal pending review, access restriction where appropriate, and escalation shall be the default posture.
155.2 Annual Conflict Disclosure. Each officer shall complete an annual conflict disclosure in the form, schedule, repository, and time required by the Corporation. The annual disclosure shall be sufficiently detailed to permit meaningful review by the Board, a designated committee, the President, the Executive Director or Chief Executive Officer where applicable, the Secretary, the Chief Legal, Compliance, and Risk Officer where approved, counsel, or another authorized reviewing body.
Annual conflict disclosures shall include, as applicable:
a) employment, consulting, advisory, board, officer, trustee, fiduciary, ownership, partnership, investment, contractor, academic, public authority, nonprofit, professional, political, campaign, lobbying, standards, certification, procurement, finance, insurance, lending, underwriting, rating, technology, data, AI, cyber, research, media, sponsor, provider, host, donor, funder, national company, Project SPV, Nexus entity, GRF, GRA, GCRI Canada, or other external relationships;
b) compensation, equity, options, carried interests, revenue shares, referral fees, success fees, finder fees, bonuses, royalties, honoraria, speaking fees, publication fees, grant interests, sponsorship interests, sponsored seats, reimbursed travel, gifts, hospitality, in-kind benefits, discounted services, cloud credits, compute credits, data access, tool access, software licenses, and other benefits;
c) related persons, family members, household members, close associates, controlled entities, affiliated entities, and beneficial ownership interests that may create a direct or indirect conflict;
d) interests in vendors, contractors, sponsors, donors, funders, hosts, providers, universities, laboratories, public authorities, capital actors, insurers, lenders, underwriters, banks, public finance actors, national companies, Project SPVs, deployment companies, infrastructure operators, data processors, AI providers, cloud providers, cybersecurity providers, and enterprise stack actors; and
e) any circumstance that may affect the officer’s ability to preserve non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, research integrity, public-safe publication, safeguards, protected knowledge, records integrity, or correctionability.
Annual disclosure is a floor, not a ceiling. A complete annual disclosure does not excuse the officer from event-based disclosure when circumstances change.
155.3 Event-Based Conflict Disclosure. Each officer shall promptly disclose any new, changed, discovered, intensified, or newly relevant conflict as soon as the officer knows or reasonably should know that the conflict may affect a matter involving the Corporation. Event-based disclosure shall occur before the officer participates in the affected deliberation, recommendation, approval, signing, expenditure, contract, publication, data access, AI-use decision, model approval, repository release, controlled-room admission, public authority reference, sponsor or donor engagement, provider engagement, correction, enforcement action, personnel decision, or public representation, unless emergency circumstances require immediate protective action subject to after-action disclosure and ratification.
Event-based disclosure shall be required where:
a) a matter involves an entity, person, funder, sponsor, donor, provider, vendor, contractor, host, public authority, investor, insurer, lender, underwriter, bank, university, laboratory, media actor, national company, Project SPV, Nexus actor, GRF, GRA, GCRI Canada, or affiliate with which the officer has a material relationship;
b) the officer may receive, or may be perceived as receiving, financial, professional, reputational, political, academic, institutional, employment, advisory, research, access, publication, or relational benefit;
c) the officer’s outside role may conflict with the Corporation’s public-benefit purpose, non-execution, role separation, public authority boundary, finance boundary, certification boundary, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, or public-safe claims discipline;
d) the officer has participated in, advised, funded, sponsored, built, promoted, evaluated, sold, insured, financed, certified, regulated, procured, deployed, hosted, or operated the relevant technology, program, project, dataset, model, dashboard, software, standard, proof pack, evidence pack, controlled room, public authority interface, or enterprise stack activity; or
e) the officer becomes aware that prior disclosure was incomplete, inaccurate, stale, misleading, or no longer sufficient.
A delayed disclosure shall be treated as a compliance concern where the officer participated in a matter before disclosure. The Corporation may impose recusal, restriction, reconsideration, correction, ratification where lawful, or enforcement measures.
155.4 Financial Conflicts. A financial conflict exists where an officer, related person, controlled entity, employer, client, funder, investor, sponsor, donor, provider, host, contractor, vendor, partner, or affiliate has a financial interest that may affect, appear to affect, or reasonably be perceived as affecting the officer’s judgment or authority. Financial interests include ownership, equity, debt, options, warrants, carried interests, profit shares, royalties, revenue shares, commissions, referral fees, finder fees, success fees, bonuses, consulting fees, employment income, grants, sponsored research, gifts, hospitality, travel, expense coverage, discounts, credits, in-kind benefits, board compensation, advisory compensation, investor interests, lending interests, insurance interests, underwriting interests, procurement interests, contract interests, and other economic benefits.
Financial conflicts are especially material where they relate to:
a) grants, donations, sponsorships, subscriptions, fees, cost recovery, restricted funds, in-kind contributions, or public-good support;
b) procurement, contracting, vendor selection, contractor engagement, professional services, cloud services, compute services, AI tools, cybersecurity tools, data services, software licenses, event services, facilities, or infrastructure support;
c) public-good software, technical baselines, repositories, datasets, dashboards, APIs, SDKs, schemas, models, evaluation harnesses, benchmark libraries, observability tools, AI-RAN tools, O-RAN tools, DePIN tools, DLT or blockchain tools, digital twin tools, cyber tools, or geospatial tools;
d) GRF-facing recognition, maturity, standing, Docket, Grid, public legitimacy, or claims-discipline inputs;
e) GRA-facing finance-readiness, capital-readability, proof-pack, insurance-readiness, diligence-translation, RNFD, NFD, UNFSD, or capital-reader inputs; or
f) public authority learning, public authority references, public finance reader rooms, regulator-listening rooms, procurement-adjacent contexts, or public infrastructure contexts.
An officer with a material financial conflict shall not approve, sign, recommend, route as neutral, control records for, supervise review of, publish, release, or represent the affected matter unless the conflict is disclosed, reviewed, and managed by competent authority. Where independence cannot be preserved, recusal and access restriction shall be required.
155.5 Institutional Conflicts. An institutional conflict exists where an officer’s obligations, loyalties, duties, employment, appointment, advisory role, funding relationship, public office, board service, academic role, consulting role, contractor role, secondment, fellowship, sponsorship role, provider role, host role, investor role, insurer role, lender role, standards role, certification role, procurement role, public authority role, media role, or Nexus-system role may conflict with the officer’s duties to the Corporation.
Institutional conflicts may arise even without personal financial benefit. They include conflicts created by organizational commitments, strategic alliances, donor expectations, sponsor expectations, employer expectations, grant obligations, public authority expectations, academic publication pressures, provider business interests, host operational interests, national company interests, Project SPV interests, GRF role obligations, GRA role obligations, GCRI Canada role obligations, Nexus Standards role obligations, Nexus Network role obligations, or other role-specific obligations.
An officer shall not use a Corporation office to advance an external institution’s agenda, secure preferential access, obtain public authority advantage, obtain technical baseline influence, steer research, influence evidence classification, influence public-safe publication, influence controlled vocabulary, influence software release, influence standards support, influence GRF-facing inputs, influence GRA-facing inputs, or influence provider or sponsor treatment.
Where institutional dual-role value is mission-enhancing and lawful, the Corporation may permit participation subject to disclosure, capacity labeling, conflict management, recusal, access restrictions, public-safe language, records, compatibility notes, and divergence logs. Where institutional conflict threatens independence, the officer shall be recused, restricted, reassigned, or removed from the affected matter.
155.6 Research Conflicts. A research conflict exists where an officer’s financial, institutional, academic, professional, publication, authorship, sponsorship, grant, employer, provider, public authority, political, personal, or reputational interests may affect the design, conduct, review, interpretation, validation, publication, correction, withdrawal, retraction, or public characterization of research, evidence, methods, observability outputs, ontology artifacts, technical truth outputs, public-good R&D, public-good software, open technical baselines, model evaluations, benchmarks, datasets, dashboards, maps, or controlled-room findings.
Research conflicts include, without limitation, conflicts involving:
a) sponsored research;
b) provider-supplied tools, data, software, models, infrastructure, compute, AI-RAN components, O-RAN components, DePIN components, DLT components, sensors, dashboards, digital twins, or cybersecurity tools;
c) funder expectations regarding outcomes, publication timing, public messaging, public authority access, or technical baseline treatment;
d) academic incentives, authorship, citation advantage, publication priority, conference participation, media exposure, or intellectual property interests;
e) prior involvement in designing, deploying, financing, insuring, underwriting, procuring, certifying, recognizing, operating, or marketing the subject system; and
f) relationships with public authorities, sponsors, donors, providers, hosts, national companies, Project SPVs, or enterprise actors affected by the research.
Research conflicts shall be disclosed in research records and handled through independent review, recusal, role separation, method transparency, sponsor disclosure, limitation language, publication integrity controls, and correction pathways. No officer shall suppress unfavorable findings, inflate favorable findings, alter confidence levels, remove uncertainty language, soften public-safe limitations, delay correction, or convert research into certification, recognition, finance-readiness, procurement approval, public authority decision, public warning, or provider endorsement.
155.7 Data / AI / Cyber Conflicts. A data / AI / cyber conflict exists where an officer’s relationship to a data provider, AI provider, model developer, cloud provider, cybersecurity provider, repository host, compute provider, software vendor, sensor operator, AI-RAN provider, O-RAN provider, DePIN network, DLT or blockchain system, digital twin provider, dashboard provider, public authority data contributor, data processor, data broker, infrastructure operator, research dataset, protected knowledge holder, or affected community may compromise or appear to compromise decisions about data access, AI use, model approval, cyber controls, repository access, public-safe publication, secure release, vulnerability handling, incident response, or correction.
Data / AI / cyber conflicts are material where the officer may influence:
a) access to restricted data, controlled-room materials, public authority data, personal information, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, community-protected data, Tribal or Indigenous data, local or territorial knowledge, or protected knowledge;
b) model selection, model approval, model benchmarking, evaluation harness design, dataset cards, model cards, system cards, benchmark cards, inference records, compute workload records, or AI-use approvals;
c) repository permissions, software releases, SBOM generation, vulnerability disclosure, secure release, credential access, key management, incident response, or disaster recovery;
d) use of data or AI outputs in public-safe reports, dashboards, maps, technical baselines, public authority learning materials, GRF-facing inputs, GRA-facing technical inputs, Docket support, or Grid support; or
e) public representation of data validity, model reliability, cyber maturity, verifiable compute, verifiable intelligence, proof receipts, or technical truth.
An officer with a data / AI / cyber conflict shall not approve access, release, publication, model use, incident treatment, vulnerability treatment, or public characterization unless competent review determines that the conflict can be managed. Where the officer is conflicted, independent technical, legal, data protection, cybersecurity, safeguards, and public-safe review shall be used where appropriate.
155.8 Public Authority Conflicts. A public authority conflict exists where an officer’s current, former, prospective, or related role with a federal, state, territorial, Tribal, Indigenous, local, municipal, county, metropolitan, port, utility, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, infrastructure, regulator, public finance, public procurement, grant-making, emergency command, public university, public laboratory, or other public authority may affect, appear to affect, or reasonably be perceived as affecting the officer’s judgment for the Corporation.
Public authority conflicts include conflicts arising from public office, employment, appointment, advisory service, procurement involvement, grant administration, public finance involvement, regulator participation, emergency-management authority, public infrastructure authority, public records obligations, open meetings obligations, government ethics obligations, gift rules, lobbying rules, procurement integrity rules, or confidential public authority information.
An officer with a public authority conflict shall not:
a) imply that the Corporation acts as or for the public authority;
b) imply official endorsement, adoption, approval, funding, procurement, public finance, regulation, public warning, or emergency command by virtue of the officer’s role;
c) use nonpublic public authority information for Corporation advantage or for any sponsor, provider, donor, funder, host, or enterprise actor advantage;
d) influence Corporation outputs to favor the public authority outside public-safe evidence and methods discipline;
e) participate in public authority-facing decisions where the officer’s public role creates conflict unless authorized after review; or
f) use the Corporation to bypass public procurement, grant, ethics, lobbying, public records, open meetings, or public authority constraints.
Public authority conflicts shall be managed through capacity classification, disclosure, recusal, non-endorsement language, public-safe notices, segregation of materials, public authority reference review, legal review, and records.
155.9 Sponsor, Donor, Funder, Provider, Host, Investor, Insurer, Lender, National Company, Project SPV, Contractor, University, Laboratory, or Partner Conflicts. A conflict exists where an officer has a relationship with a sponsor, donor, funder, provider, host, investor, insurer, lender, underwriter, bank, public finance actor, national company, state operating company, regional company, Project SPV, contractor, vendor, university, laboratory, partner, media actor, civil society organization, community organization, Tribal or Indigenous organization, or other participant that may affect the officer’s judgment, authority, access, approval, records, public statements, publication, technical release, support acceptance, or interface conduct.
Such conflicts are especially material where the external actor seeks, receives, or may be perceived to receive:
a) governance influence;
b) Board, committee, council, working group, panel, controlled-room, repository, or publication influence;
c) public authority access or public authority reference advantage;
d) provider preference or procurement advantage;
e) certification, accreditation, recognition, standing, maturity, Docket standing, Grid standing, or Nexus-compatible status;
f) finance-readiness, insurance-readiness, capital-readability, proof-pack, bankability, investability, rating, or public finance advantage;
g) access to nonpublic evidence, methods, data, AI systems, cyber materials, protected knowledge, controlled-room materials, or technical baselines;
h) research outcome, publication timing, publication veto, suppression, softening, or correction avoidance; or
i) public-safe claim advantage, logo advantage, badge advantage, event advantage, grant advantage, media advantage, or market advantage.
The Corporation shall treat such conflicts as heightened where the officer manages the relationship, negotiates the agreement, approves the benefit, supervises the work, controls the record, authors the publication, approves the release, admits the participant, routes the evidence, or represents the relationship externally. The officer shall disclose, and the Corporation shall apply recusal, independent review, access restriction, delegated reassignment, public-safe language, and records as needed.
155.10 Related-Party Transactions. A related-party transaction includes any transaction, arrangement, contract, grant, donation, sponsorship, in-kind contribution, procurement, reimbursement, compensation, benefit, license, data access, software access, controlled-room access, publication opportunity, employment, contractor engagement, consulting arrangement, fellowship, award, scholarship, stipend, travel support, public acknowledgment, or other benefit involving the Corporation and an officer, director, related person, family member, household member, controlled entity, employer, client, affiliate, sponsor, donor, funder, provider, host, investor, insurer, lender, national company, Project SPV, contractor, vendor, university, laboratory, or partner with which the officer has a material relationship.
A related-party transaction shall not be approved unless it is lawful, within the Corporation’s purposes, reasonable, fair to the Corporation, consistent with nonprofit character, consistent with tax-exempt or tax-exempt-compatible restrictions, free from private inurement, not an impermissible private benefit, properly disclosed, independently reviewed, records-supported, and approved by competent disinterested authority. Where applicable, the Corporation shall document comparability, alternatives, market reasonableness, public-benefit justification, conflict disclosure, recusal, vote record, and terms.
Related-party transactions shall not be used to create sponsor control, provider preference, public authority access purchase, outcome purchase, certification purchase, recognition purchase, finance-readiness purchase, procurement advantage, protected knowledge access, data access advantage, AI system advantage, repository advantage, technical baseline influence, public-safe publication influence, or enterprise execution pathway.
A conflicted officer shall not participate in the approval of the related-party transaction except to provide factual information requested by disinterested reviewers, and shall not be present for deliberation or vote unless permitted by the reviewing authority for a limited factual purpose and recorded accordingly.
155.11 Independent Review. Conflicts and related-party transactions shall be reviewed by disinterested authority. Independent review may be conducted by the Board, a disinterested committee, disinterested directors, a designated officer without conflict, the Chief Legal, Compliance, and Risk Officer where approved and not conflicted, counsel, tax advisor, compliance advisor, data protection advisor, cybersecurity advisor, safeguards reviewer, research integrity reviewer, or other competent reviewer as appropriate to the matter.
Independent review shall determine, as applicable:
a) whether a conflict exists;
b) whether the conflict is actual, potential, apparent, structural, recurring, or unmanageable;
c) whether the officer may participate, recommend, approve, sign, access, supervise, publish, release, represent, or decide;
d) whether recusal, access restriction, role reassignment, independent review, additional disclosure, limitation language, public-safe notice, controlled notice, or Board approval is required;
e) whether the transaction or activity is fair, reasonable, mission-aligned, lawful, and not an impermissible private benefit;
f) whether public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, research integrity, safeguards, protected knowledge, competition rules, sanctions rules, export-control rules, and controlled-technology rules are preserved; and
g) whether correction, reconsideration, ratification where lawful, refusal, return, restriction, quarantine, termination, or enforcement is required.
Independent review shall be recorded. A failure to complete independent review where required shall render the affected action voidable, suspendable, non-operative, subject to ratification where lawful, or subject to correction.
155.12 Recusal From Deliberation. An officer shall recuse from deliberation when the officer has a conflict that may affect, appear to affect, or reasonably be perceived as affecting the officer’s impartiality, independence, or duty to the Corporation. Recusal from deliberation means the officer shall not participate in discussion, framing, recommendation development, persuasion, agenda shaping, informal pre-meeting positioning, side-channel influence, drafting of decision language, controlled-room framing, public authority framing, sponsor framing, provider framing, or technical framing of the affected matter unless the reviewing authority authorizes limited factual participation.
Recusal from deliberation shall be required where the officer’s participation may influence:
a) a contract, procurement, grant, donation, sponsorship, in-kind contribution, compensation, reimbursement, benefit, or related-party transaction;
b) research design, evidence classification, method review, publication, technical baseline, software release, model approval, dataset release, dashboard release, map release, public-safe report, correction, withdrawal, retraction, or takedown;
c) public authority reference, public authority participation, regulator-listening room, public finance reader room, emergency-management learning room, or public authority data contribution;
d) GRF-facing recognition or maturity inputs, GRA-facing finance-readiness technical inputs, Docket support, Grid support, or Nexus-compatible claim language; or
e) any matter involving the officer’s external employer, client, funder, sponsor, provider, host, investor, insurer, lender, national company, Project SPV, contractor, university, laboratory, or partner.
A recused officer may provide factual information only at the request of disinterested reviewers, for a limited purpose, and subject to record.
155.13 Recusal From Recommendation. An officer with a conflict shall not make, approve, endorse, sign, route as neutral, or present a recommendation on the affected matter unless the conflict has been reviewed and the competent reviewing authority expressly permits a limited recommendation subject to disclosure and safeguards. Recommendation includes formal recommendations, informal recommendations, staff recommendations, committee recommendations, technical recommendations, vendor recommendations, publication recommendations, public authority recommendations, controlled-room recommendations, model recommendations, data access recommendations, software release recommendations, corrective action recommendations, and escalation recommendations.
No officer shall disguise a conflicted recommendation as:
a) a technical view;
b) a neutral evidence summary;
c) a methods note;
d) a public authority learning suggestion;
e) a finance-boundary note;
f) a procurement administrative note;
g) a controlled vocabulary suggestion;
h) a repository label;
i) a workflow status;
j) an AI-generated summary;
k) a staff note; or
l) an operational convenience.
Where an officer’s expertise is necessary and the officer is conflicted, the Corporation shall record the conflict, obtain independent review where practicable, identify any reliance limits, and distinguish factual or technical input from recommendation.
155.14 Recusal From Approval. An officer with a material conflict shall not approve, sign, authorize, release, admit, certify internally, publish, spend, contract, hire, reimburse, accept support, grant access, approve data use, approve AI use, approve model use, approve repository access, approve software release, approve public authority reference, approve controlled-room admission, approve correction, or approve closeout for the affected matter unless competent disinterested authority determines that the conflict is not material to the approval or that limited action is necessary and lawful under controlled conditions.
Approval recusal shall apply even where the officer otherwise has delegated authority. Delegated authority is suspended for the affected matter to the extent necessary to preserve independence. A conflicted officer may not cure the conflict by obtaining informal comfort from a subordinate, contractor, sponsor, provider, public authority participant, or conflicted colleague.
Where an approval is made in violation of this Section, the Corporation may hold, suspend, void, voidable, ratify where lawful, re-review, correct, withdraw, terminate, disclose, or otherwise remediate the action. A conflicted approval may also trigger disciplinary action, access restriction, delegation suspension, removal, contract remedy, public or controlled correction, or legal referral where appropriate.
155.15 Access Restriction During Recusal. Where recusal is required, the Corporation may restrict the officer’s access to materials, meetings, channels, rooms, repositories, datasets, model records, inference records, compute workload records, legal materials, privileged materials, Board materials, committee materials, public authority materials, sponsor materials, provider materials, protected knowledge, controlled-room exhibits, financial information, procurement materials, publication drafts, correction drafts, or other records related to the conflicted matter.
Access restriction shall be proportionate to the conflict, data sensitivity, public authority sensitivity, finance sensitivity, procurement sensitivity, certification sensitivity, sponsor or provider sensitivity, protected knowledge sensitivity, cyber sensitivity, research integrity sensitivity, and legal risk. Access restriction may include removal from distribution lists, repository permission changes, room exclusion, no-download restrictions, redaction, clean-team routing, separate counsel routing, special committee routing, privilege segregation, and audit logging.
An officer subject to access restriction shall not seek access through another person, shared account, alternate repository, informal channel, AI summary, meeting participant, public authority contact, sponsor contact, provider contact, contractor, subordinate, or technical administrator. Any attempted circumvention shall be treated as a serious violation.
Access restriction shall not be used for retaliation, concealment, suppression of dissent, or avoidance of accountability. It shall be used only to protect the Corporation, the integrity of the matter, and affected persons or communities.
155.16 Delegation Restriction During Conflict. An officer shall not delegate authority over a conflicted matter to a subordinate, contractor, advisor, working group, committee participant, technical lead, repository maintainer, controlled-room administrator, public authority liaison, sponsor liaison, provider liaison, or other person where the delegation would preserve the officer’s influence, evade recusal, obscure responsibility, or create indirect control.
Where an officer is conflicted, any delegation related to the affected matter shall be reviewed by competent authority and, where needed, reassigned to a disinterested officer, committee, director, counsel, reviewer, custodian, or independent process. The conflicted officer shall not supervise, direct, pressure, evaluate, reward, discipline, or communicate side-channel instructions to the person handling the matter unless the reviewing authority permits limited factual communications and records them.
Delegation restriction applies to all authority-bearing acts, including contract routing, expenditure approval, procurement evaluation, sponsor benefit administration, donor acknowledgment, grant reporting, publication review, evidence classification, method approval, data access, AI-use approval, repository access, software release, controlled-room admission, public authority reference, correction, withdrawal, retraction, takedown, and enforcement.
No officer shall use emergency authority, technical urgency, public authority urgency, sponsor urgency, grant deadline, publication deadline, event deadline, repository deadline, or operational convenience to retain delegated influence over a conflicted matter.
155.17 Conflict Mitigation. The Corporation may mitigate conflicts through one or more lawful and recorded controls. Mitigation may include disclosure, public or controlled disclosure where appropriate, limitation language, recusal, access restriction, abstention, reassignment, independent review, clean-team review, special committee review, counsel review, tax review, compliance review, safeguards review, data / AI / cyber review, public authority boundary review, finance-boundary review, certification-boundary review, procurement-neutrality review, provider-neutrality review, sponsor non-control review, related-party review, monitoring, reporting, cooling-off periods, role separation, capacity labeling, firewalls, separate repositories, separate rooms, separate communications, independent custody, denial of authority, or removal from the affected role.
Conflict mitigation shall be designed to preserve:
a) the Corporation’s lawful nonprofit and public-benefit purposes;
b) independence of judgment;
c) evidence and methods integrity;
d) research integrity;
e) public-safe publication;
f) public authority boundary discipline;
g) finance and regulated-perimeter discipline;
h) certification and procurement boundary discipline;
i) provider neutrality and sponsor non-control;
j) data / AI / cyber and privacy controls;
k) civil rights, accessibility, community safeguards, Tribal and Indigenous protocols, and protected knowledge;
l) validity-by-record and correctionability; and
m) Nexus role separation.
Some conflicts cannot be mitigated. Where a conflict is unmanageable, the Corporation shall prohibit participation, deny approval, refuse or terminate the transaction, reassign the matter, suspend delegation, remove the officer from the role, or take other lawful action.
155.18 Conflict Violation Response. A conflict violation includes failure to disclose, late disclosure, incomplete disclosure, misleading disclosure, participation despite required recusal, improper recommendation, improper approval, access circumvention, indirect influence, conflicted delegation, conflicted supervision, related-party transaction without review, private benefit, sponsor control, provider preference, public authority overclaim, finance overclaim, certification overclaim, procurement overclaim, data misuse, AI misuse, cyber misuse, protected knowledge exposure, research manipulation, public-safe publication manipulation, correction avoidance, retaliation, concealment, or destruction of conflict-related records.
Upon identifying a conflict violation, the Corporation may:
a) hold, suspend, quarantine, re-review, void, voidable, or treat as non-operative the affected act to the fullest extent lawful;
b) require corrective disclosure, supplemental review, independent review, Board review, counsel review, tax review, compliance review, safeguards review, data / AI / cyber review, or public authority boundary review;
c) require recusal, access restriction, delegation suspension, reassignment, corrective training, reprimand, probation, suspension, removal, termination, contract remedy, or restitution where appropriate;
d) correct, supersede, withdraw, retract, take down, archive, or publicly or controllably clarify affected materials;
e) notify affected persons, public authorities, funders, donors, sponsors, providers, hosts, communities, or regulators where required or appropriate and lawful;
f) preserve evidence, protect privilege, maintain confidentiality, and prevent retaliation; and
g) refer the matter to legal counsel, auditors, regulators, public authorities, law enforcement, funders, or other competent bodies where required or appropriate.
No officer may retaliate against any person who raises a conflict concern, requests review, refuses to participate in a conflicted act, supports correction, or provides evidence in a conflict review.
155.19 Officer Conflict, Recusal, and Related-Party Records. The Corporation shall maintain Officer Conflict, Recusal, and Related-Party Records sufficient to demonstrate disclosure, review, mitigation, recusal, access restriction, approval, refusal, correction, enforcement, and closure of officer conflicts and related-party matters. These records shall be maintained in the official repository or other approved controlled repository, subject to confidentiality, privilege, privacy, public authority, data / AI / cyber, protected knowledge, and legal hold controls.
Officer Conflict, Recusal, and Related-Party Records shall include, as applicable:
a) annual conflict disclosures;
b) event-based conflict disclosures;
c) updates, amendments, certifications, and acknowledgments;
d) conflict classifications;
e) related-party transaction records;
f) reviewer identity and independence records;
g) Board, committee, officer, counsel, tax, compliance, data / AI / cyber, safeguards, public authority boundary, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, and sponsor non-control review records;
h) recusal records;
i) access restriction records;
j) delegation restriction and reassignment records;
k) minutes, resolutions, written consents, and approval records;
l) comparability data, fairness review, public-benefit justification, private benefit review, inurement review, and tax review records where applicable;
m) sponsor, donor, funder, provider, host, public authority, investor, insurer, lender, national company, Project SPV, contractor, university, laboratory, partner, and affiliate relationship records;
n) public-safe limitation language, non-reliance language, controlled notices, public notices, correction notices, and clarification records;
o) violations, investigations, holds, quarantines, suspensions, refusals, terminations, ratifications where lawful, corrective actions, enforcement actions, and closeout records;
p) no-retaliation protections, complaints, grievance records, protected participation records, and remedy records where applicable; and
q) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that officer authority must never be separated from officer independence. Officers may manage, recommend, approve, sign, publish, access, release, admit, represent, and correct only where their authority is lawful and their judgment is not compromised by unmanaged conflict. Conflict disclosure is not a formality; it is a core public-benefit control. Related-party transactions are not prohibited solely because they are related, but they are prohibited unless lawful, fair, disclosed, independently reviewed, records-supported, and free from private inurement, impermissible private benefit, sponsor control, provider preference, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, or Nexus role collapse. Every officer conflict shall be disclosed, reviewed, managed, recorded, and correctionable.
Section 156. Officer Compensation, Reimbursement, Benefits, Expenses, and No Improper Private Benefit
156.1 Compensation Principle. Officer compensation shall be governed by the Corporation’s nonprofit character, public-benefit purpose, tax-exempt or tax-exempt-compatible posture, non-distribution obligation, private inurement prohibition, private benefit controls, fiduciary duties, budget authority, conflict rules, related-party transaction rules, compensation policy, delegation matrix, authority matrix, and records discipline. Compensation may be paid to an officer only where lawful, authorized, reasonable, properly classified, independently reviewed where required, records-supported, and consistent with the Corporation’s public-good mission and non-executing institutional character.
Officer compensation shall not be treated as an entitlement arising from title, founder status, technical centrality, public reputation, fundraising importance, sponsor relationship, provider relationship, grant relationship, public authority relationship, authorship, repository control, room control, program leadership, or Nexus interface role. Compensation is a controlled institutional expenditure, not a means of transferring surplus, rewarding influence, purchasing loyalty, compensating prohibited execution, or allocating private gain from the Corporation’s public-good assets.
The Corporation may compensate officers for bona fide services actually rendered to or for the Corporation, including executive leadership, administration, research, evidence stewardship, methods development, technical management, public-good software stewardship, data / AI / cyber governance, public authority learning support, safeguards administration, legal and compliance support, fundraising administration, operations, and other lawful work within the Corporation’s purposes. No compensation arrangement shall authorize, reward, or incentivize activity inconsistent with public-benefit purpose, nonprofit character, tax restrictions, non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, community safeguards, protected knowledge, validity-by-record, or correctionability.
156.2 Reasonableness Requirement. Officer compensation shall be reasonable in amount, structure, timing, and classification. Reasonableness shall be assessed in light of the officer’s duties, qualifications, time commitment, scope of responsibility, institutional stage, budget, fund restrictions, comparable compensation data where available, geographic and market context, nonprofit and public-benefit sector norms, tax requirements, state nonprofit law, public support constraints, grant restrictions, sponsor restrictions, donor restrictions, and the Corporation’s duty to preserve assets for public-benefit purposes.
Reasonableness review may consider, as applicable:
a) job description, authority scope, reporting line, decision authority, delegated powers, risk exposure, fiduciary or executive responsibility, technical responsibility, public authority interface responsibility, data / AI / cyber responsibility, safeguards responsibility, and records responsibility;
b) comparable compensation for similarly situated nonprofit, research, technical, public-interest, academic, standards-support, public-good software, public authority learning, data governance, cybersecurity, AI governance, legal, compliance, finance, and executive roles;
c) the Corporation’s size, stage, revenues, reserves, budget, grant restrictions, restricted funds, geographic scope, all-states-and-territories posture, North America anchor role, technical complexity, public-benefit risk, and operational maturity;
d) whether compensation is salary, hourly compensation, stipend, consulting fee, project fee, executive compensation, deferred compensation, bonus, incentive, honorarium, benefit, allowance, reimbursement, or other economic arrangement;
e) whether compensation is funded by unrestricted funds, restricted grants, restricted donations, sponsorship revenue, fees, cost recovery, public-good support, or other sources; and
f) whether the arrangement may create private inurement, impermissible private benefit, conflict of interest, related-party concern, sponsor control, provider preference, public authority confusion, finance-boundary concern, certification-boundary concern, procurement concern, or reputational risk.
No compensation shall be approved merely because funds are available. Public-benefit necessity, legal authority, fairness, proportionality, and records support shall be required.
156.3 Board Approval or Delegated Approval. The Board shall approve compensation for principal officers, senior officers, officers with substantial authority, officers who are directors, officers who are founders or related parties, officers whose compensation may create heightened tax or private benefit risk, and any officer compensation arrangement reserved to the Board by law, the Articles or Certificate, this Bylaw, policy, grant terms, donor restrictions, or Board resolution. The Board may delegate approval of non-principal officer compensation within clear written thresholds, job classifications, budget authority, conflict controls, and compensation policy.
Any approval of officer compensation shall identify, as applicable:
a) the officer role and title;
b) employment or contractor classification;
c) compensation type, amount, term, payment schedule, benefits, reimbursement rules, expense limits, and renewal conditions;
d) budget source and fund restrictions;
e) approval authority and legal basis;
f) reasonableness review method;
g) conflict disclosures and recusals;
h) tax, nonprofit, private benefit, and employment classification review;
i) reporting requirements;
j) amendment, suspension, termination, and clawback or repayment provisions where applicable; and
k) record custodian and repository location.
No officer may approve his or her own compensation. No subordinate may approve compensation for a supervising officer where independence is compromised. No sponsor, donor, funder, provider, host, public authority participant, investor, insurer, lender, national company, Project SPV, contractor, vendor, university, laboratory, partner, or Nexus interface actor may approve, control, dictate, condition, or veto officer compensation.
156.4 Independent Approval for Senior Officers. Compensation for senior officers shall be approved by disinterested authority. Senior officers may include the President, Executive Director, Chief Executive Officer, Secretary, Treasurer, 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, Chief Operating Officer, Chief Development, Grants, and Public-Good Support Officer, and any other officer designated by the Board as a senior officer.
Independent approval shall require disclosure of all material facts, abstention or recusal by conflicted persons, review by disinterested directors or an authorized disinterested committee, and records sufficient to demonstrate the basis for approval. Where required or prudent, the Corporation shall obtain advice from counsel, tax advisors, compensation consultants, auditors, accountants, employment counsel, benefits advisors, or other independent reviewers.
A senior officer whose compensation is under review shall not be present for deliberation or vote, except to provide factual information requested by the approving body. The minutes or approval record shall identify the recusal, the information reviewed, the approval standard applied, and the decision reached. Independent approval shall not be delegated to the compensated officer, to a subordinate of the compensated officer, or to a person controlled by the compensated officer.
156.5 Comparability Review Where Appropriate. The Corporation shall conduct comparability review where appropriate, required, or prudent for officer compensation. Comparability review may include review of compensation surveys, public filings, nonprofit executive compensation data, university and research institute compensation data, public-interest technology compensation data, cybersecurity and AI governance role data, comparable public-benefit organizations, comparable stage organizations, comparable geographic markets, and role-specific complexity.
Comparability review shall be calibrated to the Corporation’s size, resources, tax posture, legal obligations, and risk profile. The absence of perfect comparables shall not excuse the Corporation from reasoned judgment. Where market comparables are incomplete, the approving body may consider role description, required expertise, time commitment, budget, public-benefit constraints, mission-critical need, scarcity of expertise, and internal equity, provided that the record explains the basis for the decision.
Comparability data shall not be used mechanically to justify excessive compensation. The Corporation shall consider whether compensation is sustainable, mission-aligned, proportionate, and compatible with public trust. Where an arrangement exceeds typical nonprofit comparables, the record shall identify the public-benefit justification, heightened review, conflict controls, performance scope, and legal review supporting the decision.
156.6 Tax-Exempt and Private Benefit Review. Officer compensation shall be reviewed for compliance with tax-exempt or tax-exempt-compatible requirements, private inurement prohibitions, excess benefit transaction rules where applicable, intermediate sanctions where applicable, unrelated business income considerations where applicable, charitable trust principles where applicable, state nonprofit law, charitable solicitation law where applicable, grant restrictions, donor restrictions, sponsorship rules, and restricted fund obligations.
Tax-exempt and private benefit review shall address whether:
a) the officer is an insider, disqualified person, founder, director, related party, substantial contributor, donor, sponsor, provider, host, contractor, or person with substantial influence;
b) compensation is reasonable for services actually rendered;
c) benefits are documented, ordinary, necessary, and mission-related;
d) restricted funds may lawfully be used;
e) incentive compensation could create private benefit, mission drift, prohibited execution, sponsor control, provider preference, public authority access sale, finance-readiness sale, certification sale, procurement advantage, or research outcome pressure;
f) reimbursements are accountable, documented, and non-excessive;
g) loans, advances, guarantees, deferred compensation, severance, fringe benefits, housing, travel, relocation, or allowances create additional tax or nonprofit risk; and
h) disclosure, reporting, withholding, payroll, contractor reporting, Form 990 reporting where applicable, and state reporting obligations are satisfied.
Where tax or private benefit risk is material, compensation shall not be approved without counsel, tax advisor, Board, or disinterested committee review as appropriate.
156.7 Employment or Contractor Classification. Each compensated officer relationship shall be classified as employment, contractor, consultant, stipend, fellow, advisor, volunteer with reimbursement, or other lawful status based on the actual facts and applicable law. Classification shall be determined by the Corporation’s legal, tax, employment, finance, and operational controls, not by convenience, preference, budget treatment, title, grant category, sponsor expectation, public authority expectation, or informal practice.
Classification review shall consider control, supervision, schedule, tools, integration into operations, exclusivity, financial risk, method of payment, benefits, tax withholding, reporting, intellectual property, confidentiality, data access, AI access, cyber access, public authority interface access, repository access, controlled-room access, and applicable federal, state, territorial, local, and cross-border rules.
Misclassification shall be corrected when discovered. Correction may include payroll adjustment, tax reporting correction, contract amendment, benefit correction, withholding correction, reimbursement correction, records correction, legal review, disclosure where required, and corrective action. No officer may be classified as a contractor merely to avoid payroll duties, tax obligations, benefits obligations, employment-law obligations, conflict controls, supervision records, or fiduciary accountability.
156.8 Benefits. The Corporation may provide lawful and reasonable benefits to officers, including health benefits, retirement benefits, paid time off, disability coverage, life insurance, professional development, equipment, technology tools, cybersecurity tools, communication tools, travel support, relocation support, accessibility accommodations, workplace supports, and other benefits approved by the Board or competent authority. Benefits shall be documented, uniformly governed where appropriate, tax-reviewed where needed, and consistent with budget, employment classification, public-benefit purpose, nonprofit character, and private benefit controls.
Benefits shall not be structured to provide disguised compensation, private inurement, excessive benefit, preferential treatment without justification, sponsor-funded inducement, provider-funded inducement, public authority access inducement, or compensation tied to prohibited outcomes. Benefits shall not include personal use of restricted data, protected knowledge access, controlled-room access, public authority access, technical asset access, repository access, sponsor privileges, provider privileges, or travel benefits beyond approved institutional purpose.
Where benefits are provided through grant, donor, sponsor, or restricted funding, the Corporation shall confirm that the benefit is permitted by the funding terms and does not create donor or sponsor control. Benefits shall be reviewed periodically for reasonableness, tax compliance, equity, accessibility, and mission fit.
156.9 Reimbursement. The Corporation may reimburse officers for reasonable, necessary, documented, approved expenses incurred for lawful Corporation purposes. Reimbursement shall be governed by an accountable plan or equivalent reimbursement controls where applicable and shall require records showing business purpose, date, amount, payee, category, funding source, approval, and supporting documentation.
Reimbursable expenses may include, where approved:
a) travel, lodging, meals, ground transportation, visas, conference fees, meeting costs, public authority learning costs, research costs, fieldwork costs, accessibility costs, translation costs, software tools, secure communications, cybersecurity tools, repository tools, professional development, filings, and other mission-related expenses;
b) expenses related to Board meetings, committee meetings, controlled rooms, public authority learning sessions, research work, evidence review, methods development, public-good software work, Academy activities, safeguards activities, and Nexus interface work; and
c) emergency protective expenses incurred to preserve data security, cyber integrity, public-safe publication discipline, controlled materials, protected knowledge, legal deadlines, or continuity of operations, subject to prompt review and ratification where required.
Reimbursement shall not be used to bypass compensation approval, procurement controls, travel policy, conflict rules, sponsor non-control, provider neutrality, public authority boundary rules, finance-boundary rules, or restricted fund limitations.
156.10 Expense Documentation. Each officer expense shall be supported by documentation sufficient to permit review, audit, tax classification, grant reporting, restricted fund tracking, reimbursement approval, and public-benefit justification. Documentation shall include receipts, invoices, payment evidence, business purpose, attendees where applicable, program or project code, funding source, approval record, and any required conflict disclosure.
Where documentation is missing, incomplete, unreliable, or inconsistent, the Corporation may deny reimbursement, request additional information, classify payment as taxable compensation where required, require repayment, correct records, restrict future reimbursement, or initiate review. Credit card statements alone shall not be sufficient where receipts or itemized records are required, unless policy permits exception for low-risk expenses.
Expense documentation shall be retained in accordance with the Corporation’s records retention rules, grant requirements, tax requirements, legal hold rules, data protection rules, confidentiality rules, and audit requirements. Documentation containing personal information, public authority materials, protected knowledge, cyber-sensitive information, travel security information, or confidential third-party information shall be access-controlled.
156.11 Travel and Event Expenses. Travel and event expenses for officers shall be reasonable, mission-related, approved where required, and consistent with the Corporation’s public-benefit purpose, budget, travel policy, conflict rules, sponsor non-control, provider neutrality, public authority boundary controls, and public-safe claims discipline. Travel may be approved for Board meetings, committee meetings, public authority learning, research, fieldwork, technical workshops, public-good software work, Academy programs, safeguards engagement, lawful fundraising, grant meetings, conferences, controlled-room activities, and Nexus interface activities.
Travel and event expenses shall not be used to provide luxury benefits, disguised compensation, personal benefit, family travel without authorization, political or lobbying activity outside lawful limits, sponsor entertainment, provider inducement, public authority gift violation, procurement influence, finance-adjacent solicitation, certification sale, recognition sale, or public authority access purchase.
Where officers attend events involving sponsors, donors, funders, providers, hosts, public authorities, investors, insurers, lenders, national companies, Project SPVs, media, or enterprise actors, the Corporation shall apply conflict, gift, hospitality, public authority, competition, confidentiality, public-safe claims, and role-separation controls. Travel funded by external parties shall be reviewed for independence, public authority ethics, tax, grant, sponsor non-control, and private benefit concerns before acceptance.
156.12 No Self-Approval. No officer shall approve, authorize, sign, process, reimburse, classify, certify, or close out his or her own compensation, benefits, reimbursements, expenses, advances, travel, event costs, equipment, allowances, severance, bonus, incentive, consulting fees, stipend, fellowship payment, contractor payment, or other economic benefit. No officer shall approve the compensation or reimbursement of a related person, family member, household member, controlled entity, employer, client, sponsor, provider, host, contractor, or other related party without disclosure and independent review.
No self-approval shall occur by indirect means, including:
a) delegating approval to a subordinate under the officer’s control;
b) using a shared account, generic approval, workflow automation, pre-authorization template, AI-generated approval, or repository status to simulate approval;
c) splitting expenses or compensation into smaller payments;
d) using emergency authority without after-action review;
e) using sponsor, donor, funder, provider, host, or partner reimbursement channels;
f) characterizing compensation as reimbursement, stipend, grant, honorarium, award, gift, travel support, in-kind support, or expense when substance indicates compensation or private benefit; or
g) routing payment through an affiliate, contractor, university, laboratory, partner, national company, Project SPV, or external entity to avoid Corporation controls.
A self-approved or indirectly self-approved payment may be suspended, reversed, reclassified, denied, recovered, corrected, disclosed, or referred for legal, tax, Board, or enforcement review.
156.13 No Excess Benefit. The Corporation shall not provide an excess benefit to any officer, director, disqualified person, insider, related party, founder, substantial contributor, sponsor, donor, funder, provider, host, contractor, or other person with influence over the Corporation. An excess benefit includes any compensation, reimbursement, benefit, transfer, use of assets, access right, discount, grant, award, loan, guarantee, allowance, travel support, in-kind benefit, data access, software access, technical asset access, controlled-room access, or other economic value exceeding fair and reasonable value for services rendered or otherwise inconsistent with public-benefit purpose and legal requirements.
The Corporation shall prevent excess benefit by using approval controls, comparability review where appropriate, conflict disclosure, independent approval, documentation, restricted fund tracking, reimbursement controls, expense limits, procurement controls, related-party review, tax review, private benefit review, and corrective records. Where an excess benefit is discovered or suspected, the Corporation shall hold further payments, conduct review, seek correction, require repayment where appropriate, amend records, make tax or regulatory filings where required, impose sanctions or removal where warranted, and preserve records.
No compensation or benefit shall be justified by future fundraising expectations, anticipated sponsorship, projected provider value, public authority access, prospective recognition, prospective finance-readiness, prospective certification, prospective procurement, prospective public visibility, or future Nexus interface value.
156.14 No Private Inurement. No part of the Corporation’s net earnings, assets, revenue, public-good support, grant funds, restricted funds, sponsorship funds, donations, fees, subscriptions, cost recoveries, in-kind contributions, technical assets, datasets, software, repositories, controlled-room access, public authority interfaces, protected knowledge, or other resources shall inure to the benefit of any officer, director, member, founder, sponsor, donor, funder, provider, host, contractor, related party, private person, or private entity except as lawful, reasonable compensation for services actually rendered, lawful reimbursement, or lawful public-benefit program support consistent with the Corporation’s purposes.
Private inurement may arise through direct payment, excessive compensation, disguised compensation, below-market asset transfer, above-market purchase, related-party transaction, preferential access, private use of public-good assets, sponsor control, provider preference, public authority access sale, finance-readiness sale, certification sale, procurement advantage, research outcome purchase, protected knowledge extraction, or other diversion of charitable or public-benefit assets.
The Corporation shall interpret compensation and benefit provisions narrowly where private inurement risk exists. Any ambiguity shall be resolved in favor of public-benefit protection, independent review, record support, and corrective action.
156.15 No Compensation Tied to Sponsor Control, Provider Selection, Public Authority Access, Fundraising Outcome Outside Policy, Finance-Readiness, Recognition, Certification, Procurement, or Regulated Execution. Officer compensation shall not be structured, measured, increased, accelerated, vested, bonused, commissioned, awarded, or continued on the basis of sponsor control, sponsor satisfaction, sponsor renewal, donor control, funder control, provider selection, provider preference, vendor selection, public authority access, public authority adoption, public finance access, investor access, lender access, insurer access, national company participation, Project SPV formation, enterprise execution, public authority procurement, certification, recognition, maturity standing, Docket standing, Grid standing, Nexus-compatible status, finance-readiness, insurance-readiness, bankability, investability, rating, underwriting, lending, securities offering, capital placement, brokerage, finder activity, public finance approval, emergency command, public warning, or any regulated execution outcome.
Fundraising-related compensation, if any, shall be structured only within lawful nonprofit, tax, charitable solicitation, fundraising ethics, private benefit, and Board-approved policy limits. No percentage-based commission, success fee, finder fee, capital placement fee, securities solicitation fee, sponsorship-control fee, grant-success fee, public authority access fee, recognition fee, certification fee, finance-readiness fee, or procurement-success fee shall be paid unless counsel determines it is lawful and the Board expressly approves it within strict public-benefit controls; and in all cases, no compensation may reward prohibited functions.
Compensation metrics may consider lawful performance factors such as stewardship quality, record completeness, compliance, budget discipline, program delivery within non-execution boundaries, evidence integrity, methods quality, public-safe publication discipline, data / AI / cyber compliance, safeguards performance, accessibility, correction responsiveness, internal controls, public-benefit impact, and institutional sustainability, provided that such metrics do not create pressure to overclaim, suppress correction, favor sponsors or providers, compromise public authority boundaries, or convert the Corporation into an execution actor.
156.16 Compensation Disclosure Where Required. The Corporation shall make compensation disclosures where required by federal law, state law, territorial law, tax filings, charitable solicitation rules, grant agreements, donor restrictions, audit requirements, public filings, public authority agreements, or Board-approved transparency policies. Compensation disclosures shall be accurate, complete, timely, and consistent with privacy, safety, confidentiality, employment, tax, and legal requirements.
Compensation disclosure may include, as applicable, disclosures in tax returns, annual reports, audited or reviewed financial statements, grant reports, state filings, charitable solicitation filings, public-safe governance summaries, Board records, committee records, conflict records, and related-party transaction records. Public disclosures shall use controlled vocabulary and shall not imply that compensation confers public authority status, finance-readiness authority, certification authority, procurement authority, recognition authority, Nexus system control, or enterprise execution authority.
The Corporation may withhold, redact, aggregate, or limit compensation information where lawful and necessary to protect privacy, safety, cybersecurity, protected knowledge, legal privilege, personnel confidentiality, or other legitimate interests; provided that such limitation shall not be used to conceal private inurement, excess benefit, related-party abuse, sponsor control, provider preference, or unlawful conduct.
156.17 Compensation, Reimbursement, Benefit, and Expense Records. The Corporation shall maintain Compensation, Reimbursement, Benefit, and Expense Records sufficient to demonstrate lawful authority, reasonableness, public-benefit purpose, budget authority, fund restriction compliance, tax compliance, employment classification, conflict disclosure, independent review, approval, payment, reporting, correction, and closeout. These records shall be maintained in the official repository or other approved controlled repository, subject to confidentiality, privacy, privilege, tax, employment, legal hold, retention, audit, cybersecurity, and access controls.
Compensation, Reimbursement, Benefit, and Expense Records shall include, as applicable:
a) officer appointment records, role descriptions, employment agreements, contractor agreements, consulting agreements, offer letters, compensation schedules, benefit schedules, stipend records, fellowship records, amendments, renewals, suspensions, terminations, and closeout records;
b) Board approvals, committee approvals, delegated approvals, disinterested approval records, recusal records, written consents, minutes, resolutions, authority matrix records, delegation matrix records, budget approvals, and fund-source approvals;
c) reasonableness reviews, comparability data, compensation surveys, market notes, role analyses, public-benefit justifications, internal equity notes, tax reviews, private benefit reviews, inurement reviews, excess benefit reviews, and related-party transaction reviews;
d) payroll records, contractor payment records, tax withholding records, information return records, benefit records, reimbursement records, expense reports, invoices, receipts, credit card records, travel approvals, event approvals, accountable plan records, repayment records, and reclassification records;
e) restricted fund records, grant records, donor restriction records, sponsorship records, public-good support records, cost-recovery records, subscription records, fee records, and allocation records;
f) conflict disclosures, annual disclosures, event-based disclosures, related-person records, sponsor relationship records, provider relationship records, donor and funder relationship records, host relationship records, public authority relationship records, university and laboratory relationship records, national company and Project SPV relationship records, and other affiliation records relevant to compensation review;
g) external advisor reports, counsel review records, tax advisor records, accountant records, auditor records, compensation consultant records, employment counsel records, and benefits advisor records;
h) compensation disclosures, public filings, tax filings, charitable solicitation filings, grant reports, donor reports, Board reports, public-safe summaries where approved, and corrections to disclosures;
i) exceptions requested, exceptions refused, exceptions approved where lawful, questioned expenses, denied reimbursements, repayments, corrective payments, reclassifications, holds, suspensions, investigations, corrective actions, enforcement actions, and closeout records; and
j) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that officer compensation and reimbursement are permitted only as disciplined, reasonable, lawful, public-benefit-aligned institutional costs. Compensation shall never become a distribution of public-good assets, an excess benefit, a private inurement channel, a sponsor-control mechanism, a provider-selection incentive, a public authority access sale, a finance-readiness sale, a recognition sale, a certification sale, a procurement advantage, or a reward for regulated execution. Every officer compensation, benefit, reimbursement, and expense arrangement shall be authorized, reasonable, independently reviewed where required, conflict-managed, budget-supported, tax-aware, records-supported, and correctionable.
Section 157. Officer Reporting Duties to Board and Committees
157.1 Reporting Purpose. Officer reporting is a core governance control of the Corporation. Each officer shall report to the Board, to the Chair, to the President, to the Executive Director or Chief Executive Officer where applicable, to the Secretary, to the Treasurer or Chief Financial Officer, to a committee, or to another competent authority as required by law, the Articles or Certificate, this Bylaw, Board resolution, delegation, policy, authority matrix, committee charter, budget, grant instrument, restricted fund instrument, support agreement, public authority interface instrument, data / AI / cyber control, safeguards protocol, or other governing record.
The purpose of officer reporting is to ensure that the Board and any relevant committee can exercise informed oversight over mission lock, public-benefit purpose, nonprofit character, non-distribution, tax-exempt or tax-exempt-compatible status, public-good stewardship, evidence integrity, methods integrity, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, public authority learning, all-states-and-territories operation, North America anchor responsibilities, Nexus role separation, non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, privacy, civil rights, accessibility, community safeguards, Tribal and Indigenous protocol respect, protected knowledge, validity-by-record, correctionability, and institutional continuity.
Officer reporting shall be factual, timely, complete for its purpose, records-supported, risk-aware, public-safe where public-facing, and candid. No officer shall omit, soften, delay, reframe, or bury material information to avoid Board scrutiny, committee scrutiny, counsel review, compliance review, public-safe correction, donor or sponsor discomfort, provider objection, public authority sensitivity, program inconvenience, technical embarrassment, reputational concern, or operational delay.
157.2 Regular Board Reports. Each principal officer shall provide regular reports to the Board at intervals established by the Board, by policy, by the annual governance calendar, by committee charter, by delegation, or by the Chair. Regular Board reports shall be structured to permit the Board to assess institutional condition, mission performance, legal compliance, financial health, risk exposure, program progress, public-benefit delivery, internal controls, boundary discipline, and correction needs.
Regular Board reports may include, as applicable:
a) executive summary, reporting period, responsible officer, version, status, and matters requiring Board attention;
b) progress against Board-approved strategy, annual plan, budget, mission priorities, public-benefit objectives, and approved programs;
c) legal, tax, nonprofit, charitable solicitation, state qualification, grant compliance, lobbying, public authority, privacy, AI, cyber, sanctions, export-control, controlled-technology, competition, employment, civil rights, accessibility, and safeguards compliance matters;
d) financial position, budget variance, restricted fund status, grants, donations, sponsorships, subscriptions, fees, in-kind support, cost recovery, reserves, obligations, and material financial risks;
e) research, evidence, methods, observability, ontology, Truth Engine, public-good software, technical baseline, repository, secure-release, model, dataset, benchmark, and public-safe publication activity;
f) public authority learning, regulator-listening, public finance reader, emergency-management participant, public infrastructure operator, controlled-room, clean-room, evidence-room, data-room, and no-download-room activity;
g) Nexus interface activity involving 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, universities, laboratories, public authorities, communities, and enterprise-stack actors; and
h) decisions requested, risks escalated, conflicts disclosed, incidents reported, corrections required, policies needing amendment, records needing completion, and matters requiring Board reserved approval.
A regular Board report shall not substitute for immediate escalation of urgent, material, regulated-perimeter, public authority, finance-boundary, data / AI / cyber, protected knowledge, safeguards, public-safe publication, or institutional continuity risks.
157.3 Officer Dashboards Subject to Public-Safe and Confidentiality Controls. The Corporation may use officer dashboards, management dashboards, Board dashboards, risk dashboards, finance dashboards, evidence dashboards, methods dashboards, observability dashboards, data / AI / cyber dashboards, publication dashboards, correction dashboards, support dashboards, public authority interface dashboards, and Nexus interface dashboards to support reporting. Dashboards shall be treated as reporting tools, not as self-executing institutional decisions.
Officer dashboards shall be governed by access controls, data classification, public-safe review, privacy controls, AI-use controls, cybersecurity controls, confidentiality controls, public authority restrictions, finance-boundary restrictions, protected knowledge safeguards, sponsor and provider neutrality rules, controlled vocabulary, versioning, audit trails, and correctionability. A dashboard shall identify, where material, source, update cadence, custodian, data class, confidence level, known limitations, stale-data risks, automated-output risks, and human review status.
No dashboard shall be represented as a public warning, emergency command, public authority decision, regulatory finding, certification, accreditation, procurement approval, recognition, maturity standing, finance-readiness determination, investment recommendation, rating, insurance-readiness determination, provider preference, sponsor entitlement, or operational instruction. Where dashboard information is incomplete, provisional, disputed, stale, automated, model-derived, or safeguards-sensitive, the dashboard shall carry appropriate limitation language and shall be escalated for human review before material reliance.
157.4 Strategy Implementation Reports. The President, Executive Director or Chief Executive Officer where applicable, Chief Operating Officer where applicable, and any other officer designated by the Board shall report on implementation of Board-approved strategy, annual plans, major initiatives, institutional priorities, all-states-and-territories posture, North America anchor role, and Nexus interface plans. Strategy implementation reporting shall distinguish approved strategy, proposed strategy, exploratory work, operational work, deferred work, blocked work, and work requiring Board approval.
Strategy implementation reports shall address progress against public-benefit objectives, evidence and methods objectives, public-good software objectives, technical baseline objectives, public authority learning objectives, safeguards objectives, financial sustainability objectives, capacity-building objectives, institutional maturity objectives, and role-separation objectives. Reports shall identify material deviations, delays, dependencies, constraints, funding gaps, staffing gaps, legal barriers, state or territorial localization needs, public authority boundary concerns, sponsor or provider capture risks, data / AI / cyber constraints, protected knowledge constraints, and correction needs.
No officer may implement strategy in a manner that silently changes the Corporation’s mission, legal status, nonprofit character, tax posture, non-execution boundary, public authority role, finance role, certification role, procurement role, provider-neutrality posture, sponsor non-control posture, or relationship to GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, consortiums, national companies, Project SPVs, providers, sponsors, hosts, public authorities, or enterprise-stack actors. Any such change shall be escalated as a Board reserved matter.
157.5 Budget and Finance Reports. The Treasurer or Chief Financial Officer, and any officer with delegated financial authority, shall report on financial position, budget performance, cash position, reserves, restricted funds, unrestricted funds, grants, donations, sponsorships, subscriptions, fees, cost recovery, in-kind contributions, accounts payable, accounts receivable, commitments, obligations, bank accounts, reconciliations, tax filings, audit or review activity, internal controls, fraud risks, expense trends, and material financial exposures.
Budget and finance reports shall identify, as applicable:
a) budget-to-actual results;
b) restricted fund compliance;
c) grant condition compliance;
d) donor and sponsor restriction compliance;
e) revenue classification and tax treatment;
f) reimbursement and expense trends;
g) related-party payments;
h) compensation and benefit matters requiring review;
i) procurement or contracting thresholds reached;
j) support concentration risks;
k) liquidity and continuity risks;
l) private benefit, inurement, excess benefit, or financial capture risks;
m) financial controls exceptions;
n) questioned costs, disallowed costs, late filings, reconciliation issues, or audit findings; and
o) financial matters requiring Board approval, committee review, counsel review, tax review, or corrective action.
Budget and finance reporting shall not include investment advice, securities recommendations, capital placement activity, lending recommendations, insurance placement advice, underwriting opinion, rating opinion, public finance approval, or finance-readiness determination. Financial reports shall preserve the Corporation’s role as a nonprofit steward of its own funds and public-good support, not as a capital intermediary or regulated financial actor.
157.6 Research and Evidence Reports. The Chief Evidence Officer, Chief Research Officer, Chief Methods Officer, and other designated officers shall report on research programs, evidence doctrine, evidence intake, source lineage, provenance, validation, verification, confidence, uncertainty, disputed evidence, failed signals, spoof indicators, evidence challenges, research ethics, peer review, publication integrity, public-safe reporting, evidence corrections, method corrections, and evidentiary support to Docket, Grid, GRF-facing inputs, GRA-facing technical inputs, Nexus Observatory, Nexus Standards, public authority learning, and public-good technical baselines.
Research and evidence reports shall distinguish evidence from recognition, methods from certification, inputs from determinations, learning from public authority action, and technical support from execution. Each report shall identify material limitations, excluded scope, confidence levels, known uncertainty, source restrictions, data rights, privacy limits, protected knowledge restrictions, community safeguards, public-safe mapping limits, AI-use disclosures, sponsor or provider involvement, public authority data contributions, conflicts, and correction pathways.
No research or evidence report shall overstate findings, conceal uncertainty, suppress adverse evidence, omit sponsor or provider influence, convert evidence support into recognition, convert technical inputs into finance-readiness, convert public authority learning into official action, or convert methods into certification. Where a material evidence error is discovered, the responsible officer shall escalate promptly and initiate correction, supersession, withdrawal, retraction, takedown, or public-safe clarification as appropriate.
157.7 Methods and Technical Reports. The Chief Methods Officer, Chief Technology Officer, Chief Public-Good Software and Technical Assets Officer, Chief Data, AI, and Cyber Officer, and other designated officers shall report on methods, technical profiles, public-good software, open technical baselines, repositories, APIs, SDKs, schemas, dashboards, reference architectures, test harnesses, gold vectors, negative tests, benchmark libraries, model cards, dataset cards, system cards, benchmark cards, secure release, SBOMs, artifact signing, provenance, vulnerability handling, dependency review, licensing, IP chain-of-title, anti-enclosure controls, and technical asset retirement.
Methods and technical reports shall identify version status, custodian, repository location, approval status, access class, publication class, release class, limitation language, security posture, licensing posture, data dependencies, AI dependencies, cyber dependencies, public authority sensitivities, export-control sensitivities, controlled-technology sensitivities, and correction status. Reports involving AI-RAN, O-RAN, DePIN, DLT, blockchain, digital twins, sovereign compute, HPC, cyber-physical systems, robotics, drones, sensors, geospatial systems, Earth observation, biosecurity, climate, energy, water, food, health, disaster, telecom, supply chain, advanced manufacturing, semiconductors, or other exponential technologies shall include boundary notes where technical outputs may be misunderstood as operational authority.
No technical report shall imply that a model, dashboard, signal, proof receipt, ledger entry, protocol profile, technical baseline, software release, repository label, benchmark score, or automated output constitutes public authority action, certification, procurement approval, recognition, finance-readiness, rating, public warning, emergency command, or operational instruction unless a competent authority has separately and lawfully created such status and the record identifies that authority.
157.8 Data / AI / Cyber / Privacy Reports. The Chief Data, AI, and Cyber Officer, and any officer with delegated data, AI, cyber, privacy, secure compute, model, repository, or technical access authority, shall report on data governance, privacy, cybersecurity, AI governance, model registers, inference records, compute workload records, access controls, identity controls, key and credential controls, repository security, secure development, vulnerability management, incident response, backup, disaster recovery, business continuity, public authority data controls, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, rights-bearing data, community-protected data, Tribal and Indigenous data, protected knowledge, and cross-border transfer controls.
Data / AI / cyber / privacy reports shall identify, as applicable:
a) access grants, access revocations, privileged accounts, role changes, data-room activity, controlled-room activity, repository access changes, model access changes, and no-download room compliance;
b) approved AI systems, prohibited AI systems, material AI uses, agentic AI controls, model evaluations, model limitations, bias review, civil-rights review, public-safe review, human review, and correction pathways;
c) cybersecurity posture, vulnerabilities, incidents, attempted incidents, resolved incidents, third-party security risks, vendor security reviews, cloud security, compute security, credential hygiene, and continuity readiness;
d) privacy matters, personal information, sensitive information, retention, minimization, de-identification, aggregation, redaction, consent, data subject or participant requests where applicable, and breach notification concerns;
e) cross-border, state, territorial, Tribal, public authority, export-control, sanctions, controlled-technology, and national security sensitivity concerns; and
f) matters requiring Board, committee, counsel, data protection, cybersecurity, safeguards, public authority, or public-safe publication review.
No officer shall delay data / AI / cyber / privacy reporting where a breach, suspected breach, AI misuse, protected knowledge exposure, credential compromise, unauthorized access, public authority data issue, or infrastructure-sensitive exposure is reasonably suspected.
157.9 Public Authority Interface Reports. The Chief Public Authority Learning Officer, President, Executive Director or Chief Executive Officer where applicable, Chief Legal, Compliance, and Risk Officer where applicable, and any officer with delegated public authority interface responsibilities shall report on public authority interactions involving federal, state, territorial, District of Columbia, Tribal, Indigenous, local, county, municipal, metropolitan, port, utility, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, infrastructure, public finance, regulator, grant-making, procurement, public university, public laboratory, and cross-border public authority contexts.
Public authority interface reports shall classify each material public authority interaction by capacity, including official-capacity participation, observer status, regulator-listening status, public finance reader status, emergency-management participant status, public infrastructure operator status, simulation participant status, data contributor status, public authority room participant status, or other approved capacity. Reports shall identify public authority references, consent or authorization where required, public records implications, open meetings implications, procurement integrity issues, government ethics issues, gift issues, lobbying issues, grant compliance issues, public authority data rules, confidentiality, non-endorsement language, and public-safe claim controls.
No public authority interface report shall imply delegation, public warning authority, emergency command authority, regulatory approval, procurement approval, public finance approval, funding approval, sovereign obligation, public-private partnership, official adoption, certification, recognition, provider preference, or finance-readiness. Where public authority confusion arises, the officer shall escalate, apply limitation language, hold publication, restrict materials, seek clarification, and correct records.
157.10 Safeguards and Protected Knowledge Reports. The Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer, Chief Research Officer, Chief Data, AI, and Cyber Officer, and any officer with delegated safeguards authority shall report on civil rights, accessibility, community safeguards, Tribal and Indigenous protocols, Indigenous data safeguards, local and territorial knowledge, cultural and environmental knowledge, protected knowledge, public-safe mapping, vulnerable and remote community safeguards, consent and non-consent, attribution, withdrawal, restriction, grievance, remedy, protected participation, non-retaliation, do-no-harm review, and stop-the-line matters.
Safeguards and protected knowledge reports shall identify, as applicable:
a) safeguards reviews completed, pending, refused, escalated, or requiring Board attention;
b) protected knowledge restrictions, consent limits, non-consent records, withdrawal records, attribution limits, publication restrictions, and access restrictions;
c) public-safe mapping concerns, geospatial sensitivity, community exposure risk, infrastructure exposure risk, health-sensitive risk, public safety risk, and de-identification or aggregation decisions;
d) accessibility issues, accommodation requests, participation barriers, civil-rights concerns, discrimination concerns, harassment, retaliation, grievance matters, remedy pathways, and protected participation concerns;
e) sponsor, provider, donor, funder, host, public authority, university, laboratory, or institutional pressure to extract, publish, commercialize, reframe, suppress, or disclose protected knowledge; and
f) stop-the-line decisions, holds, quarantines, restrictions, corrections, withdrawals, takedowns, and public-safe clarifications.
Safeguards reporting shall respect confidentiality, privacy, safety, privilege, and protected participation. Reporting discipline shall not be used to expose protected persons, communities, or knowledge holders to retaliation, stigma, surveillance, commercial extraction, public authority misuse, or public harm.
157.11 Grant, Donation, Sponsorship, In-Kind, and Support Reports. The Chief Development, Grants, and Public-Good Support Officer, Treasurer or Chief Financial Officer, President, Executive Director or Chief Executive Officer where applicable, and any officer with delegated support authority shall report on grants, donations, sponsorships, in-kind contributions, restricted funds, unrestricted support, public-good infrastructure support, subscriptions, fees, cost recovery, fellowships, scholarships, awards, challenge support, and other support relationships.
Support reports shall identify source, amount or value, restrictions, purpose, benefit schedule, acknowledgment language, tax treatment, receipting status where applicable, grant conditions, reporting obligations, public acknowledgment controls, sponsor benefits, donor restrictions, funder expectations, in-kind dependencies, conflicts, related-party issues, sanctions and export-control review, data / AI / cyber review, public authority boundary review, finance-boundary review, certification-boundary review, procurement-neutrality review, provider-neutrality review, safeguards review, and anti-capture review.
No support report shall frame support as buying governance control, research outcome, publication treatment, public authority access, provider preference, recognition, maturity standing, Docket standing, Grid standing, Nexus-compatible status, finance-readiness, insurance-readiness, certification, procurement advantage, technical baseline inclusion, software feature inclusion, dashboard placement, or correction avoidance. Where support creates capture risk, the officer shall recommend refusal, restriction, return, termination, ring-fencing, disclosure, public-safe clarification, or Board review.
157.12 Risk and Compliance Reports. The Chief Legal, Compliance, and Risk Officer where approved, Chief Operating Officer where approved, Treasurer or Chief Financial Officer, Secretary, and any officer with delegated risk or compliance authority shall report on the Corporation’s risk register, issue register, control register, compliance register, incident register, legal matters, tax matters, nonprofit compliance, corporate status, filings, state qualification, charitable solicitation, grant compliance, lobbying, political activity, government ethics, procurement integrity, sanctions, export-control, controlled technology, national security sensitivity, competition and antitrust, professional boundaries, employment, contractor classification, workplace matters, insurance, internal controls, investigations, and enforcement matters.
Risk and compliance reports shall classify risks by severity, likelihood, urgency, owner, status, control maturity, required escalation, mitigation plan, deadline, residual risk, and Board attention needed. Reports shall identify whether risks implicate non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, recognition boundaries, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, protected knowledge, public-safe publication, validity-by-record, correctionability, legal separateness, tax status, or public reputation.
No officer shall treat unresolved legal ambiguity, regulatory perimeter ambiguity, public authority confusion, finance-boundary risk, certification-boundary risk, or protected knowledge risk as ordinary operational risk. Such matters shall be escalated for counsel, compliance, committee, or Board review as appropriate.
157.13 Incident Reports. Each officer shall promptly report incidents within the officer’s knowledge, authority, or area of responsibility. Incidents include cybersecurity incidents, data incidents, privacy incidents, AI incidents, model incidents, repository incidents, key or credential incidents, controlled-room incidents, public authority confusion incidents, public-safe publication incidents, evidence integrity incidents, research integrity incidents, finance-boundary incidents, certification-boundary incidents, procurement-neutrality incidents, recognition-boundary incidents, provider-neutrality incidents, sponsor-control incidents, sanctions incidents, export-control incidents, controlled-technology incidents, competition incidents, fraud incidents, financial control incidents, harassment incidents, retaliation incidents, civil-rights incidents, accessibility incidents, protected knowledge incidents, public-safe mapping incidents, and other material governance or operational failures.
Incident reports shall include, as available and appropriate:
a) incident title, date, time, location, system, room, repository, program, officer owner, and current status;
b) facts known, facts uncertain, affected persons, affected records, affected systems, affected data, affected publications, affected public authority interfaces, affected sponsors or providers, affected communities, and affected Nexus interfaces;
c) immediate containment actions, holds, quarantines, access restrictions, credential revocations, publication freezes, implementation freezes, controlled-room lockdowns, technical isolation, and evidence preservation;
d) legal, regulatory, contractual, grant, donor, sponsor, public authority, privacy, cyber, safeguards, or public notification triggers;
e) privilege and confidentiality posture;
f) correction, supersession, withdrawal, takedown, retraction, archive, notice, or remediation pathway; and
g) Board, committee, counsel, public authority, regulator, funder, donor, sponsor, provider, affected person, or community notification recommendations.
Incident reporting shall be prompt even when facts are incomplete. The report may be updated as facts develop. No officer shall delay reporting to protect reputation, avoid criticism, preserve a funding relationship, preserve sponsor or provider confidence, avoid Board review, or wait for perfect certainty.
157.14 Correction and Supersession Reports. Officers shall report on corrections, proposed corrections, supersessions, withdrawals, retractions, takedowns, public-safe clarifications, controlled clarifications, errata, archive actions, register corrections, repository corrections, data corrections, model corrections, software corrections, dashboard corrections, map corrections, public authority reference corrections, donor or sponsor acknowledgment corrections, evidence corrections, method corrections, ontology corrections, and public claim corrections.
Correction and supersession reports shall identify the defective record, output, claim, dataset, software asset, model, publication, dashboard, map, notice, register entry, proof receipt, room material, or public authority reference; the nature of the defect; the cause; the prior version; the correction authority; the affected audience; reliance risk; public-safe risk; public authority risk; finance-boundary risk; certification-boundary risk; safeguards risk; protected knowledge risk; data / AI / cyber risk; and the correction pathway.
Correction reporting shall preserve historical traceability. No correction shall silently erase prior records, conceal error, suppress dissent, protect sponsors or providers, avoid public authority embarrassment, avoid finance-boundary consequences, avoid certification-boundary consequences, or avoid accountability. Each correction report shall distinguish clerical correction, substantive correction, limitation clarification, supersession, withdrawal, retraction, takedown, archive, and disputed-evidence status.
157.15 Nexus Interface Reports. Officers with Nexus interface responsibilities shall report on interfaces with 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 Nexus Consortium, Regional Nexus Consortiums, National Nexus Consortiums, National Working Groups, National Consortium Companies, Project SPVs, qualified enterprise providers, sponsors, hosts, public authorities, universities, laboratories, communities, and enterprise-stack actors.
Nexus interface reports shall identify role, capacity, instrument, authority source, records exchanged, outputs delivered, limitations, interface risks, compatibility notes, divergence logs, public-good stack / enterprise stack separation issues, GCRI / GRF / GRA role-separation issues, public authority boundary issues, finance-boundary issues, certification-boundary issues, procurement-neutrality issues, provider-neutrality issues, sponsor non-control issues, data / AI / cyber issues, safeguards issues, and correction pathways.
No Nexus interface report shall imply that the Corporation controls Nexus Network, GRF, GRA, Nexus Standards, public authorities, consortiums, national companies, Project SPVs, providers, sponsors, hosts, or enterprise execution actors. Interface reporting shall preserve separateness, non-agency, non-merger, non-shared treasury, non-shared liability, and non-substitution.
157.16 All-States-and-Territories and North America Interface Reports. Officers responsible for United States state, territorial, District of Columbia, Tribal, local, and North America interfaces shall report on state qualifications, territorial qualifications, charitable solicitation registrations, tax registrations, employment registrations, contractor arrangements, public authority interfaces, data / AI / cyber localization, privacy localization, public records considerations, open meetings considerations, grant conditions, procurement integrity, lobbying rules, government ethics, civil rights, accessibility, community safeguards, Tribal and Indigenous protocol respect, and cross-border legal issues.
All-states-and-territories reports shall distinguish lawful operations, exploratory contacts, public authority learning, controlled-room engagement, state-specific localization, territorial localization, Tribal-interface localization, North America interface activity, and cross-border coordination. Reports shall identify jurisdictions requiring qualification, registration, legal review, tax review, data review, AI review, cyber review, public authority review, safeguards review, or publication limitations.
North America interface reports shall address coordination with GCRI Canada and other lawful North America interfaces without implying treaty authority, sovereign authority, regional regulator status, public finance authority, emergency command authority, procurement authority, certification authority, recognition authority, finance-readiness authority, or enterprise execution authority. Where conflict-of-law concerns arise, officers shall recommend hold, restriction, compartmentalization, separate instrument, compliant routing, or Board review.
157.17 Committee Reports. Officers assigned to support or report to committees shall provide committee reports consistent with the relevant committee charter, authority, scope, access class, confidentiality class, and reporting calendar. Committee reports shall be sufficient to support informed review, recommendation, decision where delegated, escalation, ratification where required, and Board oversight.
Committee reports shall identify the matter presented, authority source, record basis, conflicts, recusals, data / AI / cyber issues, public authority issues, finance-boundary issues, certification-boundary issues, procurement-neutrality issues, recognition-boundary issues, provider-neutrality issues, sponsor non-control issues, safeguards issues, protected knowledge issues, competition issues, sanctions or export-control issues, controlled-technology issues, public-safe publication issues, and recommended action.
Where a committee lacks authority to decide a matter, the officer report shall label the matter as advisory, recommendation-only, review-only, or escalation-only. No officer shall use a committee report to bypass Board reserved matters, create informal approval, convert committee consensus into legal authority, or treat advisory support as certification, recognition, finance-readiness, procurement approval, public authority action, or enterprise execution authority.
157.18 Escalation Reports. An officer shall submit an escalation report when a matter exceeds delegated authority, approaches a Board reserved matter, involves legal ambiguity, creates regulated-perimeter risk, threatens mission lock, affects nonprofit or tax status, creates public authority confusion, creates finance-boundary risk, creates certification or procurement risk, threatens provider neutrality, threatens sponsor non-control, implicates data / AI / cyber risks, implicates protected knowledge or community safeguards, threatens public-safe publication, involves a material conflict, creates reputational risk, exposes records integrity issues, requires correction, or otherwise warrants Board, committee, counsel, compliance, safeguards, or technical review.
Escalation reports shall be direct and shall not minimize materiality. The report shall identify the issue, affected authority, facts known, facts uncertain, immediate action taken, action requested, deadline, legal or policy source, risks if delayed, recommended hold or quarantine, required reviewers, public-safe communication needs, and proposed records. Escalation may be made orally in urgent circumstances but shall be reduced to a written or otherwise durable record as soon as practicable.
An officer who is uncertain whether escalation is required shall escalate. No operational convenience, public authority pressure, sponsor pressure, provider pressure, donor pressure, grant deadline, publication deadline, event deadline, technical deadline, fundraising concern, relationship concern, media concern, or reputational concern shall justify failure to escalate.
157.19 Officer Reporting Records. The Corporation shall maintain Officer Reporting Records sufficient to demonstrate that officers report accurately, timely, candidly, and within their duties to the Board, committees, counsel, compliance functions, auditors, tax advisors, data protection reviewers, cybersecurity reviewers, safeguards reviewers, public-safe publication reviewers, and other competent bodies. Officer Reporting Records shall be maintained in the official repository or other approved controlled repository, subject to confidentiality, privilege, privacy, public authority, data / AI / cyber, protected knowledge, employment, tax, legal hold, retention, audit, and access controls.
Officer Reporting Records shall include, as applicable:
a) regular Board reports, committee reports, dashboards, strategy implementation reports, budget and finance reports, research and evidence reports, methods and technical reports, data / AI / cyber / privacy reports, public authority interface reports, safeguards and protected knowledge reports, grant, donation, sponsorship, in-kind and support reports, risk and compliance reports, incident reports, correction and supersession reports, Nexus interface reports, all-states-and-territories reports, North America interface reports, and escalation reports;
b) report titles, versions, reporting periods, responsible officers, recipients, circulation lists, access classes, publication classes, confidentiality classes, data classes, public authority classes, safeguards classes, repository locations, and supersession status;
c) supporting evidence, source materials, data sources, dashboard exports, registers, logs, minutes, resolutions, action items, risk register entries, issue register entries, control register entries, incident register entries, correction register entries, proof receipts, technical records, financial records, grant records, support records, conflict records, public authority capacity records, and safeguards records;
d) conflicts disclosed, recusals recorded, minority views, dissent notes where permitted, limitations, uncertainties, stale-data notices, disputed-evidence notices, AI-use disclosures, model limitations, human review records, public-safe notices, and non-reliance language;
e) Board questions, committee questions, officer responses, counsel responses, compliance responses, data / AI / cyber responses, safeguards responses, public authority clarifications, follow-up actions, deadlines, responsible owners, and closure records;
f) urgent escalations, oral escalations reduced to record, holds, stops, quarantines, access restrictions, publication freezes, implementation freezes, controlled-room lockdowns, technical isolation, incident containment, emergency reports, ratification records, and sunset records;
g) corrections to reports, corrected reports, superseded reports, withdrawn reports, restricted reports, reclassified reports, archived reports, and public or controlled clarifications; and
h) responsible owner, custodian, repository location, access class, publication class, retention class, legal hold status, deletion status, archive status, review date, correction history, and metadata.
The governing rule of this Section is that officer reporting is not ceremonial. It is the Board’s principal operating window into the Corporation’s legal health, mission fidelity, technical integrity, financial stewardship, public authority boundary discipline, finance-boundary discipline, safeguards posture, Nexus role separation, and correctionability. Officers shall report what the institution needs to know, not merely what is convenient to say. Reports shall be truthful, records-supported, timely, bounded, risk-aware, public-safe where relevant, and correctionable. No officer report may be used to conceal risk, manufacture authority, bypass Board reserved matters, inflate public claims, imply public authority action, imply finance-readiness, imply certification, imply procurement approval, favor a provider, satisfy a sponsor, suppress protected knowledge concerns, or avoid correction.
Section 158. Officer Records, Registers, Certifications, and Record Integrity
158.1 Officer Record Requirement. The Corporation shall maintain officer records sufficient to demonstrate that each officer is lawfully appointed, properly authorized, appropriately screened, conflict-reviewed, delegation-bounded, trained, records-supported, supervised where applicable, removable where required, and accountable to the Board, applicable law, the Articles or Certificate, this Bylaw, Board resolutions, committee charters, policies, delegations, authority matrices, budgets, public-benefit purposes, nonprofit character, tax-exempt or tax-exempt-compatible obligations, non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, and correctionability.
Officer records shall not be treated as mere administrative files. They shall constitute the institutional memory by which the Corporation proves lawful officer authority, prevents unauthorized action, preserves delegation discipline, distinguishes titles from powers, protects legal separateness, supports audits and reviews, enables continuity, permits correction, and prevents authority inflation. The Corporation shall maintain officer records in the official repository or other approved controlled repository, subject to confidentiality, privilege, privacy, employment, tax, cybersecurity, public authority, protected knowledge, legal hold, retention, access, sealing, archival, and secure disposal controls.
No officer title, biography, website listing, email signature, public statement, repository permission, dashboard role, public authority contact, sponsor relationship, provider relationship, committee role, technical leadership role, Nexus interface role, or operational practice shall be treated as evidence of officer authority unless supported by a competent appointment record, delegation record, authority matrix entry, or other governing record.
158.2 Appointment Records. The Corporation shall maintain appointment records for each officer. Appointment records shall identify the officer’s legal name, title, office, appointing authority, appointment date, effective date, term where applicable, reporting line, authority source, approval record, eligibility review, consent to serve, acknowledgment of duties, conflict disclosure, independence review where required, compensation status, employment or contractor classification where applicable, and any conditions, limitations, restrictions, or review cycles applicable to the office.
Appointment records shall include, as applicable:
a) Board resolutions, written consents, minutes, incorporator records where applicable, delegated appointment records, officer appointment forms, offer letters, employment agreements, contractor agreements, consulting agreements, fellowship agreements, advisor agreements, role descriptions, and acceptance instruments;
b) fit-and-proper review records, integrity review records, sanctions screening records, export-control screening records, controlled-technology screening records, public authority boundary screening records, finance-boundary screening records, certification-boundary screening records, procurement-neutrality screening records, provider-neutrality screening records, sponsor non-control screening records, data / AI / cyber eligibility records, research integrity eligibility records, safeguards eligibility records, and conflict records;
c) required acknowledgments of this Bylaw, mission lock, public-benefit purpose, nonprofit character, non-execution, GCRI / GRF / GRA role separation, public-good stack / enterprise stack separation, public authority boundary, finance boundary, certification boundary, procurement neutrality, provider neutrality, sponsor non-control, controlled vocabulary, public-safe claims discipline, data / AI / cyber duties, safeguards duties, confidentiality, validity-by-record, correctionability, and non-retaliation; and
d) records of appointment conditions, acting status, interim status, limited authority, probation, required training, recusal obligations, access limitations, supervision conditions, review date, renewal date, and termination date.
An officer appointment shall not be inferred from performance of work, public description, program leadership, technical authorship, repository control, funding role, public authority relationship, or participation in a Nexus interface. Appointment requires a competent record.
158.3 Delegation Records. The Corporation shall maintain delegation records for each officer and for each material delegation made by or to an officer. Delegation records shall identify the delegating authority, delegate, office, scope, purpose, duration, effective date, expiration date, budget limit, contract limit, signing authority, publication authority, data access authority, AI-use authority, model approval authority, repository authority, software release authority, controlled-room authority, public authority interface authority, correction authority, emergency authority, conditions, exclusions, and revocation pathway.
Delegation records shall distinguish general managerial responsibility from authority to bind the Corporation. They shall identify which matters are Board reserved, officer reserved, committee-reviewed, counsel-reviewed, compliance-reviewed, safeguards-reviewed, data / AI / cyber-reviewed, public authority-reviewed, or prohibited. No delegation shall be read to authorize:
a) amendment of this Bylaw, the Articles or Certificate, mission lock, public-benefit purpose, nonprofit character, tax status, non-execution boundary, GCRI / GRF / GRA role separation, public-good stack / enterprise stack separation, or Board reserved matters;
b) public authority action, public warning, emergency command, regulatory approval, public finance approval, procurement approval, certification, recognition, rating, finance-readiness, insurance-readiness, securities solicitation, brokerage, lending, underwriting, insurance placement, investment advice, provider preference, sponsor control, or enterprise execution;
c) data access, AI use, model approval, repository access, software release, controlled-room admission, public-safe publication, protected knowledge disclosure, or public authority reference outside the recorded authority and review pathway; or
d) delegation of authority to a subordinate, contractor, advisor, sponsor, provider, host, public authority participant, national company, Project SPV, Nexus actor, or enterprise actor where prohibited by law, this Bylaw, policy, conflict controls, or the delegation instrument.
A delegation shall be revocable, reviewable, records-supported, and correctionable. A stale, superseded, withdrawn, expired, or orally assumed delegation shall not confer current authority.
158.4 Authority Matrix Records. The Corporation shall maintain authority matrix records identifying the current and historical authority of officers, including signature authority, banking authority, spending authority, procurement authority, contracting authority, grant agreement authority, donation agreement authority, sponsorship agreement authority, in-kind contribution agreement authority, employment and contractor engagement authority, publication authority, public statement authority, public authority reference authority, data access authority, AI-use authority, model approval authority, repository access authority, software release authority, controlled-room admission authority, incident response authority, correction authority, and emergency authority.
Authority matrix records shall identify thresholds, required co-approvals, required reviews, prohibited actions, escalation triggers, delegated substitutes, acting officers, separation-of-duty requirements, conflict-recusal effects, access restrictions, and records required for action. Where authority differs by state, territory, District of Columbia context, Tribal or Indigenous interface, public authority capacity, North America interface, cross-border context, data class, publication class, risk class, fund source, sponsor restriction, provider involvement, grant condition, or controlled-room class, the matrix shall identify the applicable limitation.
No officer shall rely on an outdated authority matrix. Where authority is uncertain, the narrower, more protective, and less authority-inflating reading shall apply pending review. A matrix entry shall guide authority, but it shall not override law, the Articles or Certificate, this Bylaw, Board reserved powers, conflict rules, safeguards, data / AI / cyber controls, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, or prohibited-function rules.
158.5 Compensation Records. The Corporation shall maintain compensation records for each compensated officer and for each officer receiving reimbursement, benefits, stipend, consulting payment, honorarium, allowance, expense payment, travel support, fellowship payment, contractor payment, deferred compensation, severance, bonus, incentive, or other economic benefit. Compensation records shall demonstrate lawful authority, reasonableness, budget authority, fund-source compliance, tax treatment, employment or contractor classification, conflict disclosure, independent review where required, approval, payment, reporting, correction, and closeout.
Compensation records shall include, as applicable, role description, compensation schedule, employment agreement, contractor agreement, Board approval, delegated approval, disinterested approval, comparability review, reasonableness review, private benefit review, inurement review, excess benefit review, related-party review, payroll records, tax withholding records, information return records, benefit records, expense reports, receipts, invoices, reimbursement approvals, restricted fund allocations, grant allocations, sponsorship allocations, and repayment or reclassification records.
No compensation record shall be structured to conceal private inurement, excessive benefit, related-party abuse, sponsor control, provider preference, public authority access purchase, finance-readiness sale, recognition sale, certification sale, procurement advantage, or regulated execution. Compensation records shall be retained and access-controlled in accordance with law, tax requirements, employment requirements, privacy requirements, audit requirements, legal hold rules, and Board-approved retention schedules.
158.6 Conflict and Recusal Records. The Corporation shall maintain conflict and recusal records for each officer. These records shall include annual disclosures, event-based disclosures, related-party disclosures, institutional conflict disclosures, financial conflict disclosures, research conflict disclosures, data / AI / cyber conflict disclosures, public authority conflict disclosures, sponsor conflict disclosures, provider conflict disclosures, host conflict disclosures, funder conflict disclosures, donor conflict disclosures, national company and Project SPV conflict disclosures, university or laboratory conflict disclosures, and other material affiliation records.
Conflict and recusal records shall identify the matter affected, conflict type, reviewer, review date, determination, mitigation, recusal scope, access restriction, delegation restriction, voting or approval restriction, factual-input permission if any, monitoring requirement, corrective action, and closeout. Where a conflict affects a contract, support relationship, public authority interface, evidence output, method output, data access, AI use, repository release, publication, correction, committee report, Nexus interface, GRF-facing input, or GRA-facing technical input, the record shall identify the affected instrument or output.
A conflict record shall not be treated as curing the conflict by disclosure alone. The record shall demonstrate review and management. Where an officer participated in a matter before disclosing a conflict, the record shall identify whether re-review, ratification where lawful, correction, withdrawal, restriction, repayment, access revocation, removal, or other remedy was required.
158.7 Training Records. The Corporation shall maintain officer training records sufficient to show that each officer has received, acknowledged, and periodically refreshed training appropriate to the officer’s role, authority, risks, access, public-facing function, technical function, public authority interface, Nexus interface, and safeguards responsibilities. Training records shall include training assigned, training completed, training deferred, training waived where lawful, training failed, corrective training required, certification of understanding, and any role-specific limitations pending training.
Officer training records shall address, as applicable:
a) this Bylaw, the Articles or Certificate, Board reserved matters, officer duties, delegation, authority matrices, records discipline, and fiduciary or management responsibilities;
b) United States nonprofit governance, tax-exempt or tax-exempt-compatible duties, private inurement, private benefit, excess benefit, compensation, reimbursement, grants, donations, sponsorships, restricted funds, charitable solicitation, state qualification, and all-states-and-territories compliance;
c) non-execution, public authority boundaries, finance boundaries, securities, investment adviser, broker-dealer, finder, banking, lending, insurance, underwriting, rating, public finance, procurement, certification, recognition, provider-neutrality, sponsor non-control, and professional boundary controls;
d) data governance, privacy, AI governance, cybersecurity, secure development, repository security, model registers, inference records, compute workload records, public-safe publication, public authority data, health-sensitive data, infrastructure-sensitive data, protected knowledge, and incident response;
e) research integrity, evidence doctrine, methods stewardship, observability methods, ontology governance, Truth Engine methods, verifiable compute and verifiable intelligence, public-good software, secure release, SBOM, provenance, licensing, and correctionability; and
f) civil rights, accessibility, Tribal and Indigenous protocols, Indigenous data safeguards, community safeguards, protected knowledge, public-safe mapping, grievance, remedy, protected participation, non-retaliation, competition, sanctions, export-control, controlled technology, government ethics, gifts, lobbying, procurement integrity, and public authority participation.
An officer shall not exercise authority requiring training unless the training has been completed or a competent authority has approved a lawful, temporary, risk-controlled exception.
158.8 Reports to Board. The Corporation shall maintain all officer reports to the Board as official records. Reports to the Board shall include regular Board reports, strategic reports, budget reports, finance reports, research reports, evidence reports, methods reports, technical reports, data / AI / cyber reports, public authority interface reports, safeguards reports, support reports, risk reports, compliance reports, incident reports, correction reports, Nexus interface reports, all-states-and-territories reports, North America interface reports, and escalation reports.
Records of reports to the Board shall identify the reporting officer, reporting period, version, date submitted, Board meeting or written circulation to which the report relates, materials reviewed, supporting records, limitations, public-safe status, confidentiality status, access class, and any Board questions, instructions, approvals, deferrals, holds, corrections, or follow-up actions. Where a report is superseded, corrected, withdrawn, restricted, or reclassified, the record shall preserve the prior version and the reason for the change.
No officer report shall be altered after circulation to remove risk, uncertainty, conflict, dissent, protected knowledge 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, safeguards concern, or correction need unless the alteration is clearly recorded as a correction or supersession.
158.9 Decisions Within Delegated Authority. The Corporation shall maintain records of decisions made by officers within delegated authority. Such records shall identify the officer, authority source, delegation, relevant policy, decision date, decision subject, affected program, affected fund, affected jurisdiction, affected public authority interface, affected sponsor or provider where applicable, affected data or technical asset, decision rationale, required reviews, conflicts, recusals, approvals, conditions, limitations, notice requirements, implementation steps, and correction pathway.
Officer decision records shall be proportionate to risk. Routine low-risk operational decisions may be recorded through approved workflows, logs, forms, registers, or system records. Material decisions shall be recorded in durable written form sufficient to support Board review, audit, legal review, compliance review, correction, and historical traceability.
No officer decision record shall be used to disguise a Board reserved matter, public authority action, finance-readiness determination, certification, recognition, procurement approval, provider preference, sponsor entitlement, or enterprise execution act. Where a decision is later determined to exceed delegated authority, the record shall be marked for review, hold, ratification where lawful, correction, suspension, withdrawal, or other remedy.
158.10 Contracts Signed. The Corporation shall maintain records of contracts signed by officers, including contracts, amendments, renewals, extensions, terminations, statements of work, purchase orders, grant agreements, donation agreements, sponsorship agreements, in-kind contribution agreements, MoUs, interface agreements, data agreements, confidentiality agreements, contributor agreements, licensing agreements, software agreements, cloud agreements, vendor agreements, contractor agreements, employment agreements, host agreements, public authority participation instruments, university and laboratory agreements, and Nexus interface instruments.
Contract records shall identify signing authority, legal review where required, budget authority, fund source, procurement process where applicable, conflicts, related-party status, tax review, nonprofit review, public authority boundary review, finance-boundary review, certification-boundary review, procurement-neutrality review, provider-neutrality review, sponsor non-control review, data / AI / cyber review, privacy review, sanctions review, export-control review, controlled-technology review, competition review, safeguards review, insurance requirements, indemnity terms, intellectual property terms, confidentiality terms, public statement terms, termination rights, and records obligations.
No officer may sign a contract that creates authority beyond the officer’s delegation, binds another Nexus actor without authority, creates agency, partnership, joint venture, shared liability, public authority delegation, finance execution, certification, recognition, procurement approval, provider preference, sponsor control, or enterprise execution unless separately and lawfully approved by competent authority and recorded.
158.11 Payments Authorized. The Corporation shall maintain records of payments authorized by officers. Payment records shall identify payee, amount, date, purpose, budget line, fund source, restricted fund status, invoice, contract, purchase order, reimbursement request, receipt, approval path, signing authority, segregation of duties, tax treatment, related-party status, conflict review, reasonableness review, grant allowability, donor restriction compliance, sponsorship compliance, procurement compliance, and any hold, exception, correction, repayment, or reclassification.
Payment records shall cover payroll, contractor payments, vendor payments, reimbursements, benefits, grants, stipends, scholarships, awards, fellowships, subscriptions, refunds, travel, event expenses, software licenses, cloud services, technical tools, data services, public authority learning costs, research costs, safeguards costs, filing fees, insurance, tax payments, professional services, and other expenditures.
No payment shall be authorized by the officer receiving the payment or by a person whose independence is compromised. No payment shall be used to disguise compensation, private inurement, excess benefit, sponsor control, provider preference, public authority access purchase, recognition purchase, finance-readiness purchase, certification purchase, procurement advantage, lobbying or political activity outside lawful limits, or prohibited execution.
158.12 Publications Approved. The Corporation shall maintain records of publications approved by officers, including public reports, whitepapers, technical baselines, methods papers, datasets, dashboards, maps, software releases, repository notices, website materials, public-safe summaries, public authority learning materials, Academy materials, grant reports, sponsor acknowledgment materials, media statements, social media statements, correction notices, supersession notices, withdrawals, retractions, takedowns, and archive notices.
Publication approval records shall identify author, approving officer, authority source, version, publication class, access class, public-safe review, legal review, research integrity review, evidence review, methods review, data / AI / cyber review, privacy review, public authority boundary review, finance-boundary review, certification-boundary review, procurement-neutrality review, provider-neutrality review, sponsor non-control review, safeguards review, protected knowledge review, controlled vocabulary review, limitation language, non-reliance language, conflicts, sponsor or provider involvement, public authority references, citation or source lineage, and correction pathway.
No publication approval record shall imply that a publication is a public warning, emergency command, public authority decision, regulatory approval, certification, procurement approval, recognition, maturity standing, finance-readiness, rating, insurance-readiness, provider endorsement, sponsor entitlement, or operational instruction unless a competent authority has separately and lawfully created that status and the publication record states such authority.
158.13 Data Access Authorized. The Corporation shall maintain records of data access authorized by officers. Data access records shall identify the requesting person, approving officer, authority source, data class, purpose, legal basis where applicable, consent basis where applicable, public authority basis where applicable, access duration, access method, repository, room, system, dataset, permitted use, prohibited use, download status, export status, retention rule, deletion rule, logging requirement, confidentiality duty, AI-use limitation, cross-border limitation, onward transfer limitation, and revocation pathway.
Data access authorization records shall distinguish public data, internal data, restricted data, controlled data, personal information, sensitive personal information, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, public authority data, rights-bearing data, community-protected data, Tribal or Indigenous data, local or territorial knowledge, protected knowledge, commercially sensitive data, and privileged or legally sensitive data.
No officer shall authorize data access where the officer lacks authority, has an unmanaged conflict, has not completed required review, or where the access would violate law, consent limits, public authority restrictions, privacy rules, data rights, Indigenous protocols, protected knowledge rules, civil-rights safeguards, cybersecurity controls, export controls, sanctions rules, competition rules, grant terms, contract terms, or public-safe publication restrictions.
158.14 AI-Use Authorized. The Corporation shall maintain records of AI use authorized by officers. AI-use authorization records shall identify the AI system, model, tool, agent, workflow, dataset, prompt or task class where appropriate, user, approving officer, authority source, purpose, permitted inputs, prohibited inputs, permitted outputs, human review requirement, model register entry, inference record requirement, compute workload record requirement, privacy classification, data classification, cyber classification, public authority classification, protected knowledge classification, publication classification, and correction pathway.
AI-use authorization records shall address, where applicable, training, fine-tuning, embedding, retrieval, model improvement, external API use, local deployment, secure enclave use, confidential computing, sovereign compute, agentic AI, automated scoring, public-safe publication, public authority learning, legal or compliance support, research support, software development, evidence review, methods review, translation, summarization, dashboarding, and decision-support limitations.
No AI-use authorization shall permit unapproved upload of confidential Board materials, privileged materials, public authority materials, personal information, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, community-protected data, Tribal or Indigenous data, protected knowledge, controlled technology, export-controlled materials, sanctions-sensitive materials, or repository secrets. No AI output shall be treated as authority without human review, record support, limitation language, and correctionability.
158.15 Controlled-Room Access Authorized. The Corporation shall maintain records of controlled-room, clean-room, evidence-room, data-room, public authority room, no-download room, tabletop room, simulation room, capital-reader learning room where applicable, regulator-listening room, and other restricted room access authorized by officers. Room access records shall identify participant, institution, capacity, approving officer, authority source, room class, materials class, access period, permitted use, prohibited use, confidentiality obligations, competition obligations, public authority boundary obligations, finance-boundary obligations, data / AI / cyber obligations, safeguards obligations, protected knowledge obligations, logging, monitoring, exhibit handling, chain-of-custody, closeout, return, deletion, and access revocation.
Controlled-room access authorization shall require screening appropriate to the room, including identity, capacity, conflict, independence, sanctions, export-control, controlled-technology, public authority, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, sponsor non-control, competition, data / AI / cyber, privacy, safeguards, and protected knowledge review where applicable.
No room access shall be represented as endorsement, approval, certification, recognition, finance-readiness, procurement approval, public authority action, provider preference, sponsor entitlement, public warning, emergency command, or execution authority. Room access may be suspended immediately where required to protect legal integrity, data security, public authority boundaries, competition discipline, protected knowledge, safeguards, or institutional trust.
158.16 Public Authority References Authorized. The Corporation shall maintain records of public authority references authorized by officers. Public authority reference records shall identify the public authority, office, agency, department, instrumentality, public university, public laboratory, utility, port, public health authority, emergency management authority, public safety authority, regulator, public finance actor, procurement actor, grant-making body, Tribal or Indigenous government, local government, or cross-border public authority involved; the capacity of participation; the source of authority for reference; the approving officer; the exact language authorized; the context; the date; and any limitations.
Public authority reference records shall distinguish official-capacity participation, observer participation, regulator-listening participation, public finance reader participation, emergency-management participant participation, public infrastructure operator participation, simulation participation, data contributor status, host status, funder status, grantor status, procurement status, and public authority learning participation. The record shall identify whether review was required for public records, open meetings, procurement integrity, government ethics, gifts, lobbying, grant compliance, confidentiality, public authority data, public-safe publication, or sovereign implication.
No officer shall authorize a public authority reference that implies endorsement, adoption, approval, funding, procurement, regulation, public warning, emergency command, public finance approval, sovereign obligation, public-private partnership, certification, recognition, finance-readiness, provider selection, or operational instruction unless such meaning is lawfully authorized by the public authority and recorded. Ambiguous public authority references shall be held or corrected.
158.17 Incidents Escalated. The Corporation shall maintain records of incidents escalated by officers. Incident escalation records shall include the officer reporting, date and time reported, date and time discovered, affected systems, affected persons, affected data, affected publications, affected public authority interfaces, affected funders or sponsors, affected providers or hosts, affected communities, affected Nexus interfaces, facts known, facts uncertain, immediate containment actions, authority used, reviewers notified, counsel involvement, privilege status, public-safe considerations, legal notification triggers, and remediation pathway.
Incident escalation records shall cover, as applicable, cyber incidents, data breaches, AI incidents, model failures, inference record failures, compute workload anomalies, repository compromises, software release defects, SBOM or vulnerability issues, key or credential compromise, controlled-room violations, public authority confusion, public-safe publication defects, finance-boundary overclaims, certification-boundary overclaims, procurement-neutrality breaches, recognition overclaims, sponsor-control incidents, provider-preference incidents, research misconduct, evidence defects, protected knowledge exposure, community harm, civil-rights concerns, accessibility failures, retaliation, harassment, fraud, conflicts, sanctions concerns, export-control concerns, competition incidents, and continuity failures.
Incident escalation records shall preserve evidence, support correction, and permit after-action review. No incident record shall be destroyed, softened, reclassified, or delayed to avoid legal review, Board review, public authority concern, sponsor concern, provider concern, media concern, reputational concern, or correction.
158.18 Corrections Authorized. The Corporation shall maintain records of corrections authorized by officers. Correction records shall identify the defective act, record, report, dataset, model output, inference record, compute record, dashboard, map, publication, software release, technical baseline, repository entry, public authority reference, support acknowledgment, controlled vocabulary entry, claim, room material, proof receipt, Docket-support input, Grid-support input, GRF-facing input, GRA-facing technical input, or Nexus interface record requiring correction.
Correction records shall identify the approving officer, authority source, correction type, correction date, reason for correction, prior version, corrected version, affected audience, reliance risk, limitation language, public-safe notice, controlled notice, public notice where approved, data / AI / cyber implications, public authority implications, finance-boundary implications, certification-boundary implications, procurement-neutrality implications, provider-neutrality implications, sponsor non-control implications, protected knowledge implications, safeguards implications, and archive status.
Corrections shall preserve historical traceability. No correction shall silently erase the fact of prior error. Where an officer lacks authority to authorize correction, the matter shall be escalated. Where correction may affect legal status, tax status, public authority relationships, public-safe publication, protected knowledge, finance-boundary status, certification-boundary status, GRF-facing inputs, GRA-facing technical inputs, or Nexus role separation, Board, committee, counsel, compliance, safeguards, or technical review shall be obtained as appropriate.
158.19 Officer Certifications. The Corporation may require officers to provide periodic, event-based, role-based, annual, quarterly, project-specific, grant-specific, support-specific, committee-specific, data-specific, AI-specific, cyber-specific, public authority-specific, publication-specific, controlled-room-specific, conflict-specific, or correction-specific certifications. Officer certifications may confirm understanding, compliance, completeness, authority, disclosure, conflict status, records status, training completion, public-safe review, data / AI / cyber review, safeguards review, or escalation status.
Officer certifications may include certification that the officer:
a) has read and understands this Bylaw and applicable policies;
b) has acted within authority;
c) has disclosed conflicts and related-party interests;
d) has not self-approved compensation, reimbursement, benefit, contract, access, publication, or support;
e) has preserved non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, and sponsor non-control;
f) has protected confidential information, public authority materials, personal information, cyber-sensitive materials, infrastructure-sensitive materials, community-protected data, Tribal or Indigenous data, protected knowledge, repository credentials, and controlled-room materials;
g) has used AI systems only as authorized;
h) has maintained required records;
i) has escalated known incidents, risks, and boundary concerns;
j) has supported correctionability and not concealed defects; and
k) has not retaliated against any person raising a concern.
An officer certification shall be a governance record. A false, misleading, incomplete, stale, or reckless certification may constitute grounds for correction, investigation, suspension, removal, repayment, access revocation, legal referral, or other remedy. Certification shall support accountability but shall not replace underlying evidence, records, independent review, or Board oversight.
158.20 Officer Record Integrity, Retention, Access, Sealing, Archival, and Secure Disposal. Officer records shall be created, maintained, corrected, retained, accessed, sealed, archived, and securely disposed of according to law, the Articles or Certificate, this Bylaw, Board-approved policy, retention schedules, legal hold requirements, tax requirements, employment requirements, audit requirements, grant requirements, donor restrictions, sponsorship restrictions, data / AI / cyber requirements, privacy requirements, public authority restrictions, safeguards requirements, and repository discipline.
Officer record integrity shall require accurate metadata, version control, custodian identification, access class, publication class, confidentiality class, retention class, legal hold status, correction history, supersession history, audit trail, repository location, and archive status. Material officer records shall not be stored only in personal email accounts, personal devices, unmanaged drives, shadow IT systems, unapproved AI systems, informal messaging channels, sponsor-controlled systems, provider-controlled systems, public authority systems, university systems, laboratory systems, or external repositories unless the Board or competent authority has approved the arrangement and required controls are in place.
Access to officer records shall be limited according to role, need, legal right, Board authority, committee authority, officer authority, audit purpose, counsel purpose, compliance purpose, tax purpose, employment purpose, safeguards purpose, data / AI / cyber purpose, public authority requirement, or lawful disclosure requirement. Records may be sealed, restricted, redacted, compartmentalized, or privileged where needed to protect confidentiality, privacy, safety, protected knowledge, legal privilege, investigation integrity, public authority restrictions, cyber-sensitive information, employment confidentiality, or non-retaliation protections.
Secure disposal shall occur only when lawful, outside legal hold, outside retention requirements, outside audit requirements, outside grant or donor retention requirements, outside public authority restrictions, and outside correction needs. Disposal shall be documented. No officer record may be destroyed, altered, backdated, withheld, or concealed to avoid accountability, Board review, committee review, audit, legal review, public authority review, correction, investigation, or enforcement.
The governing rule of this Section is that officer authority exists only as far as the records prove it and the governing instruments permit it. The Corporation shall maintain officer records with the same seriousness as it maintains Board records, technical truth records, public-good software records, data / AI / cyber records, public authority records, safeguards records, and correction records. Officer records shall show who held authority, what authority existed, how it was limited, how it was exercised, what was reported, what was corrected, what was escalated, and what remained prohibited. No undocumented authority shall be presumed; no defective record shall be inflated; no stale record shall be treated as current; and no officer record shall be immune from lawful review, correction, supersession, restriction, archival, or secure disposal.
Section 159. Officer Resignation, Removal, Suspension, Vacancy, Acting Officers, and Succession
159.1 Resignation. An officer may resign from office by delivering written notice to the Chair, the Secretary, the President, the Executive Director or Chief Executive Officer where applicable, or the Board, unless a different recipient is required by applicable law, the Articles or Certificate, this Bylaw, Board resolution, employment agreement, contractor agreement, appointment instrument, delegation instrument, or policy. A resignation may be unconditional, conditional, immediate, delayed, transition-based, or effective upon acceptance where lawful and stated in the resignation notice or governing record.
A resignation shall not, by itself, release the resigning officer from duties accrued before the effective date of resignation, including duties of confidentiality, data protection, AI-use compliance, cybersecurity, return or deletion of materials, repository access closeout, controlled-room closeout, public authority reference correction, conflict disclosure, cooperation with audits, cooperation with investigations, cooperation with legal or tax review, cooperation with grant or restricted fund reporting, correction of defective records, and protection of public-good assets.
The Corporation may require an orderly transition from a resigning officer where necessary to protect public-benefit purpose, nonprofit character, legal continuity, financial continuity, repository integrity, technical asset continuity, data / AI / cyber controls, public authority interface continuity, safeguards continuity, grants and restricted funds, Board reporting, officer reporting, Nexus interface continuity, GCRI Canada interface continuity, GRF-facing inputs, GRA-facing technical inputs, and correctionability. No resignation shall be used to evade accountability, preserve unauthorized access, conceal defects, avoid repayment, avoid conflict review, avoid incident reporting, avoid correction, or frustrate lawful investigation.
159.2 Effective Date of Resignation. An officer resignation shall be effective at the time stated in the resignation notice, or if no time is stated, upon receipt by the competent recipient, unless applicable law, the Articles or Certificate, this Bylaw, Board resolution, employment agreement, contractor agreement, appointment instrument, or policy requires acceptance, delayed effectiveness, transition conditions, or other formal action. The Board may accept, acknowledge, accelerate, delay where lawful, condition, or record the resignation in a manner consistent with law and institutional continuity.
The effective date record shall identify:
a) the officer resigning;
b) the office affected;
c) the notice date;
d) the recipient;
e) the effective date and time;
f) whether Board acceptance or acknowledgment is required;
g) whether the resignation affects statutory officer requirements, signing authority, bank authority, public authority interface authority, controlled-room authority, data access authority, AI-use authority, software release authority, publication authority, or emergency authority;
h) required transition actions;
i) access revocation timing;
j) return, deletion, sealing, or transfer obligations;
k) reporting, certification, correction, and closeout obligations; and
l) the responsible custodian for the resignation record.
Where a resignation would leave the Corporation without a legally required officer, without minimum governance capacity, without financial controls, without records custody, without public authority interface continuity, without data / AI / cyber continuity, or without safeguards continuity, the Board may appoint an acting officer, interim officer, successor officer, temporary custodian, emergency delegate, or other lawful continuity actor.
159.3 Removal by Board. The Board may remove any officer with or without cause to the fullest extent permitted by applicable law, the Articles or Certificate, this Bylaw, the officer’s appointment instrument, employment agreement, contractor agreement, Board resolution, or policy. Removal from office shall be distinguished from termination of employment, termination of contractor status, termination of fellowship, termination of advisory status, termination of committee participation, termination of access, and termination of other contractual or program relationships, although such consequences may occur together where lawful and recorded.
Board removal may be used to protect mission lock, public-benefit purpose, nonprofit character, tax-exempt or tax-exempt-compatible status, non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, records integrity, financial controls, research integrity, evidence integrity, data / AI / cyber controls, public-safe publication, civil rights, accessibility, community safeguards, Tribal and Indigenous protocol respect, protected knowledge, legal separateness, Nexus role separation, validity-by-record, correctionability, and institutional continuity.
A Board removal record shall identify the officer, office, authority for removal, whether removal is with or without cause, effective date, votes or written consent where applicable, conflicts and recusals, access consequences, delegation consequences, signing authority consequences, public statement controls, transition instructions, records custody, and any required legal, employment, tax, public authority, grant, donor, sponsor, provider, community, safeguards, or Nexus interface notice.
159.4 Removal Within Delegated Appointment Authority Where Lawful. Where the Board has lawfully delegated authority to appoint or remove a non-principal officer, the delegated authority may remove that officer within the scope, conditions, limits, and records requirements of the delegation. A delegated removal shall not apply to principal officers, statutory officers, senior officers, Board-appointed officers, officers whose removal is reserved to the Board, officers whose removal affects Board reserved matters, or officers whose removal would create material legal, tax, financial, data / AI / cyber, public authority, safeguards, or Nexus interface risk unless the Board expressly authorizes such removal or applicable law permits the delegation.
A delegated removal shall be recorded with the same discipline as a Board removal, including authority source, reason or no-cause basis where applicable, effective date, access revocation, transition duties, records custody, conflict review, employment or contractor consequences, and escalation where required. The delegated authority shall promptly notify the Chair, Secretary, President, Executive Director or Chief Executive Officer where applicable, and any relevant committee or officer.
No delegated removal may be used to retaliate against an officer for good-faith reporting, whistleblowing, protected participation, refusal to perform a prohibited function, refusal to approve an unauthorized act, escalation of public authority confusion, escalation of finance-boundary risk, correction of defective evidence, protection of protected knowledge, data / AI / cyber incident reporting, safeguards escalation, or objection to sponsor, provider, donor, funder, host, or public authority pressure.
159.5 Suspension Pending Review. The Board, Chair, President, Executive Director or Chief Executive Officer where delegated, Chief Legal, Compliance, and Risk Officer where approved, Chief Data, AI, and Cyber Officer where delegated, Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer where delegated, or another competent authority may suspend an officer’s authority, access, delegation, signing rights, publication rights, data rights, AI-use rights, repository rights, software release rights, controlled-room rights, public authority interface rights, or public statement rights pending review where necessary to protect the Corporation.
Suspension pending review may be imposed where there is a reasonable concern involving misconduct, unmanaged conflict, authority overreach, records defect, data misuse, AI misuse, cyber risk, public authority confusion, finance-boundary overclaim, certification-boundary overclaim, procurement-neutrality breach, provider-preference claim, sponsor-control concern, public-safe publication defect, protected knowledge exposure, civil-rights concern, accessibility concern, harassment, retaliation, sanctions issue, export-control issue, controlled-technology issue, competition concern, fraud, financial control issue, or other material risk.
Suspension pending review shall be proportionate, time-bounded where practicable, records-supported, non-retaliatory, and subject to review by competent authority. It may include preservation of records, access logs, devices, keys, credentials, repositories, room materials, contracts, payment records, reports, datasets, models, software artifacts, public authority materials, protected knowledge, and communications. Suspension shall not be represented as a final finding unless the competent record so states.
159.6 Grounds for Removal or Suspension. Grounds for removal or suspension may include any lawful basis determined by the Board or competent authority, including breach of duty, loss of eligibility, unmanaged conflict, misconduct, persistent non-performance, failure to report, failure to maintain records, failure to cooperate with review, misuse of authority, unauthorized public statement, misuse of name or marks, misuse of data or technical assets, public authority overclaim, finance-boundary overclaim, certification or procurement overclaim, recognition overclaim, provider-preference claim, sponsor-control violation, data misuse, AI misuse, cyber misconduct, research misconduct, protected knowledge breach, harassment, retaliation, civil-rights violation, accessibility violation, sanctions concern, export-control concern, controlled-technology concern, competition violation, private benefit concern, inurement concern, fraud, financial control failure, or conduct inconsistent with public-benefit purpose.
Grounds may be established by direct evidence, records review, audit findings, incident investigation, committee report, officer report, counsel review, compliance review, data / AI / cyber review, safeguards review, financial review, public authority clarification, participant complaint, protected disclosure, external notice, regulator notice, funder notice, sponsor or provider communication, repository logs, access logs, payment records, publication history, or other reliable information. The Corporation shall distinguish allegation, concern, preliminary finding, final finding, corrective action, and removal decision.
Removal or suspension shall not be imposed for unlawful, discriminatory, retaliatory, or bad-faith reasons. Where protected participation, whistleblowing, civil-rights complaint, safeguards complaint, public authority concern, data / AI / cyber incident reporting, correction request, or refusal to perform a prohibited function is involved, heightened review shall apply.
159.7 Breach of Duty. An officer may be suspended or removed for breach of duty. Breach of duty includes failure to act within authority, failure to act in good faith, failure to preserve public-benefit purpose, failure to preserve nonprofit character, failure to prevent private inurement or impermissible private benefit, failure to preserve tax-exempt or tax-exempt-compatible status, failure to preserve non-execution, failure to preserve GCRI / GRF / GRA role separation, failure to preserve public-good stack and enterprise stack separation, failure to preserve United States legal separateness, failure to preserve public authority boundaries, failure to preserve finance boundaries, failure to preserve certification boundaries, failure to preserve procurement neutrality, failure to preserve provider neutrality, failure to preserve sponsor non-control, failure to preserve data / AI / cyber controls, failure to preserve research integrity, failure to preserve evidence integrity, failure to preserve methods integrity, failure to preserve safeguards, failure to maintain records, failure to escalate, or failure to support correctionability.
A breach of duty may be material even if no financial loss occurs. Injury to institutional trust, public-safe claims discipline, public authority boundary discipline, data security, protected knowledge, public-good technical assets, legal separateness, evidence integrity, role separation, or correctionability may constitute material harm. Repeated minor breaches may constitute a material breach where they show disregard for governance discipline.
The Corporation may respond to breach of duty through corrective training, written warning, access restriction, delegation restriction, recusal requirement, supervision, probation, suspension, removal, contract action, repayment, correction, public or controlled clarification, legal review, or referral where required or appropriate.
159.8 Loss of Eligibility. An officer may be suspended or removed upon loss of eligibility. Loss of eligibility includes legal ineligibility, failure to maintain consent to serve, failure to maintain required licensing where applicable, failure to maintain employment or contractor eligibility where relevant, failure to satisfy fit-and-proper standards, failure to maintain good standing, failure to complete required training, failure to satisfy conflict and independence conditions, loss of authorization to access required systems, loss of sanctions or export-control eligibility, loss of data / AI / cyber eligibility, loss of public authority interface eligibility, loss of controlled-room eligibility, or other inability to perform the office lawfully and responsibly.
Loss of eligibility may be temporary, curable, conditional, or permanent. The Corporation may impose interim restrictions while evaluating whether eligibility can be restored. Restoration may require updated screening, training, disclosures, access review, legal review, tax review, safeguards review, data / AI / cyber review, Board approval, or revised delegation.
Where an officer’s eligibility is tied to a particular jurisdiction, state, territory, Tribal or Indigenous interface, public authority interface, grant, restricted fund, controlled technology, repository, dataset, model, room, public-good software asset, or Nexus interface, loss of eligibility may be limited to that function unless the risk affects broader office fitness.
159.9 Unmanaged Conflict. An officer may be suspended or removed for an unmanaged conflict of interest, undisclosed conflict, late-disclosed conflict, false or incomplete conflict disclosure, related-party transaction violation, recusal violation, access violation during recusal, conflict-based delegation misuse, sponsor conflict, provider conflict, donor or funder conflict, host conflict, public authority conflict, investor or capital actor conflict, national company conflict, Project SPV conflict, university or laboratory conflict, research conflict, data / AI / cyber conflict, publication conflict, public authority interface conflict, or safeguards conflict.
A conflict shall be treated as unmanaged where disclosure alone is insufficient and the officer has not complied with required mitigation, recusal, access restriction, independent review, delegation restriction, records control, or Board direction. A conflict may be material even where the officer believes the officer can act fairly. The standard is institutional integrity and public trust, not merely subjective intent.
Where a conflict affects a decision already made, the Corporation shall review whether the decision requires ratification where lawful, correction, withdrawal, suspension, contract action, repayment, re-review, public-safe clarification, or escalation. No officer may use position, access, records, public authority relationships, sponsor relationships, provider relationships, data, software, technical assets, public-good outputs, or Nexus interfaces to benefit a related person or related entity.
159.10 Misconduct. An officer may be suspended or removed for misconduct. Misconduct includes dishonesty, fraud, corruption, bribery, theft, misuse of funds, falsification of records, destruction of records, backdating, concealment, retaliation, harassment, discrimination, intimidation, abuse of authority, misuse of confidential information, unauthorized disclosure, unauthorized access, unauthorized use of AI systems, unauthorized use of data, unauthorized public statements, unauthorized commitments, misuse of signatures, misuse of bank authority, misuse of credentials, misuse of public authority relationships, misuse of sponsor or provider relationships, misuse of protected knowledge, or conduct that materially harms the Corporation’s public-benefit purposes or institutional trust.
Misconduct may also include reckless disregard of this Bylaw, repeated failure to follow lawful instructions, refusal to cooperate with lawful review, knowingly approving prohibited functions, pressuring others to overclaim, suppressing correction, suppressing dissent, suppressing safeguards concerns, manipulating evidence, manipulating methods, manipulating dashboards, manipulating model outputs, manipulating public-safe publication, or using technical control to bypass governance control.
The Corporation may investigate misconduct using internal review, committee review, independent review, counsel, auditors, data / AI / cyber reviewers, safeguards reviewers, employment counsel, tax advisors, or external investigators as appropriate. Misconduct findings shall be recorded with attention to confidentiality, privilege, privacy, protected participation, non-retaliation, and lawful disclosure duties.
159.11 Misuse of Name, Marks, Data, Reports, Software, Technical Assets, Public Authority References, or Nexus-Compatible Claims. An officer may be suspended or removed for misuse of the Corporation’s name, marks, logo, seal, badge, public descriptions, reports, datasets, software, technical baselines, repositories, dashboards, maps, proof receipts, controlled vocabulary, public-safe notices, public authority references, Nexus references, GRF-facing inputs, GRA-facing technical inputs, or Nexus-compatible claims.
Misuse includes unauthorized use, misleading use, sponsor-driven use, provider-driven use, finance-signaling use, certification-implying use, procurement-implying use, recognition-implying use, public authority-confusing use, public warning-implying use, emergency command-implying use, North America anchor overclaim, public-good stack overclaim, enterprise-stack confusion, or use that suggests the Corporation has authority it does not possess.
Where misuse occurs, the Corporation may require immediate cessation, correction, withdrawal, retraction, takedown, public clarification, controlled clarification, notice to affected parties, notice to public authorities where required, notice to GRF or GRA where their roles are implicated, repository correction, metadata correction, contract action, access restriction, suspension, removal, or legal response.
159.12 Public Authority, Finance, Certification, Procurement, Recognition, Provider-Preference, Sponsor-Control, or Public Warning Overclaim. An officer may be suspended or removed for any public authority, finance, certification, procurement, recognition, provider-preference, sponsor-control, or public warning overclaim. Such overclaims include stating, implying, permitting, failing to correct, or materially enabling a representation that the Corporation has issued a public warning, exercised emergency command, made a public authority decision, approved a procurement, selected a public authority vendor, certified a person or product, recognized a project, conferred maturity standing, determined finance-readiness, determined insurance-readiness, issued a rating, provided investment advice, approved public finance, recommended a provider, or allowed a sponsor to control governance, research, publication, access, or outcomes.
Overclaims may occur in contracts, MoUs, sponsorship materials, grant applications, public authority materials, investor materials, insurance materials, lender materials, provider materials, bid materials, public reports, dashboards, maps, websites, social media, presentations, emails, room materials, proof receipts, repository labels, dataset labels, model cards, system cards, benchmark cards, or public statements.
An officer responsible for an overclaim shall promptly escalate, hold affected materials, restrict further circulation, initiate correction, and preserve records. Failure to correct a known overclaim may itself constitute grounds for suspension or removal.
159.13 Data Misuse, AI Misuse, Cyber Misconduct, Research Misconduct, Protected Knowledge Breach, Harassment, Retaliation, or Civil Rights Violation. An officer may be suspended or removed for data misuse, AI misuse, cyber misconduct, research misconduct, protected knowledge breach, harassment, retaliation, discrimination, accessibility violation, civil-rights violation, or conduct inconsistent with community safeguards, Tribal and Indigenous protocol respect, protected participation, non-retaliation, and do-no-harm obligations.
Data misuse includes unauthorized access, unauthorized disclosure, unauthorized transfer, unauthorized download, unauthorized scraping, unauthorized training or fine-tuning, unauthorized model improvement, unauthorized re-identification, unauthorized publication, violation of consent limits, violation of public authority data rules, violation of protected knowledge restrictions, violation of cross-border restrictions, or violation of deletion and retention obligations. AI misuse includes uploading restricted materials to unapproved AI systems, treating AI output as authority without human review, using agentic AI outside authorization, concealing AI use where disclosure is required, or using AI to bypass review.
Cyber misconduct includes credential sharing, secret leakage, key misuse, repository compromise, insecure release, failure to report incidents, bypassing access controls, disabling logs, using shadow IT, or failing to follow incident response. Research misconduct includes fabrication, falsification, plagiarism, suppression of adverse evidence, undisclosed sponsor or provider influence, manipulation of peer review, or concealment of error. Any such matter may require immediate access revocation, preservation, investigation, correction, notification, and Board review.
159.14 Vacancy. A vacancy in an officer position occurs upon resignation, removal, suspension where the office is functionally unavailable, death, incapacity, expiration of term without renewal, loss of eligibility, abandonment of office, failure to qualify, creation of a new office without appointment, or any other event leaving an office unfilled or unable to perform required duties. A vacancy may be full, partial, temporary, emergency, acting, interim, function-specific, jurisdiction-specific, or access-specific.
The Corporation shall identify whether the vacancy affects statutory requirements, Board reporting, Secretary functions, Treasurer or Chief Financial Officer functions, financial controls, signing authority, bank authority, payroll, tax filing, charitable solicitation, grant compliance, restricted fund administration, public authority interfaces, data / AI / cyber controls, safeguards, research integrity, public-safe publication, repository security, software release, controlled rooms, incident response, correction, or Nexus interface continuity.
Vacancy shall not suspend the Corporation’s obligations under law, the Articles or Certificate, this Bylaw, grants, restricted funds, contracts, public authority interface instruments, data protection duties, cyber duties, safeguards duties, or correctionability. The Board or competent authority shall take timely action to preserve continuity.
159.15 Acting Officer. The Board may appoint an acting officer to perform the duties of a vacant, suspended, unavailable, conflicted, recused, incapacitated, or transitioning officer, or may authorize an acting officer through a succession plan, delegation matrix, emergency authority, or written appointment instrument. An acting officer shall have only the authority expressly granted and shall be subject to all limitations, conditions, reporting duties, conflict controls, access controls, and records requirements applicable to the office and the acting appointment.
An acting officer appointment shall identify the office, reason for acting status, appointing authority, effective date, duration, scope, excluded powers, reporting line, required co-approvals, access rights, public statement authority, public authority interface authority, signing authority, financial authority, data access authority, AI-use authority, repository authority, software release authority, controlled-room authority, correction authority, and review date.
Acting status shall not be used to avoid Board appointment, eligibility review, compensation review, conflict review, training, records discipline, or authority limits. An acting officer shall not exercise Board reserved matters or prohibited functions. Where acting status becomes prolonged, the Board shall review whether permanent appointment, restructuring, recruitment, external support, or narrowed delegation is required.
159.16 Interim Delegation. During a vacancy, transition, recusal, suspension, emergency, or continuity event, the Board or competent authority may issue an interim delegation to preserve necessary operations. Interim delegation may cover records custody, notices, filings, banking, payroll, restricted funds, grant reporting, contract administration, public authority communications, data access, cyber response, repository control, software release, controlled-room closeout, safeguards review, publication hold, correction, or incident response.
An interim delegation shall be written where practicable and shall identify scope, duration, purpose, limitations, approvals required, prohibited acts, reporting duties, sunset, and records. In urgent circumstances, interim delegation may be oral if lawful, but shall be reduced to a durable record as soon as practicable. The delegation shall use the narrowest authority sufficient to preserve lawful continuity and shall avoid authority inflation.
No interim delegation shall authorize public authority action, public warning, emergency command, finance execution, securities activity, investment advice, lending, insurance placement, underwriting, rating, public finance approval, procurement approval, certification, recognition, provider preference, sponsor control, enterprise execution, or amendment of governing instruments.
159.17 Succession Plan. The Corporation shall maintain officer succession planning proportionate to its size, risk, operating posture, public-benefit role, all-states-and-territories responsibilities, North America anchor role, data / AI / cyber posture, public authority interfaces, safeguards responsibilities, technical assets, repositories, grants, restricted funds, and Nexus interfaces. The succession plan may be adopted as a Board-approved plan, officer succession schedule, delegation matrix, continuity pack, emergency governance procedure, or other controlled instrument.
The succession plan shall address, as applicable:
a) principal officers;
b) statutory officers;
c) Secretary and records custody;
d) Treasurer or Chief Financial Officer and financial controls;
e) President, Executive Director, or Chief Executive Officer where applicable;
f) legal, compliance, and risk functions;
g) data / AI / cyber functions;
h) research, evidence, methods, observability, ontology, and technical truth functions;
i) public-good software, repositories, technical baselines, secure release, and technical asset functions;
j) public authority learning and public authority interface functions;
k) safeguards, civil rights, accessibility, Tribal and Indigenous protocol, and protected knowledge functions;
l) development, grants, sponsorship, restricted funds, and public-good support functions;
m) state, territorial, Tribal, local, and North America interface functions; and
n) Nexus interface, GRF-facing input, GRA-facing technical input, and GCRI Canada interface functions.
Succession planning shall not create automatic authority beyond the terms of the plan. Each succession action shall be activated, recorded, reviewed, and corrected where necessary.
159.18 Handover. A resigning, removed, suspended, transitioning, or replaced officer shall cooperate with handover unless excused or restricted by competent authority. Handover shall protect institutional continuity, records integrity, data / AI / cyber security, financial controls, public authority interface discipline, public-safe publication, safeguards, protected knowledge, grants, restricted funds, public-good technical assets, repositories, contracts, and correction pathways.
Handover may include:
a) transfer of records, files, keys, credentials, devices, tokens, signatures, seals, repositories, datasets, models, dashboards, software assets, rooms, registers, contracts, grants, donor files, sponsor files, public authority materials, technical documentation, and action logs;
b) written status reports, pending matters, deadlines, risks, incidents, disputes, conflicts, public authority sensitivities, finance-boundary concerns, certification-boundary concerns, procurement-neutrality concerns, data / AI / cyber concerns, safeguards issues, protected knowledge restrictions, and correction items;
c) meetings with successor officers, acting officers, Board representatives, committee chairs, counsel, auditors, accountants, data / AI / cyber reviewers, safeguards reviewers, and relevant custodians; and
d) certifications of return, deletion, transfer, confidentiality, access closeout, conflict disclosure update, incident disclosure, and correction cooperation.
Where there is risk of misconduct, retaliation, cyber compromise, protected knowledge exposure, evidence tampering, record alteration, or unauthorized access, handover may be supervised, restricted, forensically preserved, or conducted through counsel, IT, compliance, or designated custodians.
159.19 Access Revocation. Upon resignation, removal, suspension, vacancy, recusal, role change, acting appointment, delegation change, or other authority change, the Corporation shall review and revoke, reduce, transfer, suspend, or reclassify access as appropriate. Access affected may include physical access, Board materials, officer materials, bank systems, payroll systems, accounting systems, grant systems, donor and sponsor systems, public authority materials, repositories, cloud systems, communication systems, email, domains, keys, tokens, credentials, AI systems, datasets, models, dashboards, controlled rooms, clean rooms, evidence rooms, data rooms, no-download rooms, public authority rooms, code repositories, signing keys, software release systems, and public statement channels.
Access revocation shall be timely and risk-based. Immediate revocation shall be required where there is material risk involving cyber security, data protection, protected knowledge, public authority materials, financial controls, research integrity, evidence integrity, public-safe publication, sponsor or provider capture, retaliation, harassment, misconduct, or unauthorized public claims.
Access revocation records shall identify access categories, systems, responsible custodian, effective date, confirmation, exceptions, continuing access if any, reason for continuing access, monitoring requirements, and closeout. No former or suspended officer shall retain access by convenience, relationship, technical dependency, founder status, authorship, public authority relationship, sponsor relationship, provider relationship, or Nexus interface role.
159.20 Return, Deletion, Transfer, or Sealing of Records and Materials. The Corporation may require an officer who resigns, is removed, is suspended, changes role, is recused, completes a term, or is otherwise separated from office to return, transfer, delete, seal, archive, or restrict Corporation records and materials. Such materials include documents, emails, messages, datasets, models, dashboards, reports, public authority materials, protected knowledge, contracts, financial records, grant records, donor and sponsor records, repository materials, source code, keys, tokens, devices, credentials, controlled-room materials, evidence-room materials, data-room materials, no-download room materials, notes, recordings, minutes, public-safe publications, and technical assets.
Return, deletion, transfer, or sealing shall be conducted under supervision where required by law, policy, legal hold, audit, tax requirements, grant requirements, public authority restrictions, data protection requirements, cybersecurity requirements, protected knowledge safeguards, or investigation needs. A departing or suspended officer shall not delete, destroy, alter, conceal, export, copy, retain, or transfer Corporation materials except as expressly authorized.
Where materials are commingled with personal devices, personal accounts, university systems, sponsor systems, provider systems, public authority systems, contractor systems, or third-party systems, the Corporation shall use lawful, proportionate, privacy-respecting, evidence-preserving, and cybersecurity-aware procedures to separate, preserve, return, delete, seal, or restrict those materials. Legal hold shall override ordinary deletion.
159.21 Public or Controlled Correction Where Needed. Where an officer resignation, removal, suspension, vacancy, acting appointment, access revocation, or authority change creates public confusion, public authority confusion, sponsor confusion, provider confusion, donor or funder confusion, public-safe publication confusion, finance-boundary confusion, certification-boundary confusion, procurement-neutrality concern, recognition overclaim, Nexus-compatible claim confusion, GRF-facing input issue, GRA-facing technical input issue, or other material reliance risk, the Corporation may issue a public or controlled correction.
A correction may clarify that:
a) the officer no longer holds office;
b) the officer’s authority has changed;
c) prior statements were unauthorized, limited, superseded, withdrawn, retracted, or corrected;
d) the officer did not have authority to bind the Corporation;
e) the officer did not have authority to bind GCRI Canada, GRF, GRA, Nexus Network, Nexus Standards, consortiums, national companies, Project SPVs, providers, sponsors, hosts, public authorities, funders, universities, laboratories, or enterprise actors;
f) no public authority approval, finance-readiness, certification, procurement approval, recognition, provider preference, sponsor entitlement, public warning, emergency command, or enterprise execution authority was created; or
g) affected materials are held, restricted, superseded, withdrawn, corrected, archived, or under review.
Public or controlled correction shall be accurate, proportionate, legally reviewed where required, privacy-aware, non-retaliatory, public-safe, and records-supported. Correction shall not disclose confidential employment, investigation, protected knowledge, privileged, personal, public authority, or cyber-sensitive information unless lawful and approved.
159.22 Officer Resignation, Removal, Vacancy, and Succession Records. The Corporation shall maintain Officer Resignation, Removal, Vacancy, and Succession Records sufficient to demonstrate lawful handling of officer transitions, authority changes, access changes, continuity measures, corrective actions, and public-safe clarifications. These records shall be maintained in the official repository or other approved controlled repository, subject to confidentiality, privilege, privacy, employment, tax, audit, legal hold, data / AI / cyber, public authority, protected knowledge, safeguards, retention, archival, sealing, and secure disposal rules.
Officer Resignation, Removal, Vacancy, and Succession Records shall include, as applicable:
a) resignation notices, acceptance records, acknowledgment records, effective-date records, Board resolutions, written consents, minutes, delegated removal records, suspension records, acting appointment records, interim delegation records, and succession activation records;
b) cause or no-cause classification where applicable, investigation records where applicable, conflict records, recusal records, misconduct review records, eligibility review records, legal review records, employment review records, tax review records, compensation closeout records, reimbursement closeout records, benefits closeout records, repayment records, and related-party records;
c) access revocation records, credential revocation records, key rotation records, bank authority updates, signing authority updates, repository access updates, AI-system access updates, data access updates, controlled-room access updates, public authority interface updates, software release authority updates, publication authority updates, and emergency authority updates;
d) handover records, transition reports, continuity packs, successor briefings, pending action lists, risk lists, incident lists, correction lists, grant and restricted fund obligations, contract obligations, public authority obligations, Nexus interface obligations, GCRI Canada interface obligations, GRF-facing input obligations, GRA-facing technical input obligations, and safeguards obligations;
e) return, deletion, transfer, sealing, archival, device return, record preservation, legal hold, audit hold, forensic preservation, and secure disposal records;
f) public or controlled corrections, public-safe clarifications, public authority clarifications, sponsor or provider clarifications, donor or funder notices, participant notices, repository notices, website updates, signature authority notices, bank notices, public filing updates, and authority register updates;
g) Board, committee, counsel, compliance, data / AI / cyber, safeguards, finance, tax, audit, employment, public authority, and Nexus interface reviews;
h) exceptions requested, exceptions refused, exceptions approved where lawful, unresolved risks, open action items, responsible owners, deadlines, closeout confirmations, and correction history; and
i) responsible custodian, repository location, access class, publication class, retention class, legal hold status, archive status, sealing status, deletion status, review date, and metadata.
The governing rule of this Section is that officer transition is a governance event, not a private personnel formality. Resignation, removal, suspension, vacancy, acting authority, interim delegation, succession, handover, access revocation, materials return, and correction shall be handled so that institutional authority remains lawful, records remain intact, public-good assets remain protected, data / AI / cyber controls remain effective, public authority boundaries remain clear, finance and certification boundaries remain uninflated, safeguards remain enforceable, Nexus role separation remains intact, and correctionability remains available. No officer departure or authority change shall create a gap in mission lock, public-benefit stewardship, legal compliance, records discipline, public-safe claims discipline, or institutional continuity.
Section 160. Emergency Officer Authority, Break-Glass Authority, Ratification, and Sunset
160.1 Emergency Officer Authority Purpose. Emergency officer authority exists to preserve lawful institutional continuity, public-benefit purpose, nonprofit character, records integrity, financial control, data / AI / cyber security, public authority boundary discipline, public-safe publication discipline, safeguards, protected knowledge, research integrity, technical asset integrity, repository continuity, Nexus interface clarity, and correctionability during urgent events requiring action before ordinary Board, committee, or officer review can reasonably be completed.
Emergency officer authority shall be interpreted narrowly. It is a protective, stabilizing, temporary, records-supported authority, not an expansion of ordinary management power. It may be used to prevent harm, contain exposure, preserve evidence, secure systems, stop unauthorized circulation, protect public-safe communication, maintain required filings, preserve funds, secure records, protect controlled rooms, protect public authority materials, preserve protected knowledge, and maintain minimum operations.
Emergency officer authority shall not be used to create new mission, alter the Articles or Certificate, amend this Bylaw, approve Board reserved matters except where expressly and lawfully permitted, authorize prohibited functions, bypass conflict rules, avoid counsel review, avoid Board scrutiny, satisfy sponsor or provider pressure, accelerate finance-facing activity, imply public authority action, imply emergency command, imply certification, imply procurement approval, imply recognition, imply finance-readiness, or convert technical control into governance authority.
160.2 Break-Glass Authority. Break-glass authority is the narrow emergency authority by which an authorized officer may take immediate, proportionate, temporary, and records-supported action to prevent, contain, or mitigate serious institutional, legal, technical, financial, public-safe, cyber, privacy, public authority, safeguards, protected knowledge, or continuity risk. Break-glass authority may be activated only where delay would materially increase harm or where ordinary approval channels are temporarily unavailable, impracticable, compromised, conflicted, or too slow for the risk presented.
Break-glass authority may include, within recorded limits:
a) restricting, suspending, or revoking access to systems, repositories, datasets, models, dashboards, rooms, keys, credentials, domains, public channels, controlled materials, public authority materials, and protected knowledge;
b) freezing publication, circulation, release, implementation, deployment, repository merge, software release, dataset release, dashboard launch, public authority reference, sponsor acknowledgment, provider statement, public claim, proof receipt, or Nexus-compatible claim pending review;
c) preserving records, logs, devices, keys, credentials, communications, room materials, evidence materials, incident materials, financial records, access records, and audit trails;
d) activating incident response, cyber containment, data breach response, AI incident response, public-safe publication correction, safeguards stop-the-line, controlled-room lockdown, clean-room hold, or repository quarantine;
e) issuing internal notices, controlled notices, public-safe holding statements, authority-change notices, access notices, or correction notices where needed and lawful;
f) maintaining minimum financial, payroll, filing, insurance, registered agent, tax, grant, restricted fund, and continuity obligations; and
g) escalating to the Chair, Board, Executive Committee where created, counsel, compliance function, data / AI / cyber function, safeguards function, auditor, insurer, public authority, funder, affected participant, or other competent body where required or appropriate.
Break-glass authority shall not be exercised silently. The officer exercising it shall create a contemporaneous or prompt durable record identifying the trigger, authority used, action taken, persons affected, systems affected, materials affected, risks addressed, limitations, notice given, review required, ratification path, sunset date, and correction path.
160.3 Activation Triggers. Emergency officer authority may be activated when an authorized officer reasonably determines that a material risk requires immediate action to protect the Corporation and that ordinary review cannot reasonably occur before protective action is needed. Activation triggers include cybersecurity incidents, data breaches, AI incidents, public authority confusion, public-safe publication errors, finance-boundary overclaims, certification-boundary overclaims, procurement-neutrality breaches, recognition overclaims, provider-preference claims, sponsor-control concerns, protected knowledge exposure, civil-rights or accessibility harm, community harm, safeguards triggers, legal deadlines, regulatory perimeter risks, repository compromise, software release defects, key or credential compromise, technical asset compromise, controlled technology issues, financial control failures, fraud risks, and continuity failures.
Activation shall be based on known facts, credible indicators, reasonable suspicion, or urgent uncertainty. The officer need not wait for complete proof where delay would increase harm. The officer shall, however, distinguish facts known, facts uncertain, assumptions, preliminary indicators, and actions taken under precautionary authority.
Emergency activation shall not be used for ordinary disagreement, managerial preference, convenience, speed, reputational discomfort, donor concern, sponsor impatience, provider pressure, public authority sensitivity, event deadlines, publication deadlines, fundraising deadlines, or strategic preference where ordinary governance can reasonably be used.
160.4 Cybersecurity Incident Trigger. A cybersecurity incident trigger exists where there is actual, suspected, threatened, attempted, or imminent compromise of systems, repositories, credentials, keys, secrets, tokens, cloud environments, endpoints, domains, email, communication systems, dashboards, APIs, SDKs, software artifacts, release pipelines, signing systems, SBOM systems, observability systems, data rooms, controlled rooms, evidence rooms, public authority rooms, no-download rooms, or other technical assets.
Emergency actions may include credential revocation, key rotation, access suspension, repository freeze, release freeze, network isolation, endpoint isolation, backup verification, logging preservation, vulnerability containment, vendor escalation, incident response activation, forensic preservation, public-safe communication hold, and controlled notice. Where cybersecurity risk affects public authority materials, protected knowledge, personal information, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, community-protected data, Tribal or Indigenous data, controlled technology, export-controlled materials, or public-good software integrity, heightened containment and review shall apply.
No officer shall use cyber emergency authority to conceal insecure practices, delete evidence, bypass Board review, suppress vulnerability disclosure required by policy, retaliate against security researchers, or create unauthorized surveillance. Cyber incident handling shall remain records-supported, proportionate, legally reviewed where required, and correctionable.
160.5 Data Breach Trigger. A data breach trigger exists where there is actual, suspected, threatened, attempted, or imminent unauthorized access, disclosure, acquisition, exfiltration, alteration, loss, destruction, misuse, re-identification, transfer, publication, training use, model ingestion, or other compromise of data held, processed, accessed, received, generated, or stewarded by the Corporation.
Emergency actions may include data-room lockdown, no-download room lockdown, access suspension, export suspension, transfer freeze, publication freeze, dataset quarantine, model-use freeze, AI-use freeze, deletion hold, evidence preservation, legal hold, breach assessment, affected-system isolation, public authority notice review, participant notice review, regulator notice review, donor or funder notice review, and public-safe communication preparation.
Data breach triggers include risks involving personal information, sensitive personal information, health-sensitive data, rights-bearing data, public authority data, cyber-sensitive data, infrastructure-sensitive data, community-protected data, Tribal or Indigenous data, local or territorial knowledge, protected knowledge, confidential research data, sponsor or provider confidential information, grant data, financial data, and repository secrets. No emergency action shall authorize broader disclosure than necessary to contain and assess the breach.
160.6 AI Incident Trigger. An AI incident trigger exists where an AI system, model, agent, inference workflow, retrieval workflow, embedding system, model register, inference record, compute workload record, benchmark, evaluation harness, dashboard, automated score, digital twin, decision-support tool, or AI-enabled publication workflow creates, contributes to, or threatens material harm, unauthorized disclosure, public authority confusion, finance-boundary overclaim, certification overclaim, procurement overclaim, recognition overclaim, discrimination, accessibility harm, protected knowledge exposure, cyber risk, evidence distortion, hallucinated authority, model inversion, data leakage, prompt-injection compromise, unsafe automation, uncontrolled agentic action, or public-safe publication defect.
Emergency actions may include disabling the AI system, suspending model access, freezing agentic workflows, quarantining outputs, restricting prompts or datasets, suspending publication, preserving inference records, preserving compute workload records, requiring human review, revoking API keys, withdrawing model-generated content, correcting public claims, restricting dashboard output, and escalating to data / AI / cyber, legal, safeguards, research, evidence, and Board review.
No AI incident response shall treat AI output as final authority. No model output, agentic output, dashboard signal, automated score, digital twin inference, DePIN record, ledger entry, AI-RAN signal, sensor signal, or proof receipt shall override human review, lawful governance authority, public-safe limitation language, records discipline, or correctionability.
160.7 Public Authority Confusion Trigger. A public authority confusion trigger exists where any person could reasonably understand the Corporation, an officer, a committee, a publication, a dashboard, a report, a public authority room, a controlled-room output, a technical baseline, a proof receipt, a public-safe notice, a Nexus interface, a sponsor statement, a provider statement, or an event material to imply public authority endorsement, official adoption, regulatory approval, public warning, emergency command, procurement approval, public finance approval, sovereign obligation, grant approval, public-private partnership, public authority decision, or governmental delegation where no such lawful authority has been recorded.
Emergency actions may include holding or correcting public materials, restricting circulation, suspending public authority references, freezing public authority room materials, issuing controlled clarification, issuing public-safe clarification, requiring approval of revised language, notifying the public authority where appropriate, preserving the disputed record, and escalating to the Board, Chair, Secretary, public authority learning function, counsel, compliance function, and communications function.
Public authority confusion shall be treated as a governance risk even where caused unintentionally. The Corporation shall correct the record before reliance hardens, procurement processes are affected, public expectations are distorted, emergency communications are confused, or public authority relationships are compromised.
160.8 Public-Safe Publication Error Trigger. A public-safe publication error trigger exists where a publication, report, whitepaper, dataset, dashboard, map, software release, repository entry, model output, public-safe summary, public authority learning material, sponsor acknowledgment, provider statement, social media post, media statement, proof receipt, Docket-support input, Grid-support input, GRF-facing input, GRA-facing technical input, or Nexus interface material contains or may contain a material error, misleading claim, unsafe map, unsafe disclosure, stale evidence, unsupported evidence, omitted limitation, uncontrolled term, public authority overclaim, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, protected knowledge exposure, privacy issue, AI-use issue, cyber-sensitive disclosure, infrastructure-sensitive disclosure, or community harm risk.
Emergency actions may include publication freeze, takedown, withdrawal, retraction, supersession, errata, limitation correction, metadata correction, repository hold, dashboard disabling, map redaction, dataset quarantine, model output quarantine, public-safe notice, controlled notice, correction register entry, and escalation to research, evidence, methods, data / AI / cyber, safeguards, legal, public authority, and Board review.
No officer shall delay public-safe publication correction to protect reputation, avoid sponsor or provider discomfort, avoid public authority embarrassment, preserve media strategy, protect fundraising, or avoid acknowledgment of error. Public-safe correction shall be accurate, proportionate, traceable, and protective.
160.9 Finance, Securities, Insurance, Lending, Rating, Public Finance, Procurement, Certification, Recognition, Provider-Preference, or Public Warning Overclaim Trigger. An overclaim trigger exists where an officer reasonably determines that the Corporation, any person acting with or near it, any participant, sponsor, provider, donor, funder, public authority participant, national company, Project SPV, consortium, media actor, or external actor has stated, implied, enabled, or failed to correct a claim that may be understood as finance-readiness, insurance-readiness, bankability, investability, capital-readability, securities solicitation, investment advice, brokerage, finder activity, lending, underwriting, rating, public finance approval, procurement approval, certification, accreditation, recognition, maturity standing, Docket approval, Grid guarantee, provider preference, sponsor entitlement, public warning, emergency command, or public authority action.
Emergency actions may include claim hold, material withdrawal, public or controlled clarification, sponsor or provider notice, investor-material correction, public authority material correction, bid-material correction, room-material restriction, proof-receipt limitation, dashboard limitation, website correction, presentation correction, repository correction, and escalation to counsel, compliance, finance-boundary reviewers, procurement-neutrality reviewers, GRF where recognition is implicated, GRA where finance-readiness is implicated, and the Board where material.
No officer shall allow the Corporation’s public-good evidence, methods, observability, technical baselines, public-good software, dashboards, or controlled rooms to be converted by implication into capital execution, certification, procurement advantage, public authority approval, or market signaling.
160.10 Sponsor, Provider, Donor, Funder, Host, or Capture Trigger. A sponsor, provider, donor, funder, host, or capture trigger exists where any support relationship, in-kind dependency, hosted facility, technical dependency, funded program, donor restriction, sponsor benefit, provider participation, host condition, public acknowledgment, data contribution, software contribution, equipment contribution, compute contribution, AI-RAN or O-RAN contribution, DePIN contribution, cloud contribution, staff secondment, or relationship pressure threatens or appears to threaten the Corporation’s independence, public-benefit purpose, evidence integrity, research integrity, publication independence, provider neutrality, sponsor non-control, public authority access discipline, finance-boundary discipline, certification-boundary discipline, safeguards, protected knowledge, or Board oversight.
Emergency actions may include holding acceptance of support, suspending sponsor benefits, pausing provider participation, restricting access, freezing acknowledgments, quarantining contributed assets, requiring conflict review, ring-fencing staff or systems, suspending publication, suspending controlled-room access, restricting public references, and escalating to the Board, finance / audit / risk function, development function, legal / compliance function, safeguards function, and relevant technical custodians.
Emergency action shall be especially appropriate where a support actor seeks to purchase or influence research findings, publication timing, correction decisions, public authority access, provider preference, technical baseline inclusion, software feature inclusion, dashboard placement, Docket or Grid treatment, GRF recognition, GRA finance-readiness, Nexus-compatible status, certification, procurement advantage, or public claims.
160.11 Protected Knowledge, Civil Rights, Accessibility, Community Harm, or Safeguards Trigger. A safeguards trigger exists where there is actual, suspected, threatened, attempted, or imminent exposure, extraction, misuse, commercialization, re-identification, stigmatization, surveillance risk, mapping risk, publication risk, access risk, retaliation risk, discrimination risk, accessibility failure, community harm, Tribal or Indigenous protocol breach, Indigenous data safeguard breach, local or territorial knowledge breach, protected knowledge breach, youth or vulnerable population risk, health-sensitive risk, public safety risk, or do-no-harm concern.
Emergency actions may include safeguards stop-the-line, publication freeze, map redaction, dataset restriction, room lockdown, access revocation, consent review, non-consent enforcement, withdrawal implementation, attribution restriction, protected knowledge sealing, community notice review, grievance pathway activation, remedy pathway activation, non-retaliation protection, accessibility correction, civil-rights review, and escalation to the safeguards officer, Board, counsel, public authority function, data / AI / cyber function, research function, and relevant community or Indigenous interface where lawful and respectful.
No officer shall treat protected knowledge, civil rights, accessibility, Tribal or Indigenous protocol, or community harm concerns as secondary to technical speed, public visibility, sponsor expectations, provider expectations, research publication, public authority interest, fundraising, or event timelines. Safeguards authority may stop, hold, quarantine, re-scope, withdraw, or correct affected work.
160.12 Legal Deadline or Regulatory Perimeter Trigger. A legal deadline or regulatory perimeter trigger exists where immediate action is required to preserve corporate status, registered agent status, tax status, charitable solicitation status, state or territorial qualification, grant compliance, restricted fund compliance, contract compliance, insurance coverage, employment compliance, public authority interface compliance, data breach notice timing, cyber incident notice timing, litigation hold, investigation response, subpoena response, audit response, public filing, appeal deadline, sanctions response, export-control response, controlled-technology response, procurement integrity response, lobbying or political activity compliance, or professional boundary compliance.
Emergency actions may include filing preservation, deadline response, legal hold activation, document preservation, counsel engagement, external notice preparation, internal hold notice, restricted action hold, transaction freeze, communications restriction, authority clarification, state or territorial localization hold, cross-border transfer hold, and regulatory-perimeter quarantine.
Regulatory perimeter triggers include uncertainty about whether an activity may constitute securities activity, investment adviser activity, broker-dealer activity, finder activity, banking, lending, insurance, underwriting, rating, public finance approval, procurement approval, certification, public warning, emergency command, public authority action, legal advice, engineering opinion, medical or public health advice, or other regulated professional or governmental function. Where such ambiguity exists, the narrower and more restrictive lawful posture shall apply pending review.
160.13 Repository, Software Release, Key, Token, Credential, Technical Asset, Controlled Technology, or Infrastructure Compromise Trigger. A technical compromise trigger exists where repositories, source code, build systems, CI/CD pipelines, signing systems, artifacts, SBOMs, dependencies, packages, APIs, SDKs, schemas, dashboards, models, datasets, benchmarks, test harnesses, evaluation sets, keys, tokens, credentials, secrets, domains, public-good software, open technical baselines, observability systems, Truth Engine methods, verifiable compute systems, controlled technology, infrastructure-sensitive materials, or mission-critical technical assets are compromised, suspected to be compromised, or at imminent risk.
Emergency actions may include release freeze, repository lockdown, branch protection activation, signing key rotation, package withdrawal, dependency quarantine, SBOM correction, vulnerability disclosure handling, access revocation, contributor suspension, maintainer privilege restriction, dashboard disablement, API key revocation, model access suspension, dataset quarantine, proof receipt hold, artifact deprecation, rollback, takedown, secure rebuild, and public-safe notice.
No officer shall use emergency technical authority to create certification, procurement approval, provider preference, public authority decision, finance-readiness, or operational instruction. Technical emergency action shall protect integrity and reduce harm while preserving governance review, auditability, and correction.
160.14 Limits on Emergency Officer Authority. Emergency officer authority is limited by law, the Articles or Certificate, this Bylaw, Board reserved matters, tax-exempt or tax-exempt-compatible obligations, nonprofit character, public-benefit purpose, non-distribution, private benefit controls, conflict controls, data / AI / cyber controls, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, public-safe publication, community safeguards, protected knowledge, validity-by-record, and correctionability.
Emergency officer authority shall not authorize:
a) amendment, repeal, replacement, or restatement of this Bylaw;
b) amendment of the Articles or Certificate;
c) change of legal name, corporate form, state of incorporation, governance seat, tax status, mission lock, public-benefit purpose, or non-execution boundary;
d) merger, consolidation, dissolution, conversion, sale of substantially all assets, transfer of major public-good assets, or abandonment of mission-critical records;
e) creation of public authority power, emergency command, official public warning, regulatory approval, public finance approval, procurement approval, certification, recognition, rating, finance-readiness, insurance-readiness, investment advice, brokerage, lending, underwriting, provider preference, sponsor entitlement, or enterprise execution;
f) acceptance of material restricted support, sponsor control, provider control, donor control, or support-for-outcome arrangements;
g) waiver of required Board approval, member approval where required, counsel review where required, safeguards review where required, or data / AI / cyber review where required, except for temporary protective action pending review; or
h) destruction, alteration, concealment, or unrecorded deletion of records needed for legal hold, audit, investigation, correction, public authority clarification, protected knowledge protection, or institutional accountability.
Any emergency act exceeding these limits shall be void, voidable, suspended, non-operative, subject to ratification only where lawful, or subject to correction, withdrawal, reversal, or legal review.
160.15 No Emergency Officer Authority to Exercise Prohibited Functions. No emergency shall convert the Corporation into a regulator, emergency command body, public warning authority, public authority, public finance authority, procurement authority, certification body, recognition body, rating agency, investment adviser, broker, dealer, finder, lender, insurer, underwriter, bank, public-private partnership authority, national company, Project SPV, asset owner, provider, operator, or enterprise execution vehicle.
No officer may invoke emergency authority to:
a) direct public emergency response;
b) issue evacuation, dispatch, public health, public safety, or incident command instructions;
c) approve, deny, certify, rate, recognize, procure, finance, insure, lend to, underwrite, guarantee, or operationally authorize any person, project, provider, product, deployment, node, hub, cluster, hotspot, national dense Nexus core, AI-RAN component, O-RAN component, DePIN component, DLT component, blockchain component, digital twin, dashboard, dataset, model, system, software release, or infrastructure asset;
d) substitute for GRF recognition, GRA finance-readiness, Nexus Standards protocol authority, public authority decisions, or enterprise-stack execution;
e) solicit capital, recommend investments, make securities-related claims, provide suitability determinations, place insurance, originate credit, issue ratings, or approve public finance; or
f) bind GCRI Canada, GRF, GRA, Nexus Network, Nexus Standards, consortiums, national companies, Project SPVs, providers, sponsors, hosts, public authorities, universities, laboratories, funders, donors, communities, or enterprise actors without express lawful authority.
Emergency authority may protect against confusion about these functions; it may not perform them.
160.16 Immediate Notice to Chair or Board. An officer exercising emergency officer authority or break-glass authority shall give immediate notice to the Chair, the Secretary, the President, the Executive Director or Chief Executive Officer where applicable, the relevant Board committee, and the full Board as appropriate to the risk. Where immediate notice is impracticable, the officer shall give notice as soon as reasonably possible and shall document the reason for any delay.
The notice shall include the trigger, facts known, facts uncertain, authority used, action taken, persons or systems affected, access restrictions imposed, publications held, records preserved, reviewers engaged, risks remaining, requested ratification or review, sunset timing, and proposed next steps. Where the matter implicates privilege, employment confidentiality, protected knowledge, public authority restrictions, cyber-sensitive information, personal information, or investigation integrity, notice may be compartmentalized but shall not be withheld from competent governance oversight without lawful basis.
The Chair or Board may affirm, modify, narrow, expand within lawful limits, suspend, reverse, ratify, require further review, require correction, or terminate the emergency action.
160.17 Time-Limited Measures. Emergency officer authority shall be time-limited. Each emergency action shall identify an initial duration, review date, sunset date, or event-based termination condition. The authority shall expire when the emergency condition is resolved, when ordinary governance review becomes available, when the Board or competent authority acts, when the sunset date occurs, or when the action is superseded, withdrawn, corrected, or ratified where lawful.
Emergency measures shall be no broader than necessary and shall be narrowed as facts develop. Access restrictions, publication freezes, implementation freezes, repository lockdowns, room lockdowns, data quarantines, model freezes, dashboard holds, and public statement restrictions shall be reviewed periodically during the emergency period.
No emergency measure shall become permanent by inertia. Any continuing restriction, delegation, access change, publication status, correction status, system quarantine, support restriction, provider restriction, sponsor restriction, or public authority limitation shall be converted into a regular governance record, Board action, officer delegation, policy decision, incident record, correction record, or closeout record.
160.18 Ratification. Emergency officer actions shall be presented for ratification where required by law, the Articles or Certificate, this Bylaw, Board resolution, delegation, policy, contract, grant instrument, public authority interface instrument, or the nature of the action. Ratification shall be sought from the Board, Executive Committee where lawfully delegated, committee, officer, counsel, compliance function, safeguards function, data / AI / cyber function, or other competent authority as appropriate.
Ratification records shall identify:
a) the emergency action;
b) the officer who acted;
c) the authority asserted;
d) the trigger and factual basis;
e) the time period covered;
f) the records preserved;
g) the notices given;
h) the conflicts and recusals involved;
i) the limits and conditions imposed;
j) whether the action is affirmed, modified, narrowed, expanded within lawful limits, rejected, reversed, superseded, corrected, or referred;
k) whether further Board approval, counsel review, public authority clarification, data / AI / cyber review, safeguards review, financial review, audit review, or public-safe publication review is required; and
l) the responsible owner for closeout.
Ratification shall not validate an act that applicable law, the Articles or Certificate, this Bylaw, tax rules, nonprofit rules, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, safeguards, data / AI / cyber controls, or other mandatory rules prohibit. Where ratification is unavailable, the action shall be treated as held, void, voidable, non-operative, reversed, corrected, or otherwise remedied to the fullest extent lawful.
160.19 Sunset. Each emergency officer action shall include a sunset mechanism. Sunset may occur by date, Board action, event resolution, incident closeout, access restoration, publication correction, repository remediation, legal review completion, public authority clarification, safeguards resolution, data / AI / cyber containment, audit completion, or other recorded condition.
Upon sunset, the Corporation shall determine whether to restore ordinary authority, continue restrictions through regular governance, close the incident, initiate correction, initiate policy amendment, revise delegation, revise access controls, update registers, update public-safe notices, revise controlled vocabulary, or refer the matter for further review. Sunset shall be documented and shall not erase the emergency record.
A sunset record shall identify the action terminated, continuing measures if any, restored authorities, revoked authorities, corrected materials, outstanding risks, open action items, residual legal or technical issues, responsible owners, and archive status.
160.20 Post-Emergency Review. Following any material emergency officer action, the Corporation shall conduct a post-emergency review proportionate to the event. The review may be conducted by the Board, Executive Committee where created, relevant committee, Chair, President, Executive Director or Chief Executive Officer, Secretary, Treasurer or Chief Financial Officer, Chief Legal, Compliance, and Risk Officer where approved, Chief Data, AI, and Cyber Officer, Chief Safeguards, Civil Rights, Accessibility, and Protected Knowledge Officer, counsel, auditor, cybersecurity reviewer, safeguards reviewer, or other competent reviewer.
The post-emergency review shall assess:
a) whether the trigger was valid;
b) whether action was timely and proportionate;
c) whether records were preserved;
d) whether notice was given;
e) whether public authority, finance, certification, procurement, recognition, provider, sponsor, data / AI / cyber, safeguards, protected knowledge, research integrity, or public-safe publication boundaries were preserved;
f) whether any person was harmed or unfairly affected;
g) whether protected participation and non-retaliation were preserved;
h) whether correction, supersession, withdrawal, retraction, takedown, public clarification, controlled clarification, access restoration, repayment, contract action, or legal action is required;
i) whether policy, protocol, training, delegation, authority matrix, access matrix, repository control, public-safe notice, controlled vocabulary, or technical control changes are required; and
j) whether Board or committee action is required.
The post-emergency review shall be candid. It shall not be used to justify defective conduct, conceal errors, punish good-faith reporting, or convert temporary measures into permanent authority without governance action.
160.21 Emergency Officer Authority Records. The Corporation shall maintain Emergency Officer Authority Records sufficient to demonstrate why emergency authority was activated, who activated it, what authority was used, what actions were taken, how long the actions lasted, what records were preserved, what notices were given, how review occurred, whether ratification was obtained, how sunset occurred, and what corrections or improvements followed. Records shall be maintained in the official repository or other approved controlled repository, subject to privilege, confidentiality, privacy, cyber, public authority, protected knowledge, safeguards, legal hold, audit, retention, sealing, archival, and secure disposal rules.
Emergency Officer Authority Records shall include, as applicable:
a) activation records, trigger records, break-glass records, incident records, access restriction records, publication freeze records, repository lockdown records, room lockdown records, data quarantine records, AI-system freeze records, model freeze records, dashboard hold records, technical isolation records, key rotation records, credential revocation records, and continuity action records;
b) facts known, facts uncertain, risk assessments, legal assessments, data / AI / cyber assessments, safeguards assessments, public authority assessments, finance-boundary assessments, certification-boundary assessments, procurement-neutrality assessments, provider-neutrality assessments, sponsor non-control assessments, research integrity assessments, evidence assessments, and public-safe publication assessments;
c) notices to Chair, Board, committees, officers, counsel, compliance, auditors, insurers, public authorities, funders, donors, sponsors, providers, affected persons, communities, or Nexus interface bodies where lawful and appropriate;
d) privilege records, confidentiality records, legal hold records, forensic preservation records, audit trail records, access logs, system logs, repository logs, inference records, compute workload records, model register entries, correction register entries, incident register entries, risk register entries, and issue register entries;
e) ratification records, modification records, reversal records, rejection records, supersession records, sunset records, post-emergency review records, lessons-learned records, corrective action records, training records, policy amendment records, delegation amendment records, authority matrix amendment records, access matrix amendment records, controlled vocabulary amendment records, and public-safe notice updates;
f) public or controlled corrections, takedowns, retractions, withdrawals, errata, clarification statements, public authority clarifications, sponsor or provider clarifications, repository notices, website notices, room notices, and affected-audience notices;
g) unresolved risks, residual risks, exceptions requested, exceptions refused, exceptions approved where lawful, open action items, responsible owners, deadlines, closeout confirmations, and correction history; and
h) responsible custodian, repository location, access class, publication class, retention class, legal hold status, archive status, sealing status, deletion status, review date, and metadata.
The governing rule of this Section is that emergency authority may protect the Corporation, but it may not transform it. Emergency officer authority exists to hold, stop, contain, preserve, clarify, correct, and maintain lawful continuity within the Corporation’s public-benefit, nonprofit, non-executing, role-separated, records-based, public-safe, safeguards-respecting, and Nexus-compatible character. Every emergency action shall be temporary, bounded, recorded, reviewable, ratifiable only where lawful, sunsetted, and correctionable. No emergency shall create public authority power, finance-readiness power, certification power, procurement power, recognition power, provider preference, sponsor control, enterprise execution, unrecorded authority, or immunity from Board oversight.
Section 161. Officer Training, Certification of Understanding, Evaluation, and Accountability
161.1 Officer Training Purpose. Officer training exists to ensure that each officer of the Corporation understands the officer’s legal authority, fiduciary-adjacent responsibilities, delegated powers, operating limits, public-benefit duties, nonprofit constraints, records obligations, public-safe claim obligations, data / AI / cyber duties, safeguards duties, Nexus interface obligations, and correction responsibilities before exercising authority on behalf of the Corporation.
Training shall not be treated as a symbolic onboarding step. It shall be a continuing governance control by which the Corporation protects mission lock, United States legal separateness, tax-exempt or tax-exempt-compatible status, public-benefit purpose, non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, public-good technical assets, evidence integrity, research integrity, data security, protected knowledge, civil rights, accessibility, validity-by-record, and correctionability.
Each officer shall receive training proportionate to the officer’s office, access rights, decision authority, delegated budget authority, signing authority, public-facing role, technical role, data role, AI role, cyber role, controlled-room role, public authority interface role, Nexus interface role, safeguards role, fundraising role, and exposure to regulated-perimeter risk. No officer shall be permitted to rely on seniority, technical expertise, founder status, public prominence, professional credentials, sponsor relationship, provider relationship, public authority relationship, or prior nonprofit experience as a substitute for Corporation-specific training.
161.2 Bylaw Training. Each officer shall receive training on this Bylaw, the Articles or Certificate, Board reserved matters, officer appointment rules, officer authority rules, delegation limits, authority matrices, conflict rules, records requirements, notice requirements, repository discipline, gazette or notice-stream discipline, controlled vocabulary, public-safe claims discipline, correction pathways, and the hierarchy of governing instruments.
Bylaw training shall explain that officer authority is not created by title alone, function alone, system access alone, public authority contact alone, technical authorship alone, committee participation alone, public visibility alone, or operational convenience. Officer authority exists only to the extent supported by competent appointment, delegation, Board resolution, policy, authority matrix, budget, contract, or other lawful record.
Bylaw training shall include, as applicable:
a) the distinction between Board reserved matters, officer authority, committee recommendations, advisory body outputs, Secretariat support, technical work product, public authority participation, sponsor participation, provider participation, and enterprise-stack execution;
b) the prohibition on lower-order instruments overriding law, the Articles or Certificate, this Bylaw, Board reserved powers, public-benefit purpose, nonprofit character, non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, or correctionability;
c) the duty to escalate ambiguity, defects, conflicts, boundary concerns, public authority confusion, finance overclaims, certification overclaims, procurement overclaims, provider-preference risks, sponsor-control risks, data incidents, AI incidents, cyber incidents, public-safe publication defects, protected knowledge concerns, and correction needs; and
d) the requirement that all material officer actions be record-supported, versioned where applicable, reviewable, bounded, and correctionable.
Completion of Bylaw training shall be recorded before the officer exercises material authority unless a lawful temporary exception is approved and recorded.
161.3 Fiduciary and Public-Benefit Training. Each officer shall receive training on duties owed to the Corporation, including good-faith institutional service, faithful execution of delegated authority, loyalty to the Corporation’s public-benefit purposes, prudent management of assigned responsibilities, avoidance of private benefit, avoidance of unauthorized commitments, truthful reporting, conflict disclosure, escalation of risk, and protection of institutional integrity.
Public-benefit training shall emphasize that the Corporation exists to steward evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, verifiable compute and intelligence methods, Nexus Truth Engine methods, Nexus Observatory methods, public authority learning, community safeguards, and public-safe publication, and that officers must not convert those purposes into private advantage, sponsor advantage, provider advantage, public authority confusion, regulated execution, or enterprise delivery.
Fiduciary and public-benefit training shall address, without limitation:
a) nonprofit loyalty, institutional purpose, charitable or public-benefit compatibility where applicable, non-distribution, private inurement, impermissible private benefit, excess benefit risk, related-party risk, and reasonable compensation principles;
b) Board oversight, officer accountability, accurate reporting, truthful certifications, internal controls, financial prudence, grant and restricted fund compliance, public support integrity, and avoidance of mission drift;
c) public trust, research integrity, evidence integrity, public-safe communication, safeguards, protected participation, non-retaliation, civil rights, accessibility, and do-no-harm responsibilities; and
d) correctionability as an affirmative institutional duty rather than an optional remedial gesture.
No officer shall use the Corporation’s public-benefit status to create private leverage, market signaling, public authority leverage, finance-facing meaning, certification meaning, procurement advantage, provider preference, sponsor entitlement, or reputational benefit inconsistent with this Bylaw.
161.4 United States Nonprofit and Tax Training. Each officer whose role involves governance, finance, fundraising, grants, donations, sponsorships, restricted funds, contracts, compensation, reimbursement, public statements, state registrations, charitable solicitation, public authority interfaces, or tax-sensitive activity shall receive training on United States nonprofit and tax compliance appropriate to the officer’s responsibilities.
United States nonprofit and tax training shall address, as applicable:
a) state nonprofit corporate law, corporate filings, registered agent discipline, annual reports, good standing, minute books, Board records, officer records, member records where applicable, committee records, corporate separateness, and state qualification;
b) federal tax classification, tax-exempt or tax-exempt-compatible operations, IRS records, information returns, unrelated business income review, lobbying and political activity limits where applicable, private inurement, private benefit, excess benefit transactions, reasonable compensation, accountable reimbursement, donor acknowledgments, sponsorship treatment, grant restrictions, restricted funds, and public support;
c) charitable solicitation registration, fundraising controls, donor restrictions, sponsorship benefits, in-kind support valuation, foreign funding sensitivity, sanctions screening, grant reporting, refund or return of support, and public acknowledgment controls; and
d) state and local tax, sales tax, franchise tax, employment tax, contractor classification, volunteer classification, stipend or fellowship treatment, and cross-border tax review where applicable.
Training shall make clear that tax status, charitable status, public-benefit status, fiscal sponsorship, supporting organization status, Section 501(c)(3) status, Section 501(c)(4) status, Section 501(c)(6) status, or any other tax or nonprofit status shall not be claimed, implied, or relied upon unless supported by competent records.
161.5 All-States-and-Territories and North America Interface Training. Officers with state, territorial, District of Columbia, Tribal, Indigenous, local, regional, cross-border, or North America responsibilities shall receive training on the Corporation’s all-states-and-territories operating posture and bounded North America anchor role. Such training shall emphasize that the Corporation may support lawful public-benefit evidence, methods, observability, ontology, public-good software, technical baselines, public authority learning, and Nexus-compatible coordination across jurisdictions only through proper records, lawful registrations, capacity classifications, localization notes, compatibility notes, and divergence logs.
Training shall address, as applicable:
a) operation across all fifty states, the District of Columbia, Puerto Rico, Guam, the U.S. Virgin Islands, American Samoa, the Northern Mariana Islands, Tribal Nations and Indigenous governments where lawfully and respectfully engaged, and local, county, municipal, metropolitan, port, utility, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, and infrastructure contexts;
b) state qualification, territorial qualification, charitable solicitation, employment, contractor, tax, privacy, cybersecurity, public records, open meetings, procurement, lobbying, grant, public authority, and contracting review where applicable;
c) coordination with GCRI Canada and other North America interfaces without merger, branch status, alter ego status, common treasury, shared liability, joint employer status, mutual agency, or foreign sovereign authority; and
d) cross-border data, AI, cyber, privacy, export-control, sanctions, controlled technology, public authority, Indigenous protocol, protected knowledge, and conflict-of-law review.
No officer shall represent the North America anchor role as treaty authority, intergovernmental authority, regional regulatory authority, public finance authority, emergency command authority, procurement authority, certification authority, recognition authority, finance-readiness authority, or enterprise execution authority.
161.6 Non-Execution Training. Each officer shall receive training on the Corporation’s bright-line non-execution rule. Non-execution training shall explain that the Corporation may steward evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, public-safe reporting, public authority learning, controlled rooms, technical profiles, proof receipts, Docket-support inputs, Grid-support inputs, GRF-facing inputs, and GRA-facing technical inputs, but shall not act as an execution vehicle.
Non-execution training shall address the prohibition on:
a) securities offerings, securities distribution, solicitation, brokerage, dealer activity, finder activity, investment advice, capital placement, capital recommendation, portfolio management, transaction recommendation, suitability determination, or investor intermediation;
b) banking, deposit-taking, payment intermediation, custody, clearing, settlement, escrow, lending, credit approval, loan origination, guarantee, insurance placement, insurance binding, underwriting, pricing, claims handling, rating, public finance approval, tax credit approval, budget allocation, public guarantee, or sovereign finance approval;
c) emergency command, incident command, dispatch, evacuation instruction, public health order, public safety command, official public warning, public infrastructure operational direction, or emergency management replacement;
d) regulation, enforcement, permitting, compliance approval, procurement award, vendor selection, public authority substitution, certification, accreditation, recognition, maturity standing, provider approval, provider preference, public authority adoption, or public-private partnership creation; and
e) enterprise execution, asset ownership, Project SPV control, national company control, provider delivery, infrastructure operation, deployment management, or commercial execution.
Training shall further explain that technical integration, dashboards, AI outputs, digital twins, DePIN records, blockchain entries, AI-RAN signals, O-RAN signals, sensor signals, proof receipts, data rooms, controlled rooms, public-safe reports, and software releases do not create execution authority.
161.7 GCRI / GRF / GRA Role-Separation Training. Each officer shall receive training on the institutional separation among The Global Centre for Risk and Innovation - United States, GCRI Canada and other GCRI entities, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Standards, national and regional consortiums, national companies, Project SPVs, qualified enterprise providers, sponsors, hosts, funders, public authorities, universities, laboratories, communities, and enterprise actors.
Role-separation training shall explain that the Corporation’s role is 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 public-safe technical stewardship. It shall also explain that GRF steward functions include registry, recognition, maturity records, standing, claims discipline, stakeholder formation, public-safe reporting, and public-facing legitimacy, while GRA steward functions include finance-readiness, capital-readability, proof packs, insurance-readiness, diligence translation, RNFD, NFD, UNFSD, capital-reader rooms, and regulated-perimeter discipline.
Training shall emphasize:
a) evidence inputs are not recognition;
b) methods inputs are not maturity determinations;
c) technical baselines are not certification;
d) public-good software is not procurement approval;
e) proof receipts are not finance-readiness;
f) Docket or Grid support is not approval or guarantee;
g) GRA-facing technical inputs are not investment advice, insurance approval, rating, lending approval, underwriting, brokerage, public finance approval, or solicitation; and
h) Nexus-compatible language shall not be used to collapse public-good stack and enterprise stack functions.
No officer shall represent that the Corporation may bind GRF, GRA, GCRI Canada, Nexus Standards, Nexus Network, consortiums, national companies, Project SPVs, providers, sponsors, public authorities, capital readers, insurers, lenders, underwriters, universities, laboratories, or communities without express lawful authority and a competent record.
161.8 Public Authority Boundary Training. Officers with public authority, public university, public laboratory, regulator, public finance, emergency management, public health, public safety, public infrastructure, Tribal government, Indigenous government, state, territorial, local, municipal, port, utility, or government-adjacent responsibilities shall receive public authority boundary training.
Public authority boundary training shall address capacity classification, official-capacity participation, observer participation, regulator-listening participation, public finance reader participation, emergency-management participant participation, public infrastructure operator participation, simulation participation, data contribution, public authority references, public records, open meetings, procurement integrity, government ethics, gifts, lobbying, grant compliance, public authority data, and public-safe publication.
Training shall prohibit officers from stating or implying that public authority participation creates endorsement, adoption, approval, funding, regulation, public warning, emergency command, procurement approval, public finance approval, sovereign obligation, public-private partnership, public authority decision, or official validation unless the competent public authority has lawfully created that status and the record states the authority.
Where public authority ambiguity exists, officers shall be trained to hold, quarantine, re-scope, obtain counsel or compliance review, use approved public-safe limitation language, seek capacity clarification, preserve records, and correct confusing materials.
161.9 Finance, Securities, Insurance, Lending, Rating, Public Finance, Procurement, Certification, and Professional Boundary Training. Officers whose roles involve fundraising, support, sponsors, donors, funders, grants, public finance readers, insurers, lenders, investors, underwriters, banks, capital readers, proof packs, Docket support, Grid support, GRA-facing technical inputs, public authority rooms, controlled rooms, procurement-adjacent settings, technical profiles, public reports, or public claims shall receive regulated-perimeter and professional boundary training.
Training shall cover, as applicable:
a) securities, investment adviser, broker-dealer, finder, solicitation, capital placement, investment recommendation, suitability, public finance, municipal securities, grant approval, tax credit approval, banking, lending, insurance, underwriting, rating, procurement, certification, accreditation, professional advice, legal advice, engineering opinion, medical advice, public health advice, and emergency command boundaries;
b) finance-adjacent terms including finance-ready, insurance-ready, bankable, investable, capital-readable, proof pack, rating, score, grade, diligence, readiness, approval, qualification, recognition, certification, maturity, standing, Docket, Grid, Nexus-compatible, verified, validated, public-safe, conformant, and equivalent terms;
c) the difference between technical evidence support, public authority learning, capital-reader literacy, and regulated finance execution; and
d) mandatory hold, quarantine, legal review, compliance review, limitation language, public-safe clarification, withdrawal, retraction, takedown, and correction pathways where a claim could cross a regulated perimeter.
No officer shall use training, Academy materials, public authority learning, controlled-room access, technical profiles, dashboards, reports, proof receipts, evidence packs, or Nexus interface materials as a basis for regulated claims unless a separate competent authority has lawfully created and recorded the relevant status.
161.10 Data / AI / Cyber / Privacy Training. Each officer shall receive data / AI / cyber / privacy training appropriate to the officer’s role, access, systems, public materials, controlled rooms, repositories, datasets, models, dashboards, publications, public authority interfaces, and technical assets. Officers with elevated access shall receive heightened training before such access is granted.
Training shall address:
a) data classification, access control, need-to-know discipline, identity controls, authentication, authorization, logging, monitoring, retention, deletion, legal hold, public authority data, personal information, sensitive personal information, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, rights-bearing data, community-protected data, Tribal or Indigenous data, local and territorial knowledge, protected knowledge, confidential research data, and privileged materials;
b) AI-use authorization, approved systems, prohibited inputs, restricted outputs, model registers, inference records, compute workload records, agentic AI controls, prompt-injection risk, data leakage, hallucinated authority, model output review, human review, AI-use disclosure, retrieval controls, embeddings, fine-tuning restrictions, and prohibition on uploading controlled materials to unapproved AI systems;
c) cybersecurity practices, credential management, key management, secret protection, repository security, secure development, SBOM, vulnerability reporting, incident response, backup, disaster recovery, business continuity, device security, cloud controls, vendor security, access revocation, and shadow IT prohibition; and
d) privacy, consent, purpose limitation, minimization, de-identification, pseudonymization, aggregation, redaction, cross-border transfer, public-safe publication, breach response, and correction.
No officer shall access, export, upload, disclose, publish, train on, fine-tune with, embed, summarize, or process restricted materials unless the use is authorized, recorded, reviewable, and consistent with law, consent, contract, public authority restrictions, safeguards, and this Bylaw.
161.11 Research Integrity, Evidence, Methods, and Technical Truth Training. Officers whose work affects research, evidence, methods, observability, ontology, public-good R&D, public-good software, technical baselines, Truth Engine methods, verifiable compute, public-safe publication, Docket support, Grid support, GRF-facing inputs, or GRA-facing technical inputs shall receive research integrity, evidence, methods, and technical truth training.
Training shall address:
a) research integrity, research ethics, human-subjects review, community review, Tribal and Indigenous protocol review, protected knowledge review, conflict disclosure, sponsor disclosure, provider disclosure, peer review, reproducibility, replication, publication integrity, correction, supersession, withdrawal, retraction, and archive;
b) evidence classification, source lineage, provenance, custody, confidence, uncertainty, corroboration, validation, verification, disputed evidence, failed signals, spoof indicators, dashboard limitations, sensor limitations, AI output limitations, digital twin assumptions, DePIN and DLT limitations, AI-RAN and O-RAN signal limitations, geospatial limitations, Earth observation limitations, cyber evidence limitations, and degraded-mode awareness;
c) ontology, controlled vocabulary, taxonomies, schemas, data dictionaries, semantic interoperability, no-silent-meaning-shift, public-safe language, restricted-use terms, prohibited terms, and meaning control across GCRI, GRF, GRA, Nexus Network, Nexus Standards, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, consortiums, national companies, Project SPVs, and providers; and
d) the rule that technical truth methods support disciplined interpretation and correction, but do not create public authority decisions, recognition, finance-readiness, certification, procurement approval, ratings, public warnings, emergency commands, or operational instructions.
Officers shall be trained to record uncertainty rather than hide it, correct errors rather than defend them, and distinguish evidence support from institutional authority.
161.12 Public-Good Software and Secure Release Training. Officers and technical leaders with responsibility for public-good software, open technical baselines, repositories, APIs, SDKs, schemas, dashboards, data tools, models, datasets, test harnesses, benchmarks, reference architectures, technical profiles, secure release, contributor governance, open-source governance, licensing, or technical assets shall receive public-good software and secure release training.
Training shall address:
a) public-good software stewardship, open technology, open technical baselines, anti-enclosure, licensing, restricted licensing where needed, contributor license agreements, IP ownership, chain of title, attribution, moral rights where applicable, defensive publication, patent sensitivity, and standards-essential risk;
b) repository governance, branch protection, code review, secure development lifecycle, dependency review, SBOM, signing, provenance, reproducible builds where applicable, vulnerability management, secret scanning, key rotation, release approval, rollback, deprecation, takedown, archive, and correction;
c) AI-assisted development controls, model-generated code review, license contamination risk, insecure dependency risk, supply-chain compromise, malicious contribution risk, contributor conflict review, sponsor or provider influence review, export-control review, sanctions review, controlled technology review, and national security sensitivity review; and
d) public-safe documentation, limitation language, no-certification notices, no-procurement notices, no-provider-preference notices, no-public-authority-action notices, and no-finance-readiness notices.
No public-good software release, technical baseline, repository permission, maintainer role, fork, compatibility note, profile, benchmark, proof receipt, dashboard, API, SDK, or reference implementation shall be represented as certification, accreditation, procurement approval, provider preference, public authority decision, finance-readiness, recognition, or enterprise execution authority.
161.13 Civil Rights, Accessibility, Tribal / Indigenous Protocol, Community Safeguards, Protected Knowledge, Public-Safe Mapping, Grievance, and Non-Retaliation Training. Each officer shall receive safeguards training appropriate to the officer’s role, with heightened training for officers whose work affects communities, Tribal Nations, Indigenous governments, Indigenous knowledge holders, local or territorial knowledge, protected knowledge, civil rights, accessibility, public-safe mapping, public authority learning, research participation, public reporting, dashboards, data releases, controlled rooms, public-safe publications, or grievances.
Safeguards training shall address:
a) civil rights, non-discrimination, accessibility, inclusive participation, disability access, language access, public-safe communication, community harm prevention, vulnerable and remote community safeguards, protected participation, grievance pathways, remedy pathways, non-retaliation, harassment prevention, and whistleblower protection;
b) Tribal sovereignty respect, Indigenous governance respect, Indigenous data safeguards, Indigenous knowledge safeguards, protected knowledge restrictions, consent, non-consent, withdrawal, attribution, non-attribution, restricted circulation, public-safe mapping, location sensitivity, cultural sensitivity, environmental sensitivity, health sensitivity, and do-no-harm review;
c) avoiding extraction of protected knowledge for sponsor, provider, donor, funder, host, public authority, research, technical, publication, AI, dashboard, or institutional convenience; and
d) stop-the-line authority, escalation pathways, emergency restriction, controlled or public correction, public-safe limitation, takedown, retraction, withdrawal, sealing, and access revocation.
No officer shall treat safeguards as optional, secondary, reputational, or merely procedural. Safeguards are substantive controls on authority, publication, access, data use, AI use, mapping, technical development, public authority interface, and Nexus-compatible activity.
161.14 Competition, Sanctions, Export-Control, Controlled Technology, and National Security Sensitivity Training. Officers whose work involves meetings, councils, committees, working groups, industry participants, providers, sponsors, vendors, data sharing, benchmarking, technical comparisons, standardization support, public authority rooms, capital-reader rooms, controlled rooms, international or cross-border activity, AI-RAN, O-RAN, DePIN, DLT, blockchain, cybersecurity, sovereign compute, HPC, geospatial systems, Earth observation, sensors, drones, robotics, semiconductors, advanced manufacturing, controlled technology, or mission-critical infrastructure shall receive competition, sanctions, export-control, controlled technology, and national security sensitivity training.
Training shall address:
a) antitrust and competition-law meeting discipline, prohibited topics, price, margin, cost, wage, bid, customer, supplier, market allocation, capacity, exclusion, boycott, procurement steering, collusive strategy, competitively sensitive information, clean-team structures, clean-room structures, aggregation, de-identification, delay, independent administration, agenda controls, minute controls, and stop-meeting authority;
b) sanctions screening, restricted-party screening, export-control classification, deemed exports, controlled technology, defense or dual-use sensitivity, national security sensitivity, CFIUS-relevant sensitivity where applicable, cyber-sensitive and infrastructure-sensitive materials, cross-border transfers, foreign participation controls, and controlled-room access limits;
c) public authority, public procurement, grant, gifts, government ethics, lobbying, political activity, and procurement integrity issues where applicable; and
d) incident escalation, legal review, access restriction, export hold, contribution quarantine, software release hold, dataset restriction, meeting stoppage, correction, and referral where required.
No officer shall permit the Corporation’s public-good mission to be used as cover for collusion, sanctions evasion, export-control evasion, controlled technology leakage, improper procurement influence, public authority capture, or market coordination.
161.15 Certification of Understanding. The Corporation may require each officer to execute a certification of understanding upon appointment, annually, upon material role change, upon receipt of new authority, upon access to restricted systems, upon participation in controlled rooms, upon involvement in public authority interfaces, upon involvement in finance-adjacent or GRA-facing technical inputs, upon involvement in GRF-facing inputs, upon involvement in software releases, upon involvement in protected knowledge, and upon completion of required training.
An officer certification may require the officer to certify that the officer understands and agrees to comply with:
a) this Bylaw, the Articles or Certificate, Board resolutions, policies, delegations, authority matrices, and applicable procedures;
b) public-benefit purpose, nonprofit character, tax-exempt or tax-exempt-compatible restrictions, no private inurement, no impermissible private benefit, conflict disclosure, and recusal obligations;
c) non-execution, GCRI / GRF / GRA role separation, public-good stack / enterprise stack separation, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, and professional boundaries;
d) data / AI / cyber / privacy controls, research integrity, evidence integrity, methods integrity, technical truth controls, public-good software controls, secure release controls, public-safe publication controls, and correctionability;
e) civil rights, accessibility, community safeguards, Tribal and Indigenous protocol respect, Indigenous data safeguards, protected knowledge, grievance pathways, protected participation, and non-retaliation;
f) competition, sanctions, export-control, controlled technology, national security sensitivity, public authority participation, public records, government ethics, gifts, lobbying, grant, and procurement integrity controls where applicable; and
g) the duty to escalate risk, report incidents, preserve records, avoid overclaims, support correction, and refrain from retaliation.
A certification of understanding shall be a governance record. False, misleading, incomplete, stale, or reckless certification may support corrective training, access restriction, delegation suspension, investigation, compensation review, repayment, removal, contract action, public or controlled correction, legal referral, or other remedy.
161.16 Performance Evaluation. The Corporation may evaluate officer performance periodically, annually, event-based, role-based, project-based, grant-based, program-based, incident-based, or upon material change in responsibility. Evaluation shall assess not only output, speed, fundraising, program growth, technical production, stakeholder engagement, or public visibility, but also compliance with law, the Articles or Certificate, this Bylaw, Board resolutions, policies, delegations, authority matrices, records discipline, public-safe claim discipline, non-execution, role separation, safeguards, data / AI / cyber controls, correctionability, and institutional trust.
Officer evaluation may consider, as applicable:
a) performance against Board-approved strategy, budget, plan, delegation, program goals, public-benefit objectives, and lawful operating targets;
b) quality of Board reporting, committee reporting, records, registers, repository discipline, version control, decision logs, incident logs, correction logs, and closeout records;
c) management of conflicts, related parties, recusals, public authority interfaces, sponsor relationships, provider relationships, donor or funder relationships, host relationships, public claims, and external representations;
d) evidence integrity, research integrity, methods discipline, observability discipline, ontology discipline, public-good software stewardship, secure release, technical asset protection, and public-safe publication quality;
e) data governance, AI governance, cybersecurity, privacy, controlled-room discipline, access control, incident response, business continuity, and disaster recovery performance;
f) civil rights, accessibility, community safeguards, Tribal and Indigenous protocol respect, protected knowledge protection, grievance handling, remedy handling, protected participation, and non-retaliation performance; and
g) regulatory-perimeter judgment, finance-boundary discipline, certification-boundary discipline, procurement neutrality, provider neutrality, sponsor non-control, anti-capture conduct, competition discipline, sanctions compliance, export-control compliance, and professional boundary discipline.
Officer evaluation shall be conducted fairly, records-supported, non-retaliatory, and with appropriate confidentiality. Evaluation shall not reward boundary violations, overclaims, hidden execution, sponsor capture, provider preference, unsupported public claims, unmanaged growth, or public authority confusion.
161.17 Corrective Training. The Corporation may require corrective training where an officer has not completed required training, has failed to maintain understanding, has acted outside authority, has produced defective records, has made or permitted public-safe claim errors, has created public authority confusion, has created finance-boundary or certification-boundary risk, has failed to use controlled vocabulary, has mishandled data, has misused AI, has contributed to cyber risk, has mishandled protected knowledge, has failed to respect safeguards, has mishandled a conflict, has failed to escalate, has failed to support correction, or has otherwise created institutional risk.
Corrective training may be imposed alone or together with:
a) written warning;
b) supervision;
c) access restriction;
d) delegation restriction;
e) authority matrix revision;
f) publication restriction;
g) public statement restriction;
h) data access restriction;
i) AI-use restriction;
j) repository access restriction;
k) controlled-room restriction;
l) public authority interface restriction;
m) conflict mitigation;
n) recusal;
o) performance improvement plan;
p) compensation review;
q) suspension;
r) removal; or
s) other lawful remedy.
Corrective training shall be tailored to the failure and shall not be used as a substitute for required discipline, investigation, correction, public or controlled clarification, legal review, safeguards review, data / AI / cyber review, Board review, or removal where the severity of the matter requires more than training. Completion of corrective training shall be recorded.
161.18 Officer Accountability Records. The Corporation shall maintain Officer Training, Certification, Evaluation, and Accountability Records sufficient to demonstrate that officers were trained, certified, evaluated, corrected, restricted, held accountable, and supported in a manner consistent with law, the Articles or Certificate, this Bylaw, Board resolutions, policies, delegations, public-benefit purpose, nonprofit character, tax-exempt or tax-exempt-compatible obligations, non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, and correctionability.
Officer Accountability Records shall include, as applicable:
a) onboarding training records, Bylaw training records, fiduciary and public-benefit training records, nonprofit and tax training records, all-states-and-territories training records, North America interface training records, non-execution training records, role-separation training records, public authority boundary training records, finance-boundary training records, certification-boundary training records, procurement-neutrality training records, professional-boundary training records, data / AI / cyber / privacy training records, research integrity training records, public-good software training records, safeguards training records, competition training records, sanctions training records, export-control training records, controlled-technology training records, and national security sensitivity training records;
b) training assignments, training completion records, training waiver records where lawful, training deferral records, temporary exception records, failed training records, refresher records, corrective training records, retraining records, and training materials version records;
c) certification of understanding records, annual certification records, event-based certification records, role-change certification records, access-based certification records, controlled-room certification records, public authority interface certification records, data / AI / cyber certification records, safeguards certification records, finance-boundary certification records, and correction certification records;
d) officer evaluation records, performance review records, Board feedback records, committee feedback records, supervisor feedback records, self-assessment records, peer feedback records where approved, public authority interface feedback where lawful, safeguards feedback, incident-linked evaluation records, and improvement plan records;
e) corrective action records, access restriction records, delegation restriction records, authority matrix revision records, recusal records, conflict mitigation records, public statement restriction records, publication restriction records, data access restriction records, AI-use restriction records, repository restriction records, controlled-room restriction records, public authority interface restriction records, suspension records, removal records, contract action records, repayment records, public or controlled correction records, and legal referral records;
f) records of exceptions requested, exceptions refused, exceptions approved where lawful, unresolved risks, open action items, responsible owners, deadlines, closeout confirmations, and correction history; and
g) responsible custodian, repository location, access class, publication class, confidentiality class, retention class, legal hold status, sealing status, deletion status, archive status, review date, and metadata.
The governing rule of this Section is that officer authority shall be trained before it is exercised, certified before it is relied upon, evaluated after it is used, corrected when it fails, and recorded throughout. The Corporation shall not rely on informal confidence, reputation, expertise, urgency, title, or relationship as a substitute for officer training, certification, evaluation, and accountability. Officer accountability is part of the Corporation’s public-good architecture: it protects mission lock, legal separateness, technical truth, public-safe communication, safeguards, public authority boundaries, finance and certification boundaries, records integrity, and correctionability.
Section 162. Enforcement of Article V
162.1 Article V Enforcement Purpose. Article V shall be enforced to preserve lawful officer authority, Board supremacy, public-benefit purpose, nonprofit character, tax-exempt or tax-exempt-compatible discipline, United States legal separateness, all-states-and-territories operating integrity, North America anchor boundaries, non-execution, GCRI / GRF / GRA role separation, public-good stack and enterprise stack separation, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, research integrity, evidence integrity, methods integrity, technical truth integrity, public-safe publication, community safeguards, protected knowledge, civil rights, accessibility, validity-by-record, and correctionability.
Enforcement of this Article shall be corrective, protective, proportionate, records-supported, non-retaliatory, and mission-preserving. It shall not be used to punish good-faith dissent, protected participation, whistleblowing, public-safe correction, safeguards escalation, cyber incident reporting, conflict disclosure, refusal to perform a prohibited function, refusal to make an unsupported public claim, refusal to approve an overclaim, or lawful escalation of public authority, finance, certification, procurement, provider, sponsor, data, AI, cyber, safeguards, or Nexus boundary concerns.
The Corporation may enforce this Article through training, written direction, warning, supervision, access restriction, delegation restriction, recusal, reassignment, authority matrix revision, compensation review, repayment, contract action, investigation, corrective action, suspension, removal, public or controlled correction, legal review, regulatory referral, public authority clarification, funder notice, law enforcement referral where required or appropriate, or other lawful remedy. Enforcement shall be guided by the seriousness of the conduct, risk created, harm caused, intent, repetition, cooperation, correction, record integrity, and continuing fitness for office.
162.2 Officer Authority Violation Review. An officer authority violation review shall be initiated where there is credible concern that an officer has acted, attempted to act, represented authority, permitted reliance, approved a record, issued a statement, accessed materials, signed an instrument, authorized payment, approved publication, released software, admitted persons to a controlled room, made a public authority reference, made a finance-adjacent statement, or otherwise exercised power outside the officer’s lawful appointment, delegation, authority matrix, Board-approved budget, Board resolution, policy, contract, or this Bylaw.
Authority violations may include, without limitation:
a) acting without appointment or after resignation, removal, suspension, expiration, recusal, access revocation, delegation termination, or loss of eligibility;
b) acting beyond delegated budget authority, signature authority, contracting authority, spending authority, publication authority, data access authority, AI-use authority, model approval authority, software release authority, repository authority, controlled-room authority, public authority reference authority, correction authority, or incident response authority;
c) approving or committing the Corporation to a Board reserved matter without Board approval;
d) binding, purporting to bind, or implying authority to bind GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Standards, consortiums, national companies, Project SPVs, providers, sponsors, hosts, funders, public authorities, universities, laboratories, communities, or enterprise actors without express lawful authority;
e) treating technical centrality, authorship, system access, public authority relationship, sponsor relationship, provider relationship, operational urgency, founder status, public profile, or seniority as authority; or
f) using AI systems, dashboards, proof receipts, ledger entries, role keys, software permissions, repository rights, controlled-room admission, or technical workflows as substitutes for corporate authority.
Where an officer authority violation is suspected, the Corporation may hold the affected act, restrict further reliance, suspend related access, preserve records, notify the Board or competent officer, seek counsel review, require corrective certification, and determine whether ratification is available. No unauthorized act shall be treated as valid merely because it was operationally convenient, technically implemented, publicly circulated, relied upon by an external party, requested by a sponsor, requested by a provider, requested by a public authority participant, or not immediately challenged.
162.3 Delegation Violation Review. A delegation violation review shall be initiated where an officer has acted outside a delegation, failed to comply with delegation conditions, sub-delegated without authority, failed to record delegated action, exceeded approval thresholds, ignored required co-approval, failed to escalate a reserved matter, failed to observe sunset conditions, or used delegation to create prohibited authority.
Delegation violations include, without limitation:
a) exceeding spending, contracting, signature, publication, data access, AI-use, software release, repository, controlled-room, public authority interface, incident response, correction, or public statement limits;
b) treating a temporary delegation as permanent, a conditional delegation as unconditional, an internal delegation as external authority, or a technical permission as legal authority;
c) sub-delegating to staff, contractors, fellows, advisors, volunteers, contributors, providers, sponsors, public authority participants, university personnel, laboratory personnel, committee members, working groups, AI agents, software workflows, or automated systems without express authority;
d) bypassing required review by counsel, compliance, finance, tax, data / AI / cyber, research integrity, safeguards, public authority, or Board bodies;
e) using delegated authority during a conflict, recusal, suspension, investigation, legal hold, access restriction, or emergency hold; or
f) using a delegation to perform public authority action, finance execution, investment advice, securities activity, lending, insurance placement, underwriting, rating, procurement approval, certification, recognition, provider preference, sponsor control, public warning, emergency command, or enterprise execution.
Delegation violation review shall examine the delegation instrument, authority matrix, Board records, policies, budget, approval thresholds, communications, access logs, affected transactions, affected publications, affected technical releases, affected room admissions, and affected public claims. The Corporation may suspend, narrow, revoke, restate, or correct the delegation; require ratification where lawful; reverse or hold affected acts; and update the delegation register.
162.4 Conflict or Recusal Violation Review. A conflict or recusal violation review shall be initiated where an officer has failed to disclose a conflict, disclosed incompletely, disclosed late, participated after recusal was required, accessed restricted materials during recusal, influenced a decision from which the officer was recused, approved a related-party transaction without proper review, failed to update a conflict record, or used office to benefit a related person, sponsor, provider, donor, funder, host, public authority participant, investor, insurer, lender, underwriter, bank, national company, Project SPV, university, laboratory, contractor, or enterprise actor.
Conflict or recusal violation review shall address:
a) financial conflicts, institutional conflicts, employment conflicts, consulting conflicts, advisory conflicts, research conflicts, publication conflicts, IP conflicts, data / AI / cyber conflicts, public authority conflicts, sponsor conflicts, provider conflicts, donor or funder conflicts, host conflicts, capital actor conflicts, and family or related-person conflicts;
b) whether disclosure occurred before deliberation, recommendation, approval, access, signature, publication, public statement, data use, AI use, software release, controlled-room admission, or public authority interface;
c) whether the officer improperly influenced staff, committees, councils, working groups, reviewers, public authority participants, sponsors, providers, donors, funders, hosts, technical contributors, or external actors;
d) whether the affected action requires ratification, re-review, withdrawal, amendment, repayment, contract action, public-safe clarification, access revocation, or removal; and
e) whether the violation indicates capture risk, private benefit risk, excess benefit risk, procurement-neutrality risk, provider-preference risk, sponsor-control risk, public authority confusion, finance-boundary overclaim, certification-boundary overclaim, or research integrity concern.
No conflict shall be cured by disclosure alone where the conflict requires recusal, independent review, access restriction, delegation restriction, Board review, or prohibition. No officer may vote, recommend, approve, sign, certify, publish, release, admit, or influence through informal channels where the officer is recused.
162.5 Compensation or Private Benefit Violation Review. A compensation or private benefit violation review shall be initiated where there is credible concern that officer compensation, benefits, reimbursement, travel, consulting fees, contractor payments, stipends, bonuses, severance, grants, awards, program support, related-party payments, vendor arrangements, sponsorship benefits, donor benefits, provider benefits, host benefits, IP arrangements, data arrangements, software arrangements, controlled-room access, public authority access, publication treatment, or public recognition may create excessive compensation, private inurement, impermissible private benefit, self-dealing, excess benefit, unlawful distribution, unreasonable reimbursement, unsupported expense, or mission-inconsistent advantage.
The review shall consider:
a) Board approval, delegated approval, independent approval, comparability, reasonableness, documentation, conflict disclosure, recusal, tax treatment, employment or contractor classification, grant restrictions, donor restrictions, restricted fund restrictions, and reimbursement policies;
b) whether the officer approved, influenced, or received a benefit without proper independent review;
c) whether compensation or benefits were tied to sponsorship, fundraising outcome outside policy, provider selection, public authority access, recognition, finance-readiness, certification, procurement, technical baseline inclusion, dashboard placement, publication outcome, research finding, software feature, Docket support, Grid support, GRF-facing input, GRA-facing input, or regulated execution;
d) whether a sponsor, donor, funder, provider, host, investor, insurer, lender, bank, public authority participant, national company, Project SPV, contractor, university, laboratory, or related party received improper benefit through officer action; and
e) whether repayment, correction, compensation adjustment, tax reporting, Board ratification where lawful, contract action, support refusal, support return, benefit termination, disclosure, or legal review is required.
No compensation, reimbursement, support benefit, access benefit, publication benefit, technical benefit, room benefit, or public acknowledgment shall be used to purchase officer loyalty, institutional outcome, public authority access, provider preference, sponsor control, recognition, finance-readiness, certification, procurement advantage, or enterprise-stack advantage.
162.6 Records Violation Review. A records violation review shall be initiated where an officer fails to create, maintain, protect, version, deposit, update, correct, retain, archive, seal, return, transfer, delete, preserve, or produce records required by law, the Articles or Certificate, this Bylaw, Board resolution, policy, delegation, contract, grant, restricted fund, public authority interface, data / AI / cyber requirement, safeguards requirement, legal hold, audit, investigation, or correction process.
Records violations include, without limitation:
a) failure to record appointment, delegation, authority, approval, decision, conflict, recusal, payment, contract, publication, data access, AI use, model approval, inference record, compute workload record, software release, repository access, controlled-room admission, public authority reference, incident, correction, withdrawal, retraction, takedown, or archive action;
b) backdating, deleting, altering, concealing, fragmenting, bypassing repositories, using shadow records, using personal accounts, using unapproved messaging systems, using unapproved AI systems, failing to preserve logs, failing to preserve metadata, or failing to comply with legal hold;
c) treating unofficial drafts, slides, AI summaries, emails, working copies, repository forks, public explainers, translations, screenshots, dashboards, ledger entries, proof receipts, role keys, or informal notes as operative authority without proper adoption and record;
d) failure to deposit material officer records in the official repository or controlled repository; and
e) failure to correct, supersede, withdraw, retract, or archive defective records.
The Corporation may require immediate record preservation, repository deposit, metadata reconstruction, access log review, forensic preservation, legal hold, certification of completeness, correction entry, supersession notice, audit review, counsel review, or access restriction. Records discipline is not administrative housekeeping; it is the basis of validity-by-record, accountability, public-safe operation, legal defensibility, Nexus interoperability, and correctionability.
162.7 Public Authority Boundary Violation Review. A public authority boundary violation review shall be initiated where an officer states, implies, permits, fails to correct, or materially enables a representation that the Corporation, an officer, a committee, a controlled room, a public authority room, a report, a dashboard, a map, a dataset, a software release, a technical baseline, a public-safe notice, a proof receipt, a Nexus-compatible interface, or a public authority participant has created public authority action, official endorsement, regulatory approval, public warning, emergency command, procurement approval, funding approval, public finance approval, sovereign obligation, public-private partnership, public authority decision, or governmental delegation.
Review shall address:
a) capacity classification, official-capacity records, observer records, regulator-listening records, public finance reader records, emergency-management participant records, public infrastructure operator records, simulation records, public authority data contribution records, public authority reference records, and public statement approvals;
b) whether public authority materials were circulated without approved limitation language;
c) whether the officer used public authority names, seals, titles, rooms, data, statements, participation, meeting attendance, or correspondence in a confusing or unauthorized manner;
d) whether public records, FOIA, open meetings, public procurement, lobbying, gifts, grant, government ethics, public sector data, cybersecurity, privacy, or emergency management constraints were implicated; and
e) whether controlled correction, public correction, notice to the public authority, withdrawal, takedown, contract action, access restriction, training, recusal, suspension, or removal is required.
No officer shall use public authority participation as leverage for fundraising, provider preference, sponsor benefit, procurement advantage, finance-readiness, recognition, certification, public legitimacy, public warning, emergency command, or enterprise execution.
162.8 Finance, Securities, Insurance, Lending, Rating, Public Finance, Procurement, Certification, Recognition, Provider-Preference, Sponsor-Control, or Public Warning Boundary Violation Review. A boundary violation review shall be initiated where an officer states, implies, permits, fails to correct, or materially enables a claim that the Corporation has performed or authorized a prohibited or externally reserved function, including finance-readiness determination, insurance-readiness determination, bankability determination, investability determination, capital-readability determination, securities solicitation, investment advice, brokerage, finder activity, lending, insurance placement, underwriting, rating, public finance approval, procurement approval, certification, accreditation, recognition, maturity standing, provider preference, sponsor entitlement, public warning, emergency command, or enterprise execution.
The review shall examine the affected contracts, proposals, presentations, websites, public statements, grant materials, sponsorship materials, investor materials, insurance materials, lender materials, public authority materials, bid materials, room materials, dashboards, maps, software documentation, technical profiles, public-good baselines, model cards, system cards, benchmark cards, proof receipts, Docket-support inputs, Grid-support inputs, GRF-facing inputs, GRA-facing technical inputs, and Nexus-compatible labels.
The Corporation shall determine whether the matter requires:
a) immediate hold, quarantine, access restriction, publication freeze, implementation freeze, technical isolation, room lockdown, or public statement restriction;
b) counsel review, compliance review, finance-boundary review, procurement-neutrality review, certification-boundary review, GRF interface review, GRA interface review, public authority review, or Board review;
c) withdrawal, supersession, correction, retraction, takedown, limitation language, controlled clarification, public clarification, sponsor notice, provider notice, funder notice, public authority notice, or affected-party notice;
d) suspension, removal, delegation revocation, compensation review, contract action, support refusal, support return, or repayment; and
e) referral to competent external authority where legally required or appropriate.
No officer shall defend a boundary violation on the basis that the statement was aspirational, informal, commercially expected, commonly used in the market, requested by a funder, requested by a sponsor, requested by a provider, requested by a public authority participant, needed for fundraising, or generated by AI.
162.9 Data / AI / Cyber / Privacy Violation Review. A data / AI / cyber / privacy violation review shall be initiated where an officer accesses, uses, discloses, transfers, exports, publishes, uploads, trains on, fine-tunes with, embeds, summarizes, stores, deletes, alters, combines, re-identifies, downloads, copies, or processes data, AI systems, models, code, credentials, keys, secrets, repositories, dashboards, public authority materials, controlled-room materials, or technical assets in violation of law, consent, contract, policy, access class, data classification, AI-use rules, cyber rules, privacy rules, public authority restrictions, protected knowledge restrictions, or this Bylaw.
Review shall address:
a) personal information, sensitive personal information, rights-bearing data, health-sensitive data, children’s data, cyber-sensitive data, infrastructure-sensitive data, public authority data, community-protected data, Tribal and Indigenous data, local and territorial knowledge, protected knowledge, confidential research data, privileged materials, sponsor or provider confidential information, and repository secrets;
b) use of approved or unapproved AI systems, agentic AI, retrieval systems, embeddings, model improvement, fine-tuning, training data, prompts, outputs, inference records, compute workload records, model registers, dataset cards, model cards, system cards, benchmark cards, and evaluation harnesses;
c) unauthorized access, credential sharing, secret leakage, key misuse, shadow IT, side-channel storage, repository compromise, insecure release, disabled logs, deleted logs, unreported incidents, delayed incident reporting, insufficient backup, insufficient disaster recovery, or vendor security failure;
d) breach notification, regulator notification, public authority notification, participant notification, donor or funder notification, cyber insurer notification, legal hold, forensic preservation, and evidence preservation obligations; and
e) containment, revocation, quarantine, deletion hold, publication freeze, model freeze, dataset freeze, access suspension, correction, retraction, takedown, or public-safe clarification.
No officer shall use AI output, system convenience, technical access, urgency, or public benefit as justification for violating data, privacy, cyber, public authority, consent, or protected knowledge controls.
162.10 Research Integrity, Evidence, Methods, or Technical Asset Violation Review. A research integrity, evidence, methods, or technical asset violation review shall be initiated where an officer causes, contributes to, approves, conceals, or fails to correct fabrication, falsification, plagiarism, unsupported claim, misleading evidence classification, defective source lineage, defective provenance, broken chain of custody, improper confidence statement, improper uncertainty statement, undisclosed sponsor influence, undisclosed provider influence, suppressed contrary evidence, manipulated dashboard, manipulated model output, manipulated benchmark, manipulated digital twin assumption, manipulated AI-RAN or O-RAN signal interpretation, manipulated DePIN or DLT record, manipulated geospatial output, manipulated Earth observation output, or defective public-good technical asset.
Review shall include, as applicable:
a) evidence registers, method registers, observability records, ontology records, technical truth records, proof receipt records, public-safe publication records, research records, peer review records, model review records, red-team records, repository records, release records, SBOM records, vulnerability records, dataset cards, model cards, system cards, benchmark cards, and correction records;
b) research ethics, human-subjects review, community review, Tribal and Indigenous protocol review, health-sensitive review, youth or vulnerable population review, protected knowledge review, data / AI / cyber review, sponsor independence review, provider independence review, and publication integrity review;
c) whether the affected output has been used in Docket support, Grid support, GRF-facing inputs, GRA-facing technical inputs, public authority learning, public-safe reporting, controlled rooms, public dashboards, public maps, technical baselines, public-good software, evidence packs, proof packs, training, Academy materials, grant reports, sponsor reports, provider materials, or public statements; and
d) whether correction, supersession, withdrawal, retraction, takedown, re-review, independent review, public-safe clarification, repository correction, metadata correction, access restriction, suspension, or removal is required.
No officer shall suppress correction to protect reputation, fundraising, sponsor relationships, provider relationships, public authority relationships, publication schedules, technical pride, media strategy, or program continuity.
162.11 Civil Rights, Accessibility, Community Safeguards, Tribal / Indigenous, Protected Knowledge, or Public-Safe Publication Violation Review. A safeguards violation review shall be initiated where an officer causes, contributes to, approves, conceals, or fails to correct civil-rights harm, accessibility failure, discrimination, harassment, retaliation, grievance suppression, remedy failure, protected participation breach, community harm, public-safe mapping defect, Tribal or Indigenous protocol breach, Indigenous data safeguard breach, local or territorial knowledge breach, protected knowledge exposure, unauthorized attribution, unauthorized non-attribution, consent violation, withdrawal violation, restricted-circulation violation, do-no-harm failure, or unsafe public communication.
The review shall consider:
a) whether affected persons, communities, Tribal Nations, Indigenous governments, Indigenous knowledge holders, local or territorial knowledge holders, vulnerable communities, remote communities, youth, protected classes, accessibility users, research participants, public authority participants, or protected reporters were placed at risk;
b) whether maps, dashboards, datasets, reports, images, public statements, AI outputs, models, digital twins, sensor outputs, geospatial outputs, Earth observation outputs, proof receipts, public authority materials, controlled-room materials, Academy materials, or technical documentation created unsafe exposure;
c) whether notice, consent, non-consent, withdrawal, attribution, non-attribution, restriction, sealing, deletion, takedown, retraction, public-safe redaction, community review, Tribal or Indigenous interface review, accessibility correction, grievance pathway, remedy pathway, non-retaliation protection, or stop-the-line action is required; and
d) whether the officer’s access, delegation, publication authority, data access, AI-use authority, public authority interface authority, controlled-room authority, or external representation authority should be restricted, suspended, or revoked.
Safeguards review shall not be subordinated to technical timelines, sponsor expectations, provider expectations, grant deadlines, publication goals, public authority interest, fundraising goals, media strategy, or event schedules. Where harm risk cannot be cured by notice, the Corporation shall hold, restrict, withdraw, re-scope, quarantine, correct, refer, or terminate the affected activity.
162.12 Corrective Action. The Corporation may impose corrective action where an officer violates or may have violated this Article, where risk requires protective intervention, or where corrective action is necessary to preserve lawful authority, public-benefit purpose, records integrity, boundary discipline, data / AI / cyber controls, safeguards, or correctionability. Corrective action may be informal or formal, immediate or staged, temporary or continuing, internal or public-safe, depending on the risk.
Corrective action may include:
a) oral or written direction;
b) written warning;
c) required training or corrective training;
d) certification of understanding;
e) increased supervision;
f) narrowed delegation;
g) authority matrix revision;
h) recusal or conflict mitigation;
i) access restriction;
j) publication restriction;
k) public statement restriction;
l) data access restriction;
m) AI-use restriction;
n) repository restriction;
o) software release restriction;
p) controlled-room restriction;
q) public authority interface restriction;
r) correction, supersession, withdrawal, retraction, takedown, or public-safe clarification;
s) repayment, reimbursement denial, compensation adjustment, contract action, or support return where lawful;
t) investigation, audit, legal review, safeguards review, data / AI / cyber review, or Board review; or
u) suspension, removal, referral, or legal action where required or appropriate.
Corrective action shall be proportionate but need not wait for final findings where interim protection is required. The Corporation may act on credible risk, urgent uncertainty, incomplete records, or precautionary grounds where delay could increase harm.
162.13 Access Restriction. The Corporation may restrict, suspend, revoke, reduce, monitor, quarantine, or reclassify officer access where necessary to enforce this Article. Access restriction may apply to physical premises, Board materials, officer records, financial systems, bank systems, payroll systems, grant systems, donor systems, sponsor systems, public authority materials, repositories, cloud systems, communication systems, email, domains, keys, tokens, credentials, AI systems, datasets, models, dashboards, controlled rooms, clean rooms, data rooms, evidence rooms, no-download rooms, public authority rooms, code repositories, signing systems, software release pipelines, public statement channels, and public-good technical assets.
Access restriction shall be immediate where there is material risk involving cybersecurity, data protection, protected knowledge, public authority materials, financial controls, research integrity, evidence integrity, publication integrity, sponsor capture, provider preference, retaliation, harassment, misconduct, unauthorized public claims, or legal hold. Access restriction may be imposed without prior notice where notice would increase risk, permit destruction or alteration of records, compromise cyber containment, expose protected knowledge, impair investigation, or undermine safeguards.
Access restriction records shall identify the officer, access categories affected, systems affected, authority for restriction, reason, effective date, duration, review date, custodian, exceptions, monitoring requirements, restoration conditions, and closeout. No officer shall retain access by title, founder status, public authority relationship, technical centrality, authorship, sponsor relationship, provider relationship, or operational dependency.
162.14 Delegation Suspension. The Corporation may suspend, narrow, revoke, condition, restate, or reassign an officer’s delegation where the officer has violated this Article, where risk requires protective intervention, where authority has become unclear, where conflicts are unmanaged, where records are defective, where public authority or finance-boundary confusion exists, where data / AI / cyber or safeguards concerns exist, or where the Board or competent authority determines that continued delegation would be inconsistent with public-benefit purpose or institutional integrity.
Delegation suspension may apply to spending authority, contracting authority, signature authority, bank authority, publication authority, public statement authority, public authority reference authority, data access authority, AI-use authority, model approval authority, repository authority, software release authority, controlled-room admission authority, incident response authority, correction authority, support acceptance authority, sponsor relationship authority, provider relationship authority, and Nexus interface authority.
Delegation suspension shall not be treated as a final finding unless the competent record so states. The Corporation may impose temporary delegation suspension pending review, require co-approval, require Board approval, require counsel review, require compliance review, require safeguards review, require data / AI / cyber review, require financial review, or assign authority to an acting officer or interim delegate. Delegation suspension shall be recorded in the delegation register and authority matrix where applicable.
162.15 Officer Suspension or Removal. The Corporation may suspend or remove an officer in accordance with applicable law, the Articles or Certificate, this Bylaw, the officer’s appointment instrument, employment agreement, contractor agreement, Board resolution, delegation instrument, and policy. Suspension or removal may be imposed where necessary to protect the Corporation, even if separate employment, contractor, fellowship, advisory, committee, or program status requires separate action.
Grounds for suspension or removal include breach of duty, acting outside authority, loss of eligibility, unmanaged conflict, misconduct, persistent non-performance, refusal to maintain records, refusal to cooperate with review, misuse of name or marks, unauthorized public statement, unauthorized commitments, public authority overclaim, finance-boundary overclaim, certification-boundary overclaim, procurement-neutrality breach, provider-preference claim, sponsor-control violation, data misuse, AI misuse, cyber misconduct, research misconduct, protected knowledge breach, civil-rights violation, accessibility violation, harassment, retaliation, sanctions issue, export-control issue, controlled-technology issue, competition violation, private benefit concern, fraud, financial control failure, or conduct inconsistent with public-benefit purpose, non-execution, role separation, safeguards, validity-by-record, or correctionability.
Suspension or removal records shall identify authority, effective date, basis, votes or approvals where applicable, conflicts and recusals, access consequences, delegation consequences, signing authority consequences, public statement consequences, transition instructions, handover requirements, records custody, return or deletion duties, correction duties, and notices required. Removal from office shall not, by itself, waive confidentiality, records, cooperation, repayment, correction, data, cyber, safeguards, or legal obligations accrued before removal.
162.16 Contractual Remedy. Where an officer is also an employee, contractor, consultant, advisor, fellow, volunteer, seconded person, contributor, maintainer, or party to an agreement with the Corporation, the Corporation may pursue contractual remedies in addition to governance remedies. Contractual remedies may include warning, cure notice, suspension of services, reassignment, contract amendment, termination, clawback, repayment, withholding where lawful, indemnity claim, confidentiality enforcement, IP assignment enforcement, data return, materials return, device return, access revocation, license termination, non-disparagement enforcement where lawful, non-solicitation enforcement where lawful, or other remedy provided by contract or law.
Contractual remedies shall be coordinated with nonprofit law, tax rules, employment law, contractor classification, volunteer rules, wage and hour rules, whistleblower protections, civil-rights protections, non-retaliation, privacy, cyber, protected knowledge, public authority restrictions, legal hold, and this Bylaw. No contractual remedy shall be used to suppress lawful reporting, protected participation, correction, safeguards escalation, cyber incident reporting, conflict disclosure, or refusal to perform a prohibited function.
Where contractual remedies affect public-good software, open technical baselines, repositories, datasets, models, dashboards, controlled rooms, public authority materials, sponsor materials, provider materials, grant deliverables, public-safe publications, or Nexus interfaces, the Corporation shall preserve records, maintain continuity, protect rights, correct public claims, and avoid unlawful disruption.
162.17 Public or Controlled Correction. The Corporation may issue a public or controlled correction where an officer violation, alleged violation, authority defect, delegation defect, conflict defect, records defect, public authority confusion, finance-boundary overclaim, certification-boundary overclaim, procurement-neutrality issue, provider-preference claim, sponsor-control concern, data / AI / cyber incident, research integrity issue, evidence defect, safeguards concern, protected knowledge exposure, or public-safe publication error creates actual or potential reliance risk.
A correction may clarify, as applicable, that:
a) an officer lacked authority;
b) an officer’s authority was limited, suspended, revoked, superseded, or corrected;
c) a statement, publication, dataset, dashboard, software release, technical profile, public-safe report, proof receipt, room material, presentation, contract, proposal, sponsorship material, grant material, public authority material, investor material, insurance material, lender material, or public claim was unauthorized, limited, withdrawn, superseded, retracted, corrected, or under review;
d) no public authority approval, public warning, emergency command, finance-readiness, insurance-readiness, rating, investment recommendation, securities solicitation, lending approval, insurance approval, public finance approval, procurement approval, certification, recognition, provider preference, sponsor entitlement, Nexus-compatible status, Docket approval, Grid guarantee, or enterprise execution authority was created; or
e) affected materials are held, restricted, quarantined, withdrawn, corrected, archived, or subject to further review.
Public or controlled correction shall be accurate, proportionate, legally reviewed where required, privacy-aware, privilege-aware, cyber-aware, safeguards-aware, public-safe, non-retaliatory, and records-supported. Correction shall not disclose confidential employment, investigation, protected knowledge, privileged, personal, public authority, cyber-sensitive, infrastructure-sensitive, or legally restricted information unless lawful and approved.
162.18 Legal, Regulatory, Public Authority, Funder, or Law Enforcement Referral Where Required or Appropriate. The Corporation may refer an officer-related matter to counsel, auditors, insurers, regulators, public authorities, funders, grantors, donors, sponsors, providers, law enforcement, professional bodies, cybersecurity responders, data protection authorities, tax authorities, sanctions authorities, export-control authorities, employment authorities, civil-rights bodies, procurement authorities, or other competent bodies where required by law, contract, grant, public authority interface, insurance policy, fiduciary duty, tax duty, data breach law, cyber incident requirement, safeguarding obligation, or institutional judgment.
Referral may be appropriate where the matter involves fraud, theft, corruption, bribery, embezzlement, false records, data breach, cyber incident, protected knowledge exposure, research misconduct, civil-rights violation, harassment, retaliation, sanctions violation, export-control violation, controlled-technology exposure, competition violation, public authority misrepresentation, procurement integrity issue, securities or finance-boundary issue, insurance issue, public finance issue, tax issue, private inurement, excess benefit, misuse of public funds, restricted fund misuse, grant violation, or material risk to the Corporation or affected persons.
Referral decisions shall preserve privilege where appropriate, protect confidential information, minimize unnecessary disclosure, respect protected knowledge, protect whistleblowers, protect affected persons, avoid retaliation, preserve evidence, comply with legal hold, and use public-safe communications. The Corporation may make a referral without completing internal review where delay could increase harm, violate law, impair evidence, breach notice duties, or compromise public safety.
162.19 Enforcement Records. The Corporation shall maintain Article V Enforcement Records sufficient to demonstrate lawful, proportionate, records-supported, non-retaliatory, mission-preserving enforcement of officer authority, delegation, conflicts, compensation, records, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, research integrity, evidence integrity, methods integrity, technical asset integrity, safeguards, public-safe publication, and correctionability.
Article V Enforcement Records shall include, as applicable:
a) intake records, complaint records, concern records, incident records, escalation records, preliminary assessment records, investigation records, interview records, document review records, access log records, repository log records, financial records, conflict records, recusal records, delegation records, authority matrix records, Board records, committee records, officer records, counsel records, compliance records, safeguards records, data / AI / cyber records, research integrity records, and public-safe publication records;
b) officer authority violation review records, delegation violation review records, conflict or recusal violation review records, compensation or private benefit review records, records violation review records, public authority boundary review records, finance-boundary review records, certification-boundary review records, procurement-neutrality review records, recognition-boundary review records, provider-neutrality review records, sponsor non-control review records, data / AI / cyber / privacy review records, research integrity review records, evidence review records, methods review records, technical asset review records, civil-rights review records, accessibility review records, Tribal and Indigenous protocol review records, protected knowledge review records, and public-safe publication review records;
c) corrective action records, warning records, training records, certification records, supervision records, access restriction records, delegation suspension records, authority matrix revision records, recusal records, reassignment records, compensation adjustment records, repayment records, contract remedy records, suspension records, removal records, referral records, public correction records, controlled correction records, withdrawal records, retraction records, takedown records, supersession records, archive records, and closeout records;
d) notices to the Chair, Board, committees, officers, counsel, compliance, auditors, insurers, public authorities, funders, donors, sponsors, providers, affected persons, communities, Tribal or Indigenous interfaces, regulators, or law enforcement where lawful and appropriate;
e) records of exceptions requested, exceptions refused, exceptions approved where lawful, unresolved risks, residual risks, open action items, responsible owners, deadlines, closeout confirmations, and correction history; and
f) responsible custodian, repository location, access class, publication class, confidentiality class, privilege status, retention class, legal hold status, sealing status, deletion status, archive status, review date, and metadata.
The governing rule of this Section is that officer enforcement is part of governance, not personnel administration alone. The Corporation shall enforce Article V so that officer authority remains delegated, bounded, recorded, reviewable, non-executing, public-safe, safeguards-respecting, and correctionable. No officer shall be permitted to convert office, title, technical access, public authority relationship, sponsor relationship, provider relationship, operational urgency, or institutional reputation into unrecorded power. Enforcement shall protect the Corporation’s public-benefit mission, United States legal integrity, Nexus role separation, public-good assets, evidence and methods discipline, data / AI / cyber controls, community safeguards, public authority boundaries, finance and certification boundaries, and institutional trust.
Last updated
Was this helpful?