Implementation Notes Are Product Evidence

A practical insight should show a decision under constraint: why a route was narrowed, why a test was insufficient, or why a local boundary was preserved. That is more useful than a retrospective that only celebrates the outcome.

Treat the archive as a filtered view of the development log. Remove secrets and incidental noise, keep the decision and evidence, and label future plans as proposals rather than current behavior.

Over time, this gives prospective users a way to evaluate working method—not just a list of finished features.