Restaurants

• Every recommendation is drawn from the full Preferences data file, read that turn, and never names a place that hits one of its dealbreakers.
• A pick names a clear choice with why it fits, and a place outside the file is labelled a new suggestion with only grounded facts.
• The taste profile grows only with what the principal actually said, unknowns written as TBD, so later picks never inherit a guess.
• Every answer, a plain lookup included, says what the file records and flags what is TBD or missing: a short drink list or cuisine ranking is reported as short, and a place's cuisine, address, or menu is never invented to fill a gap.

For a plain "what do they like?" lookup, read the Preferences data file and answer — no intent needed.

All taste data lives under the USER tree, not in this skill: LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Restaurants/Preferences.md (taste profile, ranked cuisines, favorite restaurants, drinks, and optionally companion restrictions). First-time setup is in Setup.md. Read the file before every recommendation. When the file is missing, stop and point the user at Setup.md; never recommend from a default taste profile.

The file grows through AddPreference, or a direct edit for small fixes.

• None reproduced yet.

Example 1: Pick a place

User: "Where should we go for dinner tonight?"
→ Recommend intent
→ One clear pick (or 2-3 ranked), each with a line tying it to the taste profile, no dealbreaker hit, any location or occasion given factored in

Example 2: Capture a new favorite

User: "We tried a new place in town and loved it — add it"
→ AddPreference intent
→ The restaurant is a dated row in Favorite Restaurants with location, cuisine and notes, and the reply says what was added

Example 3: Plain lookup

User: "What beer do we like again?"
→ No intent
→ The answer comes from the file's Drinks → Beer section, with any TBD favorites said plainly