# XX. Chapters

### Part 20 — Chapters, State Councils, National Working Groups, Host Institutions, CERTs

*(Binding objective: enable local adoption of evidence-grade work **without** creating operational authority; enforce **jurisdiction gating** and the **non-executing perimeter**; prevent misrepresentation; preserve safety, neutrality, and record-valid accountability.)*

#### 20.1 Purpose, Scope, and System Boundary

20.1.1 **Purpose.** Provide jurisdictional adoption pathways for evidence work (methods, verification, learning, readiness patterns) while preventing “shadow institutions” and operational command.\
20.1.2 **Scope.** Chapters, State Councils, National Working Groups (NWGs), Host Institutions, jurisdictional CCells, and CERT mobilizations (measurement support only).\
20.1.3 **Non-executing perimeter reaffirmed.** No command, no dispatch, no enforcement, no procurement steering, no underwriting/custody/settlement, no intelligence tasking.\
20.1.4 **Safeguards supremacy.** This Part is subordinate to and must comply with Parts 0, 2, 3, 18, 19, and 22; safety, handling, and due process override convenience.\
20.1.5 **Voluntary-by-default.** Participation and roles are opt-in; obligations attach only upon acceptance of roles, handling classes, and record-valid participation.

***

#### 20.2 Jurisdiction Activation Rule

20.2.1 **Definition of “in-jurisdiction operating presence.”** Bright-line tests for presence: local branding, local convenings, local program claims, local “chapter/council/NWG/CERT” labels, local hosting, local recruitment using local mandate claims.\
20.2.2 **Activation prerequisites.** (i) State Council constituted by record; (ii) mandate support evidenced by competent authority (as defined).\
20.2.3 **Competent authority standard.** Recognize mandate evidence from competent administrative authorities (agency/ministry/regulator/utility/authorized public institution) rather than political claims.\
20.2.4 **Mandate evidence forms.** Minimum fields: issuer, scope, intended use, lawful basis (where applicable), non-endorsement language, expiry, renewal terms, contact verification method.\
20.2.5 **Prohibited presence absent activation.** No “office,” “node,” “chapter,” “program,” “state council,” “NWC/NWG,” “host institution,” or “CERT” claims; no local public listings.\
20.2.6 **Public listing requirements.** Every public mention must display status (Activated vs Global-only), scope, expiry, limitations, and reliance bounds.\
20.2.7 **Automatic suspension on mandate withdrawal/expiry.** Lapse triggers immediate pause and reversion to Global-only posture, recorded and publicly reflected as required.\
20.2.8 **Dispute handling for activation controversies.** Contested activations route to Part 22; interim status labeling and holds are mandatory.\
20.2.9 **Record-validity + distribution logging for activation acts.** Activation records are governance-critical; distribution logs capture who received mandate confirmations and status notices.

***

#### 20.3 Jurisdictional Topology

20.3.1 **Local governance wiring summary.** Local mirrors operate as **interfaces** to global Guilds/Councils, not separate sovereign authorities.\
20.3.2 **Primary Council anchoring invariant.** One Primary Council per Guild remains unchanged; local bodies cannot re-anchor or fork Council authority.\
20.3.3 **Stewardship safety oversight.** Stewardship Committee retains safety gates, stop-the-line holds, and handling escalation authority over local outputs.\
20.3.4 **Trustees escalation authority.** Trustees may intervene for perimeter breaches, systematic misrepresentation, repeated safety failures, or capture indicators.\
20.3.5 **Contestation rights preserved.** Local outputs are contestable via Guild/Council lanes; cross-council triggers apply for WEFH, cyber-AI coupling, CI sensitivity, and market sensitivity.\
20.3.6 **No shadow governance rule.** Local bodies cannot create independent authority, licensing, certification, procurement guidance, or operational programs.

***

#### 20.4 Chapters

20.4.1 **Definition and permitted purpose.** Community presence for learning, clinics, replication, and public-safe evidence literacy; no representation authority.\
20.4.2 **Formation requirements.** Record fields: scope, lead Guild mapping, steward, handling election, cadence, permitted outputs, expiry, renewal conditions.\
20.4.3 **Limitations.** No political mobilization, no procurement influence, no vendor endorsements, no “official” representation claims, no “policy mandate” claims.\
20.4.4 **Chapter convenings.** Safe-meeting scripts, attendee minimization, recording defaults, distribution controls, and neutrality enforcement.\
20.4.5 **Chapter outputs.** Artifact packaging only; mandatory limitations/reliance bounds/expiry/correction clock; public-safe default.\
20.4.6 **Chapter financial rules.** Nonprofit-compatible cost recovery only; no pay-to-play governance; sponsor influence caps; transparent minima.\
20.4.7 **Branding and naming.** Approved naming conventions; mandatory status labeling (Activated vs Global-only); prohibited terms list enforced.\
20.4.8 **Dissolution and archival.** Dissolve-by-default, archive outputs, preserve correction links, enforce handling survival obligations.

***

#### 20.5 State Councils

20.5.1 **Definition and role.** Jurisdictional legitimacy anchor for local adoption pathways; not a government body; not a regulator; no operational authority.\
20.5.2 **Constitution-by-record.** Minimum fields: scope, term, expiry, composition rules, reserved matters, handling regime, dispute lanes, non-executing disclaimer.\
20.5.3 **Mandate evidence.** Sourcing, validation, renewal clocks, and withdrawal handling; verification of issuer authenticity is required.\
20.5.4 **Composition requirements.** Quintuple-helix balance, independence norms, COI controls, rotation, and influence caps; no single-helix dominance.\
20.5.5 **Reserved matters.** Activation acts, NWG creation, Host Institution designation, and CERT approval (measurement-only) are reserved and record-valid.\
20.5.6 **Limits.** No enforcement, no operational directives, no procurement steering, no licensing/certification, no regulatory function, no budget allocation authority.\
20.5.7 **Minutes and identity minimization.** Role markers default; identity cell minimized; access-logged records; no public rosters by default.\
20.5.8 **Public-safe transparency minima.** Publish status, scope, expiry, limitations, and how to contest; never imply governmental delegation.\
20.5.9 **De-recognition and reconstitution.** Suspension triggers, reconstitution procedures, and continuity rules; automatic pause on mandate lapse.

***

#### 20.6 National Working Groups

20.6.1 **Definition.** Time-boxed evidence programs for methods adoption, evidence packaging, training, and pilots—informational and non-directive.\
20.6.2 **Charter-by-record.** Scope, deliverables, timebox, lead Guild-of-record, handling election, roles/PoC gates, outputs, and correction posture.\
20.6.3 **Relationship to Guild backlogs and CCells.** NWGs route work into Guild backlogs; CCells execute work units under the NWG’s scope and handling.\
20.6.4 **Composition and balance.** Helix balance, COI screening, reviewer independence, and inclusion targets; safeguards against local capture.\
20.6.5 **Prohibited actions.** Procurement steering, operational directives, enforcement, exclusivity arrangements, market coordination, or “deal room” behavior.\
20.6.6 **Outputs and release discipline.** Public-safe default; controlled annexes minimized, logged, and expiry-bound; no silent edits.\
20.6.7 **Funding and in-kind.** Nonprofit-compatible; transparent minima; sponsor influence caps; separation from governance decisions.\
20.6.8 **Performance reporting.** iVRS-linked; uncertainty and limitations mandatory; progress measured by admissible artifacts, not narratives.\
20.6.9 **Dissolution and transition.** Dissolve-by-default; archive deliverables; supersession discipline; migration to next timebox by record.

***

#### 20.7 Host Institutions

20.7.1 **Definition.** Sovereign-compatible hosts for compute-to-data, training environments, and safe convening—supporting evidence work only.\
20.7.2 **Designation prerequisites.** Activation present; mandate evidence; capacity and integrity checks; handling readiness and auditability.\
20.7.3 **Minimum capabilities baseline.** Data governance, handling controls, access logging, secure rooms (virtual/physical), incident routing, and retention discipline.\
20.7.4 **Sovereign data zone alignment.** Compute-to-data posture; no PII by default; lawful basis documentation where unavoidable; segmentation and export-control constraints.\
20.7.5 **Obligations.** Handling discipline, access logs, distribution controls, incident routing, and cooperation with correction/supersession.\
20.7.6 **Limitations.** Host status does not confer authority; outputs remain advisory artifacts with reliance bounds; no conversion into directives by implication.\
20.7.7 **Hosting agreements posture.** Non-executing, non-agency, non-employment; no regulated execution; clear liability and non-endorsement blocks.\
20.7.8 **Program types.** Labs, replication clinics, observatories, training cohorts, and controlled data rooms (where permitted).\
20.7.9 **Offboarding and termination.** Termination triggers, data disposition, de-identification, access revocation, and survivability of handling obligations.

***

#### 20.8 Competence Cells in Jurisdictions

20.8.1 **Formation requirement.** If local presence is implied, activation is required; formation record includes lead Guild mapping, scope, timebox, and PoC gates.\
20.8.2 **Scope discipline.** CCells produce work units (methods, replication, packaging, safe summaries), not operational plans or directives.\
20.8.3 **Handling and distribution.** Handling election is mandatory; controlled outputs require distribution logs; watermarking defaults apply where needed.\
20.8.4 **Identity minimization.** Role markers default; protected participation is emphasized in local contexts with heightened reprisal risk.\
20.8.5 **Security posture.** Secure rooms, device hygiene, access logging, and leak response readiness; restricted lanes require stronger controls.\
20.8.6 **Deliverable standards.** Mandatory limitations, reliance bounds, expiry, correction clock, provenance pointers, and review logs.\
20.8.7 **Dissolution and reporting.** Dissolve-by-default; archive outputs; public-safe reporting minima; correction links preserved.

***

#### 20.9 CERT Mobilizations

