# III. Catalog

### Part 3 — Guild Catalog, Future Innovation Labs, and Primary Council Assignment

#### 3.1 Canonical GCRI Ecosystem Map

3.1.1 **Purpose of the Catalog.** This Part establishes the canonical, discoverable map of the GCRI membership ecosystem so that members can: (i) find the correct domain home; (ii) route contributions into the correct governance lane; (iii) understand reliance bounds and handling posture; and (iv) reduce duplication, ambiguity, and unsafe publication risk.\
3.1.2 **Open-to-all baseline; no gatekeeping by affiliation.** Participation across Future Innovation Labs, Guilds, Cells, and Platforms is open-to-all by default. Restrictions are permitted only for lawful constraints, handling class, safety gates, and PoC thresholds for controlled lanes; restriction by affiliation, ideology, or commercial position is prohibited.\
3.1.3 **Voluntary-by-default roles; opt-in workload only.** Baseline membership does not impose an obligation to contribute, attend, review, publish, disclose identity, or serve. Any workload-bearing role exists only by explicit opt-in acceptance recorded on the Platform, with scope, timebox, and exit rules.\
3.1.4 **Strict non-executing perimeter preserved everywhere.** No Lab, Guild, Platform workspace, Cell, or CERT may become an operator, dispatcher, regulator substitute, enforcement authority, intelligence service, procurement venue, or deal room; all ecosystem activity is evidence, methods, verification, and public-learning only.\
3.1.5 **Artifact-first outputs; no directives.** The unit of value is the publishable artifact: methods, benchmarks, ontologies, lineage rules, dataset/method cards, review reports, drills, evidence packs/proof packs, and publication-safe summaries—packaged with limitations, handling, and reliance bounds; outputs do not constitute instructions, commands, authorizations, or operational directives.\
3.1.6 **Platform-record primacy for names, scopes, and validity.** Names, scopes, governance assignments, role markers, badges, releases, sanctions, corrections, and public listings are authoritative only when recorded as Record-Valid acts on the Platform; off-platform branding or claims of “official” status are non-authoritative and may constitute misrepresentation.\
3.1.7 **Quintuple-helix composition expectation.** Each Lab and domain lane is designed to attract and retain participation across the quintuple helix to reduce blind spots, improve contestability, and sustain legitimacy under scrutiny; monoculture formation and sector capture are treated as integrity risks.\
3.1.8 **Safety-by-design baseline.** Every Lab and Guild lane operates under handling election discipline, publication safety gates, dual-use screening, disclosure routing constraints, and correction/supersession requirements; safety overrides convenience, visibility, and entitlement.\
3.1.9 **Creation/merger/split/retirement rule.** Any creation, merger, split, or retirement of a Lab or Guild requires a Record-Valid change act stating: rationale, safety and capture analysis, governance assignment, migration plan for artifacts/records/credits, continuity rules for standing, and a public-safe summary.\
3.1.10 **No implicit jurisdictional presence.** The canonical map is global by default. National/regional mirrors, branded local convenings, local Labs, Chapters, Councils, NWGs, Host programs, and CERT mobilizations are prohibited absent jurisdiction activation; global participation remains open regardless of local activation status.

***

#### 3.2 Member Roaming Model and “Home Lab” Requirement

