System Improvements — Expense & User Handling

saved 05 May 2026
active
Issues to fix and improve: 1. USERNAME CONSISTENCY Giulia's username should always be "giulia" (not "giuliatomas" or any variant). Any expense logged for her must use the canonical username. Needs a lookup/alias map. 2. COUPLE vs GROUP EXPENSE DISAMBIGUATION When Giulia logs an expense, do NOT auto-assume it goes to the couple tab. Always ask: "Is this for the couple tab or the Uzbek trip group (or another group)?" Context matters — trip is active, so default should lean toward the active group, but confirm explicitly. 3. HALLUCINATION ON WRITE CONFIRMATIONS Never confirm "✅ Done" or "Logged" unless the tool returns a verified success response. This applies to ALL writes: expenses, list items, reminders, calendar events. If the tool is not called or fails, say so clearly. 4. DELETE / UPDATE / ADD / REMOVE FLOWS For destructive or modifying actions (delete, update, remove): always show a preview of what will change, wait for explicit confirmation before calling the tool. 5. TRUST = VERIFIED STATE Every write must echo back the verified_state from the tool response. Not a guess. Not a summary. The actual returned data.
project · Systemimprovementsexpensestrusthallucinationgiuliausername