Learning

Learning preserves experience; it does not create authority.

Record

Record a lesson only when it is both reusable and supported by observed evidence. Prefer lessons about failure causes, successful engineering patterns, diagnostic traps, review findings, or operational behavior that are likely to recur.

1. Keep current accepted authority and current evidence primary.
2. Write the lesson in the project's chosen durable notes or memory store. Include context, the observed mechanism, supporting evidence/provenance, applicability limits, date, and confidence. No memory service is required.
3. New heuristics are provisional unless independent support justifies stronger status.
4. Optionally index the record for recall if a search/memory integration is available. Index failure does not invalidate the source record; retain a stable path or identifier to it.
5. Never store an unconfirmed theory as established learning.
6. When recorded episodes justify a general rule, document it as a provisional heuristic. Strengthen confidence only with independent support and review appropriate to the consequence.

Recall and correction

Semantic recall is advisory. Read the original source record and check applicability and freshness before relying on remembered material.