Recipe Pattern¶
Template — instantiates Slot-Template Design
A culinary scaffold with functional ingredient or process slots that support valid substitutions.
A recipe pattern defines a dish by the functional roles its ingredients play — a leavener, a fat, a binder, a liquid — rather than by a fixed shopping list, and its whole reason to exist is to make substitution safe. Its defining move is eligibility-by-function: a slot named "fat" will accept butter, oil, or lard because each performs the fat's role, but not sugar, however tempting the swap. Because it governs swaps, it also has to check that swaps work together — that the substitutions a cook makes across several slots still combine into a coherent result. This is what separates it from a template that merely freezes structure or protects a stated purpose: a recipe pattern is machinery for choosing and combining interchangeable fills, not for holding text stable.
Example¶
A baker keeps a lean-bread pattern rather than a single sandwich-loaf recipe. It is expressed in baker's percentages[n1]: flour is the 100% base, and the other slots are defined by role and proportion — hydration (water, 60–75%), leavening (commercial yeast or mature sourdough starter), salt (2%), and an optional enrichment (fat or sugar, 0–10%). Each slot lists what may fill it: the "leavening" slot's membership rule admits yeast or active starter but rejects baking soda, which has no acid to react with and would leave the dough flat and soapy.
A home baker out of yeast substitutes 20% ripe sourdough starter. The pattern's substitution rule tells her how: starter brings its own flour and water, so she must reduce the recipe's flour and hydration to keep the totals right. Then the compatibility check bites — starter is acidic and ferments slowly, so it is incompatible with the recipe's original 90-minute quick-rise timing. The pattern flags the clash and the fix: extend the bulk ferment to several hours. Two individually valid choices — sourdough leavening and a short proof — were invalid in combination, and the pattern caught it before a dense brick came out of the oven.
How it works¶
The pattern is written function-first: name each slot by the job it does, then attach a membership rule listing fills that perform that job. Substitution is not free swapping but ratio-preserving replacement — the rule specifies how choosing one fill forces adjustments elsewhere (a wetter fat means less added liquid; a starter means less flour). The distinctive step is the cross-slot compatibility check: after all slots are filled, the pattern re-examines the combination for interactions the single-slot rules can't see — acidity against timing, moisture against temperature — because a recipe pattern's failures live in the interactions, not the individual choices.
Tuning parameters¶
- Slot abstraction — "a fat" versus "an unsalted fat that stays solid at room temperature." Broader slots invite creativity; narrower ones protect the outcome.
- Substitution tolerance — how far a fill may deviate in ratio before the result changes character. Loose tolerances empower improvisation; tight ones guard the dish's identity.
- Compatibility depth — checking only obvious clashes versus modeling every cross-slot interaction. Deeper checks catch more failures but demand more culinary knowledge encoded up front.
- Enrichment openness — how many optional slots the pattern exposes. More options widen the family of dishes but blur the pattern's edges.
When it helps, and when it misleads¶
It is at its best when a cook must adapt to what's on hand — allergies, shortages, seasonality — while keeping the dish recognizably itself; it turns "can I swap this?" from a gamble into a checkable question. Its honest failure mode is the valid-alone-but-incompatible combination: each substitution passes its own slot's rule, yet together they curdle, collapse, or seize, because the interaction was never modeled. The classic misuse is treating the pattern as a taxonomy of ingredients — a list of what counts as a fat — while skipping the compatibility pass, which is precisely where multi-substitution disasters hide. The guarding discipline is to always run the combined check after the last swap, not just validate each slot as it's filled.
How it implements the components¶
membership_criteria— each slot admits fills by the culinary function they perform, rejecting look-alikes that don't do the job.substitution_rule— specifies ratio-preserving replacement: how choosing one fill forces compensating adjustments in the others.compatibility_check— re-examines the full set of chosen fills for cross-slot interactions that individually valid choices can hide.
It does not carry a frozen text skeleton or log the finished configuration — template_structure and configuration_record are Document Template's contribution — and it does not name an abstract objective the dish must preserve; that invariant_specification framing is Curriculum Template's.
Related¶
- Instantiates: Slot-Template Design — a recipe pattern is the substitution-centric instance: functional slots plus rules for swapping and combining fills.
- Sibling mechanisms: Curriculum Template · Document Template · Design System Component Slot · Plugin Slot Registration · Policy Template with Local Options · Product Configuration Matrix · Modular Form Schema · Style Guide or Pattern Library
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Recipe Pattern operates by specifies functional slots, membership rules, and ratio-preserving substitutions in a reusable template. That concrete deployed or enacted form is Representation, Specification & Plan under the frozen taxonomy.
Nearest alternative: Interface, Display & Cue — Although Interface, Display & Cue can support this mechanism, the frozen evidence makes its operative form the act that specifies functional slots, membership rules, and ratio-preserving substitutions in a reusable template; the alternative is therefore secondary rather than defining.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Art & Aesthetics
Origin pattern: Historically ambiguous
Present-day reach: Multi-domain
Rationale: Recipes are historically culinary craft artifacts whose compositional slots permit substitution. Art and aesthetics is the least-distorting active taxonomy home, with design methodology and cultural food practice retained as alternates.
Related originating lineages:
- Engineering & Design — The engineering_design lineage materially shaped Recipe Pattern through lifecycle gates, reliability, assurance, and system integration.
- Sociology & Anthropology — The sociology_anthropology lineage materially shaped Recipe Pattern through reciprocity, social exchange, and cultural practice.
Review resolution: The blind reviewers disagreed on primary lineage. Light authoritative research resolves the defining form in favor of art_aesthetics: Recipes are historically culinary craft artifacts whose compositional slots permit substitution. Art and aesthetics is the least-distorting active taxonomy home, with design methodology and cultural food practice retained as alternates. The rejected primary is retained only when it materially shaped the mechanism, and present-day breadth is recorded separately as domain_reach=multi_domain.
Attribution caveat: The canonical taxonomy has no culinary arts, food studies, or gastronomy domain; art_aesthetics is a proxy for creative craft rather than a claim that cuisine originated in fine-art theory.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
Notes¶
[n1] Baker's percentage — the convention of expressing every ingredient as a percentage of total flour weight, so a formula scales and substitutes by ratio rather than by fixed amount. It is what lets a recipe pattern reason about a swap's downstream effects instead of just its identity. ↩