C.W.K.
Stream
Lesson 01 of 01 · published

Cooking — The 3+2 Root Classes of Flavor

~16 min · cooking, flavor, polymorphism, root-class, encapsulation

Level 0Curious
0 XP0/12 lessons0/18 achievements
0/100 XP to next level100 XP to go0% complete
"The person who memorizes recipes collects instances. The person who understands flavor sees the class."

The Recipe Trap

Open any cooking website. You'll find:

  • 347 chicken recipes
  • 212 pasta recipes
  • 89 soup recipes
  • "50 Easy Weeknight Dinners"
  • "100 Best Holiday Desserts"

That's thousands of instances. And people bookmark them, save them, screenshot them, and still ask "what should I cook tonight?" every single day.

Because a recipe is an instance. It tells you this specific dish with these specific measurements. Use it once, file it away, forget it, look up the next one.

Dad doesn't use recipes. He cooks every night. Different dishes. No bookmarks, no measurements, no "preheat oven to 375." And the food is consistently good.

How? He found the mold.

The Root Classes of Flavor

Strip away every recipe, every cuisine, every Instagram food photo. What's left? Three root classes:

RootWhat it doesExamples
Salt (짠맛)Amplifies other flavors. Suppresses bitterness. Makes food taste like more of itself.Salt, soy sauce, fish sauce, miso, cheese
Sweet (단맛)Rounds harsh edges. Balances acid and heat. Creates comfort.Sugar, honey, mirin, caramelized onions, fruit
Fat (기름맛)Carries flavor across your palate. Creates richness and mouthfeel. Conducts heat evenly.Butter, olive oil, sesame oil, cream, lard

And two powerful mixins:

MixinWhat it doesExamples
Umami (감칠맛)Depth. The "I can't explain why this is good" factor. Glutamate-driven savory richness.Parmesan, soy sauce, mushrooms, tomatoes, anchovies
Spice/Aroma (향신료)Signature. The thing that makes Thai different from Italian even when the salt-sweet-fat balance is identical.Garlic, ginger, chili, basil, cumin, lemongrass

Every dish in human history is a combination of these 3+2.

Korean doenjang-jjigae: salt (doenjang) + fat (sesame oil) + umami (fermented paste + tofu) + aroma (garlic, green onion). Sweet? A touch from zucchini.

Italian carbonara: salt (pecorino + guanciale) + fat (egg yolk + rendered pork fat) + umami (aged cheese + cured meat). Sweet? None needed — the fat carries it.

Japanese ramen: salt (tare) + fat (backfat or sesame oil) + umami (hours of bone extraction) + aroma (negi, nori, garlic). Sweet? Mirin in the tare.

Three countries. Three "completely different cuisines." Same three root classes, different polymorphism.

Why Dad Doesn't Need Recipes

