Code Archeology

This document captures historical design decisions, known technical debt, and missing pieces discovered during maintenance.

How To Use

• Historical decisions: Note when and why a design choice was made.
• Known technical debt: Record intentional compromises with rationale and impact.
• Missing pieces: List incomplete modules, undocumented interfaces, or required migration tasks.

A “gap” referenced in workflow instructions means one of the items in the Missing pieces section that blocks spec-first implementation without additional decisions or spec updates.