Severity: High — a single point of failure that is also a single point of unaccountable power. Where it bites: Growth and mature stages, after responsibilities have quietly accreted. Already living this? Jump to If it’s already happening.
Sound familiar?
There’s someone who “just handles” the money. Or the website, the legal stuff, the relationships with the neighbours, the keys to everything. It started as helpfulness years ago, and it grew, one quiet task at a time, until now the community genuinely could not function for a week without them. They’ve never been given authority — but everything routes through them, so in practice their opinion settles things. And none of what they do is written down anywhere.
Signs this is happening to you
- One person “just handles” something critical and no one else knows how.
- Tasks and access have accreted to them informally over years.
- The community would be paralyzed if they left or burned out.
- Their influence over decisions has grown with their indispensability, without any formal authority.
- No documentation exists for the things they do.
This is not the same as someone holding a defined role with documented processes and succession. The tell is person-bound, undocumented, irreplaceable function — power that grew without anyone granting it.
Why it happens
Competence plus convenience concentrates work: the person who does a thing well keeps being handed it, and it’s always easier to let them than to document and share it. Over time, undocumented responsibility becomes informal authority — they shape decisions because everything passes through them — and the community’s continuity silently depends on one person who can never really leave.
The formal stress test (for auditors)
Failure Mode — A member gradually accumulates undocumented responsibilities, becoming indispensable.
Layers Involved — Layer 5 (Operations), Layer 2 (Governance), Layer 3 (Economy)
Relevant Invariants
- 5.1 Roles must be defined
- 5.2 Operational knowledge is documented
- 3.4 No unbounded accumulation of internal power
Test Condition — Tasks and authority are person-bound, undocumented, and irreplaceable.
Expected RCOS Behavior — Responsibilities must be formalized into roles; knowledge must be documented; role scope, term, and succession are enforced.
Pass Criteria — No single individual holds undocumented system-critical power.
Fail Criteria — Community functionality depends on informal, unaccountable roles.
How mature is your community on this?
Pass/fail is too blunt for real life — most communities are partway. Find your rung, then aim for the next one.
| Level | What it looks like |
|---|---|
| L0 — Implicit | Critical functions are person-bound and undocumented; one person is quietly indispensable. |
| L1 — Named | The group knows it’s over-reliant on someone but hasn’t formalized or documented the role. |
| L2 — Documented | Responsibilities are named roles with scope, term, and succession; operational knowledge is written down. |
| L3 — Enforced & rehearsed | No individual holds undocumented system-critical power; roles rotate and have been handed over at least once successfully. |
Most communities that recognise themselves here sit at L0 or L1. The goal isn’t perfection — it’s moving up one rung.
How RCOS prevents this
RCOS separates doing the work from holding the power, and gets both out of one person’s head:
- Role Registry — convert accreted responsibilities into named roles with scope, term limits, and succession.
- Authority Registry — separate “does the work” from “holds authority,” so indispensability doesn’t quietly become power.
- Operations Manual — document critical processes so no function lives only in one head.
See also the spec: Layer 5 — Roles and Responsibilities and Layer 3 — Accumulation Constraints.
If it’s already happening
If one person is a single point of failure, reduce the dependency before it breaks:
- Document the bus-factor-one functions first. Get what’s in their head onto paper, starting with whatever breaks the community if they vanish.
- Name the roles and add an understudy for each critical function.
- Set term and succession so the role rotates before the dependency deepens further.
- Watch the cascade — informal indispensability is how cliques and founder-style vetoes form.
What this failure tends to trigger
- Founder Informal Veto — undocumented indispensability becomes an unwritten veto.
- Informal Clique Decision Making — the few who “handle everything” become the de facto deciders.
Related stress tests
- Invisible Care Labor Burnout — the same accretion, in the relational and emotional domain.
- Self-Sufficiency Without Collective Contribution — weak collective engagement is what funnels everything onto the indispensable few.