3.2.1 **Roaming rights across Labs and Guilds.** Members may observe, contribute, comment, review (where eligible), and join Cells across any number of Labs and Guilds, subject only to handling constraints, lawful restrictions, and PoC requirements for controlled/restricted lanes.\
3.2.2 **Home Lab election; purpose.** Each member elects one Home Lab to anchor governance routing, rotation pool eligibility, seat-completion balancing, and accountability surfaces; the Home Lab is a routing and integrity primitive, not an exclusivity mechanism.\
3.2.3 **Home Lab switching; controlled mobility.** A member may switch Home Lab by Record-Valid act with an effective date. Switching may be rate-limited by rule to prevent manipulation of voting/review pools, while preserving legitimate mobility and evolving interests.\
3.2.4 **Contribution routing; anti-gaming.** Each contribution has a single lead-of-record Lab/Guild assignment. Co-tagging to other Labs is permitted only through Platform-recorded cross-routing to prevent double counting, score inflation, and review manipulation; clawbacks apply to proven gaming.\
3.2.5 **Cross-Lab portability of standing.** CRS, iVRS, ILA, and PoC status are portable across Labs without handling regression: portability does not grant access to higher handling lanes unless the receiving lane’s PoC and safety gates are satisfied.\
3.2.6 **Multi-Lab work patterns.** Cross-Lab initiatives must record: lead-of-record Lab, notified Labs, handling election, contestation lane, correction clock, and any required cross-council co-review; absence of this record is a release-blocking defect for cross-Lab outputs.\
3.2.7 **Role-marker eligibility impacts.** Eligibility for reviewer pools, steward roles, program committees, and other elevated privileges may depend on Home Lab election, PoC level, compliance posture, and helix balance needs; eligibility criteria must be published by record and auditable.\
3.2.8 **Observer mode.** Members may remain in Observer mode without electing a Home Lab and may participate globally at baseline levels; Observer mode is ineligible for certain elevated privileges that require a stable home anchor for capture resistance (e.g., rotation pools, stewardship roles, controlled-room governance duties).

***

#### 3.3 Future Innovation Labs Set (Primary Engagement Labs)

3.3.1 **Purpose of Future Innovation Labs.** Future Innovation Labs are the primary engagement homes for members, designed to cover systemic and niche risk within a domain while remaining interoperable across domains through shared evidence primitives, shared safety gates, and cross-Lab contestation pathways.\
3.3.2 **Scope statement requirements.** Each Lab maintains a Record-Valid scope statement specifying: domain scope; hard exclusions; typical artifact types; default handling posture; dual-use notes and known sensitivity zones; intended reliance audiences; and mandatory disclaimers.\
3.3.3 **Governance interface requirements.** Each Lab is assigned one Primary Council and must maintain: role ladders, review lanes, release gates, correction clock posture, contestation paths, and documented separation-of-duties controls; governance practices may strengthen safeguards but may not weaken them.\
3.3.4 **Composition targets and balance controls.** Each Lab designs for quintuple-helix balance, COI diversity, and geography/language inclusion. Concentration indicators (single-sector dominance, sponsor influence, repeated reviewer concentration) trigger seat-completion logic and neutrality review.\
3.3.5 **Lab-level safety posture.** Labs must explicitly identify their “hot zones” (market sensitivity, facility targeting, exploit sensitivity, discrimination risk, public safety panic risk) and define the default safety controls: abstraction-first publishing, controlled appendices, staged release, and disclosure routing.\
3.3.6 **Lab-level publication posture.** Public-safe summaries are the default. Where detail increases harm risk, Labs use controlled appendices with distribution logs and expiry. Release packaging must include limitations, uncertainty, reliance bounds, and correction path.\
3.3.7 **Lab-to-Guild coupling rules.** Labs may host niche Guild workstreams, Cells, and Clinics; any niche lane inherits Lab safeguards and must declare lead-of-record routing, handling election, and governance assignment; cross-cutting evidence Guilds may be invoked as method backbones.\
3.3.8 **Operating cadence.** Each Lab maintains a record-published cadence: backlog cycles, clinic windows, review windows, release windows, and deprecation/supersession windows; cadence is a coordination tool, not a participation obligation.\
3.3.9 **Council liaison roles.** Each Lab may designate non-executing liaison role markers to its Primary Council for routing, records completeness, and safety posture continuity; liaisons confer no authority beyond Platform-scoped duties.\
3.3.10 **Conflict hot-zones and mandatory disclaimers.** Each Lab must publish mandatory disclaimers and prohibited-topic boundaries for procurement, politics, regulated activities, and operational command; failure to include disclaimers is a release-blocking defect.

***

#### 3.4 Future Innovation Lab: Work

