# VII. Operating System

### Part 7 — Convening Operating System

#### 7.1 Convening Doctrine and Scope (Convening as Evidence Instrument)

7.1.1 **Convenings produce artifacts, not authority.** Every convening exists to produce evidence-grade artifacts (methods, reviews, replication logs, Proof Pack pointers, minutes where elected, decision records where designated). Convenings do not issue directives, mandates, operational orders, or authoritative determinations.\
7.1.2 **Convening types and intended outcomes.** Convenings are categorized by purpose and output class, including evidence rooms (closed-loop review), replication clinics (reproducibility evidence), Future Innovation Labs sessions (domain collaboration), sprints (time-boxed builds), hearings (adversarial review), briefings (safe summaries), and trainings (PoC-linked learning).\
7.1.3 **Reliance bounds for convening outputs.** Every convening output must include intended use, non-intended use, limitations, uncertainty statements, expiry, and correction path; convening outputs cannot be represented as compliance determinations, legal advice, or operational guidance.\
7.1.4 **Handling-first convening rule.** Each convening must elect a room class and handling class by record in advance; all materials, outputs, and attendee obligations inherit that class unless a recorded elevation occurs.\
7.1.5 **Platform-record primacy for convenings.** Convening notices, role assignments, session dockets, outputs, distribution logs, and corrections are authoritative only when recorded on the platform; off-platform invitations, minutes, or claims are non-authoritative and may trigger mismatch locks.\
7.1.6 **Neutrality and political-safety posture.** Convenings must be non-partisan, election-safe, and institutionally neutral; convening outputs must be framed as evidence and methods, not political positions, endorsements, or advocacy instructions.\
7.1.7 **Competition/procurement hygiene.** Convenings must apply safe-meeting baselines and prohibited-topic lists; moderators must interrupt prohibited discussion and route to the escalation lane if needed; no bid coordination, pricing discussion, market allocation, or vendor steering is permitted.\
7.1.8 **No operational coordination rule.** Convenings must not perform dispatch, command, enforcement coordination, or authority-like emergency management functions; incident-related sessions are learning and evidence capture only.\
7.1.9 **No “deal room” rule.** Convenings cannot be used to raise capital, negotiate contracts, coordinate procurement outcomes, allocate business, or create exclusivity arrangements; any attempt triggers stop-the-line holds and may result in sanctions.\
7.1.10 **Convening liability and disclaimer pack.** Every session must include an inlined disclaimer pack (non-executing perimeter, non-endorsement, no procurement steering, no deal room, no compliance certification, reliance bounds, handling rules, recording/quote rules).

***

#### 7.2 Annual Flagship Integration and Calendar Architecture

7.2.1 **Annual integration rule.** GCRI evidence rooms and Lab sessions may align to GRF flagship cadence to support global coordination of methods and public-safe outputs; alignment does not confer GRF authority over GCRI convenings or alter GCRI’s perimeter.\
7.2.2 **Independent GCRI convenings permitted.** GCRI may convene independently year-round; all safeguards, handling rules, and record-validity requirements apply equally to independent convenings.\
7.2.3 **Global calendar-safe design.** Convenings must use neutral titles, minimal metadata, role-marker listing by default, and time-window invites where appropriate; sensitive sessions avoid revealing topic sensitivity through calendar fields.\
7.2.4 **Formation-year vs steady-state cadence.** Convening cadence (formation-year intensity vs steady-state schedule) is elected and recorded by rule, including minimum notice periods, planned review windows, and correction cycles.\
7.2.5 **Seasonality and surge windows.** Convening calendar design must recognize surge periods around release cycles, correction cycles, drills, and incident learning; surge windows trigger heightened handling posture and capacity planning.\
7.2.6 **Multi-timezone and accessibility planning.** Convenings must support multi-timezone participation through scheduling rotation, asynchronous artifact review lanes, and accessible formats (captions, transcripts where permitted, low-bandwidth options).\
7.2.7 **Convening portfolio balance.** Program planning must balance Guild and Lab coverage, helix participation, geography/language inclusion, and risk-domain diversity, without compromising safety or neutrality.\
7.2.8 **Crisis mode calendar behavior.** Crisis mode may pause public-facing convenings, shift to controlled lanes, and apply emergency templates; all crisis adjustments must be time-boxed and recorded with reasons.\
7.2.9 **Deconfliction with sensitive periods.** Convenings must avoid elections, market-sensitive windows, and active incidents where convening could amplify harm; deconfliction decisions are recorded with minimization.\
7.2.10 **Public listing posture.** What is publicly listed (title, time, safe summary) vs controlled (topics, attendees, materials) is governed by handling class; public listings must not reveal sensitive details by implication.

