II. Boundaries
12. Purpose, Constitutional Function, and Governing Rule
12.1 Purpose
This Part II establishes the bright-line constitutional perimeter of GCRI US as a nonprofit, public-benefit, scientific, educational, and strictly non-executing institution. Its purpose is to define, preserve, and enforce the boundary between what the Corporation may lawfully and constitutionally do in service of its exempt purposes and what it may never do because such acts would constitute, approximate, imply, facilitate, or drift into regulated execution, sovereign substitution, market-facing intermediation, supervisory effect, or other consequence-bearing functions inconsistent with the Corporation’s legal identity and mission.
Part II shall be read as a perimeter-protection instrument of first importance. It does not merely list undesirable activities. It sets the governing rule by which all programs, outputs, systems, partnerships, publications, technical architectures, institutional relationships, and revenue models of the Corporation must be evaluated before launch, during operation, and upon review. Its function is preventive as much as prohibitory. It exists to stop the Corporation from becoming, by ambition, convenience, technical centrality, external demand, or repeated operational drift, an institution other than the one lawfully constituted in Part I.
Accordingly, this Part shall be interpreted as:
a) a constitutional guardrail against role collapse; b) a legal and tax-protective discipline for preservation of 501(c)(3)-compatible posture; c) an anti-capture and anti-overclaim framework; d) a control structure for identifying and containing edge-of-perimeter risk; and e) a standing reminder that technical seriousness does not authorize execution, and public-benefit relevance does not authorize regulatory or market consequence.
No reader shall interpret the absence of a particular factual scenario from this Part as permission to cross the perimeter by novel form, technical indirection, or softer language. The perimeter applies by substance, not by drafting exhaustiveness.
12.2 Relationship of Part II to Mission Lock and Public-Benefit Mandate
This Part II shall be read together with Part I, and especially with the Corporation’s mission lock, exempt-purpose posture, public-benefit identity, non-execution doctrine, and doctrinal anchors. Part II is the principal operational expression of those constitutional commitments in the specific context of regulated, execution-bearing, approval-bearing, market-facing, and institutionally substitutive risk. It is therefore not independent from mission lock; it is one of the primary legal and governance means by which mission lock is preserved.
The Corporation’s public-benefit mandate depends not only on what it affirmatively produces, but also on what it refuses to become. The integrity of the Corporation’s role as a steward of evidence systems, observability, methods, public-good infrastructure, training, and scientific-operational discipline would be materially compromised if it were allowed to drift into:
a) transaction-facing roles; b) regulatory or sovereign proxy roles; c) market intermediation; d) execution-bearing technical orchestration; e) donor-shaped approval or routing functions; or f) any activity that creates private benefit or public misunderstanding inconsistent with exempt purpose.
For that reason, Part II shall be treated as a mission-preserving discipline and not as a mere compliance appendix. A proposal may appear attractive, strategic, innovative, socially useful, or ecosystem-relevant, yet still be prohibited because it would compromise the Corporation’s constitutional identity. Public-benefit purpose does not dilute the importance of perimeter discipline. It strengthens it. The more mission-significant the Corporation becomes, the greater the need for clear refusal of roles that belong elsewhere.
Where tension appears between an apparently valuable opportunity and the rules of Part II, the Corporation shall prefer constitutional fidelity over opportunistic expansion. Mission is not a justification for perimeter breach. Mission is the reason perimeter discipline must hold.
12.3 Priority of Perimeter Safety Over Convenience, Speed, Funding, or Strategic Opportunity
Perimeter safety shall have priority over convenience, operational speed, ecosystem demand, donor interest, revenue opportunity, technical feasibility, public visibility, strategic advantage, or institutional centrality. No program, output, partnership, infrastructure design, release train, public statement, or workflow shall proceed merely because it appears urgent, attractive, fundable, or technically possible if there is a material and unresolved risk that it crosses, obscures, or weakens the Corporation’s non-executing boundary.
This priority rule applies across all corporate functions, including without limitation:
a) program design and productization; b) fundraising, sponsorship, and partner negotiation; c) technical architecture and platform operation; d) publication, communications, and public claims; e) institutional interfaces with regulated or sovereign actors; f) educational and capability-building offerings; and g) any domestic or cross-border activity whose practical effect could implicate regulated or consequence-bearing roles.
The Corporation shall therefore maintain a standing institutional posture that treats perimeter safety as a threshold condition rather than a downstream cleanup exercise. If perimeter integrity is uncertain, the proper response is not optimistic implementation followed by later rationalization. The proper response is review, narrowing, hold, redesign, or refusal as appropriate.
For purposes of this rule, “perimeter safety” includes not only avoiding direct regulatory breach, but also avoiding:
i) material public misunderstanding regarding institutional role; ii) shadow execution through interface design, partner dependence, or narrative compression; iii) hidden approval surfaces; iv) improper private benefit or influence purchase; and v) any structure that would put the Corporation’s exempt status, public-benefit legitimacy, or constitutional boundedness at unreasonable risk.
12.4 Most-Restrictive Reading Rule Where Execution or Regulatory Ambiguity Exists
Where there is ambiguity as to whether an activity, output, system feature, partnership, representation, technical architecture, or institutional practice may constitute or approximate regulated execution, public-authority substitution, market intermediation, supervisory effect, routeability or approval simulation, or any other prohibited consequence-bearing role, the most restrictive reasonable interpretation shall govern unless and until the ambiguity is resolved through appropriate legal, compliance, and governance review.
For purposes of this Section, the “most restrictive reasonable interpretation” means the interpretation that best preserves:
a) non-execution doctrine; b) exempt-purpose and 501(c)(3)-compatible posture; c) public-benefit legitimacy; d) truthful role description; e) anti-capture and anti-private-benefit discipline; and f) constitutional separation from recognition, adoption, protocol authority, sovereign function, and execution-bearing activity.
This rule applies not only to direct acts, but also to indirect, hybrid, technical, embedded, branded, delegated, partner-mediated, or seemingly de minimis forms of activity. The Corporation shall not rely on:
i) ambiguous wording; ii) complexity of technical architecture; iii) novel product or workflow design; iv) disclaimers inconsistent with practical effect; or v) ecosystem shorthand
to argue for a less restrictive reading where substantive ambiguity remains.
If a plausible reading would place the Corporation inside or too near a prohibited perimeter, the Corporation shall presume that the activity is impermissible or must be materially narrowed until a contrary conclusion is reached through proper review and recorded determination. Hopeful interpretation shall not substitute for perimeter discipline.
12.5 Binding Effect of Part II Across All Organs, Programs, Outputs, and Interfaces
This Part II shall bind the Corporation as a whole and every corporate organ, officer, committee, employee, contractor, fellow, advisor, participant, program office, technical team, repository custodian, training function, platform environment, observatory, public-facing channel, and external interface acting in the Corporation’s name, under its authority, or through its systems. No internal structure, however specialized, technical, temporary, experimental, or partner-facing, shall be exempt from the boundary rules of this Part.
The binding effect of this Part extends to:
a) governance acts and internal delegations; b) technical architecture, tooling, and system behavior; c) contracts, grant instruments, sponsorship terms, and partnership arrangements; d) product and service design, including educational and capability offerings; e) all public and controlled communications; f) platform and repository operations; and g) all interfaces with regulated, sovereign, commercial, or execution-bearing actors.
No policy, program logic, funding arrangement, or operational necessity may derogate from this Part unless an exception is expressly authorized by law and by a properly recorded act of the competent authority, and even then only to the narrowest extent necessary and in a manner fully consistent with the Corporation’s Articles, exempt-purpose posture, and Part I. No informal waiver, custom, silence, or technical workaround shall have effect against the perimeter rules of this Part.
All persons subject to this Part shall have an affirmative duty to interpret and apply it conservatively, to escalate credible edge-of-perimeter issues promptly, and to refrain from proceeding where material ambiguity or breach risk remains unresolved. Perimeter discipline is not the sole responsibility of counsel or compliance personnel. It is a standing constitutional obligation of the entire institution.
13. Bright-Line Non-Execution Rule (GCRI United States)
13.1 GCRI US as a Non-Executing Institution
GCRI US is, and shall remain, a non-executing institution. This is a bright-line constitutional rule and not a matter of degree, aspiration, branding posture, or temporary operating choice. The Corporation is organized and operated as a public-benefit, scientific, educational, and infrastructural steward. It is not an executor of regulated, sovereign, market-facing, fiduciary, or transaction-bearing functions. Its lawful and constitutional role is to produce, steward, maintain, explain, test, document, educate, and improve upstream public-good systems and artifacts that may support serious downstream activity by others acting within their own lawful mandates.
For purposes of these Bylaws, “non-executing” means that the Corporation shall not itself undertake, control, intermediate, compel, authorize, settle, route as principal authority, approve, or otherwise perform acts whose legal or practical substance places the Corporation into the role of a transaction-bearing, approval-bearing, market-facing, supervisory, sovereign, or operationally determinative actor. The Corporation may contribute knowledge, structure, evidence, observability, technical systems, and education. It may not cross the line into being the actor whose act itself changes legal status, market consequence, execution state, sovereign condition, or regulated operational position.
This rule shall be applied by substance and not by presentation. An activity does not become non-executing merely because it is described as technical, mission-driven, supportive, facilitative, experimental, philanthropic, digital, or public-interest in character. If the Corporation’s act would, in practical or legal effect, constitute execution, intermediation, approval, or consequence-bearing direction, the act is prohibited unless lawfully and explicitly authorized in a manner consistent with the Corporation’s Articles, exempt purposes, and these Bylaws, which authorization shall not be presumed.
13.2 No Execution of Regulated, Licensed, or Market-Consequence Activities
The Corporation shall not execute, undertake, or functionally assume any regulated, licensed, supervised, or market-consequence activity. This prohibition applies whether the activity is direct or indirect, full-scale or pilot-scale, compensated or uncompensated, technologically mediated or document-driven, U.S.-domestic or cross-border in interface.
Without limitation, the Corporation shall not execute activities that would reasonably be characterized as:
a) securities issuance, underwriting, placement, brokerage, dealing, advising, or distribution; b) banking, deposit-taking, money transmission, payments, or treasury intermediation; c) insurance, reinsurance, claims administration, MGA, TPA, or risk-carrying functions; d) fund management, asset management, discretionary portfolio activity, or capital allocation; e) exchange operation, trade execution, clearing, settlement, custody, or safeguarding of client assets; f) regulatory approval, licensure, supervisory review, or compliance certification with public effect; g) sovereign, administrative, adjudicative, or public-authority instruction or determination; or h) any analogous activity whose performance depends on a legal status, license, delegated authority, or regulated role the Corporation does not hold.
The Corporation may create educational materials about such activities, structure upstream evidence relevant to them, or support lawful actors with mission-consistent non-directive public-good infrastructure. It may not itself become the actor whose conduct performs or substitutes for those functions. No transaction-facing or approval-bearing consequence shall be allowed to rest on the Corporation’s act.
13.3 No Execution by Narrative Compression, Functional Equivalence, or De Facto Control
The Corporation shall not do indirectly what it may not do directly. Accordingly, no activity, output, workflow, interface, technical system, partner arrangement, or public representation shall be permitted where, in substance, the Corporation is performing execution through narrative compression, functional equivalence, operational indirection, or de facto control.
For purposes of this Section:
a) narrative compression includes describing a consequence-bearing role in softened, abstracted, or euphemistic language so that execution appears to be mere support; b) functional equivalence includes designing an output or system that has the practical effect of approval, routing, transaction facilitation, or binding direction even if formal labels deny that effect; and c) de facto control includes exercising such operational, technical, economic, informational, or reputational influence over another actor’s decision space that the Corporation is, in practice, determining or constraining execution-bearing outcomes.
Examples of prohibited execution by indirection include, without limitation:
i) structuring a workflow that effectively clears a transaction while calling it a readiness review; ii) creating interface states that determine market or operational next steps while describing them as informational only; iii) using technical gating, access privileges, or dependency structures to compel downstream behavior; iv) designing public-good systems so that they become the practical approval surface for a regulated or sovereign act; or v) routing decisions through partners while retaining the real controlling judgment inside the Corporation.
The Corporation shall evaluate practical effect over formal language. If the substance of the arrangement is execution, it is prohibited regardless of wording, interface aesthetics, or architectural complexity.
13.4 No Conversion of Public-Good Infrastructure Into Operational Execution Authority
The Corporation’s public-good systems, repositories, observability environments, semantic layers, methods, training systems, technical tools, and governance-supporting artifacts shall not be converted into operational execution authority. Infrastructure stewardship is not execution authority. Public-benefit technical centrality is not market power. Shared systems are not hidden approval surfaces.
This rule prohibits the use of the Corporation’s infrastructure as:
a) a substitute for regulatory clearance; b) a mandatory gate for execution-bearing acts absent lawful basis; c) a disguised route-to-market, route-to-capital, or route-to-approval channel; d) a control surface by which the Corporation determines who may proceed, transact, or operate in regulated or consequence-bearing contexts; or e) an instrument by which others can represent that the Corporation has validated or authorized an activity beyond its lawful role.
The Corporation may maintain infrastructures that support disciplined understanding, observability, capability formation, interoperability, and correctionability. It may not transform infrastructure custody, technical indispensability, or repository centrality into executive power over others. Where a platform or system begins to function in that manner, the Corporation shall redesign, narrow, gate, re-document, or suspend it as necessary to restore perimeter safety.
13.5 No Implied Expansion of Perimeter by Growth, Technical Capability, or External Demand
The Corporation’s perimeter shall not expand by implication because the Corporation grows, becomes more technically sophisticated, acquires greater institutional visibility, attracts larger partners or funders, becomes operationally central to important ecosystems, or is pressed by external actors to “do more” at the edge of its role. Growth does not amend the Bylaws. Technical capability does not create legal authority. External demand does not cure constitutional prohibition.
Accordingly, the Corporation shall not infer permission to undertake otherwise prohibited activities from any of the following:
a) that no other actor is currently available to perform the function; b) that the Corporation could perform the function more efficiently; c) that stakeholders trust the Corporation to do so; d) that the function seems adjacent to public-benefit purpose; e) that a donor, host, or public institution requests the function; or f) that refusal would impose strategic, reputational, or ecosystem costs.
The more the Corporation becomes useful, technically capable, or central, the greater—not lesser—its obligation to preserve constitutional humility and boundary discipline. If external demand or internal ambition creates pressure to expand the perimeter, that pressure shall be treated as a governance risk and escalated accordingly. The Corporation shall remain what it was lawfully constituted to be, even when others would prefer that it become something else.
13.6 Binding Reading Rule for the Bright-Line Non-Execution Principle
This Section 13 shall be read strictly and as a standing control on every later provision of these Bylaws. Nothing elsewhere in these Bylaws shall be interpreted to authorize an act inconsistent with the bright-line non-execution rule unless such authorization is required by applicable law and expressly and narrowly stated in a duly adopted instrument consistent with the Articles and the Corporation’s exempt-purpose posture. No general corporate power, no educational function, no technical stewardship mandate, no partnership provision, and no public-benefit rationale shall override this Section by implication.
Where ambiguity exists as to whether an act remains on the non-executing side of the line, the interpretation that better preserves non-execution, narrower authority, truthful public description, and safer perimeter shall prevail unless contrary law clearly requires otherwise.
14. Core Regulatory Perimeter Test (GCRI United States)
14.1 Perimeter Test as Mandatory Control Before Action, Output, or Engagement
Before the Corporation undertakes, launches, approves, maintains, materially changes, or publicly describes any program, output, system, workflow, partnership, revenue model, institutional interface, educational offering, observability environment, technical feature, or public claim that could reasonably implicate legal, regulatory, market-facing, sovereign, fiduciary, or execution-bearing consequences, the Corporation shall apply a regulatory perimeter test. The perimeter test is a mandatory institutional control and not a discretionary best practice.
The perimeter test exists to determine, before action is taken, whether the contemplated matter:
a) falls clearly within the Corporation’s lawful, exempt-purpose, non-executing role; b) falls clearly outside that role and is therefore prohibited; or c) presents sufficient ambiguity, risk, or edge-of-perimeter characteristics that escalation, narrowing, hold, redesign, or refusal is required.
This test shall apply not only to new initiatives, but also to:
i) changes to existing systems or programs; ii) changes in practical use of existing outputs; iii) changes in counterparties, jurisdictions, or deployment conditions; iv) changes in revenue logic, funding terms, or partner expectations; and v) changes in public description that may alter perceived institutional meaning.
No person may waive the perimeter test merely because an activity resembles prior work, appears technically routine, is donor-supported, or is pressed by time. If the practical effect, institutional meaning, or recipient interpretation of a matter could move materially, the perimeter test shall be applied again.
14.2 Substance Over Form Rule
In applying the perimeter test, the Corporation shall observe a substance over form rule. Activities, outputs, workflows, labels, technical architectures, interface designs, and public descriptions shall be assessed according to their legal, operational, and practical effect rather than according to the titles, disclaimers, abstractions, euphemisms, or institutional narratives attached to them.
Accordingly, the Corporation shall not treat a matter as safe merely because it is described as:
a) advisory; b) technical; c) educational; d) supportive; e) informational; f) nonprofit; g) mission-driven; or h) public-interest oriented,
if, in substance, it would perform or materially approximate a regulated, sovereign, fiduciary, supervisory, market-facing, approval-bearing, or execution-bearing function.
This rule applies with equal force to:
i) documents that look “non-binding” but are drafted to function as executable instructions; ii) technical systems that appear informational but in practice determine downstream action; iii) partnership models that appear collaborative but embed de facto control; iv) public-safe summaries that imply approvals or standing not lawfully held; and v) revenue arrangements that appear mission-supporting but depend on execution-like outcomes.
The Corporation shall evaluate what the matter actually does, what others are likely reasonably to understand it to do, and what legal or operational consequences it is likely to produce in real use.
14.3 Functional Analysis of Activity, Output, Representation, and Outcome
The perimeter test shall include a functional analysis of the contemplated matter from at least four distinct but related angles:
a) the activity being undertaken; b) the output being produced or maintained; c) the representation being made internally or externally; and d) the outcome likely to follow in law, practice, or institutional understanding.
This functional analysis shall ask, at minimum:
i) What is the Corporation actually doing? ii) What is the artifact, system, or representation likely to be understood as meaning? iii) What consequences are likely to follow if others use, rely on, or respond to it as intended or foreseeably? iv) Would those consequences place the Corporation inside, too near, or materially adjacent to a prohibited role?
A matter may be permissible when viewed as an internal research exercise yet impermissible when externalized as a public-facing instrument. A document may be lawful as a technical note but impermissible if presented in a way that reasonably implies clearance, standing, or readiness. A system may be acceptable in prototype form but problematic once embedded in partner workflows or relied upon by execution-bearing institutions. The perimeter test shall therefore examine the full practical chain and not just the Corporation’s own preferred internal framing.
14.4 Activity Classification by Legal, Regulatory, and Practical Effect
Every perimeter-tested matter shall be classified by reference to its legal effect, regulatory significance, institutional meaning, practical consequences, and risk of role conversion. For purposes of internal discipline, the Corporation may classify a matter into categories such as:
a) clearly permissible within mission and perimeter; b) permissible with controls, meaning the matter may proceed only with specified safeguards, narrowing, documentation, or constraints; c) escalation required, meaning further legal, compliance, or Board review is mandatory before proceeding; d) hold pending review, meaning the matter shall not proceed until classification uncertainty is resolved; or e) prohibited, meaning the matter would cross or materially threaten the perimeter and may not proceed.
Classification shall not be based solely on the good faith of the proposing team or the desirability of the outcome. It shall be based on the actual role the Corporation would occupy if the matter were implemented or represented as proposed. If a matter would reasonably place the Corporation into an ambiguous position vis-à-vis regulated activity, approval effect, market consequence, sovereign implication, or hidden substitution, the classification shall reflect that risk directly and conservatively.
The Corporation shall not collapse classification into informal comfort language such as “probably fine,” “just advisory,” or “it’s only infrastructure.” Such formulations are not classifications and shall not substitute for recorded perimeter analysis.
14.5 Trigger Conditions Requiring Counsel, Compliance, or Board Escalation
The following non-exhaustive circumstances shall trigger mandatory escalation to appropriate legal counsel, compliance review, and, where material, Board-level attention before the matter may proceed:
a) the matter could reasonably be interpreted as involving regulated financial, market, licensing, supervisory, or sovereign effect; b) the matter involves new revenue models, new categories of counterparties, or new operational dependencies near the perimeter edge; c) the matter creates or could create a hidden approval surface, route-to-market surface, client-selection effect, or execution-facing workflow; d) the matter involves domestic or cross-border legal complexity, sanctions, export-control, privacy, data-governance, or sector-specific regulatory risk; e) the matter includes exclusivity, lock-in, vendor dependency, or mission-bearing infrastructure arrangements that could alter practical control; f) the matter includes donor or sponsor conditions touching substance, timing, outputs, or public description; g) the matter materially changes the likely meaning, use, or recipient interpretation of an existing artifact or system; h) the matter risks overstatement of institutional maturity, readiness, supportability, conformance, standing, or approval effect; or i) the matter cannot be confidently classified as clearly permissible by the responsible stewards applying Part I and Part II.
Escalation is a control, not a failure. Teams shall not avoid escalation because it may slow delivery, complicate funding conversations, or require narrowing of proposed activity. Where trigger conditions exist, escalation is mandatory.
14.6 Presumption Against Ambiguous Activities
Where a contemplated activity, output, system, representation, or partnership is materially ambiguous in its legal or institutional character, there shall be a presumption against proceeding in the proposed form. The burden shall rest on the proponent of the matter to demonstrate that it can be lawfully structured, truthfully described, and operationally bounded in a manner consistent with the Corporation’s exempt purposes, non-executing posture, and constitutional role.
This presumption exists because ambiguity at the perimeter edge is itself a form of risk. Ambiguous activities are especially prone to:
a) public overreading; b) partner misuse; c) internal role drift; d) donor or sponsor leverage; e) technical architectures whose practical effect outruns their intended description; and f) post hoc rationalization after the Corporation has already become operationally entangled.
The Corporation shall therefore prefer clearly bounded work over ambitiously ambiguous work. Where a valuable public-benefit objective can be accomplished through a narrower, safer, more role-faithful structure, the narrower structure shall be chosen.
14.7 Mandatory Hold Pending Review Where Classification Is Uncertain
If, after initial assessment, the correct perimeter classification of a matter remains uncertain in a way that could materially affect legality, exempt-purpose compatibility, public meaning, or role separation, the matter shall be placed on mandatory hold pending review. During such hold:
a) no public launch shall occur; b) no external representation shall be made that implies settled institutional status; c) no irreversible technical or contractual commitments shall be undertaken unless necessary for containment or preservation; and d) any continued internal work shall be limited to analysis, narrowing, containment, or redesign activities authorized for the purpose of achieving safe classification.
A mandatory hold is not a suggestion to proceed carefully. It is a prohibition on forward motion in the unresolved form. No team, officer, funder, or partner may override a hold through urgency, strategic pressure, or optimism. If a matter cannot be confidently placed within the perimeter, the Corporation shall pause rather than drift.
14.8 Recording and Auditability of Perimeter Determinations
Every perimeter determination of material significance shall be recorded in a form sufficient to preserve institutional memory, enable later review, support correction where necessary, and demonstrate that perimeter discipline has been applied. The record shall, to the extent appropriate to the matter, include:
a) a description of the activity, output, system, or representation reviewed; b) the relevant facts and context; c) the perimeter issues considered; d) the functional analysis applied; e) the resulting classification; f) any required conditions, mitigations, narrowing steps, or controls; g) whether escalation occurred and to whom; h) the authority on which the determination rests; and i) any review date, sunset, or re-evaluation trigger.
Perimeter determinations shall be treated as part of the Corporation’s governance and control environment, not as disposable advisory notes. Where circumstances materially change, earlier determinations shall be revisited rather than assumed to remain valid indefinitely. Auditability of perimeter reasoning is a protection against drift, memory loss, and unexamined expansion.
14.9 Reassessment Duty Where Use, Context, or Meaning Changes
A perimeter determination shall not be treated as permanently sufficient if the use, context, counterparties, institutional setting, technical architecture, public description, or foreseeable consequences of the matter materially change. The Corporation shall have an affirmative duty to reassess prior perimeter conclusions when:
a) a pilot becomes a scaled program; b) an internal tool becomes a partner-facing or public-facing tool; c) a research artifact becomes embedded in operational workflows; d) a technical feature begins to function as a gate, signal, or clearance layer; e) a domestic use case moves into a higher-risk regulatory environment; or f) public understanding or partner reliance begins to exceed the originally documented meaning of the matter.
Reassessment is required because perimeter safety depends not only on the original design, but on how things evolve in practice. The Corporation shall not rely on stale comfort when real-world use has materially moved.
14.10 Interpretive Rule for the Regulatory Perimeter Test
This Section shall be interpreted as establishing a standing institutional duty to test first, classify conservatively, escalate where necessary, hold where uncertain, record what is decided, and revisit where reality changes. The perimeter test is not a procedural formality. It is the Corporation’s principal decision discipline at the boundary between lawful public-benefit stewardship and prohibited or unsafe role conversion.
Where ambiguity exists in applying this Section, the interpretation that better preserves non-execution, narrower authority, safer perimeter, truthful public meaning, and exempt-purpose fidelity shall prevail.
15. General Prohibition on Regulated Financial and Market Activities (GCRI United States)
15.1 No Banking, Deposit-Taking, or Treasury Intermediation
The Corporation shall not engage in, offer, arrange, intermediate, facilitate as principal authority, or hold itself out as engaging in banking, deposit-taking, treasury intermediation, cash management for others, account holding for clients or counterparties, liquidity administration, reserve administration, or analogous financial institution activity. The Corporation shall not receive, pool, hold, route, safeguard, or administer funds in a manner that would reasonably cause it to function as a bank-like, treasury-like, or regulated financial intermediary.
This prohibition applies whether such activity is described as:
a) mission support; b) temporary facilitation; c) technical administration; d) escrow-like convenience; e) public-interest financial coordination; or f) emergency or pilot infrastructure.
The Corporation may maintain its own corporate accounts, reserves, internal treasury practices, and financial administration necessary for lawful nonprofit operations. It may not use those capacities to operate treasury or deposit functions for others or to become a financial utility by proximity to public-benefit work. No funds of third parties shall be accepted, managed, or positioned by the Corporation in a manner that materially resembles deposit-taking, treasury operation, or balance-sheet intermediation.
15.2 No Securities Issuance, Distribution, Placement, or Underwriting
The Corporation shall not issue, originate, sponsor, underwrite, place, distribute, market, solicit, sell, or intermediate securities or security-like instruments, whether directly or indirectly, and whether under federal securities law, state securities law, or any analogous legal regime. This prohibition applies regardless of whether the contemplated instrument is framed as philanthropic, public-interest, catalytic, resilience-oriented, research-linked, structured for impact, tokenized, or otherwise presented in mission-consistent language.
The Corporation shall not:
a) prepare or circulate offering documents as issuer, arranger, or placement authority; b) operate issuance pipelines or subscription pathways; c) recruit, match, or route investors to securities opportunities under its own authority; d) receive compensation contingent on securities issuance, placement, or distribution outcomes; or e) permit its public-benefit legitimacy or technical infrastructure to function as a substitute for lawful securities-market roles.
The Corporation may analyze, teach about, compare, or document securities-related structures for educational, scientific, or public-interest purposes. It may not itself become the actor that brings such instruments into issuance, distribution, or market circulation.
15.3 No Investment Advice, Portfolio Management, or Asset Management
The Corporation shall not provide investment advice, hold itself out as an investment adviser, exercise discretionary authority over the purchase, sale, allocation, retention, or disposition of assets for others, or engage in portfolio management or asset-management functions. It shall not recommend specific investments, formulate portfolio strategies for others as an adviser, manage pooled or segregated investment assets, or produce outputs that are reasonably likely to be understood as individualized or institutional investment advice.
This prohibition includes, without limitation:
a) advising on specific allocations, purchases, sales, or holdings; b) discretionary management of funds or accounts; c) model portfolio construction for implementation as an investment function; d) asset-selection or rebalancing authority; and e) compensation structures tied to investment decisions, portfolio performance, or asset-deployment results.
The Corporation may produce public-interest educational content, systems-level analyses, risk frameworks, scenario materials, and bounded technical or scientific artifacts that lawful recipients may consider within their own judgment. It may not cross the line into advising or managing capital as a regulated or functionally equivalent actor.
15.4 No Broker, Dealer, Exchange, Trading Venue, or Market Operator Function
The Corporation shall not act as, or functionally resemble, a broker, dealer, exchange, trading venue, alternative trading system, execution venue, matching facility, market operator, or other market-access or transaction-enablement institution. It shall not create or operate systems, dashboards, registries, workflows, or interface layers that materially facilitate the selection, matching, negotiation, or execution of trades, transactions, placements, or market entries under the Corporation’s authority or in a manner reasonably likely to be interpreted as such.
This rule prohibits, among other things:
a) bringing buyers and sellers together in a manner that functions as a market surface; b) operating structured matching or routing flows for transactions or capital; c) providing execution-facing venue features under softer labels; d) running decision states that effectively govern who may transact or under what terms; and e) presenting mission-consistent infrastructure as if it were a nontraditional market-access channel.
The Corporation may host discussions, educational forums, public-interest simulations, or structured technical exchanges. It may not create or operate trading, dealing, or market-access functions by architecture, documentation, workflow, or public interpretation.
15.5 No Clearing, Settlement, Custody, or Safeguarding of Client Assets
The Corporation shall not perform or approximate clearing, settlement, custody, safekeeping, escrow, asset control, wallet custody, settlement confirmation, or safeguarding functions for third-party funds, instruments, accounts, or assets. No platform, repository, observability environment, technical tool, or institutional process of the Corporation shall be designed or used as a substitute for custody or settlement infrastructure, whether in conventional, digital, tokenized, or hybrid form.
This prohibition applies to both direct and indirect arrangements, including:
a) holding or controlling third-party assets pending later action; b) acting as a necessary control point for the consummation of transfers; c) issuing confirmations that are operationally equivalent to settlement finality; d) maintaining wallets, keys, or asset-access mechanisms for others in a custody-like manner; or e) using “technical administration” language to mask practical custodial responsibility.
The Corporation may maintain internal control over its own assets and systems as necessary for nonprofit operation. It may not hold or safeguard assets for others in a way that would place it inside or adjacent to regulated custody or settlement functions.
15.6 No Insurance, Reinsurance, MGA, TPA, Claims Administration, or Risk-Carrying Function
The Corporation shall not issue, bind, broker, administer, manage, price, settle, carry, or otherwise function as an insurer, reinsurer, managing general agent, third-party administrator, claims administrator, claims-adjustment authority, or risk-bearing institution. It shall not assume underwriting risk, claims risk, actuarial authority for market-facing products, or any other consequence-bearing insurance or reinsurance function.
This prohibition includes, without limitation:
a) designing or operating claim-triggering processes with binding effect; b) acting as claims reviewer or settlement authority; c) taking premium-like consideration for coverage-related outcomes; d) carrying reserves or contingent liabilities for insured or reinsured outcomes; and e) functioning as a delegated or shadow insurance operator through technical or documentary means.
The Corporation may study, compare, teach about, or support understanding of resilience, continuity, insurance, or risk-transfer structures as part of its public-benefit mission. It may not itself become the institution that issues, carries, administers, or settles such obligations.
15.7 No Payment System, Money Transmission, or Funds-Movement Role
The Corporation shall not operate or provide a payment system, money transmission function, remittance function, funds-movement role, payment orchestration role with execution effect, or any analogous financial transfer service. It shall not receive funds for onward transmission, hold itself out as moving money for others, or design mission-bearing infrastructure that functions as a practical substitute for regulated payment rails or money services activity.
The Corporation may support education, observability, or public-interest analysis concerning payment systems and financial connectivity. It may not itself become a node of financial movement. This prohibition applies whether the relevant funds movement would be fiat, digital, tokenized, or otherwise structured, and whether described as facilitative, technical, emergency, or philanthropic.
No technical system or workflow of the Corporation shall produce the reasonable impression that the Corporation:
a) transfers money for others; b) controls release of funds between counterparties; c) confirms, intermediates, or supervises payment finality; or d) provides alternative money transmission or settlement functionality.
15.8 No Credit Intermediation, Guarantee Issuance, or Structured-Finance Execution
The Corporation shall not engage in credit intermediation, guarantee issuance, credit enhancement provision, structured-finance execution, debt placement, facility management, or analogous financial engineering or liability-assuming functions. It shall not intermediate borrowing, extend credit as a regulated or market-facing actor, provide guarantees or support undertakings on behalf of others, or structure vehicles or arrangements whose practical effect is to assume or intermediate financial risk or obligation.
This includes, without limitation:
a) issuing credit-like commitments; b) structuring guarantee pathways or support undertakings with execution effect; c) creating facilities through which others access financing under the Corporation’s authority; d) operating structured-finance workflows or shelves; and e) using mission-consistent language to obscure debt, credit, or liability-bearing roles.
The Corporation may produce research, public-interest analyses, educational frameworks, and upstream evidence artifacts relevant to financing ecosystems. It may not itself intermediate or assume credit and structured-finance functions.
15.9 No Fund, SPV, Shelf, Trust, or Vehicle Operation by GCRI US
The Corporation shall not establish, operate, manage, sponsor as controlling authority, or administer any fund, pooled vehicle, special purpose vehicle, trust, issuance shelf, structured facility, warehousing entity, capital conduit, or analogous execution-bearing vehicle whose primary purpose is to hold assets, issue instruments, intermediate capital, administer liabilities, or facilitate regulated or market-facing financial outcomes.
This prohibition applies whether the vehicle is described as:
a) mission-supporting; b) catalytic; c) philanthropic-financial; d) readiness-oriented; e) temporary; or f) technically external but effectively governed by the Corporation.
The Corporation shall not use affiliates, labels, contractual wrappers, or governance influence to create shadow vehicle operation while formally disclaiming operational responsibility. If the Corporation’s practical role would amount to vehicle operation or control, the arrangement is prohibited unless lawfully vested elsewhere and clearly separated from the Corporation’s role.
15.10 No Direct or Indirect Assumption of Financial Liability on Behalf of Others
The Corporation shall not directly or indirectly assume financial liability, contingent liability, payment responsibility, performance guarantee, indemnity-like market obligation, or analogous financial risk on behalf of third parties in a manner inconsistent with its nonprofit, non-executing, and public-benefit role. This rule protects against both explicit assumption of liability and softer forms of risk transfer through documents, workflows, or public representations.
Accordingly, the Corporation shall not:
a) guarantee the obligations of others; b) backstop transactions, facilities, or market commitments; c) accept payment or performance liability for third parties; d) create technical or documentary structures that imply such assumption; or e) allow counterparties to market or rely on Corporation involvement as if it were a financial guarantor or liability-bearing participant.
Nothing in this Section shall prohibit the Corporation from entering into ordinary-course contractual commitments, indemnification arrangements permitted by law, employment obligations, vendor contracts, insurance purchases for its own operations, or other internal legal obligations consistent with normal nonprofit functioning. The prohibition concerns assuming third-party financial or market liability as part of mission-bearing or outward-facing activity.
15.11 Interpretive Rule for Regulated Financial and Market Activities
This Section shall be interpreted broadly enough to prevent avoidance by re-labeling, technical indirection, structural layering, partner interposition, or product novelty, and narrowly enough to preserve the Corporation’s ability to conduct legitimate scientific, educational, public-benefit, and technical stewardship activities that do not cross into regulated or consequence-bearing roles. Where ambiguity exists, the interpretation that better preserves:
a) non-execution; b) exempt-purpose fidelity; c) absence of market intermediation; d) truthful institutional description; and e) safer regulatory perimeter
shall prevail unless a contrary result is required by law.
16. General Prohibition on Execution-Side Public and Sovereign Functions (GCRI United States)
16.1 No Exercise of Sovereign Authority
The Corporation shall not exercise, claim, imply, simulate, or approximate sovereign authority. It shall not present itself as possessing public power, delegated governmental power, emergency authority, police power, public-law command authority, compulsory administrative force, or any equivalent authority belonging to the United States, any State, Territory, Tribal government, local government, foreign sovereign, or any other public authority.
This prohibition applies whether the claimed or implied sovereign function would be:
a) direct or indirect; b) formal or functional; c) document-based or system-mediated; d) temporary, pilot-stage, or emergency-framed; or e) asserted through public statement, interface logic, partner arrangement, or omission likely to mislead.
The Corporation may lawfully support public-interest institutions through evidence systems, observability, methods, training, technical assistance, and public-good infrastructure. It may not convert such support into sovereign substitution. Public usefulness does not create public power. Institutional seriousness does not create delegated state capacity.
No person acting for or through the Corporation shall describe a Corporation act, output, or system as if it possessed sovereign effect unless such effect is expressly conferred by law and accepted by the Corporation in a manner consistent with its Articles, exempt purposes, and these Bylaws, which circumstance shall not be presumed and is not expected in ordinary course.
16.2 No Regulatory Approval, Licensing, or Supervisory Determination
The Corporation shall not issue, confer, imply, simulate, or approximate any regulatory approval, license, registration, supervisory clearance, compliance determination with public effect, regulated operating permission, enforcement disposition, or supervisory judgment. It shall not operate as if it were a regulator, licensing body, public compliance certifier, or supervisory decision-maker.
This prohibition includes, without limitation:
a) authorizing or purporting to authorize persons or entities to operate in regulated fields; b) issuing outputs that reasonably appear to certify compliance with binding legal effect; c) maintaining dashboards, badges, registries, or system states that function as approval surfaces; d) producing public-facing or partner-facing language suggesting that the Corporation can “clear,” “approve,” “license,” “certify,” or “validate” regulated status; and e) permitting its structured technical or evidence outputs to be used as substitutes for formal regulatory or supervisory action without prompt correction.
The Corporation may produce educational and scientific materials about regulatory architecture, compliance design, readiness, evidence quality, controls, or technical governance. It may support lawful actors who must satisfy regulatory requirements. It may not itself determine whether those requirements have been satisfied with public-law effect, nor allow its materials to be represented as if they do so.
16.3 No Binding Public-Authority Instruction, Direction, or Allocation Power
The Corporation shall not issue binding instructions, directives, allocations, approvals, denials, priorities, mandates, or compulsory operational determinations as if it held public-authority decision power. It shall not direct the use of public resources, instruct regulated counterparties under color of law, allocate legal rights or obligations, determine eligibility for public programs, or otherwise function as an authority surface that compels action.
This prohibition applies to both explicit and implicit forms of authority. The Corporation shall not:
a) issue documents drafted to function as public directives; b) design technical systems that effectively determine mandatory operational next steps for others under apparent authority; c) use convening, infrastructure control, or informational asymmetry to create de facto compulsory outcomes; d) issue rankings, labels, or states that are reasonably likely to be treated as binding instructions in public or regulated settings; or e) frame recommendations in a manner likely to obscure that independent lawful judgment remains with the recipient.
The Corporation may offer non-binding technical guidance, scientific analysis, structured options, public-interest frameworks, and mission-consistent educational materials. It may not collapse such support into direction with public-authority effect.
16.4 No Statutory, Administrative, or Adjudicative Substitution
The Corporation shall not substitute for any statutory, administrative, adjudicative, quasi-judicial, enforcement, or official review process. It shall not adjudicate legal rights, determine statutory compliance with binding effect, resolve disputes as if exercising public adjudicative power, issue sanctions under public law, or replace courts, tribunals, regulators, agencies, licensing bodies, or administrative authorities.
This prohibition includes, without limitation:
a) issuing determinations framed as final legal conclusions binding on third parties; b) running dispute or review processes represented as substitutes for formal public processes; c) creating internal mechanisms that appear to dispose of rights, obligations, permits, or regulatory status outside the Corporation’s own lawful internal affairs; d) representing internal safeguard, grievance, or review channels as external public-law remedies; and e) allowing third parties to rely publicly on Corporation outputs as though they were adjudicative or administrative rulings.
Nothing in this Section prevents the Corporation from maintaining internal review, correction, grievance, ethics, or safeguards mechanisms for its own affairs, outputs, and institutional processes. Those mechanisms are internal governance structures. They do not constitute public adjudication, administrative process, or sovereign determination beyond the Corporation’s own lawful perimeter.
16.5 No Representation as Acting for Government, Regulator, or Public Authority Absent Lawful Written Instrument
The Corporation shall not represent, imply, or permit others reasonably to understand that it is acting for, on behalf of, under mandate from, or as the authorized agent of any government, regulator, ministry, department, agency, supervisory body, public authority, or equivalent institution absent a lawful, explicit, written instrument that clearly defines such relationship and is fully consistent with the Corporation’s legal and constitutional posture.
Even where the Corporation collaborates with public institutions, receives grants, participates in consultations, provides technical assistance, or supports public-interest work alongside governmental actors, such collaboration shall not be described in a manner that suggests the Corporation has acquired governmental character, delegated public power, or authority to speak in place of the relevant public institution. Proximity to government is not government. Support to regulation is not regulation. Technical assistance is not delegated sovereign power.
Where a lawful written instrument does exist, the Corporation shall construe it narrowly, document its scope clearly, and ensure that all public representations remain faithful to the limits of the instrument. No person may generalize a narrow relationship into a broader claim of public authority.
16.6 No Use of GCRI US Outputs as Surrogates for Ministry, Regulator, or Treasury Acts
The Corporation shall not produce, maintain, or allow the use of its outputs as surrogates for ministry acts, regulatory acts, supervisory acts, licensing acts, treasury acts, or other public-authority acts. No evidence pack, observability output, technical note, dashboard state, conformance-support artifact, educational product, or public-safe summary shall be framed, positioned, routed, or allowed to function as if it were the public act itself.
This prohibition applies even where public institutions may lawfully consider Corporation outputs as part of their own independent decision-making processes. A public institution’s use of an upstream artifact does not convert that artifact into a sovereign or regulatory act. The Corporation shall preserve this distinction in metadata, document headers, disclaimers where appropriate, workflow design, public communications, and partner arrangements.
If a public actor, private actor, or partner begins using or describing a Corporation output as though it were a substitute for formal public action, the Corporation shall take reasonable steps to correct that misunderstanding, including clarification, redesign, narrowing, or withdrawal where necessary.
16.7 No Implied Public Mandate by Association, Sponsorship, Funding, or Convening
The Corporation shall not imply or permit implication that it holds a public mandate by reason of association with public institutions, attendance at official meetings, receipt of public funds or grants, collaboration with regulators or ministries, participation in panels or consultations, or convening public or quasi-public stakeholders. Institutional association, sponsorship, funding, or convening access shall not be used to manufacture a false appearance of delegated authority, official standing, or sovereign endorsement.
This rule prohibits, among other things:
a) using government logos, affiliations, or event proximity in ways that imply official mandate beyond recorded truth; b) presenting consultation participation as if it were formal appointment or public authorization; c) relying on public funding relationships to imply regulatory or sovereign standing; d) framing multi-stakeholder convening as if it created governmental decision authority in the Corporation; and e) allowing partners or sponsors to market the Corporation as a public or quasi-public authority.
The Corporation may truthfully describe its lawful collaborations and sources of support. It shall not overread them, and it shall not allow others to overread them on its behalf.
16.8 Interpretive Rule for Execution-Side Public and Sovereign Functions
This Section shall be interpreted to preserve the Corporation’s identity as a private nonprofit public-benefit institution that may support, inform, educate, and structure serious public-interest work without becoming a sovereign, regulatory, supervisory, administrative, adjudicative, or public-authority actor. Where ambiguity exists, the interpretation that better preserves:
a) non-sovereign status; b) non-execution; c) truthful description of public relationships; d) narrower implied authority; and e) safer constitutional perimeter
shall prevail unless contrary law clearly requires otherwise.
17. Prohibited Activities Schedule — Institutional Integrity and Private Benefit (GCRI United States)
17.1 Private Inurement and Impermissible Private Benefit
The Corporation shall not engage in any activity, arrangement, output, compensation structure, governance practice, funding design, technical dependency, access arrangement, or institutional pattern that gives rise to private inurement or impermissible private benefit within the meaning of applicable nonprofit and federal tax law or in any manner inconsistent with the Corporation’s public-benefit character, exempt-purpose posture, and mission lock. This prohibition is absolute in relation to private inurement and shall be interpreted strictly in relation to private benefit.
No part of the Corporation’s net earnings, assets, opportunities, institutional standing, technical commons, public-good infrastructure, or governance leverage shall inure to the benefit of any director, officer, employee, founder, donor, related party, sponsor, contractor, strategic backer, or other private person except as reasonable compensation for bona fide services rendered, reimbursement of properly incurred expenses, indemnification, insurance, or other payments expressly permitted by law and consistent with these Bylaws. Any transaction, arrangement, or pattern of conduct that could reasonably be understood as transferring economic value, institutional privilege, or structural advantage in a manner inconsistent with this rule shall be treated as presumptively prohibited until lawfully reviewed and cleared.
Impermissible private benefit may arise even where no insider receives direct financial gain. It includes situations in which the Corporation’s public-benefit resources, credibility, systems, or outputs are structured or used primarily to advantage particular private parties, enterprises, or commercial ecosystems in a manner disproportionate to the public benefit served. The Corporation shall therefore examine not only who is paid, but who benefits, how they benefit, why they benefit, and whether the public-interest rationale is genuine, proportionate, documented, and legally supportable.
The Corporation shall not rely on mission-oriented language, strategic framing, or technical necessity to excuse arrangements that in substance transfer disproportionate benefit to private actors. Where ambiguity exists, the interpretation that better protects exempt status, public-benefit legitimacy, and anti-capture discipline shall prevail.
17.2 Extraction of Private Commercial Advantage From Public-Good Stewardship
The Corporation shall not permit the extraction of private commercial advantage from its public-good stewardship in a manner inconsistent with mission, neutrality, or public-benefit integrity. The Corporation’s systems, methods, observability environments, reference assets, semantic layers, technical infrastructure, institutional credibility, and public-facing reputation shall not be used as engines of private commercial positioning, proprietary leverage, sales acceleration, market signaling, or commercial de-risking for particular firms except to the limited extent that any private benefit is incidental, lawful, mission-consistent, and subordinate to a demonstrable public benefit.
This prohibition applies to both explicit and indirect extraction, including:
a) using Corporation affiliation or outputs as a substitute for independent commercial due diligence or market approval; b) leveraging access to common infrastructure to privilege one vendor, platform, service provider, or technology stack over similarly situated alternatives absent mission-consistent and documented basis; c) converting mission-bearing technical infrastructure into a feeder channel for private products or service lines; d) structuring public-good work so that commercial actors receive strategic value disproportionate to public-interest value created; and e) permitting commercial actors to market their relationship with the Corporation in ways that imply endorsement, preferred positioning, or public-benefit validation beyond what is lawfully and truthfully supportable.
The Corporation may collaborate with commercial actors where such collaboration is lawful, mission-consistent, non-capturing, and properly bounded. It may also produce public-good infrastructure that commercial actors may lawfully and non-exclusively use. It may not allow its stewardship role to become a hidden commercial multiplier for favored private parties.
17.3 Transfer of Institutional Position Into Preferential Commercial Access
The Corporation shall not convert its institutional position, public-benefit status, scientific seriousness, technical centrality, or ecosystem visibility into preferential commercial access for any private actor. No donor, sponsor, vendor, host, contractor, collaborator, or participant shall receive preferential access to the Corporation’s common infrastructure, governance surfaces, publication timing, partner introductions, institutional credibility, technical roadmaps, or visibility channels in a manner that effectively commercializes public-benefit standing.
This rule prohibits, among other things:
a) privileged access to mission-critical repositories, systems, or non-public technical context beyond lawful and mission-consistent necessity; b) early or preferential access to public-good assets in a manner that materially advantages a private actor over others without sufficient public-interest justification; c) priority introductions, institutional referrals, or ecosystem routing conferred because of funding, strategic importance, or proximity to leadership; d) use of the Corporation’s convening or educational environments to create quasi-commercial lead-generation surfaces; and e) granting selective influence over roadmap, standards-aligned structures, semantic development, or observability patterns in ways that translate into downstream commercial advantage.
The Corporation may maintain role-based access controls, safety-based restrictions, contribution-based operational access where necessary for stewardship, and lawful collaboration channels. It shall not create or tolerate access regimes whose practical effect is to sell or transfer privileged market position under the guise of institutional cooperation.
17.4 Private Capture Through Funding, Hosting, Tooling, or Operational Dependence
The Corporation shall not allow private capture of its mission, judgment, infrastructure, or institutional position through funding dependence, hosting dependence, tooling dependence, platform lock-in, staffing dependence, secondment structures, or other forms of operational reliance that distort independent judgment or weaken constitutional boundaries. Capture need not be explicit to be real. It may arise through repeated accommodation, hidden veto points, practical dependency, or silent narrowing of institutional choice caused by the fear of losing key support.
This prohibition includes situations in which:
a) a donor, sponsor, or host acquires de facto leverage over strategic priority, publication timing, methodological framing, or infrastructure governance because the Corporation cannot realistically proceed without them; b) a vendor or technical provider becomes so embedded that mission-bearing assets cannot be maintained, ported, or corrected without private permission or cooperation inconsistent with anti-enclosure doctrine; c) secondees, embedded personnel, or dual-role actors create hidden control over decision pathways, semantic choices, system administration, or public positioning; d) a strategic partner becomes the effective arbiter of what the Corporation may say, release, support, or correct; or e) the Corporation narrows its role, claims, or correction practice to preserve access to infrastructure, funding, audiences, or platforms controlled by private actors.
The Board and officers shall actively monitor for dependency patterns that threaten independence. Where such patterns emerge, the Corporation shall diversify, redesign, document, re-scope, or exit the relevant arrangement as necessary to restore neutrality and constitutional integrity.
17.5 Related-Party Advantage Without Explicit Neutral Process and Recorded Approval
The Corporation shall not confer material benefit, access, compensation, preferential treatment, influence, visibility, priority, or strategic advantage upon any related party except through a lawful, neutral, disclosed, and properly recorded process consistent with conflict-of-interest controls, applicable law, and the Corporation’s exempt-purpose posture. For purposes of this Section, “related party” shall be interpreted broadly to include directors, officers, key employees, founders, substantial donors, family members of such persons where relevant, entities controlled by or materially affiliated with such persons, and any other person or entity whose relationship creates a credible risk of self-dealing, favoritism, or impaired judgment.
No related party shall receive:
a) preferential access to Corporation infrastructure, systems, or non-public opportunities; b) contracts, compensation, or paid roles outside fair and documented processes where such processes are reasonably required; c) privileged treatment in publication, review, convening, or institutional representation; d) preferential interpretation of institutional policies, role boundaries, or participation rights; or e) hidden or informal advantages not available to similarly situated parties absent lawful and mission-consistent reason.
Where a related-party arrangement is contemplated, the Corporation shall require disclosure, neutral evaluation, recusal where appropriate, documented rationale, and recorded approval by the properly authorized body. The absence of overt bad faith shall not excuse failure to follow neutral process. Related-party advantage is a structural risk and shall be treated accordingly.
17.6 Undisclosed Side Agreements That Alter Institutional Neutrality
The Corporation shall not enter into, honor, or permit undisclosed side agreements, informal assurances, tacit understandings, privileged commitments, or off-record arrangements that alter institutional neutrality, influence the treatment of parties, constrain publication or correction rights, modify governance expectations, create hidden priorities, or otherwise change the practical meaning of formally adopted rules, partner arrangements, or public descriptions.
This prohibition applies whether the side arrangement is written or unwritten and whether it concerns:
a) access, visibility, sequencing, or agenda influence; b) methodological treatment or interpretive framing; c) publication timing, correction, or withdrawal; d) use of institutional name, marks, affiliations, or logos; e) technical integration or system dependency; f) partner expectations at the edge of the perimeter; or g) economic, reputational, or political sensitivities.
The Corporation shall not tolerate shadow governance through “understood exceptions,” informal donor accommodations, verbal promises, or side-channel commitments that are not captured in the controlling record and reviewed for consistency with mission lock, neutrality, and public-benefit integrity. If a material side agreement is discovered, it shall be escalated promptly, documented, and either formalized through lawful process or terminated.
17.7 Hidden Subsidization of Private Activity Through GCRI Constitutional Assets
The Corporation shall not use its constitutional assets—including its public-benefit legitimacy, technical commons, educational programs, governance surfaces, observability systems, semantic infrastructure, institutional network, or public-facing credibility—to subsidize private activity in ways that are inconsistent with exempt purpose, neutrality, or anti-capture discipline. Hidden subsidization occurs when the Corporation bears costs, transfers value, or confers strategic institutional support that primarily advantages private actors while the public-benefit rationale is weak, incidental, unrecorded, or disproportionate.
Such hidden subsidization may include, without limitation:
a) devoting mission-critical staff or systems to private adaptation work without sufficient public-interest justification or proper cost discipline; b) allowing private actors to free-ride on common infrastructure in ways that degrade public-benefit access or continuity; c) subsidizing commercial pilots, market-entry efforts, or product development under the guise of public-good experimentation; d) absorbing coordination, educational, or technical costs that primarily benefit particular firms without corresponding and demonstrable public benefit; and e) maintaining “temporary” private accommodations that become long-term structural advantages.
The Corporation may lawfully engage in collaborations that incidentally benefit private actors where doing so is necessary to achieve legitimate public-benefit outcomes and where the private benefit remains incidental, proportionate, documented, and subordinate. It shall not permit its resources to become a concealed support layer for private growth, private control, or private revenue generation inconsistent with mission.
17.8 Interpretive Rule for Institutional Integrity and Private Benefit
This Section shall be interpreted to protect the Corporation’s exempt status, public-benefit legitimacy, anti-capture posture, neutrality, and constitutional distinctness from private and commercial actors. Where ambiguity exists as to whether an arrangement, output, dependency, privilege, or pattern of conduct confers impermissible private advantage or distorts the Corporation’s institutional posture, the interpretation that better preserves:
a) absence of private inurement; b) avoidance of impermissible private benefit; c) neutrality and independence; d) non-enclosure of public-good infrastructure; and e) truthful, mission-consistent stewardship
shall prevail unless a contrary result is clearly required by applicable law.
18. Prohibited Activities Schedule — Pay-to-Play, Sponsor Conditionality, and Influence Purchase (GCRI United States)
18.1 Sale of Access to Governance, Evidence, or Institutional Credibility
The Corporation shall not sell, barter, exchange, condition, or otherwise make available access to governance, evidence systems, institutional credibility, public-benefit legitimacy, technical standing, convening position, or public-facing seriousness in return for donations, sponsorships, grants, fees, hosting, technical support, secondments, or any other form of financial or in-kind consideration. The Corporation’s governance surfaces, evidence infrastructures, publications, observability systems, and public-good assets are not commercial inventory and shall not be converted into paid gateways to influence, standing, or reputational leverage.
This prohibition applies whether the access is explicit or implicit, formal or informal, direct or mediated through program structures. It includes, without limitation:
a) offering privileged governance access in exchange for funding or strategic support; b) granting special evidence visibility, review pathways, or institutional proximity because of contribution level; c) creating donor or sponsor “tiers” that materially alter access to mission-bearing systems or institutional decision channels; d) using naming rights, hosting rights, or partnership labels in ways that imply governance leverage or superior institutional standing; and e) permitting the Corporation’s marks, affiliations, or doctrinal seriousness to function as purchasable credibility assets.
The Corporation may lawfully accept financial support, charge mission-consistent fees, and maintain structured participation models where such arrangements comply with law and these Bylaws. It may not convert any lawful support mechanism into a paid path to institutional influence, constitutional significance, or enhanced public meaning. Public-benefit legitimacy is not a revenue surface.
18.2 Sponsor-Conditional Outputs, Findings, Rankings, or Conclusions
The Corporation shall not produce, maintain, alter, suppress, sequence, narrow, widen, or otherwise shape outputs, findings, rankings, classifications, conclusions, summaries, public descriptions, evidence structures, or related mission-bearing artifacts on a sponsor-conditional basis. No donor, sponsor, strategic backer, host, or commercial or institutional supporter may condition support on the expectation that the Corporation will produce, omit, emphasize, de-emphasize, delay, accelerate, soften, harden, or otherwise manipulate substantive results or institutional meaning.
This rule prohibits both overt and subtle conditionality, including:
a) explicit contractual or quasi-contractual requirements affecting substantive findings; b) expectations that funding depends on favorable framing or non-critical treatment; c) informal understandings that a sponsor’s participation entitles it to “balanced” conclusions inconsistent with the evidence; d) pressure to avoid classifications, terminology, or methodological choices that may inconvenience a supporter; and e) use of funding dependence, host leverage, or platform access to shape what the Corporation is willing to say, show, compare, or correct.
The Corporation may permit supporters to understand the scope, timeline, methodology, and handling class of work being supported. It may not permit support to become an instrument for controlling conclusions. The integrity of scientific, educational, evidentiary, and public-interest outputs depends on their independence from sponsor-defined substantive outcomes.
18.3 Funding Conditions That Shape Methods, Results, or Publication Outcomes
The Corporation shall not accept or maintain funding conditions that materially shape, distort, suppress, bias, delay, accelerate, or otherwise control the methods, interpretive logic, outputs, publication pathways, correction rights, withdrawal rights, release sequencing, or scope boundaries of mission-bearing work in a manner inconsistent with independent judgment, public-benefit purpose, or these Bylaws.
This prohibition includes funding conditions that:
a) require use of preferred methods or data inputs for non-scientific reasons; b) prohibit certain lines of inquiry, comparison, or interpretation absent lawful handling necessity; c) restrict the Corporation’s right to correct, supersede, or withdraw defective materials; d) condition publication timing on sponsor convenience where such timing would alter institutional meaning; e) require the Corporation to obtain sponsor consent before releasing or revising findings; or f) create financial penalties tied to substantive conclusions, classifications, or public descriptions.
Funding arrangements may lawfully define project scope, budget, timeline, operational milestones, security requirements, confidentiality boundaries, and mission-consistent deliverable classes, provided such conditions do not impair independent institutional judgment or turn the Corporation’s outputs into sponsor-managed artifacts. Where a funding term risks crossing that line, the term shall be rejected, renegotiated, narrowed, or subject to formal escalation before acceptance.
18.4 Preferential Docket Access, Acceleration, or Publication by Contribution Size
The Corporation shall not provide preferential docket access, review priority, publication sequencing advantage, correction priority, observability priority, issue acceleration, or institutional attention to any person or entity merely because of the size, strategic importance, or visibility of that person’s or entity’s donation, sponsorship, grant, in-kind support, or relationship to the Corporation. Contribution magnitude shall not become an informal queueing system for institutional seriousness.
This rule applies to both explicit prioritization and subtler versions of influence, including:
a) fast-tracking matters because a major donor is involved; b) delaying scrutiny, correction, or publication because a sponsor is sensitive; c) creating premium support lanes that materially alter substantive treatment or institutional attention; d) prioritizing technical integration, visibility, or staffing attention in ways not justified by mission criteria; and e) treating well-funded actors as more “institutionally real” than less-funded or non-funded actors absent lawful and mission-relevant justification.
The Corporation may lawfully prioritize matters according to public-benefit urgency, risk, safety, legal necessity, operational continuity, evidentiary significance, or other mission-consistent factors. It may not use contribution size, sponsor importance, or fundraising prospects as a substitute prioritization rule. Any priority allocation that materially benefits a supporter must be justifiable on independent institutional grounds and documented accordingly.
18.5 Influence Purchase Through In-Kind Services, Hosting, Embedded Personnel, or Secondments
The Corporation shall not permit in-kind support, hosting arrangements, embedded personnel, secondees, software credits, infrastructure donations, professional services, legal support, communications assistance, data access, or other non-cash support to function as a means of purchasing influence over governance, methods, outputs, priorities, visibility, or institutional judgment. Influence purchase may occur through dependency and access no less than through direct payment.
This prohibition is especially important where support is valuable, scarce, or operationally central. The risk is greatest when the Corporation becomes reliant on a supporter for:
a) critical infrastructure or hosting; b) technical maintenance or architecture control; c) staff augmentation or subject-matter capacity; d) legal, public-relations, or administrative support; e) access to relevant networks, institutions, or audiences; or f) proprietary data, tooling, or implementation environments.
Where such support is accepted, the Corporation shall maintain structural safeguards sufficient to prevent operational gratitude from becoming substantive deference. Those safeguards may include documentation of role limits, conflict disclosures, recusal rules, contractual non-interference clauses, independence protections, exit planning, access segmentation, and periodic Board-level review. Support is permissible only where it does not buy influence over the Corporation’s mission-bearing judgment.
18.6 Agenda Control in Exchange for Funding, Visibility, or Strategic Positioning
The Corporation shall not cede or sell agenda control over governance surfaces, public-benefit priorities, publications, research directions, semantic development, observability priorities, training agendas, convening design, or public-facing positioning in exchange for funding, visibility, partner prestige, ecosystem advantage, or strategic access. No supporter may purchase the right to define what the Corporation will care about, what it will omit, how it will frame issues, or which topics will receive institutional priority, except to the limited extent that a lawfully scoped grant or project defines a mission-consistent area of work without controlling the Corporation’s independent judgment within that area.
This prohibition includes:
a) donor-driven narrowing of uncomfortable or inconvenient topics; b) sponsor-defined public narratives that reshape institutional priorities; c) “co-created” agendas in which the Corporation’s independence becomes illusory; d) allowing event, program, or technical agendas to be structured principally to serve the positioning needs of supporters; and e) tolerating topic selection distortions caused by concentration of support from interested parties.
The Corporation may accept mission-consistent support for defined workstreams where such support advances public-benefit goals and preserves independence. It may not surrender the constitutional right and obligation to determine its own institutional priorities through lawful governance and mission-based judgment.
18.7 Privileged Treatment of Donors, Sponsors, or Strategic Backers
The Corporation shall not provide privileged treatment to donors, sponsors, strategic backers, or similarly situated supporters in ways that materially alter governance treatment, substantive rigor, institutional boundaries, publication integrity, correction discipline, or access to mission-bearing common infrastructure. Privileged treatment may take monetary, procedural, reputational, technical, documentary, or relational form. All are subject to this prohibition where they undermine neutrality, public-benefit fidelity, or truthful institutional conduct.
Prohibited privileged treatment includes, without limitation:
a) special exemptions from policies, safeguards, or review disciplines; b) quiet tolerance of boundary-pushing conduct because a supporter is important; c) selective enforcement or non-enforcement of correction, claims, or participation rules; d) elevated influence over roadmap, semantics, or public statements without proper authority; e) enhanced public signaling of legitimacy not grounded in actual institutional role; and f) privileged access to non-public institutional context in ways that distort fair treatment or public-benefit stewardship.
The Corporation may acknowledge supporters, maintain lawful stewardship relationships, and provide ordinary donor relations consistent with nonprofit practice. It may not create a class of quasi-governors, quasi-insiders, or quasi-beneficiaries whose support changes the constitutional meaning of the institution. The Corporation shall remain governable by mission and law, not by patronage.
18.8 Structural Safeguards Against Influence Purchase
To preserve the integrity of this Section, the Corporation shall maintain and, where necessary, strengthen structural safeguards against influence purchase, including appropriate combinations of:
a) donor and sponsor independence clauses; b) conflict-of-interest disclosure and recusal procedures; c) separation between fundraising functions and substantive decision functions; d) documented criteria for prioritization, publication, and technical treatment; e) restrictions on sponsor review rights and consent rights; f) periodic Board oversight of concentrated funding and dependency patterns; g) records of materially relevant support arrangements; and h) corrective authority to narrow, suspend, or terminate compromised relationships.
These safeguards shall be treated as constitutional controls rather than discretionary administrative preferences. Where the Corporation identifies recurring risk of influence purchase, it shall redesign the relevant process rather than rely solely on after-the-fact good faith.
18.9 Interpretive Rule for Pay-to-Play, Sponsor Conditionality, and Influence Purchase
This Section shall be interpreted to protect the Corporation from becoming a purchasable institution in substance, whether or not such purchase is expressed in formal contractual language. Influence may be bought through money, dependency, access, prestige, or institutional need. The Corporation shall resist all such pathways where they distort mission, outputs, governance, priorities, or public meaning.
Where ambiguity exists, the interpretation that better preserves:
a) independence of judgment; b) neutrality and anti-capture discipline; c) truthfulness of outputs and public claims; d) fairness of access to mission-bearing systems and processes; and e) public-benefit fidelity over supporter preference
shall prevail unless a contrary result is required by law.
19. Prohibited Activities Schedule — Misrepresentation, Overclaim, and False Legibility (GCRI United States)
19.1 Implied Endorsement, Approval, or Certification Without Authority
The Corporation shall not expressly or impliedly represent that it has endorsed, approved, certified, cleared, validated, accredited, authorized, or formally accepted any person, entity, product, platform, method, program, transaction, operating environment, governance structure, or institutional arrangement beyond the narrow scope of any authority lawfully and expressly vested in it. In the ordinary course, no such public-law, regulatory, supervisory, market-facing, or execution-bearing authority is vested in the Corporation, and no act, omission, formatting choice, or public statement shall be allowed to suggest otherwise.
Misrepresentation may occur not only through explicit claims, but also through:
a) labels, badges, seals, or notations that appear official or certifying in character; b) dashboards, repositories, or public-facing interfaces that create the appearance of passage through an approval gate; c) language implying that a party has been “cleared,” “recognized,” “qualified,” “approved,” “verified,” or “validated” in a formal sense beyond what is truthfully supported; d) association with the Corporation in a context that reasonably suggests endorsement; or e) silence where clarification is necessary to prevent material public misunderstanding.
The Corporation may truthfully describe the existence of collaboration, participation, contribution, structured engagement, testing, or bounded conformance-support activity where such descriptions are accurate and sufficiently qualified. It may not allow those truthful but limited facts to be presented in a manner that inflates them into endorsement, approval, certification, or formal standing. Where ambiguity exists, the narrower and less approval-suggestive description shall be used.
Any actual or reasonably foreseeable public misunderstanding of endorsement or approval effect shall be treated as a perimeter and claims-discipline issue requiring timely correction, clarification, redesign, or withdrawal as appropriate.
19.2 Misuse of Institutional Name, Marks, Badges, or Affiliations
The Corporation’s name, marks, logos, designations, badges, labels, affiliations, architectural references, citations, and other indicators of association shall not be used in any manner that creates false or exaggerated impressions regarding authority, endorsement, standing, sponsorship, readiness, maturity, legal effect, regulatory status, or institutional relationship. This prohibition applies to internal and external use, including use by directors, officers, staff, advisors, contributors, donors, sponsors, collaborators, technical partners, participants, and third parties.
Misuse includes, without limitation:
a) use of the Corporation’s name or marks to imply governmental, regulatory, sovereign, or supervisory authority; b) use of Corporation affiliation to imply that a person, entity, or product has been formally approved or certified; c) use of badges or labels in a way that reasonably implies interoperability, recognition, or conformance standing beyond what has actually been recorded; d) use of the Corporation’s identity to confer artificial legitimacy on fundraising, commercial offerings, political agendas, or transaction-facing activities; and e) use of co-branding, event branding, or public listings that materially obscure the limits of the Corporation’s role.
The Corporation shall maintain governance over the issuance, approval, and use of its marks and institutional designators. No person may infer permission to use them merely from collaboration, contribution, funding, or participation. All significant uses of name, marks, or formal identifiers shall remain subject to truthfulness, scope control, and the anti-overclaim principles of these Bylaws.
Where misuse occurs, the Corporation may require immediate cessation, correction, clarification, takedown, public disavowal, contractual remedy, restriction of access, or other appropriate measures proportionate to the seriousness of the misuse.
19.3 False Claims of Recognition, Readiness, Routeability, or Standing
The Corporation shall not make, support, tolerate, or fail reasonably to correct false claims of recognition, readiness, routeability, standing, maturity, interoperability, supportability, or institutional legitimacy where such claims concern the Corporation itself, its outputs, its systems, or any person or entity associated with it. This prohibition applies whether the claim is made explicitly, implied through context, or operationally suggested by interface design, metadata, sequencing, or omission.
In particular, the Corporation shall not allow its outputs or relationships to be described as though they establish:
a) formal recognition or standing by a governance-valid authority where none exists; b) readiness for adoption, financing, market use, or execution where such determination lies elsewhere or remains unmade; c) routeability into downstream consequence-bearing systems by virtue of upstream technical rigor alone; d) public-authority or regulatory confidence beyond what is expressly and lawfully documented; or e) institutional maturity or scale not actually achieved and supportable.
The Corporation may properly state that an artifact has been produced under certain methods, has undergone certain review or testing steps, or exists at a particular documented stage of development. It may not convert such statements into implications of broader readiness, downstream eligibility, or governance-valid standing. Where third parties overstate such meaning, the Corporation shall take reasonable corrective measures.
19.4 Presentation of GCRI US Outputs as Regulatory, Sovereign, or Transactional Instruments
The Corporation shall not present, draft, structure, format, label, or distribute its outputs in a way that causes them reasonably to appear to be regulatory instruments, sovereign instruments, transactional instruments, executable instructions, binding approvals, formal legal determinations, or market-facing instruments. This prohibition applies to mission-bearing outputs of every type, including evidence packs, technical notes, structured assessments, observability summaries, frameworks, schemas, dashboards, public-safe reports, educational materials, and partnership instruments.
This prohibition extends to both substance and presentation. Even if the content of an output is informational or educational in intent, the Corporation shall not:
a) give it formal characteristics strongly associated with approvals or authorizations if such presentation would mislead; b) position it within a workflow that makes it function as a required operative step for execution or public action; c) use headers, states, flags, or metadata that imply completed formal clearance or enforceable effect; d) omit necessary limitations where foreseeable users are likely to overread the document; or e) permit counterparties to incorporate Corporation outputs into transaction or approval packages in a manner that falsely suggests direct institutional authorization by GCRI US.
The Corporation may produce serious upstream artifacts that are valuable inputs to downstream lawful action by others. It may not let its artifacts masquerade as the downstream act itself.
19.5 Inflation of Maturity, Supportability, Deployment State, or Institutional Capacity
The Corporation shall not inflate, exaggerate, or materially overstate its own or its systems’ maturity, supportability, deployment state, institutional capacity, geographic reach, operational readiness, technical completeness, security posture, conformance posture, or organizational depth. Truthfulness about institutional state is essential to public-benefit legitimacy and to preventing reliance errors, partner confusion, funding distortion, and constitutional drift.
Inflation may take many forms, including:
a) presenting a draft or prototype as if it were stable or production-ready; b) describing pilot-stage infrastructure as if it had broad operational deployment; c) overstating support capacity, staffing depth, uptime capability, or continuity arrangements; d) representing aspirational architecture as if already implemented; e) using selective anecdotes or partnership references to imply systemic maturity; or f) failing to disclose material dependencies, limitations, uncertainties, or absence of support conditions where omission changes the overall meaning.
The Corporation may properly communicate ambition, roadmap, target states, and intended trajectory, provided that such communications clearly distinguish future plans from present realities. It shall not allow strategic storytelling, fundraising need, or ecosystem competition for attention to degrade factual accuracy concerning what is real now.
19.6 Use of Participation, Membership, Advisory Status, or Affiliation as Evidence of Official Standing
The Corporation shall not permit participation, membership, advisory status, fellowship, contribution status, event participation, consultation access, working-group inclusion, institutional dialogue, or any analogous affiliation to be used as evidence of official standing, governmental recognition, regulatory acceptance, conformance validity, execution readiness, or endorsed legitimacy beyond what such affiliation truthfully means. Participation is not certification. Membership is not approval. Advisory status is not delegated authority.
This prohibition applies both to the Corporation’s own descriptions and to third-party descriptions that the Corporation becomes aware of and can reasonably address. Misuse may include:
a) citing Corporation participation as proof of regulatory or sovereign endorsement; b) describing membership or affiliation as if it confers formal qualification or credentialed readiness; c) implying that inclusion in a dialogue, program, or directory establishes trusted status or institutional approval; d) presenting co-appearance with the Corporation as validation of product, service, or organizational legitimacy; or e) using Corporation-issued participation language to imply a ranking, standing, or status not actually granted.
The Corporation shall ensure that all participation categories are truthfully defined, bounded, and described with sufficient clarity to prevent foreseeable misuse. Where a participation construct creates repeated confusion, the Corporation shall revise its labels, materials, or access conditions.
19.7 Omission of Required Disclaimers, Boundaries, Scope Conditions, or Reliance Limits
The Corporation shall not omit disclaimers, boundary statements, scope conditions, handling notices, non-endorsement statements, non-reliance formulations, or other qualifying information where such omission would materially distort the meaning, effect, maturity, or lawful use of an output or institutional representation. Misrepresentation often occurs not through false words alone, but through the omission of necessary limiting context.
The Corporation shall therefore include appropriate limitation language, in proportion to risk and context, where needed to make clear:
a) that an output is upstream, educational, scientific, technical, or evidentiary rather than approving or executing; b) the scope and intended use of an artifact; c) material assumptions, dependencies, and limitations; d) that independent legal, regulatory, fiduciary, technical, or operational judgment remains with the recipient; and e) that the Corporation’s role remains bounded by mission and law.
This rule does not require repetitive or excessive disclaimer language in every setting. It requires enough limiting information to prevent material misunderstanding in the circumstances. The Corporation shall govern this proportionately, but it shall not allow brevity, aesthetics, or convenience to create false legibility.
19.8 Misleading Silence, Ambiguous Positioning, and Interface-Induced Overreading
The Corporation shall not rely on misleading silence, strategically ambiguous positioning, or interface design that predictably induces overreading. Even where individual statements are technically defensible, overall institutional meaning may still be materially misleading if the Corporation structures public materials, dashboards, repository views, workflow states, process names, or partnership descriptions in ways that a reasonable recipient would interpret as carrying stronger authority, readiness, approval, or institutional finality than is actually warranted.
Misleading ambiguity may arise where:
a) a system state appears equivalent to a passed clearance threshold; b) an artifact is placed in a repository tier that signals official status not actually held; c) wording is carefully hedged while surrounding design strongly suggests approval; d) relationship language is left vague so that others infer endorsement or authority; or e) the Corporation declines clarification despite knowing that third parties are materially overreading the situation.
The Corporation shall assess not only literal truth, but also overall conveyed meaning. If the likely meaning is misleading in context, the Corporation shall treat the issue as a claims and perimeter matter requiring remediation.
19.9 Corrective Duties, Withdrawal Powers, and Record of Misrepresentation Events
Where the Corporation becomes aware that a misrepresentation, overclaim, false legibility event, misleading omission, or materially confusing institutional signal has occurred or is occurring, it shall take proportionate corrective action. Such action may include:
a) internal clarification; b) external clarification; c) correction or republication of the affected material; d) withdrawal or takedown; e) redesign of labels, dashboards, or repository states; f) restriction on future use of marks, badges, or affiliations; g) contractual or participation-related remedies; or h) escalation to legal, integrity, compliance, or Board channels.
Material incidents shall be recorded sufficiently to preserve institutional memory, support remediation, and inform future control improvements. The Corporation shall not normalize recurrent overclaim problems as inevitable communications noise. Repeated misrepresentation is evidence of governance weakness and shall be addressed structurally.
19.10 Interpretive Rule for Misrepresentation, Overclaim, and False Legibility
This Section shall be interpreted to preserve truthful public meaning, bounded institutional seriousness, and protection against accidental or intentional inflation of authority, maturity, or effect. Where ambiguity exists, the interpretation that better preserves:
a) truthful description of role and status; b) narrower implied authority; c) clearer reliance limits; d) safer institutional meaning; and e) stronger protection against public misunderstanding
shall prevail unless a contrary result is required by law.
20. Prohibited Activities Schedule — Political, Partisan, and Improper Advocacy Conduct (GCRI United States)
20.1 Prohibition on Political Campaign Intervention Inconsistent With 501(c)(3) Status
The Corporation shall not participate or intervene, directly or indirectly, in any political campaign on behalf of or in opposition to any candidate for public office, nor shall it permit its resources, institutional standing, systems, outputs, platforms, events, or personnel acting in official capacity to be used for such purpose. This prohibition shall be construed in a manner fully consistent with the Corporation’s intended and maintained status under Section 501(c)(3) of the Internal Revenue Code, applicable Treasury regulations, Internal Revenue Service guidance, and other applicable law.
Political campaign intervention is prohibited whether carried out through:
a) formal endorsement or opposition; b) ratings, rankings, or scorecards structured to influence electoral outcomes; c) coordinated messaging designed to advantage or disadvantage specific candidates or parties; d) targeted release timing intended primarily to shape electoral outcomes; e) selective platform access, institutional signaling, or event design favoring one candidate or party over another; f) in-kind support, data support, list use, communications support, or infrastructure support for campaign purposes; or g) indirect arrangements through partners, coalitions, convenings, or “independent” affiliated channels where the practical effect is campaign intervention.
This prohibition applies even where a contemplated act is framed as educational, public-interest oriented, emergency-related, values-driven, or technically neutral. If the practical effect, context, timing, and foreseeable public understanding indicate that the Corporation is participating or intervening in electoral politics, the act is prohibited. No degree of mission sincerity, public urgency, or policy concern shall override this rule.
The Corporation may engage in lawful educational, scientific, and issue-based public-interest work relevant to policy environments, public systems, and resilience conditions. It may not use that work as a vehicle for campaign intervention or allow others reasonably to treat it as such.
20.2 Boundary Between Public-Interest Policy Contribution and Political Campaigning
The Corporation may, within the limits of law and these Bylaws, contribute to public-interest understanding of policy, law, technical governance, public systems, institutional capability, resilience, readiness, observability, evidence quality, and related matters. Such contribution may include publication of research, technical comments, educational analysis, structured frameworks, public-interest recommendations, and participation in lawful consultations or public dialogue. These activities are distinguishable from political campaigning and shall remain so.
The boundary between lawful public-interest policy contribution and impermissible political campaigning shall be assessed by reference to substance, context, timing, audience, tone, distribution pattern, institutional framing, and likely effect. Relevant considerations include, without limitation:
a) whether the communication is directed to issues or to electoral outcomes; b) whether it refers to candidates, parties, campaigns, or election contests; c) whether it is timed or structured in a manner that reasonably suggests electoral intent; d) whether it presents opposing positions fairly where such fairness is relevant to nonpartisan educational treatment; e) whether the Corporation is using issue advocacy as a practical surrogate for candidate support or opposition; and f) whether the overall institutional conduct would reasonably be understood by an informed observer as intervention in an election.
The Corporation shall not rely on formal disclaimers alone to save conduct whose practical meaning is partisan or campaign-oriented. Conversely, the mere existence of public controversy around an issue shall not automatically convert all issue-based education into partisan conduct. The Corporation’s duty is to preserve a clearly non-campaigning posture through disciplined design, review, and truthful public framing.
Where the distinction is uncertain, the narrower and more politically neutral course shall be adopted unless and until appropriate legal review confirms that the contemplated activity is permissible.
20.3 No Institutional Use for Electoral, Partisan, or Ideological Mobilization
The Corporation shall not permit its institutional identity, infrastructure, convening power, research outputs, educational assets, observability systems, public credibility, staff time, repository environments, technical platforms, mailing lists, event formats, or other mission-bearing resources to be used for electoral mobilization, partisan mobilization, or ideological mobilization in a manner inconsistent with its exempt purposes, public-benefit role, and nonpartisan status under law.
This prohibition applies whether mobilization is explicit or implicit, including where the Corporation’s systems or events are used to:
a) turn out voters for particular political ends; b) channel supporters toward candidates, parties, slates, or campaigns; c) normalize one political bloc as institutionally preferred; d) stigmatize or delegitimize political actors in a manner tied to electoral effect rather than mission-consistent technical or public-interest analysis; e) create issue campaigns whose practical objective is electoral advantage; or f) reinforce ideological coalitions in a way that exceeds lawful educational or scientific discourse and becomes partisan institutional action.
The Corporation may educate about public systems, governance, resilience, technical infrastructure, and policy-relevant conditions. It may not become an institutional machine for mobilization around electoral or partisan ends. This rule protects both exempt status and the constitutional distinctness of the Corporation as a bounded public-benefit institution rather than a movement apparatus, campaign platform, or ideological instrument.
20.4 No Party-Political Endorsements, Coordinated Campaigning, or Political Fundraising
The Corporation shall not make or imply party-political endorsements, coordinate with campaigns or political parties, solicit or direct funds for campaign purposes, host campaign fundraising, provide campaign infrastructure, or otherwise participate in political fundraising or electioneering activity. It shall not permit its name, premises, systems, mailing lists, events, institutional platforms, or official roles to be used as venues or channels for campaign advancement.
This includes, without limitation:
a) endorsing or opposing candidates, parties, slates, or political committees; b) coordinating public messaging or event timing with campaigns or party structures; c) providing mailing lists, data, observability outputs, or technical services for campaign use; d) fundraising for candidates, parties, PACs, or other political entities; e) using corporate events, webinars, panels, or publications to create campaign advantage; and f) permitting officers, staff, or representatives to imply that personal political activity is institutionally authorized or endorsed.
Individuals associated with the Corporation retain whatever personal political rights they hold under law in their individual capacities, subject to conflict, time, and resource constraints and subject to clear separation from institutional identity. Nothing in such personal rights authorizes use of corporate resources, titles, or channels in ways that blur personal and institutional political activity.
20.5 No Hidden Political Influence Through Programs, Panels, Publications, or Technical Surfaces
The Corporation shall not exercise or facilitate hidden political influence through programs, public-interest platforms, technical surfaces, publications, observability releases, event design, speaker selection, sequencing decisions, semantic framing, or other institutional choices that are formally presented as neutral or technical but are intentionally or foreseeably structured to produce partisan or electoral effects inconsistent with the Corporation’s lawful role.
Hidden political influence may arise where:
a) a panel or event is curated to produce one-sided political signaling while described as technical dialogue; b) publication timing or framing is chosen primarily to influence elections or legislative blocs rather than to serve mission-consistent educational or scientific purposes; c) observability or evidence outputs are selectively released or withheld to benefit political actors; d) speaker platforms are used to create implied institutional preference for partisan positions beyond the Corporation’s role; e) technical narratives are sharpened or softened for political rather than scientific or public-interest reasons; or f) the Corporation’s infrastructure is used as a seemingly neutral channel for message amplification that materially favors one political current.
The Corporation shall assess not only the literal content of its actions, but also the foreseeable public meaning and strategic effect of institutional behavior in context. It shall not hide political conduct inside technical form.
20.6 Counsel Review of Public Policy Participation at the Edge of Permissibility
Any proposed public policy engagement, consultation response, public letter, event format, publication strategy, coalition participation, public statement, or external-facing activity that could plausibly approach the edge between lawful public-interest engagement and prohibited partisan, campaign, or substantial lobbying conduct shall be subject to appropriate legal review, and where warranted, compliance or Board review, before institutional commitment or public release.
Such review shall consider, as relevant:
a) the Corporation’s tax-exempt posture and applicable legal limits; b) the nature, scope, and audience of the proposed activity; c) whether the activity involves issue education, technical analysis, consultation, advocacy, or campaign-related effect; d) whether any candidate, party, electoral contest, or legislative pressure campaign is implicated; e) the cumulative level of advocacy or lobbying exposure if relevant; f) the adequacy of role-boundary language and institutional framing; and g) whether alternative, narrower, or safer structures are available.
The Corporation shall not treat edge-of-permissibility policy activity as ordinary communications work. Activities close to legal or constitutional boundaries require discipline precisely because they may appear mission-consistent while carrying hidden political or tax risk. In cases of unresolved ambiguity, the more restrictive, nonpartisan, and lower-risk path shall prevail.
20.7 Recordkeeping, Approval, and Disclosure Discipline for Sensitive Public-Affairs Engagement
The Corporation shall maintain appropriate recordkeeping, approval discipline, and disclosure controls for public-affairs, policy-facing, consultation-facing, and other politically sensitive activities. This is necessary both for legal compliance and for constitutional integrity. Sensitive public-affairs engagement shall not occur through ad hoc, undocumented, personality-driven, or side-channel practice.
To the extent appropriate for the nature of the matter, the Corporation shall maintain records of:
a) the purpose and proposed scope of the engagement; b) the institutional basis for participation; c) any legal or compliance review undertaken; d) the approvals or sign-offs obtained; e) any relevant limitations, disclaimers, or boundary language required; f) the final materials used or submitted; and g) any subsequent clarifications, corrections, or controversies requiring follow-up.
Where disclosure is required by law or is necessary to preserve truthful institutional description, the Corporation shall make such disclosure in a manner consistent with law, security, privacy, and mission. Where disclosure is not required, the Corporation shall still preserve internal records sufficient to demonstrate that public-affairs engagement has been conducted within perimeter, tax, and mission boundaries.
No officer, staff member, advisor, or participant may commit the Corporation to politically sensitive public-affairs engagement outside such disciplined process.
20.8 Institutional Neutrality in Political Contexts
In all politically sensitive environments, the Corporation shall preserve institutional neutrality consistent with its exempt purposes and public-benefit mission. Neutrality does not require false balance in scientific or technical analysis, nor does it prohibit the Corporation from describing reality, risk, institutional weakness, or public-interest need in precise and candid terms. It does require that the Corporation not become a partisan actor, not tailor truth to electoral outcomes, and not use its institutional position to favor or disfavor political factions as such.
Institutional neutrality requires the Corporation to preserve, in politically charged contexts:
a) methodological rigor over factional convenience; b) public-benefit framing over campaign utility; c) correctionability over rhetorical entrenchment; d) scope discipline over issue-sprawl and ideological mission creep; and e) clear separation between institutional acts and personal views of associated individuals.
Where neutrality is at risk, the Corporation shall narrow, redesign, defer, or decline the relevant activity as necessary to preserve legality, mission, and public trust.
20.9 Interpretive Rule for Political, Partisan, and Improper Advocacy Conduct
This Section shall be interpreted to preserve the Corporation’s status as a nonpartisan, public-benefit, scientific, and educational institution that may contribute lawfully to public-interest understanding and policy discourse without crossing into campaign intervention, partisan institutional behavior, ideological capture, or impermissible advocacy exposure. Where ambiguity exists, the interpretation that better preserves:
a) 501(c)(3)-compatible nonpartisanship; b) truthful public-interest framing; c) narrower political effect; d) lower tax and reputational risk; and e) clearer separation between education and campaigning
shall prevail unless a contrary result is required by law.
21. Prohibited Activities Schedule — Competition, Antitrust, and Collusive Conduct (GCRI United States)
21.1 Competition and Antitrust Primacy as a Perimeter Control
The Corporation shall conduct all of its affairs in compliance with applicable U.S. antitrust, competition, unfair competition, market-conduct, procurement, and related laws, and shall treat such compliance as a primary perimeter control rather than a secondary legal afterthought. Because the Corporation convenes institutions, produces shared infrastructure, operates in information-rich environments, and may engage actors who compete in commercial markets, the risk of antitrust or competition-sensitive misconduct may arise even where the Corporation itself is not a market participant. The Corporation shall therefore govern its convening, information practices, technical interfaces, and institutional relationships with heightened discipline.
Competition-law compliance shall apply across:
a) Board and committee activity; b) councils, working groups, workshops, and technical sessions; c) public and controlled publications; d) data collection, aggregation, and dissemination practices; e) observability, benchmarking, and interoperability-related activities; f) partnerships with vendors, infrastructure providers, firms, or associations; and g) any environment in which competitors, potential competitors, customers, vendors, or market-influencing actors interact through the Corporation’s systems or convening surfaces.
The Corporation shall not treat its nonprofit status, public-benefit mission, scientific posture, or technical orientation as a shield from competition-law risk. Activities that are mission-consistent in general purpose may still be unlawful if structured or used in ways that facilitate collusion, coordination, exclusion, market signaling, or anticompetitive distortion. Antitrust discipline is therefore part of mission discipline. An institution that claims neutrality and public benefit must not become a venue for unlawful competitive coordination.
Where ambiguity exists as to whether a contemplated activity could materially implicate competition law, the Corporation shall apply the narrower, safer, and more competition-protective interpretation unless and until appropriate review determines otherwise.
21.2 Prohibited Topics, Exchanges, and Coordination Risks
The Corporation shall not host, facilitate, normalize, or tolerate the exchange of competitively sensitive information or the coordination of conduct among competitors or similarly situated market actors where such exchange or coordination could reasonably create antitrust, collusion, bid-rigging, market-allocation, price-signaling, boycott, exclusion, or similar legal risk. This prohibition applies regardless of whether the exchange occurs formally or informally, in plenary session or side conversation, synchronously or asynchronously, and whether the participants describe the exchange as educational, exploratory, technical, or strategic.
Without limitation, prohibited exchanges and topics may include:
a) current or future prices, fees, spreads, margins, or pricing strategy; b) bid strategy, procurement strategy, or competitive response strategy; c) customer or supplier allocation; d) market-division or territory-division arrangements; e) future product rollouts, production decisions, or volume strategies where competitively sensitive; f) coordinated refusals to deal, concerted exclusions, or blacklist-like behavior; g) confidential non-public commercial terms, discounts, or customer-specific arrangements; and h) strategic signaling intended to influence competitor behavior.
The prohibition is functional rather than formal. It extends to any exchange that, in context, could materially reduce competitive independence or facilitate alignment among market actors. The Corporation shall not allow “technical benchmarking,” “ecosystem coordination,” “interoperability dialogue,” “standards discussion,” or “industry readiness” language to become cover for impermissible information exchange or coordinated market conduct.
The Corporation may lawfully convene multi-actor technical, scientific, educational, and public-interest discussions where structured appropriately. It may not host or permit conversations that drift into coordination of private market behavior. All participants remain responsible for their own compliance, but the Corporation bears an independent duty not to create or maintain environments that materially elevate antitrust risk.
21.3 No Facilitation of Price Signaling, Allocation, Boycott, or Coordinated Strategy
The Corporation shall not facilitate or materially contribute to price signaling, market allocation, customer allocation, territorial division, boycott coordination, coordinated refusal to deal, exclusionary alignment, or coordinated strategy among firms, intermediaries, service providers, infrastructure actors, or other market-relevant participants. The Corporation shall remain especially vigilant where its convening role, information position, technical systems, or institutional credibility could be used to give such coordination a false appearance of neutrality or legitimacy.
Prohibited facilitation includes, without limitation:
a) structuring agendas or working sessions in ways that invite coordination on competitively sensitive conduct; b) summarizing or redistributing discussions in a manner that transmits strategic signals among competitors; c) creating dashboards, comparative products, or observability views whose level of granularity or timing makes coordination easier; d) allowing committees or task forces to evolve into de facto coordination cells for private-market participants; e) using the Corporation’s public-benefit standing to soften participants’ caution around information exchange; and f) providing shared interpretive or strategic frameworks that effectively coordinate commercial behavior rather than support public-interest understanding.
The Corporation shall not assume that facilitation requires explicit conspiracy language. In competition law, unlawful coordination may emerge through repeated signaling, structured information exchange, or “everyone knows what this means” environments. The Corporation shall therefore govern not only what is formally said, but what its structures and outputs make possible.
Where a topic, format, or comparative product presents a credible risk of enabling coordinated strategy, the Corporation shall narrow the scope, raise the level of aggregation, segment the audience, redesign the format, or refuse the activity entirely.
21.4 No Use of Forums, Councils, Working Sessions, or Technical Rooms for Competitively Sensitive Coordination
The Corporation’s forums, councils, workshops, advisory bodies, committee meetings, working sessions, technical rooms, simulations, exercises, digital collaboration spaces, repository-comment channels, and other convening surfaces shall not be used as venues for competitively sensitive coordination. This prohibition applies equally to formal meetings, informal pre-meeting and post-meeting interactions, breakout rooms, side channels, chat tools, collaborative documents, and other spaces provided, convened, administered, or legitimized by the Corporation.
All such forums shall be designed and governed to preserve:
a) lawful public-interest discussion; b) scientific and technical exchange consistent with the Corporation’s mission; c) clear boundaries against market-coordinating behavior; and d) the ability of participants to disengage from prohibited subjects without ambiguity.
The Corporation shall not tolerate the argument that “everyone in the room understands the rules” as a substitute for active design and moderation. Nor shall it assume that an antitrust problem arises only where participants expressly announce anticompetitive intent. The misuse of an otherwise legitimate forum for competitively sensitive coordination is itself a perimeter issue.
Where participants are actual or potential competitors, or where multiple market actors with aligned commercial interests are present, the Corporation shall apply heightened discipline to agenda-setting, moderation, minutes, materials circulation, and post-session handling. If a session cannot be conducted safely within those constraints, it shall not proceed in the proposed form.
21.5 Clean-Room, Aggregation, and Competition-Safe Information Discipline
Where the Corporation engages in benchmarking, structured comparison, observability, data aggregation, interoperability assessment, ecosystem analysis, or related activities that may involve information from multiple market-relevant actors, it shall maintain clean-room, aggregation, separation, and competition-safe information discipline appropriate to the risk. The Corporation shall not collect, structure, publish, or expose information in a manner that makes individual competitive positioning, future strategy, or commercially sensitive detail visible in ways that could facilitate collusion, market coordination, or strategic alignment.
This discipline may require, as appropriate:
a) de-identification or anonymization; b) aggregation above thresholds sufficient to reduce coordination risk; c) time-lagging of certain data; d) separation of analysts, moderators, or technical roles; e) restrictions on participant visibility into raw inputs; f) controlled dissemination or access segmentation; and g) explicit governance over how aggregated outputs may be used or described.
The Corporation shall not assume that aggregation is safe merely because it is mathematically aggregated. Some aggregated outputs remain competitively sensitive if the participant set is too small, the categories too narrow, the timing too current, or the context too revealing. Clean-room and aggregation design shall be driven by practical competition risk, not by formalism.
The Corporation may produce structured public-good insights where lawfully and mission-consistently possible. It shall not do so at the price of turning public-benefit analysis into a coordination aid for private actors.
21.6 Stop-the-Meeting, Stop-the-Work, and Quarantine Authority
The Corporation shall maintain stop-the-meeting, stop-the-work, and quarantine authority for any session, project, output stream, technical product, working relationship, or information flow that presents a credible risk of antitrust, collusion, market coordination, or other competition-sensitive misconduct. This authority may be exercised by the chair, moderator, legal reviewer, compliance lead, designated officer, or other person expressly authorized by policy or specific delegation.
Where such authority is invoked, the responsible person may require, as appropriate:
a) immediate cessation of the relevant discussion; b) removal or redaction of problematic material; c) segmentation of participants or channels; d) suspension of publication or circulation; e) escalation to counsel or compliance; f) temporary or longer-term quarantine of the matter pending review; and g) recorded notation of the reason for intervention.
Good-faith invocation of stop authority shall not be penalized or informally discouraged. The Corporation shall prefer a false positive in stopping a risky discussion over a false negative that permits unlawful conduct to continue under its auspices. Competition safety is more important than conversational convenience or event flow.
21.7 Incident Handling, Remediation, and Record of Competition-Sensitive Events
Any actual or reasonably suspected competition-sensitive incident—including impermissible information exchange, agenda drift into prohibited topics, problematic benchmarking design, collusion-risk signaling, misuse of forums, or other material antitrust concern—shall be treated as an institutional incident requiring appropriate containment, review, remediation, and recordkeeping. The Corporation shall not normalize or quietly absorb such events as routine meeting noise.
Incident handling may include, as appropriate:
a) immediate containment and cessation of the relevant conduct; b) preservation of relevant materials, notes, and communications; c) legal and compliance review; d) notification of affected internal leads and, where appropriate, the Board or a Board committee; e) remediation of outputs, platforms, or practices that contributed to the risk; f) participant guidance, reminders, or corrective notices; and g) redesign of the relevant process to reduce recurrence risk.
A record of material incidents shall be maintained to support institutional memory, perimeter learning, and auditability of competition-sensitive controls. The Corporation shall use such incidents not only to assign responsibility where appropriate, but also to improve structural design, moderation protocols, and risk-detection capacity. Repetition of similar incidents shall be treated as evidence of control weakness requiring stronger governance response.
21.8 Competition-Safe Design of Membership, Participation, and Visibility Structures
The Corporation shall design its membership, participation, visibility, and convening structures in a competition-safe manner. It shall not create tiers, councils, expert groups, or program tracks whose practical effect is to gather commercial competitors into privileged channels of coordinated market intelligence, strategic positioning, or exclusionary alignment. Participation design must serve public-benefit, scientific, educational, or technical ends consistent with mission—not private-market coordination.
Accordingly, the Corporation shall be attentive to whether:
a) participation groupings unintentionally cluster direct competitors in overly intimate decision environments; b) visibility structures imply preferred market positioning; c) shared workstreams create the appearance or reality of coordinated competitive conduct; d) technical standardization discussion drifts into commercial harmonization beyond lawful scope; and e) convening formats give certain actors access to commercially useful aggregated intelligence not equally or lawfully available.
The Corporation may convene diverse actors where such convening is necessary for public-benefit or technical reasons. It shall do so with design controls sufficient to prevent its own structures from becoming unintended coordination mechanisms.
21.9 Interpretive Rule for Competition, Antitrust, and Collusive Conduct
This Section shall be interpreted to preserve the Corporation as a competition-safe, non-collusive, non-coordinating public-benefit institution whose scientific, educational, and technical work does not become a vehicle for market distortion, private coordination, exclusionary conduct, or competitively sensitive signaling. Where ambiguity exists, the interpretation that better preserves:
a) independent competitive conduct by private actors; b) narrower information exposure; c) safer convening design; d) stronger antitrust and market-conduct compliance; and e) clearer separation between public-benefit coordination and private-market alignment
shall prevail unless a contrary result is required by law.
22. Prohibited Activities Schedule — Regulatory and Execution Equivalence by Proxy (GCRI United States)
22.1 No Acting Through Partners to Do What GCRI US Cannot Lawfully Do Itself
The Corporation shall not do indirectly, through any partner, affiliate, host, contractor, service provider, special-purpose arrangement, coalition structure, technical intermediary, or nominally independent actor, what it is prohibited from doing directly under these Bylaws, the Articles of Incorporation, applicable law, or its exempt-purpose posture. A perimeter breach does not become lawful merely because the final operational step is performed by someone else while the Corporation designs, directs, controls, determines, compels, or materially conditions that step.
This prohibition applies where the Corporation would, in substance:
a) design or dictate the decisive logic of a regulated or execution-bearing act while another entity merely carries it out; b) use a partner as a formal wrapper for a function the Corporation itself may not perform; c) orchestrate a sequence such that the partner is reduced to a nominal implementer of GCRI US judgment; d) preserve deniability through contractual distance while retaining operational control or decisive influence; or e) create an arrangement whose legal form appears separate but whose practical effect is that the Corporation has caused, directed, or operationally governed the prohibited function.
The Corporation may lawfully support external actors through bounded public-good infrastructure, evidence systems, methods, training, and technical assistance. It may not structure that support so that the external actor becomes the Corporation’s execution sleeve, approval sleeve, market sleeve, or sovereign sleeve. If the partner’s role exists principally to externalize legal risk while preserving substantive control within the Corporation, the arrangement is prohibited.
22.2 No Shadow Execution Through Branding, Delegation, Technical Architecture, or Embedded Control
The Corporation shall not permit shadow execution through branding, delegation, workflow design, technical architecture, embedded permissions, interface states, data dependency, process sequencing, or other indirect control mechanisms that produce execution-bearing, approval-bearing, market-facing, or sovereign-like effect while formally disclaiming responsibility. Shadow execution is prohibited whether intentional or tolerated through structural negligence.
Shadow execution includes, without limitation:
a) using GCRI US branding, credibility, or institutional position to create a practical approval surface that others treat as determinative; b) delegating nominal execution while retaining substantive decision logic or veto control; c) designing technical systems whose states, gates, or handoffs make downstream execution effectively dependent on Corporation-controlled signals; d) embedding Corporation personnel or tools inside partner environments in a way that gives the Corporation operational control over regulated or consequence-bearing acts; and e) using ostensibly neutral technical criteria that in practice compel a partner’s final action.
The Corporation shall assess not merely whether a document says “final decision remains with the partner,” but whether, in substance, the partner retains real and independent discretion, legal responsibility, and operational judgment. If the partner’s discretion is more apparent than real because the Corporation controls the meaningful preconditions, data gates, workflow states, or public legitimacy signals, the arrangement shall be treated as shadow execution and prohibited or restructured.
22.3 No Soft-Control Over Licensed, Regulated, or Public Actors That Amounts to Execution
The Corporation shall not exercise soft-control over licensed, regulated, fiduciary, supervisory, or public actors in a manner that, while stopping short of express command, effectively determines or materially constrains execution-bearing outcomes. Soft-control may arise through dependency, asymmetric information, reputational pressure, infrastructural centrality, integration design, or implied institutional expectation. If the effect is operationally decisive, the Corporation shall not evade responsibility by characterizing the arrangement as merely supportive or advisory.
Soft-control risk may arise where the Corporation:
a) controls access to mission-critical infrastructure on terms that influence a partner’s downstream legal or market conduct; b) structures workflows so that deviation from GCRI US outputs is practically disfavored or penalized; c) supplies system states or labels that are foreseeably treated as decisive go/no-go indicators; d) exerts reputational leverage over counterparties whose standing depends materially on continued Corporation association; or e) embeds itself into a chain of action in such a way that downstream actors no longer exercise genuinely independent judgment.
The Corporation may support serious institutional action through public-good infrastructure. It may not become the hidden determinant of that action. If counterparties begin treating the Corporation as the practical source of final judgment, the Corporation shall narrow, redesign, clarify, or withdraw the relevant interface.
22.4 No Indirect Brokerage, Intermediation, Referral Steering, or Transaction Choreography
The Corporation shall not engage in indirect brokerage, intermediation, referral steering, transaction choreography, counterparty matching, distribution support, market-access facilitation, or execution-adjacent routing under labels such as ecosystem support, convening, capacity-building, readiness facilitation, or technical coordination where the practical effect is to move specific transactions, opportunities, mandates, or counterparties toward closure or execution.
This prohibition includes, without limitation:
a) introducing specific parties in a manner intended to facilitate a deal, issuance, allocation, or regulated arrangement; b) curating counterparties or transaction opportunities for likely execution outcomes; c) routing particular artifacts, parties, or opportunities to selected actors in ways that resemble placement, deal origination, or market intermediation; d) designing process flows that move identified opportunities through quasi-transaction stages under GCRI US visibility or influence; and e) structuring partner networks or data rooms primarily as execution pipelines rather than public-good knowledge environments.
The Corporation may convene broad public-interest dialogue, maintain directories or ecosystem maps for mission-consistent informational purposes, and support general educational exchange. It may not use those activities as a disguised route to matching, steering, or advancing specific regulated or market-facing outcomes. General ecosystem intelligibility is permissible; specific transaction choreography is not.
22.5 No Routing of Specific Transactions, Clients, Capital, or Opportunities Under GCRI US Authority
The Corporation shall not route, select, assign, steer, recommend, channel, or prioritize specific transactions, clients, counterparties, capital sources, implementation opportunities, regulated engagements, or market opportunities under its own authority or in a way reasonably likely to be understood as the Corporation’s exercise of selection power over execution-bearing pathways.
This rule prohibits, among other things:
a) deciding which specific opportunity goes to which specific implementer, financier, service provider, or regulated actor; b) serving as a screening or triage authority for execution-bearing counterparties; c) conferring implied priority through invitation, sequencing, or endorsement-like routing; d) using internal or shared systems to govern which actors gain access to specific downstream opportunities; and e) allowing participants to market Corporation contact or routing as evidence of preferred institutional treatment.
The Corporation may publish open, neutral, and mission-consistent information that lawful recipients independently interpret. It may not transform itself into a gatekeeper, selector, recommender, or traffic controller for particular downstream deals, opportunities, or regulated relationships. If an activity requires the Corporation to choose winners, routes, or counterparties in a way that materially affects execution-bearing outcomes, the activity is presumptively prohibited.
22.6 No Revenue Models Dependent on Execution Volume, Deal Closure, Capital Placement, or Transaction Success
The Corporation shall not adopt, maintain, or tolerate revenue models, compensation structures, partnership economics, sponsorship arrangements, or performance metrics that depend materially on execution volume, deal closure, transaction completion, capital placement, financial issuance, claims payout, market uptake, regulated approvals, or other consequence-bearing outcomes that the Corporation is constitutionally prohibited from performing or approximating.
Prohibited structures include, without limitation:
a) success fees tied to closed transactions, capital deployment, placement, underwriting, issuance, or regulated operating outcomes; b) compensation linked to volume of routed opportunities or counterpart matches; c) revenue-sharing tied to downstream market or transaction activity; d) participation rights or economics contingent on execution-layer throughput; and e) internal incentives that pressure staff or programs to move opportunities toward closure in ways inconsistent with the Corporation’s bounded role.
A revenue model can quietly repurpose an institution even where its public language remains careful. If the Corporation is paid more when execution happens, the Corporation will face structural pressure to facilitate execution. That pressure is constitutionally incompatible with its public-benefit, non-executing posture. The Corporation may recover mission-consistent costs, receive grants, charge lawful fees for educational or technical services, and maintain sustainable operations. It may not tie its institutional economics to the success of downstream execution-bearing events.
22.7 No Hidden Economic Interest in Outcomes That Compromise Public-Good Neutrality
The Corporation shall not assume, conceal, or tolerate any hidden economic interest in downstream execution-bearing outcomes that would materially compromise its neutrality, independent judgment, public-benefit posture, or truthful role description. This includes direct and indirect economic stakes, contingent economic exposures, preferential upside arrangements, revenue participation, strategic value transfer, or economic dependencies that create incentives for the Corporation to favor execution, approval, selection, routing, or market uptake.
Such hidden interests may arise through:
a) contingent compensation or milestone payments linked to downstream outcomes; b) equity-like upside, token allocations, warrants, carried-interest analogues, or value-sharing arrangements; c) dependence on partner success where the Corporation’s judgment is expected to remain neutral; d) embedded sponsorship or support structures that reward the Corporation for participant conversion into execution-bearing relationships; and e) affiliated arrangements in which a separate actor captures economic benefit from outcomes materially shaped by the Corporation’s supposedly neutral role.
The Corporation shall not structure itself so that its public-benefit systems, evidence artifacts, or institutional credibility become economically entangled with downstream outcomes it is meant only to inform or support. Even where such arrangements might appear innovative, efficient, or financially attractive, they undermine the Corporation’s constitutional role and create intolerable risk of hidden bias, shadow execution, and public misunderstanding.
Any actual or contemplated arrangement creating a material economic incentive tied to downstream execution, market uptake, approval, or routeability shall be presumed prohibited absent clear demonstration to the contrary through formal review and recorded determination consistent with these Bylaws and applicable law.
22.8 Anti-Circumvention Rule for Proxy Structures
No proxy structure, affiliate arrangement, co-branded vehicle, service stack, contractual delegation, “independent” operator, special project shell, embedded team, or technical workaround shall be used to circumvent the prohibitions of this Section. If the Corporation’s economic, reputational, technical, or governance position would, in substance, make it the effective author, driver, or beneficiary of execution-bearing activity through another surface, the arrangement shall be treated as a prohibited proxy structure.
This anti-circumvention rule applies even where each individual contractual element appears facially lawful in isolation. The relevant question is the overall institutional effect: whether the Corporation remains a bounded public-good steward or has become a disguised participant in execution-bearing systems. If the latter, the arrangement shall not proceed.
22.9 Interpretive Rule for Regulatory and Execution Equivalence by Proxy
This Section shall be interpreted to prevent the Corporation from becoming an execution-bearing, approval-bearing, routing-bearing, or economically interested institution by proxy, indirection, delegation, interface design, or structural dependence. The Corporation may collaborate, support, educate, and steward public-good infrastructure. It may not cause, control, benefit from, or materially shape prohibited downstream functions while preserving only the appearance of distance.
Where ambiguity exists, the interpretation that better preserves:
a) non-execution in substance as well as form; b) independence from downstream economic incentives; c) truthful role separation; d) absence of proxy intermediation or shadow execution; and e) safer public-benefit neutrality
shall prevail unless a contrary result is required by law.
23. Independence and Neutrality Controls (GCRI United States)
23.1 Institutional Neutrality as a Condition of Legitimacy
Institutional neutrality shall be maintained as a condition of constitutional legitimacy for the Corporation. Neutrality in this context does not require moral indifference, false equivalence among claims, or the abandonment of scientific judgment, public-benefit purpose, or mission-driven seriousness. It requires that the Corporation exercise its functions without capture, favoritism, improper alignment, hidden sponsorship bias, partisan repurposing, market-serving distortion, or structural dependence that compromises its ability to act as a bounded public-benefit steward.
The legitimacy of the Corporation depends not only on what it produces, but also on the conditions under which it produces it. If the Corporation’s methods, evidence systems, observability structures, educational assets, partnerships, or public statements are materially shaped by loyalty to a firm, funder, state actor, political bloc, commercial ecosystem, vendor stack, ideological formation, or institutional faction, then even technically strong outputs may become constitutionally compromised. Neutrality is therefore not a communications posture alone. It is a governance, design, and operating requirement.
This principle requires the Corporation to preserve the practical ability to:
a) say no to funders, partners, hosts, and powerful users; b) correct material error even when correction is inconvenient; c) describe limitations and uncertainty honestly; d) refuse role expansion that serves external interests more than mission; and e) avoid becoming the instrument, amplifier, or legitimating surface of any actor whose interests exceed the Corporation’s public-benefit role.
Where neutrality is materially threatened, the Corporation shall treat the issue as a constitutional matter and not merely a reputational concern.
23.2 Neutrality From Firms, Vendors, States, Blocs, and Ideological Capture
The Corporation shall remain neutral, within the meaning of these Bylaws, from capture or practical domination by:
a) private firms and commercial operators; b) software, cloud, data, model, or tooling vendors; c) donors, sponsors, hosts, and strategic backers; d) governments, ministries, regulators, public agencies, or state-aligned blocs; e) trade groups, political coalitions, or influence networks; and f) ideological, partisan, or factional formations that would compromise the Corporation’s independent public-benefit posture.
Neutrality does not prohibit collaboration with such actors. It prohibits the Corporation from being materially subordinated to them in judgment, method, governance, language, sequencing, correction discipline, access design, or public description. The Corporation may work with firms without becoming vendor-led. It may work with public institutions without becoming quasi-governmental. It may work across viewpoints without becoming ideologically instrumentalized.
The Corporation shall be especially vigilant where neutrality risk arises through:
i) concentrated funding or sponsorship; ii) infrastructure or hosting dependence; iii) preferential access arrangements; iv) co-branding or public association that distorts perceived independence; v) embedded personnel, secondees, or advisors with dual loyalties; or vi) ecosystem narratives that pressure the Corporation to act as a validator, coordinator, or proxy for a particular bloc.
Any pattern that makes the Corporation more hesitant to contradict, correct, narrow, or refuse a particular actor than a similarly situated actor shall be treated as evidence of neutrality risk requiring review and remedy.
23.3 Prohibition on Structural Dependence That Distorts Institutional Judgment
The Corporation shall not permit structural dependence to arise or persist where such dependence materially distorts institutional judgment or creates practical barriers to independent action. Structural dependence may arise through funding, hosting, infrastructure, staffing, data access, legal support, communications support, identity association, distribution dependency, or other repeated forms of reliance that make the Corporation unable or unwilling to act consistently with mission and public-benefit integrity.
Structural dependence is prohibited where it materially impairs the Corporation’s ability to:
a) maintain independent methods or semantic controls; b) publish, correct, or withdraw outputs without external permission or fear of disproportionate consequence; c) refuse improper partner demands; d) change vendors, hosts, or support providers without existential disruption; e) preserve anti-enclosure and portability commitments; or f) govern its public-facing description truthfully rather than strategically for dependency reasons.
The Corporation shall not wait for dependency to become absolute before acting. Early indicators of structural dependence include, without limitation:
i) concentration of critical functions in one provider or supporter; ii) repeated informal accommodation of a dominant actor’s preferences; iii) absence of credible exit or continuity pathways; iv) reluctance to apply normal controls or correction discipline to powerful counterparties; and v) institutional narratives rationalizing why one actor “must not be upset.”
Where such conditions arise, the Corporation shall take proportionate measures including diversification, segmentation, contingency planning, contractual narrowing, governance reinforcement, documentation of residual risk, or exit planning, as appropriate.
23.4 Neutrality in Research, Publication, Consultation, and Convening
The Corporation shall preserve neutrality in all research, publication, consultation, convening, observability, educational, and technical stewardship functions. This requires that:
a) research questions and methods be defined by mission-consistent public-benefit logic rather than sponsor preference or ideological demand; b) publications reflect documented evidence, method, and correctionability rather than public-relations sensitivity; c) consultation participation remain bounded, truthful, and non-substituting; d) convenings be designed for lawful public-interest exchange rather than bloc formation, patronage, or institutional signaling on behalf of favored actors; and e) public-facing summaries and derivatives not be tuned to preserve alliances at the expense of meaning.
Neutrality in publication does not require the Corporation to avoid difficult or controversial truths. It requires the Corporation to reach and state such truths through institutionally disciplined methods rather than through factional alignment. Neutrality in consultation does not require silence in policy-relevant settings. It requires role-faithful contribution rather than ideological or partisan instrumentalization. Neutrality in convening does not require all participants to be treated as interchangeable. It requires that participation design, moderation, access, and outcomes not be manipulated to serve extra-constitutional loyalties.
The Corporation shall therefore maintain review and approval structures for sensitive publications, consultations, and convenings sufficient to identify whether neutrality is being preserved in substance and not merely in disclaimer.
23.5 Neutrality in Selection of Partners, Hosts, Experts, and Contributors
The Corporation shall select and work with partners, hosts, technical collaborators, experts, advisors, contributors, contractors, and comparable actors through processes that preserve neutrality, mission fit, documented rationale, and role-faithful independence. It shall not select or privilege such actors primarily because of donor pressure, institutional prestige, political alignment, commercial leverage, public signaling value, or ecosystem influence where those factors would compromise the Corporation’s public-benefit posture.
Selection processes shall be structured, to the degree appropriate to the matter, to ensure:
a) relevance to mission and lawful scope; b) competence and fitness for the relevant role; c) absence or management of material conflicts; d) no preferential treatment based solely on funding or strategic importance; e) consistency with anti-capture, anti-enclosure, and non-execution disciplines; and f) truthful public description of the relationship actually created.
Neutrality does not forbid strategic choice. It forbids strategic choice becoming covert patronage or political-commercial favoritism. The Corporation may prefer one actor over another where there is a mission-consistent, competence-based, safety-based, or legally required reason. It shall document that reason where material, and it shall not rely on ambiguity to conceal preferential treatment driven by non-public-benefit considerations.
23.6 Neutrality in Program Admission, Support, Visibility, and Institutional Attention
The Corporation shall preserve neutrality in the allocation of program admission, support, visibility, technical attention, educational support, observability focus, and public-facing institutional attention. It shall not create formal or informal systems in which support level, public visibility, or institutional seriousness is effectively purchased, politically mediated, or granted on the basis of prestige, donor influence, or ecosystem leverage rather than mission-based criteria.
Where the Corporation must choose among competing demands for institutional time, access, support, or visibility, it shall do so on the basis of criteria such as:
a) public-benefit relevance; b) mission fit; c) legal and safety constraints; d) evidentiary urgency or correction need; e) program readiness within the Corporation’s lawful role; f) resource availability and continuity considerations; and g) other criteria consistent with these Bylaws.
The Corporation shall not maintain “neutrality” in name while informally privileging those who are better funded, better connected, more politically valuable, or more difficult to say no to. If attention allocation patterns begin to reflect such dynamics, the Corporation shall treat the matter as a neutrality-control issue requiring correction.
23.7 Recorded Exceptions Only Where Lawfully Necessary and Public-Benefit Justified
Any departure from ordinary neutrality-preserving practice shall be permitted only where it is:
a) lawfully necessary; b) mission-consistent; c) public-benefit justified; d) narrowly tailored; and e) properly recorded.
Such departures might include, by way of example and without limitation, emergency continuity arrangements, legally mandated dependencies, temporary concentration of functions pending migration, or targeted support structures justified by specific public-interest needs and not by favoritism. Even in such cases, the Corporation shall not rely on informal exception-making. Any material exception to ordinary neutrality controls shall be documented with sufficient specificity to show:
i) the reason for the exception; ii) its scope and duration; iii) the risks it creates; iv) the safeguards that remain in place; and v) the exit or review conditions by which the exception will be revisited.
No exception shall be allowed to harden into permanent structural bias through repetition, convenience, or silence. Exceptions that are not recorded shall have no legitimating force and shall be treated as control failures.
23.8 Neutrality Review, Escalation, and Corrective Duty
The Corporation shall maintain a standing duty to review, detect, escalate, and correct neutrality threats. Neutrality review may arise in connection with:
a) concentrated funding or sponsorship; b) controversial publications or consultation responses; c) partner or host selection; d) event and convening design; e) platform and repository dependencies; f) public-facing descriptions and co-branding; or g) repeated patterns of preferential treatment, silence, or accommodation.
Where a material neutrality threat is identified, the Corporation shall take proportionate action, which may include:
i) clarification of scope or public description; ii) recusal or conflict management; iii) segmentation of roles or access; iv) redesign of selection or prioritization processes; v) diversification of funding, hosting, or infrastructure; vi) narrowing, suspension, or termination of the relevant arrangement; or vii) escalation to legal, integrity, compliance, or Board review.
Neutrality is not preserved by aspiration alone. It is preserved through repeated acts of detection, refusal, correction, and design discipline. The Board and officers shall ensure that neutrality controls are real in operation and not merely stated in principle.
23.9 Interpretive Rule for Independence and Neutrality Controls
This Section shall be interpreted to preserve the Corporation as an independent, neutral, non-captured, public-benefit institution capable of serious collaboration without subordination, public-interest contribution without factionalization, and technical stewardship without capture by the actors most dependent on or influential within its ecosystem.
Where ambiguity exists, the interpretation that better preserves:
a) independence of judgment; b) absence of structural dependence; c) fairness and mission-based selection; d) non-capture by firms, funders, states, or ideological blocs; and e) truthful, bounded institutional posture
shall prevail unless a contrary result is required by law.
24. Assurance-versus-Execution Separation (GCRI United States)
24.1 Assurance, Evidence, and Method Outputs as Non-Executing Artifacts
All assurance-supporting, evidence-bearing, scientific-operational, observability, semantic, methodological, educational, and governance-supporting outputs of the Corporation shall be treated as non-executing artifacts. Their purpose is to improve the quality, intelligibility, reviewability, traceability, correctionability, and lawful bounded usability of upstream material within the Corporation’s exempt purposes and public-benefit role. They are not, and shall not be described, structured, or used as, execution-bearing acts.
For purposes of this Section, “assurance” includes any structured activity by which the Corporation organizes, qualifies, tests, documents, interprets, compares, or explains evidence, methods, observability states, technical components, semantic structures, or related public-good assets so that lawful recipients may understand them more seriously. “Assurance” in this institutional sense does not mean guarantee, indemnity, insurance, certification with public-law effect, or assumption of downstream legal responsibility. It means disciplined upstream strengthening of understanding and bounded institutional usability.
Accordingly, the Corporation’s outputs may be serious, well-documented, technically mature, and relied upon as inputs by other actors. None of those characteristics shall alter their non-executing nature. The Corporation shall preserve this principle in document headers, system labels, workflow states, training materials, metadata, public description, partner communications, and all other surfaces through which meaning may travel. No assurance-bearing artifact shall be allowed to migrate in public meaning from “structured upstream support” to “permission to act,” “authority to proceed,” or “binding condition satisfied.”
The Corporation may help others see more clearly. It may not thereby act for them.
24.2 No Conversion of Assurance Into Operational Authorization
The Corporation shall not convert assurance, evidence quality, methodological rigor, observability depth, technical validation, structured review, or related upstream discipline into operational authorization. No output of the Corporation shall be drafted, positioned, sequenced, surfaced, or relied upon in a way that makes it the practical equivalent of clearance, permission, greenlight, approval, readiness authorization, routeability authorization, or execution consent.
This prohibition applies whether the attempted conversion is explicit or implicit. It includes, without limitation:
a) using assurance artifacts as if they were go/no-go approvals; b) structuring workflows so that a Corporation-issued assurance state becomes a required gate for downstream action; c) issuing status labels or badges that reasonably imply permission to operate, deploy, transact, route, issue, settle, or otherwise proceed; d) allowing third parties to market a Corporation assurance output as though it were a formal authorization; and e) tolerating internal shorthand in which “assured,” “reviewed,” “validated,” or similar terms are understood to mean “approved” or “ready to execute.”
The Corporation may describe what an assurance artifact does support: structured understanding, bounded reliance, documented method, traceable evidence, stated limitations, and disciplined review. It shall also describe what it does not support: formal authorization, sovereign act, supervisory effect, market permission, or execution entitlement. Where counterparties, partners, or internal teams begin treating assurance as authorization, the Corporation shall intervene promptly through clarification, redesign, or withdrawal as appropriate.
No level of technical rigor cures lack of authority. No degree of assurance creates power the Corporation does not lawfully possess.
24.3 No Conversion of Technical Seriousness Into Commercial Mandate
The Corporation shall not allow technical seriousness, evidence quality, platform sophistication, semantic coherence, observability depth, or institutional credibility to be converted into a commercial mandate. The fact that the Corporation’s outputs or systems are respected, interoperable, technically robust, or widely useful does not authorize their use as market-entry signals, procurement shortcuts, vendor preference tools, distribution advantages, or substitute commercial credentials.
This prohibition includes, without limitation:
a) using Corporation technical outputs as sales-enablement tools implying privileged commercial standing; b) presenting structured review by the Corporation as if it confers market trust or commercial preference; c) converting Corporation support for a public-good artifact into a private claim of product superiority, institutional preferred status, or procurement advantage; d) designing technical pathways that make association with the Corporation function as a route-to-market benefit; and e) allowing donors, sponsors, vendors, or collaborators to represent the Corporation’s technical seriousness as if it were a commercial endorsement or mandate.
The Corporation may produce technical artifacts that commercial actors lawfully find useful. It may not allow its role as steward of public-benefit infrastructure to become an upstream commercial certification or market acceleration surface. Any private benefit arising from public-good technical seriousness must remain incidental, bounded, and subordinate to public benefit. Once the practical effect becomes commercial mandate, the boundary has been crossed.
The Corporation shall therefore review not only the content of its outputs, but their market-facing uses, foreseeable misuses, and institutional signaling effects in real ecosystems.
24.4 No Execution Inference From Evidence Quality, Observability Depth, or Platform Sophistication
No person may infer, and the Corporation shall not imply, that high evidence quality, deep observability, strong documentation, technical maturity, rigorous benchmarking, or sophisticated platform design creates execution authority, approval effect, operational permission, readiness determination, market-legibility status, or legal standing. The Corporation’s seriousness shall not be allowed to distort the constitutional meaning of its role.
This rule is necessary because sophisticated outputs are often overread. A well-structured observability environment may appear to some users like an authoritative command surface. A carefully documented evidence pack may look like a clearance package. A stable technical platform may be treated as if it carries operational authority merely because others trust it. None of those inferences is permitted absent explicit lawful basis, which shall not be presumed.
The Corporation shall therefore avoid:
a) interface designs that visually or operationally mimic approval systems; b) maturity language that implies operational authorization; c) technical status states that can be mistaken for downstream permissions; d) documentation structures that obscure where independent lawful judgment remains necessary; and e) public descriptions that blur the distinction between upstream rigor and downstream authority.
The Corporation may strengthen the conditions for serious action by others. It shall not be understood as making that action lawful, approved, executable, or institutionally cleared. Better evidence is not a license. Better observability is not a mandate. Better infrastructure is not authority.
24.5 Clear Handoff Requirement at All Boundaries to Recognition, Adoption, or Execution Layers
Where an assurance-bearing, evidence-bearing, technical, or educational artifact produced by the Corporation is intended or foreseeably likely to move toward another institutional layer—whether recognition, adoption, routeability, implementation, regulation, procurement, finance, or execution—the Corporation shall maintain a clear handoff discipline. That handoff shall make explicit that responsibility, authority, and consequence move out of the Corporation’s perimeter and into the lawful remit of another actor, if at all.
A proper handoff shall, to the extent appropriate for the matter, preserve clarity regarding:
a) what the Corporation has done and what it has not done; b) the scope, assumptions, limitations, and correction status of the artifact being handed off; c) the identity of the next institution or actor responsible for its own judgment; d) the fact that no Corporation output cures absence of legal, regulatory, fiduciary, operational, or sovereign authority elsewhere; and e) where residual responsibility remains after the handoff.
The Corporation shall not tolerate “sticky” handoffs in which its outputs continue to be treated as ongoing approvals, implicit oversight mechanisms, or embedded execution permissions after the next layer is supposed to take responsibility. Nor shall it permit ambiguous handoffs that allow later actors to claim they were merely “following GCRI.” Handoff is a constitutional boundary, not just a process step.
Where no clear handoff can be established without blurring roles or public meaning, the matter shall be re-scoped, re-documented, or held.
24.6 No Claim That Assurance Cures Lack of Legal, Regulatory, or Operational Authority
The Corporation shall not claim, imply, or permit others reasonably to believe that assurance, evidence quality, review discipline, technical validation, structured observability, semantic coherence, or any other feature of a Corporation output can cure the absence of legal, regulatory, operational, fiduciary, or sovereign authority in the hands of a recipient, partner, or downstream actor. Authority deficits are not repaired by technical seriousness alone.
This prohibition applies where others attempt to use Corporation outputs to suggest that:
a) a legally unauthorized actor may proceed because the evidence is strong; b) a regulatory gap is neutralized by better documentation; c) a transaction becomes acceptable because the observability substrate is mature; d) a governance gap is cured by semantic precision or testing discipline; or e) a lack of operational competence is solved merely because an artifact is decision-grade.
The Corporation may make plain that strong upstream structures can improve decision quality, reduce uncertainty, support comparability, and help lawful actors discharge their own duties more seriously. It may not imply that upstream seriousness substitutes for the lawful existence of authority, mandate, license, capacity, or jurisdiction. Recipients remain responsible for satisfying their own legal and operational preconditions.
No amount of assurance transforms a non-authority into an authority.
24.7 Visibility of Residual Responsibility After Handoff
After any handoff from the Corporation’s perimeter to another actor, institution, or process, the residual responsibility structure shall remain visible. The Corporation shall not structure documents, systems, or public descriptions in ways that obscure who remains responsible for what. Residual responsibility includes, without limitation:
a) the recipient’s duty to apply independent judgment; b) the continued relevance of assumptions, limitations, and conditions attached to the Corporation’s artifact; c) the possibility of correction, supersession, or changed conditions affecting the artifact’s meaning; d) the responsibility of downstream actors to secure their own permissions, licenses, approvals, or legal bases; and e) the fact that the Corporation has not assumed continuing supervisory, execution, fiduciary, or sovereign responsibility by virtue of providing upstream support.
Visibility of residual responsibility is necessary to prevent “authority evaporation,” where no one clearly owns the consequence-bearing decision because each actor points to another. The Corporation shall not allow its role to be used as a shield against accountability by downstream actors, nor shall it allow downstream actors to imply that the Corporation remains responsible for execution outcomes simply because they used a Corporation artifact.
Where a residual responsibility map is materially important to lawful interpretation, it shall be documented in appropriate form and maintained as part of the record.
24.8 Interpretive Rule for Assurance-versus-Execution Separation
This Section shall be interpreted to preserve a strict and intelligible line between assurance-like upstream seriousness and execution-like downstream consequence. The Corporation may strengthen evidence, methods, observability, semantic coherence, education, and public-good infrastructure. It may not permit that strengthening to be reinterpreted as authority, approval, market mandate, sovereign effect, or execution control.
Where ambiguity exists, the interpretation that better preserves:
a) non-executing meaning of assurance outputs; b) clear handoff to other lawfully responsible actors; c) visibility of residual responsibility; d) absence of commercial, regulatory, or sovereign overread; and e) faithful role separation across the wider architecture
shall prevail unless a contrary result is required by law.
25. Research Independence and Sponsor Interference Ban (GCRI United States)
25.1 Research Independence as a Constitutional Requirement
Research independence shall be a constitutional requirement of the Corporation and not merely a professional aspiration. Because GCRI US is constituted as a public-benefit, scientific, educational, and non-executing institution, the independence of its research, methods, observability logic, interpretive frameworks, technical assessments, educational materials, and related mission-bearing outputs is integral to its legal legitimacy, tax-exempt posture, institutional neutrality, and public trust. The Corporation shall not permit its research function to be subordinated to donor interest, sponsor preference, political pressure, market convenience, reputational caution, or partner strategy.
Research independence requires that the Corporation retain real and practical control over:
a) research questions and methodological design, subject to lawful project scoping; b) data treatment, evidentiary interpretation, and analytical framing; c) the documentation of assumptions, uncertainty, limitations, and dissent; d) the right to correct, supersede, narrow, delay, withdraw, or publish outputs according to mission-consistent and methodologically justified rules; and e) the truthful public description of what the research does and does not establish.
This principle applies across all forms of mission-bearing inquiry, including formal research projects, technical studies, validation work, benchmarking, observability analysis, training content, public-interest white papers, consultation responses, implementation notes, and other structured knowledge products. The Corporation shall not treat “research independence” as limited to academic publications only. If an output carries substantive analytical or evidentiary meaning within the Corporation’s remit, independence requirements attach to it.
Where a proposed arrangement, funding structure, partnership, publication process, or governance instruction would materially compromise research independence, that compromise shall be treated as a constitutional defect rather than a manageable inconvenience.
25.2 Prohibition on Sponsor Review Rights Over Findings Beyond Defined Process
The Corporation shall not grant any donor, sponsor, host, strategic backer, partner, vendor, collaborator, or other external actor review rights over findings, conclusions, classifications, interpretive judgments, or substantive outputs beyond a narrowly defined, mission-consistent, and properly documented process that preserves the Corporation’s final and independent judgment. Any permitted review right shall be strictly limited in scope and shall not become a mechanism for substantive control.
A lawful and bounded review process may, where appropriate, allow for:
a) factual accuracy checks relating to information provided by the reviewing party; b) identification of inadvertent disclosure of protected or confidential information where the Corporation has lawfully agreed to such protection; c) comments on whether the party has been described accurately in a purely factual sense; and d) timing coordination narrowly necessary for handling, safety, legal privilege, or security reasons.
No external review right shall include, explicitly or in practice:
i) veto power over conclusions, methods, interpretations, rankings, or classifications; ii) authority to require favorable framing or the suppression of unfavorable analysis; iii) the right to delete or rewrite substantive passages for reputational convenience; iv) the right to block publication because the output is politically, commercially, or institutionally inconvenient; or v) the practical ability to delay publication indefinitely through non-response, repeated review cycles, or procedural obstruction.
The Corporation shall document all sponsor or partner review rights in writing and interpret them narrowly. Informal review expectations shall have no legitimating force. If a party attempts to convert a narrow review process into substantive control, the Corporation shall escalate the matter and may suspend or terminate the arrangement.
25.3 Prohibition on Donor or Sponsor Veto Over Publication, Correction, or Withdrawal
No donor, sponsor, strategic backer, host, partner, or other external actor shall possess or exercise a veto over publication, correction, supersession, narrowing, retraction, or withdrawal of Corporation outputs. The Corporation shall retain final authority to determine, through lawful internal governance and mission-consistent process, when and how an output is published, corrected, replaced, clarified, or withdrawn.
This prohibition is necessary because the Corporation’s public-benefit legitimacy depends on its ability to preserve truthfulness and correctionability even when that is inconvenient to powerful supporters or counterparties. A support relationship that conditions continued funding or participation on silence, delay, or refusal to correct is incompatible with these Bylaws.
Accordingly, the Corporation shall not accept or tolerate any arrangement under which an external actor may:
a) prevent publication of a completed mission-bearing output for substantive reasons; b) prevent correction of a misleading or erroneous output; c) require continued circulation of a superseded or materially defective artifact; d) block narrowing or clarification necessary to preserve truthful public meaning; or e) use financial, reputational, contractual, or infrastructural leverage to achieve the same practical effect as a veto.
The Corporation may, where lawfully necessary, sequence publication to protect safety, privilege, privacy, lawful confidentiality, or similar interests. Such sequencing shall not become sponsor-controlled suppression. Where a conflict arises, the Board or its properly authorized delegate shall act to preserve institutional integrity rather than supporter convenience.
25.4 Independence of Methods, Datasets, Models, and Interpretive Conclusions
The Corporation shall preserve the independence of its methods, datasets, model-governance choices, evaluation logic, semantic structures, and interpretive conclusions. External actors may contribute data, domain expertise, technical comments, mission-consistent funding, or contextual information, but they shall not control the Corporation’s ultimate judgment concerning what methods are used, how evidence is treated, what assumptions are disclosed, what limitations are acknowledged, what uncertainties are noted, or what conclusions are supportable.
This independence requirement means, among other things, that the Corporation shall not:
a) adopt methods because a sponsor prefers the result they are likely to produce rather than because the methods are mission-consistent and analytically justified; b) suppress or omit datasets or observations because they are inconvenient to a supporter; c) allow model selection, weighting, benchmarking conditions, scenario framing, or semantic classification to be set for external political or commercial reasons; d) maintain hidden or undocumented methodological accommodations for favored actors; or e) tailor interpretive conclusions to preserve institutional harmony at the expense of accuracy.
The Corporation may select lawful and mission-consistent methods in dialogue with partners and contributors, particularly where a project requires technical collaboration. That dialogue shall remain consultative unless these Bylaws or another lawful instrument expressly provide otherwise. Final methodological and interpretive responsibility remains with the Corporation acting through its authorized structures.
Where a partner-provided dataset, tool, model component, or technical dependency creates practical pressure to compromise this independence, the Corporation shall document that risk and take appropriate measures, which may include segmentation, alternative sourcing, limiting language, reduced reliance, or withdrawal.
25.5 Firewall Between Funding Discussions and Scientific Judgment
The Corporation shall maintain a functional and governance firewall between funding discussions and scientific judgment. Persons responsible for fundraising, donor relations, sponsorship development, strategic backer engagement, or resource mobilization shall not control, override, or distort the substantive conduct of research, evidence interpretation, observability analysis, or mission-bearing technical conclusions. Likewise, substantive teams shall not be pressured to conform outputs to fundraising needs, donor sensitivities, or relationship-management objectives.
This firewall may be implemented through such measures as are appropriate to the Corporation’s size and operating model, including:
a) separation of roles and responsibilities; b) conflict-of-interest disclosure and management; c) documented authority limits for fundraising and external-relations personnel; d) review pathways for sensitive projects where funding and substance are closely proximate; e) independent sign-off or escalation procedures for outputs that may affect supporter relationships; and f) Board oversight where concentration of funding materially increases pressure on scientific or technical functions.
The purpose of this firewall is not hostility to fundraising. It is recognition that financial dependence can distort substance unless structurally contained. Mission-consistent fundraising is lawful and necessary. Scientific or evidentiary compromise in service of fundraising is not. The Corporation shall prefer slower funding over contaminated judgment.
25.6 Disclosure and Escalation of Sponsor Interference Attempts
Any attempt by a donor, sponsor, host, partner, strategic backer, service provider, or other external actor to improperly influence methods, findings, publication timing, correction, language, review conditions, visibility, or substantive conclusions shall be treated as a sponsor interference event. Such attempts shall be disclosed internally through appropriate channels and escalated to legal, integrity, compliance, executive, or Board review as warranted by seriousness.
Sponsor interference may include, without limitation:
a) direct pressure to change conclusions; b) threats to withdraw funding unless outputs are softened, delayed, or narrowed; c) attempts to obtain informal veto rights outside documented process; d) efforts to control terminology, classification, or semantic treatment for reputational reasons; e) pressure to remove critical context, uncertainty, or limitations; and f) attempts to retaliate against personnel for independent analysis or correction.
The Corporation shall foster an internal culture in which good-faith reporting of such interference is protected and encouraged. No person shall be penalized for escalating a credible interference concern. The existence of sponsor interference risk shall not be concealed in order to preserve funding relationships, institutional calm, or public appearance.
Where material interference has occurred or been attempted, the Corporation shall determine whether additional steps are required, including documentation of the incident, adjustment of the funding relationship, public clarification, or removal of the affected party from the relevant workstream or relationship.
25.7 Remedies, Refusals, Funding Returns, and Public Clarifications Where Necessary
Where sponsor interference, compromised independence, or incompatible funding conditions are identified, the Corporation shall take proportionate and mission-faithful remedial action. Such action may include:
a) refusal of the proposed condition or demand; b) narrowing or redesign of the supported activity; c) segregation of roles, data, or review processes; d) correction or republication of affected outputs; e) suspension or termination of the relevant agreement or relationship; f) return of funds where required or prudent; g) withdrawal from the engagement; and h) public clarification or correction where continued misunderstanding would materially impair public-benefit integrity.
The Corporation shall not treat continuation of funding as a value that automatically outweighs independence. In some cases, the only constitutionally faithful response to sponsor interference will be refusal, exit, or return of support. That possibility shall be accepted as part of operating a genuine public-benefit institution.
Where public clarification becomes necessary, the Corporation shall act with care, proportionality, and legal prudence, but it shall not suppress truth solely to preserve supporter convenience. If the public record would otherwise remain materially misleading regarding the independence or integrity of Corporation outputs, the Corporation shall favor truthful clarification over strategic silence.
25.8 Independence of Educational and Training Content
The independence obligations of this Section apply not only to formal research, but also to educational, training, academy, simulation, competency, and public-interest instructional content. The Corporation shall not allow supporters, hosts, vendors, or strategic partners to determine educational conclusions, materially distort curricula, suppress limitations, or frame instructional outputs in ways that convert public-interest education into marketing, political messaging, or institutional propaganda.
Educational content may properly reflect mission-consistent choices about scope, audience, handling class, and pedagogical style. It shall not be shaped so as to imply preferred vendors, preferred platforms, favored institutions, or sponsor-sanctioned doctrines absent a lawful, truthfully described, and mission-consistent basis. Training materials are mission-bearing outputs and shall therefore remain subject to the same independence disciplines as research outputs.
25.9 Interpretive Rule for Research Independence and Sponsor Interference
This Section shall be interpreted to preserve the Corporation’s ability to produce independent, correctionable, methodologically serious, and publicly legitimate research and knowledge outputs without sponsor control, donor veto, financial contamination, or hidden narrative management. Where ambiguity exists, the interpretation that better preserves:
a) independence of judgment; b) absence of sponsor-shaped substance; c) correctionability and publication integrity; d) separation between funding and findings; and e) truthful public-benefit stewardship of knowledge
shall prevail unless a contrary result is required by law.
26. Conflict-of-Law and Cross-Border Compliance Boundary (GCRI United States)
26.1 U.S. Law as the Internal Governance Anchor
The Corporation shall be governed internally by the law applicable to its state of incorporation, applicable federal law, and all other domestic legal obligations binding upon it as a U.S. nonprofit institution, including those arising from its intended and maintained status under Section 501(c)(3) of the Internal Revenue Code. For purposes of internal governance, authority allocation, fiduciary standards, document control, Board process, officer duties, records validity, institutional interpretation, and the constitutional meaning of these Bylaws, U.S. law shall constitute the Corporation’s primary legal anchor.
This anchor is not merely formal. It determines the baseline against which all cross-border, inter-jurisdictional, or internationally interfacing conduct must be measured. The Corporation may operate in intellectually global, technically interoperable, and cross-border public-interest environments. It does so as a U.S. legal person with U.S.-anchored obligations, constraints, and fiduciary duties. Nothing in the broader architecture, no international collaboration, and no aligned semantic or institutional framework shall displace the primacy of U.S. law for internal corporate acts unless such displacement is expressly required by superior law, which shall not be presumed.
Accordingly:
a) no foreign or extra-jurisdictional practice shall be imported into the Corporation’s internal order merely because it is common elsewhere; b) no cross-border alignment shall be interpreted to reduce the Board’s fiduciary responsibilities under U.S. law; c) no international public-interest objective shall excuse noncompliance with domestic nonprofit, tax, sanctions, export-control, privacy, labor, or other applicable legal requirements; and d) no ambiguity in a cross-border situation shall be resolved by reference to convenience or ecosystem expectation where U.S. legal duties point otherwise.
The Corporation shall preserve this domestic anchor while remaining capable of lawful and carefully bounded external engagement.
26.2 No Extraterritorial Override of Mandatory Local Law
The Corporation shall not assert, imply, or behave as though its own frameworks, systems, methods, semantic structures, institutional preferences, or aligned cross-border doctrines override the mandatory local law of any jurisdiction in which it operates, convenes, publishes, partners, hosts systems, receives data, engages counterparties, or otherwise has meaningful contact. Cross-border coherence does not create legal supremacy. Institutional interoperability does not displace local law. Shared architecture is not a source of extraterritorial power.
Where the Corporation engages with jurisdictions outside the United States, it shall respect that:
a) local public law, private law, and mandatory compliance requirements may govern conduct, data handling, publishing, hosting, distribution, contracting, staffing, or technical deployment; b) counterparties in other jurisdictions may be subject to duties and restrictions different from those applicable in the United States; c) permissions, prohibitions, and legal meanings may vary materially across jurisdictions; and d) a U.S.-based institutional understanding of a workflow, artifact, or role may not travel unchanged into another legal environment.
The Corporation shall therefore not require foreign counterparties, hosts, partners, or aligned institutions to act contrary to their own mandatory legal obligations on the theory that a common architecture, public-benefit purpose, or technical standard should prevail. Nor shall it misdescribe cross-border compatibility as if it constituted legal authorization in other jurisdictions. Cross-border alignment must remain law-aware and role-aware.
26.3 Duty to Route Conflict-of-Law Questions Into Formal Review
Whenever a material issue arises concerning the possible interaction, inconsistency, incompatibility, or unresolved tension between U.S. law and the law of another jurisdiction, the Corporation shall route the matter into formal legal and governance review before proceeding with the relevant action, output, system feature, relationship, or public representation. Conflict-of-law issues shall not be resolved informally through operational improvisation, counterpart comfort, or assumptions that “everyone does it this way.”
A conflict-of-law question shall be treated as material where, among other things, it may affect:
a) the legality of a contemplated act; b) the lawful handling, transfer, hosting, or publication of data or evidence; c) the characterization of an output or institutional role; d) the enforceability or risk profile of a contract or partnership; e) export controls, sanctions, restricted-party concerns, or technology-transfer limitations; f) privacy, labor, tax, intellectual-property, or records obligations; g) the ability of the Corporation truthfully to describe what its systems or outputs mean; or h) the preservation of non-execution, public-benefit, or neutrality disciplines in another jurisdictional context.
Formal review shall be proportionate to the seriousness of the matter but shall be sufficient to ensure that the Corporation is not operating on unsupported assumptions. Where necessary, external counsel competent in the relevant jurisdiction or subject matter shall be engaged. Operational timelines shall not override the duty to review. If the matter cannot be resolved with sufficient confidence, the Corporation shall narrow, defer, compartmentalize, redesign, or decline the relevant activity.
26.4 Cross-Border Activities Subject to Sanctions, Export-Control, Privacy, Data, and Related Legal Regimes
All cross-border activities of the Corporation shall be conducted subject to all applicable legal regimes bearing on such activity, including, as relevant, sanctions, export controls, trade restrictions, anti-boycott requirements, privacy law, data protection law, cybersecurity law, records law, labor law, tax law, customs rules, and other mandatory cross-border legal controls. The Corporation shall not assume that scientific, educational, nonprofit, or public-benefit framing exempts it from these requirements.
This principle applies to, without limitation:
a) cross-border data collection, transfer, storage, hosting, access, or replication; b) provision or receipt of technical services, code, models, infrastructure, or observability tooling; c) collaboration with foreign persons, entities, or institutions; d) licensing, publication, or release of mission-bearing technical materials; e) travel, training, and convening involving restricted jurisdictions or persons; f) payments, reimbursements, grants, in-kind support, or procurement relationships; and g) any digital access arrangement that may constitute export, reexport, transfer, or facilitation under applicable law.
The Corporation shall maintain sufficient controls to prevent inadvertent violation of such legal regimes. Those controls may include screening, classification, access restrictions, geo-sensitive architecture choices, contractual terms, distribution limits, internal guidance, and formal review mechanisms. The absence of malicious intent shall not excuse unlawful cross-border conduct. Where the legal status of an activity is uncertain, the safer and more restrictive path shall prevail unless and until lawful clearance is obtained.
26.5 Localization Without Constitutional Fracture
Where cross-border engagement, interoperability, or cooperation requires adaptation to local legal or institutional conditions, the Corporation may localize its systems, practices, outputs, access conditions, or implementation structures, provided that such localization does not produce constitutional fracture—that is, does not silently dissolve the mission lock, non-execution posture, public-benefit identity, correctionability discipline, semantic integrity, or anti-capture architecture established by these Bylaws.
Localization may properly include:
a) adjustment of handling rules, access conditions, or publication classes to local law; b) jurisdiction-specific privacy, data, labor, or records controls; c) localized implementation patterns, overlays, or interface notes; d) divergence logs and compatibility notes where necessary; and e) technical segmentation or hosting choices tailored to lawful local operation.
Localization shall not be used as a pretext for:
i) assuming local sovereign or regulatory roles not lawfully held; ii) abandoning correctionability or records discipline; iii) creating undocumented semantic divergence; iv) permitting shadow execution in another jurisdiction; or v) representing jurisdiction-specific adaptations as globally canonical without appropriate process.
The Corporation shall prefer lawful adaptation with traceable divergence over informal practice drift. Cross-border flexibility is permissible only where constitutional continuity is preserved.
26.6 Controlled Participation Where Jurisdictional Risk Cannot Be Resolved
Where jurisdictional risk, legal uncertainty, sanctions risk, data-transfer uncertainty, export-control uncertainty, or comparable cross-border compliance concerns cannot be resolved to a level consistent with prudent nonprofit governance, the Corporation shall limit the relevant activity to controlled participation or decline it altogether. Controlled participation may include narrow observation, non-operational attendance, high-level educational contribution, segmented access, restricted publication, sandboxed analysis, or other bounded involvement that preserves legality and institutional safety.
This rule means that the Corporation is not required to choose only between full engagement and full withdrawal. It may, where lawful and prudent, reduce the scope of participation to remain within manageable risk bounds. Such narrowing may involve:
a) excluding certain jurisdictions, persons, or categories of data; b) limiting outputs to public-safe educational or conceptual material; c) prohibiting technical transfer or system access; d) avoiding institutional commitments that imply broader legal permission; or e) requiring specific conditions precedent before deeper engagement.
However, controlled participation shall not become a rhetorical device for proceeding with effectively full engagement while disclaiming responsibility. If risk remains material in substance, the narrowing must be real in substance. Where even controlled participation cannot be lawfully or prudently structured, the Corporation shall decline the matter.
26.7 Divergence Recording, Equivalence Notes, and Compatibility Controls
Where cross-border legal realities, local constraints, or jurisdiction-specific implementation choices require the Corporation to structure activities, systems, outputs, access rules, or interpretations differently than it otherwise would under a purely domestic or common-architecture reading, the Corporation shall maintain divergence records, equivalence notes, compatibility controls, or similar documentation sufficient to preserve intelligibility, legal traceability, and constitutional coherence.
Such documentation shall, where appropriate, identify:
a) the jurisdictional factor driving the divergence; b) the nature of the adaptation or restriction; c) whether the divergence is temporary, permanent, or conditional; d) the effect of the divergence on interoperability, portability, or public meaning; and e) any review or sunset conditions applicable to the divergence.
This discipline is necessary because undocumented divergence in cross-border settings can produce silent role drift, semantic fracture, false claims of equivalence, and misdescription of what the Corporation is actually doing. The Corporation shall therefore treat legal and jurisdictional divergence as a matter of governance record, not merely as operational improvisation.
Compatibility controls may include metadata, notices, repository segmentation, release notes, technical flags, or governance annotations, provided they are sufficient to prevent foreseeable confusion regarding what is common, what is localized, and what legal or institutional consequence follows.
26.8 Cross-Border Representation, Public Description, and Scope Discipline
In all cross-border or internationally visible contexts, the Corporation shall describe its role, capabilities, relationships, outputs, jurisdictional posture, and legal significance truthfully and with sufficient scope discipline to prevent the impression that the Corporation possesses general transnational authority, cross-border regulatory effect, treaty-like standing, or jurisdiction-neutral operational permission. Public statements about international or cross-border engagement shall distinguish clearly among:
a) legal authority; b) technical interoperability; c) conceptual or semantic alignment; d) public-interest cooperation; and e) actual operational or legal permission in a given jurisdiction.
The Corporation shall not allow the fact of global or international relevance to inflate the legal meaning of its role. It may work internationally. It remains a U.S. nonprofit institution with bounded authority. Any public communication suggesting otherwise shall be treated as a claims-discipline and perimeter issue.
26.9 Interpretive Rule for Conflict-of-Law and Cross-Border Compliance Boundary
This Section shall be interpreted to preserve the Corporation as a U.S.-anchored, law-compliant, non-executing, public-benefit institution capable of lawful cross-border engagement without legal overreach, hidden authority inflation, or constitutional fracture. Where ambiguity exists, the interpretation that better preserves:
a) compliance with U.S. law and other applicable law; b) narrower implied authority across jurisdictions; c) lawful localization rather than silent divergence; d) safer controls in the face of unresolved jurisdictional risk; and e) truthful cross-border public meaning
shall prevail unless a contrary result is required by law.
27. Perimeter Drift Prevention (GCRI United States)
27.1 Definition of Perimeter Drift
For purposes of these Bylaws, Perimeter Drift means any gradual, episodic, cumulative, or structurally embedded movement by which the Corporation’s activities, outputs, systems, public descriptions, revenue models, governance patterns, partnerships, technical architectures, or institutional expectations begin to exceed, blur, weaken, or practically circumvent the non-execution boundary, public-benefit identity, exempt-purpose discipline, neutrality controls, or other constitutional limits established in Part I and Part II. Perimeter Drift may occur without formal decision, without malicious intent, and without any single obvious breach. Its danger lies precisely in its ability to normalize boundary erosion over time.
Perimeter Drift may arise through:
a) repeated exceptions framed as temporary; b) accumulation of ambiguous outputs or partner practices; c) design choices that shift the practical effect of systems or artifacts; d) donor, sponsor, host, or ecosystem pressure; e) linguistic inflation or public shorthand that outpaces actual authority; f) technical centrality that quietly becomes operational control; or g) institutional fatigue with maintaining explicit boundary discipline.
A matter may constitute Perimeter Drift even where no one intended to change the Corporation’s constitutional role. The question is not whether drift was deliberate, but whether the Corporation’s real operating position, public meaning, or legal risk profile has moved materially toward execution, approval, market-facing intermediation, sovereign substitution, or capture. The Corporation shall therefore treat drift as a structural governance risk and not merely as a communications or compliance issue.
Perimeter Drift shall be understood as distinct from lawful evolution, controlled expansion of capacity within mission, or responsible localization. Growth consistent with these Bylaws is permissible. Drift is not. The line between the two shall be assessed by reference to constitutional fidelity, practical effect, and whether the Corporation remains recognizably the institution these Bylaws establish.
27.2 Drift Through Growth, Crisis Conditions, or Technical Success
The Corporation shall guard against Perimeter Drift arising from growth, emergency conditions, or technical success. Institutions that become useful, visible, and operationally central are often pressured to take on adjacent roles in the name of efficiency, urgency, or public need. Such pressure is especially acute where the Corporation’s evidence systems, observability environments, semantic controls, technical assets, or public-benefit legitimacy make it appear well positioned to “just do a little more.” These pressures do not amend the Bylaws.
Growth-related drift may include:
a) expanding from support into de facto approval or routing; b) allowing internal staff or partners to treat success in one domain as justification for authority in another; c) increasing operational reach without equivalent strengthening of boundary controls; d) presenting scale, adoption, or technical maturity as if they license broader institutional effect; or e) accepting new classes of work because the Corporation is “already doing something similar,” when the similarity is superficial and the legal or constitutional meaning is not.
Crisis-related drift may include:
i) emergency workarounds that become normalized; ii) assertions of exceptional necessity to bypass ordinary review; iii) compressed workflows that remove clear handoffs or residual responsibility visibility; iv) tolerance of ambiguous roles because “someone must act”; or v) public messaging that overstates the Corporation’s mandate in moments of urgency.
Technical-success drift may include:
platforms or repositories becoming practical approval gates;
observability systems being treated as command surfaces;
structured evidence becoming mistaken for legal authority; or
sophisticated architecture being overread as a source of entitlement or supervisory power.
The Corporation shall resist the idea that success justifies institutional mutation. The more effective the Corporation becomes, the more carefully it shall preserve its boundaries.
27.3 Drift Through Partner Expectation, Funding Pressure, or Hosting Dependence
Perimeter Drift may also arise through partner expectation, concentrated funding, strategic sponsorship, host dependence, infrastructure lock-in, or operational reliance on external actors. Even where no explicit demand is made, the Corporation may begin to adjust its conduct, language, priorities, sequencing, correction practices, technical roadmap, or tolerance for ambiguity in order to preserve support, access, legitimacy, or continuity. Such adaptive compromise is a classic form of drift and shall be treated as a structural warning sign.
This form of drift may manifest where:
a) partners begin to expect the Corporation to behave like an approval, routing, or execution-adjacent institution because that is “what the ecosystem needs”; b) donors or sponsors reward more expansive claims, outputs, or interfaces and penalize narrower constitutional fidelity; c) hosts or infrastructure providers quietly shape what the Corporation can publish, correct, or redesign; d) the Corporation becomes reluctant to enforce non-execution and neutrality rules against powerful counterparties; or e) institutional leaders start rationalizing boundary-softening as necessary to preserve financial sustainability or ecosystem relevance.
The Corporation shall not confuse dependency management with lawful strategy. If the practical price of retaining support is progressive erosion of constitutional boundaries, the support has become institutionally corrosive. In such circumstances, the Corporation shall prefer diversification, redesign, narrowing, or exit to silent accommodation. Boundary compromise purchased by stability is still compromise.
27.4 Drift Through Repetition, Narrative Habit, or Informal Practice
Perimeter Drift frequently occurs not through formal policy change, but through repetition, narrative habit, shorthand description, routine exception-making, and informal practice. A phrase initially used for convenience begins to harden into institutional meaning. A workflow initially tolerated as exceptional becomes standard. A partner assumption goes uncorrected often enough that it starts to function as truth. An internal description of an artifact as “effectively approved” seeps into external materials. Over time, informal practice silently reconstitutes the institution.
The Corporation shall therefore reject the proposition that repeated practice can amend constitutional meaning. In particular:
a) repeated use of execution-adjacent language shall not be allowed to normalize execution-adjacent function; b) repeated reliance on side channels shall not create lawful authority; c) repeated tolerance of ambiguous public description shall not create a broader role; d) repeated deference to powerful partners shall not become institutional custom; and e) repeated internal overreading of outputs shall not determine their actual legal or constitutional effect.
Narrative habit is especially dangerous where it is reinforced by success, praise, urgency, or ecosystem demand. The Corporation shall therefore periodically test its actual practices and descriptions against the text and purpose of these Bylaws rather than against what has recently become familiar or rhetorically convenient. Familiarity does not equal fidelity.
27.5 Drift Through Documentation, Product Language, or Market-Legibility Inflation
Perimeter Drift may occur through the gradual inflation of documentation, product language, technical labeling, public descriptions, metadata, or presentation styles that make the Corporation or its outputs appear more authoritative, mature, execution-ready, market-legible, or standing-bearing than they truly are. This form of drift is particularly dangerous because it often begins as “better messaging” or “clearer positioning” and ends as material overclaim with legal and institutional consequences.
Examples include:
a) renaming an evidence artifact in ways that imply approval or clearance; b) giving dashboards or platform states labels that resemble execution or readiness decisions; c) presenting prototypes, pilots, or partial deployments as stable institutional capabilities; d) compressing role distinctions in external materials to satisfy investors, donors, media, or public audiences; e) omitting limitations or handling conditions in public-safe derivatives; and f) allowing internal product language to be borrowed directly into external positioning without boundary review.
The Corporation shall treat naming, product positioning, public-safe summarization, and documentation design as governance issues, not merely communications tasks. If language changes the practical or perceived effect of a system, output, or relationship, the change is perimeter-relevant. No amount of stylistic polish may be permitted to push an upstream artifact into downstream meaning.
27.6 Mandatory Detection, Escalation, and Recorded Correction
The Corporation shall maintain an affirmative obligation to detect, escalate, document, and correct Perimeter Drift. Drift prevention is not passive. It requires active governance, periodic scrutiny, and willingness to narrow or reverse developments that initially appeared manageable. All directors, officers, staff, contractors, and role-holders with relevant visibility into programs, systems, partnerships, or outputs shall bear responsibility to raise credible drift concerns through appropriate channels.
Detection may arise through:
a) internal review or audit; b) legal or compliance screening; c) technical architecture review; d) public feedback or partner misunderstanding; e) correction requests; f) conflicts or neutrality reviews; or g) observed divergence between formal instruments and operational practice.
When a credible drift issue is identified, the Corporation shall, as appropriate:
i) halt or narrow the relevant activity; ii) reclassify the matter under perimeter controls; iii) redesign the relevant workflow, interface, output, or relationship; iv) clarify or correct public description; v) document the issue and response; vi) escalate to counsel, compliance, integrity, or the Board; and vii) preserve a record sufficient to support future learning and accountability.
Corrective action shall not be deferred merely because the drift was incremental or because acknowledging it may be uncomfortable. Early correction is a mark of institutional seriousness. Delayed correction is a form of drift in itself.
27.7 Structural Breach and Consequences of Unchecked Drift
Unchecked Perimeter Drift may become a Structural Breach, meaning a condition in which the Corporation’s actual operation, public meaning, incentive structure, or partner-facing role has moved so materially beyond constitutional limits that isolated corrections are no longer sufficient and structural remediation is required. Structural Breach may exist even without a single dramatic violation where, taken together, accumulated practices have effectively repurposed the institution.
Indicators of Structural Breach may include:
a) recurring use of the Corporation as a practical approval, routing, or execution-adjacent surface; b) sustained inability to maintain independent judgment because of dependency or capture; c) repeated overclaim that is not effectively corrected; d) technical systems whose default operation exceeds the non-execution boundary; e) revenue or incentive structures materially tied to downstream outcomes; f) widespread ecosystem misunderstanding that the Corporation has not remedied; or g) Board-level awareness of drift without adequate corrective response.
Where Structural Breach is identified or credibly alleged, the Corporation shall treat the matter as a constitutional emergency. Remediation may require, as appropriate:
i) immediate suspension of the affected program, platform, or relationship; ii) legal and Board review; iii) restructuring of governance, incentives, or technical architecture; iv) public clarification or correction; v) funding or partnership renegotiation; vi) leadership-level accountability measures; and vii) formal amendment only if the contemplated role is lawful, mission-consistent, and intentionally sought through proper process, which amendment shall never be presumed.
The Corporation shall not normalize Structural Breach because reversal is inconvenient. Constitutional continuity is more important than reputational smoothness or short-term strategic comfort.
27.8 Periodic Boundary Review as a Governance Requirement
To prevent Perimeter Drift from becoming normalized, the Corporation shall periodically undertake boundary review of material programs, systems, outputs, partnerships, revenue structures, and public descriptions. Such review shall examine whether the Corporation remains in practice where these Bylaws place it in principle. Boundary review is not optional hygiene; it is part of prudent governance for an institution whose value and risk both increase with centrality.
Boundary review may include, as appropriate:
a) review of output classes and how they are actually used by recipients; b) examination of platform states, workflows, and interface meanings; c) analysis of funding concentration and partner leverage; d) assessment of public descriptions against actual operational state; e) review of whether clear handoffs remain visible; f) identification of areas where partner or ecosystem expectations are outpacing lawful role; and g) validation that corrective records, divergence notes, and perimeter decisions remain current.
The form and frequency of such review may vary with scale and risk, but the duty to review shall remain. A fast-moving institution without periodic perimeter review is an institution already drifting.
27.9 Interpretive Rule for Perimeter Drift Prevention
This Section shall be interpreted to preserve the Corporation’s constitutional integrity against the cumulative effects of success, dependency, ambiguity, repetition, and convenience. Perimeter Drift is prohibited even where no individual step appears dramatic. The Corporation shall therefore prefer earlier intervention, narrower interpretation, and more explicit correction over passive hope that ambiguities will remain harmless.
Where ambiguity exists, the interpretation that better preserves:
a) non-execution in practice as well as theory; b) mission lock and exempt-purpose fidelity; c) truthful public meaning; d) independence from ecosystem pressure and dependency; and e) early rather than delayed correction of drift
shall prevail unless a contrary result is required by law.
28. Public Communications Discipline for Perimeter Safety (GCRI United States)
28.1 All External Communications Subject to Perimeter Truthfulness
All external communications of the Corporation shall be subject to perimeter truthfulness. No public statement, website text, report, deck, interview, event remark, briefing note, social post, funding document, partnership communication, metadata label, repository description, demonstration script, educational handout, or public-safe summary shall describe the Corporation, its outputs, its systems, its role, or its institutional relationships in a manner that crosses, softens, obscures, or practically undermines the non-execution boundary, public-benefit posture, exempt-purpose discipline, neutrality obligations, or claims limitations established in these Bylaws.
Perimeter truthfulness requires the Corporation to ensure that external communications are not merely literally defensible, but institutionally accurate in their overall effect. A statement may be misleading even if each sentence can be technically defended in isolation, where the total impression conveyed suggests broader authority, greater maturity, stronger approval effect, wider deployment, deeper institutional standing, or more execution-bearing capability than is lawfully and actually true. The Corporation shall therefore govern communications by communicated meaning and likely recipient understanding, not by semantic technicality alone.
This principle applies across all audiences, including:
a) governments and public institutions; b) donors, sponsors, and strategic backers; c) media and public audiences; d) technical and academic audiences; e) vendors, implementers, and infrastructure actors; f) aligned entities, host institutions, and ecosystem partners; and g) potential participants, members, fellows, or collaborators.
Different audiences may require different levels of technical detail, but no audience may be given a materially false or inflated picture of what the Corporation is, what it does, what it may lawfully do, or what its outputs mean. Communications strategy shall not outrun constitutional truth.
28.2 Mandatory Use of Non-Execution, Non-Endorsement, and Non-Reliance Formulations
Where the subject matter, context, audience, or foreseeable use of a communication creates meaningful risk that the Corporation could be misunderstood as possessing approval, execution, regulatory, sovereign, market, advisory, investment, routing, or endorsement authority, the communication shall include appropriate non-execution, non-endorsement, and non-reliance formulations. These formulations shall be used not as empty disclaimers, but as boundary-preserving instruments designed to ensure truthful institutional meaning.
Such formulations may, as appropriate to the context, clarify that:
a) the Corporation is a nonprofit, public-benefit, scientific, educational, and non-executing institution; b) the relevant output is evidentiary, technical, educational, governance-supporting, or observability-related rather than approving or transaction-bearing; c) the Corporation does not confer regulatory authorization, sovereign standing, routeability, or market permission; d) independent judgment remains with the lawful recipient; and e) no endorsement, certification, or preferential treatment should be inferred unless expressly and lawfully stated.
The Corporation shall calibrate such formulations to the risk and audience involved. Not every communication requires the same density of boundary language. However, no communication may omit necessary boundary language where the omission would materially increase the risk of overreading, hidden approval inference, or execution-side misunderstanding. Concision is permissible. Boundary erosion through elegant omission is not.
Where standard formulations are approved for recurring use, such standards shall remain subject to periodic review to ensure they remain fit for actual use patterns and do not become stale, misleading, or ceremonial.
28.3 Prohibition on Promotional Language That Implies Regulatory, Sovereign, Market, or Execution Capacity
The Corporation shall not use promotional, aspirational, fundraising, strategic, media-facing, or ecosystem-facing language that implies or reasonably suggests that the Corporation possesses regulatory capacity, sovereign authority, market-facing power, execution capability, approval rights, routeability authority, implementation mandate, enforcement ability, or other consequence-bearing functions that it does not lawfully hold. This prohibition applies even where the language is intended merely to simplify, energize, attract support, or communicate ambition.
Prohibited promotional inflation includes, without limitation:
a) language suggesting that the Corporation “approves,” “licenses,” “clears,” “authorizes,” “deploys,” “operates,” “executes,” “runs,” “settles,” “routes,” or “guarantees” in contexts where those words would be materially misleading; b) framing that compresses evidence support, interoperability, or technical infrastructure into execution-bearing outcomes; c) slogans, taglines, or visual narratives that reasonably imply public authority or market operation; d) descriptions of systems or outputs as if they were live operational authority surfaces when they are not; and e) promotional comparisons that overstate maturity, coverage, or institutional effect.
The Corporation may communicate mission, vision, strategic importance, and public-benefit ambition. It may not market itself as more powerful, deployed, authorized, or execution-capable than it is. Communications that win attention by crossing the perimeter are not successful communications; they are constitutional and governance failures.
28.4 Review and Sign-Off Requirements for Sensitive External Statements
The Corporation shall maintain review and sign-off requirements for sensitive external statements whose content, audience, timing, or foreseeable use could materially affect perimeter safety, claims discipline, public meaning, donor understanding, partner expectations, regulatory interpretation, or institutional risk. Sensitive statements shall not be released solely on the basis of subject-matter confidence, communications urgency, or the seniority of the speaker.
Sensitive external statements may include, without limitation:
a) statements regarding partnerships with public institutions, regulators, ministries, or major aligned entities; b) statements describing technical systems, deployment state, interoperability, capability, or institutional maturity; c) statements relating to policy, public affairs, crisis situations, resilience events, or public controversy; d) fundraising and strategic backer materials; e) public explanations of evidence, observability, assurance, conformance-support, or public-good technical outputs that may be overread; f) statements involving logos, badges, affiliations, or institutional architectures; and g) any communication near the legal, political, or execution-side edge of the Corporation’s role.
Review and sign-off shall be proportionate to the risk involved and may include legal, compliance, executive, technical, programmatic, and/or Board-level review where appropriate. No person may bypass such review because the statement is urgent, well-intentioned, or apparently obvious. Where external meaning could materially affect perimeter safety, speed shall remain subordinate to correctness.
28.5 Quote, Logo, Testimonial, Endorsement, and Co-Branding Controls
The Corporation shall maintain strict controls over the use of quotes, logos, testimonials, endorsements, partner references, architectural diagrams, affiliation language, and co-branding arrangements in order to prevent false endorsement, implied authority, inflated institutional standing, or hidden approval effects. The Corporation’s name and associated indicia shall not be used to create the appearance that the Corporation has validated, approved, favored, or institutionally elevated a person, product, institution, program, or ecosystem actor beyond recorded truth.
Such controls shall apply to:
a) Corporation-issued materials; b) third-party materials using the Corporation’s identity or references; c) joint event and panel branding; d) press releases and public announcements; e) websites, decks, fundraising materials, and social posts; and f) technical or ecosystem maps in which the Corporation appears alongside other actors.
No quote, testimonial, or co-branding arrangement shall be used in a manner that causes the Corporation’s public-benefit reputation to function as commercial endorsement, political sponsorship, or hidden approval. Any use of logos, marks, or institutional references that could reasonably produce such an effect shall require narrowing, qualification, or refusal. Where misuse occurs, the Corporation shall act to correct it.