# VI. Services

### Part 6 — Add-On Services Catalog

#### 6.1 Add-Ons Doctrine and Perimeter Compatibility

6.1.1 **Add-ons are services, not authority.** Add-ons are cost-recovery services that expand capability for verification, replication, publication safety, and learning. They do not confer authority, endorsement, regulatory standing, or operational mandate, and they must never be marketed as such.\
6.1.2 **Strict non-executing boundary.** Add-ons must remain inside GCRI’s non-executing perimeter: no operational command, dispatch, enforcement, procurement steering, underwriting, placement, custody, settlement, or deal-room activity.\
6.1.3 **Reliance bounds are mandatory.** Every add-on output must include reliance bounds (intended use, limitations, uncertainty, expiry, correction path) and must state what it is not (not an audit opinion, not compliance certification, not operational instruction).\
6.1.4 **Handling-first delivery.** Add-on outputs inherit a handling class and must comply with handling rules, including minimization, controlled dissemination, distribution logs, watermarking where applicable, and “no-forward” posture when designated.\
6.1.5 **Platform-record primacy.** Add-on requests, scopes, acceptance decisions, deliverables, and corrections are valid only when recorded on the platform with a record-valid work order and deliverable record. Off-platform statements are non-authoritative.\
6.1.6 **Independence and neutrality for paid services.** Paid services cannot buy influence, reviewer priority, release authority, or badge issuance. Reviewers and safety gates remain rotated, competence-gated, and independent of billing decisions.\
6.1.7 **No exclusivity / no privileged intelligence sale.** GCRI does not sell privileged intelligence, competitive advantage access, or exclusive “first look” rights that would undermine neutrality, safety, or public-interest integrity.\
6.1.8 **Liability posture and “as-is” terms.** Add-ons are delivered “as-is,” with bounded reliance, no warranties of fitness for a particular purpose, and no assumption of user responsibility. Users remain responsible for decisions and actions under their own lawful authorities.\
6.1.9 **Eligibility gates.** Add-ons may require eligibility gates including PoC thresholds, lawful participation constraints, COI screening, and safety review. Where gates are not met, service may be denied or downgraded to a safer lane.\
6.1.10 **Service suspension rights.** GCRI may suspend or pause add-on delivery due to safety holds, incident mode, integrity concerns, capacity constraints, or lawful restrictions, with reason-coded record entries and resumption criteria where feasible.

***

#### 6.2 Verification Services (Evidence Integrity; Not Regulatory Assurance)

6.2.1 **Provenance verification.** Verification may assess source traceability, lineage completeness, chain-of-custody equivalents, and tamper-evidence for artifacts, subject to available evidence and handling constraints.\
6.2.2 **Replayability / reproducibility validation.** Verification may include executing replication runs, checking method replay packs, validating environment manifests, and confirming that claims can be reproduced within stated bounds.\
6.2.3 **Data quality and documentation checks.** Verification may review dataset cards, schema conformance, missingness and bias disclosures, data quality ladders, and documentation hygiene, without implying compliance certification.\
6.2.4 **Model evaluation verification.** Where applicable, verification may check whether evaluation protocols were followed, whether reported metrics map to the stated protocol, and whether red-team formats and reporting are consistent with minimum evidence standards.\
6.2.5 **Proof Pack / AEP admissibility checks.** Verification may assess completeness of a Proof Pack, presence of limitation statements, reliance bounds, expiry, correction pathways, and minimum admissibility fields required for contestability.\
6.2.6 **Integrity of claims checks.** Verification may evaluate claim-to-evidence mapping, uncertainty disclosure, assumption clarity, and separation of observation vs inference, and may require revisions for ambiguous or overstated claims.\
6.2.7 **Controlled verification lanes.** Where restricted datasets or sensitive environments are involved, verification occurs in controlled or restricted lanes with secure sandbox requirements, distribution logging, and minimization of sensitive details.\
6.2.8 **Verification reports.** Verification reports must include: scope, method, evidence reviewed, limitations, uncertainty, reliance bounds, expiry, and correction clock. Reports must avoid language implying audit opinion, certification, or regulatory acceptance.\
6.2.9 **Verification dispute lane.** Verification outcomes are contestable via a defined dispute lane with reviewer rotation, dissent preservation, and supersession discipline; disputes must not be resolved informally off-record.\
6.2.10 **Prohibited representations.** Verification outputs must not be labeled “audit opinion,” “certified,” “compliant,” “regulator accepted,” or any equivalent phrasing that implies regulated assurance or compliance determination.