***

#### 7.3 Convening Taxonomy (Formats, Rooms, and Maturity Levels)

7.3.1 **Evidence Room.** Closed-loop review sessions producing record-valid outcomes: review findings, required changes, dissent entries, badge eligibility decisions where applicable, and correction clock activations.\
7.3.2 **Replication Clinic.** Sessions executing method replays and producing reproducibility evidence: replication logs, environment manifests, divergence notes, and updated limitation statements.\
7.3.3 **Future Innovation Labs Session.** Domain sessions anchored to Primary Councils with cross-helix participation expectations, producing method cards, research notes, issue backlogs, and safe publication drafts.\
7.3.4 **Benchmark Sprint / Evaluation Jam.** Time-boxed evaluation cycles producing benchmark results, test harness outputs, anti-gaming attestations, and standardized reporting fields with uncertainty disclosures.\
7.3.5 **Hearing / Adversarial Review Session.** Structured contestation sessions designed to surface weaknesses, preserve dissent, and document minority reports; outcomes are recorded with reason codes and correction triggers.\
7.3.6 **Public-Safe Briefing.** Public-safe sessions producing safe summaries, literacy artifacts, and “what is known/unknown” outputs with explicit uncertainty and non-amplification posture.\
7.3.7 **Controlled Briefing.** Restricted participant sessions requiring distribution logs and watermarked materials, producing controlled annexes and minimally descriptive public-safe summaries.\
7.3.8 **Training Workshop.** PoC-linked competence sessions producing learning artifacts, PoC evidence records where applicable, and non-licensure disclaimers with clear scope limits.\
7.3.9 **Incident Learning Session.** Post-incident learning sessions producing evidence capture templates, after-action summaries, what-changed records, and what-was-withheld notes—never operational instructions.\
7.3.10 **Mixed-format convenings.** Mixed sessions must segment by room class or handling lane; handling inheritance applies and any transitions require explicit recorded routing and participant re-eligibility checks.

***

#### 7.4 Program Committee and Governance Mechanics

7.4.1 **Program committee purpose.** Program committees exist to protect agenda integrity, enforce safety posture, and maintain neutrality; they are not content authorities and do not control scientific conclusions.\
7.4.2 **Appointment and rotation.** Program committees are appointed by record with term limits, helix balance requirements, and capture resistance controls; membership rotates and recusals are enforced.\
7.4.3 **Selection criteria.** Session selection is based on evidence readiness, public value, safety constraints, contestability, diversity of perspectives, and ability to produce record-valid artifacts under scrutiny.\
7.4.4 **COI screening and recusals.** COI disclosures are mandatory; conflicts trigger recusal, substitution, and, where needed, reassignment to alternate reviewers or alternate sessions.\
7.4.5 **Reviewer rotation pools.** Reviewer pools are managed to prevent dominance, ensure competence fit, and support auditability; paid relationships cannot override rotation rules.\
7.4.6 **Escalation to Stewardship Committee.** Dual-use, market-sensitive, targeting-risk, or rights-impact sessions require Stewardship escalation and may require safety veto review before proceeding.\
7.4.7 **Trustees oversight triggers.** Trustees are notified and may intervene where sessions carry high institutional risk, repeated integrity failures occur, or sponsor influence attempts are detected.\
7.4.8 **Decision records and contestation windows.** Program decisions (accept/reject/hold) must be reason-coded by record and remain contestable through defined windows with dissent preserved.\
7.4.9 **Sponsor influence prohibitions.** Sponsors cannot purchase agenda control, speaker slots, outcomes, or release authority; any attempt triggers stop-the-line holds and public-safe clarifications where appropriate.\
7.4.10 **Minimum transparency outputs.** Program committees publish public-safe summaries of the program portfolio where permissible, including limitations, handling posture, and correction readiness.

***

#### 7.5 Evidence-to-Session Maturity Ladder (Readiness Pipeline)

