> For the complete documentation index, see [llms.txt](https://docs.therisk.global/organization/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.therisk.global/organization/cooperation/nexus-guilds/membership/xxv.-forms.md).

# XXV. Forms

### Part 25 — Required Inlined Forms and Operational Schemas

*(Binding objective: “form-first governance” in which designated acts have **no force or effect** unless executed using the canonical inlined form, including mandatory handling election, explicit scope and reliance bounds, correctionability (no silent edits), and audit-grade trails for who did what, when, why, and under which authority basis.)*

***

#### 25.1 Purpose, Binding Effect, and Form-First Governance Doctrine

25.1.1 **Inlined forms as enforceable controls and guardrails.** Each inlined form is a binding governance control that hard-codes minimum required fields, attestations, scope limits, reliance bounds, handling rules, and auditability; forms are not “templates” and may not be bypassed by narrative emails, informal minutes, or ad-hoc documents.

25.1.2 **Validity-by-record (“no form, no force”).** For designated act categories (membership state changes, role markers, badge grants/revocations, safety holds, controlled distribution, jurisdiction activations, dispute outcomes), the Platform recognizes **only** acts executed through the relevant canonical form as record-valid and effective.

25.1.3 **Handling election is mandatory and determinative.** Every form instance must elect a handling class (Public-Safe / Controlled / Restricted / Special), and that election governs storage location, access controls, distribution rules, watermarking, disclosure posture, retention/deletion limits, and whether public-safe summaries are permitted or required.

25.1.4 **Non-regression rule for form evolution.** Updates to forms and form schemas may strengthen safeguards, completeness, and auditability, but shall not weaken safety, neutrality, due process, privacy minimization, identity protection, competition/procurement hygiene, or correctionability requirements.

25.1.5 **Voluntary-by-default with opt-in escalation.** Members are not compelled to execute forms unless they seek a privilege, role, controlled access, badge, publication, convening, or jurisdictional activation pathway that is explicitly gated by a form-executed act.

25.1.6 **Supersession, versioning, and effective-date discipline.** Every form has a version ID, effective date, and deprecation policy; newer versions supersede older versions by record, and where a form change affects safety or rights, the Platform publishes migration guidance and preserves the audit trail for legacy instances.

***

#### 25.2 Canonical Form Field Standards (Applies to All Forms)

25.2.1 **Minimum header and integrity fields.** Every form shall include a unique form ID, version, effective date, expiry (if applicable), handling class election, record pointer, immutable object identifier (hash/ID), status marker (draft/issued/superseded/withdrawn), and a machine-readable “validity check” block indicating required fields completed.

25.2.2 **Actor, role-marker, and consent fields.** Every form shall capture the initiating role marker, any required co-signing role markers, identity as optional unless required by lawful/handling constraints, and consent/attestation statements; contact routing shall support pseudonymous participation and identity-minimized channels.

25.2.3 **Authority basis and delegation fields.** Each form shall cite the controlling instrument section(s) and, where delegation exists, include a pointer to the delegation record; where delegation is prohibited, the form shall require an explicit “no delegation / no agency” confirmation.

25.2.4 **Scope, limitations, and prohibited-use fields.** Every form shall clearly state what the act covers, what it does not cover, what is out-of-scope by design, and what uses are prohibited; each form shall include an explicit non-executing perimeter clause applicable to the act type.

25.2.5 **Reliance bounds, uncertainty, and “no warranty” fields.** Every form shall require intended use, non-intended use, limitations and uncertainty disclosures, an expiry or review date, and a “no warranties / decision responsibility remains with the user” statement tailored to the act type.

25.2.6 **Distribution, access, and revocation propagation fields.** Each form shall define recipient sets (or a rule for recipient resolution), access tier, expiry/time-boxing, revocation propagation method (including recall notices where feasible), and watermarking obligations when controlled materials are distributed.

25.2.7 **Correction, contestation, and supersession fields.** Each form shall specify applicable correction clocks, contestation lanes, escalation routes, and the supersession mechanics that prevent silent edits and preserve prior versions with reason-coded changes.

25.2.8 **Data governance and lawful basis fields.** Each form shall classify data involved, assert minimization and purpose limitation, require lawful basis declarations where personal or sensitive data is unavoidable, capture residency/export control constraints, and enforce “no PII by default” as a standard.

25.2.9 **COI disclosure, recusal, and cooling-off fields.** Each form shall include COI prompts appropriate to the act, require disclosure where triggered, document recusals and substitutions, and flag cooling-off periods and sponsor adjacency indicators when relevant.

25.2.10 **IP, licensing, third-party materials, and contamination controls.** Each form shall require inbound rights confirmation, outbound license election (where applicable), disclosure of third-party materials and permissions, and explicit controls preventing restricted-to-open contamination and other rights hygiene failures.

***

#### 25.3 Form A — Membership Application and Attestations (Baseline Join)

25.3.1 **Join statement and lawful participation screening.** The applicant affirms voluntary participation, completes sanctions/export controls and lawful participation checks, and acknowledges that eligibility may be limited by jurisdictional or handling constraints.

25.3.2 **Non-agency, non-employment, and non-endorsement attestation.** The applicant attests they are not an agent of the Platform, not an employee, and may not represent endorsements, certification, delegated authority, or official standing by virtue of membership.

25.3.3 **Handling and conduct acknowledgment with survival obligations.** The applicant acknowledges handling rules (Public-Safe default), controlled-lane restrictions, “no copy-out/no forward” duties where applicable, and survival obligations that persist after exit for materials accessed.

25.3.4 **Political-safety, neutrality, and election-safe participation attestation.** The applicant agrees to non-partisanship, no political mobilization under Platform branding, and election-safe communications discipline consistent with neutrality and public trust.

25.3.5 **Competition/antitrust and procurement hygiene acknowledgment.** The applicant acknowledges “no deal room” and “no procurement steering” rules, prohibited topics in convenings, and agrees to comply with safe-meeting scripts and minute minimization.

25.3.6 **Export controls and sensitive jurisdiction constraints acceptance.** The applicant confirms understanding of export controls and sanctions constraints, and accepts that access, distribution, or certain work lanes may be restricted based on jurisdiction or topic sensitivity.

25.3.7 **Protected participation and anti-retaliation acknowledgment.** The applicant acknowledges protected reporting channels, anti-retaliation rules, and that retaliation or coercion triggers integrity enforcement and due process lanes.

25.3.8 **Privacy and visibility elections.** The applicant selects a privacy posture (pseudonym default), opts into or out of public attribution surfaces, and acknowledges identity minimization and the limited identity cell’s two-person unmasking rule.

25.3.9 **Consent to record-valid platform communications.** The applicant consents to receiving platform notices and record-valid communications related to membership states, access, safety holds, disputes, and corrections within the elected handling class.

***

#### 25.4 Form B — Primary Affiliation Election (Single Anchor) and Switching Record

25.4.1 **Anchor election for routing and capture-resistance.** The member elects a single primary affiliation (Guild/home domain) used for routing contributions, reviewer pools, rotation logic, and governance eligibility within anti-capture constraints.

25.4.2 **Effective date, switching limits, and anti-gaming controls.** The election records an effective date; switching is rate-limited, reason-coded, and subject to anomaly detection to prevent sybil behavior, vote stacking, or rotation manipulation.

25.4.3 **Survival obligations and cross-domain duties acknowledgement.** The member acknowledges that handling survival obligations, correction duties for authored artifacts, and COI disclosure requirements persist when roaming across Guilds or lanes.

25.4.4 **Reviewer pool routing flags without pay-to-play effect.** The election may set eligibility flags for reviewer rotation pools, but explicitly disclaims any purchase of influence, votes, credits, or roles; eligibility remains gated by PoC, COI cleanliness, and standing.

25.4.5 **Contestation window and escalation for anomalies.** The form opens a contestation window for sybil/capture indicators and defines escalation routing to integrity review, including temporary holds on rotation eligibility if risk signals are triggered.

***

#### 25.5 Form C — Identity Verification Opt-In (Optional) and Role-Marker Binding

25.5.1 **Verified identity election and scoped enablement.** The member may opt into verified identity for specified purposes (e.g., controlled access, certain host-institution contexts) while acknowledging that verification is not endorsement, certification, or authority.

25.5.2 **Identity cell processing with two-person rule and access logging.** Verification is processed through the identity minimization cell, requiring dual authorization for access and maintaining access-logged records separate from public role markers.

25.5.3 **Unmasking criteria limited to necessity and proportionality.** Unmasking is permitted only upon lawful necessity or safety necessity, must be proportionate to risk, must be reason-coded, and must be recorded as an auditable act.

25.5.4 **Retention, minimization, and visibility suppression options.** The form specifies retention schedules, deletion/de-identification options consistent with record integrity, and allows visibility suppression where safety or privacy risks warrant.

25.5.5 **Withdrawal and effect of verification reversal.** The member may withdraw verification; role markers may persist where already issued, but identity surfaces are suppressed unless lawful/handling obligations require continued retention.

***

#### 25.6 Form D — Proof of Competence (PoC) Claim and Evidence Submission

25.6.1 **PoC level request and domain-bounded scope.** The applicant specifies the PoC level requested, the domain boundary (what they claim competence for), and the reliance bounds for any privileges tied to the PoC.

25.6.2 **Evidence submission with provenance, rights, and linkage.** The form requires evidence items, provenance links, artifact IDs/hashes, and rights hygiene confirmations sufficient to allow replayability and auditability without unnecessary identity disclosure.

25.6.3 **Reviewer assignment, rotation constraints, and COI screening.** Reviewers are assigned through rotation controls that limit concentration, avoid repeated pairings, and enforce COI screening and recusal prior to accessing evidence.

25.6.4 **Decision record, expiry, and renewal clock.** The outcome is recorded with reason codes, scope limits, expiry date, and renewal requirements, including mandatory refresh triggers if the domain shifts materially or misuse risk rises.

25.6.5 **Appeal lane and remediation pathway.** The form specifies appeal rights, remediation options (training, re-submission, supervised practice), and time windows, with handling election and identity minimization preserved.

***

#### 25.7 Form E — Integrated Learning Account (ILA) Setup and Portability Election

25.7.1 **ILA creation, objectives, and learning lane selection.** The member defines learning objectives, selects learning tracks and lanes (including sensitive-lane training where relevant), and records the initial competence baseline.

25.7.2 **Handling constraints and disclosure minima for learning artifacts.** Learning artifacts are handling-classified, identity-minimized where feasible, and governed by disclosure minima that prevent learning outputs from being misused as marketing claims.

25.7.3 **Credential clocks, renewal rules, and failure effects.** The form defines renewal/recertification cycles, conditions for lapse, and the consequences of lapse (loss of controlled access or role eligibility) without retroactive harm.

25.7.4 **Portability election with non-regression enforcement.** The member may elect portability of learning records across Guilds, subject to non-regression of handling and domain-specific add-ons; portability does not confer authority.

25.7.5 **Revocation, correctionability, and appeal trail.** Learning credentials and records are correctionable only via supersession; revocations and corrections are recorded, reason-coded, and appealable.

***

#### 25.8 Form F — Contribution Intake Record (CRS Event Capture)

25.8.1 **Contribution type taxonomy and class marker.** The contribution is categorized (methods, datasets, benchmarks, proof packs, reviews, clinics, drills, maintenance, safety support) with a class marker used for CRS accounting while prohibiting pay-to-play effects.

25.8.2 **Evidence linkage and proof-of-work requirements.** The form requires artifact pointers, review logs, replication logs, session dockets, or other proof-of-work evidence proportional to the value of credit claimed, preventing hype-based accrual.

25.8.3 **COI disclosures, recusals, and sponsor adjacency flags.** The contributor discloses conflicts and sponsor adjacency where relevant; recusals and role incompatibilities are recorded to prevent self-review and influence laundering.

25.8.4 **Single-source credit assignment and co-tagging rules.** A lead Guild-of-record is selected, co-tagging is permitted under explicit rules, and double-counting is prevented through unique contribution identifiers and routing logic.

25.8.5 **Clawback triggers, reversals, and dispute integration.** The form specifies clawback triggers for fraud/gaming/misrepresentation, defines reversal mechanics, and links to dispute lanes and correction clocks.

***

#### 25.9 Form G — Review Assignment and Reviewer COI Declaration

25.9.1 **Review scope, handling class, and reliance bounds.** The assignment defines what is being reviewed, the handling constraints, and what the review can and cannot be relied upon to mean.

25.9.2 **Eligibility gates and lawful constraints.** Reviewer eligibility is gated by standing, PoC level, training, handling tier competence, export/sanctions constraints, and any jurisdiction-specific limitations.

25.9.3 **COI declaration, recusal duties, and substitution plan.** Reviewers must declare COI, recuse where triggered, and accept substitution rules; failure to disclose is sanctionable and correctionable.

25.9.4 **Rotation, anti-concentration, and pairing controls.** The form applies rotation constraints to prevent repeated pairings, single-entity dominance, or capture of queues, and logs override decisions with reason codes.

25.9.5 **Outcome record with dissent/minority preservation.** Outcomes are recorded as accept/deny/remand/hold with evidence references; dissent and minority reports are preserved and linked for correctionability and transparency.

***

#### 25.10 Form H — Release Submission (Artifact Publication Request)

25.10.1 **Complete artifact metadata and admissibility fields.** The submitter provides scope, limitations, reliance bounds, provenance, dependencies, and expiry/review date sufficient for safe reuse under scrutiny.

25.10.2 **Safety and dual-use self-assessment with targeting-cue screening.** The submitter completes a dual-use and targeting-cue screening checklist, declaring what has been abstracted, redacted, or withheld for safety.

25.10.3 **Handling election and distribution plan.** The submission specifies whether the release is public-safe, controlled, or restricted; defines recipients (or rules); and includes watermarking and “no forward” constraints where applicable.

25.10.4 **Correction clock commitment and supersession readiness.** The submitter confirms correction obligations, provides a correction contact path, and commits to supersession-only updates with traceable diffs and effective dates.

25.10.5 **Mandatory disclaimers and prohibited-claims verification.** The form enforces non-endorsement, non-certification, and “not regulatory compliance” language, and blocks prohibited claims (certified/approved/compliant/licensed).

25.10.6 **Cross-council review trigger declaration.** The submitter flags rights impacts, market sensitivity, critical infrastructure sensitivity, or other triggers requiring Stewardship gate review and/or cross-council review before release.

***

#### 25.11 Form I — Safety Gate Determination (Stewardship Review Record)

25.11.1 **Safety risk categorization with reason codes.** The Stewardship gate classifies safety risks (dual-use, critical infrastructure cues, vulnerability/exploit adjacency, market sensitivity, panic amplification, youth/vulnerable persons risk) with reason-coded findings.

25.11.2 **Required mitigations and enforceable release conditions.** The record specifies required mitigations (abstraction/redaction/delay/partition/controlled annex) and makes release conditional on completion and verification of those mitigations.

25.11.3 **Distribution restrictions and watermark mandates.** The gate defines permitted recipient sets, access tiers, watermarking requirements, expiry/time-boxing, and recall propagation obligations where controlled materials are distributed.

25.11.4 **Stop-the-line holds with mandatory expiry and reopen criteria.** If a hold is imposed, the record includes expiry, review cadence, reopen conditions, and escalation routes; indefinite holds are prohibited without renewal by record.

25.11.5 **Public-safe summary requirement and exception logic.** The gate requires a public-safe summary unless prohibited by handling or law, and records the exception rationale where public disclosure is limited.

***

#### 25.12 Form J — Stop-the-Line Hold / Takedown / Temporary Restriction

25.12.1 **Trigger classification and immediate scope definition.** The initiating party selects the trigger (safety, integrity, leak, conduct, misrepresentation) and defines exactly what is being paused (artifact, badge, role marker, room, distribution set).

25.12.2 **Hold scope, impact, and dependency mapping.** The record captures affected dependencies (downstream artifacts, citations, badge displays, registry listings) and specifies which surfaces must be updated immediately.

25.12.3 **Mandatory expiry, review cadence, and authority basis.** The hold is time-boxed, with a required review cadence and a cited authority basis; extensions require a new record with updated rationale.

25.12.4 **Notice, appeal route, and handling posture.** The record defines who is notified, the appeal lane, the handling election for the case file, and the minimum public-safe notice content where disclosure is permitted.

25.12.5 **Reopen conditions and correction obligations.** The record defines reopen conditions, required corrective actions, and whether a correction/supersession record must be issued before reinstatement.

***

#### 25.13 Form K — Correction / Errata / Supersession Record

25.13.1 **Change description with impact statement and severity tier.** The record specifies what changed, why, impact on reliance, severity classification, and whether downstream artifacts must be updated.

25.13.2 **Supersession chain and “current version” resolution.** The record links prior versions, establishes the new current version, and preserves all superseded versions with immutable pointers.

25.13.3 **Recall propagation and recipient reconciliation.** Where prior distribution occurred, the record references distribution logs, specifies who must be notified, and records recall notices and acknowledgements where feasible.

25.13.4 **Updated reliance bounds, expiry, and limitations.** The correction updates intended use/non-intended use, limitations, uncertainty disclosures, and expiry/review date to reflect new understanding.

25.13.5 **Dissent/minority preservation and contestation linkage.** Any dissent or minority reports remain linked across versions, and dispute lanes are referenced where scientific disagreement persists.

***

#### 25.14 Form L — Badge/Marking Grant, Renewal, and Revocation

25.14.1 **Badge class, scope statement, and non-equivalence disclaimer.** The record specifies badge type, what was reviewed, what was not reviewed, and explicitly disclaims certification, approval, compliance, or regulatory standing.

25.14.2 **Evidence basis and reviewer roster (role markers).** The record references provenance and review logs, lists reviewer role markers, and documents COI screening and recusals.

25.14.3 **Expiry, renewal criteria, and revalidation triggers.** Badges are expiry-bound; renewal criteria and triggers (new evidence, new vulnerabilities, misuse signals) are documented with required checks.

25.14.4 **Revocation triggers, notice, and public-safe updates.** Revocations are reason-coded, recorded with effective date, and propagated to registries and public trust surfaces with public-safe notices where permitted.

25.14.5 **Misuse monitoring and enforcement linkage.** The record links to misrepresentation reporting channels, specifies takedown actions for badge misuse, and references the due process lane for disputes and appeals.

***

#### 25.15 Form M — Convening Notice (Calendar-Safe) and Handling Election

25.15.1 **Neutral naming and metadata minimization.** The notice uses neutral titles, avoids sensitive agenda cues, minimizes location and attendee metadata, and applies handling-appropriate distribution controls.

25.15.2 **Handling election and recording/photography policy.** The notice elects handling class, specifies whether recording is prohibited/allowed, captures consent requirements, and enforces no-capture rules in controlled lanes.

25.15.3 **Safe-meeting script selection and prohibited topics.** The notice specifies the required moderator script (competition/procurement hygiene), lists prohibited topics, and identifies stop-the-line authority.

25.15.4 **Attribution rules (permissioned, scope-bounded, expiry-bounded).** The notice states attribution posture, quoting rules, and expiry-bounded permissions; role markers are preferred over identity by default.

25.15.5 **Attendee minimization and distribution logging where required.** The notice specifies attendee list minimization, access controls, and whether distribution logging is required for dockets or controlled materials.

***

#### 25.16 Form N — Convening Docket and Session Artifact Checklist

25.16.1 **Session maturity state, objectives, and deliverable intent.** The docket declares the maturity ladder state (clinic/lab/briefing), intended outputs, and whether outputs will be published as public-safe summaries or controlled annexes.

25.16.2 **Required briefing note with limitations and reliance bounds.** The docket includes pre-reads with explicit limitations, uncertainty, reliance bounds, and prohibited-use statements appropriate to the topic.

25.16.3 **Proof Pack/AEP pointers and handling constraints.** Where a Proof Pack/AEP is used, the docket references it by ID and states handling inheritance and distribution restrictions.

25.16.4 **Dissent capture plan and minute minimization rules.** The docket specifies how dissent/minority views are recorded and how minutes are minimized to avoid unnecessary sensitive detail.

25.16.5 **Post-session correction clock and publication workflow.** The docket defines timelines for publishing summaries, issuing corrections, and filing after-action records, with public-safe first as the default.

***

#### 25.17 Form O — Program Committee Appointment (Voluntary Role Acceptance)

25.17.1 **Role scope, timebox, workload disclosure, and opt-out rights.** The appointment specifies what the role covers, how long it lasts, expected workload, and the right to resign by record without penalty beyond role expiry effects.

25.17.2 **COI declaration, recusal plan, and cooling-off requirements.** The appointee declares COI, commits to recusal rules, and accepts any cooling-off periods or rotation constraints to prevent capture.

25.17.3 **Rotation and anti-capture constraints with sponsor adjacency prohibitions.** The appointment enforces rotation, prohibits sponsor influence over decisions, and flags incompatible roles that would undermine independence.

25.17.4 **Handling, attribution, and communications integrity training acknowledgment.** The appointee confirms completion of required training for the relevant handling tier and accepts communications integrity rules and non-endorsement posture.

25.17.5 **Revocation conditions and resignation-by-record mechanics.** The appointment defines revocation triggers (misconduct, COI breach, handling violations), and the process for resignation, handover, and archive.

***

#### 25.18 Form P — Competence Cell (CCell) Formation Record

25.18.1 **Scope, deliverables, timebox, and dissolve-by-default rule.** The record defines the work scope, outputs, time limits, and dissolution triggers; CCells do not persist indefinitely without renewal by record.

25.18.2 **Steward designation, responsibilities, and continuity plan.** The record assigns a Steward, defines responsibilities (handling, records, coordination), and sets a continuity plan for turnover and archiving.

25.18.3 **Minimum PoC requirements and separation-of-duties.** The record specifies PoC minima for roles, prohibits self-review, and defines separation between builders, reviewers, and safety gate roles.

25.18.4 **Data governance posture and lawful basis declaration.** The record enforces “no PII by default,” requires lawful basis if unavoidable, and defines data minimization, retention, and access logging.

25.18.5 **Handling, distribution constraints, and workspace class selection.** The record elects handling class, defines distribution and watermarking rules, and specifies secure room/tooling requirements for controlled lanes.

25.18.6 **Dissolution, archival plan, and publication plan.** The record defines end-of-cell archiving, what becomes public-safe versus controlled, and the correction obligations that survive dissolution.

***

#### 25.19 Form Q — CCell Dissolution and Archive Record

25.19.1 **Completion statement and deliverables index with pointers.** The record lists outputs, artifact IDs, dependencies, and any known limitations or unresolved issues, enabling replay and audit after dissolution.

25.19.2 **Partition statement (public-safe vs controlled vs restricted).** The record explicitly partitions outputs by handling class and defines what may be published, what must remain controlled, and what must be restricted.

25.19.3 **Outstanding corrections and follow-on routing.** The record identifies open correction items, assigns ownership or stewardship reassignment, and routes follow-on work to appropriate Guild backlogs.

25.19.4 **Offboarding attestations and access revocation.** Members attest to handling survival obligations, return/destruction where required, and confirm that access to controlled rooms and data is revoked.

25.19.5 **Lessons learned and governance recommendations (non-operational).** The record captures method improvements, safeguards strengthening recommendations, and process issues without issuing operational directives.

***

#### 25.20 Form R — CERT Mobilization Record (Non-Executing, Evidence Support Only)

25.20.1 **Trigger rationale and evidence-support scope.** The record states why the CERT is mobilized, strictly bounds it to measurement/verification/learning artifacts, and prohibits command, dispatch, or operational direction.

25.20.2 **Participating CCells and liaison routing (non-agency).** The record lists participating CCells and liaison points, clarifies non-agency status, and limits interactions to routing and evidence handling.

25.20.3 **Handling election, distribution logging, and watermarking requirements.** The record enforces handling inheritance, distribution logs for controlled materials, watermarking, time-boxed access, and recall propagation.

25.20.4 **Responsible disclosure routing constraints.** The record specifies how sensitive findings are routed (e.g., vulnerability disclosure), including redaction/abstraction rules and disclosure delays where necessary.

25.20.5 **Dissolution triggers and after-action obligations.** The record sets expiry and dissolution triggers, requires an after-action report, and defines correction clocks for any released artifacts.

25.20.6 **Explicit non-command / non-agency disclaimers.** The record includes binding disclaimers that the CERT does not exercise public authority, enforcement, or operational control, and that outputs are informational and scope-bound.

***

#### 25.21 Form S — CERT After-Action Record (Public-Safe Default)

25.21.1 **Measured vs inferred with limitations and uncertainty taxonomy.** The record distinguishes measurements from inferences, discloses uncertainty and data gaps, and states reliance bounds and expiry.

25.21.2 **Withheld content for safety (reason-coded).** The record documents what was withheld or abstracted for safety (targeting cues, exploit detail, market sensitivity) with reason codes and handling constraints.

25.21.3 **Corrections/supersessions and recall propagation.** The record lists corrections issued, supersession chains, and any recall notices or recipient notifications required by distribution logs.

25.21.4 **Integrity incidents encountered and containment summary.** The record notes any integrity/security/conduct incidents in a minimized way, using controlled annexes when necessary, and documents containment actions.

25.21.5 **Recommendations for method updates, training, and safeguards strengthening.** The record proposes updates to methods, PoC/ILA training needs, and safeguards improvements without issuing operational directives.

***

#### 25.22 Form T — Host Institution Designation Request and Acceptance

25.22.1 **Host scope and permitted activities.** The request specifies hosting purposes (compute-to-data, training, safe convening, evidence work) and prohibits execution, enforcement, procurement steering, or regulated activity.

25.22.2 **Sovereign data zone posture and compute-to-data capability.** The host declares SDZ alignment, data residency posture, access logging, and capability to support compute-to-data without centralizing sensitive data.

25.22.3 **Lawful basis and local constraints declaration (non-advice).** The host declares local legal constraints and lawful basis boundaries without receiving legal advice from the Platform, and agrees to abstention/pause rules on conflicts.

25.22.4 **Non-execution perimeter acknowledgment and non-agency clause.** The host accepts non-agency status, non-delegation, and non-endorsement constraints, and commits not to represent hosting as authority.

25.22.5 **Handling, retention, incident routing, and audit commitments.** The host commits to handling rules, retention schedules, incident reporting lanes, watermarking and distribution logs where required, and periodic audit readiness.

25.22.6 **Revocation/pause and offboarding data disposition plan.** The designation includes pause/revocation triggers, offboarding steps, and data disposition controls (return/destruction/de-identification) consistent with record integrity.

***

#### 25.23 Form U — State Council Constitution Record (Activation Prerequisite)

25.23.1 **Seat composition, helix balance evidence, and independence posture.** The record proves helix balance, documents independence criteria, captures COI disclosures, and sets rotation/cooling-off rules for capture resistance.

25.23.2 **Authority basis, perimeter reaffirmation, and reserved matters.** The record cites authority basis under Platform instruments, reaffirms strict non-execution, and enumerates reserved matters (activation, NWGs, Host Institutions, CERT approvals).

25.23.3 **Handling and identity minimization posture (role markers).** The record defines role-marker usage, identity cell access limits, minutes minimization, and handling election for Council proceedings.

25.23.4 **Contestation window and public-safe summary requirements.** The constitution opens a contestation window for legitimacy anomalies and requires a public-safe summary unless handling/law prevents disclosure.

25.23.5 **Renewal, expiry, de-recognition, and reversion-to-global-only triggers.** The record defines expiry and renewal cadence, de-recognition conditions, and automatic reversion to Global-only status upon lapse or mandate withdrawal.

***

#### 25.24 Form V — Mandate Support Evidence Record (Competent Authority)

25.24.1 **Authority source and scope of support (in/out boundaries).** The record identifies the competent authority, defines what support covers (evidence work pathways) and what it explicitly does not cover (no delegation of state authority).

25.24.2 **Duration/expiry, renewal conditions, and withdrawal mechanics.** The record specifies time bounds, renewal requirements, and withdrawal effects, including automatic pause and listing updates.

25.24.3 **Non-delegation clarification and non-agency confirmation.** The record affirms that no governmental authority is delegated and that the Platform remains non-executing and non-agency.

25.24.4 **Public listing statement and activation labeling.** The record specifies how activation status will appear in public trust surfaces (Activated / Global-only / Paused), with scope limits, expiry, and non-endorsement language.

25.24.5 **Withdrawal effects, pause protocol, and notice routing.** The record defines immediate pause triggers, communications routing, and dispute/appeal lanes if the mandate support becomes contested.

***

#### 25.25 Form W — National Working Group (NWG) Charter Record (Time-Boxed Program)

25.25.1 **Program scope, deliverables, timebox, and dissolve-by-default clause.** The charter defines outputs, timelines, and dissolution triggers, ensuring NWGs do not evolve into shadow institutions or permanent bodies without renewal.

25.25.2 **Governance lane assignment and cross-council trigger mapping.** The charter identifies the lead Guild/council lane and maps cross-council review triggers for safety, rights impacts, CI sensitivity, or market sensitivity.

25.25.3 **Handling election and publication plan (public-safe default).** The charter defines what is publishable as public-safe summaries, what requires controlled annexes, and the distribution logging rules for controlled materials.

25.25.4 **Data governance posture and lawful basis constraints.** The charter enforces minimization and “no PII default,” documents lawful basis where unavoidable, and sets access logging and retention boundaries.

25.25.5 **Dissolution, after-action obligations, and artifact routing.** The charter mandates after-action records, correction clocks, and routing of deliverables into registries/backlogs with supersession discipline.

***

#### 25.26 Form X — Jurisdictional Mirror Listing and Status Update Record

25.26.1 **Listing type and jurisdictional implications.** The record specifies mirror type (chapter, NWG, host program, CERT) and confirms whether activation prerequisites are met for in-jurisdiction presence.

25.26.2 **Activation status label, scope, and limitations.** The listing states Activated/Global-only/Paused/De-recognized, and includes explicit scope boundaries and non-authority disclaimers.

25.26.3 **Effective dates, expiry, renewal schedule, and pause triggers.** The record defines when the listing is effective, when it expires, renewal cadence, and automatic pause conditions (mandate lapse, safety incidents, non-compliance).

25.26.4 **Reliance bounds and non-endorsement disclaimers for public display.** Public listings include reliance bounds, limitations, and non-endorsement language to prevent authority confusion.

25.26.5 **De-recognition, reversion protocol, and distribution reconciliation.** The record defines de-recognition triggers and reversion to Global-only status, and references distribution logs where notices/updates must propagate.

***

#### 25.27 Form Y — Incident Report (Safety, Integrity, Security, Conduct)

25.27.1 **Incident classification, severity tier, and handling election.** The report categorizes the incident, assigns severity, elects handling class, and defines immediate access controls for case materials.

25.27.2 **Immediate containment actions and stop-the-line triggers.** The report records containment steps taken (holds, access revocations, recalls), who authorized them, and the expiry/review cadence for interim measures.

25.27.3 **Evidence preservation with chain-of-custody.** The report references logs, hashes, timestamps, and access-log entries, and enforces tamper-resistant evidence vault rules where required.

25.27.4 **Notification and disclosure routing (public-safe vs controlled).** The report defines who must be notified, what can be said publicly (if anything), and how controlled details are restricted and access-logged.

25.27.5 **Remediation plan, verification of closure, and recurrence controls.** The report sets corrective actions, assigns verification responsibilities, and requires closure verification by record.

25.27.6 **Protected participation marker and anti-retaliation routing.** The report records protected reporting status, safety accommodations, and anti-retaliation obligations with escalation triggers.

***

#### 25.28 Form Z — Appeal and Remedy Request (Due Process Lane Intake)

25.28.1 **Decision challenged with record linkage and effective date.** The appellant identifies the challenged decision, cites the record pointer, and captures effective dates and any interim measures in force.

25.28.2 **Grounds for appeal with supporting evidence pointers.** The appellant selects grounds (procedural error, new evidence, bias/COI, disproportionality) and links supporting evidence under handling constraints.

25.28.3 **Requested remedy and scope limits.** The appellant specifies the requested remedy (reconsideration, correction, reinstatement, redaction, modification of conditions) and acknowledges safeguard-first constraints.

25.28.4 **Handling election and confidentiality preferences.** The appeal is handling-classified (controlled by default), with privacy preferences and identity minimization preserved unless lawful necessity requires otherwise.

25.28.5 **Timelines, response clocks, and accessibility/language accommodations.** The form sets filing deadlines, response clocks, and provides structured requests for language support and accessibility accommodations.

***

#### 25.29 Form AA — COI Disclosure, Recusal, and Cooling-Off Record

25.29.1 **COI taxonomy selection and disclosure completeness.** The member declares COI category (financial, professional, relational, sponsor ties), materiality, and relevance to the affected matter.

25.29.2 **Affected scope mapping and risk statement.** The record specifies which artifacts, review lanes, convenings, roles, or procurement-adjacent contexts are affected and provides a brief risk statement.

25.29.3 **Recusal plan, substitution logic, and “no self-review” confirmation.** The record specifies recusal boundaries, who substitutes, and confirms that self-review and conflicted adjudication are prohibited.

25.29.4 **Cooling-off schedule, re-entry criteria, and audit trail.** The record documents cooling-off duration, re-entry conditions, and logs any exceptions with reason codes.

25.29.5 **Enforcement linkage, consequences, and appeal path.** The record links to enforcement triggers for non-disclosure, documents consequences for breach, and identifies appeal lanes.

***

#### 25.30 Form AB — Competition/Procurement Safe-Meeting Attestation (Convenings)

25.30.1 **Prohibited topics checklist and participant acknowledgement.** Participants affirm prohibited topics (pricing, allocation, market division, bid coordination, procurement steering) and agree to leave or stop if violations occur.

25.30.2 **Moderator scripts, minute controls, and redaction rules.** The attestation identifies the moderator script, defines minute minimization, and sets redaction rules to prevent capture of sensitive competitive information.

25.30.3 **Escalation triggers and stop-the-line authority with time-boxed removals.** The form names stop-the-line authority, sets escalation thresholds, and permits time-boxed removals for violations with reason-coded records.

25.30.4 **Removal conditions and non-retaliation statement.** The form defines removal triggers, prohibits retaliation for compliance actions, and provides protected reporting routes.

25.30.5 **Record-valid minutes and public-safe summary requirements.** The form requires record-valid minutes (minimized) and, where appropriate, a public-safe summary that does not disclose prohibited competitive content.

***

#### 25.31 Form AC — IP and Licensing Intake (Inbound Grant; Outbound License Election)

25.31.1 **Rights assurance and contributor warranty (minimum necessary rights).** Contributors warrant they have rights to submit, identify any restrictions, and confirm that submission does not violate contracts, confidentiality, or third-party rights.

25.31.2 **Inbound license grant terms (default posture).** The form records the inbound license grant needed for review, storage, and publication under the Platform’s default open posture, subject to handling constraints.

25.31.3 **Outbound licensing election (open by default; restricted exceptions gated).** The form records outbound license choice; restricted exceptions require explicit justification and safety/rights gating.

25.31.4 **Third-party materials disclosure with permissions and citations.** The contributor discloses third-party materials, permissions, and citations, and confirms no unauthorized copying or license incompatibility.

25.31.5 **Contamination prevention and clean-room notes.** The form enforces restricted-to-open contamination prohibitions and documents any clean-room process needed to keep open artifacts uncontaminated.

***

#### 25.32 Form AD — Data Room Access Request (Controlled/Restricted Datasets)

25.32.1 **Access purpose, scope, and non-intended use restrictions.** The request defines why access is needed, limits scope, and accepts prohibitions on targeting cues, exploitation, re-identification attempts, and onward sharing.

25.32.2 **Eligibility gate confirmation (PoC, training, lawful constraints, jurisdiction limits).** The request confirms PoC/handling competence, required training completion, export/sanctions constraints, and any jurisdictional restrictions.

25.32.3 **Distribution logging, watermark acceptance, and no copy-out controls.** The requester accepts watermarking, time-boxed access, access logging, and “no copy-out/no forward/no print” constraints for controlled data rooms.

25.32.4 **Expiry, revocation, and return/destruction attestations.** The requester accepts expiry and revocation, and commits to return/destruction or de-identification attestations on exit or upon revocation.

25.32.5 **Enforcement linkage and breach consequences.** The request links breaches to immediate access removal, incident reporting, due process lanes, and sanctions ladder outcomes as applicable.

***

#### 25.33 Form AE — Platform Governance Schema Change Proposal (Governance-Critical)

25.33.1 **Proposed change definition and invariants impact check.** The proposal clearly states the change, affected schemas and fields, and evaluates impact on invariants (safety, neutrality, due process, privacy minimization, correctionability).

25.33.2 **Safety, capture, and neutrality analysis with non-regression attestation.** The proposer provides an abuse analysis (gaming/capture risks), asserts non-regression, and identifies compensating controls if risk changes.

25.33.3 **Migration plan, backward compatibility, and rollback plan.** The proposal includes migration steps, compatibility posture, and a rollback plan that preserves record integrity and avoids retroactive harm.

25.33.4 **Notice, contestation windows, and stakeholder routing.** The proposal defines who is notified, contestation windows, and review lanes (Stewardship/Trustees/GA) with handling-appropriate disclosures.

25.33.5 **Approval lane and quorum logic.** The record specifies required approvals and quorums for governance-critical changes and logs dissent/minority reports.

25.33.6 **Effective date, audit verification, and post-change monitoring.** The proposal defines effective date, requires audit verification of correct implementation, and sets monitoring metrics for regression detection.

***

#### 25.34 Form AF — Pricing/Entitlement Change Notice (Membership Add-Ons)

25.34.1 **Change description, scope, and rationale (non-operational).** The notice states what is changing, which entitlements are affected, and why, without implying governance influence or authority changes.

25.34.2 **Anti-pay-to-play assurance statement (binding).** The notice explicitly states that payments cannot buy votes, roles, badges, review outcomes, or visibility, and that pricing changes do not alter governance rights.

25.34.3 **Scholarship/waiver continuity and accessibility impact statement.** The notice documents how waivers and scholarships continue, and assesses impacts on low-resource participants and accessibility.

25.34.4 **Notice period, effective date, and opt-out/transition path.** The notice sets a notice period, effective date, and transition options, including downgrade/exit rules without retaliation.

25.34.5 **Billing integrity dispute lane and remedy options.** The notice links to a dispute lane for billing errors, sets response clocks, and defines remedies (refunds/credits) consistent with nonprofit compatibility.

***

#### 25.35 Form AG — Service Availability / Safety Hold Notice (Non-Guarantee)

25.35.1 **Affected services/entitlements and scope of impact.** The notice identifies impacted services, the functional impact, and what remains available, avoiding over-promises or implied guarantees.

25.35.2 **Safety/integrity basis with record linkage and reason codes.** The notice cites the record basis and reason codes for the hold (security incident, integrity risk, safety concerns), consistent with handling constraints.

25.35.3 **Time-boxed duration, reopen criteria, and review cadence.** The hold is time-boxed and includes reopen conditions and review cadence; extensions require superseding notices by record.

25.35.4 **Member communications protocol (record-valid).** The notice specifies how members are informed, what can be shared publicly, and how controlled details are restricted and access-logged.

25.35.5 **Post-hoc public-safe explanation and corrections linkage.** Where permitted, the notice requires a public-safe explanation after resolution and links any resulting corrections, revocations, or policy updates.

***

#### 25.36 Form AH — Annual Transparency Pack Index (Registry Outputs)

25.36.1 **Public-safe transparency pack index and required metrics.** The index lists required public-safe counts, states, trends, corrections performance, disputes throughput, and non-endorsement disclosures.

25.36.2 **Controlled integrity pack index (access-logged).** The index lists controlled audit artifacts (sampling results, anomaly detection outputs, access-log audits) distributed on a need-to-know basis.

25.36.3 **Corrections/dispute throughput summary with clock performance.** The pack includes performance against correction clocks and dispute response targets, with limitations and uncertainty statements.

25.36.4 **Sponsor concentration indicators (public-safe).** The pack includes sponsor concentration and influence indicators in public-safe form consistent with anti-capture and neutrality posture.

25.36.5 **Improvement actions, verification schedule, and supersession links.** The pack lists improvement actions, verification checkpoints, and links to superseding records so transparency itself remains correctionable.

***

#### 25.37 Form Governance: Version Map, Deprecation, and Cross-References

25.37.1 **Canonical form index with IDs, versions, effective dates, and handling defaults.** The index is the authoritative list of valid forms and indicates default handling classes and required co-signers for each form type.

25.37.2 **Deprecation and invalidation rules with migration requirements.** The governance sets when old forms become invalid, how long grace windows last, and what migration steps are required to preserve validity.

25.37.3 **Cross-reference map to Parts 0–26 and field inheritance.** The governance maps each form to governing Parts and identifies inherited invariants and required fields that must remain consistent across the system.

25.37.4 **Audit trail requirements for changes and contestation outcomes.** Every change to forms is recorded with who proposed it, why, approval lane outcomes, dissent preservation, and contestation results, all by record.

25.37.5 **Public-safe release notes for form updates (non-marketing; limitations included).** Each form update publishes a public-safe change log describing what changed, why, the impact on members, effective dates, and any limitations or risks, without marketing language or implied endorsement.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.therisk.global/organization/cooperation/nexus-guilds/membership/xxv.-forms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.