# I. Thesis

### Part 1 — Membership Thesis and System Outcomes

#### 1.1 Purpose of GCRI Guild Membership

1.1.1 **Evidence-grade public good.** GCRI Guild Membership constitutes a voluntary, open evidence commons for developing, testing, verifying, and publishing methods, standards, and artifacts for systemic risk governance and resilience, designed for reuse across jurisdictions and sectors under scrutiny.\
1.1.2 **Infrastructure, not authority.** The Guild system provides infrastructure for evidence discipline and comparability; it does not assert operational authority, regulatory delegation, emergency command, enforcement power, procurement mandate, or intelligence tasking authority.\
1.1.3 **Artifact-as-unit-of-value.** The unit of value is the reusable artifact: replayable, contestable, and correctionable outputs with provenance, limitations, handling elections, and reliance bounds (including method cards, dataset cards, benchmark protocols, ontologies, lineage rules, proof packs, review reports, drills, and publication-safe summaries).\
1.1.4 **Competence scaling.** Membership scales competence through Integrated Learning Accounts (ILAs), Proof of Competence (PoC), and peer-verifiable work traces so that privileges are earned through recorded capability rather than reputation, affiliation, or seniority.\
1.1.5 **Sovereign-compatible adoption.** Guild outputs are designed for sovereign and institutional adoption under each adopter’s lawful authority, including data sovereignty, compute-to-data constraints, local lawful basis requirements, and public safety/national security sensitivities.\
1.1.6 **Voluntary engagement baseline.** Membership is voluntary-by-default: no duty exists to contribute, attend, review, publish, disclose identity, accept roles, or provide services; opt-in is required for any time-boxed role or controlled-lane participation.\
1.1.7 **Quintuple-helix composition objective.** Each Future Innovation Lab is designed to attract and include expertise across the quintuple helix (Public Sector; Industry & Operators; Academia & Research; Civil Society & Communities; Media & Information Stewardship) to reduce blind spots and improve legitimacy under scrutiny.\
1.1.8 **Cross-Lab roaming principle.** Members may roam across Labs to learn, contribute, and review subject to handling, lawful constraints, and PoC gates; accountability for standing, review pools, and governance routing remains anchored to the member’s elected primary home as recorded on the Platform.\
1.1.9 **Public-interest baseline.** The system is governed by do-no-harm, safeguarding, accessibility, protected participation, non-discrimination, and anti-retaliation commitments, enforced through handling discipline, incident lanes, and due process.\
1.1.10 **Reliance bounds as design constraint.** Every artifact and outcome must include reliance bounds (intended use, non-intended use, limits/uncertainty, expiry/review date, correction path, and handling constraints); any use outside those bounds is prohibited representation.

***

#### 1.2 Guild Operating Model (Voluntary-by-Default, Platform-Encoded, Peer-Governed)

1.2.1 **Voluntary participation default; opt-in role acceptance.** Participation is voluntary unless a member affirmatively accepts a scoped, time-boxed role marker by record (e.g., reviewer, steward, maintainer, CCell lead, CERT participant).\
1.2.2 **Autonomous peer collaboration.** Members collaborate peer-to-peer through Platform workspaces, issue queues, clinics, replication rooms, and review lanes, subject to handling elections, conduct baselines, and publication safety gates.\
1.2.3 **Platform-encoded governance.** Membership governance is expressed through record-validity: role markers, release gates, distribution logs, contestation windows, corrections, and sanctions are valid only when Platform-recorded under the governing council and integrity rules.\
1.2.4 **Least privilege; time-boxed authority.** Any privileges are narrow, scoped, non-transferable, revocable, and expire by default; privileges confer only Platform-limited capabilities and do not create external authority.\
1.2.5 **Dissolve-by-default formations.** Competence Cells and CERT formations are constituted by record, scoped and time-boxed with expiry; dissolution is the default state absent recorded renewal.\
1.2.6 **Neutrality by design.** Workspaces, outputs, and convenings are structured to remain market-neutral, vendor-neutral, and politically safe; safe-meeting scripts, prohibited topic boundaries, and non-endorsement rules apply.\
1.2.7 **Primary governance council assignment per Lab.** Each Future Innovation Lab has one Primary Council (one governance interface) responsible for role ladders, review gates, and release lanes; cross-council review is available where triggers apply.\
1.2.8 **Cross-council review and contestation lanes.** Members and councils may contest releases, badges, and governance acts through defined lanes; dissent and minority reports are preserved in record-valid form subject to handling.\
1.2.9 **Evidence lifecycle discipline.** Artifacts proceed through recorded states (draft → reviewed → safety-screened → released → corrected/superseded) with explicit handling elections, reliance bounds, and contestation windows proportionate to impact.\
1.2.10 **Publication-safety first.** Where dual-use or sensitivity risk exists, releases may be abstracted, redacted, delayed, partitioned, or staged (public-safe summary first; controlled details by need and PoC), with distribution logs and expiry where applicable.

