Tag Type
Technique
Date
August 29, 2026
Favorite
Notes
Processes
Resources
Tools
Zettels
A blending component’s value is target-relativeBlind and contextual tastings answer different questionsTaster variation can be evidence rather than noiseA flavor fault is dose-, matrix-, and context-dependentBlending begins with inventory architectureSmall sensory pilots support local decisions, not category lawsA blend needs a target before it needs ingredientsComponents should be screened for faults before formulationBlend complexity is the separation of perceptible roles, not the count of ingredientsBranching prototypes reduce premature commitment to one recipe pathSensory validation needs standardized decision sessions and real-use checksDiffering palates are useful when disagreement is preserved as dataProduction recipe is a starting hypothesis, not a complete component identityFactorial tasting helps isolate component variablesQuality gates should precede creative formulationA regulatory ceiling is not a sensory targetConsumer test-and-learn sessions require structured contextDrinking occasion is a legitimate blend-design variableSensory questions require distinct test methodsA triangle test detects difference without explaining itCarryover can invalidate an otherwise efficient discrimination testConsumer liking is population- and context-specificTrained assessors and target consumers answer different questionsAlcohol sensory work requires an explicit participation protocolShared sensory vocabulary does not establish assessor calibrationTasting literacy requires structure without answer-key thinkingChemical abundance alone does not establish sensory importanceExpert tasting is trained attention expressed through calibrated languageBrand ancestry is not distillery continuityBottling proof does not reveal dilution historyBalance is distinct from age, intensity and prestigeConsumer bottle bridges are hypotheses, not blend recipesOwner
Ben HoshourArchived?
Use this record for one canonical semantic concept. Before creating it, search Preferred Label and Aliases to avoid duplicates.
Definition
State the concept in one or two precise sentences. Define what it is, not merely where it appears.
Scope
Use this tag when
Do not use this tag when
Boundary examples
- Included:
- Excluded:
Vocabulary guidance
- Record alternate spellings, abbreviations, former names, and common search terms in Aliases.
- Choose one primary Tag Type.
- Assign one primary Parent Tag unless this is a root concept.
- Use Related Tags for associative links that are neither broader nor narrower.
- Do not use a second tag when an alias will preserve the distinction adequately.
Governance checklist
Preferred Label is singular, concise, and unambiguous.
Definition is present.
Tag Type is selected.
Parent Tag is assigned, or the tag is intentionally a root concept.
Aliases were checked for duplicates.
Scope Note explains important boundaries.
Governance Status is Approved before production use.
If Deprecated or Merged, Merged Into identifies the approved replacement.
Usage notes
Record decisions, edge cases, and future taxonomy review notes here.