Layer 4 · Conflict
Accountability Protocol
- Layer: 4 — Conflict, Repair & Accountability
- Status: Stub — not yet adopted
- RCOS reference: §6.4, §6.5
Triggers
An accountability check is initiated when:
- A member has not made a recognized contribution in six consecutive months (per the Membership Agreement)
- A member has breached a Membership Agreement obligation
- A member has violated a Layer 0 identity constraint or invariant
- A referral is made from the Conflict Resolution Ladder (Step 3 or above)
Investigation and Review
Breach severity guidance: A breach is medium if it involves non-compliance with a Membership Agreement obligation (e.g. participation expectations, notification requirements, or process obligations) without threatening member safety or community integrity. A breach is serious if it involves a Layer 0 invariant violation, a credible safety concern, persistent bad-faith conduct, or any action that fundamentally undermines the governance system.
- Inactivity (soft breach): Membership Admin contacts the member privately. The member has 30 days to respond. If no response: exit is triggered per the Exit & Separation Protocol. If the member responds and commits to re-engagement: outcome documented and monitored for 3 months.
- Obligation breach (medium): Membership Admin contacts the member privately with a written notice of the concern. Member has 30 days to respond and address the breach. If resolved privately: written record kept by Membership Admin. If unresolved: escalated to Conflict Resolution Ladder Step 3.
- Serious breach / invariant violation: Membership Admin may escalate directly to Conflict Resolution Ladder Step 4 or 5, bypassing the private check-in.
Due Process Guarantees
- Right to notice: The member is notified in writing of the concern before any review or sanction begins
- Right to respond: Minimum 30 days to respond to any accountability check
- Right to appeal: Any Membership Admin decision may be appealed to Full Members via the governance process (Strategic vote)
Anti-Retaliation Protections
Any member who raises an accountability concern, participates in a review, or provides information in good faith is protected from retaliation. Retaliation against a member for participating in any part of this process is itself an accountability trigger.
Sanction and Repair Options
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? |
|---|---|---|---|
| Private check-in / reminder | Inactivity or minor breach | Membership Admin | Yes — to Full Members |
| Written warning | Unresolved obligation breach after check-in | Membership Admin | Yes — to Full Members |
| Temporary access restriction | Safety-critical situation only; must be reviewed within 14 days | Membership Admin | Yes — to Full Members |
| Forced exit | Serious or unresolved breach, or Full Member decision | Full Members (Strategic vote) | Yes — via re-vote mechanism |
Conditions for Restoring Rights
- After voluntary exit: re-application per Onboarding Protocol; no automatic rights restoration
- After forced exit: minimum 6-month re-application block; re-application subject to standard admission process
- After temporary access restriction: rights restored upon Membership Admin confirmation of resolution (within 14 days of restriction being imposed)
Coordination with Layer 1
All forced exits and temporary access restrictions must follow the Exit & Separation Protocol (Layer 1). A temporary access restriction does not constitute exit and does not trigger the 6-month re-application block unless a forced exit is subsequently voted by Full Members.
Ratification Record
- Adopted:
- Decision type: Strategic
- Version:
- Decision record: