TB: Chesterton's Fence

Do not remove a fence until you understand why it was built. Before eliminating a rule, institution, or practice that seems pointless, first understand what problem it was solving. If you can't explain why it exists, you don't yet know enough to safely remove it.

Many conventions and rules exist because someone in the past encountered a problem that is now invisible. Reformers who ignore this destroy load-bearing structures while thinking they are clearing clutter. The principle applies to: code (don't delete "dead" code you don't understand), institutions (constitutional provisions that seem archaic), social norms (taboos around certain behaviors), and engineering safeguards. The bias toward action and "disruption" systematically underweights Chesterton's Fence — the status quo often encodes hard-won lessons that are no longer visible as lessons.

• No reading examples yet — will populate as books are ingested.

• Inversion — "why would someone have built this fence?" is the inversion of "should I remove it?"
• Second-Order Thinking — what will happen when the fence is gone?
• Goodhart's Law — paired concern: understanding why a rule exists before gaming or removing it