***

#### 6.3 Quality Markings and Badges (Scoped, Expiry-Bound, Revocable)

6.3.1 **Badge taxonomy by record.** Badge types, definitions, thresholds, and scope limits are defined and maintained by record-valid taxonomy; badge names must be standardized to prevent marketing drift.\
6.3.2 **“Guild-Reviewed” marking.** “Guild-Reviewed” indicates that the artifact passed a defined review threshold with documented reviewer rotation, COI controls, dissent handling, and minimum evidence hygiene. It is not an endorsement or compliance claim.\
6.3.3 **“Lab-Validated” marking.** “Lab-Validated” indicates replication evidence exists and meets specified criteria, including environment disclosure and reproducibility notes, subject to limitations and data access constraints.\
6.3.4 **“Dataset-Ready” / “Benchmark-Ready” markings.** These markings indicate documentation and readiness minima were met (dataset cards, schema, quality fields, intended use, known limits), without asserting suitability for any particular deployment decision.\
6.3.5 **“Release-Ready” marking.** “Release-Ready” indicates that required safety screening and handling election were completed, reliance bounds were present, and correction pathways and expiry were defined; it does not guarantee correctness.\
6.3.6 **“Operator-Safe Pattern” marking.** This indicates the artifact follows abstraction-first and anti-targeting-cue controls and is structured for safe reuse without exposing facility targeting cues, exploit instructions, or market-manipulation affordances.\
6.3.7 **Issuance workflow.** Badges are issued only through a record-valid workflow: submission → review → safety screening → issuance record (including scope and expiry) → trust-surface update.\
6.3.8 **Expiry, renewal, deprecation.** Badges expire automatically and must be renewed with fresh evidence; deprecations are recorded with migration notes and supersession references.\
6.3.9 **Revocation and public clarification.** Badges may be revoked for misuse, error, safety risk, or integrity breach; revocation triggers public-safe clarification and trust-surface updates to prevent downstream misrepresentation.\
6.3.10 **Badge misuse enforcement.** Misuse of badges (false claims, scope inflation, altered marks) is treated as misrepresentation and triggers the enforcement ladder with takedown, restrictions, and sanctions recorded.

***

#### 6.4 Training, Academy Access, and Clinics (Non-Licensure)

6.4.1 **Training doctrine.** Training builds competence for evidence-grade work and safe participation; it does not create licensure, compliance certification, or regulatory standing.\
6.4.2 **Open baseline vs paid clinics.** Core educational content remains open by default. Paid clinics may offer structured instruction, additional capacity, secure environments, and mentorship, without changing governance eligibility or competence gates.\
6.4.3 **Clinic formats.** Permissible formats include replication clinics, method sprints, evidence rooms, office hours, documentation bootcamps, and safety review workshops, each with handling elections and output recording rules.\
6.4.4 **Course integrity rules.** Courses must prohibit stealth advertising, procurement steering, and sponsor influence on content conclusions; sponsor disclosures are required where applicable, and neutrality posture is enforced.\
6.4.5 **Instructor eligibility.** Instructors must meet PoC minima, handling training requirements, and COI disclosures; instructors may be recused from reviewing artifacts where conflicts exist.\
6.4.6 **Safeguarding and accessibility.** Clinics must provide reasonable accommodations, apply anti-harassment safeguards, and support multilingual participation where feasible, consistent with handling constraints.\
6.4.7 **CE-style renewals.** Where continuing education renewals exist, renewal criteria must be competence-based, time-boxed, and revocable, with recorded renewal decisions and appeal lanes.\
6.4.8 **Training artifact outputs.** Training outputs (notes, method cards, lab logs) must elect handling classes, include limitations, and be recorded; no training output is permitted to become an implied directive.\
6.4.9 **Training disputes.** Assessment disputes (where applicable) follow a recorded dispute lane with minimization, reason-coded outcomes, and clear boundaries on what is appealable.\
6.4.10 **Prohibited claims.** Training materials must not claim “licensed,” “approved,” “regulator accepted,” or imply compliance certification.

***

#### 6.5 Competency Credentials (PoC-Linked; Revocable; Non-Regulatory)

6.5.1 **Credential taxonomy.** Credentials are defined by role/skill taxonomy with explicit scope, level, limitations, and non-regulatory nature; taxonomy changes require record-valid updates and supersession notices.\
6.5.2 **Evidence requirements.** Credentials require evidence: PoC tasks, reproducible work logs, handling compliance, reviewer sign-off under rotation rules, and, where relevant, safety screen completion.\
6.5.3 **Issuance mechanics.** Credential issuance is record-valid and includes expiry, renewal triggers, reason codes, and references to supporting evidence; credentials auto-expire unless renewed.\
6.5.4 **Portability bounds.** Credential portability is bounded by handling class and lawful constraints; credentials do not transfer authority across jurisdictions or imply operational competence beyond scope.\
6.5.5 **Revocation and appeal trails.** Revocation requires recorded evidence and reason codes, provides an appeal lane, and results in trust-surface updates to prevent continued reliance on invalid standing.\
6.5.6 **Display rules.** Credential display must include non-endorsement and scope limits; role markers may be displayed without revealing identity; identity is never implied by a credential unless explicitly consented and recorded.\
6.5.7 **Fraud response.** Credential fraud, forgery, or scope inflation triggers takedown, sanctions, and public-safe clarifications.\
6.5.8 **Registry integration.** Credentials appear on trust surfaces with expiry status visible; supersession and corrections are prominently surfaced.\
6.5.9 **Anti-gaming controls.** Controls include sybil resistance, reviewer rotation, audit sampling, clawbacks of credits, and disqualification from reviewer pools for manipulation attempts.\
6.5.10 **Prohibited language.** Credentials must not be framed as “certified practitioner” in a way that implies licensure, regulated status, or compliance certification.

***

#### 6.6 Tooling / Compute Add-Ons (Governance-Safe Infrastructure)

6.6.1 **Secure sandbox access.** Secure sandboxes may include isolated environments, TEEs where appropriate, controlled workspaces, and audit logging; access is PoC-gated and time-boxed.\
6.6.2 **Replication environments.** Replication environments provide standardized stacks, environment manifests, dependency disclosure, and integrity posture (including SBOM expectations), without implying security certification.\
6.6.3 **Benchmark harnesses and suites.** Benchmark tooling includes rate limits, fairness controls, integrity gates, and standardized reporting fields to reduce gaming and increase comparability.\
6.6.4 **Data room tooling.** Where lawful, data room tooling supports tiered access, expiry, distribution logs, watermarking, and compute-to-data constraints to prevent bulk extraction.\
6.6.5 **Compute credits / NUCs management.** Allocation rules must be transparent and abuse-resistant; credits are non-financial, non-transferable by default, revocable for misuse, and tracked by record.\
6.6.6 **API / connector access.** Interoperability APIs and connectors may be offered for evidence workflows and schema alignment; they must not be used for execution routing or regulated activity enablement.\
6.6.7 **Logging and auditability.** Tooling logs must be defined (what is logged, retention, privacy minimization) and applied consistently; sensitive logs are controlled and access-logged.\
6.6.8 **Security controls.** Security controls include MFA, least privilege, anomaly detection, incident response workflows, and access revocation mechanics; security incidents trigger safety holds as needed.\
6.6.9 **Tooling disputes and incident holds.** Tooling disputes follow a recorded lane; incident holds may suspend access pending investigation, with reason-coded records and resumption criteria.\
6.6.10 **Prohibited uses.** Prohibited uses include generating targeting cues, exploit development, unlawful surveillance, harassment, disinformation operations, or any activity breaching the non-executing perimeter.

***

#### 6.7 Publication Support Services (Packaging, Safety Review, Translation Integrity)

