Layer 5 · Operations
2 Role Registry
- Layer: 5 — Operations & Coordination
- Status: Stub — not yet adopted
- RCOS reference: §7.1, §7.6
Overview
RCOS definition7.1.1, 7.1.2, 7.1.4, 7.7.1
- 7.1.1 All ongoing responsibilities MUST be assigned to explicit, named roles rather than implicit expectations or informal agreements.
- 7.1.2 The community MUST maintain a **Role Registry** that includes, at minimum:
- 7.1.4 No ongoing responsibility MAY exist without an explicit role, and no person MAY be held accountable for responsibilities not formally assigned to a role.
- 7.7.1 Ongoing responsibilities MUST NOT exist without an explicit role.
Why require every responsibility to have a named role?
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.
<This registry defines all recognized roles. Every role has a defined purpose, authority, limit, and term length.>
“In good standing” means a Full Member who has met their participation expectations in the last 6 months and is not currently subject to an active accountability process or conflict review under Layer 4.
Defined Roles
| Role | Purpose | Authority | Limits | Term Length (min/max) | Selection method |
|---|---|---|---|---|---|
Ratification Record
- Adopted:
- Decision type: Strategic
- Version:
- Decision record: