# II. Governance

### Part 2 — Governance Wiring for Membership

#### 2.1 General Assembly Authority

2.1.1 **Legitimacy anchor; scope limits.** The General Assembly (GA) is the legitimacy anchor for the GCRI Guild Membership system. GA authority is confined to membership governance within the strict non-executing perimeter and shall not be interpreted to create operational, regulatory, enforcement, intelligence, procurement, or financial execution authority.\
2.1.2 **Reserved powers.** By Record-Valid act, the GA may: (i) adopt, amend, or repeal this Membership Constitution; (ii) ratify or remand safeguard-critical changes escalated by Trustees or the Stewardship Committee; (iii) approve baseline membership rights, conduct minima, due process minima, and safety safeguards; (iv) establish GA working rules for elections/ratifications; (v) receive transparency and integrity packs; and (vi) approve membership-critical minima for core Platform primitives where designated.\
2.1.3 **Safeguard-critical clause protection.** Clauses designated safeguard-critical (including perimeter prohibitions, jurisdiction activation gates, handling discipline, neutrality/competition controls, record-validity, and due process minima) are non-derogable absent heightened notice, heightened threshold, and explicit diff publication.\
2.1.4 **Voluntary participation baseline.** Participation in GA meetings, consultations, and ballots is voluntary. Abstention does not reduce baseline access rights except where a member seeks an opt-in role requiring affirmative acceptance or where legal requirements mandate a specific election.\
2.1.5 **Meeting safety, handling election, and metadata minimization.** GA proceedings follow handling-class discipline and metadata minimization: neutral event titles, minimized attendee identity exposure, minimized location disclosure where necessary, and controlled minutes when required by sensitivity.\
2.1.6 **Quorum and voting integrity.** Quorum and thresholds are set by Record-Valid rule, auditable, and proportionate to impact. Voting protocols include anti-sybil measures and capture-resistance controls, including identity-option handling, rate limits, eligibility gates, and anomaly detection.\
2.1.7 **Minority protections.** GA procedures preserve dissent, minority reports, and contestation rights. Material objections may be recorded and retained, with publication in public-safe form where permitted by handling and safety review.\
2.1.8 **Notice, change control, and publication of diffs.** Safeguard-critical changes require advance notice by Platform record, a minimum review window, an explicit summary of changes, a published diff or structured change map, an impact statement, and a contestation window; stealth amendments are prohibited.\
2.1.9 **GA conflict controls.** Voting rights and governance outcomes shall not be conditioned on payment tier, sponsorship, speaking visibility, or commercial benefit. Paid tiers may not purchase votes, veto overrides, seat allocation, or release authority.\
2.1.10 **Delegation limits for GA committees.** GA committees, where constituted, may act only within explicitly delegated scope, timebox, and non-executing limits recorded by act; committees may not create operational mandates or override Stewardship safety holds.\
2.1.11 **GA elections/ballots protocol.** Ballots specify eligibility, identity options consistent with identity minimization, COI/recusal rules, handling election, dispute lane, and effective date rules; all outcomes are Record-Valid only upon Platform record entry.\
2.1.12 **GA transparency pack and integrity pack.** The GA receives: (i) an annual public-safe transparency pack (membership health, outputs, corrections, sanctions summaries, neutrality indicators); and (ii) a controlled integrity pack (incident patterns, control testing results, audit findings, identity-cell statistics) minimized and access-logged.\
2.1.13 **Adjournment, emergency deferral, and resumption.** The GA may adjourn or defer proceedings where safety, security, or integrity risks arise, with recorded reasons, expiry, and a resumption plan; emergency deferral shall not be used for capture or to avoid contestation.\
2.1.14 **Record-validity and anchoring where designated.** GA acts are effective only when recorded as Record-Valid acts on the Platform; where designated by governing instruments, specific acts may require additional anchoring or dual-record steps consistent with the broader governance protocol.

***

#### 2.2 Board of Trustees Oversight