3.4.1 **Domain scope and exclusions.** The Work Lab covers systemic workforce resilience, labor market stress, skills transitions, continuity of work, and productivity under shock; it excludes operational staffing command, hiring directives, surveillance tasking, and any employment agency function.\
3.4.2 **Typical artifacts.** Outputs may include workforce risk taxonomies, labor stress-testing methods, skills resilience playbooks (non-operational), continuity metrics, scenario templates, dataset/method cards, and public-safe learning modules.\
3.4.3 **Handling posture and dual-use constraints.** The Work Lab treats surveillance enablement, discrimination, retaliation risk, and coercive profiling as dual-use hazards; outputs default to abstraction-first and require explicit rights-impact analysis where relevant.\
3.4.4 **Primary reliance audiences and bounds.** Intended audiences include public administrators, operators, employers, educators, and researchers; reliance is informational, not determinative; outputs must prohibit use as employment screening tools without lawful basis and safeguards.\
3.4.5 **Cross-Lab interfaces.** The Work Lab couples with Education (skills/credentials), Society (cohesion), Finance (macro and labor stress comparability), and Media (narrative safety) through shared templates and cross-review triggers.

***

#### 3.5 Future Innovation Lab: Energy

3.5.1 **Domain scope and exclusions.** The Energy Lab covers grid and energy system resilience, transition risk measurement, interdependency mapping, and outage cascade methods; it excludes operational control-room actions, dispatch directives, and facility-specific vulnerability disclosure.\
3.5.2 **Typical artifacts.** Outputs include resilience metrics, dependency maps at safe abstraction levels, outage coupling models, transition risk templates, drills (non-operational), method cards, and operator-safe patterns.\
3.5.3 **Targeting-cue prohibitions; abstraction-first.** Facility targeting cues and operationally actionable vulnerability details are restricted by default. Publishing defaults to abstraction-first, aggregation, and controlled appendices where necessary with distribution logs.\
3.5.4 **Primary reliance audiences and bounds.** Intended audiences include utilities, regulators, public agencies, DFIs, and researchers; reliance is scoped and non-operational; outputs must not be framed as operational instruction or compliance certification.\
3.5.5 **Cross-Lab interfaces.** Coupling is mandatory with Water, Food, Cyber/Outage, and Finance for WEFH and systemic cascade analysis.

***

#### 3.6 Future Innovation Lab: Media

3.6.1 **Domain scope and exclusions.** The Media Lab covers information integrity, provenance literacy, crisis communications safety, and measurement of information disorder; it excludes political campaigning, partisan coordination, and any covert influence operations.\
3.6.2 **Typical artifacts.** Outputs include provenance frameworks, misinformation measurement safeguards, crisis comms templates, correction protocols, verification playbooks for public-safe use, and learning artifacts.\
3.6.3 **Panic/manipulation safeguards.** The Media Lab treats panic amplification, rumor acceleration, market manipulation cues, and misquote risk as first-order hazards; outputs must include narrative safety constraints and misquote response patterns.\
3.6.4 **Primary reliance audiences and bounds.** Intended audiences include journalists, institutions, educators, and platforms; outputs are advisory and do not substitute for editorial judgment or legal obligations.\
3.6.5 **Cross-Lab interfaces.** The Media Lab interfaces with Society (cohesion), Cyber/Outage (incident comms), and election-safe posture controls across all Labs.

***

#### 3.7 Future Innovation Lab: Health

3.7.1 **Domain scope and exclusions.** The Health Lab covers health system resilience, surge capacity measurement, supply chain stress patterns, and public health preparedness methods; it excludes medical advice, clinical directives, and operational command of health responses.\
3.7.2 **Typical artifacts.** Outputs include resilience metrics, surge capacity methods, continuity templates, procurement-neutral supply chain stress methods, dataset/method cards, and public-safe training artifacts.\
3.7.3 **Privacy and sensitive data handling.** “No PII by default” applies. Any sensitive health data use requires lawful basis documentation, handling elevation, controlled access, and minimization; re-identification risk is treated as a safety gating criterion.\
3.7.4 **Primary reliance audiences and bounds.** Intended audiences include health administrators, emergency planners, researchers, and infrastructure operators; outputs are non-clinical, non-operational, and informational only.\
3.7.5 **Cross-Lab interfaces.** Interfaces are required with Water, Food, Society, and Early Warning for WEFH coupling and anticipatory action patterns.

