> 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/xxi.-lifecycle.md).

# XXI. Lifecycle

{% hint style="warning" %}
**Draft instrument.** The clauses, fees, credits and effective dates on this page are drafts: no adoption record exists, and nothing here is in force. Ordinary participation has no fee ([NWG](/organization/governance-in-operation/nwg.md)).
{% endhint %}

**Where this fits:** all six sectors ([The Model](/organization/model.md)) · [Labs](/organization/programme/labs.md), [Risk Academy](/organization/programme/academy.md) · communities of practice by sector, supplying the questions of the Labs pillar; National Working Groups ([NWG](/organization/governance-in-operation/nwg.md)) · community of practice.

**In brief.** \_(Binding objective: make the entire member journey safe, contestable, and auditable by design; keep escalation opt-in, privileges time-boxed, and every material event record-valid. Read against the international frameworks it serves ([UN General Assembly 2015](https://www.undrr.org/publication/sendai-framework-disaster-risk-reduction-2015-2030); [FAO 2014](https://www.fao.org/4/bl496e/bl496e.pdf); [One Health High-Level Expert Panel (OHHLEP) et al. 2022](https://doi.org/10.1371/journal.ppat.1010537)) and the [Nexus Standards](/organization/institutions/nexus-standards.md) that govern its records ([NS-0](https://nexustandards.com/standards/ns-0/), [NS-13](https://nexustandards.com/standards/ns-13/)). "An experiment is exploratory: its results are labelled as such and become evidence only after the Foundry rebuilds and the Universe tests them." (Labs pillar boundary). Ordinary participation has no fee. Paid work, internships and fellowships are separate arrangements, and unqualified contributors never take safety-critical tasks.

{% hint style="info" %}
**Read with the current model (2026-10-21).**

* Everything this page describes is a design in formation. No national, regional or global consortium is recorded as constituted or active; the current service level is R0, information and enquiries ([Status and service levels](/organization/governance-in-operation/status-and-service-levels.md)). Where the text below reads as operation, read it as design.
* Ordinary participation has no fee; selection precedes payment, and a seat never buys office, a technical conclusion, public authority or procurement treatment. Paid work, internships and fellowships are separate arrangements ([NLC](/organization/governance-in-operation/nlc.md); [NWG](/organization/governance-in-operation/nwg.md)).
* Recognition, scoring and validation record what was shown under stated conditions. None is a certification, licence, rating or approval, and no country or institution is ranked.
  {% endhint %}

### Part 21 — Lifecycle (Join → Participate → Earn Standing → Govern → Publish → Correct → Exit)

*(Binding objective: make the entire member journey **safe, contestable, and auditable** by design; keep escalation **opt-in**, privileges **time-boxed**, and every material event **record-valid**.)*

#### 21.1 Purpose, Scope, and Lifecycle Doctrine

21.1.1 **Lifecycle as governance control.** Lifecycle states exist to reduce harm, prevent capture, and preserve auditability—not to create bureaucracy.\
21.1.2 **Voluntary baseline + opt-in escalation.** Every step beyond basic access requires affirmative opt-in; no implied duties.\
21.1.3 **Non-executing perimeter reaffirmed.** No lifecycle state permits command, dispatch, enforcement, procurement steering, or regulated execution.\
21.1.4 **Platform primacy.** Lifecycle events have force only when **record-valid**; informal communications do not create rights, roles, or standing.\
21.1.5 **Safeguards supremacy.** Parts 0, 4, 10–12, 14–18, and 22 override convenience; handling/safety/due process are non-derogable.

***

#### 21.2 Entry States and Onboarding (Join)

21.2.1 **Entry states.** Visitor → Applicant → Member (Active) → Observer (optional) → Alumni (optional); transitions are record-defined.\
21.2.2 **Eligibility checks.** Sanctions/export controls, lawful participation constraints, and integrity red flags (limited and privacy-minimizing).\
21.2.3 **Consent package.** Non-agency, non-employment, non-endorsement, reliance bounds, correctionability norms, and handling survival obligations.\
21.2.4 **Baseline orientation.** PoC0: non-executing perimeter, conduct/code, handling basics, neutrality constraints, misrepresentation prohibitions.\
21.2.5 **Identity posture at entry.** Pseudonymous enrollment permitted by default; verified identity only when required by handling/lawful constraints.\
21.2.6 **Primary affiliation election.** “Primary home + roaming” anchor logic (Guild/Council routing, rotation pools, anti-gaming guardrails).\
21.2.7 **Account security setup.** MFA, recovery posture, device hygiene guidance, access logging notice, and compromise-response instructions.\
21.2.8 **Accessibility + multilingual onboarding.** Reasonable accommodations and low-bandwidth pathways; translation integrity controls.\
21.2.9 **Onboarding completion record.** Effective date, entry state, handling acknowledgements, and initial privileges.

***

#### 21.3 Participation (Contribute, Observe, Review) — Voluntary-by-Default

21.3.1 **Participation modes.** Observe, contribute, replicate, review (if eligible), convene-support (if eligible).\
21.3.2 **Contribution types.** Issues, drafts, datasets, benchmarks, method cards, templates, release notes, safe summaries, corrections.\
21.3.3 **Handling election per contribution.** Public-safe default; controlled/restricted lanes require PoC/role gates and distribution discipline.\
21.3.4 **Routing and cross-guild tagging.** Lead Guild-of-record, co-tag limits, no double-counting; anti-gaming and sybil defenses apply.\
21.3.5 **COI disclosure triggers.** Self-report baseline plus structured prompts in review/convening/badging contexts; recusal is recordable.\
21.3.6 **Safe collaboration constraints.** No procurement steering, no deal rooms, no market coordination, no operational direction, no endorsement claims.\
21.3.7 **Jurisdictional mirrors.** Participation referencing local bodies requires Part 20 activation gates; no implied local presence.\
21.3.8 **Boundary overlays.** Extra constraints for public officials (ethics/gifts/mandate safety) and regulated professionals (MNPI/market sensitivity).\
21.3.9 **Participation logs.** Auditability by record while minimizing identity exposure; role markers preferred.

***

#### 21.4 Standing and Member-in-Good-Standing (Earn Standing)

21.4.1 **Standing doctrine.** Earned by recorded work + compliance—not reputation, title, sponsorship, or payment.\
21.4.2 **Standing states.** Active, Limited, Restricted, Suspended, Removed, Read-Only; each state defines privilege ceilings.\
21.4.3 **MGS requirements.** Baseline attestations current, handling compliance, conduct compliance, sanctions compliance, and correction duties honored.\
21.4.4 **CRS linkage.** Standing may require minimum CRS footprint for certain voluntary roles, but CRS cannot buy votes, seats, or agenda control.\
21.4.5 **PoC linkage.** PoC gates privileges; PoC is platform-limited competence signaling with renewal clocks.\
21.4.6 **iVRS indicators.** Integrity/quality/correction performance may affect standing (e.g., repeated failures trigger Limited/Restricted).\
21.4.7 **Lapse + grace.** Grace windows and re-attestation requirements are record-defined; privileges downgrade on lapse.\
21.4.8 **Portability across Guilds.** Equivalent-or-stronger handling rules; no portability that reduces safeguards.\
21.4.9 **Clawbacks and corrections.** Standing may be corrected for fraud/gaming/misrepresentation with reason-coded records and appeal rights.

***

#### 21.5 Privilege Escalation (Opt-In Roles and Controlled Lanes)

21.5.1 **Least privilege.** Default minimal access; elevations are time-boxed and scope-bound.\
21.5.2 **Eligibility gates.** PoC thresholds, CRS footprint, COI cleanliness, handling training, and (where needed) jurisdiction activation.\
21.5.3 **Affirmative opt-in.** Roles are accepted explicitly; no implied duty from attendance, title, or payment.\
21.5.4 **Role scope + expiry.** Role markers include scope, duties, expiry, renewal criteria, and revocation conditions.\
21.5.5 **Controlled/restricted access.** Need-to-know, distribution logs, watermarking, expiry-by-default, and audit trails.\
21.5.6 **Rotation and recusals.** Reviewer/maintainer rotation, anti-self-review, and recusal mechanics are enforced by record.\
21.5.7 **Safety veto participation.** Eligibility is constrained; stop-the-line participation follows PoC5 rules and mandatory expiry.\
21.5.8 **Emergency-mode restrictions.** Elevated constraints, narrower scopes, tighter handling, and mandatory after-action reporting.\
21.5.9 **Transitions and handover.** Backlog continuity, handover records, and no orphaned responsibilities.

***

#### 21.6 Formation Work Units (CCells, Clinics, Sprints) — Dissolve-by-Default

21.6.1 **CCell lifecycle.** Propose → charter → staff → operate → deliver → dissolve → archive.\
21.6.2 **Clinic/sprint lifecycle.** Intake → readiness gate → run → publish summary → correct → archive.\
21.6.3 **Minimum record fields.** Scope, lead Guild mapping, handling election, deliverables, PoC gates, stewards, expiry, outputs.\
21.6.4 **Data governance per unit.** No PII by default; lawful basis required if unavoidable; compute-to-data where applicable.\
21.6.5 **Security for controlled workspaces.** Access logs, watermarking, segregation, and leak-response readiness.\
21.6.6 **Output acceptance.** Candidate/released states and reviewer sign-offs are recorded; dissent preserved.\
21.6.7 **Dissolution triggers.** Timebox end, scope completion, safety incident, mandate withdrawal, or integrity concerns.\
21.6.8 **Reuse pathways.** Replication-ready packaging, templates, and deprecation/supersession links for future cycles.

***

#### 21.7 Governance Participation (Govern)

21.7.1 **Voluntary governance participation.** Serving in governance lanes is opt-in and time-boxed.\
21.7.2 **Participation lanes.** Ballots (where permitted), comment windows, contestation submissions, rotation pools, and steward assignments.\
21.7.3 **Eligibility rules.** Anti-sybil, capture resistance, standing thresholds, and “no pay-to-play” constraints.\
21.7.4 **Governance records.** Notice, quorum, minutes minimization, handling election, and audit logs.\
21.7.5 **Dissent preservation.** Minority reports are preserved and linkable; retaliation protections apply.\
21.7.6 **Appeals linkage.** Governance disputes route to Part 22 with defined clocks.\
21.7.7 **Public-safe transparency.** Publish “what changed, scope, expiry, contestation path”—without doxxing or unsafe detail.\
21.7.8 **Recusals.** COI-driven recusals and substitutions recorded; no silent substitutions.\
21.7.9 **Public official overlays.** Ethics/gift rules, attribution safety, and mandate safety constraints.

***

#### 21.8 Publication Lifecycle (Publish)

21.8.1 **Readiness ladder.** Draft → reviewed → safety screened → release-candidate → released → deprecated/superseded.\
21.8.2 **Required components.** Limitations, uncertainty, reliance bounds, handling election, expiry, and correction path.\
21.8.3 **Badging workflow.** Scope-bound, expiry-bound, revocable markings; never “certified/approved/compliant.”\
21.8.4 **Distribution rules.** Public-safe summaries by default; controlled appendices minimized, logged, and time-boxed.\
21.8.5 **Sensitive content routing.** Dual-use, CI sensitivity, and market sensitivity triggers enforce redaction/abstraction/delay/staging.\
21.8.6 **Provenance requirements.** Dataset/method cards, lineage pointers, licenses, and reproducibility instructions.\
21.8.7 **Authorship integrity.** Contributor attribution with pseudonym support; consent-based disclosures; no forced publicity.\
21.8.8 **Post-release monitoring.** Misquote risk, misuse signals, anomaly reporting, and safety advisories.\
21.8.9 **Takedown/hold triggers.** Stewardship gate can pause or restrict dissemination with expiry and recorded rationale.

***

#### 21.9 Corrections, Deprecations, and Supersession (Correct)

21.9.1 **No silent edits.** Corrections occur via errata/deprecation/supersession records only.\
21.9.2 **Correction clocks.** Severity-tiered time targets with escalation and accountability.\
21.9.3 **Errata workflow.** Report → triage → fix → publish correction record → update pointers.\
21.9.4 **Deprecation workflow.** “Known superseded” labeling, migration guidance (where safe), and display rules.\
21.9.5 **Redistribution reconciliation.** Notify prior recipients (where logged), update distribution logs, revoke/replace as needed.\
21.9.6 **Dispute-driven corrections.** Minority reports preserved; contested points remain traceable and appealable.\
21.9.7 **Safety-driven updates.** Redaction/abstraction may occur with public-safe continuity; controlled annex handling tightened.\
21.9.8 **Integrity incident corrections.** Fraud/manipulation/gaming triggers revocations, clawbacks, and sanctions linkage.\
21.9.9 **Metrics.** Correction performance is reported in iVRS; chronic failure affects standing and privileges.

***

#### 21.10 Renewal, Lapse, Reactivation (Stay Current)

21.10.1 **Renewal cycles.** Attestations, PoC refresh, handling recertification, and security posture refresh.\
21.10.2 **Lapse states.** Grace-window downgrades; controlled access revoked by default on lapse.\
21.10.3 **Reactivation requirements.** Re-attestation, security reset, PoC renewal (as required), and COI refresh.\
21.10.4 **Role marker renewals.** Expired role markers immediately remove elevated privileges; renewals are record-valid only.\
21.10.5 **Subscription tier changes.** Subscription changes cannot confer governance influence or accelerated badging.\
21.10.6 **Scholarship/waiver renewals.** Need-based rules; disclosure minima; no sponsor-controlled renewals.\
21.10.7 **Reinstatement after restrictions.** Remedy completion, probationary access (if used), and record-valid clearance.\
21.10.8 **Notice + effective dates.** Changes take effect only by record with clear effective dates and scope.\
21.10.9 **Anti-gaming controls.** Prevent churn abuse, re-entry manipulation, and standing laundering.

***

#### 21.11 Exit, Offboarding, and Post-Exit Obligations (Exit)

21.11.1 **Voluntary exit.** Resignation-by-record with effective date; immediate role relinquishment unless a safe transition is required.\
21.11.2 **Offboarding attestations.** Handling survival, non-disclosure, and return/destruction of restricted materials where applicable.\
21.11.3 **Post-exit identity/attribution controls.** Remove/retain attribution choices (where feasible), default doxxing protection.\
21.11.4 **Post-exit correction duties.** Where feasible, authors respond to correction requests; otherwise stewardship reassigns duties by record.\
21.11.5 **Data minimization on exit.** Access removal, de-identification where possible, retention bounded by record-integrity and lawful constraints.\
21.11.6 **Alumni/read-only states.** Optional continued access to public-safe materials and legacy contributions without implied authority.\
21.11.7 **Removal for cause.** Links to Part 22 sanctions; due process, reason codes, and appeal windows required.\
21.11.8 **Rejoin rules.** Cooling-off periods and conditions after exit/removal; re-attestation and PoC refresh as required.\
21.11.9 **Final public-safe status update.** Where required, update registry status with scope/expiry/reliance bounds and contestation path.

## Sources

1. UN General Assembly (2015). Sendai Framework for Disaster Risk Reduction 2015–2030. A/RES/69/283, 3 June 2015. <https://www.undrr.org/publication/sendai-framework-disaster-risk-reduction-2015-2030>
2. FAO (2014). The Water-Energy-Food Nexus: A new approach in support of food security and sustainable agriculture. Rome: Food and Agriculture Organization of the United Nations. <https://www.fao.org/4/bl496e/bl496e.pdf>
3. One Health High-Level Expert Panel (OHHLEP), Adisasmito, W. B. et al. (2022). One Health: A new definition for a sustainable and healthy future. PLoS Pathogens 18(6): e1010537. doi:10.1371/journal.ppat.1010537. <https://doi.org/10.1371/journal.ppat.1010537>
4. Nexus Standards. NS-0: Constitution and principles. Status: PROPOSED; UNI `NXS-STD-ST-000004`. <https://nexustandards.com/standards/ns-0/>
5. Nexus Standards. NS-13: Open standards development process. Status: PROPOSED; UNI `NXS-STD-ST-000008`. <https://nexustandards.com/standards/ns-13/>
6. GCRI. The Labs pillar home. <https://therisk.global/nexus-labs/>
7. GCRI. Working groups (NWG). <https://therisk.global/consortium/national/nwg/>
8. This documentation: [Governance in operation](/organization/governance-in-operation.md); [The Model](/organization/model.md); [historical labels](/organization/reference.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.