2.2.1 **Fiduciary guardianship and perimeter enforcement.** The Board of Trustees provides fiduciary oversight of the membership system and has an affirmative duty to enforce the strict non-executing perimeter and prevent the membership system from becoming de facto operational authority.\
2.2.2 **Membership system risk ownership.** Trustees own oversight for legal, operational, reputational, security, and safety risks arising from membership operations, including dual-use publication risk, misrepresentation risk, and capture risk.\
2.2.3 **Financial controls.** Trustees oversee membership subscriptions and permissible add-ons, scholarship/waiver governance, refund/credit posture, and segregation of funds consistent with nonprofit obligations and transparent accounting.\
2.2.4 **Nonprofit compatibility and private benefit constraints.** Trustees enforce anti-inurement and private benefit constraints: membership design shall not be used to confer improper private advantage, paid influence, procurement steering, or preferential market positioning.\
2.2.5 **Sponsor concentration governance.** Trustees set and monitor sponsor concentration caps, category disclosures, influence indicators, and independence attestations to prevent sponsor/bloc capture and reputational laundering.\
2.2.6 **Audit posture.** Trustees ensure appropriate audit posture including annual audits where applicable, special audits triggered by integrity events, and periodic control testing of governance-critical processes.\
2.2.7 **Technical resilience oversight.** Trustees ensure governance-critical services (Registry, record store, role markers, correction/supersession, distribution logs) meet resilience minima: access control, audit logging, backup/restore, secure change management, and incident response readiness.\
2.2.8 **Escalation and intervention powers.** Trustees may, by Record-Valid act: (i) pause or restrict specific membership lanes pending integrity review; (ii) direct the Stewardship Committee to conduct safety reviews or investigations; (iii) appoint temporary independent reviewers; (iv) suspend a convening or release window where credible harm risk exists.\
2.2.9 **Emergency governance approvals.** Trustees approve activation of Emergency Governance Mode where required by higher instruments, including explicit expiry, ratification requirements, rollback criteria, and after-action obligations.\
2.2.10 **Non-interference principle.** Trustees do not micromanage scientific conclusions or peer review outcomes; oversight is limited to perimeter integrity, safety gates, due process, neutrality, and audit posture.\
2.2.11 **Trustee COI, recusal, confidentiality, and handling.** Trustees maintain COI disclosures, recusal discipline, confidentiality duties, and handling obligations proportionate to access; breaches are enforceable and recorded.\
2.2.12 **Delegation by record only.** Trustee delegations are valid only by Record-Valid act specifying scope, timebox, PoC where applicable, handling permissions, audit obligations, and revocation conditions; no implied authority exists by title.\
2.2.13 **Trustee transparency minima.** Trustees publish public-safe summaries of material interventions and oversight outcomes, while minimizing controlled details and access-logging any sensitive annexes.\
2.2.14 **Removal/discipline interface.** Where permitted under higher-order instruments, Trustees maintain interfaces for removal/discipline actions related to membership governance roles, ensuring due process, recorded basis, and appeal pathways.

***

#### 2.3 Stewardship Committee (Cross-Guild Integrity Governor)