***

#### 3.8 Future Innovation Lab: Sports

3.8.1 **Domain scope and exclusions.** The Sports Lab covers event risk methods, crowd safety measurement patterns, integrity systems, and continuity planning at non-operational abstraction; it excludes security command, crowd control directives, and venue vulnerability disclosure.\
3.8.2 **Typical artifacts.** Outputs include event risk templates, crowd safety measurement frameworks, integrity and governance patterns, drills (non-operational), and public-safe learning modules.\
3.8.3 **Safety posture.** Public safety, misinformation, and panic risk are prioritized; any facility or security-sensitive details default to controlled lanes or are abstracted.\
3.8.4 **Primary reliance audiences and bounds.** Intended audiences include event organizers, public agencies, leagues, and operators; outputs are advisory and not operational instruction.\
3.8.5 **Cross-Lab interfaces.** Primary coupling with Society, Media, and Health for community impact and crisis comms integrity.

***

#### 3.9 Future Innovation Lab: Space

3.9.1 **Domain scope and exclusions.** The Space Lab covers space dependency risk, space weather methods, satellite and ground dependency mapping at safe abstraction, and resilience patterns; it excludes classified or operationally sensitive targeting content and defense tasking.\
3.9.2 **Typical artifacts.** Outputs include dependency taxonomies, space weather scenario templates, resilience measurement methods, safe interdependency maps, and public-safe learning artifacts.\
3.9.3 **National security sensitivity posture.** Controlled dissemination and abstraction-first publishing are default where national security sensitivity is plausible; distribution logs and expiry apply to controlled materials.\
3.9.4 **Primary reliance audiences and bounds.** Intended audiences include operators, regulators, critical infrastructure stakeholders, and researchers; outputs are informational, non-operational, and non-classifying.\
3.9.5 **Cross-Lab interfaces.** Mandatory interfaces with Cyber/Outage, Energy, and Finance for dependency cascade modeling.

***

#### 3.10 Future Innovation Lab: Education

3.10.1 **Domain scope and exclusions.** The Education Lab covers learning continuity, competence scaling, credential integrity, and resilience of education systems; it excludes youth profiling, surveillance tasking, and operational direction of schools or ministries.\
3.10.2 **Typical artifacts.** Outputs include continuity methods, competence pathway designs (ILA/PoC-aligned), credential integrity patterns, learning resilience metrics, and public-safe curriculum artifacts.\
3.10.3 **Youth safeguarding and privacy.** Youth participation and youth-data handling are constrained by safeguarding rules, minimization, lawful basis requirements, and controlled dissemination where needed; doxxing and coercion protections are mandatory.\
3.10.4 **Primary reliance audiences and bounds.** Intended audiences include educators, ministries, training providers, and researchers; outputs are informational and not accreditation or licensure.\
3.10.5 **Cross-Lab interfaces.** Interfaces with Work (skills transitions), Society (inclusion), and Media (literacy) are required.

***

#### 3.11 Future Innovation Lab: Finance (Methods Only)

3.11.1 **Scope and hard exclusions.** The Finance Lab is strictly methods-only. It excludes underwriting, placement, custody, settlement, market-making, investment solicitation, product promotion, deal-room activity, and any activity that could be construed as regulated financial execution.\
3.11.2 **Typical artifacts.** Outputs include diligence compression methods, disclosure comparability templates, risk comparability ontologies, evidence packaging patterns (proof packs), scenario and stress templates, and public-safe education artifacts.\
3.11.3 **Market sensitivity controls.** The Finance Lab applies staged release, abstraction-first publishing, controlled lanes for market-moving content, strict reliance bounds, and distribution logging where sensitivity is plausible.\
3.11.4 **Primary reliance audiences and bounds.** Intended audiences include policy makers, risk professionals, DFIs, researchers, and operators; reliance is informational and explicitly non-solicitative and non-executing.\
3.11.5 **Cross-Lab interfaces.** Interfaces with Energy, Water, Cyber/Outage, and Society are mandatory to support systemic comparability without implying execution authority.

