- Layer: 6 — Evolution & Adaptation
- Status: Template — adapt for your community; updated when learnable events occur
- RCOS reference: §8.4, §8.6
Records major failures, adaptations, reversals, and systemic learnings. Repeated failure patterns must trigger structural review, not individual blame. Entries are prepended (most recent first).
What Constitutes a Learnable Event
RCOS clauses: 8.4.1, 8.4.4, 8.6.5, 8.7.4
Why define the trigger explicitly?
If “we should learn from this” is left to individual judgement, the hardest lessons — the ones involving conflict, failure, or embarrassment — are the ones most likely to go unrecorded. Naming the specific events that MUST produce an entry takes the question out of the moment, and makes sure uncomfortable learnings are captured rather than quietly dropped.
How to fill this in
List the specific events that obligate a Learning Log entry. State who owns the log and the synthesis cadence.
An entry MUST be added when any of the following occur:
Ownership:
Synthesis cadence:
No entries yet. First entry will be added when the first learnable event occurs.
Entry Format
RCOS clauses: [8.4.2](/articles/rcos-core/v0-1/layer-6-evolution-adaptation#84-learning-and-feedback-capture), [8.4.3](/articles/rcos-core/v0-1/layer-6-evolution-adaptation#84-learning-and-feedback-capture), [8.6.5](/articles/rcos-core/v0-1/layer-6-evolution-adaptation#86-artifacts)
Why a fixed entry template?
Free-form reflection is valuable, but it does not aggregate. A consistent schema — trigger, signals, what changed, outcome, follow-up owner — makes it possible to scan years of entries for recurring patterns and to turn isolated incidents into structural evidence. It also forces each entry to name an owner, so learning does not stop at “we noticed.”
How to fill this in
Use the template below for every entry. Each field forces a different lens on the event; do not skip the follow-up owner.
{@html `## <YYYY-MM-DD> — <Short title>
- **Trigger:** <What happened that prompted this entry>
- **Layers/artifacts implicated:** <e.g. Layer 2 — Governance Protocol>
- **What occurred:** <Short narrative>
- **Signals that triggered action:** <What made this visible as a problem>
- **What changed or was tried:** <Decision, experiment, or rule change>
- **Outcome:** <Result after review, if known>
- **Follow-up owner and due date:** <Name / role and date, or "none">`}