***

#### 1.3 What Membership Is Not (Non-Derogable Exclusions)

1.3.1 **Not employment or agency.** Membership does not create employment, contractor status, agency, partnership, joint venture, or fiduciary duty, and does not authorize any member to bind GCRI.\
1.3.2 **Not a regulator or certifier.** Membership does not confer regulatory authority, licensure, audit opinion authority, or compliance certification capability; badges are scope-bound quality signals with limitations and expiry.\
1.3.3 **Not operational command or dispatch.** Membership is not emergency management authority, operational control, dispatch, or responder unit formation; “command center” simulation is prohibited.\
1.3.4 **Not an intelligence service.** No tasking authority exists for intelligence collection, clandestine activity, surveillance direction, or covert coordination.\
1.3.5 **Not a procurement forum.** No bid steering, vendor endorsement, procurement influence, client allocation, or collusive coordination is permitted.\
1.3.6 **Not a deal room.** No underwriting, placement, custody, settlement, market-making, solicitation, or financial product promotion occurs within membership lanes.\
1.3.7 **Not a political vehicle.** No campaigning, electioneering, partisan mobilization, or lobbying mandate exists; political safety is enforced.\
1.3.8 **Not a substitute for lawful authority.** Membership does not replace public institutions, statutory functions, or local lawful decision authority; it provides methods and artifacts only.\
1.3.9 **Not a guarantee of service.** Membership does not guarantee service levels, publication acceptance, continued access, compute entitlements, event participation, or outcomes; safety holds may override access.\
1.3.10 **Not a safety shield.** Misconduct, misrepresentation, harmful disclosure, and integrity breaches remain enforceable; membership does not immunize members from accountability.

***

#### 1.4 Public Value Outcomes (What “Good” Looks Like)

1.4.1 **Reproducibility and replayability.** Outputs are designed for replay under scrutiny, using method cards, provenance, replication evidence, and reproducible pipelines appropriate to handling class.\
1.4.2 **Contestation and critique.** Critique lanes, adversarial review, and minority reports are preserved; disagreement is treated as a safety feature rather than disloyalty.\
1.4.3 **Correctionability.** Errata, supersession, deprecation, and correction clocks are mandatory; silent edits are prohibited for released artifacts.\
1.4.4 **Comparability and interoperability.** Outputs support comparability across contexts through shared semantics, lineage rules, quality ladders, standardized templates, and consistent evidence packaging.\
1.4.5 **Decision-quality uplift under uncertainty.** Outputs prioritize decision-quality by explicitly stating uncertainty, assumptions, confidence, and scenario framing, reducing over-claiming and misuse.\
1.4.6 **Measurement safety and harm reduction.** Publication safety gates reduce dual-use harm, targeting cues, panic amplification, manipulation risk, and operational compromise.\
1.4.7 **Capacity building without capture.** Standing is competence-based and revocable; sponsor/bloc influence is controlled through neutrality safeguards, rotation, and transparency minima.\
1.4.8 **Trust-under-scrutiny performance.** Auditability, distribution logs, contestation windows, correction clocks, and record-validity form the integrity substrate for defending against misquote and politicization.\
1.4.9 **Sovereign adoption readiness.** Outputs are structured for sovereign-compatible adoption, including compute-to-data patterns, lawful basis documentation templates, and localization without safeguard regression.\
1.4.10 **Public learning and literacy.** Publication-safe education artifacts and clinics improve public literacy and institutional competence without enabling harm.

***

#### 1.5 Zero-Trust Principle (Privilege Is Earned, Not Claimed)

