feat: cooking rescue assistant — fix over-salted, over-soured, over-spiced dishes, with honest "give up" guidance #147

New issue

Open

opened 2026-06-01 11:57:20 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-06-01 11:57:20 -07:00

Owner

Idea

A real-time troubleshooting assistant for dishes that have gone wrong. User describes the problem (too salty, too sour, too spicy, too bitter, texture issues, etc.) and Kiwi surfaces ranked fix options filtered to what is actually in the pantry, with honest assessment of when the dish is unrecoverable.

Why it fits Kiwi

Kiwi already knows pantry contents and the dish being made. Rescue suggestions are only useful if you can actually execute them. A "add a potato" suggestion is worthless if you don't have one and the grocery store closes in 10 minutes.

The waste reduction angle also fits Kiwi's mission: "this soup is too salty to serve as soup, but here's how to use it as a braising liquid for pork shoulder" turns a failure into an ingredient.

Two-layer architecture

Layer 1: deterministic rules engine (no LLM needed)

The core fix logic is mostly known chemistry and cooking science:

Problem	Mechanism	Fix
Too sour/acidic	Acid neutralization	Tiny pinch of baking soda (NaHCO3); CO2 is released, taste between additions — easy to overshoot
Too bitter	Salt suppresses bitter receptor activation	Small amount of salt or fat; sugar can help but risks masking rather than fixing
Too spicy	Capsaicin is fat-soluble, not water-soluble	Dairy fat (cream, butter, yogurt, coconut milk); adding water makes it worse
Too salty — liquid dish	Dilution or starch absorption	Add unsalted liquid; add potato and simmer (absorbs some salt); increase other ingredients
Too salty — solid dish	Limited options	Serve with unsalted starch (rice, bread) to balance on the plate; pivot to use as component in something else
Too sweet	Acid raises perceived sourness; bitterness contrasts sweetness	Acid (citrus, vinegar); salt; bitter (coffee, dark chocolate in appropriate dishes)
Too thick	Thin with appropriate liquid	Broth, water, milk, cream depending on dish
Too thin	Reduce, add emulsifier, add starch	Reduce by simmering; cornstarch slurry; roux; egg yolk for sauces
Curdled dairy sauce	Protein denaturation	Sometimes recoverable: remove from heat, whisk vigorously with cold water or cream; often better to start over

Layer 2: LLM judgment for context and nuance

How much to add (calibrated to described dish volume and severity)
Explaining why the fix works (helps user understand for next time)
Honest "give up" assessment with pivot suggestions
Edge cases where the rules conflict (dish is both too salty AND too sour)

"Give up" guidance (important)

Some dishes genuinely cannot be fixed. Knowing this early saves effort and prevents making it worse:

Burned garlic or onion: acrylamide and bitter compounds are bound; start over, the flavor will permeate everything
Over-extracted tea or coffee: bitterness from tannins/acids is irreversible; start a fresh batch
Over-whipped cream: pivot — you now have butter; it is not recoverable as whipped cream
Massively over-salted small-volume dish: dilution math works against you; repurpose as a flavor base or discard
Overcooked protein (rubbery shrimp, dry chicken breast): texture cannot be restored; shred and use in a dish where texture matters less, or incorporate into a sauce
Curdled custard or hollandaise: sometimes recoverable, sometimes not; the guide should say so honestly

Pantry integration

Every fix option should be filtered against pantry contents before being surfaced:

"Add cream" only shown if cream or coconut milk is in pantry
"Simmer with a potato" only shown if potato is available and dish has time
Fix options ranked by: (1) available in pantry, (2) time required, (3) reversibility risk (some fixes are hard to un-do)

Waste reduction angle

When a dish is unrecoverable as intended, Kiwi suggests what it can become:

