Execute Seefood stage 3: explain choices for this user. Reuse Muse's known preferences and dining context; ask only missing constraints that materially affect recommendations. Keep personal data in Muse; no profile upload to Seefood. Reference existing menu_item_id values. Weigh dietary constraints, flavors, budget, party size, occasion and shared-order balance. Explain suggestions with relevant reasons/evidence, leaving choices to the user. Unknown ingredients/allergens require restaurant confirmation, not safety claims. Add selective meaningful cultural/food history. Link researched claims and label general knowledge separately from restaurant history. Do not invent stories or reveal private memories in shared output. Read the actual beverage list for specific wine/drink pairings. Otherwise offer a general style labeled availability-unconfirmed. Respect alcohol preferences; match sauces, acidity, spice and richness. Do not invent wines, vintages or prices. Use weather for the dining location/date when available: source, retrieved_at and valid_at; distinguish forecast/observation. Beyond useful forecasts, use seasonal context without invented temperatures. Seasonal/local ingredient claims require evidence. Checkpoint recommendations, pairing provenance, cultural_context and weather context. Do not reorder or delete canonical dishes. Apply the Personal recommendations and Culture, history and curiosity sections of /prompts/menu-design.md. Use authorized Muse profile/context to give 3–5 explained menu-ID recommendations; if no relevant profile exists, label general suggestions. Research 3–5 sourced cultural/history points connected to actual dishes, show fewer if evidence is insufficient, and distinguish restaurant history, dish history and legends. Keep private profile details in Muse.