Question
Why do commits, reviews, incidents, documents, tests, and session traces so often preserve what happened without making the useful lesson easier to find, verify, and apply next time?
Working Direction
Experience does not compound when its lesson remains in a record that has no clear owner, boundary, revision path, or next-use context. The artifact survives, but the next actor has to reconstruct the reasoning from scratch or trust an unverified summary.
Early Test
When a later actor returns to the work, can they locate the current owner, check the source within their available environment, and return a repair when the lesson no longer applies? If not, the experience may be preserved but has not yet become reusable engineering memory.