Lesson Ledger
The lesson ledger preserves lessons that should influence future implementation and review.
Summary
Section titled “Summary”Lessons are reusable when they name a failure pattern, an evidence source, and a future behavior change.
Why This Matters
Section titled “Why This Matters”Repeated mistakes are expensive. Lessons make review memory visible before future tasks start.
Evidence Sources
Section titled “Evidence Sources”- Generated lessons
- Review summaries
- Source task history
- Harness docs
What Happened
Section titled “What Happened”Phase 1 exposed lessons around CRLF-sensitive tests, generated-summary self-reference, PII sentinel behavior, explicit harness contracts, and agent coordination.
Decision / Lesson / Pattern
Section titled “Decision / Lesson / Pattern”Lessons should be promoted from observation to accepted rule only when they are backed by task or review evidence.
What To Preserve
Section titled “What To Preserve”- Repeated failure patterns
- Testing lessons
- Code review lessons
- Agent coordination lessons
- Safe source and export boundaries
What To Recheck
Section titled “What To Recheck”- Whether a lesson is still relevant after Phase 2 architecture changes
- Whether future tests cover the failure mode
- Whether a lesson should become a standard harness rule
Carry Forward
Section titled “Carry Forward”Use docs/history-templates/lesson-record.template.md for individual lesson records.