Layer 1 · Membership
Exit & Separation Protocol
- Layer: 1 — Membership System
- Status: Stub — not yet adopted
- RCOS reference: §3.6, §3.7, §3.8
Voluntary Exit
Voluntary exit must be possible at all times. Procedures must be explicit, documented, and non-punitive.
- Any Full Member or Trial Member may exit at any time by submitting a request through ecohubsOS (reason optional)
- No notice period required; if the member holds a role, they are asked to consider a handover where appropriate
- Access is revoked within 24 hours of admin confirmation
- Contribution history and XP are retained permanently
- Membership state transitions to Exited Member
- Exit is recorded in ecohubsOS with a timestamp
Forced Exit
Must follow due process via Layer 4 mechanisms. Must not result in loss of rights beyond those explicitly tied to membership.
- Forced exit may only result from a concluded Layer 4 accountability process with a documented decision
- The affected member must be notified in writing with the reason and decision record reference before access is revoked
- Access is revoked within 24 hours of the decision being finalised
- Accounts on platforms related to ecohubsOS (Discord, Snapshot, Notion, Puckstack, etc.) may be deleted or blocked depending on the severity of the decision and platform capabilities
- Contribution history and XP are retained
- Membership state transitions to Exited Member
- The member may not reapply for a period defined in the accountability decision (minimum 6 months)
- The decision record is retained permanently; access to it is governed by the privacy rules in the Conflict Resolution Ladder
Suspension
Conditions must be explicit, time-bounded, and reviewable. Must not be used as an indefinite or punitive substitute for exit.
Formal membership suspension is not yet technically implemented. See Future Proposals for the deferred Suspended Member state design.
Asset, Role, and Responsibility Separation
Must be defined prior to exit. Covers: access revocation, role handover, resource return, obligation settlement.
The following separation steps apply to both voluntary and forced exits:
- Any roles held must be vacated and documented in the Role Registry
- Ongoing tasks claimed in Puckstack must be released or handed over
- Safe wallet co-signer or Proposer status must be removed
- All administrative access to platforms (ecohubsOS, Discord, social media, Snapshot, Notion, Puckstack, etc.) must be revoked
- Outstanding obligations (incomplete tasks, financial commitments) must be resolved or transferred before exit is finalised where possible
Ratification Record
- Adopted:
- Decision type: Strategic
- Version:
- Decision record: