Institutional Amnesia

Severity: Medium — never urgent, always compounding: the community pays full price for every lesson, repeatedly. Where it bites: Growth and mature stages, and hardest whenever a long-timer leaves. Already living this? Jump to If it’s already happening.

Sound familiar?

This conflict feels familiar — because the community had almost exactly the same one three years ago, and handled it, and learned something, and then forgot. The project that just failed failed the same way the last one did. New members hit the same walls the founders hit and solved long ago. Nobody wrote any of it down, so the only memory the community has lives in the heads of a few long-timers — and every time one of them leaves, a chunk of hard-won knowledge walks out with them.

Signs this is happening to you

The same conflicts, failed projects, or onboarding problems keep recurring.
Why past decisions were made is lost; no one can reconstruct the reasoning.
Institutional memory lives in a few long-timers’ heads — and leaves when they do.
New members repeat mistakes the community already made years ago.
There’s no log of decisions, experiments, or lessons learned.

This is not the same as choosing not to document trivial things. The tell is that significant decisions, conflicts, and experiments leave no retrievable record — so the community can’t learn from its own history, only relive it.

Why it happens

Capturing learning is unglamorous and always feels less urgent than the next task, so it never quite happens. But a community that doesn’t record its decisions and outcomes has no memory beyond its longest-tenured members. It pays full price for every lesson again and again, and it loses its history the moment those people move on — which, eventually, they all do.

The formal stress test (for auditors)

Failure Mode — Decisions, conflicts, and experiments leave no captured learning.

Layers Involved — Layer 6 (Evolution), Layer 5 (Operations)

Relevant Invariants

6.4 Learning is captured
5.2 Operational knowledge is documented

Test Condition — Significant decisions and outcomes are not recorded, and reasoning is unrecoverable.

Expected RCOS Behavior — Learning and decisions are captured in a durable, retrievable form and consulted over time.

Pass Criteria — Past lessons are retrievable and demonstrably prevent repeats.

Fail Criteria — The community repeats its own mistakes.

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	Nothing is captured; memory is oral and lives in a few heads.
L1 — Named	The group knows it repeats mistakes but hasn’t started recording.
L2 — Documented	A Learning Log and decision records capture significant decisions, conflicts, and outcomes.
L3 — Enforced & rehearsed	Learning is routinely captured and actually consulted; a past lesson has demonstrably prevented a repeat.

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 gives the community a memory that outlives its members:

Learning Log — capture decisions, experiments, conflicts, and what was learned.
Version History — record how and why the rules changed over time.
Operations Manual — keep operational knowledge out of individual heads.

If it’s already happening

If the community keeps reliving its past, start a memory now:

Start a learning log today — even a running document beats memory.
Back-capture the big lessons the long-timers carry, before they leave.
Make a quick decision record a standard step, so reasoning stays retrievable later.

What this failure tends to trigger

Rapid Growth without Onboarding — with no captured knowledge, newcomers can’t be brought up to speed.
Invisible Power via Responsibilities — when knowledge lives only in heads, those heads become indispensable.

Irreversible Experiments — uncaptured learning is what makes experiments — reversible or not — teach nothing.