Validation decides whether a candidate lesson may influence a later task, and under what conditions. Storing a trace or lesson does not grant it authority. section 4.1 section 7.5.1
Treat lesson admission as an evidence progression:
- Keep the raw execution, outcome, tool evidence, and environment version auditable as L0. section 7.5.1
- Compress a trace into an L1 candidate lesson with provenance; use it only for investigation or a closely bounded retry. section 7.5.1
- Admit an L2 replayable heuristic only with repeated independent support or a clear causal mechanism backed by external evidence; scope it to matching conditions. section 7.5.1
Preserve the conditions behind conflicting experiences instead of forcing a global winner. A replayable lesson can inform planning, diagnosis, or checks, but does not authorize tool calls or policy changes. section 7.5.1
Validate at the observable seam
In code repair, check whether a diagnosis still refers to the current revision before downstream steps rely on it; waiting until pull-request review can waste effort on stale state. section 6.2.4











































