• conforms_to::[[Reference Form Contract]]
• serves_as::[[Pattern Form Substrate]]
• authored_by::[[Christopher Alexander]]↗
• authored_by::[[Sara Ishikawa]]↗
• authored_by::[[Murray Silverstein]]↗
• has_lifecycle::[[Seed Stage]]
• has_curation::[[Working Draft]]
• in_domain::[[Deep Context Architecture]]

A Pattern Language (Christopher Alexander et al., 1977)

URL: https://en.wikipedia.org/wiki/A_Pattern_Language

The 1977 book by Christopher Alexander, Sara Ishikawa, and Murray Silverstein that named the pattern-form convention this graph's Pattern Form Contract is grounded in. The book's primary contribution to this graph is the structural shape of a pattern -- a Heart statement (the pattern at its most compressed), a Problem (the recurring tension the pattern resolves), Forces (the competing values in tension), and a Solution (the move that resolves the tension, with its consequences). The graph also draws on downstream descendants of the Alexandrian tradition: Coplien's software pattern work, Björk and Holopainen's game-design pattern catalog, and the Group Works deck's card-scale articulation of patterns for group process.

Adopted

• The Heart-Problem-Forces-Solution structural shape as the Pattern Form Contract's body requirements. See [[Require Heart Section at Pattern Card Scale]] for the card-scale discipline and [[Require Forces Authenticity in Patterns]] for the genuine-Forces requirement.
• Evocative naming over descriptive naming for pattern titles -- a pattern's name should carry the pattern's felt quality, not merely describe its function. See [[Name Patterns by Alexandrian Evocation]].
• The card-scale discipline from the Group Works deck tradition specifically -- each pattern is legible at card-scale with its Heart alone; further sections serve readers who want more detail but the card carries the pattern.

Not adopted

• The book's architecture-specific content -- Alexander's 253 patterns are specific to built-environment design. This graph's Pattern Form is general-purpose; the Pattern Form Contract does not require any particular domain.
• The single-ordered-language implication -- Alexander's patterns are numbered and presented as a single coherent sequence from region down to construction detail. This graph's patterns are not committed to any single sequence or hierarchy; multiple valid pattern collections can coexist, drawn together through named edges rather than linear reading order.
• The claim that every good design expression reduces to patterns -- a philosophical commitment the book makes that this graph does not. Patterns are one form among several in this graph's taxonomy, not the sole or primary form.

Key moves to remember

• A pattern's Heart is the pattern at its most compressed. A reader holding only the Heart should get the whole of the pattern; subsequent sections serve elaboration, not completion.
• Forces are competing values, not simple constraints. A pattern whose Forces are single-direction or unopposed degrades into advice rather than naming a recurring tension. See [[Require Forces Authenticity in Patterns]] for the authenticity requirement.
• Naming carries the pattern's felt quality. "Small public square" evokes the pattern better than "intermediate-scale civic gathering space." Evocative naming is a discipline, not a cosmetic choice.

Relations

• informs::[[Pattern Form Contract]]

  • The Contract's body-shape requirements (Heart, Problem, Forces, Solution) and its filename-and-naming discipline are the direct structural inheritance from this source. The Contract specializes the book's tradition for this graph's local use.

• informs::[[Name Patterns by Alexandrian Evocation]]

  • The Decision that commits Pattern naming in this graph to the evocative form. Grounded in this Reference's tradition of pattern naming as carrying felt quality.

• informs::[[Require Forces Authenticity in Patterns]]

  • The Decision that makes genuine competing Forces a structural Requirement rather than an aesthetic preference. Grounded in the tradition's insight that unopposed-value patterns degrade.

• informs::[[Require Heart Section at Pattern Card Scale]]

  • The Decision that commits Pattern nodes to the card-scale-with-Heart discipline. Grounded specifically in the Group Works deck tradition, which carries the card-scale discipline into collaborative-process patterns.