1.5.1 **No trust by status.** Titles, affiliations, employer brands, seniority, media visibility, or notoriety do not confer privileges or authority.\
1.5.2 **Privilege by recorded evidence.** Elevated access, publishing rights, review authority, stewardship roles, and controlled-lane eligibility require PoC thresholds, CRS footprint, and handling compliance recorded on the Platform.\
1.5.3 **Revocation-by-record with due process.** Role markers, access, and badges are revocable by record for safety, COI, misrepresentation, or misconduct, subject to defined notice and appeal minima.\
1.5.4 **Identity minimization default.** Pseudonymous participation is permitted by default; identity disclosure is optional unless required for specific controlled activities under lawful constraints; identity is never equivalent to authority.\
1.5.5 **Sybil resistance and anti-gaming.** The Platform enforces anti-gaming controls including rate limits, reviewer rotation, evidence linkage requirements, anomaly detection, and clawbacks for fraudulent credit accumulation.\
1.5.6 **Least-privilege access model.** Public-safe access is the baseline; controlled and restricted access is granted only on need, competence, handling training, and lawful eligibility.\
1.5.7 **Separation of duties.** Reviewers, authors, stewards, and safety gate roles are separated; self-review and concentration are minimized through recusal and rotation logic.\
1.5.8 **Transparency and audit posture.** Access logs, distribution logs, record trails, and correction history are treated as primary integrity controls.

***

#### 1.6 “Measurement Can Harm” Doctrine (Dual-Use Is First-Order Risk)

1.6.1 **Dual-use framing.** Measurement outputs can enable targeting, panic, manipulation, stigmatization, or operational compromise; dual-use risk is treated as a gating criterion equal to evidence quality.\
1.6.2 **Publication safety gates.** Releases may be delayed, redacted, abstracted, partitioned, or staged; public-safe summaries are preferred where details elevate harm risk.\
1.6.3 **Critical infrastructure sensitivity controls.** Facility targeting cues, exploitable dependency maps, and operationally actionable vulnerability details are restricted by default and handled under controlled disclosure patterns.\
1.6.4 **Cyber and exploit sensitivity controls.** “How-to harm” content is prohibited; responsible disclosure routing may be supported without enforcement posture; exploit details are restricted by default.\
1.6.5 **Market sensitivity controls.** Outputs plausibly affecting markets, credit, insurance, or public confidence require reliance bounds, controlled dissemination, and possibly delayed release.\
1.6.6 **Rights and community harm analysis.** Releases must consider disparate impact, stigmatization risk, retaliation risk, and community safety; mitigation may require aggregation, redaction, or non-public handling.\
1.6.7 **Crisis narrative safety.** Outputs must avoid panic amplification; rumor resistance, misquote resilience, and correction-first posture are mandatory.\
1.6.8 **Handling escalation triggers.** Criteria for elevating handling from Public-Safe to Controlled or Restricted include: targeting cues, exploitability, market sensitivity, credible retaliation risk, or legal constraints.\
1.6.9 **Stop-the-line holds.** Integrity roles may impose temporary holds on release, badging, or distribution when unsafe disclosure risk exists; holds must include reason codes, expiry, and reopen conditions.\
1.6.10 **Safety overrides entitlements.** Safety holds may suspend access, publication, or convening entitlements; safety decisions are recorded and contestable under defined lanes.

***

#### 1.7 Community Governance as a Safety Mechanism

1.7.1 **Protected reporting channels.** Members may report safety, integrity, security, COI, conduct, handling breaches, and misrepresentation via protected channels with access logging and confidentiality constraints.\
1.7.2 **Anti-retaliation baseline.** Retaliation against reporters, dissenters, or protected participants is prohibited and enforceable by record with escalating sanctions.\
1.7.3 **Stop-the-line mechanics.** The system defines who can place holds, the scope of holds, mandatory expiry, reopening conditions, and an appeal lane; indefinite silent blocks are prohibited.\
1.7.4 **Dissent preservation.** Minority reports and dissenting views are recorded, preserved, and may be published in public-safe form consistent with handling and safety review.\
1.7.5 **Safeguarding rules.** Harassment, discrimination, threats, coercion, stalking, and doxxing are prohibited; safeguarding applies across online, hybrid, and in-person participation.\
1.7.6 **Identity exposure minimization.** Role markers are used to represent authority; rosters and attendee lists are minimized by default; identity unmasking requires controlled procedures.\
1.7.7 **Moderation and escalation lanes.** The system provides graduated interventions (education, warnings, restrictions, suspension, removal) with recorded basis and contestation rights.\
1.7.8 **Restoration and remediation.** Remediation may include training, supervised re-entry, restricted participation, or loss of privileges; restoration is optional and recorded.\
1.7.9 **Safety-first convening discipline.** Convenings adopt room classes, scripts, minutes minimization, and controlled distribution rules proportionate to sensitivity and dual-use risk.

***

#### 1.8 Reliance Bounds Doctrine (How Outputs May Be Used)