2.3.1 **Mandate.** The Stewardship Committee is the cross-Guild integrity and safety governor responsible for system invariants: handling discipline, publication safety, correction clocks, neutrality controls, due process minima, and integrity of membership primitives.\
2.3.2 **Scope limits.** The Committee does not direct operations, determine policy outcomes, task intelligence collection, influence procurement, promote financial products, or substitute for lawful authorities; it acts only to preserve safety, legality, perimeter integrity, and due process.\
2.3.3 **Handling classes governance.** The Committee defines handling classes, election rules, distribution constraints, watermarking defaults, “no-forward” rules, and declassification constraints, with non-regression guarantees and migration discipline.\
2.3.4 **Publication safety gate.** The Committee operates a dual-use and sensitivity screening gate, applying abstraction/redaction/staging and controlled dissemination when necessary to reduce targeting, exploit, market, panic, retaliation, or rights-impact risks.\
2.3.5 **Stop-the-line holds.** The Committee may impose temporary holds on releases, badges, or convenings when credible safety or integrity risk exists; holds must include reason codes, scope, expiry, reopen conditions, and an appeal lane.\
2.3.6 **Correction clocks.** The Committee sets and enforces correction, supersession, and deprecation discipline; silent edits are prohibited for record-valid releases; correction performance is measured and reported.\
2.3.7 **Misrepresentation controls.** The Committee administers takedowns, clarifications, and restrictions for role-marker abuse, false “node” claims, false endorsements, and brand laundering, with recorded basis and due process.\
2.3.8 **Sanctions ladder administration.** The Committee administers sanctions outcomes (warning → restriction → suspension → removal) consistent with due process minima and recorded evidence basis.\
2.3.9 **CRS/iVRS/ILA/PoC integrity baseline.** The Committee maintains anti-gaming controls, clawbacks, reviewer rotation, sybil resistance measures, anomaly detection, and separation-of-duties rules for governance-critical primitives.\
2.3.10 **Governance schema change gate.** Membership-critical schema changes (roles, sanctions, records, appeals, credits, identity options) require a gated change process: diff publication, migration plan, notice window, contestation window, and rollback criteria.\
2.3.11 **Incident lanes and triage clocks.** The Committee maintains incident lanes for safety, integrity, security, and conduct, with triage clocks, containment protocols, escalation logic, and after-action record requirements.\
2.3.12 **Identity minimization cell oversight.** The Committee governs the identity minimization cell: two-person rule, unmasking criteria, access logging, segregation of identity mapping, and breach response, minimizing identity exposure by default.\
2.3.13 **Neutrality enforcement.** The Committee enforces political safety, procurement neutrality, and competition hygiene, including prohibited-topic controls and safe-meeting scripts for councils, Labs, and convenings.\
2.3.14 **Committee composition safeguards.** Composition must be balanced across the quintuple helix and include independent integrity expertise; terms, recusals, and rotation protect against capture.\
2.3.15 **Rotation, term limits, recusals, influence caps.** The Committee maintains term limits, recusal rules, cooling-off where needed, and influence caps to prevent concentration and self-review.\
2.3.16 **Reporting outputs.** The Committee issues public-safe summaries of material integrity actions and maintains controlled records minimized and access-logged, supporting audit readiness and trust under scrutiny.

***

#### 2.4 Domain Councils (Quintuple-Helix Governance Councils)

2.4.1 **Purpose and scope.** Domain Councils provide the governance interface for membership within their domain lanes: role ladders, review lanes, release gates, and commissioning of CCells/CERTs within global invariants.\
2.4.2 **Primary governance council assignment per Lab.** Each Future Innovation Lab is assigned exactly one Primary Council as its governance interface; this prevents fragmented authority and shadow governance.\
2.4.3 **Permitted actions.** Domain Councils may, by record: set roadmaps/backlogs; commission, renew, or dissolve CCells; approve or deny release submissions subject to Stewardship safety gates; set reviewer rotations; and define domain quality thresholds for readiness states.\
2.4.4 **Reviewer rotation pools and separation-of-duties.** Councils maintain rotation logic to prevent repeated concentration; authors, reviewers, stewards, and safety gate roles are separated; recusals are mandatory where COI exists.\
2.4.5 **Domain-specific PoC tasks.** Councils define domain PoC tasks and competence evidence requirements within global PoC invariants, ensuring testable capability and safe handling competence.\
2.4.6 **Domain quality thresholds.** Councils define thresholds and checklists for “ready-for-review,” “release-candidate,” “released,” “deprecated,” and “superseded” states consistent with correctionability and reliance bounds.\
2.4.7 **Limits.** Councils may not override Stewardship safety holds, weaken handling or neutrality rules, create local operating presence absent activation, bind GCRI externally, or imply endorsement/certification.\
2.4.8 **Cross-domain coupling rules.** Councils must trigger cross-council review where dual-use, infrastructure sensitivity, market sensitivity, rights impacts, or unresolved disputes are plausible; co-review patterns are used when required.\
2.4.9 **Workload controls and voluntary service.** Council participation is opt-in and time-boxed; workload expectations, surge windows, and deliverables are recorded; members may opt out without penalty except for survival obligations tied to controlled access.\
2.4.10 **Minutes discipline.** Council convenings follow safe-meeting scripts and minutes minimization; controlled minutes are used when sensitivity requires; identity exposure is minimized.\
2.4.11 **Escalation pathways.** Councils escalate safety/integrity issues to Stewardship; fiduciary or systemic risk issues to Trustees; and designated membership-constitutional matters to GA lanes.

***

#### 2.5 Guild Autonomy Boundaries (Non-Derogable Invariants)

