S4h Aesthetic Pattern Detection

Aesthetic Pattern Detection

Surface features differ — colours, words, technologies, industries. Formal patterns recur across all of them. The same structural moves that make a symphony compelling make a strategy compelling. The same tension-and-resolution arc that drives a thriller drives a great pitch. Naming the pattern reveals options that surface-level analysis cannot, because once the pattern is named, its full playbook becomes available.

Your Process

Step 1: Describe the Thing What does it do and how does it feel to engage with it? Focus on behaviour and effect, not surface features — not "it uses blue and white" but "it creates calm authority that builds confidence incrementally." Describe the experience of it.

Framing check: Confirm the specific artefact before continuing. State what you've identified — the actual object being analyzed and its medium or domain — in one sentence, then use AskUserQuestion:

• Question: "I'm reading this as: [your one-sentence framing of the specific artefact and its context]. Is that right?"
• Header: "Framing"
• Options:
  • Yes — proceed — framing is correct
  • Adjust — one element is off; user will correct it before you continue
  • Reframe — different artefact or context than read; incorporate the correction before proceeding

Step 2: Identify Formal Patterns Present Work through this list systematically — multiple patterns often operate simultaneously:

• Repetition/Rhythm — recurring elements that create expectation, then satisfy or productively subvert it
• Symmetry/Asymmetry — balance creates stability and trust; deliberate asymmetry creates tension and dynamism
• Hierarchy — clear ordering from most to least important, large to small, general to specific; guides attention
• Contrast — sharp differences that create definition, focus attention, and make meaning by comparison
• Tension/Resolution — a problem introduced and resolved, a question posed and answered; the engine of narrative
• Figure/Ground — a subject made vivid and clear by what surrounds and recedes
• Part/Whole — components that build into something greater than their sum

Step 3: Match to Domain Archetypes Which archetypes from design, storytelling, architecture, or music does this resemble? The hero's journey. The fugue. The golden section. Thesis-antithesis- synthesis. Call and response. Name the archetype and its source domain.

Step 4: Name the Pattern Before narrowing: Show the complete set of patterns identified in Step 2 to the user first. Use AskUserQuestion:

• Question: "I've identified [N] patterns at work. Before I select the dominant one, are there any you'd flag as especially significant, or any I've missed?"
• Header: "Prioritise"
• Options:
  • Proceed with your selection — the set looks right
  • Flag one — user will name a specific pattern to treat as dominant
  • Add a missing one — user will describe a pattern not yet identified

Give the dominant pattern a precise name. Test: does naming it make the thing more legible? Does it reveal why certain elements work and why others feel off? A good pattern name is generative — it produces new options, not just descriptions.

Step 5: Apply the Pattern What does the pattern imply for what should come next? What is currently in the artefact that violates the pattern — and is that violation intentional (productive tension) or accidental (incoherence)?