# Cooking Framework Design **Date:** 2026-03-25 **Context:** Personal cooking system for a frequent traveler. Needs to work in partial kitchens (hostel/shared, 1–2 burners) with whatever ingredients are locally available. Budget-first, beginner-skill, scalable over time. --- ## Goals - Replace ingredient-specific recipes with a flexible formula that works in any region - Teach flavor relationships from first principles so the system can be reasoned from, not just memorized - Support weekly meal planning with a market-first assessment flow - Start small, scale indefinitely as repertoire grows --- ## Architecture: Three Layers Every meal is composed by filling a universal formula using the logic of a chosen flavor profile, guided by an understanding of how each role works. ``` LAYER 1: Universal Formula Protein + Produce + Starch + Fat + Acid + Aromatic + Technique The formula never changes. Only what fills each role changes. LAYER 2: Flavor Profile Formulas Each profile defines the principles for each role — not specific items. Profiles are identified by their fat + acid + aromatic character. LAYER 3: Role Substitution Logic Teaches category thinking over product thinking. "No lemons? → any citrus → white vinegar cut with water" "No soy sauce? → fish sauce → miso + salt → any fermented paste" ``` --- ## Layer 1: Universal Formula | Role | Function | How to fill it | |---|---|---| | **Protein** | Primary substance; main umami source when browned | Meat, fish, eggs, legumes, tofu | | **Produce** | Texture, color, micronutrients | Any vegetables; 2–3 per meal | | **Starch** | Volume, satiety | Any grain, root vegetable, legume, or bread | | **Fat** | Flavor solvent; carries aromatics through the dish | Any cooking oil or animal fat | | **Acid** | Palate reset; cuts richness | Citrus juice, any vinegar, fermented liquid, yogurt | | **Aromatic** | Base complexity; defines regional character | Alliums (garlic, onion, leek, shallot, scallion) + secondary spice | | **Technique** | Determines texture and umami generation | One-Pan Sear or Steam-Sauté (see Frameworks.md) | --- ## Layer 2: Flavor Profile Formulas Each profile is defined by its **fat + acid + aromatic character**. Identify two or three of these in a local market and the profile works — you do not need every listed item. | Profile | Fat principle | Acid principle | Aromatic character | Signature feel | |---|---|---|---|---| | **Mediterranean** | Neutral oil; olive oil to finish | Citrus or wine-derived vinegar | Garlic + onion + dried herbs (oregano, thyme, rosemary, or local equivalent) | Bright, clean, herbaceous | | **East Asian** | Neutral oil to cook; nutty/toasted oil to finish | Rice vinegar or lime; soy/fish sauce as salt+acid hybrid | Garlic + ginger + scallion or leek | Savory-umami, sharp finish | | **Latin American** | Neutral oil or lard | Lime or acidic fermented liquid (pickle brine, vinegar) | Onion + hot pepper + cumin | Smoky, earthy, acidic punch | | **French/Continental** | Butter or cream if available; neutral oil otherwise | Wine, lemon, or mustard | Shallot/leek + garlic + soft herbs (parsley, tarragon) | Rich, coating, aromatic | | **South Asian** | Ghee or coconut oil; neutral otherwise | Yogurt, citrus, or tamarind-adjacent sour | Onion + garlic + ginger + warm spices (cumin, coriander, turmeric) | Warm, layered, complex | | **Standard American** | Butter or bacon fat; neutral otherwise | Apple cider vinegar or hot sauce | Onion + garlic | Simple, rich, direct | --- ## Layer 3: Role Substitution Logic Substitution is about **category**, not product. Ask: what role does this ingredient play, and what else plays that role locally? **Acid substitution hierarchy:** Fresh citrus → other citrus → mild vinegar (rice, white wine) → strong vinegar diluted with water → fermented liquid (pickle brine, yogurt whey) **Fat substitution hierarchy:** Neutral high-smoke oil → animal fat (lard, ghee, tallow) → olive oil (lower heat only) → coconut oil (changes flavor profile toward South Asian/Southeast Asian) **Aromatic substitution hierarchy:** Garlic + onion are available almost everywhere and form a valid aromatic base for any profile. Secondary aromatics (ginger, leek, shallot, hot pepper) add regional specificity when available. **Umami substitution hierarchy:** Brown your protein well (Maillard) → add a fermented condiment (soy, fish sauce, miso, Worcestershire, any fermented paste) → add tomato paste or dried mushrooms → add aged or hard cheese as a finish **Starch substitution hierarchy:** Any grain cooked by absorption → root vegetables (potato, sweet potato, yuca, taro) → legumes (beans, lentils) → flatbread or commercial bread --- ## Flavor Sense: Mechanism Layer These are the four principles that explain *why* the formula works. Internalize these and the profiles become consequences of logic rather than things to memorize. ### Fat is a flavor solvent Most aromatic compounds are fat-soluble — they don't dissolve well in water. When you cook an aromatic in fat, the fat extracts those compounds and carries them into every other ingredient in the pan. This is why "aromatic in fat first" is universal across every cuisine: it's chemistry, not tradition. Skipping this step means the flavor stays trapped in the aromatic instead of spreading through the dish. ### Acid resets the palate Fat coats your tongue and lingers — that's what makes rich food satisfying. But coating means each bite tastes slightly less than the last, because taste receptors are progressively buried. Acid stimulates saliva production, which physically clears the fat coating and resets your receptors. This is why lemon on fried fish or vinegar in a stir-fry makes the dish taste *cleaner* without tasting sour — it's removing interference, not adding brightness. **Too heavy → needs acid. Too sharp or flat → needs fat.** ### Salt works in layers, not as a finish Salt needs moisture to dissolve and penetrate. Applied to a dry surface, it sits on top and you taste it directly. Applied with moisture present, it dissolves, penetrates, and seasons from within. - **Salt protein before cooking** (15–30 min minimum): draws moisture out, which reabsorbs seasoned — this is what Bone-Dry Patting achieves - **Salt cooking water heavily**: the only chance to season a starch's interior - **Salt in layers at each stage**: protein, then vegetables as they go in, then taste and adjust at the end - **Target feeling**: salt should be undetectable as its own flavor. "Flat" = under-salted. "Tastes salty" = over-salted. Correct = everything tastes more like itself ### Browning creates umami Umami is the fifth taste — the sense of depth, completeness, and satisfaction. It comes from glutamates, which are amino acids released when proteins break down through browning, fermentation, or slow cooking. Your brain evolved to detect them as a signal for protein and nutrition. The One-Pan Sear is the primary umami-generation step in this framework. The browned crust is concentrated glutamate. Without it, the dish can be technically correct (salted, acidic, well-seasoned) and still feel hollow. **Umami sources by method:** - Browning: seared meat, roasted vegetables, toasted grains - Fermentation: soy sauce, fish sauce, miso, Worcestershire, aged cheese, fermented paste - Concentration: tomato paste, dried mushrooms, reduced stock **If a dish tastes flat despite correct salt and acid: it needs umami.** Add something fermented or browned. --- ## Weekly Planning Flow The entry point for the system. Works market-first — assess what's available before deciding what to make. ### Step 1: Market assessment (before buying) Walk the market and categorize what you see into roles: - What protein is affordable and fresh? *(pick 1–2)* - What produce looks good in quantity? *(pick 2–3)* - What starch is available? *(pick 1)* - What fats, acids, and aromatics are on the shelf? *(these determine which profile is possible)* ### Step 2: Profile matching Look at available fats/acids/aromatics. Match to the profile whose **two or three defining elements** you can satisfy. You do not need every item — you need the ones that define the profile's character. ### Step 3: Fill the formula For each planned meal: ``` Technique: [One-Pan Sear / Steam-Sauté] Profile: [which flavor logic] Protein: _______________ Produce: _______________, _______________ (+ _______________ optional) Starch: _______________ Fat: _______________ Acid: _______________ Aromatic: _______________ ``` ### Step 4: Shopping list The list writes itself from the formula fills. Pantry staples (salt, a fat, a basic acid) stay stocked between markets. Fresh components (protein, produce) are bought per week or per location. --- ## Existing Files and Their Role in the System | File | Layer | Role | |---|---|---| | `Frameworks.md` | Layer 1 (Technique) | Documents One-Pan Sear, Steam-Sauté, Starch-Buffer methods | | `Flavor Profile Matrix.md` | Layer 2 | Specific ingredient examples per profile — use as a reference, not a requirement | | `Essential Non-Perishables.md` | Layer 3 | Pantry stocking guide; the "always have" items that make substitution easier | | `References/Bone-Dry Patting.md` | Flavor Sense | Technical detail on salt timing and Maillard prerequisites | | `References/High Smoke Point Fats.md` | Flavor Sense | Technical detail on fat selection for searing | --- ## Implementation Scope The framework design is complete. Implementation involves building out the note structure that makes this usable: 1. A **Flavor Sense** reference note (the four mechanisms) 2. Revised **Flavor Profile Formulas** note (role principles, not specific items) 3. A **Role Substitution Logic** reference note (substitution hierarchies) 4. A **Weekly Planning Template** note (the market-first flow with formula slots) 5. Light revision of existing files to link into the new structure Out of scope for now: individual meal builds, cuisine-specific deep dives, nutrition tracking.