V. Stewardship
77. Purpose, Constitutional Function, and Governing Rule
77.1 Purpose
This Part V constitutes the asset-governance, stewardship, non-enclosure, and public-good technical continuity charter of GCRI US. It fixes the constitutional rules by which the Corporation shall govern intellectual property, repositories, code, documentation, ontologies, schemas, methods, technical baselines, governance artifacts, labels, marks, and other intangible assets so that they remain aligned with mission lock, public-benefit distinctness, non-execution discipline, and the wider public-good architecture of the Nexus-oriented order.
Part V is necessary because intellectual property in a public-benefit institution is never merely a matter of ownership title or administrative housekeeping. It is one of the principal surfaces through which mission may either be protected or quietly compromised. Asset governance determines, among other things:
a) whether core technical and semantic infrastructure remains available for lawful public-good use or drifts into enclosure; b) whether repositories, code, methods, and reference assets remain reviewable, interoperable, and correctable; c) whether contributions strengthen the common rail or contaminate it with restrictions, encumbrances, or hidden dependencies; d) whether marks and labels preserve truthful public meaning or become vehicles for overclaim, exclusivity, or institutional confusion; and e) whether the Corporation remains a steward of common public-good assets or mutates into a rights-extraction or commercialization vehicle inconsistent with its constitutional role.
This Part therefore serves as the Corporation’s principal answer to the question: how shall we hold, protect, license, release, govern, and transmit intangible assets in a way that preserves the public-good core rather than exploiting it? The answer is not that the Corporation abandons property discipline. It is that property discipline must itself be subordinated to mission, continuity, interoperability, non-enclosure, and safeguards integrity.
Accordingly, Part V shall be read as:
i) the governing constitutional map for asset classes and stewardship posture; ii) the principal anti-enclosure rule for core public-good technical and semantic infrastructure; iii) the baseline for licensing, contribution acceptance, repository control, and open-source integrity; and iv) the continuity doctrine by which core assets survive transition, stress, succession, or institutional change without private capture.
Part V is not a commercial annex. It is part of the constitutional architecture that determines whether GCRI US can remain a trustworthy steward of public-good infrastructure over time.
77.2 Relationship of Part V to Mission Lock, Public-Benefit Mandate, and Public-Good Distinctness
Part V shall be interpreted together with Parts I through IV as an integral part of the Corporation’s constitutional order. It operationalizes, in the domain of intellectual property and technical stewardship, the deeper commitments already fixed elsewhere in these Bylaws: mission lock, public-benefit distinctness, non-execution, non-capture, protected participation, and federation-compatible public-good continuity.
Mission lock without asset discipline is incomplete. A corporation may proclaim public-benefit purpose while allowing its code, methods, semantic baselines, repositories, or documentary infrastructure to drift into exclusive control, private dependency, opaque licensing, or commercialization logic that gradually neutralizes the public-good core. Part V prevents that drift by requiring that the governance of assets remain subordinate to constitutional purpose.
Public-benefit mandate also requires that the Corporation’s asset posture not be interpreted through a default proprietary maximization model. GCRI US is not constituted to treat every intangible output as an opportunity for exclusion, extraction, monetization, or leverage. It is constituted to steward public-good infrastructure lawfully and seriously. Asset governance under Part V shall therefore be read through the following propositions:
a) core assets exist first to preserve mission, integrity, continuity, and public-benefit functionality; b) ownership and custody are tools of stewardship, not ends in themselves; c) control is justified where it protects non-enclosure, correctness, safety, marks integrity, and public meaning—not where it merely accumulates negotiable institutional advantage; and d) the Corporation’s technical and semantic estate must remain intelligible and governable across time, contributors, repositories, and successor conditions.
Public-good distinctness is especially important in the U.S. context because the legal and commercial environment strongly normalizes exclusive rights logic, monetization strategy, and aggressive portfolio treatment of intangible assets. These Bylaws reject automatic importation of that logic into the core of GCRI US. The Corporation may hold rights. It may protect marks. It may recover costs in lawful and bounded ways. But it may not allow asset governance to repurpose the institution into a quiet commercialization layer inconsistent with its nonprofit and public-benefit identity.
Where any asset-related decision could move the Corporation toward enclosure, dependency, extraction, exclusivity, or proprietary constitutional drift, Part V shall control against that movement unless a narrower and lawfully justified exception is expressly recorded.
77.3 Intellectual Property as a Governance Surface, Not Merely a Commercial Asset Class
For purposes of these Bylaws, intellectual property shall be treated as a governance surface and not merely as a commercial asset class. That means patents, copyrights, repositories, code, schemas, governance documents, ontologies, data dictionaries, methods, names, marks, and derivative works shall all be governed according to what they do to institutional meaning, public-good continuity, interoperability, control, trust, and role fidelity—not only according to abstract legal rights of exclusion or monetization.
This governance-surface approach is necessary because intellectual property in an institution like GCRI US performs several constitutional functions at once. It can:
a) stabilize common semantics and authoritative technical baselines; b) preserve lineage, integrity, and correctionability of institutional outputs; c) protect against misleading forks, counterfeit canonical claims, and mark misuse; d) prevent private enclosure of assets necessary to the public-good core; and e) structure how future contributors, partners, hosts, successors, and the public may interact with the Corporation’s technical and documentary estate.
At the same time, poorly governed IP can become a source of constitutional harm. It can:
i) create hidden chokepoints over shared infrastructure; ii) allow partners or vendors to capture or encumber public-good assets; iii) make core semantics or technical baselines non-reviewable or non-portable; iv) distort public meaning through marks, badges, and labels; and v) incentivize revenue logic that conflicts with institutional neutrality and mission.
The Corporation shall therefore not permit any part of its IP posture to be shaped solely by default assumptions such as “maximize rights,” “preserve optionality,” “monetize where possible,” or “treat all assets alike.” Those are not constitutional instructions for a public-benefit steward. Instead, GCRI US shall ask of each asset class: what role does this asset play in preserving the common rail, institutional truth, public-good reusability, and non-enclosure? The answer to that question shall guide the governance of the asset more fundamentally than the mere existence of a legal right.
Where tension exists between maximizing proprietary advantage and preserving public-good integrity, the latter shall generally prevail unless a contrary result is clearly justified by mission, integrity, or safeguards necessity and is recorded as such.
77.4 Public-Good Technical Stewardship as a Constitutional Duty of GCRI US
Public-good technical stewardship shall be treated as a constitutional duty of GCRI US. This means that the Corporation’s responsibility for code, schemas, methods, ontologies, reference implementations, governance-related technical materials, repositories, documentation, and related intangible infrastructure is not optional, ornamental, or secondary to external partnership or product opportunity. It is part of the institutional burden the Corporation is constituted to carry.
This duty includes, without limitation:
a) preserving the continuity and integrity of canonical public-good assets within its remit; b) ensuring that core technical and semantic materials remain reviewable, documented, and capable of lawful reuse consistent with mission; c) maintaining repository, versioning, and lineage discipline so that official assets are not lost, fragmented, or counterfeited by confusion; d) resisting enclosure, encumbrance, or hidden proprietary contamination of public-good core materials; and e) protecting the distinction between core assets, controlled assets, third-party materials, and derivative forms in a way that preserves institutional clarity.
Public-good technical stewardship does not require that everything be published without restriction. Nor does it eliminate the need for controlled handling where rights, security, privacy, or mark integrity require it. What it does require is that the Corporation govern technical and documentary assets from the standpoint of stewardship first: what must remain available, reviewable, interoperable, and continuous so that the public-good core does not fracture or become privately captured?
In the U.S. context, this duty also means that GCRI US shall not assume that strong stewardship can be outsourced entirely to vendors, platforms, sponsors, volunteers, or better-resourced ecosystem actors. External support may be used. The constitutional burden of stewardship remains with the institution. If the Corporation cannot explain who holds the authoritative repository, what counts as canonical, how continuity will be preserved, how licensing aligns with mission, and how core assets remain resistant to enclosure, then it has not yet fulfilled its stewardship duty.
Public-good technical stewardship is therefore not a technical hobby. It is part of how GCRI US remains itself across time.
77.5 Binding Effect of Part V Across All Outputs, Platforms, Repositories, Contributions, Partnerships, and Successor Arrangements
Part V shall bind all outputs, repositories, codebases, documentation sets, schemas, ontologies, data dictionaries, taxonomies, governance documents, marks, labels, badges, templates, research outputs, platforms, technical environments, contribution pathways, licensing decisions, joint-development arrangements, partner-facing asset interfaces, and successor or transition structures of GCRI US. No material asset-related practice of the Corporation shall sit outside the constitutional logic of this Part merely because it appears operational, technical, informal, or external-facing.
Its binding effect extends across, without limitation:
a) assets created by staff, officers, contractors, fellows, volunteers, researchers, or other contributors acting for or through the Corporation; b) assets maintained in institutional repositories, hosted environments, partner-controlled environments, or mirrored environments; c) working papers, internal drafts, formal releases, models, configurations, methods notes, governance artifacts, and derivative outputs; d) trademarks, wordmarks, logos, seals, labels, badges, and related public-trust assets; e) licensing choices, contribution terms, open-source dependencies, and third-party incorporated materials; and f) continuity, transition, exit, restructuring, or successor arrangements affecting stewardship of core assets.
No officer, team, or contributor may claim that Part V does not apply because the relevant asset is “just code,” “only a draft,” “only internal,” “just a partner repository,” “only a mark-use issue,” or “not yet official.” If the asset or arrangement can materially affect public-good continuity, canonical meaning, public representation, licensing posture, non-enclosure, or future stewardship, this Part applies.
Likewise, no successor arrangement, restructuring plan, partnership transition, or wind-down scenario may bypass Part V on the assumption that constitutional asset rules cease to matter when institutional form is changing. In many cases, transition is the moment at which non-enclosure, continuity, and custodial integrity matter most. Part V therefore binds not only present operations, but future transfer and succession conditions as well.
The Corporation shall interpret this binding effect broadly enough to prevent quiet asset drift, quiet repository capture, quiet licensing erosion, or quiet successor enclosure through unmanaged exception. Intellectual property and technical stewardship are too central to the Corporation’s identity to be left to fragmented local practice.
77.6 Interpretive Rule for Part V
This Part V shall be interpreted to preserve a controlling proposition: the intellectual and technical estate of GCRI US exists to serve mission, continuity, integrity, interoperability, and public-good stewardship before it serves exclusion, leverage, or revenue logic. Ownership, custody, licensing, and control are constitutionally justified only to the extent that they preserve those higher institutional purposes.
Where ambiguity exists under this Part, the interpretation that better preserves:
a) public-good continuity and non-enclosure; b) truthful canonical stewardship and repository integrity; c) interoperability, reviewability, and traceable lineage of core assets; d) bounded rather than expansive proprietary claims over public-good infrastructure; and e) institutional continuity through partnership, transition, and successor arrangements
shall prevail unless a contrary result is required by law.
78. Public-Good Stewardship Posture (GCRI United States)
78.1 Public-Good Stewardship as the Default Legal and Institutional Posture
The default legal and institutional posture of GCRI US with respect to intellectual property, repositories, documentation, technical baselines, semantic assets, methods, marks, and related intangibles shall be public-good stewardship. This means the Corporation shall approach assets first as objects of fiduciary-like care for mission continuity, public benefit, interoperability, reviewability, and lawful reuse—not as inventory to be enclosed, opportunistically monetized, or strategically hoarded for institutional leverage.
Public-good stewardship as a default posture requires the Corporation to begin from the following assumptions:
a) the Corporation exists to preserve and govern a public-good technical and semantic estate within its lawful remit; b) assets that are foundational to the common rail, to public-benefit trust, or to institutional continuity are presumptively to be stewarded in ways that keep them governable, legible, and non-fragmenting; c) ownership, custody, and control exist to protect those ends, not to displace them; and d) proprietary forms of control must be justified in relation to mission, integrity, marks protection, safeguards, or continuity—not assumed by default because the law allows them.
This default posture shall apply across asset categories of differing sensitivity and handling profile. It does not require that every asset be fully public, freely redistributable, or without restrictions. It requires that restrictions be imposed for principled, reviewable, and constitutionally aligned reasons. For example, controlled handling may be justified for rights-bearing materials, security-sensitive assets, or trust-bearing marks. But even those restrictions must be understood as expressions of stewardship rather than as silent movement toward enclosure or extraction.
In practical governance terms, a public-good stewardship posture means the Corporation shall ask, for each material asset or asset class:
i) is this part of the public-good core or materially adjacent to it; ii) what degree of openness, control, attribution, integrity protection, and custodial discipline best serves mission and continuity; iii) how can this asset remain reviewable, correctable, and interoperable over time; and iv) what restrictions, if any, are truly necessary rather than merely convenient.
Where these questions are not asked, default legal forms may quietly repurpose the institution. Part V requires that they be asked every time material asset governance is at issue.
78.2 Stewardship Distinct From Absolute Proprietary Control
Public-good stewardship shall be distinguished sharply from absolute proprietary control. GCRI US may own, license, protect, restrict, or enforce rights in particular assets where lawfully appropriate. But the Corporation shall not interpret stewardship to mean that it must maximize exclusivity, retain every possible right, suppress lawful reuse, or centralize all control in a manner inconsistent with mission and public-good continuity.
Stewardship is a constitutional role. Absolute proprietary control is a market posture. The two are not the same. Stewardship in these Bylaws means:
a) maintaining asset integrity and authoritative lineage; b) preventing misleading forks, false canonical claims, or harmful misuse; c) preserving continuity across contributors, repositories, and institutional transitions; d) enabling lawful review, reuse, interoperability, and correction consistent with asset class and safeguards profile; and e) ensuring that rights attached to assets remain subordinate to the public-benefit purpose of the institution.
By contrast, absolute proprietary control would tend toward:
i) enclosure for bargaining advantage; ii) control for its own sake rather than for continuity or integrity; iii) suppression of legitimate reuse to maintain institutional dominance; iv) conversion of shared infrastructure into negotiable scarcity; and v) conflation of legal right with constitutional legitimacy.
These Bylaws reject that proprietary maximization model for the core public-good estate of GCRI US. The Corporation may need firm control over some assets precisely to keep them public-good aligned. But that is different from claiming the broadest possible exclusionary power because the institution could. Part V therefore requires the Corporation to justify control by reference to stewardship aims rather than to abstract legal entitlement alone.
Where a governance decision could be framed either as stewardship or as absolute proprietary assertion, the Corporation shall adopt the reading that better preserves public-good continuity, reviewability, and non-enclosure unless a stronger control posture is specifically justified and recorded.
78.3 No Enclosure of Common Infrastructure Necessary for the Public-Good Core
GCRI US shall not enclose any common infrastructure necessary for the public-good core in a manner that undermines lawful access, continuity, interoperability, reviewability, or public-benefit governance. Common infrastructure for purposes of this Part includes technical, semantic, documentary, and governance assets without which the Corporation’s public-good mission—or the wider common rail with which it must remain compatible—would become materially more fragmented, dependent, opaque, or privately constrained.
Such common infrastructure may include, without limitation:
a) canonical schemas, ontologies, and semantic baselines; b) core methods and evidence logic; c) reference implementations and public-good technical baselines; d) governance templates, process logic, and documentary frameworks central to the institutional order; e) data dictionaries, mappings, and taxonomic structures required for interoperability; and f) repository and lineage structures without which the above cannot be reliably stewarded.
The Corporation shall not enclose such infrastructure through:
i) exclusive licensing inconsistent with public-good continuity; ii) platform friction designed to create artificial access dependency; iii) technical lock-in that makes lawful reuse or migration practically impossible; iv) contractual or procedural gating that turns common infrastructure into negotiated scarcity; or v) silent transformation of shared baselines into internal-only or partner-captured assets.
This clause does not prohibit controlled handling where rights, security, mark integrity, or lawful restrictions require it. It prohibits conversion of what must remain functionally public-good into effectively private constitutional inventory. If the Corporation begins to depend for mission continuity on assets that are legally or practically enclosed beyond its ability to steward them for public-benefit use, then the institution has accepted a structural risk inconsistent with this Part.
Accordingly, the Corporation shall review enclosure risk not only when drafting licenses, but when selecting infrastructure, accepting contributions, entering partner arrangements, moving repositories, or designing public access conditions.
78.4 No Repurposing of Shared Technical and Semantic Infrastructure Into Private Constitutional Inventory
The Corporation shall not repurpose shared technical, semantic, or documentary infrastructure into private constitutional inventory. A private constitutional inventory exists where assets that function as part of the common public-good rail are gradually treated as if they were internal exclusive institutional property whose deeper governance significance is no longer acknowledged. This can occur even where no explicit privatization is announced.
Repurposing may take place through:
a) moving common baselines into restricted repositories without sufficient justification; b) treating shared ontologies, schemas, or methods as negotiable partner advantages rather than public-good coordination assets; c) converting common governance documents or templates into internal proprietary operating assets; d) redesigning access or attribution rules so that lawful public-good reuse becomes effectively impractical; or e) using formal ownership to erase the fact that an asset functions as shared infrastructure for a broader governance and interoperability order.
The Corporation shall not normalize such drift. The public-good core of GCRI US depends upon distinguishing between:
i) assets that the institution owns and uses internally in a bounded operational sense; and ii) assets that, even if lawfully owned or custodied by the institution, must still be governed as part of a shared infrastructure necessary to the public-good core.
This distinction is constitutional, not merely administrative. An asset may be held by GCRI US and still not be available for enclosure, bargaining, or private constitutional repurposing because its role in the common rail makes such treatment incompatible with mission. The Corporation shall preserve that understanding in licenses, repository design, contribution policy, partner negotiations, and public description.
If an asset once treated as shared infrastructure begins to be governed like a private strategic resource, the matter shall be escalated as a potential Part V defect.
78.5 Asset Use Must Remain Subordinate to Mission, Integrity, and Public Benefit
All asset use by GCRI US shall remain subordinate to mission, integrity, and public benefit. No repository, method, mark, codebase, template, ontology, publication, or derivative asset shall be used primarily in a manner that conflicts with these superior constitutional commitments, even if such use is legally permissible in the abstract.
This means, among other things, that the Corporation shall not use its assets in ways that:
a) materially compromise neutrality or public-trust posture; b) convert public-good infrastructure into institutional bargaining chips; c) create incentives for misleading scarcity or exaggerated canonical dependence; d) encourage partner arrangements that distort the public-benefit logic of the assets; or e) subordinate long-term continuity and reviewability to short-term leverage, funding convenience, or ecosystem advantage.
Mission-subordinate use requires the Corporation to ask not merely whether it can exercise a right, but whether doing so strengthens or weakens the public-good constitutional identity of the institution. Integrity-subordinate use requires the Corporation to preserve truthful asset meaning, provenance, and custodial discipline. Public-benefit-subordinate use requires the Corporation to consider whether asset governance produces lawful accessibility, reusability, and continuity in a way consistent with the broader nonprofit role of GCRI US.
Where these principles conflict with a narrower institutional advantage—such as exclusivity pressure, partner convenience, platform lock-in, or monetization opportunity—the Corporation shall ordinarily prefer the path that better preserves mission and public benefit, unless a contrary and well-recorded justification grounded in safeguards or marks integrity requires otherwise.
78.6 No IP Governance That Quietly Converts GCRI US Into a Commercial Rights-Extraction Vehicle
GCRI US shall not permit its intellectual property governance to quietly convert the institution into a commercial rights-extraction vehicle. A rights-extraction posture exists where the Corporation begins to govern its technical, semantic, documentary, and branding assets primarily in order to generate exclusionary leverage, licensing rents, proprietary bottlenecks, access tolls, or strategic dependency rather than to preserve the public-good core.
Such conversion may occur gradually through:
a) increasingly restrictive licensing without mission-grounded justification; b) expanding mark or asset control beyond integrity protection into broad commercial leverage; c) monetization structures that depend upon restricting access to what should remain public-good infrastructure; d) partner arrangements that reward scarcity, exclusivity, or lock-in over interoperability; or e) internal culture that begins to speak of the asset estate primarily in terms of portfolio exploitation rather than stewardship.
These Bylaws reject that evolution. GCRI US may lawfully recover costs, protect marks, and govern controlled assets with seriousness. It may not become a body whose public-good technical and semantic core is treated as an extractive revenue surface. The distinction is subtle but essential. A public-benefit institution may need resources to sustain its work. It may not reconfigure the terms of access to shared core infrastructure so that mission becomes functionally dependent on exclusion.
Accordingly, any proposal, practice, or partner pressure that would materially push the Corporation toward rights-extraction logic shall be treated as constitutionally sensitive and subject to heightened review under this Part.
78.7 Duty to Maintain Reusability, Reviewability, and Interoperability of Core Public-Good Assets
GCRI US shall maintain an affirmative duty to preserve the reusability, reviewability, and interoperability of core public-good assets within its remit, subject to lawful safeguards and controlled-handling requirements. This duty reflects the reality that public-good infrastructure does not remain public-good merely because it is nominally “open” once. It remains public-good only if it can continue to be understood, examined, reused lawfully, ported, compared, and integrated without artificial institutional obstruction.
The duty of reusability requires that assets be governed so that lawful and mission-consistent reuse remains practically possible. The duty of reviewability requires that authoritative assets be inspectable, documentable, and not hidden behind opaque dependencies or unjustified restrictions. The duty of interoperability requires that the core public-good estate remain capable of interacting with other legitimate systems, entities, and contexts without semantic fracture or proprietary dead ends.
This may require, as appropriate:
a) clear licensing and provenance metadata; b) repository integrity and authoritative-source discipline; c) documentation sufficient to support use and review; d) avoidance of hidden dependencies incompatible with public-good continuity; e) compatibility review when adding third-party components or restrictive terms; and f) public clarification where an asset is controlled, canonical, experimental, or non-authoritative.
The Corporation shall not satisfy this duty merely by posting files to a repository while allowing documentation decay, platform friction, dependency opacity, or ambiguous asset status to make meaningful reuse impracticable. Formal availability without practical usability is not enough.
Where reuse or review must be restricted for safety, privacy, security, rights, or mark-integrity reasons, the Corporation shall still seek the least restrictive posture consistent with those needs and shall avoid allowing exceptional restriction to become baseline opacity.
78.8 Most-Protective Reading Where Public-Good Core and Proprietary Claims Could Conflict
Where ambiguity exists between a public-good-core reading of an asset and a more proprietary, restrictive, or exclusionary reading, the Corporation shall adopt the reading that better protects continuity, public-benefit integrity, reusability, interoperability, and non-enclosure, unless a narrower proprietary posture is clearly required by law, marks integrity, rights protection, or another constitutionally recognized ground.
This rule applies, among other things, to ambiguity concerning:
a) whether an asset belongs to the core public-good estate or to a more restricted class; b) whether a proposed control mechanism is genuinely necessary or merely convenient; c) whether a license term would impair lawful interoperability or reviewability; d) whether a partner claim would convert shared infrastructure into restricted inventory; or e) whether a repository or derivative work is being presented with more exclusivity than its constitutional role permits.
The burden of proving that a more restrictive or proprietary reading is appropriate shall rest on the party advocating that reading. General assertions of strategic value, negotiation flexibility, institutional optionality, or abstract commercial prudence shall not satisfy that burden without closer alignment to the constitutional purposes of this Part.
This rule does not abolish property discipline. It places it within the hierarchy of the institution’s public-benefit constitution. In case of doubt, GCRI US shall prefer stewardship over exclusion, public-good continuity over opportunistic scarcity, and intelligible common infrastructure over quiet enclosure.
78.9 Interpretive Rule for Public-Good Stewardship Posture
This Section shall be interpreted to preserve a controlling proposition: the asset posture of GCRI US is one of public-good stewardship, not proprietary maximization. The Corporation may hold and protect rights, but it shall do so to secure mission, continuity, integrity, and interoperability—not to create avoidable exclusion, hidden dependency, or extraction from the common rail.
Where ambiguity exists, the interpretation that better preserves:
a) public-good stewardship as the default institutional posture; b) distinction between stewardship and absolute proprietary control; c) resistance to enclosure of common infrastructure; d) subordination of asset use to mission, integrity, and public benefit; and e) stronger reusability, reviewability, and interoperability of core assets
shall prevail unless a contrary result is required by law.
79. IP Ownership and Stewardship Categories (GCRI United States)
79.1 Categories of Intellectual Property and Intangible Assets in Scope
For purposes of these Bylaws, the intellectual property and intangible asset estate of GCRI US shall include all legally protectable, contractually governed, technically governed, trust-bearing, or institutionally material intangible assets created, acquired, commissioned, maintained, controlled, licensed, hosted, or otherwise stewarded by or for the Corporation. The Corporation shall not treat asset governance as limited only to formal copyrightable works or federally registered rights. Part V governs the full practical estate through which the Corporation’s mission, technical continuity, public meaning, and institutional integrity are expressed.
Asset classes within scope include, without limitation:
a) copyright-bearing works, including reports, white papers, governance instruments, bylaws, frameworks, guidance, templates, manuals, educational materials, briefs, slides, websites, data dictionaries, technical documentation, and other documentary outputs; b) software and technical assets, including source code, object code, repositories, scripts, configurations, packages, build logic, deployment artifacts, models, reference implementations, test suites, pipelines, and system-level technical materials; c) semantic and knowledge assets, including ontologies, taxonomies, controlled vocabularies, schemas, data models, classifications, mappings, indicator logic, glossary structures, naming conventions, metadata rules, evidence logic, and related semantic baselines; d) governance and institutional architecture assets, including bylaws, terms of reference, committee structures, process maps, forms, registers, charter documents, decision logic, and procedural instruments; e) marks and trust-signaling assets, including names, wordmarks, logos, seals, labels, badges, certification-like signals, design marks, domain naming patterns, and public-description identifiers; f) database and curated information assets, including structured repositories, knowledge graphs, curated corpora, issue or incident taxonomies, asset inventories, metadata fields, and provenance structures, subject to the distinctions elsewhere in this Part between IP, privacy, safeguards, and data rights; g) derivative, composite, adapted, localized, or mixed-origin works, including reworked documents, translated materials, wrapped code, merged schemas, combined taxonomies, adapted frameworks, and generated or transformed outputs based on preexisting materials; and h) contractual or quasi-contractual intangible interests, including license rights, sublicenses, stewarded repository rights, contribution rights, publication rights, naming permissions, and continuity rights associated with assets not wholly owned by the Corporation.
The Corporation shall also recognize that some materials may fall into more than one category at once. A technical repository may be simultaneously a code asset, a semantic asset, and a public-trust asset if it carries canonical schemas, controlled vocabularies, and public reference code. A mark-bearing label may also be a governance-signaling device. A governance template may also be a semantic baseline. These Bylaws therefore require governance by function and significance, not by superficial classification alone.
Where doubt exists as to whether an intangible falls within the scope of this Part, the Corporation shall presume inclusion if the asset materially affects mission execution, public meaning, continuity, interoperability, contribution governance, repository integrity, or the Corporation’s public-good core.
79.2 Institutional Ownership, Custody, and Stewardship of Canonical Core Assets
Canonical core assets within the remit of GCRI US shall be held, controlled, or otherwise stewarded so that their institutional ownership, custody, and stewardship remain aligned with public-benefit continuity rather than with personal, ad hoc, or partner-dependent control. The Corporation shall ensure that assets central to its public-good technical and semantic estate are not left in legal or practical ambiguity regarding who owns them, who holds authoritative custody, and who is responsible for maintaining their continuity and integrity.
For purposes of this Section:
a) ownership concerns the legal title or legally recognized control interest in an asset; b) custody concerns where the authoritative copy, repository, or operational control of the asset resides; and c) stewardship concerns the duty to preserve the asset’s integrity, lineage, accessibility, and public-good function over time.
These three dimensions may overlap, but they shall not be confused. The Corporation may legally own an asset while another environment temporarily hosts it. It may steward an asset under a license without owning all rights in it. It may hold authoritative custody of a repository whose components include mixed-origin materials. What matters constitutionally is that the Corporation always be able to explain, for each canonical core asset:
i) who owns it or what legal basis governs it; ii) where the authoritative version resides; iii) who has lawful write, release, or change authority; iv) what continuity plan exists if current custodial arrangements fail; and v) how the asset remains protected against enclosure, unauthorized drift, or false claims of canonical status.
The Corporation shall not allow canonical assets to remain dependent on personal accounts, individual laptops, informal collaborator custody, unrecorded third-party hosting, or partner-side arrangements without explicit institutional control logic. That is not stewardship. It is fragility disguised as convenience.
Where a canonical asset cannot presently be brought into fully institutional custody, the Corporation shall record the reason, classify the dependency as a governance issue, and apply continuity and transition controls sufficient to reduce the risk that the asset will be lost, fractured, or privately captured.
79.3 Differentiation Between Core Public-Good Assets, Controlled Assets, and Third-Party Assets
The Corporation shall differentiate clearly among core public-good assets, controlled assets, and third-party assets, and shall not govern all intangible materials through a single undifferentiated property logic.
For purposes of these Bylaws:
a) Core public-good assets are those technical, semantic, documentary, or trust-bearing assets that are essential or materially important to the Corporation’s mission, public-good infrastructure, common-rail compatibility, canonical baselines, or continuity of stewardship. These assets are presumptively subject to the strongest non-enclosure, continuity, and interoperability protections. b) Controlled assets are assets that may legitimately require tighter licensing, access control, publication limits, or restricted handling due to rights, safeguards, security, controlled-room, mark-integrity, or other constitutionally recognized concerns. These assets remain within the Corporation’s stewardship logic but are not governed by a blanket openness rule. c) Third-party assets are assets owned or controlled by entities other than GCRI US, including licensed materials, incorporated standards, vendor components, partner-owned materials, external marks, and contributed materials subject to conditions that the Corporation must respect and govern lawfully.
The Corporation shall not:
i) treat core public-good assets as though they were merely controlled internal property; ii) treat controlled assets as though they were freely distributable public assets when safeguards or integrity duties require restriction; or iii) treat third-party assets as if they were GCRI-owned canonical materials merely because they are integrated into Corporation workflows or publications.
This differentiation shall be reflected in:
repository structure;
licensing and access terms;
contribution acceptance;
public description and provenance metadata;
continuity planning; and
enforcement posture.
Where an asset appears mixed in character—for example, a Corporation repository containing both core schemas and third-party licensed modules—the Corporation shall preserve clear internal and external distinctions rather than collapsing them into one convenient classification. The constitutional integrity of Part V depends in part on this disciplined separation of asset types.
79.4 Treatment of Staff-Created, Contractor-Created, Volunteer-Created, and Contributed Works
All material works created for, through, or on behalf of GCRI US by staff, contractors, volunteers, fellows, advisors, secondees, or other contributors shall be governed by clear rules ensuring that ownership, stewardship, contribution rights, and public-good continuity do not depend on informal assumptions. The Corporation shall not assume that because a work was created “for the mission,” its legal posture is automatically clear.
Accordingly:
a) works created by employees within the scope of employment shall, to the maximum extent permitted by applicable law and subject to these Bylaws, be treated as institutional works stewarded by GCRI US; b) works created by contractors shall be governed by written terms addressing ownership, licensing, reuse, third-party dependencies, attribution, and continuity; c) works created by volunteers, fellows, or other non-employee contributors shall be subject to contribution terms, assignment or license logic, and provenance recording sufficient to preserve lawful use and future stewardship; and d) contributed works received from external parties shall not be accepted into the Corporation’s authoritative estate without clarity regarding authority to contribute, applicable rights, restrictions, and stewardship implications.
The Corporation shall be especially careful with informal contribution cultures common in nonprofit, academic, and open technical environments. Valuable public-good infrastructure is often built through mixed-origin collaboration. That makes documentation more important, not less. A draft ontology created by a fellow, a reference script written by a volunteer, or a process template built collaboratively in a workshop may later become central to the Corporation’s core estate. If rights were never clarified, future continuity becomes unstable.
The Corporation shall therefore ensure that contributor status does not determine constitutional seriousness. A volunteer-created schema may require more documentation and stewardship discipline than a routine staff memo if its functional significance is higher. Asset governance follows role and consequence, not prestige of authorship alone.
79.5 Ownership of Drafts, Working Papers, Templates, Ontologies, Schemas, and Governance Artifacts
Drafts, working papers, templates, ontologies, schemas, governance artifacts, forms, mappings, process instruments, and similar semi-formal or developmental materials shall be governed with the same constitutional seriousness as more polished outputs where their functional significance warrants it. The Corporation shall not assume that because a work is “just a draft,” “only a template,” or “internal working material,” it lies outside Part V.
In particular:
a) drafts and working papers may carry intellectual, methodological, or reputational significance and shall be governed in terms of ownership, attribution, release conditions, and later supersession or withdrawal; b) templates and forms may embed governance logic, semantic assumptions, or process architecture and therefore require clear custodial and licensing treatment; c) ontologies and schemas are often core semantic infrastructure and shall be presumptively treated as stewardship-significant assets, not casual by-products; and d) governance artifacts such as procedures, matrices, registers, and decision frameworks may function as part of the institutional constitution in practice and therefore require strong repository, version, and lineage discipline.
The Corporation shall distinguish between:
i) non-authoritative drafts; ii) working materials under active development; iii) formally adopted or operative governance artifacts; and iv) canonical semantic or technical baselines.
This distinction must be visible in metadata, repository structure, public description, and change control. Without it, drafts may be mistaken for operative standards, and canonical assets may be undermined by ambiguous working copies. The Corporation’s stewardship duty includes preventing that confusion.
Ownership or custodial rules for these assets shall be sufficiently clear that later questions of reuse, publication, adaptation, or supersession can be answered without reconstructing institutional memory from personal accounts or informal practice.
79.6 Ownership of Code, Repositories, Models, Configurations, and Documentation
All code, repositories, models, configurations, pipelines, deployment logic, technical documentation, and related software-adjacent assets material to the Corporation’s work shall be governed under explicit ownership and stewardship rules consistent with Part V. The Corporation shall not permit technically central assets to remain in ambiguous ownership, unclear repository authority, or undocumented platform dependency.
This requires, among other things, that GCRI US determine for each material technical asset:
a) whether the Corporation owns it outright, holds it under license, or depends on mixed-origin rights; b) what repository is authoritative; c) who has write, merge, release, or deployment authority; d) what dependencies or encumbrances affect lawful reuse or continuity; and e) how transitions, forks, mirrors, or recovery would be handled if current maintainers or platforms change.
The Corporation shall distinguish clearly between:
i) code or documentation that is canonical public-good reference infrastructure; ii) code or models that are restricted for safeguards, security, or misuse reasons; iii) third-party software components incorporated under license; and iv) experimental or local materials not yet constituting official Corporation assets.
Technical ownership is not only about source code title. Models, configurations, build scripts, environment descriptors, deployment templates, and documentation may determine whether a system can actually be rebuilt, understood, or transitioned. The Corporation shall therefore avoid false completeness where it “owns the repo” but lacks practical stewardship over the environment necessary to make the asset meaningful.
Where code or documentation is maintained in partner-controlled or third-party-controlled environments, the Corporation shall classify that condition explicitly and govern it as a continuity and dependency issue rather than pretending it is full institutional custody.
79.7 Ownership of Data Dictionaries, Taxonomies, and Semantic Assets
Data dictionaries, taxonomies, vocabularies, mappings, classification systems, ontology fragments, semantic rules, glossary assets, and related semantic infrastructure shall be treated as high-significance intangible assets of the Corporation where they materially shape common meaning, interoperability, evidence logic, repository discipline, or public-facing technical function.
The Corporation shall not treat semantic assets as low-value appendices to code or documentation. In many cases they are the deeper constitutional layer beneath those materials, because they determine what categories exist, what terms mean, how systems interoperate, and how institutional truth is encoded.
Accordingly, GCRI US shall ensure that:
a) semantic assets are identified as a distinct governance category; b) their ownership, custodial logic, and provenance are documented; c) they are not silently absorbed into private or partner-owned systems without clear stewardship terms; d) canonical semantic baselines are protected against unauthorized revision or misleading fork; and e) derivative or localized semantic adaptations are recorded in relation to the canonical core.
Where a semantic asset is jointly built, mixed-origin, or derived from external material, the Corporation shall still preserve enough documentation to know what it may lawfully steward, adapt, or release. Semantic ambiguity at the ownership layer often leads to deeper governance ambiguity later. Part V requires earlier discipline.
79.8 Ownership of Marks, Wordmarks, Seals, Labels, and Badges
All marks, wordmarks, logos, seals, labels, badges, designators, visual trust assets, public-status signals, and related identity-bearing indicia used by GCRI US shall be treated as institutional trust assets subject to clear ownership or lawful control arrangements. The Corporation shall not leave such assets in vague custody, founder-personal control, designer-personal control, or partner-dependent status where public meaning depends on institutional integrity.
The Corporation shall determine, for each material trust-bearing mark or signal:
a) who legally owns it or what use rights the Corporation holds; b) whether the Corporation has sufficient authority to protect and police it; c) whether the mark is part of the formal institutional identity, a program label, a controlled badge, or another class of signifier; and d) what restrictions and continuity rules apply to prevent misuse, confusion, or unauthorized survival after relationship change.
Marks and badges are not governed only to protect branding aesthetics. They are governed because they can imply recognition, approval, canonical status, affiliation, or trust conditions beyond the truth. Ownership and control over such assets therefore must be institutionally coherent. A Corporation that cannot govern its own trust signals invites public confusion and constitutional drift.
The Corporation shall not permit contractors, hosts, partner platforms, or informal ecosystem actors to hold de facto control over marks or trust-bearing labels central to institutional meaning without explicit agreement and review under this Part.
79.9 Ownership of Derivative and Composite Works
The Corporation shall govern derivative works and composite works with explicit attention to provenance, stewardship, and public meaning. A derivative work may include revised, translated, adapted, localized, reformatted, summarized, forked, or transformed versions of preexisting materials. A composite work may combine multiple source assets, internal and external, into a single output, repository, schema package, publication, or platform component.
For such works, GCRI US shall determine, as appropriate:
a) what source materials were used; b) what ownership or license rights attach to each source component; c) what new rights, if any, arise in the derivative or composite form; d) whether the resulting work can be treated as canonical, derivative, experimental, or mixed-authority; and e) whether any part of the work carries third-party, contributor, or restricted obligations that affect release, reuse, or continuity.
The Corporation shall not allow derivative or composite works to erase lineage. Nor shall it permit a composite asset to be presented as wholly GCRI-owned if core elements remain third-party or jointly governed. Likewise, it shall not allow derivative outputs to be treated as canonical merely because they are newer or more visible. Canonical status remains a governance determination, not a natural consequence of revision.
Where a derivative or composite work becomes central to the public-good core, the Corporation shall ensure that the rights logic of the component parts does not silently make the resulting asset impossible to steward, release, or preserve consistently with Part V.
79.10 Treatment of Jointly Developed Assets and Mixed-Origin Materials
Any jointly developed asset or mixed-origin material involving GCRI US and one or more partners, contributors, hosts, vendors, public bodies, academic institutions, or other participants shall be governed through written, reviewable, and constitutionally aligned terms sufficient to preserve ownership clarity, stewardship continuity, publication rights, licensing posture, and public meaning.
Such materials often present the greatest risk of later dispute or quiet enclosure because:
a) their creation is collaborative; b) source materials may have different legal regimes; c) participants may assume shared purpose is enough to avoid documentation; and d) later success may increase the stakes of ownership and control.
Accordingly, the Corporation shall not accept ambiguity in jointly developed or mixed-origin assets where the asset is materially significant. It shall determine, as appropriate:
i) who owns which components; ii) what rights the Corporation receives or retains; iii) whether the asset is part of the core public-good estate, a controlled asset, or a more limited joint output; iv) what publication and release conditions apply; v) how future versions, forks, or repository moves will be governed; and vi) how the asset will be handled upon dispute, exit, restructuring, or successor transition.
The Corporation shall be especially careful not to let partner drafting convenience erode Part V. A joint asset touching the common rail, semantic baselines, or reference infrastructure shall not be placed under terms that effectively subordinate public-good continuity to partner commercial preference or ambiguous shared control.
Mixed-origin materials shall be governed with candor. If the asset contains components with incompatible licenses, uncertain ownership, or unresolved restrictions, the Corporation shall classify that as a governance problem, not merely a drafting inconvenience. No materially significant mixed-origin asset shall be allowed to function as canonical until its rights posture is sufficiently clear.
79.11 Interpretive Rule for IP Ownership and Stewardship Categories
This Section shall be interpreted to preserve a controlling proposition: the asset estate of GCRI US must be categorized, owned, custodied, and stewarded in a way that preserves public-good continuity, truthful provenance, canonical clarity, and lawful distinction among core, controlled, and third-party materials. Ambiguity about category is often the first step toward enclosure, drift, or governance confusion.
Where ambiguity exists, the interpretation that better preserves:
a) explicit rather than assumed ownership and custodial clarity; b) clear differentiation among core public-good assets, controlled assets, and third-party assets; c) stronger provenance and lineage discipline for drafts, code, semantic assets, and mixed-origin materials; d) institutional rather than personal or ad hoc custody of canonical assets; and e) constitutionally aligned treatment of jointly developed and derivative works
shall prevail unless a contrary result is required by law.
80. Canonical Public-Good Core Assets (GCRI United States)
80.1 Definition of Canonical Public-Good Core Assets
For purposes of these Bylaws, Canonical Public-Good Core Assets are those intellectual, technical, semantic, documentary, and governance-bearing assets within the remit of GCRI US that are so foundational to the Corporation’s public-benefit mission, public-good technical stewardship, institutional continuity, common-rail compatibility, and truthful public meaning that they must be governed under the strongest continuity, non-enclosure, provenance, and integrity disciplines of Part V. The structure of this Section follows the controlling Part V outline provided in the uploaded materials and is here fully adapted for GCRI US.
An asset shall be treated as canonical public-good core where one or more of the following conditions is met:
a) the asset materially defines or stabilizes the Corporation’s core semantic, methodological, technical, or governance architecture; b) the asset is necessary to preserve interoperability, reviewability, or continuity of the public-good core stewarded by the Corporation; c) the asset functions as an authoritative reference point for internal or external understanding of how the Corporation’s public-benefit systems, concepts, or processes work; d) the asset carries canonical lineage or status such that misleading variation, enclosure, or confusion would materially impair trust or institutional coherence; or e) the asset is so central to the Corporation’s stewardship role that its fragmentation, encumbrance, disappearance, or privatization would create constitutional risk rather than merely operational inconvenience.
Canonical public-good core assets are not defined by polish, age, or publicity alone. A highly visible publication may not be canonical if it is derivative or contextual. A technical schema, ontology fragment, governance matrix, or repository structure may be canonical even if few people outside specialist circles understand its importance. Canonicality is determined by functional constitutional significance.
The Corporation shall not use the word “core” loosely. Not every useful or mission-relevant asset belongs in this category. The category is reserved for assets whose governance conditions materially shape whether GCRI US remains able to steward a coherent public-good estate over time. Overclassification weakens discipline; underclassification invites quiet drift. The Corporation shall therefore apply this category with seriousness and reviewability.
Where doubt exists as to whether an asset is canonical public-good core, the Corporation shall err toward protective provisional classification pending recorded review rather than allowing a possibly core asset to remain governed as ordinary institutional material by default.
80.2 Scope of Core Assets Including Methods, Evidence Logic, Ontologies, Schemas, and Reference Implementations
The scope of canonical public-good core assets shall include, without limitation, those methods, evidence logics, ontologies, schemas, semantic baselines, mappings, taxonomies, reference implementations, governance-bearing technical structures, documentary baselines, and related assets that materially sustain the Corporation’s public-good technical and institutional architecture.
Core asset classes may therefore include:
a) canonical methods, frameworks, and process logics by which the Corporation structures evidence, observability, rights-aware review, public-benefit technical discipline, or institutional continuity; b) evidence logic and methodological baselines that materially determine how artifacts are classified, related, interpreted, or translated across the Corporation’s systems and outputs; c) ontologies, semantic models, data dictionaries, controlled vocabularies, schema families, taxonomies, mappings, and glossary structures that anchor common meaning or interoperability; d) reference implementations, base code, exemplar configurations, canonical documentation, or technical baselines that embody official public-good logic in executable or quasi-executable form; e) governance-bearing documentary assets, such as key templates, process instruments, record structures, and version-controlled constitutional forms, where these operate as essential institutional infrastructure; and f) authoritative repository structures, release patterns, provenance controls, and lineage maps without which the above assets cannot be stewarded reliably.
The Corporation shall recognize that the public-good core often exists less in a single document or repository than in a connected architecture of semantic, technical, and documentary assets. Canonicality may therefore attach to a set, family, lineage, or structured estate rather than only to a singular artifact. The Corporation shall govern such asset families accordingly, rather than treating each component as an isolated object divorced from its role in the whole.
At the same time, the Corporation shall distinguish between what is truly core and what is merely helpful, illustrative, local, provisional, experimental, or derivative. A white paper explaining a method may be important without itself being the canonical method asset. A local implementation profile may be valuable without displacing a canonical schema. A public-facing explainer may increase adoption without carrying the same stewardship weight as the underlying controlled vocabulary it describes. This distinction shall be made explicit in records, repositories, metadata, and release practice.
The Corporation shall not permit ambiguity in scope to be exploited by those seeking either to over-claim canonical status for non-core materials or to understate the canonical significance of assets whose enclosure or alteration would materially damage public-good continuity.
80.3 Controlled Vocabulary, Governance Semantics, and Core Technical Baselines as Protected Common Assets
The Corporation shall treat its controlled vocabulary, governance semantics, canonical naming logic, core classifications, repository-designating terms, and core technical baselines as protected common assets where they function as the shared language and structure of the public-good core. These assets are protected not because the Corporation seeks arbitrary exclusivity over language or technical logic, but because ungoverned alteration, misleading imitation, or proprietary capture of them would threaten continuity, interoperability, and truthful public meaning.
Protected common assets for purposes of this Section may include:
a) defined governance terms whose consistency is necessary to preserve institutional coherence across documents, repositories, technical systems, and public explanation; b) semantic baselines and canonical mappings that allow assets, records, and technical components to relate to one another predictably; c) naming conventions, release labels, status vocabularies, and public-trust indicators that distinguish authoritative from non-authoritative materials; d) core technical baselines, including reference patterns, authoritative schemas, and base interoperability logic, without which the Corporation’s public-good estate would lose stable internal relation; and e) documentary and metadata conventions that preserve provenance, version meaning, or custody significance.
These assets shall be treated as common in the constitutional sense that they must remain stewarded for public-good continuity rather than enclosed as private bargaining chips or repurposed as hidden institutional leverage. They are protected in the sense that the Corporation must guard them against misleading divergence, counterfeit canonical claims, semantically incompatible appropriation, and rights or licenses that would make them practically unavailable for the public-good role they are meant to serve.
The Corporation shall therefore not allow core semantic or technical baselines to be:
i) silently redefined through local practice; ii) embedded in proprietary packages in ways that make lawful review or compatibility impracticable; iii) rebranded as if they were private or partner-owned canonical systems; iv) exposed to ambiguous fork conditions that destroy confidence in what is authoritative; or v) governed through public descriptions so vague that the difference between canonical and non-canonical usage collapses.
Where the Corporation protects such assets through marks, licensing, repository rules, or clarifying notices, that protection shall be understood as stewardship of common infrastructure, not privatization of it.
80.4 No Transfer of Core Assets in a Way That Undermines Public-Benefit Access and Governance Continuity
GCRI US shall not transfer, assign, exclusively license, abandon, segregate, or otherwise dispose of canonical public-good core assets in any manner that would materially undermine public-benefit access, governance continuity, repository integrity, reviewability, interoperability, or future stewardship control consistent with these Bylaws.
This prohibition applies whether the transfer is:
a) explicit, through sale, exclusive assignment, or long-term exclusive control; b) indirect, through platform dependency or custody arrangements that deprive the Corporation of meaningful practical control; c) functional, through packaging or governance design that leaves the Corporation unable to steward the asset as a public-good core resource; or d) gradual, through repeated exceptions that cumulatively shift authority over the asset outside the Corporation’s constitutional frame.
The Corporation shall not transfer core assets merely because:
i) a partner offers scale, distribution, or capital; ii) a vendor environment appears more convenient; iii) joint development has made ownership politically awkward; iv) short-term institutional pressure makes exclusivity seem attractive; or v) a transition or restructuring scenario creates temptation to convert common assets into negotiable exit value.
Any movement of a core asset outside ordinary institutional custody must be judged by the stricter question: does this preserve or impair the ability of the asset to remain a stable, non-enclosed, public-good anchor over time? If the answer is impairment, the transfer shall not proceed absent extraordinary, recorded, and constitutionally defensible justification.
This clause does not prevent lawful backup, mirrored continuity, succession planning, or narrowly tailored stewardship-sharing arrangements. It does require that such arrangements be designed so that the public-good character of the asset survives them. Transfer is permissible only where stewardship continuity remains materially intact.
80.5 No Exclusive Licensing of Assets Essential to the Common Rail Without Exceptional Recorded Justification
The Corporation shall not grant exclusive licenses or equivalent exclusionary control rights over assets essential to the common public-good rail, except in truly exceptional circumstances supported by elevated review and recorded justification demonstrating that the exclusivity:
a) is narrowly tailored; b) does not materially enclose or fracture the common rail; c) does not undermine interoperability, reviewability, or future stewardship continuity; d) is necessary for reasons superior to the default non-enclosure rule; and e) is compatible with mission lock, public-benefit distinctness, and the Corporation’s non-extractive posture.
Assets essential to the common rail may include canonical schemas, semantic baselines, core methods, reference implementations, critical repository structures, public-trust labels tied to core meaning, and other assets whose openness or governed accessibility is necessary for coherent public-good function. Exclusive licensing of such assets is presumptively disfavored because it converts shared infrastructure into privileged access.
Exceptional justification shall not be satisfied by ordinary arguments of commercial attractiveness, partner preference, negotiation leverage, speed, or institutional optionality. It must show why exclusivity is necessary to preserve something constitutionally superior to the non-enclosure baseline, such as:
i) protection against a grave integrity threat; ii) rights or security concerns that cannot be addressed by narrower means; iii) temporary transition conditions necessary to prevent loss of the asset; or iv) another comparably weighty ground consistent with these Bylaws.
Where exclusivity is exceptionally approved, the Corporation shall record:
the precise asset or asset scope affected;
the duration and limits of exclusivity;
the reasons less restrictive alternatives were insufficient;
continuity and exit protections; and
the conditions under which the asset returns fully to ordinary public-good stewardship posture.
No exclusive arrangement shall be permitted to survive as a vague, open-ended, or under-documented deviation from the core constitutional rule. Exceptional means exceptional, bounded, reviewable, and hard to normalize.
80.6 Duty to Preserve Continuity, Compatibility, and Traceable Lineage of Canonical Assets
The Corporation shall maintain an affirmative duty to preserve the continuity, compatibility, and traceable lineage of all canonical public-good core assets. A canonical asset does not remain canonical merely by being declared so. It remains canonical only if its versions, repository states, derivative relations, custodial movements, and supersession history remain knowable and governable over time.
This duty requires, as appropriate:
a) designation of an authoritative source or repository of record; b) clear versioning, release, and change-control discipline; c) preservation of compatibility statements, divergence logs, and migration notes where material changes occur; d) traceable relation between drafts, releases, derivatives, localized adaptations, and superseding versions; e) prevention of unofficial or misleading “latest” claims that bypass authoritative lineage; and f) continuity planning so that personnel turnover, infrastructure change, partnership exit, or legal stress does not break access to authoritative history.
The Corporation shall also preserve compatibility in the deeper semantic sense. Canonical continuity is not only file continuity. It includes maintenance of intelligible relation among terms, schemas, mappings, repository states, and official documentation. A new version that breaks common meaning without recorded explanation may be technically newer but institutionally defective.
Traceable lineage shall be sufficient that the Corporation, and where appropriate the relevant protected public, can determine:
i) what the authoritative asset is; ii) what it was before; iii) what changed and why; iv) whether an adaptation remains compatible, partially compatible, or non-equivalent; and v) whether any competing asset claim is spurious or merely local.
The Corporation shall not permit convenience publishing, informal forking, undocumented partner edits, or unmanaged repository sprawl to erode this lineage duty. Canonical assets must be history-bearing, not merely presently available.
80.7 Recordkeeping and Repository Control for Canonical Assets
All canonical public-good core assets of GCRI US shall be subject to strict recordkeeping and repository control sufficient to preserve authenticity, authoritative status, change discipline, access control, continuity, and proof against counterfeit or misleading claims. Repository control for canonical assets is not an engineering convenience. It is a constitutional control surface under Part V.
This means the Corporation shall, for canonical assets:
a) designate authoritative repositories or custodial locations; b) distinguish authoritative copies from mirrors, working branches, forks, snapshots, or local adaptations; c) preserve release approvals, provenance markers, and authorship or contribution metadata to the degree appropriate; d) control write authority, merge authority, and release authority through defined institutional roles rather than informal convenience; e) maintain archival and recovery logic sufficient to survive system or personnel failure; and f) document material repository moves, restructurings, splits, or custodial transitions.
The Corporation shall not allow canonical assets to be governed through informal digital habits such as:
i) “latest version” living in unmanaged shared drives; ii) public release through non-authoritative channels without repository linkage; iii) partner mirrors becoming de facto authoritative by convenience; iv) untracked branch divergence later treated as official; or v) reliance on individual custodians without institutional fallback.
Where canonical assets must, for practical reasons, be mirrored or distributed across systems, the Corporation shall preserve enough repository discipline that there is never serious ambiguity about what controls, what is derivative, and what the public or contributors may safely rely upon.
Repository governance shall also be coordinated with Parts III and IV where rights-sensitive or controlled assets are implicated, so that canonical integrity and protective handling do not diverge into incompatible systems.
80.8 Public Clarification Duties Where Competing Claims to Canonical Assets Arise
If competing, misleading, ambiguous, or conflicting claims arise concerning which asset, repository, schema, document, semantic baseline, code branch, or technical artifact is canonical, GCRI US shall undertake a duty of public or controlled clarification proportionate to the seriousness of the confusion. The Corporation shall not allow ambiguity about canonical status to persist where that ambiguity could materially impair trust, interoperability, contribution discipline, public meaning, or stewardship continuity.
Competing claims may arise where:
a) a derivative or localized asset is presented as though it were the authoritative core asset; b) an old version continues to circulate without proper supersession markings; c) a partner, host, vendor, or contributor presents a mixed-origin or jointly developed work as the canonical baseline; d) a fork, mirror, or unofficial repository acquires practical visibility that outpaces the repository of record; or e) public descriptions, platform design, or naming conventions allow reasonable observers to mistake non-canonical assets for canonical ones.
In such cases, the Corporation may need to:
i) issue a clarifying notice, statement, or repository designation; ii) update metadata, labels, or release notes; iii) correct partner or third-party descriptions; iv) distinguish clearly between authoritative, derivative, experimental, and historical versions; v) take enforcement or takedown steps where marks, public meaning, or stewardship integrity are being misused; and vi) preserve a record of the clarification sufficient for future audit and recurrence prevention.
The Corporation shall not assume that technical insiders will “know the difference” and therefore no clarification is needed. Canonical confusion often damages governance precisely because different audiences rely on different signals. Public clarification is therefore part of stewardship, not merely communications hygiene.
Where a full public clarification would itself create rights, security, or controlled-handling concerns, the Corporation shall still produce the most truthful and safe bounded clarification possible under the circumstances.
80.9 Interpretive Rule for Canonical Public-Good Core Assets
This Section shall be interpreted to preserve a controlling proposition: canonical public-good core assets are the assets whose continuity, integrity, non-enclosure, authoritative lineage, and repository discipline are most essential to preserving GCRI US as a steward of coherent public-good infrastructure. They must therefore be governed more carefully than ordinary institutional materials.
Where ambiguity exists, the interpretation that better preserves:
a) careful and reviewable identification of canonical public-good core assets; b) protection of controlled vocabulary, governance semantics, and core technical baselines as common assets; c) continuity, compatibility, and lineage of authoritative assets over time; d) resistance to transfer, exclusivity, or confusion that would impair the common rail; and e) clear public or controlled clarification where competing canonical claims arise
shall prevail unless a contrary result is required by law.
81. Licensing Model and Public-Good Use Rights (GCRI United States)
81.1 Licensing Philosophy for GCRI US Outputs and Assets
The licensing philosophy of GCRI US shall be governed by a single constitutional proposition: licenses exist to preserve public-good continuity, lawful reuse, reviewability, integrity, and mission-faithful stewardship—not to maximize exclusion, create hidden tollbooths, or convert core institutional assets into private bargaining instruments. Every licensing decision taken by or on behalf of the Corporation shall therefore be interpreted through the hierarchy already established in Parts I through V: mission lock, public-benefit distinctness, non-execution, non-enclosure, continuity of the common rail, safeguards protection, and truthful public meaning.
The Corporation shall not treat licensing as a purely technical legal form selected after the substantive asset decision has already been made. Licensing is itself a governance surface. It determines:
a) who may access and use an asset; b) whether an asset can be reviewed, audited, replicated, or adapted; c) whether interoperability remains practically possible; d) whether provenance, attribution, and integrity can be preserved; e) whether the Corporation’s public-good core remains open enough to avoid enclosure while still protected enough to avoid misuse, confusion, or rights harm; and f) whether future contributors, partners, hosts, successors, and the public inherit a coherent stewardship regime or a fragmented and contradictory one.
Accordingly, GCRI US shall approach licensing by first asking what constitutional function the asset serves. A canonical schema, ontology, governance template, reference implementation, or public-good technical baseline is not to be licensed according to the same logic as a restricted security-sensitive artifact, a trust-bearing badge, or a controlled internal record. Licensing must track stewardship category, not merely convenience or prevailing ecosystem fashion.
The Corporation shall also recognize that license selection can silently reconfigure institutional posture. A permissive form used where continuity or provenance discipline is essential may allow fragmentation. An overly restrictive form used for core public-good infrastructure may create enclosure by friction rather than by explicit prohibition. Licensing philosophy under this Part therefore rejects both carelessness and opportunism. The right license is the one that most faithfully carries forward the constitutional role of the asset.
81.2 Open Licensing as the Default for Public-Good Technical and Documentary Assets, Subject to Safeguards
For public-good technical and documentary assets that are properly classified as open or public-facing under these Bylaws, open licensing shall be the default posture, subject always to rights, safeguards, controlled-handling, marks-integrity, and non-misrepresentation requirements. Open licensing under this Part is not an aesthetic preference or a generic innovation slogan. It is the legal expression of the Corporation’s public-benefit stewardship posture for assets whose mission function depends on lawful accessibility, reviewability, and reuse.
Open licensing shall generally be presumed appropriate for asset classes such as:
a) public-good technical reference assets and reference implementations; b) canonical or non-canonical documentation intended for public learning, review, or interoperability use; c) schemas, taxonomies, glossaries, mappings, and ontological assets intended to support lawful public-good coordination; d) public guidance, methods papers, technical notes, educational materials, and non-sensitive governance-facing templates; and e) other assets whose wider lawful reuse supports mission, transparency, public-benefit adoption, and continuity of the common rail.
This default shall not be construed as requiring publication or open licensing of everything the Corporation creates. The default applies only once the asset has been properly classified as suitable for such treatment. Rights-bearing, security-sensitive, community-sensitive, Indigenous-sensitive, retaliation-sensitive, or otherwise restricted assets remain governed by the controlled-handling and restricted-licensing logic elsewhere in this Part and in Part IV.
Where open licensing is the default, the Corporation shall still ensure that the selected form:
i) preserves provenance and attribution discipline; ii) does not create hidden incompatibility with other core public-good assets; iii) does not undermine controlled vocabulary or canonical clarity; iv) does not accidentally authorize misleading use of marks, status claims, or false endorsement; and v) does not defeat the Corporation’s ability to issue corrections, clarifications, or superseding versions in a disciplined way.
The Corporation shall not retreat from open licensing merely because a more restrictive posture appears strategically stronger in the short term. Nor shall it use open licensing performatively while surrounding the asset with platform friction, undocumented barriers, or confusing release practices that make lawful reuse difficult in practice. Open licensing must be real in effect, not rhetorical in posture.
81.3 Controlled Licensing for Sensitive, Restricted, or Rights-Bearing Materials
Where an asset is sensitive, restricted, rights-bearing, security-sensitive, community-sensitive, Indigenous-sensitive, retaliation-sensitive, mark-sensitive, or otherwise unsuitable for ordinary open release, GCRI US shall apply controlled licensing or equivalent restrictions proportionate to the reasons the asset cannot be governed through the open default. Controlled licensing is not a departure from public-good stewardship. It is often the correct form of stewardship where open release would produce harm, false inference, unsafe exposure, or constitutional confusion.
Controlled licensing may be required, among other things, for:
a) assets whose disclosure or reuse would materially increase rights risk, retaliation risk, or community harm; b) technical materials that could be abused if widely distributed without context or restriction; c) materials whose handling is governed by controlled-room or need-to-know conditions; d) trust-bearing assets such as marks, seals, badges, labels, and related public signals; e) mixed-origin or third-party-incorporated materials whose use rights are themselves limited; and f) high-consequence internal or cross-entity materials whose institutional meaning would be distorted by unbounded circulation.
Controlled licensing may include, as appropriate:
i) use limitations; ii) no-redistribution or bounded-redistribution terms; iii) no-modification or integrity-preservation clauses where lawful and justified; iv) restricted class-of-user access; v) purpose-bound licensing; vi) requirement of contextual notices or controlled-handling obligations; and vii) explicit reservations regarding marks, endorsement, status signaling, or derivative canonical claims.
The Corporation shall not overuse controlled licensing as a convenience substitute for ordinary public-good openness. Restrictions must be grounded in actual risk, stewardship needs, or constitutional duties—not in vague caution, partner pressure, or preference for tighter organizational control. At the same time, the Corporation shall not force open licensing onto assets that cannot be safely governed that way without violating Part IV or distorting public meaning.
Where controlled licensing is chosen, the Corporation shall ensure that the specific restriction corresponds to the actual risk or stewardship issue, rather than bundling broad unnecessary prohibitions into the license simply because stronger control feels safer.
81.4 Criteria for Selecting License Types by Asset Class
GCRI US shall select license types and licensing structures according to asset class, constitutional function, sensitivity profile, interoperability needs, provenance requirements, and continuity implications, not by administrative habit alone. License selection shall therefore be a reasoned governance act rather than a default administrative template.
In choosing among licensing approaches, the Corporation shall consider, as appropriate:
a) whether the asset is core public-good infrastructure, supportive public-good material, controlled material, mark-bearing material, or mixed-origin material; b) whether the asset’s constitutional role depends on broad lawful reuse, narrow contextual use, or controlled access; c) whether reuse, adaptation, or forkability would strengthen public-good continuity or instead create semantic fracture, integrity risk, or public confusion; d) whether the asset includes third-party components or dependencies affecting permissible licensing; e) whether attribution, provenance, or compatibility requirements are central to the asset’s stewardship; and f) whether the asset’s handling is constrained by rights, privacy, security, community trust, or other Part IV concerns.
Accordingly, the Corporation shall avoid undifferentiated licensing practices such as:
i) applying the same permissive license to every technical artifact regardless of function; ii) applying blanket proprietary restrictions to all documentation or code because some subset is sensitive; iii) using marks terms as if they governed technical asset rights generally; or iv) accepting partner-proposed license structures without review against this Part.
License selection criteria shall also account for future institutional conditions. A license that appears acceptable under current personnel or repository conditions may prove destructive in a successor, fork, insolvency, partner exit, or platform migration scenario. The Corporation shall therefore select forms that remain mission-faithful not only today but under foreseeable institutional stress.
Where a chosen license departs from what would ordinarily be expected for that asset class under this Part, the departure shall be recorded together with the specific reason for it.
81.5 Compatibility With Open-Source and Open-Knowledge Ecosystems
GCRI US shall maintain compatibility, to the greatest extent consistent with mission and safeguards, with legitimate open-source and open-knowledge ecosystems. The Corporation’s public-good stewardship duty includes ensuring that its technical and documentary assets can, where appropriate, lawfully interact with, build upon, and contribute to broader communities of review, learning, interoperability, and collective improvement.
Compatibility in this sense includes:
a) legal compatibility of chosen licenses with common open-source or open-knowledge usage patterns where appropriate; b) practical compatibility through documentation, repository access, and provenance clarity; c) semantic compatibility through controlled vocabulary and non-fracturing adaptation logic; and d) contribution compatibility through acceptance of lawful and appropriately governed external participation.
The Corporation shall not treat ecosystem compatibility as an automatic duty overriding all other concerns. A rights-sensitive or security-sensitive asset may properly remain outside ordinary open collaboration. A trust-bearing mark may need tighter control than underlying code or documentation. Compatibility must remain subordinate to safeguards and integrity. But where no such stronger reason exists, the Corporation shall prefer not to create unnecessary incompatibility with legitimate open ecosystems.
This means the Corporation shall avoid:
i) custom licensing or access structures that create needless friction for lawful public-good reuse; ii) platform or packaging choices that artificially isolate assets from common open workflows; iii) license combinations that silently make interoperation impractical; and iv) semantic or documentary opacity that makes technically “open” assets functionally closed.
The public-good value of GCRI US’s asset estate depends in part on whether others can truthfully and safely understand, examine, and work with it. Compatibility is therefore not merely a community-relations choice. It is one of the operating conditions of non-enclosure.
81.6 No License Terms That Defeat Interoperability, Reviewability, or Lawful Public-Good Reuse
The Corporation shall not adopt, impose, or tolerate license terms that defeat interoperability, reviewability, or lawful public-good reuse of assets whose constitutional role depends on those qualities. A license that is formally “available” but practically blocks lawful understanding, integration, correction, migration, or review is inconsistent with this Part where the asset belongs to the public-good core or to public-good-supporting categories.
Prohibited licensing effects may include, among other things:
a) restrictions that prevent lawful compatibility with other public-good core assets; b) terms that make it impossible or impractical to inspect, compare, or verify canonical logic; c) anti-adaptation clauses applied to assets whose lawful localization or bounded adaptation is necessary to the public-benefit function of the ecosystem; d) hidden restrictions embedded in delivery mechanism, account gating, or contractual wrappers that are inconsistent with the apparent openness of the license; and e) licensing structures that, in practice, privilege a single platform, vendor, or institutional actor as the only feasible point of lawful use.
The Corporation shall distinguish between legitimate integrity protections—such as prevention of false canonical claims, misleading mark use, or unsafe derivative presentation—and overbroad restrictions that effectively enclose the asset. Integrity protection is permissible. Functional anti-public-good friction is not.
Where there is tension between a proposed license term and the public-good role of the asset, the Corporation shall adopt the narrower term that adequately protects legitimate interests without collapsing interoperability or lawful reuse. If no such narrowing is possible, the asset classification or release posture itself may need to be revisited.
81.7 No Hidden Restriction Through Packaging, Terms of Access, or Platform Friction
GCRI US shall not create hidden restriction through packaging, access pathways, technical gating, approval rituals, opaque terms of access, vendor lock-in, platform friction, or undocumented administrative barriers where the formal license appears more open than the actual experience of lawful use. Hidden restriction is constitutionally problematic because it allows the institution to claim openness while functionally reproducing enclosure.
Hidden restriction may arise where:
a) a permissively licensed asset is available only through cumbersome or controlled access pathways; b) source materials are nominally open but critical documentation, version history, or dependencies are withheld; c) platform terms or account requirements create barriers inconsistent with the apparent license posture; d) the Corporation uses packaging or distribution practice to make lawful reuse difficult without ever openly restricting it; or e) derivative notices, access click-throughs, or side-channel conditions quietly narrow what the public-facing license suggests is allowed.
The Corporation shall ensure that the practical conditions of access, retrieval, review, and lawful reuse are broadly consistent with the licensing posture represented. This does not prohibit reasonable technical safeguards, anti-abuse measures, repository integrity controls, or download management. It does prohibit using those tools as disguised substitutes for a more restrictive license the Corporation would not openly defend under this Part.
Where technical, security, or operational realities require friction beyond what would ordinarily accompany an open asset, the Corporation shall either:
i) justify and record the reason clearly; ii) reclassify the asset more honestly; or iii) redesign access so that the friction no longer undermines the represented use rights.
A public-benefit steward must not rely on legal openness paired with practical inaccessibility as a means of controlling what it is unwilling to openly restrict.
81.8 License Notices, Attribution, and Provenance Requirements
All assets released, shared, or otherwise made available by GCRI US shall carry clear license notices, attribution rules, and provenance requirements sufficient to preserve truthful public meaning, lawful reuse, and traceable lineage. The Corporation shall not permit assets—especially core or publicly relied-upon assets—to circulate without enough information for recipients to know what they may use, under what terms, and from what authoritative or non-authoritative source the asset derives.
License notices shall, as appropriate:
a) identify the governing license or access terms; b) indicate whether the asset is canonical, derivative, historical, experimental, restricted, or otherwise specially classified; c) state what integrity, attribution, or mark-related limitations apply; and d) provide enough reference to provenance that the user can determine the asset’s relation to the authoritative estate.
Attribution requirements shall be designed to preserve provenance and truthful credit, not to create artificial barriers to lawful use. They may include, where appropriate:
i) naming GCRI US as steward or authoring institution; ii) preserving contributor acknowledgment where consistent with contributor terms and safety; iii) identifying mixed-origin or third-party components; and iv) preventing the removal of provenance notices necessary to avoid misleading canonical claims.
Provenance requirements are especially important for public-good core and derivative assets. Without provenance, an adapted asset may be mistaken for a canonical one, a third-party component may be falsely absorbed into GCRI’s estate, or an outdated historical version may be treated as current. The Corporation shall therefore treat provenance metadata and notices as mandatory control fields for serious release practice, not as optional documentation niceties.
81.9 Reservation of Rights Where Necessary for Integrity, Marks, or Safeguards
Nothing in the open-licensing and public-good-use-rights posture of this Part shall prevent GCRI US from reserving rights where such reservation is necessary to protect:
a) integrity of canonical assets; b) truthful public meaning and non-misrepresentation; c) marks, seals, badges, labels, or other trust-bearing signals; d) rights-bearing, community-sensitive, Indigenous-sensitive, privacy-sensitive, or security-sensitive materials; or e) other constitutionally recognized safeguards under Parts II through IV.
Such reservation of rights may include, as appropriate:
i) prohibition on false claims of endorsement, approval, or canonical status; ii) restriction on use of marks or trust signals even where the underlying technical material is more openly licensed; iii) controlled handling or no-redistribution for sensitive materials; iv) limits on derivative presentation where the derivative would likely mislead as to source or status; and v) rights retained to correct, clarify, supersede, or withdraw materials in ways consistent with this Part.
The Corporation shall, however, ensure that reserved rights remain narrowly connected to legitimate integrity or safeguards interests. Reserved rights shall not become an all-purpose mechanism for recreating de facto enclosure around public-good core assets. A reservation justified by marks integrity is not a license to control all lawful technical reuse. A reservation justified by rights-sensitive handling is not a license to suppress unrelated critical review. The constitutional discipline of this Part requires fit between the right reserved and the interest protected.
Where a reservation is broader than ordinary practice for the relevant asset class, the reason for that breadth shall be recorded and reviewable.
81.10 Review and Change Control for Licensing Decisions Affecting Core Assets
Any licensing decision that materially affects canonical public-good core assets, or any class of assets central to continuity, interoperability, public meaning, or non-enclosure, shall be subject to review and change control proportionate to the significance of the asset and the materiality of the licensing effect. The Corporation shall not allow core-asset licensing posture to change casually through repository default, partner insistence, developer convenience, platform migration, or administrative oversight.
Review shall, as appropriate, consider:
a) whether the proposed license posture remains compatible with the asset’s stewardship category; b) whether it preserves interoperability, reviewability, and non-enclosure; c) whether it creates unexpected third-party or partner leverage; d) whether it affects contribution acceptance or future successor stewardship; and e) whether rights, safeguards, or marks concerns justify a more controlled posture.
Change control shall require enough documentation to determine:
i) what the prior license posture was; ii) what is changing; iii) why the change is proposed; iv) who approved it; and v) what compatibility or continuity implications follow.
The Corporation shall not treat license changes affecting core assets as mere legal housekeeping. They are constitutional events within the logic of Part V because they alter the terms on which the common public-good estate may be used, trusted, and sustained. If the Corporation cannot explain a material license change in stewardship terms, the change should not be made.
81.11 Interpretive Rule for Licensing Model and Public-Good Use Rights
This Section shall be interpreted to preserve a controlling proposition: licensing in GCRI US is a stewardship instrument. It must keep public-good core assets lawfully reusable, reviewable, interoperable, and non-enclosed, while still protecting marks, integrity, and rights-sensitive materials where narrower control is genuinely required.
Where ambiguity exists, the interpretation that better preserves:
a) open licensing as the default for true public-good technical and documentary assets; b) narrow, justified controlled licensing for sensitive or restricted materials; c) compatibility with legitimate open-source and open-knowledge ecosystems; d) freedom from hidden restrictive friction inconsistent with apparent openness; and e) disciplined review of any license change affecting canonical core assets
shall prevail unless a contrary result is required by law.
82. Contributor Declarations and Contribution Terms (GCRI United States)
82.1 Requirement for Contributor Terms for All Material Contributions
GCRI US shall require Contributor Terms or functionally equivalent written contribution conditions for all material contributions to the Corporation’s technical, semantic, documentary, governance, repository, data-dictionary, mark-adjacent, or other intangible asset estate. The Corporation shall not accept, merge, operationalize, publish, or otherwise rely upon material contributed assets on the basis of goodwill, informal understanding, email acquiescence, workshop atmosphere, or assumed mission alignment alone. The governing structure for this Section follows the Part V outline supplied in the uploaded material and is here fully adapted for GCRI US.
This requirement exists because the public-good nature of the Corporation’s work does not reduce the need for rights clarity. It increases it. Without contributor terms, the Corporation risks:
a) unclear authority to use, publish, adapt, or steward the contribution; b) hidden third-party encumbrances; c) later disputes over ownership, attribution, or withdrawal; d) contamination of core assets by incompatible rights or restrictions; e) inability to preserve continuity through repository moves, successor stewardship, or derivative adaptation; and f) false assumptions that “voluntary contribution” means unrestricted institutional use.
Contributor Terms shall therefore be required wherever a contribution is more than trivial in constitutional, technical, or stewardship significance. The Corporation shall not excuse the absence of such terms merely because the contributor is trusted, senior, mission-aligned, academic, volunteer, donor-adjacent, or already known to the institution. The more important the contribution, the more necessary the written terms.
This rule does not require that every contribution agreement take the same form. It does require that every material contribution be governed by enough written structure to establish:
i) what is being contributed; ii) under what legal and stewardship terms; iii) what representations the contributor makes; iv) what rights GCRI US receives or preserves; and v) what restrictions, dependencies, or attribution conditions attach.
Where a material contribution has already been received without adequate terms, the Corporation shall treat that gap as a governance defect requiring cure, re-documentation, narrowing of use, or, if necessary, non-acceptance into the authoritative asset estate.
82.2 Scope of Contributions Covered
The Contributor Terms requirement shall apply to all material contributions to GCRI US, whether contributed directly, through repositories, through workshops or collaborations, through academic or volunteer channels, through partner interfaces, or through commissioned or semi-formal development arrangements. The Corporation shall interpret “contribution” broadly enough to prevent significant assets from entering the institutional estate through procedural side doors.
Contributions covered by this Section may include, without limitation:
a) source code, scripts, modules, configurations, documentation, tests, models, and technical artifacts; b) ontologies, taxonomies, schemas, mappings, vocabularies, data dictionaries, glossary entries, or semantic logic; c) governance drafts, templates, forms, procedural instruments, methodologies, matrices, or reference texts; d) research drafts, working papers, publications, explanatory materials, educational assets, and technical notes; e) design systems, diagrams, visual identity materials, badge frameworks, naming structures, or public-description elements; f) curated datasets, structured repositories, metadata schemes, provenance structures, or documentary compilations, subject also to Part IV and Section 79 distinctions concerning rights-bearing data; and g) derivative, adapted, localized, translated, or composite works offered into the Corporation’s repositories or official workstreams.
The Corporation shall not limit the scope of this Section to “code contributions” in the narrow software sense. A seemingly modest semantic contribution may carry more constitutional significance than a routine code patch. A governance template may become more central to institutional continuity than a large but non-canonical document set. Coverage under this Section turns on material significance, not on technical genre alone.
The Corporation may determine that some trivial, non-original, or purely administrative inputs do not require full contributor terms treatment. But wherever a contribution could reasonably affect ownership clarity, licensing posture, canonical continuity, provenance, public meaning, repository integrity, or rights compatibility, the safer presumption shall be that this Section applies.
82.3 Warranties of Authority, Originality, and Rights to Contribute
Every contributor making a material contribution to GCRI US shall provide warranties or representations, proportionate to context and contribution type, regarding authority, originality, and rights to contribute. The purpose of these warranties is not adversarial distrust. It is institutional clarity. A public-good steward cannot safely incorporate material into its core estate unless it has reasonable grounds to believe the contributor had the right to provide it.
Such contributor warranties shall address, as appropriate:
a) that the contributor has authority to make the contribution under the applicable legal and institutional circumstances; b) that the contribution is original to the contributor or lawfully derived in a manner that permits the proposed contribution; c) that any incorporated third-party materials have been disclosed and are lawfully includable; d) that the contributor is not breaching employer, funder, partner, host, academic, confidentiality, or other obligations by making the contribution; and e) that the contribution does not carry hidden encumbrances inconsistent with the declared contribution terms.
The Corporation shall not interpret these warranties mechanically. In some cases, especially academic, volunteer, or mixed-institution settings, full originality may not be the relevant representation. Lawful authority and proper disclosure may matter more. The key is that the Corporation must know enough to govern the contribution responsibly.
Where the contributor cannot warrant full originality because the work incorporates preexisting materials, collaborative inputs, public standards, or third-party open components, that fact shall not bar the contribution automatically. It shall, however, trigger heightened disclosure and review so that GCRI US does not absorb rights ambiguity into its authoritative estate by accident.
False or materially incomplete warranties may constitute grounds for rejection, revocation, corrective action, repository removal, or further escalation under this Part.
82.4 Disclosure of Third-Party Dependencies, Restrictions, and Encumbrances
Contributors shall disclose all material third-party dependencies, restrictions, encumbrances, incorporated components, license obligations, access limits, or other conditions that may affect the Corporation’s ability to lawfully use, release, adapt, steward, or rely upon the contribution. The Corporation shall not accept contributions into its material asset estate on the assumption that undisclosed restrictions either do not exist or can be solved later without consequence.
Disclosure obligations may include, as appropriate:
a) incorporation of third-party code, libraries, modules, standards text, diagrams, figures, templates, datasets, or documentation; b) use of materials subject to copyright, license, patent, or database-right limitations; c) employer or institutional claims that might affect ownership or licensing; d) confidentiality or non-disclosure constraints; e) funder, partner, academic, or host conditions affecting publication or reuse; and f) patent, royalty, copyleft, attribution, or redistribution obligations that attach to all or part of the contribution.
The Corporation shall require sufficient disclosure not only to know that a dependency exists, but to understand whether the dependency is compatible with the stewardship category of the receiving asset. A third-party component may be fully acceptable in a controlled asset while being incompatible with a canonical public-good core asset. A documentation excerpt may be fair and lawful for internal review while being unsuitable for official release. Disclosure is necessary so that those distinctions can be made consciously.
The contributor’s duty is to disclose. The Corporation’s duty is to review. Neither side may rely on deliberate vagueness as a substitute for governance. If the contribution enters the institutional estate under hidden encumbrance, the damage may be structural and long-lasting. Part V is designed to prevent that.
82.5 Agreement to License Terms, Attribution Rules, and Integrity Protections
Every material contribution shall be made subject to explicit agreement regarding the applicable license terms, attribution rules, and integrity protections that will govern the contribution once accepted into GCRI US’s asset estate or repositories. Contributors shall not be left to assume that contribution means only one thing, and the Corporation shall not rely on ambiguity to enlarge its position after the fact.
Accordingly, Contributor Terms shall establish, as appropriate:
a) whether the contribution is assigned, licensed, or stewarded under another permitted legal structure; b) what reuse, adaptation, and publication rights GCRI US receives; c) what license or license family will apply once the contribution is incorporated into a relevant asset class; d) what attribution the contributor may expect and under what limits; and e) what integrity protections apply, including non-misrepresentation, provenance preservation, and limits on false canonical claims.
Integrity protections are especially important for public-good infrastructure. The Corporation may need to adapt, refactor, localize, redact, or supersede contributions over time. Contributors shall therefore understand that preservation of attribution is not the same as preservation of exact form or perpetual prominence. Likewise, the Corporation shall understand that public-good stewardship does not authorize it to erase provenance or misstate the origin and lineage of material contributions.
This clause also protects contributors by making clear what they are and are not giving. A person contributing to an ontology, schema, paper, repository, or governance instrument should not later discover that the Corporation treated the contribution as something categorically different from what the written terms described. Clarity is therefore in the interest of both institutional continuity and contributor fairness.
82.6 Contributor Duty to Avoid Malware, Hidden Dependencies, and License Incompatibilities
Every contributor of material technical, documentary, semantic, or repository-bound content shall bear a duty to avoid introducing malware, malicious logic, hidden dependencies, insecure components, incompatible licenses, undisclosed external calls, unsafe telemetry, or other hidden conditions that would materially impair the Corporation’s security, integrity, continuity, or public-good stewardship obligations.
This duty is not confined to software in the narrow sense. It applies, as relevant, to:
a) code and software packages; b) build scripts, automation pipelines, deployment logic, and configuration files; c) models, prompts, embedded references, or generated artifacts carrying external dependency assumptions; d) documentation or templates containing embedded external rights burdens or unsafe links; and e) semantic or data assets whose use depends on hidden proprietary or controlled infrastructure.
The contributor shall not:
i) bury legal or technical dependence in a way that is hard to detect; ii) include code or logic sourced from unknown or untrusted origins without disclosure; iii) structure contributions so that the Corporation becomes dependent on unstated external services or accounts; iv) include components known to create mission-incompatible or public-good-incompatible license effects; or v) present a contribution as self-contained when in fact its safe or lawful use depends on external conditions not disclosed.
The Corporation shall not rely solely on the contributor’s assurances here. But the contributor’s duty matters because intentional or negligent concealment of such issues can impose severe costs on the institutional estate. Public-good stewardship is impossible if the Corporation’s core assets are seeded with hidden traps—legal, technical, or both.
82.7 Contribution Review, Acceptance, Rejection, and Revocation Rules
All material contributions shall be subject to review, acceptance, rejection, and, where necessary, revocation rules proportionate to their significance, sensitivity, and effect on the Corporation’s asset estate. Contribution does not become part of the authoritative institutional estate merely because it was submitted or because a maintainer found it useful. It becomes part of that estate only through proper review and acceptance.
Review shall consider, as appropriate:
a) whether the contribution fits the relevant asset class and stewardship category; b) whether contributor authority and third-party disclosures are sufficient; c) whether licensing and provenance are compatible with the target asset; d) whether the contribution introduces security, integrity, semantic-fracture, or public-meaning risk; and e) whether the contribution should enter a canonical, derivative, experimental, local, or restricted branch of the estate.
Acceptance shall be recorded to a degree proportionate to significance. The Corporation shall preserve enough record to determine who accepted the contribution, into what class of asset or repository, under what rights basis, and under what release or handling posture.
Rejection may be appropriate where:
i) the rights posture is unclear; ii) the contribution is incompatible with the asset’s licensing or stewardship conditions; iii) the contribution creates material security, legal, or mission risk; iv) provenance is materially incomplete; or v) the contribution would distort canonical continuity or public meaning.
Revocation or withdrawal after acceptance may be required where the contribution is later found to carry false warranties, hidden encumbrances, malware, mission-incompatible licensing, rights-sensitive defects, or materially misleading provenance. Revocation shall be governed by fairness, traceability, and continuity logic. The Corporation shall not quietly remove material from authoritative histories in ways that obscure what occurred, but it shall act decisively where continued presence of the contribution would compromise the estate.
82.8 Special Rules for Volunteer, Academic, Partner, and Contractor Contributions
Because GCRI US will often receive material contributions through volunteer, academic, partner, contractor, fellowship, and other mixed-institution channels, the Corporation shall maintain special rules ensuring that such contexts do not become loopholes through which major rights uncertainty enters the public-good core.
For volunteer contributions, the Corporation shall ensure that good-faith informality does not substitute for contributor clarity. Volunteers may be mission-aligned yet still lack authority to contribute certain materials or may misunderstand how their contribution will be used.
For academic contributions, the Corporation shall account for employer rights, institutional IP policies, publication expectations, authorship norms, funding disclosures, and academic-freedom-related constraints. Academic collaboration shall not be treated as automatically equivalent to unrestricted institutional assignment.
For partner contributions, the Corporation shall be especially alert to hidden commercial interests, exclusivity assumptions, background IP claims, and mixed-governance ambiguity. A partner contribution may be valuable while still being constitutionally unsuitable for canonical incorporation if its terms would compromise the public-good core.
For contractor contributions, the Corporation shall not assume work-for-hire language alone resolves every issue. It shall also address preexisting materials, open-source dependencies, attribution, continuity, documentation sufficiency, and repository integration.
These special rules do not create weaker governance. They require stronger fit-for-context governance. Mixed-origin contribution channels are often where the most important public-good assets are born—and where the greatest long-term ambiguity risks enter. The Corporation shall therefore govern these channels with heightened clarity rather than relaxed oversight.
82.9 Moral Rights, Attribution Integrity, and Waiver Limits
The Corporation shall address moral rights, attribution integrity, and any waiver limits applicable under the governing legal context in a manner consistent with both contributor fairness and the Corporation’s need to steward, adapt, correct, supersede, localize, and preserve continuity of its public-good asset estate.
This means, as appropriate, that Contributor Terms shall:
a) preserve truthful attribution where appropriate and safe; b) clarify whether, and to what extent, adaptation, editing, translation, or technical modification may occur; c) ensure that contributors do not later claim that ordinary stewardship actions are per se impermissible distortions if those actions were within the agreed contribution framework; and d) respect any non-waivable legal protections while still allowing the Corporation to perform its constitutional duties.
The Corporation shall not treat attribution as a mere courtesy. Provenance and truthful credit are part of public-good integrity. At the same time, the Corporation shall not allow attribution claims to be weaponized in ways that block necessary correction, redaction, safety-driven restriction, or supersession. These tensions must be anticipated in the Contributor Terms themselves.
Where law does not permit broad waiver, the Corporation shall document how the contribution may still be used within lawful limits. Where waiver is possible and appropriate, it shall be tailored to institutional stewardship needs rather than drafted as an unnecessarily sweeping erasure of contributor dignity.
82.10 Recordkeeping and Auditability of Contribution Acceptance
The Corporation shall maintain sufficient recordkeeping and auditability for contribution intake, review, acceptance, rejection, and revocation so that the legal and stewardship condition of its asset estate can later be reconstructed without guesswork. A contribution system that cannot show how a material asset entered the institutional estate is not adequate for a public-good steward.
Records may include, as appropriate:
a) contributor identity or protected identifier; b) the material contributed; c) the applicable Contributor Terms; d) contributor warranties and disclosures; e) the reviewing and accepting authority; f) classification of the contribution into a particular asset category or repository; g) any restrictions, reservations, or special conditions; and h) later correction, revocation, or supersession events affecting the contribution.
The Corporation shall not require maximal bureaucracy for trivial inputs. But where a contribution is material enough to affect canonical assets, repository integrity, licensing posture, or future continuity, the record must be strong enough to support later questions of provenance, compatibility, rights scope, and public meaning. Auditability is not antagonistic to openness. It is one of the preconditions for trustworthy openness.
Where records are missing for historically important contributions, the Corporation shall classify the gap, assess its effect on current stewardship risk, and take remedial steps where feasible rather than pretending the uncertainty is harmless.
82.11 Interpretive Rule for Contributor Declarations and Contribution Terms
This Section shall be interpreted to preserve a controlling proposition: material contributions to GCRI US must enter the institutional estate through written, reviewable, provenance-preserving terms that protect the public-good core against hidden encumbrance, ambiguity, contamination, and false assumptions of unrestricted use.
Where ambiguity exists, the interpretation that better preserves:
a) required contributor terms for all material contributions; b) stronger disclosure of third-party dependencies and encumbrances; c) clearer rights to steward, adapt, and preserve continuity of accepted contributions; d) stricter review of volunteer, academic, partner, and contractor materials; and e) better recordkeeping and auditability of contribution acceptance
shall prevail unless a contrary result is required by law.
83. Patent, Royalty, and Anti-Encumbrance Controls (GCRI United States)
83.1 Patent and Royalty Position Consistent With Public-Good Mission
GCRI US shall maintain a patent and royalty position consistent with its nonprofit public-benefit mission, its non-executing institutional posture, and its duty to preserve the public-good technical and semantic core against enclosure, dependency, and exclusionary monetization. The Corporation shall not adopt a patent or royalty posture modeled on commercial portfolio extraction, strategic blocking, or private rights accumulation for its own sake. The governing structure for this Section follows the Part V outline supplied in the uploaded material and is here adapted for GCRI US.
This does not mean the Corporation must categorically refuse all patent-related or royalty-related considerations in every circumstance. It means that where such considerations arise, they must be governed under a strict constitutional hierarchy. The controlling question is not: “What rights could GCRI US claim?” The controlling question is: “What posture best preserves mission, public-good continuity, interoperability, reviewability, non-enclosure, and resistance to hidden private capture?”
Accordingly, the Corporation’s patent and royalty position shall be guided by the following principles:
a) the Corporation shall not use patents or royalty claims to create artificial scarcity around core public-good methods, schemas, semantic baselines, or reference infrastructure; b) the Corporation shall not permit patent or royalty arrangements to distort neutrality, contribution openness, or future stewardship continuity; c) where patent-sensitive or royalty-sensitive conditions arise, the institution shall prefer non-assertion, defensive preservation, substitution, or bounded protective structures over extractive monetization models; and d) any departure from the ordinary anti-encumbrance posture must be treated as exceptional and subject to heightened review.
The Corporation shall also recognize that patent and royalty issues do not arise only when GCRI US itself contemplates filing or asserting rights. They also arise where contributors, partners, vendors, or incorporated technologies bring latent or explicit patent claims into the Corporation’s asset estate. The institution’s public-good mission is compromised not only by what it chooses to patent, but also by what patent risks it allows to embed silently in the common rail.
Part V therefore requires that the Corporation maintain a principled posture of restraint: strong enough to protect public-good continuity, disciplined enough to resist enclosure, and honest enough to identify when an asset or collaboration is drifting into a patent-dependent or royalty-burdened condition inconsistent with the Corporation’s role.
83.2 No Patent Assertion Strategy That Conflicts With Public-Benefit Stewardship
GCRI US shall not adopt, maintain, or tolerate any patent assertion strategy that conflicts with public-benefit stewardship. The Corporation is not constituted to operate as an asserting patent holder, strategic patent enforcer, or exclusion-oriented rights gatekeeper over public-good technical or semantic infrastructure. Any use of patent rights, whether direct or indirect, must therefore remain subordinate to mission, non-enclosure, public-good continuity, and truthful role fidelity.
A patent assertion strategy shall be deemed constitutionally inconsistent where it would, among other things:
a) seek licensing revenue from core public-good infrastructure as an independent institutional objective; b) use patent threat or enforcement to control lawful public-benefit adoption of methods, schemas, mappings, or interoperability baselines; c) create dependence on GCRI US permission for activities that should remain governed through open or non-enclosed stewardship models; d) pressure contributors, partners, or ecosystem participants into compliance through fear of IP exclusion rather than through truthful governance and public-good alignment; or e) position the Corporation as a proprietary bottleneck in relation to assets whose constitutional role is to stabilize the common rail.
The Corporation shall not justify such a strategy by appealing to ordinary market practice, portfolio rationality, or strategic leverage. Those are not sufficient grounds under these Bylaws. A public-benefit steward may protect integrity, provenance, and non-misrepresentation. It may not transform stewardship into patent-based dominance.
This clause does not prevent the Corporation from defending itself, resisting misappropriation of marks or false canonical claims, or taking carefully bounded action where a partner or third party seeks to privatize the common rail. But such actions must remain defensive, proportionate, and aligned to the anti-enclosure posture of Part V. Defensive protection shall not be allowed to mature into a standing assertion strategy by habit or institutional drift.
If any proposed patent-related action could reasonably be understood as moving the Corporation toward patent-centered extraction, gatekeeping, or strategic exclusivity, the matter shall be treated as a constitutional governance issue requiring elevated review rather than routine legal management.
83.3 No Royalty Model That Encloses Core Interoperability or Canonical Semantics
The Corporation shall not impose, accept, or depend upon any royalty model that encloses core interoperability, canonical semantics, shared schemas, reference methods, common mappings, or other assets essential to the public-good core and the common rail. A royalty structure that conditions lawful use of such assets on recurring payment, restricted classes of approved users, outcome-linked consideration, or other scarcity-producing mechanisms is presumptively incompatible with the stewardship posture required by these Bylaws.
This prohibition applies whether the royalty model is:
a) explicit, through direct license royalty or fee-for-use terms; b) indirect, through required paid access to what should remain common infrastructure; c) embedded, through platform dependency, proprietary wrappers, or access-gated packaging; or d) functionally equivalent, through recurring rights-based tolling that achieves enclosure without using the word “royalty.”
The Corporation shall distinguish carefully between lawful cost recovery and impermissible royalty enclosure. Cost recovery may be permissible under later sections of Part V where it remains bounded, transparent, and non-extractive. Royalty enclosure occurs where payment is attached to the legal right to use what should remain part of the shared public-good estate or where the payment structure materially distorts neutrality, access, or continuity.
Accordingly, the Corporation shall not allow:
i) canonical semantics to become proprietary toll roads; ii) interoperability baselines to become recurring revenue instruments; iii) reference implementations to be distributed only under royalty-bearing use rights where non-enclosed models would suffice; or iv) semantic or technical dependence on core assets to be monetized as an institutional business model.
Where a proposed arrangement may appear at first to concern only a non-core implementation or support layer, the Corporation shall still review whether the practical effect would be to burden access to the core itself. A royalty model that nominally attaches to the wrapper but functionally encloses the common baseline is still inconsistent with this Section.
83.4 Exceptional Patent or Royalty Decisions Subject to Elevated Review and Recorded Justification
Any exceptional patent-related or royalty-related decision that departs from the anti-encumbrance and non-enclosure posture of this Part shall be subject to elevated review and recorded justification. The Corporation shall not allow significant patent or royalty departures to emerge by incremental practice, routine counsel advice, partner template, or transactional convenience.
An exceptional decision may arise, for example, where:
a) defensive legal protection is proposed to prevent private capture of a critical public-good asset; b) a narrowly tailored royalty or rights reservation is argued to be necessary to preserve marks integrity, security, or another constitutionally recognized protective interest; c) a partner or co-development arrangement presents unavoidable patent-related complexity that cannot be resolved through the default anti-encumbrance posture; or d) a continuity-preserving transaction requires temporary rights structuring that would otherwise appear inconsistent with the general rule.
In any such case, the Corporation shall require review sufficient to determine:
i) why the ordinary anti-encumbrance rule is not adequate; ii) why less restrictive alternatives are not sufficient; iii) whether the affected asset is truly outside the core public-good estate or, if not, what extraordinary basis justifies the exception; iv) what continuity, interoperability, non-misrepresentation, and exit protections will remain; and v) how the exception will be prevented from becoming precedent by drift.
Recorded justification shall, at a minimum, identify the asset or asset class affected, the specific encumbrance or royalty logic, the reason for the exception, the duration or scope of the arrangement, the approving authority, and the conditions for review, narrowing, or termination. No broad, open-ended, or under-documented patent or royalty deviation shall be permitted to persist under the cover of ambiguity.
The Corporation shall presume that exceptional approval is difficult to justify and shall treat difficulty of justification as a feature, not a problem. The anti-enclosure posture of this Part is intended to be stable against ordinary transactional pressure.
83.5 Disclosure of Known Patent Risks, Claims, or Encumbrances
GCRI US shall require timely and truthful disclosure of known patent risks, known royalty claims, known assertion threats, known encumbrances, or known dependency conditions affecting any material asset, repository, contribution, partnership, or release within its public-good estate. The Corporation shall not allow known patent or royalty hazards to remain latent in the stewardship chain where they may later impair continuity, lawful reuse, or public-good credibility.
Disclosure obligations may arise in relation to:
a) incoming contributions subject to patent claims or patent-risking components; b) joint development arrangements involving parties with relevant patent portfolios; c) third-party technologies incorporated into or adjacent to core technical baselines; d) standards or specifications whose implementation may be encumbered; e) known infringement allegations, notices, or compatibility warnings; and f) licenses, access conditions, or commercial dependencies that create practical royalty-like obligations.
The Corporation shall not interpret “known” narrowly so as to exclude risks that are credibly flagged, reasonably inferable from disclosed facts, or expressly reserved by a partner or contributor even if not yet litigated. Where the risk is serious enough that a prudent steward would want to know it before canonical incorporation or public release, disclosure is required.
Once disclosed, the Corporation shall classify the issue according to seriousness and compatibility with the asset’s stewardship category. A known patent risk that is manageable in an experimental side repository may be constitutionally unacceptable in a canonical core asset. Disclosure is therefore the beginning of governance, not its completion.
Where an actor deliberately conceals a material patent risk or encumbrance in connection with a contribution or partner arrangement, the Corporation may treat that conduct as a serious integrity breach under this Part and other relevant Parts of these Bylaws.
83.6 Defensive Protection, Non-Assertion, and Covenant Mechanisms Where Appropriate
Where patent-related or rights-related conditions cannot be avoided entirely, GCRI US shall, where appropriate, prefer defensive protection, non-assertion commitments, covenants not to assert, or similarly bounded mechanisms over exploitative assertion models. These tools may, in some circumstances, help preserve the public-good core against enclosure by others while still maintaining the Corporation’s overall non-extractive stewardship posture.
Such mechanisms may be considered where, for example:
a) a core asset or indispensable public-good baseline is at risk of private capture or aggressive assertion by another actor; b) a jointly developed asset would otherwise be vulnerable to later enclosure by one participant; c) a bounded rights structure is necessary to ensure broad lawful implementation without fear of later assertion; or d) continuity of the common rail requires legal reassurance to contributors, adopters, or interoperating institutions.
Where used, such mechanisms shall be designed so that they:
i) reduce rather than increase enclosure risk; ii) preserve broad lawful public-good use consistent with asset class; iii) do not become a disguised proprietary licensing regime; iv) remain compatible with contributor terms, open-source posture, and interoperability duties; and v) are documented with sufficient clarity that recipients understand both the protection and its limits.
The Corporation shall not allow “defensive” language to mask assertive commercial strategy. A non-assertion covenant that still leaves the public-good core dependent upon discretionary institutional goodwill is weaker than the anti-encumbrance posture envisioned by this Part. The governing objective is to reduce credible threats to public-good continuity, not to create new institutional discretion over who may safely use core infrastructure.
83.7 Treatment of Partner Patent Claims Over Jointly Developed Infrastructure
Where a partner, vendor, co-developer, host, academic collaborator, or other external actor asserts, reserves, or appears to hold patent or royalty claims over jointly developed infrastructure or over assets materially adjacent to the Corporation’s public-good core, GCRI US shall treat the matter as a high-significance governance issue rather than an ordinary contractual detail.
The Corporation shall not accept partner positions that would:
a) convert jointly developed common infrastructure into partner-controlled exclusivity; b) impose royalties or assertion risk on what should remain public-good baseline material; c) leave the Corporation unable to continue stewarding the asset independently if the partnership ends; d) create uncertainty about who may lawfully implement, adapt, or review the resulting infrastructure; or e) undermine the distinction between jointly developed support layers and the non-enclosable common core.
Accordingly, the Corporation shall require that joint-development arrangements clarify, as appropriate:
i) ownership and stewardship of jointly developed outputs; ii) treatment of any partner background IP; iii) whether any patent rights exist or may be asserted; iv) what non-assertion, broad-use, or anti-encumbrance protections attach to the resulting assets; and v) how continuity, exit, and successor stewardship will be preserved.
The Corporation shall not rely on the hope that mission alignment will prevent later patent assertion. If an asset is important enough to matter to the common rail, it is important enough to require documentary clarity. Where partner patent conditions cannot be reconciled with the public-good stewardship posture of Part V, the Corporation shall narrow, redesign, segregate, or decline the relevant arrangement rather than allowing a contaminated asset to become structurally central.
83.8 Mitigation, Substitution, or Removal of Encumbered Components
Where an existing or proposed asset, repository, codebase, method, standard, or dependency is found to contain or rely upon encumbered components inconsistent with the Corporation’s public-good stewardship posture, GCRI US shall undertake mitigation, substitution, segregation, narrowing, or removal sufficient to preserve continuity without normalizing the encumbrance.
This may require, as appropriate:
a) replacing the encumbered component with a functionally adequate non-encumbered alternative; b) isolating the encumbered material into a non-core or controlled layer so that it does not contaminate canonical assets; c) documenting divergence and compatibility impacts where immediate substitution is not yet feasible; d) revising releases, documentation, and repository structure to reflect the changed status of the component; and e) if necessary, withdrawing or reclassifying affected assets until constitutional alignment can be restored.
The Corporation shall not prefer retention of an encumbered component merely because substitution is inconvenient, technically expensive, politically awkward, or disruptive to existing workflows. Those concerns may shape transition planning, but they do not dissolve the constitutional problem. Where the common rail is materially at stake, the institution’s duty is to preserve stewardability, not to preserve comfort.
Mitigation decisions shall be recorded with enough specificity that later users, contributors, and reviewers can understand what was encumbered, what was done in response, and what residual risk, if any, remains.
83.9 Public Notice and Compatibility Review for Material Encumbrance Risks
Where a material encumbrance risk affects a public-good asset, or an asset that could reasonably be mistaken for a non-encumbered public-good asset, GCRI US shall undertake compatibility review and, where appropriate, provide public or controlled notice sufficient to prevent false reliance, false openness assumptions, or distorted canonical expectations.
Compatibility review shall assess:
a) whether the encumbered condition affects lawful reuse, adaptation, reviewability, or interoperability; b) whether the asset can remain in its current stewardship category; c) whether users of related assets may need migration support, substitution guidance, or warning; and d) whether the encumbrance alters public meaning of the asset or its relation to canonical core infrastructure.
Notice may, as appropriate, include:
i) clarifying repository metadata; ii) release-note warnings; iii) public-safe or controlled notices to affected users or contributors; iv) provenance records indicating the encumbered status; and v) correction of prior public description if that description assumed broader openness than remains accurate.
The Corporation shall not conceal material encumbrance merely to preserve a smoother public narrative. If users could reasonably rely on a core or public-good asset as open, reviewable, or non-enclosed, then a material deviation from that condition must be governed transparently enough to prevent continued misconception.
At the same time, notice shall remain proportionate to rights, security, and controlled-handling concerns. Some notices may need to be restricted rather than fully public. What matters is that the institution not allow material encumbrance risk to operate invisibly where it changes the lawful or trustworthy condition of the asset.
83.10 Interpretive Rule for Patent, Royalty, and Anti-Encumbrance Controls
This Section shall be interpreted to preserve a controlling proposition: the public-good core of GCRI US must remain protected against patent-centered extraction, royalty enclosure, and hidden encumbrance, while still allowing narrow defensive measures genuinely necessary to preserve continuity and non-enclosure.
Where ambiguity exists, the interpretation that better preserves:
a) a mission-consistent, non-extractive patent and royalty posture; b) non-assertion and anti-enclosure treatment of core interoperability and canonical semantics; c) strict review and documentation of any exceptional deviation; d) early disclosure and mitigation of known encumbrance risk; and e) substitution, segregation, or clarification of encumbered components before they can distort the common rail
shall prevail unless a contrary result is required by law.
84. Trademark, Marks, Seals, and Badge Governance (GCRI United States)
84.1 Marks as Institutional Trust Assets Rather Than Pure Commercial Property
All names, wordmarks, logos, seals, symbols, visual identifiers, labels, badges, design marks, and other public-facing trust signals of GCRI US shall be treated as institutional trust assets and not merely as a subclass of commercial property. Their governance under these Bylaws arises not primarily from brand strategy or merchandising logic, but from their function as carriers of public meaning, canonical distinction, stewardship integrity, and non-misleading institutional signal. The structure of this Section follows the controlling Part V outline provided in the uploaded material and is here adapted for GCRI US.
A mark or trust signal becomes constitutionally significant because it can communicate, often more powerfully than text:
a) whether an asset, repository, or publication is authoritative or not; b) whether an activity, participant, or institution is affiliated, recognized, hosted, or merely adjacent; c) whether a badge or label carries any conformance, trust, or governance significance; d) whether an output originates from GCRI US, another institution, a partner, or a derivative community; and e) whether the public should understand a given signal as ordinary descriptive branding or as part of the controlled constitutional surface of the institution.
The Corporation shall therefore reject any assumption that marks governance may be optimized primarily for revenue, promotional flexibility, or broad market-style licensing. Marks and related trust assets may be legally protectable property, but their legal protection serves a constitutional function here: preventing false endorsement, false canonicality, false recognition, misleading association, and erosion of public-good trust. A public-benefit steward must protect its marks not because it seeks ordinary exclusivity for its own sake, but because ungoverned public signals can deform the institutional order.
Accordingly, every decision concerning mark ownership, permitted use, co-branding, badge issue, revocation, or enforcement shall be evaluated not only for legal defensibility but also for its effect on:
i) public truthfulness; ii) mission integrity; iii) non-enclosure of the public-good core; iv) institutional neutrality and non-overclaim; and v) compatibility with Parts I through IV of these Bylaws.
Marks under this Part are thus governed less like commercial inventory and more like trust-bearing constitutional instruments.
84.2 Ownership and Custody of GCRI US Names, Wordmarks, Logos, Seals, and Labels
The Corporation shall maintain clear legal and custodial control over the names, wordmarks, logos, seals, labels, and related trust-bearing identifiers that materially constitute or signal the institutional identity of GCRI US. Such assets shall not remain in ambiguous ownership, founder-personal control, designer-personal custody, agency-side dependency, or partner-default management where truthful public meaning depends upon institutional control.
Accordingly, GCRI US shall determine and maintain, for each material mark or identifier:
a) the legal owner or lawful controller of the mark; b) the authoritative versions and variants of the mark; c) the repository or custodial location of official design files, usage standards, and release-approved forms; d) the class of institutional signal the mark represents, including whether it is a house mark, program mark, label, seal, badge framework, or controlled trust signal; and e) the continuity plan applicable if current custodians, vendors, or repositories change.
The Corporation shall not rely on informal continuity assumptions such as “the designer has the files,” “the domain provider knows,” or “the partner will continue hosting the badge system.” These conditions are legally and constitutionally unstable. A trust-bearing asset is not properly stewarded unless the institution can identify its authoritative form, its legal basis, and its practical means of continuity.
Where a mark or identifier is already in use but ownership or custody is unclear, the Corporation shall treat the ambiguity as a governance defect requiring cure, restriction, clarification, or transition planning. Marks central to institutional identity may not safely remain in legal or operational limbo merely because current relationships are cordial.
This clause also applies to labels and seals that may not be formally registered but nevertheless operate as meaningful institutional signals. A public-facing governance label can produce confusion or false inference even if it lacks formal registration. Part V governs by institutional significance, not registration status alone.
84.3 Permitted and Prohibited Uses of GCRI US Marks
GCRI US shall maintain clear rules distinguishing permitted from prohibited uses of its marks, seals, badges, labels, and trust-bearing identifiers. The Corporation’s marks shall be usable only in ways consistent with truthful provenance, role-faithful public meaning, and the non-misrepresentation principles established throughout these Bylaws.
Permitted use may include, as appropriate:
a) official institutional use by GCRI US in connection with its own governance, publications, repositories, platforms, and public communications; b) use by authorized contributors, partners, or hosts under bounded written terms that preserve truthful public meaning; c) descriptive reference to GCRI US where such reference is accurate and does not imply endorsement, recognition, or canonical status beyond what is true; and d) use of controlled badges or labels where the Corporation has expressly defined the conditions of issue, duration, and meaning.
Prohibited use shall include, without limitation:
i) use implying endorsement, approval, recognition, certification, or affiliation not lawfully and expressly granted; ii) use that falsely signals canonical status of a derivative, adaptation, fork, or partner-developed asset; iii) use suggesting that GCRI US is a regulator, sovereign authority, market approver, or executing body where it is not; iv) use in connection with activities, products, or institutions that would reasonably cause public confusion about GCRI US’s role, boundaries, or neutrality; and v) use surviving suspension, termination, exit, or narrowed relationship contrary to the Corporation’s written conditions.
The Corporation shall not frame mark permissions loosely where the public is likely to infer more institutional significance than the underlying arrangement supports. Mark permission is not merely a courtesy. It is a controlled public signal. Accordingly, the narrower, truer, and less misleading use shall always be preferred to the broader, more flattering, but more ambiguous one.
84.4 No Use of Marks to Imply Endorsement, Approval, Recognition, or Regulatory Status Beyond Recorded Truth
No mark, label, seal, badge, co-branded visual, repository designation, or other trust-bearing identifier of GCRI US may be used to imply endorsement, approval, recognition, certification, regulatory standing, protocol effect, canonical authority, or any comparable institutional status beyond what has been expressly recorded and lawfully established. This prohibition is central to the constitutional function of marks under this Part.
The Corporation shall therefore prohibit uses that would reasonably cause an observer to infer, for example:
a) that GCRI US has approved a partner product, technical implementation, or public claim as institutionally valid beyond the truth; b) that a derivative work or local adaptation is canonical merely because it displays a GCRI-related signal; c) that a participant or partner has governance standing, membership status, or official role merely because of visual affiliation; d) that a host, donor, government, vendor, or program operates “under” GCRI US authority beyond the actual relationship; or e) that any badge, seal, or label issued or displayed by GCRI US carries legal or regulatory force it does not in fact possess.
This clause shall be interpreted strictly. The Corporation shall not excuse misleading implication on the ground that the text elsewhere is technically accurate. If the visual or combined communicative effect is misleading, the use is defective. Public-benefit institutions are not entitled to trade on ambiguity where trust signals are concerned.
Where a mark-bearing use requires explanatory context to avoid overread, the Corporation shall either provide that context clearly or decline the use. Marks are powerful shorthand. Shorthand that outruns truth is constitutionally unsafe.
84.5 Co-Branding Rules With Partners, Hosts, Funders, Governments, and Other Nexus Institutions
All co-branding involving GCRI US and any partner, host, donor, funder, government, academic institution, multilateral body, vendor, other GCRI expression, GRF, GRA, protocol authority, or related institution shall be governed by written or otherwise controlled rules sufficient to preserve distinct legal identity, role separation, truthful association, and non-overclaim.
Co-branding may be permissible where it accurately reflects:
a) collaboration on a bounded publication, event, or initiative; b) hosting or venue support; c) acknowledged partnership or contribution; d) lawful institutional interface or co-development under defined terms; or e) another relationship that can be communicated truthfully without collapsing constitutional distinctions.
Co-branding shall not be used in ways that:
i) imply unified legal personhood where none exists; ii) suggest common governance, mutual authority, or cross-entity endorsement beyond recorded truth; iii) obscure whether a mark-bearing signal is institutional, programmatic, derivative, or partner-originated; iv) cause the public to infer that GCRI US has validated or recognized another institution’s authority surface; or v) leverage GCRI US marks to enlarge the apparent status of a funder, host, vendor, or partner in ways inconsistent with neutrality or mission lock.
The Corporation shall be especially careful with co-branding involving governments, public authorities, and other Nexus institutions because those contexts create unusually strong public inference. A combined logo line or visual stack may communicate far more than any accompanying paragraph can later unwind. The Corporation shall therefore prefer slightly more explicit but truthful co-branding over elegant but constitutionally misleading design.
Where co-branding risk cannot be reduced to an acceptable level through layout, wording, or explanatory framing, GCRI US shall decline co-branding and instead use controlled acknowledgment language or separated attribution.
84.6 Badge Governance, Integrity Controls, and Revocation Rights
Any badge, seal, status marker, designation, or other controlled trust signal issued by or associated with GCRI US shall be subject to strict badge governance, integrity controls, and revocation rights. The Corporation shall not permit trust-bearing visual or textual indicators to exist without defined issuance criteria, use boundaries, duration logic, verification rules, and revocation pathways.
Badge governance shall require, as appropriate:
a) clear definition of what the badge or signal means and does not mean; b) explicit authority within the Corporation for issuance, renewal, suspension, and revocation; c) duration, scope, and context of permitted display; d) controls on derivative use, stylization, embedding, or co-display with other marks; e) mechanisms to verify whether a displayed badge or signal is current and valid; and f) recordkeeping sufficient to determine who received what signal, when, on what basis, and under what continuing conditions.
Revocation rights are essential because badges and trust signals can become misleading over time even if properly granted at the outset. The Corporation shall therefore retain the right to revoke, suspend, narrow, or publicly clarify badge use where:
i) the underlying conditions for issue no longer exist; ii) the badge is being displayed in a misleading or overclaiming context; iii) the holder has breached use conditions; iv) the relationship has ended, narrowed, or been suspended; or v) continued badge display would compromise public meaning or institutional integrity.
The Corporation shall not issue trust-bearing badges casually. Every badge is a compressed constitutional statement. The tighter and more truthful that compression, the safer the badge governance system will be.
84.7 Monitoring, Enforcement, Takedown, and Corrective Statement Powers
GCRI US shall maintain powers of monitoring, enforcement, takedown, withdrawal demand, and corrective public statement sufficient to protect its marks and trust signals against misuse, overclaim, confusion, counterfeit canonicality, false endorsement, or continued unauthorized use.
The Corporation may monitor for:
a) misleading partner or vendor use; b) counterfeit or ambiguous badge display; c) unauthorized derivative works presented as official; d) outdated mark use after exit, suspension, or relationship change; e) domain, platform, repository, or digital-surface uses creating public confusion; and f) uses that, while technically subtle, materially alter public understanding of GCRI US’s role.
Where misuse is identified, the Corporation may take one or more of the following actions, as appropriate:
i) request clarification or correction; ii) demand cessation of use; iii) issue a takedown or withdrawal notice; iv) narrow or revoke permission previously granted; v) publish or circulate a corrective statement to relevant audiences; and vi) escalate to legal, integrity, security, executive, or Board lanes if the seriousness warrants.
The Corporation shall not fail to act merely because the misuse appears flattering, strategically useful, or donor-pleasing. Misleading trust amplification is still misuse. A public-benefit institution cannot preserve truthful public meaning if it tolerates convenient falsehoods about its marks.
At the same time, enforcement shall remain proportionate and role-faithful. The purpose is not aggressive brand maximalism. It is correction of false public meaning and protection of the constitutional trust surface.
84.8 Survival of Mark Restrictions on Exit, Suspension, or Termination
All material restrictions, conditions, and limitations governing use of GCRI US marks, badges, labels, seals, and trust-bearing identifiers shall survive exit, suspension, narrowing, termination, dissolution of a relationship, or other change in status to the extent necessary to prevent misleading public meaning, stale endorsement, counterfeit continuity, or unauthorized residual affiliation.
Accordingly, the Corporation shall ensure that:
a) departing contributors, partners, hosts, vendors, fellows, or other participants do not continue to use marks as if the prior relationship remained current; b) archived, mirrored, or derivative materials do not remain online or in circulation in a way that creates present-tense overclaim; c) badge or status displays are removed or reclassified when their basis lapses; and d) post-termination rights, if any, are clearly distinguished from live institutional affiliation.
Survival rules are especially important in digital and repository-heavy environments, where outdated logos, labels, and README references may continue to circulate long after the relationship on which they were based has changed. The Corporation shall not treat such residue as harmless legacy clutter where it creates real confusion.
This clause also means that any partner, host, or contributor terms involving mark use shall clearly address post-relationship duties, including takedown, update, archive labeling, or controlled historical reference. Without such terms, institutional truth decays after exit even if it was reasonably protected during the relationship itself.
84.9 Public Clarification Duties for Misuse, Misrepresentation, or Ambiguous Association
Where misuse, public confusion, false endorsement, counterfeit canonicality, stale affiliation, or otherwise ambiguous mark-bearing association arises in a way that materially affects public meaning, GCRI US shall have a duty of public or controlled clarification proportionate to the seriousness and audience of the confusion.
This duty may arise where:
a) a derivative or partner asset is being mistaken for an official GCRI US asset; b) a former collaborator continues to appear institutionally affiliated; c) a co-branded initiative is publicly overread as common governance; d) a badge or label is being interpreted beyond its actual significance; or e) marks are being used in contexts that distort GCRI US’s role as a nonprofit public-benefit steward.
Clarification may include, as appropriate:
i) update of repository or website text; ii) public-safe clarifying notice; iii) direct communication to affected stakeholders; iv) metadata or label correction; v) controlled correction in specialist or partner channels; and vi) cross-reference to authoritative sources where necessary.
The Corporation shall not assume that legal enforcement alone is sufficient. In many cases, the immediate constitutional problem is not unauthorized copying but false public meaning. That problem may require clarification even where legal action is not the first or best step. Likewise, the Corporation shall not allow uncertainty to persist simply because only a niche audience is affected. If that niche audience includes contributors, implementers, partners, or governance actors, the misunderstanding may still be materially significant.
84.10 Interpretive Rule for Trademark, Marks, Seals, and Badge Governance
This Section shall be interpreted to preserve a controlling proposition: marks, seals, badges, and related identifiers of GCRI US are trust-bearing constitutional assets, and must be governed so that they communicate no more and no less than the truth of the institution’s role, relationships, and authoritative outputs.
Where ambiguity exists, the interpretation that better preserves:
a) marks as trust assets rather than ordinary commercial inventory; b) clear institutional ownership and custody of key identifiers; c) tighter control against false endorsement, counterfeit canonicality, and ambiguous association; d) stronger badge-governance and revocation discipline; and e) more timely clarification and correction of misleading mark use
shall prevail unless a contrary result is required by law.
85. Open-Source Compliance and Supply-Chain Integrity (GCRI United States)
85.1 Open-Source Governance as a Mandatory Integrity Discipline
GCRI US shall treat open-source governance as a mandatory integrity discipline and not as a casual engineering preference, community-relations gesture, or procurement afterthought. The Corporation’s public-good technical stewardship duty requires that all open-source software, open technical components, package dependencies, models, build artifacts, tooling chains, and related incorporated materials be governed with legal, security, provenance, and continuity seriousness proportionate to their significance. The governing structure for this Section follows the Part V outline supplied in the uploaded material and is here adapted for GCRI US.
Open-source governance is mandatory because the Corporation’s public-good technical estate is only as trustworthy as the components and dependency chains through which it is built, documented, distributed, and maintained. If the institution treats open-source intake, update, release, or integration casually, then the risks are not only technical. They are constitutional. Poor open-source discipline can introduce:
a) hidden license incompatibilities that fracture the public-good core; b) security vulnerabilities that compromise trust, continuity, or rights-sensitive handling; c) opaque or unmaintainable dependencies that create hidden enclosure by practical lock-in; d) provenance failures that make lineage and reviewability unreliable; and e) supply-chain risks that undermine the Corporation’s ability to certify what an authoritative asset really contains.
The Corporation shall therefore govern open-source usage through a principled posture combining:
i) legal compatibility review; ii) security and provenance verification; iii) dependency discipline; iv) repository and build integrity; and v) mission-aligned judgment about whether a technically attractive component is constitutionally suitable for inclusion in the public-good estate.
This Section shall apply not only to formal software releases, but to internal repositories, build chains, reference implementations, scripts, pipelines, models, container bases, test environments, and any other technical surface where incorporated third-party components materially affect the stewardship condition of Corporation assets.
The Corporation shall not excuse weak open-source governance by appealing to the speed of technical iteration, the ubiquity of package reuse, or the informal norms of volunteer software culture. A public-benefit institution whose mission depends on trust and continuity must be stricter, not looser, than the average software project where the common rail is at issue.
85.2 Inventory of Components, Dependencies, and Licenses
GCRI US shall maintain a reliable inventory of components, dependencies, and licenses for all material technical assets within its remit, especially those included in authoritative repositories, canonical reference implementations, released software, public-good tools, or controlled technical environments. The Corporation shall not permit critical technical assets to exist in a state where it cannot tell what third-party components they contain, under what rights terms, and with what stewardship implications.
This inventory shall, as appropriate, cover:
a) direct software dependencies and packages; b) indirect and transitive dependencies where material to legal, security, or continuity risk; c) models, pretrained components, embedded rule sets, and integrated technical artifacts; d) build tools, package managers, compilers, container bases, infrastructure images, and deployment dependencies; e) incorporated documentation generators, test harnesses, UI components, and analytics libraries; and f) the license, source, version, and provenance status of each materially relevant component.
The Corporation shall ensure that the inventory is not a static paperwork exercise. It must remain current enough to support real governance decisions. That means, among other things, that the institution shall be able to determine:
i) whether a dependency is compatible with the stewardship category of the asset into which it is incorporated; ii) whether a component introduces copyleft, attribution, patent, privacy, security, or redistribution obligations; iii) whether a vulnerability or license issue affects released or canonical assets; and iv) whether an asset remains dependent on an external source that creates continuity or lock-in risk.
The Corporation shall not accept “we think it uses standard packages” or “the maintainer knows what is in there” as sufficient inventory discipline. If a component materially shapes the legal, technical, or continuity condition of the asset, it must be inventoried in a way that can later be reviewed and acted upon.
Where a historically significant repository lacks sufficient dependency inventory, the Corporation shall treat that absence as a material governance gap and prioritize remediation proportionate to the asset’s role.
85.3 License Compatibility Review Before Incorporation or Release
Before any third-party component, package, module, framework, library, model, dataset-like technical artifact, or other incorporated material is accepted into a material Corporation asset—or before a material asset containing such components is released, published, or designated authoritative—GCRI US shall conduct license compatibility review appropriate to the significance of the asset and the nature of the incorporated material.
This review shall assess, as appropriate:
a) whether the component’s license is compatible with the license or stewardship class of the receiving asset; b) whether incorporating the component would alter the licensing posture of the whole in ways inconsistent with Part V; c) whether the component introduces attribution, notice, source-availability, reciprocity, or patent obligations that must be preserved; d) whether the component’s terms create friction, enclosure, or redistribution issues inconsistent with public-good continuity; and e) whether the component is suitable for canonical, derivative, restricted, or experimental asset classes.
The Corporation shall not permit “technical usefulness” to outrun license review. A component that is functionally excellent but legally incompatible may be inappropriate for a canonical asset even if it would save time, improve performance, or align with community norms. Likewise, the Corporation shall not treat license review as a one-time event if later updates, version changes, relicensing, or dependency shifts alter the legal condition of the receiving asset.
Compatibility review must also account for layered asset structures. A component might be acceptable in a side tool or experimental branch while being unsuitable for the public-good core. The Corporation shall preserve those distinctions rather than forcing one-size-fits-all approvals across very different stewardship categories.
Where compatibility is unclear, the safer presumption shall be non-incorporation or controlled quarantine pending resolution rather than optimistic inclusion followed by later discovery of structural conflict.
85.4 Software Bill of Materials, Provenance, and Secure Build Discipline
For all material technical assets, and especially for any released, canonical, or otherwise stewardship-significant software or executable technical artifact, GCRI US shall maintain Software Bills of Materials, provenance records, and secure build discipline sufficient to preserve legal traceability, security confidence, reproducibility, and continuity of stewardship.
A Software Bill of Materials shall, to the degree appropriate, identify the significant components, versions, and dependency structure of the asset. Provenance shall identify where components came from, how they entered the asset, and what trust basis supports their inclusion. Secure build discipline shall ensure that the path from reviewed source and approved dependency set to released or authoritative artifact is governed rather than improvised.
The Corporation shall therefore strive to ensure that, for material technical assets, it can answer questions such as:
a) what components are included; b) from what sources and versions they were obtained; c) whether the build or assembly process was controlled and reviewable; d) whether later reproduction or forensic review would be possible; and e) whether the released artifact corresponds to the reviewed and approved source state.
This discipline is necessary because public-good trust depends not only on what a repository appears to contain, but on whether the institution can credibly show that the released or deployed artifact matches what it says it stewarded. Without SBOM, provenance, and build integrity, authoritative technical assets may become legally ambiguous, operationally irreproducible, or vulnerable to hidden dependency and supply-chain drift.
The Corporation need not impose the same depth of build discipline on every experimental script or internal notebook. But once an asset becomes materially relied upon, canonical, or publicly released, the Corporation’s stewardship duty requires more than informal technical confidence. It requires structured traceability.
85.5 No Use of Components That Create Unacceptable Legal, Security, or Mission Risks
GCRI US shall not knowingly use, maintain, or release any component, dependency, toolchain element, model, repository source, or technical artifact that creates unacceptable legal risk, unacceptable security risk, or mission-incompatible risk relative to the stewardship category of the receiving asset. “Useful” does not mean “acceptable.” The Corporation shall govern for constitutional fit, not merely technical convenience.
A component may create unacceptable risk where, among other things:
a) its license terms would materially encumber or distort the public-good core; b) its provenance is unreliable or too opaque to support trust; c) it is vulnerable in ways that materially threaten security, controlled handling, or continuity; d) it depends on external services, accounts, or proprietary infrastructure inconsistent with the asset’s stewardship posture; e) it undermines the Corporation’s ability to document, review, or continue the asset over time; or f) it introduces obligations, telemetry, or hidden functions inconsistent with rights protection, privacy, or public-benefit distinctness.
The Corporation shall not normalize the use of such components on the theory that “everyone uses them,” “we can clean it up later,” or “it is only an internal dependency.” Internal dependencies often become core before the institution fully notices. Mission-sensitive infrastructure must therefore be governed with foresight.
Where a component’s risks are significant but potentially mitigable, the Corporation shall decide whether to:
i) reject it; ii) isolate it to a non-core layer; iii) control and document it under restricted conditions; iv) substitute it; or v) redesign the relevant asset so that the component is no longer necessary.
No asset essential to canonical public-good stewardship shall knowingly depend on a component whose continued presence the Corporation could not publicly or constitutionally defend in stewardship terms.
85.6 Vulnerability Tracking, Patching, and Deprecation Obligations
The Corporation shall maintain vulnerability tracking, patching, and deprecation discipline for material open-source and third-party technical components within its stewardship estate. Public-good continuity does not end at incorporation. It includes ongoing duty to respond to evolving legal, security, and dependency conditions.
Accordingly, GCRI US shall, to a degree proportionate to asset significance:
a) monitor or cause to be monitored known vulnerabilities affecting critical components; b) assess whether identified vulnerabilities materially affect rights-sensitive, canonical, or publicly relied-upon assets; c) patch, update, isolate, or replace affected components within a timeframe appropriate to severity and role; d) deprecate components that are no longer safely maintainable, legally supportable, or mission-compatible; and e) communicate or record significant deprecation or migration events in ways consistent with Part V and Part IV.
The Corporation shall not assume that because a component was acceptable when first adopted it remains acceptable indefinitely. Open-source ecosystems change, maintainers disappear, licenses evolve, support declines, vulnerabilities emerge, and package trust conditions deteriorate. A stewardship-based institution must remain attentive to those changes.
Where patching is not immediately feasible, the Corporation shall consider interim containment, restricted use, migration planning, or warning mechanisms rather than passive continuation. Likewise, a deprecated component shall not remain silently embedded in core assets where it materially undermines the Corporation’s ability to stand behind those assets.
This clause applies to legal deprecation as well as technical deprecation. A component may become mission-incompatible because of new licensing, ownership, governance, or provenance conditions even in the absence of a software exploit.
85.7 Review of Copyleft, Reciprocal, Attribution, and Redistribution Implications
Before incorporating or releasing material technical assets using third-party components, GCRI US shall review the copyleft, reciprocal, attribution, source-disclosure, redistribution, and comparable obligations attached to those components. The purpose of this review is not ideological avoidance of open-source reciprocity. It is constitutional fit. The Corporation must understand whether such obligations are compatible with the stewardship category of the asset and with the public-good continuity model of Part V.
This review shall ask, as appropriate:
a) whether the receiving asset may lawfully and appropriately carry reciprocal obligations; b) whether those obligations would conflict with the treatment of canonical core assets; c) whether the Corporation can practically satisfy source, notice, or attribution requirements without compromising rights-sensitive handling or mixed-origin governance; d) whether downstream users of the public-good asset would face unexpected legal friction inconsistent with lawful reuse; and e) whether the relevant reciprocal terms would better support or weaken continuity, interoperability, and stewardship.
The Corporation shall not adopt a reflexive anti-copyleft or anti-reciprocity stance. Some reciprocal forms may be compatible with the Corporation’s mission in some contexts. Others may be destabilizing for canonical public-good core assets or mixed-origin repositories. The key is governance discipline, not ideology.
Where the implications are uncertain or conflict with the Corporation’s ability to preserve clear stewardship categories, the component shall not be incorporated into the relevant asset class until the issue is resolved. Ambiguity about legal consequence is especially dangerous where the receiving asset is canonical, widely distributed, or difficult to later unwind.
85.8 No Hidden Proprietary Dependency in Public-Good Reference Assets Without Recorded Exception
GCRI US shall not allow hidden proprietary dependency to remain embedded within public-good reference assets, canonical baselines, or other assets presented or relied upon as part of the non-enclosed public-good core, unless an exceptional and recorded justification has been approved under this Part. Hidden proprietary dependency exists where an asset that appears public-good in form depends in practice upon proprietary services, vendor-locked components, private APIs, closed-source modules, controlled accounts, or other restricted elements not evident from the public-facing description of the asset.
This prohibition exists because hidden proprietary dependency can produce all the harms of enclosure while allowing the institution to continue claiming openness. It may create:
a) practical non-portability; b) hidden licensing or continuity burdens; c) future extraction leverage by vendors or partners; d) false assumptions by contributors and adopters; and e) inability of successor stewards to maintain the asset independently.
The Corporation shall therefore ensure that any public-good reference asset can be accurately described in terms of its dependency posture. If a proprietary component is necessary and accepted under exceptional review, the Corporation shall ensure that:
i) the dependency is disclosed at an appropriate level; ii) the rationale for it is recorded; iii) continuity and exit planning are defined; iv) the proprietary condition does not silently spread into canonical semantics or common interoperability baselines; and v) the asset is not misleadingly presented as fully open or self-contained.
The Corporation shall not accept hidden dependence simply because the proprietary component is well known to engineers. What matters is whether the stewardship reality of the asset is truthful and governable.
85.9 Third-Party Repository and Package Source Trust Controls
The Corporation shall maintain trust controls for third-party repositories, package sources, registries, distribution channels, and dependency origins from which material components are obtained. Open-source governance is not only about licenses. It is also about whether the source of the component is trustworthy enough to enter the Corporation’s stewardship estate.
Trust controls may include, as appropriate:
a) use of reputable and reviewable sources; b) validation of package origin and maintainer identity where feasible; c) avoidance of arbitrary, abandoned, or suspicious repositories for material dependencies; d) restrictions on direct incorporation from unreviewed personal repositories or unpinned remote sources; e) use of vetted mirrors, internal registries, or controlled fetch procedures for significant assets; and f) review of repository governance, maintenance status, and update patterns where those factors materially affect risk.
The Corporation shall not rely solely on popularity metrics, download counts, or community familiarity as proof of trustworthiness. Nor shall it assume that a package source is safe merely because it is widely used. A public-benefit steward must ask whether the source can be depended upon for legal clarity, security hygiene, provenance traceability, and continuity under stress.
Where a third-party source cannot be trusted at the level required for the receiving asset’s stewardship category, the Corporation shall reject, mirror under controlled conditions, substitute, or otherwise narrow reliance rather than normalize low-trust intake.
85.10 Escalation and Response for Supply-Chain Incidents or License Failures
Any material supply-chain incident, license failure, dependency compromise, provenance defect, package-origin concern, or other open-source governance failure affecting GCRI US assets shall be subject to structured escalation and response consistent with the Corporation’s broader safeguards, incident, and corrective-action architecture.
Such response may be required where, among other things:
a) a component is discovered to carry incompatible or undisclosed license obligations; b) a dependency has been compromised, poisoned, or otherwise rendered untrustworthy; c) a released or canonical asset can no longer be truthfully described as legally or technically compliant; d) hidden proprietary dependence is discovered in a public-good reference asset; e) a vulnerability or provenance issue materially affects rights-sensitive or publicly relied-upon systems; or f) a package source or repository origin is found to be unreliable or deceptive.
Response may include, as appropriate:
i) immediate containment or hold on release or use; ii) restriction, takedown, withdrawal, or reclassification of affected assets; iii) legal and technical compatibility review; iv) substitution, patching, or removal of the affected component; v) corrective communication or provenance clarification; and vi) escalation to legal, security, integrity, executive, or Board functions depending on severity.
The Corporation shall not downplay such incidents as “just engineering issues” where the consequence affects legality, trust, continuity, or public-good integrity. In the logic of Part V, a supply-chain failure in a canonical or public-facing asset is a governance problem first and a technical problem second.
Where the failure reveals broader weakness in inventory, trust controls, or contributor review, the response shall include structural correction and not merely case-by-case remediation.
85.11 Interpretive Rule for Open-Source Compliance and Supply-Chain Integrity
This Section shall be interpreted to preserve a controlling proposition: the public-good technical estate of GCRI US must be legally compatible, provenance-aware, security-conscious, and free from hidden dependency patterns that would compromise trust, continuity, or non-enclosure. Open-source governance is therefore a constitutional integrity function, not just a software hygiene practice.
Where ambiguity exists, the interpretation that better preserves:
a) rigorous inventory, license review, and SBOM/provenance discipline; b) rejection or mitigation of components creating unacceptable legal, security, or mission risk; c) stronger attention to reciprocal-license consequences and hidden proprietary dependence; d) greater trust control over third-party package and repository sources; and e) faster escalation and structural response to supply-chain or license failures
shall prevail unless a contrary result is required by law.
86. Research Publication Ethics and Scholarly Integrity (GCRI United States)
86.1 Research Publication as a Governed Public Function
All research publication, technical publication, scholarly release, methods publication, working-paper issuance, evidence summary, institutional white paper, consultation response, commentary, technical note, briefing document, educational paper, or other knowledge-bearing release by GCRI US shall be treated as a governed public function and not merely as an exercise of discretionary authorship or reputation-building communication. Publication, in the constitutional order of these Bylaws, is one of the primary ways by which GCRI US shapes public meaning, technical trust, ecosystem expectations, and the perceived boundaries of its authority. The structure of this Section follows the controlling Part V outline supplied in the uploaded materials and is here adapted for GCRI US.
This means that research publication by the Corporation is not governed only by style, speed, or external dissemination goals. It must be governed according to whether the publication:
a) is truthful in institutional provenance and authorship; b) accurately represents the status, maturity, scope, and limitations of the work; c) preserves the distinction between exploratory research, working method, institutional position, and operative public-good baseline; d) avoids rights, safeguards, community, privacy, or public-meaning harms; and e) remains compatible with the Corporation’s non-executing, non-overclaiming, public-benefit identity.
A publication of GCRI US may function simultaneously as scholarship, institutional guidance, technical documentation, public positioning, and part of the documentary lineage of the Corporation’s common estate. The Corporation shall therefore not treat publication as merely expressive. It is constitutive. A paper can become de facto authority if the institution is not careful. A methods note can silently become canonical if provenance and release discipline are weak. A public-facing technical document can overstate maturity and thereby distort trust. Publication governance exists to prevent these shifts from occurring by accident.
Accordingly, all publication pathways of GCRI US shall be structured so that they can answer, for each material release:
i) what kind of publication is this; ii) who stands behind it and in what institutional capacity; iii) what degree of review it received; iv) what can and cannot be inferred from it; and v) what correction, supersession, or withdrawal discipline applies later.
The Corporation shall not accept the proposition that because publication is common in academic, nonprofit, or technical communities, it requires lighter governance than other institutional acts. For a public-benefit steward, publication is one of the most consequential governance surfaces in the entire institutional estate.
86.2 No Ghost Authorship, Hidden Sponsorship, or Suppression of Material Findings
GCRI US shall prohibit ghost authorship, hidden sponsorship, concealed material influence, undisclosed editorial control, and suppression of material findings in all publications governed by this Part. The Corporation’s public-good legitimacy depends in part on whether readers can trust that publications say who is actually responsible, disclose who materially shaped the work, and do not strategically omit findings or limitations in ways that distort the meaning of the release.
The Corporation shall therefore not permit:
a) publication under the names of individuals or the institution where material drafting, analysis, or shaping was performed by undisclosed parties in a way that would matter to reader understanding; b) funders, sponsors, partners, hosts, vendors, or strategic actors to materially shape substantive content without disclosure where such influence is relevant to trust or interpretation; c) suppression of material caveats, contrary evidence, known limitations, uncertainty, or internal dissent in order to improve public reception, fundraising, policy attractiveness, or strategic positioning; d) use of editorial processes to erase inconvenient findings that are necessary to avoid misleading overclaim; or e) institutional presentation of a document as independent, neutral, or comprehensive where material external shaping or internal suppression makes that characterization false.
This clause does not prohibit editorial support, research assistance, lawful confidential review, or mission-aligned funding. It requires that such support be governed truthfully. The relevant standard is whether the undisclosed factor would reasonably matter to a serious reader’s understanding of the work’s origin, independence, reliability, or limitations.
The Corporation shall also be careful not to use “team-authored” or “institutionally authored” labels as a shield behind which meaningful authorship or influence becomes invisible. Institutional authorship is legitimate where true. It is not a mechanism for hiding responsibility or influence that should be legible in context.
Where hidden shaping or suppression is discovered after release, the Corporation shall treat the matter as a publication-integrity issue requiring correction, clarification, or other remedial action proportionate to seriousness.
86.3 Authorship, Attribution, and Contribution Transparency
Every material publication of GCRI US shall be governed by clear rules of authorship, attribution, and contribution transparency sufficient to preserve truthful provenance, institutional accountability, and non-misleading public meaning. The Corporation shall not allow publications to circulate under ambiguous responsibility structures where readers cannot tell whether a document is the work of a named author, a collective authoring body, a mixed-institution team, or a more limited contributor set.
Accordingly, GCRI US shall determine and communicate, as appropriate:
a) who is the author or authors of the publication; b) whether the publication is institutionally authored, individually authored under institutional auspices, jointly authored, or otherwise attributed; c) what material contributions were made by others whose role does not rise to authorship but remains relevant to transparency; d) whether the publication represents an official institutional position, a bounded analysis, an exploratory paper, or another defined class of release; and e) how contributors, editors, researchers, reviewers, technical assistants, and affiliated institutions should be acknowledged in a way consistent with safety and law.
The Corporation shall not inflate authorship for prestige or understate it for simplification. Nor shall it use acknowledgments as a substitute for authorship where substantive responsibility should actually be visible at the authoring layer. Contribution transparency is not performative courtesy. It is part of how readers understand what kind of document they are reading and what weight to attach to it.
Where publication safety or protected participation considerations limit how much attribution may safely be made public, the Corporation shall still preserve enough controlled internal record to support later accountability and provenance review. Public attribution may be bounded. Internal traceability shall not disappear.
The Corporation shall also distinguish clearly between attribution of authorship and attribution of endorsement. Listing a contributor, reviewer, or consultation participant shall not be permitted to imply broader institutional, community, or personal endorsement than is true.
86.4 Disclosure of Funding, Conflicts, and Limitations
All material publications governed by this Section shall include, as appropriate to context and sensitivity, disclosure of funding, material conflicts or interests, and relevant limitations necessary to preserve truthful reader understanding. A publication that is technically accurate in isolated statements may still be materially misleading if readers are not told enough about who funded it, what interests surrounded it, and what constraints limit what can responsibly be inferred.
Such disclosure may include, as appropriate:
a) the existence and general nature of funding support for the relevant work; b) whether a sponsor, host, partner, or collaborating institution had a material role in shaping the work, its scope, or its release; c) material conflicts of interest affecting authors, reviewers, editors, or institutional decision-makers connected to the publication; d) methodological, dataset, contextual, or interpretive limitations that materially affect how the publication should be read; and e) whether parts of the publication rely on controlled, incomplete, provisional, or non-public inputs that constrain certainty or reproducibility.
The Corporation shall not treat limitations as weak points to be minimized rhetorically. In public-benefit publication practice, limitations are often part of integrity. They help preserve the distinction between what the publication shows, what it suggests, and what it does not establish. Likewise, conflict disclosure is not an accusation. It is part of trustworthy context.
Where full disclosure is restricted by law, controlled handling, rights protection, or other Part IV constraints, the Corporation shall still provide the most truthful bounded disclosure reasonably possible and shall preserve fuller controlled records where needed for later review. Hidden material influence or hidden limitation is constitutionally problematic even if the publication remains rhetorically strong.
86.5 Correction, Retraction, Clarification, and Versioned Supersession Discipline
GCRI US shall maintain rigorous correction, retraction, clarification, and versioned supersession discipline for all publications within the scope of this Part. The Corporation’s publication estate must be correctable in practice, not merely in principle. A public-benefit institution that cannot repair its documentary record when material error, changed conditions, misleading framing, unsafe disclosure, or new evidence emerges is not a reliable steward of knowledge.
Accordingly, the Corporation shall maintain the ability to:
a) correct discrete inaccuracies, omissions, misstatements, or metadata defects; b) clarify how a publication should and should not be interpreted where public overread has become material; c) retract a publication or version where it is materially defective, unsafe, or no longer fit for circulation; and d) supersede a publication through orderly versioned replacement that preserves lineage rather than creating documentary confusion.
These actions shall be governed by disciplined questions such as:
i) what exactly is wrong or outdated; ii) does the defect alter substance or only presentation; iii) is bounded clarification enough or is a deeper corrective act required; iv) what public or controlled notice is necessary to prevent continued false reliance; and v) how will the authoritative record preserve both the original and the corrective history?
The Corporation shall not silently alter publicly relied-upon materials in ways that erase the fact of change where that fact matters for trust, lineage, or interpretation. At the same time, it shall not preserve harmful or misleading versions in circulation merely because historical continuity is administratively easier than cleanup. The correct approach is versioned honesty: preserve lineage, but do not let superseded or unsafe versions masquerade as current.
Retraction shall be used carefully but without hesitation where required. Clarification shall not be used as a weak substitute when the actual condition is retraction or supersession.
86.6 Distinction Between Working Papers, Publication Drafts, and Operative Institutional Outputs
The Corporation shall preserve a strict distinction between working papers, publication drafts, and operative institutional outputs. These categories are not merely editorial stages. They carry different governance meaning, different public inferences, and different levels of institutional authority.
For purposes of this Part:
a) Working papers are provisional analytical or exploratory documents that may inform internal thought, external discussion, academic exchange, or bounded policy dialogue, but do not by virtue of their existence constitute authoritative institutional guidance or canonical baselines. b) Publication drafts are documents in active editorial or review progression toward a possible release state, but are not yet authoritative and shall not be represented as such. c) Operative institutional outputs are formally released or otherwise designated publications that carry institutional significance beyond exploratory circulation and may influence repositories, guidance, public meaning, or official reference practice.
The Corporation shall make these distinctions visible through metadata, labels, repository placement, release controls, and public explanation. It shall not allow:
i) working papers to be mistaken for final institutional position; ii) drafts to circulate without status markers in ways that create false reliance; iii) operative outputs to be weakened by being mixed indistinguishably with exploratory material; or iv) historical or draft versions to remain discoverable without enough context to prevent misreading.
This distinction matters especially in GCRI US because its publications may be read by actors who will treat even preliminary material as highly consequential. The Corporation must therefore discipline not only what it publishes, but how the publication state is signaled. A drafts discipline is a constitutional discipline.
Where working-paper openness is institutionally valuable, the Corporation may permit such circulation, but only with enough status clarity that exploration is not mistaken for canonical institutional settlement.
86.7 Ethical Review and Contextual Risk Handling for Sensitive Publications
Any publication that is rights-sensitive, community-sensitive, Indigenous-sensitive, sovereignty-sensitive, security-sensitive, retaliation-sensitive, or otherwise high-consequence under Part IV shall be subject to ethical review and contextual risk handling before release, circulation, or operational reliance. The Corporation shall not assume that ordinary editorial review is adequate where publication itself could become a vector of harm.
Such review may consider, as appropriate:
a) whether the publication discloses or implies identities, community contexts, locational information, or governance-sensitive details that create foreseeable risk; b) whether the framing of the work could amplify exclusion, stigmatization, unsafe public meaning, or overclaim; c) whether summary, redaction, controlled release, delayed release, or non-publication is the more legitimate course; d) whether the publication relies on community-originated or protected information whose reuse conditions require narrower handling; and e) whether the likely audience, geopolitical context, or downstream actor set changes the risk profile of otherwise accurate content.
The Corporation shall not treat ethical review as a literary sensitivity check. It is part of institutional safeguards governance. A technically strong paper may still be unfit for release in present form if its public effects would be constitutionally unsafe. Likewise, a publication need not be suppressed entirely if risk can be managed through narrowing, summary, reclassification, or contextual framing. The institution’s duty is to choose the least harmful truthful form of release consistent with public-benefit purpose.
Where review identifies unresolved material risk, the publication shall be held, redesigned, reclassified, or escalated under Part IV. The desire to publish important work shall not outrun the institution’s duty not to cause preventable harm through publication.
86.8 Peer Review, Replication, and Dissent Capture Where Applicable
Where appropriate to the type of publication, GCRI US shall support peer review, replication, critical review, and dissent capture as instruments of scholarly and public-good integrity. The Corporation shall not claim a false aura of scientific or technical seriousness while structuring publication practice to insulate itself from critical scrutiny or suppress meaningful challenge.
This does not require that every publication undergo the same review model. It does require that where the publication purports to carry analytical, methodological, or technical weight, the Corporation shall consider whether legitimacy requires:
a) expert review prior to release; b) possibility of lawful replication or verification of methods; c) preservation of key assumptions and limitations sufficient for informed scrutiny; d) structured space for serious methodological or interpretive disagreement; and e) capture, in controlled or public form as appropriate, of material dissent that would change how the publication should be understood.
The Corporation shall be especially careful where a publication is likely to be treated as quasi-authoritative in policy, governance, or technical settings. In such contexts, review and dissent visibility may be even more important than in ordinary academic circulation because the public meaning stakes are higher.
The Corporation shall not confuse consensus aesthetics with integrity. A publication that appears cleaner because internal or external critique has been erased may be less trustworthy, not more. Where dissent is materially relevant to interpretation, the institution shall preserve it in some appropriate form rather than letting polished release practice convert contestable work into falsely settled work.
86.9 No Publication Strategy That Converts Evidence Work Into Promotional Overclaim
GCRI US shall not adopt or tolerate any publication strategy that converts evidence work, technical work, policy work, scholarly work, or methodological work into promotional overclaim, institutional self-inflation, or false implication of authority, maturity, validation, or public consensus beyond what the work actually supports.
This prohibition applies to:
a) exaggeration of the certainty, completeness, or field status of findings; b) styling exploratory, partial, or provisional work as if it were canonical institutional settlement; c) using publication design or language to imply broader recognition, adoption, review, or external validation than has actually occurred; d) framing evidence documents as though they authorize execution, approval, or regulated consequence beyond the Corporation’s non-executing role; and e) shaping publications more for fundraising, partner persuasion, or institutional positioning than for truthful expression of what the work is and is not.
The Corporation may communicate ambition, significance, and public-benefit value. It may not do so by blurring the line between research and endorsement, between technical note and authoritative protocol, between consultation response and public mandate, or between internal method and widely accepted common standard. These lines matter because the Corporation’s trust depends not only on the quality of what it says, but on whether it says more than it knows.
Where publication strategy pressures authors, editors, or institutionally situated communicators to overstate maturity, certainty, adoption, or endorsement, the matter shall be treated as a publication-integrity issue and not merely as a communications style disagreement.
86.10 Repository Integrity and Citation Discipline for Official Releases
All official releases, authoritative publications, and repository-linked documentary outputs of GCRI US shall be subject to repository integrity and citation discipline sufficient to preserve authoritative reference, traceable provenance, and resistance to quote-fragment drift or documentary confusion. An official release shall not circulate as a floating file without clear relation to the authoritative record.
This means the Corporation shall, as appropriate:
a) ensure that official releases are stored or linked through authoritative repositories or documented release channels; b) distinguish clearly between current, historical, superseded, withdrawn, and draft versions; c) preserve citation-relevant metadata such as version, date, status, and authoritative source; d) maintain stable enough identifiers or references that later readers can determine what document is being cited; and e) avoid release practices that encourage copies to outrun the authority of the record.
Citation discipline matters because, in governance-heavy and technical institutional contexts, old text often outlives corrected text unless the record is structured to make supersession visible. The Corporation shall therefore not treat proper citation and repository linkage as optional scholarly ornament. They are part of stewardship. They determine whether the institution can later correct, clarify, or rebut misuse of its own textual estate.
Where a publication cannot safely be fully public, the same logic shall apply in restricted form: there must still be an authoritative record, a stable internal or controlled reference, and enough version discipline that the document’s lineage remains governable.
86.11 Interpretive Rule for Research Publication Ethics and Scholarly Integrity
This Section shall be interpreted to preserve a controlling proposition: research and scholarly publication by GCRI US is a governed public act that must remain truthful in authorship, transparent in influence and limitation, correctable over time, safe in context, open to serious review where appropriate, and disciplined against promotional overclaim.
Where ambiguity exists, the interpretation that better preserves:
a) publication as a governed public function rather than a casual expressive act; b) transparency regarding authorship, sponsorship, conflicts, and limitations; c) stronger correction, retraction, and versioned supersession discipline; d) stricter distinction between working papers, drafts, and operative institutional outputs; and e) publication integrity over strategic narrative inflation
shall prevail unless a contrary result is required by law.
87. Third-Party Standards, Frameworks, and Incorporated Materials (GCRI United States)
87.1 Lawful and Disciplined Incorporation of Third-Party Standards and Reference Materials
GCRI US may lawfully reference, align with, interoperate with, map to, compare against, or incorporate third-party standards, frameworks, taxonomies, specifications, reference documents, templates, methodologies, and other protected or unprotected external materials where doing so advances mission, public-benefit intelligibility, technical rigor, or interoperability. Such use, however, shall be governed by a discipline of lawful incorporation, provenance clarity, non-misrepresentation, and compatibility review. The Corporation shall not treat third-party materials as a free raw resource simply because they are influential, useful, publicly discussed, or aligned in spirit with the Corporation’s work. This Section follows the Part V structure supplied in the uploaded outline and is here adapted for GCRI US.
Lawful and disciplined incorporation requires that the Corporation determine, for any material third-party standard or framework it uses:
a) what the source material is and who controls it; b) whether the Corporation is merely referring to it, incorporating portions of it, adapting it, or substituting it into an institutional asset; c) whether the relevant use is lawful under applicable copyright, license, or other rights conditions; d) whether the use risks misleading the public or contributors about ownership, canonical status, or endorsement; and e) whether the external material remains compatible with the public-good stewardship posture of Part V and the safeguards logic of Part IV.
The Corporation shall not allow “industry standard,” “widely used,” or “publicly available” to substitute for legal and governance analysis. Nor shall it assume that because a document is easy to access, it is unrestricted for reproduction, embedding, or adaptation. Public-benefit institutions must model disciplined use of external materials precisely because they often operate in ecosystems where copying and blending are normalized informally.
Accordingly, every material reliance on third-party standards or reference materials shall be governed by the principle that respect for external provenance and lawful limits is part of internal integrity. The Corporation’s public-good posture does not authorize appropriation. It requires careful relation.
87.2 No Unlicensed or Improper Reproduction of Protected Materials
GCRI US shall not reproduce, embed, republish, mirror, distribute, adapt, or otherwise use protected third-party materials in a manner that is unlicensed, improper, excessive, or materially inconsistent with the rights conditions governing those materials. The Corporation shall not assume that mission alignment or nonprofit status creates a blanket exemption from lawful rights discipline.
This prohibition applies, without limitation, to:
a) direct reproduction of protected standards text, figures, diagrams, tables, templates, schemas, or graphics beyond lawful or licensed scope; b) incorporation of substantial excerpts into official GCRI US publications, templates, training materials, or repositories without proper basis; c) repackaging of protected materials into derivative products or guidance as though the rights issue were merely formal; d) use of restricted standards content inside technical or semantic assets that are later released under broader GCRI licensing terms; and e) treating licensed access by an individual, partner, or reviewer as though it automatically grants institutional reproduction rights.
The Corporation shall also avoid improper reproduction by transformation. A rights problem is not necessarily solved merely because material is reformatted, summarized too closely, translated, diagrammed, or woven into technical prose if the resulting work still depends upon impermissible copying of protected expression. At the same time, the Corporation may lawfully reference, compare, map, and discuss external standards in ways consistent with law and proper scholarly or technical practice. The duty is disciplined distinction, not total avoidance.
Where a proposed use falls into a gray area, the Corporation shall prefer narrower quotation, descriptive reference, mapping by concept rather than by extensive copied text, or non-incorporation pending rights clarification. Public-benefit integrity is not advanced by casual infringement.
87.3 Recording of Source, Scope, and Terms of Use for Incorporated Materials
Whenever GCRI US materially relies upon, incorporates, adapts, maps, or otherwise uses third-party standards, frameworks, or incorporated materials, it shall preserve a record of the source, scope, and terms of use governing that reliance. The Corporation shall not allow material external inputs to disappear into its internal estate without traceable record of origin and legal condition.
Such records shall, as appropriate, identify:
a) the name and origin of the third-party material; b) the relevant version or edition; c) the owner, steward, or publishing body where material; d) the nature of the Corporation’s use, including whether the material is being referenced, partially incorporated, adapted, mapped, compared, or substituted; e) the legal or practical terms governing the use, including license, permission, fair-use judgment, quotation limits, or other relevant conditions; and f) any restrictions that must survive into derivative or mixed-origin Corporation assets.
This recording duty is especially important where external standards or frameworks influence canonical or semi-canonical GCRI US assets. Without such records, later users may wrongly assume that the resulting asset is entirely GCRI-originated or entirely free of inherited obligations. The Corporation shall avoid that confusion.
Where the external material influences only background reasoning and is not materially embedded in the output, lighter documentation may suffice. But where the material is structurally important to the resulting asset, the record shall be strong enough to support future review, rights compliance, repository integrity, and corrective action if the third-party material later becomes unavailable, contested, or incompatible.
87.4 Distinction Between Reference, Incorporation, Adaptation, and Substitution
GCRI US shall maintain a clear distinction between reference, incorporation, adaptation, and substitution when dealing with third-party standards, frameworks, and reference materials. These are not stylistic variations. They are materially different legal and governance postures with distinct consequences for rights, provenance, and public meaning.