Layer 6 · Evolution

Learning Log

  • Layer: 6 — Evolution & Adaptation
  • Status: Active — 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

An entry MUST be added when any of the following occur:

  • A governance decision is reversed, rolled back, or found to contradict another adopted rule
  • An experiment concludes (success, failure, or early termination)
  • A conflict escalates to Step 5 (Governance decision) of the Conflict Resolution Ladder
  • A structural or systemic failure is identified that caused harm, confusion, or repeated process breakdown
  • A major adaptation to community operations is adopted that significantly changes how a layer functions
  • A near-miss: a situation that could have caused significant harm but was caught before it did
  • Any event the community collectively identifies as worth learning from

Minor operational adjustments, routine decisions, and individual member issues that are fully resolved at Step 1–3 of the Conflict Resolution Ladder do not require a Learning Log entry.

Ownership: The Blueprint Steward is responsible for ensuring entries are created and maintained. Any Full Member may draft an entry and submit it to the Blueprint Steward for review and publication.

Synthesis cadence: The Learning Log is reviewed quarterly at the Reflection & Learning meeting. The Blueprint Steward prepares a brief synthesis of entries added since the last review, noting any recurring patterns that may require structural attention.


No entries yet. First entry will be added when the first learnable event occurs.


Entry Format

## <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">

← Back to Evolution