**RCOS — Regenerative Community Operating System**

# Role Registry

- **Generated:** 2026-04-29
- **Source (latest version):** [https://blueprint.ecohubs.community/articles/rcos-templates/layer-5/role-registry](https://blueprint.ecohubs.community/articles/rcos-templates/layer-5/role-registry)
- **All RCOS templates:** [https://blueprint.ecohubs.community/articles/rcos-templates](https://blueprint.ecohubs.community/articles/rcos-templates)

---
- **Layer:** 5 — Operations & Coordination
- **Status:** Template — adapt for your community
- **RCOS reference:** [§7.1](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-5-operations-coordination#71-roles-and-responsibilities), [§7.6](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-5-operations-coordination#76-artifacts)

---

## Overview

*RCOS clauses: [7.1.1](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-5-operations-coordination#71-roles-and-responsibilities), [7.1.2](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-5-operations-coordination#71-roles-and-responsibilities), [7.1.4](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-5-operations-coordination#71-roles-and-responsibilities), [7.7.1](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-5-operations-coordination#77-layer-invariants)*

<details data-kind="rationale">
<summary>Why require every responsibility to have a named role?</summary>

Ongoing responsibilities without explicit roles become invisible labor — done by whoever notices, resented silently, and impossible to hand over. Making every ongoing responsibility a named, accountable role is what prevents the community from running on the unpaid goodwill of a few members.

</details>

<details data-kind="instructions">
<summary>How to fill this in</summary>

Distinguish operational roles (carrying delegated authority per the Decision Matrix) from functional roles (contribution-scoped, no special governance authority). State the "in good standing" definition you will use for eligibility.

</details>

This registry defines all recognized roles within the community. Roles are either **operational** (carrying delegated authority per the Decision Matrix) or **functional** (contribution-scoped, no special governance authority beyond Full Member rights).

> **"In good standing"** means a Full Member who has met their participation expectations in the last _<period>_ and is not currently subject to an active accountability process or conflict review under Layer 4.

---

## Summary Table

| Role | Type | Current Holder |
|---|---|---|
| _<Role name>_ | _<Operational / Functional>_ | _<holder or "Vacant">_ |
| _<...>_ | _<...>_ | _<...>_ |

---

## Operational Roles

*RCOS clauses: [7.1.2](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-5-operations-coordination#71-roles-and-responsibilities), [7.1.3](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-5-operations-coordination#71-roles-and-responsibilities)*

<details data-kind="rationale">
<summary>Why define accountability for delegated authority?</summary>

Operational roles carry real power — they can act without a community vote within their scope. That power only stays safe if each role has a clear accountability mechanism: who can raise concerns, how review happens, and how a role can be reassigned when trust breaks.

</details>

<details data-kind="instructions">
<summary>How to fill this in</summary>

For each operational role, fill in the template below with concrete scope, decision authority, interfaces, eligibility, term, appointment, review/removal, and handover requirements.

</details>

Operational roles carry delegated authority to act within explicitly defined limits without a Full Member vote, as defined in the Decision Matrix (Layer 2). All operational role holders are accountable to Full Members collectively. Any Full Member may raise a concern about how a role is being performed; reassignment requires a Strategic vote.

---

### _<Operational Role Name, e.g. Membership Admin>_

- **Purpose:** _<one-sentence purpose.>_
- **Scope of responsibility:** _<concrete responsibilities.>_
- **Decision authority:** _<which decisions in the Decision Matrix this role executes; explicit limits.>_
- **Interfaces:** _<other roles this role hands off to or receives from.>_
- **Eligibility criteria:** _<Full Member in good standing; any additional criteria.>_
- **Term / rotation:** _<ongoing / rotating / fixed term.>_
- **Appointment process:** _<how the role is assigned.>_
- **Review and removal:** _<how concerns are raised; reassignment via Strategic vote.>_
- **Handover:** _<what must be transferred before vacating.>_

---

### _<Operational Role Name, e.g. Finance Steward>_

- **Purpose:** _<purpose.>_
- **Scope of responsibility:** _<responsibilities.>_
- **Decision authority:** _<Decision Matrix scope; spending limit.>_
- **Interfaces:** _<other roles.>_
- **Eligibility criteria:** _<Full Member in good standing.>_
- **Term / rotation:** _<...>_
- **Appointment process:** _<...>_
- **Review and removal:** _<...>_
- **Handover:** _<...>_

---

### _<Add additional operational roles as needed (e.g. Infrastructure Steward, Communications Steward).>_

---

## Functional Roles

*RCOS clauses: [7.1.1](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-5-operations-coordination#71-roles-and-responsibilities), [7.1.2](https://blueprint.ecohubs.community/articles/rcos-core/v0-1/layer-5-operations-coordination#71-roles-and-responsibilities)*

<details data-kind="rationale">
<summary>Why separate functional from operational roles?</summary>

Not every contribution needs delegated authority — most work is about doing, not deciding. Functional roles name contribution scopes without bundling in governance power, so members can opt into work without an authority transfer, and so the governance system stays clear about who can act on behalf of the community.

</details>

<details data-kind="instructions">
<summary>How to fill this in</summary>

For each functional role, define purpose, scope, interfaces, eligibility, and handover. Functional roles do not require a vote to assume — declaration is sufficient.

</details>

Functional roles define a member's contribution scope. They carry no delegated governance authority beyond Full Member rights. Any Full Member may take on a functional role by declaring it; no vote is required. Roles may be vacated at any time by notification.

---

### _<Functional Role Name, e.g. Facilitator>_

- **Purpose:** _<purpose.>_
- **Scope of responsibility:** _<responsibilities.>_
- **Decision authority:** _<Full Member rights only.>_
- **Interfaces:** _<other roles.>_
- **Eligibility criteria:** _<Full Member; any additional preferences.>_
- **Term / rotation:** _<ongoing until vacated.>_
- **Appointment process:** _<self-declaration.>_
- **Review and removal:** _<may be vacated at any time; conflict-of-interest substitution per Layer 4 if relevant.>_
- **Handover:** _<active commitments to brief in.>_

---

### _<Add additional functional roles as needed.>_

---

## Ratification Record

- **Adopted:** <YYYY-MM-DD>
- **Decision type:** Strategic
- **Version:** <version>
- **Decision record:** <link to decision record>