6.7.1 **Method packaging support.** Packaging includes method cards, assumptions, limitations, reproducibility steps, uncertainty disclosures, and standardized metadata to support replayability and contestability.\
6.7.2 **Safety screening service.** Safety screening evaluates dual-use risks, targeting cues, market sensitivity, and panic amplification; it may recommend abstraction, redaction, staged release, or restricted appendices.\
6.7.3 **Documentation hygiene.** Support may include lineage notes, citations discipline, versioning, correction templates, and clear separation of observation vs inference.\
6.7.4 **Translation integrity.** Translation support includes version control, meaning-preservation checks, misquote risk controls, and alignment of translated content with handling and reliance bounds.\
6.7.5 **Editorial review.** Editorial review focuses on clarity, structure, defensibility under scrutiny, and mandatory disclaimers; it must not manufacture endorsements or implied approvals.\
6.7.6 **Pre-publication checklists.** Services may include checklists for handling election, distribution planning, correction clock readiness, dissent capture, and reliance bounds completeness.\
6.7.7 **Post-publication corrections.** Support for errata and supersession records ensures “no silent edits,” provides diffs, and updates trust surfaces with correction status.\
6.7.8 **Controlled appendix preparation.** Controlled appendices are minimized, access-logged, watermarked where required, and accompanied by public-safe summaries and reliance bounds.\
6.7.9 **Publication disputes.** Disputes route through contestation lanes with reviewer rotation, dissent preservation, and recorded decisions; informal resolution without record is invalid.\
6.7.10 **Prohibited publication services.** Prohibited services include ghostwriting endorsements, drafting lobbying content, political messaging, or content designed to induce procurement outcomes.

***

#### 6.8 Convening Services (Clinics, Sprints, Demo Days; No Deal Room)

6.8.1 **Convening as evidence instrument.** Convenings are treated as evidence instruments: outputs must be record-valid, scoped, and paired with reliance bounds and correction pathways.\
6.8.2 **Safe-meeting scripts.** Convenings enforce competition hygiene and procurement neutrality using safe-meeting scripts and prohibited-topic boundaries; deviations require incident recording.\
6.8.3 **Program committee support.** Program committee support includes selection integrity, reviewer rotation, COI controls, and safety screening criteria, without sponsor influence over outcomes.\
6.8.4 **Presenter readiness checks.** Presenters must meet PoC/handling requirements and provide COI disclosures; attribution is permissioned, scoped, and expiry-bound.\
6.8.5 **Session artifact requirements.** Each session must have a briefing note, Proof Pack pointer where applicable, limitations, reliance bounds, dissent handling, and correction clock election.\
6.8.6 **Recording/photography controls.** Recording rules follow handling classes, consent requirements, watermarking where required, and attendee identity minimization.\
6.8.7 **Distribution controls.** Default outputs are public-safe summaries with controlled appendices where needed; distribution logs apply to controlled/restricted artifacts.\
6.8.8 **Post-event corrections.** Misquote response, errata windows, and supersession discipline apply to all published outputs, including slide decks and recordings.\
6.8.9 **Incident mode convenings.** In incident mode, handling elevates, access narrows, expiry is mandatory, and after-action records are required.\
6.8.10 **Prohibited convening uses.** Convenings cannot be used for procurement steering, capital raising, contract negotiation, exclusivity bargaining, or any deal-room behavior.

***

#### 6.9 Controlled Data Rooms and Restricted Collaboration (Where Lawful)

6.9.1 **Lawful basis and eligibility.** Controlled data rooms require lawful basis, sanctions/export control compliance, and eligibility screening; reasons for denial are recorded with minimization.\
6.9.2 **Access tiers and PoC.** Access is least-privilege, time-boxed, and PoC-gated; restricted lanes may require verified identity where lawful and necessary.\
6.9.3 **Distribution logs and watermarking.** Distribution logs and watermarking are mandatory; leak indicators trigger incident mode and access revocation.\
6.9.4 **Data minimization and de-identification.** No PII by default; de-identification and minimization are applied where possible; sensitive fields may be abstracted or withheld.\
6.9.5 **No facility targeting cues.** Default posture prohibits facility targeting cues; operator-safe abstractions are preferred, and sensitive operational details are restricted.\
6.9.6 **Compute-to-data posture.** Compute-to-data is preferred over extraction; audit trails record queries and outputs where feasible within privacy constraints.\
6.9.7 **Retention and destruction.** Retention is time-boxed; destruction/offboarding attestations may be required; controlled exports are limited and logged.\
6.9.8 **Incident escalation.** Security incidents, misuse, or suspected leaks trigger escalation pathways, lawful notifications where required, and public-safe clarification where appropriate.\
6.9.9 **Oversight and independent review.** High-sensitivity lanes trigger independent review and enhanced controls; approvals are recorded and auditable.\
6.9.10 **Prohibited data room content.** Prohibited content includes weaponizable exploit instructions, unlawful surveillance materials, or content whose dissemination would predictably enable harm.

