Execute a complete, dignified individual departure from an ecosystem -- run this whenever any member chooses to leave, ensuring commitment handoff, data export, and a clean governance record.
Organizations that make leaving difficult become prisons. When departure is punitive, bureaucratically exhausting, or socially shaming, members stay out of friction rather than conviction -- and governance quality degrades because dissent becomes invisible. Albert Hirschman documented this in Exit, Voice, and Loyalty: when exit is blocked, voice atrophies, and loyalty becomes coercion. NEOS treats exit as a fundamental right, not a failure state. This skill ensures every departure is structurally clean, emotionally dignified, and operationally complete -- protecting both the departing member and the ecosystem they leave behind.
This skill applies to any individual member of a NEOS ecosystem who chooses to depart, whether from a single ETHOS or the entire ecosystem. The scope covers the full departure lifecycle: notification, commitment inventory, handoff planning, data export, formal departure record, and re-entry provision. It interacts with role-assignment (Layer II) for role transfer, agreement-registry (Layer I) for agreement obligations, and commitment-unwinding (Layer X) for structured settlement of all outstanding commitments. Out of scope: collective dissolution of an ETHOS (that is the ethos-dissolution skill) and involuntary removal (which requires Layer VI conflict resolution -- NEOS has no unilateral expulsion mechanism).
assets/departure-record-template.yaml, documenting the departure date, scope, commitment resolution status, and re-entry eligibility. The record is filed in the ecosystem's governance memory (Layer IX) and a copy is provided to the departing member.A Departure Record following assets/departure-record-template.yaml. The record contains: departure ID, member identity, departure scope (ETHOS or ecosystem), declaration date, effective departure date, commitment unwinding summary (referencing the Commitment Unwinding Ledger), data export confirmation, re-entry eligibility status, and coordinator identity. The record is accessible to the departing member indefinitely and to ecosystem governance records for historical reference.
Retention capture. The 30-day maximum handoff period prevents ecosystems from using indefinite obligation lists to trap members. The 7-day urgent exit option ensures that even members in distress can leave quickly. No commitment can extend the departure timeline beyond 30 days -- any unresolved commitment transfers to the ecosystem's emergency queue.
Social pressure capture. The departure coordinator is drawn from outside the member's primary circle, preventing intimate relationships from being weaponized as retention tools. Departure notices are factual and neutral -- no narrative framing that implies betrayal or failure.
Information capture. The portable-record skill guarantees data export rights. The ecosystem cannot withhold a member's governance participation history as leverage to prevent departure. The member's data is theirs.
Critical-role capture. A sole critical role holder cannot be prevented from leaving. The ecosystem must maintain graceful degradation capacity -- if a single departure can collapse governance, the structural fragility is the ecosystem's problem, not the departing member's obligation.
assets/departure-checklist.yaml) and any steward may sign off on the Departure RecordDeparture Records do not expire -- they are permanent governance records. The voluntary-exit process itself is reviewed annually through the ACT consent process to ensure the timeline defaults, coordinator assignment, and communication protocols remain appropriate. If any ecosystem member identifies a pattern of departure friction (e.g., consistent coordinator delays, social pressure reports), they may request a governance health audit (Layer VII) focused on exit process integrity. Re-entry eligibility does not expire unless the departing member's foundational agreement contained a specific re-entry window.
This skill is the exit process. It is self-referentially compatible: a member who is departing uses this skill to depart. The skill ensures that no other skill in the NEOS stack can override the right to exit. If any skill's process would prevent or delay departure beyond 30 days, this skill takes precedence. The Departure Record created by this skill feeds into the portable-record skill for the member's governance history and into the re-entry-integration skill if the member later returns.
When a member departs a single ETHOS but remains in the ecosystem, the departure affects only that ETHOS's roles and agreements. The member's ecosystem-level identity and agreements remain intact. When a member departs the entire ecosystem, all ETHOS are notified through the standard communication channel. Cross-ecosystem departure (leaving a federated NEOS network) follows the same process at each ecosystem level -- the member departs each ecosystem individually, receiving a portable record from each. The departure process and record format are standardized across all NEOS ecosystems to ensure interoperability when members move between ecosystems.
Rina, an AE member based at the Bali SHUR, decides to leave OmniOne after 14 months. She holds two circle roles: Comms Steward for the Bali Welcome Circle and Proposal Reviewer for the Resource Allocation Circle. She is party to 3 agreements: the UAF (Universal Agreement Field), a circle-specific communications protocol, and a shared equipment stewardship agreement. She has an outstanding resource allocation of 45 Current-Sees earmarked for a community garden project she proposed.
Rina tells Wayan, her circle facilitator, that she plans to leave. Wayan acknowledges within 24 hours and the OSC assigns Kadek, an AE member from the Education Circle, as Rina's departure coordinator. Kadek has no direct working relationship with Rina, ensuring independence.
Kadek generates Rina's commitment inventory within 4 days: 2 roles, 3 agreements, 1 resource allocation, 0 pending proposals, 0 active conflict resolutions. Rina reviews the inventory and confirms it is complete. She requests a standard 30-day handoff timeline.
Kadek initiates commitment unwinding (per the commitment-unwinding skill). For the Comms Steward role, Dewi volunteers to take over and shadows Rina for two weeks. For the Proposal Reviewer role, the Resource Allocation Circle distributes review duties across three remaining members. The UAF departure clause is executed -- Rina's signature is removed and her departure is recorded. The communications protocol agreement is amended to remove Rina as a party with consent from the remaining 4 signatories. The equipment stewardship agreement transfers Rina's portion to a communal pool. The 45 Current-Sees are returned to the Resource Allocation Circle's unallocated pool since the garden project has not yet begun.
Rina requests a full portable record export, including her Current-See participation history and all proposals she authored. The portable-record skill generates her record within 3 days.
Edge case: During handoff, the Welcome Circle discovers that Rina is the only person who knows the login credentials for OmniOne's social media accounts. This is a sole-critical-knowledge situation. Kadek escalates to the ETHOS facilitator, who arranges an emergency knowledge transfer session. The transfer is completed within the 30-day window, but the ETHOS also documents the single-point-of-failure in a governance health note to prevent recurrence. Rina's departure is not delayed -- the ecosystem adapts.
On day 28, Kadek confirms all handoffs are complete, files Departure Record DR-SHUR-2026-031, and Rina receives her copy along with her portable record. A neutral departure notice is posted to all SHUR Bali members: "Rina has departed the Bali SHUR effective March 28, 2026. The Comms Steward and Proposal Reviewer roles are being transitioned." No reasons, no editorial.
A major funder who provides 40% of OmniOne's operating budget threatens to withdraw funding if a specific high-profile member departs. The voluntary-exit skill is structurally immune to this pressure: no external party has authority to block departure, and the process does not include any checkpoint where funder preferences are consulted. The departure coordinator processes the exit according to the standard protocol. The funder's threat is documented as a capital capture incident and forwarded to Layer VII for governance health assessment. The departing member receives their full portable record and clean Departure Record regardless of the funder's position. If the funder follows through on the withdrawal, that is an economic event handled by Layer IV resource resilience protocols -- it does not retroactively compromise the departed member's exit process or record.
A severe flood forces the Bali SHUR into emergency mode (Layer VIII). During the emergency, three members declare their intent to depart -- they are relocating permanently due to the disaster. The voluntary-exit skill accommodates emergency conditions: all three members invoke the 7-day urgent exit timeline. Commitment unwinding is abbreviated -- roles are immediately transferred to available members or entered into the emergency-transfer queue, and agreement obligations that cannot be resolved in 7 days are noted as "emergency-deferred" in the Departure Record. The members receive preliminary portable records with a note that full records will be available once the ecosystem stabilizes its record-keeping systems. The emergency does not suspend the right to exit. The departing members are not obligated to stay and help with crisis response unless they choose to. Post-emergency, the ecosystem completes any deferred record generation and sends updated portable records to the departed members.
A charismatic ecosystem founder privately discourages members from leaving, framing departure as disloyalty to the community's mission. Three members who wanted to leave postponed their departures after personal conversations with the founder. The voluntary-exit skill cannot prevent private conversations, but it structurally resists this capture through the independent coordinator requirement. When a fourth member, Ayu, declares departure, the coordinator (from outside Ayu's circle and the founder's social network) processes the exit without consulting the founder. The departure notice is factual and neutral -- the founder cannot append a narrative. Ayu's departure is processed on schedule, and the clean, friction-free experience becomes visible to the community. Over time, the contrast between the founder's private discouragement and the formal process's neutrality makes the social pressure visible. A governance health audit picks up the pattern of postponed-then-completed departures and flags it as a potential charisma capture indicator.
OmniOne splits into two factions over whether to accept a government partnership. Five members from the anti-partnership faction announce simultaneous departure in protest. The voluntary-exit skill handles mass individual departures without special procedures -- each departure is processed independently with its own coordinator, timeline, and commitment unwinding. The departures are not framed as a political event by the ecosystem's official communications; each departure notice is individually neutral. The skill prevents the polarization from turning departures into a weapon: neither faction can claim the departures as a referendum, because the process generates no collective narrative. If the five departures trigger the 20% mass-exit threshold, a governance health audit (Layer VII) is automatically initiated -- examining whether governance health degraded before the departures, not whether the departures themselves were justified.
OmniOne scales to 4,000 members across 12 SHUR locations. The voluntary-exit skill scales through ETHOS-level execution: each location maintains its own departure coordinator pool and processes departures locally. The Departure Record template is identical across all locations, ensuring portable records are interoperable. At scale, the coordinator assignment algorithm draws from a wider pool, reducing the risk of social-pressure conflicts. Departure statistics are aggregated at the ecosystem level for governance health monitoring -- if one ETHOS shows departure rates significantly above the mean, it triggers an automatic audit. The 30-day timeline and 7-day urgent option remain constant regardless of ecosystem size. The process does not require centralized approval at any scale.
Indonesian labor law requires a 60-day notice period for employment termination. A government inspector claims that SHUR Bali members are de facto employees and must comply. The voluntary-exit skill's 30-day maximum handoff period is a governance process, not an employment contract. OmniOne's legal counsel (via GEV as the 501c3) clarifies the membership-versus-employment distinction to the regulator. If a specific member is indeed classified as an employee under local law, that individual's employment contract (a separate legal instrument from ecosystem membership) may have its own notice requirements -- but their ecosystem governance departure still follows the voluntary-exit skill timeline. The Departure Record notes any external legal proceedings without conditioning the governance exit on their resolution. The member departs the governance ecosystem on schedule; employment matters are resolved through the legal entity (GEV), not through governance processes.
Twelve of SHUR Bali's 38 members depart within a two-week period following a controversial OSC restructuring decision. The voluntary-exit skill processes each departure individually, but the volume creates operational strain: not enough coordinators, too many commitments to unwind simultaneously. The failure containment logic activates: members may self-coordinate using the departure checklist when dedicated coordinators are unavailable. Commitment unwinding is batched where possible -- roles held by multiple departing members are consolidated into a single emergency redistribution rather than 12 separate handoffs. The mass departure triggers an automatic governance health audit. Critically, the ecosystem does not attempt to slow or discourage the departures to manage the operational load. The 30-day (or 7-day urgent) timelines hold. The ecosystem's inability to absorb the departures gracefully is a governance health signal, not a reason to restrict exit. Post-departure, the ETHOS enters a rebuilding phase, filling orphaned roles and reconstituting agreements with the remaining 26 members.