The repo records WHAT changed; it does not record the wrong turn that cost an hour, the env quirk that breaks a fresh checkout, or the correction the owner gave you. Each iteration re-reads the session and diff asking one question — what did we learn that is not written anywhere? — and writes one durable note per lesson (the fact, why it matters, how to apply it next time), skipping anything the code or docs already record. Distinct from checkpoint-driven-execution (a during-task plan-and-evidence ledger): this runs AFTER the work and exits loop-until-dry, when two consecutive review passes surface nothing unrecorded.
Loop
- Goal
- every non-obvious lesson from the session — gotchas, environment quirks, corrections received — is captured as a durable note with why it matters and how to apply it
- Exit when
- two consecutive review passes over the session and diff surface no lesson that is not already recorded in the notes
Check between iterations