1.8.1 **Scoped and conditional reliance.** Reliance is permitted only within stated intended use, limits/uncertainty, expiry/review date, correction path, and handling constraints.\
1.8.2 **Non-endorsement.** Outputs do not imply endorsement of any policy, vendor, product, institution, or operation; badges are not approvals.\
1.8.3 **Non-equivalence.** Outputs and badges are not certifications, audit opinions, regulatory determinations, legal advice, or operational authorization.\
1.8.4 **Correction condition.** Reliance is conditioned on respecting correction and supersession status; known-superseded outputs must not be represented as current.\
1.8.5 **Responsibility allocation.** Users and adopting institutions remain responsible for decisions, lawful compliance, and operational actions; outputs are informational and bounded.\
1.8.6 **Handling inheritance.** Reuse must preserve handling constraints; controlled/restricted material may not be laundered into public distribution.\
1.8.7 **Citation and attribution controls.** Attribution is permissioned, scope-bounded, expiry-bound, and subject to misquote correction processes; role markers may be used instead of identity.\
1.8.8 **Distribution constraints.** “No-forward,” controlled sharing, and distribution log requirements must be respected; unauthorized sharing is a breach.\
1.8.9 **Prohibited representations.** Members and users may not represent outputs as “approved by GCRI,” “certified by GCRI,” or “compliant with GCRI,” except where a specific, scope-bound badge explicitly states otherwise with limitations.\
1.8.10 **Reliance dispute and clarification lane.** Clarification requests and reliance disputes are handled through a record-based lane; public-safe clarifications are issued by record where appropriate.

***

#### 1.9 Sovereign-Compatible Adoption Doctrine (Global Methods, Local Lawful Authority)

1.9.1 **Universal methods; local authority.** Methods are universal; adoption, implementation, and action remain under local lawful authority; no in-jurisdiction operating presence occurs absent activation.\
1.9.2 **Host Institutions as lawful adoption organs.** Host Institutions may support lawful hosting for evidence work, training, and convening, preserving sovereignty and lawful basis; they do not delegate authority to GCRI.\
1.9.3 **Data sovereignty and compute-to-data.** Patterns prioritize data minimization, compute-to-data, and sovereign data zones; no requirement exists to centralize sensitive data.\
1.9.4 **Lawful basis documentation.** Adoption patterns include documentation templates for lawful basis, consent/authority, minimization, and security controls.\
1.9.5 **Export controls and sanctions.** Participation and sharing are subject to sanctions/export controls; access may be restricted or denied where required.\
1.9.6 **National security and public safety sensitivities.** Sensitive outputs may require controlled dissemination and disclosure routing; abstraction-first is default where details create risk.\
1.9.7 **Localization without safeguard regression.** Localization may adapt methods to context but may not weaken safeguards, handling discipline, correctionability, or perimeter constraints.\
1.9.8 **Cross-border collaboration constraints.** Cross-border sharing follows handling, identity minimization, disclosure routing, and lawful constraints; restricted materials require distribution logs and expiry.\
1.9.9 **Mandate evidence for local programs.** Any local program posture requires mandate evidence and activation records; absent these, only global participation is permitted.\
1.9.10 **De-recognition and reversion.** Withdrawal or expiry of mandate support triggers pause and reversion to global-only participation with public listing updates by record.

***

#### 1.10 CERT Doctrine (GCRI) — Evidence Support, Verification, Public Learning (Non-Executing)

1.10.1 **CERT definition.** A CERT is a time-boxed, record-valid, multi-CCell formation for evidence capture, measurement support, verification assistance, and structured public learning within the non-executing perimeter.\
1.10.2 **Scope limitation.** CERT scope is limited to evidence and verification outputs; CERTs do not coordinate response operations or assume authority functions.\
1.10.3 **Non-command; non-dispatch rule.** CERTs may not dispatch resources, issue operational directives, simulate command structures, or represent emergency authority.\
1.10.4 **Handling-first formation.** CERT formation requires handling election, distribution rules, PoC minima where controlled, and mandatory distribution logging for controlled/restricted outputs.\
1.10.5 **Liaison and disclosure routing.** Liaison points (if any) and disclosure routing constraints are recorded; CERTs may route responsible disclosures without enforcement posture.\
1.10.6 **Responsible disclosure support.** CERTs may support structured disclosure pathways (e.g., cyber vulnerability reporting formats) while remaining non-executing and non-regulatory.\
1.10.7 **Dissolution and after-action.** CERTs dissolve by default at expiry/completion; every CERT must file an after-action record including limitations, withheld details for safety, corrections, and lessons learned.\
1.10.8 **Publication outputs.** Default public output is a public-safe summary with limitations and reliance bounds; sensitive annexes, if any, are controlled with distribution logs.\
1.10.9 **Safety gate escalation.** Sensitive incidents involving infrastructure, cyber, markets, or retaliation risk require Stewardship safety gate review and may require staged release.\
1.10.10 **Activation dependence for local mobilization.** No local CERT mobilization may occur absent jurisdiction activation and mandate support evidence; absent activation, only global method work and publication-safe learning is permitted.

