Production History as Code Footprint Signal
The property that distinguishes a code footprint from a well-designed template is not documentation quality or design correctness. It is production history — the decisions that survived real query loads, real multi-tenant constraints, real incidents.