***

#### 6.10 Incident Measurement Support (Evidence Capture; Not Operations)

6.10.1 **Evidence capture templates.** Incident support may provide templates for timelines, logs, impact statements, decision records, and uncertainty statements, designed for replayability and correctionability.\
6.10.2 **Replay packs for incidents.** Replay packs may capture reproducible steps and environment notes, with strict limits to avoid enabling harm and with reliance bounds clearly stated.\
6.10.3 **Responsible disclosure routing support.** Support may help route disclosure to appropriate responsible channels without implying enforcement authority, regulator posture, or operational command.\
6.10.4 **Public-safe communications drafts.** Public-safe drafts emphasize non-amplification, uncertainty disclosure, and correction readiness, and avoid tactical details.\
6.10.5 **After-action learning artifacts.** After-action artifacts capture what changed, what was withheld and why, what holds, and what corrected, with supersession and migration notes.\
6.10.6 **Liaison constraints.** Any liaison is informational only; GCRI does not direct response, allocate resources, issue directives, or claim incident command authority.\
6.10.7 **Handling escalation during incidents.** Handling may elevate to controlled/restricted; distribution logs and expiry are mandatory, and declassification is constrained.\
6.10.8 **Preservation and continuity.** Evidence preservation favors integrity and minimization, with access logs and chain-of-custody equivalents where relevant and lawful.\
6.10.9 **Dispute and contestation lanes.** Incident artifacts remain contestable; dissent and minority reports are preserved in safe form with recorded dispute outcomes.\
6.10.10 **Prohibited incident support.** Prohibited support includes operational directives, tactical response playbooks, exploitation guidance, or any content enabling harm or breaching the non-executing perimeter.

***

#### 6.11 Service Request Intake, Scoping, and Acceptance Gates

6.11.1 **Request submission fields.** Requests must specify scope, intended use, handling election, jurisdiction constraints, reliance audience, desired deliverables, and any sensitive context triggers.\
6.11.2 **COI and independence screening.** COI screening and independence checks apply to reviewers and service providers; recusals and rotation pools are enforced and recorded.\
6.11.3 **Safety screening.** Safety screening assesses dual-use risk, targeting cues, market sensitivity, panic amplification risk, and sensitive rights impacts; outcomes are reason-coded.\
6.11.4 **Lawful constraints screening.** Screening includes sanctions/export controls, local law, data rights, and disclosure constraints; denial must be reason-coded with minimization.\
6.11.5 **Acceptance/rejection reason coding.** Accept/reject decisions require recorded reason codes and, where safe, a public-safe summary of the decision basis.\
6.11.6 **Engagement record as a work order.** Accepted services require a record-valid work order with scope, deliverables, timeline assumptions, handling, and correction pathway defined.\
6.11.7 **Change control during delivery.** Scope changes require record-valid amendments with diffs; silent scope creep is invalid and triggers corrective actions.\
6.11.8 **Deliverable record requirements.** Deliverables must include limitations, uncertainty, reliance bounds, expiry, and correction clocks; controlled outputs require distribution logs.\
6.11.9 **Member responsibilities.** Members must confirm rights to provide inputs, accuracy of representations, and lawful basis for any sensitive data; misrepresentation triggers termination and sanctions.\
6.11.10 **Termination rights.** GCRI may terminate services for safety holds, breach, unlawful constraints, misrepresentation, or abuse, with record-valid termination notices and reason codes.

***

#### 6.12 Commercial Terms, Billing, and Financial Controls (Nonprofit-Compatible)