2.5.1 **Autonomy within invariants.** Labs and Guild work units may define internal workflows and norms only where they strengthen, and never weaken, safeguard-critical invariants.\
2.5.2 **Non-derogable safeguard list.** Non-derogable safeguards include: strict non-executing perimeter; jurisdiction activation gate; handling discipline; neutrality/competition/procurement controls; validity-by-record; correction discipline; protected participation; and due process minima.\
2.5.3 **Open-to-all baseline.** Participation is open-to-all by default; restrictions are permitted only for handling class, lawful constraints, PoC thresholds for controlled lanes, or safety—never for affiliation, ideology, or commercial advantage.\
2.5.4 **No quasi-regulatory structures.** Labs may not create licensure schemes, “approved provider” regimes, compliance programs, or structures that mimic regulatory authority.\
2.5.5 **No procurement or deal-room behavior.** Labs may not use workflows to steer procurement, recommend vendors, coordinate bids, negotiate contracts, or facilitate capital raising; such conduct triggers restriction and sanctions lanes.\
2.5.6 **IP, provenance, and publication hygiene.** Labs must enforce inbound license grant, provenance requirements, and no contamination from restricted to open artifacts; release packaging must include limitations and reliance bounds.\
2.5.7 **Local representation restrictions.** Members may not represent local “nodes/offices/chapters” absent activation; branding and public claims must reflect activation status and scope.\
2.5.8 **Charter compatibility and conflict rule.** Lab-level rules must remain compatible with this Constitution and higher safeguards; in conflict, safeguards prevail and the stricter rule governs.

***

#### 2.6 Competence Cells (CCells) — Time-Boxed Work Units

2.6.1 **Definition and permitted purposes.** A CCell is an opt-in, time-boxed work unit constituted by record to produce defined artifacts, benchmarks, verification outcomes, replication results, or structured learning outputs within a Primary Lab and under its Primary Council.\
2.6.2 **Formation by record; mandatory fields.** Formation records must specify: scope, objectives, deliverables, timebox/expiry, handling election, distribution constraints, named steward, role PoC minima, review plan, COI disclosures, and dissolution triggers.\
2.6.3 **Data governance posture.** CCells must document data sources, data minimization posture, lawful basis where applicable, and “no PII by default”; sensitive data requires handling elevation and controlled access rules.\
2.6.4 **Access control and audit logging.** Controlled and restricted lanes require Platform access controls, audit logs, distribution logs, and secure workspaces/sandboxes where designated.\
2.6.5 **Separation of duties and COI/recusal.** CCells must define separation of duties and COI/recusal plans, including reviewer substitution and rotation; self-review is restricted and recorded.\
2.6.6 **Deliverable integrity requirements.** Outputs must include limitations, uncertainty disclosure, reliance bounds, expiry/review date, correction pathway, and reproducibility evidence proportionate to handling.\
2.6.7 **Dissolution-by-default and archival/publication plan.** CCells dissolve at expiry unless renewed by record; dissolution includes archival rules, what is published public-safe vs retained controlled, and correction responsibilities.\
2.6.8 **Participation and exit rules.** Participation is voluntary; exit is permitted at any time subject to handling survival obligations (no unauthorized disclosure, return/destruction where required, offboarding attestation where applicable).\
2.6.9 **No shadow governance.** CCells may not create independent decision bodies bypassing councils or Stewardship; escalations route through Platform governance lanes.

***

#### 2.7 CERTs (Community Emergency Response Teams) — Evidence Support Only

2.7.1 **Definition and permitted scope.** A CERT is an opt-in, record-valid, time-boxed formation of multiple CCells for evidence capture, measurement support, verification assistance, and structured public learning—never emergency command, dispatch, enforcement, procurement, or intelligence tasking.\
2.7.2 **Formation triggers and authorization by record.** CERTs require recorded triggers and authorization, naming participating CCells, stewards, scope, objectives, handling election, and expiry; activation-gated rules apply for local mobilizations.\
2.7.3 **Handling election, distribution logs, watermarking, expiry.** CERT outputs inherit the CERT handling class; controlled/restricted outputs require distribution logs and watermarking; expiry and dissolution are mandatory.\
2.7.4 **Liaison points and disclosure routing.** Liaison points (if any) and disclosure routing constraints are recorded; CERTs may support responsible disclosure pathways without enforcement posture.\
2.7.5 **Prohibited activities.** CERTs may not simulate command structures, issue directives, coordinate responders, steer procurement, publish targeting cues, or share exploit details; breaches trigger immediate containment.\
2.7.6 **After-action record requirement.** Every CERT must file an after-action record including: what was measured, what was inferred, what was withheld for safety, what was corrected, and what was superseded, with a public-safe summary where possible.\
2.7.7 **Handling inheritance and declassification constraints.** CERT artifacts inherit handling; declassification requires recorded basis and safety review; public releases default to safe summaries.\
2.7.8 **Relationship to activation gate.** No in-jurisdiction CERT mobilization or branded local activity occurs absent activation and mandate support evidence; absent activation, only global method work and public-safe learning outputs are permitted.

