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.