20.9.1 **Definition.** Evidence support only: measurement, verification, safe summaries, and learning artifacts; strictly non-executing.\
20.9.2 **Trigger criteria.** Public interest, safety/integrity need, lawful basis, and evidence value; no “mobilization” for political theatre.\
20.9.3 **Activation dependency and liaison constraints.** If operating presence is implied, activation is required; liaison is routing-only—no command authority.\
20.9.4 **Formation record requirements.** Scope, triggers, lead Guild, liaison, handling class, expiry, distribution plan, after-action obligations.\
20.9.5 **Handling inheritance.** CERT inherits elevated handling; distribution logging is mandatory; staged release patterns are default.\
20.9.6 **Responsible disclosure routing.** Security/vulnerability and public safety constraints apply; no exploit detail publication; proper escalation lanes recorded.\
20.9.7 **Prohibited acts.** Operational directives, targeting cues, exploit instructions, procurement steering, or coordination of responders.\
20.9.8 **Post-mobilization obligations.** After-action record, corrections discipline, deprecation of unsafe material, and publication of public-safe learning.

***

#### 20.10 Cross-Border and Regional Mirrors

20.10.1 **When permitted.** Cross-border mirrors are informational/federative only; RNFD/UNSFD interfaces do not relax jurisdictional gates.\
20.10.2 **Consent-based sharing.** Data sharing is consent-based and handling-preserving; compute-to-data favored; no forced centralization.\
20.10.3 **Export controls and sanctions.** Access gating, abstention/pause rules, and restricted dissemination apply.\
20.10.4 **Multi-language and accessibility.** Translation integrity and accessibility accommodations are required where feasible; meaning-preservation is enforced.\
20.10.5 **Conflict of laws.** Abstention/pause by default; record-valid explanation; minimize exposure.

***

#### 20.11 Naming, Branding, and Public Representation Controls

20.11.1 **Mandatory status labeling.** “Activated” vs “Global-only” labels are required on all local pages, notices, and materials.\
20.11.2 **Prohibited representations.** No government delegation, certification, enforcement authority, “official node,” or regulatory standing claims.\
20.11.3 **Spokesperson rules.** Permissioned attribution only; scope/expiry-bound; role markers default; comms integrity review required for sensitive domains.\
20.11.4 **Co-branding restrictions.** Sponsor/partner co-branding cannot imply influence; requires disclosure minima and neutrality checks.\
20.11.5 **Misrepresentation response.** Takedown and clarification workflows link to Part 19; repeated breaches trigger suspensions and public-safe notices.

***

#### 20.12 Local Convening Rules

20.12.1 **Safe-meeting scripts.** Antitrust/procurement prohibited topics; interrupt protocol; escalation triggers; minimal minutes.\
20.12.2 **Handling election for every convening.** Room class determines recording permissions, distribution rules, and artifacts.\
20.12.3 **Attendee minimization.** Role markers default; identity minimization cell optional; attendee lists are minimized and access-logged where controlled.\
20.12.4 **Recording/photography rules.** Default prohibited unless elected by record; watermarking and distribution logs for controlled outputs.\
20.12.5 **Public-safe summaries and corrections.** Default to public-safe summaries; correction windows and supersession rules apply.

***

#### 20.13 Local Financial and Resource Controls

20.13.1 **Permissible local cost recovery.** Venue/tooling/training costs only; no hidden spreads; transparent minima.\
20.13.2 **Scholarships/waivers/sliding scale.** Equity-first seat completion and inclusion; avoid prestige capture.\
20.13.3 **Sponsor concentration controls.** Local concentration caps and influence indicators; disclosure minima mandatory.\
20.13.4 **No pay-to-play governance.** Explicit prohibition on paid votes, agenda control, badges, roles, or seats.\
20.13.5 **Reporting minima.** Public-safe reporting for funding sources (where lawful), spending categories, and conflict mitigations.

***

#### 20.14 Incident, Integrity, and Safety Operations in Jurisdictions

20.14.1 **Incident routing lanes.** Safety, security, conduct, and misrepresentation lanes with defined triage clocks and escalation triggers.\
20.14.2 **Emergency governance mode.** Time-boxed; expiry-bound; higher handling; mandatory after-action and ratification where required.\
20.14.3 **Leak response and audits.** Watermark drills, distribution log audits, and containment playbooks; public-safe comms discipline.\
20.14.4 **Safety holds and release pauses.** Stewardship authority to pause releases; reopen conditions are recorded; no indefinite silent holds.\
20.14.5 **Trustees escalation.** Severe or repeated breaches escalate to Trustees; may trigger de-recognition and reversion to Global-only.

***

#### 20.15 Lifecycle and Compliance Testing for Local Mirrors

20.15.1 **Lifecycle.** Formation → operation → reporting → renewal → dissolution; expiry-by-default is enforced.\
20.15.2 **Control testing calendar.** Records completeness, neutrality compliance, handling compliance, corrections discipline, and distribution logs.\
20.15.3 **Seat completion and helix balance audits.** Local audits detect dominance/capture and address gaps with scholarships and targeted invitations.\
20.15.4 **Corrective actions.** Remediation plans are recorded; closure requires verification; repeat failures escalate.\
20.15.5 **Reversion-to-global-only protocol.** Automatic upon mandate lapse/non-compliance; public listing updated; access and branding permissions revoked by record.


---

# 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/xx.-chapters.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.