***

#### 2.8 Delegation Limits and Role-Marker Authority

2.8.1 **No implied authority.** Titles, reputation, affiliation, payment tier, meeting presence, or media visibility confer no authority; internal authority exists only via role markers recorded on the Platform.\
2.8.2 **Delegation by record only.** Delegations must specify scope, expiry, PoC requirements, handling permissions, audit duties, revocation conditions, and separation-of-duties constraints; delegations are non-transferable.\
2.8.3 **Non-delegable constraints.** No one may delegate or assume authority for: operational command, enforcement, intelligence tasking, procurement authority, regulatory approvals, or binding GCRI externally.\
2.8.4 **Cooling-off, rotation, separation-of-duties.** Reviewer/maintainer/steward delegations require COI screening, recusals, rotation schedules, and cooling-off periods where needed to prevent capture and self-review.\
2.8.5 **Revocation-by-record and emergency revocation.** Role markers and access privileges are revocable by record; emergency revocation may occur for imminent harm risk with recorded basis, expiry, and post-hoc review.\
2.8.6 **Role survival obligations.** Handling survival obligations, confidentiality, record integrity duties, and controlled-material return/destruction duties survive role expiry or resignation.

***

#### 2.9 Cross-Council Review, Contestation, and Safety Veto

2.9.1 **Contestation as design feature.** Contestation is structural and protected; it is a safety feature enabling correction and reducing capture risk.\
2.9.2 **Mandatory triggers.** Cross-council review is required where dual-use risk, infrastructure sensitivity, market sensitivity, rights impacts, activation ambiguity, or unresolved evidence quality disputes are plausible.\
2.9.3 **Review lanes and triage clocks.** Review lanes include standard, accelerated, and emergency lanes, each with triage clocks and recorded outcomes; prolonged silence is prohibited by reopen/expiry rules.\
2.9.4 **Minority reports and dissent preservation.** Dissent and minority reports are recorded and retained; publication in public-safe form occurs where permitted by handling and safety review.\
2.9.5 **Reviewer rotation and auditability.** Reviewer privileges rotate; concentration triggers neutrality review; review outcomes are audit-traceable by role marker and record basis.\
2.9.6 **Safety veto routing.** Safety vetoes route to Stewardship, must include reason codes, scope, expiry, reopen conditions, and an appeal lane; indefinite blocks are prohibited.\
2.9.7 **Co-review patterns.** Co-review patterns apply when Primary Council capacity is insufficient or helix balance is incomplete; independent reviewers may be appointed with recorded scope.

***

#### 2.10 Emergency Governance Mode (Integrity/Safety Incident Mode)

2.10.1 **Purpose and eligibility triggers.** Emergency Governance Mode exists to prevent imminent harm and contain integrity or security incidents affecting membership operations, including leaks, account compromise, unsafe publication risk, or coordinated harassment/misrepresentation.\
2.10.2 **Permitted measures.** Measures may include temporary publication pause, handling elevation for specific workspaces, temporary role/access restriction, mandatory watermarking, distribution log elevation, and forced correction clocks.\
2.10.3 **Expiry, ratification, rollback, after-action.** Emergency measures must include expiry and recorded reopen conditions; post-hoc ratification or rollback is required by the appropriate authority; after-action records and public-safe summaries are required unless prohibited by law or safety.\
2.10.4 **Communications integrity during emergency mode.** Communications must be factual, non-amplifying, and record-linked; speculation and identity exposure are minimized; misquote response procedures activate by default.\
2.10.5 **Member protections.** Protected reporting, anti-retaliation, and minimal identity exposure apply; emergency mode shall not be used to suppress dissent or enable capture.

***

#### 2.11 Governance Transparency Minima and Records Minimization

