emergencelisted

# Emergence ## Overview **Emergence**: many interacting parts produce whole-level properties that cannot be predicted from the parts alone. Wetness, consciousness, market dynamics — none exist at the part level; they emerge from interaction at scale. Philip W. Anderson (Nobel 1977) formalized this in "More Is Different" (1972): reducing things to fundamental laws does not give you the ability to reconstruct the whole. Composes with [`cynefin`](../cynefin/SKILL.md), [`feedback-loops`](../feedback-loops/SKILL.md), [`network-effects`](../network-effects/SKILL.md), [`tipping-point`](../tipping-point/SKILL.md), [`first-principles`](../first-principles/SKILL.md). ## When to Use - Strategy in markets, cultures, ecosystems; platform / community / open-source design - Diagnosing why a previously-working approach fails at scale - Cultural change; codebase architecture at scale **Not when:** the system is simple or complicated with knowable causal structure. ## Coaching Novices (Adaptive Front Door) - **Engine mode:** concrete case → run The Process directly. - **Coach mode:** new to framework → guide step by step. In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop. 1. One-line: many interacting parts + no central control = emergent whole. Design seed conditions; observe; adjust. Don't predict and control. 2. Check fit: mechanical system (few parts, knowable causation)? Emergence doesn't apply. 3. Elicit: what's