Accountability Protocol

Download this template

Generated 2026-04-29 · Download all templates

  • Layer: 4 — Conflict, Repair & Accountability
  • Status: Template — adapt for your community
  • RCOS reference: §6.4, §6.5

Triggers

RCOS clauses: 6.4.1, 6.5.4

Why enumerate what starts an accountability check?

If accountability checks only happen when someone feels strongly enough to push, they become political. Naming the exact triggers — inactivity, breach, invariant violation, referral — means the process starts from a condition anyone can verify, not from a judgement about a person.

How to fill this in

List the specific, verifiable triggers that initiate an accountability check. Each trigger should be observable from records or a direct referral.

An accountability check is initiated when:

Investigation and Review

RCOS clauses: [6.4.2](/articles/rcos-core/v0-1/layer-4-conflict-repair-accountability#64-sanctions-repair-and-separation), [6.4.3](/articles/rcos-core/v0-1/layer-4-conflict-repair-accountability#64-sanctions-repair-and-separation), [6.4.6](/articles/rcos-core/v0-1/layer-4-conflict-repair-accountability#64-sanctions-repair-and-separation), [6.5.4](/articles/rcos-core/v0-1/layer-4-conflict-repair-accountability#65-artifacts)

Why graduate the response by severity?

Treating a missed contribution the same as an invariant violation either crushes minor cases with heavy process or lets serious ones slip through a private chat. Graduated pathways — soft check-in, medium written notice, direct escalation for serious breaches — match response weight to breach weight and keep repair the default where repair is still possible.

How to fill this in

Define soft (inactivity), medium (obligation breach), and serious (invariant violation, safety) pathways. State who initiates, the response window, and the escalation route for each.

Breach severity guidance:

  • Inactivity (soft breach):
  • Obligation breach (medium):
  • Serious breach / invariant violation:

Due Process Guarantees

RCOS clauses: [6.4.2](/articles/rcos-core/v0-1/layer-4-conflict-repair-accountability#64-sanctions-repair-and-separation), [6.4.4](/articles/rcos-core/v0-1/layer-4-conflict-repair-accountability#64-sanctions-repair-and-separation), [6.5.4](/articles/rcos-core/v0-1/layer-4-conflict-repair-accountability#65-artifacts)

Why spell out notice, response, and appeal rights?

Accountability without due process is just punishment with paperwork. A member facing a sanction needs to know the concern, have real time to respond, and have somewhere to appeal to — otherwise the deciding body’s word is final by default, which concentrates power exactly where it should not concentrate.

How to fill this in

State the right to written notice, a minimum response window, and an explicit appeal path to Full Members.

  • Right to notice:
  • Right to respond:
  • Right to appeal:

Anti-Retaliation Protections

RCOS clauses: [6.3.2](/articles/rcos-core/v0-1/layer-4-conflict-repair-accountability#63-safeguards)

Why protect participants explicitly?

If raising a concern or giving information can cost a member standing, relationships, or access, people will stay silent and the accountability system collapses in practice. Naming retaliation as itself a trigger makes the cost of suppression higher than the cost of reporting.

How to fill this in

State that retaliation against any member who raises, participates in, or gives information to an accountability process is itself an accountability trigger.

Sanction and Repair Options

RCOS clauses: [6.4.1](/articles/rcos-core/v0-1/layer-4-conflict-repair-accountability#64-sanctions-repair-and-separation), [6.4.2](/articles/rcos-core/v0-1/layer-4-conflict-repair-accountability#64-sanctions-repair-and-separation), [6.4.3](/articles/rcos-core/v0-1/layer-4-conflict-repair-accountability#64-sanctions-repair-and-separation), [6.4.5](/articles/rcos-core/v0-1/layer-4-conflict-repair-accountability#64-sanctions-repair-and-separation), [6.4.6](/articles/rcos-core/v0-1/layer-4-conflict-repair-accountability#64-sanctions-repair-and-separation), [6.5.4](/articles/rcos-core/v0-1/layer-4-conflict-repair-accountability#65-artifacts)

Why pre-define the menu of sanctions?

Ad-hoc sanctions invented mid-process reflect whoever is loudest in the room, not what the breach warrants. A fixed menu — with preconditions, authorized body, and appeal path for each — keeps responses proportional, prevents informal exclusion from becoming the default punishment, and makes it obvious when a sanction is out of scope for the body applying it.

How to fill this in

For each sanction type, define preconditions, authorized body, and appeal path. Repair-oriented responses should be the default; punitive ones reserved for safety-critical or unresolved breaches.

Repair-oriented responses are preferred over punitive ones except in safety-critical cases. Sanctions must be proportional, time-bounded where applicable, documented, and never applied through informal exclusion or social pressure.

Type Preconditions Authorized body Appealable?

Conditions for Restoring Rights

RCOS clauses: [6.4.4](/articles/rcos-core/v0-1/layer-4-conflict-repair-accountability#64-sanctions-repair-and-separation)

Why make restoration conditions explicit?

If there is no defined path back, every sanction becomes effectively permanent and every exit becomes a life sentence. Explicit restoration conditions signal that accountability is about repair where repair is possible, and they prevent post-hoc gatekeeping about whether someone is “really” welcome back.

How to fill this in

For each sanction class, state the path to restoration of rights — re-application after voluntary exit, re-application block after forced exit, restoration after temporary restriction.

  • After voluntary exit:
  • After forced exit:
  • After temporary access restriction:

Coordination with Layer 1

RCOS clauses: [6.4.4](/articles/rcos-core/v0-1/layer-4-conflict-repair-accountability#64-sanctions-repair-and-separation)

Why tie this to the Exit & Separation Protocol?

Exit rules live in Layer 1 for a reason — they govern who is and is not a member. If accountability actions created their own parallel exit path, there would be two sets of rules, two sets of records, and a loophole for skipping due process. One canonical exit protocol closes that gap.

How to fill this in

State that all forced exits and temporary access restrictions follow the Exit & Separation Protocol (Layer 1), and clarify that a temporary restriction does not constitute exit.


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.