7.5.1 **Draft → Pre-review.** Materials must meet minimum fields (scope, intended audience, limitations, evidence pointers) before they can be scheduled; incomplete submissions are returned without prejudice.\
7.5.2 **Reviewed → Safety screened.** Review must be completed before safety screening where possible; safety screening evaluates dual-use, targeting cues, market sensitivity, and narrative harm.\
7.5.3 **Room-brief ready.** Room-brief readiness requires a briefing note, reliance bounds, handling election, correction clock election, and clear “what will be decided vs explored” boundaries.\
7.5.4 **Session-ready.** Session-ready status requires participant eligibility gates, COI resolution, distribution plan, recording election, and template completion, all recorded by platform.\
7.5.5 **Post-session corrections.** Sessions activate correction windows; errata and supersession rules apply immediately, and recipients must be reachable for correction redistribution where required.\
7.5.6 **Deprecation and withdrawal.** Materials may be withdrawn or deprecated for error discovery, misuse risk, or safety concerns; withdrawal must be recorded with reasons and public-safe notice where appropriate.\
7.5.7 **Versioning rules.** Session materials cannot be silently edited; changes require version increments, diffs, and re-screening if the change could alter safety, reliance, or claims.\
7.5.8 **Evidence pack integration.** Proof Packs/AEP pointers must be linked where applicable, with admissibility checklists and explicit notes on what evidence is missing or unavailable.\
7.5.9 **Dissent capture templates.** Dissent and minority reports are templated and must be recorded when material disagreement exists; dissent is treated as safety, not disloyalty.\
7.5.10 **Publication routing.** Post-session routing determines whether outputs go to Nexus Journals, remain as controlled appendices, are staged for release, or are held under safety veto with expiry and reopen conditions.

***

#### 7.6 Session Artifact Requirements (What Every Session Must Produce)

7.6.1 **Session docket.** Each session must produce a docket stating scope, objectives, deliverables, roles, timebox, and explicit authority limits.\
7.6.2 **Briefing note.** Each session must produce a briefing note (public-safe or controlled), including limitations, uncertainty, and reliance bounds; briefing notes must avoid operational instructions.\
7.6.3 **Artifact pointers.** Sessions must record pointers to artifacts under discussion (Proof Packs, datasets, methods, harnesses) with handling inheritance and access constraints.\
7.6.4 **Handling election.** Handling class and room class election must be recorded, including distribution rules, watermark defaults, and recording/photography policy.\
7.6.5 **Reliance bounds statement.** A reliance bounds statement must be attached to each session’s outputs, including expiry and correction path, and explicit non-endorsement language.\
7.6.6 **COI log and recusal actions.** COI disclosures and recusals must be recorded as a session artifact, with substitutions documented and minimal necessary identity exposure.\
7.6.7 **Decision record and action register.** Where decisions are made, a decision record and action register must be produced with owner, due date, and timebox; actions dissolve by default if not renewed by record.\
7.6.8 **Dissent/minority report capture.** If material disagreement exists, dissent must be captured and preserved, including a safe form suitable for later publication if feasible.\
7.6.9 **Post-session summary.** A post-session summary is mandatory; public-safe is the default with controlled annex minimized; summaries must include limits and what was withheld.\
7.6.10 **Correction clock activation.** The session must elect and activate correction clocks, including errata window length, supersession triggers, and redistribution requirements.

***

#### 7.7 Participant Eligibility, Role Gates, and Protected Participation

7.7.1 **Baseline eligibility.** Any active participation requires PoC0 orientation and handling acknowledgment; observers may attend public-safe sessions without additional gates.\
7.7.2 **Elevated role gates.** Moderators, reviewers, stewards, recorders, and safety leads require PoC thresholds, handling training, and rotation eligibility; role markers are time-boxed and revocable.\
7.7.3 **Handling training by room class.** Controlled and Restricted rooms require additional handling training and distribution-log competence; failure to comply results in removal from the room and access restriction.\
7.7.4 **Identity options and attribution controls.** Pseudonymous participation is permitted by default; authority is expressed via role markers; named attribution requires explicit consent, scope, and expiry.\
7.7.5 **Protected participation.** Protected participation includes anti-retaliation safeguards, safe reporting channels, identity minimization, and “no compulsory disclosure” posture absent lawful necessity.\
7.7.6 **Public-sector constraints.** Public officials must comply with ethics rules, gift constraints, and mandate safety; participation must not be used to claim governmental endorsement.\
7.7.7 **Media participation rules.** Media participants must comply with information integrity constraints, embargo behavior, and quote rules; convenings are not press conferences unless explicitly designated.\
7.7.8 **Accessibility and inclusion.** Convenings must offer accommodations where feasible (language support, captions, accessible materials) and provide asynchronous participation paths for low-resource members.\
7.7.9 **Removal/suspension during sessions.** Conduct breaches, safety risks, or handling violations permit immediate removal under stop-the-line authority, followed by recorded reason codes and due process lanes.\
7.7.10 **Post-session obligations.** Participants assigned actions must comply with handling survival obligations, correction participation, and evidence integrity requirements until dissolution-by-default or recorded closure.

***

#### 7.8 Room Classes, Recording Rules, and Distribution Controls

7.8.1 **Room class taxonomy.** Rooms are classified as Public-Safe, Controlled, Restricted, or Incident Mode, each with specific eligibility, distribution, and recording constraints.\
7.8.2 **Consent requirements.** Consent is required for recording, quotes, photography, and named attribution; consent must be recorded with scope and expiry.\
7.8.3 **Recording defaults.** Default is “no recording” unless explicitly elected by record; if recording is elected, distribution rules, redaction needs, and retention periods must be specified.\
7.8.4 **Photography rules.** Default is no photography; exceptions require recorded election and may require watermarking; screenshots are treated as distribution events in controlled/restricted rooms.\
7.8.5 **Attendee list minimization.** Attendee lists are minimized by default (role markers preferred); identity is maintained in a limited identity cell where necessary under a two-person rule.\
7.8.6 **Distribution logs.** Controlled and Restricted outputs require distribution logs; recipients must be enumerated or recorded via validated access mechanisms, and expiries must be tracked.\
7.8.7 **Watermarking and leak response.** Watermarking is default for controlled/restricted outputs where feasible; leak response includes containment, investigation, reason-coded actions, and sanctions routing.\
7.8.8 **Embargo and delayed-release rules.** Embargo may be applied for market/public safety sensitivity; embargo periods require expiry and planned reevaluation; embargo does not permit silent indefinite holds.\
7.8.9 **Secure workspace controls.** Access is least-privilege and time-boxed; audit logs record access and changes; controlled rooms require strong authentication and anomaly detection posture.\
7.8.10 **Cross-border sharing constraints.** Sharing must comply with sanctions/export controls/local law and handling rules; when conflicts arise, abstention and escalation are recorded.

***

#### 7.9 Competition / Procurement / Market Neutrality Controls for Convenings

7.9.1 **Prohibited topics.** Prohibited topics include pricing, bids, market allocation, customer restrictions, collusive coordination, and confidential competitive strategy sharing.\
7.9.2 **Procurement steering prohibitions.** Convenings cannot create vendor shortlists, endorse vendors, steer procurements, coordinate bids, or influence award outcomes.\
7.9.3 **Safe-meeting script.** Each session begins with a safe-meeting opening statement, an interrupt protocol, and escalation routing; moderators are required to enforce it.\
7.9.4 **Controlled minutes discipline.** Minutes are minimized; sensitive content is abstracted; where redactions occur, they must be reason-coded; “no minutes” is permitted where allowed by handling class and recorded election.\
7.9.5 **Moderator duties.** Moderators must enforce neutrality, interrupt prohibited content, invoke stop-the-line when needed, and route incidents to Stewardship with recorded reason codes.\
7.9.6 **Market sensitivity screening.** Sessions addressing market-moving topics require market sensitivity screening and may require controlled lanes, embargo, staged release, or safety veto.\
7.9.7 **Speaker content review.** Speakers must comply with non-solicitation and non-pitch rules; content must avoid product promotion and avoid creating implied endorsements.\
7.9.8 **Sponsor visibility boundaries.** Sponsors may be acknowledged within defined disclosure bounds but cannot influence agenda or outcomes; sponsor disclosures must be public-safe and recorded.\
7.9.9 **Post-session compliance attestations.** Where designated, moderators and recorders complete compliance attestations confirming safe-meeting rules were followed and noting any incidents.\
7.9.10 **Sanctions for violations.** Violations trigger reason-coded enforcement actions, from warnings to removal, including public-safe clarifications if reputational harm or misrepresentation risk exists.

***

#### 7.10 Safety, Dual-Use Screening, and Measurement Harm Controls

7.10.1 **Dual-use taxonomy for convenings.** Convening content is screened for weaponization potential, targeting cues, exploit enablement, panic amplification, manipulation affordances, and rights harms.\
7.10.2 **Targeting-cue prevention.** Critical infrastructure sessions must default to abstraction-first materials; facility identifiers and operational vulnerability details are restricted or withheld unless lawful and necessary.\
7.10.3 **Cyber exploit constraints.** No exploit-development instructions, weaponizable proof-of-concepts, or step-by-step harm content; responsible disclosure routing is permitted without operational direction.\
7.10.4 **Panic and rumor safeguards.** Convenings must avoid speculative amplification, employ uncertainty disclosures, and produce safe summaries designed for misquote resilience.\
7.10.5 **High-risk gating.** High-risk sessions require Stewardship safety gates, possibly including independent safety reviewers, tightened handling, and restricted participant eligibility.\
7.10.6 **Redaction/abstraction requirements.** Where risk exists, materials must be redacted/abstracted and released in staged form; controlled appendices may exist with strict access logging.\
7.10.7 **Incident Mode convenings.** Incident Mode elevates handling, narrows participation, mandates expiry, and requires after-action artifacts; it does not permit operational command.\
7.10.8 **Safety veto routing.** Safety vetoes must include reason codes, expiry, reopen conditions, and an appeal lane; silent indefinite holds are prohibited.\
7.10.9 **After-action safety learning.** Safety learning outputs are public-safe by default, explicitly stating what was withheld and why, with correction readiness and limits.\
7.10.10 **Participant safety.** Participant safety includes doxxing prevention, harassment controls, protected reporting, and identity minimization; violations trigger immediate intervention.

***

#### 7.11 Post-Convening Publication Discipline and Corrections

7.11.1 **Release record requirements.** Releases must record what was released, to whom, under what handling, with reliance bounds, expiry, and correction path.\
7.11.2 **Public-safe summaries default.** Public-safe summaries are the default output; controlled annexes are minimized and exist only when necessary and lawful.\
7.11.3 **Corrections and misquote response.** Misquote response and correction clocks apply to all convening outputs, including recordings where elected; corrections must be redistributed to all recipients where feasible.\
7.11.4 **Supersession discipline.** No silent edits; supersession requires diffs, effective dates, and status updates on trust surfaces and registry entries.\
7.11.5 **Withdrawal and takedown.** Withdrawal may occur for misrepresentation, safety risk, error discovery, or breach; withdrawal must be recorded with public-safe notice and minimization.\
7.11.6 **Nexus Journals routing.** Convening outputs destined for Nexus Journals undergo peer review and safety screening, and are published with versioning and correction mechanisms.\
7.11.7 **Nexus Registry entries.** Badges, releases, sanctions, and correction logs are recorded in the Registry as system-of-record; registry status is the authoritative truth.\
7.11.8 **Redistribution reconciliation.** Where controlled outputs were distributed, redistribution reconciliation ensures correction notices reach recipients and expiry/withdrawal status is enforced.\
7.11.9 **Translation/localization controls.** Translation must preserve meaning and handling constraints; corrections must propagate across language versions with parity and record linkage.\
7.11.10 **Archival and retention.** Retention rules follow handling class; access logs apply for controlled/restricted archives; de-identification and minimization are applied where feasible.

***

#### 7.12 Jurisdictional Convenings, Chapters, and Activation Gates

7.12.1 **In-jurisdiction convening definition.** A convening constitutes local presence when it is branded as local, conducted as a chapter/node, run as a State Council/NWG program, or executed through Host programs in-jurisdiction.\
7.12.2 **Activation gate.** In-jurisdiction convenings require activation: State Council constituted by record plus mandate evidence from competent authorities; absent activation, convenings remain global-only and must not imply local authority.\
7.12.3 **Host Institution convenings.** Host Institution convenings are sovereign-compatible, require lawful basis, and must avoid implied authority; GCRI supports methods and evidence only.\
7.12.4 **National Working Group sessions.** NWG sessions are time-boxed programs with explicit scope limits, handling rules, and dissolution/renewal rules by record.\
7.12.5 **CERT-related convenings.** CERT convenings are measurement support and learning only; no operational coordination is permitted, and handling elevation may be required.\
7.12.6 **Local law conflicts and abstention.** When local law conflicts with platform rules, abstention and escalation are recorded; safety and lawful compliance govern.\
7.12.7 **Public listings for local convenings.** Public listings must disclose activation status, scope, limitations, and expiry; mislabeling triggers misrepresentation enforcement.\
7.12.8 **Local identity and attribution constraints.** Public official participation must respect mandate safety and ethics; attribution is permissioned, scoped, and expiry-bound.\
7.12.9 **Cross-border participant restrictions.** Cross-border participation must comply with sanctions/export controls and handling; restricted jurisdictions may require exclusions or restricted lanes.\
7.12.10 **De-activation and pause.** Mandate withdrawal or expiry triggers pause and reversion to global-only posture; de-activation is recorded with public-safe notices.

***

#### 7.13 Operational Resilience of Convenings (Continuity, Security, and Integrity)

7.13.1 **Continuity plans.** Convenings must have continuity posture for platform outages, including alternate channels for continuity with later record reconciliation, without weakening handling or identity minimization.\
7.13.2 **Secure change management.** Templates, schemas, and convening system changes require controlled change management with versioning, approval records, and rollback capability.\
7.13.3 **Access control baselines.** MFA, least privilege, time-boxed access, and role-marker enforcement apply to convening tooling; privileged roles require stronger controls.\
7.13.4 **Leak incident response.** Leak incidents trigger triage, containment, distribution log analysis, sanctions routing, and correction/withdrawal actions where appropriate.\
7.13.5 **Watermark drills and control testing.** Watermark drills and distribution log audits are conducted on a control testing calendar linked to governance assurance posture.\
7.13.6 **Data protection during convenings.** No PII by default; any necessary sensitive data is minimized and handled in controlled lanes with access logs and retention constraints.\
7.13.7 **Supply-chain hygiene.** Virtual tools are reviewed for security posture where feasible; dependencies and risks are tracked consistent with handling and integrity requirements.\
7.13.8 **Physical security for in-person sessions.** Location minimization, controlled check-ins, identity minimization, and prohibition of casual photography apply; physical materials follow handling rules.\
7.13.9 **Record completeness audits.** Completeness audits ensure dockets, decision records, COI logs, distribution logs, and correction clocks exist and are internally consistent.\
7.13.10 **Post-event integrity review triggers.** High sensitivity sessions, repeated incidents, or neutrality breaches trigger independent integrity review and may lead to procedural hardening.

***

#### 7.14 Convening Templates and Required Inlined Forms

7.14.1 **Convening notice template.** Calendar-safe notice including handling election, room class, reliance bounds summary, recording defaults, and opt-in participation posture.\
7.14.2 **Safe-meeting script template.** Standard opening statement, prohibited topics list, interrupt protocol, escalation route, and closing compliance reminder.\
7.14.3 **Session docket template.** Scope, objectives, deliverables, timebox, authority limits, role assignments, and eligibility gates.\
7.14.4 **Briefing note template.** Facts/claims separation, limitations, uncertainty, intended/non-intended use, expiry, correction path, and handling inheritance.\
7.14.5 **Decision record + action register templates.** Reason-coded decisions, owners, due dates, timeboxes, dependencies, and closure verification fields.\
7.14.6 **COI disclosure + recusal form.** Session-scoped disclosures, recusal triggers, substitutions, and record entry fields.\
7.14.7 **Attribution request + consent form.** Named attribution consent with scope, expiry, revocation path, and misquote response routing.\
7.14.8 **Recording/photography consent form.** Consent options by room class, distribution constraints, watermarking rules, and retention schedule.\
7.14.9 **Distribution log schema.** Mandatory schema for controlled/restricted outputs including recipient mechanism, expiry, revocation, and redistribution reconciliation fields.\
7.14.10 **Post-session correction / misquote report form.** Structured intake for correction requests, evidence, urgency, handling election, and escalation to Stewardship where required.


---

# 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/vii.-operating-system.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.