codify

# Codify ## Step 1 — Read the inbox Read `LEARNINGS.md` at the project root. Candidates are entries without a `Codified →` marker. If there are none, report that and stop. If the file doesn't follow the standard `## YYYY-MM-DD — Title` entry format (e.g. a numbered takeaways list), treat each discernible item as an entry and place markers where they unambiguously attach to the item. ## Step 2 — Cluster Group candidate entries that share a root cause or a target file. A pattern across several entries is stronger evidence than any single entry — codify the pattern, not each instance. ## Step 3 — Find the structural fix The entry recorded the symptom and (usually) the likely cause at capture time. Now do the analysis the capture deliberately skipped: ask why the system allowed the failure, and what change prevents recurrence. Test every proposed fix: **would it have prevented the original incident even if nobody remembered the learning?** "Be more careful" or "remember to X" fails this test — put the knowledge where the future reader will already be looking (the skill they will load, the rule that is always in context, the template they will copy). Prefer the smallest change that passes. Some entries need no fix: a durable technical fact (version pin, API quirk) with no better home is already serving its purpose where it is. Others are not ready — a single incident with an unclear cause stays in the inbox until the pattern repeats. ## Step 4 — Choose the target | Learn...