***

#### 1.11 No Shadow Institutions Doctrine (Brand and Authority Safety)

1.11.1 **No imitation of state functions.** Membership structures shall not imitate state/regulatory authority or emergency command; titles, rooms, and processes must avoid “government-like” misrepresentation.\
1.11.2 **No implied offices, chapters, or nodes.** Members may not claim “GCRI office,” “chapter,” “node,” or “national program” absent activation; violation is misrepresentation.\
1.11.3 **No private mandates.** No private actor may claim delegated public authority through badges, convenings, role markers, or membership participation.\
1.11.4 **No brand laundering.** GCRI identity may not be used to launder legitimacy for unsafe, unlawful, deceptive, or conflicted projects.\
1.11.5 **Misrepresentation as first-order breach.** Misrepresentation triggers stop-the-line, takedown, restriction, and sanctions lanes by record with due process.\
1.11.6 **Public listing discipline.** Public listings must state activation status, scope limits, handling posture, and expiry/review date to prevent authority confusion.

***

#### 1.12 Trust-Under-Scrutiny Objective (Adversarial, Misquote, Politicization Resilience)

1.12.1 **Design for adversarial review.** Processes and outputs are designed to withstand adversarial scrutiny through provenance, replayability, logs, and correction discipline.\
1.12.2 **Default safe summaries.** Where details increase harm risk, public outputs default to abstraction and public-safe summaries; controlled details are minimized and logged.\
1.12.3 **Disciplined attribution.** Attribution is permissioned, scope-bounded, expiry-bound; role markers may be used to reduce doxxing and politicization risk.\
1.12.4 **Corrections as legitimacy.** Corrections are treated as a trust mechanism; fast errata and transparent supersession are required; concealment and silent edits are breaches.\
1.12.5 **Record-as-defense doctrine.** The authoritative defense against misinformation is the Platform record: what was decided/released, under what handling, to whom distributed, and what was corrected.\
1.12.6 **Crisis communications integrity.** The system prioritizes non-amplification, rumor resistance, correction-first posture, and misquote mitigation procedures.\
1.12.7 **Reputation risk containment.** Public trust surfaces minimize identity exposure; rosters and attribution are limited; escalation protocols exist for coordinated misrepresentation or harassment.

***

#### 1.13 Legal, Operational, and Technical Safety Baseline (Member Duties Without Compulsion)

1.13.1 **Compliance-by-default; voluntariness preserved.** Members must comply with applicable law and Platform rules; participation remains voluntary-by-default and does not create compelled service obligations.\
1.13.2 **Competition/antitrust hygiene.** Members must not coordinate pricing, market allocation, bids, client restrictions, or other anti-competitive conduct; safe-meeting scripts and prohibited topic boundaries apply.\
1.13.3 **Security and handling discipline.** Members must respect handling elections, distribution constraints, watermarking, access controls, and no-forward rules; breaches may trigger immediate containment and restriction pending review.\
1.13.4 **IP hygiene.** Contributions must be made with sufficient rights; inbound license grants and provenance statements are required; restricted materials must not contaminate open releases.\
1.13.5 **Data protection baseline.** Data minimization is the default; retention and deletion are governed by lawful obligations and record-integrity constraints; PII is avoided by default.\
1.13.6 **Incident reporting pathways.** Members who become aware of safety, integrity, security, conduct, or handling breaches must route reports through Platform incident lanes; anti-retaliation applies.\
1.13.7 **No implied services.** Membership does not guarantee support levels, compute availability, tool access, or publication acceptance; safety holds may override entitlements.\
1.13.8 **Role survival obligations on exit.** Handling survival obligations (confidentiality, non-disclosure of controlled materials, return/destruction where required) persist after exit; offboarding attestations may be required for controlled lanes.\
1.13.9 **Technical integrity expectations.** Tampering with records, logs, role markers, badges, or distribution controls is prohibited and enforceable as an integrity breach.\
1.13.10 **Acceptable use baseline.** Abuse (harassment, disinformation weaponization, unsafe automation, credential sharing, evasion of controls, or gaming of credits) is prohibited and enforceable through restriction and sanctions lanes.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.therisk.global/organization/cooperation/nexus-guilds/membership/i.-thesis.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.