concept · concepts/Pattern Language.md
Pattern Language
A connected set of design patterns meant to be used in sequence by the people who live with the result. It is supposed to generate a coherent whole, not just store good ideas (Alexander — The Origins of Pattern Theory (OOPSLA 1996)).
The three aims software missed
- Moral: is the result good, not just efficient?
- Coherence: does the language as a whole produce a whole? Alexander tested this by generating designs with it. "Many of the languages that one creates… contain a bunch of good ideas" and still produce incoherent results.
- Generativity: patterns applied one after another, each fitting the context the last one left. His later generative languages are "much more like what you call code."
The test for this wiki (T1)
Working Heuristics — Data, Matching, Product, Org, Tooling is a set of "fragmentary, atomic ideas." By Alexander's standard it isn't yet a language: nothing orders the heuristics or says which one to apply next. That joins Willingham's critique (Metacognitive Strategies: maxims need worked examples) and the Borges finding (The Borges Map: the cluster runs 11× its source). Shared remedy: fewer pages, each with real worked examples, arranged as a sequence that produces a whole. See Method Reflection T1.
For the front door
Write the front door's pattern language as a sequence (threshold → ways in → page as center → frontier…), and test it by generating actual screens with it. Done 2026-11-08: Front Door Pattern Language, six patterns; the thin slice is the coherence test.
Connections
- Living Structure — the deeper theory: patterns are invariants of living centers.
- Metacognitive Strategies — a list of patterns, like a list of maxims, is a cue, not a capability.
- Legibility in the Lens, Not the Land — the front door's pattern language starts there.