Skip to content

Archetype Pattern Indexing

Index recurring patterns by structural signature so they can be recognized, compared, and reused across contexts.

The Diagnostic Story

Symptom: Recurring situations keep getting solved from scratch because the patterns behind them are scattered across individual memory, case files, and expert intuition. When someone finally names a pattern, a debate breaks out over whether this case really fits — because no one can inspect the structural signature, only the label. Meanwhile, everyone is either reinventing solutions or grabbing the most fashionable archetype regardless of fit.

Pivot: Convert scattered pattern knowledge into an indexed retrieval structure by defining the structural signature of each archetype, pairing it with examples and counterexamples, and explicitly mapping the distinctions from its nearest neighbors.

Resolution: The index makes structural recognition inspectable rather than expert-only. Retrieval becomes a structural match against signatures rather than a memory test, and response guidance is traceable to fit conditions — so pattern application disciplines itself.

Reach for this when you hear…

[clinical diagnosis] “We keep treating these as separate presentations, but they're the same underlying structure — we need a decision aid we can actually look at, not just what the senior doctor remembers.”

[software architecture] “Everyone argues about whether this is a Facade or a Mediator, and it's because nobody wrote down what structurally distinguishes them.”

[legal practice] “We have a hundred precedents and no way to find the one that actually matches the fact pattern — we're searching by case name, not by what the case is about.”

When This Archetype Applies

Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.

People repeatedly encounter structurally similar situations but treat them as isolated, or they remember pattern names without a reliable way to recognize, retrieve, compare, and reuse the relevant archetype. Knowledge remains scattered across cases, experts, documents, or anecdotes, so pattern recognition depends on memory and intuition rather than inspectable structure.

Show the applicability expression

Applicability expression5 distinct conditions

Recurring cross-context casesandRecognition-dependent responseandany oneWeak pattern retrievalorConfusing surface resemblanceorUnorganized examples
Algebraic12(ABC)

groundedpartly groundedopen

Equivalent to the 3 condition sets it replaces, with 4 duplicate condition cards removed.

2Required in every casenumbered 1–2

These hold no matter which pattern applies.

1

Recurring cross-context cases · grounded

Similar cases recur across contexts

2

Recognition-dependent response · open

Response guidance depends on recognizing the pattern

3At least one of theselettered A–C

Any single one of these completes the pattern.

A

Weak pattern retrieval · open

Pattern names exist but retrieval is weak

B

Confusing surface resemblance · open

Surface resemblance creates confusion

C

Unorganized examples · open

Examples are available but not organized

1 of 5 conditions grounded · 4 open.

Read the methodologyDownload the trigger-logic data

Mechanisms / Implementations

  • Anti-Pattern Catalog: Indexes recurring structures that reliably go wrong, pairing each with the near-misses that are actually fine and the remediation that follows once a match is confirmed.
  • Case Library: Indexes concrete, cited precedents by their case features so a new situation retrieves the closest prior case rather than an abstract rule.
  • Design Pattern Catalog: Indexes proven solution structures by their forces and structure, with known uses and the neighboring patterns each is easily confused with.
  • Diagnostic Atlas: Maps presenting symptoms to candidate patterns with the look-alikes to rule out and a stated confidence in the fit.
  • Pattern Card Template: A fixed entry form that forces every pattern to carry the minimum fields — provenance, confidence, and the rest — needed for retrieval and reuse.
  • Pattern Library: Collects approved recurring patterns and examples that can be reused or recombined.
  • Solution Archetype Archive: A governed, versioned repository that preserves each archetype's provenance, variants, and merge history on a maintenance cadence to prevent duplicate drafting.
  • System Archetype Index: Indexes recurring feedback-loop structures by their dynamics, distinguishing look-alike loops and naming the leverage point each implies.
  • Tagging Schema: A controlled vocabulary of facets and tags, governed and maintained, that turns free-text search into structured retrieval by problem features.

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

Also references 6 related abstractions

  • Analogy: Transfer structure between domains.
  • Compression: Reduce redundancy.
  • Representation: Model complex ideas.
  • Schema: Structured knowledge framework.
  • Transfer of Learning: Apply knowledge across contexts.
  • Universality: Systems with different microscopic detail obey identical macroscopic laws because only a low-dimensional signature survives coarse-graining.

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Diagnostic Archetype Indexing · subtype · recognized

Indexes archetypes so a current case can be compared against diagnostic pattern signatures.

Design Pattern Indexing · domain variant · recognized

Indexes reusable design patterns by problem context, forces, structure, examples, and known tradeoffs.

Anti-Pattern Indexing · risk or failure variant · recognized

Indexes recurring harmful or failure-prone structures so they can be recognized and avoided.

Case-Based Pattern Indexing · implementation variant · recognized

Uses concrete cases as retrieval anchors for recurring patterns, with each case linked to structural signatures and neighbor distinctions.

Editorial Notes

Problem Classification

Classification: Information Overload, Search & Attention FailureKnowledge Retrieval, Pattern & Wayfinding

Problem kernel: recurring structural patterns cannot be found or reused

Rationale: Relevant archetypes remain scattered across cases and memory without indexed recognition cues, comparison links, or reliable retrieval paths.

Independent corroboration: The earliest necessary condition in the frozen evidence is: People repeatedly encounter structurally similar situations but treat them as isolated, or they remember pattern names without a reliable way to recognize, retrieve, compare, and reuse the relevant archetype. That is a knowledge retrieval pattern and wayfinding problem because Relevant information or structural analogies exist but cannot be found, recognized, sequenced, or navigated from current local cues.

Review outcome: Independent reviewer agreement; high confidence.