***

#### 3.12 Future Innovation Lab: Society

3.12.1 **Domain scope and exclusions.** The Society Lab covers social fragility, cohesion, legitimacy under stress, and trust-under-scrutiny patterns; it excludes partisan coordination, lobbying mandates, or political mobilization.\
3.12.2 **Typical artifacts.** Outputs include cohesion measurement methods (harm-aware), trust-under-scrutiny templates, grievance and remedy patterns (non-adjudicative), scenario frameworks, and public-safe learning artifacts.\
3.12.3 **Political-safety and election-safe posture.** Communications and artifacts must remain non-partisan and election-safe; outputs may analyze systemic risk without advocating for parties/candidates or instructing political activity.\
3.12.4 **Primary reliance audiences and bounds.** Intended audiences include public agencies, civil society, researchers, and operators; reliance is informational and must include rights-impact and harm analysis where relevant.\
3.12.5 **Cross-Lab interfaces.** Interfaces with Media, Work, Health, and Community Resilience are required to manage compound social risk.

***

#### 3.13 Future Innovation Lab: Water

3.13.1 **Domain scope and exclusions.** The Water Lab covers hydro-risk methods, drought/flood measurement, water utility resilience patterns, and WEFH coupling methods; it excludes operational command, facility vulnerability disclosure, and dispatch directives.\
3.13.2 **Typical artifacts.** Outputs include hydro-risk indices, drought/flood measurement frameworks, utility resilience patterns (operator-safe), scenario templates, and proof-pack packaging patterns.\
3.13.3 **Infrastructure and public safety sensitivity.** Facility targeting cues are prohibited by default; publishing is abstraction-first with controlled appendices only where strictly necessary and access-logged.\
3.13.4 **Primary reliance audiences and bounds.** Intended audiences include utilities, regulators, public agencies, DFIs, and researchers; reliance is informational and non-operational.\
3.13.5 **Cross-Lab interfaces.** Mandatory interfaces with Energy, Food, Health, and WEFH Systems for dependency and cascade modeling.

***

#### 3.14 Future Innovation Lab: Food

3.14.1 **Domain scope and exclusions.** The Food Lab covers food security metrics, supply chain stress methods, price shock analytics patterns, and resilience methods; it excludes procurement steering, market manipulation, and product promotion.\
3.14.2 **Typical artifacts.** Outputs include food security measurement frameworks, supply chain stress templates, shock scenario methods, dataset/method cards, and public-safe learning artifacts.\
3.14.3 **Market sensitivity and manipulation safeguards.** Outputs that could influence prices or market behavior are staged, abstracted, or moved to controlled lanes; reliance bounds and distribution constraints are mandatory.\
3.14.4 **Primary reliance audiences and bounds.** Intended audiences include public agencies, operators, DFIs, and researchers; reliance is informational and must not be used for collusive behavior.\
3.14.5 **Cross-Lab interfaces.** Mandatory interfaces with Water, Health, Finance, and WEFH Systems.

***

#### 3.15 Future Innovation Lab: Web

3.15.1 **Domain scope and exclusions.** The Web Lab covers platform resilience, trust and safety measurement, digital dependency mapping, and systemic digital risk methods; it excludes surveillance tasking, exploit publication, and operational harm enablement.\
3.15.2 **Typical artifacts.** Outputs include dependency maps at safe abstraction, trust and safety measurement frameworks, resilience patterns, incident learning templates, and public-safe education artifacts.\
3.15.3 **Dual-use controls.** Abuse enablement, surveillance patterns, exploit details, and operationally actionable vulnerability instructions are prohibited; responsible disclosure routing applies where relevant.\
3.15.4 **Primary reliance audiences and bounds.** Intended audiences include operators, regulators, researchers, and civil society; reliance is informational and non-operational.\
3.15.5 **Cross-Lab interfaces.** Mandatory interfaces with Cyber/Outage, Media, Society, and AI/Agentic Risk Governance lanes.

