Evergreen Mental Model & Concept Definition

Template Overview

High-velocity thinkers do not memorize isolated facts; they build an interconnected lattice of foundational mental models. By understanding durable principles from physics, biology, computer science, and microeconomics, practitioners can evaluate novel situations rapidly.

A mediocre concept note merely copies an encyclopedic definition without explaining how the mental model functions in practice. A high-leverage mental model entry details the core principle, intuitive analogies, concrete real-world manifestations, failure boundaries, and anti-patterns.

This template standardizes mental model definitions: formal formulation, accessible metaphor, multi-disciplinary applications, edge cases where the model breaks down, and cross-vault wikilinks.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Concept: [Mental Model / Principle Name]"
date: [YYYY-MM-DD]
type: "concept-definition"
discipline_origin: "[Physics / Computer Science / Economics / Psychology]"
status: "Evergreen"
aliases: ["[Alternative Name 1]", "[Alternative Name 2]"]
tags: [pkm, mental-models, decision-making, systems-thinking, concepts]
---

# Concept: [Mental Model / Principle Name]

## 1. Formal Definition & The Core Principle
- **Formal Definition:** A rigorous 2-sentence explanation of the mechanism.
- **The Core Invariant:** In simple terms, what fundamental constraint does this concept enforce?
- **Mathematical / Formal Representation (If Applicable):**
  $$f(x) \propto \frac{1}{x^\alpha}$$

## 2. Intuitive Metaphor & Plain-English Analogy
*An accessible analogy that makes the abstract principle intuitively memorable.*

[Insert vivid analogy here...]

## 3. Multi-Disciplinary Applications & Manifestations
### In Software & Systems Architecture
- How does this principle govern distributed systems, memory management, or API design?

### In Human Organizations & Strategy
- How does this principle dictate team structures, incentives, or business competition?

### In Personal Decision-Making
- How should an individual adjust their behavior or investments in light of this reality?

## 4. Boundaries of Applicability & Failure Modes
- **Where the Model Fails:** What conditions render this mental model misleading or false?
- **The Seductive Anti-Pattern:** How do novice thinkers misapply or overextend this concept?
- **Countervailing Principle:** What opposing mental model balances this one?

## 5. Bidirectional Vault Connections
- **Higher-Order MOC:** [[Mental-Models-Lattice-MOC]]
- **Reinforcing Concepts:**
  - [[Related-Principle-A]]
  - [[Related-Principle-B]]
- **Dialectical Counter-Weights:**
  - [[Opposing-Principle-C]]

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Concept: Chesterton's Fence"
date: [YYYY-MM-DD]
type: "concept-definition"
discipline_origin: "Political Philosophy & Systems Thinking"
status: "Evergreen"
aliases: ["The Law of Unintended Consequences", "Reform Precondition Rule"]
tags: [pkm, mental-models, decision-making, systems-thinking, concepts]
---

# Concept: Chesterton's Fence

## 1. Formal Definition & The Core Principle
- **Formal Definition:** The principle that reforms, deletions, or structural modifications should never be enacted until the reformer fully understands the original reasoning behind the existing state of affairs.
- **The Core Invariant:** Systems that survive over long evolutionary periods usually possess hidden adaptive functions that are not immediately legible to outside observers.

## 2. Intuitive Metaphor & Plain-English Analogy
In his 1929 book *The Thing*, G.K. Chesterton described a traveler encountering a fence erected across a country road:

> The more modern type of reformer goes cheerfully up to it and says, "I don't see the use of this; let us clear it away." To which the more intelligent type of reformer will do well to answer: "If you don't see the use of it, I certainly won't let you clear it away. Go away and think. Then, when you can come back and tell me that you do see the use of it, I may allow you to destroy it."

## 3. Multi-Disciplinary Applications & Manifestations
### In Software & Systems Architecture
- **Legacy Code Removal:** Before deleting an apparently redundant `sleep(50)` call or arcane validation check in a legacy codebase, an engineer must investigate why it was added. It often guards against an undocumented race condition in hardware drivers.
- **Refactoring Invariant:** Never refactor a module whose test suite you have not yet written and understood.

### In Human Organizations & Strategy
- **Corporate Bureaucracy:** Annoying approval gates often exist because a catastrophic compliance or financial disaster occurred five years ago. Removing the gate without addressing the underlying vulnerability invites history to repeat itself.

### In Personal Decision-Making
- **Habit Disruption:** Before attempting to eliminate an ingrained negative coping habit (e.g., late-night snacking), understand what emotional relief or stress buffering it currently provides.

## 4. Boundaries of Applicability & Failure Modes
- **Where the Model Fails:** In rapidly shifting environments where the underlying constraints have fundamentally changed (e.g., an architectural workaround for a floppy disk bottleneck on a 100Gbps NVMe cluster).
- **The Seductive Anti-Pattern:** Weaponizing Chesterton's Fence to justify perpetual institutional paralysis and resist necessary innovation.
- **Countervailing Principle:** [[First-Principles-Thinking]] — Deconstructing a problem to fundamental physics truths rather than deferring to historical convention.

## 5. Bidirectional Vault Connections
- **Higher-Order MOC:** [[Decision-Making-Mental-Models-MOC]]
- **Reinforcing Concepts:**
  - [[Conways-Law-Organizational-Mirroring]]
  - [[Second-Order-Thinking-Long-Term-Effects]]
- **Dialectical Counter-Weights:**
  - [[First-Principles-Thinking]]

When to Use and When to Avoid

When to Use

• Building an evergreen library of cross-disciplinary mental models and thinking heuristics.
• Deconstructing complex systems-thinking principles from physics, software, and economics.
• Creating shared reference definitions for engineering and executive leadership teams.
• Connecting abstract theory to concrete operational decision-making.

When to Avoid

• Logging ephemeral daily to-do tasks or grocery shopping checklists.
• Recording unrefined personal emotional diary entries.
• Writing transient software release notes or patch announcements.
• Documenting customer support tickets.

On-Device AI Integration

Document evergreen mental models with Oyma on macOS:

Analyze the concept or mental model:
1. Synthesize a formal definition and clarify the core systemic invariant.
2. Provide a vivid, memorable analogy or historical parable illustrating the principle.
3. Detail concrete manifestations across software engineering, organizations, and decision-making.
4. Establish clear boundaries of applicability, anti-patterns, and countervailing principles.
Output in structured, evergreen CommonMark.

Your private mental models and thinking frameworks stay completely local on your Mac.