Pattern Card Template¶
Template — instantiates Archetype Pattern Indexing
A fixed entry form that forces every pattern to carry the minimum fields — provenance, confidence, and the rest — needed for retrieval and reuse.
A Pattern Card Template is the empty, fixed form every entry in an index must fill — a slot for each field a pattern needs to be retrievable and reusable, so that no entry can be admitted while missing the parts people forget. Its defining move is that it is meta: it ships no filled patterns and makes no claims about any domain; it constrains the shape of entries other mechanisms populate. Its whole value is as a forcing function[n1] — by refusing to accept a card whose provenance slot or confidence slot is blank, it prevents the slow decay in which a growing library fills with half-documented entries that look complete and retrieve badly.
Example¶
A company standing up an internal knowledge base of engineering patterns keeps getting inconsistent entries: some have vivid write-ups but no citation, some assert confidence they cannot back, some are un-findable because the author skipped the fields the search runs on. The team's fix is a pattern card template — a required form with fixed slots: name, structural signature, at least one example, source (where this came from and who has used it), confidence (how well-established, from "battle-tested" to "one team's hunch"), and the retrieval tags. The form is enforced at submission: a card cannot be saved with the source or confidence slot empty. Overnight the character of the library changes — not because anyone wrote better patterns, but because every card now carries the same minimum, so the index can be searched uniformly and a reader can see a pattern's pedigree and maturity at a glance. The template authored no content; it made the content complete.
How it works¶
The template is a schema of required and optional slots plus a rule that entries conform before admission. Its leverage is entirely in what it makes mandatory: it does not supply a pattern's signature or examples — the catalogs do that — but it insists those slots exist and are filled, and it mandates the two fields authors most reliably skip because they feel like overhead. A source slot forces every card to record its provenance so an entry can be traced and trusted. A confidence slot forces every card to declare its maturity so a reader is not misled by a polished write-up of an unproven idea. Conformance is checked at the boundary; the template's work is done the moment an incomplete card is rejected.
Tuning parameters¶
- Required vs. optional slots — how many fields are mandatory. More required slots raise entry quality but raise the authoring cost and can deter contribution.
- Slot rigidity — how tightly each field is specified (free text vs. controlled values). Rigid slots make entries comparable and machine-readable; loose ones flex across pattern types but drift.
- Enforcement point — whether conformance is checked at submission, at review, or never. Earlier enforcement keeps the library clean but adds friction to contributing.
- Confidence vocabulary — the scale the confidence slot uses, from a two-way flag to a graded maturity ladder. Finer scales carry more information but demand honest self-assessment.
When it helps, and when it misleads¶
Its strength is uniformity: a single enforced form is what lets a library scale without decaying into a pile of inconsistent entries, and it quietly guarantees that the fields retrieval and trust depend on — provenance, maturity — are never simply omitted.
Its failure mode is template theater: authors fill every slot to satisfy the form while the content is thin, so the card looks complete and rigorous but its signature is vague and its confidence self-flattering — form standing in for substance. The classic misuse is treating a fully-populated template as proof of a good pattern. The guarding discipline is to pair the template with review of the content of the load-bearing slots, not just their presence, and to keep the confidence vocabulary honest so "battle-tested" has to be earned rather than typed.
How it implements the components¶
entry_template— it is the entry template: the fixed set of slots every indexed pattern must fill to be admitted.source_trace— it makes a provenance slot mandatory, so no card can be saved without recording where it came from and who has used it.confidence_label— it makes a maturity slot mandatory, forcing every entry to declare how well-established it is rather than implying certainty by polish.
It supplies no pattern_signature, no example_set, and no retrieval_index of its own — it only reserves the slots for them; the filled signatures come from Design Pattern Catalog, the worked examples from Case Library, and the working index from Tagging Schema.
Related¶
- Instantiates: Archetype Pattern Indexing — it supplies the entry-shape discipline that keeps every other mechanism's cards complete and comparable.
- Sibling mechanisms: Design Pattern Catalog · Anti-Pattern Catalog · Case Library · Diagnostic Atlas · System Archetype Index · Solution Archetype Archive · Tagging Schema · Pattern Library.
Editorial Notes¶
Form Classification¶
Form family: Interface, Display & Cue
Rationale: The mechanism is a user-facing entry form whose required provenance, confidence, signature, and example slots shape what authors must supply.
Nearest alternative: Rule, Policy & Commitment — Admission requires conformance, but the concrete deployed form is the form affordance that elicits the fields.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Architecture & Urban Planning
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Reusable pattern entries descend from Christopher Alexander's architectural pattern-language practice.
Related originating lineages:
- Computer Science & Software Engineering — Software patterns materially standardized structured pattern documentation for technical reuse.
- Human-Computer Interaction — Pattern Card Template is rooted in human-computer interaction: Information-design practice uses constrained templates and forcing functions to make provenance fields unskippable.
- Library & Information Science — Library and information science materially shaped Pattern Card Template through persistent identification, metadata, retrieval, and stewardship. Metadata and provenance practice shaped the fixed retrieval fields on the card.
Review resolution: Light authoritative-source research resolves the primary-origin disagreement in favor of architecture, spatial design, and planning practice. Christopher Alexander and the Pattern Language Movement directly documents the defining practice or theory described in the selected origin rationale. Other listed domains are retained only where the blind reviews identify material co-development or translation; broader adoption remains separate as domain_reach=multi_domain.
Attribution caveat: The particular provenance-and-confidence card is an encyclopedia-specific template built on established pattern forms.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
The template is deliberately upstream of the catalogs: it shapes their entries but authors none, which is why it appears in their Consumes lines rather than the reverse. Keeping the form separate from the filled collections is what lets an index tighten its entry standard — add a required field, sharpen the confidence scale — without rewriting the patterns themselves.
[n1] A forcing function (Donald Norman, The Design of Everyday Things) is a constraint that makes an error impossible or a required step unskippable — here, refusing to admit a card whose provenance or confidence slot is blank, so the fields people would otherwise omit cannot be omitted. ↩