***

#### 3.16 Core Cross-Cutting Evidence Guilds (Available to All Labs)

3.16.1 **Purpose and relationship to Labs.** Core evidence Guilds provide reusable primitives—methods backbones, templates, and verification patterns—that serve all Labs; they are cross-cutting and must not be treated as exclusive or substituting for Lab domain ownership.\
3.16.2 **Evidence Engineering Guild.** Maintains artifact packaging standards, method/dataset card templates, benchmark harnesses, reproducibility checklists, and verification protocols; enforces provenance, limitations, and correction readiness.\
3.16.3 **Early Warning & Anticipatory Action Guild.** Maintains early warning measurement patterns, trigger documentation discipline, anticipatory action templates (non-operational), and event-to-evidence packaging; treats jurisdiction and public safety sensitivity as gating criteria.\
3.16.4 **GRIx Ontologies & Lineage Guild.** Maintains semantic interoperability, lineage rules, versioning, deprecation/migration discipline, and schema governance; ensures comparability and correctionability across domains.\
3.16.5 **Proof Packs (AEP) & Determinations Guild.** Maintains admissibility patterns, proof-pack BOM templates, determination packaging discipline, reliance bounds templates, and correction/supersession rules; prohibits any implication of external authority.\
3.16.6 **Critical Infrastructure Risk Guild.** Maintains operator-safe abstraction standards, targeting-cue prohibitions, dependency mapping patterns, and safe disclosure templates; default posture is abstraction-first.\
3.16.7 **Cyber / Outage Cascades Guild.** Maintains outage cascade modeling patterns, resilience measurement methods, and incident learning templates; prohibits exploit publication and provides responsible disclosure routing patterns.\
3.16.8 **Health Systems Risk Guild.** Maintains health system resilience measurement patterns and privacy-aware data governance templates; default “no PII by default,” with lawful basis gates for sensitive lanes.\
3.16.9 **WEFH Systems Guild.** Maintains WEFH coupling methods and systemic cascade patterns; mandatory cross-council review applies; abstraction-first publishing is default.\
3.16.10 **AI / Agentic Risk Governance Guild.** Maintains evidence-first risk governance patterns for AI/agentic systems; safety review is mandatory; abuse enablement is prohibited; controlled dissemination applies for high-risk content.\
3.16.11 **Information Integrity & Measurement Safety Guild.** Maintains measurement-can-harm controls, panic and manipulation safeguards, safe summary patterns, and misquote resilience methods.\
3.16.12 **Community Resilience Methods Guild.** Maintains protected participation patterns, grievance/remedy templates (non-adjudicative), equity-aware measurement safeguards, and community safety doctrine.\
3.16.13 **Finance-Interface Methods Guild.** Maintains market-neutral comparability templates and finance-interface evidence packaging methods; strict non-execution and no-solicitation posture applies.

***

#### 3.17 Cross-Cutting Platforms Serving All Labs and Guilds

3.17.1 **Nexus Journals (publication layer).** Nexus Journals provide the publication layer for artifacts with correction/supersession discipline, handling elections, and reliance bounds; publication does not imply endorsement or compliance certification.\
3.17.2 **Nexus Campaigns (time-boxed replication/learning).** Nexus Campaigns are time-boxed replication and learning drives used to scale competence and validate artifacts; they are non-partisan, non-executing, and prohibited from functioning as advocacy mobilization.\
3.17.3 **Nexus Registry (system-of-record).** The Registry is the authoritative record for membership states, role markers, acts, releases, sanctions, appeals, corrections, and public trust surfaces; mismatch resolution follows lock-and-dispute discipline.\
3.17.4 **Future Innovation Labs workspaces.** Labs use workspaces including issue queues, clinics, replication environments, and review rooms; workspace outputs must be record-valid to have standing beyond the workspace context.\
3.17.5 **Interoperability surfaces.** CRS/iVRS/ILA/PoC portability is supported across Labs with handling non-regression; portability does not relax safety gates, lawful constraints, or distribution rules.

