ARTICLE VII. CONFLICTS
Section 197. Conflict of Interest Purpose and Policy Requirement
197.1 Conflict of Interest Purpose
197.1.1 The purpose of this Article is to preserve the independence, public-benefit integrity, nonprofit character, tax-exempt or tax-exempt-compatible discipline, evidence integrity, methods integrity, research integrity, public-good software integrity, open technical baseline integrity, public authority learning integrity, public-safe claims discipline, civil rights, accessibility, community safeguards, Tribal and Indigenous protocol respect, protected knowledge stewardship, Nexus role separation, and non-executing institutional character of The Global Centre for Risk and Innovation - United States.
197.1.2 Conflict governance under this Article shall be interpreted as a constitutional safeguard of the Corporation and not merely as an administrative disclosure practice. It protects the Corporation against actual conflicts, potential conflicts, perceived conflicts, structural conflicts, financial conflicts, institutional conflicts, related-party influence, private inurement, impermissible private benefit, sponsor control, donor capture, provider preference, public authority confusion, finance-readiness overclaim, procurement influence, certification overclaim, recognition overclaim, research distortion, evidence distortion, technical-baseline capture, public-good software capture, data / AI / cyber compromise, protected knowledge extraction, and enterprise-stack capture.
197.1.3 No Covered Person may use position, access, authorship, technical control, governance influence, public authority proximity, donor relationship, sponsor relationship, provider relationship, host relationship, committee role, repository role, data-room role, controlled-room role, clean-room role, public communications role, or Nexus-facing status to obtain improper private advantage, distort institutional outputs, bias evidence or methods, prefer a provider, signal endorsement, influence regulated execution, or shift the Corporation away from its public-good role.
197.2 Written Conflict of Interest Policy Requirement
197.2.1 The Board shall adopt, maintain, periodically review, amend where necessary, and enforce a written conflict of interest policy consistent with this Article, applicable law, the Articles or Certificate, nonprofit and tax-exempt or tax-exempt-compatible requirements, fiduciary duties, Board reserved powers, public-benefit purpose, non-execution, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, and correctionability.
197.2.2 The conflict of interest policy shall address, at minimum:
197.2.2(a) Covered Persons, Related Parties, affiliates, sponsored representatives, coordinated participants, beneficial owners, controlled entities, and persons with practical influence over Corporation decisions or outputs; 197.2.2(b) actual, potential, perceived, financial, institutional, fiduciary, employment, contractual, research, evidence, methods, publication, data, AI, cybersecurity, privacy, technical asset, public authority, sponsor, donor, funder, provider, host, enterprise, capital actor, safeguards, competition, sanctions, export-control, lobbying, political activity, government ethics, procurement integrity, professional boundary, and regulatory-perimeter conflicts; 197.2.2(c) annual disclosures, initial disclosures, event-based disclosures, access-based disclosures, publication-based disclosures, transaction-based disclosures, public authority-based disclosures, sponsor-based disclosures, provider-based disclosures, data / AI / cyber disclosures, safeguards disclosures, certification of completeness, certification of accuracy, and certification of understanding; 197.2.2(d) intake, triage, materiality assessment, classification, escalation, independent review, disinterested approval, fairness determination, comparability review, best-interest finding, public-benefit purpose finding, no-private-inurement finding, no-impermissible-private-benefit finding, anti-capture finding, and boundary-compliance finding; 197.2.2(e) recusal, access restriction, deliberation restriction, recommendation restriction, approval restriction, voting restriction, delegation restriction, role restriction, committee restriction, information firewall, clean-team handling, clean-room handling, public-safe disclosure, controlled disclosure, ring-fencing, monitoring, denial, refusal, return, termination, suspension, withdrawal, re-scoping, and correction; and 197.2.2(f) records, registers, minutes, determinations, mitigation records, related-party transaction records, gift and hospitality records, independence records, capture records, enforcement records, redaction, sealing, retention, archival, secure disposal, and legal hold.
197.2.3 No failure, delay, defect, silence, incompleteness, ambiguity, or inconsistency in an implementing policy shall suspend the direct force of this Article. This Article shall apply as binding bylaw authority whether or not a policy, schedule, form, register, matrix, checklist, or operating procedure has been adopted.
197.3 Public-Benefit Integrity Purpose
197.3.1 Conflict governance shall ensure that every governance action, officer action, committee recommendation, technical review, research output, evidence classification, method classification, public-safe publication, public-good software release, controlled-room admission, public authority interface, support relationship, GRF-facing input, GRA-facing technical input, and Nexus-facing communication is made for the Corporation’s lawful public-benefit purposes.
197.3.2 A Covered Person shall not subordinate the Corporation’s public-benefit purpose to personal gain, employer interest, sponsor preference, donor preference, funder expectation, provider interest, host interest, public authority pressure, capital actor expectation, publication pressure, technical ego, institutional ambition, enterprise opportunity, political objective, reputational interest, or market signal.
197.4 Nonprofit Integrity Purpose
197.4.1 Conflict governance shall preserve the Corporation’s nonprofit character, non-distribution obligation, private inurement prohibition, private benefit discipline, reasonable compensation controls, related-party transaction discipline, restricted fund discipline, and public-good asset stewardship.
197.4.2 No Covered Person may use the Corporation’s nonprofit status, public-benefit language, public-good software, technical baselines, evidence outputs, controlled rooms, public authority learning activities, or Nexus-facing status to divert value to private persons or private entities except through lawful, reasonable, recorded, mission-aligned, and independently reviewed arrangements.
197.5 Tax-Exempt or Tax-Exempt-Compatible Integrity Purpose
197.5.1 Conflict governance shall preserve any tax-exempt, tax-exempt-compatible, charitable, public-benefit, educational, scientific, research, or other tax-sensitive posture of the Corporation.
197.5.2 Where a conflict may affect tax classification, charitable solicitation, public support, unrelated business income, private inurement, private benefit, excess benefit, restricted funds, donor acknowledgments, sponsorship treatment, compensation, reimbursement, grants, fellowships, awards, or public filings, the matter shall be escalated for tax, legal, Board, committee, or independent review as appropriate.
197.6 Evidence Integrity Purpose
197.6.1 Conflict governance shall protect evidence from distortion, selection bias, sponsor influence, provider influence, public authority pressure, funder expectation, publication incentive, capital-reader pressure, recognition pressure, finance-readiness pressure, certification pressure, procurement pressure, or enterprise-stack advantage.
197.6.2 Evidence shall be classified, reviewed, recorded, challenged, corrected, superseded, withdrawn, retracted, or archived according to source lineage, provenance, custody, confidence, uncertainty, limitations, public-safe status, and correctionability, not according to the interests of a Covered Person or Related Party.
197.7 Methods Integrity Purpose
197.7.1 Conflict governance shall protect methods, models, protocols, profiles, schemas, benchmarks, observability methods, ontology methods, Truth Engine methods, verifiable compute methods, AI evaluation methods, cyber methods, public-safe mapping methods, and technical baseline methods from improper influence.
197.7.2 No Covered Person shall select, alter, suppress, frame, or approve a method to favor a sponsor, donor, funder, provider, host, public authority participant, capital actor, national company, Project SPV, enterprise actor, publication interest, research interest, or personal interest.
197.8 Research Integrity Purpose
197.8.1 Conflict governance shall protect research design, hypothesis selection, data selection, model selection, fieldwork, peer review, red-team review, publication review, authorship, attribution, replication, reproducibility, research ethics, human-subjects review where applicable, community review, Tribal and Indigenous protocol review, protected knowledge review, and correction.
197.8.2 Research shall not be structured to deliver predetermined conclusions, sponsor-desired conclusions, provider-preferred conclusions, donor-friendly conclusions, public authority-desired conclusions, finance-facing conclusions, recognition-facing conclusions, certification-facing conclusions, procurement-facing conclusions, or public-relations conclusions.
197.9 Public-Good Software and Technical Asset Integrity Purpose
197.9.1 Conflict governance shall protect public-good software, open technical baselines, repositories, APIs, SDKs, schemas, data dictionaries, dashboards, reference architectures, test harnesses, benchmarks, model cards, dataset cards, system cards, benchmark cards, proof receipts, and technical profiles from capture, enclosure, misleading compatibility claims, insecure release, license misuse, IP distortion, or provider preference.
197.9.2 No Covered Person shall use maintainer status, repository access, code ownership, release authority, contributor status, cloud dependency, AI dependency, cyber dependency, software dependency, standards-support role, or technical authorship to create hidden governance authority, certification meaning, procurement meaning, recognition meaning, finance-readiness meaning, public authority meaning, or private control over public-good technical assets.
197.10 Data / AI / Cyber / Privacy Integrity Purpose
197.10.1 Conflict governance shall protect data governance, privacy, AI governance, cybersecurity, model registers, inference records, compute workload records, repository security, identity controls, access controls, cyber-sensitive materials, infrastructure-sensitive materials, health-sensitive materials, public authority data, community-protected data, Tribal and Indigenous data, protected knowledge, and controlled-room materials.
197.10.2 No Covered Person shall use data access, AI access, model access, cyber access, repository access, cloud access, compute access, dashboard access, credential access, key access, or controlled-room access for personal benefit, sponsor benefit, provider benefit, public authority leverage, finance-facing leverage, certification advantage, procurement advantage, research distortion, protected knowledge extraction, or enterprise-stack advantage.
197.11 Public Authority Boundary Integrity Purpose
197.11.1 Conflict governance shall preserve the Corporation’s public authority boundary. The Corporation may support public authority learning, evidence literacy, technical literacy, public-safe reporting literacy, scenario learning, simulation learning, tabletop learning, after-action learning, and capacity classification, but it shall not become a public authority, regulator, public finance authority, procurement authority, grant authority, public warning body, emergency command body, public-private partnership authority, or sovereign decision-maker.
197.11.2 Public authority participation, public authority data contribution, official-capacity participation, observer participation, regulator-listening participation, public finance reader participation, emergency-management participation, public infrastructure operator participation, simulation participation, or public authority room access shall not create endorsement, adoption, approval, funding, procurement, regulation, public warning, emergency command, public finance approval, sovereign obligation, or public-private partnership unless separately and lawfully created by the competent public authority and recorded.
197.12 Finance, Securities, Insurance, Lending, Rating, Public Finance, Procurement, Certification, Recognition, and Professional Boundary Integrity Purpose
197.12.1 Conflict governance shall preserve boundaries against securities activity, investment advice, broker-dealer activity, finder activity, capital placement, lending, banking, insurance placement, underwriting, rating, public finance approval, procurement approval, certification, accreditation, recognition, maturity standing, professional advice, public warning, emergency command, and other regulated or externally reserved functions.
197.12.2 No Covered Person shall use the Corporation’s evidence, methods, observability outputs, public-good software, open technical baselines, dashboards, proof receipts, public-safe reports, GRF-facing inputs, GRA-facing technical inputs, Nexus-compatible language, public authority learning materials, Academy materials, or controlled-room outputs to imply finance-readiness, insurance-readiness, bankability, investability, capital-readability, rating, procurement approval, certification, recognition, public authority approval, public warning, emergency command, or professional endorsement.
197.13 Civil Rights, Accessibility, Community Safeguards, Tribal / Indigenous, Local, Territorial, Cultural, Environmental, and Protected Knowledge Integrity Purpose
197.13.1 Conflict governance shall preserve civil rights, accessibility, community safeguards, Tribal and Indigenous protocol respect, Indigenous data safeguards, local and territorial knowledge protection, cultural knowledge protection, environmental knowledge protection, protected knowledge stewardship, public-safe mapping, grievance pathways, remedy pathways, protected participation, non-retaliation, and do-no-harm controls.
197.13.2 No Covered Person shall participate in, influence, approve, publish, map, extract, commercialize, train on, embed, disclose, suppress, reframe, or dispute community knowledge, Tribal or Indigenous knowledge, protected knowledge, local knowledge, territorial knowledge, cultural knowledge, environmental knowledge, grievance information, or safeguards-sensitive materials where the person has a conflicting interest or where independent safeguards review is required.
197.14 Sponsor, Donor, Funder, Provider, Host, Public Authority, Investor, Insurer, Lender, National Company, Project SPV, Vendor, Contractor, and Enterprise Capture Prevention Purpose
197.14.1 Conflict governance shall prevent capture by sponsors, donors, funders, providers, vendors, hosts, public authorities, investors, insurers, lenders, underwriters, banks, public finance actors, capital readers, national companies, state operating companies, regional companies, Project SPVs, contractors, universities, laboratories, media actors, community organizations, or enterprise actors.
197.14.2 Capture may occur through funding concentration, technical dependency, data dependency, cloud dependency, AI dependency, cyber dependency, hosting dependency, staff dependency, shared systems, shared records, shared rooms, shared publications, sponsored seats, controlled agendas, veto rights, renewal pressure, market expectation, public authority pressure, public visibility, or informal influence. The Corporation shall evaluate capture by practical effect, not only by formal legal rights.
197.15 Conflict Policy as Mandatory Implementing Instrument
197.15.1 The conflict of interest policy shall be a mandatory implementing instrument of this Bylaw. It may supplement, operationalize, and clarify this Article, but it shall not narrow, waive, suspend, contradict, or dilute this Article.
197.15.2 The policy may include schedules, forms, registers, matrices, checklists, disclosure tools, training materials, controlled vocabulary, public-safe notices, escalation workflows, and review protocols, provided that all such instruments remain subordinate to this Bylaw and applicable law.
197.16 Conflict Policy Records
197.16.1 The Corporation shall maintain Conflict Policy Records sufficient to demonstrate that the conflict of interest policy has been adopted, amended, reviewed, implemented, trained, enforced, corrected, superseded, and archived.
197.16.2 Conflict Policy Records shall include the policy title, version, adopting authority, effective date, review date, custodian, repository location, access class, publication class, disclosure forms, registers, training materials, certifications, policy amendments, exceptions refused, exceptions approved where lawful, enforcement actions, corrective actions, and archive status.
Section 198. Covered Persons
198.1 Covered Person Definition
198.1.1 A Covered Person means any person whose role, authority, access, influence, participation, contribution, review function, public-facing function, technical function, data function, AI function, cyber function, public authority interface, sponsor interface, provider interface, safeguards role, publication role, controlled-room role, repository role, Nexus-facing role, GRF-facing role, GRA-facing role, or relationship to the Corporation may affect the Corporation’s decisions, outputs, records, assets, claims, public meaning, or integrity.
198.1.2 Covered Person status shall be determined by substance, not title. A person may be a Covered Person even if not a director, officer, employee, member, contractor, or formal agent of the Corporation.
198.2 Directors
198.2.1 Each director is a Covered Person for all purposes of this Article. Directors shall disclose conflicts affecting Board service, committee service, officer interaction, compensation review, support review, public authority interface, finance-boundary matters, certification-boundary matters, procurement-neutrality matters, public-safe claims, data / AI / cyber controls, safeguards, GRF-facing inputs, GRA-facing technical inputs, and Nexus interfaces.
198.2.2 A director shall not use Board position to secure improper benefit, influence related-party transactions, favor sponsors or providers, influence public authority access, obtain technical access, shape publications, affect recognition inputs, affect finance-readiness inputs, influence procurement meaning, or collapse the Corporation’s public-good role into enterprise execution.
198.3 Officers
198.3.1 Each officer is a Covered Person. Officers shall comply with this Article when managing operations, signing instruments, approving expenditures, supervising staff, approving publications, approving data access, approving AI use, authorizing repository access, releasing software, interacting with public authorities, managing sponsors or providers, managing grants or donations, handling controlled rooms, and representing the Corporation.
198.3.2 Officer authority shall be suspended, restricted, or conditioned for any matter in which the officer has an unmanaged conflict.
198.4 Employees
198.4.1 Employees are Covered Persons where their work affects Corporation operations, evidence, methods, research, data, AI, cybersecurity, privacy, public-good software, technical assets, publications, public authority interfaces, safeguards, support relationships, contracts, controlled rooms, or public communications.
198.4.2 Employee conflicts shall be reviewed according to role, access, authority, reporting line, influence, and the affected matter.
198.5 Contractors and Consultants
198.5.1 Contractors and consultants are Covered Persons when they provide services, advice, technical work, research support, data processing, AI support, cyber support, legal or compliance support, public authority interface support, software development, publication support, sponsorship support, program support, or any work that may affect Corporation outputs or records.
198.5.2 Contractor or consultant status shall not be used to avoid conflict disclosure, confidentiality, IP, data, AI, cyber, safeguards, public-safe claims, records, or correction obligations.
198.6 Fellows
198.6.1 Fellows are Covered Persons where they conduct research, participate in Academy programs, access data or technical assets, publish under the Corporation’s name, participate in public authority learning, contribute to public-good software, join controlled rooms, or represent the Corporation’s work.
198.6.2 Fellow status shall not create governance authority, certification authority, recognition authority, finance-readiness authority, procurement authority, public authority status, or enterprise execution authority.
198.7 Advisors
198.7.1 Advisors are Covered Persons when they provide strategic, technical, legal, research, public authority, safeguards, community, fundraising, communications, software, data, AI, cyber, finance-boundary, certification-boundary, procurement-neutrality, or Nexus-interface advice.
198.7.2 Advisor participation shall be disclosed and bounded. Advisors shall not control Board decisions, officer decisions, publications, public authority interfaces, sponsor relationships, provider relationships, technical baselines, GRF-facing inputs, GRA-facing inputs, or Nexus-facing claims unless separately and lawfully authorized by competent record.
198.8 Volunteers
198.8.1 Volunteers are Covered Persons where they access Corporation materials, participate in work products, support events, assist programs, contribute technical work, interact with public authorities, handle community information, or represent the Corporation.
198.8.2 Volunteer status shall not exempt a person from confidentiality, conflict disclosure, data / AI / cyber controls, safeguards, records discipline, public-safe claims discipline, or non-retaliation obligations.
198.9 Seconded Personnel
198.9.1 Seconded personnel, hosted personnel, loaned personnel, embedded personnel, sponsored staff, public authority detailees, university secondees, laboratory secondees, provider secondees, sponsor secondees, and similar persons are Covered Persons where they support Corporation activity.
198.9.2 Secondment shall be subject to enhanced conflict review, including loyalty, reporting line, confidentiality, IP, data access, public authority boundary, sponsor non-control, provider neutrality, procurement neutrality, competition, and capture risks.
198.10 Committee Members
198.10.1 Committee members are Covered Persons for matters within the committee’s jurisdiction and for any matter affected by their committee access, recommendation, review, vote, deliberation, or public-facing role.
198.10.2 Committee membership shall not create authority beyond the committee charter and shall not shield members from conflict review.
198.11 Council Members
198.11.1 Council members, including Leadership Council members and other council participants, are Covered Persons where their advice, access, status, public profile, institutional affiliation, or participation may affect Corporation decisions, public meaning, or outputs.
198.11.2 Council membership shall not create fiduciary authority, officer authority, Board authority, public authority status, finance-readiness authority, certification authority, procurement authority, recognition authority, or authority to bind the Corporation.
198.12 Helix Council Participants
198.12.1 Helix Council participants are Covered Persons where they contribute sectoral, public authority, academic, provider, community, capital-reader, technical, media, workforce, or public-interest perspectives to Corporation work.
198.12.2 Helix Council participation shall be subject to conflict, competition, public authority capacity, finance-boundary, provider-neutrality, sponsor non-control, safeguards, and confidentiality controls.
198.13 Advisory Forum Participants
198.13.1 Advisory Forum participants are Covered Persons where their participation affects learning materials, public-safe reports, public authority understanding, community safeguards, technical outputs, or public communications.
198.13.2 Participation in an advisory forum shall not constitute consent, endorsement, approval, recognition, certification, finance-readiness, procurement approval, public authority adoption, or waiver unless expressly and lawfully recorded.
198.14 Working Group Members
198.14.1 Working group members are Covered Persons where they draft, review, test, advise, maintain, classify, document, or recommend Corporation work products.
198.14.2 Working group members shall disclose conflicts affecting technical drafts, methods, evidence, public-good software, open technical baselines, public-safe materials, standards-support materials, Academy materials, and Nexus-facing outputs.
198.15 Expert Panel Members
198.15.1 Expert panel members are Covered Persons where they review or advise on technical, scientific, legal, public authority, finance-boundary, certification-boundary, procurement-neutrality, safeguards, data / AI / cyber, or public-safe publication questions.
198.15.2 Expert panel outputs shall identify conflicts, limitations, dissent, assumptions, and review boundaries where material.
198.16 Peer Reviewers
198.16.1 Peer reviewers are Covered Persons for the work they review and for any related research, evidence, methods, publication, data, AI, cyber, sponsor, provider, public authority, safeguards, or technical conflict.
198.16.2 Peer review shall not be treated as independent unless reviewer conflicts have been disclosed and managed.
198.17 Model Reviewers
198.17.1 Model reviewers are Covered Persons where they review AI systems, model cards, system cards, benchmark cards, dataset cards, evaluation harnesses, inference workflows, agentic AI controls, retrieval systems, embeddings, fine-tuning restrictions, or model outputs.
198.17.2 Model reviewers shall disclose relationships with model providers, AI tool providers, cloud providers, data providers, benchmark owners, cyber vendors, and affected sponsors or providers.
198.18 Technical Contributors, Developers, Maintainers, Repository Participants, and Open-Source Contributors
198.18.1 Technical contributors, developers, maintainers, repository participants, and open-source contributors are Covered Persons where their contributions affect public-good software, technical baselines, repositories, release pipelines, schemas, APIs, SDKs, dashboards, benchmarks, models, datasets, documentation, or public-safe claims.
198.18.2 Maintainer or contributor status shall not create governance authority, public authority meaning, certification meaning, procurement meaning, provider preference, recognition meaning, finance-readiness meaning, or Nexus-compatible status.
198.19 Public Authority Participants Where Relevant
198.19.1 Public authority participants are Covered Persons where they participate in Corporation programs, committees, forums, controlled rooms, public authority learning sessions, data contributions, simulations, after-action reviews, or public-facing materials.
198.19.2 Public authority participants shall be capacity-classified where relevant and shall disclose public office, public employment, procurement role, grant role, regulatory role, public finance role, emergency management role, public infrastructure role, public records constraint, and government ethics constraint.
198.20 Sponsors, Donors, Funders, Providers, Vendors, Hosts, Partners, Universities, Laboratories, Communities, Tribal / Indigenous Representatives, Media Participants, and Enterprise Actors Where Relevant
198.20.1 Sponsors, donors, funders, providers, vendors, hosts, partners, universities, laboratories, communities, Tribal or Indigenous representatives, media participants, and enterprise actors are Covered Persons where their participation, support, access, contribution, public reference, technical dependency, public authority proximity, or relationship may influence Corporation work or public meaning.
198.20.2 Coverage shall be proportionate to role, access, influence, sensitivity, and risk. No support, contribution, participation, hosting, partnership, public authority connection, media visibility, or enterprise relationship shall exempt a person from this Article where conflict risk exists.
198.21 Members, Non-Voting Members, Supporters, Subscribers, Observers, Controlled-Room Participants, Data-Room Participants, Clean-Room Participants, and Program Participants Where Relevant
198.21.1 Members, non-voting members, supporters, subscribers, observers, controlled-room participants, data-room participants, clean-room participants, evidence-room participants, public authority room participants, no-download-room participants, and program participants are Covered Persons where access, participation, status, or influence may affect Corporation outputs, records, decisions, or public meaning.
198.21.2 Participation shall not create governance authority, public authority approval, finance-readiness, certification, recognition, procurement approval, provider preference, sponsor entitlement, or enterprise execution authority.
198.22 Related Parties, Affiliates, Sponsored Representatives, Coordinated Participants, and Beneficial Owners Where Relevant
198.22.1 Related Parties, affiliates, sponsored representatives, coordinated participants, beneficial owners, controlled entities, controlling persons, persons under common control, and persons acting in coordination with a Covered Person shall be treated as within the conflict architecture where their relationship may affect independence, public benefit, records, outputs, access, or institutional meaning.
198.22.2 The Corporation may aggregate related interests, coordinated interests, sponsored seats, affiliate interests, and common-control relationships to determine materiality, capture risk, independence, related-party status, or required mitigation.
198.23 Covered Person Records
198.23.1 The Corporation shall maintain Covered Person Records sufficient to identify persons subject to this Article, their role, capacity, affiliation, access class, disclosure status, certification status, conflict status, related-party status where disclosed or known, independence status where reviewed, training status where required, recusal status, access restrictions, mitigation measures, and closeout.
Section 199. Conflict Categories
199.1 Conflict Category Purpose
199.1.1 Conflict categories shall guide disclosure, review, classification, materiality assessment, mitigation, recusal, access restriction, independent approval, correction, and enforcement. Categories are not exclusive, and a single matter may involve multiple categories.
199.1.2 Conflict classification shall be based on substance, public meaning, practical influence, independence risk, public-benefit risk, and correctionability, not merely on legal labels or the subjective belief of the Covered Person.
199.2 Actual Conflict
199.2.1 An actual conflict exists where a Covered Person’s interests, duties, loyalties, relationships, compensation, authority, access, or external obligations in fact conflict with the Corporation’s public-benefit interest or with the Covered Person’s duties to the Corporation.
199.3 Potential Conflict
199.3.1 A potential conflict exists where circumstances may reasonably develop into an actual conflict or where a Covered Person’s relationship, interest, access, or obligation may affect a future decision, output, transaction, publication, or interface.
199.4 Perceived Conflict
199.4.1 A perceived conflict exists where a reasonable person could question the independence, neutrality, integrity, or public-benefit alignment of a Covered Person, decision, transaction, review, output, or relationship, even if no actual improper influence has occurred.
199.5 Financial Conflict
199.5.1 A financial conflict exists where a Covered Person or Related Party has a financial interest that may affect or appear to affect judgment. Financial interests include compensation, equity, debt, revenue share, royalties, fees, consulting payments, grants, donations, sponsorships, restricted funds, IP interests, contract rights, provider interests, host interests, investment interests, insurance interests, lending interests, underwriting interests, public finance interests, and related-party financial interests.
199.6 Institutional Conflict
199.6.1 An institutional conflict exists where a Covered Person’s duties, appointments, affiliations, employment, governance roles, advisory roles, public authority roles, sponsor roles, provider roles, host roles, university roles, laboratory roles, capital actor roles, national company roles, Project SPV roles, or enterprise roles may affect judgment or loyalty to the Corporation.
199.7 Fiduciary Conflict
199.7.1 A fiduciary conflict exists where a Covered Person owes fiduciary, trustee, director, officer, public office, professional, agency, or equivalent duties to another entity or person whose interests may differ from the Corporation’s interests.
199.8 Employment Conflict
199.8.1 An employment conflict exists where current, prospective, former, seconded, part-time, consulting, advisory, contractor, or dependent employment creates a risk that a Covered Person’s judgment, access, recommendations, or actions may serve an employer or prospective employer rather than the Corporation.
199.9 Contractual Conflict
199.9.1 A contractual conflict exists where a Covered Person or Related Party is bound by a contract, grant, sponsorship, confidentiality obligation, IP obligation, data obligation, publication obligation, exclusivity obligation, non-disclosure obligation, non-compete obligation where lawful, consulting arrangement, vendor arrangement, or other agreement that may affect service to the Corporation.
199.10 Research Conflict
199.10.1 A research conflict exists where financial, institutional, publication, authorship, funding, sponsor, provider, public authority, academic, reputational, data, AI, cyber, IP, or methodological interests may affect research design, conduct, review, interpretation, publication, correction, withdrawal, or retraction.
199.11 Evidence Conflict
199.11.1 An evidence conflict exists where a Covered Person or Related Party may benefit from selection, exclusion, classification, interpretation, confidence scoring, uncertainty disclosure, verification, validation, challenge, correction, or public presentation of evidence.
199.12 Methods Conflict
199.12.1 A methods conflict exists where a Covered Person or Related Party may benefit from the adoption, rejection, design, calibration, validation, benchmarking, scoring, publication, or correction of a method, model, evaluation harness, technical profile, or public-safe methodology.
199.13 Publication Conflict
199.13.1 A publication conflict exists where a Covered Person or Related Party may benefit from the timing, wording, authorship, attribution, omission, limitation, release, withholding, correction, withdrawal, retraction, takedown, or public characterization of a publication.
199.14 Data Conflict
199.14.1 A data conflict exists where control, ownership, access, contribution, processing, publication, commercial use, AI use, rights, restrictions, public authority status, protected knowledge status, or dependency involving data may affect judgment or institutional outputs.
199.15 AI Conflict
199.15.1 An AI conflict exists where relationships to AI systems, model providers, AI tool providers, model developers, training datasets, evaluation vendors, benchmarking tools, embeddings, retrieval systems, agentic AI systems, compute providers, or AI outputs may affect judgment, safety, publication, access, or technical claims.
199.16 Cybersecurity Conflict
199.16.1 A cybersecurity conflict exists where relationships to cybersecurity vendors, cloud providers, repository providers, vulnerability reporters, security researchers, incident responders, infrastructure operators, key managers, credential custodians, or affected systems may affect security review, incident handling, disclosure, remediation, or accountability.
199.17 Public Authority Conflict
199.17.1 A public authority conflict exists where public office, public employment, government contracting, public authority advisory service, procurement role, grant role, regulatory role, public finance role, emergency management role, public infrastructure role, public records duty, open meetings duty, government ethics rule, lobbying role, or public authority relationship may affect judgment or public meaning.
199.18 Sponsor Conflict
199.18.1 A sponsor conflict exists where sponsorship, sponsor benefits, sponsor recognition, sponsor expectations, sponsor renewal, sponsor technical contribution, sponsor public authority proximity, sponsor data contribution, or sponsor relationship may affect Corporation decisions, publications, access, technical outputs, or public meaning.
199.19 Donor or Funder Conflict
199.19.1 A donor or funder conflict exists where donations, grants, restricted funds, funder expectations, reporting pressure, donor restrictions, funding concentration, renewal expectations, or public acknowledgments may affect the Corporation’s independence, research integrity, publication independence, safeguards, or public-safe claims.
199.20 Provider or Vendor Conflict
199.20.1 A provider or vendor conflict exists where a provider, vendor, contractor, integrator, cloud provider, AI provider, cyber provider, data processor, software provider, repository provider, equipment provider, AI-RAN provider, O-RAN provider, DePIN provider, DLT provider, dashboard provider, or technical supplier may benefit from Corporation outputs, access, evaluation, public authority proximity, or public-safe claims.
199.21 Host Conflict
199.21.1 A host conflict exists where a host institution, site host, cloud host, data host, compute host, lab host, university host, public authority host, community host, infrastructure host, event host, or controlled-room host may influence access, outputs, publication, public authority perception, safeguards, or records.
199.22 Investor, Insurer, Lender, Underwriter, Bank, Public Finance, or Capital-Reader Conflict
199.22.1 A capital actor conflict exists where an investor, insurer, lender, underwriter, bank, public finance actor, rating actor, capital reader, fund, adviser, broker, dealer, finder, or finance-adjacent participant may benefit from or influence Corporation evidence, methods, public-safe reports, proof receipts, GRA-facing inputs, Docket support, Grid support, or Nexus-compatible claims.
199.23 National Company, State Operating Company, Regional Company, Project SPV, or Enterprise Stack Conflict
199.23.1 An enterprise-stack conflict exists where a national company, state operating company, regional company, Project SPV, provider, operator, asset owner, infrastructure vehicle, commercial delivery entity, or enterprise actor may benefit from Corporation outputs being treated as approval, authorization, recognition, finance-readiness, certification, procurement advantage, public authority adoption, or operational endorsement.
199.24 Community, Tribal / Indigenous, Local, Territorial, Cultural, Environmental, Protected Knowledge, Civil Rights, or Accessibility Conflict
199.24.1 A safeguards conflict exists where interests in research, publication, mapping, data release, AI use, public authority engagement, sponsor benefit, provider benefit, community access, public visibility, or institutional convenience may conflict with civil rights, accessibility, community safeguards, Tribal or Indigenous protocol, local knowledge, territorial knowledge, cultural knowledge, environmental knowledge, protected knowledge, consent, non-consent, attribution, withdrawal, grievance, remedy, non-retaliation, or do-no-harm.
199.25 Competition, Antitrust, Sanctions, Export-Control, Controlled Technology, National Security, Lobbying, Political Activity, Government Ethics, Procurement Integrity, Professional Boundary, or Regulatory-Perimeter Conflict
199.25.1 A regulatory-perimeter conflict exists where a matter implicates competition law, antitrust, sanctions, export-control, controlled technology, national security sensitivity, lobbying, political activity, government ethics, procurement integrity, professional advice, securities, investment advice, broker-dealer activity, finder activity, banking, lending, insurance, underwriting, rating, public finance, certification, accreditation, public warning, emergency command, or other regulated or externally reserved functions.
199.26 Conflict Category Records
199.26.1 The Corporation shall maintain Conflict Category Records identifying the conflict category, affected Covered Person, Related Party where applicable, affected matter, disclosure source, review authority, classification, materiality, mitigation, recusal, access restriction, approval or denial, correction, closeout, and archive status.
Section 200. Financial Conflicts
200.1 Financial Conflict Definition
200.1.1 A financial conflict exists where a Covered Person or Related Party has, expects, seeks, receives, controls, influences, or may reasonably be perceived as having a financial interest that could affect judgment, recommendation, review, access, approval, publication, technical release, public authority interface, support relationship, controlled-room admission, or public meaning.
200.2 Equity Interests
200.2.1 Equity interests include shares, membership interests, partnership interests, options, warrants, restricted stock, phantom equity, carried interests, profit interests, convertible instruments, token interests, digital asset interests, beneficial ownership, or other ownership rights in any entity whose interests may be affected by the Corporation.
200.3 Debt Interests
200.3.1 Debt interests include loans, notes, credit instruments, guarantees, lender relationships, borrower relationships, creditor rights, revenue-backed obligations, convertible debt, public finance obligations, infrastructure finance obligations, or other debt arrangements involving a Covered Person, Related Party, provider, sponsor, donor, funder, host, public authority, capital actor, national company, Project SPV, or enterprise actor.
200.4 Revenue Interests
200.4.1 Revenue interests include revenue shares, profit shares, carried interests, performance fees, royalty-like revenues, success payments, subscription shares, licensing shares, platform revenues, data revenues, software revenues, consulting revenues, or other variable economic interests tied to a person, project, provider, technology, publication, recognition, finance-readiness, certification, procurement outcome, or enterprise activity.
200.5 Royalty Interests
200.5.1 Royalty interests include payments based on IP, patents, copyrights, trademarks, trade secrets, datasets, models, software, benchmarks, technical baselines, dashboards, APIs, SDKs, schemas, documentation, licenses, standards-essential rights, or derivative works.
200.6 Fee Interests
200.6.1 Fee interests include professional fees, consulting fees, advisory fees, speaking fees, teaching fees, review fees, contractor fees, expert fees, management fees, grant administration fees, sponsorship management fees, referral fees, success fees, transaction fees, placement fees, and other compensation tied to services or outcomes.
200.7 Compensation Interests
200.7.1 Compensation interests include salary, bonus, stipend, fellowship support, honoraria, benefits, deferred compensation, severance, consulting compensation, contractor compensation, expense coverage, reimbursement, travel support, housing support, relocation support, cloud credits, compute credits, data access, tool access, software licenses, and in-kind compensation.
200.8 Consulting Interests
200.8.1 Consulting interests include paid or unpaid consulting, advisory, technical support, public authority support, provider support, sponsor support, research support, grant support, strategy support, standards support, finance-boundary support, certification-boundary support, procurement support, public relations support, media support, or enterprise support.
200.9 Finder, Referral, Success, Placement, Commission, Contingent, or Transaction-Based Compensation Interests
200.9.1 Finder, referral, success, placement, commission, contingent, or transaction-based compensation interests are presumptively high-risk where they relate to grants, donations, sponsorships, capital, insurance, lending, underwriting, public finance, procurement, provider selection, certification, recognition, finance-readiness, Project SPVs, national companies, enterprise actors, or public authority access.
200.9.2 No such interest may be approved unless lawful, expressly authorized, independently reviewed, tax-reviewed where required, counsel-reviewed where required, public-benefit justified, and recorded. No such interest may reward prohibited functions.
200.10 Grant, Donation, Sponsorship, or Restricted Fund Interests
200.10.1 Grant, donation, sponsorship, or restricted fund interests include direct or indirect interests in receiving, renewing, administering, reporting, restricting, acknowledging, allocating, or benefiting from support.
200.10.2 Such interests shall be reviewed for donor control, sponsor control, funder control, private benefit, research influence, public authority access purchase, provider preference, publication influence, technical-baseline influence, and correction suppression.
200.11 IP, Patent, Copyright, Trademark, Trade Secret, Data, Model, Software, Dataset, Benchmark, Technical Baseline, or Repository Interests
200.11.1 Financial interests in IP, data, models, software, datasets, benchmarks, technical baselines, repositories, dashboards, reference architectures, APIs, SDKs, schemas, or related technical assets shall be disclosed where affected by Corporation action.
200.11.2 Such interests shall be reviewed for anti-enclosure, public-good asset integrity, licensing, chain of title, standards-essential risks, royalty interests, commercial-use claims, provider preference, certification overclaim, procurement overclaim, and Nexus-compatible claim risks.
200.12 Provider, Vendor, Contractor, Host, Cloud Provider, AI Provider, Cybersecurity Provider, Data Processor, or Repository Provider Interests
200.12.1 A Covered Person shall disclose any financial interest in or compensation from a provider, vendor, contractor, host, cloud provider, AI provider, cybersecurity provider, data processor, repository provider, software provider, equipment provider, or technical supplier whose goods, services, data, tools, or platforms are used, reviewed, referenced, compared, or affected by Corporation activity.
200.13 Investor, Insurer, Lender, Underwriter, Bank, Public Finance Actor, Capital Reader, Fund, SPV, National Company, or Project Company Interests
200.13.1 A Covered Person shall disclose financial interests involving investors, insurers, lenders, underwriters, banks, public finance actors, capital readers, funds, SPVs, national companies, state operating companies, regional companies, Project SPVs, project companies, or capital-adjacent entities where Corporation outputs could affect perceived readiness, risk, maturity, credibility, insurability, financeability, routeability, or public-sector suitability.
200.14 Family, Household, Affiliate, Employer, Client, Beneficial Owner, Controlled Entity, or Related-Party Financial Interests
200.14.1 Financial interests of family members, household members, affiliates, employers, clients, beneficial owners, controlled entities, commonly controlled entities, and Related Parties shall be disclosed where such interests may affect or appear to affect a Covered Person’s judgment.
200.15 Materiality Assessment
200.15.1 Materiality shall be assessed based on amount, nature, timing, dependency, relationship, role, influence, public meaning, access, sensitivity, affected decision, affected output, public trust risk, public authority risk, finance-boundary risk, certification-boundary risk, procurement risk, provider-neutrality risk, sponsor-control risk, safeguards risk, data / AI / cyber risk, tax risk, and correctionability.
200.16 Disclosure Requirement
200.16.1 A Covered Person shall disclose financial conflicts annually, initially upon appointment or engagement where required, and promptly upon becoming aware of any event-based financial conflict.
200.17 Recusal and Mitigation
200.17.1 A financial conflict may require disclosure, recusal, access restriction, role restriction, independent review, comparability review, fairness determination, Board approval, counsel review, tax review, public-safe disclosure, controlled disclosure, denial, refusal, return, termination, repayment, correction, or other mitigation.
200.18 Financial Conflict Records
200.18.1 The Corporation shall maintain Financial Conflict Records identifying the financial interest, Covered Person, Related Party, affected matter, value or estimated value where known, materiality assessment, review authority, determination, mitigation, recusal, access restriction, approval, denial, monitoring, correction, and closeout.
Section 201. Institutional Conflicts
201.1 Institutional Conflict Definition
201.1.1 An institutional conflict exists where a Covered Person’s affiliation, office, employment, appointment, governance role, advisory role, fiduciary role, public authority role, sponsor role, provider role, host role, donor or funder role, capital actor role, university role, laboratory role, media role, community role, Tribal or Indigenous interface role, national company role, Project SPV role, enterprise role, or Nexus-system role may affect judgment, loyalty, public meaning, or institutional independence.
201.2 Role in GCRI Canada
201.2.1 A role in GCRI Canada shall be disclosed where the Covered Person participates in or influences GCRI US matters involving North America interfaces, cross-border records, shared doctrine, public-good software, technical baselines, data sharing, public authority learning, publication, public-safe claims, legal separateness, or Nexus compatibility.
201.2.2 Shared mission shall not be treated as shared authority, shared treasury, shared liability, agency, merger, branch status, or automatic permission to bind either entity.
201.3 Role in Other GCRI Entity
201.3.1 A role in any other GCRI entity shall be disclosed where it may affect GCRI US governance, funding, records, software, technical assets, public authority interfaces, publications, controlled vocabulary, data, AI, cyber, safeguards, or Nexus-facing work.
201.4 Role in The Global Risks Forum (GRF)
201.4.1 A role in The Global Risks Forum (GRF) shall be disclosed where the Covered Person participates in matters involving registry, recognition, maturity records, standing, claims discipline, stakeholder formation, public-safe reporting, public-facing legitimacy, Docket, Grid, GRF-facing inputs, or public claims.
201.4.2 GCRI US evidence, methods, observability, ontology, public-good software, or technical-baseline support shall not be treated as GRF recognition or maturity action.
201.5 Role in The Global Risks Alliance (GRA)
201.5.1 A role in The Global Risks Alliance (GRA) shall be disclosed where the Covered Person participates in matters involving finance-readiness, capital-readability, proof packs, insurance-readiness, diligence translation, RNFD, NFD, UNFSD, capital-reader rooms, public finance readers, investors, insurers, lenders, underwriters, or GRA-facing technical inputs.
201.5.2 GCRI US technical input shall not be treated as finance-readiness, insurance-readiness, rating, underwriting, lending approval, investment advice, public finance approval, or capital execution.
201.6 Role in Nexus Standards or Protocol Authority
201.6.1 A role in Nexus Standards, a protocol authority, standards body, conformance body, technical profile authority, or similar body shall be disclosed where the matter involves standards support, technical baselines, schemas, APIs, SDKs, proof receipts, role keys, interoperability, compatibility, conformance, certification, or Nexus-compatible terminology.
201.7 Role in Nexus Network, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, or Nexus Competence Cells
201.7.1 A role in any Nexus body, environment, program, platform, rail, grid, academy, observatory, risk management, universe, or competence cell shall be disclosed where the Covered Person participates in related GCRI US evidence, methods, public authority learning, public-good software, technical baselines, safeguards, or public-safe claims.
201.8 Role in Global, Regional, National, State, Territorial, Tribal, Local, or Sector Nexus Consortium
201.8.1 A role in a Global Nexus Consortium, Regional Nexus Consortium, National Nexus Consortium, state, territorial, Tribal, local, or sector Nexus consortium shall be disclosed where the matter may affect consortium formation, stakeholder formation, public authority engagement, national working groups, competence cells, public-good stack interfaces, or enterprise-stack interfaces.
201.9 Role in National Company, State Operating Company, Regional Company, Project SPV, Provider, Vendor, Host, Sponsor, Donor, Funder, Investor, Insurer, Lender, Bank, Public Finance Actor, University, Laboratory, Public Authority, Community Organization, Tribal / Indigenous Organization, Civil Society, Media, or Partner Entity
201.9.1 Such roles shall be disclosed where they may affect or appear to affect Corporation judgment, technical outputs, publications, public authority learning, support acceptance, provider neutrality, sponsor non-control, finance-boundary discipline, certification-boundary discipline, procurement neutrality, safeguards, protected knowledge, or Nexus-facing claims.
201.10 Multiple Fiduciary or Governance Roles
201.10.1 A Covered Person holding multiple fiduciary, governance, trustee, officer, public office, advisory, committee, council, or management roles shall disclose all roles that may intersect with the Corporation’s work.
201.10.2 Multiple roles may be permitted only where lawfully managed through disclosure, recusal, role segregation, independent review, capacity labeling, compatibility notes, divergence logs, or access restrictions.
201.11 Dual Loyalty
201.11.1 Dual loyalty exists where a Covered Person owes loyalty to another institution whose interests may diverge from the Corporation’s public-benefit purpose. Dual loyalty shall be disclosed and reviewed even where the Covered Person believes alignment exists.
201.12 Conflicting Institutional Mandates
201.12.1 Conflicting mandates include obligations to advance another organization’s strategy, funding goals, regulatory goals, public authority goals, sponsor goals, provider goals, publication goals, enterprise goals, finance goals, certification goals, procurement goals, or political goals in ways that may conflict with GCRI US.
201.13 Shared Personnel, Shared Systems, Shared Records, Shared Funding, Shared Programs, Shared Rooms, or Shared Publications
201.13.1 Shared personnel, shared systems, shared records, shared funding, shared programs, shared rooms, or shared publications shall be disclosed and reviewed for legal separateness, agency risk, confidentiality, privilege, data protection, IP ownership, public authority confusion, sponsor control, provider preference, public-safe claims, and correctionability.
201.14 Institutional Capture Risk
201.14.1 Institutional capture risk exists where another institution may acquire practical control over the Corporation’s agenda, records, outputs, funding, staffing, rooms, software, public authority access, publications, technical baselines, controlled vocabulary, or public meaning.
201.15 Disclosure, Recusal, Role Segregation, Interface Agreement, Compatibility Note, or Divergence Log
201.15.1 Institutional conflicts may be managed through disclosure, recusal, role segregation, access restriction, independent review, interface agreement, compatibility note, divergence log, public-safe limitation, controlled disclosure, or Board review.
201.16 Institutional Conflict Records
201.16.1 The Corporation shall maintain Institutional Conflict Records identifying the institution, Covered Person, role, affected matter, conflict type, role-separation risk, public authority risk, finance-boundary risk, certification-boundary risk, procurement-neutrality risk, safeguards risk, mitigation, recusal, compatibility note, divergence log, and closeout.
Section 202. Research, Evidence, Methods, and Publication Conflicts
202.1 Research Conflict Definition
202.1.1 A research conflict exists where a Covered Person’s financial, institutional, professional, academic, publication, authorship, grant, sponsor, provider, public authority, political, reputational, data, AI, cyber, IP, or personal interest may affect research design, conduct, interpretation, review, publication, correction, or archive.
202.2 Evidence Conflict Definition
202.2.1 An evidence conflict exists where a Covered Person or Related Party may benefit from the selection, exclusion, classification, validation, verification, confidence scoring, uncertainty disclosure, interpretation, presentation, challenge, correction, or suppression of evidence.
202.3 Methods Conflict Definition
202.3.1 A methods conflict exists where a Covered Person or Related Party may benefit from the adoption, rejection, calibration, validation, benchmarking, scoring, publication, withdrawal, correction, or public characterization of a method, model, protocol, benchmark, technical profile, evaluation harness, or public-safe methodology.
202.4 Publication Conflict Definition
202.4.1 A publication conflict exists where a Covered Person or Related Party may benefit from the timing, framing, authorship, attribution, omission, limitation, release, withholding, correction, withdrawal, retraction, takedown, archive, or public characterization of a publication or public-safe output.
202.5 Conflicts Affecting Research Design
202.5.1 Research design shall not be shaped to achieve sponsor-desired outcomes, provider-preferred outcomes, donor-friendly narratives, public authority preferences, finance-facing outcomes, recognition-facing outcomes, certification-facing outcomes, procurement-facing outcomes, or enterprise-stack advantage.
202.6 Conflicts Affecting Hypothesis Selection
202.6.1 Hypotheses shall be selected according to public-benefit relevance, evidence need, methods discipline, systemic risk significance, public-safe utility, safeguards, and research integrity, not according to external pressure, funding preference, publication incentives, or market signaling.
202.7 Conflicts Affecting Data Selection
202.7.1 Data selection shall be reviewed where data sources, data owners, providers, sponsors, public authorities, communities, Tribal or Indigenous data stewards, AI vendors, cyber vendors, or technical dependencies may affect inclusion, exclusion, weighting, transformation, or interpretation.
202.8 Conflicts Affecting Evidence Interpretation
202.8.1 Evidence interpretation shall distinguish facts, assumptions, uncertainty, limitations, model outputs, automated signals, public authority inputs, sponsor inputs, provider inputs, and human judgment. Conflicted persons shall not control interpretation where the conflict may affect meaning.
202.9 Conflicts Affecting Confidence Scoring
202.9.1 Confidence scoring shall not be manipulated to favor a project, provider, sponsor, public authority, capital actor, national company, Project SPV, recognition pathway, finance-readiness pathway, certification pathway, procurement pathway, or public-facing narrative.
202.10 Conflicts Affecting Uncertainty Disclosure
202.10.1 Uncertainty shall not be concealed, softened, exaggerated, or selectively disclosed to support fundraising, sponsor satisfaction, provider positioning, public authority comfort, market signaling, publication impact, recognition, finance-readiness, certification, procurement, or enterprise execution.
202.11 Conflicts Affecting Method Selection
202.11.1 Method selection shall be based on fit, validity, repeatability, auditability, public-safe use, safeguards, data rights, technical limits, and correctionability. Conflicted method selection shall require disclosure and independent review.
202.12 Conflicts Affecting Benchmark Design
202.12.1 Benchmark design shall not be structured to advantage a provider, vendor, sponsor, technology, dataset, model, cloud service, AI system, cyber tool, AI-RAN component, O-RAN component, DePIN system, DLT system, dashboard, or enterprise actor.
202.13 Conflicts Affecting Model Evaluation
202.13.1 Model evaluation shall account for data provenance, training restrictions, evaluation independence, bias, limitations, known failure modes, hallucinated authority, privacy risk, cyber risk, public authority risk, protected knowledge risk, and human review.
202.14 Conflicts Affecting Technical Baseline Drafting
202.14.1 Technical baseline drafting shall not be controlled by providers, sponsors, donors, funders, hosts, standards participants, public authorities, national companies, Project SPVs, or enterprise actors whose interests may be affected by baseline language.
202.15 Conflicts Affecting Public-Good Software Roadmaps
202.15.1 Public-good software roadmaps shall not be shaped to favor a provider, sponsor, cloud platform, AI tool, proprietary system, controlled dependency, enterprise strategy, or procurement advantage unless the choice is public-benefit justified, reviewed, recorded, and bounded.
202.16 Conflicts Affecting Publication Timing
202.16.1 Publication timing shall not be accelerated, delayed, withheld, timed, embargoed, or sequenced to serve sponsor renewal, provider marketing, donor comfort, public authority politics, finance signaling, recognition timing, certification timing, procurement timing, fundraising, media strategy, or enterprise advantage.
202.17 Conflicts Affecting Publication Conclusions
202.17.1 Publication conclusions shall be based on evidence, methods, limitations, confidence, uncertainty, safeguards, and public-safe language. Conclusions shall not be purchased, negotiated, suppressed, softened, exaggerated, or rewritten to satisfy external interests.
202.18 Sponsor, Provider, Donor, Funder, Host, Public Authority, University, Laboratory, or Enterprise Influence on Research or Publication
202.18.1 Influence by sponsors, providers, donors, funders, hosts, public authorities, universities, laboratories, or enterprise actors shall be disclosed, reviewed, and controlled where it may affect research design, data access, methods, review, publication, correction, public authority references, or public-safe claims.
202.19 Required Disclosure in Internal Records and Public-Safe Publications Where Appropriate
202.19.1 Conflicts affecting research, evidence, methods, or publication shall be disclosed in internal records and, where public trust, public-safe reliance, research integrity, sponsor transparency, provider transparency, public authority transparency, or publication integrity requires, in public-safe publications.
202.20 Independent Review, Peer Review, Recusal, Method Note, Controlled Annex, Correction, Supersession, Withdrawal, or Retraction
202.20.1 Research, evidence, methods, and publication conflicts may require independent review, peer review, model review, red-team review, recusal, method note, sponsor disclosure, provider disclosure, controlled annex, public-safe limitation, correction, supersession, withdrawal, retraction, takedown, or archive.
202.21 Research, Evidence, Methods, and Publication Conflict Records
202.21.1 The Corporation shall maintain Research, Evidence, Methods, and Publication Conflict Records identifying conflicts, disclosures, reviewers, recusals, affected outputs, method notes, peer review, sponsor or provider influence, public authority influence, safeguards review, public-safe disclosures, corrections, supersessions, withdrawals, retractions, takedowns, and closeout.
Section 203. Data, AI, Cybersecurity, Privacy, and Technical Asset Conflicts
203.1 Data Conflict Definition
203.1.1 A data conflict exists where a Covered Person’s or Related Party’s relationship to a dataset, data source, data owner, data processor, data broker, public authority data contributor, community data steward, Tribal or Indigenous data steward, protected knowledge holder, data platform, dashboard, sensor system, or data-dependent output may affect judgment, access, processing, interpretation, publication, correction, or deletion.
203.2 AI Conflict Definition
203.2.1 An AI conflict exists where a Covered Person’s or Related Party’s relationship to an AI system, model developer, AI tool provider, model provider, evaluation vendor, training dataset, fine-tuning process, embedding system, retrieval system, agentic AI workflow, compute provider, model output, or AI-enabled publication workflow may affect judgment, access, approval, interpretation, publication, or correction.
203.3 Cybersecurity Conflict Definition
203.3.1 A cybersecurity conflict exists where a Covered Person’s or Related Party’s relationship to cybersecurity tools, vendors, incident responders, vulnerability reporters, cloud providers, repository providers, credential systems, key systems, domains, infrastructure operators, or security findings may affect review, containment, disclosure, remediation, or accountability.
203.4 Privacy Conflict Definition
203.4.1 A privacy conflict exists where a Covered Person or Related Party has an interest that may affect decisions about personal information, sensitive personal information, health-sensitive information, children’s data, rights-bearing data, public authority data, community-protected data, cross-border data, retention, deletion, redaction, aggregation, consent, or breach response.
203.5 Technical Asset Conflict Definition
203.5.1 A technical asset conflict exists where a Covered Person or Related Party has an interest in public-good software, open technical baselines, repositories, source code, APIs, SDKs, schemas, dashboards, datasets, models, benchmarks, test harnesses, reference architectures, technical profiles, proof receipts, role keys, smart licenses, SBOMs, signing systems, or technical documentation.
203.6 Data Access Conflict
203.6.1 A data access conflict exists where access to data may benefit or appear to benefit a Covered Person or Related Party, including through research advantage, commercial advantage, public authority advantage, provider advantage, sponsor advantage, publication advantage, AI training advantage, or enterprise-stack advantage.
203.7 Data Processing Conflict
203.7.1 A data processing conflict exists where processing choices, transformation, aggregation, redaction, linkage, de-identification, re-identification, retention, deletion, AI use, publication, or transfer may benefit a Covered Person or Related Party.
203.8 Dataset Contribution Conflict
203.8.1 A dataset contribution conflict exists where a contributor may benefit from the inclusion, exclusion, classification, weighting, public presentation, public-safe publication, model use, or proof receipt treatment of a contributed dataset.
203.9 Model Provider Conflict
203.9.1 A model provider conflict exists where a model provider, model developer, model evaluator, AI vendor, or related participant may benefit from Corporation review, adoption, benchmarking, reference, public-safe reporting, public authority learning, or technical baseline use of the model.
203.10 AI Tool Provider Conflict
203.10.1 An AI tool provider conflict exists where a provider of AI tools, agents, copilots, retrieval systems, embedding systems, translation systems, summarization tools, coding tools, or evaluation tools may influence or benefit from Corporation use, approval, publication, or public characterization.
203.11 Cloud Provider Conflict
203.11.1 A cloud provider conflict exists where reliance on a cloud provider creates financial, technical, operational, cyber, data localization, sovereign compute, public authority, sponsor, provider, public-safe, or continuity risks.
203.12 Cybersecurity Vendor Conflict
203.12.1 A cybersecurity vendor conflict exists where a vendor may influence or benefit from vulnerability classification, incident handling, remediation prioritization, security posture claims, public-safe notices, or procurement-adjacent language.
203.13 Repository Provider Conflict
203.13.1 A repository provider conflict exists where repository hosting, access, permissions, dependency, platform terms, moderation, issue control, CI/CD, release tooling, archival status, or public visibility may affect technical assets or institutional records.
203.14 Data Processor Conflict
203.14.1 A data processor conflict exists where a processor’s financial, technical, contractual, geographic, public authority, AI, cyber, or commercial interests may affect processing integrity, confidentiality, privacy, deletion, publication, or public-safe reporting.
203.15 Public-Good Software Maintainer Conflict
203.15.1 A public-good software maintainer conflict exists where a maintainer’s employer, sponsor, provider relationship, client, IP interest, consulting interest, technical preference, repository authority, public profile, or enterprise role may affect roadmap, code review, dependency selection, release approval, licensing, security, or compatibility claims.
203.16 Open-Source Dependency Conflict
203.16.1 An open-source dependency conflict exists where a dependency, maintainer, sponsor, provider, license, vulnerability, ownership, commercial interest, or standards-essential right may affect public-good software integrity, security, licensing, anti-enclosure, or public-safe use.
203.17 Vulnerability Disclosure Conflict
203.17.1 A vulnerability disclosure conflict exists where a person or entity may benefit from delaying, suppressing, exaggerating, monetizing, publicizing, or controlling disclosure of a vulnerability affecting Corporation systems, public-good software, technical baselines, repositories, public authority materials, protected knowledge, or public-safe outputs.
203.18 Secure Release Conflict
203.18.1 A secure release conflict exists where a Covered Person or Related Party may benefit from release timing, feature inclusion, vulnerability suppression, dependency selection, signing, SBOM treatment, publication wording, compatibility claims, or release approval.
203.19 IP, License, Patent, Standards-Essential, Royalty, Anti-Enclosure, or Commercial Use Conflict
203.19.1 IP and licensing conflicts shall be disclosed where rights, royalties, patents, standards-essential claims, trade secrets, copyright, trademarks, data rights, model rights, commercial-use restrictions, open-source obligations, anti-enclosure provisions, or licensing choices may affect public-good technical assets.
203.20 Access Restriction, Independent Review, Segregation of Duties, Code Owner Review, Clean-Room Controls, or Technical Quarantine
203.20.1 Data, AI, cybersecurity, privacy, and technical asset conflicts may require access restriction, independent review, segregation of duties, code owner review, clean-room controls, technical quarantine, repository freeze, release freeze, model freeze, dataset freeze, credential rotation, key rotation, or incident escalation.
203.21 Data, AI, Cybersecurity, Privacy, and Technical Asset Conflict Records
203.21.1 The Corporation shall maintain Data, AI, Cybersecurity, Privacy, and Technical Asset Conflict Records identifying conflict type, affected systems, affected data, affected models, affected repositories, affected technical assets, access restrictions, reviewers, mitigation, technical controls, correction, and closeout.
Section 204. Public Authority, Government Ethics, Lobbying, Political Activity, Procurement Integrity, and Public-Sector Conflicts
204.1 Public Authority Conflict Definition
204.1.1 A public authority conflict exists where a Covered Person’s current, former, prospective, or related role with a public authority, public office, public employer, public contractor, public university, public laboratory, public infrastructure operator, regulator, public finance actor, procurement actor, grant actor, emergency management actor, public health actor, public safety actor, or public sector body may affect or appear to affect judgment for the Corporation.
204.2 Federal Public Authority Conflict
204.2.1 A federal public authority conflict exists where a Covered Person’s federal role, federal contract, federal grant, federal advisory position, federal regulatory role, federal procurement role, federal employment, federal public finance role, federal data access, or federal confidentiality obligation may intersect with Corporation activity.
204.3 State Public Authority Conflict
204.3.1 A state public authority conflict exists where a Covered Person’s state role, state employment, state procurement role, state grant role, state regulatory role, state public finance role, state emergency management role, state infrastructure role, or state data access may affect Corporation activity or public meaning.
204.4 Territorial and District of Columbia Public Authority Conflict
204.4.1 A territorial or District of Columbia public authority conflict exists where a Covered Person’s role in Puerto Rico, Guam, the U.S. Virgin Islands, American Samoa, the Northern Mariana Islands, the District of Columbia, or related public-sector contexts may affect Corporation activity, public authority meaning, data handling, public-safe reporting, or localization.
204.5 Tribal and Indigenous Government Conflict
204.5.1 A Tribal or Indigenous government conflict exists where a Covered Person’s role with, service to, representation of, or relationship with a Tribal Nation, Indigenous government, Indigenous institution, Indigenous data steward, Indigenous knowledge holder, or Indigenous community may affect Corporation activity.
204.5.2 Such conflicts shall be handled with respect for sovereignty, self-determination, governance protocols, consent, non-consent, protected knowledge, Indigenous data safeguards, cultural restrictions, attribution, non-attribution, withdrawal, and public-safe mapping.
204.6 Local, County, Municipal, Metropolitan, Utility, Port, Public Health, Emergency Management, Public Safety, Public Works, Telecom, Energy, Water, Food, Cyber, and Infrastructure Public Authority Conflict
204.6.1 A local or infrastructure public authority conflict exists where a Covered Person’s role with local, county, municipal, metropolitan, utility, port, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, transportation, or infrastructure bodies may affect Corporation learning, data, publications, public authority references, or public-safe outputs.
204.7 Public Employment Conflict
204.7.1 Public employment shall be disclosed where it may affect Corporation work, public authority participation, public records, procurement, grants, government ethics, public statements, confidentiality, or official-capacity references.
204.8 Public Office Conflict
204.8.1 Public office shall be disclosed where elected, appointed, advisory, or official status may affect or appear to affect the Corporation’s governance, public authority interfaces, publications, public-safe reports, funding, public statements, or external reliance.
204.9 Government Contractor Conflict
204.9.1 Government contractor roles shall be disclosed where a Covered Person or Related Party may benefit from public authority proximity, procurement knowledge, public authority learning, controlled-room access, public-safe reports, technical baselines, or provider-neutrality language.
204.10 Public Grant Conflict
204.10.1 Public grant conflicts shall be disclosed where a Covered Person participates in grant application, award, administration, reporting, compliance, evaluation, renewal, publication, or public authority interface matters involving the Corporation.
204.11 Public Procurement Conflict
204.11.1 Public procurement conflicts shall be disclosed and managed where a Covered Person’s role, knowledge, employer, client, provider relationship, sponsor relationship, or public authority connection may affect procurement, bid specifications, vendor selection, provider introductions, procurement-safe language, or public authority reliance.
204.12 Revolving-Door Conflict
204.12.1 A revolving-door conflict exists where a Covered Person’s current, former, or prospective public authority, provider, sponsor, vendor, capital actor, national company, Project SPV, or enterprise role may create improper influence, privileged access, confidential-information misuse, procurement risk, or public authority confusion.
204.13 Lobbying Registration or Activity Conflict
204.13.1 Lobbying registration, lobbying activity, policy advocacy, legislative advocacy, regulatory advocacy, or public authority influence activity shall be disclosed where it intersects with Corporation work, public statements, public authority learning, grant activity, procurement, public funding, public finance, or regulated-perimeter matters.
204.14 Political Campaign or Partisan Activity Conflict Where Applicable
204.14.1 Political campaign, partisan, electoral, candidate, party, PAC, ballot, referendum, or political activity shall be disclosed where it may affect or appear to affect Corporation neutrality, public authority engagement, public-benefit purpose, tax posture, public statements, public-safe reports, or public trust.
204.15 Government Ethics, Gifts, Honoraria, Travel, Procurement Integrity, Public Records, FOIA, Sunshine, Open Meetings, and Public Sector Confidentiality Conflict
204.15.1 Government ethics, gifts, honoraria, travel, procurement integrity, public records, FOIA, sunshine, open meetings, and public sector confidentiality obligations shall be disclosed and respected in all public authority interfaces.
204.16 Public Authority Data Conflict
204.16.1 Public authority data conflicts shall be disclosed where public authority data, restricted public records, cyber-sensitive information, infrastructure-sensitive information, health-sensitive data, procurement information, regulatory information, emergency management information, or confidential public-sector information may be used, processed, published, mapped, or referenced.
204.17 Public Authority Reference Conflict
204.17.1 Public authority reference conflicts shall be disclosed where a Covered Person may benefit from naming, quoting, displaying, implying, or associating a public authority with the Corporation, a publication, a dashboard, a controlled room, a public authority room, a sponsor, a provider, a project, a National Consortium Company, a Project SPV, or a Nexus-facing output.
204.18 No Use of Public Authority Role to Create Endorsement, Adoption, Funding, Procurement, Regulation, Public Warning, Emergency Command, Public Finance Approval, Sovereign Obligation, or Public-Private Partnership
204.18.1 No Covered Person shall use a public authority role, public authority title, public authority attendance, public authority data, public authority correspondence, public authority room, official-capacity participation, public authority seal, public authority logo, public authority quotation, public authority silence, or public authority proximity to imply endorsement, adoption, funding, procurement, regulation, public warning, emergency command, public finance approval, sovereign obligation, public-private partnership, or official decision.
204.19 Public Authority Conflict Mitigation, Recusal, Capacity Classification, Reference Control, and Correction
204.19.1 Public authority conflicts may require capacity classification, recusal, access restriction, public authority reference review, government ethics review, procurement integrity review, public records review, public-safe limitation language, counsel review, controlled correction, public correction, withdrawal, takedown, or Board review.
204.20 Public Authority and Government Ethics Conflict Records
204.20.1 The Corporation shall maintain Public Authority and Government Ethics Conflict Records identifying public authority roles, capacity classifications, public authority references, ethics reviews, procurement reviews, lobbying reviews, public records considerations, data restrictions, recusals, mitigation, corrections, and closeout.
Section 205. Sponsor, Donor, Funder, Provider, Host, Enterprise, and Capital Actor Conflicts
205.1 Sponsor Conflict Definition
205.1.1 A sponsor conflict exists where a sponsorship, sponsor benefit, sponsor acknowledgment, sponsor access, sponsor renewal, sponsor technical contribution, sponsor data contribution, sponsor public authority proximity, sponsor-controlled platform, sponsor-provided staff, sponsor-hosted room, or sponsor expectation may affect or appear to affect Corporation governance, research, evidence, methods, publication, public authority learning, public-good software, technical baselines, public-safe claims, GRF-facing inputs, GRA-facing technical inputs, Nexus-facing claims, or correction.
205.2 Donor Conflict Definition
205.2.1 A donor conflict exists where donation, donor restriction, donor recognition, donor relationship, donor renewal expectation, donor-advised support, donor public authority relationship, donor enterprise relationship, donor family relationship, or donor public profile may affect or appear to affect the Corporation’s judgment, independence, public statements, publications, programs, or records.
205.3 Funder Conflict Definition
205.3.1 A funder conflict exists where a grantor, foundation, public funder, philanthropic funder, development funder, research funder, challenge funder, Academy funder, technical asset funder, or restricted fund source may influence or appear to influence agenda, outputs, evidence, methods, publication, data access, public authority access, safeguards, or correction.
205.4 Provider Conflict Definition
205.4.1 A provider conflict exists where a provider, vendor, contractor, integrator, cloud provider, AI provider, cybersecurity provider, data provider, dashboard provider, software provider, equipment provider, sensor provider, AI-RAN provider, O-RAN provider, DePIN provider, DLT provider, blockchain provider, digital twin provider, geospatial provider, or enterprise provider may benefit from or influence Corporation action.
205.5 Host Conflict Definition
205.5.1 A host conflict exists where a host institution, event host, site host, lab host, data host, cloud host, compute host, repository host, public authority host, community host, university host, laboratory host, facility host, controlled-room host, or infrastructure host may influence access, outputs, publications, public authority perception, public-safe claims, or records.
205.6 Enterprise Actor Conflict Definition
205.6.1 An enterprise actor conflict exists where a commercial actor, provider, operator, national company, state operating company, regional company, Project SPV, asset owner, deployment vehicle, infrastructure operator, investor-backed entity, or enterprise-stack participant may benefit from Corporation outputs being interpreted as approval, recommendation, recognition, finance-readiness, certification, procurement advantage, public authority adoption, or operational authorization.
205.7 Investor, Insurer, Lender, Underwriter, Bank, Public Finance Actor, and Capital Reader Conflict Definition
205.7.1 A capital actor conflict exists where a capital reader, investor, insurer, lender, underwriter, bank, public finance actor, rating actor, fund, adviser, broker, dealer, finder, guarantee provider, blended finance actor, development finance actor, MDB / DFI / IFI participant, or finance-adjacent actor may influence or benefit from Corporation evidence, methods, public-safe reports, proof receipts, GRA-facing technical inputs, Docket support, Grid support, public authority rooms, or Nexus-facing claims.
205.8 Sponsored Seat Conflict
205.8.1 A sponsored seat conflict exists where sponsorship, donation, funding, hosting, in-kind contribution, technical contribution, or public support is connected to participation in a Board-adjacent body, committee, council, forum, working group, panel, controlled room, public authority room, Academy program, or Nexus-facing structure.
205.8.2 Sponsored seats shall not create governance control, agenda control, vote control, access purchase, public authority proximity purchase, provider preference, recognition, finance-readiness, certification, procurement advantage, or public-safe claims advantage.
205.9 Sponsored Research Conflict
205.9.1 Sponsored research conflicts shall be reviewed where sponsors, donors, funders, providers, hosts, public authorities, universities, laboratories, or enterprise actors provide support for research that may affect findings, methods, data, publication, correction, public authority learning, or public-safe claims.
205.10 Sponsored Public Authority Access Conflict
205.10.1 Sponsored public authority access conflict exists where a sponsor, donor, funder, provider, host, capital actor, national company, Project SPV, or enterprise actor may gain or appear to gain public authority proximity, public authority meeting access, public authority room access, regulator-listening access, public finance reader access, emergency-management learning access, or public infrastructure operator access through support or participation.
205.11 Sponsored Publication Conflict
205.11.1 Sponsored publication conflicts shall be reviewed where support may affect publication topic, timing, authorship, attribution, limitation language, conclusions, public authority references, sponsor acknowledgment, provider references, corrections, withdrawal, retraction, or takedown.
205.12 Sponsored Technical Baseline Conflict
205.12.1 Sponsored technical baseline conflicts shall be reviewed where funding, technical contribution, hosting, data contribution, provider support, or sponsor expectation may affect open technical baselines, schemas, APIs, SDKs, benchmarks, test harnesses, reference architectures, public-good software, or Nexus-compatible claims.
205.13 Sponsored Benchmark Conflict
205.13.1 Sponsored benchmark conflicts shall be reviewed where benchmark design, data selection, model selection, scoring, result presentation, publication, public authority use, provider comparison, public-safe claims, or market interpretation may be affected by sponsor, provider, donor, funder, host, or capital actor interests.
205.14 Provider Evaluation Conflict
205.14.1 Provider evaluation conflicts shall be reviewed where Corporation materials, reviews, dashboards, benchmarks, public authority learning, technical baselines, public-safe reports, or controlled rooms may be used to compare, rank, prefer, approve, certify, recognize, or signal provider suitability.
205.15 Provider Contribution Conflict
205.15.1 Provider contribution conflicts shall be reviewed where providers contribute software, data, models, compute, cloud credits, cyber tools, equipment, AI-RAN components, O-RAN components, DePIN components, DLT systems, dashboards, staff, technical documentation, or in-kind support.
205.16 Provider Marketing Conflict
205.16.1 Provider marketing conflicts shall be reviewed where a provider seeks to use Corporation participation, logo, name, publication, public authority interface, technical baseline, software reference, benchmark, proof receipt, controlled-room access, or Nexus-compatible language for marketing, procurement, finance, certification, recognition, or public authority advantage.
205.17 Host Activation Conflict
205.17.1 Host activation conflicts shall be reviewed where a host site, public authority host, university host, laboratory host, community host, infrastructure host, cloud host, data host, or event host may influence program design, access, publication, public authority perception, data rights, safeguards, or public-safe claims.
205.18 National Company, State Operating Company, Regional Company, or Project SPV Interface Conflict
205.18.1 Interfaces with national companies, state operating companies, regional companies, Project SPVs, project companies, deployment vehicles, asset owners, infrastructure vehicles, or enterprise actors shall be reviewed to preserve legal separateness, non-agency, non-control, non-execution, public-good stack / enterprise stack separation, provider neutrality, finance-boundary discipline, certification-boundary discipline, procurement neutrality, and public-safe claims.
205.19 Capital-Adjacent Evidence Conflict
205.19.1 Capital-adjacent evidence conflicts shall be reviewed where evidence, methods, dashboards, proof receipts, public authority learning materials, Docket support, Grid support, or GRA-facing technical inputs may be used by capital readers, investors, insurers, lenders, underwriters, banks, public finance actors, national companies, Project SPVs, sponsors, or providers to infer finance-readiness, insurance-readiness, bankability, investability, risk rating, or public finance approval.
205.20 No Control-for-Cash, Pay-to-Play, Outcome Purchase, Veto, Suppression, Recognition Purchase, Finance-Readiness Purchase, Certification Purchase, Procurement Advantage, Provider Preference, or Public Authority Access Purchase
205.20.1 The Corporation shall not permit control-for-cash, pay-to-play, access-for-money, outcome purchase, evidence conclusion purchase, method design purchase, publication conclusion purchase, correction suppression, public authority access purchase, Docket or Grid input purchase, standards outcome purchase, recognition purchase, finance-readiness purchase, certification purchase, procurement advantage purchase, provider preference purchase, or public authority legitimacy purchase.
205.20.2 Any arrangement containing, implying, concealing, or practically creating such rights shall be refused, returned, restricted, terminated, corrected, escalated, or referred as appropriate.
205.21 Enhanced Review, Recusal, Ring-Fencing, Clean-Room Handling, Independent Review, Disclosure, Refusal, Return, Restriction, or Termination
205.21.1 Sponsor, donor, funder, provider, host, enterprise, and capital actor conflicts may require enhanced review, recusal, access restriction, ring-fencing, clean-room handling, independent review, public-safe disclosure, controlled disclosure, support refusal, support return, benefit restriction, contract amendment, termination, correction, public clarification, or Board review.
205.22 Sponsor, Donor, Funder, Provider, Host, Enterprise, and Capital Actor Conflict Records
205.22.1 The Corporation shall maintain Sponsor, Donor, Funder, Provider, Host, Enterprise, and Capital Actor Conflict Records identifying the relationship, affected matter, support, benefit, access, contribution, public authority proximity, public-safe claim, provider-neutrality issue, sponsor non-control issue, capital boundary issue, review, mitigation, refusal, return, restriction, termination, correction, and closeout.
Section 206. Community, Tribal / Indigenous, Civil Rights, Accessibility, Protected Knowledge, and Safeguards Conflicts
206.1 Community Safeguards Conflict Definition
206.1.1 A Community Safeguards Conflict exists where a Covered Person, Related Party, sponsor, donor, funder, provider, host, public authority participant, university, laboratory, media participant, national company, Project SPV, capital actor, enterprise actor, or other participant has an interest, role, incentive, duty, pressure, access, relationship, or expectation that may affect or appear to affect the Corporation’s duty to protect communities from harm, extraction, stigmatization, retaliation, exposure, exclusion, public authority misuse, surveillance risk, public-safe mapping risk, or institutional convenience.
206.1.2 Community safeguards conflicts shall be interpreted broadly. They include conflicts affecting research design, fieldwork, public authority learning, observability outputs, dashboards, maps, datasets, AI outputs, digital twins, public-safe reports, technical baselines, Academy materials, controlled rooms, public statements, grievance intake, remedy design, and correction.
206.1.3 No person may treat community safeguards as secondary to technical ambition, sponsor expectation, provider convenience, publication timing, fundraising interest, public authority interest, finance-readiness interest, recognition interest, certification interest, procurement interest, or institutional reputation.
206.2 Tribal and Indigenous Conflict Definition
206.2.1 A Tribal or Indigenous Conflict exists where a Covered Person or Related Party has an interest, role, relationship, institutional duty, research objective, public authority connection, sponsor relationship, provider relationship, publication interest, data interest, mapping interest, AI-processing interest, or enterprise interest that may affect the Corporation’s respect for Tribal sovereignty, Indigenous governance, Indigenous data safeguards, protected knowledge, cultural protocols, consent, non-consent, attribution, non-attribution, withdrawal, correction, and public-safe handling.
206.2.2 Tribal and Indigenous conflicts shall be reviewed with heightened care. Participation by a Tribal Nation, Indigenous government, Indigenous institution, Indigenous community, Indigenous knowledge holder, or Indigenous data steward shall not be treated as consent, endorsement, knowledge transfer, data transfer, publication permission, mapping permission, AI-use permission, or waiver of rights unless expressly, lawfully, specifically, and appropriately recorded by the competent authority.
206.2.3 A Covered Person with a conflicting role in a sponsor, provider, public authority, university, laboratory, funder, media organization, national company, Project SPV, or enterprise actor shall not control Tribal or Indigenous safeguards review.
206.3 Local and Territorial Knowledge Conflict Definition
206.3.1 A Local or Territorial Knowledge Conflict exists where a person’s interest may affect the identification, classification, use, mapping, publication, attribution, non-attribution, translation, AI processing, archiving, restriction, withdrawal, or correction of local knowledge, territorial knowledge, community-protected knowledge, cultural knowledge, ecological knowledge, environmental knowledge, or other place-based knowledge.
206.3.2 Local and territorial knowledge shall not be treated as freely usable merely because it is observable, publicly discussed, technically accessible, government-held, published elsewhere, contributed by a participant, or useful to systemic risk analysis.
206.3.3 Where the use of such knowledge may expose persons, locations, infrastructure, ecological assets, cultural sites, community vulnerabilities, or protected relationships, the matter shall be routed through safeguards review before publication, mapping, model use, or external circulation.
206.4 Civil Rights Conflict Definition
206.4.1 A Civil Rights Conflict exists where a Covered Person or Related Party has an interest, relationship, duty, policy position, research agenda, public authority role, provider role, sponsor role, data role, AI role, or publication role that may affect the Corporation’s duties of non-discrimination, equal access, fairness, protected participation, language access, disability access, procedural fairness, non-retaliation, and rights-respecting design.
206.4.2 Civil rights conflicts shall be reviewed where Corporation activity could create discriminatory exclusion, disparate treatment, disparate impact, biased evidence interpretation, biased model output, inaccessible participation, inequitable access to controlled rooms or Academy materials, retaliation risk, harassment risk, or suppression of protected complaints.
206.4.3 No Covered Person shall participate in a civil rights review where the person has an interest in defending, minimizing, concealing, or reframing the alleged harm or exclusion.
206.5 Accessibility Conflict Definition
206.5.1 An Accessibility Conflict exists where a Covered Person or Related Party has an interest, convenience, budget pressure, timing pressure, platform dependency, publication objective, event design preference, technology preference, host-site interest, or operational role that may affect accessible participation, accessible notices, accessible digital surfaces, accessible dashboards, accessible Academy materials, accessible public-safe reports, accessible meetings, or accessible grievance pathways.
206.5.2 Accessibility shall be treated as a governance condition and not as optional presentation refinement. A conflict affecting accessibility may require redesign, delay, alternative format, additional support, restricted publication, or access correction.
206.5.3 No urgency, sponsor deadline, provider platform limitation, event schedule, publication launch, or technical preference shall justify avoidable accessibility exclusion.
206.6 Protected Knowledge Conflict Definition
206.6.1 A Protected Knowledge Conflict exists where a person or entity may benefit from accessing, extracting, publishing, mapping, translating, attributing, suppressing, generalizing, commercializing, licensing, training on, embedding, transferring, or otherwise processing protected knowledge.
206.6.2 Protected knowledge includes Tribal, Indigenous, local, territorial, cultural, environmental, ecological, sacred, community-protected, vulnerability-related, infrastructure-sensitive, health-sensitive, safety-sensitive, grievance-related, and other knowledge designated as protected by law, protocol, consent terms, community process, safeguards review, or competent record.
206.6.3 Protected knowledge shall not be used as raw material for institutional convenience, technical demonstration, sponsor storytelling, provider marketing, public authority persuasion, finance-facing narrative, media content, AI training, benchmark creation, dashboard enrichment, or publication value.
206.7 Conflict Between Research Goals and Community Safeguards
206.7.1 Where research goals conflict with community safeguards, the Corporation shall prioritize lawful, rights-respecting, public-benefit, public-safe, and do-no-harm handling.
206.7.2 Research goals shall be narrowed, delayed, redesigned, independently reviewed, restricted, or terminated where continuation would create material risk of harm, exposure, stigmatization, retaliation, extraction, protected knowledge misuse, civil rights harm, accessibility exclusion, public authority misuse, or public misunderstanding.
206.7.3 No research output shall be justified solely by scientific interest, technical novelty, data availability, publication opportunity, sponsor support, public authority interest, or Nexus relevance where safeguards risk remains unresolved.
206.8 Conflict Between Publication Goals and Protected Knowledge
206.8.1 Where publication goals conflict with protected knowledge duties, the Corporation shall apply the most protective lawful handling until competent safeguards review determines whether publication, redaction, aggregation, suppression, delay, controlled circulation, or withdrawal is appropriate.
206.8.2 Publication shall not proceed where protected knowledge may be exposed in text, tables, maps, dashboards, metadata, model outputs, images, geospatial layers, repository commits, technical annexes, training materials, public-safe reports, or AI-generated summaries.
206.8.3 Public-safe publication may require:
206.8.3(a) removal of sensitive location details; 206.8.3(b) aggregation, blurring, delay, or masking; 206.8.3(c) suppression of names, affiliations, or specific community identifiers; 206.8.3(d) controlled annex treatment; 206.8.3(e) non-attribution; 206.8.3(f) community, Tribal, Indigenous, or safeguards review; 206.8.3(g) limitation language; and 206.8.3(h) correction, withdrawal, or takedown if risk is identified after release.
206.9 Conflict Between Mapping Goals and Public Safety
206.9.1 Where mapping, geospatial analysis, Earth observation, dashboarding, digital twins, sensor outputs, AI-RAN signals, O-RAN signals, DePIN records, DLT records, cyber telemetry, or public-safe observability outputs may create public safety risk, protected knowledge risk, infrastructure exposure, ecological exposure, cultural site exposure, vulnerable-population exposure, or retaliation risk, mapping goals shall yield to public-safe handling.
206.9.2 Public-safe mapping controls may include aggregation, masking, blurring, time delay, suppression, no-download viewing, restricted legends, controlled-room review, public authority limitation language, community safeguards review, and publication freeze.
206.9.3 No map, dashboard, digital twin, AI output, sensor signal, or observability artifact shall be released merely because it is technically accurate if its release may create foreseeable harm or misuse.
206.10 Conflict Between Sponsor or Provider Interests and Community Interests
206.10.1 Where sponsor or provider interests conflict with community interests, the Corporation shall preserve community safeguards, protected knowledge, civil rights, accessibility, public-safe language, and non-extraction duties.
206.10.2 Sponsor or provider interests shall not control community engagement, story selection, imagery, evidence framing, public authority access, data access, publication timing, protected knowledge use, public-safe mapping, grievance handling, remedy design, or correction.
206.10.3 A sponsor, donor, funder, provider, host, vendor, national company, Project SPV, capital actor, or enterprise actor shall not receive access to community information, protected knowledge, grievance information, or community trust by reason of financial support, technical contribution, event support, hosting, platform provision, or public authority proximity.
206.11 Conflict Between Public Authority Interest and Community Non-Consent
206.11.1 Where public authority interest conflicts with community non-consent, Tribal non-consent, Indigenous non-consent, protected knowledge restrictions, or community safeguards, the Corporation shall not treat public authority interest as overriding consent, non-consent, withdrawal, restriction, attribution, non-attribution, public-safe mapping, or do-no-harm duties unless legally required and reviewed through competent process.
206.11.2 Public authority participation shall not convert community information into public authority-approved information, public warning material, emergency command material, official record for public action, procurement material, regulatory material, public finance material, or public-safe publication material.
206.11.3 Where law requires disclosure or public authority notice, the Corporation shall preserve the narrowest lawful disclosure, record the basis, protect affected persons where possible, and apply public-safe communication discipline.
206.12 Conflict Between Open Data and Protected Knowledge
206.12.1 Open data principles shall not override protected knowledge, privacy, public authority restrictions, infrastructure sensitivity, cyber sensitivity, health sensitivity, community safeguards, Tribal and Indigenous protocols, or civil rights.
206.12.2 Before data is released as open data, public-good data, benchmark data, training data, evaluation data, dashboard data, schema examples, repository samples, or technical baseline material, the Corporation shall review whether the data contains protected knowledge, rights-bearing data, public authority restrictions, re-identification risk, location sensitivity, or downstream misuse risk.
206.12.3 Data may be withheld, redacted, aggregated, syntheticized, delayed, restricted, sealed, or removed from open release where open release would undermine safeguards.
206.13 Conflict Between AI Processing and Rights-Bearing Data
206.13.1 AI processing shall not be used to bypass safeguards applicable to rights-bearing data, protected knowledge, public authority data, community-protected data, health-sensitive data, youth data, grievance data, local or territorial knowledge, Tribal or Indigenous data, or infrastructure-sensitive materials.
206.13.2 A conflict exists where AI tools, model providers, cloud providers, data processors, researchers, developers, maintainers, sponsors, providers, or public authorities may benefit from processing restricted materials for training, fine-tuning, embeddings, retrieval, summarization, translation, classification, benchmark creation, or model evaluation.
206.13.3 AI processing involving rights-bearing data shall require approved tools, permitted purpose, access controls, no-training restrictions, no-unapproved-embedding restrictions, human review, logging, retention controls, deletion controls, and incident escalation.
206.14 Conflict Between Institutional Convenience and Do-No-Harm Controls
206.14.1 Institutional convenience shall not override do-no-harm controls. Convenience includes speed, fundraising value, sponsor satisfaction, provider convenience, public authority interest, publication timelines, event deadlines, media opportunities, operational ease, technical efficiency, AI automation, dashboard utility, or repository simplicity.
206.14.2 Where do-no-harm review identifies unresolved risk, the Corporation may pause, narrow, redesign, route to controlled room, restrict access, freeze publication, require independent safeguards review, notify affected participants, or abandon the activity.
206.14.3 A decision to proceed despite identified safeguards risk shall require competent authority, recorded rationale, mitigation plan, correction pathway, and, where appropriate, Board or counsel review.
206.15 Tribal Sovereignty and Indigenous Governance Respect
206.15.1 Tribal sovereignty and Indigenous governance shall be respected as foundational safeguards in all relevant conflict determinations.
206.15.2 The Corporation shall not assume that public authority participation, university participation, nonprofit participation, researcher participation, community organization participation, funder support, sponsor support, or individual participation creates authority to speak for, bind, waive rights of, or transfer knowledge from any Tribal Nation, Indigenous government, Indigenous institution, Indigenous community, or Indigenous knowledge holder.
206.15.3 Where authority is uncertain, the Corporation shall adopt a restrictive handling posture until the competent authority, consent pathway, non-consent pathway, or protection protocol is clarified by record.
206.16 Consent, Non-Consent, Attribution, Withdrawal, Restriction, Correction, Grievance, and Remedy Pathways
206.16.1 Conflict review shall preserve consent, non-consent, attribution, non-attribution, withdrawal, restriction, correction, grievance, and remedy pathways where applicable.
206.16.2 Consent shall not be inferred from attendance, silence, prior participation, public availability, public authority presence, sponsor support, provider support, data contribution, publication in another context, or technical accessibility.
206.16.3 Where withdrawal, restriction, correction, or remedy is requested, the Corporation shall review the request in good faith and may impose immediate protective measures pending review.
206.17 Safeguards Stop-the-Line
206.17.1 Any person acting in good faith may escalate a safeguards conflict for stop-the-line review where continuation may create material harm to persons, communities, protected knowledge, civil rights, accessibility, public safety, public authority trust, or institutional integrity.
206.17.2 Stop-the-line measures may include hold, quarantine, access restriction, publication freeze, implementation freeze, meeting suspension, controlled-room lockdown, data freeze, model freeze, repository freeze, public authority clarification, sponsor or provider access restriction, and Board escalation.
206.17.3 No person shall be retaliated against for good-faith safeguards escalation, dissent, refusal to publish, refusal to map, refusal to process data, refusal to upload to AI, grievance support, or correction request.
206.18 Independent Safeguards Review
206.18.1 Independent safeguards review shall be required where a conflict materially affects community safeguards, Tribal or Indigenous protocols, protected knowledge, civil rights, accessibility, public-safe mapping, vulnerable communities, non-retaliation, or do-no-harm.
206.18.2 Independent safeguards review shall not be controlled by the sponsor, provider, public authority, researcher, publication lead, technical lead, data owner, AI provider, host, capital actor, national company, Project SPV, or enterprise actor whose interests are affected.
206.18.3 Independent safeguards review may recommend approval, restriction, redesign, non-public handling, controlled annex treatment, redaction, aggregation, delay, non-attribution, withdrawal, takedown, remedy, or termination.
206.19 Community, Tribal / Indigenous, Civil Rights, Accessibility, Protected Knowledge, and Safeguards Conflict Records
206.19.1 The Corporation shall maintain Community, Tribal / Indigenous, Civil Rights, Accessibility, Protected Knowledge, and Safeguards Conflict Records identifying the affected matter, affected persons or communities where appropriate and lawful, conflict type, knowledge class, consent or non-consent status, restrictions, safeguards reviewer, public-safe mapping review, AI-use review, civil rights review, accessibility review, grievance or remedy pathway, stop-the-line action, mitigation, correction, withdrawal, takedown, closeout, and archive status.
Section 207. Related-Party Transactions
207.1 Related-Party Transaction Definition
207.1.1 A Related-Party Transaction means any transaction, arrangement, relationship, commitment, transfer, exchange, support relationship, access grant, rights grant, compensation arrangement, contract, contribution, publication arrangement, data arrangement, technical arrangement, public authority interface, controlled-room admission, or other matter in which the Corporation participates and in which a Covered Person or Related Party has a financial, institutional, personal, professional, reputational, technical, data, AI, cyber, public authority, sponsor, provider, host, capital, safeguards, or enterprise interest.
207.1.2 Related-party status shall be determined by substance, not label. A transaction may be related-party even if routed through an affiliate, employer, client, fund, foundation, sponsor, provider, public authority instrumentality, university, laboratory, national company, Project SPV, fiscal sponsor, subcontractor, repository, open-source project, AI agent, data processor, controlled entity, or informal representative.
207.2 Related Party Definition
207.2.1 A Related Party includes any person or entity whose relationship to a Covered Person may affect or appear to affect the Covered Person’s judgment or may create benefit, influence, access, authority, or public meaning through the Corporation.
207.2.2 Related Parties include family members, household members, domestic partners, close personal relationships, employers, clients, business partners, controlled entities, affiliates, beneficial owners, commonly controlled organizations, sponsors, donors, funders, providers, vendors, hosts, contractors, investors, insurers, lenders, banks, public finance actors, universities, laboratories, public authorities, community organizations, Tribal or Indigenous organizations, media organizations, political organizations, national companies, Project SPVs, and enterprise actors where relevant.
207.3 Director Related Party
207.3.1 A Director Related Party includes any person or entity connected to a director through financial interest, family or household relationship, employment, fiduciary role, advisory role, board service, consulting role, sponsor relationship, provider relationship, public authority role, capital actor role, university or laboratory role, national company role, Project SPV role, or other relationship that may affect Board judgment.
207.3.2 Director related-party transactions shall require heightened review, disinterested approval, recusal, record support, and compliance with applicable law, Articles, this Bylaw, tax rules, nonprofit rules, and Board reserved matters.
207.4 Officer Related Party
207.4.1 An Officer Related Party includes any person or entity connected to an officer through employment, compensation, consulting, contracting, family, household, sponsorship, provider relationship, public authority relationship, capital actor relationship, technical asset relationship, data relationship, AI relationship, cyber relationship, or enterprise relationship.
207.4.2 An officer shall not approve, negotiate, manage, certify, sign, supervise, evaluate, pay, or record a transaction involving the officer’s Related Party unless competent authority has imposed a lawful, recorded, and appropriately supervised process.
207.5 Employee, Contractor, Fellow, Advisor, Volunteer, Committee Member, Council Member, Contributor, Sponsor, Donor, Funder, Provider, Host, Partner, Public Authority Participant, or Enterprise Actor Related Party Where Relevant
207.5.1 Related-party status may arise for employees, contractors, fellows, advisors, volunteers, committee members, council members, contributors, maintainers, reviewers, sponsors, donors, funders, providers, hosts, partners, public authority participants, capital actors, national companies, Project SPVs, and enterprise actors where their relationships may affect access, outputs, contracts, publications, data, software, controlled rooms, public authority interfaces, support arrangements, or public-safe claims.
207.5.2 The Corporation may require disclosure, recusal, access restriction, independent review, contract controls, public-safe limitation, or denial of the transaction.
207.6 Family, Household, Affiliate, Employer, Client, Investor, Beneficial Owner, Controlled Entity, Controlling Person, Controlled Organization, and Common-Control Relationships
207.6.1 The Corporation shall aggregate family, household, affiliate, employer, client, investor, beneficial owner, controlled entity, controlling person, controlled organization, and common-control relationships where necessary to determine related-party status, materiality, independence, capture risk, or required mitigation.
207.6.2 A transaction shall not avoid review because the direct counterparty is not the Covered Person if the practical benefit flows to a Related Party or if influence is exercised through a related structure.
207.7 Transaction Types
207.7.1 Related-party transaction review applies to financial, contractual, technical, programmatic, research, publication, data, AI, cyber, public authority, safeguards, controlled-room, repository, IP, support, employment, reimbursement, grant, sponsorship, donation, in-kind, host-site, capital-adjacent, and enterprise-stack arrangements.
207.7.2 The Corporation shall classify the transaction type before approval and shall apply the highest applicable review standard where multiple categories apply.
207.8 Contracts
207.8.1 Contracts with Related Parties shall be reviewed for lawful authority, public-benefit purpose, necessity, fair value, alternatives, conflicts, private benefit, tax treatment, procurement neutrality, data / AI / cyber controls, IP rights, confidentiality, public-safe claims, and termination rights.
207.8.2 No Related Party shall receive a contract because of insider status, donor status, sponsor status, provider proximity, public authority proximity, technical centrality, personal relationship, or informal influence.
207.9 Grants
207.9.1 Grants involving Related Parties shall be reviewed for mission alignment, eligibility, fair process, restricted fund compatibility, conflicts, private benefit, reporting, public authority implications, data rights, publication rights, safeguards, and correctionability.
207.9.2 No grant shall be used to provide private inurement, impermissible private benefit, research influence, public authority access purchase, sponsor advantage, provider preference, certification purchase, recognition purchase, finance-readiness purchase, or procurement advantage.
207.10 Donations
207.10.1 Donations involving Related Parties shall be reviewed for donor restrictions, donor control, tax treatment, public acknowledgment, public authority implications, sponsor overlap, provider overlap, reputational risk, private benefit, and anti-capture concerns.
207.10.2 A Related Party donation shall not create governance rights, agenda rights, publication rights, veto rights, public authority access rights, provider preference, recognition, finance-readiness, certification, procurement advantage, or control over institutional outputs.
207.11 Sponsorships
207.11.1 Sponsorships involving Related Parties shall be reviewed for sponsor benefits, acknowledgment terms, public-safe language, tax treatment, sponsor control risk, provider preference risk, public authority access risk, publication influence, research influence, and enterprise-stack advantage.
207.11.2 Related-party sponsorship shall not include sponsor veto, sponsor approval of conclusions, sponsor selection of public authority participants, sponsor selection of providers, sponsor control of technical baselines, sponsor control of software releases, or sponsor control of correction.
207.12 In-Kind Contributions
207.12.1 In-kind contributions involving Related Parties, including compute, cloud credits, AI tools, datasets, software, hardware, sensors, dashboards, cybersecurity services, facilities, staff time, event support, or technical services, shall be reviewed for value, restrictions, conflicts, dependency, data rights, IP rights, cyber risk, export-control risk, sanctions risk, protected knowledge risk, and public-safe claims.
207.12.2 In-kind support shall not create hidden control, technical lock-in, repository dependence, provider preference, procurement signal, public authority endorsement, certification meaning, finance-readiness meaning, or enterprise-stack capture.
207.13 Compensation
207.13.1 Compensation involving Related Parties shall be reasonable, lawful, independently reviewed, properly classified, budget-authorized, tax-reviewed where appropriate, and supported by comparability or other appropriate evidence.
207.13.2 A Covered Person shall not approve, influence, process, document, verify, or supervise the person’s own compensation or compensation payable to a Related Party.
207.14 Reimbursements
207.14.1 Reimbursements to Related Parties shall be limited to reasonable, necessary, documented, authorized, and mission-aligned expenses.
207.14.2 Reimbursement shall not be used as disguised compensation, donor benefit, sponsor benefit, provider benefit, public authority access purchase, or private distribution.
207.15 IP Licenses
207.15.1 IP licenses involving Related Parties shall be reviewed for ownership, chain of title, license scope, public-good access, anti-enclosure, royalty terms, standards-essential rights, attribution, moral rights where applicable, commercialization rights, open-source compatibility, repository implications, and public-safe claims.
207.15.2 No IP license shall permit a Related Party to convert public-good software, open technical baselines, schemas, data dictionaries, APIs, SDKs, dashboards, proof receipts, technical profiles, or controlled vocabulary into private constitutional inventory or proprietary control over Nexus-compatible meaning.
207.16 Data-Sharing Arrangements
207.16.1 Data-sharing arrangements involving Related Parties shall be reviewed for lawful basis, permitted use, privacy, public authority restrictions, health sensitivity, infrastructure sensitivity, cyber sensitivity, community-protected data, Tribal and Indigenous data, protected knowledge, AI-use restrictions, retention, deletion, publication, and correction.
207.16.2 Data sharing shall not create hidden benefit, sponsor advantage, provider advantage, AI training advantage, research distortion, public authority confusion, finance signal, certification signal, procurement advantage, or protected knowledge extraction.
207.17 Software, Repository, Cloud, AI, Cybersecurity, Equipment, Facilities, and Service Arrangements
207.17.1 Technical service arrangements involving Related Parties shall be reviewed for security, privacy, dependency, continuity, portability, logging, auditability, incident support, license terms, vendor lock-in, access controls, repository permissions, AI-use restrictions, cyber risk, public authority data, protected knowledge, export-control risk, sanctions risk, and termination rights.
207.17.2 No Related Party technical arrangement shall create control over official records, public-good software, release pipelines, model outputs, compute records, evidence records, controlled rooms, or public-facing technical claims inconsistent with this Bylaw.
207.18 Public Authority, Provider, Sponsor, Host, Enterprise, National Company, Project SPV, or Capital-Adjacent Arrangements
207.18.1 Related-party arrangements involving public authorities, providers, sponsors, hosts, enterprise actors, national companies, Project SPVs, capital actors, investors, insurers, lenders, underwriters, banks, or public finance actors shall receive heightened review.
207.18.2 Such arrangements shall not create public authority delegation, public warning, emergency command, procurement approval, funding approval, regulatory approval, public finance approval, finance-readiness, insurance-readiness, bankability, rating, certification, recognition, provider preference, sponsor control, or enterprise execution by the Corporation.
207.19 Disclosure, Independent Review, Fairness Determination, Disinterested Approval, Record Support, and Monitoring
207.19.1 A Related-Party Transaction shall not be approved unless the relevant interest has been disclosed, reviewed, classified, and routed to a competent disinterested authority.
207.19.2 Approval shall require, as appropriate:
207.19.2(a) a written disclosure of the relationship and interest; 207.19.2(b) recusal and access restriction for interested persons; 207.19.2(c) independent review; 207.19.2(d) comparability or fair-value support where relevant; 207.19.2(e) a fairness determination; 207.19.2(f) a public-benefit purpose finding; 207.19.2(g) a no-private-inurement and no-impermissible-private-benefit finding; 207.19.2(h) an anti-capture and boundary-compliance finding; 207.19.2(i) conditions, monitoring, and correction rights; and 207.19.2(j) Board, committee, counsel, tax, safeguards, or data / AI / cyber review where required.
207.20 Related-Party Transaction Records
207.20.1 The Corporation shall maintain Related-Party Transaction Records identifying the Covered Person, Related Party, transaction type, affected matter, disclosure, review authority, conflicts of reviewers, recusals, access restrictions, comparability evidence, fairness determination, approval or denial, conditions, monitoring, payments, deliverables, public-safe limitation language, corrections, termination, closeout, and archive status.
Section 208. Annual Disclosure, Event-Based Disclosure, Continuing Duty to Update, and Certification
208.1 Annual Disclosure Requirement
208.1.1 Each director, officer, senior employee, committee chair, council chair, working group lead, principal investigator, lead maintainer, public authority interface lead, safeguards lead, development lead, technical asset custodian, repository custodian, controlled-room lead, and other Covered Person designated by the Board, policy, officer, or competent authority shall submit an annual disclosure statement.
208.1.2 Annual disclosure shall identify interests, roles, relationships, transactions, duties, compensation, support relationships, technical access, data access, AI access, cyber access, public authority roles, sponsor relationships, provider relationships, capital relationships, safeguards exposure, and other matters relevant to conflicts, independence, anti-capture, and related-party review.
208.2 Initial Disclosure Upon Appointment, Admission, Engagement, or Access
208.2.1 Initial disclosure shall be required upon appointment, election, hiring, engagement, admission, onboarding, controlled-room access, repository access, data-room access, public authority room access, committee service, council service, panel service, fellowship, advisory role, contractor engagement, sponsorship relationship, provider participation, host participation, or other role designated by policy.
208.2.2 Initial disclosure shall be completed before the Covered Person receives material authority, access, participation rights, voting rights, review responsibility, publication authority, repository permissions, controlled-room admission, or public-facing status unless emergency provisional access is recorded and time-limited.
208.3 Event-Based Disclosure Requirement
208.3.1 Event-based disclosure shall be required before a Covered Person participates in any matter where a conflict may exist or where new facts make a prior disclosure incomplete, stale, or misleading.
208.3.2 Event-based disclosure applies before deliberation, recommendation, review, drafting, approval, voting, signing, publishing, releasing, granting access, processing data, using AI, reviewing evidence, engaging a public authority, accepting support, selecting a provider, entering a transaction, or taking corrective action.
208.4 Continuing Duty to Update
208.4.1 Each Covered Person has a continuing duty to update disclosures promptly when facts change.
208.4.2 The duty to update applies to new employment, new consulting, new compensation, new investments, new public authority roles, new sponsor or provider relationships, new Related Parties, new technical dependencies, new data access, new AI or cyber interests, new publication interests, new safeguards issues, and new enterprise-stack relationships.
208.5 Disclosure of Financial Interests
208.5.1 Covered Persons shall disclose financial interests, including equity, debt, compensation, consulting fees, grants, donations, sponsorships, restricted funds, reimbursements, gifts, honoraria, travel support, revenue interests, royalty interests, IP interests, success fees, referral fees, transaction-based compensation, provider interests, capital interests, and related-party financial interests.
208.5.2 Financial interests shall be disclosed whether direct or indirect, certain or contingent, current or expected, personal or through a Related Party.
208.6 Disclosure of Institutional Roles
208.6.1 Covered Persons shall disclose institutional roles, including director, officer, employee, trustee, partner, manager, advisor, consultant, contractor, public official, public employee, public authority participant, university participant, laboratory participant, sponsor representative, provider representative, host representative, capital actor, national company role, Project SPV role, media role, community organization role, or enterprise role.
208.6.2 Institutional roles shall be disclosed where they may affect GCRI US governance, outputs, records, public authority interfaces, publications, technical assets, support relationships, public-safe claims, GRF-facing inputs, GRA-facing technical inputs, or Nexus interfaces.
208.7 Disclosure of Family, Household, Affiliate, Employer, Client, Investor, Beneficial Owner, and Related-Party Interests
208.7.1 Covered Persons shall disclose family, household, affiliate, employer, client, investor, beneficial owner, controlled entity, controlling person, common-control, and Related Party interests where such interests may affect or appear to affect judgment.
208.7.2 Disclosure shall be sufficient to allow the Corporation to determine whether interests should be aggregated, whether related-party review is required, and whether recusal, access restriction, or mitigation is necessary.
208.8 Disclosure of Research, Evidence, Methods, Publication, Data, AI, Cyber, Public Authority, Sponsor, Provider, Host, Enterprise, Capital, Safeguards, Competition, Sanctions, Export-Control, and Professional Boundary Interests
208.8.1 Covered Persons shall disclose interests affecting research, evidence, methods, publication, data, AI, cybersecurity, privacy, public authority interface, sponsor relationships, donor or funder relationships, provider relationships, host relationships, enterprise actors, capital actors, community safeguards, Tribal and Indigenous protocols, protected knowledge, competition, sanctions, export-control, controlled technology, lobbying, political activity, government ethics, procurement integrity, and professional boundaries.
208.8.2 Disclosure shall include interests that may affect public-safe reports, dashboards, maps, public-good software, technical baselines, datasets, models, benchmarks, proof receipts, Docket support, Grid support, GRF-facing inputs, GRA-facing inputs, Nexus-compatible claims, and public authority learning.
208.9 Certification of Completeness
208.9.1 The Corporation may require a Covered Person to certify that the disclosure is complete and includes all interests, roles, relationships, transactions, and facts known or reasonably knowable to the Covered Person.
208.9.2 Certification of completeness may be required annually, upon appointment, before sensitive access, before Board or committee action, before controlled-room admission, before public authority interface participation, before publication approval, before support acceptance, before repository permission, before software release authority, and before any matter designated by policy.
208.10 Certification of Accuracy
208.10.1 The Corporation may require a Covered Person to certify that disclosures are accurate, truthful, current, and not misleading.
208.10.2 A false, misleading, reckless, stale, or materially incomplete certification shall constitute a conflict violation and may support recusal, access restriction, suspension, removal, contract remedy, repayment, support return, correction, legal review, or referral.
208.11 Certification of Understanding
208.11.1 The Corporation may require a Covered Person to certify understanding of this Article, the conflict of interest policy, public-benefit purpose, non-execution, role separation, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, and correctionability.
208.11.2 Certification of understanding shall not excuse misconduct, failure to disclose, failure to recuse, or improper influence.
208.12 Failure to Disclose
208.12.1 Failure to disclose includes omission, delay, false denial, partial disclosure, misleading characterization, concealment through a Related Party, concealment through an affiliate, concealment through informal communication, failure to update, or failure to certify when required.
208.12.2 Failure to disclose may result in conflict classification, access restriction, recusal, investigation, transaction hold, approval denial, reconsideration of prior action, correction, suspension, removal, termination, repayment, rescission, public or controlled clarification, legal referral, or other remedy.
208.13 Corrective Disclosure
208.13.1 A Covered Person who discovers an incomplete, inaccurate, stale, or misleading disclosure shall submit corrective disclosure promptly.
208.13.2 Corrective disclosure shall identify the omitted or corrected information, date of discovery, affected matters, prior participation, materials accessed, recommendations made, votes cast, approvals given, publications affected, transactions affected, public authority interfaces affected, and any urgent mitigation required.
208.13.3 Corrective disclosure does not automatically cure a violation but shall be considered in determining appropriate mitigation and remedy.
208.14 Disclosure Records
208.14.1 The Corporation shall maintain Disclosure Records, including annual disclosures, initial disclosures, event-based disclosures, corrective disclosures, certifications of completeness, certifications of accuracy, certifications of understanding, disclosure reminders, non-response records, late disclosure records, incomplete disclosure records, conflict classifications, mitigation, recusals, access restrictions, corrections, enforcement actions, and closeout.
Section 209. Conflict Intake, Triage, Classification, Materiality, and Escalation
209.1 Conflict Intake
209.1.1 The Corporation shall maintain a conflict intake process for receiving disclosures, reports, questions, complaints, suspected conflicts, related-party concerns, independence concerns, capture concerns, gift concerns, public authority concerns, finance-boundary concerns, safeguards concerns, data / AI / cyber concerns, and alleged violations of this Article.
209.1.2 Intake may occur through disclosure forms, annual statements, event-based notices, committee reports, officer reports, controlled-room reports, public authority interface reports, whistleblower channels, safeguards channels, audit findings, counsel review, compliance review, Board referral, or participant report.
209.2 Conflict Case ID
209.2.1 Each material conflict matter shall receive a Conflict Case ID or other controlled record identifier sufficient to preserve traceability, uniqueness, lifecycle status, authority path, review history, mitigation, correction, and closeout.
209.2.2 A conflict matter shall not be managed solely through informal email, chat, oral discussion, meeting memory, or untracked document comments where the matter may affect institutional action.
209.3 Intake Form Requirement
209.3.1 The Corporation may require an intake form or equivalent record identifying the Covered Person, Related Party where applicable, affected matter, conflict type, transaction type, access involved, authority involved, public meaning involved, urgency, known facts, documents, requested action, and proposed interim controls.
209.3.2 The intake form shall include sufficient information to permit triage without relying on undisclosed context.
209.4 Preliminary Review
209.4.1 A preliminary review shall determine whether the matter is within this Article, whether immediate protective measures are required, whether the matter is complete enough for review, whether additional information is needed, and which authority should handle the matter.
209.4.2 Preliminary review may impose interim holds, access restrictions, recusals, publication freezes, transaction holds, controlled-room restrictions, or public authority clarification pending full review.
209.5 Classification
209.5.1 Conflict classification shall identify the conflict category, severity, affected matter, affected authority surface, affected records, affected public meaning, affected access, affected outputs, required reviewers, and required escalation.
209.5.2 Classification may include no conflict, immaterial conflict, disclosed and manageable conflict, conflict requiring mitigation, conflict requiring recusal, conflict requiring access restriction, conflict requiring independent review, conflict requiring Board review, prohibited conflict, unresolved conflict, under-investigation conflict, corrected conflict, or closed conflict.
209.6 Materiality Assessment
209.6.1 Materiality shall be assessed based on value, role, access, authority, decision consequence, public trust, public authority implication, finance-boundary implication, certification implication, procurement implication, recognition implication, provider-neutrality implication, sponsor-control implication, safeguards implication, data / AI / cyber implication, tax implication, nonprofit implication, research integrity implication, technical asset implication, and correctionability.
209.6.2 A low-dollar interest may be material where it affects authority, independence, public trust, protected knowledge, public authority meaning, finance meaning, certification meaning, procurement meaning, or technical control.
209.7 Legal Review Where Required
209.7.1 Legal review shall be required where a conflict may implicate fiduciary duties, nonprofit law, corporate law, tax law, charitable solicitation, contracts, employment, privacy, AI, cybersecurity, public authority law, public records, procurement law, lobbying, political activity, government ethics, sanctions, export-control, controlled technology, competition, civil rights, research ethics, professional boundaries, or regulated-perimeter issues.
209.8 Tax and Private Benefit Review Where Required
209.8.1 Tax and private benefit review shall be required where a conflict may affect tax-exempt or tax-exempt-compatible status, private inurement, impermissible private benefit, excess benefit transactions, reasonable compensation, donor restrictions, sponsorship classification, unrelated business income, charitable solicitation, public support, or restricted fund treatment.
209.9 Public Authority Boundary Review Where Required
209.9.1 Public authority boundary review shall be required where a conflict may affect official-capacity participation, public authority references, public authority data, public authority rooms, regulator-listening status, public finance reader status, emergency-management participation, procurement, grant, regulatory, public finance, public records, public warning, emergency command, or official adoption risk.
209.10 Finance, Securities, Insurance, Lending, Rating, Public Finance, Procurement, Certification, Recognition, and Professional Boundary Review Where Required
209.10.1 Finance and regulated-perimeter review shall be required where a conflict may affect securities, investment advice, broker-dealer activity, finder activity, banking, lending, insurance, underwriting, rating, public finance, procurement, certification, accreditation, recognition, maturity, standing, Docket, Grid, Nexus-compatible status, provider preference, professional advice, public warning, or emergency command.
209.11 Data / AI / Cyber / Privacy Review Where Required
209.11.1 Data / AI / cyber / privacy review shall be required where a conflict involves data access, public authority data, personal information, health-sensitive data, infrastructure-sensitive data, cyber-sensitive materials, community-protected data, protected knowledge, AI systems, model outputs, embeddings, training data, compute records, repositories, credentials, keys, logs, dashboards, or controlled rooms.
209.12 Research Integrity Review Where Required
209.12.1 Research integrity review shall be required where a conflict may affect research design, data selection, evidence interpretation, method selection, benchmark design, model evaluation, authorship, peer review, publication timing, publication conclusions, sponsored research, correction, withdrawal, retraction, or archive.
209.13 Community Safeguards and Protected Knowledge Review Where Required
209.13.1 Community safeguards and protected knowledge review shall be required where a conflict may affect civil rights, accessibility, Tribal or Indigenous protocols, local or territorial knowledge, protected knowledge, public-safe mapping, consent, non-consent, withdrawal, grievance, remedy, non-retaliation, vulnerable communities, or do-no-harm controls.
209.14 Competition, Sanctions, Export-Control, Controlled Technology, Lobbying, Political Activity, Government Ethics, Procurement Integrity, and National Security Sensitivity Review Where Required
209.14.1 Specialized compliance review shall be required where a conflict may affect competition or antitrust discipline, market-sensitive information, clean-room controls, sanctions screening, export-control, controlled technology, national security sensitivity, lobbying, political activity, government ethics, gifts, procurement integrity, grant compliance, or public-sector confidentiality.
209.15 Escalation to Board, Committee, Officer, Counsel, Compliance Function, Safeguards Function, or External Reviewer
209.15.1 A conflict shall be escalated to the Board, a Board committee, an authorized officer, counsel, compliance function, safeguards function, data / AI / cyber function, finance function, public authority learning function, or external reviewer where required by law, this Bylaw, policy, materiality, independence risk, public meaning, or institutional significance.
209.15.2 Escalation shall not be controlled by the conflicted person or by a person under the conflicted person’s influence.
209.16 Conflict Intake, Classification, and Escalation Records
209.16.1 The Corporation shall maintain Conflict Intake, Classification, and Escalation Records identifying intake source, Conflict Case ID, preliminary review, facts received, missing information, classification, materiality assessment, interim controls, review lane, escalation path, reviewers, conflicts of reviewers, actions taken, timing, closeout, and archive status.
Section 210. Recusal, Access Restriction, Deliberation Restriction, Recommendation Restriction, Approval Restriction, and Voting Restriction
210.1 Recusal Purpose
210.1.1 Recusal protects independence, fiduciary integrity, public-benefit purpose, research integrity, evidence integrity, methods integrity, public authority boundary discipline, finance-boundary discipline, certification-boundary discipline, procurement neutrality, provider neutrality, sponsor non-control, safeguards, data / AI / cyber controls, validity-by-record, and correctionability.
210.1.2 Recusal shall be substantive and shall prevent direct and indirect influence, not merely final voting.
210.2 Mandatory Recusal
210.2.1 Mandatory recusal shall be required where law, Articles, this Bylaw, policy, Board action, committee action, conflict determination, counsel advice, compliance review, safeguards review, or prudent governance requires exclusion from a matter.
210.2.2 Mandatory recusal applies where a Covered Person has a material financial interest, institutional conflict, related-party interest, public authority conflict, sponsor or provider conflict, research conflict, data / AI / cyber conflict, safeguards conflict, or other conflict that may impair or appear to impair independent judgment.
210.3 Voluntary Recusal
210.3.1 A Covered Person may voluntarily recuse where the person believes participation may create actual, potential, perceived, structural, relational, reputational, or public-trust concern.
210.3.2 Voluntary recusal shall be recorded and may be accepted, expanded, narrowed, or supplemented by competent authority.
210.4 Recusal From Deliberation
210.4.1 A recused person shall not participate in deliberation, framing, agenda setting, document drafting, meeting preparation, staff direction, reviewer selection, evidence interpretation, method selection, publication framing, public authority messaging, or outcome discussion for the affected matter.
210.5 Recusal From Recommendation
210.5.1 A recused person shall not make, draft, influence, sign, endorse, transmit, or summarize a recommendation concerning the affected matter unless competent authority authorizes limited factual input under recorded restrictions.
210.6 Recusal From Approval
210.6.1 A recused person shall not approve, condition, reject, sign, countersign, certify, authorize, release, publish, pay, contract, admit, grant access, or otherwise decide the affected matter.
210.7 Recusal From Voting
210.7.1 A recused person shall not vote on the affected matter and shall not be counted as a voting participant for that matter except where applicable law requires a different treatment and the record identifies the governing rule.
210.8 Access Restriction
210.8.1 Access restriction shall be imposed where recusal alone is insufficient to protect confidentiality, independence, evidence integrity, public authority materials, finance-sensitive materials, protected knowledge, personal information, cyber-sensitive materials, technical assets, or public-safe publication.
210.8.2 Access restriction may apply to Board materials, committee materials, contracts, financial records, public authority materials, datasets, models, prompts, inference records, compute records, repositories, source code, dashboards, maps, controlled rooms, clean rooms, data rooms, evidence rooms, public authority rooms, no-download rooms, and privileged materials.
210.9 Information Firewall
210.9.1 An information firewall may be required to prevent a conflicted person or Related Party from receiving, transmitting, influencing, storing, forwarding, or indirectly accessing restricted information.
210.9.2 Firewall controls may include technical permissions, document separation, meeting exclusion, communication restrictions, clean-team assignment, independent staff assignment, logging, monitoring, and certification of non-access.
210.10 Clean-Team or Clean-Room Handling
210.10.1 Clean-team or clean-room handling shall be used where conflicts involve competition-sensitive information, market-sensitive information, procurement-sensitive information, finance-sensitive information, provider-sensitive information, public authority-sensitive information, data-sensitive information, cyber-sensitive information, protected knowledge, or confidential technical materials.
210.10.2 Clean-team and clean-room outputs shall be aggregated, sanitized, restricted, or reviewed as appropriate before broader circulation.
210.11 Role Restriction
210.11.1 A conflicted person may be restricted from holding a chair, lead, reviewer, rapporteur, records custodian, publication approver, software release approver, public authority interface, finance-boundary reviewer, safeguards reviewer, or repository maintainer role for the affected matter.
210.12 Delegation Restriction
210.12.1 A conflicted person shall not exercise delegated authority over the affected matter and shall not delegate the matter to a subordinate, affiliate, Related Party, sponsored representative, or person subject to the conflicted person’s influence unless competent authority approves an independent delegation path.
210.13 Meeting Exit and Re-Entry
210.13.1 A recused person may be required to leave the meeting, virtual room, controlled room, data room, public authority room, clean room, or deliberation channel during discussion and decision.
210.13.2 Meeting exit and re-entry shall be recorded where material.
210.14 Minutes Notation
210.14.1 Minutes or records shall identify the recusal, affected matter, recused person, basis where appropriate, departure or access restriction where applicable, vote exclusion, and any limited factual participation authorized.
210.15 Quorum Impact
210.15.1 Where recusal affects quorum, voting threshold, committee authority, Board authority, or approval validity, the matter shall be deferred, escalated, re-routed, or handled under applicable law, Articles, this Bylaw, and competent authority.
210.15.2 A quorum defect shall not be cured by permitting conflicted participation unless permitted by law and recorded with limitation.
210.16 Continuing Participation Where Limited and Approved
210.16.1 A recused person may provide limited factual information only where competent authority determines that the information is necessary, the participation is narrowly scoped, the person does not influence deliberation or decision, and the record identifies the limits.
210.16.2 Limited factual participation shall not include advocacy, recommendation, vote, drafting control, negotiation, pressure, or public characterization.
210.17 Failure to Recuse
210.17.1 Failure to recuse includes failure to disclose, failure to leave deliberation, continued access, back-channel influence, document editing, staff direction, public statement, repository action, AI-generated influence, sponsor pressure, provider pressure, public authority pressure, or any direct or indirect attempt to shape the affected matter.
210.17.2 Failure to recuse may require reconsideration, rescission, correction, access restriction, suspension, removal, contract remedy, public or controlled clarification, legal review, or referral.
210.18 Recusal and Restriction Records
210.18.1 The Corporation shall maintain Recusal and Restriction Records identifying the conflict, affected matter, recused person, basis, scope, access restriction, meeting exclusion, vote exclusion, limited factual participation, quorum impact, information firewall, technical controls, monitoring, violation, correction, closeout, and archive status.
Section 211. Independent Review, Disinterested Approval, Fairness Determination, Comparability, and Best-Interest Finding
211.1 Independent Review Purpose
211.1.1 Independent review ensures that conflicted matters, related-party transactions, compensation arrangements, support relationships, sponsor or provider relationships, public authority interfaces, finance-adjacent outputs, certification-adjacent claims, procurement-adjacent matters, safeguards matters, data / AI / cyber matters, and technical asset matters are reviewed by persons able to exercise independent judgment for the Corporation’s public-benefit purposes.
211.2 Disinterested Decision-Makers
211.2.1 A disinterested decision-maker is a person who does not have a material conflict, Related Party interest, dependence, loyalty, role, compensation, public authority constraint, sponsor relationship, provider relationship, capital actor relationship, safeguards conflict, or other interest that may affect judgment on the matter.
211.2.2 Disinterested decision-makers shall disclose their own conflicts before reviewing the matter.
211.3 Independent Committee Review
211.3.1 A matter may be referred to an independent Board committee, standing committee, special committee, or other competent body composed of disinterested persons.
211.3.2 The committee shall have a recorded mandate, access to relevant records, authority to request information, authority to impose interim controls where delegated, and duty to report findings.
211.4 External Review Where Appropriate
211.4.1 External review may be required where the matter is high-risk, technically complex, legally sensitive, tax-sensitive, public authority-sensitive, finance-sensitive, certification-sensitive, procurement-sensitive, safeguards-sensitive, data / AI / cyber-sensitive, or institutionally significant.
211.4.2 External reviewers shall be screened for conflicts, confidentiality capacity, data / AI / cyber eligibility, sanctions and export-control concerns where applicable, and professional competence.
211.5 Legal Review
211.5.1 Legal review shall be obtained where required by law, Board policy, counsel determination, material risk, regulated-perimeter concern, public authority concern, litigation risk, investigation risk, contract risk, privilege concern, or significant institutional consequence.
211.6 Tax Review
211.6.1 Tax review shall be obtained where a matter may affect tax-exempt or tax-exempt-compatible posture, private inurement, impermissible private benefit, excess benefit, unrelated business income, charitable solicitation, donor restrictions, sponsorship classification, grant treatment, compensation, reimbursement, or public support.
211.7 Comparability Data
211.7.1 Comparability data may be required for compensation, contracts, related-party transactions, provider arrangements, technical services, in-kind valuation, IP licensing, consulting, grants, fellowships, stipends, awards, reimbursements, and other benefit arrangements.
211.7.2 Comparability data may include market rates, nonprofit benchmarks, public-benefit context, role scope, expertise, scarcity, deliverables, alternatives, independent quotes, prior transactions, grant restrictions, and budget constraints.
211.8 Fair Market Value Review
211.8.1 Fair market value review shall assess whether the Corporation receives or pays value consistent with lawful, reasonable, and arm’s-length terms, subject to public-benefit purpose and nonprofit constraints.
211.8.2 Fair market value alone shall not justify a transaction that creates capture, private inurement, impermissible private benefit, public authority confusion, finance overclaim, certification overclaim, procurement advantage, provider preference, or safeguards harm.
211.9 Fairness Determination
211.9.1 A fairness determination shall assess whether the transaction or matter is fair to the Corporation, consistent with public-benefit purpose, reasonable in scope, properly documented, free from prohibited control, and compatible with institutional integrity.
211.10 Reasonableness Determination
211.10.1 A reasonableness determination shall assess amount, scope, timing, necessity, alternatives, budget, deliverables, restrictions, conflicts, dependency, and public-benefit justification.
211.11 Best-Interest Finding
211.11.1 A best-interest finding shall determine whether the action serves the best interests of the Corporation as a United States nonprofit, public-benefit, non-executing technical institution and not the private interest of a Covered Person, Related Party, sponsor, provider, public authority participant, capital actor, national company, Project SPV, or enterprise actor.
211.12 Public-Benefit Purpose Finding
211.12.1 A public-benefit purpose finding shall identify how the matter advances evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, public authority learning, safeguards, education, or another lawful public-benefit purpose of the Corporation.
211.13 No Private Inurement Finding
211.13.1 A no-private-inurement finding shall determine that no net earnings, assets, rights, institutional opportunities, technical assets, data assets, or public-good value are being distributed or diverted to insiders or private persons in violation of nonprofit or tax constraints.
211.14 No Impermissible Private Benefit Finding
211.14.1 A no-impermissible-private-benefit finding shall determine that any private benefit is incidental, lawful, reasonable, proportionate, mission-aligned, and not inconsistent with the Corporation’s public-benefit purpose.
211.15 Anti-Capture Finding
211.15.1 An anti-capture finding shall determine that the matter does not give a sponsor, donor, funder, provider, host, public authority, capital actor, national company, Project SPV, enterprise actor, or Related Party improper control over governance, agenda, evidence, methods, publication, public authority access, technical baselines, public-good software, records, controlled vocabulary, correction, or public meaning.
211.16 Boundary Compliance Finding
211.16.1 A boundary compliance finding shall determine that the matter does not create or imply public authority delegation, public warning, emergency command, finance-readiness, securities activity, investment advice, lending, insurance, underwriting, rating, public finance approval, procurement approval, certification, accreditation, recognition, provider preference, professional advice, or enterprise execution by the Corporation.
211.17 Conditions, Mitigation, Monitoring, or Denial
211.17.1 Independent review may result in approval, conditional approval, mitigation, monitoring, limitation language, access restriction, recusal, ring-fencing, clean-room handling, contract changes, public-safe disclosure, controlled disclosure, denial, refusal, return, termination, withdrawal, re-scoping, or Board escalation.
211.18 Independent Review and Approval Records
211.18.1 The Corporation shall maintain Independent Review and Approval Records identifying the matter, reviewers, reviewer conflicts, disclosures, materials reviewed, comparability data, legal review, tax review, fairness determination, reasonableness determination, best-interest finding, public-benefit purpose finding, no-private-inurement finding, no-impermissible-private-benefit finding, anti-capture finding, boundary compliance finding, approval or denial, conditions, monitoring, correction, and closeout.
Section 212. Conflict Mitigation Measures
212.1 Mitigation Purpose
212.1.1 Conflict mitigation measures shall preserve institutional independence, public-benefit purpose, nonprofit integrity, evidence integrity, methods integrity, research integrity, technical asset integrity, public authority boundaries, finance boundaries, certification boundaries, procurement neutrality, provider neutrality, sponsor non-control, data / AI / cyber controls, safeguards, validity-by-record, and correctionability.
212.1.2 Mitigation shall be proportionate to risk and shall be strengthened where ambiguity, public trust risk, protected knowledge risk, public authority risk, finance risk, certification risk, procurement risk, sponsor-control risk, provider-preference risk, or enterprise-stack risk exists.
212.2 Disclosure
212.2.1 Disclosure may be used as a mitigation measure only where disclosure is sufficient to allow informed review and where the conflict can be safely managed without further restriction.
212.2.2 Disclosure alone shall not cure a material conflict requiring recusal, access restriction, independent review, denial, refusal, or termination.
212.3 Recusal
212.3.1 Recusal may be required from deliberation, recommendation, approval, vote, review, drafting, publication, release, public statement, access, technical action, data action, AI action, public authority interface, or other influence.
212.4 Access Restriction
212.4.1 Access restriction may be imposed to protect confidential materials, privileged materials, public authority data, finance-sensitive materials, commercially sensitive materials, personal information, health-sensitive data, cyber-sensitive materials, infrastructure-sensitive materials, protected knowledge, technical assets, models, repositories, and controlled rooms.
212.5 Role Restriction
212.5.1 Role restriction may prevent a conflicted person from serving as chair, lead, reviewer, records custodian, public authority interface, publication approver, software release approver, procurement reviewer, finance-boundary reviewer, safeguards reviewer, or technical maintainer for the affected matter.
212.6 Committee Restriction
212.6.1 Committee restriction may remove or suspend a person from a committee, council, working group, forum, panel, competence cell, controlled-room group, clean-room group, or advisory body for a matter, class of matters, or term of service.
212.7 Voting Restriction
212.7.1 Voting restriction may prevent a conflicted person from voting on an affected matter and may require exclusion from quorum calculations where required by law, Articles, this Bylaw, policy, or determination.
212.8 Segregation of Duties
212.8.1 Segregation of duties may require separation among request, review, approval, execution, payment, publication, release, repository merge, data access, AI processing, controlled-room admission, monitoring, and correction functions.
212.9 Independent Reviewer
212.9.1 An independent reviewer may be appointed to review facts, evidence, methods, compensation, fair value, technical assets, data handling, AI use, cyber controls, public authority risk, finance-boundary risk, certification-boundary risk, procurement risk, safeguards risk, or correction.
212.10 Clean-Team Handling
212.10.1 Clean-team handling may be used to isolate conflicted or sensitive information from persons whose roles, employers, sponsors, providers, capital interests, public authority roles, or enterprise relationships create risk.
212.11 Clean-Room Handling
212.11.1 Clean-room handling may be used where the matter involves competition-sensitive, market-sensitive, provider-sensitive, finance-sensitive, public authority-sensitive, data-sensitive, cyber-sensitive, infrastructure-sensitive, or protected knowledge materials.
212.12 Information Firewall
212.12.1 An information firewall may restrict communication, document access, repository access, meeting access, data access, AI access, model access, controlled-room access, and informal influence between conflicted and disinterested persons.
212.13 Public-Safe Disclosure
212.13.1 Public-safe disclosure may be required where external users, public authorities, researchers, communities, funders, sponsors, providers, capital readers, or the public may reasonably rely on an output affected by a conflict.
212.13.2 Public-safe disclosure shall be accurate, limited, non-defamatory, privacy-respecting, privilege-preserving, and sufficient to prevent misleading reliance.
212.14 Controlled Disclosure
212.14.1 Controlled disclosure may be required where a conflict must be disclosed to the Board, committee, counsel, compliance function, funder, public authority, controlled-room participants, reviewers, affected community, or other limited audience, but public disclosure would create confidentiality, privacy, privilege, legal, cyber, public authority, or safeguards risk.
212.15 Sponsor, Provider, Donor, Funder, Host, or Enterprise Ring-Fencing
212.15.1 Ring-fencing may separate sponsor, provider, donor, funder, host, or enterprise actor support from governance, research design, evidence conclusions, method design, public authority access, publication timing, technical baseline content, public-good software release, correction, certification claims, recognition claims, finance-readiness claims, procurement signals, or Nexus-facing language.
212.16 Contractual Control
212.16.1 Contractual control may include conflict clauses, confidentiality clauses, IP clauses, data clauses, AI-use restrictions, cyber controls, public authority boundary clauses, non-reliance clauses, non-endorsement clauses, sponsor non-control clauses, provider neutrality clauses, publication independence clauses, correction clauses, audit rights, termination rights, and remedies.
212.17 Conflict Monitor
212.17.1 The Corporation may appoint a conflict monitor to oversee compliance with mitigation measures, access restrictions, recusal, ring-fencing, reporting, disclosure, public-safe language, and correction obligations.
212.18 Time-Limited Permission
212.18.1 Permission to proceed despite a manageable conflict may be time-limited, matter-limited, access-limited, role-limited, output-limited, or condition-limited.
212.18.2 Time-limited permission shall require renewal review before extension.
212.19 Renewal Review
212.19.1 Conflict mitigation shall be reviewed periodically or upon material change. Renewal review shall assess whether conditions remain adequate, whether the conflict has worsened, whether public meaning has changed, whether records remain complete, and whether additional mitigation is required.
212.20 Refusal, Return, Termination, Suspension, Withdrawal, or Re-Scoping
212.20.1 Where a conflict cannot be safely mitigated, the Corporation may refuse a transaction, return support, terminate an arrangement, suspend participation, withdraw from a project, re-scope activity, revoke access, freeze publication, or abandon the matter.
212.20.2 The Corporation shall prefer lawful refusal, narrowing, or termination over mission drift, private benefit, sponsor control, provider preference, public authority confusion, finance overclaim, certification overclaim, procurement overclaim, protected knowledge exposure, or public-safe publication defect.
212.21 Conflict Mitigation Records
212.21.1 The Corporation shall maintain Conflict Mitigation Records identifying the conflict, affected matter, mitigation selected, rationale, responsible person, conditions, timeline, monitoring, public-safe disclosure, controlled disclosure, recusal, access restriction, ring-fencing, contract controls, renewal review, violation, correction, closeout, and archive status.
Section 213. Gifts, Hospitality, Travel, Honoraria, Speaking Fees, Sponsored Attendance, and Benefits
213.1 Gifts and Hospitality Purpose
213.1.1 Gift, hospitality, travel, honoraria, speaking fee, sponsored attendance, and benefit controls protect the Corporation from bribery, corruption, subtle influence, sponsor capture, donor capture, provider preference, public authority confusion, procurement distortion, research distortion, publication pressure, finance-boundary overclaim, certification-boundary overclaim, recognition overclaim, and improper private benefit.
213.1.2 Such controls apply to all Covered Persons and to benefits offered by or through sponsors, donors, funders, providers, vendors, contractors, hosts, public authorities, investors, insurers, lenders, underwriters, banks, universities, laboratories, national companies, Project SPVs, enterprise actors, media actors, community participants, and Related Parties.
213.2 Gift Definition
213.2.1 A gift includes anything of value given without full fair-value consideration, including money, goods, services, discounts, tickets, memberships, subscriptions, software access, hardware, meals, entertainment, travel, lodging, access, honoraria, consulting opportunities, employment opportunities, speaking opportunities, platform access, public visibility, or favors.
213.3 Hospitality Definition
213.3.1 Hospitality includes meals, receptions, entertainment, event access, hosted gatherings, private briefings, VIP access, travel-related support, social events, recreational activities, and other hosted benefits.
213.4 Travel Benefit Definition
213.4.1 A travel benefit includes transportation, lodging, meals, registration fees, per diem, local transport, visa support, companion travel, upgrades, hosted tours, conference access, field visit support, or other travel-related support.
213.5 Honorarium Definition
213.5.1 An honorarium means a payment, stipend, token payment, courtesy payment, or equivalent benefit for speaking, teaching, reviewing, advising, participating, presenting, attending, writing, moderating, judging, or contributing.
213.6 Speaking Fee Definition
213.6.1 A speaking fee means compensation or benefit for appearing, speaking, presenting, moderating, briefing, panel participation, media participation, teaching, training, or public representation.
213.7 Sponsored Attendance Definition
213.7.1 Sponsored attendance means payment, waiver, discount, access, travel, lodging, event admission, controlled-room admission, public authority room access, or other benefit provided to enable or encourage attendance at a meeting, event, conference, training, Academy program, Nexus Universe activity, public authority session, controlled room, or other Corporation-related activity.
213.8 Benefit Definition
213.8.1 A benefit includes any tangible or intangible advantage that may affect or appear to affect judgment, including access, visibility, status, employment opportunity, consulting opportunity, research opportunity, publication opportunity, funding opportunity, public authority proximity, technical access, data access, AI access, repository access, controlled-room access, or business opportunity.
213.9 Prohibited Gifts
213.9.1 The Corporation prohibits bribes, kickbacks, facilitation payments, cash gifts, cash equivalents, hidden commissions, improper discounts, personal favors, family benefits, side payments, luxury gifts, excessive gifts, repeated gifts that create dependency, and gifts intended or reasonably appearing to influence institutional action.
213.9.2 Gifts connected to procurement, provider selection, sponsorship, donations, grants, public authority access, research conclusions, publication timing, technical baseline inclusion, software release, public-safe claims, finance-readiness, certification, recognition, Docket, Grid, Nexus-compatible status, or public authority interface shall be refused unless competent authority determines a lawful and de minimis exception applies.
213.10 Prohibited Hospitality
213.10.1 The Corporation prohibits hospitality that is excessive, hidden, repeated, conditioned, lavish, personal, unrelated to institutional purpose, connected to an affected decision, or likely to create appearance of improper influence.
213.10.2 Hospitality shall not be accepted where it may affect public authority interfaces, procurement, provider neutrality, sponsor non-control, finance-boundary matters, certification-boundary matters, research integrity, evidence integrity, safeguards, protected knowledge, or publication independence.
213.11 Prohibited Sponsored Travel
213.11.1 Sponsored travel shall be prohibited where it is intended or likely to influence judgment, purchase access, create sponsor control, create provider preference, influence public authority access, affect publication, affect research, affect procurement, affect finance-readiness, affect certification, affect recognition, or generate private benefit.
213.11.2 Sponsored travel may be permitted only where lawful, mission-aligned, reasonable, disclosed, approved, recorded, and not inconsistent with independence, public trust, government ethics, tax rules, grant rules, procurement rules, or public authority restrictions.
213.12 Prohibited Honoraria or Speaking Fees Where Conflict Exists
213.12.1 Honoraria or speaking fees shall be prohibited where the source, amount, timing, subject matter, audience, affected decision, or relationship creates a conflict that cannot be safely mitigated.
213.12.2 Honoraria or speaking fees related to sponsors, providers, public authorities, capital actors, national companies, Project SPVs, procurement matters, finance-adjacent matters, certification-adjacent matters, recognition matters, public-safe reports, technical baselines, or Nexus-compatible claims shall require heightened review.
213.13 Public Authority Gift Rules
213.13.1 Gifts, hospitality, travel, honoraria, speaking fees, sponsored attendance, or benefits involving public officials, public employees, public authority participants, regulator-listening participants, procurement officials, grant officials, public finance actors, emergency management personnel, or public infrastructure operators shall comply with applicable government ethics, gifts, travel, public records, procurement, grant, lobbying, political activity, and public-sector rules.
213.13.2 The Corporation shall not offer or provide a benefit to influence public authority action, procurement, funding, regulation, public finance, official adoption, public warning, emergency command, or sovereign decision.
213.14 Government Ethics Rules
213.14.1 Government ethics rules shall be reviewed where a Covered Person holds public office, public employment, advisory status, government contract role, procurement role, grant role, regulator role, public finance role, emergency management role, or public infrastructure role.
213.14.2 Where public-sector rules are more restrictive than this Bylaw, the more restrictive lawful rule shall apply.
213.15 Sponsor and Provider Gift Rules
213.15.1 Gifts, hospitality, travel, honoraria, speaking fees, sponsored attendance, or benefits from sponsors or providers shall be reviewed for sponsor control, provider preference, procurement risk, public authority access risk, research influence, publication influence, technical baseline influence, software release influence, certification overclaim, recognition overclaim, finance overclaim, and public-safe claims risk.
213.15.2 A sponsor or provider benefit shall not create or imply preferred status, procurement advantage, public authority endorsement, certification, recognition, finance-readiness, Nexus-compatible status, or control over outputs.
213.16 Donor and Funder Gift Rules
213.16.1 Gifts or benefits from donors and funders shall be reviewed for donor control, funder control, restricted fund influence, reporting pressure, public acknowledgment pressure, publication influence, research influence, program influence, and private benefit.
213.17 Contractor and Vendor Gift Rules
213.17.1 Gifts or benefits from contractors, vendors, consultants, service providers, cloud providers, AI providers, cybersecurity providers, data processors, repository providers, equipment providers, and technical suppliers shall be reviewed for procurement integrity, vendor selection, contracting influence, technical dependency, and provider neutrality.
213.18 De Minimis Threshold Where Approved
213.18.1 The Board or authorized policy may establish a de minimis threshold for modest, ordinary-course, lawful, non-cash, non-repeated, non-decision-linked benefits.
213.18.2 No de minimis threshold shall apply to cash, cash equivalents, bribes, kickbacks, prohibited benefits, public authority violations, procurement-linked benefits, finance-linked benefits, certification-linked benefits, recognition-linked benefits, or benefits intended to influence.
213.19 Disclosure Requirement
213.19.1 Covered Persons shall disclose gifts, hospitality, travel, honoraria, speaking fees, sponsored attendance, and benefits where required by policy, where above threshold, where connected to an affected matter, where offered by a sponsor, provider, public authority, donor, funder, host, vendor, contractor, capital actor, national company, Project SPV, or enterprise actor, or where a reasonable person could perceive influence.
213.20 Approval Requirement
213.20.1 Approval shall be required before accepting any benefit that is not clearly permitted by policy.
213.20.2 Approval shall be disinterested, recorded, and based on value, source, timing, purpose, affected matter, public meaning, public authority restrictions, tax implications, procurement implications, finance implications, certification implications, research implications, safeguards implications, and public-trust risk.
213.21 Return, Decline, Donation, or Reimbursement
213.21.1 A prohibited or unapproved benefit shall be declined, returned, reimbursed, donated where lawful and appropriate, surrendered to the Corporation, or otherwise handled under policy.
213.21.2 Where return or refusal may create public authority, diplomatic, community, Tribal, Indigenous, cultural, or safety sensitivity, the Corporation shall apply lawful and respectful handling while preserving independence and records.
213.22 Gift and Hospitality Register
213.22.1 The Corporation shall maintain a Gift and Hospitality Register recording disclosed gifts, hospitality, travel, honoraria, speaking fees, sponsored attendance, benefits, approvals, refusals, returns, reimbursements, donations, exceptions, and corrective actions.
213.23 Gift, Hospitality, Travel, Honoraria, Speaking Fee, Sponsored Attendance, and Benefit Records
213.23.1 The Corporation shall maintain Gift, Hospitality, Travel, Honoraria, Speaking Fee, Sponsored Attendance, and Benefit Records identifying source, recipient, Related Party where applicable, value, description, date, purpose, affected matter, approval authority, conflict classification, public authority implications, sponsor or provider implications, finance or procurement implications, safeguards implications, disposition, correction, and closeout.
Section 214. Cooling-Off, Revolving-Door, Post-Service Restrictions, and Former-Role Controls
214.1 Cooling-Off Purpose
214.1.1 Cooling-off controls protect the Corporation from improper influence, privileged-access conversion, insider advantage, public authority confusion, sponsor capture, provider preference, procurement distortion, finance-boundary overclaim, certification-boundary overclaim, recognition overclaim, protected knowledge misuse, and misuse of institutional records after a person changes role, leaves service, changes employer, joins a provider, joins a sponsor, joins a public authority, joins a capital actor, joins a national company, joins a Project SPV, or otherwise moves between institutional surfaces.
214.1.2 Cooling-off controls shall be interpreted as integrity controls and not as punitive restraints. Their purpose is to preserve the public-benefit mission, non-execution boundary, validity-by-record, correctionability, public authority boundary discipline, finance-boundary discipline, provider neutrality, sponsor non-control, confidentiality, data / AI / cyber safeguards, protected knowledge, and public trust.
214.1.3 Cooling-off controls may apply before, during, and after service where a role transition creates actual, potential, perceived, structural, relational, reputational, technical, financial, public authority, safeguards, or enterprise-stack risk.
214.2 Revolving-Door Purpose
214.2.1 Revolving-door controls protect against the conversion of GCRI US service into later private advantage, market advantage, procurement advantage, financing advantage, recognition advantage, certification advantage, public authority access advantage, repository advantage, technical asset advantage, controlled-room advantage, or public claim advantage.
214.2.2 A revolving-door risk exists where a person moves between the Corporation and any sponsor, donor, funder, provider, vendor, host, public authority, university, laboratory, national company, Project SPV, investor, insurer, lender, bank, underwriter, public finance actor, capital reader, media actor, public-interest organization, community organization, Tribal or Indigenous interface, or other entity whose interests may be affected by the person’s prior or new role.
214.2.3 Revolving-door review shall be required where a person’s prior access, influence, authorship, technical knowledge, confidential information, public authority interface, records role, methods role, publication role, safeguards role, data access, AI access, cyber access, finance-boundary role, or Nexus interface role may create an unfair or misleading advantage after transition.
214.3 Former Director Restrictions
214.3.1 A former director shall remain bound by confidentiality, privilege, records, public-safe claims, role-separation, non-execution, data / AI / cyber, safeguards, public authority boundary, finance-boundary, certification-boundary, procurement-neutrality, provider-neutrality, sponsor non-control, and related obligations that expressly or by necessary implication survive Board service.
214.3.2 A former director shall not use prior Board service to claim continuing governance authority, special access, inside status, preferred provider standing, public authority endorsement, finance-readiness significance, certification significance, recognition significance, procurement advantage, Nexus-compatible status, or authority to speak for the Corporation.
214.3.3 A former director shall not represent that prior Board approval, prior Board deliberation, prior Board materials, prior Board relationships, or prior Board service creates approval of any later transaction, project, provider, sponsor, public authority engagement, funding matter, publication, technical asset, Docket input, Grid input, GRF-facing input, GRA-facing input, or Nexus-facing claim.
214.3.4 Where a former director seeks to transact with, advise, represent, fund, sponsor, provide services to, lobby, influence, review, publish with, or otherwise engage the Corporation in a matter related to the former director’s prior Board service, the matter shall be subject to conflict review, related-party review where applicable, access restriction, and independent approval.
214.4 Former Officer Restrictions
214.4.1 A former officer shall remain bound by all surviving duties arising from appointment, delegation, employment, contractor terms, confidentiality agreements, IP instruments, data access rules, AI-use rules, cyber rules, repository rules, controlled-room rules, public authority interface rules, publication rules, correction rules, and this Bylaw.
214.4.2 A former officer shall not use prior title, delegated authority, institutional knowledge, public authority relationships, sponsor relationships, provider relationships, repository access, controlled-room access, publication authority, technical authorship, methods authorship, or leadership proximity to create apparent continuing authority.
214.4.3 A former officer shall not negotiate, influence, or benefit from a matter that the officer materially shaped while in service unless the matter is reviewed and approved through a disinterested process.
214.4.4 A former officer’s later employment by, consulting for, investment in, representation of, or leadership role in a sponsor, provider, public authority, national company, Project SPV, capital actor, university, laboratory, host, donor, or funder shall trigger review where the new role relates to matters handled by the former officer.
214.5 Former Employee, Contractor, Fellow, Advisor, Volunteer, Committee Member, Council Member, Reviewer, or Contributor Restrictions
214.5.1 A former employee, contractor, fellow, advisor, volunteer, committee member, council member, reviewer, working group participant, maintainer, developer, contributor, rapporteur, panelist, or controlled-room participant shall not use prior access or participation to create improper advantage, public overclaim, insider status, continuing authority, or unauthorized reliance.
214.5.2 Such persons shall not disclose or use confidential information, privileged information, public authority materials, personal information, health-sensitive information, infrastructure-sensitive information, cyber-sensitive information, community-protected information, Tribal or Indigenous knowledge, protected knowledge, unpublished evidence, draft methods, draft publications, source code, credentials, keys, tokens, model prompts, inference records, compute records, repository materials, or controlled-room materials except as expressly authorized.
214.5.3 Former role participants shall not present themselves as continuing reviewers, maintainers, advisors, representatives, fellows, public authority liaisons, or Nexus interface actors unless a current written role record authorizes such status.
214.6 Former Public Authority Role Controls
214.6.1 Where a Covered Person has formerly served in a federal, state, territorial, Tribal, local, District of Columbia, public infrastructure, public health, emergency management, public safety, public works, telecom, water, energy, food, cyber, port, utility, public finance, procurement, regulatory, grant, legislative, executive, judicial, or other public authority role, the Corporation shall review whether the former role creates continuing legal, ethical, confidentiality, procurement, lobbying, government ethics, public records, public authority boundary, or public perception constraints.
214.6.2 A former public authority role shall not be used to imply public authority endorsement, privileged government access, official adoption, procurement likelihood, funding likelihood, public finance approval, regulatory approval, public warning authority, emergency command authority, or sovereign mandate.
214.6.3 Where a former public authority role creates restricted communications, cooling-off rules, gift restrictions, procurement restrictions, lobbying restrictions, representation limits, or confidentiality obligations, the Corporation shall apply the more restrictive lawful rule.
214.7 Former Provider, Sponsor, Donor, Funder, Host, National Company, Project SPV, Investor, Insurer, Lender, Bank, Public Finance Actor, or Enterprise Role Controls
214.7.1 Where a Covered Person formerly served a provider, sponsor, donor, funder, host, national company, Project SPV, investor, insurer, lender, bank, underwriter, public finance actor, capital reader, cloud provider, AI provider, cybersecurity provider, data processor, equipment supplier, integration provider, or enterprise actor, the Corporation shall review whether the former role creates conflict, loyalty, confidentiality, procurement, influence, data, IP, cyber, public authority, finance-boundary, or provider-neutrality risk.
214.7.2 A former enterprise-side role shall not be treated as disqualifying by default, but it shall be disclosed, classified, and managed where it may affect evidence, methods, technical baselines, public-good software, procurement neutrality, provider neutrality, sponsor non-control, public authority access, public-safe claims, or Nexus-facing outputs.
214.7.3 A person with a recent or material enterprise-side role shall not lead review of that entity, its competitors, its products, its proposed technical baseline, its evidence submission, its public authority engagement, its finance-facing materials, its provider-status claim, or its Nexus-compatible claim unless competent authority records a narrow, lawful, and independently supervised exception.
214.8 Post-Service Confidentiality
214.8.1 Confidentiality obligations survive the end of service, appointment, employment, engagement, committee participation, council participation, controlled-room access, repository access, advisory role, fellowship, volunteer service, or contributor status.
214.8.2 Post-service confidentiality applies to confidential governance information, privileged material, Board materials, committee materials, financial records, donor records, sponsor records, public authority materials, public authority capacity records, controlled-room materials, clean-room materials, evidence-room materials, data-room materials, no-download room materials, research records, unpublished drafts, protected knowledge, personal information, cyber-sensitive materials, infrastructure-sensitive materials, software security information, credentials, and other restricted materials.
214.8.3 Post-service confidentiality shall not prevent lawful whistleblowing, protected reporting, legal compliance, regulator communication, court-ordered disclosure, or other legally protected conduct, subject to lawful preservation of privilege, privacy, public safety, protected knowledge, and confidentiality where applicable.
214.9 Post-Service Data, AI, Cyber, Repository, and Controlled-Room Access Revocation
214.9.1 Upon transition, resignation, removal, termination, completion of assignment, expiry of role, suspension, or other change in authority, the Corporation shall revoke or reclassify access to data, AI systems, compute environments, repositories, credentials, keys, tokens, dashboards, maps, models, inference records, compute records, controlled rooms, clean rooms, data rooms, evidence rooms, public authority rooms, no-download rooms, and collaboration systems.
214.9.2 Access revocation shall include, where applicable:
214.9.2(a) removal of role-based permissions; 214.9.2(b) credential, token, and key rotation; 214.9.2(c) repository permission downgrade; 214.9.2(d) controlled-room offboarding; 214.9.2(e) return or deletion of restricted materials; 214.9.2(f) device, account, and cloud access review; 214.9.2(g) audit-log preservation; 214.9.2(h) certification of non-retention where required; and 214.9.2(i) incident escalation where unauthorized access may have occurred.
214.9.3 No former role, friendship, founder proximity, technical centrality, emergency convenience, or pending transition shall justify unrecorded continuing access.