ARTICLE VI. COMMITTEES
Section 163. Committee and Advisory Architecture
163.1 Committee and Advisory Architecture Purpose. The Corporation may establish a disciplined committee, council, advisory, working-group, expert-panel, peer-review, model-review, public-authority-forum, safeguards-forum, technical-panel, leadership-council, Helix-council, competence-cell, controlled-room review, and program-steering architecture to support the Board, officers, and public-benefit mission of the Corporation. The purpose of this architecture is to provide specialized expertise, fiduciary support, evidence review, methods stewardship, public-good software oversight, public authority learning support, safeguards review, technical review, public-safe publication review, data / AI / cyber review, finance-boundary discipline, and Nexus interface coordination without impairing Board authority or creating substitute governance.
The committee and advisory architecture shall be interpreted as a supporting architecture. It shall not create public authority status, emergency command authority, public warning authority, finance-readiness authority, certification authority, procurement authority, recognition authority, rating authority, provider-preference authority, sponsor-control rights, or enterprise execution authority.
163.2 Board Committees. The Board may create Board committees to assist in the discharge of Board oversight, reserved matters preparation, fiduciary review, risk review, policy review, officer oversight, financial oversight, audit readiness, governance renewal, public-benefit protection, and other lawful Board functions. A Board committee shall be created only by Board resolution, this Bylaw, or another competent Board record.
A Board committee may exercise only the authority expressly delegated to it by law, the Articles or Certificate, this Bylaw, Board resolution, or written charter. Unless expressly authorized, a Board committee shall recommend, review, prepare, monitor, and report; it shall not finally approve Board reserved matters.
163.3 Standing Committees. The Board may establish standing committees for continuing governance functions, including governance, nominating, ethics, finance, audit, risk, internal controls, evidence, methods, observability, ontology, technical truth, research integrity, data governance, AI governance, cybersecurity, public-good software, public authority learning, safeguards, legal compliance, development, programs, federation, interoperability, and continuity.
Standing committees shall have continuing charters, defined membership, reporting duties, records duties, review cycles, and sunset or renewal discipline. The existence of a standing committee shall not reduce the Board’s ultimate responsibility for oversight.
163.4 Special Committees. The Board may establish special committees for time-limited, transaction-specific, incident-specific, investigation-specific, project-specific, jurisdiction-specific, state-specific, territorial-specific, Tribal-interface-specific, North America-interface-specific, public authority-interface-specific, or technical matter-specific purposes.
A special committee shall have a defined mandate, scope, duration, records custodian, authority limit, and reporting path. A special committee shall dissolve, sunset, or be renewed by recorded action when its purpose has been completed, superseded, withdrawn, or made part of a standing structure.
163.5 Executive Committee Where Created. The Board may create an Executive Committee only where permitted by applicable law, the Articles or Certificate, and this Bylaw. The Executive Committee, where created, may act between Board meetings within expressly delegated authority and subject to ratification, reporting, and limitations established by the Board.
The Executive Committee shall not be used to bypass full Board deliberation for constitutional, structural, mission-lock, tax-status, public-benefit, non-execution, role-separation, public authority, finance, certification, procurement, recognition, safeguards, data / AI / cyber, dissolution, merger, or major asset matters except to the limited extent expressly lawful and recorded.
163.6 Leadership Councils. The Corporation may establish Leadership Councils to provide strategic feedback, ecosystem coordination, public-good perspective, technical and institutional insight, regional awareness, state and territorial awareness, North America interface awareness, and Nexus interface feedback. A Leadership Council shall be advisory unless a lawful delegation expressly provides otherwise.
No Leadership Council participant shall acquire fiduciary authority, officer authority, Board authority, public authority status, recognition authority, finance-readiness authority, certification authority, procurement authority, or authority to bind the Corporation by reason of Council participation.
163.7 Helix Councils. The Corporation may establish Helix Councils as cross-sector advisory structures representing or organizing perspectives from public authorities, universities, laboratories, industry, operators, providers, communities, Tribal and Indigenous interfaces, civil society, media, public-interest groups, capital-reader literacy participants, open-source communities, workforce participants, and other relevant sectors.
Helix Councils shall be designed to promote structured learning, translation, feedback, and public-benefit alignment while preserving competition-law discipline, public authority boundary discipline, finance-boundary discipline, provider neutrality, sponsor non-control, safeguards, and non-execution.
163.8 Advisory Councils. The Corporation may create advisory councils to provide expertise, stakeholder feedback, field intelligence, technical review, public-safe communication review, public authority learning insight, community safeguards insight, or program design feedback. Advisory councils shall not govern the Corporation unless their members are separately appointed as directors or officers under lawful instruments.
163.9 Public Authority Forums. The Corporation may establish Public Authority Forums to support public authority learning, evidence literacy, technical literacy, public-safe reporting literacy, scenario learning, simulation learning, tabletop review, after-action learning, capacity classification, and public authority interface discipline.
Public Authority Forums shall not create public authority delegation, public warning authority, emergency command authority, procurement approval, funding approval, regulatory approval, public finance approval, sovereign obligation, public-private partnership, or official adoption by participation.
163.10 Scientific and Technical Advisory Bodies. The Corporation may establish scientific and technical advisory bodies to advise on evidence, methods, research design, validation, observability, ontology, technical truth, 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 chain, advanced manufacturing, semiconductors, and other exponential technologies.
Scientific and technical advisory advice shall not constitute certification, accreditation, procurement approval, legal compliance approval, finance-readiness, recognition, rating, public authority decision, public warning, emergency command, or operational authorization.
163.11 Working Groups. The Corporation may establish working groups to prepare drafts, methods, recommendations, implementation notes, controlled vocabularies, technical profiles, research summaries, public-safe materials, software proposals, evidence review notes, operating procedures, or program recommendations. Working groups shall operate under a charter, workplan, or recorded mandate.
163.12 Drafting Groups. Drafting groups may be created to prepare bylaws, policies, protocols, schedules, forms, controlled vocabularies, technical profiles, public-safe notices, program charters, committee charters, interface agreements, or other instruments. Drafting groups shall not adopt the instruments they prepare unless separately empowered by competent authority.
163.13 Expert Panels. Expert panels may be established to review defined technical, legal, research, public authority, safeguards, community, cyber, AI, data, finance-boundary, certification-boundary, or public-safe publication questions. Expert panel outputs shall identify scope, assumptions, evidence reviewed, dissenting views where material, limitations, and any matters requiring Board, officer, counsel, safeguards, data / AI / cyber, or public authority review.
163.14 Peer Review Panels. Peer review panels may be used to review research integrity, evidence quality, methods quality, publication readiness, reproducibility, replication, public-good software design, technical baselines, model outputs, evaluation harnesses, and public-safe claims. Peer review shall improve quality and accountability; it shall not create external certification or final authority unless a separate competent authority lawfully does so.
163.15 Model Review Panels. Model review panels may be used to review AI systems, model cards, system cards, benchmark cards, evaluation harnesses, dataset cards, inference workflows, compute workload records, agentic AI controls, retrieval workflows, embeddings, fine-tuning restrictions, public-safe output controls, and human-review rules. Model review panel outputs shall not be represented as public authority approval, regulatory approval, certification, finance-readiness, procurement approval, rating, or operational authorization.
163.16 Nexus Competence Cells. The Corporation may establish Nexus Competence Cells to support structured learning, method localization, technical literacy, public-good software literacy, public authority learning, safeguards literacy, state and territorial localization, Tribal and Indigenous protocol respect, and train-the-trainer capability. Competence Cells shall not be professional licensing bodies, certification bodies, recognition bodies, procurement bodies, finance-readiness bodies, or enterprise execution units by default.
163.17 Program Steering Groups. Program steering groups may support program planning, implementation monitoring, cross-functional coordination, public authority learning support, safeguards implementation, technical workstream alignment, and closeout review. Program steering groups shall not override Board approvals, budget limits, delegation limits, data / AI / cyber controls, safeguards, public authority boundaries, finance boundaries, certification boundaries, or non-execution.
163.18 Controlled-Room Review Groups. The Corporation may establish controlled-room review groups to manage access, review exhibits, supervise clean-room or evidence-room protocols, review confidential or sensitive materials, preserve chain of custody, and support public-safe outputs. Such groups shall operate under access classifications, confidentiality rules, no-download restrictions where applicable, logging requirements, and closeout procedures.
163.19 Distinction Between Governance Bodies, Advisory Bodies, Technical Bodies, Learning Bodies, and Participation Surfaces. The Corporation shall distinguish governance bodies, advisory bodies, technical bodies, learning bodies, and participation surfaces. Governance bodies may exercise authority only if lawfully created and delegated. Advisory bodies may advise. Technical bodies may prepare, test, review, and recommend. Learning bodies may educate and receive feedback. Participation surfaces may enable stakeholder involvement, public authority learning, community engagement, or technical collaboration.
No body shall be treated as a governance body merely because it is visible, technically important, externally respected, sponsor-supported, provider-supported, public authority-attended, or Nexus-referenced.
163.20 No Body Has Authority Except as Expressly Created, Chartered, Delegated, and Recorded. No committee, council, forum, panel, working group, drafting group, competence cell, program body, public authority forum, Helix Council, Leadership Council, or controlled-room group shall have authority unless expressly created, chartered, delegated, and recorded. Authority shall not arise by custom, practice, urgency, meeting attendance, system access, public prominence, technical authorship, sponsor relationship, provider relationship, public authority participation, AI workflow, dashboard access, proof receipt, ledger entry, or Nexus interface reference.
163.21 Committee and Advisory Architecture Records. The Corporation shall maintain Committee and Advisory Architecture Records, including charters, creation records, Board resolutions, officer delegations, membership lists, appointment records, scope statements, authority statements, access classifications, conflict records, confidentiality records, meeting records, recommendation records, reports, review cycles, sunset records, dissolution records, and correction records.
Section 164. Creation, Chartering, Amendment, Suspension, Sunset, and Dissolution of Committees and Advisory Bodies
164.1 Creation Authority. A committee, council, advisory body, working group, expert panel, Helix Council, Leadership Council, public authority forum, competence cell, program steering group, or controlled-room review group may be created only by the Board, by this Bylaw, or by an officer acting within a recorded delegation. Creation authority shall identify whether the body is a Board committee, officer-supported body, advisory body, technical body, learning body, working group, or participation surface.
164.2 Board-Created Committees. Board-created committees shall be created by resolution, written consent, or other lawful Board record. The record shall identify the committee’s name, purpose, authority, scope, membership, chair, reporting line, records custodian, access classification, review cycle, and limits.
A Board-created committee shall remain subject to the Board. Its existence shall not diminish Board reserved powers, Board fiduciary oversight, or member approval rights where applicable.
164.3 Officer-Created Working Groups Where Delegated. An officer may create a working group, drafting group, technical group, program group, or operational group only within delegated authority. Officer-created groups shall not be described as Board committees unless approved by the Board. Officer-created groups may prepare work product, coordinate tasks, collect feedback, conduct technical review, or support operations, but may not exercise Board powers, adopt policies, approve reserved matters, bind the Corporation beyond delegation, or create public authority, finance, certification, procurement, recognition, provider, sponsor, or execution authority.
164.4 Charter Requirement. Each material committee or advisory body shall have a written charter, terms of reference, mandate, work order, or creation record. The charter shall be adopted before the body exercises material authority or receives sensitive access, except in an emergency where temporary creation is necessary and promptly documented.
164.5 Charter Contents. A charter shall include, as applicable:
a) name, short name, body type, creation authority, effective date, version, status, and custodian;
b) purpose, scope, excluded scope, authority, delegation, decision status, recommendation status, and advisory status;
c) membership, eligibility, appointment method, removal method, chair or lead, quorum where applicable, voting where applicable, meeting cadence, and reporting line;
d) records, confidentiality, privilege, access class, data / AI / cyber class, public authority class, finance-boundary class, certification-boundary class, procurement-neutrality class, recognition-boundary class, safeguards class, and publication class;
e) conflict, recusal, competition, sanctions, export-control, controlled-technology, public authority, provider, sponsor, donor, funder, host, and enterprise actor controls; and
f) review cycle, sunset date, amendment path, suspension path, dissolution path, and correction path.
164.6 Purpose. The purpose of each body shall be stated with sufficient precision to prevent mission drift, authority inflation, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, recognition overclaim, provider preference, sponsor control, competition risk, data / AI / cyber risk, safeguards risk, or enterprise execution.
164.7 Authority. The authority of each body shall be express, limited, and recorded. If the body may decide, the charter shall state the decision scope. If the body may only recommend, review, advise, draft, educate, or coordinate, the charter shall say so. Silence shall be interpreted as advisory and non-binding.
164.8 Scope. The charter shall identify subject-matter scope, institutional scope, geographic scope, state or territorial scope where applicable, Tribal or Indigenous interface scope where applicable, North America interface scope where applicable, Nexus interface scope, data scope, technical asset scope, public authority interface scope, finance-boundary scope, safeguards scope, and excluded matters.
164.9 Membership. The charter shall state eligible and ineligible participants, appointment authority, term, capacity, independence requirements, conflict duties, confidentiality duties, access limits, public statement limits, and removal standards. Membership shall not be used to give governance control to sponsors, providers, donors, funders, hosts, public authorities, investors, insurers, lenders, national companies, Project SPVs, or enterprise actors.
164.10 Chair or Lead. Each body shall have a chair, co-chair, lead, or coordinator where appropriate. The chair or lead shall manage agenda discipline, meeting discipline, conflict disclosure, recusal handling, confidentiality, public authority boundary discipline, finance and certification boundary discipline, competition-law discipline, reporting, and records.
164.11 Reporting Line. Each body shall report to the Board, a Board committee, an officer, or another competent authority as stated in its charter. The reporting line shall not create authority beyond the charter. A body reporting to an officer shall not thereby become an officer or Board body.
164.12 Quorum Where Applicable. Where a body has decision authority, recommendation authority requiring formal approval, or material review authority, the charter shall specify quorum. Advisory bodies may use consensus, chair-approved recommendations, written reports, or other procedures if recorded. Quorum rules shall account for recusals and access restrictions.
164.13 Decision, Recommendation, or Advisory Status. Each charter shall identify whether outputs are decisions, recommendations, advisory views, technical comments, peer-review notes, minority views, drafts, learning materials, or participation records. No output shall be inflated beyond its recorded status.
164.14 Records Custodian. Each body shall have a records custodian. The custodian may be the Secretary, Secretariat, committee secretary, officer, or designated records lead. The custodian shall ensure minutes, recommendations, decisions, materials, conflicts, recusals, attendance, access records, and reports are captured in the approved repository or controlled repository.
164.15 Confidentiality Class. Each charter shall identify confidentiality classification, including public, internal, controlled, confidential, privileged, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, public authority restricted, personal information, health-sensitive, community-protected, Tribal / Indigenous, local / territorial knowledge, or protected knowledge status where applicable.
164.16 Data / AI / Cyber / Privacy Class. Each charter shall identify whether the body may access or process datasets, models, prompts, embeddings, inference records, compute workload records, public authority data, personal information, cyber-sensitive materials, infrastructure-sensitive materials, source code, keys, credentials, secrets, repositories, dashboards, or controlled-room materials. Access shall be limited by need, authorization, logging, and security controls.
164.17 Public Authority Boundary Class. Each charter shall identify whether public authorities may participate, whether participation is official, observer, regulator-listening, public finance reader, emergency-management participant, public infrastructure operator, simulation participant, or another approved capacity, and what limitation language is required.
164.18 Finance, Certification, Procurement, Recognition, and Public Warning Boundary Class. Each charter shall classify exposure to finance, insurance, lending, securities, public finance, procurement, certification, accreditation, recognition, maturity, standing, Docket, Grid, public warning, emergency command, provider preference, and sponsor-control risks. Where such exposure exists, controlled vocabulary, limitation language, counsel review, compliance review, GRA interface review, GRF interface review, or Board review may be required.
164.19 Safeguards and Protected Knowledge Class. Each charter shall classify safeguards exposure, including civil rights, accessibility, community safeguards, Tribal or Indigenous protocol, Indigenous data safeguards, protected knowledge, local or territorial knowledge, public-safe mapping, youth or vulnerable populations, health-sensitive information, grievance, remedy, non-retaliation, and do-no-harm considerations.
164.20 Conflict Controls. Each charter shall require conflict disclosure, recusal, access restriction, related-party review, sponsor and provider capture review, public authority conflict review, research conflict review, data / AI / cyber conflict review, and competition-law discipline where applicable.
164.21 Sunset Date or Review Cycle. Each material body shall have a sunset date, renewal date, or periodic review cycle. No body shall continue indefinitely by inertia where its purpose has ended, its scope has drifted, its membership creates capture risk, or its authority has become unclear.
164.22 Charter Amendment. A charter may be amended only by the authority that created it or by another authority expressly empowered to amend it. Material charter amendments shall be recorded, versioned, deposited, and communicated to affected participants.
164.23 Suspension. A body may be suspended where it exceeds authority, lacks records, mishandles conflicts, breaches confidentiality, creates public authority confusion, creates finance or certification overclaim, creates competition risk, mishandles data or AI, exposes protected knowledge, becomes captured, or otherwise threatens the Corporation’s public-benefit purpose or legal boundaries.
164.24 Dissolution. A body may be dissolved when its mandate is complete, its purpose is obsolete, its risks exceed its utility, its work is transferred, its authority is revoked, its charter expires, or the Board determines dissolution is in the best interests of the Corporation.
164.25 Chartering, Amendment, Suspension, Sunset, and Dissolution Records. The Corporation shall maintain records of creation, chartering, amendment, suspension, sunset, renewal, dissolution, membership, authority, materials, outputs, conflicts, recusals, access, reports, and closeout for each committee and advisory body.
Section 165. Committee Authority Limits and Non-Substitution Rule
165.1 Committee Authority Limit Purpose. Committee authority limits preserve Board supremacy, nonprofit law compliance, public-benefit purpose, mission lock, non-execution, role separation, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, and correctionability.
165.2 Committees Act Only Within Charter. Each committee, council, forum, panel, working group, drafting group, competence cell, or program body shall act only within its charter, mandate, delegation, work order, or creation record. Action outside scope shall be unauthorized unless ratified where lawful by competent authority.
165.3 Committees Subject to Board Authority. All committees and advisory bodies are subject to Board authority. The Board may review, amend, suspend, override, reject, ratify, withdraw, dissolve, or correct any committee act or output to the fullest extent permitted by law.
165.4 Committees Subject to Bylaw, Policies, Delegations, Budget, and Records Requirements. Committees and advisory bodies shall comply with this Bylaw, Board resolutions, policies, delegation matrices, budgets, public-safe language, controlled vocabulary, records requirements, conflict rules, confidentiality rules, competition rules, data / AI / cyber controls, safeguards rules, and lawful limitations.
165.5 Advisory Bodies Advise Only Unless Expressly Delegated. Advisory bodies advise only unless expressly delegated authority by competent record. Advisory participation, technical expertise, public authority status, sponsor support, provider support, or stakeholder prominence shall not create governance authority.
165.6 Working Groups Develop Work Product Only Unless Expressly Delegated. Working groups may draft, test, review, coordinate, analyze, and recommend. They shall not adopt policies, certify outputs, approve public statements, approve procurement, determine finance-readiness, recognize actors, bind the Corporation, or exercise Board powers unless expressly delegated within lawful limits.
165.7 Expert Panels Review or Recommend Only Unless Expressly Delegated. Expert panels may review evidence, models, methods, public-safe publication, technical assets, safeguards, or boundary questions and may recommend action. Panel review shall not constitute approval, certification, rating, recognition, finance-readiness, procurement approval, public authority decision, or emergency command.
165.8 No Committee May Override Board Reserved Matters. No committee or advisory body may override Board reserved matters. Matters reserved to the Board remain reserved unless applicable law, the Articles or Certificate, this Bylaw, and a lawful Board delegation expressly permit committee action.
165.9 No Committee May Amend the Bylaw. No committee, council, advisory body, forum, working group, or panel may amend, repeal, replace, restate, suspend, waive, or reinterpret this Bylaw except through lawful recommendation to the Board or another competent authority.
165.10 No Committee May Alter Mission Lock. No body may alter the Corporation’s public-benefit purpose, nonprofit character, tax-exempt or tax-exempt-compatible posture, public-good technical institution character, all-states-and-territories posture, North America anchor role, or Nexus role separation.
165.11 No Committee May Alter Non-Execution Boundary. No body may convert the Corporation into an execution vehicle, provider, operator, asset owner, national company, Project SPV, fund, broker, lender, insurer, rating agency, public authority, regulator, certification body, procurement body, public warning body, or emergency command body.
165.12 No Committee May Create Public Authority Status. No body may create public authority status, official endorsement, public authority adoption, public warning, emergency command, regulatory approval, public finance approval, sovereign obligation, funding approval, procurement approval, public-private partnership, or governmental decision.
165.13 No Committee May Create Finance-Readiness, Insurance-Readiness, Investment Suitability, Bankability, Rating, Capital-Readability, or Public Finance Approval. No body may create or imply finance-readiness, insurance-readiness, investment suitability, bankability, capital-readability, securities suitability, underwriting approval, lending approval, rating, credit opinion, resilience rating, public finance approval, tax credit approval, or capital execution.
165.14 No Committee May Create Certification, Accreditation, Procurement Approval, Recognition, Standing, Maturity, Docket Approval, Grid Guarantee, or Nexus-Compatible Status Unless Separately Authorized by Competent Body and Record. No body may create certification, accreditation, compliance approval, procurement approval, recognition, standing, maturity, Docket approval, Grid guarantee, or Nexus-compatible status unless a competent body lawfully empowered to create that status does so by recorded act. Technical review, peer review, model review, evidence review, public-good software review, or advisory recommendation shall not be inflated into such status.
165.15 No Committee May Select Providers for Public Authorities. No committee or advisory body shall select, rank, recommend, approve, or prefer providers for public authorities unless separately and lawfully authorized under applicable procurement law and consistent with this Bylaw. The Corporation’s default posture is provider neutrality.
165.16 No Committee May Control Enterprise Execution. No committee or advisory body may control enterprise execution, manage Project SPVs, direct national companies, operate infrastructure, deploy assets, manage providers, issue operational instructions, or assume commercial delivery responsibilities.
165.17 No Committee May Substitute for GRF, GRA, Nexus Standards, Public Authorities, National Companies, Project SPVs, Providers, Lenders, Insurers, Funds, or Regulated Actors. No committee shall substitute for GRF recognition functions, GRA finance-readiness functions, Nexus Standards protocol authority, public authority decisions, enterprise-stack execution, provider delivery, lender approval, insurer approval, underwriting, rating, capital execution, or regulated professional judgment.
165.18 Committee Non-Substitution Records. Each body shall maintain records sufficient to show that it acted within scope and did not substitute for the Board, GRF, GRA, Nexus Standards, public authorities, regulated actors, providers, sponsors, national companies, Project SPVs, or enterprise execution actors.
Section 166. Committee Membership, Eligibility, Appointment, Removal, Good Standing, and Independence
166.1 Committee Membership Purpose. Committee membership rules ensure that persons serving on committees, councils, advisory bodies, working groups, expert panels, public authority forums, Helix Councils, Leadership Councils, competence cells, and controlled-room review groups are eligible, fit, independent where required, conflict-disclosed, access-appropriate, trained where needed, and subject to records discipline.
166.2 Directors as Committee Members. Directors may serve on Board committees and advisory bodies where appointed or authorized. A director serving on a committee remains subject to fiduciary duties, conflict duties, confidentiality duties, Board duties, and this Bylaw.
166.3 Officers as Committee Members. Officers may serve as committee members, ex officio participants, liaisons, presenters, or support persons where authorized. Officer participation shall not convert a committee into management authority or expand officer powers beyond appointment and delegation.
166.4 Staff and Contractor Participation. Staff and contractors may participate where their role, contract, confidentiality obligations, access rights, and conflict disclosures support the committee’s purpose. Staff and contractor participation shall not create director, officer, fiduciary, public authority, or governance status.
166.5 Fellows and Advisors. Fellows and advisors may participate subject to written terms, confidentiality, IP, conflict, data / AI / cyber, public-safe claims, safeguards, and non-authority rules. Fellowship or advisory title shall not create authority to bind the Corporation.
166.6 External Experts. External experts may be appointed to committees, panels, forums, or councils where their expertise supports the Corporation’s public-benefit purposes. External experts shall be screened for conflicts, confidentiality capacity, sanctions, export-control, controlled technology, public authority boundary, competition, data / AI / cyber, and safeguards risks as appropriate.
166.7 Public Authority Participants. Public authority participants may participate only in classified capacities, including official capacity, observer, regulator-listening, public finance reader, emergency-management participant, public infrastructure operator, simulation participant, or other approved status. Participation shall not create public authority delegation, official adoption, procurement approval, funding approval, public warning, emergency command, or sovereign obligation.
166.8 University and Laboratory Participants. Universities, laboratories, researchers, and academic participants may participate subject to research integrity, publication, IP, data, confidentiality, conflict, human-subjects, community review, protected knowledge, and sponsor disclosure rules. Academic participation shall not create certification, recognition, finance-readiness, procurement approval, or public authority approval.
166.9 Community, Tribal, Indigenous, Civil Society, and Public-Interest Participants. Community, Tribal, Indigenous, civil society, and public-interest participants may participate to support public-safe design, safeguards, protected knowledge protection, local and territorial knowledge respect, civil-rights review, accessibility, and do-no-harm review. Participation shall not be treated as consent, endorsement, waiver, approval, or transfer of rights unless expressly and lawfully recorded.
166.10 Provider, Sponsor, Donor, Funder, Host, and Enterprise Participants Subject to Enhanced Controls. Providers, sponsors, donors, funders, hosts, vendors, investors, insurers, lenders, underwriters, national companies, Project SPVs, and enterprise actors may participate only under enhanced controls. Such participation shall not create provider preference, sponsor control, donor control, funder control, host control, procurement advantage, certification advantage, recognition advantage, finance-readiness advantage, public authority access purchase, or research outcome purchase.
166.11 Eligibility Criteria. Eligibility may include role relevance, expertise, independence, good standing, integrity, conflict disclosure, confidentiality capacity, data / AI / cyber capacity, safeguards capacity, competition-law compliance capacity, and willingness to comply with this Bylaw and applicable charters.
166.12 Appointment Authority. Appointment authority shall be stated in the charter. Committee members may be appointed by the Board, committee chair, officer, Secretariat, or other competent authority only within recorded limits. No person shall self-appoint or acquire membership by attendance, contribution, title, sponsorship, provider status, donation, public authority status, or technical access.
166.13 Term of Service. Committee members may serve fixed, renewable, project-based, event-based, review-based, or indefinite terms as stated in the charter. Terms shall be reviewable and may end by expiration, resignation, removal, loss of eligibility, access revocation, completion of mandate, or dissolution.
166.14 Good Standing Requirement. Committee members shall remain in good standing, including compliance with law, this Bylaw, charter, confidentiality rules, conflict rules, access rules, competition rules, data / AI / cyber rules, safeguards rules, public-safe claims discipline, and non-retaliation.
166.15 Conflict Disclosure. Committee members shall disclose conflicts before appointment and update disclosures when circumstances change. Conflicts include financial, institutional, research, technical, public authority, sponsor, provider, donor, funder, host, employment, IP, data, AI, cyber, procurement, finance, and personal conflicts.
166.16 Independence Review. Independence review shall be conducted where the body’s work affects Board recommendations, finance boundaries, certification boundaries, procurement neutrality, recognition inputs, public authority interfaces, research outputs, public-safe publications, public-good software, technical baselines, or safeguards.
166.17 Sanctions, Export-Control, Controlled Technology, Data / AI / Cyber, Public Authority, Finance-Boundary, and Safeguards Screening Where Applicable. Participants may be screened for sanctions, export-control, controlled technology, national security sensitivity, data access, AI use, cyber risk, public authority capacity, finance-boundary exposure, competition risk, protected knowledge exposure, civil-rights risk, and safeguards capacity before receiving access.
166.18 Removal. A committee member may be removed by the appointing authority, Board, committee chair where authorized, officer where delegated, or other competent authority for loss of eligibility, breach of duty, conflict, confidentiality breach, competition violation, data misuse, AI misuse, cyber misconduct, public authority overclaim, finance overclaim, certification overclaim, procurement overclaim, provider-preference claim, sponsor-control concern, safeguards breach, retaliation, harassment, non-participation, or mission-inconsistent conduct.
166.19 Resignation. A committee member may resign by written notice or other recorded method. Resignation shall not waive confidentiality, records, cooperation, return, deletion, access revocation, correction, or non-retaliation obligations.
166.20 Suspension. A participant may be suspended pending review where continued participation may create risk. Suspension may include access restriction, meeting exclusion, material restriction, repository suspension, controlled-room suspension, publication restriction, or public statement restriction.
166.21 Offboarding and Access Revocation. Upon resignation, removal, suspension, term expiration, or committee dissolution, access shall be reviewed and revoked or reduced as appropriate. Materials shall be returned, deleted, sealed, transferred, or preserved according to policy and legal hold.
166.22 Committee Membership Records. The Corporation shall maintain committee membership records, including appointment, eligibility, capacity, term, conflicts, recusals, confidentiality acknowledgments, screening, access rights, training, resignation, removal, suspension, offboarding, and access revocation records.
Section 167. Committee Chairs, Leads, Secretaries, Rapporteurs, and Custodians
167.1 Committee Chair Role. A committee chair shall lead the committee within its charter, manage agendas, facilitate deliberation, preserve meeting discipline, ensure conflicts are disclosed, ensure recusals are honored, support public-safe language, maintain boundary discipline, and report to the Board, officer, or other competent authority.
167.2 Working Group Lead Role. A working group lead shall coordinate work product, deadlines, participants, drafts, reviews, technical inputs, evidence inputs, and records. The lead shall not adopt outputs, bind the Corporation, approve public statements, or expand scope unless expressly delegated.
167.3 Panel Chair Role. A panel chair shall manage review criteria, reviewer independence, minority views, confidentiality, materials handling, and final report preparation. The panel chair shall ensure that review outputs are framed as review findings, recommendations, or advisory outputs, not certification or approval unless expressly authorized by competent authority.
167.4 Secretariat Support. The Secretariat may support agendas, notices, minutes, action items, repository deposits, attendance, access records, conflict records, and closeout. Secretariat support shall not create substantive authority unless separately delegated.
167.5 Rapporteur Role. A rapporteur may prepare neutral summaries, technical notes, meeting notes, minority-view summaries, and recommendation drafts. A rapporteur shall not alter substantive meaning, suppress dissent, rewrite recommendations to imply authority, or create unapproved public claims.
167.6 Records Custodian Role. The records custodian shall preserve committee records, including charters, attendance, materials, minutes, recommendations, decisions where delegated, conflicts, recusals, confidentiality acknowledgments, access logs, reports, and closeout records. The custodian shall ensure versioning, repository discipline, retention, sealing, archival, and correction.
167.7 Meeting Discipline. Chairs and leads shall maintain meeting discipline by keeping discussions within scope, preventing prohibited topics, pausing for conflicts, stopping boundary-violating discussions, protecting confidentiality, and escalating issues.
167.8 Agenda Discipline. Agendas shall identify purpose, topics, materials, decision or recommendation status, conflicts, public authority capacity, finance-boundary relevance, certification-boundary relevance, data / AI / cyber relevance, safeguards relevance, and required limitations where material.
167.9 Conflict and Recusal Management. Chairs and leads shall request conflict updates, identify recusals, restrict access where needed, record recusals, and prevent recused participants from deliberating, recommending, approving, influencing, or accessing restricted materials.
167.10 Public Authority Boundary Management. Chairs and leads shall ensure that public authority participation is capacity-classified, properly recorded, and accompanied by limitation language where needed. They shall prevent statements implying public authority adoption, endorsement, emergency command, public warning, funding approval, procurement approval, regulatory approval, sovereign obligation, or public-private partnership.
167.11 Finance and Certification Boundary Management. Chairs and leads shall prevent finance-readiness overclaims, investment advice, insurance approval, lending approval, underwriting approval, rating claims, public finance approval, certification claims, procurement approval, recognition claims, provider preference, sponsor entitlement, and similar boundary violations.
167.12 Competition and Antitrust Meeting Discipline. Chairs and leads shall prevent discussion of prices, margins, costs, bids, wages, customers, suppliers, market allocation, capacity, exclusion, boycotts, procurement steering, competitively sensitive strategy, or collusive conduct. They may stop a meeting, remove materials, consult counsel, or escalate concerns.
167.13 Confidentiality and Controlled-Material Handling. Chairs, leads, secretaries, rapporteurs, and custodians shall protect confidential, privileged, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, personal, health-sensitive, public authority, community-protected, Tribal / Indigenous, local / territorial, and protected knowledge materials.
167.14 Action-Item Tracking. Action items shall identify responsible owners, deadlines, dependencies, required approvals, boundary conditions, records needed, and closeout status. Action items shall not authorize substantive acts beyond delegated authority.
167.15 Reporting to Board or Delegated Officer. Chairs and leads shall report material recommendations, risks, conflicts, minority views, boundary issues, public authority issues, finance or certification concerns, data / AI / cyber issues, safeguards concerns, and correction needs to the Board or delegated officer.
167.16 No Chair, Lead, Secretary, Rapporteur, or Custodian Authority Beyond Charter and Delegation. No chair, lead, secretary, rapporteur, or custodian shall have authority beyond charter and delegation by reason of title, meeting control, records access, drafting role, technical centrality, public authority relationship, sponsor relationship, provider relationship, or public visibility.
167.17 Chair, Lead, Secretary, Rapporteur, and Custodian Records. The Corporation shall maintain appointment, authority, conflict, confidentiality, access, meeting, report, action-item, and closeout records for chairs, leads, secretaries, rapporteurs, and custodians.
Section 168. Executive Committee
168.1 Executive Committee Creation. The Board may create an Executive Committee only by Board resolution or this Bylaw, and only to the extent permitted by applicable law and the Articles or Certificate. The Executive Committee shall be a Board committee composed as required by law, the Articles or Certificate, this Bylaw, and Board resolution.
168.2 Executive Committee Purpose. The Executive Committee may support Board continuity, urgent Board-level review, interim governance, agenda preparation, officer interface, emergency oversight, and action between Board meetings. Its purpose is to preserve Board effectiveness, not to replace the Board.
168.3 Authority Between Board Meetings. The Executive Committee may act between Board meetings only within delegated authority. Actions taken between meetings shall be reported to the Board and ratified where required. The Board may modify, supersede, reject, or correct Executive Committee action to the fullest extent lawful.
168.4 Scope of Delegated Authority. The Board shall define the Executive Committee’s scope, including whether it may approve routine matters, emergency measures, interim actions, agenda matters, officer recommendations, or time-sensitive items. Ambiguity shall be interpreted narrowly.
168.5 Emergency Support Function. The Executive Committee may support emergency governance, break-glass review, incident containment, public-safe holds, access restrictions, legal holds, repository lockdowns, controlled-room lockdowns, public authority clarification, data / AI / cyber containment, safeguards stop-the-line review, and ratification pathways where lawful.
168.6 Membership. Membership shall be determined by the Board and may include the Chair, Vice-Chair, committee chairs, independent directors, and other directors as lawful and appropriate. Officer attendance may be permitted, but officer attendance shall not convert officers into Executive Committee members unless lawfully appointed.
168.7 Quorum. The Executive Committee charter shall define quorum. Quorum shall account for recusals and shall be heightened where appropriate for emergency, financial, legal, public authority, data / AI / cyber, safeguards, or boundary-sensitive matters.
168.8 Voting. Voting shall follow the charter, Board resolution, this Bylaw, and applicable law. Conflicted members shall recuse and shall not influence votes. Written consent or electronic approval may be used only where lawful and properly recorded.
168.9 Reporting to Board. The Executive Committee shall report all actions, recommendations, emergency measures, conflicts, recusals, risks, and unresolved matters to the Board at the next Board meeting or sooner where material.
168.10 Ratification Where Required. Executive Committee actions requiring full Board ratification shall be presented promptly. Ratification shall identify the action, authority, facts, risks, conflicts, records, limitations, sunset, and correction needs.
168.11 Limits on Executive Committee Authority. The Executive Committee shall not approve matters prohibited by law, the Articles or Certificate, this Bylaw, Board resolution, member approval requirements where applicable, or its charter.
168.12 No Amendment of Bylaw Unless Expressly Permitted by Law, Articles, Bylaw, and Board Delegation. The Executive Committee shall not amend, restate, repeal, suspend, replace, or waive this Bylaw unless expressly permitted by applicable law, the Articles or Certificate, this Bylaw, and a specific Board delegation. Silence shall mean no authority.
168.13 No Approval of Reserved Matters Unless Expressly Authorized and Lawful. The Executive Committee shall not approve Board reserved matters unless expressly and lawfully authorized. Even where authorized, the Executive Committee shall preserve Board notice, reporting, ratification, records, conflicts, and safeguards.
168.14 No Emergency Exercise of Prohibited Functions. No emergency permits the Executive Committee to exercise prohibited functions. The Executive Committee may hold, stop, quarantine, preserve, clarify, correct, and maintain continuity; it may not create public authority power, finance-readiness, certification, procurement approval, recognition, provider preference, sponsor control, public warning, emergency command, or enterprise execution.
168.15 Executive Committee Minutes and Records. Executive Committee minutes shall record attendance, quorum, notice, materials, conflicts, recusals, deliberation summary, decisions, votes, emergency grounds, limitations, action items, ratification needs, sunset dates, and correction paths.
168.16 Executive Committee Review, Sunset, or Dissolution. The Board shall periodically review the Executive Committee’s necessity, performance, scope, conflicts, records, and authority. The Board may sunset, redesign, suspend, or dissolve the Executive Committee at any time within lawful authority.
Section 169. Governance, Nominating, Ethics, and Board Renewal Committee
169.1 Committee Purpose. The Governance, Nominating, Ethics, and Board Renewal Committee may support Board composition, director recruitment, director qualification review, independence review, ethics oversight, Board evaluation, committee evaluation, succession planning, bylaw review, governance policy review, anti-capture review, and fiduciary development.
169.2 Board Composition Review. The Committee may assess Board size, structure, skills, independence, public-benefit competence, United States nonprofit governance competence, all-states-and-territories awareness, North America interface awareness, evidence and methods competence, data / AI / cyber competence, public authority literacy, safeguards competence, finance-boundary competence, and Nexus role-separation competence.
169.3 Director Recruitment. The Committee may identify and cultivate director candidates who strengthen the Corporation’s mission lock, public-benefit purpose, legal compliance, evidence integrity, technical competence, public authority learning, safeguards, anti-capture posture, geographic awareness, and institutional resilience.
169.4 Director Eligibility and Independence Review. The Committee may review legal eligibility, consent, fit-and-proper status, integrity, time capacity, confidentiality capacity, conflict disclosures, independence, sanctions, export-control, controlled technology, public authority, finance-boundary, certification-boundary, sponsor, provider, donor, funder, host, national company, Project SPV, and enterprise actor risks.
169.5 Director Nominations. The Committee may recommend director nominations to the Board or members where applicable. Recommendations shall include candidate qualifications, conflicts, independence assessment, skills contribution, safeguards awareness, data / AI / cyber awareness, boundary understanding, and any restrictions.
169.6 Board Succession Planning. The Committee may support Board succession planning, including chair succession, committee chair succession, emergency continuity, director pipeline development, continuity packs, and knowledge transfer.
169.7 Officer Succession Interface. The Committee may coordinate with the Board and relevant officers on officer succession, emergency acting officer arrangements, continuity planning, and separation between Board and management roles.
169.8 Governance Policy Review. The Committee may review governance policies, conflict policies, ethics policies, Board procedures, committee charters, delegation principles, public-safe claim controls, and controlled vocabulary governance.
169.9 Bylaw Review Support. The Committee may periodically review this Bylaw and recommend amendments, restatements, clarifications, corrections, or supersession to the Board. It shall not amend the Bylaw directly unless expressly authorized by law and this Bylaw.
169.10 Fiduciary Training Support. The Committee may support director training on fiduciary duties, nonprofit law, tax-exempt or tax-exempt-compatible duties, public-benefit purpose, non-execution, role separation, public authority boundaries, finance boundaries, data / AI / cyber controls, safeguards, competition, sanctions, export-control, and correctionability.
169.11 Board Evaluation. The Committee may support annual Board self-assessment, director performance review, attendance review, skills matrix review, independence review, conflict review, committee performance review, and renewal recommendations.
169.12 Committee Evaluation. The Committee may review committee performance, charters, membership, authority, records, conflicts, independence, capture risk, and sunset status.
169.13 Ethics Oversight Interface. The Committee may coordinate with ethics, safeguards, legal, compliance, and risk functions on governance ethics, conflicts, related-party transactions, public claims, non-retaliation, and accountability.
169.14 Conflict Policy Oversight Interface. The Committee may review conflict policy effectiveness, disclosure cycles, recusal records, dual-role controls, related-party controls, sponsor and provider capture controls, and remediation.
169.15 Diversity, Accessibility, Geographic, State, Territorial, Tribal, and Public-Interest Perspective Review. The Committee may review whether Board and committee composition reflects appropriate diversity of expertise, geography, state and territorial awareness, Tribal and Indigenous respect, accessibility competence, community safeguards perspective, and public-interest legitimacy.
169.16 Anti-Capture Governance Review. The Committee shall support anti-capture review of governance structures, including risks from sponsors, providers, donors, funders, hosts, public authorities, investors, insurers, lenders, national companies, Project SPVs, and enterprise actors.
169.17 Governance, Nominating, Ethics, and Board Renewal Records. The Committee shall maintain records of nominations, evaluations, independence reviews, conflicts, succession plans, training, governance policy reviews, ethics reviews, anti-capture reviews, recommendations, and Board actions.
Section 170. Finance, Audit, Risk, and Internal Controls Committee
170.1 Committee Purpose. The Finance, Audit, Risk, and Internal Controls Committee may support financial oversight, budget review, accounting integrity, audit readiness, restricted fund oversight, grant and support oversight, internal controls, fraud prevention, procurement process discipline, signing authority, insurance, risk registers, issue registers, control registers, and financial anti-capture review.
170.2 Budget Review. The Committee may review proposed annual budgets, material budget amendments, program budgets, grant budgets, restricted fund budgets, public-good software budgets, technical asset budgets, controlled-room budgets, and continuity budgets before Board approval where required.
170.3 Financial Statement Review. The Committee may review financial statements, management accounts, cash flow, balance sheet, statement of activities, restricted fund schedules, support schedules, variance reports, and financial disclosures.
170.4 Accounts, Reconciliations, and Treasury Review. The Committee may review accounting systems, bank accounts, reconciliations, reserves, cash management, treasury controls, bank authority, signatory controls, payment controls, and segregation of duties.
170.5 Audit, Review Engagement, Compilation, or Independent Financial Review Oversight. The Committee may oversee audits, review engagements, compilations, independent financial reviews, tax return preparation, management letters, auditor independence, remediation, and Board reporting.
170.6 Restricted Funds Oversight. The Committee may monitor restricted funds, donor restrictions, grant restrictions, sponsorship restrictions, public-good support restrictions, in-kind contribution restrictions, release conditions, expenditure compliance, and closeout.
170.7 Grant, Donation, Sponsorship, Subscription, Fee, In-Kind, and Cost-Recovery Oversight. The Committee may review the financial treatment and controls for grants, donations, sponsorships, subscriptions, training fees, Academy fees, program fees, cost recovery, fellowships, prizes, awards, and in-kind contributions.
170.8 Procurement and Contracting Oversight. The Committee may review procurement processes, vendor selection procedures, contracting thresholds, conflicts, related-party controls, competition compliance, documentation, and alignment with public-benefit purpose. Procurement oversight shall not create public procurement authority or provider preference.
170.9 Signing Authority and Expenditure Threshold Oversight. The Committee may recommend signature authorities, spending thresholds, bank authorities, payment approvals, co-signature requirements, emergency spending limits, and authority matrix controls.
170.10 Fraud, Anti-Corruption, Gifts, Hospitality, and Expense Oversight. The Committee may oversee fraud prevention, anti-corruption controls, gifts, hospitality, travel, expenses, reimbursement, credit cards, procurement integrity, whistleblower channels, and investigation escalation.
170.11 Tax and Nonprofit Compliance Interface. The Committee may coordinate with legal, tax, and compliance functions on tax-exempt or tax-exempt-compatible operations, federal tax filings, state filings, charitable solicitation, unrelated business income review, private benefit, inurement, excess benefit transactions, and public support.
170.12 Insurance Oversight. The Committee may review directors’ and officers’ insurance, general liability, cyber, professional liability, employment practices, fiduciary, crime, event, property, research, lab, travel, and other insurance.
170.13 Risk Register Oversight. The Committee may review the risk register, including financial, legal, operational, cyber, data, AI, public authority, finance-boundary, certification-boundary, safeguards, reputation, continuity, and Nexus interface risks.
170.14 Issue Register and Control Register Oversight. The Committee may review issue registers, control registers, remediation status, open action items, responsible owners, deadlines, and closeout.
170.15 Internal Controls Testing. The Committee may oversee internal controls testing, including cash controls, contracting controls, grant controls, restricted fund controls, reimbursement controls, access controls, segregation of duties, approval workflows, and record integrity.
170.16 Private Benefit, Inurement, and Related-Party Financial Review. The Committee may review compensation, reimbursements, related-party transactions, sponsor benefits, donor benefits, provider arrangements, host arrangements, intellectual property arrangements, data arrangements, and other transactions for private benefit, inurement, and excess benefit concerns.
170.17 Financial Capture and Concentration Review. The Committee may review reliance on major sponsors, donors, funders, providers, hosts, cloud providers, AI providers, technical contributors, public authorities, or enterprise actors where financial dependency may threaten independence, publication integrity, technical integrity, public authority access discipline, or public-benefit purpose.
170.18 Finance, Audit, Risk, and Internal Controls Records. The Committee shall maintain records of budgets, financial reviews, audit materials, restricted funds, support controls, procurement reviews, signing authorities, internal controls, risk registers, issue registers, fraud matters, private benefit reviews, capture reviews, recommendations, and Board actions.
Section 171. Evidence, Methods, Observability, Ontology, and Technical Truth Committee
171.1 Committee Purpose. The Evidence, Methods, Observability, Ontology, and Technical Truth Committee may support oversight of evidence doctrine, method integrity, observability methods, ontology governance, controlled vocabulary, technical truth methods, source lineage, provenance, confidence, uncertainty, public-safe technical claims, Truth Engine methods, and correction pathways.
171.2 Evidence Doctrine Oversight. The Committee may review evidence doctrine, evidence classes, admissible sources, evidence quality, data-to-evidence conversion, evidentiary limitations, public-safe evidence use, and evidence interface rules for Docket support, Grid support, GRF-facing inputs, and GRA-facing technical inputs.
171.3 Evidence Quality Review. The Committee may review evidence for reliability, relevance, provenance, sufficiency, uncertainty, bias, incompleteness, technical limitations, stale status, disputed status, and correction history.
171.4 Source Lineage and Provenance Review. The Committee may review source lineage, custody, provenance, chain of custody, data origin, sensor origin, model origin, dashboard origin, software origin, DLT or blockchain references, DePIN records, AI-RAN or O-RAN signal origin, and human review.
171.5 Confidence and Uncertainty Framework Review. The Committee may review confidence frameworks, uncertainty classifications, confidence language, probability language, error ranges, limitation language, public-safe summaries, and misuse prevention.
171.6 Data-to-Evidence Rules Review. The Committee may review rules converting raw data, sensor feeds, model outputs, cyber telemetry, geospatial materials, Earth observation data, digital twin outputs, DePIN records, DLT records, AI-RAN signals, O-RAN signals, and dashboard outputs into evidence records.
171.7 Assurance and Evidence Pack Review. The Committee may review assurance structures and evidence packs for completeness, limitations, provenance, public-safe language, controlled vocabulary, boundary compliance, and correctionability. Evidence packs shall not be represented as recognition, finance-readiness, certification, procurement approval, rating, or public authority action.
171.8 Methods Stewardship Review. The Committee may review methods for validation, verification, corroboration, benchmarking, red-team review, model review, simulation, scenario analysis, degraded-mode awareness, and public-safe reporting.
171.9 Method Versioning and Custody Review. The Committee may review method registers, versioning, custodianship, effective dates, review cycles, supersession, withdrawal, archive status, and correction records.
171.10 Observability Methods Review. The Committee may review Nexus Observatory methods, observability-node methods, hub methods, cluster methods, hotspot methods, regional cluster methods, national dense Nexus core methods, sensor methods, cyber telemetry, geospatial methods, Earth observation methods, digital twin methods, edge compute, AI-RAN, O-RAN, DePIN, DLT, and dashboard methods.
171.11 Nexus Observatory Methods Review. The Committee may support Nexus Observatory compatibility by reviewing method quality, interoperability, public-safe limits, data governance, AI governance, cyber safeguards, degraded-mode awareness, and correction paths. It shall not operate as protocol authority unless separately and lawfully designated.
171.12 Ontology and Controlled Vocabulary Review. The Committee may review definitions, taxonomies, schemas, data dictionaries, risk categories, maturity concepts, technology-family terms, public authority capacity terms, finance-boundary terms, certification-boundary terms, recognition terms, Docket terms, Grid terms, proof receipt terms, and Nexus-compatible claim terms.
171.13 Semantic Interoperability Review. The Committee may review semantic interoperability across GCRI US, GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Standards, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, consortiums, national companies, Project SPVs, providers, sponsors, hosts, public authorities, universities, laboratories, and communities.
171.14 Nexus Truth Engine Methods Review. The Committee may review Truth Engine methods for source comparison, corroboration, contradiction, failed signals, spoof indicators, confidence, uncertainty, human review, automated output limitation, public-safe output, and correction triggers.
171.15 Technical Truth Output Limits Review. The Committee shall ensure that technical truth outputs are not represented as public authority decisions, public warnings, emergency commands, recognition, finance-readiness, certification, procurement approval, rating, investment advice, provider preference, sponsor entitlement, or operational instructions.
171.16 Evidence Challenge, Correction, Supersession, Withdrawal, and Retraction Review. The Committee may review challenges to evidence, methods, observability outputs, ontology terms, public-safe reports, technical baselines, datasets, dashboards, proof receipts, public claims, and technical truth outputs, and may recommend correction, supersession, withdrawal, retraction, takedown, or archive.
171.17 Evidence, Methods, Observability, Ontology, and Technical Truth Records. The Committee shall maintain records of evidence reviews, method reviews, observability reviews, ontology reviews, controlled vocabulary reviews, Truth Engine reviews, confidence and uncertainty reviews, challenges, corrections, supersessions, withdrawals, retractions, and recommendations.
Section 172. Research Integrity, Ethics, Peer Review, and Publication Integrity Committee
172.1 Committee Purpose. The Research Integrity, Ethics, Peer Review, and Publication Integrity Committee may support oversight of research integrity, research ethics, peer review, publication integrity, human-subjects review coordination, community review, Tribal and Indigenous protocol review, protected knowledge review, sponsored research independence, research misconduct review, correction, supersession, withdrawal, retraction, and archive.
172.2 Research Agenda Review. The Committee may review research agendas for public-benefit alignment, evidence integrity, methods quality, safeguards, data / AI / cyber controls, conflicts, sponsor independence, feasibility, and public-safe publication.
172.3 Research Integrity Oversight. The Committee may oversee integrity controls addressing fabrication, falsification, plagiarism, misleading claims, undisclosed conflicts, suppressed evidence, sponsor influence, provider influence, improper authorship, data misuse, model misuse, and defective corrections.
172.4 Research Ethics Oversight. The Committee may review research ethics pathways, consent requirements, participant protections, community review, public authority data restrictions, human-subjects review, health-sensitive review, youth and vulnerable population review, and do-no-harm considerations.
172.5 IRB or Equivalent Review Interface Where Applicable. Where human-subjects research or equivalent review is required or appropriate, the Committee may coordinate with an institutional review board, ethics board, university, laboratory, public authority, community review structure, or other competent body. The Committee shall not substitute for legally required IRB or equivalent review unless lawfully authorized.
172.6 Human-Subjects Review. The Committee may identify whether activities involve human subjects, personal information, interviews, surveys, observation, behavioral data, health-sensitive data, children’s data, vulnerable populations, public authority personnel, community participants, or other protected participants requiring review.
172.7 Health-Sensitive Research Review. The Committee may review health-sensitive research for privacy, consent, risk, public-safe reporting, public health boundary discipline, non-clinical limits, non-medical advice limits, protected knowledge, and public authority interface concerns.
172.8 Youth and Vulnerable Population Review. Research involving youth, vulnerable populations, remote communities, disaster-exposed communities, climate-exposed communities, infrastructure-exposed communities, or rights-bearing populations shall receive heightened review.
172.9 Community Review. The Committee may require community review where research affects communities, local knowledge, territorial knowledge, public-safe mapping, vulnerability, environmental sensitivity, health sensitivity, civil rights, accessibility, or community harm risk.
172.10 Tribal, Indigenous, Local, Territorial, Cultural, Environmental, and Protected Knowledge Review. Research involving Tribal Nations, Indigenous governments, Indigenous knowledge holders, Indigenous data, local knowledge, territorial knowledge, cultural knowledge, environmental knowledge, or protected knowledge shall be reviewed for consent, non-consent, withdrawal, attribution, non-attribution, restricted circulation, and do-no-harm.
172.11 Sponsored Research Independence Review. The Committee may review sponsored research for independence, publication rights, sponsor disclosure, provider disclosure, funding influence, outcome purchase, veto risk, suppression risk, data access, conflict, and public-safe reporting.
172.12 Research Conflict Review. The Committee may review conflicts affecting researchers, officers, directors, sponsors, providers, donors, funders, hosts, public authorities, universities, laboratories, contractors, and contributors.
172.13 Reproducibility and Replication Review. The Committee may review reproducibility, replication, data availability, code availability, methods clarity, limitations, model dependency, uncertainty, benchmark integrity, and public-good technical memory.
172.14 Peer Review and Technical Review Design. The Committee may design peer review and technical review processes, including reviewer eligibility, independence, blind or open review, minority views, red-team review, model review, public-safe review, and publication readiness.
172.15 Research Publication Integrity Review. The Committee may review publications, whitepapers, reports, datasets, dashboards, maps, public-safe summaries, Academy materials, technical notes, and repository materials for accuracy, limitation language, authorship, attribution, conflicts, sponsor disclosure, provider disclosure, public authority boundary, finance boundary, certification boundary, procurement neutrality, recognition boundary, data / AI / cyber controls, and safeguards.
172.16 AI-Use Disclosure in Research Review. The Committee may require disclosure of AI use in research design, data analysis, drafting, coding, model evaluation, summarization, translation, peer review, figure generation, or publication workflows. AI-assisted work shall be human-reviewed and record-supported.
172.17 Research Misconduct Intake and Review. The Committee may receive or review allegations of research misconduct, including fabrication, falsification, plagiarism, data manipulation, model manipulation, benchmark manipulation, undisclosed conflicts, sponsor influence, retaliation, protected knowledge misuse, or publication suppression.
172.18 Research Correction, Supersession, Withdrawal, Retraction, and Archive Review. The Committee may recommend correction, errata, supersession, withdrawal, retraction, takedown, archive, public-safe clarification, controlled notice, or further review where research outputs are defective or unsafe.
172.19 Research Integrity, Ethics, Peer Review, and Publication Integrity Records. The Committee shall maintain records of research reviews, ethics reviews, IRB interfaces, community reviews, Tribal and Indigenous reviews, protected knowledge reviews, conflicts, peer reviews, publication reviews, misconduct reviews, corrections, withdrawals, retractions, and archives.
Section 173. Data Governance, Privacy, AI Governance, Verifiable Compute, and Cybersecurity Committee
173.1 Committee Purpose. The Data Governance, Privacy, AI Governance, Verifiable Compute, and Cybersecurity Committee may support oversight of data governance, privacy, rights-bearing data, AI governance, model registers, inference records, compute workload records, agentic AI, verifiable compute, cybersecurity, secure development, repository security, incident response, business continuity, disaster recovery, and vendor security.
173.2 Data Governance Oversight. The Committee may review data classification, data minimization, purpose limitation, access controls, retention, deletion, legal hold, provenance, data-sharing rules, public authority data rules, and public-safe release controls.
173.3 Privacy Oversight. The Committee may review privacy practices, consent, notice, de-identification, pseudonymization, aggregation, redaction, cross-border transfer, breach response, and privacy-by-design.
173.4 Rights-Bearing Data Oversight. The Committee may review rights-bearing data, including personal information, sensitive personal information, children’s data, health-sensitive data, civil-rights-relevant data, public authority personnel data, community-protected data, and protected knowledge.
173.5 Public Authority Data Oversight. The Committee may review public authority data contribution, use, publication, confidentiality, access restrictions, public records sensitivity, cybersecurity obligations, public-safe limitation language, and official-reference controls.
173.6 Health-Sensitive, Cyber-Sensitive, Infrastructure-Sensitive, Community-Protected, Tribal / Indigenous, and Protected Knowledge Data Review. The Committee may apply heightened controls to data involving health, cyber, infrastructure, communities, Tribal or Indigenous data, local or territorial knowledge, environmental sensitivity, cultural sensitivity, protected knowledge, or safety-sensitive locations.
173.7 Cross-Border Transfer and Sovereign Data Zone Review. The Committee may review cross-border transfers, North America data interfaces, sovereign data zones, cloud location, compute location, data localization, public authority restrictions, Tribal and Indigenous data expectations, and conflict-of-law issues.
173.8 AI Governance Oversight. The Committee may review AI-use policies, approved systems, prohibited systems, prohibited inputs, output review, human oversight, AI-use disclosures, automated decision limits, public-safe output controls, model risk, and agentic AI restrictions.
173.9 Model Register Review. The Committee may review model registers documenting model identity, owner, purpose, data sources, access class, approval status, risk class, evaluation status, limitations, review date, retirement status, and correction history.
173.10 Dataset Card, Model Card, System Card, Benchmark Card, and Evaluation Harness Review. The Committee may review dataset cards, model cards, system cards, benchmark cards, evaluation harnesses, test sets, gold vectors, negative tests, assumptions, limitations, bias assessments, and public-safe summaries.
173.11 Training, Fine-Tuning, Embedding, Retrieval, and Model Improvement Restrictions Review. The Committee may review restrictions on using Corporation materials, public authority data, personal information, protected knowledge, confidential research, sponsor or provider confidential materials, code, documents, prompts, embeddings, and outputs for model training, fine-tuning, retrieval, or model improvement.
173.12 Inference Records and Human Review Review. The Committee may review inference-record requirements, output logging, prompt logging, human review, escalation triggers, public-safe limitations, hallucinated authority controls, and correction pathways.
173.13 Agentic AI Control Review. The Committee may review agentic AI tools, autonomous workflows, tool access, permissions, sandboxing, approval gates, financial restrictions, publication restrictions, repository restrictions, public authority restrictions, data access limits, and emergency stop controls.
173.14 Verifiable Compute and Compute Workload Record Review. The Committee may review verifiable compute methods, compute-to-data, secure enclaves, confidential computing, sovereign compute, workload records, audit trails, proof receipts, compute-output correction, and human-review requirements.
173.15 Cybersecurity Baseline Review. The Committee may review cybersecurity baselines, identity and access management, authentication, authorization, logging, monitoring, vulnerability management, key management, secret management, device security, cloud security, repository security, and incident readiness.
173.16 Secure Development, Repository Security, Secure Release, SBOM, Signing, Provenance, and Vulnerability Review. The Committee may review secure development lifecycle, code review, dependency review, software bills of materials, artifact signing, provenance, reproducible builds where applicable, vulnerability disclosure, patching, rollback, and release gates.
173.17 Incident Response, Business Continuity, Backup, Disaster Recovery, and Vendor Security Review. The Committee may review incident response plans, breach response, AI incident response, cyber incident response, backup, disaster recovery, business continuity, vendor security, cloud provider risk, AI provider risk, data processor risk, and continuity of public-good technical assets.
173.18 Data, Privacy, AI, Compute, and Cybersecurity Records. The Committee shall maintain records of data reviews, privacy reviews, AI reviews, model registers, inference records, compute workload reviews, cyber reviews, incident reviews, access controls, vendor reviews, and corrective actions.
Section 174. Public-Good Software, Open Technical Baselines, Intellectual Property, Licensing, and Secure Release Committee
174.1 Committee Purpose. The Public-Good Software, Open Technical Baselines, Intellectual Property, Licensing, and Secure Release Committee may support oversight of public-good software, open technical baselines, reference architectures, schemas, APIs, SDKs, dashboards, data dictionaries, technical profiles, test harnesses, benchmarks, repository governance, secure release, software supply chain, contributor governance, licensing, IP chain of title, anti-enclosure, compatibility claims, commercial use boundaries, takedown, correction, deprecation, retirement, and archive.
174.2 Public-Good Technical Asset Register Review. The Committee may review the public-good technical asset register, including asset title, version, custodian, repository, access class, publication class, license, dependency status, security status, review cycle, supersession, archive status, and correction history.
174.3 Public-Good Software Stewardship Review. The Committee may review whether software assets are stewarded for public-benefit purposes, reproducibility, interoperability, secure use, anti-enclosure, public-safe documentation, technical literacy, and Nexus public-good stack compatibility.
174.4 Open Technical Baseline Review. The Committee may review open technical baselines, reference implementations, interoperability profiles, schemas, data dictionaries, benchmark libraries, technical documentation, and public-good methods to ensure they are accurate, versioned, limited, and not overclaimed.
174.5 Reference Architecture, Schema, API, SDK, Dashboard, Data Dictionary, Technical Profile, Test Harness, Gold Vector, Negative Test, and Benchmark Asset Review. The Committee may review technical assets for purpose, scope, assumptions, inputs, outputs, limitations, dependencies, security, privacy, AI governance, public authority boundary, finance boundary, certification boundary, procurement neutrality, safeguards, and correctionability.
174.6 Repository Governance Review. The Committee may review repository ownership, access, branch protection, maintainer rights, contributor roles, issue handling, pull request review, release approvals, archive status, fork notices, and repository security.
174.7 Secure Development Lifecycle Review. The Committee may review secure development procedures, threat modeling, code review, dependency scanning, secret scanning, vulnerability handling, static or dynamic analysis, test coverage, model-generated code controls, and release readiness.
174.8 Secure Release Review. The Committee may review release gates, signing, provenance, SBOM, release notes, limitation language, public-safe notices, rollback plans, vulnerability disclosures, access classifications, and publication approvals.
174.9 Supply-Chain Assurance Review. The Committee may review software supply-chain risks, dependencies, packages, maintainers, build systems, CI/CD systems, artifacts, registries, container images, third-party components, AI-generated code, and malicious contribution risks.
174.10 SBOM, Artifact Signing, Provenance, Dependency, and Vulnerability Review. The Committee may review software bills of materials, artifact signing, provenance attestations, dependency health, license conflicts, vulnerability reports, patch plans, exploitability, secure release timing, and public-safe vulnerability communication.
174.11 Contributor Terms and Contributor License Agreement Review. The Committee may review contributor terms, contributor license agreements, assignment instruments, developer certificates, attribution, moral rights where applicable, employer rights, sponsor or provider disclosure, and contributor eligibility.
174.12 IP Ownership and Chain-of-Title Review. The Committee may review IP ownership, chain of title, third-party rights, open-source obligations, proprietary restrictions, data rights, model rights, documentation rights, patent sensitivity, trademarks, logos, badges, and public-good asset protections.
174.13 Open Licensing and Restricted Licensing Review. The Committee may review license strategy, open licensing, permissive licensing, copyleft licensing, defensive licensing, restricted licensing where needed, public-good use restrictions, commercial use boundaries, sanctions restrictions, export-control restrictions, protected knowledge restrictions, and public authority restrictions.
174.14 Patent, Defensive Publication, Royalty, Standards-Essential, and Anti-Enclosure Review. The Committee may review patent exposure, defensive publication, royalty restrictions, standards-essential risks, interoperability risks, anti-enclosure provisions, public-good continuity, and avoidance of private capture of public-good technical assets.
174.15 Fork, Compatibility, and Nexus-Compatible Claim Review. The Committee may review forks, derivative works, compatibility claims, Nexus-compatible claims, implementation claims, conformance statements, benchmark claims, proof-receipt claims, and public-good software references. No fork, technical asset, benchmark result, or compatibility note shall be represented as certification, procurement approval, recognition, finance-readiness, provider preference, public authority adoption, or operational authorization unless separately and lawfully authorized.
174.16 Commercial Use Boundary Review. The Committee may review commercial use of public-good software, technical baselines, datasets, APIs, dashboards, schemas, benchmarks, documentation, and marks to prevent private capture, misleading claims, provider preference, sponsor control, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, and unsafe reliance.
174.17 Takedown, Correction, Deprecation, Retirement, and Archive Review. The Committee may recommend takedown, correction, limitation, patching, revocation, deprecation, retirement, archive, supersession, public-safe notice, security advisory, or repository restriction for defective, unsafe, stale, vulnerable, misleading, overclaimed, rights-infringing, protected-knowledge-exposing, or boundary-violating technical assets.
174.18 Public-Good Software, Technical Baseline, IP, Licensing, and Secure Release Records. The Committee shall maintain records of technical asset reviews, repository reviews, secure release approvals, SBOMs, signing, provenance, vulnerability reviews, contributor terms, IP reviews, licensing reviews, anti-enclosure reviews, fork and compatibility reviews, commercial use reviews, takedowns, corrections, deprecations, retirements, archives, and Board or officer actions.
Section 175. Public Authority Learning, Government Interface, Public-Safe Reporting, and Capacity Classification Committee
175.1 Committee Purpose. The Public Authority Learning, Government Interface, Public-Safe Reporting, and Capacity Classification Committee may be established to support the Corporation’s public authority learning function, government-interface discipline, public-safe reporting discipline, and capacity-classification controls. The Committee shall assist the Board, officers, and authorized program bodies in ensuring that federal, state, territorial, District of Columbia, Tribal, Indigenous, local, county, municipal, metropolitan, utility, port, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, infrastructure, and cross-border public authority interfaces remain lawful, bounded, recorded, non-executing, non-substitutive, and public-benefit aligned.
The Committee shall operate as a review, learning-support, interface-discipline, and escalation body. It shall not act as a public authority, emergency command body, public warning authority, regulator, public finance approver, procurement authority, grant approver, permitting body, sovereign decision-maker, public-private partnership approving body, or official government representative.
175.2 Federal Public Authority Interface Review. The Committee may review interfaces with federal agencies, federal departments, federal commissions, federal emergency, health, safety, infrastructure, cyber, environment, energy, telecom, science, technology, national security, grants, and research bodies, and federal public authority participants. Such review shall address capacity classification, participation terms, data restrictions, public records sensitivity, ethics constraints, public-safe limitation language, public authority reference permissions, meeting records, and non-delegation language.
Federal public authority interface review shall not imply federal endorsement, federal adoption, regulatory approval, funding approval, procurement approval, grant approval, public warning, emergency command, or sovereign obligation.
175.3 State Public Authority Interface Review. The Committee may review interfaces with state agencies, governors’ offices, state emergency management bodies, state public health bodies, state public safety bodies, state environmental agencies, state infrastructure agencies, public utility bodies, state cyber offices, state research and innovation bodies, state procurement offices, state finance offices, and other state public authority participants. Review shall ensure state-by-state localization without fragmentation and shall verify that no state interface is represented as legal authority, procurement approval, funding commitment, regulatory approval, public warning, or official adoption unless separately created by lawful public authority action outside GCRI US governance.
175.4 District of Columbia and Territorial Public Authority Interface Review. The Committee may review District of Columbia and territorial public authority interfaces, including Puerto Rico, Guam, the U.S. Virgin Islands, American Samoa, and the Northern Mariana Islands, where lawfully engaged. Review shall include local legal context, public authority capacity, territorial data restrictions, public-safe reporting limitations, language and accessibility needs, infrastructure sensitivity, emergency management context, community safeguards, and records discipline.
No District of Columbia or territorial interface shall be used to imply territorial public authority delegation, procurement preference, public finance approval, public warning, emergency command, certification, recognition, finance-readiness, or enterprise execution.
175.5 Tribal and Indigenous Government Interface Review Where Lawfully and Respectfully Structured. The Committee may review interfaces with Tribal Nations, Indigenous governments, Indigenous institutions, Indigenous knowledge holders, and Indigenous data stewards where lawfully and respectfully structured. Review shall preserve Tribal sovereignty, Indigenous governance, consent and non-consent pathways, protected knowledge, Indigenous data safeguards, cultural protocols, attribution and non-attribution rules, withdrawal rights where applicable, public-safe mapping limits, and do-no-harm discipline.
No interface with a Tribal Nation or Indigenous government shall be treated as consent, endorsement, data transfer, knowledge transfer, public authority delegation, official adoption, or waiver of rights unless expressly, lawfully, and specifically recorded by the competent Tribal or Indigenous authority.
175.6 Local, County, Municipal, Metropolitan, Port, Utility, Public Health, Emergency Management, Public Safety, Public Works, Telecom, Energy, Water, Food, Cyber, and Infrastructure Interface Review. The Committee may review interfaces with local, county, municipal, metropolitan, port, utility, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, transportation, and infrastructure actors. Review shall consider operational sensitivity, public-safe language, infrastructure-sensitive information, emergency communications boundaries, data controls, cyber controls, public records exposure, procurement integrity, community safeguards, accessibility, and capacity classification.
Such review shall not create operational control over public infrastructure or public services. The Corporation may support learning, evidence literacy, methods literacy, observability literacy, scenario learning, and after-action learning, but shall not direct public resources, issue public orders, dispatch responders, trigger evacuations, approve procurement, or assume emergency management functions.
175.7 Capacity Classification Review. The Committee shall support classification of public authority participation capacity. Capacity categories may include official capacity, observer, regulator-listening, public finance reader, emergency-management participant, public infrastructure operator, simulation participant, technical learner, data contributor, advisory participant, or other approved classification.
Capacity classification shall be recorded before or promptly after material participation and shall be reflected in meeting records, attendance records, public authority materials, public-safe reports, controlled-room records, data contribution records, and public references where material. Ambiguity shall be resolved through the most restrictive lawful reading until clarified.
175.8 Official-Capacity Records Review. Where a public authority participant acts or appears in official capacity, the Committee may review whether the official capacity has been properly documented. Official-capacity records shall identify the public authority, participant, title, scope, attendance purpose, authority limitations, any approval or non-approval status, data contribution constraints, public statement limits, and whether the participant may be named publicly.
Official-capacity records shall not be used to imply public authority adoption of GCRI US outputs unless the public authority has separately and lawfully adopted such outputs through its own procedures.
175.9 Observer, Regulator-Listening, Public Finance Reader, Emergency-Management Participant, Public Infrastructure Operator, and Simulation Participant Status Review. The Committee may review specialized public authority statuses, including observer, regulator-listening, public finance reader, emergency-management participant, public infrastructure operator, and simulation participant status. Each status shall include limitation language making clear that participation does not create public authority delegation, public warning, emergency command, procurement approval, finance approval, public finance approval, regulatory approval, funding approval, sovereign obligation, or official adoption.
Where the context involves finance-adjacent, procurement-adjacent, emergency-adjacent, or regulatory-adjacent material, the Committee shall require heightened records, limitation language, and escalation to counsel, compliance, Board, or competent officer where appropriate.
175.10 Public Authority Data Contribution Review. The Committee may review public authority data contribution arrangements for authority, consent, permitted use, classification, confidentiality, privacy, public records exposure, cyber sensitivity, infrastructure sensitivity, health sensitivity, retention, deletion, publication, redaction, aggregation, public-safe mapping, cross-border transfer, and correction obligations.
Public authority data contribution shall not by itself create endorsement, adoption, public warning, regulatory approval, funding approval, procurement approval, public finance approval, official decision, or permission to publish sensitive data.
175.11 Public Authority Reference Approval Review. The Committee may review proposed references to public authorities in reports, websites, decks, grant materials, sponsorship materials, press materials, public-safe reports, maps, dashboards, datasets, public-good software documentation, Academy materials, technical baselines, controlled-room summaries, and public statements. Review shall ensure that references do not imply endorsement, adoption, approval, partnership, procurement, funding, public finance, emergency command, public warning, or sovereign support unless specifically authorized by competent record.
175.12 Public Authority Room and Controlled-Room Review. The Committee may review the creation, admission criteria, access class, confidentiality rules, material controls, public authority capacity classification, no-download rules, data handling, AI-use restrictions, record custody, and closeout requirements for public authority rooms and controlled rooms involving public authorities. Such rooms shall be designed for learning, evidence review, scenario review, public-safe clarification, or technical literacy, not for government decision-making unless separately and lawfully structured by the public authority outside the Corporation.
175.13 Public-Safe Reporting Support. The Committee may support public-safe reporting by reviewing limitation language, audience classification, redaction, aggregation, map sensitivity, protected knowledge risk, public authority references, emergency communication risk, finance-boundary risk, procurement-boundary risk, certification-boundary risk, and public reliance risk.
Public-safe reporting shall be accurate, bounded, evidence-supported, correctionable, and non-executing. It shall not be drafted to create alarm, public warning, public command, market signal, investment signal, procurement signal, or governmental reliance beyond its stated purpose.
175.14 No Public Authority Delegation Review. The Committee shall review and prevent public authority delegation overclaims. No committee, council, officer, staff member, participant, public authority room, controlled room, dashboard, dataset, AI output, proof receipt, technical baseline, public-safe report, meeting, exercise, simulation, or public statement shall be treated as granting public authority power to the Corporation unless a lawful public authority delegation exists and the Board has separately approved acceptance where lawful.
175.15 No Public Warning, Emergency Command, Procurement Approval, Funding Approval, Regulatory Approval, Public Finance Approval, Sovereign Obligation, PPP, or Official Adoption by Participation Review. The Committee shall review public authority interfaces for prohibited overclaims, including claims that participation creates public warning, emergency command, procurement approval, funding approval, regulatory approval, public finance approval, sovereign obligation, public-private partnership, official adoption, official standard, official risk classification, official readiness finding, or official implementation decision.
Where such risk exists, the Committee may recommend hold, correction, withdrawal, takedown, re-scope, limitation language, controlled notice, public clarification, counsel review, public authority notice, or Board review.
175.16 Public Authority Correction Review. The Committee may review and recommend corrections where public authority participation, public authority data, public authority reference, public authority room materials, public-safe reports, dashboards, maps, technical baselines, evidence packs, or public statements create confusion or reliance risk. Corrections may include controlled clarification, public clarification, supersession, withdrawal, retraction, takedown, archive, public authority notice, participant notice, or repository correction.
175.17 Public Authority Learning and Government Interface Records. The Committee shall maintain Public Authority Learning and Government Interface Records, including capacity classifications, attendance records, meeting records, official-capacity records, observer records, regulator-listening records, public finance reader records, emergency-management participant records, public infrastructure operator records, simulation records, public authority data contribution records, public authority reference approvals, limitation language, public-safe reporting reviews, corrections, escalations, and Board or officer actions.
Section 176. Ethics, Safeguards, Civil Rights, Accessibility, Community, Tribal / Indigenous, and Protected Knowledge Committee
176.1 Committee Purpose. The Ethics, Safeguards, Civil Rights, Accessibility, Community, Tribal / Indigenous, and Protected Knowledge Committee may be established to protect the Corporation’s public-benefit purpose, rights-respecting posture, community safeguards, civil rights, accessibility, Tribal and Indigenous protocol respect, Indigenous data safeguards, protected knowledge controls, public-safe mapping discipline, grievance pathways, remedy pathways, non-retaliation, and do-no-harm obligations.
The Committee shall ensure that technical ambition, public authority interest, sponsor expectations, provider interests, publication timelines, research incentives, operational convenience, AI outputs, dashboard outputs, or Nexus interface pressures do not override safeguards, rights, consent, dignity, protected participation, protected knowledge, or public-safe communication.
176.2 Community Safeguards Review. The Committee may review programs, publications, datasets, dashboards, maps, AI outputs, digital twins, observability methods, field activities, public authority learning sessions, controlled rooms, technical pilots, Academy materials, public-safe reports, and external communications for community harm risk. Review may address vulnerability exposure, stigmatization, location sensitivity, retaliation risk, public authority misuse risk, infrastructure sensitivity, ecological sensitivity, cultural sensitivity, health sensitivity, and public misunderstanding.
176.3 Tribal Sovereignty and Indigenous Governance Respect Review. The Committee shall support review of activities involving Tribal Nations, Indigenous governments, Indigenous institutions, Indigenous communities, Indigenous knowledge holders, Indigenous data, or Indigenous territories. Review shall respect self-determination, governance protocols, consent and non-consent, restricted circulation, attribution and non-attribution, withdrawal, collective rights, cultural authority, and lawful interface pathways.
176.4 Indigenous Data and Indigenous Knowledge Safeguards Review. The Committee may review Indigenous data and Indigenous knowledge handling, including collection, storage, access, classification, publication, mapping, model training, embedding, retrieval, translation, attribution, non-attribution, deletion, sealing, archive, and correction. Indigenous data or knowledge shall not be extracted, commercialized, generalized, trained into models, publicly mapped, or used for sponsor, provider, funder, public authority, or institutional convenience without lawful and respectful authority.
176.5 Local, Territorial, Cultural, Environmental, and Protected Knowledge Review. The Committee may review local knowledge, territorial knowledge, cultural knowledge, environmental knowledge, community-protected knowledge, and other protected knowledge. Review shall determine whether materials require restriction, redaction, aggregation, non-public handling, community review, consent, non-consent, attribution limits, or do-no-harm controls.
176.6 Civil Rights Review. The Committee may review civil rights implications of programs, participation rules, datasets, models, AI systems, public-safe reports, maps, dashboards, Academy materials, public authority interfaces, controlled rooms, research activities, and communications. Review may address discrimination, disparate impact, exclusion, retaliation, harassment, accessibility barriers, language access, due process concerns, and protected participation.
176.7 Non-Discrimination Review. The Committee may review whether the Corporation’s activities, access rules, program designs, participation criteria, publications, software, datasets, AI systems, or public statements create unlawful discrimination or unjustified exclusion. Corrective measures may include redesign, limitation, translation, accessibility remediation, public-safe redaction, eligibility correction, training, or suspension.
176.8 Accessibility Review. The Committee may review accessibility of governance materials, notices, participation materials, digital surfaces, websites, dashboards, forms, Academy materials, public-safe reports, meetings, controlled-room access, public authority sessions, and training materials. Accessibility shall be treated as a governance and public-benefit requirement, not merely a presentation preference.
176.9 Vulnerable and Remote Community Review. The Committee may apply heightened review to activities affecting vulnerable communities, remote communities, disaster-exposed communities, climate-exposed communities, health-exposed communities, infrastructure-exposed communities, low-resource communities, marginalized groups, youth, elders, persons with disabilities, and communities at risk of surveillance, extraction, stigmatization, or retaliation.
176.10 Public-Safe Mapping Review. The Committee may review maps, geospatial outputs, Earth observation outputs, dashboards, digital twins, sensor outputs, AI-generated spatial outputs, infrastructure maps, hotspot maps, community vulnerability maps, and public authority maps to ensure that they do not expose sensitive locations, protected knowledge, vulnerable populations, critical infrastructure, ecological assets, cultural sites, or community risk in unsafe ways.
Public-safe mapping may require aggregation, blurring, delay, suppression, controlled circulation, no-download access, restricted legends, non-attribution, or takedown.
176.11 Consent, Non-Consent, Attribution, Withdrawal, Restriction, and Correction Pathway Review. The Committee may review whether consent is required, whether non-consent has been expressed, whether attribution is appropriate, whether non-attribution is required, whether withdrawal rights apply, whether restrictions have been honored, and whether correction pathways are accessible. Consent shall not be inferred from attendance, silence, prior participation, public authority involvement, community representation, or data availability unless lawful and specifically recorded.
176.12 Grievance and Remedy Review. The Committee may review grievance pathways, complaint intake, remedy options, response timelines, confidentiality, non-retaliation, accessibility, language access, community interface, escalation, and closeout. Remedies may include correction, apology, takedown, access restriction, participation adjustment, process redesign, referral, sanctions, training, or other appropriate measures.
176.13 Protected Participation, Whistleblowing, Dissent Protection, Confidential Reporting, and Non-Retaliation Review. The Committee shall support protected participation, whistleblowing, safeguards escalation, dissent, confidential reporting, and non-retaliation. No person shall be penalized for good-faith reporting of safeguards concerns, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, data misuse, AI misuse, cyber risk, research misconduct, harassment, discrimination, protected knowledge breach, or public-safe publication concern.
176.14 Safeguards Stop-the-Line Review. The Committee may recommend or support stop-the-line action where continuation of an activity may create material harm to persons, communities, protected knowledge, civil rights, accessibility, privacy, public safety, public authority trust, or institutional integrity. Stop-the-line action may include hold, quarantine, access restriction, publication freeze, implementation freeze, public authority clarification, data freeze, model freeze, repository restriction, or Board escalation.
176.15 Do-No-Harm Review. The Committee may conduct do-no-harm review for any activity with material public-facing, community-facing, public authority-facing, technology-facing, or rights-bearing implications. Do-no-harm review shall assess foreseeable misuse, reliance risk, exposure risk, stigmatization, extraction, inequity, cyber risk, public authority misuse, finance misuse, provider misuse, sponsor misuse, and correctionability.
176.16 Sponsor, Provider, Donor, Funder, Host, Public Authority, and Institutional Convenience Extraction Risk Review. The Committee shall review risks that sponsors, providers, donors, funders, hosts, public authorities, universities, laboratories, media actors, or the Corporation itself may extract data, knowledge, access, legitimacy, stories, imagery, public authority proximity, community trust, or protected knowledge for purposes inconsistent with public benefit and safeguards.
176.17 Ethics, Safeguards, Civil Rights, Accessibility, Community, Tribal / Indigenous, and Protected Knowledge Records. The Committee shall maintain safeguards records, including reviews, consent and non-consent records, restrictions, grievances, remedies, protected participation records, stop-the-line records, do-no-harm reviews, accessibility reviews, civil rights reviews, public-safe mapping reviews, protected knowledge records, Tribal and Indigenous interface records, corrections, and closeout records.
Section 177. Legal, Compliance, Sanctions, Export-Control, Competition, and Professional Boundary Committee
177.1 Committee Purpose. The Legal, Compliance, Sanctions, Export-Control, Competition, and Professional Boundary Committee may be established to support legal compliance, nonprofit compliance, tax compliance, charitable solicitation compliance, state qualification, privacy compliance, AI governance compliance, cybersecurity compliance, research ethics compliance, employment and workplace compliance, accessibility and civil rights compliance, lobbying and political activity controls, government ethics, gifts, grant compliance, procurement integrity, sanctions, export-control, controlled technology, national security sensitivity, competition and antitrust discipline, professional boundary controls, regulatory-perimeter review, incident review, investigation support, enforcement support, appeals, and corrective action.
The Committee shall not provide legal services to third parties, issue legal opinions unless properly authorized through counsel, act as regulator, or permit compliance review to become certification, procurement approval, finance-readiness, recognition, public authority approval, or regulated execution.
177.2 Corporate Compliance Review. The Committee may review corporate governance compliance, state nonprofit corporate requirements, registered agent status, registered office status, annual reports, minute books, director records, officer records, member records where applicable, Board resolutions, committee records, charitable solicitation registrations, foreign qualifications, and governance filings.
177.3 Tax and Nonprofit Compliance Review. The Committee may review federal tax compliance, state tax compliance, tax-exempt or tax-exempt-compatible posture, private inurement, impermissible private benefit, excess benefit transactions, unrelated business income, donor restrictions, grant restrictions, sponsorship treatment, subscription fees, program fees, cost recovery, and public support.
177.4 Charitable Solicitation and State Qualification Review. The Committee may review charitable solicitation requirements, state registrations, exemptions, fundraising language, donation receipts, online fundraising, event fundraising, restricted fund solicitations, sponsorship solicitations, and state or territorial qualification requirements.
177.5 Privacy Compliance Review. The Committee may review privacy obligations arising from personal information, sensitive personal information, children’s data, health-sensitive data, rights-bearing data, public authority data, community-protected data, cross-border data, vendor processing, data sharing, publication, retention, deletion, breach response, and privacy notices.
177.6 AI Governance Compliance Review. The Committee may review AI governance policies, approved AI tools, restricted AI uses, prohibited AI inputs, agentic AI controls, training data restrictions, model improvement restrictions, human review, AI-use disclosure, model registers, inference records, and AI incident escalation.
177.7 Cybersecurity Compliance Review. The Committee may review cybersecurity policies, identity and access controls, logging, monitoring, vulnerability management, incident response, breach notification, business continuity, disaster recovery, repository security, cloud security, vendor security, key management, secret management, and controlled-room security.
177.8 Research Ethics Compliance Review. The Committee may review research ethics, human-subjects pathways, IRB or equivalent review, public authority data restrictions, community review, Tribal and Indigenous review, protected knowledge review, health-sensitive research, youth and vulnerable population research, and publication ethics.
177.9 Employment, Contractor, Volunteer, Fellow, Advisor, Workplace, Accessibility, and Civil Rights Compliance Review. The Committee may review employment law, contractor classification, volunteer rules, fellow and advisor terms, workplace policies, harassment prevention, discrimination prevention, accessibility, accommodation, wage and hour considerations, workplace safety, remote work, secondment, confidentiality, IP, and offboarding controls.
177.10 Lobbying, Political Activity, Government Ethics, Gifts, Grant, and Procurement Integrity Review Where Applicable. The Committee may review lobbying limits, political activity restrictions, electioneering restrictions, government ethics, gifts, hospitality, public authority meetings, grant restrictions, procurement integrity, public sector conflict rules, and public authority participation constraints. No activity shall be framed to evade lobbying, campaign, procurement, or government ethics rules.
177.11 Sanctions Screening Review. The Committee may review sanctions screening for participants, donors, sponsors, funders, providers, vendors, contractors, contributors, fellows, advisors, public authority participants, controlled-room participants, data contributors, software contributors, international participants, and counterparties where appropriate.
177.12 Export-Control Review. The Committee may review export-control issues involving controlled technology, dual-use technology, technical data, software, AI models, compute systems, cryptography, cyber tools, satellite or geospatial outputs, sensors, AI-RAN, O-RAN, DePIN, DLT, robotics, drones, quantum-relevant systems, HPC, sovereign compute, and cross-border collaboration.
177.13 Controlled Technology and National Security Sensitivity Review. The Committee may review controlled technology, national security sensitivity, CFIUS-relevant sensitivity where applicable, defense or dual-use implications, infrastructure-sensitive materials, cyber-sensitive materials, public authority restrictions, and publication controls. Review may recommend restriction, compartmentalization, counsel review, export-control review, public-safe redaction, controlled-room treatment, or termination.
177.14 Competition and Antitrust Review. The Committee may review competition and antitrust controls for meetings, councils, Helix Councils, working groups, benchmarking, indices, market baseline libraries, data sharing, standards-support activities, provider participation, sponsor participation, public authority sessions, clean rooms, and controlled rooms.
177.15 Procurement Neutrality Review. The Committee may review activities that could imply provider preference, public procurement steering, vendor selection, bid advantage, public authority procurement approval, procurement-safe harbor, or procurement mandate. Corrective action may include limitation language, agenda changes, recusal, clean-team handling, public authority notice, or withdrawal.
177.16 Professional Boundary Review. The Committee may review risks that Corporation outputs could be treated as legal advice, engineering opinion, medical advice, clinical guidance, public health order, investment advice, insurance advice, banking advice, credit advice, rating opinion, procurement recommendation, emergency instruction, or other regulated professional service.
177.17 Regulatory-Perimeter Review. The Committee may review regulated-perimeter issues involving securities, investment adviser, broker-dealer, finder, banking, lending, insurance, underwriting, rating, public finance, procurement, certification, accreditation, emergency command, public warning, public authority decision, lobbying, professional services, sanctions, export-control, privacy, AI, cyber, consumer protection, and research regulation.
177.18 Incident, Investigation, Enforcement, Appeal, and Corrective Action Review. The Committee may support incident intake, investigation design, evidence preservation, legal hold, privilege protection, enforcement recommendations, appeals, corrective action, training, remediation, referrals, public or controlled correction, and closeout.
177.19 Legal, Compliance, Sanctions, Export-Control, Competition, and Professional Boundary Records. The Committee shall maintain records of compliance reviews, legal escalations, counsel interfaces, sanctions reviews, export-control reviews, controlled-technology reviews, competition reviews, procurement-neutrality reviews, professional-boundary reviews, regulatory-perimeter reviews, incidents, investigations, corrective actions, referrals, appeals, and closeout.
Section 178. Development, Grants, Donations, Sponsorship, Public-Good Support, and Anti-Capture Committee
178.1 Committee Purpose. The Development, Grants, Donations, Sponsorship, Public-Good Support, and Anti-Capture Committee may be established to support fundraising strategy, grant strategy, donation strategy, sponsorship strategy, public-good support strategy, in-kind contribution review, restricted fund review, support acceptance, tax and nonprofit compatibility, public acknowledgment controls, donor reporting, financial sustainability, and anti-capture discipline.
The Committee shall ensure that support strengthens the Corporation’s public-benefit mission without creating sponsor control, donor control, funder control, provider control, host control, public authority access purchase, outcome purchase, research finding purchase, publication veto, finance-readiness purchase, certification purchase, recognition purchase, procurement advantage, or enterprise-stack capture.
178.2 Fundraising Strategy Review. The Committee may review fundraising strategy for alignment with public-benefit purpose, nonprofit character, tax posture, mission lock, non-execution, role separation, independence, public-safe claims, and anti-capture protections. Fundraising shall not be structured as securities solicitation, investment advice, brokerage, finder activity, lending, insurance placement, public finance approval, procurement influence, or sale of institutional outcomes.
178.3 Grant Strategy Review. The Committee may review grant strategy, including public grants, private foundation grants, institutional grants, research grants, program grants, public-good infrastructure grants, Academy grants, technical baseline grants, software grants, community safeguards grants, and capacity-building grants. Grant terms shall be reviewed for mission consistency, restricted fund controls, reporting obligations, data rights, publication rights, IP rights, sponsor influence, public authority constraints, and correctionability.
178.4 Donation Strategy Review. The Committee may review donation strategy, including unrestricted donations, restricted donations, major gifts, online donations, event donations, donor-advised fund support, matching support, and in-kind donations. Donation materials shall not imply tax treatment unless lawful, and shall not offer governance control, public authority access, recognition, finance-readiness, certification, procurement advantage, provider preference, or outcome control.
178.5 Sponsorship Strategy Review. The Committee may review sponsorship strategy, sponsor categories, sponsor benefits, acknowledgment terms, event sponsorships, program sponsorships, report sponsorships, Academy sponsorships, challenge sponsorships, lab sponsorships, platform sponsorships, and public-good technical asset sponsorships. Sponsorship benefits shall be limited, transparent, public-safe, non-controlling, non-exclusive unless lawful and justified, and shall not permit sponsor veto, sponsor editorial control, sponsor research influence, sponsor provider preference, sponsor public authority access purchase, or sponsor outcome purchase.
178.6 Public-Good Support Strategy Review. The Committee may review support for public-good infrastructure, open technical baselines, public-good software, research, methods, observability, ontology, public authority learning, community safeguards, data / AI / cyber controls, Academy programs, fellowships, and public-safe reporting. Public-good support shall be structured to preserve open access, anti-enclosure, public-benefit use, correctionability, and independence.
178.7 In-Kind Contribution Review. The Committee may review in-kind contributions, including compute, cloud credits, AI services, data, software, hardware, AI-RAN equipment, O-RAN systems, DePIN resources, sensors, dashboards, cyber tools, facilities, professional services, staff secondments, event space, travel support, publications support, and technical assistance. In-kind contributions shall be valued, classified, restricted where necessary, conflict-reviewed, data-reviewed, cyber-reviewed, export-control-reviewed where applicable, and recorded.
178.8 Restricted Fund Review. The Committee may review restricted funds, donor restrictions, grant restrictions, sponsorship restrictions, expenditure limits, reporting requirements, release conditions, accounting controls, and closeout. Restricted funds shall not override mission lock, non-execution, role separation, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, safeguards, data / AI / cyber controls, publication integrity, or correctionability.
178.9 Support Acceptance Test Review. The Committee may apply a support acceptance test requiring that support be lawful, mission-aligned, non-controlling, tax-compatible, conflict-reviewed, anti-capture-compliant, public-safe, reputation-compatible, data / AI / cyber-compliant where applicable, safeguards-compliant, and compatible with non-execution and role separation.
178.10 Tax and Nonprofit Compatibility Review. The Committee may review whether support affects tax-exempt or tax-exempt-compatible status, private inurement, impermissible private benefit, excess benefit, unrelated business income, charitable solicitation, donor acknowledgment, sponsorship classification, public support tests, and restricted fund treatment.
178.11 Public Acknowledgment and Benefit Schedule Review. The Committee may review sponsor and donor acknowledgment, logo placement, event mentions, website listings, report acknowledgments, public-safe statements, benefit schedules, access benefits, ticket allocations, learning access, and controlled-room exclusions. Acknowledgment shall not imply endorsement, certification, recognition, provider preference, finance-readiness, public authority approval, procurement advantage, or official adoption.
178.12 Donor, Funder, Sponsor, Provider, Host, and Enterprise Actor Non-Control Review. The Committee shall review whether any donor, funder, sponsor, provider, host, or enterprise actor has or may obtain improper control over governance, research agenda, evidence conclusions, methods, publication timing, public authority access, technical baseline content, software release, public-safe reporting, procurement signals, certification signals, recognition signals, or finance-readiness signals.
178.13 Influence Cap and Concentration Review. The Committee may review concentration of support by source, sector, sponsor, provider, donor, funder, host, public authority, investor, insurer, lender, national company, Project SPV, region, or technology family. Influence cap review may recommend diversification, ring-fencing, independent review, firewalling, restricted acknowledgment, refusal, return, or termination.
178.14 No Control-for-Cash, Pay-to-Play, Outcome Purchase, Veto, Suppression, Public Authority Access Purchase, Provider Preference, Recognition Purchase, Finance-Readiness Purchase, Certification Purchase, or Procurement Advantage Review. The Committee shall identify and prevent any support arrangement that creates or appears to create control-for-cash, pay-to-play, outcome purchase, veto, suppression, public authority access purchase, provider preference, recognition purchase, finance-readiness purchase, certification purchase, procurement advantage, regulated-activity advantage, or enterprise-stack advantage.
178.15 Donor Reporting and Public-Safe Financial Summary Review. The Committee may review donor reports, funder reports, sponsor reports, public financial summaries, restricted fund summaries, grant closeout reports, public-safe impact summaries, and support acknowledgments. Reporting shall be accurate, records-supported, public-safe, non-misleading, and shall not overstate outcomes, public authority adoption, finance-readiness, certification, recognition, procurement advantage, or operational execution.
178.16 Refusal, Return, Restriction, Termination, or Closeout of Support. The Committee may recommend refusal, return, restriction, termination, or closeout of support where support is unlawful, mission-inconsistent, tax-incompatible, reputationally harmful, capture-risk creating, sponsor-control creating, provider-preference creating, public authority-confusing, finance-overclaiming, certification-overclaiming, procurement-overclaiming, safeguards-inconsistent, data / AI / cyber-inconsistent, or otherwise incompatible with this Bylaw.
178.17 Development, Support, and Anti-Capture Records. The Committee shall maintain records of fundraising strategy, grant review, donation review, sponsorship review, in-kind contribution review, restricted fund review, support acceptance tests, tax review, public acknowledgment review, anti-capture review, influence concentration review, refusals, returns, restrictions, terminations, closeouts, and Board or officer actions.
Section 179. Programs, Activation Dockets, Academy, Training, Fellows, Challenges, Labs, and Capability Formation Committee
179.1 Committee Purpose. The Programs, Activation Dockets, Academy, Training, Fellows, Challenges, Labs, and Capability Formation Committee may be established to support review and oversight of programs, activation dockets, readiness programs, host activations, adoption windows, replication and validation sprints, governed pilots, research labs, technical labs, controlled labs, challenge labs, Nexus Universe labs, structured data feeds, indices, signal feeds, evidence pack directories, schema registries, interoperability mapping, Academy programs, training, fellowships, scholarships, stipends, awards, technical residencies, challenges, prizes, bounties, hackathons, module foundries, venture-building enablement boundaries, partnering-office functions, needs discovery, capability mapping, delegation design, benchmarking subscriptions, market baseline libraries, program correction, closeout, and archive.
The Committee shall ensure that programs form capability without becoming execution vehicles, brokers, procurement channels, certification tracks, recognition tracks, finance-readiness pathways, provider selection mechanisms, public authority command channels, or sponsor-controlled pipelines.
179.2 Program Approval Review. The Committee may review proposed programs for public-benefit purpose, legal authority, budget, staffing, records, data / AI / cyber controls, safeguards, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, public-safe claims, and correctionability. Where Board approval is required, the Committee may recommend approval, modification, deferral, re-scope, hold, or rejection.
179.3 Activation Docket Review. The Committee may review activation dockets as structured records for proposed or ongoing program activations. Review may include purpose, scope, stakeholders, evidence basis, public authority capacity, host context, data classification, safeguards, technical readiness, resource needs, boundary risks, risk owner, decision owner, escalation path, and closeout status.
An activation docket shall not be represented as public authority approval, finance-readiness, certification, procurement approval, recognition, Grid guarantee, Docket approval by GRF, or enterprise execution authorization unless separately and lawfully created by the competent body.
179.4 National, State, Territorial, Tribal, Local, Host, and North America Readiness Program Review. The Committee may review readiness programs for national, state, territorial, Tribal-interface, Indigenous-interface, local, host-site, sectoral, and North America contexts. Review shall ensure localization without fragmentation and shall preserve public authority boundaries, non-execution, data / AI / cyber controls, safeguards, competition discipline, and role separation.
179.5 Host Activation Review. The Committee may review host activations involving universities, laboratories, public authorities, communities, facilities, infrastructure operators, innovation hubs, field sites, controlled rooms, data rooms, labs, or Nexus Universe environments. Host activation review shall address site permissions, safety, data access, facility controls, public authority context, community safeguards, operational boundaries, host confidentiality, public references, and closeout.
179.6 Adoption Window Review. The Committee may review adoption windows used for learning, onboarding, method uptake, software testing, technical literacy, public authority learning, or controlled experimentation. Adoption windows shall not be represented as procurement windows, certification windows, finance-readiness windows, provider selection windows, public authority adoption windows, or mandatory implementation periods unless separately and lawfully established by competent authority.
179.7 Replication and Validation Sprint Review. The Committee may review replication and validation sprints used to test evidence methods, technical baselines, software modules, observability methods, AI outputs, benchmarks, data pipelines, dashboards, or public-safe reporting workflows. Validation sprint results shall be classified with confidence, limitations, method notes, and correction paths and shall not be overclaimed as certification, recognition, finance-readiness, procurement approval, or public authority approval.
179.8 Governed Pilot Review. The Committee may review governed pilots to ensure that pilot scope, authority, data access, public authority participation, host participation, provider participation, sponsor participation, risk controls, safeguards, technical controls, and closeout are recorded. A governed pilot shall not create enterprise execution by GCRI US unless separately and lawfully structured outside the prohibited functions and approved by competent authority.
179.9 Research Lab, Technical Lab, Controlled Lab, Challenge Lab, and Nexus Universe Lab Review. The Committee may review lab environments, including research labs, technical labs, controlled labs, challenge labs, and Nexus Universe labs. Review shall address charter, access, safety, data class, AI-use restrictions, cyber controls, export-control risks, sponsor and provider boundaries, public authority boundaries, IP terms, publication review, public-safe claims, and closeout.
179.10 Structured Data Feed, Index, Signal Feed, Evidence Pack Directory, Schema Registry, and Interoperability Mapping Review. The Committee may review structured data feeds, indices, signal feeds, evidence pack directories, schema registries, and interoperability mappings for source legitimacy, provenance, update cycle, accuracy, access class, public-safe release, public authority reliance risk, finance reliance risk, certification reliance risk, procurement reliance risk, data / AI / cyber controls, and correctionability.
179.11 Academy Program Review. The Committee may review Academy programs, curricula, training modules, credentials of completion, learning pathways, public authority learning materials, technical literacy materials, evidence literacy materials, AI governance literacy, cyber literacy, safeguards training, and fellowship training. Academy outputs shall not be represented as professional licenses, regulated credentials, certifications, procurement qualifications, or provider approvals unless separately and lawfully authorized.
179.12 Training and Competence Record Review. The Committee may review training records and competence records for directors, officers, committee members, staff, fellows, advisors, volunteers, contributors, public authority participants, community participants, technical contributors, and controlled-room participants. Competence records shall document learning, readiness for participation, and internal access eligibility; they shall not create professional licensure or external certification by default.
179.13 Fellowship, Scholarship, Stipend, Award, and Technical Residency Review. The Committee may review fellowships, scholarships, stipends, awards, technical residencies, visiting researcher arrangements, student programs, and workforce pathways. Review shall address eligibility, public-benefit purpose, conflicts, compensation or stipend reasonableness, tax treatment, IP, confidentiality, data / AI / cyber access, safeguards, publication rights, and non-authority rules.
179.14 Challenge, Prize, Bounty, Hackathon, Module Foundry, and Venture-Building Enablement Review. The Committee may review challenges, prizes, bounties, hackathons, module foundries, and venture-building enablement activities. Such activities shall include rules, eligibility, judging criteria, IP terms, data rules, cyber rules, AI-use rules, export-control rules, sanctions screening, safety controls, sponsor restrictions, provider neutrality, public-safe claims, and non-execution language.
Venture-building enablement shall not include securities solicitation, investment advice, brokerage, capital placement, provider preference, procurement approval, certification, recognition, finance-readiness determination, or enterprise execution by the Corporation.
179.15 Partnering Office, Curated Introduction, Needs Discovery, Capability Mapping, Delegation Design, and No-Brokerage Review. The Committee may review partnering-office functions, curated introductions, needs discovery, capability mapping, and delegation design to ensure they remain educational, convening, evidence, methods, or public-good coordination functions. Such functions shall not become brokerage, finder activity, securities solicitation, procurement steering, provider selection, investment advice, lending facilitation, insurance placement, or public finance execution.
179.16 Benchmarking Subscription and Market Baseline Library Review. The Committee may review benchmarking subscriptions and market baseline libraries for competition-law compliance, aggregation, de-identification, delay, independent administration, public-safe limitations, anti-collusion controls, data rights, and non-reliance language. Benchmarking outputs shall not become ratings, investment recommendations, procurement recommendations, provider rankings, or finance-readiness determinations.
179.17 Program Correction, Closeout, and Archive Review. The Committee may review program correction, closeout, and archive. Closeout shall address deliverables, records, open risks, conflicts, data return or deletion, access revocation, public-safe correction, participant notice, funder reporting, sponsor reporting, public authority notice, technical asset archive, and lessons learned.
179.18 Programs, Academy, Training, Fellowships, Challenges, Labs, and Capability Formation Records. The Committee shall maintain records of program approvals, activation dockets, readiness programs, host activations, adoption windows, validation sprints, governed pilots, lab reviews, data feed reviews, Academy reviews, training records, fellowship records, challenge records, partnering-office reviews, benchmarking reviews, corrections, closeouts, and archives.
Section 180. Federation, Interoperability, United States State / Territorial Interfaces, North America Interfaces, Emergency Mode, and Continuity Committee
180.1 Committee Purpose. The Federation, Interoperability, United States State / Territorial Interfaces, North America Interfaces, Emergency Mode, and Continuity Committee may be established to support review of federation architecture, interoperability, GCRI Canada interfaces, GRF interfaces, GRA interfaces, Nexus Standards and Protocol Authority interfaces, Nexus Network interfaces, Nexus Observatory interfaces, Nexus Universe interfaces, Nexus Risk Management interfaces, Nexus Rails interfaces, Nexus Grid interfaces, Nexus Academy interfaces, Nexus Competence Cell interfaces, state interfaces, territorial interfaces, Tribal and Indigenous interfaces, local interfaces, sectoral interfaces, public authority interfaces, university and laboratory interfaces, community interfaces, provider and sponsor interfaces, North America cross-border interfaces, localization without fragmentation, cross-entity routing, mismatch detection, reconciliation, cure, federation KPIs, emergency governance mode, continuity of operations, recovery objectives, successor administration, data portability, exit assistance, suspension, wind-down, and orderly transfer.
180.2 Federation Architecture Review. The Committee may review federation architecture to ensure that distributed bodies, state interfaces, territorial interfaces, Tribal and Indigenous interfaces, local interfaces, public authority interfaces, technical nodes, observability environments, competence cells, controlled rooms, and program bodies operate under consistent mission lock, non-execution, role separation, records discipline, public-safe claims, data / AI / cyber controls, safeguards, and correctionability.
180.3 GCRI Canada Interface Review. The Committee may review interfaces with GCRI Canada to preserve legal separateness, shared mission without merger, shared doctrine without shared liability, shared ontology without shared treasury, shared methods without automatic agency, cross-border data controls, compatibility notes, divergence logs, and correction pathways.
180.4 GRF Interface Review. The Committee may review interfaces with The Global Risks Forum (GRF) to ensure that GCRI US evidence, methods, observability, ontology, technical baselines, correction signals, and technical support do not become GRF recognition, maturity standing, public-facing legitimacy, registry determinations, or claims-discipline determinations by GCRI US.
180.5 GRA Interface Review. The Committee may review interfaces with The Global Risks Alliance (GRA) to ensure that GCRI US technical evidence inputs, methods inputs, observability inputs, public-good baselines, correction signals, and public authority learning materials do not become finance-readiness, capital-readability, insurance-readiness, proof-pack approval, investment advice, underwriting approval, lending approval, public finance approval, rating, or regulated execution by GCRI US.
180.6 Nexus Standards, Protocol Authority, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, and Competence Cell Interface Review. The Committee may review interfaces with Nexus instruments and bodies to ensure mission alignment, interoperability, legal separateness, public-good stack compatibility, one-rail / two-stacks discipline, non-execution, validity-by-record, correctionability, public-safe language, technical boundary discipline, and no unauthorized protocol authority.
180.7 State Nexus Interface Review. The Committee may review state Nexus interfaces, including state-level public authority learning, observability methods, evidence support, technical literacy, Academy activity, competence cells, and controlled rooms. Review shall preserve state law compliance, public authority capacity classification, procurement neutrality, public finance boundaries, data / AI / cyber requirements, and safeguards.
180.8 Territorial Nexus Interface Review. The Committee may review territorial Nexus interfaces for lawful localization, public authority capacity classification, language and accessibility needs, infrastructure and disaster sensitivity, data handling, public-safe reporting, and non-execution.
180.9 Tribal and Indigenous Nexus Interface Review. The Committee may review Tribal and Indigenous Nexus interfaces for lawful and respectful structure, consent and non-consent, protected knowledge, Indigenous data safeguards, public-safe mapping, governance protocols, and no assumption of Indigenous governance authority.
180.10 Local, Metropolitan, Sectoral, Public Authority, University, Laboratory, Community, Provider, Sponsor, Host, and Partner Interface Review. The Committee may review local, metropolitan, sectoral, public authority, university, laboratory, community, provider, sponsor, host, and partner interfaces to ensure that interface terms, roles, data flows, records, public references, conflicts, access rights, technical dependencies, and closeout remain lawful and bounded.
180.11 North America Cross-Border Interface Review. The Committee may review North America cross-border interfaces involving Canada, Mexico, the Caribbean, Arctic, Great Lakes, Pacific, Atlantic, Gulf, border regions, Indigenous cross-border contexts, and regional systems. Review shall address conflict of law, data transfers, public authority status, export controls, sanctions, privacy, cyber, public-safe language, local law respect, and legal separateness.
180.12 Interoperability Standards Review. The Committee may review interoperability standards, profiles, schemas, data dictionaries, APIs, SDKs, proof receipts, role keys, technical profiles, smart licenses, public-good software, controlled vocabulary, and observability interfaces. Review shall not create standards authority, certification, procurement mandate, or Nexus-compatible status unless separately and lawfully authorized by competent authority.
180.13 Localization Without Fragmentation Review. The Committee shall support localization without fragmentation. State, territorial, Tribal-interface, local, sectoral, North America, or public authority localization shall not weaken public-benefit purpose, non-execution, role separation, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, records discipline, validity-by-record, or correctionability.
180.14 Cross-Entity Routing, Mismatch Detection, Reconciliation, and Cure Review. The Committee may review routing across GCRI US, GCRI Canada, GRF, GRA, Nexus Standards, Nexus Network, consortiums, national companies, Project SPVs, providers, sponsors, public authorities, universities, laboratories, and communities. Where role mismatch, record mismatch, terminology mismatch, authority mismatch, data mismatch, or public claim mismatch occurs, the Committee may recommend reconciliation, correction, supersession, routing change, access restriction, or escalation.
180.15 Federation KPI and Corrective Action Review. The Committee may review federation indicators, including interface integrity, record completeness, correction timeliness, boundary incidents, public authority clarification needs, data / AI / cyber incidents, safeguards incidents, compatibility notes, divergence logs, and continuity status. Corrective action may include training, charter revision, role clarification, workflow redesign, access changes, public-safe correction, or Board review.
180.16 Emergency Governance Mode Review. The Committee may review emergency governance mode for events involving cyber compromise, data breach, AI incident, public authority confusion, public-safe publication defect, sponsor or provider capture risk, protected knowledge exposure, legal deadline, regulatory-perimeter risk, repository compromise, controlled technology issue, or continuity disruption. Emergency mode shall be time-limited, recorded, reviewable, and incapable of authorizing prohibited functions.
180.17 Continuity of Operations, RTO / RPO, Successor Administrator, Data Portability, Exit Assistance, Suspension, Wind-Down, and Orderly Transfer Review. The Committee may review continuity of operations, recovery time objectives, recovery point objectives, successor administrator arrangements, repository continuity, register continuity, data portability, exit assistance, controlled-room continuity, suspension procedures, wind-down procedures, orderly transfer, archive, and public-good asset preservation.
180.18 Federation, Interoperability, Emergency Mode, and Continuity Records. The Committee shall maintain records of federation reviews, interface reviews, interoperability reviews, localization reviews, routing reviews, mismatch detection, reconciliation, corrective actions, federation KPIs, emergency mode reviews, continuity reviews, wind-down reviews, transfer records, compatibility notes, divergence logs, and closeout.
Section 181. Leadership Council
181.1 Leadership Council Purpose. The Corporation may establish a Leadership Council to provide high-level advisory input, strategic feedback, ecosystem perspective, public-good coordination insight, technical and institutional judgment, program feedback, public authority learning feedback, and Nexus interface awareness. The Leadership Council shall strengthen the Corporation’s ability to understand public-benefit needs without transferring governance control to non-directors.
181.2 Leadership Council as Advisory and Coordination Body Unless Otherwise Delegated. The Leadership Council shall be advisory and coordinative unless expressly delegated a lawful, limited, recorded function. Advisory status means the Council may comment, recommend, convene, review, and provide feedback but may not govern, bind, approve, certify, recognize, finance, procure, command, or execute.
181.3 Composition. The Leadership Council may include directors, officers, advisors, fellows, public-interest leaders, scientific and technical experts, community representatives, Tribal or Indigenous interface participants where lawfully and respectfully structured, public authority learners, academic leaders, civil society leaders, open-source leaders, safeguards experts, and other persons appointed under the Council charter.
Composition shall be reviewed for independence, conflicts, public-interest perspective, geographic and disciplinary diversity, state and territorial awareness, North America awareness, safeguards competence, and capture risk.
181.4 Eligibility. Council eligibility may require integrity, expertise, public-benefit alignment, confidentiality capacity, conflict disclosure, compliance with participation terms, public-safe claim discipline, and willingness to respect non-execution, role separation, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, and correctionability.
181.5 Appointment. Council members shall be appointed by the Board, the Chair, the President, an authorized officer, or another competent authority as stated in the Council charter. Appointment shall be recorded and shall identify term, capacity, rights, limitations, access, confidentiality, conflict obligations, and public statement limits.
181.6 Term. Council members may serve fixed, renewable, project-based, or advisory terms as stated in the charter. Term renewal shall consider participation, independence, conflicts, contribution, public-benefit alignment, and capture risk.
181.7 Chair or Co-Chairs. The Leadership Council may have a chair or co-chairs. Council chairs shall manage agenda, participation, meeting discipline, conflicts, public authority limitations, finance and certification boundaries, records, and reporting. Council chairs shall not acquire authority to bind the Corporation by title alone.
181.8 Role in Strategy Feedback. The Leadership Council may provide feedback on strategy, priorities, public-benefit needs, systemic risk themes, emerging technology issues, public-good software priorities, public authority learning needs, Academy needs, safeguards concerns, and Nexus interface opportunities. Strategy feedback shall be advisory and shall not substitute for Board approval.
181.9 Role in Public-Good Ecosystem Coordination. The Council may support public-good ecosystem coordination by identifying gaps, opportunities, learning needs, stakeholder needs, research needs, technical literacy needs, and public-safe communication issues. Coordination shall not create agency, partnership, joint venture, procurement channel, finance channel, or execution channel.
181.10 Role in United States All-States-and-Territories Awareness. The Council may provide awareness of state, territorial, District of Columbia, Tribal-interface, local, metropolitan, rural, coastal, island, border, Arctic, Great Lakes, Gulf, Pacific, Atlantic, and regional contexts. Such awareness shall assist lawful localization without fragmenting the Bylaw or weakening core controls.
181.11 Role in North America Anchor Awareness. The Council may provide feedback on North America anchor issues, including cross-border evidence architecture, public authority learning, critical infrastructure, climate, cyber, health, energy, water, food, biodiversity, telecom, AI-RAN, DePIN, supply chain, ports, borders, Arctic, Great Lakes, and regional systemic risk.
181.12 Role in Nexus Interface Awareness. The Council may provide feedback on 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, public authorities, universities, laboratories, communities, and media.
181.13 Role in Program and Public Authority Learning Feedback. The Council may provide feedback on programs, activation dockets, Academy materials, public authority learning sessions, controlled rooms, public-safe reports, stakeholder engagement, and capability formation. Feedback shall not become public authority approval, finance-readiness, certification, recognition, procurement approval, or implementation mandate.
181.14 No Fiduciary Authority Unless Council Member Is Also a Director Acting as Director. A Leadership Council member shall not have fiduciary authority merely by Council appointment. A person who is also a director acts as a director only when acting in that capacity under Board procedures, not when participating solely as a Council member.
181.15 No Governance Control. The Leadership Council shall not control the Board, officers, committees, budgets, research conclusions, publications, public-good software releases, technical baselines, public authority interfaces, GRF inputs, GRA inputs, Nexus interfaces, provider relationships, sponsor relationships, or enterprise-stack actors.
181.16 No Public Authority, Finance, Certification, Procurement, Recognition, or Execution Authority. The Leadership Council shall not issue public warnings, exercise emergency command, approve public finance, determine finance-readiness, provide investment advice, approve insurance, approve lending, issue ratings, certify, accredit, recognize, approve procurement, select providers, bind public authorities, or execute enterprise activity.
181.17 Leadership Council Records. The Corporation shall maintain Leadership Council records, including charter, appointments, terms, attendance, agendas, materials, conflicts, recusals, public authority classifications, confidentiality acknowledgments, recommendations, minority views, reports, access records, and closeout.
Section 182. Helix Councils
182.1 Helix Council Purpose. The Corporation may establish Helix Councils as cross-sector advisory structures to organize insight from multiple domains while preserving public-benefit purpose, non-execution, role separation, competition discipline, public authority boundary discipline, finance-boundary discipline, provider neutrality, sponsor non-control, safeguards, and records integrity. Helix Councils shall enable structured learning and translation across sectors, not governance capture.
182.2 Helix Councils as Cross-Sector Advisory Structures. Helix Councils may be organized by sector, discipline, technology family, geography, state, territory, public authority context, community context, or Nexus interface. They shall provide advice, learning, feedback, and coordination insight. They shall not approve Board matters, bind the Corporation, determine recognition, determine finance-readiness, certify, accredit, approve procurement, or direct execution.
182.3 Public Authority Helix. A Public Authority Helix may include federal, state, territorial, District of Columbia, Tribal, Indigenous, local, metropolitan, utility, port, public health, emergency management, public safety, public works, infrastructure, telecom, energy, water, food, cyber, and other public authority participants. It shall operate under capacity classification and limitation language.
182.4 Academic and Research Helix. An Academic and Research Helix may include universities, laboratories, research networks, researchers, students, fellows, and scientific advisors. It may advise on research integrity, methods, evidence quality, reproducibility, publication integrity, and public-good R&D, while preserving academic independence, conflict disclosure, data controls, and sponsor transparency.
182.5 Industry, Operator, and Provider Helix. An Industry, Operator, and Provider Helix may include operators, providers, vendors, technical companies, cloud providers, AI providers, infrastructure actors, systems integrators, and enterprise actors under enhanced controls. It shall be designed to receive technical and operational learning without creating provider preference, procurement steering, sponsor control, finance-readiness, certification, recognition, or enterprise execution by the Corporation.
182.6 Community, Tribal / Indigenous, Civil Society, and Public-Interest Helix. A Community, Tribal / Indigenous, Civil Society, and Public-Interest Helix may include community leaders, Tribal or Indigenous interface participants where lawfully and respectfully structured, civil society, public-interest organizations, accessibility advocates, environmental justice representatives, youth representatives, local knowledge holders, and safeguards experts. Participation shall not be treated as consent, endorsement, knowledge transfer, or waiver unless expressly and lawfully recorded.
182.7 Media, Communications, and Public Literacy Helix. A Media, Communications, and Public Literacy Helix may advise on public literacy, public-safe communication, misinformation risk, public explanation, accessibility, translation, media education, and non-reliance language. It shall not control editorial independence of media participants or authorize participants to speak for the Corporation without separate authority.
182.8 Capital-Reader and Finance-Literacy Helix Subject to GRA Boundary. A Capital-Reader and Finance-Literacy Helix may include capital readers, insurers, lenders, banks, underwriters, public finance readers, development finance readers, philanthropic capital readers, and finance-literacy participants where appropriate. It shall operate subject to GRA boundaries and shall not provide investment advice, securities solicitation, brokerage, lending approval, insurance approval, underwriting, rating, finance-readiness determination, public finance approval, or capital execution by GCRI US.
182.9 Technology and Open-Source Helix. A Technology and Open-Source Helix may include developers, maintainers, open-source participants, public-good software contributors, cybersecurity experts, AI governance experts, data engineers, infrastructure technologists, observability experts, and technical architects. It shall preserve repository access controls, contributor terms, secure development, IP discipline, licensing discipline, public-safe claims, and no technical permission as governance authority.
182.10 Youth, Workforce, Academy, and Fellows Helix Where Approved. A Youth, Workforce, Academy, and Fellows Helix may advise on training, workforce formation, fellowships, Academy programs, technical literacy, accessibility, youth safeguards, and learning pathways. It shall not create professional licensure, regulated credentials, certification, employment entitlement, or public authority qualification by participation.
182.11 Helix Council Charter. Each Helix Council shall have a charter or terms of reference identifying purpose, scope, composition, appointment, chair, term, reporting line, meeting rules, access class, confidentiality, conflicts, public authority classifications, finance boundary controls, competition controls, safeguards controls, output status, records custodian, review cycle, and sunset.
182.12 Helix Council Participation Terms. Participants shall accept participation terms covering role limits, confidentiality, conflicts, public statements, data / AI / cyber rules, competition rules, safeguards, public authority boundaries, finance boundaries, provider neutrality, sponsor non-control, and correction obligations.
182.13 Competition and Antitrust Controls. Helix Councils involving competitors, providers, vendors, operators, capital actors, public authorities, or industry participants shall operate under competition and antitrust controls, including agenda review, do-not-discuss lists, clean-room rules where appropriate, aggregation, de-identification, delayed publication, independent administration, and stop-meeting authority.
182.14 Public Authority Boundary Controls. Public authority participation in Helix Councils shall be capacity-classified and shall not imply public authority delegation, endorsement, official adoption, funding approval, procurement approval, regulatory approval, public finance approval, emergency command, public warning, sovereign obligation, or public-private partnership.
182.15 Finance and Regulated-Perimeter Controls. Helix Councils shall avoid securities solicitation, investment advice, brokerage, finder activity, lending, insurance placement, underwriting, rating, public finance approval, procurement steering, certification, professional advice, and regulated execution. Finance-adjacent discussions shall be framed as literacy, translation, evidence requirements, and boundary-aware learning only.
182.16 Provider and Sponsor Non-Control Controls. Helix Councils shall not permit providers, sponsors, donors, funders, hosts, or enterprise actors to control agendas, outputs, evidence conclusions, research priorities, publications, public authority access, technical baselines, software releases, or public-safe statements.
182.17 Safeguards Controls. Helix Councils shall preserve safeguards, including community protection, Tribal and Indigenous protocol respect, protected knowledge, civil rights, accessibility, grievance pathways, non-retaliation, and public-safe communication.
182.18 No Helix Council Authority to Bind GCRI US. No Helix Council may bind the Corporation, make governance decisions, approve budgets, approve policies, authorize public statements, issue certifications, determine recognition, determine finance-readiness, select providers, or represent public authority adoption unless expressly and lawfully authorized by competent record.
182.19 Helix Council Records. The Corporation shall maintain Helix Council records, including charters, participation terms, appointments, attendance, agendas, materials, conflicts, recusals, public authority capacity records, competition controls, recommendations, reports, limitation language, corrections, and closeout.
Section 183. Scientific and Technical Advisory Council
183.1 Scientific and Technical Advisory Council Purpose. The Corporation may establish a Scientific and Technical Advisory Council to provide scientific, technical, engineering, research, data, AI, cyber, observability, methods, software, systems, and mission-critical technology advice. The Council shall strengthen technical rigor and public-benefit quality without creating certification, procurement approval, finance-readiness, recognition, public authority approval, provider preference, or execution authority.
183.2 Evidence Methods Advice. The Council may advise on evidence methods, source lineage, provenance, confidence, uncertainty, validation, corroboration, contested evidence, failed signal handling, evidence packs, public-safe evidence presentation, and correction triggers.
183.3 Research Methods Advice. The Council may advise on research methods, reproducibility, replication, peer review, experimental design, observational methods, simulation design, benchmark design, measurement integrity, bias detection, limitation language, and public-good research translation.
183.4 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 Chain, Advanced Manufacturing, Semiconductors, and Other Exponential Technology Advice. The Council may advise on technologies and systems relevant to systemic risk and resilience, including 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 systems, telecom, supply chains, advanced manufacturing, semiconductors, and other exponential technologies. Advice shall be framed with assumptions, limitations, uncertainty, applicable controls, and correction pathways.
183.5 Observability and Truth Engine Methods Advice. The Council may advise on observability methods, Nexus Observatory methods, node methods, hub methods, cluster methods, hotspot methods, regional cluster methods, national dense Nexus core methods, Truth Engine methods, signal validation, sensor fusion, spoof detection, degraded-mode awareness, confidence scoring, dashboard interpretation, and public-safe reporting.
183.6 Public-Good Software and Technical Baseline Advice. The Council may advise on public-good software, open technical baselines, reference architectures, APIs, SDKs, schemas, data dictionaries, test harnesses, benchmark libraries, secure releases, public-good technical memory, interoperability, and anti-enclosure.
183.7 Verifiable Compute and Model Governance Advice. The Council may advise on verifiable compute, verifiable intelligence, model governance, model registers, inference records, compute workload records, secure enclaves, confidential computing, sovereign compute, proof receipts, evaluation harnesses, AI output review, and human oversight.
183.8 Secure Release and Repository Advice. The Council may advise on repository governance, secure development, dependency management, SBOMs, artifact signing, provenance, vulnerability disclosure, rollback, release controls, open-source contribution, and controlled repositories.
183.9 Technical Challenge Review. The Council may advise on technical challenges, unresolved methods questions, contested evidence, model limitations, benchmark failures, signal failures, system vulnerabilities, interoperability problems, public-good software risks, and research gaps.
183.10 No Certification or Technical Approval by Advisory Advice. Advice from the Scientific and Technical Advisory Council shall not constitute certification, accreditation, standards conformance approval, safety approval, legal compliance approval, procurement approval, professional engineering opinion, technical approval for public authorities, or operational authorization unless separately and lawfully approved by competent authority.
183.11 No Public Authority, Procurement, Finance-Readiness, Recognition, or Provider Preference by Advisory Advice. Council advice shall not create public authority decision, public warning, emergency command, procurement approval, provider preference, recognition, maturity standing, Docket approval, Grid guarantee, finance-readiness, insurance-readiness, bankability, rating, investment suitability, or public finance approval.
183.12 Scientific and Technical Advisory Council Records. The Corporation shall maintain records of Council charter, membership, conflicts, independence review, materials reviewed, advice issued, limitations, minority views, technical challenge notes, corrections, public-safe language, and Board or officer actions.
Section 184. Public Authority Advisory Forum
184.1 Public Authority Advisory Forum Purpose. The Corporation may establish a Public Authority Advisory Forum to support public authority learning, evidence literacy, technical literacy, observability literacy, public-safe reporting literacy, scenario learning, simulation feedback, after-action feedback, public authority data boundary feedback, capacity classification, and government-interface discipline.
The Forum shall be advisory and educational. It shall not create public authority delegation, public warning authority, emergency command authority, procurement authority, funding authority, regulatory authority, public finance authority, sovereign obligation, public-private partnership, or official adoption by participation.
184.2 Federal Public Authority Participation. Federal public authority participants may participate in the Forum where lawful and consistent with applicable federal rules, ethics rules, public records constraints, procurement rules, grant rules, confidentiality requirements, and capacity classification. Participation shall be recorded with limitation language.
184.3 State Public Authority Participation. State public authority participants may participate where lawful and capacity-classified. State participation shall not imply state endorsement, procurement approval, funding commitment, regulatory approval, public warning, emergency command, public finance approval, or official adoption.
184.4 Territorial and District of Columbia Participation. Territorial and District of Columbia public authority participants may participate where lawful and capacity-classified. Participation records shall account for territorial context, local law, public authority restrictions, language needs, accessibility, and public-safe reporting.
184.5 Tribal and Indigenous Government Participation Where Lawfully and Respectfully Structured. Tribal and Indigenous government participation may occur only where lawfully and respectfully structured. The Forum shall respect sovereignty, governance protocols, consent and non-consent, protected knowledge, Indigenous data safeguards, cultural restrictions, attribution and non-attribution, and public-safe mapping.
184.6 Local, County, Municipal, Metropolitan, Utility, Port, Public Health, Emergency Management, Public Safety, Public Works, Telecom, Energy, Water, Food, Cyber, and Infrastructure Participation. Local and infrastructure-related public authority participants may participate to support technical literacy, evidence literacy, observability literacy, scenario learning, simulation feedback, and after-action learning. Such participation shall not give the Corporation operational control over infrastructure or emergency functions.
184.7 Capacity Classification. Each public authority participant shall be capacity-classified where material. Classification shall identify official capacity, observer, regulator-listening, public finance reader, emergency-management participant, public infrastructure operator, simulation participant, or other approved status.
184.8 Public Authority Learning Feedback. The Forum may receive feedback from public authority participants on learning needs, evidence usability, technical literacy, observability interpretation, public-safe reporting, scenario design, capability gaps, public authority data boundaries, and legal or operational constraints.
184.9 Scenario, Simulation, Tabletop, Exercise, and After-Action Feedback. The Forum may support feedback on scenarios, simulations, tabletops, exercises, and after-action learning. Such activities are learning tools only and shall not be represented as emergency command, official incident management, public warning, public authority decision, or operational resource direction by the Corporation.
184.10 Public Authority Data Boundary Feedback. The Forum may receive feedback on public authority data boundaries, including permitted use, confidentiality, publication, public records, cyber sensitivity, infrastructure sensitivity, privacy, retention, deletion, aggregation, and public-safe mapping.
184.11 No Public Authority Delegation. Forum participation shall not delegate public authority power to the Corporation, its Board, officers, committees, staff, advisors, participants, software, dashboards, AI systems, controlled rooms, or public-safe reports.
184.12 No Public Warning or Emergency Command. The Forum shall not issue public warnings, emergency commands, evacuation instructions, public health orders, dispatch instructions, incident management directions, public safety orders, or operational resource directions.
184.13 No Procurement, Funding, Regulation, Public Finance, Sovereign Obligation, PPP, or Official Adoption by Participation. Forum participation shall not create procurement approval, vendor selection, funding approval, regulatory approval, public finance approval, sovereign obligation, public-private partnership, official standard, official adoption, or public authority endorsement.
184.14 Public Authority Advisory Forum Records. The Corporation shall maintain Forum records, including charter, participation terms, capacity classifications, attendance, agendas, materials, public authority data boundary notes, feedback, limitation language, conflicts, confidentiality acknowledgments, corrections, and closeout.
Section 185. Community, Tribal / Indigenous, Safeguards, Accessibility, and Protected Knowledge Advisory Forum
185.1 Forum Purpose. The Corporation may establish a Community, Tribal / Indigenous, Safeguards, Accessibility, and Protected Knowledge Advisory Forum to support community safeguards, protected knowledge stewardship, public-safe mapping, accessibility, civil rights, local and territorial knowledge respect, Tribal and Indigenous protocol respect, grievance pathways, remedy pathways, and do-no-harm review.
The Forum shall be advisory and safeguards-supporting. It shall not convert participation into consent, endorsement, public authority approval, recognition, finance-readiness, certification, procurement approval, provider preference, sponsor control, or knowledge transfer unless expressly and lawfully recorded.
185.2 Community Participation. Community participants may provide feedback on public-safe communication, local impacts, vulnerability exposure, harm risk, access barriers, public authority interface concerns, trust concerns, remedy needs, and correction needs. Community participation shall be accessible, respectful, non-coercive, and protected from retaliation.
185.3 Tribal and Indigenous Participation. Tribal and Indigenous participation may occur where lawfully and respectfully structured and shall preserve sovereignty, governance protocols, consent and non-consent, Indigenous data safeguards, protected knowledge, cultural restrictions, attribution rules, non-attribution rules, withdrawal pathways, and public-safe mapping limits.
185.4 Local and Territorial Knowledge Participation. Local and territorial knowledge participation shall be treated as sensitive where appropriate. Such knowledge shall not be extracted, generalized, mapped, published, trained into models, or transferred into public-good software, datasets, dashboards, or technical baselines without lawful authority, safeguards review, and appropriate records.
185.5 Civil Rights and Accessibility Participation. Civil rights and accessibility participants may advise on discrimination risk, inclusion, access barriers, language access, disability access, accessibility of meetings and materials, public-safe summaries, grievance pathways, and equitable participation. Accessibility shall be embedded in governance and program design.
185.6 Public-Safe Mapping Advice. The Forum may advise on public-safe mapping, geospatial sensitivity, location masking, aggregation, delayed publication, non-public handling, protected knowledge removal, community review, ecological and cultural sensitivity, infrastructure sensitivity, and harm reduction.
185.7 Protected Knowledge Advice. The Forum may advise on protected knowledge classification, permitted use, restricted use, attribution, non-attribution, consent, non-consent, withdrawal, sealing, access limits, public-safe redaction, and correction.
185.8 Vulnerable and Remote Community Advice. The Forum may advise on risks to vulnerable and remote communities, including disaster exposure, climate exposure, infrastructure exposure, health exposure, marginalization, surveillance, stigmatization, extraction, language barriers, and access barriers.
185.9 Consent, Non-Consent, Withdrawal, Correction, and Remedy Pathway Advice. The Forum may advise on consent, non-consent, withdrawal, correction, and remedy pathways. Consent shall not be presumed from attendance, participation, silence, community affiliation, public authority participation, prior consultation, or publicly available information.
185.10 Grievance and Non-Retaliation Advice. The Forum may advise on grievance intake, confidential reporting, non-retaliation, protected participation, escalation, investigation, remedy, closeout, and public-safe correction.
185.11 Do-No-Harm Advice. The Forum may advise on do-no-harm review for programs, publications, datasets, dashboards, maps, AI outputs, digital twins, public authority learning sessions, controlled rooms, Academy materials, and technical releases.
185.12 No Extraction of Knowledge. The Forum shall not be used to extract knowledge, legitimacy, consent, public authority access, community trust, stories, imagery, cultural materials, ecological knowledge, local knowledge, territorial knowledge, Indigenous knowledge, or protected knowledge for sponsor, provider, donor, funder, host, public authority, media, academic, or institutional convenience.
185.13 No Advisory Participation as Consent Unless Specifically Recorded. Forum participation shall not constitute consent to use, publish, map, attribute, transfer, train, embed, commercialize, or otherwise process information unless consent is expressly, specifically, lawfully, and appropriately recorded.
185.14 No Public Authority, Finance, Certification, Procurement, Recognition, or Provider Meaning by Forum Participation. Participation in the Forum shall not create public authority approval, public warning, emergency command, finance-readiness, insurance-readiness, bankability, rating, certification, accreditation, procurement approval, provider preference, recognition, standing, maturity, Docket approval, Grid guarantee, or Nexus-compatible status.
185.15 Community, Tribal / Indigenous, Safeguards, Accessibility, and Protected Knowledge Advisory Forum Records. The Corporation shall maintain Forum records, including participation terms, community feedback, Tribal and Indigenous interface records, consent and non-consent records, protected knowledge records, public-safe mapping advice, accessibility advice, civil rights advice, grievances, remedies, non-retaliation records, do-no-harm notes, restrictions, corrections, and closeout.
Section 186. Peer Review Panels, Model Review Panels, Evidence Review Panels, and Red-Team Panels
186.1 Peer Review Panel Purpose. The Corporation may establish Peer Review Panels to review research outputs, evidence outputs, methods, publications, technical reports, public-good software, open technical baselines, datasets, dashboards, maps, Academy materials, public-safe summaries, and other materials requiring independent or structured expert review. Peer review shall support quality, accuracy, reproducibility, integrity, limitations, and correctionability.
186.2 Model Review Panel Purpose. The Corporation may establish Model Review Panels to review AI systems, models, model cards, system cards, benchmark cards, dataset cards, evaluation harnesses, inference records, agentic AI controls, retrieval systems, embeddings, fine-tuning, training restrictions, output review, human oversight, public-safe limitations, and AI incident risks.
186.3 Evidence Review Panel Purpose. The Corporation may establish Evidence Review Panels to review evidence quality, source lineage, provenance, confidence, uncertainty, corroboration, contradiction, contested evidence, stale evidence, failed signals, sensor data, AI-RAN signals, O-RAN signals, DePIN records, DLT records, geospatial evidence, Earth observation evidence, cyber evidence, digital twin assumptions, and public-safe evidence summaries.
186.4 Red-Team Panel Purpose. The Corporation may establish Red-Team Panels to identify weaknesses, misuse risks, adversarial risks, public-safe risks, cyber risks, AI risks, model risks, data risks, public authority confusion risks, finance overclaim risks, certification overclaim risks, procurement overclaim risks, provider-preference risks, sponsor-control risks, safeguards risks, and correction failures.
186.5 Panel Charter. Each panel shall have a charter, terms of reference, or review mandate identifying purpose, scope, materials, reviewers, independence requirements, conflicts, confidentiality, data / AI / cyber rules, public authority rules, safeguards rules, review criteria, output status, records custodian, timelines, limitations, and escalation path.
186.6 Reviewer Eligibility. Reviewer eligibility may require subject-matter expertise, independence, integrity, confidentiality capacity, conflict disclosure, data / AI / cyber eligibility, export-control eligibility where applicable, sanctions screening where applicable, public authority boundary understanding, safeguards competence, and willingness to follow review instructions.
186.7 Reviewer Independence. Panels shall apply independence review appropriate to the subject matter. Reviewers with sponsor, provider, donor, funder, host, public authority, research, publication, IP, employment, financial, data, AI, cyber, or personal conflicts may be restricted, recused, separated from materials, or excluded.
186.8 Reviewer Conflict Disclosure. Reviewers shall disclose conflicts before review and update disclosures if circumstances change. Conflicts and recusals shall be recorded. A reviewer shall not review, influence, or access materials from which the reviewer is recused.
186.9 Confidentiality Duties. Reviewers shall protect confidential, privileged, public authority, cyber-sensitive, infrastructure-sensitive, commercially sensitive, finance-sensitive, personal, health-sensitive, community-protected, Tribal / Indigenous, local / territorial, cultural, environmental, and protected knowledge materials.
186.10 Data / AI / Cyber / Privacy Duties. Reviewers shall follow data, AI, cyber, and privacy rules, including restrictions on downloading, copying, uploading to AI systems, model training, embeddings, external sharing, screenshots, side-channel storage, repository access, key handling, and deletion.
186.11 Public Authority Boundary Duties. Reviewers shall not represent panel access, public authority participation, public authority data, or review status as public authority approval, public warning, emergency command, funding approval, procurement approval, regulatory approval, public finance approval, sovereign obligation, official adoption, or government endorsement.
186.12 Safeguards Duties. Reviewers shall protect community safeguards, Tribal and Indigenous protocols, protected knowledge, civil rights, accessibility, vulnerable populations, public-safe mapping, non-retaliation, and do-no-harm requirements. Reviewers shall escalate safeguards concerns promptly.
186.13 Review Criteria. Panel review criteria may include accuracy, evidence quality, methods quality, provenance, reproducibility, uncertainty, bias, limitations, data governance, privacy, AI governance, cyber risk, public authority boundary, finance boundary, certification boundary, procurement neutrality, recognition boundary, safeguards, public-safe language, and correctionability.
186.14 Majority and Minority Views. Panels may record majority and minority views where material. Minority views shall not be suppressed where they identify credible evidence concerns, method defects, safety issues, public authority confusion, finance or certification overclaims, data / AI / cyber risks, safeguards concerns, or correction needs.
186.15 Review Records. Panel review records shall identify the panel, mandate, reviewers, conflicts, recusals, materials reviewed, review criteria, findings, limitations, majority views, minority views, recommendations, escalation items, public-safe language, and closeout.
186.16 No Panel Review as Certification, Rating, Public Authority Decision, Finance-Readiness Determination, Procurement Approval, Recognition, or Public Warning. No peer review, model review, evidence review, or red-team review shall be represented as certification, accreditation, rating, public authority decision, finance-readiness, insurance-readiness, bankability, investment suitability, procurement approval, recognition, standing, maturity, Docket approval, Grid guarantee, Nexus-compatible status, public warning, emergency command, or operational authorization unless separately and lawfully created by a competent authority.
186.17 Correction, Challenge, and Appeal Interface. Panel findings may support correction, challenge, appeal, supersession, withdrawal, retraction, takedown, additional review, Board review, officer action, safeguards review, data / AI / cyber review, public authority clarification, or counsel review. Challenge and appeal pathways shall be recorded and shall not be used to suppress good-faith disagreement or protected participation.
186.18 Review Panel Records. The Corporation shall maintain Peer Review Panel, Model Review Panel, Evidence Review Panel, and Red-Team Panel Records, including charters, reviewer appointments, eligibility records, independence records, conflicts, recusals, confidentiality acknowledgments, review materials, findings, minority views, recommendations, corrections, challenges, appeals, and closeout.
Section 187. Technical Working Groups, Drafting Groups, Standards-Support Groups, and Open-Source Maintainer Groups
187.1 Working Group Purpose. Technical Working Groups may be established to develop, review, refine, test, document, and maintain technical, evidentiary, research, software, data, AI, cyber, observability, ontology, standards-support, public-good software, open technical baseline, public authority learning, safeguards, and Nexus-interface work products within a defined and recorded scope. A Working Group shall function as a structured work-product body and not as a governing body unless a lawful and specific delegation is expressly recorded.
Each Working Group shall preserve the Corporation’s public-benefit character, non-execution boundary, GCRI / GRF / GRA role separation, public authority boundary, finance boundary, certification boundary, procurement-neutrality boundary, provider-neutrality boundary, sponsor non-control, data / AI / cyber discipline, protected knowledge safeguards, competition discipline, validity-by-record, and correctionability.
187.2 Drafting Group Purpose. Drafting Groups may be established to prepare drafts of policies, technical baselines, methods, schemas, controlled vocabulary entries, public-safe reports, software documentation, governance instruments, Academy materials, public authority learning materials, open technical specifications, data dictionaries, model cards, system cards, benchmark cards, dataset cards, templates, forms, registers, annexes, and public-safe explanatory materials.
Drafting Groups shall not adopt, approve, publish, certify, recognize, determine finance-readiness, approve procurement, bind the Corporation, or alter institutional meaning unless the competent authority separately approves the relevant instrument through the required records and adoption process.
187.3 Standards-Support Group Purpose. Standards-Support Groups may support the development, comparison, mapping, interpretation, implementation literacy, evidence requirements, technical baselines, interoperability profiles, conformance-support materials, and controlled vocabulary needed for standards-related work. Such groups may provide technical inputs to Nexus Standards or other competent standards bodies where lawfully and separately structured.
No Standards-Support Group shall be treated as Nexus Standards, a protocol authority, certification body, accreditation body, conformance approval body, public procurement body, or public authority body by reason of technical support, reference architecture, test harness, schema, software, benchmark, proof receipt, or advisory output.
187.4 Open-Source Maintainer Group Purpose. Open-Source Maintainer Groups may support secure, public-good, and controlled maintenance of open-source or public-good repositories, software tools, APIs, SDKs, schemas, dashboards, reference architectures, documentation, tests, gold vectors, negative tests, evaluation harnesses, and related technical assets. Maintainer authority shall be repository-specific, permission-specific, revocable, recorded, and subordinate to this Bylaw, applicable policies, IP terms, secure development rules, public-safe release rules, and delegated authority limits.
187.5 Charter Requirement. Each Technical Working Group, Drafting Group, Standards-Support Group, and Open-Source Maintainer Group shall have a charter, terms of reference, issue mandate, repository mandate, or recorded work order. The charter shall identify, at minimum:
purpose, scope, work product, timeline, chair or lead, reporting line, and records custodian;
membership, eligibility, access class, conflict rules, confidentiality class, and participation terms;
data / AI / cyber classification, protected knowledge treatment, public authority boundary, finance boundary, certification boundary, procurement boundary, and provider / sponsor boundary;
review, approval, publication, correction, supersession, retirement, and archive path; and
sunset date, review cycle, or closeout conditions.
187.6 Scope of Work. A group’s scope of work shall be specific, bounded, and recorded. Scope may include research drafting, method drafting, software maintenance, schema review, benchmark review, evidence review, technical baseline drafting, controlled vocabulary development, public authority learning materials, public-safe publication preparation, interoperability mapping, or safeguards review.
No group may expand its scope by practice, urgency, technical centrality, repository control, sponsor request, public authority interest, provider dependency, community demand, or operational convenience. Any material expansion shall require charter amendment, delegation review, and records update.
187.7 Deliverable Definition. Each group shall define its deliverables before or during formation. Deliverables may include draft text, technical specifications, reference code, software releases, issue reports, review memoranda, datasets, schemas, model cards, benchmark cards, public-safe summaries, controlled annexes, training modules, or recommendations.
Deliverables shall be classified as draft, advisory, internal, controlled, public-safe, approved, superseded, withdrawn, archived, deprecated, or other applicable status. A deliverable shall have no operative effect beyond its recorded status.
187.8 Contribution Terms. Participants shall be subject to contribution terms appropriate to their role and access class. Contribution terms may include confidentiality, IP assignment or license, contributor license agreement, moral rights treatment where applicable, data rights, AI-use restrictions, export-control obligations, sanctions compliance, cyber rules, public-safe claims rules, conflict disclosure, attribution rules, and correction obligations.
187.9 Repository Access Controls. Repository access shall be role-based, least-privilege, revocable, logged, and subject to secure development rules. Access may be separated by public repository, private repository, controlled repository, no-download repository, archival repository, evidence repository, model repository, software repository, schema repository, and publication repository.
Repository permission shall not create governance authority, publication authority, certification authority, public authority status, finance-readiness authority, procurement authority, or authority to bind the Corporation.
187.10 IP and Licensing Controls. Each group shall follow IP and licensing controls, including chain-of-title review, contributor license agreement review, assignment review, open-license review, restricted-license review, third-party dependency review, patent and defensive publication review, standards-essential rights review, anti-enclosure review, and commercial-use boundary review.
No participant may contribute, copy, license, relicense, publish, release, or transfer IP or technical assets in a manner inconsistent with the Corporation’s public-benefit purpose, public-good software discipline, open technical baseline discipline, contractual obligations, protected knowledge safeguards, or Board-approved IP policy.
187.11 Secure Development Controls. Technical groups shall follow secure development practices, including code review, dependency review, SBOM preparation where appropriate, vulnerability scanning, secret and credential controls, artifact signing where used, provenance controls, branch protection, release approvals, rollback planning, security issue intake, vulnerability disclosure handling, and repository audit logging.
187.12 Data / AI / Cyber Controls. Groups handling data, AI systems, models, embeddings, retrieval systems, inference outputs, compute records, cyber tools, infrastructure-sensitive materials, public authority data, health-sensitive data, community-protected data, Tribal / Indigenous data, or protected knowledge shall comply with applicable data / AI / cyber controls. Such controls may include access restriction, no-download handling, no unapproved AI upload, no model training, no embedding, no external sharing, redaction, aggregation, encryption, logging, retention, deletion, and incident escalation.
187.13 Competition and Antitrust Controls. Groups involving providers, vendors, operators, competitors, capital actors, sponsors, public authorities, or market participants shall operate under competition and antitrust controls. Prohibited topics include prices, margins, costs, wages, bids, customers, suppliers, capacity, market allocation, exclusion, boycott, procurement steering, competitively sensitive forward-looking plans, or collusive strategies. Meetings shall be agenda-controlled, minute-controlled, and subject to stop-meeting authority.
187.14 Public Authority Boundary Controls. Groups involving public authorities shall use capacity classification, public authority reference controls, data contribution controls, official-capacity records where applicable, and limitation language. No group may create or imply public authority delegation, public warning, emergency command, regulatory approval, funding approval, procurement approval, public finance approval, sovereign obligation, public-private partnership, or official adoption by participation.
187.15 Provider and Sponsor Non-Control Controls. Providers, sponsors, donors, funders, hosts, vendors, national companies, Project SPVs, investors, insurers, lenders, underwriters, banks, public finance actors, and enterprise actors shall not control a group’s agenda, outputs, evidence conclusions, method choices, technical baseline contents, publication timing, repository permissions, public authority access, public-safe language, recognition inputs, finance-readiness inputs, certification claims, or procurement signals.
187.16 No Working Group Authority to Adopt Standards, Certify, Approve Procurement, Recognize, Determine Finance-Readiness, or Bind GCRI US Unless Expressly Delegated Within Lawful Scope. No Technical Working Group, Drafting Group, Standards-Support Group, or Open-Source Maintainer Group shall adopt standards, issue certifications, accredit, approve procurement, recognize standing, determine maturity, approve Docket status, guarantee Grid status, determine Nexus-compatible status, determine finance-readiness, determine insurance-readiness, issue ratings, approve public finance, provide investment advice, bind the Corporation, speak for the Corporation, or exercise public authority unless a competent authority has expressly, lawfully, specifically, and narrowly delegated such function and such delegation is not prohibited by this Bylaw.
187.17 Working Group Records. The Corporation shall maintain Working Group Records, including charters, mandates, members, access permissions, contribution terms, conflicts, recusals, meeting records, deliverables, review comments, repository actions, IP and licensing records, secure development records, data / AI / cyber records, competition controls, public authority capacity records, safeguards records, recommendations, corrections, supersessions, withdrawals, retirements, archives, and closeout records.
Section 188. Nexus Competence Cells
188.1 Nexus Competence Cell Purpose. Nexus Competence Cells may be established as bounded learning, capability, methods-transfer, technical-literacy, safeguards-literacy, public authority learning, and public-good implementation-support structures within the Corporation’s non-executing public-benefit role. Competence Cells shall help participants understand evidence, methods, observability, ontology, data governance, AI governance, cybersecurity, public-good software, technical baselines, public authority learning, and safeguards without creating professional licensure, regulated credentials, certification, procurement status, provider status, recognition, finance-readiness, or enterprise execution.
188.2 Evidence Competence Cell. An Evidence Competence Cell may support evidence literacy, evidence intake, evidence classification, source lineage, provenance, confidence, uncertainty, contested evidence handling, evidence pack preparation, evidence challenge, evidence correction, and public-safe evidence presentation. It shall not determine recognition, maturity, finance-readiness, certification, procurement approval, public authority decision, rating, public warning, or emergency command.
188.3 Methods Competence Cell. A Methods Competence Cell may support learning and capability in validation methods, corroboration methods, scenario methods, simulation methods, AI output review methods, AI-RAN and O-RAN signal interpretation methods, DePIN and DLT validation methods, sensor fusion, digital twin assumption review, geospatial methods, Earth observation methods, cyber evidence methods, verifiable compute methods, and correction methods.
188.4 Observability Competence Cell. An Observability Competence Cell may support learning regarding Nexus Observatory methods, observatory nodes, hubs, clusters, hotspots, regional clusters, national dense Nexus cores, sensor networks, edge systems, AI-RAN signals, DePIN signals, cyber telemetry, digital twins, Earth observation, dashboards, degraded-mode awareness, resilience indicators, and public-safe observability outputs. It shall not issue public warnings or emergency commands.
188.5 Ontology Competence Cell. An Ontology Competence Cell may support controlled vocabulary, taxonomies, schemas, data dictionaries, risk categories, maturity concepts, evidence classifications, technology families, public authority capacity semantics, finance boundary semantics, certification boundary semantics, Nexus-compatible claim semantics, and semantic interoperability across the Nexus public-good stack and enterprise stack.
188.6 Data Governance Competence Cell. A Data Governance Competence Cell may support lawful, ethical, secure, and public-safe data practices, including data classification, data minimization, provenance, permitted use, retention, deletion, redaction, aggregation, public authority data handling, health-sensitive data handling, infrastructure-sensitive data handling, community-protected data handling, cross-border transfer review, and protected knowledge controls.
188.7 AI Governance Competence Cell. An AI Governance Competence Cell may support learning regarding approved AI-use rules, model registers, inference records, dataset cards, model cards, system cards, benchmark cards, evaluation harnesses, agentic AI controls, human review, AI output limitations, AI incident escalation, prohibited AI uses, and no-AI-as-authority discipline.
188.8 Cybersecurity Competence Cell. A Cybersecurity Competence Cell may support cybersecurity literacy, identity and access management, logging, vulnerability management, secure development, incident response, business continuity, disaster recovery, repository security, SBOMs, artifact signing, secret management, vendor security, cyber-sensitive data handling, and cyber incident escalation.
188.9 Public-Good Software and Technical Baseline Competence Cell. A Public-Good Software and Technical Baseline Competence Cell may support capability in public-good software stewardship, open technical baselines, reference architectures, APIs, SDKs, schemas, test harnesses, benchmark libraries, secure release, licensing, anti-enclosure, repository discipline, technical asset registers, deprecation, correction, and archive.
188.10 Public Authority Learning Competence Cell. A Public Authority Learning Competence Cell may support public authority evidence literacy, technical literacy, observability literacy, public-safe reporting literacy, scenario learning, tabletop learning, simulation learning, after-action learning, capacity classification, and public authority reference discipline. It shall not create public authority delegation, public warning, emergency command, procurement approval, funding approval, regulatory approval, public finance approval, sovereign obligation, or official adoption.
188.11 Community Safeguards and Protected Knowledge Competence Cell. A Community Safeguards and Protected Knowledge Competence Cell may support safeguards literacy, civil rights awareness, accessibility, public-safe mapping, Indigenous data safeguards, Tribal and Indigenous protocol respect, protected knowledge handling, consent and non-consent pathways, grievance pathways, remedy pathways, protected participation, non-retaliation, and do-no-harm review.
188.12 State, Territorial, Tribal, Local, Sectoral, and North America Competence Cell Localization. Competence Cells may be localized for state, territorial, District of Columbia, Tribal-interface, Indigenous-interface, local, metropolitan, rural, coastal, island, border, Arctic, Great Lakes, Gulf, Pacific, Atlantic, sectoral, host-site, and North America contexts. Localization shall not fragment the Corporation’s mission lock or weaken core controls.
188.13 Train-the-Trainer Function. Competence Cells may support train-the-trainer functions for directors, officers, staff, fellows, advisors, public authority learners, technical contributors, community participants, host participants, and partner participants. Train-the-trainer records shall document learning, scope, materials, date, instructor, limitations, and whether participation affects access eligibility.
188.14 Public-Safe Playbooks. Competence Cells may develop or support public-safe playbooks, checklists, templates, learning modules, scenario guides, intake forms, review forms, controlled vocabulary guides, and public authority learning aids. Such playbooks shall be non-operative unless adopted by competent authority and shall include limitation language where public reliance, public authority reliance, finance reliance, procurement reliance, certification reliance, or safety reliance may arise.
188.15 Controlled Annexes. Competence Cells may support controlled annexes for sensitive methods, public authority data, cyber-sensitive materials, infrastructure-sensitive materials, protected knowledge, export-controlled materials, sanctions-sensitive materials, model-sensitive materials, repository security materials, or confidential sponsor / provider / host materials. Controlled annexes shall have access class, custodian, retention, publication restriction, correction path, and closeout rules.
188.16 No Competence Cell as Certification Body by Default. No Competence Cell shall be treated as a certification body, accreditation body, licensing body, credentialing body, standards authority, procurement authority, provider approval body, recognition body, finance-readiness body, public authority body, or professional regulator by default.
188.17 Competence Records Not Professional Licenses or Regulated Credentials. Competence records, training records, attendance records, module completions, fellowship records, Academy records, participation records, or learning records shall not constitute professional licenses, regulated credentials, certification, accreditation, procurement qualification, provider qualification, public authority qualification, finance-readiness, insurance-readiness, or recognition unless separately and lawfully created by competent authority and expressly recorded.
188.18 Nexus Competence Cell Records. The Corporation shall maintain Nexus Competence Cell Records, including charters, localization records, participants, instructors, materials, attendance, learning records, controlled annexes, public-safe playbooks, access eligibility records, limitations, conflicts, public authority capacity records, safeguards records, corrections, supersessions, retirements, archives, and closeout.
Section 189. Committee Meetings, Quorum, Voting, Recommendations, Minority Views, and Written Actions
189.1 Committee Meeting Rules. Each committee, council, forum, working group, panel, competence cell, and advisory body shall conduct meetings under its charter, this Bylaw, applicable policies, delegation limits, confidentiality rules, competition rules, public authority boundary rules, finance boundary rules, certification boundary rules, data / AI / cyber rules, safeguards rules, and records requirements.
189.2 Regular Meetings. Regular meetings may be held on a schedule set by charter, Board resolution, committee resolution, chair instruction, or delegated officer instruction. Regular meetings shall have agendas, materials, attendance records, and minutes or notes appropriate to the body’s function and records class.
189.3 Special Meetings. Special meetings may be called for urgent, time-sensitive, technical, legal, compliance, public authority, finance-boundary, certification-boundary, data / AI / cyber, safeguards, publication, repository, correction, or governance matters. Special meeting records shall identify the reason for calling the meeting and any expedited notice used.
189.4 Emergency Meetings. Emergency meetings may be convened where delay may create material legal, fiduciary, cyber, data, AI, public authority, finance, certification, procurement, public warning, sponsor-control, provider-control, protected knowledge, civil rights, accessibility, public-safe publication, repository, or continuity risk. Emergency meetings shall be time-limited, recorded, subject to post-meeting review, and incapable of authorizing prohibited functions.
189.5 Virtual and Hybrid Meetings. Meetings may be held virtually or in hybrid format where lawful and appropriate. Virtual and hybrid meetings shall use secure systems appropriate to confidentiality class, identity verification, access logging, recording restrictions, data protection, AI-use restrictions, and controlled-room requirements.
189.6 Notice. Notice shall be given as required by charter, policy, delegation, or applicable law. Notice may include date, time, location or connection method, agenda, purpose, materials, confidentiality class, access restrictions, conflict reminders, public authority capacity reminders, competition-law reminders, and AI-use restrictions.
189.7 Agenda. Agendas shall identify topics, presenters, expected action, decision or advisory status, required recusals, public authority issues, finance-boundary issues, certification-boundary issues, procurement-neutrality issues, data / AI / cyber issues, safeguards issues, competition-sensitive items, and records expectations.
189.8 Materials. Materials shall be circulated securely and with appropriate classification. Confidential, privileged, public authority, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, personal, health-sensitive, community-protected, Tribal / Indigenous, local / territorial, cultural, environmental, or protected knowledge materials shall be marked, access-controlled, and handled under applicable restrictions.
189.9 Quorum. Quorum shall be determined by charter, Board resolution, delegation, or policy. Advisory bodies may operate by attendance without quorum where the charter permits, but no delegated decision may be made without the required quorum and authority. Recusal-related quorum loss shall be recorded and escalated where necessary.
189.10 Voting Where Committee Has Decision Authority. A committee may vote only where it has lawful and recorded decision authority. Voting shall follow the charter, delegation, quorum, recusal, conflict, and records requirements. No vote may approve a matter outside scope or within Board reserved matters unless expressly and lawfully authorized.
189.11 Recommendation Approval. Where a body has advisory or recommendation authority, recommendations shall be approved by the process stated in the charter. Recommendations shall identify basis, evidence, limitations, conflicts, minority views where material, and boundary notes.
189.12 Advisory Consensus. Advisory bodies may use consensus, rough consensus, recorded sense of the group, majority recommendation, minority report, or chair summary as permitted by charter. Consensus shall not be represented as binding approval unless separately authorized.
189.13 Minority Views. Minority views shall be recorded where material to evidence quality, method validity, public authority boundary, finance boundary, certification boundary, procurement neutrality, safeguards, data / AI / cyber risk, legal compliance, public-safe publication, or institutional integrity.
189.14 Abstentions. Abstentions shall be recorded where a vote occurs. Abstention shall not cure a required recusal, conflict violation, quorum defect, or authority defect.
189.15 Recusals. Recusals shall be recorded and shall identify the participant, matter, conflict basis where appropriate, effect on access, effect on deliberation, effect on vote, and any mitigation. A recused participant shall not influence the matter from which the participant is recused.
189.16 Written Actions Where Permitted. Written actions may be used where permitted by law, charter, Board resolution, delegation, and policy. Written actions shall identify the decision or recommendation, authority, materials reviewed, participants, approvals, abstentions, recusals, conflicts, effective date, and records custodian.
189.17 Electronic Participation. Electronic participation shall require identity verification, secure access, confidentiality compliance, AI-use compliance, cyber controls, and records integrity. Participants shall not use unauthorized recording, transcription, screenshots, AI summarization, side-channel storage, or external sharing.
189.18 Identity Verification and Secure Systems. The Corporation may require identity verification, multi-factor authentication, approved platforms, role-based access, waiting rooms, locked meetings, watermarking, no-download restrictions, recording controls, and attendance logs for meetings.
189.19 Committee Meeting Records. Meeting records shall include notice, agenda, attendance, quorum where applicable, materials, conflicts, recusals, votes, recommendations, minority views, action items, escalations, public authority capacity notes, competition controls, confidentiality class, corrections, and closeout.
Section 190. Confidentiality, Privilege, Data Access, Public Authority Materials, Protected Knowledge, and Controlled-Room Rules for Committees and Advisory Bodies
190.1 Confidentiality Requirement. Each committee, council, forum, working group, panel, competence cell, and advisory body shall protect confidential materials and shall require participants to comply with confidentiality obligations appropriate to their role and access class. Confidentiality obligations may arise under law, contract, policy, participation terms, controlled-room terms, public authority restrictions, research ethics, privacy law, cyber controls, protected knowledge protocols, or Board designation.
190.2 Attorney-Client Privilege and Work Product Protection. Privileged materials and attorney work product shall be handled only through approved channels. The presence of non-lawyers, advisors, public authority participants, providers, sponsors, or external experts shall be managed to avoid unnecessary waiver. Privilege status shall be marked and preserved where applicable.
190.3 Public Authority Confidentiality. Public authority materials may be subject to statutory, regulatory, contractual, public records, security, emergency management, procurement, grant, ethics, investigative, or confidentiality constraints. Public authority materials shall not be published, quoted, summarized, mapped, transferred, trained into AI systems, or disclosed unless permitted by law and record.
190.4 Cyber-Sensitive and Infrastructure-Sensitive Materials. Cyber-sensitive and infrastructure-sensitive materials shall be access-controlled, marked, logged, and handled under heightened security. Such materials may include vulnerabilities, incident information, network architecture, critical infrastructure data, operational dependencies, facility data, security procedures, cyber threat intelligence, and system diagrams.
190.5 Finance-Sensitive and Commercially Sensitive Materials. Finance-sensitive and commercially sensitive materials shall be handled in a manner that preserves confidentiality, competition-law discipline, non-reliance, finance-boundary controls, and procurement neutrality. Such materials shall not be used to provide investment advice, ratings, finance-readiness, insurance approval, lending approval, public finance approval, procurement approval, or provider preference.
190.6 Personal Information and Rights-Bearing Data. Personal information, sensitive personal information, rights-bearing data, employee data, participant data, fellow data, volunteer data, health-adjacent data, community data, and grievance data shall be processed under privacy, data protection, confidentiality, access, retention, deletion, redaction, and incident response rules.
190.7 Health-Sensitive Data. Health-sensitive data, public health data, clinical-adjacent data, youth data, vulnerable population data, and emergency health data shall receive heightened review and may require de-identification, aggregation, suppression, access restriction, legal review, research ethics review, public authority review, or controlled-room handling.
190.8 Community-Protected, Tribal / Indigenous, Local, Territorial, Cultural, Environmental, and Protected Knowledge. Community-protected knowledge, Tribal and Indigenous knowledge, local and territorial knowledge, cultural knowledge, environmental knowledge, sacred knowledge, ecological knowledge, and other protected knowledge shall be handled under safeguards, consent and non-consent, attribution and non-attribution, public-safe mapping, access restriction, and correction rules. Such knowledge shall not be extracted, generalized, mapped, published, trained into AI systems, or transferred for institutional convenience.
190.9 Controlled-Room Rules. Controlled rooms shall have admission rules, access classifications, confidentiality terms, data-handling rules, AI-use rules, competition rules, public authority boundary rules, finance boundary rules, safeguards rules, logging, monitoring, exhibit controls, chain-of-custody, closeout, and access revocation.
190.10 No-Download Room Rules. No-download rooms may be used where materials require heightened protection. Participants shall not download, copy, screenshot, scrape, transcribe, print, forward, photograph, record, upload, summarize with unapproved AI, or otherwise remove materials except as expressly permitted by room rules.
190.11 Data-Room Rules. Data rooms shall identify data owner, permitted users, permitted purpose, classification, access limits, retention, export restrictions, AI-use restrictions, publication restrictions, data return, deletion, sealing, and audit logs.
190.12 Evidence-Room Rules. Evidence rooms shall preserve source lineage, provenance, chain-of-custody, confidence, uncertainty, challenge history, correction history, disputed-evidence handling, and public-safe status. Evidence-room access shall not create recognition, finance-readiness, certification, procurement approval, public authority approval, or execution authority.
190.13 Clean-Room Rules. Clean rooms may be used for competition-sensitive, market-sensitive, provider-sensitive, public authority-sensitive, data-sensitive, or finance-sensitive analysis. Clean rooms shall include independent administration, aggregation, de-identification, delayed reporting, participant separation, counsel or compliance review where appropriate, and strict do-not-discuss discipline.
190.14 AI-Use Restrictions on Committee Materials. Committee materials shall not be uploaded to, processed by, summarized by, embedded in, trained into, fine-tuned into, or otherwise exposed to unapproved AI systems. Approved AI use shall be recorded where material and shall respect confidentiality, privacy, cyber, public authority, protected knowledge, IP, export-control, and data-use restrictions.
190.15 No Upload to Unapproved AI Systems. No participant shall upload confidential materials, public authority materials, personal information, health-sensitive data, infrastructure-sensitive data, cyber-sensitive data, finance-sensitive data, commercially sensitive data, protected knowledge, draft bylaws, legal advice, controlled-room materials, repository credentials, or technical secrets to an unapproved AI system.
190.16 No Shadow IT or Side-Channel Storage. Participants shall not store committee materials in unauthorized personal drives, messaging systems, email accounts, note tools, transcription systems, AI tools, external repositories, side-channel collaboration spaces, or unmanaged devices. Shadow IT and side-channel storage shall be treated as a security and records risk.
190.17 Breach Response. Confidentiality, data, AI, cyber, public authority, protected knowledge, privilege, competition, or controlled-room breaches shall be escalated promptly. Response may include access suspension, forensic review, legal hold, notification review, public authority notice, participant notice, takedown, deletion, credential rotation, publication freeze, correction, discipline, contractual remedy, or Board review.
190.18 Confidentiality, Privilege, Data Access, and Controlled-Room Records. The Corporation shall maintain records of confidentiality classifications, privilege markings, access permissions, room rules, participant acknowledgments, data-room logs, evidence-room logs, clean-room controls, AI-use approvals, access revocations, breaches, incident responses, corrections, and closeout.
Section 191. Conflicts, Recusal, Related-Party Participation, Sponsored Participants, Provider Participants, and Independence Review
191.1 Conflict Disclosure Requirement. All committee, council, forum, working group, panel, competence cell, and advisory body participants shall disclose conflicts relevant to their role, access, recommendations, decisions, work products, public authority interfaces, sponsor relationships, provider relationships, research outputs, data access, technical contributions, publication activity, finance-adjacent materials, and safeguards matters.
191.2 Annual Disclosures. Participants serving on continuing bodies may be required to submit annual conflict disclosures. Annual disclosures shall be reviewed for financial, institutional, research, data, AI, cyber, public authority, sponsor, donor, funder, provider, host, investor, insurer, lender, contractor, university, laboratory, national company, Project SPV, and personal conflicts.
191.3 Event-Based Disclosures. Participants shall update disclosures promptly when a new conflict arises or when a previously disclosed conflict becomes material. Event-based disclosure is required before deliberation, recommendation, review, vote, access, publication, or public statement where the conflict may affect the matter.
191.4 Financial Conflicts. Financial conflicts may include compensation, equity, debt, grants, donations, sponsorship, consulting fees, employment, board roles, advisory roles, investment interests, revenue share, IP royalties, vendor payments, reimbursement arrangements, or other financial interests.
191.5 Institutional Conflicts. Institutional conflicts may include affiliation with public authorities, universities, laboratories, sponsors, providers, hosts, donors, funders, investors, insurers, lenders, national companies, Project SPVs, enterprise actors, media organizations, advocacy groups, political bodies, or other institutions with interests affected by the matter.
191.6 Research Conflicts. Research conflicts may include authorship, peer review relationships, sponsor influence, publication interests, academic competition, data ownership, method ownership, prior conclusions, reputational interests, and research funding.
191.7 Data / AI / Cyber Conflicts. Data / AI / cyber conflicts may include control of data sources, model ownership, AI vendor relationships, cloud provider relationships, cybersecurity vendor roles, vulnerability disclosure interests, compute sponsorship, repository permissions, or access to sensitive technical information.
191.8 Public Authority Conflicts. Public authority conflicts may include official duties, procurement roles, regulatory roles, grant roles, public finance roles, emergency management roles, public infrastructure roles, lobbying roles, government ethics restrictions, or public records constraints.
191.9 Sponsor, Donor, Funder, Provider, Host, Investor, Insurer, Lender, National Company, Project SPV, Contractor, University, Laboratory, or Partner Conflicts. Conflicts involving sponsors, donors, funders, providers, hosts, investors, insurers, lenders, national companies, Project SPVs, contractors, universities, laboratories, or partners shall be reviewed for control risk, capture risk, publication influence, provider preference, procurement influence, finance influence, certification influence, recognition influence, and public authority access influence.
191.10 Sponsored Participant Review. Sponsored participants shall be reviewed for source of sponsorship, sponsor relationship, scope, expected benefits, independence, public statement limits, access limits, and influence risk. Sponsorship shall not purchase committee seat control, agenda control, output control, public authority access, provider preference, recognition, finance-readiness, certification, procurement advantage, or publication influence.
191.11 Provider Participant Review. Provider participants shall be reviewed for provider neutrality, competition-law compliance, procurement neutrality, public authority influence, technical dependency, data access, software contribution, sponsor relationships, and public-safe claim risk. Provider participation shall not create preferred provider status.
191.12 Public Authority Participant Review. Public authority participants shall be reviewed for capacity classification, official-capacity authority, public records constraints, government ethics, procurement constraints, grant constraints, regulatory constraints, public finance constraints, emergency management boundaries, and public statement limits.
191.13 Related-Party Participation Review. Related-party participation shall be reviewed where a participant is related to a director, officer, employee, contractor, donor, sponsor, provider, host, public authority participant, or enterprise actor in a manner that may affect independence. Review may require disclosure, recusal, access restriction, independent review, or exclusion.
191.14 Recusal. Recusal shall be required where a conflict materially affects or may reasonably appear to affect impartiality, independence, public trust, research integrity, evidence integrity, procurement neutrality, finance boundary discipline, certification boundary discipline, public authority boundary discipline, or safeguards. Recusal may include exclusion from discussion, recommendation, voting, drafting, access, or publication review.
191.15 Access Restriction During Recusal. Where necessary, a recused participant shall be denied access to materials, drafts, data, deliberations, meeting rooms, repositories, controlled rooms, or decision records related to the matter. Access restrictions shall be documented and enforced through technical and administrative controls.
191.16 Independence Review. Independence review may be conducted at appointment, annually, event-by-event, before sensitive access, before peer review, before publication, before public authority interface, before sponsor-supported work, before provider-involved work, or before finance-adjacent work. Independence review shall consider both actual and apparent conflicts.
191.17 Capture-Risk Mitigation. Capture-risk mitigation may include diversification of membership, independent chairing, clean-team handling, agenda limits, voting restrictions, access restrictions, recusal, separation of sponsor-funded work, external review, public-safe disclosure, refusal of support, termination of participation, or Board review.
191.18 Conflict Violation Response. Failure to disclose conflicts, breach of recusal, unauthorized access, improper influence, sponsor or provider control, public authority overclaim, finance overclaim, certification overclaim, procurement overclaim, or misuse of committee status may result in correction, access restriction, suspension, removal, termination, public or controlled clarification, contractual remedy, legal referral, or other action.
191.19 Committee Conflict, Recusal, Related-Party, and Independence Records. The Corporation shall maintain records of disclosures, reviews, recusals, access restrictions, independence determinations, sponsored participant reviews, provider participant reviews, public authority participant reviews, related-party reviews, mitigation measures, violations, corrective actions, and closeout.
Section 192. Competition, Antitrust, Market-Sensitive Information, Clean Teams, and Do-Not-Discuss Discipline
192.1 Competition Discipline Purpose. The Corporation shall apply competition and antitrust discipline to committees, councils, forums, working groups, panels, labs, benchmarking activities, indices, data-sharing structures, standards-support activities, provider participation, sponsor participation, public authority learning sessions, clean rooms, controlled rooms, and public-good coordination activities. The purpose of such discipline is to preserve lawful collaboration while preventing collusion, exclusion, price coordination, procurement steering, market allocation, output restriction, wage coordination, or misuse of competitively sensitive information.
192.2 Application to Committees, Councils, Forums, Working Groups, Panels, Labs, Benchmarking, Indices, Data Sharing, and Standards-Support Activities. Competition discipline applies to any setting in which competitors, providers, vendors, contractors, operators, capital actors, public authorities, sponsors, donors, funders, hosts, universities, laboratories, or enterprise actors exchange information or participate in shared work. The fact that a setting is public-benefit, research-oriented, standards-supporting, public authority-facing, or nonprofit shall not exempt it from competition controls.
192.3 Do-Not-Discuss List. The Corporation may maintain a do-not-discuss list for meetings and collaboration spaces. The list shall prohibit discussion of competitively sensitive or collusive topics and may be included in agendas, meeting openings, participation terms, controlled-room rules, clean-room rules, and training materials.
192.4 No Price, Margin, Cost, Bid, Wage, Customer, Supplier, Market Allocation, Capacity, Exclusion, Boycott, Procurement Steering, or Collusive Strategy Discussion. Participants shall not discuss, exchange, coordinate, signal, request, recommend, or agree upon prices, margins, costs, bids, wages, hiring terms, customers, suppliers, territories, market allocation, production capacity, service capacity, output restrictions, exclusion, refusals to deal, boycotts, procurement steering, provider steering, or collusive strategy.
192.5 Competitively Sensitive Information Controls. Competitively sensitive information shall be identified, restricted, aggregated, de-identified, delayed, independently administered, or excluded as appropriate. Such information may include pricing, cost structures, strategic plans, bid strategies, non-public customer data, supplier terms, wage data, capacity plans, market share data, proprietary performance information, and provider-specific commercial terms.
192.6 Clean-Team Structures. Clean teams may be used where restricted review is necessary. Clean-team participants shall be independent or appropriately walled off, subject to written terms, prohibited from sharing restricted information with unauthorized persons, and required to produce only approved aggregated or sanitized outputs.
192.7 Clean-Room Structures. Clean rooms may be used for analysis involving market-sensitive, provider-sensitive, finance-sensitive, public authority-sensitive, cyber-sensitive, infrastructure-sensitive, or data-sensitive information. Clean rooms shall include defined inputs, permitted analyses, approved participants, access logs, output review, publication restrictions, and closeout.
192.8 Aggregation, De-Identification, Delay, and Independent Administration. Benchmarking, indices, market baselines, provider comparisons, capability maps, and shared datasets shall use aggregation, de-identification, delayed reporting, independent administration, or other safeguards where needed to reduce competition risk. No benchmark or index shall be used to coordinate prices, wages, bids, capacity, procurement, or market conduct.
192.9 Agenda Review. Agendas for competition-sensitive meetings shall be reviewed before circulation. Agenda review may be conducted by chair, secretary, counsel, compliance officer, or authorized staff. Agenda items creating competition, procurement, provider-preference, or market-conduct risk shall be revised, removed, restricted, or escalated.
192.10 Minute Review. Minutes of competition-sensitive meetings shall accurately record permitted topics and shall not include competitively sensitive details unless necessary, lawful, and appropriately protected. Minute review may be required before circulation, approval, publication, or repository deposit.
192.11 Stop-Meeting Authority. The chair, counsel, compliance officer, secretary, authorized officer, or any participant acting in good faith may stop or suspend discussion that appears to create competition, antitrust, procurement, collusion, or market-conduct risk. The stop shall be recorded, and the matter shall be escalated where appropriate.
192.12 Incident Escalation. Competition incidents shall be escalated to the appropriate officer, committee, counsel, compliance function, or Board. Escalation may result in privilege preservation, participant instruction, meeting termination, correction of minutes, deletion or sequestration of materials, training, access restriction, investigation, public or controlled clarification, or legal referral.
192.13 Corrective Action. Corrective action may include agenda revision, minute correction, participant removal, training, clean-room redesign, information deletion, output withdrawal, public-safe correction, provider-neutrality clarification, procurement-neutrality clarification, suspension of activity, or termination of a group.
192.14 Competition Training. Participants in competition-sensitive bodies may be required to complete competition and antitrust training. Training may include do-not-discuss rules, clean-room rules, benchmarking rules, procurement-neutrality rules, provider-neutrality rules, sponsor non-control, public authority boundary rules, and incident reporting.
192.15 Competition and Antitrust Records. The Corporation shall maintain competition and antitrust records, including training records, agenda reviews, meeting notices, do-not-discuss reminders, clean-team records, clean-room records, aggregated-output reviews, incident records, stop-meeting records, corrective action records, and counsel or compliance reviews.
Section 193. Committee Reporting, Recommendations, Escalation, Ratification, and Board Review
193.1 Reporting Requirement. Each committee, council, forum, working group, panel, competence cell, and advisory body shall report as required by its charter, Board resolution, officer delegation, policy, or applicable law. Reports shall be accurate, records-supported, public-safe where circulated beyond controlled audiences, and clear as to advisory, recommendation, decision, draft, controlled, or final status.
193.2 Report Frequency. Report frequency may be regular, quarterly, annual, project-based, event-based, emergency-based, closeout-based, or as otherwise required by charter or delegation. Material risks shall be reported promptly and shall not await regular reporting cycles.
193.3 Report Contents. Reports may include activities, attendance, work products, recommendations, decisions within delegated authority, evidence basis, methods notes, conflicts, recusals, minority views, data / AI / cyber issues, public authority issues, finance-boundary issues, certification-boundary issues, procurement-neutrality issues, competition issues, safeguards issues, corrections, open risks, and action items.
193.4 Recommendations. Recommendations shall identify the recommending body, authority, scope, evidence basis, methods basis, limitations, confidence, uncertainty, alternatives considered, conflicts, minority views, required approvals, and proposed next steps. Recommendations shall not be represented as final decisions unless approved by competent authority.
193.5 Evidence Base for Recommendations. Recommendations involving evidence, methods, publications, technical baselines, public authority materials, finance-adjacent materials, certification-adjacent materials, public-safe reports, dashboards, maps, or AI outputs shall include sufficient evidence basis, source lineage, confidence, uncertainty, and limitation notes to support review.
193.6 Method Notes for Recommendations. Where recommendations depend on methods, models, simulations, benchmarks, statistical analysis, AI systems, digital twins, sensor fusion, AI-RAN signals, O-RAN signals, DePIN records, DLT records, geospatial analysis, cyber telemetry, or public authority data, method notes shall identify assumptions, known limits, validation status, correction path, and public-safe status.
193.7 Conflicts and Recusals in Reports. Reports shall identify material conflicts and recusals that affected deliberation, access, voting, recommendation, drafting, review, or publication. Where necessary, reports shall state whether conflicted participants were excluded from access and influence.
193.8 Minority Views in Reports. Reports shall include minority views where material to evidence integrity, method validity, research integrity, data / AI / cyber risk, public authority boundary, finance boundary, certification boundary, procurement neutrality, provider neutrality, sponsor control, safeguards, protected knowledge, or public-safe publication.
193.9 Risk and Boundary Notes. Reports shall identify risk and boundary issues, including legal, tax, nonprofit, fiduciary, regulatory-perimeter, non-execution, role-separation, public authority, finance, securities, insurance, lending, rating, public finance, procurement, certification, recognition, provider preference, sponsor control, public warning, emergency command, and professional-boundary issues.
193.10 Data / AI / Cyber Notes. Reports involving data, AI, cyber, repositories, software, models, compute, public authority data, health data, infrastructure-sensitive data, community-protected data, protected knowledge, or controlled rooms shall identify classification, access, AI-use restrictions, cyber controls, incidents, and unresolved risks.
193.11 Public Authority Notes. Reports involving public authorities shall identify capacity classifications, official-capacity records, public authority data constraints, public authority reference permissions, public records risks, procurement risks, funding risks, regulatory risks, public finance risks, emergency management boundaries, and limitation language.
193.12 Finance, Certification, Procurement, Recognition, and Public Warning Boundary Notes. Reports shall explicitly identify whether the matter implicates finance-readiness, insurance-readiness, bankability, capital-readability, ratings, certification, accreditation, conformance, procurement, recognition, maturity, standing, Docket, Grid, Nexus-compatible status, public warning, emergency command, or public authority decision risk. Where implicated, reports shall include limitation language and escalation path.
193.13 Safeguards and Protected Knowledge Notes. Reports shall identify community safeguards, Tribal and Indigenous protocols, protected knowledge, consent and non-consent, public-safe mapping, civil rights, accessibility, grievance pathways, remedy pathways, non-retaliation, and do-no-harm issues.
193.14 Escalation to Board. Matters shall be escalated to the Board where required by law, Articles, this Bylaw, Board reserved matters, charter, delegation, risk level, conflict severity, boundary risk, public authority sensitivity, finance sensitivity, certification sensitivity, procurement sensitivity, safeguards concern, data / AI / cyber incident, or institutional significance.
193.15 Escalation to Officer. Matters may be escalated to an appropriate officer where within delegated authority, including the President, Executive Director or Chief Executive Officer, Secretary, Treasurer or Chief Financial Officer, Chief Evidence Officer, Chief Research Officer, Chief Methods Officer, Chief Technology Officer, Chief Data, AI, and Cyber Officer, Chief Public Authority Learning Officer, Chief Safeguards Officer, Chief Legal, Compliance, and Risk Officer, or other authorized officer.
193.16 Escalation to Counsel or Compliance Function. Legal, compliance, privilege, regulatory-perimeter, sanctions, export-control, competition, professional-boundary, public authority, public finance, procurement, data breach, AI incident, cyber incident, protected knowledge, civil rights, accessibility, research ethics, or employment matters may be escalated to counsel or compliance function.
193.17 Ratification Where Required. Where a committee, officer, working group, or emergency actor takes action requiring ratification, the action shall be presented to the competent authority with records, basis, scope, timing, authority claim, limits, risks, and proposed ratification or cure. Ratification shall not validate an action that law or this Bylaw prohibits.
193.18 Board Review. The Board may review any committee, council, forum, working group, panel, competence cell, advisory recommendation, delegated decision, emergency action, correction, or record. Board review may affirm, modify, reject, suspend, require correction, require investigation, require legal review, require safeguards review, dissolve a body, or change a delegation.
193.19 Reporting, Recommendation, Escalation, Ratification, and Review Records. The Corporation shall maintain reporting records, recommendations, minority views, risk notes, boundary notes, public authority notes, data / AI / cyber notes, safeguards notes, escalations, ratifications, Board reviews, officer reviews, counsel reviews, compliance reviews, corrections, and closeout records.
Section 194. Committee Records, Registers, Minutes, Decisions, Recommendations, Corrective Actions, and Retention
194.1 Committee Record Requirement. Each committee, council, forum, working group, panel, competence cell, advisory body, and controlled-room review group shall maintain records sufficient to demonstrate lawful creation, scope, authority, membership, meetings, materials, decisions, recommendations, conflicts, recusals, confidentiality, access, reports, corrections, and closeout.
194.2 Committee Register. The Corporation shall maintain a Committee Register identifying each body, charter, creation authority, status, purpose, scope, authority type, reporting line, chair or lead, records custodian, members, confidentiality class, review cycle, sunset date, suspension status, and dissolution status.
194.3 Charter Records. Charter Records shall include the original charter, amendments, delegated authority, scope changes, suspension records, renewal records, sunset records, dissolution records, and supersession history.
194.4 Membership Records. Membership Records shall include appointment, eligibility, capacity, term, role, access class, conflict disclosure, independence review, confidentiality acknowledgment, training, sanctions or export-control screening where applicable, offboarding, and access revocation.
194.5 Attendance Records. Attendance Records shall identify participants, capacity, role, public authority classification where applicable, absences, guests, observers, recused persons, and persons excluded from sensitive portions.
194.6 Notice Records. Notice Records shall include meeting notice, waiver where applicable, emergency notice basis, agenda circulation, materials circulation, confidentiality reminders, competition reminders, public authority reminders, AI-use restrictions, and access instructions.
194.7 Agenda Records. Agenda Records shall include topics, presenters, expected action, boundary notes, conflict items, public authority items, finance-boundary items, certification-boundary items, procurement-neutrality items, data / AI / cyber items, safeguards items, and competition-sensitive items.
194.8 Material Records. Material Records shall include materials reviewed, document status, confidentiality class, source, version, repository location, access restrictions, public-safe status, and any materials withheld due to recusal, privilege, confidentiality, protected knowledge, public authority restrictions, or legal limits.
194.9 Minute Records. Minute Records shall record attendance, quorum where applicable, matters considered, decisions, recommendations, votes, abstentions, recusals, minority views, conflicts, materials reviewed, action items, escalations, and corrections. Minutes shall avoid unnecessary inclusion of confidential, privileged, protected, public authority, cyber-sensitive, infrastructure-sensitive, commercially sensitive, or competition-sensitive details.
194.10 Recommendation Records. Recommendation Records shall identify recommendation text, authority, evidence basis, method basis, limitations, confidence, uncertainty, boundary notes, conflicts, recusals, minority views, required approvals, and disposition.
194.11 Decision Records Where Delegated. Where a body has delegated decision authority, Decision Records shall identify delegation source, scope, quorum, vote, effective date, conditions, limitations, action owner, implementation path, and ratification requirements where any.
194.12 Conflict and Recusal Records. Conflict and Recusal Records shall identify disclosures, review determinations, recusals, access restrictions, mitigation, violations, and corrective actions. Records shall be protected where confidentiality, privacy, privilege, employment, or legal constraints apply.
194.13 Confidentiality Acknowledgments. Confidentiality acknowledgments shall be maintained for participants with access to confidential, privileged, public authority, cyber-sensitive, infrastructure-sensitive, finance-sensitive, commercially sensitive, personal, health-sensitive, community-protected, Tribal / Indigenous, local / territorial, cultural, environmental, or protected knowledge materials.
194.14 Data / AI / Cyber Access Records. Data / AI / Cyber Access Records shall document access to data rooms, repositories, models, compute environments, AI systems, cyber materials, keys, credentials, logs, dashboards, controlled rooms, no-download rooms, and restricted technical assets.
194.15 Public Authority Capacity Records. Public Authority Capacity Records shall identify each public authority participant’s capacity, authority limitations, public authority reference permission, data contribution restrictions, public records constraints, public statement limits, procurement constraints, funding constraints, regulatory constraints, public finance constraints, and emergency management boundaries.
194.16 Safeguards Records. Safeguards Records shall include community safeguards reviews, Tribal and Indigenous protocol records, consent and non-consent records, protected knowledge restrictions, civil rights reviews, accessibility reviews, public-safe mapping reviews, grievance records, remedy records, non-retaliation records, and do-no-harm records.
194.17 Competition Compliance Records. Competition Compliance Records shall include do-not-discuss reminders, agenda review, minute review, clean-team records, clean-room records, benchmarking controls, incident escalations, stop-meeting records, training records, and corrective actions.
194.18 Corrective Action Records. Corrective Action Records shall include issue identification, responsible body, action owner, deadlines, remediation steps, correction language, supersession, withdrawal, takedown, archive, participant notice, public authority notice, public-safe notice, Board action, officer action, and closeout.
194.19 Sunset, Review, Suspension, and Dissolution Records. Records shall document periodic review, renewal, redesign, suspension, sunset, dissolution, transfer of work, transfer of records, access revocation, repository closeout, unresolved risks, and public-safe status of remaining outputs.
194.20 Retention, Access, Sealing, Deletion, Archival, and Secure Disposal of Committee Records. Committee records shall be retained, accessed, sealed, deleted, archived, or securely disposed of under applicable law, record policy, legal holds, privacy requirements, public authority restrictions, research ethics obligations, contract terms, protected knowledge restrictions, cyber controls, and public-good archive needs.
Section 195. Periodic Review, Evaluation, Renewal, Sunset, and Redesign of Committees and Advisory Bodies
195.1 Periodic Review Purpose. The Corporation shall periodically review committees, councils, forums, working groups, panels, competence cells, and advisory bodies to determine whether each remains necessary, lawful, effective, independent, properly scoped, properly recorded, and aligned with public-benefit purpose, non-execution, role separation, data / AI / cyber discipline, safeguards, competition controls, and correctionability.
195.2 Charter Review. Charter review shall assess whether the body’s purpose, scope, authority, membership, reporting line, access class, confidentiality class, data / AI / cyber class, public authority boundary, finance boundary, certification boundary, procurement-neutrality rule, safeguards class, review cycle, and sunset remain appropriate.
195.3 Membership Review. Membership review shall assess composition, eligibility, participation, attendance, expertise, diversity, public-interest perspective, geographic relevance, state and territorial awareness, Tribal and Indigenous interface respect, independence, conflicts, training, access needs, and offboarding needs.
195.4 Independence Review. Independence review shall assess whether sponsor, donor, funder, provider, host, public authority, investor, insurer, lender, national company, Project SPV, contractor, university, laboratory, political, personal, or institutional relationships compromise or appear to compromise the body’s work.
195.5 Conflict Review. Conflict review shall examine annual disclosures, event-based disclosures, recusals, access restrictions, related-party participation, sponsored participants, provider participants, public authority participants, and conflict violation history.
195.6 Performance Review. Performance review shall assess whether the body fulfills its purpose, produces useful work, meets deadlines, maintains records, escalates risks, respects limitations, supports correction, and avoids duplicative or obsolete activity.
195.7 Records Review. Records review shall assess completeness, accuracy, repository location, access controls, confidentiality class, public authority capacity records, data / AI / cyber records, safeguards records, competition records, recommendations, decisions, corrections, and closeout.
195.8 Boundary Compliance Review. Boundary compliance review shall assess compliance with non-execution, role separation, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, public-safe claims, no-AI-as-authority, no-dashboard-as-authority, no-proof-receipt-as-authority, and no-signal-as-authority rules.
195.9 Public Authority Boundary Review. Public authority boundary review shall assess whether public authority participation has been capacity-classified and whether any activity may imply public authority delegation, official adoption, public warning, emergency command, procurement approval, funding approval, regulatory approval, public finance approval, sovereign obligation, public-private partnership, or governmental decision.
195.10 Finance, Certification, Procurement, Recognition, Provider-Preference, and Public Warning Boundary Review. The Corporation shall review whether any body has produced or appeared to produce finance-readiness, insurance-readiness, bankability, capital-readability, rating, certification, accreditation, procurement approval, recognition, maturity, standing, Docket approval, Grid guarantee, Nexus-compatible status, provider preference, public warning, emergency command, or regulated professional advice.
195.11 Data / AI / Cyber / Privacy Review. Review shall assess data access, AI use, cyber controls, privacy compliance, model registers, inference records, compute records, repository security, approved tools, unapproved AI risk, breach history, vulnerability management, and incident response.
195.12 Safeguards Review. Safeguards review shall assess community protection, Tribal and Indigenous protocols, protected knowledge, civil rights, accessibility, public-safe mapping, consent and non-consent, grievances, remedies, non-retaliation, vulnerable communities, and do-no-harm controls.
195.13 Competition and Antitrust Review. Competition and antitrust review shall assess agenda controls, meeting discipline, do-not-discuss compliance, clean-team structures, clean-room structures, benchmarking practices, provider participation, market-sensitive information handling, incident history, and training.
195.14 Sponsor and Provider Capture Review. Sponsor and provider capture review shall assess whether sponsors, donors, funders, providers, vendors, hosts, national companies, Project SPVs, enterprise actors, or capital actors have influenced or may influence agendas, outputs, research conclusions, publication timing, technical baselines, software releases, public authority access, provider status, recognition inputs, finance-readiness inputs, certification claims, or procurement signals.
195.15 Renewal. A body may be renewed where it remains necessary, lawful, useful, independent, properly scoped, and compliant. Renewal may be unconditional or subject to changes in charter, membership, access, reporting, records, safeguards, competition controls, or sunset.
195.16 Redesign. A body may be redesigned where its purpose remains useful but its structure, membership, scope, authority, reporting line, controls, or records require correction. Redesign may include merger, split, narrowing, expansion where lawful, role clarification, access reclassification, control strengthening, or transfer of work.
195.17 Sunset. A body may sunset automatically or by decision when its mandate is completed, obsolete, redundant, unsafe, noncompliant, underperforming, captured, or no longer aligned with the Corporation’s purpose. Sunset shall include records closeout, access revocation, work-product classification, unresolved-risk notes, and archive.
195.18 Dissolution. A body may be dissolved by the Board or other competent authority consistent with its charter and applicable delegation. Dissolution shall not impair required records, confidentiality, legal holds, correction obligations, public authority notice obligations, data deletion obligations, or protected knowledge restrictions.
195.19 Review, Renewal, Redesign, Sunset, and Dissolution Records. The Corporation shall maintain records of periodic reviews, evaluations, renewal decisions, redesign decisions, sunset actions, dissolution actions, records transfers, access revocations, unresolved risks, corrections, and archive.