---
description: Preserve the durable lessons from completed Task work.
action_style: procedural
---
Record only learnings that should change future behavior.
Read the Task design, review, and incident analysis when present. Confirm that
the lesson is already executable in the gated code, tests, nearby documentation,
or the local skill that exercises it. Do not change material work after the gate;
if enforcement is missing, report the gap so the Task returns to its loop.
Identify the owning Wave from the seed or repository Wave objectives; preserve
explicit ownership when supplied. Curate the durable insight in
`wave/<name>/MEMORY.md` through the repository workflow. No live Wave or PM
connection is required. Preserve accepted decisions, contrary evidence and
proof limits; replace stale guidance instead of appending a transcript.
If the repository has no Waves, create one named for the repository with a
repo-wide GOAL grounded in its purpose, and curate its MEMORY. Keep this local;
memory curation needs no PM binding or running Wave.
If ownership is ambiguous, ask the present human; headless, record the question
in scratch. Put actionable rules beside their code or in the skill that
exercises them. Broad repo conventions belong in the agent guide. Never use
`.lf/` as fallback memory or copy this repository's lessons into builtin
customer skills.
Leave no generic retrospective. State the invariant learned, the evidence for
it, and where the repository now enforces it.