6.12.1 **Pricing posture.** Pricing uses published bands where feasible, sliding-scale options, and scholarship overlays; individualized quotes require recorded justification and COI screening.\
6.12.2 **Payment terms and invoicing.** Payment terms must comply with jurisdiction constraints and avoid inducement perceptions, especially for public-sector participants; invoicing is record-linked.\
6.12.3 **Refunds and credits.** Refunds and credits follow recorded policy; safety holds may pause delivery without liability beyond published policy; disputes route to due process lanes.\
6.12.4 **Segregation of duties.** Billing operations are separated from governance decisions, badge issuance, reviewer assignment, and safety gates to prevent pay-to-play risk.\
6.12.5 **Sponsor-funded add-ons firewall.** Sponsor funding may support capacity but cannot steer outcomes; sponsor influence is prohibited and monitored through influence indicators.\
6.12.6 **Tax/VAT/GST posture.** Where applicable, tax considerations are handled per jurisdiction; communications include disclaimers and avoid creating regulated interpretations.\
6.12.7 **Anti-fraud controls.** Anti-fraud controls verify payer legitimacy and detect abuse patterns; fraud triggers holds, review, and potential termination with recorded reason codes.\
6.12.8 **Recordkeeping and audit trail.** Service billing and delivery records must support audit readiness, including scope, deliverables, approvals, exceptions, and conflicts handling.\
6.12.9 **Billing dispute lane.** Billing disputes follow a recorded lane aligned to Part 22, with minimization and reason-coded outcomes.\
6.12.10 **Prohibited fee structures.** Success fees or compensation tied to procurement wins, financing outcomes, underwriting outcomes, or market impacts are prohibited.

***

#### 6.13 Prohibited Monetization and Forbidden Offers (Hard List)

6.13.1 **No sale of targeting cues or weaponizable intelligence.** GCRI must not sell targeting cues, facility identifiers, or operational vulnerability details that would enable harm.\
6.13.2 **No sale of competitive advantage access.** GCRI must not sell privileged access that confers competitive advantage or creates unequal intelligence distribution inconsistent with neutrality.\
6.13.3 **No exclusivity tied to governance.** Exclusive memberships, restricted clubs, or premium governance privileges are prohibited.\
6.13.4 **No “VIP influence” pricing.** Any pricing that purchases influence, stage access, reviewer priority, or release shortcuts is prohibited.\
6.13.5 **No paywalled harmful intelligence.** Content likely to amplify panic, enable manipulation, or create systematic harm cannot be monetized or paywalled.\
6.13.6 **No procurement steering bundles.** Bundling services with vendor endorsements, bid steering, or procurement influence is prohibited.\
6.13.7 **No financial product promotion or execution.** Any monetization implying underwriting, custody, settlement, or solicitation is prohibited.\
6.13.8 **No political services.** Campaigning, lobbying-for-hire, electioneering, or partisan messaging services are prohibited.\
6.13.9 **No deanonymization services.** Selling identity unmasking, doxxing, or identity mapping is prohibited.\
6.13.10 **No perimeter breaches.** Any offer that breaches the non-executing perimeter is prohibited regardless of demand or funding offered.

***

#### 6.14 Quality, Corrections, Disputes, and Enforcement for Add-On Outputs

6.14.1 **Minimum quality fields.** All service outputs must include: scope, method, evidence basis, limitations, uncertainty, reliance bounds, expiry, handling election, and correction pathway.\
6.14.2 **Correction clocks.** Corrections follow defined clocks with errata and supersession discipline; silent edits are prohibited, and diffs are preserved.\
6.14.3 **Contestation and disputes.** Service outputs are contestable through peer dispute lanes with reviewer rotation and dissent preservation; dispute outcomes are record-valid.\
6.14.4 **Misrepresentation response.** Misuse of service outputs in marketing or claims of “approval/certification” triggers takedown, clarification, and sanctions processes.\
6.14.5 **Sanctions ladder linkage.** Add-on misconduct routes into the sanctions ladder (warnings → restrictions → suspension → removal), with reason-coded records and appeal pathways.\
6.14.6 **Public clarification protocol.** If public claims were made based on add-on outputs, public-safe clarifications must be issued to prevent downstream reliance errors, without exposing sensitive details.\
6.14.7 **Retention and access logging.** Controlled service outputs require access logging, distribution logging, retention schedules, and offboarding attestations where applicable.\
6.14.8 **Appeals pathway.** Appeals for service disputes follow Part 22 linkage, bounded to process integrity and record completeness, not guaranteed outcomes.\
6.14.9 **Periodic audits of service integrity.** Trustees oversee periodic audits and control tests for add-on integrity, pay-to-play risks, reviewer independence, and safety gate performance.\
6.14.10 **Service sunset and supersession.** Add-on offerings may be deprecated or sunset only by record-valid act with migration notices, effective dates, and clarity on continuing obligations.


---

# 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/vi.-services.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.