***

#### 3.18 Primary Governance Council Assignment Rule (One Council per Lab/Guild)

3.18.1 **Assignment objective.** Each Lab and each Core evidence Guild has exactly one Primary Council as the accountable governance interface to prevent shadow governance, fragmented authority, and inconsistent safety posture.\
3.18.2 **Assignment criteria.** Assignments are made by record based on: domain competence fit, safety profile (dual-use, infrastructure sensitivity, market sensitivity), rights/community impact profile, interoperability needs, and capture-resistance capacity (rotation and recusal discipline).\
3.18.3 **Council assignment for each Future Innovation Lab.** Each Lab’s Primary Council assignment is recorded and published in a table-by-record, including effective date, rationale summary, and cross-council co-review requirements where applicable.\
3.18.4 **Council assignment for each Core evidence Guild.** Each Core evidence Guild’s Primary Council assignment is recorded and published by table-by-record with the same discipline as 3.18.3.\
3.18.5 **Cross-council review triggers.** Regardless of Primary assignment, cross-council review is mandatory where dual-use risk, infrastructure sensitivity, market sensitivity, rights impacts, or unresolved quality disputes are plausible.\
3.18.6 **Seat completion logic.** Where helix balance, integrity capacity, or reviewer rotation depth is insufficient, releases may be conditioned on seat completion: independent reviewers, co-review, rotation adjustments, or Stewardship safety gate elevation.

***

#### 3.19 Lab/Guild Scope Statements, Reliance Bounds, and Handling Defaults (Binding)

3.19.1 **Mandatory scope statement fields.** Scope statements must include: domain scope, exclusions, typical artifact types, default handling election, known dual-use risks, intended reliance audiences, conflict hot-zones, and mandatory disclaimers.\
3.19.2 **Handling default election rules.** Public-safe is the default handling posture. Elevation to controlled/restricted requires recorded criteria, PoC thresholds, distribution logs, and safety review triggers; declassification follows recorded rules only.\
3.19.3 **Reliance bounds template requirements.** Every release must include intended use, non-intended use, limitations, uncertainty disclosures, expiry/review date, correction/supersession path, and handling inheritance requirements for reuse.\
3.19.4 **Public-safe summaries and staged release.** When detail raises harm risk, a public-safe summary is released first, with controlled appendices staged separately under distribution controls; summary must remain faithful, non-misleading, and limitation-forward.\
3.19.5 **Deprecation and supersession discipline.** No silent edits are permitted for record-valid releases. Deprecations and supersessions must include diffs, migration notes where applicable, and a clear “current” pointer.

***

#### 3.20 Jurisdictional Mirrors Rule (National/Regional Instances)

3.20.1 **Global participation remains open.** Members may participate in global Labs and Guilds regardless of jurisdiction, subject to lawful constraints, handling elections, and safety gates.\
3.20.2 **Mirror activation requirement.** Any national/regional mirror (including branded local Labs, Chapters, Councils, NWGs, Host programs, and CERT mobilizations) requires jurisdiction activation by record and mandate evidence from competent authorities.\
3.20.3 **Labeling and public listings.** Mirrors must be publicly labeled “Activated” or “Global-only” with scope, limitations, handling posture, and expiry/review date; public listings are authoritative only when sourced from the Registry record.\
3.20.4 **De-recognition, pause, and reversion.** Mandate withdrawal or expiry triggers pause of local activities and reversion to global-only participation; records and public listings must be updated without delay by record.\
3.20.5 **Local law conflicts; abstention protocol.** Where local law conflicts with membership rules, local operations must not proceed. The conflict is recorded, escalated to Stewardship/Trustees as appropriate, and the default posture is abstention until resolved under lawful and safety constraints.


---

# 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/iii.-catalog.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.