Part 0 — Front Matter: Authority, Perimeter, Platform Primacy, Validity-by-Record
0.1 Title Page
0.1.1 Instrument name. GCRI Guild Membership System Constitution — Unified Operating Model (Membership Only).
0.1.2 Version ID and document control code. This instrument is issued with a unique version identifier and document control code recorded on the Platform as the authoritative change-log pointer.
0.1.3 Effective date. This instrument is effective as of 01 January 2026.
0.1.4 Handling class. Default handling election for this instrument is Public-Safe, subject to 0.18 and any Record-Valid elevation for specific excerpts, notices, or controlled annex pointers (if any).
0.1.5 Supersession. This instrument supersedes all prior membership constitutions, membership terms, or guild participation rulebooks previously issued by GCRI to the extent of inconsistency, as listed in the Platform supersession record.
0.1.6 Issuing authority signature block. This instrument is issued by Record-Valid act under the authority of the issuing body(ies) designated in the Platform record; signatures may be expressed as role-marker execution with the controlling record reference.
0.2 Issuing Entity, Institutional Boundary, and Scope Election
0.2.1 Issuing entity. The issuing entity is The Global Centre for Risk and Innovation (GCRI), a public-good institution mission-locked to evidence, methods, and risk-intelligence infrastructure.
0.2.2 Public-good stack relationship and firewall doctrine. GCRI operates within the Nexus public-good stack and is bound by a strict firewall doctrine: GCRI is governance-only, evidence-only, methods-only, and non-executing by design.
0.2.3 Scope election. This instrument governs membership only and applies to: (i) all members; (ii) all Future Innovation Labs constituted under GCRI governance; and (iii) all membership operations performed through GCRI Nexus Platforms.
0.2.4 Two-nonprofit structure boundary where applicable. Where GCRI operates as legally separate nonprofit entities across jurisdictions, this instrument applies only within the issuing entity’s lawful scope and does not merge or confuse legal personality, liability, or jurisdictional stewardship boundaries.
0.2.5 Non-agency; non-employment; non-partnership; non-fiduciary creation rule. Membership does not create employment, contractor status, agency, partnership, joint venture, fiduciary duty, or authority to bind GCRI.
0.2.6 Non-partisanship and election-safe posture. GCRI Guild Membership is institutionally neutral, non-partisan, and election-safe; membership systems must not be used for campaigning, lobbying mandates, or partisan coordination.
0.2.7 No implied endorsement; no delegation rule. Membership, participation, badges, or role markers do not imply endorsement, certification, approval, delegated authority, or regulatory standing.
0.2.8 Reliance bounds and liability posture. All outputs and participation are subject to explicit reliance bounds and limitations; GCRI provides membership infrastructure and artifacts “as is,” within the limits set in this instrument and the Platform’s published terms.
0.3 Binding Context Notes
0.3.1 Public-good purpose. GCRI exists to improve the quality, comparability, contestability, and correctionability of evidence and methods used in systemic risk governance and resilience.
0.3.2 Membership as commons participation. Membership is a voluntary, open commons for contributing to methods, standards, artifacts, and public learning under scrutiny, with optional pathways to higher responsibility through recorded competence.
0.3.3 Outputs are artifacts, not directives. Outputs are publishable artifacts (methods, benchmarks, ontologies, lineage rules, proof pack templates, review reports, drills, and public-safe summaries) and are not operational instructions or mandates.
0.3.4 No shadow institutions. Membership shall not create or simulate parallel state institutions, regulators, intelligence services, enforcement bodies, emergency command centers, or procurement authorities.
0.3.5 Sovereign-compatible adoption. Methods may be global; adoption and action are local and lawful. GCRI does not substitute for governmental authority, statutory duty, or regulated execution.
0.3.6 All-hazards and all-society posture. Future Innovation Labs and councils are designed for systemic, all-hazards, all-society risk governance, requiring cross-sector participation and disciplined safeguards.
0.4 Jurisdiction Activation Rule
0.4.1 Definition of “in-jurisdiction operating presence.” “In-jurisdiction operating presence” includes any branded local posture, including: chapters, local councils, national working groups, host-institution programs, CERT mobilizations, locally hosted convenings, or any representation implying a GCRI node, office, or program in that jurisdiction.
0.4.2 Activation prerequisites. In-jurisdiction operating presence may occur only after: (i) a State Council is constituted by Platform record; and (ii) mandate support is evidenced from competent city/state/country authorities (as applicable) by Platform record.
0.4.3 Global participation permitted absent activation. Absent activation, members may participate in global work (methods, learning, peer review, publication under handling rules) but may not operate, convene, recruit, or represent a local GCRI node.
0.4.4 Misrepresentation rule. Any claim of local chapter, office, national program, or authority absent activation is misrepresentation and is subject to restrictions and sanctions by record.
0.4.5 Mandate withdrawal or expiry. Withdrawal or expiry of mandate support triggers: (i) pause of local operations; (ii) de-listing or relabeling of the node; and (iii) reversion to global-only participation unless and until renewed.
0.4.6 Public listing requirements. Any activated node must publish, in public-safe form: activation status, scope, limitations, handling posture, and expiry/review date.
0.4.7 Conflict-of-law handling. Where local law conflicts with membership practices, local operations shall not proceed; the constraint is recorded and escalated through the governance lanes for abstention, modification, or termination.
0.5 Instrument Hierarchy and Precedence
0.5.1 Supremacy of higher-order instruments. This instrument is subordinate to GCRI’s higher-order governing instruments and may not derogate from safeguard-critical constraints.
0.5.2 Platform terms and security/handling rules. Platform terms of use, security baselines, and handling rules apply to all membership conduct; where conflict exists, the stricter rule governs.
0.5.3 Future Innovation Lab charters. Lab charters may specify domain practices and outputs but may not weaken safeguard-critical invariants or expand beyond the non-executing perimeter.
0.5.4 Handling & integrity code and enforcement ladder. Handling classes, publication safety gates, misrepresentation controls, and enforcement ladders apply across all membership operations.
0.5.5 Conflict resolution. In any conflict: safeguards prevail; then safety; then due process; then transparency; then usability.
0.5.6 Ambiguity interpretation. Ambiguities are interpreted to preserve the non-executing perimeter, measurement safety, and correction discipline; convenience shall not override integrity.
0.5.7 Supremacy of record-validity. Governance acts are valid only if recorded; off-platform assertions do not create membership standing, authority, or entitlements.
0.6 Strict Non-Executing Perimeter
0.6.1 Permitted scope. Membership and Future Innovation Labs operate only as science/standards/evidence/observatory/education commons, producing artifacts with limitations and reliance bounds.
0.6.2 Prohibited: operational command or dispatch. No member, Lab, council, or formation may command operations, dispatch resources, or issue operational directives.
0.6.3 Prohibited: emergency response authority. No emergency coordination or incident command is performed as a GCRI authority function.
0.6.4 Prohibited: enforcement or compulsion. Membership does not include enforcement actions, investigative compulsion, or any quasi-police authority.
0.6.5 Prohibited: regulatory determinations or compliance certification. No compliance certification, regulatory determinations, or “approval” findings are issued; prohibited labels include “certified,” “approved,” “compliant,” “licensed,” except as quoted within a critique context with explicit disclaimer.
0.6.6 Prohibited: procurement steering and endorsements. No procurement steering, preferred vendor lists, bid influence, exclusivity, or pay-for-access advantage.
0.6.7 Prohibited: deal room and regulated execution. No underwriting, placement, custody, settlement, market-making, or solicitation; no negotiations to form binding commercial terms within membership spaces.
0.6.8 Prohibited: political campaigning and electioneering. No partisan coordination, campaigning, or lobbying mandates through membership channels.
0.6.9 Prohibited: intelligence tasking or clandestine activity. No intelligence collection tasking, surveillance mandate, clandestine operations, or covert coordination.
0.6.10 Reliance bounds requirement. All outputs must state intended use, non-intended use, limitations, expiry/review date, correction path, handling constraints, and non-endorsement posture.
0.7 Governance Topology
0.7.1 General Assembly. Membership legitimacy lane; adoption and amendment of membership rules by record; no operational mandates.
0.7.2 Board of Trustees. Fiduciary oversight of the membership system; perimeter enforcement; risk, audit, and controls; escalation powers by record only.
0.7.3 Stewardship Committee. Cross-Lab integrity and safety governor: handling discipline, publication safety, correction clocks, misrepresentation controls, sanctions ladder administration (with due process), and identity minimization rules.
0.7.4 Nexus Councils as Domain Councils. Quintuple-helix Domain Councils provide governance interfaces for Labs: review gates, role ladders, competence expectations, and cross-council contestation lanes.
0.7.5 Future Innovation Labs. Primary collaboration units producing artifacts; open participation by default; governance via the assigned Primary Council and Platform rules.
0.7.6 Competence Cells. Time-boxed work units constituted by record; dissolve-by-default; accountable to a Lab of record; outputs must be correction-ready.
0.7.7 CERT formations. Time-boxed, evidence/verification/public-learning formations only; explicitly non-executing; scoped by record with expiry, handling election, and after-action record.
0.7.8 State Councils, National Working Groups, Host Institutions. Adoption organs for sovereign-compatible programs; activation-gated; no implied authority absent mandate evidence.
0.7.9 Delegation limits. Delegations exist only by role marker; they are narrow, time-boxed, revocable, and confer no external authority.
0.8 Quintuple-Helix Doctrine
0.8.1 Purpose. The helix model exists to reduce blind spots, strengthen contestability, and preserve legitimacy under scrutiny by ensuring diverse oversight of systemic risks.
0.8.2 Helix set. Public Sector; Industry & Operators; Academia & Research; Civil Society & Communities; Media & Information Stewardship.
0.8.3 Primary Council rule. Each Future Innovation Lab is assigned exactly one Primary Council (a Domain Council) as its governance interface by record.
0.8.4 Composition expectation. Each Lab must actively attract and enable cross-helix participation; dominance by a single helix triggers seat-completion and independence measures.
0.8.5 Cross-council contestation. Any council may trigger cross-council review for safety, market sensitivity, critical infrastructure sensitivity, rights impacts, or unresolved evidence disputes.
0.8.6 Seat completion. Where a helix is missing or underrepresented, the governance system may require remedial recruitment, rotation, independent review, or constrained release scope.
0.8.7 Independence controls. COI disclosure, recusals, rotation, and influence caps apply; repeated concentration is treated as an integrity indicator requiring review.
0.8.8 No pay-for-influence. Funding, sponsorship, or subscription tier shall not purchase governance powers, votes, release authority, or veto overrides.
0.9 Independence, Neutrality, and Political-Safety Posture
0.9.1 Institutional neutrality. GCRI membership governance is non-partisan and neutral; it does not endorse parties, candidates, or political blocs.
0.9.2 Election-safe communications. Communications are designed to be election-safe and resistant to weaponization; attribution is permissioned, scoped, and expiry-bound.
0.9.3 Anti-capture posture. Sponsor concentration caps, bloc behavior indicators, and rotation requirements are enforced; undue influence triggers review, restrictions, or de-recognition by record.
0.9.4 No implied endorsement. Badges and markings are scoped quality signals only, with limitations and expiry; they are not endorsements or approvals.
0.9.5 Protected participation. Members may report concerns via protected channels; retaliation, doxxing, and harassment are prohibited and enforceable by record.
0.9.6 Misrepresentation controls. Brand laundering, false node claims, false authority claims, and misuse of badges are integrity breaches subject to takedown and sanctions.
0.9.7 Narrative safety. Outputs must avoid panic amplification and must include uncertainty and limitations; crisis communication hygiene is mandatory.
0.10 Competition, Procurement, and Market Neutrality
0.10.1 Competition hygiene. Convenings and workspaces follow antitrust/competition safe-meeting rules; prohibited topics include pricing coordination, market allocation, bid coordination, client restrictions, or collusive conduct.
0.10.2 Procurement neutrality. No vendor steering, preferred supplier lists, or procurement influence; technical comparisons must be framed as methods evidence with neutrality disclaimers.
0.10.3 Market sensitivity handling. Where outputs could move markets or affect credit/insurance/public confidence, the default posture is abstraction-first, staged release, controlled dissemination, and reliance bounds.
0.10.4 No deal room. Membership spaces are not used to negotiate commercial terms, raise capital, solicit investments, or form exclusivity arrangements.
0.10.5 Minutes discipline. Minutes are minimized; where required, controlled minutes may be used with role markers and handling constraints; attendee identity is minimized by default.
0.10.6 Violation response. Suspected violations trigger stop-the-line holds, restrictions pending review, and recorded outcomes.
0.11 Platform Primacy
0.11.1 System-of-record rule. The Platform record is authoritative for membership state, privileges, roles, badges, releases, sanctions, appeals, corrections, and notices.
0.11.2 Role marker rule. Role markers are the only valid expression of internal authority; titles, reputation, payment tier, or meeting attendance do not confer authority.
0.11.3 Distribution log rule. For controlled/restricted lanes, distribution logs are a validity condition: who received what, under which handling, with which expiry.
0.11.4 Expiry-by-default. Privileged access and scoped roles expire by default and require renewal by record; privilege creep is treated as an integrity defect.
0.11.5 No off-platform standing claims. Claims of standing or authority not reflected in the Platform record are invalid; mismatch triggers lock and dispute routing.
0.11.6 Auditability minima. Governance-critical events require audit logs and replayability; access controls and change management are mandatory for core registry functions.
0.12 Validity-by-Record for Membership and Lab Acts
0.12.1 Record-Valid acts. Record-Valid acts include: membership admissions and status changes; role marker grants/revocations; release approvals; badge issuances; sanctions; appeals; corrections; supersessions; and contestation outcomes.
0.12.2 Release gates. Publication readiness progresses through recorded states (at minimum): draft → reviewed → safety-screened → released, with handling election and reliance bounds at each gate as applicable.
0.12.3 No silent edits. Released artifacts cannot be silently edited; updates occur only through recorded errata, deprecations, and supersessions.
0.12.4 Contestation windows. Material releases and governance changes include contestation windows proportionate to impact; dissent and minority reports are preserved subject to handling.
0.12.5 Sanctions and due process traceability. Sanctions require recorded basis, reason codes, minimum evidence basis, scope, expiry, and appeal lane.
0.12.6 Mandatory record fields. Authority scope, limitations, handling class, intended use, non-intended use, expiry/review date, distribution constraints, and correction path are mandatory for designated acts.
0.12.7 Expiry and renewal. Roles, badges, and privileged lanes require renewal by record; renewal may require competence refresh, COI refresh, and handling recertification.
0.12.8 Linkage and provenance. Artifacts must retain lineage pointers sufficient to understand provenance, dependencies, and correction history within handling constraints.
0.13 Rights and Public-Interest Baseline
0.13.1 Dignity and non-discrimination. Membership is administered without discrimination; accessibility and accommodations are supported within reasonable limits.
0.13.2 Safeguarding. Harassment, threats, coercion, stalking, and doxxing are prohibited; safeguarding applies to online and in-person contexts.
0.13.3 Protected participation. Protected reporting channels exist for integrity, safety, and conduct incidents; retaliation is prohibited.
0.13.4 Privacy by default. “No PII by default” is the baseline; where lawful identity verification is required for specific controlled activities, it is minimized and access-logged.
0.13.5 Youth and vulnerable persons. Participation by minors or vulnerable persons, if permitted, is strictly gated with safeguarding, consent, and privacy constraints consistent with applicable law.
0.13.6 Do-no-harm. Measurement safety and harm minimization are first-order duties; outputs must consider dual-use, panic, targeting, and misuse risks.
0.14 Core Platform Primitives
0.14.1 CRS. Contribution Recognition System (CRS) records work contributions, review activity, and engagement signals; it is protected against gaming through audits, rotation, and clawbacks.
0.14.2 iVRS. Integrated Value Reporting System (iVRS) provides operational transparency of membership health and integrity; it is not marketing and must include uncertainty and limitations.
0.14.3 ILAs. Integrated Learning Accounts (ILAs) track learning progress, training completion, and competence evidence; portability is bounded by handling class.
0.14.4 PoC. Proof of Competence (PoC) is the privilege-gating ladder; higher privileges require recorded evidence, refresh cycles, and revocation-by-record.
0.14.5 Utility credits. eCredits/pCredits/vCredits/NUCs are non-financial utility credits used for access, compute, and participation economics; they are not investments, not securities, and not vote instruments.
0.14.6 Non-transferability and anti-sale. Credits and privileges are non-transferable by default and may not be sold for influence; anti-gaming controls apply.
0.14.7 No PII by default. Default contributions and artifacts must avoid personal data; where exceptions exist, lawful basis and minimization are mandatory.
0.14.8 Identity minimization cell. A limited identity cell may exist where necessary for lawful compliance; unmasking requires a two-person rule, access logging, and recorded justification.
0.14.9 Resilience minima. Governance-critical platform services must maintain access control, audit logs, backup/restore, incident response, and secure change management.
0.15 Definitions and Abbreviations
0.15.1 Canonical definitions. Definitions used in this instrument are maintained as a Platform record and are authoritative for interpretation.
0.15.2 Handling vocabulary. Handling classes and distribution rules are defined and maintained by the Stewardship Committee by record.
0.15.3 Role marker vocabulary. Role markers define scoped internal privileges and expire by default; they do not map to external authority.
0.15.4 Artifact vocabulary. Core artifact types include proof packs/AEPs, method cards, dataset cards, review reports, drills, and public-safe summaries.
0.15.5 Standing vocabulary. Membership standing states (including Member-in-Good-Standing and restricted/suspended states) are defined by record with transitions and due process minima.
0.15.6 Reliance bounds vocabulary. Reliance bounds include intended use, non-intended use, limitations, expiry/review date, correction path, and handling constraints.
0.16 Interpretation Rules and Legal Mechanics
0.16.1 Severability. If any provision is held invalid, the remainder continues in effect to the maximum extent permitted by law.
0.16.2 Survival. Handling obligations, confidentiality constraints, IP license terms, and dispute clauses survive termination to the extent necessary for integrity and lawful compliance.
0.16.3 Non-waiver. Failure to enforce a provision is not a waiver of future enforcement.
0.16.4 No third-party beneficiaries. This instrument creates no third-party beneficiary rights unless expressly designated by record.
0.16.5 Assignment restrictions. Membership is personal to the member account and non-assignable; attempts to transfer standing or privileges are invalid.
0.16.6 Translations. If translations exist, the controlling language is that designated by record.
0.16.7 Local law compliance. Members must comply with applicable local law, including export controls and sanctions regimes; access may be restricted where required.
0.16.8 Notices. Authoritative notices are given by Platform record; external communications are non-authoritative convenience copies.
0.16.9 Membership dispute lane. Membership disputes and remedies are resolved through the membership dispute lane designated by record; the lane is membership-only and does not confer external adjudicative authority.
0.16.10 Enforcement reservation. GCRI reserves the right to restrict access, revoke role markers, and enforce handling controls by record, subject to due process minima.
0.17 Core Disclaimers
0.17.1 No certification or approval. No output, badge, or listing constitutes certification, approval, or compliance determination.
0.17.2 No advice. Nothing provided through membership constitutes legal, financial, medical, or professional advice.
0.17.3 No operational direction. Membership outputs do not direct operations and do not create emergency command authority.
0.17.4 No procurement influence. Membership is not a procurement forum and does not endorse vendors.
0.17.5 No financial product promotion. Membership does not solicit or promote financial products and does not provide investment solicitation.
0.17.6 No intelligence tasking. Membership does not task intelligence collection or conduct clandestine operations.
0.17.7 Reliance bounds and uncertainty. Outputs must be used only within stated reliance bounds; uncertainty and limitations are mandatory.
0.17.8 As-is and limitation of liability. Outputs are provided “as is,” subject to platform terms and this instrument’s limitation posture; members remain responsible for their own decisions and compliance.
0.18 Handling Class Election Rule
0.18.1 Handling election requirement. Every artifact, workspace, and convening must elect a handling class and distribution rules by record.
0.18.2 Public-Safe default. The default is Public-Safe with mandatory limitations statements; detail may be abstracted to reduce dual-use risk.
0.18.3 Controlled/restricted lanes. Controlled and restricted lanes require PoC thresholds, distribution logging, and additional access controls as designated by record.
0.18.4 Watermarking and no-forward posture. Watermarking and no-forward/no-print rules may be mandatory for controlled/restricted materials; breaches trigger containment.
0.18.5 Recording and photography. Recording/photography rules are elected by handling class; attendee identity is minimized; consent rules apply.
0.18.6 Disclosure routing. Sensitive artifacts and incident contexts follow disclosure routing rules (including responsible disclosure patterns) designated by record.
0.18.7 Breach response. Handling breaches trigger stop-the-line powers, temporary restrictions, incident triage, and recorded outcomes.
0.19 Document Change Log Pointer
0.19.1 Change log location. The authoritative change log is maintained as a Platform record referenced by the document control code.
0.19.2 Supersession protocol. Updates occur only by recorded supersession with clear diffs, effective dates, and member notice.
0.19.3 Effective date and notice minima. Changes must specify an effective date and a notice period proportionate to impact; safeguard-critical changes require enhanced notice and contestation windows.
0.19.4 Safeguard-critical change rule. Changes affecting perimeter, handling, due process, identity minimization, jurisdiction activation, or misrepresentation controls require: (i) impact statement; (ii) contestation window; and (iii) Stewardship safety gate prior to adoption.