2.11.1 **Public-safe summary default.** Material governance outcomes produce public-safe summaries stating what occurred, scope, limitations, expiry, and correction path.\
2.11.2 **Controlled detail minimization.** Controlled records (identity mapping, sensitive incident details, restricted artifacts) are minimized, access-logged, and retained only as necessary for integrity and lawful obligations.\
2.11.3 **Auditability requirements.** Material acts are traceable: who acted (role marker), authority basis, what changed (diff/supersession), distribution completion, and correction history.\
2.11.4 **No marketing substitution.** Governance reporting is not marketing; uncertainty and limitations are mandatory; performance claims require recorded basis.\
2.11.5 **Attribution discipline.** Attribution is permissioned, scoped, and expiry-bound; role markers may substitute for identity; unauthorized attribution is misrepresentation.

***

#### 2.12 Jurisdiction Activation and Mandate Controls (Presence Gate)

2.12.1 **Binding presence gate.** Any in-jurisdiction operating presence requires: (i) State Council constituted by record, and (ii) mandate support evidenced from competent authorities; absent both, local operation and representation are prohibited.\
2.12.2 **No implied chapters/offices/nodes.** Members must not represent chapters, offices, nodes, or national programs absent activation; such claims are misrepresentation.\
2.12.3 **Mandate withdrawal/expiry effects.** Withdrawal or expiry triggers pause of local activities and reversion to global-only participation until renewed; public listings must update by record.\
2.12.4 **Public listing requirements.** Any public listing of local structures must display activation status, scope, limitations, handling posture, and expiry/review date.\
2.12.5 **Local law conflicts and abstention protocol.** Where local law conflicts with membership rules, local operations must not proceed; conflicts are recorded and escalated; abstention is the default where legality is uncertain.\
2.12.6 **Misrepresentation classification and enforcement.** Misrepresentation is treated as a first-order integrity breach, routed to Stewardship for takedown/restriction and to Trustees where systemic risk exists.

***

#### 2.13 Integrity Assurance Program for Governance

2.13.1 **Control testing calendar.** Governance integrity is tested through periodic audits of records completeness, distribution logs, watermark drills, correction clock performance, neutrality indicators, and competition safe-meeting compliance.\
2.13.2 **Privilege creep detection.** Role-marker integrity checks detect privilege creep, unauthorized role persistence, and anomalous access patterns; corrective actions are recorded.\
2.13.3 **Correction clock performance.** Correction cycle times are measured and reported; repeated failures trigger remediation and may trigger independent review.\
2.13.4 **Sponsor influence and capture monitoring.** Sponsor concentration, influence indicators, and bloc behavior are monitored; breaches trigger interventions and disclosure updates.\
2.13.5 **Competition hygiene compliance.** Convenings and workspaces are tested for prohibited-topic compliance and safe-meeting protocol adherence; violations trigger restrictions and retraining.\
2.13.6 **Corrective actions.** Findings require recorded corrective actions with owners, deadlines, verification of closure, and repeat-prevention controls.\
2.13.7 **Independent review triggers.** High-impact incidents, repeated failures, or credible capture indicators trigger independent integrity review under controlled handling and access logging.

***

#### 2.14 Records Discipline (Validity-by-Record, Supersession, and Notice)

2.14.1 **Record-validity requirement.** Every material governance act (membership state, role markers, releases, sanctions, appeals, corrections, activation determinations) is valid only when recorded with scope, authority basis, limitations, expiry, and distribution rules.\
2.14.2 **No silent edits; supersession-only.** Record-valid acts may not be silently altered; updates occur by supersession with explicit diffs, effective dates, and transition rules.\
2.14.3 **Notice by Platform record.** Notices to members are authoritative only when issued by Platform record; other channels are convenience-only and non-authoritative.\
2.14.4 **Evidence basis and reason codes.** Restrictions, sanctions, role changes, and access removals must cite record basis, reason codes, minimum evidence basis, and appeal pathway.\
2.14.5 **Retention, deletion, de-identification.** Records are retained consistent with integrity needs and lawful obligations; deletion requests are honored within record-integrity limits through minimization, de-identification, or access restriction where appropriate.\
2.14.6 **Mismatch and lock discipline.** Off-platform assertions conflicting with Platform records trigger dispute lane routing and, where necessary, temporary locks pending correction, with recorded rationale and expiry.


---

# 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/ii.-governance.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.