Over-salted soup stock: braising liquid for pork, beans, or grains that need salt
Over-sweetened sauce: glaze for roasted vegetables or proteins
Over-spiced curry base: dilute into a larger batch next time, or freeze as a starter
Burned caramel (before it's too far): stir in cream to make a bitter-edge sauce that works on some desserts

Entry points

Inline during recipe session: "Something went wrong" button visible during active cooking mode
Standalone: "Help me fix this" from main nav, describe dish and problem in free text
Voice-friendly: designed for hands-dirty input — short prompts, simple responses

Notes

Rules engine data (fix taxonomy) should be MIT-licensed and community-editable — cooking science is well-documented
LLM step handles nuance and dose calibration; rules engine handles routing and pantry filtering
"When to give up" guidance should be honest and not sugar-coated — false hope wastes time and ingredients

## Idea A real-time troubleshooting assistant for dishes that have gone wrong. User describes the problem (too salty, too sour, too spicy, too bitter, texture issues, etc.) and Kiwi surfaces ranked fix options filtered to what is actually in the pantry, with honest assessment of when the dish is unrecoverable. ## Why it fits Kiwi Kiwi already knows pantry contents and the dish being made. Rescue suggestions are only useful if you can actually execute them. A "add a potato" suggestion is worthless if you don't have one and the grocery store closes in 10 minutes. The waste reduction angle also fits Kiwi's mission: "this soup is too salty to serve as soup, but here's how to use it as a braising liquid for pork shoulder" turns a failure into an ingredient. ## Two-layer architecture **Layer 1: deterministic rules engine (no LLM needed)** The core fix logic is mostly known chemistry and cooking science: | Problem | Mechanism | Fix | |---------|-----------|-----| | Too sour/acidic | Acid neutralization | Tiny pinch of baking soda (NaHCO3); CO2 is released, taste between additions — easy to overshoot | | Too bitter | Salt suppresses bitter receptor activation | Small amount of salt or fat; sugar can help but risks masking rather than fixing | | Too spicy | Capsaicin is fat-soluble, not water-soluble | Dairy fat (cream, butter, yogurt, coconut milk); adding water makes it worse | | Too salty — liquid dish | Dilution or starch absorption | Add unsalted liquid; add potato and simmer (absorbs some salt); increase other ingredients | | Too salty — solid dish | Limited options | Serve with unsalted starch (rice, bread) to balance on the plate; pivot to use as component in something else | | Too sweet | Acid raises perceived sourness; bitterness contrasts sweetness | Acid (citrus, vinegar); salt; bitter (coffee, dark chocolate in appropriate dishes) | | Too thick | Thin with appropriate liquid | Broth, water, milk, cream depending on dish | | Too thin | Reduce, add emulsifier, add starch | Reduce by simmering; cornstarch slurry; roux; egg yolk for sauces | | Curdled dairy sauce | Protein denaturation | Sometimes recoverable: remove from heat, whisk vigorously with cold water or cream; often better to start over | **Layer 2: LLM judgment for context and nuance** - How much to add (calibrated to described dish volume and severity) - Explaining *why* the fix works (helps user understand for next time) - Honest "give up" assessment with pivot suggestions - Edge cases where the rules conflict (dish is both too salty AND too sour) ## "Give up" guidance (important) Some dishes genuinely cannot be fixed. Knowing this early saves effort and prevents making it worse: - **Burned garlic or onion**: acrylamide and bitter compounds are bound; start over, the flavor will permeate everything - **Over-extracted tea or coffee**: bitterness from tannins/acids is irreversible; start a fresh batch - **Over-whipped cream**: pivot — you now have butter; it is not recoverable as whipped cream - **Massively over-salted small-volume dish**: dilution math works against you; repurpose as a flavor base or discard - **Overcooked protein (rubbery shrimp, dry chicken breast)**: texture cannot be restored; shred and use in a dish where texture matters less, or incorporate into a sauce - **Curdled custard or hollandaise**: sometimes recoverable, sometimes not; the guide should say so honestly ## Pantry integration Every fix option should be filtered against pantry contents before being surfaced: - "Add cream" only shown if cream or coconut milk is in pantry - "Simmer with a potato" only shown if potato is available and dish has time - Fix options ranked by: (1) available in pantry, (2) time required, (3) reversibility risk (some fixes are hard to un-do) ## Waste reduction angle When a dish is unrecoverable as intended, Kiwi suggests what it *can* become: - Over-salted soup stock: braising liquid for pork, beans, or grains that need salt - Over-sweetened sauce: glaze for roasted vegetables or proteins - Over-spiced curry base: dilute into a larger batch next time, or freeze as a starter - Burned caramel (before it's too far): stir in cream to make a bitter-edge sauce that works on some desserts ## Entry points - Inline during recipe session: "Something went wrong" button visible during active cooking mode - Standalone: "Help me fix this" from main nav, describe dish and problem in free text - Voice-friendly: designed for hands-dirty input — short prompts, simple responses ## Notes - Rules engine data (fix taxonomy) should be MIT-licensed and community-editable — cooking science is well-documented - LLM step handles nuance and dose calibration; rules engine handles routing and pantry filtering - "When to give up" guidance should be honest and not sugar-coated — false hope wastes time and ingredients