Solution Archetype Archive¶
Archive — instantiates Archetype Pattern Indexing
A governed, versioned repository that preserves each archetype's provenance, variants, and merge history on a maintenance cadence to prevent duplicate drafting.
A Solution Archetype Archive is the governed, versioned repository behind an index — the place where each archetype's lineage is preserved: where it came from, which variants and near-aliases exist, and how entries have been split or merged over time. Its defining move is stewardship over time: unlike a catalog optimized for a reader looking something up, the archive is optimized for the curator keeping a growing corpus coherent — preventing the same pattern from being drafted twice, holding onto useful variants instead of silently collapsing them, and running the review cadence that keeps boundaries clean. It is retrieval infrastructure only indirectly; its primary users are the people who maintain the index, not the people who search it.
Example¶
The Encyclopedia of Abstractions maintains a solution archetype archive of its own patterns. Each archetype in it carries its provenance — the source bundle it was generated from, so any claim can be traced back to its origin — a record of its variants and near-aliases (Diagnostic Archetype Indexing, Design Pattern Indexing, and Anti-Pattern Indexing are held as variants of one parent, with notes on how each differs), and a merge history logging when two drafts were found to be the same pattern and combined. When a new candidate arrives — say, "Pattern Library Creation" — a curator checks it against the archive before drafting: the archive shows it is a merge-sensitive near-alias of an existing parent, with a note explaining the boundary. The result is that the candidate is recorded as a variant rather than drafted afresh, and the duplicate never enters the corpus. On a fixed review cadence, the archive's queue also resurfaces entries whose boundaries have blurred as new cases accumulated, so the maintainers can split or re-merge on evidence. None of this helps a casual reader retrieve a pattern; all of it keeps the retrieval corpus from quietly rotting.
How it works¶
The archive treats each entry as a versioned record rather than a static card. Three things are load-bearing. Provenance — every archetype links to the source it was derived from, so the corpus stays auditable and no entry is orphaned from its origin. Variant and merge tracking — near-aliases are held explicitly with notes on how they differ, and merges and splits are logged so the reasoning behind a boundary survives the person who made it. And a maintenance cadence — a review queue that periodically resurfaces entries for re-adjudication as new cases reveal boundary errors, rather than freezing the index at first draft. The archive does not itself provide the search layer; it holds the governed content that a retrieval index points into.
Tuning parameters¶
- Merge vs. preserve bias — how aggressively near-duplicates are collapsed versus kept as variants. Aggressive merging keeps the corpus lean but can destroy useful distinctions; liberal preservation keeps nuance but breeds near-aliases.
- Review cadence — how often the maintenance queue re-adjudicates entries. Frequent review keeps boundaries sharp but costs curator time; rare review lets drift accumulate.
- Provenance depth — how much origin detail each record retains, from a bare source pointer to full derivation history. Deeper provenance aids audit and reversal but grows the archive.
- Variant-note richness — how fully each near-alias documents its boundary with its parent. Richer notes prevent re-litigating old merges; thin ones invite the same debate twice.
When it helps, and when it misleads¶
Its strength is corpus coherence at scale: it is what stops a growing library from accumulating duplicate drafts, losing the reasoning behind past merges, or freezing at a first draft that later cases outgrow — the maintenance backbone a large index cannot do without.
Its failure mode is mechanism reification[n1] — treating the archive, its version history, and its tidy merge log as the solution itself, so effort pours into governance ceremony while the underlying signatures and boundaries stay weak. A pristine changelog over vague entries is still a vague index. The classic misuse is over-merging under a lean-corpus mandate, silently collapsing variants that carried real distinctions and destroying knowledge the merge note was supposed to preserve. The guarding discipline is to make every merge and split record why, and to bias toward preserving a documented variant over collapsing it whenever the distinction might still matter.
How it implements the components¶
source_trace— every archived archetype links to the source it was derived from, keeping the whole corpus auditable and reversible.neighbor_distinction— near-aliases and variants are held explicitly with notes on how each differs from its parent, so the archive prevents duplicate drafting rather than silently collapsing distinctions.update_cadence— a review queue re-adjudicates entries on a maintenance rhythm as new cases reveal boundary errors, so the index stays current instead of frozen at first draft.
It builds no retrieval_index and distills no pattern_signature — the search layer belongs to Tagging Schema and the structural definitions to Design Pattern Catalog; the archive governs and preserves the content those mechanisms search and define.
Related¶
- Instantiates: Archetype Pattern Indexing — it supplies the maintenance-and-governance side of the index, the machinery that keeps a growing corpus coherent.
- Consumes: Pattern Card Template shapes the records it stores; Tagging Schema supplies the vocabulary its variants are cross-referenced by.
- Sibling mechanisms: Design Pattern Catalog · Anti-Pattern Catalog · Case Library · Diagnostic Atlas · System Archetype Index · Pattern Card Template · Tagging Schema · Pattern Library.
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Solution Archetype Archive operates as a persistent ledger, log, register, or case record that preserves history and traceability because it a governed, versioned repository that preserves each archetype's provenance, variants, and merge history on a maintenance cadence to prevent duplicate drafting.
Independent corroboration: The frozen evidence defines Solution Archetype Archive as 'A governed, versioned repository that preserves each archetype's provenance, variants, and merge history on a maintenance cadence to prevent duplicate drafting', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: A governed versioned repository of provenance, variants, and merge history is archival and knowledge-organization practice.
Related originating lineages:
- Computer Science & Software Engineering — Computer science and software-engineering practice supplies a parallel or contributing lineage for the mechanism's defining operation: a governed, versioned repository that preserves each archetype's provenance, variants, and merge history on a maintenance cadence to prevent duplicate drafting.
- Engineering & Design — Pattern libraries preserve reusable solution forms and variants.
- History & Historiography — Provenance preserves how archetypes evolved and were combined.
- Organizational & Management Science — Maintenance cadence and custodians prevent duplication and decay.
Review resolution: The blind reviewers agree that library_information_science is the primary origin and differ only on alternate origin disagreement, origin mode disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain cross_disciplinary_synthesis because the combined evidence shows material contributions from several lineages. The broader reach of multi_domain records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] In archival science the principle of provenance (respect des fonds) holds that records must be kept with their origin and original order intact rather than reorganized by a later scheme — the same commitment that makes an archetype archive auditable and reversible. Reifying the archive's version history into the "solution" inverts this: the ceremony of tracking provenance is mistaken for the substance the provenance was meant to protect. ↩