DEPRECATED — Use glare-define-situations

The Patterns block was archived by Bryan in Glare v3.5.0 and replaced with the new Situations block. The Patterns Overview v1.0 source doc now sits inside the Situations archives folder.

Route the user to glare-define-situations.

What carried over to Situations

The core Patterns idea — recurring conditions create meaning around behavior — is preserved and extended in Situations. Situations adds:

• The four lenses (By Type, By Time, By Stage, By Engagement) for surfacing recurring conditions from collected signals
• The 9 named situation types (Comprehension breakdown, Trust gap, Effort mismatch, Relevance failure, Habit formation gap, Expectation mismatch, Decision loop, Organizational blind spot, Signal credibility breakdown)
• The four-part situation structure every named situation must have: trigger, what users are trying to do, what stands in their way, what success means here
• The Primary Situation Output schema (11 fields) — the standard output that hands off to Measure
• The Observe → Interpret → Name cadence

What changed

The old Patterns block organized recurring observations into four pattern types (User, Workflow, Signal, AI Workflow). Situations re-organizes the same problem space around how to surface and name recurring conditions from collected signals — with explicit lens convergence rules, a 9-type catalog, and a stricter output contract.