Membership State Registry

Download this template

Generated 2026-04-29 · Download all templates

  • Layer: 1 — Membership System
  • Status: Template — adapt for your community
  • RCOS reference: §3.1, §3.8

Defined Membership States

RCOS clauses: 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.1.5

Why a single table of states?

Rights and obligations scattered across documents drift apart. Collecting every state, its rights, its obligations, and its transitions into one table makes the membership system auditable at a glance — you can see every door into and out of the community, and what each one grants. If two documents ever disagree, this registry is the tiebreaker.

How to fill this in

Define every membership state your community recognizes (e.g. Applicant, Trial Member, Full Member, Exited Member). For each, list rights, obligations, entry condition, and exit condition. Keep states mutually exclusive — no individual may hold two states simultaneously.

State Rights Obligations Entry condition Exit condition

No individual may hold multiple membership states simultaneously. No rights or obligations may be assumed outside of the individual’s current membership state.

Technical Notes

Why preserve data after exit?

The community’s history belongs to the community, not to any individual account. Retaining contribution records after exit protects the integrity of audit trails, governance history, and recognition accounting — while revoking access and removing the person from active listings respects the finality of their departure.

How to fill this in

Describe which records persist after exit, where state assignments are tracked operationally, and how access revocation interacts with platform capabilities.

Current Member List

RCOS clauses: 3.8.2

Why separate the definition from the list?

This document defines what the states mean; the live registry tracks who is in which state today. Keeping them separate means the definitions are stable and governable while the assignments stay current — and nobody has to change a ratified artifact every time a member joins or leaves.

How to fill this in

Link to the operational system or document where current member-to-state assignments are tracked. This artifact should not need to be changed every time a member joins or leaves.

The live member list is maintained in . This document defines the states; the registry tool holds the current assignments.


Ratification Record

  • Adopted:
  • Decision type: Strategic
  • Version:
  • Decision record:

RCOS Blueprint by EcoHubs

A modular operating system that defines how intentional communities organize — from governance and roles to resource sharing and conflict resolution — in support of resilience, fairness, and regeneration.

Connect

© 2026 EcoHubs Platform. All rights reserved.