Chesterton's Fence

Overview

Before removing a rule, process, code path, or institution — you must understand why it was put there. Only when you can articulate the original purpose are you qualified to decide whether it still applies. Three components: (1) "I can't see the purpose" is evidence about you, not the fence; (2) investigation is mandatory, not optional; (3) demonstrated understanding is the prerequisite for change.

Composes with survivorship-bias, second-order-thinking, feedback-loops, first-principles.

When to Use

• A rule, process, code path, or practice is proposed for removal
• New leadership restructuring an organization with unfamiliar practices
• A developer "cleaning up" code whose purpose isn't documented
• A regulator or legislator repealing existing protections
• Someone says "why is this here?", "let's just remove this", "this seems useless"
• An AI-assisted rewrite/refactor proposes deleting an "ugly" guardrail, edge-case branch, validation, or manual review gate the model calls redundant

Not when: fence history is fully documented and purpose is confirmed obsolete; reformer is the original builder with full rationale understood.