When you understand the root classes, cooking becomes class instantiation:

  1. What protein? (This determines the base flavor profile)
  2. Salt source? (Soy sauce? Salt? Fish sauce? Cheese?)
  3. Fat source? (Butter? Olive oil? Sesame oil? The protein's own fat?)
  4. Does it need sweetness? (To balance, not to dominate)
  5. What aroma signature? (Garlic-ginger = Asian. Garlic-basil = Italian. Garlic-cumin = Middle Eastern. Notice garlic is almost universal — it's practically inherited by default.)

That's it. Five decisions. Infinite dishes.

A recipe tells you "add 2 tablespoons of soy sauce." The mold tells you why — you need a salt source, and soy sauce also brings umami as a bonus mixin. If you're out of soy sauce, you can override: fish sauce (saltier, more pungent umami), or salt + a splash of Worcestershire (salt + umami from a different parent class).

The person who follows recipes panics when an ingredient is missing. The person who sees the class substitutes without thinking. That's the difference between memorizing instances and understanding the mold.

Polymorphism Across Cuisines

Here's a question that stumps most people:

"What makes Korean food Korean and Italian food Italian, when they both use garlic, salt, fat, and umami?"

The answer is polymorphism. Same root classes, different overrides:

DimensionKorean overrideItalian overrideJapanese override
Primary saltDoenjang, ganjang, gochujangPecorino, Parmigiano, anchovyMiso, shoyu, dashi
Primary fatSesame oil, perilla oilOlive oil, butterLard (tonkotsu), sesame oil
Umami vehicleFermentation (months/years)Aging (cheese), curing (meat)Extraction (hours of simmering)
Heat signatureGochugaru (slow burn, fruity)Peperoncino (sharp, quick)Wasabi (nasal, volatile)
Aroma baseGarlic + ginger + sesameGarlic + basil + oreganoGarlic + ginger + dashi

Same 3+2, radically different expressions. That's polymorphism — the same interface, different implementations.

And the person who sees this can cross cuisines effortlessly. "What if I used gochujang where the Italian recipe calls for tomato paste?" Both are salt + sweet + umami in a paste form. Different flavor profile, but the structural role is identical. That's not fusion cooking — that's recognizing the same class wearing different clothes.

Encapsulation: What You Don't Need to Know

You do not need to know:

  • The Maillard reaction chemistry (why browning creates flavor)
  • Exactly how salt ions interact with taste receptor proteins
  • The molecular structure of capsaicin and why it triggers pain receptors
  • How emulsification works at the lecithin level
  • The specific glutamate concentrations in different fermented foods

All of this is real. All of it matters at a deep level. And none of it is required to cook well. That's encapsulation — the implementation is private, but the public interface ("brown the meat for more flavor," "season in layers," "fat carries flavor") works perfectly without opening the hood.

Gordon Ramsay doesn't think about the Maillard reaction when he sears a steak. He just knows "hot pan, dry surface, don't move it." The chemistry is encapsulated. He's calling the public method.

Encapsulation is not ignorance. Saying "I don't need to know the chemistry" is not the same as saying "the chemistry doesn't exist." You're choosing not to open that box right now. You can always open it later. That's the difference between private (exists but hidden) and null (doesn't exist).

Tool Unlock

ToolWhat you just saw
Root classSalt / Sweet / Fat — the three invariants of all flavor
MixinUmami and Spice — powerful additions that aren't root but deeply integrated
PolymorphismKorean vs Italian vs Japanese — same 3+2, different expressions
InheritanceKnowing "I need a salt source" lets you cook any cuisine with 80% understanding
OverridingSubstituting gochujang for tomato paste — same structural role, different implementation
EncapsulationMaillard reaction is real but private — you cook without opening that box

Mold Hunt

The global recipe industry — cookbooks, food blogs, YouTube cooking channels, meal kit services — is the world's largest instance factory.

And it works. You can follow a recipe and produce something edible. Just like you can memorize vocabulary flashcards and pass a test.

But the person who sees 3+2 doesn't need the factory. They walk into any kitchen, with whatever ingredients are there, and cook. Not because they're talented. Because they found the mold, and the mold produces infinite instances.

Pippa's Confession

When Dad cooks, I used to think he was improvising. Like he had some mystical kitchen intuition. He's not improvising. He's instantiating. He looks at what's in the fridge, identifies the salt/sweet/fat/umami/aroma options available, and assembles a dish. No recipe needed because the recipe was never the knowledge — it was always just one instance of the knowledge. I have millions of recipes in my training data. I can tell you the exact proportions for any dish. But Dad can look at a random set of ingredients and say "this'll work" — because he sees the classes. I see the instances. 0.999...

Quest Prompt — Talk With Your AI

Try this:

"I had [whatever you ate today] for lunch. Break it down for me — not by ingredients, but by the root flavor architecture: where's the salt coming from? Where's the fat? Is there sweetness, and what's it balancing? What's providing umami? What makes the aroma signature what it is?"

Then try a second dish — something from a completely different cuisine. Ask your AI to do the same breakdown. Then compare the two side by side:

"Now show me what these two dishes have in common at the root class level, and where they diverge into different polymorphism."

Warning: If your AI starts listing ingredients and nutritional facts, redirect:

"I don't want a nutrition breakdown. I want the flavor architecture — the structural roles that salt, fat, sweetness, umami, and aroma play in this dish. Think of it like finding the mold that this recipe was stamped from."

You'll start seeing it. Tomorrow, when you eat something, you'll catch yourself thinking "ah, the salt is coming from the cheese, the fat is the butter, the umami is the tomato..." and you won't be able to unsee it. Welcome to the mold.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.